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. - ThreadSky

didd.uk • 174 days ago

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.

Comments

didd.uk•173 days ago

1/ If you're wanting to make a did:web, there's a few tools around. These are the two I recommend:
* https://github.com/afternooncurry/bsky-did-web (👍 @afternooncurry.net)
* https://bskydidweb.pages.dev/ (👍 @goeo.lol)

didd.uk•173 days ago

2/ As with anything, check to make sure any of these tools are updated. did:web's can me made incorrectly, and if this happens, deleting the account will have consequences: Bluesky's AppView counts a deletion of did:web as permanent. Test it out on a throw-away subdomain at first!

didd.uk•173 days ago

3/ A few extra caveats:
* You cannot migrate between DID methods: your DID is tied to your account forever
* Be wary of potential domain/TLD takedowns (see: .io fiasco). If you lose that domain, you lose the account. Stick to the registrar policies and don't be 100% trustful of ccTLDs/gTLDs

didd.uk•173 days ago

(right, I'm done now, @fry69.dev — WhiteWind article coming soon 😄)

nicejs.codersquack.nl•173 days ago

📌

didd.uk•174 days ago

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

didd.uk•174 days ago

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!

lathrys.at•173 days ago

oh hey i’m one of those people :)

didd.uk•174 days ago

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

didd.uk•174 days ago

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

didd.uk•174 days ago

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

didd.uk•174 days ago

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.