safeshare

5 ms·

1. 1.▲
   by safeshare 9mo ago

   I built SafeShare, a local-first URL cleaner that removes common tracking parameters (utm_*, gclid, fbclid, msclkid, etc.) in the browser. Why: these params leak into chats, emails, docs, tickets and carry extra metadata. How it works: past
2. 2.▲
   Show HN: SafeShare Pro – a local-first URL cleaner (removes tracking params)(j-ai-71.github.io)

   1 points by safeshare 10mo ago|0 comments
3. 3.▲
   Show HN: SafeShare – Clean up tracking parameters (UTM, fbclid, gclid)(j-ai-71.github.io)

   1 points by safeshare 10mo ago|0 comments
4. 4.▲
   by safeshare 10mo ago

   If you have a few real-world URLs where you’d want to keep/edit specific params, I’d be happy to use them as test cases.
5. 5.▲
   by safeshare 10mo ago

   Thanks a lot for the thoughtful comment. You’re right that for many HN folks the interesting part is not just “make the URL shorter”, but understanding what is being removed and being able to keep / edit specific bits. Right now SafeSh
6. 6.▲
   SafeShare – strip tracking parameters from links before you share them(github.com)

   3 points by safeshare 10mo ago|4 comments
7. 7.▲
   by safeshare 10mo ago

   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 t
8. 8.▲
   Show HN: SafeShare – Clean tracking params locally (PWA and bookmarklets(j-ai-71.github.io)

   2 points by safeshare 11mo ago|0 comments