Ótima extensão.

thanks for continuing the project and making it available for firefox also

I like the update, very cool

works perfectly fine. hope it continiues to do so

thank you

genuinely one of the best addons

Could it be that YouTube made an update today that disabled YCS? It's definitely a 5-star add-on when it's working. Hope there is a workaround, soon, I really like using YCS.

Tue 07 Oct 2025: Looks like it's back!

Brilliant.

Works perfect! I can't believe how this is not a native feature on youtube

Works perfectly

excellent work continuing one of the best addons

Finally! One of the best expansion in my FF
But it stopped working.

THX for super fast fixing!
⭐⭐⭐⭐⭐

Great continuation! However I can not make it to work correctly with the Dark Reader extension. For some reason the black button text on the grey buttons change to white text on white buttons so you can´t read them.

Works perfectly. Thanks for the updates!

The best extension for this task at the moment. Thanks a lot! Please make option to keep the YCS interface collapsed/hidden under the video until it is needed.

thank you so much for forking this. Hadzy (a website) can only do so much.

Doesn't handle whitespace. Searching for "pro" returns comments that contain standalone instances of "pro" but also any comment containing a string with pro in it, like "pronounce" or "product." That's fine, but then if I search for "pro " with a space after pro, I get the exact same results.

Also, and this is not a big deal, it highlights substrings that are one character shorter than what you type in. So when I searched for "pro" it for some reason highlighted any instances of "pr" in the comment. Note that this doesn't actually affect which comments are returned, it's just a highlighting issue. So if you search for "pro" and a comment said "practice profiling perps," it would show up as a search result, and the pr in practice and the pr in profiling would be highlighted. But if a comment said "practice running," it would not show up as a result, so that's good.

Edit: thank you for the response! If I click "extended search" then searching using whitespace (in quotes) does indeed yield the correct results. As noted in that github thread, it no longer highlights the identified string in the comments when extended search is checked, but that's no big deal. Also the issue I mentioned with it highlighting a string that's one character shorter than the string searched for is not happening today, so that's cool.