They're taking Kind 01 out of NIP 01.

They're taking Kind 01 out of NIP 01.

What does that entail? 😅
I don't know, but neither do they, and they're going to do it, anyway, because they're bored.
I wish they’d stop changing existing NIPs. Just make new NIPs.
What nips have been changed?
I stumbled upon this, by accident, looking for a threads NIP. And I needed a bit of time, to absorb the information.
note1jfate2jfvk9td58xpxvp54nuuwrwk0acrfh82ezet087p5afg3jshp5gck
They're going to say moving it won't change anything.
Their changes never change anything, but they are very urgent changes because reasons.
It’s bullshit. By changing existing NIPs, it makes liars out of relays and clients that were once compliant. One would need a NIP versioning system to ensure that when you say you implement a NIP, everyone knows what you mean.
Yes, we need NIP configuration management. No way to keep up with NIPs, anymore. Pure chaos.
That's how they demoralize the competition.
Big corporations do stuff like this, all the time. Fiddle with the regulations, to stymie smaller competition.
Year 1: All of the measuring sticks need to be 4 feet long.
Year 2: All measuring sticks need to be 3 feet long. *everyone cuts the sticks down*
Year 3: All measuring sticks need to be 5 feet long. *half the companies go bankrupt because they can't afford to buy new sticks*
They try to do the same with bitcoin
Who’s doing it? And why don’t they design things backwards compatible😅?
I see your point now about how editing could become a super annoying way of trolling. I am new to the circus so this kind of stuff doesn't occur to me. Love the passion. Not sure what could do but one thing I know is that removing features from an app is one of the easiest forks to make. 🌱🌴🦜🏴☠️
I am increasingly under the impression that the inmates are running the asylum.
A lot of plebs are listening but - speaking for myself now - do not know what to do!
I don't know why an edit feature is at all appealing on Nostr, but it seems like something that some clients could choose to use and others not - but you're saying that editing is being integrated into the Nostr protocol?
One way to change the Nostr protocol is to simply implement the change in your software. If enough clients implement the change, it gets written down and formalized as a NIP.
So, the one way to prevent one popular client from pressuring every other client development team to adopt their non-feature and end up with it as a NIP, like some sort of feature-virus, is for npubs who use those clients to scream their head off on Nostr that
WE DO NOT WANT THAT, DO NOT BUILD THAT. THAT IS A BUG, NOT A FEATURE.
Otherwise, you're going to get it, good and hard.