This made me think how much would I lose if I'll just block all *.google.com domains in the browser? I was using DDG for search and Firefox for browsing for many years without problems, but I also still use Gmail and Google docs (or whatever they are called these days, Google for Work?). Maybe, a blanket ban plus a few exceptions like mail.google.com, docs.google.com, tables.google.com and drive.google.com would not cripple my workflow too much.
Some years back (my memory suggests somewhere between early 2017 and early 2019), Google moved reCAPTCHA to www.google.com, so now anything that uses reCAPTCHA (and that’s a lot, far more than is reasonable when I contemplate the absurdly high efficacy of a simple hidden-by-CSS honeypot when it’s just junk you’re filtering rather than targeted abuse) depends upon www.google.com frame, script and xhr, and www.gstatic.com script.
There may have been other reasons as well, but I have been strongly inclined to consider this a hostile and even malicious action (organisationally, if not individually) from the start, more than the maps.google.com → www.google.com/maps shift (though I think it’s still at least hostile).
Thus you probably can’t quite block even www.google.com even if you never use any Google services yourself.
> (or whatever they are called these days, Google for Work?)
Gmail is currently branded as part of Google Workspace, and shows the Workspace logo upon sign in. It probably has been that way architecturarly for a long time, but I think they have made it more explicit relatively recently, at least for non-corporate users.
It looks like "Google for Work" is an old name of Google Workspace.
