Return YouTube Dislike is an open-source extension that returns the YouTube dislike count.
Available for Chrome and Firefox as a Web Extension.
Also available for other browsers as JS Userscript.
On November 10th, 2021, Google announced that the YouTube dislike count would be removed.
Additionally, the dislike field in the YouTube API was removed on December 13th, 2021, removing any ability to judge the quality of content before watching.
With the removal of dislike stats from the YouTube API, our backend switched to using a combination of scraped dislike stats, estimates extrapolated from extension user data and estimates based on view\like ratios.
You can learn more at our website at: returnyoutubedislike.com
Third party use of this open API is allowed with the following restrictions:
- Attribution: This project should be clearly attributed with either a link to this repo or a link to returnyoutubedislike.com.
- Rate Limiting: There are per client rate limits in place of 100 per minute and 10'000 per day. This will return a 429 status code indicating that your application should back off.
The API is accessible over the following base URL:
https://returnyoutubedislikeapi.com
List of available endpoints is available here:
https://returnyoutubedislikeapi.com/swagger/index.html
Example to get votes of a given YouTube video ID:
/votes?videoId=kxOuG8jMIgI
{
"id": "kxOuG8jMIgI",
"dateCreated": "2021-12-20T12:25:54.418014Z",
"likes": 27326,
"dislikes": 498153,
"rating": 1.212014408444885,
"viewCount": 3149885,
"deleted": false
}None existing YouTube ID will return status code 404 "Not Found".
Wrong formed YouTube ID will return 400 "Bad Request".
We have an issue which is happening to a low percentage of Chrome users. service worker (ex background script) goes to Inactive state and doesn't wake up even when youtube tab is reopened. Only switching the extension off and on in extensions tab helps. This looks like a Chrome manifestv3 bug - so if anyone knows a good workaround - please open an issue\create a PR.
Looks like its this bug in chromium, and there is no good workaround. If anyone is aware of a workaounds - please contact.
Please read the contribution guide.
trig404