vinney...axkl on Nostr: Interesting or totally moronic: generating a new random nostr keypair for each post, ...
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).
the 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.
then 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.
if 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

Published at
2026-01-27 17:49:37 UTCEvent JSON
{
"id": "829a2caa92818f5f43919fd3d1f82b779a01ea779f0296eec64fb6459fe0e4b1",
"pubkey": "2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331",
"created_at": 1769536177,
"kind": 1,
"tags": [
[
"emoji",
"laugh_lg",
"https://i.nostr.build/j3ke3aXltqR8o1sU.gif"
]
],
"content": "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:",
"sig": "014c840f55e8a17d6ebe6f883b211fa64b0cc8379e33306baca623521bf22527b317cf9548dd093e3029502cb1aa2780be81d40c4f1693805863e2b7f6ba7466"
}