Facebook (Canned) Responds
It’s backbone was broken, conveniently after a whistleblower took a scalpel to their profit model.
With the official narrative of Facebook, and probably the correct one in this rare case that the outage yesterday was caused by an internal infrastructural error (though the debate about the intentionality of the “error” is still up in the air) we got this statement from a blogpost by a FB top engineer with the Wall Street Journal making sure to prominently disseminate the official narrative to millions.
From a technological perspective, the argument is sound. A network tool, used to analyze FB data center and connection capability failed during routine maintenance. Routine maintenance the day after 60 minutes ran an interview with the whistleblower that dropped some damning comments about their profits before people business model (not that we’d expect any different from a capitalist company intricately tied to world business, politics, and Washington).
One of the most interesting comments to me that adds more questions than it answers is this quote from the article
Our primary and out-of-band network access was down, so we sent engineers onsite to the data centers to have them debug the issue and restart the systems. But this took time, because these facilities are designed with high levels of physical and system security in mind. They’re hard to get into, and once you’re inside, the hardware and routers are designed to be difficult to modify even when you have physical access to them. So it took extra time to activate the secure access protocols needed to get people onsite and able to work on the servers. Only then could we confirm the issue and bring our backbone back online.
In layman’s terms, facebook was disconnected from its own network, and its internal network was crippled in its ability to to remote in and fix the problem remotely. Thus, they had to send engineers (and whoever else) into the many physical data centers they use, hosted by Amazon Web Services, to physically access the servers (also the internal ones) and reset their addressing to reconnect them to the Facebook DNS, to reconnect that to the BGP.
So the news it seems is inconsequential according to the official corporate media.
To be a fly on the wall in the newsrooms that serve empire.
MSNBC CNN and FOX in unision: Well, that’s not interesting news.
In the Fox newsroom: The employee was a secret operative of the Chinese government, china bad.
Editorial team, yeah, go with that.
MSNCB newsroom: The employee was a secret Russian operative connected with Trump.
Editorial team, yeah, go with that.
CNN newsroom: The employee was both a Chinese and Russian Operative of dual citizenship trying to dismantle the pristine institution that is Facebook.
Editorial team, yeah go with that.
Jokes aside, It’s just too damn coincidental. And I realize that we’ll probably never have the whole story. But imagine the scenario since we know facebook is an absolutely terrible company that manipulates people into anger and profits off of hate speech, it was fueling QAnon ffs.
Though speculative, it’s entirely plausible, that the physical access allowed access to files stored on those servers. Files that could be absolutely damning to facebook if they ever came to light, such as the files not leaked by our whistleblower to the Wall Street Journal. As of the time of this writing, the files have not been made available to the public.
If anyone does find a link to them, of if they do leak, send me a message or drop them in the comments. The world deserves to comb through these, more so than the corporate whores who daily sell their souls to twist narrative for US hegemony in the quest for profit.
My work is entirely reader supported, my content is free and will always be free. If you enjoy reading my work, consider making a donation to keep the lights on. Solidarity, comrades. -Z