I built a tiny browser-based tool called SafeShare.
You paste a URL, it removes common tracking parameters (utm_source, gclid, fbclid, etc.), tries to unwrap obvious redirect parameters (url=, redirect=, u=…), and shows you a cleaner link to share.
There is no login, no accounts, no tracking cookies – it runs as a simple web app on GitHub Pages and processes links locally in the browser.
It’s intentionally limited to “link hygiene” and transparency:
– It’s not a full security scanner.
– It does not follow every redirect hop across the network.
– It focuses on cleaning links you want to share (mail, messenger, newsletter, social), not on doing deep inspection.
App: https://j-ai-71.github.io/Supersystem/app.html
Code: https://github.com/j-ai-71/Supersystem
I’d be happy about feedback from this crowd:
– Would you actually use a tool like this in your own workflow?
– Which parameters or patterns would you expect it to handle that it doesn’t yet?
– Is the UX clear enough, or is something confusing/over-engineered?
Any comments, criticism or “this is useless, but here’s what would be useful instead” are welcome.
chasing0entropy•18m ago
Neat, I remove all POST strings as a habit; I would imagine most intermediate skill users would also. Using a webpage to do so would be helpful for more complicated links where the url POST data includes the content ID in one of the strings
I would imagine what you have would be far more useful to HN folks if you add some type of attribution system - meaning parse the URL, identity the tracking strings, and then tell the user what each string one does.
Then let the use check a radio box to re-appeand the desired tracking string to the url(. Maybe add the option to edit the string?
safeshare•39m ago
There is no login, no accounts, no tracking cookies – it runs as a simple web app on GitHub Pages and processes links locally in the browser.
It’s intentionally limited to “link hygiene” and transparency: – It’s not a full security scanner. – It does not follow every redirect hop across the network. – It focuses on cleaning links you want to share (mail, messenger, newsletter, social), not on doing deep inspection. App: https://j-ai-71.github.io/Supersystem/app.html Code: https://github.com/j-ai-71/Supersystem
I’d be happy about feedback from this crowd: – Would you actually use a tool like this in your own workflow? – Which parameters or patterns would you expect it to handle that it doesn’t yet? – Is the UX clear enough, or is something confusing/over-engineered?
Any comments, criticism or “this is useless, but here’s what would be useful instead” are welcome.
chasing0entropy•18m ago
I would imagine what you have would be far more useful to HN folks if you add some type of attribution system - meaning parse the URL, identity the tracking strings, and then tell the user what each string one does.
Then let the use check a radio box to re-appeand the desired tracking string to the url(. Maybe add the option to edit the string?