grantwinney / hide-comments-everywhere

A browser extension for hiding major commenting systems like Disqus, Livefyre, Facebook plugin, WordPress, YouTube, etc.
MIT License
38 stars 6 forks source link

A new site I'd like you to consider blocking (Piped - piped.kavin.rocks) #103

Closed MrChocolatine closed 2 years ago

MrChocolatine commented 2 years ago

Here's a new site I'd like you to consider blocking:

piped.kavin.rocks

(please include any other relevant details)

What is Piped? https://github.com/TeamPiped/Piped

An alternative privacy-friendly YouTube frontend which is efficient by design.

Thank you.


Extension's information:

grantwinney commented 2 years ago

Comments on that site are already being blocked, since any elements with a "comment" class applied to them are hidden by default. Is there a particular page where you're still seeing them?

MrChocolatine commented 2 years ago

Comments on that site are already being blocked, since any elements with a "comment" class applied to them are hidden by default. Is there a particular page where you're still seeing them?

Weird, on my side I see comments, for instance on this page:

https://piped.kavin.rocks/watch?v=bS4Q-WWyl3Q

And my whitelist is empty.

grantwinney commented 2 years ago

I don't see them on that page either. Hmm..

MrChocolatine commented 2 years ago

I ended up uninstalling and reinstalling the extension (especially after seeing the error in the console), and now I can see the comments are blocked. The extension was not out-of-date, all the setting page is exactly the same as it was before reinstalling it (and same information about the versions).

I have no idea what happened ¯_(ツ)_/¯ ...

MrChocolatine commented 2 years ago

Feel free to close the issue if you want, as I am not sure we can investigate further, sorry for the noise.

grantwinney commented 2 years ago

Sorry I missed the details in the original post. That's odd. You had the latest version of the addon but it was failing to download the file that tells it what to hide. I'll probably dig around in the code to see what might've caused it to behave like that, but glad reinstalling it worked!