What is Nostr?
mikedilger /
npub1acg…p35c
2024-11-26 22:16:13
in reply to nevent1q…jp2a

mikedilger on Nostr: Two paths: 1) Work with other people, decide on a good path forward, go together down ...

Two paths:

1) Work with other people, decide on a good path forward, go together down that path for maximum compatibility
2) Believe you are the smartest person in every room, reject other proposals without any deep reasoning or discussion about them, and do it your way as fast as possible and roll it out as far as possible to force other clients to do it your way since you "beat them to it". Then argue from the position of "it's working" and "we have 50,000 edits already".

You took path (2). It is indistinguishable from an embrace-extend-extinguish attack on nostr. I don't think any protocol can defend against this kind of attack. It is why Microsoft was so successful at crushing open technologies in the early days.

Since edits are not just an additive feature, but a fork of kind-1 and it's very meaning, all we can do is not implement PR 1090 and let the nostr community naturally fork.

So that is what we are doing. IMHO edits will be Amethyst only, and eventually Amethyst users will either recognize the futility of fake edits, or they will become a separate community.

If other devs worked together and decided that PR 1090 was the right path forward, then we could all go there. But the devs are spread out into very different opinions on how edits should happen.
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c