Quite disturbing to learn about such "artifacts" from a big-name mfgr. More so, that this was a known to them issue at the release time to be mentioned in user

Quite disturbing to learn about such "artifacts" from a big-name mfgr. More so, that this was a known to them issue at the release time to be mentioned in user manual! By the way, reading the blog post I stumbled on quite a few minor typos (like "arrors" for "errors" etc.). Should be easy to fix, but in a way this adds more emphasis and mood to the content...