You can inspect details of the most recent raw HTTP requests which have been made by a web page (see below).
This is mostly useful to advanced users who want to investigate exactly what a web page has been doing. But logging these HTTP requests requires memory, and if you don't care about this technical information, then memory is being wasted.
Hence this field which lets you adjust the maximum number of the most recent HTTP requests which are to be logged for further inspection.
Enter “0” to turn off detailed logging (and consequently reduce the memory footprint of µMatrix).
You can inspect details of the most recent raw HTTP requests which have been made by a web page (see below).
This is mostly useful to advanced users who want to investigate exactly what a web page has been doing. But logging these HTTP requests requires memory, and if you don't care about this technical information, then memory is being wasted.
Hence this field which lets you adjust the maximum number of the most recent HTTP requests which are to be logged for further inspection.
Enter “0” to turn off detailed logging (and consequently reduce the memory footprint of uMatrix).
Blacklisted cookies are not prevented by µMatrix from entering your browser. However they are prevented from leaving your browser, which is what really matters. Not blocking cookies before they enter your browser gives you the opportunity to be informed that a site tried to use cookies, and furthermore to inspect their contents if you wish.
Once these blacklisted cookies have been accounted for by µMatrix, they can be removed from your browser if you wish so.
Important note: Extensions can make web requests during the course of their normal operation. These requests can result in cookies being created in the browser. If the hostname from where a cookie originate is not whitelisted, the cookie will be removed from the browser by µMatrix if this option is checked. So be sure that the hostname(s) with which an extension communicate is whitelisted.
", + "message": "Blacklisted cookies are not prevented by uMatrix from entering your browser. However they are prevented from leaving your browser, which is what really matters. Not blocking cookies before they enter your browser gives you the opportunity to be informed that a site tried to use cookies, and furthermore to inspect their contents if you wish.
Once these blacklisted cookies have been accounted for by uMatrix, they can be removed from your browser if you wish so.
Important note: Extensions can make web requests during the course of their normal operation. These requests can result in cookies being created in the browser. If the hostname from where a cookie originate is not whitelisted, the cookie will be removed from the browser by uMatrix if this option is checked. So be sure that the hostname(s) with which an extension communicate is whitelisted.
", "description": "" }, "privacyDeleteNonBlockedSessionCookiesPrompt1" : { @@ -358,7 +358,7 @@ "description": "Second part of 'Clear browser cache every [n] minutes'" }, "privacyClearCacheHelp" : { - "message": "Some web sites are really bent on tracking you, so much that they will use not-so-nice tricks to work around whatever measures you take in order to not be tracked.
A few of these tricks rely[1, 2] on the browser cache, which content is often long lasting since rarely will users take the time to regularly clear their browser cache.
There is little inconvenience to clear the browser cache regularly (likelihood is that you won't notice when it happens), and the benefit is to prevent these obnoxious trackers from invading your privacy.
Check this option to have µMatrix do it for you, at the interval you wish.
[1] “Preventing Web Tracking via the Browser Cache”
[2] “Cookieless cookies”
Some web sites are really bent on tracking you, so much that they will use not-so-nice tricks to work around whatever measures you take in order to not be tracked.
A few of these tricks rely[1, 2] on the browser cache, which content is often long lasting since rarely will users take the time to regularly clear their browser cache.
There is little inconvenience to clear the browser cache regularly (likelihood is that you won't notice when it happens), and the benefit is to prevent these obnoxious trackers from invading your privacy.
Check this option to have uMatrix do it for you, at the interval you wish.
[1] “Preventing Web Tracking via the Browser Cache”
[2] “Cookieless cookies”
From Wikipedia:
HTTP referer is an HTTP header field that identifies the address of the webpage that linked to the resource being requested. ... Because referer information can violate privacy, some web browsers allow the user to disable the sending of referer information.
If this setting is checked, µMatrix will spoof the HTTP referrer information if the domain name of the HTTP referrer is third-party to the domain name of net request.", + "message": "
From Wikipedia:
HTTP referer is an HTTP header field that identifies the address of the webpage that linked to the resource being requested. ... Because referer information can violate privacy, some web browsers allow the user to disable the sending of referer information.
If this setting is checked, uMatrix will spoof the HTTP referrer information if the domain name of the HTTP referrer is third-party to the domain name of net request.", "description": "" }, "privacyNoMixedContentPrompt" : { @@ -402,7 +402,7 @@ "description": "" }, "privacyProcessBehindTheSceneHelp" : { - "message": "
According to Google Chrome Privacy Whitepaper, Chromium might send HTTP requests to Google without the user expressly visiting a web page. Let's call these special requests behind-the-scene requests. Also, other installed browser extensions can send behind-the-scene HTTP requests.
µMatrix lets you intercept and treat these requests like any other request: they can be processed in order to allow/block them as per your whitelist/blacklist.
Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests.
Beware! Blocking behind-the-scene net requests is potentially causing an issue when the user wants to install an extension from the Chrome store (including maybe preventing extensions from being updated), hence the ability to disable the feature here. Blocking can also cause other installed extensions to not work properly (those querying for remote data).
Even if this feature is not enabled, behind-the-scene requests are still logged by µMatrix. You can inspect these requests on the Statistics page.
", + "message": "According to Google Chrome Privacy Whitepaper, Chromium might send HTTP requests to Google without the user expressly visiting a web page. Let's call these special requests behind-the-scene requests. Also, other installed browser extensions can send behind-the-scene HTTP requests.
uMatrix lets you intercept and treat these requests like any other request: they can be processed in order to allow/block them as per your whitelist/blacklist.
Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests.
Beware! Blocking behind-the-scene net requests is potentially causing an issue when the user wants to install an extension from the Chrome store (including maybe preventing extensions from being updated), hence the ability to disable the feature here. Blocking can also cause other installed extensions to not work properly (those querying for remote data).
Even if this feature is not enabled, behind-the-scene requests are still logged by uMatrix. You can inspect these requests on the Statistics page.
", "description": "" }, @@ -564,7 +564,7 @@ "description": "" }, "aboutRestoreConfirm" : { - "message": "All your settings will be overwritten using data backed up on {{time}}, and µMatrix will restart.\n\nOverwrite all existing settings using backed up data?", + "message": "All your settings will be overwritten using data backed up on {{time}}, and uMatrix will restart.\n\nOverwrite all existing settings using backed up data?", "description": "Message asking user to confirm restore" }, "aboutRestoreError" : { diff --git a/src/js/start.js b/src/js/start.js index d7c5caf..24c9d47 100644 --- a/src/js/start.js +++ b/src/js/start.js @@ -60,7 +60,7 @@ var defaultLocalUserSettings = { 'rgba(0,0,0,0.05) 75%,', 'rgba(0,0,0,0.02) 75%,', 'rgba(0,0,0,0.02)', - ') #fff center center / 10px 10px repeat scroll' + ') center center / 10px 10px repeat scroll #fff' ].join(''), placeholderBorder: '1px solid rgba(0, 0, 0, 0.05)', placeholderDocument: [