diff --git a/tools/_locales/am/messages.json b/tools/_locales/am/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/am/messages.json +++ b/tools/_locales/am/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/ar/messages.json b/tools/_locales/ar/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/ar/messages.json +++ b/tools/_locales/ar/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/bg/messages.json b/tools/_locales/bg/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/bg/messages.json +++ b/tools/_locales/bg/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/bn/messages.json b/tools/_locales/bn/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/bn/messages.json +++ b/tools/_locales/bn/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/ca/messages.json b/tools/_locales/ca/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/ca/messages.json +++ b/tools/_locales/ca/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/cs/messages.json b/tools/_locales/cs/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/cs/messages.json +++ b/tools/_locales/cs/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/da/messages.json b/tools/_locales/da/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/da/messages.json +++ b/tools/_locales/da/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/de/messages.json b/tools/_locales/de/messages.json index 80d1906..a2d622f 100644 --- a/tools/_locales/de/messages.json +++ b/tools/_locales/de/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Einstellungen", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Rückgängig machen", "description":"Will remove all temporary rules" diff --git a/tools/_locales/el/messages.json b/tools/_locales/el/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/el/messages.json +++ b/tools/_locales/el/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/en_GB/messages.json b/tools/_locales/en_GB/messages.json index 381c729..f2c9525 100644 --- a/tools/_locales/en_GB/messages.json +++ b/tools/_locales/en_GB/messages.json @@ -7,6 +7,10 @@ "message":"Point & click to forbid\/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Dashboard", + "description":"" + }, "settingsPageName":{ "message":"Settings", "description":"a tab in dashboard" @@ -311,6 +315,14 @@ "message":"

According to Google Chrome Privacy Whitepaper<\/a>, Chromium<\/i> might send HTTP requests to Google<\/i> without the user expressly visiting a web page. Let's call these special requests behind-the-scene<\/strong> requests. Also, other installed browser extensions can send behind-the-scene<\/strong> HTTP requests.<\/p>

µMatrix<\/i> 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.<\/p>

Click the extension icon while viewing this page to get started. Required reading: Behind-the-scene requests<\/a>.<\/p>

Beware!<\/span> Blocking behind-the-scene<\/strong> net requests is potentially causing an issue<\/a> 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).<\/p>

Even if this feature is not enabled, behind-the-scene<\/strong> requests are still logged by µMatrix<\/i>. You can inspect these requests on the Statistics<\/a> page.<\/p>", "description":"" }, + "userRulesPermanentHeader":{ + "message":"Permanent rules", + "description":"" + }, + "userRulesTemporaryHeader":{ + "message":"Temporary rules", + "description":"" + }, "userRulesRevert":{ "message":"Revert", "description":"Will remove all temporary rules" diff --git a/tools/_locales/es/messages.json b/tools/_locales/es/messages.json index d54a96d..62cf27c 100644 --- a/tools/_locales/es/messages.json +++ b/tools/_locales/es/messages.json @@ -4,9 +4,13 @@ "description":"" }, "extShortDesc":{ - "message":"Señalar & pulsar para prohibir\/permitir cualquier tipo de peticiones hechas por el navegador. Úselo para bloquear scripts<\/i>, iframes<\/i>, anuncios, facebook, etc.", + "message":"Señalar y hacer clic para prohibir\/permitir cualquier tipo de peticiones hechas por el navegador. Úselo para bloquear scripts<\/i>, iframes<\/i>, anuncios, facebook, etc.", "description":"this will be used as short description in web stores: MUST BE 132 characters OR LESS" }, + "dashboardPageName":{ + "message":"µMatrix — Panel de control", + "description":"" + }, "settingsPageName":{ "message":"Configuración", "description":"a tab in dashboard" @@ -68,7 +72,7 @@ "description":"HAS TO FIT IN MATRIX HEADER!" }, "matrixNoNetTrafficPrompt":{ - "message":"Tráfico de red no detectado para esta pestaña hasta ahora.", + "message":"Tráfico de red no detectado en la pestaña hasta ahora.", "description":"" }, "matrixMtxButtonTip":{ @@ -76,15 +80,15 @@ "description":"Tool tip for matrix button: {{}} is a placeholder for number of blocked requests." }, "matrixPersistButtonTip":{ - "message":"Guardar cambios transitorios para este ámbito.", + "message":"Guardar cambios temporales para este ámbito.", "description":"Tool tip for the persist button" }, "matrixRevertButtonTip":{ - "message":"Eliminar cambios transitorios para este ámbito.", + "message":"Eliminar cambios temporales para este ámbito.", "description":"Tool tip for the revert local permission button" }, "matrixRevertButtonAllTip":{ - "message":"Eliminar todos los cambios transitorios.", + "message":"Eliminar todos los cambios temporales.", "description":"Tool tip for the revert all permissions button" }, "matrixReloadButton":{ @@ -136,7 +140,7 @@ "description":"" }, "statsPageDetailedBehindTheScenePage":{ - "message":"Chromium: Entre bambalinas (Behind the scene)", + "message":"Chromium: Behind the scene", "description":"" }, "statsPageOverview":{ @@ -168,7 +172,7 @@ "description":"Second part of Remember the last [n] HTTP requests per page" }, "statsPageLogSizeHelp":{ - "message":"

Se pueden inspeccionar los detalles de las peticiones HTTP directas más recientes hechas por una página web (ver debajo).<\/p>

Esto es útil sobre todo para usuarios avanzados que deseen investigar que ha estado haciendo exactamente una página. Pero registrar estas peticiones HTTP requiere memoria, la cual puede terminar siendo malgastada si dicha información técnica no es de su interés.<\/p>

Por ello este campo le permite ajustar el número máximo de peticiones HTTP recientes que se van a registrar para una inspección ulterior.<\/p>

Introduzca “0<\/code>” para desactivar el registro detallado (con el consecuente ahorro de memoria de µMatrix<\/i>).<\/p>", + "message":"

Se pueden inspeccionar los detalles de las peticiones HTTP directas más recientes hechas por una página web (ver debajo).<\/p>

Esto es útil sobre todo para usuarios avanzados que deseen investigar que, exactamente, ha estado haciendo una página. Pero el registro de estas peticiones HTTP requiere memoria, la cual puede terminar siendo malgastada si dicha información técnica no es de su interés.<\/p>

Por ello este campo le permite ajustar el número máximo de peticiones HTTP recientes que se van a registrar para una inspección ulterior.<\/p>

Introduzca “0<\/code>” para desactivar el registro detallado (con el consecuente ahorro de memoria de µMatrix<\/i>).<\/p>", "description":"To help user understand the purpose of the log size value" }, "statsPageRefresh":{ @@ -196,27 +200,27 @@ "description":"" }, "settingsMatrixDisplayColorBlind":{ - "message":"Accesible para daltonianos", + "message":"Accesible para daltónicos", "description":"" }, "settingsMatrixConvenienceHeader":{ - "message":"Conveniencia", + "message":"Comodidad", "description":"English: Convenience" }, "settingsMatrixAutoReloadPrompt":{ - "message":"Al cerrarse la matriz, hace una recarga inteligente de las siguientes pestañas:", + "message":"Al cerrar la matriz, hacer recarga inteligente de las siguientes pestañas:", "description":"" }, "settingsMatrixAutoReloadNone":{ - "message":"Ninguno", + "message":"Ninguna", "description":"" }, "settingsMatrixAutoReloadCurrent":{ - "message":"Actual", + "message":"Actuales", "description":"" }, "settingsMatrixAutoReloadAll":{ - "message":"Todo", + "message":"Todas", "description":"" }, "settingsMatrixAutoReloadInfo":{ @@ -272,7 +276,7 @@ "description":"Second part of 'Clear browser cache every [n] minutes'" }, "privacyClearCacheHelp":{ - "message":"

Algunos sitios web están tan enfocados en rastrearle, que usarán algunos trucos bastantes sucios para burlar cualquier medida que se tome para evitar ser rastreado.<\/p>

Algunos de estos trucos se basan[1, 2]<\/sup> en la caché del navegador<\/a>, cuyo contenido es perdurable como norma, pues raramente los usuarios se toman el trabajo de limpiarlo regularmente.<\/p>

Limpiar la caché regularmente es bastante fácil (normalmente no se percibe cuando ocurre), con el beneficio de impedir a estos molestos rastreadores invadir su privacidad.<\/p>

Active esta opción para que µMatrix<\/i> lo haga por usted, con el intervalo deseado.<\/p>

[1] “Preventing Web Tracking via the Browser Cache”<\/a>
[2] “Cookieless cookies”<\/a><\/p>", + "message":"

Algunos sitios web están tan enfocados en rastrearle, que usarán ciertos trucos bastantes sucios para burlar cualquier medida que se tome para evitar ser rastreado.<\/p>

Unos cuantos de estos trucos se basan[1, 2]<\/sup> en la caché del navegador<\/a>, cuyo contenido como norma es perdurable, ya que raramente los usuarios se toman el trabajo de limpiarlo de forma regular.<\/p>

Limpiar la caché de manera regular es bastante fácil (probablemente ni siquiera lo perciba cuando ocurra), con el beneficio de impedir a estos molestos rastreadores invadir su privacidad.<\/p>

Active esta opción para que µMatrix<\/i> lo haga por usted, en el intervalo deseado.<\/p>

[1] “Preventing Web Tracking via the Browser Cache”<\/a>
[2] “Cookieless cookies”<\/a><\/p>", "description":"" }, "privacyProcessRefererPrompt":{ @@ -280,7 +284,7 @@ "description":"" }, "privacyProcessRefererHelp":{ - "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.<\/b>”<\/p>

If this setting is checked, µMatrix<\/i> will remove the HTTP referer information if both<\/b> of the following conditions are true: