Reviews for Return YouTube Dislike
Return YouTube Dislike by Dmitry Selivanov
Review by THX1138
Rated 1 out of 5
by THX1138, 14 hours agoDas ist nicht mehr die ursprüngliche Erweiterung. Sie entwickelt sich in eine Richtung, die mir nicht gefällt. Habe kein gutes Gefühl. Wird deinstalliert!
Developer response
posted 14 hours agoDanke für dein Feedback. Es tut mir leid, dass du wegen der Erweiterung ein ungutes Gefühl hast.
Die Erweiterung wird tatsächlich von Mozilla empfohlen, sie halten sie also nicht für schädlich oder gefährlich.
RYD hat den Umgang mit deinen Daten nicht geändert. Geändert hat sich, wie Mozilla diese Berechtigungen bezeichnet - nicht, was die Erweiterung mit deinen Daten macht.
Ajay, der Entwickler von SponsorBlock und DeArrow, hat dieses Problem ebenfalls bei Mozilla angesprochen. Er erklärt, wie die neue Formulierung den Eindruck erwecken kann, eine bestehende Erweiterung hätte plötzlich angefangen, neue Daten zu sammeln, ohne klarzustellen, auf welche Websites sie zugreifen kann. Seinen Beitrag im Mozilla-Forum kannst du hier lesen: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
Die Erweiterung nutzt nur die Daten, die sie braucht, um Dislikes anzuzeigen und Stimmen zu zählen.
Ihre Website-Berechtigungen gelten für YouTube und ihre eigene API unter returnyoutubedislikeapi.com. RYD liest keine anderen Websites aus, und diese Website-Berechtigungen können nicht genutzt werden, um auf sie zuzugreifen.
Personenbezogene Daten - die von RYD zufällig generierte, anonyme Benutzer-ID, mit der Stimmen gezählt werden. Das ist nicht dein Google- oder YouTube-Konto.
Surfaktivität - das Öffnen des nächsten YouTube-Videos, damit die Erweiterung dessen Video-ID senden und die neue Dislike-Anzahl abrufen kann.
Website-Inhalte - zum Beispiel die sichtbare Like-Anzahl, die bei der Berechnung der geschätzten Dislike-Zahlen hilft.
Website-Aktivität - das Klicken auf Like oder Dislike.
Noch einmal: Hier geht es um Aktivitäten auf YouTube. Die Erweiterung verfolgt nicht alles, was du im Internet machst - mit diesen Website-Berechtigungen kann sie das schlicht nicht.
Die neuen Bezeichnungen klingen beunruhigend, geben der Erweiterung aber keinen Zugriff auf weitere Websites.
RYD ist Open Source, du kannst dir also ansehen, wie es funktioniert: https://github.com/Anarios/return-youtube-dislike
Die Erweiterung wird tatsächlich von Mozilla empfohlen, sie halten sie also nicht für schädlich oder gefährlich.
RYD hat den Umgang mit deinen Daten nicht geändert. Geändert hat sich, wie Mozilla diese Berechtigungen bezeichnet - nicht, was die Erweiterung mit deinen Daten macht.
Ajay, der Entwickler von SponsorBlock und DeArrow, hat dieses Problem ebenfalls bei Mozilla angesprochen. Er erklärt, wie die neue Formulierung den Eindruck erwecken kann, eine bestehende Erweiterung hätte plötzlich angefangen, neue Daten zu sammeln, ohne klarzustellen, auf welche Websites sie zugreifen kann. Seinen Beitrag im Mozilla-Forum kannst du hier lesen: https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410
Die Erweiterung nutzt nur die Daten, die sie braucht, um Dislikes anzuzeigen und Stimmen zu zählen.
Ihre Website-Berechtigungen gelten für YouTube und ihre eigene API unter returnyoutubedislikeapi.com. RYD liest keine anderen Websites aus, und diese Website-Berechtigungen können nicht genutzt werden, um auf sie zuzugreifen.
Personenbezogene Daten - die von RYD zufällig generierte, anonyme Benutzer-ID, mit der Stimmen gezählt werden. Das ist nicht dein Google- oder YouTube-Konto.
Surfaktivität - das Öffnen des nächsten YouTube-Videos, damit die Erweiterung dessen Video-ID senden und die neue Dislike-Anzahl abrufen kann.
Website-Inhalte - zum Beispiel die sichtbare Like-Anzahl, die bei der Berechnung der geschätzten Dislike-Zahlen hilft.
Website-Aktivität - das Klicken auf Like oder Dislike.
Noch einmal: Hier geht es um Aktivitäten auf YouTube. Die Erweiterung verfolgt nicht alles, was du im Internet machst - mit diesen Website-Berechtigungen kann sie das schlicht nicht.
Die neuen Bezeichnungen klingen beunruhigend, geben der Erweiterung aber keinen Zugriff auf weitere Websites.
RYD ist Open Source, du kannst dir also ansehen, wie es funktioniert: https://github.com/Anarios/return-youtube-dislike
5,041 reviews
- Rated 5 out of 5by Firefox user 20155700, 3 hours agoLeaving a five-star review to support in wake of recent data collection labeling requirements change. Thanks for the work you do on this add-on!
Developer response
posted 2 hours agoThanks for your support and 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.
The extension uses only the data it needs 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 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 - Rated 5 out of 5by Greyshirk, 4 hours agoThanks for the clear concise responses to the permissions update.
Developer response
posted 4 hours agoThanks for reading the explanation and sharing your feedback.
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 only data the extension uses is what 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 may 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 - Rated 1 out of 5by Firefox user 18608524, 4 hours ago
- Rated 1 out of 5by William Kane, 4 hours ago
- Rated 5 out of 5by Firefox user 12490047, 5 hours agoThanks for explaining the 'new permissions'. It's a shame about how they're labelling this, because it rather dilutes the meaning of such a warning.
Developer response
posted 5 hours agoThanks for taking the time to read the explanation and 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.
The extension uses only 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 can 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 - Rated 1 out of 5by Moises Lima, 5 hours ago
Developer response
posted 6 hours agoThanks for leaving 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.
To show dislikes and count votes, the extension only uses the data it needs.
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 may 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- Rated 5 out of 5by Firefox user 20155385, 8 hours ago
- Rated 5 out of 5by Dan, 9 hours ago
- Rated 1 out of 5by Firefox user 20155287, 10 hours agoyeah so why do you need my personally identifying data?
and where can we verify you aren't just selling it to data brokers.Developer response
posted 9 hours agoUnrortunatelly a randomly generated id, used to count your likes and dislikes (without any link to your email or YouTube account) is still "personally identifying data".
and my standard copy-pasta full explainer:
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
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.
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 here: https://github.com/Anarios/return-youtube-dislike - Rated 1 out of 5by JC, 10 hours ago
- Rated 1 out of 5by Firefox user 19780246, 10 hours ago"The developer says the extension will collect: personally identifying information, browsing activity, web site content, website activity" Get this spyware off my device
Developer response
posted 10 hours agoThanks for sharing your concerns.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
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.
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 here: https://github.com/Anarios/return-youtube-dislike - Rated 5 out of 5by ARMINION, 10 hours ago
- Rated 5 out of 5by Firefox user 17856566, 10 hours ago
- Rated 1 out of 5by Firefox user 20100239, 11 hours agospyware, please ignore whatever the 'developer' has claimed, I'm sure they've been hacked and this is a compromised account now, reported.
Developer response
posted 11 hours agoNo, I haven't been hacked. I just have to copy paste the same response everywhere because people don't bother to read.
The extension is actually recommended by Mozilla
But anyways - thanks for the feedback. Let me explain what those permissions mean.
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 - Rated 2 out of 5by Judas, 12 hours agomy browser has been taking a whole lot more memory since this got updated...
Developer response
posted 11 hours agoSorry you’re having trouble with memory usage.
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 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 - Rated 5 out of 5by Firefox user 13927441, 12 hours agoThe developer claims that Mozilla changed the labeling system, but I have a lot of extensions installed, and none of them asked for additional permissions to collect my data. Why do I smell bs?
EDIT: I asked Mozilla about this situation, and they confirmed that the developer isn't lying. So, I am changing my review to 5 stars and would like to apologize to the developer for my accusations.
I also asked them to post some kind of clarifying message on the add-on's page.Developer response
posted 12 hours agoOther extenions haven't requested it because they haven't gone throught the "data disclosure" process yet (check Sponsorblock's and De-Arrow author's response in my discord server). This extension is just among the first few unlucky ones. Mozilla are actually considering changing this labeling system to make it more clear to users about what is going on.
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
EDIT: Hey, thanks a lot. - Rated 1 out of 5by Firefox user 20155068, 12 hours agoNew permission requirements make this an automatic hard pass - recommendation should be revoked.
Edit in response to the developer:
I think you're missing the point.
The issue isn't that Mozilla suddenly gave RYD access to the whole internet. It's that Mozilla has now made explicit data collection that was apparently already happening, but wasn't previously disclosed.
And "anonymous user ID" doesn't really solve that. It's a persistent identifier tied to YouTube activity. That's pseudonymous, not meaningfully anonymous.
More importantly, the extension being open source only tells us what gets sent. The RYD backend is still a black box. Once that data leaves the browser, we're being asked to trust RYD not to retain, correlate, profile, monetize, or sell it — particularly after we've learned the collection was previously undeclared.
The fact that the data is useful to RYD doesn't mean it's necessary for the extension's basic advertised function. Showing a dislike count doesn't inherently require building a persistent record of users' YouTube activity.
And the Chrome and Firefox stores don't even have identical data-collection declarations, so "Mozilla just changed the labels" doesn't really explain everything away.
That's why I find the response a bit tone deaf. The concern isn't "OMG, RYD can now read every website." It's "why does a simple dislike-count extension need to collect this much information about my YouTube activity, and why was that collection not clearly disclosed before?"
Edit 2:
The vote/registration pipeline isn't anonymous — it's pseudonymous and persistent, and your own code and privacy policy confirm it:
1) Persistent identifier: generateUserId() creates a unique 36-character ID at registration, which createBrowserCredentialStore() persists in browser.storage.sync. It isn't rotated per session or video.
2) Persistent correlation: performVote() sends { userId, videoId, value } to /interact/vote and /interact/confirmVote. Reusing the same identifier lets your backend associate votes and video activity with the same user over time. That's pseudonymization, not anonymization.
3) Additional identifiers: Your privacy policy says IP address and request time are also collected. Those can further associate the persistent identifier with a real-world network connection.
4) Your own policy treats the identifier as personal data. So describing it to users simply as an "anonymous" ID is misleading. Randomly generated does not mean anonymous when the value is persistent and specifically used to correlate records.
The appropriate description is pseudonymous, persistent user identification, not anonymous collection.Developer response
posted 12 hours ago"why simple dislike-count extension need to collect this much information about my YouTube activity" - it's explained under every review here. Try reading the response, please. I literally list every point, and why it is there. They are trivial, like detecting what video is playing (to show dislikes for that video) and detecting that like or dislike button was clicked.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
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
I'll copy-paste it once more
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. - Rated 5 out of 5by User, 12 hours agoThank you so much for making this extension that helps us to not get scammed on YouTube, among other things.
Developer response
posted 12 hours agoThanks 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 Developer response
posted 13 hours agoThanks 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- Rated 5 out of 5by Dex Luther, 15 hours agoIt's amazing people take the time to leave a 1-star review, but don't bother to take that time to look anything up.
It's still sad that we even need an extension like this, but it's not doing what the 1-star reviews will have you think it does.Developer response
posted 14 hours agoThanks 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 Developer response
posted 15 hours agoThanks for the feedback.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
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.
Let me explain 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- Rated 5 out of 5by Gresol, 16 hours ago
Developer response
posted 15 hours agoThanks for the feedback.
The extension is actually recommended by Mozilla, so they do not consider it harmful or dangerous.
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.
Let me explain 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