![]() ![]() There is no concept of specificity in static filtering - and even more, there is no concept of dynamic filtering rules relinquishing filtering to static filters (dynamic filtering's noop rules).īasic ABP-like syntax, 30000 filters MAX.Īnd there I was recently testing how uBO handled over half a million network filters with the 3rd-gen HNTrie. Dynamic filtering logic requires an arbitrary amount of block/allow rules overriding other block/allow rules based on specificity. There is no way to transpose either either dynamic filtering, dynamic URL filtering, per-site/per-scope switch logic (let's refer to all these as "dynamic filtering"), into static filters. If there is really such phase out planned, and if the declarativeNetRequest is strictly an implementation of static filtering à la ABP, this would be the death of uBO and uMatrix. It is explicitly stated this is meant to phase out webRequest API? If so, where? Quickly perusing the page, I don't see such phase out being stated. It appears that Google is phasing out the webRequest API (Plus there's the change from background page to ServiceWorker.) I would expect big changes needed to uBO and other blockers. ![]() Looking at the new API page, it's a rather different way of doing things. This API is currently being implemented, and will be available to both the current manifest version and Manifest V3, but will be the primary way to modify network requests in Manifest V3. This is also better for user privacy, as the details of the network request are never exposed to the extension. ![]() This allows us to ensure efficiency since a) we have control over the algorithm determining the result and b) we can prevent or disable inefficient rules. Thus, instead of the above flow where Chrome receives the request, asks the extension, and then eventually gets the result, the flow is that the extension tells Chrome how to handle a request and Chrome can handle it synchronously. At its core, this API allows extensions to tell Chrome what to do with a given request, rather than have Chrome forward the request to the extension. The declarativeNetRequest API is an alternative to the webRequest API. IMHO, all they will do is make a fork famous, probably Brave has the most momentum.It appears that Google is phasing out the webRequest API in favor of their new declarativeNetRequest. The demand is too great for this to carry any weight. So in order for me, Pale Moon, in combination with a portable, feature freeze Chrome/Edge. I will not, under any circumstances, watch Youtube with ads. If indeed this gutting happens and Chrome and Edge cut off updates, I will probably pihole my network and just stop updating. ![]() I personally moved to Pale Moon, it's safe, but not the best compatibility out there and has a bit of a learning curve (forked off Firefox 3.5 UI, so more customizable, but most addons are legacy). They made all other changes in lockstep with Chrome and I'm afraid that all you're getting is a bit of time at the cost of a long migration process. Mozilla is telemetrying my pants size, pinky primise not to sell it, while hobbling their browser by making old extensions not work, redoing the UI and generally aping Chrome to the point that they are indistinguishable. I moved off recently because they are really, really not that good at it. Specially when said feature could save your ass if you accidentally clicked something you didn't want to download. You tell me if a feature being changed permanently (it is not toggable unless you mess with the ever 'will-be-removed-by-next-version' about:config settings) can be justified by an argument that uses the word "usually" in two sentences back to back. Having to click a second time for a download to start is usually unnecessary. It is a potential security risk:įirefox no longer shows the dialog by default because downloads are usually intentional. It is not "just" a matter of "you will get used to it". A recent update (FF 98) changed dramatically how files downloaded are handled. Sadly firefox has its head up its own ass and listen to zero feedback when it comes to their "it isn't broken, but we fixed it regardless" updates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |