Mirrors/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2024-11-16 15:33:38 +01:00
Code Issues Releases Wiki Activity

Grammar & URL Updates, Misc Updates

q1800 2022-02-01 22:19:15 -06:00
parent 47976567b0
commit 572c31917b
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
Dashboard:-Settings.md

@ -32,7 +32,7 @@ See [Cloud storage](./Cloud-storage) documentation.
If you check this, this will enable [uBlock's dynamic filtering](./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.
Unchecking this disables dynamic filtering. And the dynamic filtering pane in the popup UI will no longer be available.
_Advanced user_ mode also gives access to the [advanced settings](./Advanced-settings) (normally hidden), and enables the ability to filter [behind-the-scene network requests](./Behind-the-scene-network-requests).
@ -44,7 +44,7 @@ You should avoid playing with advanced features and settings unless [you underst
### Disable pre-fetching
Checking this will disable prefetching in your browser. When prefetching is enabled, the browser _can_ still establish connections to remote servers even if the resource from these remote servers are meant to be blocked by uBlock.
Checking this will disable prefetching in your browser. When prefetching is enabled, the browser _can_ still establish connections to remote servers even if the resources from these remote servers are meant to be blocked by uBlock.
This prevents the browser from bypassing uBlock's filtering engine before establishing connections to remote servers.
@ -66,7 +66,7 @@ On Chromium 51 and above (including browsers based on Chromium 51 and above), th
### Disable hyperlink auditing
Checking this will prevent hyperlink auditing. _Hyperlink auditing_ is best summarized as "phone home" feature (or more accurately "phone anywhere") meant to inform one or more servers of which links you click on (and when). The details are well explained [here](https://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/) and the case of why such feature is harmful to users is well argued [here](https://www.wilderssecurity.com/threads/major-browsers-to-prevent-disabling-of-click-tracking-privacy-risk.415381/#post-2822723).
Checking this will prevent hyperlink auditing. _Hyperlink auditing_ is best summarized as a "phone home" feature (or more accurately "phone anywhere") meant to inform one or more servers of which links you click on (and when). The details are well explained [here](https://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/) and the case of why such feature is harmful to users is well-argued [here](https://www.wilderssecurity.com/threads/major-browsers-to-prevent-disabling-of-click-tracking-privacy-risk.415381/#post-2822723).
***
@ -79,7 +79,7 @@ Browsers now obfuscate LAN addresses by mDNS:
- Firefox: ["Enable mDNS hostname obfuscation"](https://bugzilla.mozilla.org/show_bug.cgi?id=1588817)
- Chromium: ["mDNS service for IP handling in WebRTC"](https://bugs.chromium.org/p/chromium/issues/detail?id=878465)
Option is still available in Android Firefox, because obfuscation is still not implemented there: ["Support mDNS hostname obfuscation on Android"](https://bugzilla.mozilla.org/show_bug.cgi?id=1581947)
The option is still available in Android Firefox because obfuscation is still not implemented there: ["Support mDNS hostname obfuscation on Android"](https://bugzilla.mozilla.org/show_bug.cgi?id=1581947)
<details>
<summary>Details</summary>
@ -90,13 +90,13 @@ Background info: [STUN IP Address requests for WebRTC](https://github.com/diafyg
Test case: [Prevent WebRTC from leaking local IP address](./Prevent-WebRTC-from-leaking-local-IP-address)
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.
Keep in mind that this feature is to prevent **leakage** of your non-internet-facing IP address. 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 the 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.
- the feature works only on versions 42 and above.
- Firefox:
- due to differences in handling of network connections by different browsers, before version [1.18.12](https://github.com/gorhill/uBlock/commit/977178bef23c7711a050181be979a4668bfebcfb) WebRTC was completely disabled if Firefox was not configured to use proxy. Related issue: [#3009](https://github.com/gorhill/uBlock/issues/3009#issuecomment-329798696)
- due to differences in the handling of network connections by different browsers, before version [1.18.12](https://github.com/gorhill/uBlock/commit/977178bef23c7711a050181be979a4668bfebcfb) WebRTC was completely disabled if Firefox was not configured to use a proxy. Related issue: [#3009](https://github.com/gorhill/uBlock/issues/3009#issuecomment-329798696)
</details>
@ -108,11 +108,11 @@ Keep in mind that this feature is to prevent **leakage** of your non-internet-fa
You can block network requests made as a result of your browser reporting Content Security Policy violations ("CSP reports") to a remote server (which can be 3rd-party to the site where the violation occurred).
**Important:** disabling CSP reporting is not something which will break web pages, the purpose of CSP reporting is _strictly_ a development tool for web sites.
**Important:** disabling CSP reporting is not something that will break web pages, the purpose of CSP reporting is _strictly_ a development tool for web sites.
Consider this excerpt from [Reporting API / Privacy Considerations](http://wicg.github.io/reporting/#privacy) (my emphasis):
Consider this excerpt from [Reporting API / Privacy Considerations](https://w3c.github.io/reporting/#privacy) (my emphasis):
> 8.6. Disabling Reporting
> 9.4. Disabling Reporting
>
> [...]
>
@ -122,7 +122,7 @@ There is currently no way to easily toggle CSP reporting in either Chromium or F
Note that as opposed to all other network requests, behind-the-scene network requests which are actual CSP reports will also be filtered out according to this setting. So if you globally disable CSP reporting in uBO, this will also apply to behind-the-scene network requests.
Note that the blocking of CSP reports is implemented as a per-site switch internally in uBO, so this means that an advanced user could create rules in the _My rules_ pane in the dashboard to allow a more granular control of the blocking of CSP reports. For example:
Note that the blocking of CSP reports is implemented as a per-site switch internally in uBO, so this means that an advanced user could create rules in the _My rules_ pane in the dashboard to allow more granular control of the blocking of CSP reports. For example:
no-csp-reports: example.com false
@ -148,7 +148,7 @@ The setting will be disabled on platforms not supporting this feature. It's curr
In some edge cases, it might be necessary to disable this setting to prevent network-related issues. For example, [_"Pages load slowly when uBlock Origin is installed"_](https://bugzilla.mozilla.org/show_bug.cgi?id=1694404#c5), which occurred when funneling network requests through a proxy.
**Important note when using extension-based proxy service:** Extension-based proxy services are often done on-the-fly through a [browser API](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/proxy/onRequest), and in such case uBO's own DNS queries to uncloak canonical names will **NOT** be caught and proxied by an extension-based proxy service. So you may want to disable this setting when using an extension-based proxy service.
**Important note when using extension-based proxy service:** Extension-based proxy services are often done on the fly through a [browser API](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/proxy/onRequest), and in such case uBO's own DNS queries to uncloak canonical names will **NOT** be caught and proxied by an extension-based proxy service. So you may want to disable this setting when using an extension-based proxy service.
***
@ -164,6 +164,6 @@ Please see: ["Per site switches"](./Per-site-switches)
The bottom-most section is for you to easily backup/restore/reset all settings in uBlock.
It's done by saving text file to location specified by your browser.
It's done by saving a text file to the location specified by your browser.
It is suggested you backup all your settings regularly.