4 ms·
Exactly. When I share links, I always test a link (load the link in a private window) after stripping out the extra URL info before sharing it. I'm not sure h
by Osiris 9y ago
Exactly. When I share links, I always test a link (load the link in a private window) after stripping out the extra URL info before sharing it. I'm not sure how a browser would do that automatically.
- labster 9y agoActually your process seems pretty easy to automate. Reload a page until you get the minimum set needed to reproduce the current DOM.
- ikeboy 9y agoExcept many pages have unique data on each load
- Osiris 9y agoIf that's what Chrome is doing, verifying that the shortened URL produces the same DOM, then I wouldn't have a problem with that.
- dullgiulio 9y agoThat has exponential complexity, is network-bound (slow) and still doesn't handle many cases (for example a "current DOM" where all relative links and images are broken).
- bluepnume 9y agoShould be O(n) unless you're trying to optimize for every single permutation of query param, right? I'd assume the majority of the time the individual params would be independent from one another. Plus you'd only need to do it once in a while for any given base url and persist the result.
- labster 9y agoCompared to GGP's approach of having a human do it, this is still fast. Also not sure why you'd want to share a link to a page where all the images and links are broken in the first place.
- yjftsjthsd-h 9y agoWith JavaScript in play, even reloading the exact same page might yield a different DOM
- colejohnson66 9y agoOr corporate websites where something as simple as looking at my schedule has a “query run” time
- illnewsthat 9y agoI do the same thing. That being said, a huge majority of users wouldn't take these extra steps.