AMD Gaslights Security Researcher, Changes Rules Retroactively [video]

A fresh AMD headache has turned into full-on comment-section theater. The core issue is simple: a security researcher known as Mr Bruh says AMD software had an updater that could be tampered with, and when he reported it, AMD allegedly shut things down by saying it didn’t count under the company’s reward rules. That alone was enough to set off a mini-riot, but the real fireworks came from the crowd arguing over whether AMD was dodging blame, playing paperwork games, or just being swallowed by its own giant-company bureaucracy.

The sharpest split came from commenters trying to decode whether this was a cover-up or a scope dispute. One camp was furious, echoing the video’s tone that AMD had effectively changed the rules after the fact. Another pushed back hard, with Thomas Ptacek arguing AMD wasn’t saying the flaw was fake, just that it fell outside the bounty program. Translation for normal humans: the bug may have been real, but the payment fight is a separate mess. Then came the skeptics rolling their eyes at what one commenter called “overwrought YouTube drama,” steering readers to the researcher’s own write-up.

And yes, the pedants arrived right on schedule: one of the funniest side-quests was a commenter bluntly declaring, “Gaslighting does not mean lying.” Meanwhile others cranked the stakes to spy-thriller levels, warning that powerful state actors could have abused the flaw. So the vibe is deliciously chaotic: half consumer outrage, half semantic cage match, with a side of “please stop turning every bug report into a PR soap opera.”