Sorry, I was trying to find out how you nuked the list in the first place to avoid doing it myself. I am very much locked in my Amethyst for a year now but I started experimenting with all there is to find on Spring and I'm afraid of randomly nuking something
I actually don’t know exactly how it works (I’m sure nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe can fill us in) but it seems like Nostur keeps a local copy of your kind 3 and then when you start it up, if it detects a new version, it asks you if you want to accept the changes or restore your old list. Very useful.
Discussion
Mixing clients is definitely how it happens. You can usually use a new client with just your npub (without needing to sign any events) and that avoids this risk. If using a browser that supports a NIP-07 extension or other remote signer, that can also prevent this type of thing.
Thank you!
Just make sure to backup your data with something like metadata.nostr.com before you start going wild