The returnyoutubedislikeapi (RYD) is experiencing a critical issue wherein Likes and Dislikes are not being properly displayed for age-restricted videos. This problem persists across multiple methods of accessing the data, including direct API calls, Userscript implementation via Tampermonkey/Greasyfork on Chrome, and the yt-dlp RYD Plugin with Cookies and AGB. However, it's important to note that the RYD Chrome extension is functioning correctly, indicating a specific issue with other methods.
Similarly, using the RYD Userscript via Tampermonkey or Greasyfork on Chrome results in missing Like and Dislike counts for age-restricted videos. Example data provided below:
The RYD Chrome extension is the only method currently providing accurate Like and Dislike counts for age-restricted videos. Example data provided below:
Utilizing the yt-dlp RYD Plugin with browser Cookies provided and AgeGateBypass also fails to retrieve accurate Like and Dislike counts for age-restricted videos. Example JSON data provided below:
Have you tried to find similar issues (open or recently closed)?
Browser
Chrome
Browser Version
Version 121.0.6167.185 (Official Build) (64-bit)
Extension or Userscript?
Userscript
Extension/Userscript Version
version 3.1.4
Video link where you see the problem
https://www.youtube.com/watch?v=BJDH36BQ-qo
What happened?
Problem
The returnyoutubedislikeapi (RYD) is experiencing a critical issue wherein Likes and Dislikes are not being properly displayed for age-restricted videos. This problem persists across multiple methods of accessing the data, including direct API calls, Userscript implementation via Tampermonkey/Greasyfork on Chrome, and the yt-dlp RYD Plugin with Cookies and AGB. However, it's important to note that the RYD Chrome extension is functioning correctly, indicating a specific issue with other methods.
How to reproduce/recreate?
Methods Tested / how 2 Reproduce
RYD API URL:
RYD Tampermonkey/Greasyfork Userscript on Chrome:
RYD Chrome Extension (WORKING):
yt-dlp RYD Plugin (with Cookies + AGB):
Will you be available for follow-up questions to help developers diagnose & fix the issue?
Yes