uBlock Origin 1.10.5b11
This post was published 9 years ago. Download links are most likely obsolete. If that's the case, try asking the uploader to re-upload.
Windows Sofware | uBlock Origin 1.10.5b11 | 4.6Mib
uBlock Origin - an excellent blocker intrusive and annoying advertisements to FireFox browser, Opera, Google Chrome, and on its basis. Unlike other add-ons to the browser with the ability to stop the run ad units, this extension practically eats system resources.
At the same time the opportunities and effectiveness uBlock Origin is not inferior to a well-known blockers:
• Supports loading of filters in the list of third-party developers.
• There is a function block certain elements on the page for selection.
• You can create a whitelist to unlock
• etc.
Remarkably, according to developers, they do not take money from the advertisers for the inclusion of their ad units on a permanent or temporary basis in block list of exceptions that sometimes occurs in other programs. Test studies have shown that uBlock Origin really bad at work: all the major advertising banners have been blocked, and the performance as the Chrome browser and the computer in general, remained at a high level.
Like many extensions for web-browsers after installing uBlock Origin located in the upper right corner of the taskbar. To check how many requests have been blocked, just click on the icon additions. Right-clicking will allow to go to the settings menu, where you will get acquainted with the list of its own and third-party filters, so the user can create a whitelist of sites and configure other options.
Installation instructions:
• For Chrome (and others like him): go to the "Settings" -> "extensions" checkbox and set the "Developer mode" and then click "Load unpacked extension" to specify the path to the folder (uBlock0.chromium).
• For FireFox: uBlock0.firefox.xpi simply drag the browser window (about: addons).
uBlock Origin is a open source browser extension for content-filtering, including ad-blocking. The extension is available for several browsers, including Chrome, Firefox, and Opera. uBlock Origin has received praise from technology websites, and is reported to be much less memory-intensive than other extensions with similar functionality. uBlock Origin's stated purpose is to give users the means to enforce their own (content-filtering) choices.
Whats New 1.10.5b11
Asset managements was refactored: details. It strongly suggested you make a backup of your data before installing this beta version.
Procedural cosmetic filters can now be chained and recursive (something which was planned) . Examples:
Chained: example.com##.item:matches-css-after(position: fixed):has-text(Promoted)
Recursive: mobile.twitter.com##main [role="region"] > [role="grid"] > [role="rowgroup"] [role="row"]:if(div:last-of-type span:has-text(/^Promoted by/)) (actually a real use case).
There is no limit on the number of operators chained, or the number of recursion level, aside common sense. As a reminder, use procedural cosmetic filters only for when plain CSS selectors won't solve a case.
New procedural cosmetic filter operators:
:has-text(argument): to filter elements according to whether they have a specific text string found in them. Use /.../ to match a literal regular expression instead of plain text.
:if()/:if-not(argument): use to implement recursion, argument is itself a valid procedural cosmetic filter, but can also be a plain CSS selector.
Any of the operator which accept a text string value to match can also accept of literal regular expression value.
The :xpath() operator can now accept a plain CSS selector as prefix (i.e. example.com##.item:xpath(...)), just like all other operators. The XPath evaluation will use whatever element matches the CSS selector as the context node for the XPath.
The cost of parsing procedural cosmetic filters has been moved from content script-time to filter list compile-time, i.e. done only once when a filter list is updated.
The element picker supports all procedural cosmetic filters, i.e. it will also provide visual feedback as you enter manually such filters in the input field. Invalid filters, procedural or not, will be labelled with a bright red E.
Efficient procedural cosmetic filters (or any cosmetic filters really) are the ones which result in the smallest set of nodes to visit. The element picker input field will display the number of elements matching the current filter. The element picker will only consider the entered text up to the first line break, while leaving the rest as is. You can use this feature to break up your filter to find out the size of the resultset of the first part(s) of your filter: the smallest resultset the most efficient is your cosmetic filter.
Homepage: https://www.ublock.org/