Sorry to see you go jawz and thanks for all the feedback you’ve given over the years.

The thing this add-on does and others don’t is simply auto-detect embedded URLs. This also causes many breakages and means the ruleset has to be whitelisting instead of when & how to clean links…

I’m sure the UI and many other things can be improved, but I have limited time on my hands, Also any suggestions on improvements of the UI or anything else are always welcome.

Please read that issue fully, or have a look at the latest version (4.0.2), which DOES NOT REQUIRE « Download » permissions. « access to all Tabs » was always needed, CleanLinks can’t work otherwise.

On your further questions:
- I don’t control which permissions are show by AMO and how they are worded. The full list of permissions required by CleanLinks are in the manifest.json file and explained here: https://github.com/Cimbali/CleanLinks/#why-are-the-requested-permissions-required
- I don’t know why you would trust an add-on that has access to data for all websites (thus could read all your login/passwords!) but not one that has access to the download list. In any case, check the source code before installing/upgrading (and also before rating the add-on…) if you’re unsure!

Just download the add-on, unzip it, and look inside. CleanLinks does not minify/uglify code so you can look at it. Not only can you see what the add-on does, but you can also compare the permissions from the different versions that way, and see that they are the same (if not less) for v4 than for v3.x.

As explained in its description, the extension blocks all links that contain hidden URLs inside them. You can then whitelist manually which use cases seem reasonable to you from the add-on’s popup menu.

Hi @user 14773836, and thanks for your feedback. Currently control click works fine for me. If you could come over to https://github.com/Cimbali/CleanLinks/issues/ to report your setup (OS, Firefox version, etc.) and an example of a link on which this happens, then I could have a look at fixing it for you too!

Hi @user14702040, sometimes you can be tracked by images, and when that is automatically detected the add-on blocks them.

Fortunately you can easily whitelist per domain by clicking the add-on icon, selecting the offending link, and click "Whitelist Selection."

You can also choose to have the application only clean links that you clean, not other resources loaded, by unticking "Clean outgoing HTTP Requests" in the add-on preferences.

This is now possible since the v4 was released.

Hi and thanks for using Clean Links! When encountering a bug, you can report it on https://github.com/Cimbali/CleanLinks/issues with the original link that loads incorrectly, so that I can find out what went wrong and fix it.

The bug causing "Request URI Too Large" has been fixed in version 3.2.4

Hi, I'm not sure what you mean. We un-obfuscate links when they are clicked and when they are loaded, but none of those are really aware of the location bar. If you open an issue on https://github.com/Cimbali/CleanLinks/issues we can discuss it and I'll look into it.

Hi and thanks for using Clean Links! As it stands there is a bit of a learning curve with Clean Links where everyone builds up their whitelist. I'm looking to get a centralized set of rules while still allowing customization, which isn't easy -- but I'm working on it.

Hi! If you only care about clicked-llink tracking and not other kind of fishy redirects, you can untick "redirect watcher" and "outgoing HTTP requests" in the addon's preferences.

Then we only clean the redirect links that you click on, and we're pretty accurate on those! Only a few whitelist items are ever needed, and most of them are shipped by default.

Otherwise please report any shortcomings or suggestions at https://github.com/Cimbali/CleanLinks/issues