my blog https://overreacted.io

nit

+2 -2
+2 -2
public/where-its-at/index.md
··· 271 271 272 272 A DID Document really *is* like an internet passport for an identity: here's their handle, here's their signature, and here's their location. It connects a handle to a hosting while letting the identity owner change *either* the handle *or* the hosting. 273 273 274 - ![](./9.svg) 274 + ![did:web:iam.ruuuuu.de is bidirectionally connected to the swappable @ruuuuu.de handle, and points to swappable blacksky.app hosting](./9.svg) 275 275 276 276 Users who interact with `@ruuuuu.de` on different apps in the atmosphere don't need to know or care about his DID *or* about his current hosting (and whether it moves). From their perspective, his current handle is the only relevant identifier. As for developers, they'll refer to him by DID, which conveniently never changes. 277 277 ··· 328 328 329 329 Let's visualize this: 330 330 331 - ![](./10.svg) 331 + ![did:plc:fpruhuo22xkm5o7ttr2ktxdo is bidirectionally connected with the swappable @danabra.mov handle, and points at swappable morel.us-east.host.bsky.network hosting](./10.svg) 332 332 333 333 Although my handle is `@danabra.mov`, the actual server storing my data is currently `https://morel.us-east.host.bsky.network`. I'm happy to keep hosting it there but I'm thinking of moving it to a host I control in the future. I can change both my handle and my hosting without disruption to my social apps. 334 334