Subnostr

#[2] #[3] fyi

This is just me spitballing, but maybe its only necessary to have an event type that says "this key is compromised" then its up to the client/user to find the new pubkey through their social circle.

Then maybe there could be a new kind of event that would be published by anyone which would say "X's new key is Y". then the client could gather these events from your followers or random strangers? and show the user a few options (hopefully just one) for a new pubkey to follow. almost like a social voting system? idk

Reply to this note

Please Login to reply.

Discussion

someone 2y ago

Attacker may delete the "this key is compromised" event.

This just made me realize relays must block the deletion requests for 101.

hzrd149 2y ago

The soft deletion of events always puts a twist on these types of things.

That's why I think it could be a good idea for the client/user to rely on other users to find the new pubkey because other users events can't be as easily deleted.

Also off topic, but what client are you using? I noticed it's not adding a "root" event tag to your notes so they aren't showing up correctly in threads in my client.

someone 2y ago

I was on Snort. Now Amethyst