While everything I report may not be totally on focus, I strongly believe, and hope, it will help in solving any problems using ublock-origin in the PureOS environment. Furthermore, ublock then behaved as it did prior to the latest update of purebrowser to version 68.0.02-1pureos3, in remaining enabled after exiting and reopening the browser and in filtering as it should. I then installed webext-ublock-origin-1.22.0 from GNU FSF and this did put ublock in the list of enabled addons. This failed to put ublock origin in the list of enabled extensions at about:addons I then did apt-clean followed by apt install purebrowser which then reinstalled the two!! packages I had purged. I then did apt purge webext-ublock-origin, which for some reason not clear to me also removed purebrowser-68.0.2-1pureos3 as well as version 1.18.4+dfsg-2 of ublock, the same version I installed previously from amber. ![]() required to false from their defaiult of true.Īlthough off-focus, this allowed me to finally uninstall privacy-badger, not from within purebrowser, but using apt purge webext-privacy-badger. I think you should pay attention, as you have, to what I report for two reasons I have been solving (and causing) programming problems since likely before you were born, and I have solved the problems I initially told you about.īefore starting, I set in about:config and xpinstall.whitelist. I apologize for not providing more information about version numbers, but not for going off-focus. I joined this thread because I had two problems I thought were related to the subject matter. ![]() Purebrowser presented what seemed to be Firefox home page with quick links to stuff like facebook, and the icon for the Firefox account (see the first picture bellow).īellow are the pictures of the different steps of this process In this process i did noticed other things that i do not know if they are normal: Just reloading the about:config page after enabling Firefox compatibility mode, and then reloading the about.addons page. So i retraced my steps by doing the process again from an image in GNOME Boxes.ġ - did a sudo apt update & sudo apt dist-upgrade, only update available was purebrowser 68.0.2esr-1pureos3Ģ - launched purebrowser, uBlock Origin was not availableģ - Followed this tutorial to enable Firefox compatibility mode so i can install addons: firefox_compat_modeĤ - reloaded the addons page, from that point on i was able to install more addonsĪll these steps in Purebrowser were done without closing it and launching it again. Chrome will be similar to Apple’s Safari browser, which now supports “ content blockers” that operate in a speedy, standard way.- what is probably more interesting is what you did in-between: Did you start PureBrowser while the addon was removed? This change may speed up Chrome by limiting what all browser extensions can do-ad blocking extensions and other extensions. ![]() If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin (“uBO”) and uMatrix, can no longer exist.īeside causing uBO and uMatrix to no longer be able to exist, it’s really concerning that the proposed declarativeNetRequest API will make it impossible to come up with new and novel filtering engine designs, as the declarativeNetRequest API is no more than the implementation of one specific filtering engine, and a rather limited one (the 30,000 limit is not sufficient to enforce the famous EasyList alone).Įven Hill notes that ad blockers aren’t going away if this goes through. Raymond Hill notes that, if this change goes through, ad blocker uBlock Origin and content filter uMatrix can’t do anything special: However, declarativeNetRequest uses an Adblock Plus-style filtering system. Chrome itself does the blocking without waiting for extensions to respond, and this should be faster. Chrome won’t have to wait for extensions to weigh in while loading a page.Īd blockers must use the “ declarativeNetRequest” API to tell Chrome what they want to block. Extensions can only watch these events, and that should speed up page load times. If the proposed change goes through, extensions won’t be able to block events with this API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |