nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z isn't it too much purism to include an ["alt", "a short note:
Discussion
I think something like https://github.com/nostr-protocol/nips/pull/1828 is a better solution. Someone must do something about it.
I was going to propose to deprecate Alts. They don't do anything.
So all clients need to know about all kinds even if they don't deal in them, and render their own alt string, and only fallback to something generic like "unknown event kind=230987" if the kind number wasn't coded at all (new kind, or not documented kind). ? I like that. Less data.
Yes, but the point is that "knowing" is cheap, doesn't require any code and can be just slurped from someone else's registry.
Turns out maintaining such a registry is not a task easy enough that can be done in 15 minutes.
I got it started here: https://github.com/fiatjaf/alts
If someone else is better at dealing with AIs than I am maybe you can try making it more useful because aside from the kinds I manually edited most are very useless (well, actually they're not entirely useless, since they have the event kind "name", which is something).
I think we should probably remove the {{pubkey}} and {{created_at}} from the templates, as clients can just always show these anyway, an in a nicer manner than a vague text, since they're present in all events.
Not really. All they need to do is to open an njump.me (or similar) preview for the unknown kinds or just implement nip89 and send to other clients. Either way, Alts are not a good solution.
another thing I was too lazy to implement and now is already getting deprecated. love when this happens lol
What if an app was able to embed another app specialized on loading all kinds of nostr events by just adding an iframe set to "44billion.net/+
I think that the one that builds such nostr "special app" to load event kinds, if well done thus used by other apps, kinda will dictate what is the "official" event structure for each nostr kind.