Revisiones de Return YouTube Dislike
Return YouTube Dislike por Dmitry Selivanov
Revisado por Infrequent_User
Se valoró con 2 de 5
por Infrequent_User, hace 7 díasBE CAUTIOUS:
In the most recent update (September 7th, 2026 as of writing this), the developers have made it so the extension collects data on personal browsing, website activity, website content, and personally identifying information.
After looking through reviews, I saw the developer mention that these "additions" have always been there and are being disclosed due to an update in Mozilla's developer TOS
I don't see how a "user ID" is personally identifying data as many people go by an online username, not their real name, and so "personally identifying" in the context of personal data feels rather vague. I initially gave a one star after the update but I urge the developer to write an explanation in the "about" section outlining what about Mozilla's policy they're working under. I feel like suddenly seeing a "hey, this extension needs your personal data now" notification would lead to a justifiable outcry from users, especially with no further explanation. Users can look at the website for the API but most people won't do that, and it's up to the developer to be as clear and open as possible. I do not blame the users for immediately growing weary and angry, especially when I had to look through other negative comments just to find a dev response.
Mozilla themselves are already on thin ice in regards to our personal private data; no one wants a stranger trying to access it too.
In the most recent update (September 7th, 2026 as of writing this), the developers have made it so the extension collects data on personal browsing, website activity, website content, and personally identifying information.
After looking through reviews, I saw the developer mention that these "additions" have always been there and are being disclosed due to an update in Mozilla's developer TOS
I don't see how a "user ID" is personally identifying data as many people go by an online username, not their real name, and so "personally identifying" in the context of personal data feels rather vague. I initially gave a one star after the update but I urge the developer to write an explanation in the "about" section outlining what about Mozilla's policy they're working under. I feel like suddenly seeing a "hey, this extension needs your personal data now" notification would lead to a justifiable outcry from users, especially with no further explanation. Users can look at the website for the API but most people won't do that, and it's up to the developer to be as clear and open as possible. I do not blame the users for immediately growing weary and angry, especially when I had to look through other negative comments just to find a dev response.
Mozilla themselves are already on thin ice in regards to our personal private data; no one wants a stranger trying to access it too.
Respuesta del desarrollador
publicado el hace 7 díasThanks for explaining why the wording felt unclear.
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
RYD uses only the data needed to display dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Here’s what those permissions mean:
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new wording can sound alarming, but it doesn’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike
RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.
Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
RYD uses only the data needed to display dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Here’s what those permissions mean:
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new wording can sound alarming, but it doesn’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike