I'm curious, what is the motivation for avoiding that stuff? It seems to just be there to make it easier for Stripe to see where traffic is coming from, in this case.

Why? I mean you're still sending the referer header, right?

No, browsers don't send the referer header for https links.

That's only if linking from https to an http page which is not the case here.

Off topic: Is there a chrome extension that will strip these query parameters off automatically when a user clicks on links?

I found https://chrome.google.com/webstore/detail/url-tracking-strip... but wasn't sure if someone might have found a superior extension.

I created this [1] some time ago to manipulate links in the pages that I visit.

This part [2] removes the UTM parameters from the links in certain websites.

However, I stopped updating the extension when I switched to Safari some time ago.

I used to use this one [3] which was actually my inspiration to create my own project.

[1] https://github.com/cixtor/markasread

[2] https://github.com/cixtor/markasread/blob/08726ce/markasread...

[3] https://github.com/jparise/chrome-utm-stripper

I prefer "Ghostery" which is more efficient in "Tracking" overall. try it out.

Aren't ghostery the ones who sell your personal info and allow advertisers to pay them to get on a whitelist? UBlock Origin is my recommendation.

> UBlock Origin is my recommendation.

You may prefer it to Ghostery, but it doesn't actually address GP's request, for query parameter stripping does it?

Can someone explain how that utm_* stuff got there if the original poster didn't include it? And if he did, where did he get this URL from?

utm_source is set to 'HN', so the original poster did include it, or it would say something else.

OP is Stripe employee, so that'd make sense

Google Analytics.

damn, another lesson in reading the comments before clicking on the article