https://pomf2.lain.la/f/uc9hp3yw.png   
      
   An optimized and (mostly) ungoogled release of Chromium 143.0.7484.0 has   
   been successfully built and you can too!   
      
   According to   
   https://browserbench.org/Speedometer3.1/   
   it scored quite a bit higher than librewolf. Which is a good browser to   
   consider.   
      
   Be sure to limit the number of cores used when building. Otherwise you   
   might overheat your hardware.   
   https://pomf2.lain.la/f/wsg7rwbf.png   
      
   For a privacy-oriented build that is still functional, here's an overview   
   of the tweaks that were made in the build configuration (args.gn):   
      
   - Google services removed, no telemetry, empty API keys   
   - H.264/AAC codec support, extensions, print preview enabled   
   - Vulkan/VA-API GPU support   
   - Desktop integration: Native Wayland/X11, GTK, notifications   
      
   If you're wondering what the empty API keys are about, here are some   
   Google features which won't be available without it:   
      
   --  google_api_key  --   
   Controls access to:   
      
   * Google Translate integration   
      
   * Google Safe Browsing (malware/phishing protection)   
      
   * Geolocation services (using Google's location API)   
      
   * Speech recognition (Google Speech API)   
      
   * Spell check (Google spell-check service)   
      
   --  google_default_client_id + google_default_client_secret  --   
      
   Controls OAuth2 authentication for:   
      
   * Chrome Sync (bookmarks, history, passwords across devices)   
      
   * Google account sign-in in browser   
      
   * "Sign in to Chrome" feature   
      
   * Chrome Web Store authentication   
      
   * Google Drive integration   
      
   * Gmail notifications   
      
   That's right. Google mommy isn't going to be able to read your weird   
   German scat website and offer to translate it for you. You're going to be   
   on your own there. Scheiße!   
      
   On the other hand, you should still be able to print on your local   
   network, log into wifi at a hotel, and watch videos in the browser.   
      
   This build can be achieved through the build configuration alone without   
   any patches to source required. I have it at around 35G for the source   
   code, 931M for depot_tools, 8.7G for the build, and 570M for the installed   
   files. Once it is installed, that 570M install is all you need to keep.   
   Until you need to update to the next major release...   
      
   This is not a comprehensive guide to building Chromium. This build   
   configuration is intended as a reference to help you achieve the same   
   level of ungoogled Chromium for your system. YMMV and you will need to   
   tweak things appropriately for your system. You will certainly need to   
   determine the dependencies and tools required for your system.   
      
   Nevertheless, it can be done.   
      
   ==================================================================   
    OPTIMIZED UNGOOGLED-CHROMIUM BUILD CONFIGURATION   
   ==================================================================   
   The settings shown here are a good reference for what you should use for   
   an "ungoogled" build. You will have to modify it based on your system.   
   https://ghostbin.lain.la/paste/n2ak4   
      
   ==================================================================   
    POST-INSTALL NOTES   
   ==================================================================   
   You may need to run the binary with certain flags. I ended up using a   
   wrapper script to launch the binary so I could set a location for the   
   user-data-dir. I have more than one version of Chromium installed atm and   
   didn't want to use the default. I also added the flag --ozone-platform=x11   
   because Chromium apparently hasn't integrated support for Vulkan on   
   Wayland on AMD systems. I don't really know what the situation is there,   
   but the X11 fallback works.   
      
   The other big point to note is if you want sandboxing to work, you'll need   
   to set up user namespaces. AppArmor and SELinux are most common for   
   managing this. Otherwise you will want to launch the binary with the --no-   
   sandbox flag.   
      
   ==================================================================   
    UPDATING YOUR BUILD   
   ==================================================================   
   One reason to keep the source and your build is so you don't need to do an   
   entire rebuild to update.   
      
   When new Chromium versions are released:   
      
   # Work from wherever you have the source   
   cd ~/chromium/src   
   
   
   # Update source code   
   git fetch origin   
   git checkout main   
   git pull origin main   
   
   
   # Update dependencies   
   gclient sync --with_branch_heads --with_tags   
   
   
   # Rebuild   
   autoninja -C out/Release chrome   
      
   ==================================================================   
    MAKING LLM USEFUL   
   ==================================================================   
   I have found that LLM *can* be helpful with keeping track of what you're   
   doing and setting everything up as long as you first provide the current   
   src/docs/linux/build_instructions.md and valid args that can be used.   
      
   The list of valid args can be generated from withing the chromium src   
   directory with:chromium-valid-args.txt   
   gn args out/Release --list > chromium-valid-args.txt   
      
   Provide build_instructions.md and chromium-valid-args.txt to the LLM and   
   it should be a lot less stupid in assisting you. Pay attention to wtf you   
   are doing instead of blinding following a dumb ass reddit chatbot when it   
   tells you to put a tilde in your PATH declaration. I know a guy who did   
   that.   
   https://pomf2.lain.la/f/zjonvaa5.png   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)