3 ms·
From https://atproto.com/specs/handle https://atproto.com/specs/handle section "HTTPS well-known Method" It is unclear where the handle query goes However, yo
by verdverm 2y ago
From https://atproto.com/specs/handle https://atproto.com/specs/handle
section "HTTPS well-known Method"
It is unclear where the handle query goes
However, you don't need a document per day. It can be dynamically generated by a handler or server less function on that route. This is important as employees at an org change, this information could be obtained from a database
You can for example: `curl https://verdverm.bsky.social/.well-known/atproto-did https://verdverm.bsky.social/.well-known/atproto-did`
So for an organization, one might have a single handler responding to `*.atproto.company.com/.well-known/atproto-did` with the subdomain becoming the primary input variable
- xeonmc 2y agono, like I said I already know that .well-known/atproto-did returns the DID value, but there doesn't seem to be any documentation for where the inquirer will next expect to fetch the actual DID document to complete the circular verification.
- verdverm 2y agoThis peer-thread might offer us some clues: https://news.ycombinator.com/item?id=42750241 https://news.ycombinator.com/item?id=42750241 `curl -s "https://plc.directory/$(curl https://plc.directory/$(curl -s https://verdverm.bsky.social/.well-known/atproto-did https://verdverm.bsky.social/.well-known/atproto-did)" | jq .`