ublock users

[trium]

i have tryed the memory usage on w8.1 64bit; ff 43.0.4; ublock origin v1.5.5; adblock plus v2.7.1

ff with adblock plus offline = 235 mb

ff with ublock origin offline = 185 mb

+ online

ff with adblock plus and 4 opend tabs = 405 - 435 mb

ff with ublock origin and 4 opend tabs = 385 - 400 mb

[Andavari]

Please be careful when searching for ublock0 in the Chrome store. The real one (by gorhill) is listed below a third party one.

I always click the gorhill one, the others shown in the Chrome store I was wondering why they were even there (minus the new fork which I knew about) but went with what everyone was recommending in this topic.

[trium]

ublock v1.6.0

gorhill released this

5 days ago

Important: Please, do not ask me to publish to AMO or Chrome store. I am being very careful before publishing, and it may have already been done, but the submissions are pending review.

New: Ability to set the default state of per-site switches (issue #1193)

It is now possible to set the default value of per-site switches from the Settings pane in the dashboard, under the Default behavior header (see figure below). It was possible before to modify the default setting, but this had to be done by manually entering the proper rule in the My rules pane -- not very suitable to non-advanced users.

Block media elements by size (issue #1163)

This is a new per-site switch:

Primary purpose is to save bandwidth. See documentation for more information.

Note that this feature has been implemented with the utmost care to not add overhead to those not using it. The content scripts to handle interaction with blocked media elements are injected if and only if large media elements were actually blocked.

Closed as fixed: Firefox

• Adding subscription from resource: URI does not work
• Remove toolbar button code path for FF29-35: fall back on legacy
• uBO fails to block popup
• IPv6 raw addresses are not correctly handled
• [non-Australis] Button is not added to Navigation Toolbar on new profiles

Core:

• Fix problems reported in Debian Lintian's runs
• Broken domainCachePrune may lead to un-garbage-collected memory
• Refreshing in the dashboard
• Logger doesn't show origin of filters with unescaped regexes
• Make cloud storage import+merge more discoverable?

[trium]

ublock v1.6.1

gorhill released this

a day ago

Closed as fixed:

Core:

• Popups with "no popups" switch enabled on uploadrocket

[hazelnut]

Chrome store is once again showing a 'not genuine' ublock origin as top of the list.

It has even copied the ublock0 icon.

[hazelnut]

New release 1.6.1 ( a bug fix)

https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/

For Chrome

https://chrome.google.com/webstore/search/ublock%20origin

(remember it's ublock origin by gorhill you need)

[Andavari]

Chrome store is once again showing a 'not genuine' ublock origin as top of the list.

It has even copied the ublock0 icon.

Google probably doesn't care, or is lazy, otherwise it wouldn't have been there for so long.

[trium]

ublock v1.6.2

gorhill released this

a day ago

Closed as fixed: Core:

• uBlock is not able to apply ONLY my cosmetic filters
• Logger displays wrong source for some filters

[trium]

ublock v1.6.3

gorhill released this

6 hours ago

Notes

This release is mostly changes to comply with Opera store requirements -- a language translation must not be used if there is no corresponding description available.

[trium]

ublock v1.6.4

gorhill released this

2 days ago

Changes:

Popup filters can also be used to filter popunders. This was the case in the original implementation of popunder filtering, however this was removed eventually as this was causing too many false positives for popunders, causing legitimate tabs to be closed (#1010). The new solution is to still filter popunders according to existing popup filters, but to disregard popup filters which are too broad. Cases for which a popunder cannot be taken care by an existing popup filter, an explicit popunder filter should be used.

Closed as fixed: Pale Moon

• A minor bug with the "Block media elements" function

Firefox 31 and less, Pale Moon

• UO (when used with uMatrix) displays old connected domains

Core:

• Empty domain line (cell) - how can this be?
• Logger doesn't show not blocked popups
• dev version has problems when opening _blank target links
  • Reopened, a new solution has been implemented.

[trium]

ublock v1.6.6

gorhill released this

a day ago

Closed as fixed:

Chromium

• Port instance destroyed instead of reused in contentscript-start.js
• Google Analytics still tracks on GitHub - collection sent via POST

Firefox

• Showing incorrect context for github websockets

Core

• uBO doesn't count discarded cosmetic filters with 'Parse and enforce cosmetic filters' disabled
• Misinterpreting filters with elemhide
• Closing legit tabs as popunders
• HOSTS file filtering also blocking domains with a different ccTLD
• In logger, exceptions rules with "elemhide" are "red"

[trium]

ublock v1.6.8

gorhill released this

2 days ago

Changes:

From now on, uBlock Origin will pull assets (filter lists, scriptlets) from a project dedicated strictly for the purpose of maintaining those resources: uBlockOrigin/uAssets. Notice that this project is owned by uBlockOrigin, an organization I created to maintain all things related to uBlock Origin, uMatrix. For now uAssets is the first project to be held under that organization.

The goal of uBlockOrigin/uAssets is to receive all the reports for the need of new filters, or reports of web pages broken by existing filters, and will be open for people to contribute (i.e. given write permissions on the project). Ideally I wish there will be eventually a small army of volunteers dedicated to deal with filter issues.

Closed as fixed: Firefox

• uBlock Origin ignores changed tld

Core

• I can't filter this elements
• Too long URLs in dropdown selector causes desktop glitch

[trium]

ublock v1.7.0

gorhill released this

4 days ago

Changes

Element picker

The element picker has been beefed-up:

• It will now offer as filter choice background images, if any. (#1202)
• When you click on an element on the page, it will report all elements found under the mouse.
  • Previously, the picker would report filters only for the element clicked and its ancestors.
• Filters for media elements will now be offered, if any. (#1545)
• You can now preview the effect of the selected filter on the page. (#650)

Chromium-based browsers

It is now possible to block websocket connections for Chromium-based browsers. (Chromium issue, #956, #1497):

Ability to filter websocket connections like any other network requests will take care of a new breed of ad-delivery techniques seen on more and more sites, and currently existing protocol-independent filters in filter lists will take care to filter out many of these websocket connections just like they did for http/https connections. For those wholesale-blocking 3rd parties on a site, websocket connections to 3rd-party servers will no longer escape the block.

Examples of cases solved by the ability to filter websocket connections with no need for special filters:

• https://forums.lanik.us/viewtopic.php?f=62&t=30068&p=92706
• https://forums.lanik.us/viewtopic.php?f=62&t=29304&p=91894

A general observation though, is that webscokets are more and more used: you will spot their use on sites such as GitHub, New York Times, etc.

Making uBO aware of websocket connections allows it to report these (previously invisible^[1]) connections to the user, through the logger or through the dynamic filtering pane in the popup panel.

_{[1] from uBO's point of view.}

Closed as fixed:

Chromium

• Unable to block websockets. (see #1497).

Firefox

• uBO can cause FF 45 "Exit" to not terminate correctly

Core

• Preferring document over popup filters
• Redirection fails for filters having : in the host part
• Element picker does not offer a filter to block the clicked video element
• A "no-popups: * true" rule will block new tabs opened from "chrome://extensions/"
• [Request] Block Background Ads
• [suggestion] Preview element picker filters

[trium]

ublock v1.7.2

gorhill released this

2 days ago

Changes: Chromium-based browsers only

Emergency fix: removed WebSocket support for the time being (#1604):

• I overestimated the number of people using the dev build of uBO -- and as a consequence assumed that any issue would have been reported prior to release.
• I underestimated the use of WebSocket in the field -- turns out it's used way more than expected.

Sorry for the unexpected breakage.

Ideally, fixing the root issue would be best -- maybe starring the issue will make it more likely to be fixed sooner than later.

Update: There is now a companion extension for uBlock Origin, which will restore the ability of uBlock Origin to see/filter WebSocket connection attempts: https://chrome.google.com/webstore/detail/ublock-origin-websocket/pgdnlhfefecpicbbihgmbmffkjpaplco.

[trium]

ublock 1.7.4

gorhill released this

2 days ago

Notes

Chromium-based browsers

No significant change: I just tidied up changes made for the emergency fix released as 1.7.2. Now-unused code paths related to WebSocket wrapper code have been removed (they were bypassed in 1.7.2).

Reminder: if you wish uBlock Origin to be WebSocket-aware, install the companion extension uBO-WebSocket. (Issues encountered in the original code have been fixed.)

[trium]

ublock 1.7.6

gorhill released this

a day ago

Closed as fixed: Firefox

• Disable DNS prefetching when pre-fetching is disabled in settings
• NoScript + uMatrix = cookie leak
  • uBO was not suffering from the specific reported issue, but was theoretically suffering from the root cause at the source of incompatiblity between uMatrix and NoScript.

Tor browser

• Addons do not work randomly

Core

• Element picker: blocking data: URI-based resources does not work
• For certain rules logger does not show from which list(s) it originates
• Dynamic filtering problem
• Regex-based filters should not be case sensitive by default
• Preview "##iframe" in element picker, hides element picker
• Logger unduly discarding events in edge cases
• Complex whitelist rules never catch on localhost

[trium]

ublock v.1.8.0

gorhill released this

16 days ago

New:

New cosmetic filtering operators: :has(), :xpath(), :style(). See detailed documentation at "Static filter syntax".

These new operators are to be used only for cosmetic filtering cases which are hard to crack -- more and more of these are surfacing (for example DOM elements with random class or id values).

When it comes to cosmetic filtering, preferably, always favor a plain old CSS3-based cosmetic filter, since they can be used in a declarative way, inside a style tag. But there are cases where no CSS3-based expression will work, and in such case consider these new :has and :xpath operators.

Note that unlike :has, :xpath is not a valid CSS4 expression, so they will always be enforced in a non-declarative way (in other word, javascript is doing the filtering, through document.evaluate).

These new cosmetic filtering operators can be "excepted" like any other standard CSS3-based cosmetic filter using the usual #@# prompt. Such exception cosmetic filters do not have to be specific however, i.e. you do not have to associate them to a specific hostname/entity.

Changes

The content script code responsible to implement cosmetic filtering has been re-factored:

• To harden against sites which tries to work around uBO's cosmetic filtering.
• To improve general performance and memory usage.
• To support the new cosmetic filters.

Closed as fixed:

Firefox

• uMatrix's fix to issue #540 has been imported into uBO.

SeaMonkey

• Toolbar icon gone in private browsing window

Core

• "Can't properly upload attachments to any XenForo-based sites"
• Own static filter not immediately available?!
• Logger visual issue
• Domain-anchored filters that can't be tokenized, are rejected
• Fixed a static filtering issue reported in EasyList forum.
• Separator ^ is being stripped off filters
• Support cosmetic filters with explicit style properties
• Firefox 42 and cosmetics

[trium]

ublock v.1.8.2

gorhill released this

12 days ago

Fixed

A regression bug which caused a non-catched exception to be thrown when creating a filter using the element picker.

[trium]

ublock v.1.8.4

gorhill released this

11 days ago

Fixed:

• Unspecified element removed: regression introduced in 1.8.0 when cosmetic filtering was refactored. Some classes of exception cosmetic filters were disregarded.

[trium]

ublock v.1.9.0

gorhill released this

15 hours ago

New:

Cosmetic filtering operator matches-css(), to remove any DOM element which matches specific CSS properties (see uBlockOrigin/uAssets#84).

It is now possible to tell uBO to ignore all generic cosmetic filters from loaded filter lists (see #1892).

Fixed: Chromium

• ws-gateway websocket circumvention ?

Firefox

• Bug 1232354 - uBlock Origin makes the loading of a long page hang the content process
  • The issue is not specific to uBO, it likely affects any extension which implements shouldLoad().
  • The person who reported the bug would have found many other extensions being worst than uBO (including BluHell at 20s).
  • I could find a sensible work around for the shouldLoad() issue for uBO though, as explained in the bug comments.
  • Though the code change obviously benefits the specific test case in the bug report, it will lower the overhead uBO add to web pages in general in Firefox (e10s enabled or not).

Core

• Hostname anchor matching behavior
• Browser hangs with uBlock + uMatrix + disabled javascript
• uBO fails to disable inline script execution on aranzulla.it
• Popup filter closes a page as popunder
• Element picker has a problem with creating rules with specific unicode/HTML-code
• NSFW - wrong pornhub filter proposed by element picker
• Add "Ignore generic cosmetic filters" option in the "3rd-party filters" pane
• script:inject filters are discarded when disabling the parsing of cosmetic filters
• Optimize SVG icons [fixed by @asamuzaK]
• Cosmetically filtered DOM elements in embedded frames are not counted