More like vitor is doing something extremely disruptive to the rest of nostr and he doesn’t seem to care. Oh well, it’s his users who will suffer. I am no longer going to recommmend amethyst and point users to plebstr instead.
Discussion
Agreed! His responses seem callous. Plebstr works great! Damus is the king!
I do care. That's why I am being disruptive. NIP-94 was discussed for 2 months and merged.
I am not the one refusing to go along with everybody else here...
🫂
As an outsider to Nostr development, this is something I’m puzzled by. According to the GitHub page, “[NIPs] should be implemented in at least two clients and one relay — when applicable” before they’re accepted. Yet it seems as though Vitor is the first to implement NIP-94?
https://github.com/nostr-protocol/nips#criteria-for-acceptance-of-nips
Actually, https://filestr.vercel.app/ implemented NIP-94 before Amethyst.
cc #[6]
Thank you for the correction. Still, isn’t the order supposed to be implementation in two clients, then acceptance?
Theoretically, yes.
But it doesn't always work like that.
Sometimes a single implementation pushes a NIP acceptance (i.e. Zaps or Repost in Damus), sometimes implementation waits till a NIP merge, even months later!! (I.e. NIP-42 Auth).
Hm. I think the recent unpleasantness could have been avoided if everyone had seen Vitor’s implementation before NIP-94 was accepted. Will would have objected, and there wouldn’t have been consensus to merge the NIP.
Sometimes implementation is important, yes.
But communication is always more important.
🫂
That didnt take long for the in fighting to start
Plebstr isn't in a trust worthy app store yet. I only really trust f-droid at this point: https://f-droid.org
I understand recommending the Android client that suits more the way you think nostr micro-social should work, of course.
But building a Damus Android client because you don't agree with Amethyst direction looks like wanting to control yourself where micro-social nostr is going, imho.
Just my opinion, ofc.
