Guys! How do you decide what number for a new “kind”?
What is the consensus on testing new kind and new NIP concept?
Do we just pick a number that we like?
I’m trying out something new for parameterised replaceable events, so I simply just pick a number that I like that is between 30000-39999?
#asknostr nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
👀 working along these lines as well.
Long shot but maybe nostr:npub1tfrzlfsyfd9cmgcc229xnpaytcadlqet68ryh453p6k0an0sw4qszua36t knows 🐶🐾🤷♂️
from what i understand a lot of developers check to see what's not in use then just kind of pick whatever number they feel like.
I think nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft called "yolo driven development"
Curious what the thought is. I link something that may inspire from amateur radio. The situation is clearly different. But I do wonder if some thought could go into breaking up the kinds into zones of use. From hypothetical use cases and leaving large swaths open for experimentation to be detailed later. https://www.arrl.org/band-plan
pick a number that looks good and unused. If more people use it the same way it may be de facto standard. I believe fiatjaf tends to publish when 2+ developers embrace it.
Hash the contents of the NIP, then add each character to each other until you get to a number that fits the boundaries.
You skipped the “bech32 the hash” part
Any unused number is fine.
