Welcome to the Republic of Nostr.
Where
- the NIP repo owners are the supreme court
- the developers are the legislators
- and the npubs are sovereign

Welcome to the Republic of Nostr.
Where
- the NIP repo owners are the supreme court
- the developers are the legislators
- and the npubs are sovereign

If you think of your developer as your NIP-deliberation representative, that gives you pause, doesn't it?
Do we all want to be represented by the same person?
Does that person share our Nostr values?
Does that person contemplate the wider impact of his decisions?
My fellow npubs:
Who are you sending to the table, where the protocol is written?
Or "her", of course, cuz there's me. π
There are devs who build NIP implementations that aren't Twitter-clone clients, so we understand how those clients work and take an interest in the PRs, but we're more impartial about which particular client to use.
Few know this.
good analogy - 2 key players in my view - 1. Dev implementing those NIPs in Relay / App and 2. Users really need/using/adopting it those feature in MAJORITY
a good WIDE ADOPTED NIP (not push for sake pushing enforcing) is measure of success , less wide adopted NIP or standard means if didnot become popular enough to plebs/users.
Yes, some NIPs should probably be rewritten or rolled-back, for lack of end-user enthusiasm.
Protocol spam, basically, like old laws about the proper method for weighing salt in trade for horseshoes. π