Hacker News Reader

Comment by evbogue | Hacker News Reader

Yah it clearly has always done this, but why doesn't it support multi-PDS replication?

But you're right that the screenshot proto and the copy and paste proto are quite successful as a distributed system these days.

View on HN

There's nothing stopping multi-PDS replication right now. It would work fine. No one would know that content is available elsewhere, is kind of the main chicken-and-egg problem.

Hubble is starting to come online, which is a network cache. With excellent storage and runtime characteristics, cheap to run. I'm not sure if this is in the same https://microcosm.blue banner-head, but the same developer, as another incredibly fantastic network service that's open for use, that's open source, that other people can also run themselves. https://atproto.com/blog/introducing-hubble-a-public-mirror-...

I agree that yes the PDS's hopefully start doing more mirroring too. It'd be nice if they would themselves also attest that they have seen it too.

Having the content available everywhere seems like the definition of a distributed system to me. Hashing content is not a discovery issue, one simply iterates over a list of hosts and asks if they have the msgs by their hash.

What would be the upsides and downsides of that? It’s unclear what you’re asserting. Do you just want IPFS?

IPFS already exists. What I want is distributed Bluesky, since it's a product success and I do like most of the proto and the team. Do you want to fix this? I just spoke with Claude and I don't think it'd be too difficult these days for us to fix this in the core product.

Upside: data is always available even if Bluesky's funding is pulled. Downside: we lose deletes.

Reply on news.ycombinator.com