dngray
openpgp4fpr:588f6e4eabe8c7b552d00fa641911f722b0f9ae3
Just be mindful decentralization doesn’t inherently mean there is privacy.
Seems like a step up from “Covenant Eyes” with weirdo politicians sharing their porn habits with their children.
It’s probably also media’s fault for this. They only publish when a bad person does a bad thing on the internet with it, not all the millions of users who don’t do bad things. That would be boring.
Download Navi from F-Droid. It does not have as much web functionality as Vanadium
From the looks of it Navi is just a download manager, not an actual web browser.
For that reason, I use IceCat on computer.
But do you actually compile those binaries yourself. A lot of browsers are open source.
Brave is still Chromium in a new coat of paint and you’re still aiding Google in their domination of web standards.
That is a little unfair tbh, they do quite a lot, such as their privacy shields, including the script blocking one which is basically like NoScript.
They also do some work on anti fingerprinting tech and other things along that vein.
Ungoogled Chromium is my current favourite
The reason we don’t recommend Ungoogled Chromium and instead recommend Brave on the privacyguides.org website is because they have proper build infrastructure managed by the Brave. With Ungoogled Chromium the binaries are produced by third parties, vary in version etc. People claim they would only use “open source software” but they do download binary versions nevertheless and don’t compile that code themselves. This increases the risk of a supply chain attack, where a malicious binary is submitted and nobody has really knows until it is too late. The other issue is they disable CRLSets because of “google hate” which we think actually increases the likelihood of a MiTM attack occurring because rogue certificates are not detected and invalidated as quickly as they could have been.
This article describes a few other things https://qua3k.github.io/ungoogled/
ungoogled chromium exists
The reason is they have proper build infrastructure managed by the Brave. With Ungoogled Chromium the binaries are produced by third parties, vary in version etc. People claim they would only use “open source software” but they do download binary versions nevertheless and don’t compile that code themselves. This increases the risk of a supply chain attack, where a malicious binary is submitted and nobody has really knows until it is too late. The other issue is they disable CRLSets because of “google hate” which we think actually increases the likelihood of a MiTM attack occurring because rogue certificates are not detected and invalidated as quickly as they could have been.
This article describes a few other things https://qua3k.github.io/ungoogled/