Beating Google at their own game, they (apparently) are.
Often you see the opposite, where a third party service provides customers with a feature extending the features of a big service like youtube or twitter, and then the big service buys the startup offering that extension, or integrates the feature themselves, leaving the extension dead. Now we see it happening in reverse direction, very interesting.
edit: there's a Linus Tech Tips video on this which goes into more detail. Here: https://www.youtube.com/watch?v=Nz9b0oJw69I
Extensions probably acquire the video url and make their own API call just to retrieve the dislike count. To me, that seems cleaner than trying to snoop on the main API call response (I think extensions might not have access to those, maybe they do). Basically, the data is available via API calls.
[0]https://developers.google.com/youtube/analytics/metrics#disl...
And your other comment says "The dislike count is also still present in the [0] video API response." but the page says right there "Note: The statistics.dislikeCount property was made private as of December 13, 2021."
The dislike count is also still present in the [0] video API response.
[0]https://developers.google.com/youtube/v3/docs/videos#resourc...
It's not marked as deprecated or removed because dislikes were never deprecated or removed, nor implied to be.
They made it private (readable only to the uploader) and marked it as private.
A plug-in using this API will only tell you the dislike count for your own videos.