Important to clarify here that in describing the exploit, the author of this article is not doing anything wrong -- they're raising awareness of an issue with t

Important to clarify here that in describing the exploit, the author of this article is not doing anything wrong -- they're raising awareness of an issue with the Chromium dev tools that people absolutely should be made aware of. It's very much in the same vein as some of the "login interceptor" extensions that got published back when the tech community was trying to encourage sites like Facebook to switch to HTTPS. The full text of the article makes the author's intentions pretty clear, and I think it's good that they published this article. Otherwise, agreed. Users have a fundamental right to inspect code that is running on their devices (https://anewdigitalmanifesto.com/#right-to-modify https://anewdigitalmanifesto.com/#right-to-modify), and anti-debugging techniques (including invasive systems like DRM) are distasteful because they try to deny users that right. I'm also pleased to see the Firefox alert, but there's no specific mention I can find about why it doesn't work in Firefox. I'd love to see some more information about that.