Loading Comments stopped working.

[programmer1o1]

Clicking "reload" on the comments doesn't load the comments anymore or just loading doesn't work anymore. Please fix it. Thanks you so much.

[NicPalacio]

Exactly it happen for me recently too , it does not work in any browser

@sonigy , @knoajp, @Letssharearow any idea why ? If you need help I will be happy to contribute but I think that it has to do with something more technical.

[bluecxt]

For me, it doesn't work with firefox

[JackOfSpade]

Guys, the author has probably died by now. Just move on to another chrome extension. There are plenty.

[programmer1o1]

Guys, the author has probably died by now. Just move on to another chrome extension. There are plenty.

To be fair, it's the best one right now. There aren't many good extensions like these in Firefox, and maybe Chrome too.

[NicPalacio]

@JackOfSpade mm not sure why you say that xD, but there us not really an alternative to this extension, only this one does the work

[RenegadeScooter]

I use Brave (version 1.64.113, Chromium 123.0.6312.86, 64-bit). The extension loads comments for normal windows, but not private windows.

[knoajp]

@NicPalacio Thank you for mentioning me😆, by quick investigation, it does load comments but only fails to handle/show. Although I haven't checked the extension code yet, it could be caused by just a JSON structural modification by YouTube.

As well as making a quick patch on the YCS, I expect some nice alternatives to appear, like the IYCS project. 😉 https://github.com/StellarSt0rm/IYCS @StellarSt0rm

[knoajp]

🤔 It seems to take much effort to solve it...

YCS source code on Mac Chrome (minified): Library/Application Support/Google/Chrome/Default/Extensions/pmfhcilikeembgbiadjiojgfgcfbcoaa/1.1.12_0/web-resources/wresources.js

JSON API: https://www.youtube.com/youtubei/v1/next?key=xxxx

Currently, comments are in: JSON.frameworkUpdates.entityBatchUpdate.mutations

But there are no such property names in wresources.js. Still, I can find JSON.onResponseReceivedEndpoints in wresources.js, which might haven't changed.

[knoajp]

My biggest reason for using YCS is to browse popular comments by Likes order. So my temporal workaround is using the CSS below to highlight popular comments.

#vote-count-middle{
  color: black !important;
  border-radius: .5em;
  padding: .25em .5em;
}
/*1000-*/#like-button:has(:is(button[aria-label*="K "], button[aria-label*="M "])) + #vote-count-middle{
  font-weight: bold;
  background: #f008;
  border: 1px solid #f00f;
}
/*100-999*/#vote-count-middle{
  background: #f004;
  border: 1px solid #f008;
}
/*10-99*/#like-button:has(:is(
  button[aria-label*=" 10 "], button[aria-label*=" 11 "], button[aria-label*=" 12 "], button[aria-label*=" 13 "], button[aria-label*=" 14 "], button[aria-label*=" 15 "], button[aria-label*=" 16 "], button[aria-label*=" 17 "], button[aria-label*=" 18 "], button[aria-label*=" 19 "],
  button[aria-label*=" 20 "], button[aria-label*=" 21 "], button[aria-label*=" 22 "], button[aria-label*=" 23 "], button[aria-label*=" 24 "], button[aria-label*=" 25 "], button[aria-label*=" 26 "], button[aria-label*=" 27 "], button[aria-label*=" 28 "], button[aria-label*=" 29 "],
  button[aria-label*=" 30 "], button[aria-label*=" 31 "], button[aria-label*=" 32 "], button[aria-label*=" 33 "], button[aria-label*=" 34 "], button[aria-label*=" 35 "], button[aria-label*=" 36 "], button[aria-label*=" 37 "], button[aria-label*=" 38 "], button[aria-label*=" 39 "],
  button[aria-label*=" 40 "], button[aria-label*=" 41 "], button[aria-label*=" 42 "], button[aria-label*=" 43 "], button[aria-label*=" 44 "], button[aria-label*=" 45 "], button[aria-label*=" 46 "], button[aria-label*=" 47 "], button[aria-label*=" 48 "], button[aria-label*=" 49 "],
  button[aria-label*=" 50 "], button[aria-label*=" 51 "], button[aria-label*=" 52 "], button[aria-label*=" 53 "], button[aria-label*=" 54 "], button[aria-label*=" 55 "], button[aria-label*=" 56 "], button[aria-label*=" 57 "], button[aria-label*=" 58 "], button[aria-label*=" 59 "],
  button[aria-label*=" 60 "], button[aria-label*=" 61 "], button[aria-label*=" 62 "], button[aria-label*=" 63 "], button[aria-label*=" 64 "], button[aria-label*=" 65 "], button[aria-label*=" 66 "], button[aria-label*=" 67 "], button[aria-label*=" 68 "], button[aria-label*=" 69 "],
  button[aria-label*=" 70 "], button[aria-label*=" 71 "], button[aria-label*=" 72 "], button[aria-label*=" 73 "], button[aria-label*=" 74 "], button[aria-label*=" 75 "], button[aria-label*=" 76 "], button[aria-label*=" 77 "], button[aria-label*=" 78 "], button[aria-label*=" 79 "],
  button[aria-label*=" 80 "], button[aria-label*=" 81 "], button[aria-label*=" 82 "], button[aria-label*=" 83 "], button[aria-label*=" 84 "], button[aria-label*=" 85 "], button[aria-label*=" 86 "], button[aria-label*=" 87 "], button[aria-label*=" 88 "], button[aria-label*=" 89 "],
  button[aria-label*=" 90 "], button[aria-label*=" 91 "], button[aria-label*=" 92 "], button[aria-label*=" 93 "], button[aria-label*=" 94 "], button[aria-label*=" 95 "], button[aria-label*=" 96 "], button[aria-label*=" 97 "], button[aria-label*=" 98 "], button[aria-label*=" 99 "],
dummy)) + #vote-count-middle{
  background: #f002;
  border: 1px solid #f004;
}
/*1-9*/#like-button:has(:is(
  button[aria-label*=" 1 "], button[aria-label*=" 2 "], button[aria-label*=" 3 "], button[aria-label*=" 4 "], button[aria-label*=" 5 "], button[aria-label*=" 6 "], button[aria-label*=" 7 "], button[aria-label*=" 8 "], button[aria-label*=" 9 "],
dummy)) + #vote-count-middle{
  background: #f001;
  border: 1px solid #f002;
}

[xNasuni]

this is happening to me aswell. from my investigation the API is returning the data, and the extension does get all the comments, but it never actually puts them in the UI. this might be due to a change in the structure of how they return stuff that could've changed recently which made this issue arise but until I or someone else does more research this will stay broken.

for some reason this repository does not contain the source code of the YCS extension which is a little sad, but I will make my own version of this extension on github if I do manage to fix it, with credits to the original creator ofcourse. (the extension that you can download from webstore is minified)

suprisingly still works on my laptop, which has had the extension for a long time, weird...

[xNasuni]

~~i've figured out atleast 1 issue.~~

~~this extension stops working some versions after chromium 122, i've tested this extension and it's worked on 121.0.6156.0 (chromium build), and 122.0.6261.137 (chrome build) but stopped working around 123.0.6312.106 (chrome build) which released to the stable channel around the time this issue was posted.~~

when i mention chromium i also mean chrome as chrome is built on top of chromium, so they are practically interchangeable.

the statement above and list below may not be correct as the extension has become unresponsive after a day on the same instance. see my latest issue on 04/07/2024 to read more

Version	Working
≤122.0.6261.137 (less than or equal to)
any version inbetween may or may not work
≥123 (greater than or equal to)

YCS on chrome 121, looked the same on chromium 122, worked like it used to YCS on chrome 123, basically just wouldn't load at all

this means that the extension Youtube Comment Search is not broken, but the versions/releases of chrome after or on 123 are breaking it.

i will try fixing the extension to work in these new versions, but for now the only solution if you want to use YCS, is to go back/downgrade to 121 or 122.

[mauigirl]

I'm running Chrome 116 on three older laptops and it stopped working on all those installations too, so it's not a v123 issue for me. Same in Firefox. I've turned off other extensions, cleared history, sometimes that will get a few comments or chat to load briefly but never the transcript anymore and even the partial comments don't last long (minutes).

[Slowlyness]

I have the same issue with Firefox 124.0.2 (64-bit). Reload-Button of "comments" is grayed out. Search in comments is not working. I thought it might be an issue with uMatrix etc. which could block a script from a change on the Youtube.com website. But it was not the case. Even when all extensions in FF are disabled, the issue with YCS persists. Unfortunately, I'm not a web developer who could parse the issue deeper. Hope a solution will be found soon. I like the YCS extension => Thanks to the maintainer(-s)!!! 👍

[NicPalacio]

It is very true @xNasuni two weeks ago stopped working for me in Edge and continued to work for me in Chrome but with the update this morning it stopped working in Chrome too which shows that it is a problem with the new chronium.

[NicPalacio]

Hi @xNasuni , how are you, any updates?

I've been reviewing it, but I can't seem to understand the error in the code. The problem is that all browsers have already updated to version 123 of Chromium, so as of now, it's not working on any browser. I also looked into your advice on downgrading Chrome, but I'm not sure how I could do that. I found tools like FileHippo, but the latest version available for download is 104, and YCS doesn't work on that version either. Do you know of any way to specifically use Chromium 122?

[RenegadeScooter]

It's not working for me at all anymore. Brave version 1.64.116, Chromium 123.0.6312.105, 64-bit

[ahmed2m]

Did youtube change the API interface? What's happening, anyone knows how to access the extension's devtools?

[xNasuni]

Hi @xNasuni , how are you, any updates?

I've been reviewing it, but I can't seem to understand the error in the code. The problem is that all browsers have already updated to version 123 of Chromium, so as of now, it's not working on any browser. I also looked into your advice on downgrading Chrome, but I'm not sure how I could do that. I found tools like FileHippo, but the latest version available for download is 104, and YCS doesn't work on that version either. Do you know of any way to specifically use Chromium 122?

I usually use npx to install chromium builds for testing by using the command npx @puppeteer/browsers install chrome@version and in this case I would run npx @puppeteer/browsers install [email protected] but I think my original hypothesis was incorrect.

Both versions that I tested it on have stopped working as of currently and nothing I can do gets it to work unless I completely reset the browser which goes inline with one of the reviews that said some of these fixes only work for about a day or so then it stops working.

I guess that's what I am facing with now, using a brand new browser with no previous data or similar fixes it for a day or so and then it breaks again. I will continue trying to find a fix for this, and in the mean time I have sent an inquiry to the developer's personal email and also sent the same email to the contact email for this project [email protected] which I doubt I'll get a reply from.

[ahmed2m]

I usually use npx to install chromium builds for testing by using the command npx @puppeteer/browsers install chrome@version and in this case I would run npx @puppeteer/browsers install [email protected] but I think my original hypothesis was incorrect.

Both versions that I tested it on have stopped working as of currently and nothing I can do gets it to work unless I completely reset the browser which goes inline with one of the reviews that said some of these fixes only work for about a day or so then it stops working.

I guess that's what I am facing with now, using a brand new browser with no previous data or similar fixes it for a day or so and then it breaks again. I will continue trying to find a fix for this, and in the mean time I have sent an inquiry to the developer's personal email and also sent the same email to the contact email for this project [email protected] which I doubt I'll get a reply from.

Yea, it's not a browser thing it seems, maybe switching versions somehow serves you a different version of youtube web api temporarily because they're using a/b testing for different versions/changes.

A classic thing for such extensions is that YT has done an API change or patched something that the extension was using and likely it can't be solved with either a fix from the author or a fork of the extension with a fix.

[NicPalacio]

Thank you @xnasuni for your response and your work. I will try to find a fix as well, but to be honest, I don't have too much technical knowledge. If anyone discover some alternative or workaround to fetch all comments of a Youtube video with the recently changes, please let us know. I use the extension a lot to search for timestamped comments, most liked comments, and the YouTube experience decreases a lot without it :(

[Slowlyness]

Hi there, For guys who want to test with other browser emulations or older versions of Edge: I know, that in Edge it is possible to emulate other browser/versions etc.

Here's the how to (extract from copilot - I checked it for another purpose last week):

Open Microsoft Edge1. Press Ctrl+Shift+P (Windows, Linux) or Command+Shift+P (macOS) to open the Command Menu1. Type network conditions, select Show Network conditions, and then press Enter to open the Network conditions tool1. In the User agent section, clear the Use browser default checkbox1. Select a user agent from the dropdown list, or enter a custom user agent1

If someone is searching for older firefox versions: click

Source with more information for firefox downgrading: click

Hope it helps someone. 🙂

[NicPalacio]

@Slowlyness Thank you for the info. I tried changing the network conditions, but it only shows the latest version of Edge. Do you know how I can specify a previous version, like 122 or something?"

I attempted to install an older version of Firefox, but none of them worked. It's probably because the issue stems from the Chromium version in which the extension runs, rather than the specific version of Firefox itself.

[NicPalacio]

@xNasuni I'm not sure if you've noticed, but the extension loads Chat replay correctly. Perhaps this gives an idea of why it's not able to do the same with comments.

Additionally, I found this other 2 extensions that do a similar job :

• https://chromewebstore.google.com/detail/youtube-actual-top-commen/hbdmelobmfcompinikjdaiphhonbgfpn .

• https://chromewebstore.google.com/detail/comments-search-for-youtu/fbbhnhgdgjbfnkoiiedglmlnmleefjga

• https://chromewebstore.google.com/detail/timetags-for-youtube/hpbmedimnlknflpbgfbllklgelbnelef (fetches only comments with timestamps)

Interestingly, they fetch the comments properly and the first one even orders them by likes. The only issue with the first one is that it's a pop-up and doesn't stay on top always, plus the UI isn't that good and additionally I notice that it does not always fetch ALL the comments (sometimes only 70% of the total), while the second one fetches all comments. However, I think reviewing the code of those extensions could provide some valuable clues to help resolve the problem of YCS not fetching the comments.

[Slowlyness]

Do you know how I can specify a previous version, like 122 or something?"

Unfortunately no. Mhhh.

[Slowlyness]

I checked YCS on my FireFox portable version 122.1.1 64-bit on my mediacenter pc. It's still working there. I also check to click the "reload" button for comments. On my mediacenter pc the buttons is labelled "load". After this, the YCS is searching only the transscript of the video. Not sure how it behaved before.

[Aldo113A]

Eugene Gubar

Has anyone yet? This is too valuable an extension to lose

[Miwer]

I saw another post somewhere, that the distributed .xpi files of a firefox add-on, is basically just a zip file. So I got inspired to try to extract it, and I have posted the embedded source code here: https://github.com/Miwer/YCS-firefox-source

The code is compacted into very unreadable format, but I managed to run it through some beautifiers to make it more readable.

Maybe somebody can use it to make a new fork or something like that. wink wink

Enjoy ;)