Return YouTube Dislike incelemeleri
Return YouTube Dislike geliştiren: Dmitry Selivanov
Firefox kullanıcısı 18821540 adlı kullanıcının incelemesi
5 üzerinden 5 puan
yazan: Firefox kullanıcısı 18821540, 22 gün önceThank god my data isn't getting stolen. I was scared there for a second before reading the recent reviews and the developer response
Geliştiricinin yanıtı
gönderilme: 22 gün önceThanks. Yep - this new system gives a very scary impression.
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
But in reality - the extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere.
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
But in reality - the extension can only access these permissions on two sites - YouTube and it's own returnyoutubedislike - on all other sites it's not even allowed to "turn on".
Personally identifiable information - RYD’s randomly generated private user ID used to count votes, not your real identity.
Browsing activity - i.e. navigating to the next video, so that the next dislikes can be shown
Website content - i.e. the like\dislike container element
Website activithy - i.e. clicking like or dislike button.
As I already said - only on YouTube. Not everywhere.
5.212 inceleme
- 5 üzerinden 5 puanyazan: Firefox kullanıcısı 20200698, 2 saat önceNOTHING HAS CHANGED, you can still opt-out of data being collected under the Options tab > "Disable logging to console" for this addon. This has always been there, it's just the FireFox had changed their policy so addons/extensions now have to report this.
Some people are just too quick to judge before verifying, lol. - 5 üzerinden 1 puanyazan: King, 4 saat önce
- 5 üzerinden 1 puanyazan: Firefox kullanıcısı 17431847, 4 saat önceRecent update started to collect information, browsing data, etc... So it look like it turned into spyware.
- 5 üzerinden 1 puanyazan: Firefox kullanıcısı 20196980, 7 saat önce
- 5 üzerinden 1 puanyazan: VestraPater, 7 saat önce
- 5 üzerinden 1 puanyazan: Firefox kullanıcısı 17975154, 18 saat önce
- 5 üzerinden 1 puanyazan: Nakita, bir gün önceNach dem Update kam die Meldung für neue benötigte Berechtigungen. Die Berechtigungen zu Aktivitäten, etc. sind völlig unnötig und zählen für mich zum Datendiebstahl. Daher wieder entfernt
- 5 üzerinden 1 puanyazan: kinge, bir gün önce
- 5 üzerinden 1 puanyazan: Firefox kullanıcısı 20197346, bir gün öncenow you injecting ads and beg for money???
- 5 üzerinden 1 puanyazan: 123424542234524, 2 gün önceScrew your data harvesting update. As soon as there is a viable alternative I am switching to that and I recommend everyone else do the same
- 5 üzerinden 1 puanyazan: Firefox kullanıcısı 20196369, 2 gün önceThe fact that the data processing method hasn't changed means it was being collected all along.
- 5 üzerinden 1 puanyazan: Cody Jade, 2 gün önce
- 5 üzerinden 1 puanyazan: Firefox kullanıcısı 19553534, 3 gün önceI have disabled the extension after getting a popup reading "New required data collection: The developer says the extension will collect: personally identifying information, browsing activity, website content, website activity"
The developer has been responding to this by saying it's simply a matter of misleading descriptions because of updated FireFox policy: "Here’s the same problem discussed by Ajay, the author of SponsorBlock and DeArrow: (URL)"
The problem? Ajay's extensions SponsorBlock and DeArrow, both of which I have installed and updated to the latest version, only say they access data for specific domains, and listed are domains like dearrow.ajay.app or youtube.com or sponsor.ajay.app.
Why is it that the dev's shining example seems immune from this policy change? I don't buy it.
With how little communication is being done, I'm not ready to let the updated extension run on my computer, and you shouldn't be either. - 5 üzerinden 2 puanyazan: Firefox kullanıcısı 14207324, 3 gün önceI agree with Infrequent_User's review for how the developer should address privacy concerns in regards to Mozilla changing the way addon's permissions are explained.
I am reposting Infrequent_User's words below:
" I don't see how a "user ID" is personally identifying data as many people go by an online username, not their real name, and so "personally identifying" in the context of personal data feels rather vague. I initially gave a one star after the update but I urge the developer to write an explanation in the "about" section outlining what about Mozilla's policy they're working under. I feel like suddenly seeing a "hey, this extension needs your personal data now" notification would lead to a justifiable outcry from users, especially with no further explanation. Users can look at the website for the API but most people won't do that, and it's up to the developer to be as clear and open as possible. I do not blame the users for immediately growing weary and angry, especially when I had to look through other negative comments just to find a dev response. " - 5 üzerinden 1 puanyazan: Firefox kullanıcısı 18428698, 3 gün önceI'm not giving you my data.
Gross, pointless, and creepy.
You should all be incredibly ashamed of yourselves. - 5 üzerinden 5 puanyazan: Kamik, 3 gün önce
Geliştiricinin yanıtı
gönderilme: 3 gün önceThanks 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.
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- 5 üzerinden 1 puanyazan: Guto, 3 gün önceNow they have to explicitly state that they collect information about users. Before, they were collecting it without users’ consent.
Geliştiricinin yanıtı
gönderilme: 3 gün önceThanks 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.
RYD uses only 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 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 - 5 üzerinden 5 puanyazan: Firefox kullanıcısı 12720423, 3 gün önceDoes what it claims well. Everyone who's freaking about the permissions change needs to calm down and go read up on it more. It's not doing anything nefarious/different. It's not spying on everything you do. It's not saving your youtube info.
You can go into extensions settings and view permissions for an extension in Firefox and it shows you the sites/urls that the extension is allowed to operate on. If it's not listed there, then Firefox itself won't allow the extension to access information on other sites.
Scroll down and read comments from the developer which have more complete information on what actually happened.Geliştiricinin yanıtı
gönderilme: 3 gün önceThanks for taking the time to leave a review and explain 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
RYD only uses the data it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Here’s what those permissions mean:
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels can sound worrying, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike - 5 üzerinden 1 puanyazan: Firefox kullanıcısı 11533654, 3 gün önceAfter recent update extension began to collect your sensitive data for sale. You can see it in recent changelogs.
Geliştiricinin yanıtı
gönderilme: 3 gün önceI understand why those permission 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.
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.
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 - 5 üzerinden 2 puanyazan: Infrequent_User, 3 gün önceBE CAUTIOUS:
In the most recent update (September 7th, 2026 as of writing this), the developers have made it so the extension collects data on personal browsing, website activity, website content, and personally identifying information.
After looking through reviews, I saw the developer mention that these "additions" have always been there and are being disclosed due to an update in Mozilla's developer TOS
I don't see how a "user ID" is personally identifying data as many people go by an online username, not their real name, and so "personally identifying" in the context of personal data feels rather vague. I initially gave a one star after the update but I urge the developer to write an explanation in the "about" section outlining what about Mozilla's policy they're working under. I feel like suddenly seeing a "hey, this extension needs your personal data now" notification would lead to a justifiable outcry from users, especially with no further explanation. Users can look at the website for the API but most people won't do that, and it's up to the developer to be as clear and open as possible. I do not blame the users for immediately growing weary and angry, especially when I had to look through other negative comments just to find a dev response.
Mozilla themselves are already on thin ice in regards to our personal private data; no one wants a stranger trying to access it too.Geliştiricinin yanıtı
gönderilme: 3 gün önceThanks for explaining why the wording felt unclear.
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 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 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 - 5 üzerinden 1 puanyazan: Firefox kullanıcısı 19563331, 4 gün önce
Geliştiricinin yanıtı
gönderilme: 3 gün önceThanks for sharing your concerns about the update.
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 it needs to show dislikes and count votes.
Its site permissions cover YouTube and its own API at returnyoutubedislikeapi.com. RYD doesn’t read other websites, and these site permissions cannot be used to access them.
Here’s what those permissions mean:
Personally identifiable information - RYD’s randomly generated, anonymous user ID, used to count votes. This isn’t your Google or YouTube account.
Browsing activity - opening the next YouTube video, so the extension can send its video ID and fetch the new dislike count.
Website content - things like the visible like count, which helps calculate dislike estimates.
Website activity - clicking Like or Dislike.
Again, this is about YouTube activity. The extension isn’t watching everything you do across the internet - it simply can’t do that with these site permissions.
The new labels can sound worrying, but they don’t give the extension access to more websites.
RYD is open source, so you can see how it works: https://github.com/Anarios/return-youtube-dislike- 5 üzerinden 1 puanyazan: Firefox kullanıcısı 18717684, 5 gün önceGood job bud, keep up the greediness and see how far it gets you in life.
Geliştiricinin yanıtı
gönderilme: 3 gün önceI’m sorry the changes have been frustrating.
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.
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