• 3 Posts
  • 560 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle










  • Edit: As rtxn and n0x0n point out, we can adjust settings in Firefox itself and expect them to stay applied, but any settings done within the websites for Mozilla’s services could be changed on the Mozilla end at any time. Probably best to have an extra layer to this just in case.


    Yes. Yes it can, and you bet your bibby people will be watching to see if Mozilla bypassed those settings, not that they ever have in their multiple decades of existence.

    You’ll also have to opt out of using Mozilla services like browsing and bookmark sync.


  • What? What?

    Their track record has no instance of them not respecting settings! A track record of multiple decades! The code is fully auditable, so any of those shenanigans would be caught immediately!

    I feel like I’m taking crazy pills lately.

    We need to be on guard and verify they don’t do this shit, but outright expecting it? When Firefox also has a history of absolutely abysmal PR on shit like this, without the follow up of abysmal practices?

    It feels like accelerationism. Like people want Firefox to fail, rather than just wanting to be prepared if it does.


  • What? I’ve grown up around people in the nuclear industry, and nothing I’ve ever learned about the function “wastes” water.

    Some rambling on how I understand water to be used by reactors

    You’ve got some amount of water in the “dirty loop” exposed to the fissile material, and in the spent fuel storage tanks. Contaminated water is stuck for that use, but that isn’t “spending” the water. The water stays contained in those systems. They don’t magically delete water volume and need to be refilled.

    Outside of that you have your clean loop, which is bog standard “use heat to make steam, steam move turbine, moving turbine make electiricity, steam cools back to water”. Again, there’s no part of that which somehow makes the water not exist, or not be usable for other purposes.


    Not saying you’re wrong. Renewables are absolutely preferable, and Texas is prime real estate to maximize their effectiveness. I’m just hung up on the “waste water building reactors” part.

    Guessing it was some sort of research about the building process maybe, that I’ve just missed?





  • Yes, they allow full avoidance of any potential data collection through the browser, if they remove the collection features.

    Mozilla would need to change their licensing terms to prevent forks from being able to remove things like that, and forks could just use the last version of the code before the license change and just backport new features.

    Also Firefox is fully open source, unlike chromium which relies on a closed source binary blob in the middle. Some chromium forks have replaced the binary blob with open source code, but the default is for chromium forks to have a nice chunk in them controlled by google that no one can deeply inveatigate what it does. Firefox does not have this issue.

    Mozilla can’t hide any potential data collection in Firefox due to the full open source nature (unlike chrome forks). They also can’t stop fork devs from stripping out any data collection functions. And as of today, they have not introduced any data collection that is not supremely anonymized, and they have not introduced any data collection that cannot be opted out of through the browser settings (and about:config).