-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v122 #1764
v122 #1764
Conversation
Aren't there any new settings related to Global Privacy Control? |
the PR isn't finished - but as for GPC, the pref has been there for a while, what they have done is expose it in the UI - edit: and turn the api on |
* Controls what protections FPP uses globally, including "RFPTargets" (despite the name these are | ||
* not used by RFP) e.g. "+AllTargets,-CSSPrefersColorScheme" or "-AllTargets,+CanvasRandomization" | ||
* [NOTE] Be aware that not all RFP protections are necessarily in RFPTargets | ||
* [WARNING] Not recommended. Either use RFP or FPP at defaults |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have the feeling that quite a few RFPTargets can be enabled without any disadvantage. For example most spoofed boolean like +CSSPrefersColorScheme
.
What are you thoughts about that? Am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I missing something
line 709
edit: ok, to put it bluntly - there is no fucking point see #1334 - your goal is to defeat naive scripts (see wiki) - so use RFP or FPP. There is no point to fiddling with them, because the only bit that really matters here is the randomizing
No description provided.