What this has done for me has highlighted how many things are tracker me and how badly those things are designed because they don’t fail gracefully.
I had a telehealth visit link today that broke using this feature. So that’s nice to know. My virtual doctors appointments are being tracked by a third party.
Edit, looks like Firefox is smarter than me, ignore this.
I don’t know what the link was doing, but just because FF thought it was “tracking info” does not mean it was nefarious. It could be used for authentication or security. I have not tested it, but I presume this would break a “reset your password” email link.
I’m rather certain, the way it works is that it removes parameters that are named like well-known tracking parameters. For example, most webpages use Google Analytics, so you see UTM parameters everywhere.
A “reset your password” link could theoretically use a parameter that’s named utm_content, then it would presumably get removed by this feature, but I see no sane reason why one would name their password-reset parameter like that.
In general, such tracking parameters are usually named in a way that it will rarely clash with other parameters a webpage may want to use, so for example they may have a prefix like utm_.
Looking at some comments on the linked post, I think you are right, and it would probably be fine for things like a password reset. I could play around with it, but my laptop is in the other room.
Umm, your telehealth link was basically a one time password to log you in/authenticate you.
This feature is for browsing the web where you shouldn’t have to identify yourself to visit a blog about Ravens. If you’re visiting your bank, a service you already use, etc, then the unique url was more for them to confirm it’s you because only you have that unique url.
It’s just the GET parameters it’s stripping, those can be used for all sorts of things to pass information to a website to be used as variables for all manner of innocuous things… They just get (ab)used by trackers more than normal web traffic since most of the other uses comes from a site that can pass that as a POST instead, which embeds the parameters in the request header rather than making the URL a mile long, and wouldn’t be useful (and could actually be problematic) to be shared with others as part of copying it
This is a good step forward for privacy. However, how it’ll handle data embedded in the URL like MVC?
Also, if it does work well, it’s a matter of time until developers find a way to get around it and probably enhance and increase data collected in the process.
What this has done for me has highlighted how many things are tracker me and how badly those things are designed because they don’t fail gracefully.
I had a telehealth visit link today that broke using this feature. So that’s nice to know. My virtual doctors appointments are being tracked by a third party.
Edit, looks like Firefox is smarter than me, ignore this.
I don’t know what the link was doing, but just because FF thought it was “tracking info” does not mean it was nefarious. It could be used for authentication or security. I have not tested it, but I presume this would break a “reset your password” email link.
So click the regular copy button instead?
I’m rather certain, the way it works is that it removes parameters that are named like well-known tracking parameters. For example, most webpages use Google Analytics, so you see UTM parameters everywhere.
A “reset your password” link could theoretically use a parameter that’s named
utm_content, then it would presumably get removed by this feature, but I see no sane reason why one would name their password-reset parameter like that.In general, such tracking parameters are usually named in a way that it will rarely clash with other parameters a webpage may want to use, so for example they may have a prefix like
utm_.Looking at some comments on the linked post, I think you are right, and it would probably be fine for things like a password reset. I could play around with it, but my laptop is in the other room.
Oh, so it’s not just stripping the GET parameters? Okay, that’s smarter than I was assuming
Stripping all GET parameters would break many, many legitimate webpages. 🫠
Umm, your telehealth link was basically a one time password to log you in/authenticate you.
This feature is for browsing the web where you shouldn’t have to identify yourself to visit a blog about Ravens. If you’re visiting your bank, a service you already use, etc, then the unique url was more for them to confirm it’s you because only you have that unique url.
deleted by creator
It’s just the GET parameters it’s stripping, those can be used for all sorts of things to pass information to a website to be used as variables for all manner of innocuous things… They just get (ab)used by trackers more than normal web traffic since most of the other uses comes from a site that can pass that as a POST instead, which embeds the parameters in the request header rather than making the URL a mile long, and wouldn’t be useful (and could actually be problematic) to be shared with others as part of copying it
This is a good step forward for privacy. However, how it’ll handle data embedded in the URL like MVC?
Also, if it does work well, it’s a matter of time until developers find a way to get around it and probably enhance and increase data collected in the process.