@coracinho @mcc #bluesky is like Mastadon amd makes a big deal of being decentralised, any one can run a server or build a client and interoperate, just like email.
This annoyed people because it wasn't practically possible to run a Bluesky server yourself, the demands for storage etc were wild.
#Blacksky are seeming to have made progress in doing so.
Post
No replies yet
Be the first to share your thoughts.
@falken @coracinho Also the *way* in which Blacksky is making progress seems to me to make it look improbable any of the rest of us will reproduce what Blacksky has done. It's taken months of Rudy's time and he's had to purchase storage for "terabytes" of data because *standing up a new Blacksky "instance", in a total sense, requires literally mirroring everything posted on the network*, including spam and old inaccessible chats on people's https://stream.place streams
@mcc @coracinho huh. Still!
Don't suppose there is a write up somewhere that digs into it? Like, rather than mirroring the firehose, could they not store new stuff, and fall back to grabbing from Bluesky if missing.
@mcc @coracinho @falken This is the best writeup on bluesky's decentralization I've seen which gets very in the weeds. Christine is an expert on decentralized communication and one of the authors of the ActivityPub spec that powers fedi so I don't think you'll find a better analysis
https://dustycloud.org/blog/how-decentralized-is-bluesky/
@Eliot_L @mcc @coracinho and it answers my thought about what why #blacksky can not just fetch on demand.
"
[in #bluesky unlike #fediverse ] there is no directed delivery; if you want to see replies which are relevant to your messages, you (or someone operating on behalf of you) had better sort through and know about every possible message to find out what messages could be a reply.
"
Which is bonkers.