Why not write a userscript for this kind of thing and publish it on userscripts.org? 1) It's cross-browser: Firefox (Greasemonkey), Chrome (Tampermonkey), Oper

Why not write a userscript for this kind of thing and publish it on userscripts.org? 1) It's cross-browser: Firefox (Greasemonkey), Chrome (Tampermonkey), Opera users can install it 2) Users can easily read the source code before installation to assure it doesn't do anything malicious If it changes DOM, but doesn't interact with the browser itself, it should be a userscript. A small introductory presentation about userscripts and GM_ API that I've recently done: https://speakerdeck.com/jakubg/userscripts-augmenting-and-automating-web-browsing-and-debugging https://speakerdeck.com/jakubg/userscripts-augmenting-and-au...