Skip to content

What does a stranger see when verifying a published note? #232

Open

Description

@brianorwhatever

Part of #227

Question

What does a stranger see when they verify a published note?

This is the product. A reader with no boop account, no wallet, and no idea what a DID is lands on a published note and must come away confident about who wrote it and that it has not been altered.

Open: what is on the page by default vs behind a click? What words are used — "verified" is a loaded and often-abused term. What does failed verification look like, and what does "altered since publish" look like as distinct from "edited, and here is the history"? Does verification run client-side against the DID log, or is it a claim boop makes?

Note that this problem is unsolved for lists too — whatever is decided here likely applies to the whole product.

Resolve with /prototype. Blocked by the sealing decision, since what can be shown depends on what the signature covers.

Activity

  1. brianorwhatever commented on Oct 8, 2026

    @brianorwhatever
    ContributorAuthor

    Input from #244/#286: a seal is signed by a device key registered in the author's did:webvh. Verification resolves the author's DID history and checks the device key was authorized at seal time. The page has to present 'signed by (from device D)' without making strangers understand delegation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions