> Firstly, yes you can 20 year old paper. "Domain tagging," Felten and Schneider's proposed countermeasure, was implemented as "cache partitioning" in Firefox,

> Firstly, yes you can 20 year old paper. "Domain tagging," Felten and Schneider's proposed countermeasure, was implemented as "cache partitioning" in Firefox, Safari, and Chrome. If you're aware of extant issues please let me know. > In fact, I don't actually know of a time where I've seen perf metrics being used without tracking Google's own library: https://github.com/GoogleChrome/web-vitals#overview https://github.com/GoogleChrome/web-vitals#overview, which is recommended in OP's article. > I'm not in favour of that for something as trivial (in most case) as just making a website load slightly faster No performance RUM means no knowledge of performance regressions. I have deployed changes that looked great on our CI and then gravely impacted performance for a segment of customers. Blinding a business to user experience because you've read papers on historic exploits seems like odd logic to me. You can't do anything malicious with a DB of LCP timings. HN's anti-telemetry mindset is baffling to me.