Replying to Avatar PABLOF7z

I don't agree with that;

I think if generic clients had a way to parse "unknown events" in a way that makes sense of them, the experience can be perfect.

Think about a picture; someone shares one as a kind 1. People comment on it. A discussion ensues. You want to be able to see what your follow list is discussing around that picture.

A song, a list, a highlight, an item for sell, anything is the same thing; if done publicly, it should be done in a kind 1. That's the cool thing about nostr; data flows unencumbered, not siloed.

What we need is a way for clients to be able to render and discover handlers for unhandled kinds.
Avatar
bu5hm4nn 2y ago

Maybe it would still make sense to additionally define a 5th parameter to "e" tags for the root event where the replies carry the root kind. So [ "e", "", "", "root", 31337 ] for example.

Reply to this note

Please Login to reply.

Discussion

Avatar
PABLOF7z 2y ago

nothing special to be done there; this should already be the case since the `a` tag of the root is tagged.

Avatar
bu5hm4nn 2y ago

I’m trying to avoid the client to have to retrieve “root” events the user chose to ignore. So if you receive a comment, it would be good if the client can filter it directly.