I'm not really sure what point you're trying to make, since I very clearly wrote I also don't think this was Google's fault (even if they did stop sending people through that area a mere couple of weeks after this incident).
I also don't think it's fair to blame these people for this, and so I'm trying to understand what you would've done differently in the same situation.
And what exactly would you have done differently? At what point would you have started to ignore the GPS directions and randomly drive around in an area you know nothing about?
This isn't the same as driving off a cliff or the wrong direction on a one-way road, these people were targeted by experienced criminals. I'm not saying it's Google's fault, but maybe let's try to avoid blaming the victims of a vicious attack.
I ended up going with addy.io since their Lite plan is cheaper and offers what I'm currently looking for, but I'll keep SimpleLogin in mind for whenever I need to upgrade.
I've heard of them before, good to know they support this. I'll check out their plans, thanks!
I was aware of SimpleLogin but I hadn't heard of this service before, thanks for the tip! I'll try to check them out and come back with a comparison.
Thanks for the recommendation! Unfortunately this approach doesn't really work for me since my domain includes my real name, I'm also relying on email masking for some degree of anonymity.
Your proposed solution to overly complex systems seems to be to ignore the requirements that make them complex in the first place. If that works for you, this is a perfectly fine approach. But most companies with actual signed SLAs won't accept "we'll just have a few seconds of downtime/high latency every time a developer deploys something to production #yolo".