Not so important how much telemetries, but where these go. A complex feature rich browser can have a lot of tech telemetries, but this is only bad if these go to sites not related to the functionality and third parties, eg. to Facebook, Amazon and others.
A secure browser ought to phone home on startup (and honestly with as little overhead as requests incur nowadays, on tab open) and make sure it’s updated to the latest version, do a dns sanity check, etc.
I don’t even mind Firefox having ads in the default homepage.
Important only which requests go out and to where. If tech data go to the company of the browser, it’s OK, but not if user data goes to Amazon, Alphabet, Facebook, Towerdata, etc., which has nothing to do with the functionality of the browser. Permissions can be restricted in the settings of the OS.
Not so important how much telemetries, but where these go. A complex feature rich browser can have a lot of tech telemetries, but this is only bad if these go to sites not related to the functionality and third parties, eg. to Facebook, Amazon and others.
Yeah it’s unimportant how many requests go out.
A secure browser ought to phone home on startup (and honestly with as little overhead as requests incur nowadays, on tab open) and make sure it’s updated to the latest version, do a dns sanity check, etc.
I don’t even mind Firefox having ads in the default homepage.
Important only which requests go out and to where. If tech data go to the company of the browser, it’s OK, but not if user data goes to Amazon, Alphabet, Facebook, Towerdata, etc., which has nothing to do with the functionality of the browser. Permissions can be restricted in the settings of the OS.
And what the requests are, I don’t care if some cdn is carrying Mozilla’s homepage requests, for example.