nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe about the first point, now these events are kind 1 instead of 20 with a k tag with 20 as a value? Is this correct?

Reply to this note

Please Login to reply.

Discussion

correct

Why? 🧐

Because there is no compelling reason to break compatibility with kind-1 clients, anything that is possible with kind 20 is also possible with kind 1 + k-tag 20.

Isn't that up to the kind-1 client to decide to include kind 20 events?

I was surprised that my new created event was also showing up in other apps now, while that was not my intention. Now I need to use another client for specific kind 20 events..

Is this change somewhere documented in an updated NIP which I missed?

When other kind-1 apps also add kind 20 support your posts would show up there against your intention so you would need to find another solution not based on kind numbers.