Oddbean new post about | logout
▲ ▼
Brunswick | 1 months ago (raw) | root | parent | reply | flag 
 Why not create a new nsec/npub first, post from your original identity indicating the new npub, then burn your old npub? To just burn and start over with the same underlying identity, I would like to know why that is a preferable procedure?
▲ ▼
Final | 1 months ago (raw) | root | parent | reply | flag +1 
 That would be the standard procedure, but circumstances about the event meant I couldn't. Users should announce change of keys if able to.
▲ ▼
Brunswick | 1 months ago (raw) | root | parent | reply | flag 
 Understood
▲ ▼
Brunswick | 1 months ago (raw) | root | parent | reply | flag 
 This sounds ominous
▲ ▼
hodlpleb | 1 months ago (raw) | root | parent | reply | flag 
 If planning ahead, could plant a SHA-256 message somewhere in your feed, then if you ever need to use it you can post the clear message on your new npub and point to the old SHA, to show that you were the one that posted the message on the old npub
▲ ▼
Final | 1 months ago (raw) | root | parent | reply | flag 
 Wasn't really something I looked into since it was extremely unexpected. Also up to believe official GrapheneOS platforms would suffice in announcing my key change. I dont want to spread fear by people misunderstanding a personal and isolated incident as a GrapheneOS one.