onei

(Former akamai employee) Akamai have an incident process that handles both "things are bad for multiple customers" as well as "we need eyes on this from multiple departments/stakeholders asap". If you're hitting a wall debugging an issue on your own, especially if it's not overtly customer impacting, declaring an incident is an effective way of getting the attention needed to solve it.

Once you declare the incident, the process includes these status page updates, alongside equivalent internal status updates.

In this case, they probably wanted to maximise coordination, so used the process designed for that.

What was it like to work in the film industry, presumably as a software developer? I've heard lots of anecdotes about the games industry, but nothing whatsoever about working on a film.

Is that a recent-ish improvement? I feel like HTTP/2 would be roughly the same performance for JSON and protobuf, so maybe this is HTTP/2 vs HTTP/3?

It's a tracking tool. You have a bunch of sites embed an image, and requests to those sites also make requests to said image, which you can use to start tracking a client. A single pixel is merely the cheapest image.

I recall Facebook doing it years ago, I imagine they still do.

Hex is 0-9, a-f. P and q are outside that character set.

It's not that the article is inherently unsafe, it's that the UK law imposes a liability the author is unwilling to shoulder.

I read that line and thought "so, the solution is code review?". What has to happen to your processes that code review is not only missing, but unironically claimed to be the solution?

I know there are some companies that never did code review, but this is Amazon. They should know better.

It's the Isle of Man to the best of my knowledge, but the people, and language, are called Manx. Like the English are from England.

If you want emails from some random internal machine, you can use one of the HPE SMTP servers. There was one for internal email, another for external iirc although I'm not sure there was a difference in practice. Those SMTP servers would do a DNS lookup before accepting the email.

When I set this sort of thing up, I'd get myself a hostname on an internal subdomain. But that was a truly miserable experience. It was a multi-stage form submission on a server I imagine to be the closest possible relation to an actual potato. It was soul-destroyingly slow. Alternatively, you could just pretend your machine was hpe.com - the hostname was valid, even if the IP was totally wrong, and the SMTP server would accept it.

My guess is that there was a bunch of stuff that pre-dated the HP/HPE split and they took the quick and dirty option whenever the old internal domain name got yanked during the changeover. And if your process runs as root, you get [email protected] and hope there's something in the subject/body to identify the specific machine.