Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What about when Bluesky goes out of business and plc.directory is shut down?

This all seems unnecessarily fragile.



To strongman the article, I imagine that's the reason behind:

> Bluesky is currently moving PLC to an independent legal entity in Switzerland to address some of these concerns. The AT community is also thinking and experimenting.

(The article has links there.)


I've also linked to https://updates.microcosm.blue/3lz7nwvh4zc2u and https://plc.wtf/ which are relevant. These are good questions to ask!


What happens when the independent legal entity stops getting funding and has to shut down?


The content can be mirrored, and being content-addressed with an algorithm the client verifies, the mirror can’t tamper with any of it. Switching to another DID method like did:ipfs is also a possibility. It’s not a perfect solution to every possible disruption, but it’s a system designed to evolve in response.


Need a PLC+DHT thing maybe? Or maybe someone will try to blockchain?


What happens when the blockchain goes out of business, doesn't have enough hash to ensure security, or rugpulls?

The PLC is arguably equivalent to a proof-of-authority ledger


I was trying to be funny. That did not work.

I do think some DHT like things could help. On AT if you lose your domain it's a disaster (right?) I'm foggy on the move to new domain for identity process.


For most people on AT, losing your domain is not a disaster because very few people use did:web (100s) and the PLC allows for changing your domain based handle without losing everything. This is one of the PLC's core enablements


This is no different then how the web works. So not a great argument against this protocol.


How does it improve over the existing system, other than slapping the word "decentralized" on?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: