Not sure if separate kind 20 for image posts is a good idea, but added support to iris.to anyway

Reply to this note

Please Login to reply.

Discussion

support for display that is

kind 20 started appearing in my popular feed so had to add support or hide them

It is because it allows clients to be developed that only care about that kind and none of the kind 1 bullshit we have to deal with.

It could have been done with a label tag without breaking interoperability. Now clients need to add custom handling for kind 20 or hide them (when people react or reply to them)

Yeah, but not all clients need to add this. It's the same for the video events. If you don't have a player, it doesn't make sense to add.

Iris will continue to use kind 1 instead of kind 20 for image post creation:

* Works on most clients, doesn't break existing clients' reaction / reply based feeds

* Kind 1 events reach larger audience than 20

* No added complexity, no different handling for kind 20. Keep nostr client implementation simple.

* Clients that don't support images can just show the text content, or filter out notes that have images

* Clients that only want images can filter out posts that don't have images

* Optionally, they can use ['l', 'picture-first'] or similar tag for relay indexing of image posts

nostr:nevent1qgsy2ga7trfetvd3j65m3jptqw9k39wtq2mg85xz2w542p5dhg06e5qpz3mhxue69uhhvct4d36zu6tjd9ejuar09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqzqpdj0dmmuqxgt4u6xe86au3zyh6v2lkq9xzpuajdrqusv4n0fm3yqskns0