It was hot, the night we burned Chrome.
You might be thinking “how do you destroy software, the source code must have thousands of copies?”. Well, the purpose of a system is what it does; so we attacked that, the tracking data.
The techbro conceit of putting all the system code in one giant repository meant it was easy to suborn a minor contractor to leak the data storage code. A datacentre cleaner replaced a console cable with a logger, then another night dislodged a power cord. Technicians attended. Once the logger acquired some credentials, we injected our payload. Not into the running system, into the backup daemon. The vast archive of all the clicks, views and habits of half the planet slowly began to accumulate poison.
After two backup cycles, we struck. A datacentre fire is is a survivable event for a competent organization. Restore the offsite backups to an alternative DC and keep on truckin’. Unless those backups were not the data you thought they were.
So, long story short, if you were wondering why all your ads today are for dildos, because us. You’re welcome.
@Unixbigot
Understood_the_reference.gif