Return YouTube Dislike のレビュー
Return YouTube Dislike 作成者: Dmitry Selivanov
Grendel666 によるレビュー
5 段階中 5 の評価
Grendel666 によるレビュー (2時間前)Dodatek może nie jakoś szczególnie ważny, ale przydatny. Zbyt wiele jest przypadków filmów, w których wręcz należy dać kciuk w dół.
合計レビュー数: 5,219
- 5 段階中 1 の評価Firefox ユーザー 16808659 によるレビュー (20時間前)
- 5 段階中 1 の評価Morales_Dog によるレビュー (1日前)Previously collected ALL your browsing data, without clearly informing you.
The only reason they started informing you, is that firefox terms updated requiring clearer information about predatory data collection.
There is an opt-out deep down in the config, but since they had the gall to collect all that data without informing you previously, the credibility of that opt-out seems... less than stellar. - 5 段階中 5 の評価Firefox ユーザー 20200698 によるレビュー (1日前)NOTHING 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 段階中 1 の評価Firefox ユーザー 17431847 によるレビュー (2日前)Recent update started to collect information, browsing data, etc... So it look like it turned into spyware.
- 5 段階中 1 の評価Firefox ユーザー 20196980 によるレビュー (2日前)
- 5 段階中 1 の評価VestraPater によるレビュー (2日前)
- 5 段階中 1 の評価Firefox ユーザー 17975154 によるレビュー (2日前)
- 5 段階中 1 の評価123424542234524 によるレビュー (3日前)Screw 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 段階中 1 の評価Firefox ユーザー 20196369 によるレビュー (3日前)The fact that the data processing method hasn't changed means it was being collected all along.
- 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 によるレビュー (4日前)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 によるレビュー (4日前)I'm not giving you my data.
Gross, pointless, and creepy.
You should all be incredibly ashamed of yourselves. 開発者の返信
投稿日時: 4日前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