←back to thread

When imperfect systems are good: Bluesky's lossy timelines

(jazco.dev)
768 points cyndunlop | 3 comments | 19 Feb 25 17:48 UTC | HN request time: 0.606s | source
Show context
nightpool ◴[19 Feb 25 18:05 UTC] No.43105223[source]▶
Note that all of this reflects design decisions on Bluesky's closed-source "AppView" server—any federated servers interacting with Bluesky would need to construct their own timelines, and do not get the benefit of the work described here.
replies(4): >>43105263 #>>43105526 #>>43105578 #>>43106325 #
1. evbogue ◴[19 Feb 25 19:27 UTC] No.43106325[source]▶
My thinking has evolved on this topic significantly as of late. My current thinking is we should create a secure gossip network on top of the Bluesky API, and forgot about all the DAG-CBOR stuff that gets stripped from the Jetstream. Hash the posts on the gossip layer and if posts change then diff them. This is all prep for when X billionaire buys out Bluesky then we just pop some signing key crypto on top of this gossip layer and wow! It's distributed!
replies(1): >>43107283 #
2. pfraze ◴[19 Feb 25 20:34 UTC] No.43107283[source]▶
isnt that ssb?
replies(1): >>43107376 #
3. evbogue ◴[19 Feb 25 20:40 UTC] No.43107376[source]▶
reverse-ssb