Thread

The NIPs repo has been going downhill recently anyway. Bad specs getting through, good specs being stuck for no reason, etc.
Dustin Dannenhauer's avatar Dustin Dannenhauer
@fiatjaf why delete something that’s gaining momentum? We’re already past 4 million DVM events, kind 5300 is crushing it, and deleting the spec without recommending anything better doesn’t help. https://stats.dvmdash.live/kind-stats Each DVM kind can have its own flow, NIP-90 flow is a suggestion, not a requirement.
View quoted note →

Replies (8)

This is why the VC bro cult and their lackeys should be ignored. Uncreative, selfish people are clearly not in it for the good of the protocol. This best get fixed now. This is a foundational issue. Foundations need to be firm. Cracks are showing that will cause untold horrors in the future.
semisol's avatar semisol
The NIPs repo has been going downhill recently anyway. Bad specs getting through, good specs being stuck for no reason, etc. View quoted note β†’
View quoted note →
↩ replying to α΄›Κœα΄‡ α΄…α΄‡α΄€α΄›Κœ ᴏꜰ α΄ΚŸα΄‡α΄‹α΄œ
Yeah, it's so massive that any selection has become arbitrary. Doubt it's possible to even review all the PRs, anymore. I don't think we need approval, anyway. We've all de facto switched to implied action, for everything but the most core NIPs, where implementations coalesce upon NIPs in order to coordinate with related implementations. Like pools of NIPs.
↩ replying to α΄›Κœα΄‡ α΄…α΄‡α΄€α΄›Κœ ᴏꜰ α΄ΚŸα΄‡α΄‹α΄œ
IMO the fact they kicked semi means that we can really for real disregard getting our protocols added to the spec and actually, for real, start documenting them on our relays in events using alexandria text events, or whatever is the best option because it's gonna go down hill so fast without him talking sense into them.