Hacker News Reader

Comment by lrae | Hacker News Reader

Sounds like they tried to restrict and killed an/their own ("unofficial") API, and shot themselves into the foot.

Definitely the kind of mistake that gets made after losing an enormous fraction of your institutional knowledge.

Sure. Or it could just the kind of mistake that is being made all the time. I remember for example facebook taking itself offline[0], or cloudflare taking itself offline[1]. And of course pre-Musk twitter is well known itself to regularly have had significant incidents.

This new twitter incident could well be a result of layoffs and the resulting loss of institutional knowledge, but that's hardly a foregone conclusion.

[0] https://en.wikipedia.org/wiki/2021_Facebook_outage

[1] https://blog.cloudflare.com/cloudflare-outage-on-june-21-202...

They've pretty obviously had an increase in service problems since the culling. Most services this size very rarely have outages. You had to go back to 2021 for facebook. Twitter has had several major outages since Musk's purchase.

Twitter also has made a lot of changes in the past few months. I don't recall a time in recent history where they've made so many changes so rapidly. Arguably not all for the better but "move fast and break things", right?

Move fast for no reason is stupid

Twitter had a code freezenfrom the time of culling until January roughly. They appeared to make a lot of changes due to botched launches, e.g. they released checkmarks for sale, reversed it and re-released it. Does that count as 3 changes, or one half-baked one?

It could all be part of Musk’s plan. Make people upset that they can’t use the website properly, and then offer a paid service that provides them with a working version?

Reply on news.ycombinator.com