SilberWitch on Nostr: The problems with everyone working with NIPs as permanent PRs is that * people keep ...
The problems with everyone working with NIPs as permanent PRs is that
* people keep starting new PRs to cover the same topic, rather than joining in the working group that already exists
* without a NIP ever being merged or listed, there's no reference point, for newcomers
* the NIP never reaches a frozen state, as you leave the PR discussion and come back and files have been added and whatnot, and it's like, At which point in this PR thread did I implement this NIP?
* there are almost 600 PRs, already, and Nostr is still relatively small
* some PRs do actually get merged, but there's no clear criteria or schedule for merging, so it just looks like favoritism
* all of Nostr's use cases are documented and discussed primarily on GitHub, which is embarrassing for a communications protocol (i.e. "the developers of Nostr don't want to use on Nostr")
* people keep starting new PRs to cover the same topic, rather than joining in the working group that already exists
* without a NIP ever being merged or listed, there's no reference point, for newcomers
* the NIP never reaches a frozen state, as you leave the PR discussion and come back and files have been added and whatnot, and it's like, At which point in this PR thread did I implement this NIP?
* there are almost 600 PRs, already, and Nostr is still relatively small
* some PRs do actually get merged, but there's no clear criteria or schedule for merging, so it just looks like favoritism
* all of Nostr's use cases are documented and discussed primarily on GitHub, which is embarrassing for a communications protocol (i.e. "the developers of Nostr don't want to use on Nostr")