I sympathize with our bitcoin queen mother, unfortunately I don't have experience with twitter in this way. Its been years.

This brings up a concern in regard to investing in your nostr identity. Yes we have NIP05, but that only passes the buck to a different identity mechanism (DNS.) One could be much more secure in their identity if we leveraged the bitcoin key management scheme. In particular, we can use a seedphrase to derive a keypair, and publish the xpub for the seedphrase to one's published identity/metadata (nip01/kind0). The owner of the seedphrase can implicitly revoke a compromised keypair by posting the next keypair in the deterministic sequence. A list of revoked npubs with a revocation date can be enumerated for the older keys in the metadata. Since this metadata message is signed, the relay only needs to check that the metadata isnt signed with an older key before allowing the metadata event to be posted. Any notes could be posted with newer and older keys, and it could be up to the client to reject notes signed by revoked keys after the revokation date.

This scheme allows the holder of the identiy seedphrase to only unlock the private derivation phrase when their hot keypair has become comprimised.