GeorgeSoros Honestly, the defaults are perfect for the average person. I see no need to change anything unless your threat model requires it. I’ve been a part of the privacy sphere for years now and I’ve come to notice that as people create their fully customized privacy setup, they’ve substantially reduced the security model, their privacy, or their convenience in one way or another.
Take for example, someone who decides to install the flavor of the month Firefox fork instead of using Vanadium. The ONLY people installing these esoteric browsers are in the privacy space, which makes it doubly ironic that they’re substantially reducing their security and privacy by using them. They also tend to tack on every privacy extension under the sun. This user is now on a browser which is less secure than vanadium, very arguably less private, slower, and less trusted (considering that a random dev makes a new Firefox fork every month or so)
Another example is someone who decides to sell their iPhone to install lineage or something, they’ve immeasurably decreased their security and usability for negligible, if any, privacy gains.
This is why sticking to defaults coded by sane, competent devs who intimately understand the trade offs between security, privacy, and usability is the absolute best choice.