zlacker

>>benhur+(OP)
This makes me anxious about my long time Gmail address. Back then I got it just because it and Google was cool, and their services had a good reputation. It was a different Google back then. If they had launched it this year I would never have got one because chances are it would have been cancelled by 2025. Gmail is really the only valuable thing that actually ties my life to Google. And it's not that hard to replace, but just a bother to inform some people and update account details.

>>jug+36
Start the process of getting out right now.

Get an email address that you own, on a domain you control. Switch to a provider that takes your money for whom you are the customer - not the product.

I did this with Fastmail and Iki.fi, a Finnish non-profit[1], who have been selling people "permanent" email addresses since 1995.

[1] http://www.iki.fi/

>>theshr+Jd
If you get your own domain, get one on a well-known TLD (e.g. .com, .org or your own country code). If you get a gTLD that's not well-known, there are some endpoints that will block you because your email is "not valid".

>>krageo+de
Is .dev or .io considered a well-known gTLD by now? I’m in process of setting up email for my .dev domain.

>>blntec+Pe
Do not use .dev, some companies are using .dev for internal dev hosts and might be blocking on DNS level all external dev addresses.

>>martin+ig
The sysadmins at these companies must be laid off right now. Same with Windows admins using .local for their AD domain name, now you shot yourself in the foot never being able to sign some services with globally trusted certificates.

>>lillec+Zk
What? Many of these domains date back to when there were like 10 gTLDs and adding a new one was a rare event.

>>Macha+pu
RFC2606 dates to 1999, so they've had a little time to migrate. tl;dr: .test .example .invalid .localhost