New Update ClearURLs

[oldschool]

will ClearURLs update itself or do I have to go to chromestore and play with it?

It auto-updated on Brave but for some reason didn't in Edge. You may also go to the dev GitLab page and download CRX file.

 

[simmerskool]

It auto-updated on Brave but for some reason didn't in Edge. You may also go to the dev GitLab page and download CRX file.

OK! I see that it did autoupdate in Brave. Nice when things work

 

[oldschool]

Latest ClearURLs update:

[1.19.0] - 2020-07-22

Changed url decoding to prevent endless loop

 

[Stopspying]

Latest ClearURLs update:

[1.19.0] - 2020-07-22

Changed url decoding to prevent endless loop

Thanks for the heads up on this.

On Firefox 'Check for updates' in the Add-ons Manager does not find this update. Ver 1.18.1 is the last update that was installed on June 10.

 

[SeriousHoax]

Thanks for the heads up on this.

On Firefox 'Check for updates' in the Add-ons Manager does not find this update. Ver 1.18.1 is the last update that was installed on June 10.

Same here. Updates are reviewed manually so it takes a bit of time sometimes. Already up to date on Chromium Edge.

 

[oldschool]

@Stopspying @SeriousHoax M$ Store is faster to update extensions than Chrome WS. At least, that's what I'm seeing. I don't use FF. Those will update later.

 

[Stopspying]

@Stopspying @SeriousHoax M$ Store is faster to update extensions than Chrome WS. At least, that's what I'm seeing. I don't use FF. Those will update later.

Firefox got the 1.19.0 update today.

 

[oldschool]

Open issues have been accumulating for this extension. Now there is this post from the developer:

"ClearURLs is currently being completely rewritten to make it better and faster. This may result in longer delays than usual when processing issue tickets."

Announcement: ClearURLs will be rewritten (#703) · Issues · Kevin R. / ClearURLs

 

[eXDj]

this year ?

 

[oldschool]

this year ?

He didn't give a timeline.

 

[oldschool]

Here is the roadmap for planned fixes, but it's unclear if ETag filtering will be fixed in Chromium. We'll see ...

 

[oldschool]

ClearURLs update: v.1.20.0

​

• Added Dutch translation by Harm M.

• Changed url decoding to prevent endless loop
• Performance optimizations for rules by @thexeos
• Changed default rules and hash host to Github Pages
• Changed rules changelog button href to the new rules submodule repo
• Updated various translations - thanks to all contributors

Currently available in Chrome Web Store only, which is stange since it's usually last to get updates.

 

[HarborFront]

I think it still hasn't settled the eTag issue. Below is taken from Chrome Web Store for ClearURLs

All functions in a nutshell

* Removes tracking from URLs automatically in the background
* Blocks some common ad domains (optional)
* Has a built-in tool to clean up multiple URLs at once
* Supports redirection to the destination, without tracking services as middleman
* Adds an entry to the context menu so that links can be copied quickly and cleanly
* Blocks hyperlink auditing, also known as ping tracking
* Prevents tracking injection over history API
* Prevents Google from rewriting the search results (to include tracking elements)
* Prevents Yandex from rewriting the search results (to include tracking elements)

ClearURLs - Chrome Web Store

Remove tracking elements from URLs.

chrome.google.com

 

[oldschool]

I think it still hasn't settled the eTag issue.

I don't think he's figured out how to fix it. He has indicated "it's something with Chromium", as if there is no fix, which we know is incorrect.

He had also indicated the entire extension would be re-written, but I don't think it's happened with this version.

 

[oldschool]

I've added italics for emphasis.

ETag filtering not working? (#524) · Issues · Kevin R. / ClearURLs

That's weird. ClearURLs removes the ETag header, but Chromium somehow seems to store it anyway, so it doesn't matter if ClearURLs deletes it or not.

I have to investigate this again. Maybe it would help if I also remove the If-None-Match header. If it is no longer sent, it should theoretically not be possible to map it anymore with the ETag. However, this header is also used for POST requests to avoid duplicates. So here we need to make a distinction by request type. I don't know yet whether this is possible so easily.

ClearURLs fails the eTag test at Cookieless Cookies. · Issue #67 · ClearURLs/Addon

I know about this problem. Unfortunately, the eTag filtering under Chrome does not work correctly at the moment. Under Firefox everything is cleaned up correctly. I have to find out why this is the case.

 

[HarborFront]

v1.20.0 is available for Firefox now

ClearURLs – Get this Extension for 🦊 Firefox (en-US)

Download ClearURLs for Firefox. Removes tracking elements from URLs

addons.mozilla.org

 

[oldschool]

Rewrite is in progress. From the changelog.md :

• Rewrite ClearURLs completely form scratch in typescript
• Add features from the milestone %1
• Dedicated documentation page like docs.drasyl.org

 

[HarborFront]

Removing ClearURLs for Firefox

The reason why this extension still exist in my FF is its ability to remove ETags

You can remove this extension (if you want) if you have Adguard for Desktop and add the necessary 'Strip URLs tracking parameters' to it. Its 'Block hyperlink auditing' is now handled by FF itself because I have auditing/block CSP reports in uBO disabled and it pass the Ping Spotter test below

Ping Spotter

armin.dev

To pass the cookieless cookie test go to change the preference settings as below

Quote

crssi commented on Dec 4, 2017​

About ETags and performace... To get rid of ETags, I have set: user_pref("browser.cache.memory.enable", false); user_pref("browser.cache.memory.capacity", 0); No ETags, but I don't see any performance issues too.

Unquote

Etags: solutions besides clearing/disabling cache [which does clear/block etags, sorry about the confusion] · Issue #179 · arkenfox/user.js

snip

github.com

Notes:-

1) The above same settings affect the setting of FF to RAM by setting
user_pref("browser.cache.memory.enable", true);
user_pref("browser.cache.memory.capacity", -1);

2) You can set a certain amount of the RAM or set -1 for dynamic allocation of RAM.

3) Besides the above two settings other settings are also needed to completely set FF to RAM. So the decision lies with the user.

Test it at

Lucb1e.com :: Cookieless Cookies

Now, I have one extension less

 

[eXDj]

when new version for edge chromium ?

 

[amirr]

when new version for edge chromium ?

Maybe soon. New version updated for Chrome today.