nostr:nevent1qqsq5qsarv0mhcza44j3nqycrj6umc3elc0nqaa7pvv9ma92zq60zagzyqlhwrt96wnkf2w9edgr4cfruchvwkv26q6asdhz4qg08pm6w3djgqcyqqqqqqgpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgswaehxw309ahx7um5wgh8w6twv5q95y0g
nostr:nevent1qqsfshavnz4jqa7t9skp47mlzr6c8sd3ans3uu7tkuyzuapea3vfdmgzyzwflq0d090s7hh62kyn9qjxslvyl3lx5n86dk6ad5a4pl9hl7hvyqcyqqqqqqgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgcwaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmqpz3mhxue69uhkummnw3ezummcw3ezuer9wc536jnw
It’s hard to get normies on #Nostr. As soon as they learn that their NSEC can’t be recovered or reset, or that discoverability on Nostr is mostly non-existent (except for reposts), they’ll be heading for the exit…
The problem with Nostr identities not being recoverable if compromised is a massive problem. It’s my biggest problem with the Nostr protocol.
It only takes one mistake where the user pastes their NSEC into a malicious client. As Nostr grows (if it ever does), we will see an increase in malicious clients popping up.
Think about building up a following on Nostr just to lose it all because you made one mistake pasting your NSEC into the wrong client.
It’s discouraging to creators…
Login to reply