🍵
When you've #privacy #RedPilled so hard, you look up the most common browser resolutions and change your kwin rules to always make your new #LibreWolf windows to be that size (after getting the size right with a "what is my browser size" website since the browser doesn't report the room taken up by the chrome.
@rl_dane
True, it might be tricky — even though there is an option to achieve adaptive design in pure CSS now, some websites still rely on JS, so the safest bet is to enable it only on the websites you trust and use some sort of containerisation or at least "private mode" on those you do not 😩
Yeah, I used to use #NoScript like @sotolf does, but with some sites like banking and "professional" websites, it's a trip and half to get the site to work at all, then to work in non-Chrome browsers, then to work with uBo/PrivacyBadger/CanvasBlocker, then adding NoScript to all of that jazz would really send me loopy. XD
But I think it's totally valid to have a "general browsing" browser that's locked down like Fort Knox, and then a very vanilla one for "don't break on me, cheems!" work sites.
I dunno. :P
@rl_dane
Keeping things separate is never a bad strategy!
And yes, the process of figuring out what to allow and what to keep denied can be daunting, expecially when you have to deal with Google or MS web "apps" which bring scripts and content in from dozens of different domains — on the other hand, you don't have to do it often: once you figure it out, it usually keeps working at least till the end of the year 😅
@m0xee
The only thing I've come across quite like that is the letterboxing option, but it's quite annoying to use in practice. It basically snaps the view to certain pre-set sizes, which means that a sizeable chunk of your window is inert/unused.