4 ms·
What most people don't understand is that a targeted IP, with a stream size and a timestamp is enough to identify pretty every https page uniquely if it is acce
by cookiengineer 6y ago
What most people don't understand is that a targeted IP, with a stream size and a timestamp is enough to identify pretty every https page uniquely if it is accessible by a spider.
A headless chrome makes measurements of timings even easier these days. The order of how files are loaded, which file size e.g. jquery.123.min.js has, and where and when exactly in which order it is loaded from is very unique among all pages of a website.
- parliament32 6y ago>stream size and a timestamp I think that's more complicated than you realize. That list would be impossibly large to scrape and search, not to mention collisions and dynamic content problems. >The order of how files are loaded It's a good idea, but you don't know what files I have in my cache and when they expire, or what files my extensions are blocking. This'd only work in an ideal-case scenario.