ShittyKopper [they/them]

  • 1 Post
  • 46 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle






  • They aren’t forced to do anything. Manifest v3 is just a part of the WebExtensions API (which is not a standard and is really just “whatever Chrome does except we find/replace’d the word chrome to browser”) which both Safari and Firefox chose to implement in order to make porting of Chrome extensions easier.

    Before that, Firefox had a much more powerful extension system that allowed extensions quite a lot of access to browser internals, but that turned out to be a maintenance nightmare so they walled those APIs off (not a coincidence that Firefox started getting massive performance improvements after that, and extensions stopped breaking every other release) and decided to go the WebExtensions route. I have no clue what Safari was up to but I think they implemented it after.

    If they don’t implement Manifest v3, extensions that want to work across multiple browsers need to support both the older Manifest v2 and the later Manifest v3, which would be a burden not many extension authors would want to bother with, which would make them just say “yeah we’re not supporting anything outside Chrome”. Firefox avoids this problem by extending the v3 API to allow for the functionality necessary for powerful ad blocking Google removed in v3 (webRequestBlocking) while also implementing the new thing (declarativeNetRequest) side by side, so extensions that want to take advantage of the powerful features on Firefox can do so, while Chrome extensions that are fine with the less powerful alternative can still be ported over relatively easily.

    Firefox does have it’s fair share of extensions on top of the WebExtension API already (sidebar support for one), so adding one more isn’t too big of a deal.


  • the rule of thumb here is that you should really just use one browser ad blocker. having multiple will conflict especially regarding anti-adblocker prevention (as uBO will try to hide itself and redirect to a “defused” version of an ad script and whatever other ad blocker you have will think that’s an ad and block it)

    not entirely sure how well DNS ad blockers fit into this. there is a chance they could make your ad blocking detectable by blocking a request uBO intentionally lets through (possibly in a modified state), but as far as i’m aware there haven’t been too many issues stemming from combining DNS blockers with uBO and the likes.





  • One of the reasons I use containers instead of installing things directly is that i can completely uninstall a service by deleting a single directory (that contains a compose.yml and any necessary volumes) and running a docker/podman system prune -a

    or that i can back up everything by backing up a single “containers” dir, which i could have on a subvolume and snapshot if i wanted to

    systemd/quadlet on the other hand makes me throw files in /etc (which is where you’re supposed to put them, but ends up resulting in them being tangled together with base system configuration often partially managed by the package manager)

    The Solution™ to this is configuration management like ansible or whatnot, which needlessly overcomplicates things for the use cases i need (though they’re still useful for getting a base system “container ready” wrt ssh hardening and such)

    tldr: i want my base system to be separated from my services, and systemd integration is the exact wrong tool for this job