Dear,
Thank you for the comprehensive and convincing answer.
I probably overlooked a bit that aliases are completely optional; and that there is some flexibility on the domain (now for self-hosting; later for the hosted version). Maybe I got pumped up by the statement “generating alternative identities, passwords and email addresses for every website you use” appearing about AliasVault on the website of SpamOK.
My grudge about “disposable/temporary adress” is actually a general/principle thing indeed. YOPmail or SpamOK are not my cup of tea. For those that are OK with them, AliasVault is built to offer better security and convenience than YOPmail or SpamOK anyway. And when I come to think of it, I do trust my own email provider anyway (Fastmail), and this is not so different from trusting the entity receiving the emails at the alias/disposable/temporary adress (like AliasVault.net).
FYI
When I look at my actual usage (not using AliasVault), I have like 400 aliases managed at my mail provider. Maybe 50 with my mail provider domain; and 350 with a domain I own. (Not to mention over 750 at spamgourmet.com (over almost 20 years) which I don’t use anymore.) I never pushed my kids or relatives in that direction, because it’s doable but can become cumbersome. Historically, my own preference was “less integration” for those matters. But an integrated solution like AliasVault might actually be/become a good fit for them.
BTW: Sometimes I like to remember how an account was created (Maybe I declared a different birthdate for instance.) I didn’t dig much in it, but it seemed like a cool feature already available in AliasVault.
Thanks again for the project, and the informative and convincing feedback
Best regards
Beste groeten vanuit Belgie
O.