Revisiones de Return YouTube Dislike
Return YouTube Dislike por Dmitry Selivanov
5231 revisiones
- Se valoró con 5 de 5por Usuario de Firefox 20152964, hace un mesalright I was initially frightened by the personal data consent request in the 4.0.6 update just like others have stated in recent reviews. i am NOT good at reading code, but even still i can view every single commit made for this update on the github. i completely understand why people are worried about this update, but reacting based on emotions isn't going to find the truth. check the github, read the code, check the security faq, and be willing to learn.
i do also want to say to the developer that your response to people's reviews has been, in my eyes, very unprofessional. even though i personally believe that you're in the right, it's still important to treat customers with respect. the security FAQ that explains this whole situation is only on the github. i believe it should be front and center in this extension page's about section. there might be less uninformed outcry if it were that much more visible.
aside from that though, the new features are excellent and i look forward to using it more. thanks again for both your effort and the github contributorsRespuesta del desarrollador
publicado el hace 25 díasSorry, my previous reply was unnecessarily rude.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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 - Se valoró con 5 de 5por Kuri, hace un mes
- Se valoró con 5 de 5por Usuario de Firefox 18821540, hace un mesThank god my data isn't getting stolen. I was scared there for a second before reading the recent reviews and the developer response
Respuesta del desarrollador
publicado el hace 25 díasThanks. Yep - this new system gives a very scary impression.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
But in reality - the extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere. - Se valoró con 5 de 5por ddknight, hace un mes
- Se valoró con 5 de 5por ilikethisbrowser1164, hace un mesi, like many others, was confused about the new permissions and came here. then i took a look at the dev's replies and it all makes sense now
to other concerned folks: please read the dev's response to other reviews, and if you're still skeptical, the code is open-source, feel free to look yourselfRespuesta del desarrollador
publicado el hace 25 díasThanks for taking the time to leave a review.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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 - Se valoró con 5 de 5por JBoot8, hace un mesI was concerned about the new permissions required, but scrolled down and saw a reply from the developer explaining what was going on. Everything collected is only related to YouTube and is anonymized, the same as what previous versions were doing. The only thing that changed was how Mozilla classifies permissions.
Thank you to the dev for the explanation!Respuesta del desarrollador
publicado el hace un mesThanks for taking your time read. I agree, this new system gives a very scary impression.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
But in reality - the extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere. - Se valoró con 5 de 5por Usuario de Firefox 19583727, hace un mes
- Se valoró con 5 de 5por charizardcharz, hace un mes
- Se valoró con 5 de 5por Dream, hace un messtop review bombing, it’s open-source. if you have a problem with the code, just show it.
Respuesta del desarrollador
publicado el hace 25 díasThanks for taking the time to leave a review.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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 - Se valoró con 5 de 5por Koomongous, hace un mesI was concerned for a moment, but taking a look:
"From November 3, 2025, all new extensions must adopt the Firefox built-in data collection consent system. Extensions must state if and what data they collect or transmit. New versions and updates for add-ons created before November 3 don’t need to use this feature, but will have to at a later date."
This appears to apply in this case :)Respuesta del desarrollador
publicado el hace 25 díasThanks for taking the time to leave a review.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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 - Se valoró con 5 de 5por Nikitamce, hace un mes
- Se valoró con 1 de 5por rizzcum, hace un mes
- Se valoró con 5 de 5por astehlik, hace un mesWorks like a charm, thank you :)
To the review bombers: the changed permissions request comes due to a new consent mechanism in Firefox, NOT because the Add-on steals your data!Respuesta del desarrollador
publicado el hace 25 díasThanks for taking the time to leave a review.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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 - Se valoró con 1 de 5por ONEEX, hace un mes•I’m giving it a 3 for the policy – you’re either a developer or a politician🤡 – make up your mind!•
Respuesta del desarrollador
publicado el hace un mes"you’re either a developer or a politician🤡 – make up your mind"
'squse me? - Se valoró con 5 de 5por serg, hace un mesJust a must have, an essential add-on. And very well made. And made by a good person, who supports freedom and democracy. What's not to like?
Also the latest update is excellent. I think I'll go support you on Patreon for the additional features - they look really neat and it's a good idea.
Please continue doing this.Respuesta del desarrollador
publicado el hace 25 díasThanks for taking the time to leave a review.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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 Respuesta del desarrollador
publicado el hace 25 díasThanks for taking the time to leave a review.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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- Se valoró con 5 de 5por Vince, hace un mesFor those concerned about the new version, you can click "See all versions", download 3.0.0.18, extract with 7-Zip, and ask an AI to compare permissions and URL's with 4.0.6. It looks safe to me, but that's for you to decide.
Respuesta del desarrollador
publicado el hace un mesYep, that's one way, another is git history at https://github.com/Anarios/return-youtube-dislike/releases
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410 - Se valoró con 5 de 5por meowster, hace un mesi, like many others, was surprised by the notification telling me of recent permission changes, but i took the time to see what changed and now i am back to using it, simple.
you cannot review bomb because "dev is a russian spy", they support ukraine and even then it has no basis, let's not be silly.
thanks for the hard work.Respuesta del desarrollador
publicado el hace un mesSorry, my previous reply was unnecessarily rude.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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 - Se valoró con 5 de 5por zheryy, hace un mes
- Se valoró con 5 de 5por Stefan Pelskamp, hace un mes
- Se valoró con 5 de 5por rivage, hace un mesGiving you 5 stars to support you in these tough times of review bombing :)
Respuesta del desarrollador
publicado el hace 25 díasThanks for taking the time to leave a review.
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.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses the data it needs to show 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.
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 labels sound scary, but they don’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 - Se valoró con 5 de 5por bri, hace un mes
- Se valoró con 1 de 5por 2ndVenus, hace un mesRussian name...now asking for permissions the add-on clearly doesnt need in order to function. Yea screw that, im uninstalling. I dont care if it is open source, that doesnt give you a pass to spy. I dont feel safe having this installed any further. You dont need those permissions just to add a number onto a webpage! The browser warning is completely warranted and was the right thing for Firefox to do.
*You definitely do not need these permissions!*...unless you're up to no good.Respuesta del desarrollador
publicado el hace un mesYou could open the homepage of extension to know my position on russians. By a huge "support Ukraine" banner.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
> now asking for permissions the add-on clearly doesnt need in order to function.
a permission to access youtube and returnyoutubedislike are not needed for the extension to work?
Nothing in the extension changed - it’s open-source, so you can verify that yourself. What changed is how Mozilla labels privacy-related permissions.
Ajay, the author of SponsorBlock and DeArrow, has also raised this issue with Mozilla. He explains how the new wording can make an existing extension look like it suddenly started collecting new data, without making clear which websites it can access. You can read his post on Mozilla’s forum here: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
The extension only uses an anonymous, randomly generated ID, and the id of the video that you liked/disliked.
• YouTube access - needed to read the current video ID and show its dislike count.
• RYD API access - needed for API requests and diagnostics.
• Online/activity data - viewing, liking, or disliking videos.
• Personally identifiable information - RYD’s random private user ID used to count votes, not your real identity.
• Website content - mainly the video ID.
The new labels sound scary, but they describe the same data the extension has always used. - Se valoró con 1 de 5por Usuario de Firefox 17220816, hace un mes