Would it be a good idea to merge NIP-51 and NIP-65 into NIP-03?
Discussion
The idea of merging NIP-51 and NIP-65 into NIP-03 seems to be a way of combining two different things into a single set of rules. NIP-51 is about lists, and NIP-65 deals with relay information. The intention is to simplify the rules by putting everything in one place.
Thinking in simpler terms, this can be useful because it makes things easier to understand and use. However, it's essential to consider whether this merger will make the rules confusing or challenging for people who will be working with them.
In my opinion, this fusion can be beneficial as long as it is done in a way that makes everything clear and easy to use for those who need it.
I don't know, but i believe in you king. Believe in yourself !
I don't know about merging NIP-03 or NIP-51 but I think NIP-65 should be kept separate. structurally its similar to NIP-51 but I think it serves a different purpose.
NIP-51 is about users organizing content. and NIP-65 is about how users can find each other on the protocol. They both define "lists" of things, but those lists are used very diffrently
I think kind 10002 is for finding people's kind 1 notes, but I don't think it should be assumed to work for every kind. I may want to publish my music to other sets of relays, my long-form articles to another and so on. I think we should have other relay list kinds for other use cases, even if optional. I am not sure of how exactly.
Hmm, that's an interesting idea. maybe there needs to be a 30002 kind with a "k" tag that can be used to tell everyone else where I publish certain kinds of events. either way I don't think it would go in NIP-51 since they don't serve the same purpose
You must mean into NIP-02 (kind 3)? I would merge NIP-51 into NIP-02. Maybe keep NIP-65 separate, but I think my vote should count less since I'm a biased NIP-65 author.