From a8539f0988cf28f8cfd36e4a3b48e231fe7d7067 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Mon, 8 Jun 2015 07:36:35 -0400 Subject: [PATCH] Updated About the required permissions (markdown) --- About-the-required-permissions.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/About-the-required-permissions.md b/About-the-required-permissions.md index 61e2431..2ac8c13 100644 --- a/About-the-required-permissions.md +++ b/About-the-required-permissions.md @@ -75,8 +75,7 @@ This is necessary to be able to: - This will ensure no TCP connection is opened **at all** for blocked requests: **It's for your own protection privacy-wise.**[1] - For pages with lots for blocked requests, this will actually remove overhead from page load (if you did not have the setting already disabled). - When uBlock blocks a network request, the expectation is that it blocks **completely** the connection, hence the new permission is necessary for uBlock to do **truthfully** what it says it does. -- Disable _"Disable hyperlink auditing/beacon"_ (0.9.8.5) - - [Background information](http://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/). +- Disable [hyperlink auditing/beacon](http://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/) (0.9.8.5) uBlock's primary purpose is to block **network connections**, not just data transfer. Not blocking the connection while just blocking the data transfer would mean uBlock is lying to users. So this permission will stay, and sorry for those who do not understand that it actually allows uBlock to do its intended job more thoroughly[2]. A blocker which does not thoroughly prevent connections is not a real blocker.