News for hackers. Stuff that matters.
Re:Twitter engineer: I thought I’d been hacked. It turned ou... by idiotsecant on Friday December 02, 2022 @03:39PM (#33836565)
>Based on the fact that they've gone through several waves of layoffs and nothing significant has broken yet.

But a bunch of stuff did break. Famously 2FA stopped working, there has been an explosion of spam, and other widely reported issues- which are only the ones we know about - there could very well be some truely abhorrent stuff going under the hood to keep the wheels from falling off.

The idea that a week or two of something other than total violent collapse being a measure of how well you're handling staffing has got the smell of management track thinking all over it.

Re:Twitter engineer: I thought I’d been hacked. It turned ou... by smoldesu on Friday December 02, 2022 @03:45PM (#33836638)
2 weeks is certainly nothing, I agree that the proof will be in the pudding. But so far, I remain unconvinced that Twitter is going to "break" in the traditional sense. If stuff goes down, we have protocol for bringing it back up. When 2FA dies, the process for recovering it is the same under Musk as it was under Dorsey.

We'll really just have to wait and see what happens. I really want Twitter to destroy itself beyond repair, but the core platform seems intact.

Re:Twitter engineer: I thought I’d been hacked. It turned ou... by mcspiff on Friday December 02, 2022 @05:23PM (#33837781)
This isn’t entirely true fwiw. That assumes a constant load on the systems. If you start running into a capacity crunch on a given system, your best case is scale horizontally or vertically using established procedures. But if you hit a limit there (vertical scaling limit, architectural limit) and actually need to refactor? Good luck!