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.

Aggreates are, by definition, not personal.

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.

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.

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.

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

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.

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.

TLDR: Random user id used for counting votes is personal data by law and by mozillas rules. that's why this warning appears.

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.

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

TLDR: Random user id used for counting votes is personal data by law and by mozillas rules. that's why this warning appears.

I understand why the permission labels changed how you felt about the extension.

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 needed 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 can sound worrying, but they don’t give the extension access to any more websites.

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

TLDR: Random user id used for counting votes is personal data by law and by mozillas rules. that's why this warning appears.


I understand why that update prompt put you off.

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 uses only 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.

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

TLDR: Random user id used for counting votes is personal data by law and by mozillas rules. that's why this warning appears.

I understand why seeing those labels raised 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.

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 wording can sound alarming, but it doesn’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

TLDR: Random user id used for counting votes is personal data by law and by mozillas rules. that's why this warning appears.


Thanks for asking what those data categories are used for.

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

Those labels can sound scary, but they don’t let the extension access additional websites.

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

TLDR: Random user id used for counting votes is personal data by law and by mozillas rules. that's why this warning appears.

Thanks for asking about the notification. I understand why it raised 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.

The extension only uses data needed 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 wording can sound worrying, but it doesn’t give the extension access to any more websites.

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

TLDR: Random user id used for counting votes is personal data by law and by mozillas rules. that's why this warning appears.

I understand why that notification made you uncomfortable.

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 labels can sound alarming, 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

Wdym "prevents"? There's a usual X im top right corner - you close it and never see it again. Sorry if it was annoying, most of the money is spent on the hosting servers.

Sorry, it's only supposed to be shown once in a lifetime. Did you see it more than once?

It should only have been once on update install. (i.e. two times in a total of five years, if I'm not mistaken) You have seen it multiple times? Do you have "stock" mozilla - not a modified one? (waterfox, etc)

Sorry the dislike counts aren’t showing for you. I understand how frustrating that is.

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 can sound worrying, but they don’t give the extension access to any more websites.

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

I understand why the permission request put you off.

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

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 alarming, 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