Nostr should give you control of which NIPs you want to adhere to. It should not have to be up to the developers forever.
In that way, users could show support for one NIP to be implemented vs another in a decentralized manner.
Users could show support for specific NIPs or capabilities and enable them after some period when it becomes available.
It's seems most users express themselves by choice of client plus notes and issue trackers. I think it'll quickly become clear which NIPs make it.
Love the chaos of early days personally.
I disagree. If you don’t like the set of features for the available clients, make a new client.
I don’t appreciate the illiterate telling publishers that authors shouldn’t write books.
I think just keep it light. Do without doing.
NIPs should just be documentation of something observed in the wild and already in use by users.
Honestly, users never know what/how things get developed.
Best is for devs to create things and users/market chose which projects to use. That sends market signals to devs to then chose which nips/features are in real demand.
🎯💯
I'm not sure if this is true. Allegedly Steve Jobs said something along the lines of:
'Some people say, "Give the customers what they want." But that's not my approach. Our job is to figure out what they're going to want before they do. I think Henry Ford once said, "If I'd asked customers what they wanted, they would have told me, 'A faster horse!'" People don't know what they want until you show it to them. That's why I never rely on market research. Our task is to read things that are not yet on the page.'
“You’ve got to start with the customer experience and work back towards the technology.” -Steve Jobs
This quote suggests that while it's important to innovate and create new technology, the ultimate goal should be to provide a positive experience for users. In other words, companies should start by understanding what users need and want, and then work to create technology that meets those needs.
This approach may not always involve simply giving users exactly what they say they want, but rather understanding the underlying problems they're trying to solve and creating solutions that address those problems in new and innovative ways.
The cool thing about NIPS is a user can propose one and get what they want AND devs can also propose one to address underlying problems in innovative ways.
These are not mutually exclusive.
