Nostr Web Client

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.

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.

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

i wrote it up as a draft spec originally on github - just to have it out there. I'm not asking any change to the protocol, but ideas on how events can be organized and retreived. Its been on github since December, but its gotten way more visibility and feedback here.

Cool, I missed it on github then. The spec on wikifreedia seems much more generic than NUDs, almost a competing spec to the wiki one. So maybe it's not as applicable as I thought?

Generic is the point, i wouldn't say it competes however. A wiki has a spec for their articles. This spec is attempting to distil ideas individually so they can be worked with an grouped together. It comes with a 30041 which is very related to wikis 30023, but 30041 are just fragmented notes - and wouldn't be typically be shown by themselves. 30041 basically is an indication that it belongs to something broader - you can decompose a existing blog or paper, or you can just publish a modular article with the explicit concept that the ideas can be separated.

You'd show them as a modular article, or note collection, via 30040 which can be a collection of any event type. I wouldn't expect any client other than what we are making to display the individual fragments.

that stands for Nostr Knowledge Base Implementation Possibility because it's a spec describing how to form a knowledge base.

a spec for a specific use case, not a new type of spec

Ok, so NUDs are a new idea then? What do you dislike about them? They seem to solve most of your complaints, in that they're:

- Permissionless

- Published in a wiki format

- Forkable and can be voted on

- Nostr-native

I personally don't have a problem with the specific idea. An NKBIP can perfectly have a NUD tag if someone wants to add it, i just don't think it adds more meaning than NKBIP.

Not an argument against a NUD, just that if things are already going to be so different, a global naming convention wouldn't make sense, and that NKBIP announces the purpose within its name.

There's value in posting a spec in a real wiki event.

fiatjaf 1y ago

Standards are necessarily centralized, you can't have each person use their own standard.

https://undocumented.nostrkinds.info/

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.

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

> 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.

Why should we go back there?

We are trying to move all of our interactions to Nostr, not away from it. We are putting our code and our documentation where our ♥️ is.

If you decide you want to change a venue in real life, you don't just show up at the new one and expect everyone to be there.

Y'all built the venue. I assumed that you would all be arriving, eventually.

Would you and/or nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hszxmhwden5te0wfjkccte9ehx7um5wfcxcetzwvhxxmmd9uq35amnwvaz7tmwdaehgu3ww35x2umpd4jkxct59e5k7tcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qguwaehxw309a6xsetrd96xzer9dshxummnw3erztnrdakj7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hszrnhwden5te0dehhxtnvdakz7qpqm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqtqc5tv like to come on the TGFN podcast to talk about it?

This topic, i don't know if I'd be too comfortable talking about 😅

Yeah, it's ehspicy. I was looking at your profile to find out more about you, but didn't really find anything. Do you have a project you work on I could read about?