You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
apologies if I'm missing any others! With the enabling of this GitHub Discussions feature recently, i'm hoping to start a central point of discussion to determine:
scope of improving anti-fingerprint measures in UC. how far we could go, what goes beyond the scope of this project, etc.
feature and design ideas
feedback for features to be implemented
to start the discussion with a question i have: what should the scope of this effort look like? would we want to rival Brave's work in this area? do we want to add flags where we can and leave it at that? or can we go as far as we like/need to improve objective 3, as long as it doesn't affect objective 2?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
there have been a number of issues created around browser fingerprinting and improving protections in UC against it:
#783
#822
#1192
#1226
apologies if I'm missing any others! With the enabling of this GitHub Discussions feature recently, i'm hoping to start a central point of discussion to determine:
to start the discussion with a question i have: what should the scope of this effort look like? would we want to rival Brave's work in this area? do we want to add flags where we can and leave it at that? or can we go as far as we like/need to improve objective 3, as long as it doesn't affect objective 2?
Beta Was this translation helpful? Give feedback.
All reactions