I create unique identities for each online account to pair with password management. I should really go further and rotate them. It seems that there is a rela

I create unique identities for each online account to pair with password management. I should really go further and rotate them. It seems that there is a relationship between the # of times an email identity has been reused and the quantity of breaches that show up on haveibeenpwned. My system allows for transparent replies via gmail/outlook etc and I can redirect where the emails land easily. I just started playing with the system again and I wanted to add a few features. 1. vanity domains and shorter ids. I wonder what if i can get away with 8 char ids... example s0gt7i9n3uhd@green.foo.com I'll route the email based on "green" and "s0gt7i9n3uhd" in a way return emails can be reverse routed transparently. 2. bitwarden client integration. I think CLI client is the way to go, tips on a bitwarden gui library I could integrate with would be appreciated. 3. cloud object backend. For some accounts storing all the email on S3 or other object store would be fine. I'd like to get away from using gmail. I plan to have a ringbuffer to store recent emails per identity and then fetch/render them in my webapp. 4. I want to write some more advanced reporting. I track every address that sends to an identity and can for example trigger when the sender domain doesn't match the identity domain. This has indicated breaches. Once I know there is a breach I can easily blackhole the identity.