Page 1 of 1

uBlock Origin

Posted: 2023-02-07, 17:55
by fatboy
Good Day folks,

I am here to ask a favour, can someone please update uBlock Origin on the Pale Moon extensions page? The last update was in 2021 and I feel it might be a good time to get a new version on there for those of us who can't compile it ourselves?

Thank You

Re: uBlock Origin

Posted: 2023-02-07, 20:38
by Nigaikaze
fatboy wrote:
2023-02-07, 17:55
can someone please update uBlock Origin on the Pale Moon extensions page? The last update was in 2021
Requests to update that extension should be made on its GitHub page. The problem is that the person maintaining that extension (JustOff) lives n the Ukraine, and has not been heard from online since the Russian invasion last February. Either gorhill will have to update that extension himself or someone will have to step up and have permission from gorhill to fill JustOff's shoes until JustOff (hopefully) comes back online.

Re: uBlock Origin

Posted: 2023-02-08, 00:26
by moonbat
What do you want a new version for?

Re: uBlock Origin

Posted: 2023-02-09, 18:39
by fatboy
moonbat wrote:
2023-02-08, 00:26
What do you want a new version for?
So that I can use this filter (https://raw.githubusercontent.com/Dande ... rtener.txt) in its entirety and not just 12 urls of its 2116

Re: uBlock Origin

Posted: 2023-02-10, 01:20
by moonbat
fatboy wrote:
2023-02-09, 18:39
So that I can use this filter (https://raw.githubusercontent.com/Dande ... rtener.txt) in its entirety and not just 12 urls of its 2116
Why would a malfunctioning filterlist be a problem with uBO? :wtf:

Re: uBlock Origin

Posted: 2023-02-10, 05:09
by nicolaasjan
fatboy wrote:
2023-02-09, 18:39
moonbat wrote:
2023-02-08, 00:26
What do you want a new version for?
So that I can use this filter (https://raw.githubusercontent.com/Dande ... rtener.txt) in its entirety and not just 12 urls of its 2116
uBlock-for-firefox-legacy does not support $removeparam.
Open issue.

Re: uBlock Origin

Posted: 2023-02-10, 15:39
by BopBe

Re: uBlock Origin

Posted: 2023-02-11, 06:15
by nicolaasjan
Just tested these (both seem unmaintained).
They didn't remove tracking parameters from e.g. google.com (added these to their configuration).
Nothing related in error console.

Example:

Code: Select all

https://www.google.com/search?q=treesize+free&source=hp&ei=wijnY9vkIM-ykwXa942oBg&iflsig=AK50M_UAAAAAY-c20mGzFlU5qFyeLqtPxQVUKEnARyTH&oq=tree&gs_lcp=Cgdnd3Mtd2l6EAEYADIKCAAQsQMQgwEQQzIICAAQgAQQsQMyBAgAEEMyCwguEIAEEMcBEK8BMgsILhCABBDHARCvATILCAAQgAQQsQMQgwEyBQgAEIAEMggIABCABBCxAzIICAAQgAQQsQMyCwguEIAEEMcBEK8BOgoIABDqAhC0AhBDOhQIABDqAhC0AhCKAxC3AxDUAxDlAjoRCC4QgAQQsQMQgwEQxwEQ0QM6CAguEIAEELEDOgsILhCABBCxAxCDAToOCC4QgAQQsQMQxwEQ0QM6CAgAELEDEIMBOhEILhCABBCxAxCDARDHARCvAVCACFj2DmC-KWgBcAB4AIABQIgB9AGSAQE0mAEAoAEBsAEK&sclient=gws-wiz
[Edit]
On Firefox with uBlock Origin 1.46.1.100 and the relevant lists, I get:

Code: Select all

https://www.google.com/search?q=treesize+free&hl=nl

Re: uBlock Origin

Posted: 2023-02-12, 06:12
by Konrad
nicolaasjan wrote:
2023-02-11, 06:15
They didn't remove tracking parameters from e.g. google.com (added these to their configuration).
The legacy add-on Google Search Link Fix smoothly removes tracking parameters from links on the Google and Yahoo search websites.

Classic Add-ons Archive > caa:addon/google-search-link-fix/versions?page=1#version-1.4.9.1-signed

Re: uBlock Origin

Posted: 2023-02-12, 22:57
by moonbat
nicolaasjan wrote:
2023-02-11, 06:15
Just tested these (both seem unmaintained).
They didn't remove tracking parameters from e.g. google.com (added these to their configuration).
You didn't do it properly if you were using PureURL - adding them most definitely works, as seen below with iflsig.

Code: Select all

[PureURL:]Original request: https://www.google.com/search?q=treesize+free&iflsig=AK50M_UAAAAAY-c20mGzFlU5qFyeLqtPxQVUKEnARyTH&oq=tree&sclient=gws-wiz
Cleaned request:https://www.google.com/search?q=treesize+free&oq=tree&sclient=gws-wiz
And there is nothing to maintain - the whole point of having a configurable garbage parameter list is so that you can add whatever extra parameter you want instead of depending on a server side list you have no control over.

Re: uBlock Origin

Posted: 2023-02-13, 05:17
by nicolaasjan
moonbat wrote:
2023-02-12, 22:57
You didn't do it properly if you were using PureURL - adding them most definitely works, as seen below with iflsig.

Code: Select all

[PureURL:]Original request: https://www.google.com/search?q=treesize+free&iflsig=AK50M_UAAAAAY-c20mGzFlU5qFyeLqtPxQVUKEnARyTH&oq=tree&sclient=gws-wiz
Cleaned request:https://www.google.com/search?q=treesize+free&oq=tree&sclient=gws-wiz
And there is nothing to maintain - the whole point of having a configurable garbage parameter list is so that you can add whatever extra parameter you want instead of depending on a server side list you have no control over.
OK, I reinstalled the extension and now it works. :P
I guess PEBKAC. :oops:

Sorry for the noise...

Only 4 errors in Error Console regarding ei and ved parameters (which were removed regardless):
E.g.:

Code: Select all

Timestamp: 13-02-23 05:58:44
Error: [PureURL error:] URI= https://www.google.com/gen_204?atyp=i&ei=fMPpY5GEFPSK9u8Psb61kAM&ved=0ahUKEwiRsv-Y25H9AhV0hf0HHTFfDTIQ39UDCAY&zx=1676264324872
modified path=/gen_204?atyp=i&zx=1676264324872
[Exception... "Component returned failure code: 0x80004004 (NS_ERROR_ABORT) [nsIURI.path]"  nsresult: "0x80004004 (NS_ERROR_ABORT)"  location: "JS frame :: chrome://pureurl4pm/content/common.jsm :: observe :: line 292"  data: no]
Source File: chrome://pureurl4pm/content/common.jsm
Line: 295

Re: uBlock Origin

Posted: 2023-02-13, 09:07
by moonbat
Yeah, the failure code thing is in some internal code, I've never been able to find what causes it. For the rest, just add whatever parameters you encounter that you want removed, then clear the log and refresh the page to see if it gets removed. By default the extension just has the most common utm_source and a few others.