I've noticed that too. This is not hard to solve, if the person writing the NIP wants it to be found. They can do a NUD, or they can submit a PR to the NIPs repo to link to an external NIP, which is also something that exists. But if people don't want to make sure people know about their own standards, there's not much anyone can do.

1) Most standards don't need to be found by most devs because they don't use them. Nobody uses all of the NIPs, either, after all, and that effect is about to go parabolic. I think everyone just needs to sort of give up on spec management. 2) It's not impossible to find them. There is a list in the wiki for events or you can simply use elasticsearch on nos.today. Or just #asknostr. Make a DVM spec discovery tool. 3) You can see the events popping up on relays and just search for the ones that seems stick around for a while and add them to the list yourself. This is dynamic discovery and someone already built it.

Undocumented Nostr Event Kinds Tracker

4) I don't need an event to announce the event that I'm publishing on relays and writing about in the wiki and in articles and discussing in communities. That's the same event being announced like 50 times and would encourage people to reserve NUD numbers that they don't end up using, or having NUD numbers assigned to unpopular events, like we have with the NIPS. This creates an ID "honeypot". 5) We don't need the "NUD". We have our own prefix. It's obvious that it is a Nostr spec, if it deals with Nostr and is a spec. 6) Implementations should lead. Marketing is proof of work. The best implementation will get the most attention and their spec will float to the top of the wiki or dominate the timeline for the people interested in that topic, and become the de facto standard. 7) We publish our specs on the wiki or other long-form articles, give the event a searcheable identifier, and then we implement it and talk about it all on Nostr. That gives everyone enough opportunity to find it, who is genuinely interested. https://wikifreedia.xyz/nip-event-register/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl

You basically announce what you are doing. If others like it, then they will also use, even help refine it. Point me to the exact places in the spec to help me find information i need to know - an address. Or a comment someone said on nostr relating to the situation. Sure, things could be super mixed up, but you could weight opinions or endorsements to find the best way to find your answers. There are ways to filter out noise, or they will be found because of need. I wrote two specs on Nostr Knowledge Bases (NKB). How can we navigate nostr's information, on any event. I'm not a web developer, so I have 2 NKBIPs out there (wikifreedia), asking for fast feedback and quick iteration. If people really like an idea, but if its not actively being worked on, other's can still see and work with it. There may be changes, but wouldn't that be good? The original author can still be in the conversation.

Yeah, you basically need an index. That's the github nips repo README. Of course, it's incomplete because people don't submit PRs to it, but it's there. Wikifreedia's #nud tag or something else could also serve as an index. We just have a tragedy of the commons because these things (or some thing thing) aren't being used.

> We don't need the "NUD". We have our own prefix. Apparently, but this is the first time I've heard about NKBIPs. The least you could have done is mention it on the github repository. We're directionally aligned here, I just really don't understand the hostility toward the existing forum for talking about nostr.

TIL about NKBIPs. Are these conceptually the same as NUDs?