Pour utiliser ces modules complémentaires, vous devez télécharger Firefox.

Connexion
Icône du module

Critiques pour Return YouTube Dislike

Return YouTube Dislike par Dmitry Selivanov

4,5 étoiles sur 5
5
4 385
4
193
3
88
2
67
1
499
5 232 notes
  • par sealovedmoon, il y a 12 jours
    I think the description needs updating.

    Everyone is freaking out about the new permissions and instead of replying to every one-star/two-star review that complains, it can be advertised in the description where indeed "everyone can see it".

    Lastly, everyone including me, is complaining about the premium analytics, which are also not advertised in the description. This is not an add-on that simply returns the dislikes, so please act like it. Rewrite the description accordingly. You don't deserve that Recommended badge, it's as outdated as your description.
  • par Cheese Louise, il y a 12 jours
  • par Utilisateur ou utilisatrice 18304804 de Firefox, il y a 12 jours
  • par stair, il y a 12 jours
    Amazing add-on, I just wish you could see if you've disliked a video or not. This seems to be a new thing but I can only see the number of dislikes and not the actual dislike button itself
  • par gyah, il y a 12 jours
    You add "buy premium" popups, I rate you one star and uninstall. Simple as.
  • par BananaSplit97, il y a 12 jours
    I can safely say this extension isn't harvesting my data (the developer isn't being insidious in what they're saying, it really is free to check the Github), but this extension isn't really what I downloaded it for anymore.

    Opening Youtube to see the new interface that- while I confidently believe is entirely human made- just reads like generic vibe-coded design was offputting. The new window isn't needed and serves as yet another case of "fixing what isn't broken".

    The plugin's behavior wasn't consistent anyway, with the like to dislike ratio being dramatically different from what it actually was supposed to be. I reckon one's better off without a plugin like this anyway. When they DO work, it's "kinda sorta".

    It still does what it says on the box, even if not perfect, but I think you're better off without from the get.
  • par Skibidi, il y a 13 jours
    RYD does not harvest your data, go read the github.
  • par SilverGuy, il y a 13 jours
  • par galaxy chill, il y a 13 jours
    "Required data collection, according to the developer:
    - Browsing activity
    - Personally identifying information
    - Website activity
    - Website content

    Enough said. Basically confessing to spying on you"

    same.
  • par AJ, il y a 13 jours
    Required data collection, according to the developer:
    - Browsing activity
    - Personally identifying information
    - Website activity
    - Website content

    Enough said. Basically confessing to spying on you.
  • par Utilisateur ou utilisatrice 20183682 de Firefox, il y a 14 jours
    The extension has started to NOT work on Private Windows with the release of the latest update. My copy of Firefox is heavily modded and therefore doesn't have the feature to create non-Private Windows. Firefox tells me that "this extension is not allowed to work on Private Windows", meaning I cannot toggle the "allowed on Private Windows" setting. This situation renders this add-on absolutely useless. Please fix.
  • par Spark-ool, il y a 14 jours
    Good add-on, and good for explaining what the new data requirements mean. But some reviews are right : you should explain this in the description of the actual add-on, not just in replies to bad reviews.
  • par dan9, il y a 14 jours
  • par Dugor, il y a 15 jours
    Used to be great, now is yet another data miner.

    Réponse du développeur

    mis en ligne : il y a 14 jours
    Thanks for sharing your concerns.

    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.

    The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.

    RYD 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.

    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 labels can sound worrying, 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
  • par Utilisateur ou utilisatrice 20179589 de Firefox, il y a 15 jours
    Used to be great, but does not work anymore for me.

    Removed from browser after oblique request to collect personal info.

    Réponse du développeur

    mis en ligne : il y a 15 jours
    the extenion didn't change - Mozillas processes changed.

    Here's the same problem discussed by Sponsorblock's author:
    https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

    "Personal data" mentioned - is the random user id used to count likes and dislikes
    "Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
    "Website activity" - clicking likes and dislikes.

    This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.
  • par wo, il y a 15 jours
    While permissions may not have changed overall, the author's attitude towards the use of that data has. Begging for subscribers for a "premium" version that, in short, exposes the exact kind of analytics - even in aggregate - that most people who use Firefox abhor.

    We've known in research communities that aggregate data is easily deaggregated using metadata or side-channel information, all of which this plugin's author has access to.

    I took the time to create an account here just to file this specific review.

    To the addon creator: Do better.

    Réponse du développeur

    mis en ligne : il y a 15 jours
    Aggreates are, by definition, not personal.
  • par Utilisateur ou utilisatrice 19964793 de Firefox, il y a 16 jours
    I DON'T KNOW WHAT'S GOING ON WHEN I WAS NOTIFIED BY YOUTUBE THAT IT WANTED PERSONAL INFO, BUT I WISH THEY'D LIST EXACTLY WHAT IS BEING TAKEN.

    Réponse du développeur

    mis en ligne : il y a 15 jours
    I understand why you want a clear explanation of those data categories.

    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.

    The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.

    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.

    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 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
  • par WStegem, il y a 16 jours
    Using the changelog page to push a patreon advertisement is really scummy.
  • par Utilisateur ou utilisatrice 16494765 de Firefox, il y a 16 jours
    1 star and removed from my browser after request for new permissions (serious privacy concerns). Not even close to worth it.

    Réponse du développeur

    mis en ligne : il y a 16 jours
    the extenion didn't change - Mozillas processes changed.

    Here's the same problem discussed by Sponsorblock's author:
    https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

    "Personal data" mentioned - is the random user id used to count likes and dislikes
    "Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
    "Website activity" - clicking likes and dislikes.

    This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.
  • par cbohorquezm, il y a 16 jours
    Why do you require new permissions, for no new functionality? 1 star until clarified or removed.

    Réponse du développeur

    mis en ligne : il y a 16 jours
    As I've replied to many - the extenion didn't change - Mozillas processes changed.

    Here's the same problem discussed by Sponsorblock's author:
    https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

    "Personal data" mentioned - is the random user id used to count likes and dislikes
    "Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
    "Website activity" - clicking likes and dislikes.

    This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.
  • par Utilisateur ou utilisatrice 20177296 de Firefox, il y a 16 jours
    Requiring new permissions but no easily accessible way to tell why they're needed. Should update the extension description here or on your website to explain what changed.

    Réponse du développeur

    mis en ligne : il y a 16 jours
    the extenion didn't change - Mozillas processes changed.

    Here's the same problem discussed by Sponsorblock's author:
    https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

    "Personal data" mentioned - is the random user id used to count likes and dislikes
    "Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
    "Website activity" - clicking likes and dislikes.

    This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.
  • par Utilisateur ou utilisatrice 14725694 de Firefox, il y a 16 jours
    Instead of replying to every 1 star reviews with the same info about the new permissions notification you should really just update the description of the extension to explain why each permission is needed. A direct link to the github repo would help too.

    Edit: Dude you just replied to my review instead of putting the info where everyone can see it. What's wrong with you? You have the opportunity to stop the spread of misinformation instead of wasting time replying to every review individually, just do it.

    Réponse du développeur

    mis en ligne : il y a 16 jours
    Hi, direct link: https://github.com/Anarios/return-youtube-dislike/

    Here's the same problem discussed by Sponsorblock's author:
    https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

    As I've replied to many - the extenion didn't change - Mozillas processes changed.

    "Personal data" mentioned - is the random user id used to count likes and dislikes
    "Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
    "Website activity" - clicking likes and dislikes.

    This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.
  • par Utilisateur ou utilisatrice 17646948 de Firefox, il y a 16 jours
  • par mlatpren, il y a 17 jours
  • par sophienix neuroi, il y a 17 jours
    the new perms are fucking stupid all my other extensions do not ask this it is not need. saying that mozilla forcing you guys to do this is bs. i will not be updating also not only that it does not ask for data and info in chrome / opera. just found out how to extract the file i now have a backup.

    Réponse du développeur

    mis en ligne : il y a 16 jours
    " saying that mozilla forcing you guys to do this is bs" - that is exactly what is happening. Every extension will go through this with the next updates.

    Here's the same problem discussed by Sponsorblock's author:
    https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

    As I've replied to many - the extenion didn't change - Mozillas processes changed.

    "Personal data" mentioned - is the random user id used to count likes and dislikes
    "Browsing activity" = detecting that you navigated to the next video to show you the dislikes for the next video
    "Website activity" - clicking likes and dislikes.

    This is how the extension worked from the day one - but now Mozilla requires explicit user consent for this. And they do it on update release - which makes users think that something in the extension changed.