![]() When uBO blocks a network request, the expectation is that it blocks completely the connection, hence the new permission is necessary for uBO to do truthfully what it says it does. ![]() For pages with lots of blocked requests, this will remove overhead from page load (if you did not have the setting already disabled).This will ensure no TCP connection is opened at all for blocked requests: It's for your own protection privacy-wise.Disable "Prefetch resources to load pages more quickly". ![]() Without this permission, uBO would not be able to use more than 5 MB, which is not enough for uBO to function properly. The storage used by uBO is shown at the bottom of the Settings pane in the dashboard. uBO uses client-side storage to save the assets downloaded from remote servers (filter lists and other assets), the compiled version of those assets and the selfie representation of various assets (for efficient launch time). This permission is necessary to allow uBO to use more than 5 MB of storage. "Store unlimited amount of client-side data" Newer versions of Firefox no longer ask for this permission. There is a Firefox issue regarding the confusing wording of the permission. uBO has no access to (and no need to know) your specific IP address. Important: the statement "IP address" refers to the IP address of the servers to which your browser connects, NOT your specific IP address. Note that even without this permission, uBO can see the IP address and hostname information, through the browser.webRequest API which uBO already requires. The purpose is for uBO to gain the ability to reveal the canonical name of aliased hostnames. This warning is triggered by the dns permission, which allows using the browser.dns API. "Access IP address and hostname information"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |