{"type":"rich","version":"1.0","title":"vinney...axkl wrote","author_name":"vinney...axkl (npub19m…8axkl)","author_url":"https://yabu.me/npub19ma2w9dmk3kat0nt0k5dwuqzvmg3va9ezwup0zkakhpwv0vcwvcsg8axkl","provider_name":"njump","provider_url":"https://yabu.me","html":"Interesting or totally moronic: generating a new random nostr keypair for each post, but including a signature on each note to prove that a single particular public key wrote them all (could be an npub or another scheme).  \n\nthe point being to, for specific use-cases, remove the relevant private key from the loop wrt to nostr clients. (you'd use whatever signing software you like. PGP, say.) use nostr as a potentially-unsafe broadcast mechanism, segregating the key you care about from nostr entirely.  \n\nthen you could use a client like anonostr.com - or really any client at all, with a new keypair each time. saving you mental overhead in your opsec endeavors. \nif you wanted discoverability and something like a chain of connection between the notes, you could use a unique hashtag. and readers who follow this hashtag would have to verify that your generic key \"meta-signed\" the notes, since their nostr clients wouldn't do this automatically anymore. ....until someone built a nostr client that had this feature :laugh_lg:"}