Oddbean

yes, exactly, there would be a page for every kind in a wiki there wouldn't be NIPs at all, these are some dumbshit idea that presupposes the existence of a working protocol that does enough to be usable nostr is not at that level yet, how long was it between the inception of the bitcoin network and the inception of the BIPs? a lot longer than it's been here, that's for sure and yeah, unfortunately that's the chaos of the protocol at this point - you have to pick a client or several clients and examine their outputs to understand what you want to do for automated processing and not just dumb relaying if you'd asked me about mentions i would have referenced what i have seen in raw JSON of mention containing events, and the "mention" string in the tag and the "nostr:bech32" thing were both part of that, and i only caught the gist of that because of Uncle Bob's client using the prior scheme with tag-numbered references in square brackets a wikimedia style wiki, like the one used to run wikipedia, would totally work, with the same "staff" manning the moderation roles as the non-searchable git repository with zero-information numbers referencing everything and creating an in-group of people who have memorised them due to building - mainly - clients building actual smart relay services is outside of that bubble and the guys inside it have been insulated from reality for so long that they think they are invincible and omniscient

put it this way, i could convert the repo, and all the PRs into the wiki version in a week, but i got bills to pay and i have to spend 20 hours a weak at least on earning an income, so, unless someone wants to pay me equal to 700 euros a week to run the wiki i'm busy doing things that are paying me that much

there can be a transition first step is migrating the data into the new format next is keeping track of the way the data being put into it is disorganised, and especially investigating the actual code of those who are contributing to measure against what they have pushed to their PRs i don't think a whole new protocol is required, just some competent, adequately paid moderators who make sure vandals don't mess up the talk pages and make them useless it just really doesn't translate to a git repository do you want to have 65535 separate folders for kinds? they have to exist!

Do you know who is that person capable of meticulously classifying all the things all day every day? Also why can't we keep the current system but have that amazing person do the job on the side? It would be great and eventually people could naturally transition to the new document since it would be better and more complete as the person could also incorporate Blossom and other rogue specs that exist out there.

for example, a kind, could be 'managed' by a set of all client teams that implement that kind. when an implementation diverges, the kind is categorized into client sections or pages (depending on how combative). a page or section that describes a client implementation and is maintained by that clients team.. that way the updates can flow. people can subscribe to the kinds to get notified of changes to them (another pain point of the git strategy)

it doesnt have to update the nip unless everyone agrees.. im just looking for more data on how things are used. right now i have to try every client, and i dont have an iphone so i have to find someone that does to try it for me. if it was in a wiki, this would help a lot. one example is quote notes. another is as i found today all clients need a "mention" in the tag to mention someone, yet this is not in nip01 all clients have already moved onward to some other nip that uses kind1 new ways. i also frequently search for nip-Xx or a, keyword, or kind # and github doesnt show results for it .. some of these specs have updated (like zaps?), so its not like they never do, and right now theres no feed for this. anyway, i know this would be quite an effort and require some hosting etc.. just brainstorming what might augment the git

Endorsements, weighted endorsements, how would that be different? How many forks and edits would be concerning? Popularity is likely power law distributed - find the one that is most popular and implement that, or you can try something else and let it compete with the rest. In any case: nostr:nevent1qqswszxz7tcj2e0hh70tjd58plum89cd753q0vs2gszetc5v72t0p6spr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqp2ewuqq

I don't even understand the point of this conversation. We already moved all of the NIPs and the event register to Nostr's wiki months ago. I don't even look at GitHub anymore and I don't need to use some other wiki.