nips
nips copied to clipboard
nostr-protocol
NIP-71: NUDs
Permissionless NIPs.
https://github.com/nostr-protocol/nips/blob/nuds/71.md
@pablof7z @mleku @jb55 @staab @vitorpamplona @Semisol @arthurfranca @mikedilger
I think it's a good idea.
I wish relays could indicate support. supported_nuds ?
I am not sure if we need to change the name from NIP to NUD (to me they are the same thing), but great idea.
We could migrate all NIPs to NUDs with a random key out there.
Then we just need a way for Clients to declare compliance to each one and a website to rank them by compliance and boom, no need for this repo anymore.
I like NUDs because NIPs have numerical IDs, eg supported_nips is a number[]. supported_nuds is a string[]
Plus my wife will not roll her eyes every time I say NUDs.
That's a stronger point than the original.
Plus my wife will not roll her eyes every time I say NUDs.
You know this is going to be pronounced "nudes" right? The joke can't not be made, especially alongside "nips".
SNED NUDS
At this point, I think @fiatjaf does these things on purpose. It's all about marketing.
-- Says the owner of "SheetStr"
i want to see the abolition of this repository in favor of a wikifreedia subject/entry and associated tree of linked articles (with human readable labels instead of stupid numbers)
ACK!
@mleku i want to see the abolition of this repository in favor of a wikifreedia subject/entry and associated tree of linked articles (with human readable labels instead of stupid numbers)
It may be worth testing the idea of decentralizing ~NIPs~NUDs by making this repo stop accepting new NIPs. The repo's README.md could be converted to a explanation of what are NIPs (explain it isn't adding new entries) what are NUDs, with a link to a wikifreedia "NIP" (I guess singular title instead of plural as wikipedia does?) article authored by fiatjaf/official-nostr-npub with what is currently the README.md content (also the article would need to link to nip-01, 02, .. etc articles also authored by fiatjaf/official-nostr-npub) and a link to a "NUD" article (but this time not from a specific author).
Does wikifreedia have article comments? If not, meanwhile this repo could continue being used for new NUD discussions.
The NIPs repo is one of the main things holding Nostr together. To abolish it would be brave but retarded. How about we see how well this new thing works first. Has anybody published a NUD yet? What is the best client for doing so?
The NIPs repo is one of the main things holding Nostr together. To abolish it would be brave but retarded. How about we see how well this new thing works first. Has anybody published a NUD yet? What is the best client for doing so?
Yeah, seconded. We need the tools to publish and read nostr-native NIPs before it can become a useful source of information. Maybe wikifreedia can be co-opted to support them. But that has to be built first.
I may be wrong but I think NUDs won't become a thing if this repo keeps accepting new NIPs. The current repo maintainers may curate NUDs by writing a "NUD" article with a shared key.
I may be wrong but I think NUDs won't become a thing if this repo keeps accepting new NIPs.
NIP numbers are scarce and they're about to end.
NIP numbers are scarce and they're about to end.
Alright the 01 to 99 range I suppose. I guess niche specs such as #1094 don't deserve a rare NIP slot but are free to become NUDs.
i like it, now we just need to get the wikifreedia polished up a bit more so this kind of thing can become normal
i did a lot of work making a more human-readable way of mapping out the structure of the protocol, and it is a lot easier to navigate and learn
i think the key thing to understand about this is that NIPs tend to be too narrow, with the exception of the first one, that you end up with this giant index in your memory "now what is 42? what is 59? what is 3?" instead of a mnemonic word or phrase that makes it patently obvious what it relates to, that can be stacked under subections like how i did with envelope types and the top level envelope parsing flow logic in my nostr library ( https://github.com/Hubmakerlabs/replicatr/pkg/nostr )
We can't fetch only NUDs, right? For example, do we need
["l", "nud"]?
You can fetch by #c: ["Nostr"] to get all the nostr-specific things
You can fetch by #c: ["Nostr"] to get all the nostr-specific things
Can you? What is this c tag about? I've never heard of that.
Can you? What is this
ctag about? I've never heard of that.
Probably the c tag is a category. I opened #1270.
I am not sure if we need to change the name from NIP to NUD (to me they are the same thing)
Agree, it would get messy and confusing to have a two tier system. Just call it an early stage NIP. Right now getting a NIP through the NIP approval process is too heavy a lift for most developers. Let NIPs evolve like FEPs do.
The whole point of Nostr was supposed to be an outlet for developers to experiment, tinker and express their creativity. It's not that at all, right now. The solution is to have NIPs go through stages of maturity, which is in the spirit of bottom-up open source development.
