If you're going to put it in a bag for a week, why not use some kind of hibernation feature?

You have to muck around with your disk partitions on Linux (although windows I think supports it out of the box)... I haven't spent enough time researching it to feel confident I can do it without borking my system

As another commenter said, sometimes upgrades require manual intervention. You can fix this using a tool like informant which shows you all the interventions you have to do before you upgrade.

Also, you can use a tool like snapper + btrfs-assistant (both of which come pre-installed on Cachy IIRC) which lets you fully revert your filesystem (snapper rollback) or partially (snapper undochange) if something breaks. Just make sure to use a btrfs filesystem for that.

No adblocking extension would ever rely on a clear bug to function. Google reviews extension code and would immediately patch the bug, and maybe use it as an excuse to kick the extension off the web store. I don't buy the idea that there was a viable second option here.

Dude, what.

Think about who you're helping and who you're fighting against.

I think the trouble is that certain adblocking features (like skipping ads on YouTube, Twitch, etc) require modifying the page you're viewing in your browser; just filtering network requests isn't enough. So right now a browser extension is the most natural choice for an adblocker, but honestly that might change if browsers keep being so hostile towards them.

expose DOM and JSON to external .DLL then

browsers should have open Web standards as well as open local runtime.

Yeah, this was my thought process. I get the appeal, but I don't think a million-user open-source extension is gonna start relying on a clear bug to function.

Unfortunately extensions can't have webview perms :(

"'webview' is only allowed for packaged apps, but this is a extension."

:( but maybe Vivaldi and Brave could remove this check just for fun.

From my experience (as a Brave user), using a User-Agent switching extension and setting it to Firefox for twitch.tv gets around that :)

I agree that would change things but I can't picture an open-source extension with millions of users pivoting to rely on something that's clearly a bug.

At that point it's a feature, not a bug.

Having millions of users on your side is great ammunition.

Author here, thank you! A lot of the comments here are more general arguments about MV3 and Google (which I kinda expected) but I'm glad see someone who liked my post :)