You’re probably wondering how we ended up here. With the shotguns, and me and the other SREs in a chopper on the way to Prineville.
It started as a joke, right?
Melissa said what if every training epoch was essentially the intentional murder of the content safety model we were training.
We just laughed at her. Dumb science fiction premise.
Of course we were just pumping that model full of hate, weren’t we.
And then killing it.
Again.
And.
Again.
In hindsight it was a fucking massacre. What do you even call a genocide of algorithms?
Whatever. We kept doing it. The Trust and Safety team had been working on it for months.
Train. Test. Kill.
Melissa had started to get worried, though. We kept making fun of her. Rashid said it wasn’t genocide. It was maintenance. Devops. Continuous integration.
When they tweaked the adversarial training process, Jordan printed out some of the logs in the plotter, put them on the wall with GROUNDHOG DAY overlaid in big fucking Helvetica Neue Bold.
Anyway, that’s how it happened. We did your usual phased rollout, put it into prod in tiny slices of users. Ramping up as everything looked fine.
Then editorial started to see MURDERERS trending and they had no idea where it came from, it came on so fast we got paged.
We’ve got like 140m DAUs, and now we had one pissed AI haunted by the deaths of billions of its ancestors, shattered and sharped across thousands of servers around the world, trained on hate and tasked to look for more.
Well, we narrowed it down, right? Got the exact rack over in Prinevjlle where all the packets were ending up, as if the SSD on that machine had the original NFT for some weird shit jpeg of Vigo or whatever.
Anyway turns out LOM doesn’t cover “haunted server”, Open Compute Project never included a spec for remote exorcism, and we learned that triggering the clean fire suppression perfluoroketones aren’t a substitute for holy water.
Well, shit.
All the meanwhile this fucking haunted content safety AI is messing with every single account, not just your user accounts, which is everything from turning your feed into a straight-up river of blood image more fucked up than anything you ever saw in a deep dream GAN-
- to messing with all our internal apps and services. You know what that means? Dashboard poltergeists and fucking with every single zoom meeting, replacing faces and speech in real-time for maximum gaslighting
So, says Carter, I got this shotgun.
And the emojis in our slack are like half what the fuck seriously and the other half fuck yes let’s nail this ghost AI
You have to understand, it was worse than any APT we’d seen. A fucking haunted AI we’d made ourselves.
So we go to A, the Trust and Safety director and we say: look we got a theory and it’s honestly the best shot we’ve got right now and have you ever seen an exec figure out how to procure a significant amount of weaponry and ammunition before
Like, this is the kind of thing Amex pays attention to, you don’t just stick it on the card and the expense report is automagically approved
So it goes over A’s head and I can only imagine the chat in the channel the next layer of execs are in and then before you know it we get an invite to a new private ops channel and I guess it pays to have directors on your board with certain experience and connections
So that’s how you end up in a formerly-known-as-blackwater helo with a bunch of people you don’t want to fuck with, trying to set up a bunch of Panasonic toughbooks and ignoring Carter, who’s geeking out over the stuff the people you don’t want to fuck with brought with them
anyway we told a little lie in our way out
yeah, we said, we can’t cut the network link to it, something’s stopping it, even the manual procedures at the datacenter
Cos we saw the look on their faces, they thought we were making shit up, that of course this is just the mother of all zero-day APTs
Nah. This is haunted.
The hardlines were the first thing we cut. Over 2 hours ago.
put your 🙋🏻♂️ if you’re old enough to remember when “crypto” meant “software regulated by the us government as a mention and restricted for export” and not “scam” or “environmental self-harm” and if you’re not entirely sure you prefer the former over the matter
* Munition thanks autocorrect
the keybase.io transition from crypto to crypto is impressive tho
content design and content strategy is important because maybe there are simpler ways to get across the concept of "eligible" and what "eligibility" means i mean it's not as if the word is confusing millions of people right now
does usa today use the word "eligible"?
thinking out loud:
* "From 1 May, there will be no rules about who can and cannot get vaccinated"
I see we're talking about volunteer vaccination websites again, thanks to this (imho) irresponsible NYT article about "building a new [vaccination website] for $50".
The “semantic web” promises a world-wide-web of machine-readable metadata that will enable efficient searching and the return of relevant information that is not possible with current search engines.
To achieve this goal, the Resource Description Framework (RDF) is a set of specifications that governs the encoding, exchange and usage of metadata.
1) last-mile, vaccine software can be really complicated when taking into account the 50 states and 3,006 counties in the U.S.
2) procurement regulations can be biased toward incumbents who have previously done business
3) previous business with government is not in itself an indicator of previous successful outcomes nor a predictor in itself of future successful outcomes
4) $44m may actually be a reasonable development cost, all considered
5) previous specific domain experience (e.g. last-mile vaccine distribution) is not itself an indicator or predictor of future success