In the post mortems on Ron DeSantis’s less that wholly satisfactory campaign debut, I’ve seen plenty of derision – Donald Trump is firmly aligned with the Left here – and some pro-DeSantis apologetics, mostly along the lines of, “Everybody will forget this in a week or two.” What I haven’t seen is so much as a breath of suspicion that the Twitter Spaces meltdown might not have been simply the result of the deployment of not-adequately-tested technology. Yet the grounds for suspicion sit in plain sight.
When Elon Musk acquired Twitter, many, many employees did not welcome their new overlord, to put it mildly. They were overwhelmingly Musk-hostile for a variety of reasons, some stemming from his imperious management style, others from dislike of his perceived political opinions, which jibe poorly with the tech world’s longstanding woke orthodoxy and increasingly woke orthopraxis. Many malcontents were fired in the wake of the takeover, but Musk couldn’t, even if he seriously tried, get rid of them all and conjure a loyal work force into being.
The DeSantis campaign rollout was intended to publicize not just the candidate but also Twitter Spaces, which is supposed to be Twitter’s Next Big Thing. For employees who loathe both Ron DeSantis and Elon Musk, what could be more tempting than a bit of sabotage to make sure that both looked inept?
Elon Musk doesn’t – he can’t – oversee all the steps needed to host a Twitter Spaces event that will be accessed by hundreds of thousands of people, no more than he can personally supervise SpaceX countdowns. A very few people in the right places at the right time could have created last night’s “technical difficulties”, with virtually no risk of leaving behind evidence of their actions. Did something like that happen? We will never know, unless the perpetrators come forward to boast about their exploit, but, such are the times in which we live, that the idea is far from unthinkable.
Comments