Return YouTube Dislike에 대한 리뷰
Return YouTube Dislike 제작자: Dmitry Selivanov
AnonymousX86 님의 리뷰
개발자 답글
13시간 전에 게시됨Thanks 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
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,200개
- 5점 만점에 1점Firefox 사용자 19553534 님, 4시간 전I 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점 만점에 2점Firefox 사용자 14207324 님, 6시간 전I 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점 만점에 1점Firefox 사용자 18428698 님, 9시간 전I'm not giving you my data.
Gross, pointless, and creepy.
You should all be incredibly ashamed of yourselves. 개발자 답글
13시간 전에 게시됨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.
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개발자 답글
13시간 전에 게시됨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.
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점 만점에 5점Firefox 사용자 12720423 님, 18시간 전Does 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.개발자 답글
13시간 전에 게시됨Thanks 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점 만점에 1점Firefox 사용자 11533654 님, 하루 전After recent update extension began to collect your sensitive data for sale. You can see it in recent changelogs.
개발자 답글
13시간 전에 게시됨I 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점 만점에 2점Infrequent_User 님, 하루 전BE 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.개발자 답글
13시간 전에 게시됨Thanks 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점 만점에 1점Firefox 사용자 19563331 님, 2일 전
- 5점 만점에 1점Firefox 사용자 18717684 님, 2일 전Good job bud, keep up the greediness and see how far it gets you in life.
개발자 답글
13시간 전에 게시됨I’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 - 5점 만점에 1점Firefox 사용자 15155323 님, 3일 전Fundamentally changed the extension from what it was. No longer good and has bloat
- 5점 만점에 2점sealovedmoon 님, 4일 전I think the description needs updating.
Everyone is freaking out about the new permissions and instead of replying to every one-star/two-star review that complains, it can be advertised in the description where indeed "everyone can see it".
Lastly, everyone including me, is complaining about the premium analytics, which are also not advertised in the description. This is not an add-on that simply returns the dislikes, so please act like it. Rewrite the description accordingly. You don't deserve that Recommended badge, it's as outdated as your description. - 5점 만점에 1점Cheese Louise 님, 4일 전
- 5점 만점에 4점Firefox 사용자 18304804 님, 4일 전
- 5점 만점에 3점BananaSplit97 님, 4일 전I can safely say this extension isn't harvesting my data (the developer isn't being insidious in what they're saying, it really is free to check the Github), but this extension isn't really what I downloaded it for anymore.
Opening Youtube to see the new interface that- while I confidently believe is entirely human made- just reads like generic vibe-coded design was offputting. The new window isn't needed and serves as yet another case of "fixing what isn't broken".
The plugin's behavior wasn't consistent anyway, with the like to dislike ratio being dramatically different from what it actually was supposed to be. I reckon one's better off without a plugin like this anyway. When they DO work, it's "kinda sorta".
It still does what it says on the box, even if not perfect, but I think you're better off without from the get.