Pretty sure nostr does not suck. Just no one can agree on how to fix what is broken and make it better. That is why we need to become a DAO with community consensus voting.
So instead of waiting for the guardians of the nips to decide on something from their tiny throwns of power.
We the people can vote on what is really important and implement features that are truly needed.
Nah dude, you really just need me to live long enough to post more dev bounties. What actually works matters more than whatever a democratic mass of idiots think would work
Here is the issue. When you have a protocol where fixes need to be made. Improvements need to be done. Yet no one can agree definitively on how to proceed forward. On a platform (GitHub) run by an evil organization. Controlled by a select group of individuals (Guardians of the Nips). What you get is a clusterfuck of people going off in their own directions deciding what is important. While rarely agreeing on what to do in order to move forward gracefully.
By giving power to the people who can vote on the issues. By utilizing a combination of sats and proof that they are humans who are active within the community who pass a web of trust background. The developers will no longer stop ignoring the problems if they wish to remain in line with the protocol.
Right now as it is Nostr is like a bunch of independent kingdoms running around in different directions doing many things that they THINK are the most important. While having a loose affiliation by choosing which nips to implement, or ignore completely. Paying dev bounties does nothing but promote alliances within certain nostr kindoms that benefit certain clients. Not the protocol as a whole.
Right now I am watching Nostr fragment before my very eyes. Developers are giving up, because they have very little leadership, direction, or can collectively agree on anything that would improve the situation. Our market share is diminishing. People leave every day due to either broken clients, or lack of engagement. If we do not find a way to come together NOW as a community to improve upon our situation. Buckle down, be more professional, start working with consensus public voting out in the open. On our own git servers funded by donations. Then we are going to die a slow painful death as a protocol.
This is the hard fact of life. Adapt, or die. We are not adapting to fix problems, or innovate fast enough. We just have a bunch of people bitching on their own that Nostr is dead. Instead of manning and womaning up to patch our shit and get to work. We need to revamp this protocol and reassess our situation from the ground up. This means focus groups. Taking surveys from the community. Asking we the people what we need. Then working together to make it happen now.
You're worried about nostr fragmenting. I am too.
A big worry of mine is a JavaScript-based P2P nostr taking off before a JavaScript-free nostr takes off. That could lead to fragmentation that's really hard to fix.
We can split paths without fragmenting so badly if the path splits like this -
1. The web-compatibility-focused, semi-centralized JavaScript-and-relay-server-based branch
2. The pure-decentralization-focused, P2P JavaScript-free branch
These 2 branches can just talk to each other, translate nostr:nevents between each other's formats, and be useful enough at different times to be worth the tradeoff, without it becoming too much of a clusterheck to patch it all together and keep clients and users "near" other clients and users.
I forgot to say geographically neutral. The P2P JavaScript-free geographically neutral branch vs the English-centric-web-compatibility-focused branch
I am not sure we are at the forking point. Although we are getting pretty damn close.
If we can't figure out a way to come together and rally the Nostr ostriches to agree on a solution. Then yes. We are going to get some forks from the ever growing number of frustrated developers. Who are quite frankly from what I have been hearing so frustrated from the broken state of things and half assed coding. That they want to claw their own eyes out (their words not mine).
This is a problem. A VERY BIG FUCKING PROBLEM. Developers should be excited, hopeful, and are enjoying the process of innovation. Not being hindered by a lack of focus, consensus, half assed vibe coding, lack of proper testing, and overall positive direction as a protocol.
Did you see my "3 simple suggestions" post on my profile just now? You might appreciate it
