Module document 

Reading the server’s own did:web document: the parse, the id check, and the signing key it publishes.

The fetch itself belongs to whoever has a network — didbot-claim over HTTP, a page over fetch. Everything a caller does with the body it got back is here, so both read the document the same way and refuse the same documents.

Enums

SigningKeyError

Why the server’s document does not yield a usable signing key.

Functions

did_json_url

The URL hostname’s did:web document is served at.

did_of 🔒

The did:web a hostname spells; see [didbot_identity::did::did_web_for_host].

parse_did_document

Parses body as did’s document, checking its id against what was asked for.

parse_document

Parses body as hostname’s DID document, checking its id against what was asked for.

signing_key

The document’s #atproto signing key, checked to be a public key atproto actually verifies commits with.

usable 🔒

multibase, once it is known to be a public key on a curve atproto verifies with.