the most logical solution for follow list hell would be shifting the storage of follow lists to a consensus driven data system, so you can just add and remove instead of blasting out the new version every 5 seconds as you click follow on a thread with a hell client that enables insta-following
or a modification of the "replaceable events" protocol that allows you to just send a change that is +/- pubkey each time and that the database keeps them together and prunes off the outdated data
it's a problem that probably nobody wants to deal with but it has a nasty collision with the limitations of websockets and the inefficiency of hexadecimal encoded pubkeys
in fact, you could just add a add/remove protocol to this it just means that searching for this kind of event has to be exhaustive like a bitcoin utxo provenance verification (which is most of what the processing in initial block download is for)
mleku / mleku™️
npub1fj…mleku
2024-05-10 14:04:58
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2024-05-10 14:04:58Event JSON
{
"id": "5a103b37e12b1d2230ce883c2901ed1e3eab463b6c7d2cd8b63a1da672a2f3d2",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1715342698,
"kind": 1,
"tags": [],
"content": "the most logical solution for follow list hell would be shifting the storage of follow lists to a consensus driven data system, so you can just add and remove instead of blasting out the new version every 5 seconds as you click follow on a thread with a hell client that enables insta-following\n\nor a modification of the \"replaceable events\" protocol that allows you to just send a change that is +/- pubkey each time and that the database keeps them together and prunes off the outdated data\n\nit's a problem that probably nobody wants to deal with but it has a nasty collision with the limitations of websockets and the inefficiency of hexadecimal encoded pubkeys\n\nin fact, you could just add a add/remove protocol to this it just means that searching for this kind of event has to be exhaustive like a bitcoin utxo provenance verification (which is most of what the processing in initial block download is for)",
"sig": "589a9ecc88a06adb6ab8b4e7189a956e317abc6bce44921920d4001d761c7fbf80a0319dd9be815d907db4641bea635dfe663fa45b571d9daaffa93756b83e86"
}