Hacker News Reader

It wasn’t corrupted. It was bad code. Bad code which clearly wasn’t tested.

Really? We know, for a fact, yesterday, that the “update” was a file full of complete null characters, unless there was some update on that.

That’s quite open to the possibility of a disk failure or CDN failure. Bad code would at least show something that can’t be executed.

official company statement says that null characters were not cause of the problem