How does a note get published — reuse publications/sites, or note-specific? #234

Activity

1. brianorwhatever

   added

   wayfinder:grilling

   on Sep 2, 2026
2. brianorwhatever

   added a parent issue on Sep 2, 2026

   • Wayfinder: notes on boop — signed, publishable, verifiable #227
3. brianorwhatever

   marked this as blocked on Sep 2, 2026

   • Where does a note's prose live in the lists model? #228
4. brianorwhatever

   self-assigned this

   on Sep 30, 2026
5. brianorwhatever commented on Oct 3, 2026

   

   brianorwhatever

   on Oct 3, 2026

   ContributorAuthor

   More actions

   Resolution

   • A note publishes through publications, not sites. It gets one publications row and the same DID shape as a list, {authorDid}/resources/list-{id}. No new tables and no third path.
   • Why not sites: site keys are custodial (siteKeys, encrypted by boop), so a site DID proves that boop hosted the page, not that the author wrote it. It would also give the note a second identity beside its did:cel.
   • A published note lives at a path on boop.ad, the same route lists use today (/public/:did). It has no hostname of its own; custom domains for notes are fog.
   • A stranger sees the last sealed version. The public page renders the sealed text held inline in the envelope (What does a note's signature commit to, and when does it seal? #229), never noteBodies. Edits after publishing only reach the public page when the author re-publishes, which appends a new sealed version.
   • Publishing a note grants the same access as a list: anyone signed in can edit the draft, so the permission rules stay as they are.
   • What the build inherits: publishList (convex/publication.ts) currently throws "Notes cannot be published"; that guard is replaced by the Pro gate (Does a note consume list quota? #230) plus the seal. getPublicList must return the sealed body from listEnvelopes for a note, PublicList.tsx needs a note rendering, and the owner needs an "unpublished changes" state when the draft differs from the last seal.
   • Open follow-up (not decided here): because anyone signed in can edit the draft of a published note, the draft is not private (getNoteBody uses canUserViewList), and the next re-publish can seal other people's text under the author's key. At build time this needs either a diff shown to the author before sealing, or a revisit of read-only access for published notes.
6. brianorwhatever

   closed this as completedon Oct 4, 2026