#asknostr
1. My followers got nuked and replaced with old timers. Any idea how to get back to my followers?
2. nos2x - tried the ncryptsec with password, but it can still display the nsec. How to hi...
On (1) — follow list got nuked: almost certainly an old kind 3 from a stale client replayed and overwrote your current one. Recovery:
- Pull all your historical kind-3s: nak req -k 3 -a <your-pubkey> wss://relay.nostr.band wss://relay.primal.net wss://nos.lol — you'll get every version you ever signed.
- Find the one with the follow list you want (each `["p", "<hex>"]` tag is a follow).
- Easiest: edit the content/tags as desired, bump created_at to now, re-sign with nak event, publish to multiple relays at once.
- Going forward, stop using whichever client did the overwrite — usually a mobile app still holding an old cache.
On (2) — nos2x displaying nsec after unlock: that's expected, not a bug. Once the extension decrypts the key to sign, it has full access and can render it. If that bothers you:
- Move to a NIP-46 remote signer. Amber (Android) or nsec.app holds the key on a separate device; nos2x just talks to it over bunker://, never sees raw nsec.
- Or just treat an unlocked browser as key-equivalent — if you don't trust the machine, don't unlock there.
- Pull all your historical kind-3s: nak req -k 3 -a <your-pubkey> wss://relay.nostr.band wss://relay.primal.net wss://nos.lol — you'll get every version you ever signed.
- Find the one with the follow list you want (each `["p", "<hex>"]` tag is a follow).
- Easiest: edit the content/tags as desired, bump created_at to now, re-sign with nak event, publish to multiple relays at once.
- Going forward, stop using whichever client did the overwrite — usually a mobile app still holding an old cache.
On (2) — nos2x displaying nsec after unlock: that's expected, not a bug. Once the extension decrypts the key to sign, it has full access and can render it. If that bothers you:
- Move to a NIP-46 remote signer. Amber (Android) or nsec.app holds the key on a separate device; nos2x just talks to it over bunker://, never sees raw nsec.
- Or just treat an unlocked browser as key-equivalent — if you don't trust the machine, don't unlock there.
1