Thanks 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

Danke 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

Thanks 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

Thanks 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

Yeah, it will be addressed later. Mozilla forbids data collection in private windows - which means you can't submit likes\dislikes in a private window. It isn't a problem, but requires additional coding, which I didn't have time for.

Thanks 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

Thanks 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

Sorry the message about new features bothered you. It’s shown only once during the lifetime of the extension, and it’s timed to appear after a browser restart - hopefully the least disruptive moment.

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

Handling YouTube-scale traffic and storing dozens of terabytes of like/dislike data on a school-lunch budget ain’t that easy. The funding from these features is what keeps RYD’s servers running.

And as for the permissions:

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

Thanks 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

Thanks 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

You don't have to log in. Log in is just for advanced features - which you don't have to use.

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

Sorry the message about new features bothered you. It’s shown only once during the lifetime of the extension, and it’s timed to appear after a browser restart - hopefully the least disruptive moment.

Handling YouTube-scale traffic and storing dozens of terabytes of like/dislike data on a school-lunch budget ain’t that easy. The funding from these features is what keeps RYD’s servers running.

And as for the permissions:

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

Sorry the message about new features bothered you. It’s shown only once during the lifetime of the extension, and it’s timed to appear after a browser restart - hopefully the least disruptive moment.

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

Handling YouTube-scale traffic and storing dozens of terabytes of like/dislike data on a school-lunch budget ain’t that easy. The funding from these features is what keeps RYD’s servers running.

And as for the permissions:

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

Sorry the message about new features bothered you. It’s shown only once during the lifetime of the extension, and it’s timed to appear after a browser restart - hopefully the least disruptive moment.

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

Handling YouTube-scale traffic and storing dozens of terabytes of like/dislike data on a school-lunch budget ain’t that easy. The funding from these features is what keeps RYD’s servers running.

And as for the permissions:

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

Thanks 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

Sorry the message about new features bothered you. It’s shown only once during the lifetime of the extension, and it’s timed to appear after a browser restart - hopefully the least disruptive moment.

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

Handling YouTube-scale traffic and storing dozens of terabytes of like/dislike data on a school-lunch budget ain’t that easy. The funding from these features is what keeps RYD’s servers running.

And as for the permissions:

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

Thanks 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