Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If they have a bug that can crash their servers, they likely won't want to publicize the details until it is fully patched. I wouldn't expect that detail for a while.


As an ex CTO having lots of fire fighting experience, I wanna give the honor to the team being able to identify such a user triggered bug in such a short period of time. Hardly anyone would anticipate a single user can trigger a meltdown to the internet!


It reminds me of that ancient joke: A QA engineer walks into a bar. He orders a beer. Orders 0 beers. Orders 99999999999 beers. Orders a lizard. Orders -1 beers. Orders a ueicbksjdhd.

First real customer walks in and asks where the bathroom is. The bar bursts into flames, killing everyone.


You forgot the part where the QA engineer ticks off the checklist and gives the bar a pass.


The blog post actually says it’s fixed already (but I would definitely expect them to keep the details private until they’re 100% sure, yeah)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: