This creates an ecosystem that is much harder to associate with the identity of random events online. You can't simply query a relay for all messages from a user. You have to download everything and do the work.
Discussion
Imagine if the protocol removed the pub key field. Now, no event is verifiable unless you:
- Verify every message against all Nostr profiles - all keys (proof of work)
- You have a small list of friends and you only verify their messages.
Sounds like a brand new protocol: Monerostr
I couldn't find the NIP that says pubkey is a required field. :)Ā So... š¤·
It doesn't say pubkey is required. Some of the other fields are definitely not required (we have seen events without tags). So.. Maybe it's still open to an experiment? :)
Itās hard to tell if you are being facetious or just joking. Probably joking because of the emoji at the end xD You are joking, right?
Related to the idea? No. I think it would be a better social network.
Related to the spec? Kind of. Specs are hard. If you leave it open, somebody will create and start mixing their events with the regular events in the network. And NIPs are trash right now.
I seriously hope that questions like these can help solidify where the community is and change the spec for the better.
I think NIPs could be worded better, but more words donāt necessarily mean itās better. Look at DID wall-of-text and the first thing that comes to mind is: I donāt have time to read all this crap.
If you have suggestions on the NIPs to improve wording and make things more explicit I and you I ask you to please submit your recommendations on a PR. This is the only way things can get better is by people pitching in.
It's not about the wording. It's about clarity. NIP authors simply have not had enough clarity themselves to know where the boundaries of the protocol are. And boundaries are the only thing that matter in specs.
I agree, DIDs went overboard. And yes, I am submitting PRs.
Thank you for the PRs. This is a community effort after al!
Discussion is upĀ https://github.com/nostr-protocol/nips/issues/135
š
š¤