Thanks for the feedback about the permission labels.

RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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.

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

Ajay, the author of SponsorBlock and DeArrow, discusses the same problem here:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD uses only the data 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.

Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.

Browsing activity - moving to 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 work out dislike estimates.

Website activity - clicking Like or Dislike.

Again, this concerns activity on YouTube. The extension isn’t watching everything you do across the internet - these site permissions simply don’t allow that.

Those new labels can sound scary, but they don’t allow the extension to access more websites.

RYD’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for raising your concern about 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.

The same issue is discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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, we’re talking about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t with these site permissions.

The new labels can sound alarming, but they don’t give the extension access to additional websites.

RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for 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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD only uses the data needed 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 - moving to 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 work out 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’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike

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.

Ajay, the author of SponsorBlock and DeArrow, discusses the same problem here:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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.

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 concerns activity on YouTube. The extension isn’t watching everything you do across the internet - these site permissions simply don’t allow that.

Those new labels can sound scary, but they don’t allow the extension to access more websites.

RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for the feedback about the permission labels.

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 same issue is discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD uses only the data 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.

Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.

Browsing activity - moving to 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 work out dislike estimates.

Website activity - clicking Like or Dislike.

Again, we’re talking about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t with these site permissions.

The new labels can sound alarming, but they don’t give the extension access to additional websites.

RYD’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for taking the time to share 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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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 raising your concern about 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, discusses the same problem here:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD only uses the data needed 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 - moving to 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 work out dislike estimates.

Website activity - clicking Like or Dislike.

Again, this concerns activity on YouTube. The extension isn’t watching everything you do across the internet - these site permissions simply don’t allow that.

Those new labels can sound scary, but they don’t allow the extension to access more websites.

RYD’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for 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 same issue is discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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.

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, we’re talking about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t with these site permissions.

The new labels can sound alarming, but they don’t give the extension access to additional websites.

RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike

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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD uses only the data 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.

Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.

Browsing activity - moving to 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 work out 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’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for the feedback about the permission labels.

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, discusses the same problem here:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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 concerns activity on YouTube. The extension isn’t watching everything you do across the internet - these site permissions simply don’t allow that.

Those new labels can sound scary, but they don’t allow the extension to access 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.

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 same issue is discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

The message about new features is 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 only uses the data needed 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 - moving to 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 work out dislike estimates.

Website activity - clicking Like or Dislike.

Again, we’re talking about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t with these site permissions.

The new labels can sound alarming, but they don’t give the extension access to additional websites.

RYD’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for raising your concern about 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.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

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.

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.

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, discusses the same problem here:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

The message about new features is 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 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.

Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.

Browsing activity - moving to 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 work out dislike estimates.

Website activity - clicking Like or Dislike.

Again, this concerns activity on YouTube. The extension isn’t watching everything you do across the internet - these site permissions simply don’t allow that.

Those new labels can sound scary, but they don’t allow the extension to access more websites.

RYD’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike

Sorry the message about new features bothered you.

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 same issue is discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

The message about new features is 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:

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, we’re talking about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t with these site permissions.

The new labels can sound alarming, but they don’t give the extension access to additional websites.

RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for the feedback about the permission labels.

RYD hasn’t changed how it handles your data. What changed is how Mozilla labels these permissions - not what the extension does with your data.

Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD only uses the data needed 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 - moving to 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 work out 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’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for 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.

Ajay, the author of SponsorBlock and DeArrow, discusses the same problem here:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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.

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 concerns activity on YouTube. The extension isn’t watching everything you do across the internet - these site permissions simply don’t allow that.

Those new labels can sound scary, but they don’t allow the extension to access more websites.

RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike

Thanks for raising your concern about 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.

The same issue is discussed by Ajay, the author of SponsorBlock and DeArrow:
https://discourse.mozilla.org/t/the-new-data-transmission-permissions-seem-to-be-misleading-to-users/149410

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

RYD uses only the data 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.

Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.

Browsing activity - moving to 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 work out dislike estimates.

Website activity - clicking Like or Dislike.

Again, we’re talking about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t with these site permissions.

The new labels can sound alarming, but they don’t give the extension access to additional websites.

RYD’s source code is public, so you can check how it works: https://github.com/Anarios/return-youtube-dislike