Yeah, the system does cache handle lookup results and it is possible for a handle to end up in a bad state. Do you recall how long it has been since you first tried? The cache is 24 hours from what I remember.
Comments
Log in with your Bluesky account to leave a comment
Hmmm, it sounds like result has got stuck in the cache and will require manual intervention from Bluesky support to clear the cache (I think their current backlog is a few weeks `[email protected]`). The resolution process is separate from the cache so the HTTP .well-known method will not fix it...
...in theory at least, but you could try that. If you don't have a web server running for that domain, you could use GitHub pages (should only take about 5 mins to set up (create repository, link domain, add `.well-known/atproto-did` file) or you could use our hosted service (https://handles.net).
@jason.goecke.net put together a quick template for GitHub Pages in case you do want to try using the HTTP .well-known method without a web server: https://github.com/prompt/bsky-verify-with-pages :)
Comments