

I suspect they probably do far more than their title lets on; but damn that’s an extremely unfortunate title to have. I can’t imagine that particular part of the title sells well on the resume.
That said; I think numbers 2 through 5 could probably see their pay halved or cut by a third and they’d still be fine. I wouldn’t push anyone below 200k though. I didn’t suggest the Chairperson because it appears that Mozilla isn’t actually paying them, some other entity is doing so and it’s being reported here for “tax purposes”.
Note: This isn’t to suggest that they need to cut these folks’ pay right now; it’s just observing where Mozilla might reduce spending if it were to become necessary to keep things going for them. I am actually assuming good faith that each of these folks are well worth their current pay.
This is mostly useless to me; I already enforce all tabs into unique containers to isolate browsing and website contexts from one another; while still allowing me to make exceptions to the rule and “unbreak” things if that’s causing an issue, but still keeping things isolated from the rest of the browsing.
As for Tab Management; I use two windows and a plugin; Tab Stash Plus; which collapses tabs I stash into a bookmark.
Every so often when I reach a critical mass of tabs I personally go through them and play “Keep/Toss” with more odds on Toss. Only useful tabs get stashed and are then searchable from the plugin.
In general; since this feature now presents a possibility of an extremely UNWANTED AI integration I will be setting the config to off and leaving it off…using a relevant config policy tool or plugin to enforce this to off if needed. I hate AI features that I didn’t ask for and this one definitely doesn’t seem like it’s going to be helpful nor compatible with my current workflow.