Waterfox: No AI* Here - A Response to Mozilla's Next Chapter
https://www.waterfox.com/blog/no-ai-here-response-to-mozilla/
Waterfox: No AI* Here - A Response to Mozilla's Next Chapter
https://www.waterfox.com/blog/no-ai-here-response-to-mozilla/
LibreWolf is another option. It is a custom version of Firefox, focused on privacy, security and freedom with all bad bits (like LLM/AI, No trackers/telemetry, enhanced privacy etc) removed.
* Repo https://codeberg.org/librewolf
* Home page https://librewolf.net
@tragivictoria I think we are all misunderstanding each other.
Anyway, which telemetry can be good? I think each data transmission from the consumer to the supplier should be voluntary and actively done. For instance, when sending a crash report.
@sebzuen anything that's not sensitive/private info is fine. There's no reason collecting hardware information is bad.
And opt-in telemetry is worse than not having it at all.
@tragivictoria Realistically speaking, I agree that everything non-sensitive/private is fine for devs to collect.
Generally, it's a matter of policy in my eyes. When it is only for the supplier to decide which kind of telemetry they collect, consumers have to trust their goodwill or live with the consequences of them gathering bad telemetry. There is no way for consumers to actively take part in the decision process what is gathered.
@sebzuen Thats why transparent telemetry is important (in the topic of Mozilla, not sure they qualify here? Not sure). But realistically any and all telemetry discourse is poisoned by "NOOOO DON'T SPY ON ME PLEASE DONT COLLECT MY PRIVATE INFORMATION I WILL SWITCH TO SOMETHING ELSE PLESSE DONT", so any public discussions on the topic dont do any good :(
That being said, i would love privacy laws to restrict the bad telemetry. Not sure how this one would be feasible tho.