Expand description
The handle the operator goes by, for the homepage.
The operator poll already reads the operator’s DID document on every
tick. Its first valid alsoKnownAs entry is the handle the operator
claims, and the claim counts only once the handle resolves back to the
same DID: atproto’s bidirectional rule, the one
didbot_operator::names applies on the command line. The answer is kept
here until the next tick, so the page never waits on the network and a
visitor cannot make this server fetch anything.
The check runs in a task of its own, under LOOKUP_TIMEOUT. The tick
that read the document goes on to the operator’s claim without waiting
for it: a slow resolver delays a name on a page, never the claim the
grace window and the e-stop are driven by.
The handle resolves through crate::handles, asking the
DNS-over-HTTPS resolver [operator] dns_resolver names. The HTTPS fetch
refuses this deployment’s own network, like every other fetch the poll
makes to a host a document named.
Structs§
- Operator
Handle - The operator’s handle, as the last poll tick verified it.