packetslave

Literally every movie ever made was made by an LLC created specifically to make that movie. This is not some nefarious thing. It’s common business practice in any number of industries

Funny how nobody asks the folks who build golf courses "what about water usage?"

hint: An individual 18-hole course uses between 300,000 to 1 million gallons per day

As someone once put it: "McDonald's is a real estate company with a hamburger hobby"

Nobody cares. Read it, or don't. Complaining about perceived LLM writing adds nothing to the conversation.

This is absolutely something that's happening. There are even paid scraper API's that offer "Wayback Machine fallback" as a feature.

And you're under the impression that the purpose of a company blog is WHAT, exactly?

> Didn't the DoD at one point build a 1k+ PS3 cluster based on their multi-core chip and had a mini supercomputer CotS?

The Air Force did (Condor) and it hit #33 on the 2010 Top500.

Nintendo is probably THE most aggressive company in the industry in terms of going after people for using their IP in unauthorized ways. They don't have a blind eye.

> Waymo driver? The vehicles are autonomous

the "Waymo Driver" is how they refer to the self-driving platform (hardware and software). They've been pretty consistent with that branding, so it's not surprising that they used it here.

> Importantly, Waymo takes full ownership for something they write positively [...] But Waymo weasels out of taking responsibility for something they write about negatively

Pretty standard for corporate Public Relations writing, unfortunately.

right-click, search Google: "MSK most commonly refers to Memorial Sloan Kettering Cancer Center, a world-renowned institution for cancer treatment and research"

yep, and it was this exact requirement that also caused the exact same outage back in 2013 or so. DDoS rules were pushed to the GFE (edge proxy) every 15 seconds, and a bad release got out. Every single GFE worldwide crashed within 15 seconds. That outage is in the SRE book.

I have a bit of a different take on browser fingerprinting: I don't want to uniquely identify you as a person so I can serve you ads, or whatever. I want to identify your traffic when you're scraping my content from 2,000 different IP's and 1,000 different user accounts, I can block you or rate limit you without hurting anyone else.

Given the scale of scrapers these days (AI companies with VC money have no problem spinning up thousands of VMs running Chrome), fingerprinting at the browser level is the only realistic option.

(obligatory: my personal opinion, not necessarily my employer's)