Link Cleaner 的評論
Link Cleaner 作者: Erwan Ameil
15 筆評論
- 評價 4 分,滿分 5 分來自 Rico Liebscher,5 年前
- 評價 4 分,滿分 5 分來自 Firefox 使用者 15700431,5 年前Thank you for your great work. You're making the internet a better place. Appreciate it! :)
Does this add-on also remove "&fbadid=" and "?fbadid=" ?
Then I see "?utm_", but does it also remove "&utm_"? Or does it simply remove all "utm_"s ?
And what about Twitter's AMP redirection ("?amp=1") ?
Keep up the good wotk! :-D :thumbsup: - 評價 4 分,滿分 5 分來自 Firefox 使用者 14643790,6 年前
- 評價 4 分,滿分 5 分來自 Firefox 使用者 14242938,7 年前
- 評價 4 分,滿分 5 分來自 Faculty Row Spam,8 年前Great add-on thanks for sharing this link cleaner add-on with all
- 評價 4 分,滿分 5 分來自 Firefox 使用者 13033547,8 年前
- 評價 4 分,滿分 5 分來自 DoubleATam,8 年前I presume that's what's happening when the "support page" link on this very page isn't cleaned of fluff.
Which is a shame, because I would like to be tell what page I am outgoing to? On this site? It's like, the site where I most notice the unclean links??? dangit firefox - 評價 4 分,滿分 5 分來自 Firefox 使用者 13188500,8 年前
- Works nicely on Firefox Desktop, but it seems to have issues in Fennec Nightly — I had tried it before, and it plain and simply didn't work; but I just reinstalled it (after some time of disuse) and while it cleans the first link (with utm tracking parameters) it fails to clean the Amazon.com link. Weird. Again, it works fine on Desktop Stable, but at least on Fennec Nightly your mileage might vary. I cannot test on Fennec Stable/Beta/Aurora, so... Keep it in mind.
開發者回應
張貼於 8 年前Should be fixed once the new version passes review, thanks to andreicristianpetcu on github. Please tell me if it's still an issue for version 1.3 - Running the addon with the release version of firefox, both example links are 'cleaned' as indicated. However, when installing the addon under Nightly, only the first link is cleaned, the Amazon link remains the same.
For what it's worth, this seems to be the case for other similar addons.開發者回應
張貼於 8 年前Thanks for noticing (I don't use nightly daily, so I didn't see that it wasn't working there).
You can thank https://github.com/andreicristianpetcu who provided a fix, it should be fixed when the new version hits addons.mozilla.org.