Skip Navigation
139 comments
  • My opinion I'd say lose chrome if you absolutely need a chromium browser use thorium any other time use Firefox or a fork of it like Librewolf.

    The reason I say Thorium is because this is in the readme.

     undefined
        
    Manifest V2 support force enabled (Starting in M128 they are experimenting with disabling MV2). It will be completely removed in M136 (10 months from now), and when they finally do remove the actual code for loading MV2 extensions, it will be restored, because F**k Google! Even if it takes a crapload of work, I am determined to restore it, because without UBlock Origin working properly in Thorium, I wouldn't even want to use my own browser!
    
    
    
      
  • is there a way to force dark mode like in chromium? #enable-force-dark has been a life saver for me. I have a TBI and white screens are physically painful. I keep trying to go back to FireFox, but none of the darkmode addons seem to have this kind of always on, no exceptions kind of feature

    • So, you haven't used the "Dark Reader" extension on Firefox. It has "automatic", "scheduled", "system default" options. Also you can disable or enable dark mode for specific websites.

    • i have the same issue you have, bright screens are the worst (i hated visiting wikipedia). try this addon in firefox. instead of messing with the colors and the contrast of the page, it rather puts an dark overlay over the entire page, reducing the brightness and preserving the look.

      https://addons.mozilla.org/en-US/firefox/addon/dark-mode-screen/

      • well see now I am in a pickle. Do I go to the webpage that does not allow itself to be accessible and lose a day of my life to drugs and bed. or just keep using what I am using.

    • Dark Reader can do this, though it requires a little bit of tinkering. First you need to tick "Enable on restricted pages" in the Advanced section of Dark Readers settings (in the old design the settings can be found under "More > All Settings"). Then in about:config, all entries in extensions.webextensions.restrictedDomains need to be removed and privacy.resistFingerprinting.block_mozAddonManager needs to be set to "true". If some of this doesn't work, there's also a GitHub Discussion with different solutions, but what I wrote here should do the trick.

139 comments