Twitter Support just posted: "Some parts of Twitter may not be working as expected right now. We made an internal change that had some unintended consequences. We’re working on this now and will share an update when it’s fixed." https://twitter.com/TwitterSupport/status/163279294226274713...
Are they going to put "fired the people who used to enforce our change control procedures" in the post-mortem?
Twitter was down
211–220 of 493 posts
Re: Twitter was down
#212Earlier quoted context omitted.
Do you actually think it will go down for good? That seems extremely unlikely to me.
No, eventually they would figure out how to rewrite it if they can't get it working again. But I could definitely see a multi-week outage.
This thread is just an hour old btw, not sure when the issue started.
Seems like a huge reaction from HN for an hour long downtime given that Twitter has gone down for longer in the past.
Re: Twitter was down
#213Twitter Support just posted: "Some parts of Twitter may not be working as expected right now. We made an internal change that had some unintended consequences. We’re working on this now and will share an update when it’s fixed." https://twitter.com/TwitterSupport/status/163279294226274713...
Re: Twitter was down
#214Earlier quoted context omitted.
Please don’t do that. You deserve better as a worker. If a company is unable to function without infringing on the free time of their workers, that company should not exist.
I believe GP said he had fun. People should be allowed to work how they want to, they have the freedom (especially in this industry) to go elsewhere. I've pulled late nights, they bought us pizza and gave us a half day later. Sometimes you have to put in work during critical times. It's certainly not construction work anyway, people are kinda soft here sometimes.
I disagree. There is a race to the bottom and a tragedy of the commons. A company could easily exploit this by gamifying the work and hiring workers with addictive tendencies. Most national labor laws and labor contracts set a maximum number of daily and weekly working hours for a reason. Workplace safety is only one of those reasons.
Re: Twitter was down
#215Re: Twitter was down
#216Twitter Support just posted: "Some parts of Twitter may not be working as expected right now. We made an internal change that had some unintended consequences. We’re working on this now and will share an update when it’s fixed." https://twitter.com/TwitterSupport/status/163279294226274713...
Thanks for typing out their tweet. I wouldn't have been able to have read it otherwise, seeing twitter is down.
Re: Twitter was down
#217Re: Twitter was down
#218Twitter Support just posted: "Some parts of Twitter may not be working as expected right now. We made an internal change that had some unintended consequences. We’re working on this now and will share an update when it’s fixed." https://twitter.com/TwitterSupport/status/163279294226274713...
Thanks for typing out their tweet. I wouldn't have been able to have read it otherwise, seeing twitter is down.
I remain astounded by how much their product has declined (even pre-Musk acquisition) from their glory days of being so light weight that they were used to organize protests when governments would clamp down on internet access.
Re: Twitter was down
#219{"errors":[{"message":"Your current API plan does not include access to this endpoint, please see https://developer.twitter.com/en/docs/twitter-api for more information","code":467}]}
Re: Twitter was down
#220I can't remember a major service nosediving so monumentally in such a short period of time. Just a steady degradation of service.
Lots of people were waiting with baited breath for Twitter to fail the first week Musk bought it, but most of the failure conditions had been automated away...
Instead the reliability loss creep happened more slowly. The people that understood the edge conditions in the system were fired. Then new changes need implemented and the old, now not understood systems, were ripped out and new pieces put in. And lo and behold they have tons of failure conditions and edge cases that can knock out the system.
Even if your programming team wrote immaculate documentation on all these edge conditions, it can take an immense amount of time to both read them, and then fully understand them, and when you have a micromanager breathing down your neck for changes 10 minutes ago this is what happens.