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".
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.
It doesn't really contain a spoken word part, but the poor pronunciation made me think of Yes Sir, I Can Boogie by Baccara.
I highly recommend a scale (with 0.1g precision) to weigh how much coffee goes in vs how much liquid comes out. Without it you're just going to be eyeballing and that will quickly become frustrating (I've been there). No need to spend a lot of money, a cheap €20 one will get you a long way.
Once you get a scale, you can follow this simple recipe:
- grind 18g of coffee (weigh the grounds, do not weigh the beans unless you have a very good grinder with low/no retention)
- Extract your espresso for 30 seconds
- Weigh the liquid in the cup, it should be around 36g (1:2 ratio). If it's under 36g you're grinding too fine, if it's over then you're grinding too coarse.
- Repeat until you consistently get it right.
After it's dialed in, you can start making micro-adjustments to your liking.
I've been using Loop for a year or two and it's great.
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.
I've been trying out Firefox Relay for a couple of months, and I really like the idea of hiding my real email address. The only thing putting me off from this concept is the fact that it makes my experience significantly worse, as it's now harder to quickly understand where the email comes from.
A simple example: if I give my real email address to an online shop, I will receive a confirmation email with
From: Online Shop
Which is trivial to read.
If I give a generated Relay address, then the emails will come as
From: "noreply@onlineshop.com [via Relay]"
Which is much harder to parse off a quick glance, especially on smaller screens like a smartwatch.
When receiving emails, I don't really care if they were forwarded via Relay, and I would much rather see the original sender in the From field. Is this necessary for proper privacy, or just an issue specific to Firefox Relay? And if so, is there any other email masking platform that supports what I'm looking for?