The generated addresses are all completely distinct, and can be revoked.
They look like for example:
happy.wombat-0a@icloud.com
dingus-capybara.0e@icloud.com
The generated addresses are all completely distinct, and can be revoked.
They look like for example:
happy.wombat-0a@icloud.com
dingus-capybara.0e@icloud.com
I also use random name aliases on each signup. Even if you aggregate multiple breaches I doubt anybody would link it to an individual (me).
The big remaining issue is payments. I use multiple cards and rotate them regularly (I don't have access to privacy.com or similar where I am based).
I believe this is the future - feed each service you signup to a new set of information and keep track in a password managers. Most services don't care what your real name is (I've been using an alias on services like Uber for ~10+ years).
icloud is also a good option - but I don't want to signal being an iCloud user.
Like grandparent said: by having a catch-all email address on a domain. Then emails that are being sent to invalid email accounts on that domain end up in that mailbox.
Another commenter in the thread presented how their company "normalizes" gmail addresses by removing "." character and "+..." suffixes, so users don't abuse their system by creating multiple accounts with what is basically the same email. Having a catch-all mailbox allows people to circumvent this "security" measure.
I'm imagining that you actually want to have separate emails pointing to separate mailboxes, and for that case indeed, your solution is better, but for the life of me I can't imagine why anyone would prefer having to check multiple emails, instead of a single one. :D