What do you think of the idea discussed at the beginning of https://www.youtube.com/watch?v=kk1x0Bjtes8 about creating a new short text tag that can be added to any weird new event kinds so clients that don't support these kinds can render that as a fallback?

Reply to this note

Please Login to reply.

Discussion

I'm in favor of specialization and not showing stuff that doesn't matter for a particular client.

For example: I don't want to see every single comment that someone adds to a "Google Doc" in my social feed, even though it might be a nostr event.

I think that’s a valid point. otherwise everything could just be kind 1 with application-specific tags.

Seems appropriate, we have alt text for Web media that doesn't show, with Ada also coming into play

This seems like a good idea for accessibility but also doesn't solve any problems for clients who are grabbing every note.

I don't think clients should request a kind unless they explicitly support it. Not all kinds are meant for timeline/social feed consumption.

It's not for requesting, it's for rendering references.

👍

I think an inheritance system would be better. Any kind could extend a simpler kind that has easy to render fallbacks if the client doesn't know how to deal with the more complex kind.