Brave does farbling: https://github.com/brave/brave-browser/issues/11770

JShelter is a nice extension that tries to implement the same things in other browsers, it’s a bit limited by the fact that it’s an extension.

https://jshelter.org/farbling/

I’ve yet to see a serious review of Duckduckgo browser, the only thing I saw was that because of it’s agreement with Microsoft for their search engine the browser, for a time, had rules to avoid blocking Microsoft tracking.

Sadly Firefox has no tab sandboxing on mobile so yeah, it is less secure.

And while I agree the Brave company is shady, the browser has good security features.

Well in the end I think I’m needlessly nitpicking. It doesn’t matter if it’s strictly immutable or not. What matter is that it has the good parts of reproducibility, immutability and declarativity.

Isn’t immutability related to the root filesystem being read-only? I can write on my root filesystem, even if it’s mostly links to the store I can replace those links.

Yes, or use flakes which gives you a lockfile pinning everything. But this is related to reproducibility, not immutability.

I’ve had NixOS absolutely refuse to run some compiler toolchain I depended upon that should’ve been dead simple on other distros, I’m really hesitant to try anything that tries to be too different anymore.

Yes, some toolchain expect you to run pre-compiled dynamically linked binaries. These won’t work on NixOS, you need to either find a way to install the binary from nix and force the toolchain to use it or run patchelf on it somehow.

Well that was an approximation to keep it simple and disprove the given example. There are other directories in the root filesystem that are in the path by default, or used in some other critical way (like /etc). Even if they are links to directories in the nix store you can replace the link.

These seems to be related to flatpak, not immutability.

What things?

What namespace are you talking about?

To be honest I don’t know these very well. I only use NixOS. My understanding is that in an immutable distribution the root filesystem is read-only. Granted in NixOS the nix store is immutable and most things in the root filesystem are just links to the nix store, but the root filesystem itself is not read-only.

I’m on NixOS right now and just dropped a Chewy in my /bin, only had to sudo touch /bin/chewy.

if it’s being read from, it can be written to.

Why would being able to read imply being able to write?

Having an extra step or two in the way doesn’t make it “extremely secure”.

Well it can greatly improve security by preventing a compromised app to achieve persistence.

The store is immutable but the system itself definitely isn’t.

I wouldn’t call NixOS immutable.

I don’t know, if your goal is security Pixels have the best hardware and GrapheneOS the best software. It makes a lot of sense.

You can destroy it all the same with cp or cat.

Yeah, I expected this.

You accuse me of shifting the conversation and you end up being the one doing it. I never said the conversation was irrelevant, I said that whether or not the end goal was to stop or not was irrelevant in deciding about switching to a less toxic mode of consumption.

You complain that it’s mostly bro-saying, marketing and low quality source but when the conversation becomes serious you drop it and never bring any research to your argument.

And you don’t even know the definition of words central to the subject, like vaporisation or aerosol, and yet you act like you know, saying so many approximate to downright false things. It’s OK not to know a subject, no one can know everything, but don’t act like you, misleading people along the way.

I’m OK continuing this conversation if you bring some substance to it. Other please edit your initial message to avoid misleading people.

This is what’s called “risk reduction”, less harmful is better.

I meant regulated as having standards, of course.

Of course it says further research is needed, most papers say that. Again I’ve yet to see a paper that puts vape as more harmful that smoke.

I’ve never seen vape marketing using the word steam, vapor is the scientifically correct word, it’s not an aerosol. An aerosol is a solid or liquid element in suspension inside a gas, this is not the case, the elements you are inhaling are gaseous, it’s a vapor.

And how would you know the amount of water in the myst you see? How can you visually differentiate between the elements? The vapor is composed of all the elements with lower boiling point (I made a mistake using the word melting point in my previous message) than what you set on the vaporiser. Smoke has water in it too.

It’s really simple, burn the thing and you get a very night temperature, almost everything gets vaporised, a lot of elements react to create more harmful ones and you get a lot of smoke (with a little bit of water in it too). Now use a vaporiser, heat it a lot less, to a lower temperature and less elements get vaporised, there are way less reactions (no CO) and you get way less visible gas.