Hide Comments Everywhere

Hides various commenting systems across the web, including (but not limited to) Disqus, YouTube, various news sites and forums, etc.

Available for Firefox, Chrome, Brave (chrome extensions work natively), and Opera (requires an additional extension).

How's it work?

The extension checks whether the loaded URL should block comments, then unblocks those URLs that match any regex patterns you've specified on the "options" page.

You can also specify a list of URLs as regex patterns, one per line, that should display comments all the time (the extension is effectively disabled for those URLs). Your list of excluded sites uses synchronized storage, so it should be available on any machine you've installed the extension on.

Quickly add the URL of the current page by opening the extension popup (by clicking the icon in the toolbar), and then selecting a URL (or entering a custom one) and pressing the "Allow" button. Note that, unlike the "options" page, these URLs are entered normally and not as regular expressions.

Click on the icon in the toolbar and press the large "toggle" button to temporarily toggle enabling/disabling the extension for a single tab.

It's triggered when the page is first loaded, or the URL changes (you click a link), or the comments are injected into the page (Disqus and YouTube delay loading comments), or when you open the popup (via the extension icon in the toolbar) and choose to toggle a page or whitelist (allow) a new URL.

If you're interested, you can read more about what I learned.


You'll be notified that it can "read and change all your data on the websites you visit" because that's how it works - it hides certain comment-related elements on the page so you don't see them.

It also uses storage to save its state, but it shouldn't prompt you for that.

Contributions / Questions

If you notice a commenting system that could be blocked by default, open an issue. Include the website where you noticed it, and I'll try to tackle it as time permits.

If you're comfortable with RegEx and HTML/CSS, you could just create a pull request against the file that defines which sites and html elements are blocked.

Have a question, comment or request? Open a new issue with as many details as possible. The more you let me know upfront, the less I'll have to ask later. I'll get to it as time permits.

Shut Up!

There's another extension called Shut Up (what a name, lol) that I just found the other day. Haven't tried it, but it seems to have gained a lot of traction and has high reviews so I'm assuming it works well. Might want to check it out too.

It also requests access to all sites (an extension of this nature needs to be able to modify any page to hide the comment sections), and also periodically calls out to get updated definitions (way more versatile than releasing an update to the extension).

The main difference is that Shut Up applies a lot of CSS to every site in order to hide any possible "comment" elements, whereas mine uses JavaScript to detect the site you're on and only apply a subset of styles depending on the URL. Is one more efficient than the other? Meh.


Grant Winney

I write when I've got something to share - a personal project, a solution to a difficult problem, or just an idea. We learn by doing and sharing. We've all got something to contribute.