Pohódnoćenja za Return YouTube Dislike
Return YouTube Dislike wot Dmitry Selivanov
Pohódnoćenje wot Wužiwar Firefox 20153128
Z 5 z 5 pohódnoćeny
wot Wužiwar Firefox 20153128, pre 2 danaWorks as intended. As for the "This requires new permissions". After taking a look all its doing is hashing your user name (so you cant dislike bomb as a single user) and grabs what page your viewing (so it knows how many dislikes there are). Otherwise this app can't function as intended. For those quickly disliking this is a firefox thing. Its good to be skeptical in these times but please use due diligence :)
Wotmołwa wuwiwarja
je so pre 2 dana napisałThanks!.
Tiny correction - it's not even hashing username - it's randomly generated
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.
Tiny correction - it's not even hashing username - it's randomly generated
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.