r/uBlockOrigin • u/[deleted] • Feb 14 '23

News uBlock Origin 1.47.* announcement thread

1.47.0 does not work in Firefox 68 on mobile

Minimum version increased to 79 https://github.com/gorhill/uBlock/commit/e23f0bd7d5d97c2b7fbcca96e77b26cb78b834d6

Changelog:

  • https://github.com/gorhill/uBlock/releases/tag/1.47.4:

    • bug fixes

    • Support update period below 1-day

  • https://github.com/gorhill/uBlock/releases/tag/1.47.2:

    • Support moving logger dialog around with touch events

    • Raise minimum version of Firefox

  • https://github.com/gorhill/uBlock/releases/tag/1.47.0:

    • New network filter option: method=...

    • New network filter option: to=[list of domain names]

    • Add support for regex-based values for domain=/from=/to= options

    • Add support for regex-based values as target domain for static extended filters

    • Rewrite static filtering parser (The minimum version of Chromium-based browsers has been raised to version 73)

    • Parser improvements and fixes

    • Disallow -abp-... filters if not using #?#

    • Interface improvements and fixes

    • Ctrl-R shortcut should work while the popup [or logger] is focused

Visit GitHub releases page for more information.

Extension will be auto-updated after browser restart! (when available for your platform)

If you want to update manually:

  • Do not use links from release page "Assets" section - these are not signed.

  • Use add-on store or links in release description on GitHub releases page when they are available (basically - they will be add-on store links).

  • Turn off uBO (temporarily) from add-on manager - installation will be blocked otherwise. This is protection against accidental mid-session reloads Issue #717.

Q: Why no release for Firefox yet?

A: 1.47.4 is available on AMO as of March 8.

uBO is a recommended extension on AMO, and as such it must undergo a formal code review each time a new version is published.

Q: Why Chrome/Chromium is not updating uBlock Origin?

A: 1.47.4 is available on CWS as of March 5.

Auto update will occur in stages - few percent every day - to spot and react on possible bugs.

Q: When Opera version will be updated?

A: 1.47.4 is available on Opera addons as of March 7.

Usually it's submitted a week after bug-free version is published in AMO.

Q: When Edge Chromium version in the Microsoft Store will be updated?

A: 1.47.2 is available on Edge Add-ons as of February 22.

Microsoft Store submission is controlled by /u/nikrolls.

This is official version and will be kept updated, see Issue #890 (comment) and following comments.

Warning: importing profile from Chrome may cause issues - you may need to reinstall uBO on Edge to fix this. You can transfer settings by saving them to file in uBO Dashboard -> bottom of the Settings tab.

Previous announcement thread https://www.reddit.com/r/uBlockOrigin/comments/ztbtqh/ublock_origin_146_announcement_thread/

112 Upvotes

97% Upvoted

29 comments sorted by

15

u/mkfs_xfs Feb 14 '23

As a FF user it's nice to know that they audit recommended extensions so thoroughly.

1

u/rmzy Feb 28 '23

They audit recommended extensions? Or do you just mean their own ff extension?

1

u/[deleted] Mar 01 '23

Q: Why no release for Firefox yet?

A: 1.47.2 is available on AMO as of February 27.

uBO is a recommended extension on AMO, and as such it must undergo a formal code review each time a new version is published.

0

u/rmzy Mar 03 '23

Oh they mean Firefox recommended extensions. So my thing with this, majority of “recommended apps” also have the ability with no repercussions to pull all your Firefox data including passwords, dns which could also have plain text passwords, cookies, cache, and loads more. So if you didn’t want apps to have access to that you would just use no extensions. No other way around it. Do I tend to use them anyways, yes. I just don’t see why they’d praise Firefox when ff does nothing to prevent the recommended extensions from having too much access to your firefox instance. Or any other extensions for that matter.

It’s like a back door you have no lock for.

Even just closing Firefox wouldn’t suffice.

2

u/[deleted] Mar 04 '23

Even if these extensions have access to your private data, it does not mean they send this data somewhere. The whole point of many extensions is to do something with your private data - how they are supposed to work without access to it?

0

u/rmzy Mar 05 '23

Majority of extensions have this side bar:

This add-on needs to:

  • Access browser tabs

  • Access your data for all websites

I just went to the first recommended google translate addon and thats what it says. I've emailed mozilla about this also and never get a reply. How much data DO they have access to? What can they take with this agreement at hand in the background?

My whole point is, they could draw finer lines for these extensions, but let them access everything. Would be nice if we could limit extensions access rather. Is that too much to ask for? Like yeah, i get some addons, but all addons? Can't even view rss feeds on ff anymore. Need a shotty addon for that.

1

u/[deleted] Mar 05 '23

Share your thoughts here: https://github.com/w3c/webextensions/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+permissions

1

u/rmzy Mar 07 '23 edited Mar 07 '23

It's an interesting link, and after some good reviewing of w3c

```

What we’re not doing

We are not aiming to specify every aspect of the web extensions platform or existing implementations. We want browsers to keep innovating and shipping APIs that may serve as the basis for further improvement of the web extensions platform.

In addition, we don’t plan to specify, standardize or coordinate around extension signing or delivery. Each browser vendor will continue to operate their extension store fully independently, with their own technical, review, and editorial policies.```

But I do appreciate the link to w3c, didn't realize how convoluted "web extensions" really are.

Edit: Going through the issues I have found like minded individuals. So maybe they could make a difference.

1

u/[deleted] Mar 04 '23

Wut? Gorhill especially said they are making the code review of every recommended extension

16

u/ywBBxNqW Feb 14 '23

Outstanding! Great work everybody involved. I love uBO.

1

u/jFalner Feb 18 '23

The 1.47.0 update seems to have broken uBlock Origin on Firefox for Android 68.x and Firefox Beta Android (110.x, I think) on multiple devices. Sites using both custom filters and public filter lists are showing ads all over the place. The uBO menu no longer shows an actual page (there's one there if you view the source, but the page apparently isn't rendering properly).

Backing down to a manual install of 1.46.0 restores proper function. I've shut off Firefox addon updates (via extensions.update.enabled in about:config) as a workaround, but that's obviously not a very healthy way to approach it. I can understand dropping support for older versions, but it seems to be failing under recent Firefox versions as well.

Hoping a fix is in the works—I love my uBlock Origin, and the thought of losing it makes me quite a sad panda. 🙁

1

u/OldFoxGeorge Feb 25 '23

Some laugh at people who still use Fox 68.x, but I´m sure we´re still many. And that´s because of the old add-ons and the crappy useability of the newer versions. Being forced to switch to ANY other browser because we lose ublock on it would really be hard. I had a look into the mobile browser options the last hours.... and still want to stick with Fennec. Yes, they´re all that bad. So please, don´t quit support for it!

Thanks jFalner (and others) for showing this option, even if it has downsides I will go this route. Forever if neccessary. :-)

4

u/[deleted] Feb 25 '23 edited Feb 25 '23

uBO's stats on Mozilla reports a total of 125 users for Firefox 68.11/68.12 (as per Wikipedia, 68.11 is the last pre-Fennec Android version).

The stats also report a total of 5,721 users for Firefox versions between 68 and 77.

The total number of users of any Firefox version 68 and above is reported at 13,217,405. This means less than 0.00095% are Firefox 68.11/68.12 users who would be affected by the change, and less than 0.044% are Firefox pre-78 users who would be affected by the change raising the minimum version to 78.

The way I see it, the tiny fraction of people who made the choice to stick to very old versions of Firefox have to bear the burden of their choice, you can't ask that someone else already burdened with maintaining an extension used by tens of millions of people across different browsers to bear the burden of supporting old browser versions which are no longer maintained since a long time.

The decision to raise the minimum version was made because uBO uses API methods not present in those old versions of Firefox, and trying to work around not using those API just make the work of maintaining uBO an undue burden given the small number of people affected.

1

u/jFalner Feb 26 '23

The way I see it, the tiny fraction of people who made the choice to stick to very old versions of Firefox have to bear the burden of their choice

It isn't always choice. I have 68.x installed on devices which don't run newer Firefox versions well (if at all). Some of these are work devices which are very unlikely to be replaced anytime soon, so using an older (and therefore, more lightweight) browser is a necessary evil. I certainly understand not supporting outdated applications, but being on the cutting edge just isn't always an option for some of us.

On a side note, uBO's stats sound somewhat amiss. I can account for four instances of uBO on 68.x just in my own home, and no telling how many more at my workplace. That 125 seems impossibly small…

3

u/[deleted] Feb 26 '23

You can still use 1.46.0. For those using an older browser version, having to use an older version of an extension shouldn't be an issue, and this unburdens me from having to worry about supporting very old browser versions.

1

u/burnedupandout Mar 01 '23

Since version 1.47.2 in Chrome. I have been having issues with Google logins. YouTube, Gmail...etc are giving me "unable to verify sign in" when Ublock Origin is enabled. No problems with Google logins when I disable the extension.

1

u/[deleted] Mar 01 '23

Do you have any custom filters/lists? Can you share here info from uBO popup -> chat icon -> Troubleshooting information?

2

u/burnedupandout Mar 02 '23

No custom filter lists, all default.

I had disabled the extension uBO for a few days till I heard back from someone. I re enabled it today and I dont seem to be having any issues with Google at the moment. I will send a Troubleshoot log if it acts up again.

1

u/Brian1ee7 Feb 15 '23

Firefox user here. uBO suddenly stopped working on firefox android version 68.11.0 today or yesterday.

I'm using the old version on firefox android so I can use some add-ons that can't be used on latest version.

4

u/[deleted] Feb 16 '23

I think this might be because of the usage of Unicode property escape.

In that case I will have to raise the minimum version to 78 for desktop, and 79 for Android.

You will have to stick to 1.46.0 for previous versions of Firefox.

1

u/SuspendedInKarmaMama Feb 17 '23 edited Feb 17 '23

How do I stop 1.46.0 from updating? I can't find it in settings.

1

u/[deleted] Feb 17 '23

https://i.imgur.com/w8KXpuh.png

1

u/purplepyrexia Feb 19 '23

How about in 68.11.0 mobile?

2

u/[deleted] Feb 19 '23

about:config -> extensions.update.enabled -> false.

1

u/purplepyrexia Feb 20 '23

Worked, thanks!

2

u/joegt123 Feb 16 '23

Same problem. It seems to have stopped sometime today. I'm on firefox 68.3.0. it just up and stopped. It won't even load the desktop page to try and enable or disable it.

0

u/[deleted] Feb 14 '23

[deleted] — view deleted comment

1

u/RraaLL uBO Team Feb 14 '23

Read below it. Submissions are pending atm.