I don’t actually want to do this right now, but I do want to know if it’s really decentralized yet. Completely looks like it means each of:
- A client ✅
- A personal data server ✅
- A relay ❓
- Labelers ✅
- Feed generators ✅
It looks like the relay might be the bottleneck. If I’m understanding the protocol correctly, a relay could consume less than the whole network so it doesn’t have to be ridiculously expensive to operate, but I’m not finding examples of people doing it.
ive been asking about this for a long time. ive yet to be presented with a non-bluesky controlled relay instance. this is a lynch-pin of the protocol and prevents true federation.
happy to be proven wrong someday, but bluesky is just twitter with user-contolled nodes. they can decide to remove nodes at their whim.
This is a good breakdown. A firehose relay takes TB’s of storage and is not practical for self-hosting, and AppView isn’t hostable yet: https://alice.bsky.sh/post/3laega7icmi2q
A firehose relay takes TB’s of storage
which is similar nonsense which ActivityPub has with replicating whole datasets everywhere… cept its one company controlling the whole shebang. its a failure of design.
My friend, it’s not nonsense, it’s basically how decentralised communication has to work if you want any reasonable level of recency & history in the data.
Usenet was basically the original and I believe a modern news provider requires something like 50 petabytes of storage to run a 10 year data retention service
