He's in a big conglomerate and they let everyone choose their own JIRA tags and within 6 months, there were so many JIRA tags that you type the letter "A" and you can go get an coffee while the list loads.
Discussion
A bit different though, a nostr client doesn't have to load or know all kinds, just the ones that it needs for the feats it wants to use. The event payload doesn't really matter for kinds. But related yes I think there can be a risk of having multiple things using specific kinds for their use cases that when they could all be using the same.
The problem is in the reservation of entire ranges and everyone including the top number. Lots of people will include 3000 or 55000, for instance.
And what if there are 2 apps using 3000, and you only want to read from one of them?
And I didn't even think of people using kinds/tags as counters. I'm like, Wow, that's really stupid.
But a lot of developers are stupid.
That was the thing. He made me realize that kinds are tags, not IDs.
They seem like IDs because they're numbers.
I think you can use tags do differ them. In this scenario i think it's "d" tag. Ephemeral events also use specific tags for each app, but as a client you don't even have a way to prevent others apps to misbehave, like Vitor P. Issue of people sending DMs with kind 1. A client app cannot do nothing about it.
Yes, people can simply use the wrong kind.
Probably really tempting because of the numbering. 1 is an easy, nice number. Otherwise, you have to go find the appropriate number and it won't be as nice. 981 or something.
Seems sort of silly, but there's a psychology to numbers. People will always start counting at the smallest number, so implementations will cluster most at the smallest numbers.
Same with the NIPs. They're in numerical order. Everyone reads NIP-01 and you've lost nearly everyone by NIP-25.
Only way to get people to pay attention to the kind and NIP content is to remove information from the numbers.