Wait what? Doesn’t this mess with the whole underpinnings or am I reading that wrong? The nips changing portion. And doesn’t that mean it’s an attack vector for something malicious?

Also I have two thoughts on knowing who is working on protocol level dev: 1) I have been wondering who exactly is involved here and didn’t know if I just hadn’t researched it yet and thus didn’t know or if it wasn’t public 2) I know it could lead to harassment of the devs so I can also see why someone might want to remain anonymous.

57 of 99 I think I need to spend some time on GitHub to understand how that’s even possible …

Reply to this note

Please Login to reply.

Discussion

The vast majority of projects in open source are open and transparent. Nostr is well below par on that front, it is an open protocol, but barely. What is needed is a community driven nostr, which is open, and everyone knows who controls it. People can build closed or proprietary things on Nostr, and that is fine. But the base protcol should be open and not owned by anyone, no matter how well meaning.

Annnnd I didn’t realize it wasn’t. 🤦‍♀️ It’s absolutely implied that it’s fully an opensource project.

BUT I would also be ok with the idea of there being a core team working on the first portion of the protocol simply for speed’s sake as long as there’s an opensource audit going on with the team listening to feedback (you can’t take action or prioritize everything all at once and some people don’t get that too. Gets tiring watching people scream at devs who are in fact trying to listen but are also trying to get something to the next stage as well.)