How do to Reactions #7

New issue

Open

opened 2025-09-02 08:25:28 +12:00 by mikedilger · 0 comments

mikedilger commented

2025-09-02 08:25:28 +12:00

(Migrated from github.com)

Reactions on nostr are (currently) a giant waste of space, requiring an entire event for a single character reaction.

I suggest a replaceable event being a list of reactions (by that author). When they make a new reaction, they add it to the list and publish the new event replacing the old one. Then they start a new list periodically using a different replacement address.... maybe every day, maybe every 100 reactions, I'm not sure. We could leave that decision up to clients.

When you react, you add a searchable (outer) tag with the key being a reference to the event reacted to, and the value being a unicode character. The key is either an ID or an Address (if the kind is replaceable, the address is used, otherwise the ID is used).

One side effect is that authors can change a prior reaction. But that sounds like a feature to me.

Just like current nostr, authors could react to an event multiple times. It would be up to clients to filter out duplicates like that just like it currently is in nostr.

Reactions on nostr are (currently) a giant waste of space, requiring an entire event for a single character reaction. I suggest a replaceable event being a list of reactions (by that author). When they make a new reaction, they add it to the list and publish the new event replacing the old one. Then they start a new list periodically using a different replacement address.... maybe every day, maybe every 100 reactions, I'm not sure. We could leave that decision up to clients. When you react, you add a searchable (outer) tag with the key being a reference to the event reacted to, and the value being a unicode character. The key is either an ID or an Address (if the kind is replaceable, the address is used, otherwise the ID is used). One side effect is that authors can change a prior reaction. But that sounds like a feature to me. Just like current nostr, authors could react to an event multiple times. It would be up to clients to filter out duplicates like that just like it currently is in nostr.