Raw JSON

{
  "kind": 30023,
  "id": "3a23e84ce080fe0ffeacae13974957d08ffee7148f4f9c8565181ef2f6967057",
  "pubkey": "af70ff513cc8f7428085fb8415f6ba402a5fbc1cab6382caa65530338ef07bdd",
  "created_at": 1773443890,
  "tags": [
    [
      "d",
      "discussion-laboratory-v01"
    ],
    [
      "title",
      "Nostr Improvement Possibility — Discussion Laboratory v0.1"
    ],
    [
      "summary",
      "Loose conventions for anchoring discussions so experiments and results reconnect to where the question started."
    ],
    [
      "t",
      "nostr"
    ],
    [
      "t",
      "nip"
    ],
    [
      "t",
      "discussion"
    ],
    [
      "t",
      "governance"
    ],
    [
      "t",
      "protocol"
    ],
    [
      "t",
      "proposal"
    ],
    [
      "t",
      "proposal"
    ],
    [
      "published_at",
      "1773442824"
    ]
  ],
  "content": "# Nostr Improvement Possibility — Discussion Laboratory v0.1\n\n## Human Description\n\n### What this is\n\nNostr conversations generate a lot of interesting sparks — ideas, questions, rabbit holes worth exploring.\n\nPeople often go off and look into those things on their own. Sometimes they run experiments, find sources, or learn something useful. But those results rarely make it back to the original discussion.\n\nThe effect is a bit like hearing a news story with no follow-up. You know something happened, but the outcome never quite reconnects to the place where the question started.\n\nAn alternate pattern might look like this:\n\n- someone proposes an idea\n- others explore it or challenge it\n- experiments or research happen\n- people report what they found\n- eventually someone attempts a synthesis\n\nIn practice that sequence rarely appears.\n\nNostr already contains many of the pieces needed for it though. This document is an attempt to see whether a few simple conventions could help those pieces line up often enough to make discussions easier to follow and build on — in the open, without requiring specialized clients.\n\nNothing here is strict. These are loose conventions meant to help conversations produce useful knowledge.\n\n---\n\n## Core Idea\n\nEvent kind **30023** defines a living discussion document that can evolve over time while keeping related discussion anchored to a stable address.\n\nReplies reference the document using an **`a` tag** (`30023:\u003cpubkey\u003e:\u003cd-tag\u003e`), allowing experiments, reports, and discussion to remain connected even if the root document updates.\n\nRole tags (`proposal`, `experiment`, `report`, `synthesis`) signal the purpose of replies so clients and indexing systems can organize the discussion.\n\nExample root event:\n\n```jsonc\n{\n  \"kind\": 30023,\n  \"tags\": [\n    [\"d\", \"topic-id\"],\n    [\"title\", \"Example topic\"],\n    [\"t\", \"proposal\"]\n  ],\n  \"content\": \"\",\n  \"created_at\": 0,\n  \"pubkey\": \"...\",\n  \"sig\": \"...\"\n}\n```\n\n---\n\n## Event Types\n\nNotes may include tags describing their role in the discussion.\n\n```\n[\"t\",\"proposal\"]     # introduces an idea\n[\"t\",\"experiment\"]   # describes an attempt or test\n[\"t\",\"report\"]       # results or observations\n[\"t\",\"synthesis\"]    # summary of current understanding\n```\n\nThese tags are signals rather than strict requirements.\n\n---\n\n## Anchoring Replies\n\nReplies SHOULD reference the root document using an address reference (`a` tag).\n\n```\nkind: 1\n\n[\"a\",\"30023:\u003cpubkey\u003e:\u003cd-tag\u003e\"]\n```\n\nA relay hint MAY be included:\n\n```\n[\"a\",\"30023:\u003cpubkey\u003e:\u003cd-tag\u003e\",\"wss://relay.example\"]\n```\n\nUsing the address reference ensures replies remain connected even when the root document is updated.\n\n---\n\n## Poll Events\n\nPolls and votes MAY be used as lightweight coordination tools.\n\n- **kind:1068 — Poll event** (question and options)\n- **kind:1018 — Vote event** (response selecting an option)\n\nExample poll:\n\n```\nkind: 1068\n```\n\nExample vote:\n\n```\nkind: 1018\n```\n\n---\n\n## Simple Models\n\nBasic exploration\n\n```\nroot document (kind:30023)\n        │\n        ├─ proposal\n        ├─ experiment\n        │      └─ report\n        └─ synthesis\n```\n\nDiscussion and friction\n\n```\nroot document (kind:30023)\n        │\n        ├─ proposal\n        │\n        ├─ discussion\n        │      ├─ counterpoint\n        │      └─ clarification\n        │\n        ├─ experiment\n        │      └─ report\n        │\n        └─ synthesis\n```\n\n---\n\n## Loose Conventions\n\n1. Root document MAY update as understanding improves.  \n2. Replies SHOULD reference the root address.  \n3. Experiments SHOULD include evidence when possible.  \n4. Reports SHOULD describe what actually happened.  \n5. Syntheses summarize the current state of the discussion.\n\n---\n\n## How to Find These Events\n\nDiscovery mechanisms are intentionally left open for experimentation.\n\nPossible approaches may include:\n\n- filtering by `kind:30023` root documents\n- indexing replies that reference the root via the `a` tag\n- searching for role tags such as `proposal`, `experiment`, `report`, or `synthesis`\n- relay or client-specific indexing strategies\n\nDifferent clients and indexing systems may experiment with their own discovery methods.\n\n---\n\n## Open Questions\n\nFuture exploration may include:\n\n- spam handling\n- web-of-trust weighting\n- contributor credit\n- bounty distribution\n- poll coordination\n- AI summarization or indexing\n- how discussion events are discovered or indexed\n\nThese are not required for the discussion laboratory to function.\n",
  "sig": "0a202a74ff9f677e7d4bff0d34d584a32457b1b24445f1fb7fc62dd8b88a3f24791f5ef52032723d63b4a7d43d81d81e1afc5b234840d4592054b603a04eff60"
}