21 Nov 2026
Planet Mozilla
Mozilla Addons Blog: Developer Spotlight: WebBrain
AI and user privacy aren't standard bedfellows. But WebBrain - a browser extension-based AI companion - was built privacy forward from the start. It runs entirely locally. WebBrain uses offline LLMs, so your browsing data stays on your device.
"When you ask a cloud provider anything," explains WebBrain developer Emre Sokullu, "it isn't end-to-end encrypted and the things you share can be very intimate and personal. That's bad… health data, financial, private life."
WebBrain is capable of performing complex automated tasks like eCommerce assignments.
WebBrain's offline LLMs are designed to work well on devices with at least 16 GB RAM or a GPU with 16 GB of VRAM. Nothing leaves your machine. If curious how WebBrain is built, Sokullu invites anyone to explore WebBrain's GitHub repo, which documents the extension's privacy features in detail.
So what does WebBrain do?
Conveniently, WebBrain lets you know what it's capable of doing on any given web page.
If you're reading a news article or browsing a page with a lot of information, WebBrain can provide a tidy summary; it can even analyze and contextualize images. On a video site, WebBrain might ask if you want to download the media. WebBrain can even be customized to perform complex automated page tasks like GitHub and social media interactions (e.g. auto re-tweeting).
WebBrain learns about you the more you use it, so it becomes even more capable over time. Let's say you fill out a lot of form pages. WebBrain will learn your preferred username, email address, etc. Again, all data remains exclusively on your device.
WebBrain offers an impressively robust free tier of usage. But if you already have paid AI accounts, WebBrain can integrate with those as well.
And though it may sound scary, Sokullu says his favorite WebBrain feature is something called Apocalypse Mode. "It's a neat feature I want people to try. It's an offline LLM chat with offline Wikipedia and medical sources. During emergencies like Covid, war, natural disaster, or internet outages."
Do you have an intriguing extension development story? Do tell! Maybe your story should appear on this blog. Contact us at amo-featured [at] mozilla [dot] org and let us know a bit about your extension development journey.
The post Developer Spotlight: WebBrain appeared first on Mozilla Add-ons Community Blog.
21 Nov 2026 2:07am GMT
20 Nov 2026
Planet Mozilla
Mozilla Addons Blog: Unveiling the All-New Firefox Add-on Developer Hub
Sixteen years ago, Mozilla launched the add-ons developer hub to be a one-stop shop for Firefox extension and theme creators. While it served our community well for a long time, we knew it was time for a modern upgrade. Today, we're thrilled to announce a completely reimagined Firefox add-ons developer hub, rolling out this December.
![]() |
![]() |
At the start of 2026, we surveyed over a hundred Firefox add-on developers to learn about your biggest pain points. Your feedback was crystal clear: you wanted faster reviews, clearer guidelines, deeper insights into submission workflows, and better overall communication from Mozilla.
We took that feedback to heart when building the new developer hub, putting transparency, clarity, and communication at its core. With every submission, you'll see exactly where your version stands in the review process, what step comes next, and actionable advice if policy issues arise. Best of all, we will be integrating all communications right into the dashboard - no more digging through email threads! (Don't worry, you'll still get the emails)
Beyond workflow enhancements, we've streamlined navigation, unified messaging, and even added native dark mode support.
The preview release supports everything needed to submit and manage extensions in your default locale. We're actively building out additional features over the coming weeks, and you can seamlessly switch back to the classic hub at any point if you need legacy functionality.
Invitations to the preview release are rolling out gradually. When your account is invited, you'll see a "Try the new Developer Hub" link in the top navigation menu in the Developer Hub. Give it a spin and let us know what you think via the feedback link.
Happy developing!
The post Unveiling the All-New Firefox Add-on Developer Hub appeared first on Mozilla Add-ons Community Blog.
20 Nov 2026 5:21pm GMT
The Mozilla Blog: Why there are still no non-WebKit browsers on iOS
Firefox on iPhone is growing fast across the world. This is especially true in the EU since 2024, when the EU Digital Markets Act (DMA) started requiring Apple to let people choose their default browser; millions have picked Firefox, and daily use on iOS has doubled. People want to choose the browser on their phone.
But there remains an important limitation to what is available on iPhones: Apple forces all browsers on iOS to be built on Apple's own browser engine.
This has meant that companies like Mozilla cannot easily bring the full range of Firefox features and functionality to iPhone users because many of these are built within our browser engine, Gecko. iPhones and iPads are unique in having this restriction. On all other major operating systems, including Apple's macOS, people can access the Gecko-powered version of Firefox.
As a result of the DMA, Apple began allowing alternative browser engines on iOS in the EU. It published a set of conditions that companies like Mozilla must comply with to bring their own browser engine. At the time we said Apple's rules made it "as painful as possible" for alternatives like Gecko. In the meantime, Japan also introduced new rules requiring alternative browser engines on iOS. Apple applied very similar conditions in Japan to those in the EU.
Nearly three years since Apple introduced these conditions in the EU and almost a year since Japan, not one developer has been able to launch a non-WebKit browser on iOS. The reason is simple: Apple's conditions remain unworkable. The real test of any rule is whether it delivers the change it was meant to achieve in practice. Compliance on paper alone falls short of that test.
Since the DMA came into effect we've been working behind the scenes to test and improve Apple's conditions so that we can bring Gecko to iOS users. Those efforts have so far largely failed.
One of the conditions requires us not to disclose non-public information related to the project, but here's an example of what we are up against: to use Gecko, we can't simply update the Firefox app people already use and love. We'd have to build a whole separate app, a second Firefox. Then we'd have to ask every Firefox user to download it, move their bookmarks, passwords and history across, and manually switch over, step by confusing step.
That's a lot to ask of people who already made their choice. A significant proportion of people would understandably give up, including many who picked Firefox from the EU's choice screen.
The conditions Apple imposes, including a level of user friction Apple would never accept for its own apps, mean that the open door feels more like a trap door.
Firefox users on iPhone chose an independent browser. They should get everything that comes with it, including Gecko, the last major browser engine not developed by a big tech company. We'll keep pushing for a real level playing field, not an opening that drops independent browsers through the floor.
The post Why there are still no non-WebKit browsers on iOS appeared first on The Mozilla Blog.
20 Nov 2026 2:03pm GMT
19 Nov 2026
Planet Mozilla
Firefox Tooling Announcements: Firefox MCP v0.11.0 released
New release of Firefox MCP. Available on npm at https://www.npmjs.com/package/@mozilla/firefox-mcp
Firefox DevTools MCP is now called Firefox MCP.
The npm package is now @mozilla/firefox-mcp, and the repository is now GitHub - mozilla/firefox-mcp: Model Context Protocol (MCP) server that lets AI agents browse the web and debug web pages with Firefox · GitHub. Existing setups keep working: the same build is still published as @mozilla/firefox-devtools-mcp.
External contributors authored half of the PRs released today, huge thanks to:
Added
- Snapshots now include elements inside open shadow roots, so elements of web components get a UID
- Clicks, fills, key presses and
evaluate_scriptnow work on UIDs inside same-origin iframes - Snapshots show the label, type and checked state of form controls. Password values are never included
fill_by_uidon a select picks options by value or visible text, and supports multiple selects. An unknown or disabled option is an error that lists the available optionslist_extensionsis now available in the public package. It uses WebDriver BiDi and no longer needsMOZ_REMOTE_ALLOW_SYSTEM_ACCESS=1
Fixed
fill_by_uidnow replaces the value of fields that write their value back on focus, such as controlled React inputs, instead of appending to it- Dialogs (
alert,confirm,prompt) now stay open untilaccept_dialogordismiss_dialogis called.accept_dialogon a prompt uses its default value when no text is given
Changed
- The README and the Gemini extension now use
firefoxas the MCP server key, so new setups get tool names likemcp__firefox__navigate_page. Existing configs keep their own key - The Mozilla-internal package is now
@mozilla/firefox-mcp-moz - Local data moves from
~/.firefox-devtools-mcpto~/.firefox-mcpat startup - Tool calls now return as soon as a dialog opens, and other tools are refused while a dialog is open, with an error that points to
accept_dialoganddismiss_dialog - The dialog tools now use WebDriver BiDi instead of WebDriver Classic
Full changelog: Release v0.11.0 · mozilla/firefox-mcp · GitHub
Repository and issues: GitHub - mozilla/firefox-mcp: Model Context Protocol (MCP) server that lets AI agents browse the web and debug web pages with Firefox · GitHub
Public chatroom: https://chat.mozilla.org/#/room/#firefox-devtools-mcp:mozilla.org
1 post - 1 participant
19 Nov 2026 10:57am GMT
Firefox Tooling Announcements: Happy BMO Push Day! (20261118.1)
The following changes have been pushed to bugzilla.mozilla.org:
3 security fixes along with the following enhancements:
- Bug 2061445 - Migrate Bugzilla (system info) REST resource to native Mojo API
- Bug 2086124 - [HACKBOT] Structured metadata on comments
- Bug 2094200 - [MENTIONS] Make the banner bigger for needinfo mentions so it is more noticable
Discuss these changes in the BMO Matrix Room
1 post - 1 participant
19 Nov 2026 1:05am GMT
18 Nov 2026
Planet Mozilla
This Week In Rust: This Week in Rust 678
Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @thisweekinrust.bsky.social on Bluesky or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.
This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.
Want TWIR in your inbox? Subscribe here.
Updates from Rust Community
Official
Foundation
Newsletters
Project/Tooling Updates
Observations/Thoughts
- How Rust Changed Me As A Developer
- OpenCode Browse rewrote its browser tool in Rust: 97% less memory
- Mutex poisoning is not for everyone
- Rust in the Linux kernel: lines of code, unsafe and calls into C for every release since v6.1
- How to Bypass Rust's Orphan Rule
- Most Rust projects don't bundle CA roots
- Modern cryptography is fast, so you have no excuse for continuing to use C and Assembly
Rust Walkthroughs
- Foreign Function Interface (FFI) in Rust, Part 1: Unsafe Foundations
- sccache: Stop compiling the same Rust code again and again
- [series] Encoding TCP in Rust's Type System, Part 2: Placeholder Values Are Not Our Friends
- [series] 15 million web servers on one VM - smoltcp, DPDK, AF_XDP
- [video] Miscompilation in Rust 1.97 with Yoni Peleg
Research
Crate of the Week
This week's crate is xdgen, a crate for translation of AppStream metainfo files via fluent.
Thanks to Sosthène Guédon for the suggestion!
Please submit your suggestions and votes for next week!
Calls for Testing
An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization.
If you are a feature implementer and would like your RFC to appear in this list, add a call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.
No calls for testing were issued this week by Rust, Cargo, Rustup or Rust language RFCs.
Let us know if you would like your feature to be tracked as a part of this list.
RFCs
Rust
Rustup
If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.
Call for Participation; projects and speakers
CFP - Projects
Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!
Some of these tasks may also have mentors available, visit the task page for more information.
- AppBridge - [easy] Add CLI subcommand
appbridge deltato inspect byte savings between two .appbridge bundles - AppBridge - [medium] Support real Ed25519 asymmetric keypair generation and verification for .appbridge bundles
- presswork - Hardware matrix: run the IPP conformance suite against real printers
- presswork - Expand ipptool conformance matrix to remaining upstream .test files
- rightcommit - Add a minimal Local CI workflow example
- rightcommit - Add a regression test for Local CI Makefile precedence
- Rustidian - Make the AppImage open its demo vault on first launch
If you are a Rust project owner and are looking for contributors, please submit tasks here or through a PR to TWiR or by reaching out on Bluesky or Mastodon!
CFP - Events
Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.
No Calls for papers or presentations were submitted this week.
If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a PR to TWiR or by reaching out on Bluesky or Mastodon!
Updates from the Rust Project
616 pull requests were merged in the last week
Compiler
- avoid hoisting uninitialized reads in EarlyOtherwiseBranch
- do not suggest
as_dereffor a slice pattern onErr - improve index inference diagnostics
- normalize the simd field type before reading its length
- reflection: reflect attributes from adts, fields, and variants
- some attribute related cleanups
- support nested functions with
#[offload_kernel] - use 2 parallel frontend threads by default on the nightly and dev channel
Library
- add
allocator()tovec_deque::IntoIterandvec_deque::Drain - alloc: unstably add
Vec::repeatandVec::repeat_in - don't overflow when rounding up huge thread stack sizes on unix
- implement
core::ops::FnAddr - stabilize
int_from_ascii
Cargo
config: Add a generated schema fileconfig: Iterate on config.toml's schematrim-paths: sanitize absolute source paths in fingerprint- add support for
annotate-snippets'sno-graphicsoutput format - compile: switch dev profile to debug=lines-and-tables-only
- reworked output mtime tracking
- test: add unordered to
pub_priv::verify_mix_cargo_feature_z - unified invoked.timestamp location for compilation and build script units
Rustdoc
- prevent inlining of foreign items through glob reexports named
_ - correctly filter deref impls on type aliases
Rustfmt
- consistently use "Diff Check" throughout
- don't split link destinations when
wrap_commentsis enabled - fix idempotency issue with raw strings
- don't leave trailing whitespace before a skipped impl item
Clippy
missing_errors_doc: exempt never-like error types- extend
assert_is_emptyto coverVecDeque - fix
single_match/single_match_elsesuggestion lose semicolon - fix incorrect suggestions from
unnecessary_literal_unwrap
Rust-Analyzer
.foradd ref when only ref impls into-iter- complete
fn unsafeafterconst - do not complete types when trait in type anchor
- large u128 values should not const eval to negative floats
- replace
builtin #with forced keywords
Rust Compiler Performance Triage
A generally positive week, with improvements significantly outweighing regressions for an average of -1.1% instructions on primary benchmarks.
Triage done by @simulacrum. Revision range: 54d0b7ed..6ca2b346
5 Regressions, 12 Improvements, 4 Mixed; 0 of them in rollups 147 artifact comparisons made in total
Approved RFCs
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
Final Comment Period
Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.
Tracking Issues & PRs
- debugger: stabilize trim-paths unremap file loading
- Stabilization of the
documentationscope inrustc - Stabilize
char::is_case_ignorable,char::is_cased, and thetitlecasefeature - std: use
_exitforprocess::exit - Add lint against duplicate parameter names in fns without body
- Stabilize unchecked
nonzero_ops - Update
PartialEq/PartialOrdguarantees for comparisons to match reality - Move lint validation to attribute parsing
- parser: Feature-gate ambiguous attributes on expressions (take 2)
- make conflicting_repr_hints a hard error
- Make unsafe unknown diagnostic attributes an error again
No Items entered Final Comment Period this week for Rust RFCs, Cargo, Language Team, Leadership Council or Unsafe Code Guidelines. Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
New and Updated RFCs
Upcoming Events
Rusty Events between 2026-11-18 - 2026-12-16 🦀
Virtual
- 2026-11-18 | Hybrid (Vancouver, CA) | Vancouver Rust
- 2026-11-19 | Virtual (Berlin, DE) | Rust Berlin
- 2026-11-22 | Virtual (Bengaluru, India) | Embedded Rust Discord
- 2026-11-24 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup
- 2026-11-26 | Virtual | betterCode() Rust
- 2026-11-28 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup
- 2026-12-01 | Virtual | Rust 🦀 Maven
- 2026-12-01 | Virtual | ERNI
- 2026-12-01 | Virtual (London, UK) | Women in Rust
- 2026-12-02 | Virtual (Indianapolis, IN, US) | Indy Rust
- 2026-12-03 | Virtual (Berlin, DE) | Rust Berlin
- 2026-12-04 | Hybrid (Moscow, RU) | RustCon RU
- 2026-12-05 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup
- 2026-12-06 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup
- 2026-12-08 | Virtual (Dallas, TX, US) | Dallas Rust User Meetup
- 2026-12-08 | Virtual (London, UK) | Women in Rust
- 2026-12-12 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup
- 2026-12-15 | Virtual (Washington, DC, US) | Rust DC
- 2026-12-16 | Hybrid (Vancouver, CA) | Vancouver Rust
Asia
- 2026-12-12 | Bangalore, IN | Rust Bangalore
Europe
- 2026-11-19 | Aarhus, DK | Rust Aarhus
- 2026-11-19 | Bergen, NO | Rust Bergen
- 2026-11-20 - 2026-11-21 | Augsburg, DE | Rust Meetup Augsburg
- 2026-11-24 | Basel, CH | Rust Basel
- 2026-11-25 | Amsterdam, NL | Rust Developers Amsterdam Group
- 2026-11-25 | Dortmund, DE | Rust Dortmund
- 2026-11-26 | Copenhagen, DK | Copenhagen Rust Community
- 2026-11-26 | London, UK | Rust London User Group
- 2026-11-26 | Manchester, UK | Rust Manchester
- 2026-11-26 | Stockholm, SE | Stockholm Rust
- 2026-11-28 | Stockholm, SE | Stockholm Rust
- 2026-12-01 | Paris, FR | Rust Paris
- 2026-12-02 | Frankfurt, DE | Rust Rhein-Main
- 2026-12-04 | Hybrid (Moscow, RU) | RustCon RU
North America
- 2026-11-18 | Hybrid (Vancouver, CA) | Vancouver Rust
- 2026-11-18 | San Francisco, CA, US | Bay Area Rust
- 2026-11-21 | Boston, MA, US | Boston Rust Meetup
- 2026-11-21 | Minneapolis, MN, US | Minneapolis Rust Meetup
- 2026-11-28 | Boston, MA, US | Boston Rust Meetup
- 2026-12-03 | Montréal, CA | Rust Montréal
- 2026-12-04 | New York, NY, US | Rust NYC
- 2026-12-04 | New York, NY, US | Women in Rust
- 2026-12-15 | San Francisco, CA, US | San Francisco Rust Study Group
- 2026-12-16 | Hybrid (Vancouver, CA) | Vancouver Rust
Oceania
- 2026-11-24 | Barton, AU | Canberra Rust User Group
If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.
Jobs
Please see the latest Who's Hiring thread on r/rust
Quote of the Week
Presenter: One of the obvious dangers of AI, it may one day rewrite all code in some cryptic programming language no human is capable of understanding, just because AI understands it much better and finds so efficient to work with ...
Voice from the hall: "Do you mean Rust?"
- Unknown people overheard during a meeting
Thanks to Bourumir for the suggestion!
Please submit quotes and vote for next week!
This Week in Rust is edited by:
- nellshamrell
- llogiq
- ericseppanen
- extrawurst
- U007D
- mariannegoldin
- bdillo
- opeolluwa
- bnchi
- KannanPalani57
- tzilist
- alex-semenyuk
Email list hosting is sponsored by The Rust Foundation
18 Nov 2026 5:00am GMT
Mozilla Performance Blog: Making Firefox on Android Faster When Opening Links from Other Apps
Firefox on Android now opens links from other apps about 20% faster than it did in January. On a typical mid-range phone, that's close to half a second back every time you tap a link in a chat, an email or a social app.
How you'll feel the difference
You are in a group chat, somebody drops a link and you tap it - and then you wait. Not long, but long enough to notice, and long enough to think about it. Firefox is opening, but the thing you actually tapped isn't there yet. You just wanted to see what your friend had sent you.
We call that moment an app link launch: a link tapped in some other app, handed to Firefox, which then has to wake up, start all of its background processes, and put a page in front of you. No single piece of work controls this delay. Firefox has to start the app, load the user's settings, prepare browser features, and request the page, often at the same time. Our goal is to get the startup out of the way quickly.

Time you get back
Firefox now finishes an app link launch about 20% faster than it did in January. Exactly how much faster depends on which phone you have and which site you're opening, but in real time it works out to somewhere between a fifth of a second and half a second. We measure this in our test lab on a set of reference Android phones, so your own numbers may be different, but you'll still notice a difference.
Take the Samsung A55, our mid-range reference phone. Opening a news site on it went from about 2,054 ms in January to 1,597 ms in October.

Here's how we did it:
| What Was Happening | What Firefox Does Now |
|---|---|
| Your extensions all woke up while your page was still loading, so the two competed for a phone that only has so much to give | Unless an extension is needed for that first page, it waits until your page is on screen |
| The network sat idle for hundreds of milliseconds while Firefox got itself ready, even though Android had already told us where you were navigating to | Firefox now starts connecting to the site the moment Android hands it the link, before the rest of the browser has even finished starting, which saves about 400 ms on slow networks and about 115 ms on fast Wi-Fi |
| Firefox's animated splash screen kept systemui busy repainting during startup, making the CPU do extra startup work | The Firefox splash screen now uses static screen instead of an animation, and cold-start first frame improved by 10% |
Those are just the top line, most impactful changes that you'll immediately notice. We also discovered some bugs that just needed to be fixed. The following things no longer happen at startup, or have had their impact reduced: background and location service calls, cookie and saved login lookups, crash reporter starting multiple times, emoji-compatibility background tasks, duplicate "are you online" checks, as well as language and region sorting.
Startup performance is hardly ever one expensive thing - it is many cheap things that all insist on happening before the part you care about.
Also shipped: a clearer prompt when a link leaves Firefox
This one runs in the opposite direction from everything above, and it isn't a speed fix, but it's part of the same moment of handing a link between apps. When a link you tap in Firefox wants to open in a different app, Firefox asks you first. That prompt has been redesigned for people who have never heard the phrase "app link" and should not have to, and after a stretch of testing it became the default for everyone in August. Along the way it also got fixes for two crashes, one of them triggered by very long links, and for a security issue.

Where that leaves us
Faster than January by a comfortable margin, on every phone we measure and every site where we have solid data, with better measurement than we started the year with and automatic alerts in place to catch it if things slip.
One last thing worth shouting out: fifteen different people landed a piece of this, across performance, networking, cookies, crash reporting, telemetry, graphics, Android UI and test infrastructure. That just goes to show that startup time does not belong to any one team, and neither does improving it.
Still slow for you?
Then we want to hear about it. We are continuing to make startup faster; your voice helps us prioritize.
18 Nov 2026 4:13am GMT
17 Nov 2026
Planet Mozilla
Thunderbird Blog: Thundermail Q4 2026 recap: new features, your feedback, and what’s next

It has been quite a year. When we started welcoming our first Early Birds into Thundermail, we had a waitlist, a vision, and a lot of work ahead of us. Since then, thousands of you have joined, tested, filed ideas, and helped us shape what this service is becoming. The upcoming new year is a great chance to look back at everything we've built together and what we have coming up in 2027.
(If you're interested in being a Thundermail Early Bird, sign up to the waitlist to get your invitation.)
What we've built so far
Webmail
Webmail was the single most-requested feature from our early users, and in July, we delivered the initial alpha version of it.
Since then, a lot has taken shape. The compose window has seen the biggest changes with address auto-complete, CC and BCC, attachments, and scheduled send. Your inbox now lets you star messages, search and hide non-matching results, minimize drafts so you don't lose work mid-session, and use updated keyboard shortcuts if you're a power user. Contacts have moved into the left sidebar, with support for multiple address books, a contacts trash folder, and easy alias switching. You can now also manage your identities directly in the Contacts space, so you can compose and reply from the right address every time.
There are still some rough edges, but development is active and completely open in the Stormbox repository on GitHub. If you have ideas for what comes next, visit our ideas board to upvote, comment, or share something new.
Custom domains
Custom domain support is one of the most celebrated features among early users. Every mailbox now includes 15 aliases from the @thundermail.com or @tb.pro domains, and you can bring up to three domains of your own on top of that. For custom domains, you can create unlimited aliases and set up a catch-all, so any email sent to any address at your domain lands in your inbox automatically. You can even send from those addresses on the fly, without setting each one up individually.
Multi-factor authentication
Multi-factor authentication (MFA) adds an extra layer of security by requiring more than a password to sign in. You can set up an authenticator app directly from your account dashboard, and we recommend adding recovery codes as a backup so you don't get locked out.
Send and Appointment
Both features are part of your Thundermail subscription and are here to stay. Send offers end-to-end encrypted file sharing, perfect for large attachments, and Appointment gives you a simple way to let others book time with you.
What we've heard from you
Every survey response, support ticket, and ideas board entry gets read by our team. We celebrate the wins with you, and take the constructive feedback just as seriously. All of it tells us something important about where Thundermail needs to go, and we're grateful for all of it.
What you're asking for:
- A full calendar experience in webmail is one of the most requested additions. Right now Thundermail supports calendars via CalDAV, but there's no calendar interface in webmail yet. Users want to manage events, view their schedule, and get notifications without leaving the browser.
- Many of you want the ability to have separate inboxes per custom domain, rather than everything routing into one. This is one of the most upvoted ideas on the board and something we're actively thinking about.
- More flexible pricing is one of the most requested changes. Not everyone needs the same plan, and we're hearing that clearly from users who want monthly billing, to those who need more storage or aliases, to families who want to share a subscription. We're actively exploring what additional tiers could look like, with the goal of having options ready as the first annual memberships come up for renewal.
- Many of you are in the process of migrating to Thundermail from another provider and want to bring your email, calendar, and contacts history with you. We know migrating is a big ask, and we want to make it easier. This is on the roadmap.
What's working:
- Many of you have said that having a privacy-first, open source email service to move to is what matters most. "Glad to have somewhere to go that isn't Gmail" captures a lot of what we're hearing. That's why we built this.
- Custom domains continue to be a highlight. One user called it "frankly, amazing! That alone is worth the price." Several of you have compared it favorably to competitors charging significantly more for the same number of domains.
- Setting up Thundermail in Thunderbird is landing well. "The ease of setup with Thunderbird is fantastic" and "the fast sign-in was a great touch" are showing up in both the 3-day and 13-day surveys.
- Even users flagging friction are rooting for the product. "I knew what I was in for," "I fully believe the team will get this where it needs to be." This trust means a lot and we don't take it lightly.
A note on support:
One of the things that has come through clearly in the feedback is how much our support team has meant to early users. Response times, technical depth, and the feeling of being genuinely heard have all been called out specifically. One response put it this way:
"Your support team is FIRE. They reply within 24 hours, they are technical, efficient, polite, and not a single response is canned. I had been toying with seeking a refund, but my positive support experiences changed my mind. It's EXACTLY that kind of thing that will keep me on Thundermail for the next 25 years."
We're sharing this because the team deserves to be celebrated for their hard work and dedication, and because maintaining that standard as Thundermail grows is something we're committed to.
What's coming next
You've told us what matters most, and we're building accordingly. Here's what's currently in flight.
- Server-side email filtering is one of the most-requested features from power users, and a stated blocker for several of you switching from Gmail or Fastmail. We're targeting a v1 of the visual mail rules editor in December.
- Calendar in webmail is on its way. We're building a full calendar view directly into the webmail interface, so you'll be able to manage your schedule, create and edit events, and set notifications without ever leaving your inbox. We're targeting Q1 2027 for this one.
A final note
To everyone in the Thunderbird community who has followed along, shared the word, and supported this project, it means more to us than we can say. And a special thanks to our Early Birds, your valuable feedback is shaping every decision we make. We'd encourage you to visit the ideas board to share what you'd like to see next.
And if you're still on the waitlist, more invites are on the way and we are looking forward to welcoming you onboard!
The post Thundermail Q4 2026 recap: new features, your feedback, and what's next appeared first on The Thunderbird Blog.
17 Nov 2026 8:23pm GMT
The Mozilla Blog: Has Microsoft wronged you? Firefox opens a complaints line at Microsoft Ignite
This week, Firefox is taking over the streets around the Moscone Center in San Francisco, where Microsoft is holding Ignite, its biggest conference of the year.
While they talk about what's next for Windows, Firefox is taking over the surrounding streets to remind them of what they haven't fixed: Microsoft hasn't changed the concerning design practices that undermine their users' choices, including keeping people's chosen default browser.
We are running an ad campaign that is styled like personal-injury lawyer ads. All we ask is that you call us and tell us what you think of Microsoft's tactics to undermine browser choice.
The hotline is real. Call 1-855-25-FIREFOX and you can leave a message where you can make your point. We want to ensure that Microsoft understands a real problem they are creating. We are doing this publicly because we previously shared and discussed research proving this problem with Microsoft and have yet to see meaningful action.
In July, Mozilla released Over The Edge 2.0, the second independent report from deceptive design experts Dr. Harry Brignull and Cennydd Bowles on how Windows, Edge, Bing, and Copilot are designed to lead people away from the browser they chose. The researchers have published their proof so anyone can check it. A hundred days later, we discovered that for people outside the European Economic Area, almost nothing has changed:
- Windows Search and Widgets open links in Edge instead of the default browser.
- Even if you set another browser as the default, Windows will still keep Edge as the default for common file types like PDF.
- Windows Backup attempts to silently make Edge the default when restoring a PC.
- Copilot opens web links in Edge in all regions tested, including Europe.
The point is, there *is* a fairer version of Windows out there. Microsoft built it for Europe, where the Digital Markets Act demanded it. Same Windows, same Edge, different design choices. Everywhere else, including the US, UK, and India, they get the version that can override their choice.
We showed the report to Microsoft and discussed it with them before any of this was released to the public. We've asked for two things: one, to give every Windows user the fairer designs that already live in Europe; and two, to stop the remaining practices, like Copilot, that persist everywhere. None have been shipped.
So we took the complaint to Microsoft's own conference. Ignite is where Microsoft discusses what's next for Windows. And we thought it was a good place to ask if respect for people's choice in the browser is part of that future.
If this has happened to you, call the number below.
Microsoft can do better. And it has, for the people in Europe. Until it does so everywhere, keep calling 1-855-25-FIREFOX and let your voice be heard.
The post Has Microsoft wronged you? Firefox opens a complaints line at Microsoft Ignite appeared first on The Mozilla Blog.
17 Nov 2026 1:59pm GMT
Firefox Tooling Announcements: Firefox Profiler Deployment (November 17, 2026)
The latest version of the Firefox Profiler is now live! Check out the full changelog below to see what's changed:
Highlights:
- [mstange] Add a basic function list panel (#6403)
- [minwookshin] Add Ctrl/Cmd+A to select all visible timeline tracks (#6371)
- [fatadel] Move timeline marker styles into marker schemas (#6293)
Other Changes:
- [GBra-4-669] Invalidate the hovered sample when the thread changes (#6374)
- [mstange] Fix tar parser correctness issues (#6430)
- [mstange] Give flame graph siblings with the same function name a defined order (#6419)
- [canova] Point bootstrapped profiler-cli users at mach bootstrap for new profies that the CLI can't parse (#6443)
- [canova] [Deploy preview] Skip pseudo-libraries like [vdso] during symbolication (#6099)
- [canova] Keep the source code cache tied to the profile it was filled for (#6410)
- [canova] Read Chrome screenshot sizes without the DOM Image API (#6455)
- [fatadel] Show the selected marker of a loaded URL in profiler-cli status (#6448)
- [fatadel] Bump profiler-cli version to 0.14.0 (#6466)
Big thanks to our amazing localizers for making this release possible:
de: Ger, Michael Köhler
en-GB: Ian Neal
fr: JOSIAS, Théo Chevalier, WilliamMrc, YD
fy-NL, nl: Fjoerfoks
ia: Melo46
it: Francesco Lodolo
ru: Valery Ledovskoy
sv-SE: Andreas Pettersson, Luna Jernberg
zh-TW: Pin-guang Chen
Find out more about the Firefox Profiler on profiler.firefox.com! If you have any questions, join the discussion on our Matrix channel!
1 post - 1 participant
17 Nov 2026 1:24pm GMT
16 Nov 2026
Planet Mozilla
Firefox Tooling Announcements: MozPhab 2.26.0 Released
Bugs resolved in Moz-Phab 2.26.0:
- bug 2045153 Add a --format-patch arg to moz-phab
- bug 2077608
moz-phab reorgoffers to abandon revisions that have already landed - bug 2086809 moz-phab silently truncates stacks of more than 100 revisions
- bug 2092092 Add a warning to moz-phab for non-staff submitting patches for bugs they're not assigned to
Discuss these changes in #engineering-workflow on Slack or #Conduit Matrix.
1 post - 1 participant
16 Nov 2026 11:14pm GMT
The Rust Programming Language Blog: Enabling the parallel frontend on nightly
TL;DR: We are enabling the parallel frontend of the Rust compiler on nightly by default, to find remaining issues in preparation for its stabilization.
Context
The Rust compiler has been using multiple threads to compile code in its "backend" part (using LLVM) for a long time. However, its "frontend" part (which includes type checking and borrow checking) has been executing sequentially, on a single thread, which of course limits the performance of the compiler. If you are interested in a more in-depth explanation of parallelism in the Rust compiler, see this previous post.
The compiler frontend actually had support for running in parallel for a long time, but it was not enabled by default due to various issues. Three years ago, we made it possible to opt into the parallel frontend on the nightly channel, with the plan to stabilize it in 2024. Clearly, we did not achieve that goal, but work on the parallel frontend was still slowly progressing in the meantime.
Last year, Vadim Petrochenkov, together with several other contributors, started a coordinated effort to finally get the parallel frontend over the finish line. Since then, many long-standing issues were fixed, and its performance was improved. Now we are at a point where we would like to make it widely available. But before that, we want to find out if people encounter issues with it in the wild, which is why we are enabling it by default only on the nightly channel. Once we will be confident enough that it is working well, we want to stabilize it.
The parallel frontend has been enabled on the nightly channel by default since nightly-2026-11-14.
Benefits
The primary benefit of enabling the parallel frontend is, of course, faster compilation of Rust programs.
We benchmarked the parallel frontend in our benchmark suite, which measures the duration to compile the leaf crate in a crate graph. As usual, the results were varied. In some benchmarks, the parallel frontend barely helped. In others, for example when performing a cargo check of the nalgebra, cargo or diesel crates, the compilation was almost three times faster, using 8 threads.
In the table below, you can find the aggregated wall-time mean change for the real-world benchmarks in our suite, when building a single crate from scratch across several configurations, compared to the same build using a sequential frontend.
| Frontend threads / Profile | check |
clippy |
debug |
opt |
|---|---|---|---|---|
| 2 | -21.95 % | -20.74 % | -14.2 % | -12.51 % |
| 4 | -37.99 % | -36.01 % | -29.14 % | -23.67 % |
| 8 | -44.23 % | -41.76 % | -36.1 % | -27.88 % |
It is clear that the parallelization is not perfect, and we definitely plan to invest more effort into improving its performance. Nevertheless, with 8 threads, it can make the end-to-end compilation time of cargo check ~2x faster for several crates that we tested, which is still quite an improvement.
The performance benefits for incremental rebuilds are much more modest, and also very hard to compare, because the performance of rebuilds depends on what was changed and how were the codegen units laid out. In our benchmark suite, we saw a mean improvement of 3-5% for incremental rebuilds. But we currently do not have great benchmarks for this use-case, so your results might vary.
We can also zoom in on an individual crate. Here is a chart of how the wall-time scales when compiling the nalgebra 0.33 crate, for a full non-incremental build (full), full incremental build (incr-full) and an incremental rebuild (incr-patched) across several build configurations:

What is interesting to note is that enabling the parallel frontend can actually also make the backend faster, for reasons explained here.
It is important to note that all benchmark results presented above measured only the compilation of a single crate. When compiling a whole crate graph, your CPU cores might already be saturated because of backend (LLVM) parallelism or by Cargo compiling multiple crates in parallel. So the final performance effect will vary heavily based on the workload that you are running, and on the number of cores that you have available.
We also benchmarked cargo check end-to-end (checking the whole crate graph) on the cargo crate itself on a machine with 8 CPU cores. With 8 threads, it resulted in a ~15% end-to-end improvement:
- 36.7s with 1 frontend thread
- 35.1s with 2 frontend threads
- 31.9s with 4 frontend threads
- 30.8s with 8 frontend threads
As can be seen from the results above, when the CPU cores are already saturated with parallel crate compilation and LLVM, the positive effect of the parallel frontend is reduced.
Tuning the thread count
At the start, the nightly toolchain will default to the parallel frontend using only 2 threads. This is a conservative choice that should still allow us to find potential issues while not increasing memory usage a lot at the same time.
If you want to test out the performance with different thread counts, you can override the number of threads used for the frontend using the --jobs-frontend compiler flag. It can be specified either in the RUSTFLAGS environment variable, or you can put it into a .cargo/config.toml file:
[build]
rustflags = ["-Zunstable-options", "--jobs-frontend=8"]
Currently, the performance of the parallel frontend will likely not scale very well above ~8 threads, but you can try it on your workload to test what happens. Note that using higher thread counts will likely lead to higher memory usage of the compiler, and in extreme cases it might cause you to run out of memory.
Limitations and known issues
Due to the used parallelism, the produced order of diagnostics might not be deterministic when using the parallel frontend.
In some situations, the generated binary might also not be reproducible, though we currently consider these cases bugs, and we would like to identify them and fix them.
There are currently some known issues related to the reproducibility of the Rust compiler when using the parallel frontend, which are being worked on.
How do I opt out?
To reiterate: this is only being enabled on nightly for now. If you are using the stable toolchain, you will still be using the sequential frontend by default.
If you want to disable the parallel frontend on the nightly channel, pass -Zunstable-options --jobs-frontend=1 to rustc, either via the RUSTFLAGS environment variable, or with the .cargo/config.toml configuration file:
[build]
rustflags = ["-Zunstable-options", "--jobs-frontend=1"]
If you have to do this for some reason, please do tell us why on GitHub or on Zulip. We would especially like to know about any compiler crashes that you encounter, or the produced binaries not being reproducible when the parallel frontend is enabled.
What's next?
Over the next few months, we will be monitoring GitHub and Zulip for any reported issues about the parallel frontend. Once we have enough confidence that it is working well, and there are no major issues, we would like to move forward and finally stabilize it.
We would also like to improve its performance, and make more things parallel. So far, a lot of the work on the parallel frontend has been focused on making it work correctly, rather than tuning its performance down to the last percent. We thus expect that we might still be able to make further performance improvements to it.
We would also like to make more parts of the frontend actually parallel, as some parts are currently still sequential even if parallelism is enabled. There is some ongoing work on this. Last year, we had a Google Summer of Code project focused on enabling parallel macro expansion and name resolution, and there is also an open pull request for parallelizing the lowering of the Abstract Syntax Tree (AST) to the High-Level Intermediate Representation (HIR). More work remains to be done on this front.
16 Nov 2026 12:00am GMT
12 Nov 2026
Planet Mozilla
Firefox Tooling Announcements: MozPhab 2.25.0 Released
Bugs resolved in Moz-Phab 2.25.0:
- bug 2086084 Submitting part of a stack with git adds double blank lines after the commit subject of the remaining commits
- bug 2088204 Uncommitted changes detected on clean checkout
- bug 2088229 Parse Conduit search results into frozen data models
- bug 2088739 Use enums and a frozen
Transactionfor the fixed values moz-phab compares and sends - bug 2089259 Split patch into resolving, planning and applying steps
- bug 2090820
moz-phab upliftshould be able to post a merge conflict as the first diff of the revision it resolves
Discuss these changes in #engineering-workflow on Slack or #Conduit Matrix.
1 post - 1 participant
12 Nov 2026 11:49pm GMT
Firefox Tooling Announcements: Happy BMO Push Day! (20261112.1)
The following changes have been pushed to bugzilla.mozilla.org:
- Bug 2088705 - Record the acting user in flag_activity.who, as a nullable column (first step of bug 2085398)
- Bug 2090094 - Release Management setting a Phab uplift to "abandoned" does not set the corresponding tracking flag to
- - Bug 2090252 - 2_test_login_totp.t reads the page before the TOTP enrollment and verification API calls return
- Bug 2087012 - [mentions] @username mentioniing during when bug is created does not needinfo the person but it should
- Bug 2085072 - Set a cookie when hiding or showing external attachments and use the cookie for all future bug pages save preference
- Bug 2088987 - Bug shouldn't be closed when github commit and backout arrive on the same message
- Bug 2089049 - REST /bug/2048343/history fails with internal error: Can't call method "iso8601" on an undefined value at Bugzilla/API/V1/Util.pm line 362
- Bug 2089200 - Enforce unique nicknames with a UNIQUE index on profiles.nickname
- Bug 2085141 - [mentions] Make it more obvious when @mention is going to needinfo someone
- Bug 2085052 - [mentions] For @mentions in comments, allow the autocompletion when typing @ like github does
- Bug 2091217 - Avoid stale-element failure in bug-edit Selenium test
- Bug 2091218 - Wait for product details in the Selenium test
- Bug 2091196 - fetch_product_versions is not cached for the request: buglist.cgi makes 42 memcached lookups, and a new HTTP request on every call when the product-details endpoint fails
- Bug 2091444 - TrackingFlags bug_check_can_change_field runs a database query for every custom field on show_bug.cgi, including fields that aren't tracking flags
- Bug 2091129 - Bugzilla::DB pings MySQL before every query (about 200 pings per show_bug.cgi request)
- Bug 2091167 - SizeLimit plugin parses all of /proc/self/smaps in pure Perl after every request (~3 ms per request)
Discuss these changes in the BMO Matrix Room
1 post - 1 participant
12 Nov 2026 11:25pm GMT
Firefox Tooling Announcements: Nov 12th Deploy
The latest version of PerfCompare is now live!
New view alert! 
The cross-platform view in PerfCompare!
How it started: Matthew Gaudet sought to answer one question that keeps coming up for engineers looking at a performance change: "Do these improvements or regressions agree across platforms?" Until now, answering that meant opening each platform's results one at a time and comparing them by hand. He saw that gap and filed Bug 2069050 asking for an official cross platform view in PerfCompare.
What we have now and how it works: The new cross-platform subtests view is live now! It shows each subtest as a row and each platform as a column. An Agreement column sums up the result at a glance, like "3/3 improved", "2/3 regressed" or "Mixed". Regressions are sorted to the top by default, and you can sort and filter by agreement. You can also click any cell to go to that platform's detailed results. You get there from the new "Compare across platforms" link in a test's header, which appears whenever two or more platforms have subtest data.
Please feel free to leave feedback or file bugs through the links below.
Check out the change-log below to see the updates:
Highlights:
[kala-moz]:
-
Bug 2068298 Simple View: match the advanced options selections for both results and subtests page
-
Bug 2067300 Simple view: Persist advanced options in cookies (with URL taking precedence)
-
Bug 2075051 Magnitude filter "Medium" option matches no rows; rows show "Moderate" instead
-
Add a fake Treeherder backend for ?fakedata
[moijes]: Bug-2003889: Show Lando try-push status instead of a blank-revision error
Other changes:
[kala-moz]:
-
Bug 2069050 - prepare code for cross-platform subtests view (#1134)
-
Bug 2082629 Remove unused and phantom fields from Mann-Whitney U types (#1130)
Thank you for the contributions!
Bugs or feature requests can be filed on Bugzilla. The team can also be found on the #perfcompare channel on Matrix. Come and chat!
1 post - 1 participant
12 Nov 2026 7:28pm GMT
The Mozilla Blog: An open letter to every family’s designated IT support
Almost every family has one. They're the only ones who know which remote turns on the TV and which controls the volume and channels. They know what an HDMI cable actually does and where to plug it in. They've even fixed multiple phone issues within seconds through a little-known, well-kept secret procedure (turning it off and back on).
Perhaps they are a parent, tech-savvy sibling, cool aunt or uncle, or close family friend. Whatever the relation, the role stays the same. They are the unpaid, on-call tech specialist for every relative's forgotten password, printer jam, and device settings update.
If this sounds like you, we would first like to thank you for doing a job you never signed up for. Second, we would like to share a simple way you can help your family and friends protect their privacy and security without adding more to your plate.
A small settings change that makes a big difference
With Android and iPhone's latest releases, and Black Friday deals rapidly approaching, many people are upgrading their current phone to a newer model. As the family's go-to tech helper, you'll likely be setting up a few new devices in the near future. You already know the routine: connect to Wi-Fi, choose a language, and transfer data from the old phone to the new one. But beyond the steps you are prompted to take when setting up a new phone lies a quiet decision many people never think twice about: their default browser.
While people in some regions, like Europe and Japan, get to choose their default browser when setting up a new phone, this is not the case everywhere. Most phones ship with a browser preinstalled and set as the default, ready to start collecting data and monetizing off user activity the minute it's opened. Unless deliberately changed, that's the browser that will be used moving forward. Not because it's the best option, but because it's already there.
But remember, everyone can choose the browser they use, and as the designated tech whiz of the family, you can help inspire others to choose the right one.
Choosing Firefox means choosing privacy from the very first tap.
The browser is where the data lives
A browser is the door to everything you do online, and depending on how it's designed, it can see a lot. Every site visited. Every phrase searched. Every link tapped. As we socialize, work, and explore on our phones, the browser can be the biggest funnel of personal data leaving that device, and how it's built determines who collects that data, who can sell it, and how long it sticks around.
Privacy is the starting point for our browser, not an afterthought. Firefox is built on the principle that not even Mozilla should know which websites you visit or what you do there.
Why Firefox is the right call
Firefox is backed by Mozilla, a nonprofit-backed company with no shareholders to report to. Instead of chasing financial returns for a small group, Mozilla aims to provide an internet that truly puts people first. This means we limit the data we know about you and give you more choice about what data you share and when.
This commitment to user privacy is built into the browser itself. On both Android and iOS, Enhanced Tracking Protection (ETP) is enabled by default, blocking known trackers every time you browse. This helps prevent advertisers and data brokers from following people across sites, no setup required. You can also adjust ETP to fit different needs, including turning it off altogether or activating Strict mode for even stronger protection.
Control and choice are built in, too. Firefox has an easily accessible AI controls section where people can customize how AI features show up in the browser, or turn them off entirely - because AI should always be a choice, not a requirement.
To carry these principles and protections across every link opened on a new phone, set Firefox as the default mobile browser in just a few taps.
How to set Firefox as the default browser on Android and iOS
Downloading the Firefox mobile app isn't enough on its own, since most phones will keep opening links in whatever browser came preinstalled unless told otherwise. Here's how to make Firefox the browser that actually opens by default. Make sure Firefox is installed on the device you're working with before you begin.
On Android:
- Open Firefox
- Tap the three-dot menu button.
- Tap Settings.
- In the General section, locate the Set default browser option.
- Tap the toggle next to Set as default browser to turn it on.
- Select Firefox from the listed options.
- Tap Set as default.
On iOS:
- Open phone Settings.
- Tap Apps.
- Tap Default Apps.
- Tap Browser App.
- Select Firefox from the listed options.
Once Firefox has been selected as the default browser, links tapped from messages, email, social media, or anywhere else will open in Firefox automatically. No additional steps required by your less tech-savvy family members and friends, and no relying on them to open the "right" browser every time they want to access the internet.
A little help on day one, lasting benefits later
The way a device is initially set up tends to stick. Whichever browser is already selected as default and whatever privacy settings are (or aren't) adjusted on day one often just…stay that way. That's a lot of reliance on whatever defaults the phone is purchased with.
So this fall, whether you are setting up a shiny new Google Pixel 11 for your aunt, an iPhone 18 Pro for your brother, or any other model for any one of your non-paying tech support "clients," take an extra five minutes to help them download Firefox and set it as their default browser. They can start their new device journey browsing with privacy, choice, and control built in. And you can check one more thing off your unofficial family IT to-do list.
The post An open letter to every family's designated IT support appeared first on The Mozilla Blog.
12 Nov 2026 2:00pm GMT



