- cross-posted to:
- technology@lemmy.world
- firefox@fedia.io
- hackernews@derp.foo
- cross-posted to:
- technology@lemmy.world
- firefox@fedia.io
- hackernews@derp.foo
In order to measure the user experience, Firefox collects a wide range of anonymized timing metrics related to page load, responsiveness, startup and other aspects of browser performance. Collecting data while holding ourselves to the highest standards of privacy can be challenging. For example, because we rely on aggregated metrics, we lack the ability to pinpoint data from any particular website. But perhaps even more challenging is analyzing the data once collected and drawing actionable conclusions. In the future we’ll talk more about these challenges and how we’re addressing them, but in this post we’d like to share how some of the metrics that are fundamental to how our users experience the browser have improved throughout the year.
uMatrix died years ago since you can do the same things in uBlock & the result is easier to share.
I use uBlock in allowlist mode for JavaScript. The number of SPAs that shouldn’t be as well as zero effort put into a basic, semantic noscript to at minimum say what the script will do & remind to allow JS is pretty gross tho. Web developers need to do better.
people keep saying you can do the same thing in ublock as in umatrix but the UI is completely different and not nearly as intuitive and I don’t nearly have as granular control as I had in umatrix