Gigi and 21 others @Gigi and 21 others - 4d
who is building the "other stuff" client that ignores all kind1s and helps me surface cool new kinds and apps and stuff
Leo Wandersleb @LeoWandersleb - 4d
I had been tracking kinds back in the old days of nostr. https://npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6.blossom.band/6ccfc8b154bfe842825c834b74d33c0d8d2512c5df375ce64389605876fc528c.png You can watch the events scroll by and learn about their types but it's not very accessible yet. https://nostr.info/relays/
don't tempt me with a good time!
👀
Silberengel @Silberengel - 4d
Yeah, getting harder and harder to keep kind 01 from being a madhouse, with everyone dumping everything into it.
2 minutes. Give or take 2 minutes.
Geez.
Laeserin @Laeserin - 4d
We are permissionless, so the client dev can define what he'll tolerate, for himself. Our clients include "m" and "M" tags, in addition to tags, and we can filter for those. They're more useful than kinds, without breaking from normal Internet standards. https://wikistr.com/nkbip-06*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319
*in addition to "kind" tags
Laeserin @Laeserin - 3d
Not yet. Would be good for the wiki, so that people can fork and add their own stuff.
The idea comes from nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku and I thought it was brilliant and immediately added it to my Sybil-created events. Have a single-letter tag means you can filter for it, on the relay, in stages.
In order to find 30040s, for instance, you could say, please filter for all metadata events, or filter for all metadata events that are indexes, or filter for all metadata events that are indexes and replaceable, and get a narrower set of results with each step. M: meta-data/index/replaceable You could do the same with articles or notes or etc. It creates nested categories.
Maybe. I don't know. It's a long and detailed list that a small group of people manages, which is already a nightmare with the NIP repo. As soon as you want to build something new, that isn't on the Lexikon list, everyone refuses to host your events and the Official Lexikon Committee can completely censor your development. The Lexikon also demands the use of MIME types, like in our "m" tag.
I prefer kinds precisely because they're sort of vague, and there are so many numbers free to choose from. They give relay admins and client devs control over what they display. That should be a conscious choice. We added in more clarify with m/M, and gave people the ability to characterize their events and figure out "what is this", and we have kind 1111 comments, now, but that shouldn't replace the development freedom allowed by kinds. People complaining about there being too many kinds, so everything should be Kind 01 and we just use a lexicon, are sort of missing the whole point of the protocol: that it frees the users, but it also frees the developers.
mleku @mleku - 3d
it's based on two things about how tags and filters work 1. single letter tags are indexed so finding them is fast and selective 2. the match on the second field (all elements after [ "#x", "<value>", ... ] are prefix matches, whatever your <value> is, it matches if the candidate event tag has that same prefix. i don't know if that is explicitly stated in the NIP-01 spec but that's how fiatjaf implemented it in Go for go-nostr. so, yes, it enables precisely this kind of thing, where you have general -> specific segments of the tag string. Tag strings are limited to 100 characters but that is plenty for concise multi-segment values.
Because it's documentation in a central registry.
that's a terrible name btw, just sayin'
i'd use "communitions" as a kinda subtle joke about how cryptography was once categorised as a weapon
Everyone should be able to delete or not delete what they want. And everything can be cloned and/or stored, so why should I care what they do with it?
I suspect we are. I'm a fan of the chaos. It's creative destruction. Devs that can't keep up don't make the cut.
