-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Allow advanced users to turn prefetching back on #274
Comments
Ok, I will provide such setting (enabled by default), though uBlock will still need Chromium's Privacy permission to act on the setting. Unfortunately, the Privacy permission is not in the set of optional permissions. |
How fast the next version is published will depend on how fast the translation work comes in. Now people can re-enable pre-fetching with this new setting, but at least I am satisfied that users are made aware of the negative consequences of pre-fetching, while before those negative consequence were not disclosed up front, undermining the primary purpose of uBlock. |
👍 thanks gorhill |
@gorhill wrote: "...but at least I am satisfied that users are made aware of the negative consequences of pre-fetching." That's a good public education service! How are they currently made aware? |
@galambalazs The new setting is worded as follow:
If you meant "currently" as in "before the new setting", well, the release notes informed why this was needed. |
Is there a way to make a prefetch whitelist for sites and only allow prefetching of data on those sites? |
I use uBlock mostly for the ad-blocking aspect but also partially for privacy reasons. However, prefetching actually helps with my connection, which can be high-latency at times. Since my IP is dynamic and changes on a near-daily basis, I wouldn't mind as much if I had it on. Can you add an advanced option for overriding this? Since the extension asks for control of the setting, it's no longer user-controlled.
P.S.: I know this is essentially a feature request, but I feel it's relevant due to the new permissions and tried to condense it as much while still explaining why I felt it was important.
The text was updated successfully, but these errors were encountered: