"Total cookie protection" from Firefox is a great step in the right direction of putting user interest above those who are actively trying to invade our privacy. Thank you for pioneering this.
Sadly, that horse has long left the barn. The FF multi-account containers extension and Firefox Focus were popular for years for a good reason. The battle lines have now moved to stealing our CPU cycles, network bandwidth & memory. We now need client-side resource protection, with full user control.
Many sites and extensions/apps have taken the liberty of using our computers against our wishes. CPU is the biggest pain-point. The client-server DDoS pattern has now been completely inverted. Many Firefox processes are taking too much CPU. I'm seeing processes that are taking 100% CPU for hours. The service providers are now the biggest abusers and we're being DoSed and charged for electricity we don't really use. 100% CPU utilization for hours, all night, when the (desktop) browser isn't even used is wasted energy and a great contributor to climate change as well. A double whammy. The band-aid I now use is a cronjob to periodically check for abuse and kill Firefox CPU hogging processes.
Users should have full control over what every site gets in terms of resources, with some good defaults:
Option: completely freeze/suspend apps that are not in use (unexposed tabs & minimized windows)
If a tab needs to work in "the background" (e.g. a mail tab to check whether I have new mail or calendar app to update new appointments) I want to be able to limit it to what is in my interest, e.g.: - Foreground processes: active tabs: Never consume more than P% CPU and never more than X CPU seconds (cumulative) - Background processes: non active tabs and minimized windows: - Get a CPU time slice only once every N seconds, no more - When given a time-slice: never work continuously for more than M seconds (unless explicitly allowed)
Thoughts/ideas for defaults: - When FF is minimized, freeze the CPU for everything. Including web sockets / async updates. - Processes in tabs that aren't exposed should NEVER be taking 100 %pct CPU. If they do, they should be considered misbehaving and the user should have an option to restrict them. - Even for an active/visible tabs: more than X% CPU for more than N minutes/seconds (both user settable), should be considered abusive. IOW: users need the FF CPU/task scheduler to be in their full control.
Thanks for listening.
... View more