That's basically because Larry Page really, really cares about it. He's kinda like your friend with a Kubrick obsession that can't stop bringing up facts:

https://twitter.com/elonmusk/status/727189428142235648

He was on to something! Jokes aside, I think he just has a heightened sense of smell and that's why he had air filters stronger than law requirements installed everywhere, at least in Mountain View.

https://www.usenix.org/conference/srecon18asia/presentation/...

You can see there's a section on privacy and deleted data as well.

Each team has its own policies, because each product is different: at a bare minimum they might be using different storage systems, but it's very likely that their data pipelines are quite different, too. In any case, each team's targets are at least as strict as any published ones, of course.

I bet it's not free to run, but it's cheaper and easier than elsewhere, because Google's infrastructure is built in-house and mostly integrated. I don't envy other companies that want to do the same.

Yes, it triggered a GET for /. But that generated HTML (usually the service's homepage, as was our case), which the browser would attempt to parse as an image, obviously failing. It would not trigger a recursive fetching of all the resources on the page. Even without recursion, it already inflicted major damage, because our service's homepage was dynamic, while the resources linked from it were mostly static (and thus a lot cheaper, as well as cacheable). I think I would have noticed if it multiplied other traffic, not just the homepage.

This was the bane of my existence for many months. Every few weeks I would have to fire up Dremel and try to figure what was causing the spurious page loads. I hated and still hate SQL, so that was no fun. I knew when it was time to investigate thanks to our human monitoring system: our PMs would get excited or puzzled by a sudden jump in the page view dashboards. (They lived by those graphs...)

Thank you Chris and co. for your contributions in killing the browser version from hell.

He was very approachable and understood well the technology that we were building. Most of my colleagues seemed to like him, too. He wasn't the money guy at the top of the org chart that doesn't understand his own products. That was even clearer when I talked to him in person once, after a company-wide meeting. He wasn't in a rush to get away from us plebeians, either.

Someone next to me made a comment about surveillance and he replied along the lines of "You know, I grew up in the Hoover days", explaining that he had seen the potential for abuse of power or personal information since a young age and that he held that as something to keep in mind or avoid when making strategic decisions.

As for other machines, I don't know of other signatures, but there are often Easter eggs. Commodore machines had funny stuff on their PCBs: codenames Rock Lobster, Junebug, plus the Fred/Wilma LEDs, etc. Lots of integrated circuits from several companies had artwork in unused areas of the silicon die.

More seriously, he admitted that the presence of the dog set a much informal tone in the office and made it easier to hire "unconventional" characters.

On the other hand, scrolling to the very top of the page reveals the original address bar.

A possible mitigation would be to use a custom background or gradient for the bar that a web page can't guess. I'd be tempted to suggest the Google account's picture (if Chrome is logged in), but I don't know how safe that is from cross-site shenanigans.

https://youtu.be/a7cJHTpW4Tg (jump to 49:00 or so for the more relevant bits)

Note also that he had a quarter century of experience before Apple, having worked on anything from the (RotJ?) Darth Vader helmet to the Oral B CrossAction, which is, a bit surprisingly, the product he thinks defines his career.