Allow users/creators to confirm dislike count via OAuth (Heavily requested feature)

[SpareLeader]

Extension or Userscript?

Both

Request or suggest a new feature!

Greetings.

As the title suggests, i would like to request that the creators be allowed to share actual dislike data with the extension.

The FAQ on the RYD website states that the users can share their dislike count in an unspecified time in the future, but they never have, and there is no sign that this is in the works.

It has been more than 2 and a half years since the extension's initial commit on Github, and during that time, many users have requested that creators be able to share the dislike count with the extension, or at least show how many users have liked or disliked. Each time, the conversation died out, no approval, no rejection, just silence.

Ways to implement this!

As suggested, we can receive the data via OAuth, or some third-party API. We can even tell users to create or find an exempted API token and plug it into their extension.

Also, if we find a way to show the actual dislikes, we can show a warning symbol telling users that the count is estimated.

Can you work on this?

• Yes
• No

Will you be available for follow-up questions to help developers implement this?

Yes

[jpa102]

it seems like they were heavily debating about it before because a malicious actor can just modify and sabotage the actual dislike counts on their end and other stuff

i got impatient so i ended up posting the dislike counts myself by json files in a repository that i made (and also put the like and dislike counts on every video description)

hoping the devs see this. i was wishing for this feature to exist

[mastermajorman]

I was initially planning to create a similar enhancement request, but a few concerns came to mind:

• How can we ensure the security of creators who share their client ID and client secret with us?
• Will creators feel strongly enough about this feature to risk potential security issues?
• Who will be responsible for reaching out to creators and providing this service?

These uncertainties held me back from pursuing the feature as initially envisioned. However, I still believe there’s significant value in comparing our user-oriented, extrapolated data with verified, real-world data from creators.

Instead of moving forward with the original OAuth concept, I propose pivoting this enhancement to focus on polling trustworthy creators who are willing to provide their channel data. By doing so, we can identify and analyze discrepancies between our extrapolated data and the actual figures, paving the way for improved accuracy and more robust solutions.

Additionally, I suggest adding a disclaimer to the website and/or extension view, clearly stating that the displayed dislike count is an estimate. This transparency would help manage user expectations while reinforcing our commitment to continually refining our methodology to source more accurate data.