in its first iteration, it strips all AI shit, doesn’t just disable it; the hero went through the source tree and patched it by hand!

it differs from LibreWolf and friends as there’s an intention to hard-fork the thing (LW should be based on basebrowser) and let the abomination that is the mozilla shell-game-corp of today behind, thus returning to the original idea behind creating mozilla, best described by the dude who gave us the thing:

In my humble but correct opinion, Mozilla should be doing two things and two things only:

  1. Building THE reference implementation web browser, and
  2. Being a jugular-snapping attack dog on standards committees.
  3. There is no 3.

mastodon thread: https://mastodon.social/@sarahjamielewis/116994970688711387

the patch repo: https://codeberg.org/basebrowserproject/organization

firefox repo: https://github.com/mozilla-firefox/firefox

build instructions: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html

the only thing missing’s how to apply the patch. it’s as simple as going to the firefox source folder and applying the patch file with:

patch -p1 < the.patch

and then proceed with ./mach build.

this was my first time building firefox from source and it wasn’t half as bad; about 30ish minutes on an i7-870 in the background without any excessive load that woulda made the system unusable.

  • douglasg14b
    link
    fedilink
    arrow-up
    8
    ·
    5 hours ago

    How are they going to maintain the hard fork when something like 95+% of all engineering efforts that support LibreWolf and similar come from the Firefox engineering team?

    Mostly mundane stuff like security patches, performance fixes, and web standards features and updates make up the bulk of the engineering efforts.