[Donald]

Their status page has been reporting the wrong certificate all weekend: https://status.twitter.com/

It has also rotated through various content (404 page, etc) which suggests someone has been fruitlessly trying to resolve the problem. Rebuilding their internal knowledge about "how to run this Twitter thing" is going to be an adventure for those left.

[sanguy]

A cert issue like this is pretty trivial..... concerning if they have nobody who knows how to fix it.

[duxup]

One thing I wondered about the whole story about Tesla engineers reviewing code was… how many of them and how much time would it take for them to understand organizationally who is needed / knows what to do for a site like Twitter?

Is “I think this codes is not optimally written.” Even useful after a week?

I once was a part of an acquisition where they quickly fired a lot of redundant people.

Including the entire mailroom, dock workers, facilities staff.

After a week they randomly called the tech support number and a group of us who had never been to the dock struggled to open the door for a weeks worth of deliveries.

[badpun]

Trivial in a small, no-nonsense company, probably absolutely non-trivial in a place like Twitter, where I expect they have a custom, byzantine devops/config management solution in place.

[abhv]

I was intrigued. As of Monday AM, status.twitter.com was still serving a DigiCert cert for "*.twimg.com"