Wisp now ignores any inbox relay that attempts to AUTH/Dox you
Only relays you explicitly set to AUTH will be allowed
You don't have to do or know anything, everything still works and privacy protec...
One caveot here: Clients do not have to AUTH with their own pubkey just to send a NIP17 DM though.. Only to receive. They do have to AUTH, but it can be with any key.. At least, that's how I have it setup. Unsure about the other relay solutions. The receiving side is where the relay attempts to 'protec', by only sending DMs that were intended for who is authing. Any other relay, that does not have auth, will just send all of them from everyone to anyone, waiting to be decrypted in the future if one of the keys is p0wned.
The other reasons AUTH is good is that if you're using a relay that is trying to provide you a solid service, like an aggregator relay, or a custom feed relay.. These you will notice because you are a 'customer' of them, and AUTHing puts you ahead in the queue on a busy relay by increasing your limits.
Anyway, that's my speil on why AUTH is not just for doxing. It's hard to implement and so I think devs tend to talk only about it's downsides. I think you're on the right track here with the wisp tho! Thank you for giving people options to AUTH.
The other reasons AUTH is good is that if you're using a relay that is trying to provide you a solid service, like an aggregator relay, or a custom feed relay.. These you will notice because you are a 'customer' of them, and AUTHing puts you ahead in the queue on a busy relay by increasing your limits.
Anyway, that's my speil on why AUTH is not just for doxing. It's hard to implement and so I think devs tend to talk only about it's downsides. I think you're on the right track here with the wisp tho! Thank you for giving people options to AUTH.
2❤️1
