yes, if you enable resist fingerprinting on any Firefox build it will cap refresh rate to 60hz. Mull is not doing anything special, it’s just changing about:config options by default.
you can disable resist fingerprinting in mull and regain standard refresh rate (although you lose fingerprinting protection) just as you can enable resistFingerprinting in Firefox beta or nightly and see refresh rate cap at 60.
while, yes, regardless of your privacy settings google still collects a sickening amount of data on you, much of these things (like voice recordings and location history) can be managed and disabled in the settings. if you wish to go further, grapheneos removes A LOT of tracking potential.
these should be opt in features, but one can opt out of much of them.
out of curiosity, are you aware what changes exactly make the Play Integrity API eligibility requirements not able to be met? with Google play installed, the compatibility layer should be able to facilitate the necessary communication, I would think.
or are they just arbitrarily saying anything that’s not stock isn’t eligible?
all your first points are generally correct, as far as the last one however, that is the entire point in running your own instance. too many uses on matrix.org. all fedi platforms have this issue as well.
I said nothing about not having anything to hide. I said it doesn’t mean much. dns resolvers were intended to be cloud based. the only difference between nextdns and standard dns resolvers is the control over function nextdns hands the user.
using cloud services also allows home devices to stay secured via keeping ports closed. the whole “the cloud is someone else’s computer” is just another way of saying “I don’t know how to practice good opsec”.
your isp/vpn provider also can log all your data, or are you going to suggest running everything over tor now?
a dns query does not send that much info since all the contained data from site to user is encrypted and takes network routes separate from the DNS query.
Firefox has a weaker sandbox than chromium and less mature site isolation and therefore has lower security. privacy is a different story, but remember you’re only as private as you are secure so Firefox is inherently not that private assuming a malicious site escapes the sandbox.
I’m fully against chrome’s growing monopoly as well as Google surveillance capitalism but let’s not be so dramatic with the “google mother ship” nonsense.
using chromium as a base does not equal data being sent back to Google, just like using Android as a base doesn’t inherently send data back to Google.
that is a fair point, I wish people didn’t trust cloud storage as much but I blame Microsoft for putting it as the default home directory on windows unless disabled. even chromebooks default to local storage unless you select Google drive while windows defaults straight to OneDrive without any obvious signifiers
I 100% agree, I just think it’s dangerous rhetoric to push because you end up with normies that have been told “open source is more secure” and end up running any script they find on GitHub without having a clue how to audit what it’s actually doing. (this was me 5/6 years ago until I figured out what I was doing).
this is the same reason I find people claiming that Linux is more secure than windows dangerous. I can exfiltrate data from the average Linux install much easier than windows. you can harden Linux to a much greater degree but if you don’t know how or that you even need to, you are in a much worse position.
you need to use Firefox beta, nightly, mull, or Fennec F-Droid to access about:config and from there you can search for and enable resistFingerprinting. it’s not an option in the settings.