decentralized social network: https://jazco.dev/2025/02/19/imperfection/
Discussion
Isn't a "lossy timeline" just nostr? :)
Yes, it is, but they have that same feature on a big central server now.
Maybe time isnt required, but order (sequence).
Nostr signing to outbox could include a sequence kv (tag, number) - e.g. public:665, dm: 34323. You declare in outbox who can fetch your current sequences counts.
Would let clients find dropped posts, and let users know what they have signed.
What about just an incremental nonce per npub (like in web3)?
While a post feed can be more lossy 😅 with some other features like notifications or message I would think most like to have a consistent feeling
Interesting to see how nostr will try to handle these tech design trade offs
With being decentralized as main objective, I would expect to see lot of features moving to the edge of the network
Latency being the least important factor … personal nodes could handle lot of the heavy lifting
â–‘â–‘â–‘â–‘â–“â–“â–‘â–‘â–‘â–‘
â–‘â–‘â–‘â–‘â–“â–“â–‘â–‘â–‘â–‘
â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“
â–‘â–‘â–‘â–‘â–“â–“â–‘â–‘â–‘â–‘
â–‘â–‘â–‘â–‘â–“â–“â–‘â–‘â–‘â–‘
â–‘â–‘â–‘â–‘â–“â–“â–‘â–‘â–‘â–‘
â–‘â–‘â–‘â–‘â–“â–“â–‘â–‘â–‘â–‘
> This means each user gets their own Timeline partition, randomly distributed among shards of our horizontally scalable database (ScyllaDB), replicated across multiple shards for high availability
Typical decentralized infrastructure
ahahahah
This was painful to read:
"This process involves looking up all of your followers, then inserting a new row into each of their Timeline tables in reverse chronological order with a reference to your post."
https://news.ycombinator.com/item?id=43105028
Sadly no comments citing Nostr, 3/4 refer to Mastodon.