cross-posted from: https://sh.itjust.works/post/51860525

Bluesky.

The saga continues! A Firefox developer has taken to social media to note there will be some sort of "kill switch" to completely remove AI features in the wake of the news about more AI features coming along with the new CEO.

TL;DR: The big tech AI company LLMs have gobbled up all of our data, but the damage they have done to open source and free culture communities are particularly insidious. By taking advantage of those who share freely, they destroy the bargain that made free software spread like wildfire.

That was complete bullshit, of course. Yes, I absolutely branded Mozilla.org that way for the subtext of "these free software people are all a bunch of commies." I was trolling.

Once upon a time, Mozilla was three commies in a trenchcoat.

Mozilla is in a tricky position. It contains both a nonprofit organization dedicated to making the internet a better place for everyone, and a for-profit arm dedicated to, you know, making money. In the best of times, these things feed each other: The company makes great products that advance its goals for the web, and the nonprofit gets to both advocate for a better web and show people what it looks like. But these are not the best of times. Mozilla has spent the last couple of years implementing layoffs and restructuring, attempting to explain how it can fight for privacy and openness when Google pays most of its bills, while trying to find its place in an increasingly frothy AI landscape.

Fun times to be the new Mozilla CEO, right? But when I put all that to Anthony Enzor-DeMeo, the company’s just-announced chief executive, he swears he sees opportunity in all the upheaval. “I think what’s actually needed now is a technology company that people can trust,” Enzor-DeMeo says. “What I’ve seen with AI is an erosion of trust.”

Mozilla is not going to train its own giant LLM anytime soon. But there’s still an AI Mode coming to Firefox next year, which Enzor-DeMeo says will offer users their choice of model and product, all in a browser they can understand and from a company they can trust. “We’re not incentivized to push one model or the other,” he says. “So we’re going to try to go to market with multiple models.”

For people who still care about taking back the web.

I'm trying it out, given the Mozilla news today. Made the community. Join if you want.

cross-posted from: https://sh.itjust.works/post/51748026

cross-posted from: https://sh.itjust.works/post/51716383

Hmm, #Firefox používám opravdu dlouho, fakt dlouho, ale asi nastal čas ho opustit, #AI prohlížeč fakt nechci, tak kam půjdeme? @firefox

There weren't any straightforward guides when I looked this up, and I even had to ask myself. But I just needed to put so and so together, get some feedback here, and voila! Hopefully this can work for you too, and could edit userchrome.css in your favorite editor, and see the changes in Firefox immediately. I tested that it works with @import url("folder/file.css");, and nested imports too (if folder/file.css contained @import url("Another folder/file.css");.

1. Install fx-autoconfig (I haven't tested it with other Firefox JS loaders), following the whole install section: https://github.com/MrOtherGuy/fx-autoconfig?tab=readme-ov-file#install
2. In the chrome/JS/ folder, create <any file name>.uc.mjs (I named mine refresh.uc.mjs) and paste the script below (it's slightly modified from this snippet): * The part containing @onlyonce is needed so fx-autoconfig loads it just once, rather than spawn a new instance of the script every time a new firefox window is opened.
3. Clear startup cache: https://github.com/MrOtherGuy/fx-autoconfig?tab=readme-ov-file#deleting-startup-cache
4. You may need to toggle the script. You can go to Menu Bar > Tools > userScripts.

Script

// ==UserScript==
// @onlyonce
// ==/UserScript==

// Script from here:  https://gist.github.com/jscher2000/ad268422c3187dbcbc0d15216a3a8060?permalink_comment_id=3259657#gistcomment-3259657
setInterval(() => {
    /*
       Code to paste and run in the Browser Console
       Requires devtools.chrome.enabled => true in about:config
       Tested in Firefox 68.0.1 on Windows
    */

    // Create references to APIs we'll use
    var ss = Cc["@mozilla.org/content/style-sheet-service;1"].getService(Ci.nsIStyleSheetService);
    var io = Cc["@mozilla.org/network/io-service;1"].getService(Ci.nsIIOService);
    var ds = Cc["@mozilla.org/file/directory_service;1"].getService(Ci.nsIProperties);
      
    // Get the chrome directory in the current profile
    var chromepath = ds.get("UChrm", Ci.nsIFile);

    // Specific file: userChrome.css or userContent.css
    chromepath.append("userChrome.css");

    // Morph to a file URI
    var chromefile = io.newFileURI(chromepath);

    // Unregister the sheet
    if(ss.sheetRegistered(chromefile, ss.USER_SHEET)){
      ss.unregisterSheet(chromefile, ss.USER_SHEET);
    }

    // Reload the sheet
    ss.loadAndRegisterSheet(chromefile, ss.USER_SHEET);
}, 1000)

OC by @TheTwelveYearOld@lemmy.world

There weren't any straightforward guides when I looked this up, and I even had to ask myself. But I just needed to put so and so together, get some feedback here, and voila! Hopefully this can work for you too, and could edit userchrome.css in your favorite editor, and see the changes in Firefox immediately. I tested that it works with @import url("folder/file.css");, and nested imports too (if folder/file.css contained @import url("Another folder/file.css");.

1. Install fx-autoconfig (I haven't tested it with other Firefox JS loaders), following the whole install section: https://github.com/MrOtherGuy/fx-autoconfig?tab=readme-ov-file#install
2. In the chrome/JS/ folder, create <any file name>.uc.mjs (I named mine refresh.uc.mjs) and paste the script below (it's slightly modified from this snippet):
   • The part containing @onlyonce is needed so fx-autoconfig loads it just once, rather than spawn a new instance of the script every time a new firefox window is opened.
3. Clear startup cache: https://github.com/MrOtherGuy/fx-autoconfig?tab=readme-ov-file#deleting-startup-cache
4. You may need to toggle the script. You can go to Menu Bar > Tools > userScripts.

Script

// ==UserScript==
// @onlyonce
// ==/UserScript==

// Script from here:  https://gist.github.com/jscher2000/ad268422c3187dbcbc0d15216a3a8060?permalink_comment_id=3259657#gistcomment-3259657
setInterval(() => {
    /*
       Code to paste and run in the Browser Console
       Requires devtools.chrome.enabled => true in about:config
       Tested in Firefox 68.0.1 on Windows
    */

    // Create references to APIs we'll use
    var ss = Cc["@mozilla.org/content/style-sheet-service;1"].getService(Ci.nsIStyleSheetService);
    var io = Cc["@mozilla.org/network/io-service;1"].getService(Ci.nsIIOService);
    var ds = Cc["@mozilla.org/file/directory_service;1"].getService(Ci.nsIProperties);
      
    // Get the chrome directory in the current profile
    var chromepath = ds.get("UChrm", Ci.nsIFile);

    // Specific file: userChrome.css or userContent.css
    chromepath.append("userChrome.css");

    // Morph to a file URI
    var chromefile = io.newFileURI(chromepath);

    // Unregister the sheet
    if(ss.sheetRegistered(chromefile, ss.USER_SHEET)){
      ss.unregisterSheet(chromefile, ss.USER_SHEET);
    }

    // Reload the sheet
    ss.loadAndRegisterSheet(chromefile, ss.USER_SHEET);
}, 1000)

When I started working on AI at Mozilla two years ago, I was a Python developer with a background in web services and three months of machine learning experience from working on the Nuclia DB project. I was not someone who had trained models from scratch or built production ML infrastructure. Today, Firefox ships multiple AI features that run entirely on-device, and I helped build the infrastructure that makes that possible. This is a retrospective on what we accomplished and what I learned along the way.

Whenever you open Firefox, we want it to feel like it speaks your language and matches your style. This month, our mobile team is rolling out features inspired by community ideas, user requests and the small everyday moments that make browsing more delightful.

In 2025, we rolled out one update after another, all aimed at making your browsing better — with more flow, speed, choice, and control over your information and experience. Your window to the internet, whether on desktop, mobile, or across all your devices, has gotten an upgrade this year.

Last year, the Firefox team set out to test something fans requested: choosing a custom app icon. The experiment was simple. Offer a small set of options and see how people use them.

Almost a month after releasing version 145, Mozilla has launched Firefox 146, the latest update to its popular open-source web browser, now available for download.

The release brings notable platform updates. Linux users running Wayland now benefit from native fractional scaling support, improving visual clarity and rendering accuracy on high-DPI displays.

On macOS, Firefox enables a dedicated GPU process by default, isolating WebGPU, WebGL, and WebRender. This change prevents full-browser crashes from graphics faults, instead restarting the GPU process transparently to maintain session stability.

https://www.xuldev.org/misc/ucjs.php