What about adding "status" and "topic" fields to the event register, and maybe adding a second dimension to the events?
Discussion
Then we could sort the list by topic, instead of number, since numbers are easily searchable in the browser, but it's confusing to have the events for similar things spread over the list.
Or do y'all need the event numbers listed in order?
Feel like the numbering was just up for grabs anyway instead of order created/priority etc. Now being a distributed registry, makes even less sense.
Just say its the "{name} nip"
Yeah, the kind and NIP ID order never actually had any significance. It's ordinals used in a system that isn't sequential. 😂
Nostr apparently had a shitcoin after all 🙃
😂
I feel like we just liberated all of Nostr from the tyranny of numbers that don't actually count anything, but are actually just names. 😂
That's been driving me absolutely bonkers. 🤣🤣
Why are they numbers?
We like numbers.
This is why we are years in and still debating what a Kind 01 note is. Is it a tweet/microblog, a comment/reply, a generic/basic note ...?
What is a 01 note????????
Is it about non-english speakers?
Total guess. Just throwing it in there lol. I shouldn't comment on this lolol but here I am
But they almost all program in English. And if you can't read the letters, you can still just copy the word as a string.
I mean, it could just be a nonsense string, right, or a foreign word, or some sort of combo string like tweetstat03. It doesn't have to make any sense.
Yeah true. I just wanted to guess lol
Good guess. 😂
But the reason why I see it as a problem is that numbers imply order and these don't have any particular order, once you get past 00 and 01.
But the ordering of numbers allows a dev to just reserve 6000-10000, and come up with some harebrained scheme were he uses kind numbers as counters, or something.
And numbers are more limited because they're fewer characters to combine. You can get more combinations out of a short string than a long integer. That's why our keys contain letters.
So, no upside, but some downside.
using letters thins out the possible meaningful namespace, but 32 bits human readable has been a tradition for a long time, macOS has used this format for file type magics forever and i've also used this format in my own binary encodings
totally there would be a way to compress them into a single number meaningfully, probably you could even have them as long as 6 characters and have almost no collisions just by simply summing the ascii code of each letter, and you can compress it further by allowing 3-6 instead of all 6
Life in the background!
I'm from the RFC-age... – https://www.rfc-editor.org/standards#IS
We're they not already?
By dimension, I mean that I'd add a field to the table for sub-events, to the right of the main-events. Or add a field to label them as one or the other.
Right now, they're just listed flatly, but in order.
Sorry, forgot the link to the register
https://wikifreedia.xyz/nip-event-register/dd664d5e4016433a8c
We need an extensible Nostr browser. Something more robust than JS to let you customize the UI. It won't be funded, so best hope is to beg existing client devs and get ignored. 😀
These changes would, of course, turn the list into something that could be easily exported, parsed and filtered, so that might open up interesting use cases.