We need to address this and work towards building consensus. The ecosystem feels somewhat fragmented and unclear, largely because the specification being implemented is frozen and resides in a pull request, making it difficult for everyone to fully understand. This often leads to custom implementations. However, this is a broader issue with the NIPs themselves tho. Dvmdash calls can be a good opportunity to discuss these challenges and make the specification evolve. Wdyt?
Discussion
I think nothing. Im not disagreeing that not everything is consistent, im not disagreeing that some things could be better, but thats the way when multiple people build things "their way". I'm pissed af that 1) everytime i tried to bring some clearance to nip90 it gets a stalled PR and 2) calling the whole thing a mistake instead of actually working to improve these minor things. 3) Most major Clients, besides Damus, implemented Dvms. The arguments are invalid.
Realize that is the key to moving toward something better. I believe we can find clearer and more effective ways to define specifications that are widely implemented. The current NIPs model doesn’t work well, it should have a standardized way to expose current implementations and their adoption. I’ve already written about this without much success, and you’re definitely not the only one frustrated by it.
But these are the challenges of building on a permissionless protocol with a form of "centralized" governance. That said, I think Nostr is worth the effort, and we should dive into this to find a better model.
On the other hand, I think, identifying some pain points is a good first step. It sheds light on the issues. But I get you mate, sometimes it’s incredibly frustrating 🫂
You gotta practice what you preech. There are 15 open PRs on the DVM repo and mine has been open since Feb 5 with 0 comments.
Yeah, I was doing fast track compared to the nip repo last year (and I was just one of the persons on the repo) and then people write Longform article about how for this kind this parameter is inconsistent and for that kind that tag is stupid. I hope you will receive comments by either someone familiar with the topic or by a longterm grantee who is currently paid to work on Nostr and is competent enough to discuss every single little parameter up and down for months and then, when they are happy, fingers crossed, merges your pr.
Because this is exactly what this discussion is about.
Maybe we could start with some ground rules. Like, never send a web coder to do an engineers work.
Don’t stop pushing for this. You’re doing the right thing