Your own wrongdoing. Always use a site-specific auth method, i.e. by email. And a separate email for each site.
Your own wrongdoing. Always use a site-specific auth method, i.e. by email. And a separate email for each site.
(Use a catch-all to have different email addresses for different sites, because when one gets hacked, then the damage is limited.)
So you can use different email addresses for different accounts while having only one Gmail account.
I like using company initials & random numbers @ my domain .tld
You need to send them an email to cancel. When I tried they said “you need to cancel from the same email you signed up with.” :/
The funniest part was that for one it work great for the signup part, but they used a third party tool for licences that broke because of my e-mail. For another, only the js code was verifying the e-mail, and I could push it by removing the validation. When the owner had to validate my account, they got a message that the e-mail was incorrect when they tried to submit the form. They called me and had a great discussion about web apps security. We had a good time.
I would point out that it kind of prevents you from checking if your email is in a leak database as you need to test each aliases you used.
"But I use my addresses on my own domain" ok your domain registrar, then.
Hopefully, domain registrars are less prone to locking people out compared to Apple, given cause of the lockout is caused by Apple itself.
Reminds me of the time Namecheap stopped doing business with Russian accounts, even then they still gave some time for them to transfer their domains.
Eg: Dynadot decided what my birthdate is a secure pin two years ago. No combination of it works and I'm not even sure if I'm not shadowbanned for the attempts.