Why? 🧐
Discussion
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.