Oddbean

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.