Clients, please consider implementing the NOTIFY command from relays. Nostr.wine and relay.tools already send subscription renewals via the spec, and Amethyst displays them.
Discussion
I don’t need spam from relays, and this is just another NIP that’s fucked up the protocol and is turning Nostr into shit like XMPP. We can already start preparing for a proper protocol, without this Nostr crap — and without JSON and WebSocket as well.
Lol, then prepare it. Let's see how far it goes.
As a relay subscriber, I like that feature.
Say I am connected to wine and some other shitty relay I once trusted. This shitty relay gets compromised and sends me a NOTIFY invoice to pay for my wine subscription.
It is then up to the client's implementation making sure to properly inform the user which relay sent the NOTIFY.
If the NOTIFY message is exactly the same as the one I am used to getting from wine, I may fat finger it.
Also, while difficult to achieve, man in the middle attacks can also exploit users into paying for nefarious invoices.
This is a cool feature but sounds dangerous without relay key/signature in place.
Am I getting this wrong or time for a NIP for an extra relay trust layer which is not handled by transport/os?