Skip to main content

Module foreign

Module foreign 

Source
Expand description

The deployment’s one reader for records in repositories it does not hold.

didbot-lookup is the cache and the fetch; this is where a running server’s own facts reach it — which repositories it already holds, which names it answers to, and whether this stack may fetch from its own network. One reader per process, not one per session: plan/ai-preference.md’s “one resolver, one cache, deployment-wide” is the difference between being a good guest on somebody else’s server and being the traffic that gets a deployment defederated.

Structs§

Hosted 🔒
The registry, answering “is this ours?” for the reader.

Enums§

Document 🔒
What a DID document fetch from elsewhere found.
DocumentError 🔒
Why a DID document fetch from elsewhere found nothing.

Functions§

fetch_document 🔒
Fetches did’s document from url, which didbot_identity::document_url gave for it, through a client pinned to the addresses it checked.
reader 🔒
The reader this deployment gives its evaluators.
serves 🔒
Whether host is a name this deployment answers to: an account’s document or handle, or anything in or at the apex of one of its zones.