Hacker News Reader

Comment by adamrmcd | Hacker News Reader

> Naturally, this move led to a huge outcry outside (and apparently inside) Google, and now, the company seems to be backing down from most of the harsher terms of the initial announcement. [..] > the company is surprised by how many people this change affected.

I would expect that this system is too complicated to simply run `select count(*) from users where status = 'legacy'` but I'm certain they knew exactly how many free-loading "businesses" would be affected.

Too late for me, already started my migration to Fastmail.

The article does address paid content, which is good, but my larger concern is still with my Cloud Identity. I've used my custom domain under Google as authentication on hundreds of third-party sites.

If i use this migration tool and move to @gmail.com, will third-party sites still recognize and honour my custom domain Google login credentials?

View on HN

> If i use this migration tool and move to @gmail.com, will third-party sites still recognize and honour my custom domain Google login credentials?

I'd imagine so, as you can already have a Google account without a Gmail address on your own domain name.

> I'd imagine so, as you can already have a Google account without a Gmail address on your own domain name.

From the google "upgrade" page[1]

"This new option won't include premium features like custom email"

so, no, having a google account without a gmail address will no longer work unless you switch to google workspace (paid).

Logins using <name>@<custom-domain>.com will still work, but if you need a password reset using email (very common), it will fail unless you set your email up again with a different email provider (e.g. fastmail).

[1] https://support.google.com/a/answer/60217#data&zippy=%2Cif-i...

You can add your custom domain as an alias on your free Gmail account. That is my setup. Works perfectly.

Which is absolutely not even remotely close to being the same as your custom domain being a Google OAuth provider. The question stands - hard to imagine how it won't require action on users' parts.

And even in the context of this thread, having a sending alias doesn't magically make you able to check mail on a domain you don't control... having a forward alias means nothing in this context.

Examples:

* If anyone were using a paid Tailscale plan with a free GSuite account, they're probably just hosed. I have no idea how they're going to migrate short of Tailscale extending their auth mechanisms.

* Anyone "logging in" with a custom domain email might need to click a link to finish logging in. Unless your GSuite admin migrates mail services manually, you're not getting that email.

When Google announced the shutting down of legacy Gsuite they stated that authentication based upon the legacy accounts would continue to work. As would access to apps and media purchased under that account. Hopefully this will continue to be the plan if one doesn't take advantage of the migration tool.

Are you paying for email hosting on the custom domain and forwarding the received emails to Gmail?

If so that doesn't really solve the problem of the product no longer being free anymore, you now have to pay for email hosting...

Google is entitled to stop offering a specific feature if they want.

The outcry was because they did not offer any migration strategy for accounts that had been created under the free GSuite offer - it was either pay up, or have the account and all associated data be deleted across all Google services.

There is a difference between having your email hosted by them, and having an account where your email address is the account identity ("username")

Reply on news.ycombinator.com