I love @jb55 and all his work to lead Nostr into the huge ecosystem we have today.
However, he is wrong about NIP-94.
NIP-94 was discussed for 2 months, agreed and merged. Amethyst is just implementing the consensus. I am not the one going sideways to implement my own way of doing things.
Thread
Login to reply
Replies (10)
Sheesh. Happy Monday
#[3] let’s try really hard to not make the same mistake done here kind sir 🙏
How is proposing an optional header to a NIP comparable to this in any way? Our relays will never implement non-backwards compatible changes in this way - full stop. If clients can’t access our relays we lose all of our value. I think you completely misunderstand where I’m coming from.
I didn’t say any of that... I half expected you to reply with something along the lines: we won’t let it happen under our watch ✊
Oh well it’s Monday and I didn’t intent to join the drama so I apologize and please forget I tagged you
😂 very well, my apologies then. The timing was odd given the conversation we just had about NIP98 and the context of this thread.
I am passionate about making sure people get their notes and other stuff. We won’t let it happen. 🫂
🫂
Nostr is evolving but also testing its consensus limits
#[0]
😆
#[3]
The second implementation matters since it makes the NIP official?
#[3]
