i should start did:web-ing again, its been too long

Oh no, I just began to clean this account up to reboot it — not entirely sure what I obliterated there 😔

Also worth mentioning, like a did:plc, once a did:web account is deleted: that's it, its burned forever. Some apps can handle a recreated did:web, but Bluesky's AppView treats it as the end game (and, tbf, that should be the way all AV's should treat the event)

Ah yes, I feel like I should have mentioned the inability to:
* See the handle history (no "ops" like with did:plc)
* See when the account was truly created (the date conjured up by Bluesky's AppView is unreliable)

7/ As an extra caveat, ATProto has the possibility to support extra DID methods in the future, so think about this when designing your identity resolving code. Do *not* assume 'did:plc' as the default (i.e. don't use that on an 'else' clause). Futureproof your stuff: your future-self will thank you.

6/ And, there you go! You've supported did:web, and made the small minority of us extremely happy. 😊

5/ 3) Fetch the DID Doc from the well-known path of the domain (i.e. 'https://didd.uk/.well-known/did.json')
4) Consume the DID Doc as if it were a 'did:plc' — from this point on, your code can remain exactly the same

4/ To support our accounts:

1) Resolve the handle to the DID, as normal; this time, the DID will return as 'did:web...' instead of 'did:plc:...' (e.g. @didd.uk is 'did:web:didd.uk')
2) Pull out the domain from the 'did:web:...' (i.e. 'didd.uk') — do not assume the domain is the same as the handle

3/ Currently, there are ~50 did:web users here. While that may not seem like much, this number has been slowly increasing recently as tools now exist to make setting up a did:web much more accessible. Plus, we're all frankly some real cool people who would love to test your ATProto thing out!

2/ For some background, ATProto currently supports did:plc and did:web. did:plc requires you looking up against plc.directory to receive the "DID Doc", whereas did:web is entirely self-hosted by the user.

did:web 101 (a thread)

So, looks like someone sent you to this post because your app doesn't support did:web. That's cool, it's relatively easy to fix.