From ac531f141c2d4822b9d0294510dbe0d3eda45bd4 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Wed, 3 Jun 2015 07:29:16 -0400 Subject: [PATCH] Updated About the required permissions (markdown) --- About-the-required-permissions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/About-the-required-permissions.md b/About-the-required-permissions.md index 1a9369f..2a5fcef 100644 --- a/About-the-required-permissions.md +++ b/About-the-required-permissions.md @@ -15,7 +15,7 @@ uBlock's required permissions are the same as those of [Privacy Badger](https:// "https://*/*" ], -"[`privacy`](https://developer.chrome.com/extensions/privacy)" is the only permission added in [version 0.9.8.2](https://github.com/gorhill/uBlock/releases/tag/0.9.8.2). All the others were there since when uBlock was first published (except for `"contextMenus"` which was added at some point, to support blocking element from within the context menu). +[`"privacy"`](https://developer.chrome.com/extensions/privacy) is the only permission added in [version 0.9.8.2](https://github.com/gorhill/uBlock/releases/tag/0.9.8.2). All the others were there since when uBlock was first published (except for `"contextMenus"` which was added at some point, to support blocking element from within the context menu). The `privacy` permission is needed for uBlock to be able to disable the setting "Prefetch resources to load pages more quickly". This will ensure no connection is opened at all for blocked requests: It's for your own protection privacy-wise.