Skip to content

Dashboard: Settings

Raymond Hill edited this page Jan 4, 2016 · 29 revisions

Figure 1

Below more details for the non-self-explanatory items


Make use of context menu where appropriate

If checked, this gives permission for uBlock to add items in the context menu which are meant to improve convenience. Currently, only one item is added to the context menu, "Block element", which purpose is to launch the element picker in order to filter out a specific element on a page.


Color-blind friendly

Currently mostly useful for users who checked "I am an advanced user" (see below).


I am an advanced user

If you check this, this will enable uBlock's dynamic filtering, and the dynamic filtering pane will become available from uBlock's popup UI.

Unchecking this disables the dynamic filtering. And the dynamic filtering pane in the popup UI will no longer be available.

Advanced user mode also enables the ability to filter behind-the-scene network requests.


Disable pre-fetching

Checking this will disable prefetching in your browser. When prefetching is enable, the browser can still establish connections to remote servers even if the resource from these remote servers are meant to be blocked by uBlock.

This prevent the browser from bypassing uBlock's filtering engine before establishing connections to remote servers.

Mozilla's "Link prefetching FAQ":

Privacy implications Along with the referral and URL-following implications already mentioned above, prefetching will generally cause the cookies of the prefetched site to be accessed.

Google's "Make webpages load faster":

If you turn this setting on in Chrome, websites (and any of their embedded resources) that are prerendered or prefetched may set and read their own cookies as if you had visited them before -- even if you don’t visit the prerendered or prefetched pages after all.


Disable hyperlink auditing/beacon

Checking this will prevent hyperlink auditing/beacon[1]. Hyperlink auditing and Send beacon are best summarized as "phone home" features (or even "phone anywhere"). The details are well explained here.

[1] Important note: "Send beacon" can not be disabled in Chromium. Advanced users can filter behind-the-scene network requests, where the beacon-related network requests show up.


Prevent WebRTC from leaking local IP address

c

Background info: STUN IP Address requests for WebRTC

Test cases:

Keep in mind that this feature is to prevent leakage of your non-internet-facing IP adresses. The purpose of this feature is not to hide your current internet-facing IP address -- so be cautious to not misinterpret the results of the tests above. For example, if you use a VPN, your internet-facing IP address is that of the VPN, so your ISP-provided IP address should not be visible to outside world with this setting checked. However, if you are not behind any VPN or proxy, your ISP-provided IP address will be visible regardless of this setting.

Caveats:

  • Chromium-based browsers: the feature works only on version 42 and above.
  • Firefox: the only way to prevent local IP address leakage is to disable completely WebRTC.
    • WebRTC is required for Firefox Hello to work properly.

Backup/restore section

The bottom-most section is for you to easily backup/restore/reset all settings in uBlock.

It is suggested you backup all your settings regularly.

Clone this wiki locally