Wiki suggestions for a more hardened settings

[rodrgz]

Description

Improve security awareness for flags by indicating security levels in the flag information.

Who's implementing?

• [ ] I'm willing to implement this feature myself

The problem

A lay user may have no idea which flag adds security or removes it.

Possible solutions

Solution 1:

1. Review the available flags and their respective security implications.
2. Select a set of flags that provide a high level of security by default.
3. Create the text in the wiki, providing clear explanations of the effects of each flag to help users make informed decisions.

Solution 2:

1. Enhance the table on https://github.com/ungoogled-software/ungoogled-chromium/blob/master/docs/flags.md by indicating the level of security provided by each flag.

Alternatives

No response

Additional context

No response

[ghost]

I see that you probably want something hardened OOTB akin to Tor Browser and LibreWolf. However, the added flags related to privacy and safety are mostly just changes that makes sense to be implemented at the browser level. Flipping these on by default and calling the browser hardened without also recommending or packaging additional extensions/patches that address the endless potential concerns is irresponsible.

Some of us simply want a "quiet" base browser—and this project is as close as it gets.

Regarding your proposed solutions:

1. Flags are flags mostly because they are tangential to the project and not everyone wants to turn on those features. If the flags' descriptions are incomplete, they can be improved. At the moment, they are concise without unnecessary bias.

2. "Security level" is highly subjective and arbitrarily assigning values will only give users a false sense of safety. Maybe categorizing the flags by type (i.e. privacy, safety, look & feel, etc.) can help with discovery.

[rodrgz]

I am satisfied with your answer. But, I believe a better description of the flags would help.