Đánh giá cho Return YouTube Dislike
Return YouTube Dislike bởi Dmitry Selivanov
Đánh giá bởi g1zm02k
Xếp hạng 5 trong số 5
bởi g1zm02k, 2 ngày trướcOh no, an extension requires information to do its job properly; everyone panic and start hoarding toilet rolls and bottled water!
2020's lunacy at its finest🤦🏻♂️
Nice update Dmitry, it's looking mighty fine. Sorry you have to suffer the deranged rantings of the masses, it's not like they got off their arses and made a similar extension themselves; ungrateful buggers.
Thanks man, much appreciated!
2020's lunacy at its finest🤦🏻♂️
Nice update Dmitry, it's looking mighty fine. Sorry you have to suffer the deranged rantings of the masses, it's not like they got off their arses and made a similar extension themselves; ungrateful buggers.
Thanks man, much appreciated!
Phản hồi của nhà phát triển
đã đăng 2 ngày trướcThanks!
And default copypasta to be seen on top.
Regarding the situation with permissions:
The extension only collects data that it requires to function.
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.
Nothing in the extension changed - it’s open-source, so you can verify that yourself. What changed is how Mozilla labels privacy-related permissions.
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
The new labels sound scary, but they describe the same data the extension has always used.
And default copypasta to be seen on top.
Regarding the situation with permissions:
The extension only collects data that it requires to function.
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.
Nothing in the extension changed - it’s open-source, so you can verify that yourself. What changed is how Mozilla labels privacy-related permissions.
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
The new labels sound scary, but they describe the same data the extension has always used.