Just came up with a new plan for fixing replaceable events with @semisol
The biggest issue with replaceable events (contact lists, profiles, lists,) is that there is no versioning scheme. This leads to many issues where your contact list is dropped, comments+likes+zaps appearing only on older versions of a post, etc.
We need a concept of versioned events in nostr and a way of querying those effectively. Looking forward to working with @semisol on this and implementing it in Damus, nostrdb and hopefully strfry once we figure it all out.
Thread
Login to reply
Replies (2)
discussion: 📃.txt
ohh.. I thought somebody would go for a Unified Format type of thing. :(
You should probably specify what happens when Clients filter for replaceables. I am willing to bet very few clients add a limit 1 to get only the latest update. They might end up receiving all historical events if relays are now keeping the entire history and we change the way the filter works.