frbitten on Nostr: Nostr by definition is all optional. With that, no one is obliged to implement a NIP ...
Nostr by definition is all optional. With that, no one is obliged to implement a NIP and there is no need to have a decision or consensus. All implementations are welcome.
Relays should have protections for sending large amount of data in the event if this is not in your interest. Independent of the NIP-95, this protection should already exist. This makes the network more resilient to attacks.
I created NIP-95 to open up the discussion of something that is flawed in NOSTR and needs to be supported. Social media is visual currently text only is an outdated feature already. But I also created it to make life easier for relays that can easily refuse the NIP, unlike if the standard event was used for that. Clients have to evolve to only send events to the supported relay. This sending everything to everyone has to end.
Relays should have protections for sending large amount of data in the event if this is not in your interest. Independent of the NIP-95, this protection should already exist. This makes the network more resilient to attacks.
I created NIP-95 to open up the discussion of something that is flawed in NOSTR and needs to be supported. Social media is visual currently text only is an outdated feature already. But I also created it to make life easier for relays that can easily refuse the NIP, unlike if the standard event was used for that. Clients have to evolve to only send events to the supported relay. This sending everything to everyone has to end.