That sounds awesome, maybe Colby can figure out all new DMs after the gitnestr 😎
Discussion
key rotation requires an interactive protocol, which is outside of the pubsub model of nostr
there is the potential for some kind of key rotation by sending a return address with each forward message, that only fails if the reply is not seen, this is still better than what we have
i was using "send reply address" in a more advanced form - send return PATH - in the indranet project
indeed, this could be even done here, but it then adds an extra layer of turning relays into ... proxies... and raises the spectre of spammy dummy content being used to jam up the channel, which again comes back to auth - in this case, a passive form that is simpler "accept event based on pubkey" and then you just need anon payments for these relaying accounts
but this is all a lot more complicated than neccesary for the simple task of making most relays respect FUCKING CONFIDENTIALITY
i don't accept the "band-aid" perjorative
if it's not worse than trusting google, then it's fine, shut the fuck up and take my money
note that "return addresses" protocol gets complicated because you are gonna be tying a request IP address to the keys when you use them, so there's not really much point in adding this complication
I have no idea, sometimes I think down these scenarios and run into a solid wall... Then back out and think some more. Lot goin' on w this stuff.
For the auth, yea, it's clear it needs implemented. That's all I really know at this point. 😁🦀
yep, solve the harder problems tomorrow, easy problems should not remain unsolved this long