Twitter does not have separate development, test, staging, and production environments. At least 5,000 employees had privileged access to production systems.

https://x.com/avidhalaby/status/1602127460677844993

Orange Site discussion

54
Jump in the discussion.

No email address required.

https://x.com/AvidHalaby/status/1602132485743480832/photo/1

I'm not transcribing this, but god darn. Basically their systems start up by reading data from other systems, so if everything goes down, there is very literally no way to bring it back up "from nothing". That's right, if all their servers suffer a brief 1-minute power outage, the whole system is fricked basically permanently until a series of manual code changes are implemented to address it.

This thread actually seems way juicier than the "twitter files" shit, at least in terms of actual legal action. I'd bet nothing happens :marseysal: but maybe someone will get slapped for fraud.

Jump in the discussion.

No email address required.

>a single determined actor could have made Twitter shut down permanently

>nobody did it

nothing ever happens :marseydepressed:

Jump in the discussion.

No email address required.

Where's the fraud? It isn't illegal to have a backend that's held together with duct tape and shell scripts, in fact, that probably describes a majority of backends. A bit uncommon for a web property operating at Twitter's scale though.

Jump in the discussion.

No email address required.

You're right, their shitty engineering isn't illegal at all. But lying to the government about your infrastructure and security practices is.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.