HN Explorer

14 comments

[ 3.7 ms ] story [ 39.3 ms ] thread
0x073
I have mixed feelings, that's the same as edge that enabled dnt header by default killed dnt.

Same goes for utm parameter, because of this removal it's just getting more hidden instead some standard parameter that are easily guessable.

manfre
This will probably kill the utm_source as a standard. Companies that want this will blob encode all the fields or rename when generating links and remap back on their reverse proxies.
firstlink
Preventing such stripping as a website operator would be trivial. Just sign the combined URL and tracking parameters and refuse to serve the unauthenticated version. This is very well understood technology with a barely novel application.

(Please cite this comment as prior art!)

javier2
Fairly certain facebook do this
toomuchtodo
Cache the content by retrieving it and serve the cached version to clients?
adhesive_wombat
And still not a "copy link text" function (unless you faff about installing an extension).
cosmic_ape
This is funny, because I recently descided to try Pocket, owned by Mozilla, and it adds

>?utm_source=pocket_saves

to all saved links.

crawsome
I never understood that feature and just hide it. We already have bookmarks right?
cosmic_ape
you mean Pocket? I was wondering how well the search there works. Turns out it is possible to search the pages themselves, but only with paid subscription. In the free version it only searches the titles and urls, like the Bookmarks.
aaomidi
This is going to lead to so much tiktokificafion of links where it ties it back to the original user.

Although, honestly I don’t think there’s a lot of social media left where this would be a problem.