danabra.mov / overreacted
my blog https://overreacted.io
fork atom

Fix small typos in A Social Filesystem #2

open opened by denlukia.bsky.social targeting main from denlukia.bsky.social/overreacted: main

Thank you for another great article, Dan!

Labels

None yet.

assignee

None yet.

Participants 1
AT URI
at://did:plc:ikbkczooeq5mxyajup725udb/sh.tangled.repo.pull/3mcvk4orbdg22
+5 -5
Diff #0
unified split
+5 -5
public/a-social-filesystem/index.md
··· 255 255 256 256 ```js 257 257 { 258 - avatar: 'https://example.com/dril.jpg", 258 + avatar: 'https://example.com/dril.jpg', 259 259 displayName: 'wint' 260 260 } 261 261 ``` ··· 283 283 284 284 ```js 285 285 { 286 - avatar: 'https://example.com/dril.jpg", 286 + avatar: 'https://example.com/dril.jpg', 287 287 displayName: 'wint' 288 288 } 289 289 ``` ··· 647 647 648 648 Now we need somewhere to host this document, and some way for you to edit it. 649 649 650 - 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. 650 + 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. 651 651 652 652 Let's see if we can use mathematics to help with this. 653 653 ··· 661 661 } 662 662 ``` 663 663 664 - 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. 664 + 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. 665 665 666 666 Okay, but how do you update your handle or your hosting in this registry? 667 667 ··· 671 671 672 672 (More on the trust model [in the PLC specification](https://web.plc.directory/spec/v0.1/did-plc).) 673 673 674 - 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. 674 + 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. 675 675 676 676 Since 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.) 677 677

History

1 round 0 comments
sign up or login to add to the discussion
denlukia.bsky.social submitted #0
1 commit
expand
65645f78
Fix small typos in A Social Filesystem
no conflicts, ready to merge
expand 0 comments