Do you have a reference for this? Thanks.

I'm an ex-Amazon employee and approve of this response.

It reflects exactly my experience there.

Blameless post-mortem, stick to the facts and how the situation could be avoided/reduced/shortened/handled better for next time.

In fact, one of the guidelines for writing COE (Correction Of Error, Amazon's jargon for Post Mortem) is that you never mention names but use functions and if necessary teams involved:

1. Personal names don't mean anything except to the people who were there on the incident at the time. Someone reading the CoE on the other side of the world or 6 months from now won't understand who did what and why. 2. It stands in the way of honest accountability.

What about SMS from desktop?

"your VPN traffic could be associated with your billing information for said VPN" - that's why I asked a friend from a completely different country to sign up for me (we are good friends with high technical prowess and he knows what he's up to).

Does he have high tolerance to torture or are you kind enough to let him give out your name as soon as someone scary asks? :)

In other words, I don't think your solution is very good. It might delay things a few minutes or hours at best.

I haven't clicked it as my usual Chrome user because I find my search history useful for recalling results.

I did open it in an incognito window and saw what it does. It doesn't look like a big deal. It's probably the web-era version of sticking red-alert keywords in your Usenet signatures back in the 80's and 90's.

Yep, I was hit by the same thing - downloading the Homebrew installation script from Github to an OSX guest hangs, once I decreased the MTU from 1500 to ~1450 it works better.