···255255256256```js
257257{
258258- avatar: 'https://example.com/dril.jpg",
258258+ avatar: 'https://example.com/dril.jpg',
259259 displayName: 'wint'
260260}
261261```
···283283284284```js
285285{
286286- avatar: 'https://example.com/dril.jpg",
286286+ avatar: 'https://example.com/dril.jpg',
287287 displayName: 'wint'
288288}
289289```
···647647648648Now we need somewhere to host this document, and some way for you to edit it.
649649650650-Let's revisit the "centralized registry" from approach #2. One problem with it was using handles as permanent identifiers. Also, centralized is bad, but why is it bad? It's bad for many reasons, but usually it's the risk of abuse of power or a single point of failure. Maybe we can, if not remove, then reduce some of those risks. For example, it would be nice if could make the registry's output self-verifiable.
650650+Let's revisit the "centralized registry" from approach #2. One problem with it was using handles as permanent identifiers. Also, centralized is bad, but why is it bad? It's bad for many reasons, but usually it's the risk of abuse of power or a single point of failure. Maybe we can, if not remove, then reduce some of those risks. For example, it would be nice if we could make the registry's output self-verifiable.
651651652652Let's see if we can use mathematics to help with this.
653653···661661}
662662```
663663664664-To resolve a link like this, we ask the registry for the document belonging to `6wpkkitfdkgthatfvspcfmjo`. It returns current your hosting, handle, and public key. Then we fetch `com.twitter.post/34qye3wows2c5` from your hosting.
664664+To resolve a link like this, we ask the registry for the document belonging to `6wpkkitfdkgthatfvspcfmjo`. It returns your current hosting, handle, and public key. Then we fetch `com.twitter.post/34qye3wows2c5` from your hosting.
665665666666Okay, but how do you update your handle or your hosting in this registry?
667667···671671672672(More on the trust model [in the PLC specification](https://web.plc.directory/spec/v0.1/did-plc).)
673673674674-With this approach, the registry is still centralized but it can't forge anyone's documents without the risk of that being detected. To further reduce the need to trust the registry, we make its entire operation log auditable. The registry would hold no private data and be entirely open source. Ideally, it would [eventually be spun it out](https://docs.bsky.app/blog/plc-directory-org) into an independent legal entity so that long-term it can be like ICANN.
674674+With this approach, the registry is still centralized but it can't forge anyone's documents without the risk of that being detected. To further reduce the need to trust the registry, we make its entire operation log auditable. The registry would hold no private data and be entirely open source. Ideally, it would [eventually be spun out](https://docs.bsky.app/blog/plc-directory-org) into an independent legal entity so that long-term it can be like ICANN.
675675676676Since most people wouldn't want to do key management, it's assumed the hosting would hold the keys on behalf of the user. The registry includes a way to register an overriding rotational key, which is helpful in case the hosting itself goes rogue. (I wish for a way to set this up with a good UX; most people don't have this on.)
677677
denlukia.bsky.social