SUMO BlogAsk a Fox: A full week celebration of community power

From September 22–28, the Mozilla Support team ran our first-ever Mozilla – Ask a Fox virtual hackathon. In collaboration with the Thunderbird team, we invited contributors, community members, and staff to jump into the Mozilla Community Forums, lend a hand to Firefox and Thunderbird users, and experience the power of Mozillians coming together.

Rallying the Community

The idea was simple: we want to bring not only our long time community members, but newcomers and Mozilla staff together for one-week of focused engagement. The result was extraordinary.

  • The event generated strong momentum for both new and returning community members. This was reflected in the significant growth in total contributors, which rose by 41.6 %.
  • For the past year, our Community Forum had been struggling to maintain a strong reply rate as inbound questions grew. During the event, however, we achieved our highest weekly reply rate of the year, which was more than 50% above our daily average from the first half of 2025.
  • Time to first response (TTFR) also improved by 44.6%, which signal significant improvement in community responsiveness. The event also highlighted the importance of time to first response (TTFR) not just for users, but for the community as a whole. We saw a clear correlation: the faster users received their first reply, the more likely they were to return and continue the conversation.

Together, we showed just how responsive and effective our community can be when we rally around a common goal.

More Than Answering Forum Questions

Ask a Fox wasn’t only about answering questions—it was about connection. Throughout the week, we hosted special AMAs with the WebCompat, Web Performance, and Thunderbird teams, giving contributors the chance to engage directly with product experts. We also ran two Community Get Together calls to gather, share stories, and celebrate the spirit of collaboration.

For some added fun, we also launched a and ⚡ emoji hunt accross our Knowledge Base articles.

Recognizing contributors

We’re grateful for the incredible participation during the event and want to recognize the contributors who went above and beyond. Those who participated in our challenges should receive exclusive SUMO badges in their profile by now. And the following top five contributors for each product will soon receive a $25 swag voucher from us to shop our limited-edition Ask a Fox swag collection, available in the NA/EU swag store.

Firefox desktop (including Enterprise)

Congrats to Paul, Denyshon, Jonz4SUSE, @next, and jscher2000.

Firefox for Android

Congrats to Paul, TyDraniu, GerardoPcp04, Mad_Maks, and sjohnn.

Firefox for iOS 

Congratulations to Paul, Simon.c.lord, TyDraniu, Mad_Maks, and Mozilla-assistent.

Thunderbird (including Thunderbird for Android)

Congratulations to Davidsk, Sfhowes, Mozilla98, MattAuSupport, and Christ1.

 

We also want to extend a warm welcome to newcomers who made impressive impact during the event: mozilla98, starretreat, sjohnn, Vexi, Mark, Mapenzi, cartdaniel437, hariiee1277, and thisisharsh7.

And finally, congratulations to Vincent, winner of the staff award for the highest number of replies during the week.


Ask a Fox was more than a campaign—it was a celebration of what makes Mozilla unique: a global community of people who care deeply about helping others and shaping a better web. Whether you answered one question or one hundred, your contribution mattered.

This event reminded us that when Mozillians come together, we can amplify our impact in powerful ways. And this is just the beginning—we’re excited to carry this momentum forward, continue improving the Community Forums, and build an even stronger, more responsive Mozilla community for everyone.

The Mozilla BlogCelebrate the power of browser choice with Firefox. Join us live.

Firefox is celebrating 21 years of Firefox by hosting four global events celebrating the power of browser choice this fall. 

We are inviting people to join us in Berlin, Chicago, Los Angeles and Munich as part of Open What You Want, Firefox’s campaign to celebrate choice and the freedom to show up exactly as you are — whether that’s in your coffee order, the music you dance to, or the browser you use. These events are an opportunity to highlight why browser choice matters and why Firefox stands apart as the last major independent option.

Firefox is built differently with a history of defiance. It is built in a way to best push back against the defaults of Big Tech. Firefox is the only major browser not backed by a billionaire or built on Chromium’s browser engine. Instead, Firefox is backed by a non-profit, and maintains and runs on Gecko, a flexible, independent, open-source browser engine.

So, it makes sense that we are celebrating differently too. We are inviting people to join us at four community-driven “House Blend” coffee rave events. What is a coffee rave? A caffeine-fueled day rave celebrating choice, freedom, and doing things your own way – online and off. These events are open to everyone and in partnership with local coffee shops.

Each event will have free coffee, exclusive merch, sets by two great, local DJs, a lot of dancing, and an emphasis on how individuals should get to shape their online experience and feel control online — and you can’t feel in control without choice.

We are kicking off the celebrations this Saturday, Oct. 4 in both Chicago and Berlin, will move to Munich the following Saturday, Oct. 11 and will end in Los Angeles Saturday, Nov. 8, for Firefox’s actual birthday weekend.

Berlin (RSVP here)
When: Saturday, Oct. 4, 2025 | 13:00 – 16:00 CEST
Where: Café Bravo, Auguststraße 69, 10117 Berlin-Mitte

Chicago (RSVP here)
When: Saturday, Oct. 4, 2025 | 10:00AM – 2:00PM CT
Where: Drip Collective, 172 N Racine Ave, Chicago Illinois 

Munich (RSVP here)
When: Saturday, Oct. 11, 2025 | 13:00 – 16:00 CEST
Where: ORNO Café, Fraunhoferstraße 11, 80469 München

Los Angeles 
When: Saturday, Nov. 8, 2025 
More information to come

We hope you will join our celebration this year, in person at a coffee rave, or at one of our digital-first activations celebrating internet independence.  As Firefox reflects on another year, it’s a good reminder that the most important choice you can make online is your browser. And browser choice is something that we should all celebrate and not take for granted.

Download Firefox

Take control of your internet

The post Celebrate the power of browser choice with Firefox. Join us live. appeared first on The Mozilla Blog.

The Mozilla BlogBlast off! Firefox turns data power plays into a game

We’re celebrating Firefox’s 21st anniversary this November, marking more than two decades of building a web that reflects creativity, independence and trust. While other major browsers are backed by billionaires, Firefox exists to ensure that the internet works for you — not for those cashing in on your data.

That’s the idea behind Billionaire Blast Off (BBO), an interactive experience where you design a fictional, over-the-top billionaire and launch them on a one-way trip to space. It’s a playful way to flip Big Tech’s power dynamics and remind people that choice belongs in our hands.

BBO lives online at billionaireblastoff.firefox.com, where you can build avatars, share memes and join in the joke. Offline, we’re bringing the fun to TwitchCon, with life-size games and our card game Data War, where data is currency and space is the prize.

Cartoon man riding rocket through space holding Earth with colorful galaxy background.

Create your own billionaire avatar

Play Billionaire Blast Off

The billionaire playbook for your data, served with satire 

The goal of Billionaire Blast Off isn’t finger-wagging — it’s satire you can play. It makes the hidden business of your data tangible, and instead of just reading about the problem, you get to laugh at it, remix it and send it into space.

The game is a safe, silly and shareable way to talk about something serious: who really holds the power over your data.

Two ways to join the fun online:

  • Build a billionaire: Create your own billionaire to send off-planet for good. Customize your avatar with an origin story, core drive and legacy plan.
  • Blast off: We’re not just making little billionaires. We’re launching them into space on a real rocket. Share your creation on social media for a chance to secure a seat for your avatar on the official launch.
<figcaption class="wp-element-caption"> Customize your billionaire avatar at billionaireblastoff.firefox.com.</figcaption>

Next stop: TwitchCon

At TwitchCon, you’ll find us sending billionaires into space (for real), playing Data War and putting the spotlight on the power of choice. 

Visit the Firefox booth #2805 (near Exhibit Hall F) to play Data War, a fast-paced card game where players compete to send egomaniacal, tantrum-prone little billionaires on a one-way ticket to space. 

Step into an AR holobox to channel your billionaire villain era, create a life-size avatar and make it perform for your amusement in 3D.

<figcaption class="wp-element-caption">Try out your billionaire in our AR holobox at TwitchCon booth #2805</figcaption>

On Saturday, Oct. 18, swing by the Firefox Lounge at the block party to snag some swag. Then stick around at 8:30 p.m. PT to cheer as we send billionaire avatars into space on a rocket built by Sent Into Space

Online, the fun continues anytime at billionaireblastoff.firefox.com. Because when the billionaires leave, the web opens up for you.

Download Firefox

Take control of your internet

The post Blast off! Firefox turns data power plays into a game appeared first on The Mozilla Blog.

Mozilla L10NLocalizer Spotlight: Selim

About You

My name is Selim and I’m the Turkish localization manager. I’m from İstanbul, Türkiye. I’ve been contributing to Mozilla since 2010.

Your Contributions

Selim (first left) with fellow Turkish Mozillians Onur, Didem and Serkan (Mozilla Summit Brussels)

Selim (first left) with fellow Turkish Mozillians Onur, Didem and Serkan (Mozilla Summit Brussels)

Q: Over the years, do you remember how many projects you’ve been involved in (including ones that may no longer exist)?

A: It’s been so many! I began with Firefox 15 years ago, but I think I’ve been involved in around 30 projects over the years. We currently have 23 projects active in Pontoon, and I’ve been involved in every single one of them to some degree.

Q: Roughly how many Mozilla events have you joined — whether localization meetups, company-wide gatherings, MozFest, or others?

A: I’ve attended six of them. My first one was the Mozilla Balkans Meetup 2011 in Sofia. Then I had the chance to meet fellow Mozillians in Zagreb, Brussels, Berlin, Paris, and my hometown İstanbul. They were all great experiences, both enlightening and rewarding.

Q: Looking back, are there any contributions or milestones you feel especially proud of?

A: When I first began contributing, my intention was to complete a few missing translations I had noticed in Firefox. However, I quickly realized that the project was huge and there was much more to it than met the eye. Its Turkish localization was around 85% complete at that time, but the community lacked the resources to push it forward. I took it as my duty to reach 100% first, and then spellcheck and fix all existing translations. It took me a few months to get there, but Firefox has clearly had the best Turkish localization among all browsers ever since.

Your Background

Q: Does your professional background support or connect with your work in localization?

A: I currently work as a freelance editor and translator, translating and editing print magazines (mostly tech, popular science, and general knowledge titles), and localizing software and websites.

And the event that kickstarted my career in publishing and professional translation was volunteering for localization. (No, not Firefox. It didn’t even exist yet!) Back in high school, I began localizing an open-source CMS called PHP-Nuke to be used on my school’s website. PHP-Nuke became very popular in a short amount of time, and a computer magazine editor approached me to build the magazine’s website using open-source tools, including PHP-Nuke. I’ve been an avid reader of those magazines since my childhood but never imagined that one day I’d be working for Türkiye’s best-selling computer magazine!

In time, I began translating and writing articles for the magazine as a freelancer and joined the editorial staff after graduating from university.

I’ve written hundreds of software and website reviews and kept noticing that some of them were high-quality products that needed better localization. Now, with a better understanding of how things work and with some technical background, I began contributing to more and more open-source projects in my free time, and Firefox was one of them.

I was lucky that the previous Turkish contributors did a great job “localizing” Firefox, not just translating it. I learned a great deal from them, and it had a huge impact on my later professional work.

I was also approached and/or approved by several clients who had seen my volunteer localization work.

So, in a way, my professional background does support my work in localization — and vice versa.

Q: In what ways has being part of Mozilla’s localization community influenced you — whether in problem-solving, leadership, or collaborating across cultures?

A: Once I started contributing, I quickly realized that Mozilla had something none of the other projects I had contributed to previously had: a community that I felt part of. These people loved the internet, and they were having fun localizing stuff, just like me.

The localization community helped me improve myself both professionally and personally in a lot of ways: I learned how to collaborate better with a team of volunteers from different backgrounds, how to use different translation tools, how to properly report bugs, how to deal with different time zones, and how to get out of my comfort zone and talk to people from abroad both in virtual and face-to-face events.

Your Community

Q: As a long-time contributor, what motivates you to continue after all these years?

A: First and foremost, I believe in Mozilla’s mission wholeheartedly. But there’s a practical motivation too: Turkish is spoken by tens of millions of people, so the potential impact of localization is huge. Ensuring my fellow nationals have access to high-quality, localized open-source software is a driving force. And I’m still having fun doing it!

Q: Many communities struggle with onboarding or retaining contributors, especially after COVID limited in-person events. What are the challenges you face as a manager and how do you address them? And how do you engage with active contributors today? Do you have a process or approach for welcoming newcomers?

A: The Turkish community had its fair share of struggles with onboarding and retaining contributors, but it never became a huge challenge because of an advantage we had: The first iteration of the community started very early. Firefox 1.0 was already available in Turkish, and they maintained a good localization percentage for most Mozilla products, even if not 100%. So when I joined, there were things to do but not a single project that needed to be started from scratch. They were maintainable by one or two enthusiastic localizers. And when I took on the manager role, I always tried to keep it that way. I did approve a number of new projects, but not before ensuring that we had the resources to always keep them at least 90% complete.

But that creates a dilemma: New Turkish contributors usually face strings that are harder to grasp without context or are more difficult to translate, because the easier and more visible strings have already been translated. I guess that makes newcomers frustrated and they leave after translating a few strings. In fact, over the past 10 years, we’ve had only one contributor (Grk) who has translated more than 10,000 strings (apart from myself), and two contributors (Ali and Osman) with more than 1,000 strings. I’d like to thank them once again for their awesome contributions.

The Turkish community has always been very small: just a few people contributing at a time, and that has worked for us. So I’m not anxiously trying to onboard or retain contributors, but if I see an enthusiastic newcomer, I try to guide them by commenting on their translations or sending a welcome email to let them know how things work.

Something Fun
Q: Could you share a few fun or unexpected facts about yourself that people might not know?

A: Certainly:

  • I’m a metalhead, and the first thing I ever translated as a hobby was the lyrics of a Sentenced song. I’ve been translating song lyrics ever since, and I have a blog where I publish them.
  • My favorite documentary is Helvetica.
  • I built my first website when I was 13, by manually typing HTML in Windows Notepad. That’s when I discovered the internet’s endless possibilities and fell in love with it.

The Mozilla Thunderbird BlogThunderbird Monthly Development Digest: August 2025

Hello again from the Thunderbird development team! As autumn settles in, we’re balancing the steady pace of ongoing projects with some forward-looking planning for 2026. Alongside coding and testing, some of our recent attention has gone into budgets, roadmaps, and setting priorities for the year ahead. It’s not the most glamorous work, but it’s essential for keeping our momentum strong and ensuring that the big features we’re building today continue to deliver value well into the future. In the meantime, plenty of exciting progress has landed across the application, and here are some of the highlights.

Exchange support for email is here

Exchange support has officially landed in Thunderbird 144, which will roll out as our October monthly release. A big final push from the team saw a number of important features make it in before the merge:

  • Undo/Redo operations for move/copy/delete
  • Notifications
  • Basic Search
  • Folder Repair
  • Remote message content display & blocking
  • Status Bar feedback messaging
  • Account Settings screen changes
  • Autosync manager for message downloads
  • Attachment delete & detach
  • First set of advanced server settings
  • Experimental tenant-specific configuration options (behind a preference) now being tested with early adopters

The QA team is continuing to work through their test plans with support from a small beta test group, and their findings will guide the documentation and support we share more broadly with users on monthly release 144, as well as the priorities to tackle before we head into the next chapter.

Looking ahead, the team is already focused on:

  • Expanding advanced server settings for more complex environments
  • Improving search functionality
  • Folder Quotas & Subscriptions
  • Refining the user experience as more real-world feedback comes in
  • A planning session to scope work to support calendar and address book via EWS

Keep track of feature delivery here.

Conversation View Work Week

One of the biggest milestones this month was our dedicated Conversation View Work Week which recently wrapped up, where designers and engineers gathered in person to tackle one of Thunderbird’s most anticipated UX features. 

The team aligned early on goals and scope, rapidly iterated on wireframes and high-fidelity mockups, and built out initial front-end components powered by the new Panorama database. 

By the end of the week, we had working prototypes that collapsed threads into a Gmail-style conversation view, demonstrated the new LiveView architecture, and produced detailed design documentation. It was an intense but rewarding sprint that laid the foundation for a more modern and intuitive Thunderbird experience.

Account Hub

We’ve now added the ability to manually edit an EWS configuration, as well as allow for users to create an advanced EWS configuration through the manual configuration step

The ability to cancel any loading operation in account hub for email has been completed and will be added to daily shortly

  • This also had the side effect of users who click “Stop” in the account old setup with an OAuth window open now closing the OAuth window automatically
  • We will be uplifting this change to beta and then ESR

Progress is being made with adding a step for 3rd party hosting credentials confirmation, with the UI complete and the logic being worked on

  • This progress will have to take into account changes from the cancel loading patch, as there are conflicting changes
  • Once this feature is complete, it will be uplifted to beta, and then ESR

Work will soon be starting to enable the creation of address books through account hub by default.

Follow progress in the Meta Bug

Calendar UI Rebuild

After a long pause, work on the Calendar re-write has resumed! We’ve picked things back up by continuing focus on the event read dialog. A number of improvements have already landed, including proper handling of description data and several small bug fixes.

We have seven patches under review that cover key areas such as:

  • Accessibility improvements, including proper announcements of event and calendar titles.
  • Adding the footer for acceptance.
  • Updating displays and transitioning current work to use the mod-src protocol.
  • Handling resizing

Development is also underway to add attendee support, after which we’ll move on to polishing the remaining pieces of the read dialog UI.

Maintenance, Recent Features and Fixes

August was set aside as a focus for maintenance, with a good number of our team dedicated to handling upstream liabilities such as our continued l10n migration to Fluent and module loading changes. In addition to these items, we’ve had help from the development community to deliver a variety of improvements over the past month:

  • Tree restyling following upstream changes – solved
  • An 18 year old bug to enable event duplication via drag & drop – solved
  • A 15 year old bug to sort by unread in threads correctly – solved
  • Implementation of standard colours throughout the application. [meta bug]
  • Modernization of module inclusion. [meta bug]
  • and many more which are listed in release notes for beta.

If you would like to see new features as they land, and help us squash some early bugs, you can try running daily and check the pushlog to see what has recently landed. This assistance is immensely helpful for catching problems early.

Toby Pilling

Senior Manager, Desktop Engineering

The post Thunderbird Monthly Development Digest: August 2025 appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogState of the Thunder 12: Community, Android, and Mozilla Connect

We’re back with our twelfth episode of the State of the Thunder! In this episode, we’re talking about community initiatives, filling you in on Android development, and finishing our updates on popular Mozilla Connect requests.

Want to find out how to join future State of the Thunders? Be sure to join our Thunderbird planning mailing list for all the details.

Austin RiverHacks and Ask-A Fox

Thunderbird is a Silver sponsor for Austin RiverHacks NASA Space Apps Challenge 2025! If you’re in or around Austin, Texas from October 4th-5th, and want to join an in-person event where curious minds delve into NASA data to tackle real-life problems, we’d love to see you.

This week (as in right now! Check it out and get involved!), we’re joining forces with Firefox for the Ask-A-Fox event on Mozilla Support! Earn swag, join an incredible community, and help fellow Thunderbird users on desktop and Android! Want a great overview of how to contribute to SUMO? Watch our Community Office Hours with advice on getting started.

Android Plans for Q4 2025

It’s hard to believe we’re almost into the last three months of the year! We’ve just released our joint July/August Mobile Progress report. We also want to give you all an update on our overall progress on the roadmap we created at the beginning of the year.

The new Account Drawer, currently in Beta, isn’t finished yet. We’re still working on real, proper unified folders! We’ll have mockups of the account drawer progress before the end of the month and more info in the next beta’s release notes. We’ll also have updates soon on message list status notifications (similar to the desktop). In the single message view, we have improvements coming! This includes making attachments quicker to see and open.

The battle for proper IMAP fetch continues. Different server setups complicate this struggle, but we want to get this right, nonetheless. This will bring the Android app more on par with other emails apps.

Unfortunately, work on things like message sync, notifications, and Android 15 might delay features like HTML signatures.

Mozilla Connect Updates, Continued

We’re tackling more of the most frequently requested changes and features on Mozilla Connect, and we’re answering questions about native operating system integration, conversation view, and Thunderbird Pro related features!

Native Operating System Integration

When your operating system is capable of something Thunderbird isn’t, we share your frustration. We want things like OS-native progress bars that show you how downloads are going. We’ve started work on OS-native notification actions, like deleting messages. We love how helpful and time-saving this is, and want to expand it to things like calendar reminders.

There’s possibility and limitation in this, thanks to both Firefox and the OS itself. Firefox enables us more than it restricts us. For example, our work on the progress bar comes straight from Firefox code. Though there are some limits, and Thunderbird’s different needs as a mail client sometimes mean we need to improve an aspect of Firefox to enable further development. But the beauty of open source means we can contribute our improvements upstream! The OS often constrains us more. For example, we’d love snoozeable native OS calendar notifications, but they just aren’t possible yet.

Conversation View

We just finished an entire in-person work week focused on this in Vancouver! Conversation view, if you’re not familiar with it, includes ALL messages in a conversation, including your replies and messages moved to different folders. This feature, along with others, depends on having a single database for all messages in Thunderbird. Our current database doesn’t do this; instead, each folder is its own database.

The new SQLite database, which we’re calling Panorama, will enable a true Conversation View. During the work week, we thought about (and visualized) what the UI will look like. Having developers and designers in the same room was incredibly helpful for a complicated change. (Having a gassy Boston Terrier in said room, less so.) The existing code expects the current database, so we’ll have to rebuild a lot and carefully consider our decisions. The switch to the new database will probably occur next year after the Extended Support Release, behind a preference.

This change will help Thunderbird behave like a modern email client! Moving to Panorama will not only move us into the future, but into the present.

Thunderbird Pro Related-Requests

Three Mozilla Connect requests (Expanding Firefox Relay, a paid Mozilla email domain, and a Thunderbird webmail) were all out of our control once. But now, with the upcoming Thunderbird Pro offerings, these all will be possible! We’re even experimenting with a webmail experience for Thundermail, in addition to using Thunderbird (or even another email client if you want.) We’ll have an upcoming State of the Thunder dedicated to Thunderbird Pro with more info and updates!

Watch the Video (also on PeerTube)

Listen to the Podcast

The post State of the Thunder 12: Community, Android, and Mozilla Connect appeared first on The Thunderbird Blog.

The Mozilla BlogCozy games: A slower pace, and a place to belong

Pixel art plants growing in browser windows, with a cursor hovering a watering can.

This essay was originally published on The Sidebar, Mozilla’s Substack.

There’s a moment Wiandi Vreeswijk knows well. After tending virtual crops in “Stardew Valley” and chatting with other players on Discord, he types: “I can’t anymore. I have to go lay in bed.” It’s the fatigue from long COVID setting in — and almost always, the replies roll in: “Oh yeah, me too.”

Cozy games like “Stardew Valley,” where players complete simple-yet-satisfying tasks like running a farm, have become a safe space for Wiandi.

A video game developer in the Netherlands, Wiandi led an active lifestyle until he got COVID-19 in 2023. He’s had long COVID since then, which makes it difficult for him to go out with friends and family, or to play some of the more intense video games he once enjoyed. That shift led him to explore a different kind of play, one that emphasizes comfort and connection.

For players like Wiandi who are seeking a slower-paced environment, cozy games offer an easy and welcoming entry point. The genre has seen a 57% increase in online mentions in just one year, as more people seek out calm and connection online.

A space to gather

Wiandi recently started a community on the gaming platform Steam where players with chronic conditions can congregate. Since then, he’s set up a public “Stardew Valley” server where people can drop into a shared game, “farm” and chat as they please. The group currently has 56 members, while a corresponding Discord chat has hundreds of participants. 

“It’s been bigger than I expected,” says Wiandi, who initially started with a Dutch community before expanding internationally. “I noticed that a lot of people wanted to join.”

For Wiandi, the best part of building this online community is connecting with others who can relate to what he’s going through. The virtual world allows him to meet people he otherwise wouldn’t have. He can simply fire off a message on Discord.

Pixel art fish in a browser window with a cursor hovering on a fishing rod.

Bonding over shared comfort

Laura Dale, an accessibility consultant for video games and the author of “Uncomfortable Labels: My Life as a Gay Autistic Trans Woman,” often plays cozy games to connect with her neurodivergent friends. She says they’ll regularly chat online while building towns in “Animal Crossing” on their respective Nintendo Switches, a group activity that began during COVID lockdowns but is still going strong.

As someone who sometimes finds social chatter challenging, especially when there’s no obvious topic to discuss (like a video game), playing cozy games gave Laura a relaxing way to maintain and build her relationships.

“I found a lot of solace in playing ‘Animal Crossing’ with friends online,” Laura says. “Having this shared activity gave us a safe topic of conversation.”

Each person doesn’t even need to be playing the same game, as long as they share the same cozy vibe.

“We’re all doing different cozy game activities, but we’re doing them together,” Laura adds.

The appeal of low-pressure play

From “Tetris” to “Elden Ring,” there’s a video game out there for everyone. So what is it about cozy games that attracts players like Laura and Wiandi?

For Wiandi, the answer is obvious: Cozy games have a low barrier to entry.

“Even my mom could learn it in like a day,” he says of “Stardew Valley.” “That’s the charm of a cozy game. When you start, even if you have no experience, you don’t feel overwhelmed by any of the mechanics or the visuals. Everything has to be super easy and minimal — the user experience, the music, the sound effects, even the gameplay.”

Many of the defining characteristics of cozy games, like their leisurely pace, mean they’re more accessible to a wider range of gamers. There’s less pressure to press buttons quickly or get the timing of an attack perfectly right. Titles like “Stardew Valley” and “Animal Crossing” also offer a fixed top-down camera angle, which makes them a better option for some gamers who experience motion sickness, compared to the disorienting camera movement of a first-person shooter. In general, cozy games are also less likely to feature the kind of visual overstimulation that’s common in other genres and can be an issue for players with epilepsy or autism. 

For some players with conditions that affect memory or focus, like ADHD, these games are also designed to quickly remind you what task you were in the middle of during your last session. In “Animal Crossing,” for example, there’s almost always a non-player character nearby ready to explain (or re-explain) what you need to do next if you need it.

“All of these things lend themselves to a wide range of neurodiverse players being able to more safely assume that a cozy game is going to be accessible in a way that you can’t assume as easily with other genres,” Laura says.

Accessibility beyond cozy labels

Cozy games aren’t a perfect fit for every type of disability — there’s no one-size-fits-all solution for such a wide and disparate community.

For Grant Stoner, a games journalist who primarily covers physical accessibility in the industry, cozy games aren’t necessarily more or less accessible than any other genre. Stoner was diagnosed with Spinal Muscular Atrophy type II at 13 months old, and his muscles have weakened over time as a result; he relies on customizable settings and hardware to play most games. There are still some limitations to the types of games he can play, however, including some titles that fall under the cozy genre. 

“Depending on what your disability is, cozy games can be either very overwhelming or very secure safe spaces,” Grant says.

He adds that one of the benefits of a cozy game is the “routines that keep people grounded.” He played an earlier version of “Animal Crossing” for the Nintendo DS handheld, but found that some of the tasks in the latest iteration, for the Nintendo Switch, were too exhausting for him. And anyway, it’s not his video game genre of choice.

“I don’t really like cozy games,” Stoner says. “Not that I think there’s anything wrong with them, it’s just not my genre.” He prefers “intense action games” but still sees the value of titles like “Stardew Valley.” “They have a purpose in the industry.”

Making room for more players

Laura praises the cozy game genre for the many ways it caters to neurodivergent players, but she also recognizes that there’s plenty of room for improvement. One easy fix is in the way these games direct your attention. For plenty of video games, audio cues are a crucial way to convey information, but Laura often plays with the sound off to avoid overstimulation. She’s noticed that some titles are starting to use other methods to achieve the same result.

“I appreciate when cozy games offer visual flashes on screen to communicate information you otherwise need to hear,” Laura says. “Little details like that aren’t always designed for autistic players, but can still be useful.”

For Grant, the most important thing is that the video game industry doesn’t try to shoehorn certain players into a specific type of game or focus its accessibility efforts on just one genre.

“The disabled experience is so individualistic and so vast,” he says. “It’s not fair to the disabled community to say definitively that one [genre] is more accessible than the other.”

As a video game developer himself, Wiandi has plenty of opinions on how to make cozy games better. But for now, he’s just happy to have this new community. 

The small “Stardew Valley” server Wiandi built continues to show how simple interactions in calm digital spaces can create genuine bonds. Players come and go as they please, planting virtual seeds, raising pixelated animals and sharing small triumphs in a chat filled with mutual understanding. 

For Wiandi, the ability to play a game like “Stardew Valley” with other people who are experiencing something similar to him has been empowering.

“It makes me feel good,” he says. “It’s awesome.”

Download Firefox

Take control of your internet

The post Cozy games: A slower pace, and a place to belong  appeared first on The Mozilla Blog.

The Mozilla BlogMozilla welcomes Raffi Krikorian as Chief Technology Officer

Today Mozilla is excited to announce Raffi Krikorian — technologist, innovator and community builder — as our first-ever portfolio wide Chief Technology Officer. 

Reporting to Mozilla President, Mark Surman, Raffi will be part of the team that coordinates efforts across our whole family of organizations. He will work alongside the existing bench of technical leaders including Anthony Enzor-DeMeo (GM / Firefox), Bobby Holley (CTO / Firefox), and Ryan Sipes (Thunderbird).

As AI and technology development becomes increasingly concentrated in the hands of a few, Krikorian joins Mozilla at a moment of urgency and opportunity. It is a pivotal time to shape a different future  — one where we build AI we can trust, use with agency, and understand — rather than accept a future defined by opacity and control. Krikorian will lead Mozilla’s efforts to develop trustworthy and open source AI, ensuring Mozilla is inventing and building technology that pushes us all in the right direction. 

“We need to make sure AI and the internet belong to all of us, not just a few big companies,” said Mark Surman, President of Mozilla. “Raffi is the right person to lead that charge — creative, innovative and passionate about responsible technology. He puts wind in our sails, accelerating Mozilla’s mission of building technology based on the values in our Manifesto.”

Krikorian brings a record of impact across sectors to Mozilla, with roles spanning tech, politics, media and philanthropy. Raffi joins us from having been the CTO at Emerson Collective, where he led efforts to bring technologists into sectors like education, the environment, immigration, and economic mobility — and to help people in those sectors see themselves as technologists. He also hosted the “Technically Optimistic” podcast and Substack, exploring technology’s impact on society.

Prior to that, he was the first CTO of the US’s Democratic National Committee, where he used data, technology, and digital security to support the election processes of Democratic candidates up and down the ballot; Director of Uber’s Advanced Technologies Center, where he led the development and rollout of the first passenger-carrying self-driving car fleet; and Vice President of Platform Engineering at Twitter, where he managed and built Twitter’s global infrastructure. 

Krikorian has served on the Mozilla Foundation Board of Directors since 2023, on Mozilla.ai’s Board since 2024, and on the Mozilla.org Board since its inception.

“We don’t just need critiques on how AI is being built — we need real, working alternatives,” said Krikorian. “Mozilla is one of the few places that can actually do that. It’s built for this moment. I’m excited to join the team and help shape technology that reflects values we care about — transparency, openness, participation, and trust.”

The post Mozilla welcomes Raffi Krikorian as Chief Technology Officer appeared first on The Mozilla Blog.

SeaMonkeySeaMonkey 2.53.22 Beta is out!

Hi All,

The SeaMonkey Project is pleased to announce the immediate release of SeaMonkey 2.53.22 Beta 1.

Please checkout [1] and/or [2].

Please also note, just to be explicit,  SeaMonkey 2.53.22 Beta 1 dropped support for the x86 binaries (Linux i686 and Win32).  So 2.53.21 is the last SeaMonkey version to support Linux i686 and Win32.    I actually use both Linux i686 and Win32 binaries, so I’m kinda sad to see them go.  Anyone remember the OSX x86 binaries (I think it was called Universal binary).  ?    C’est la vie, I guess.   In one way, this lessens the burden of the devs.

Now it’s all x86_64, baby!   x86 binaries have died.  Long live x86 binaries!

:ewong

[1] – https://www.seamonkey-project.org/releases/seamonkey2.53.22

[2] – https://www.seamonkey-project.org/releases/2.53.22b1

Mozilla Add-ons BlogNow you can roll back to a previous version of your extension

Firefox logoIn response to feedback we’ve heard from the community, AMO (addons.mozilla.org) just introduced a new feature allowing developers the ability to quickly roll back to a previously approved extension version. The most common need for roll-back ability are occasions when developers may release a new version they later discover has critical bugs. Now in such cases, instead of needing to make fast fixes and quickly submit an even newer version, which could be further delayed during a review process, developers are free to revert back to a previously approved version.

For users who may have already installed the buggy version that’s later pulled, the extension will update to the roll-back version when Firefox checks for the next update (which occurs every 24 hours by default, save for users who’ve turned off automatic updates from the Add-ons Manager).

To learn more about the new roll-back feature, please visit Extension Workshop.

The post Now you can roll back to a previous version of your extension appeared first on Mozilla Add-ons Community Blog.

The Mozilla BlogYoung people are outsmarting period tracking apps

Out-of-focus person holding a phone in the foreground, with a background of a lush tree covered in bright yellow flowers under a clear blue sky.

This essay was originally published on The Sidebar, Mozilla’s Substack.

Trigger warning: Discussion of pregnancy loss.

Open up TikTok on any given day and you’ll find confident young women openly discussing their periods. They might recognise a low mood is due to the luteal phase or feel amazing because they are ovulating. They acknowledge the importance of self-care and that everybody is different. Periods are normal, but there’s no such thing as a normal period!

For me, a peri-menopausal woman who was surprised by my period every month until trying to get pregnant well into my 30s, this self-awareness and desire of young women to understand their own bodies and cycles is a source of great feminist pride. It is welcome progress from the shame and secrecy traditionally surrounding menstruation education.

A craving for knowledge and understanding has made cycle tracking apps very popular with women and girls from a young age. “I didn’t know about tracking apps until I was 17”, says Gen Z’er Sara*. Some users are keen to share cycle information with their partner and friends to encourage understanding around mood swings, or share funny stories about loud notifications alerting all to the consistency of their discharge today.

Cycle tracking apps are certainly having a moment. There are hundreds available on app stores, from simple calendars to full hormone testing. One study found that the top three cycle tracking apps dominating the market were downloaded 250 million times globally.

Often framed as simple period prediction tools that aid or avoid pregnancy, most usage of cycle tracking apps relates to everyday mental and physical wellbeing. By logging a wide range of symptoms and events, women and girls can track mood, energy levels, manage health conditions and work with their bodies. Apps can provide health and nutrition information as well as recommendations for exercise and meditation.

Cycle tracking apps are also the poster girl of what is going wrong with women’s rights today. The dark side of cycle tracking apps are just that — the tracking. The two-fold threat of increased reproductive surveillance and the sale of sensitive data for advertising is in danger of outweighing the benefits of trusting these apps with information about our bodies and state of mind.

It has been three years since the overturning of Roe v. Wade, which ended the federal protection for abortion in the U.S. Many experts at the time urged women to delete cycle tracking apps in the face of the threat of tracking data being used to “prove” an abortion via a missed period. But is this actually what women are doing? Or, are they finding alternative solutions, workarounds, and new ways to engage with these tools?

Apps that were ahead of the game in terms of a good privacy commitment and track record saw a benefit. Ana Ramirez, co-executive director of Euki, a cycle tracking app and information service remembers, “Our largest download surges were immediately after Roe fell, when Euki received media coverage as a standout privacy period tracker…”

Amy Thompson, founder of the Moody Month app focused on improving mental health observed, “Moody, like much of the industry, saw users delete apps post-Roe v. Wade, but increased media coverage also drove new downloads.”

So while many did delete, tracking apps were not abandoned entirely. Ana explains, “People are hungry for a way to track their sexual and reproductive health without giving up their privacy. In this political climate, period trackers aren’t just tools — they’re lifelines.”

Concerns reached the U.K. where increased surveillance, investigation and prosecution of women suspected of “illegal” abortions after pregnancy loss added to a climate of fear, mistrust and misinformation. Azure*, 16, suspected of the app she uses, It’s dodgy and sends information to the government. It tracks to see if you’ve had an illegal abortion or something.”

Chella Quint, founder of Period Positive and author of Own Your Period saw increased awareness of data privacy risks reaching many U.K. Gen Z’ers in the wake of Roe v. Wade being overturned which affected their use of cycle tracking apps, Some people now use workarounds like avoiding login, using a Notes app instead, or tracking their cycles in a paper diary. Others — both adults and children — are aware of the risks but still find the apps too useful to give up.”

Rose*, 19, agreed “I think most [people] are aware of the issues surrounding privacy and data collection…it’s just a bit overwhelming and I’ve kind of just accepted that it will happen in one way or another.”

High-profile cases in the U.S. related to data breaches and apps selling or sharing customer data with third parties also led users to seek out privacy respecting alternatives, which pushed companies to raise the bar for stricter privacy standards and win back user trust.

For 20-year-old Ella* based in the U.K., a concern over the sale of data by an app in the U.S. prompted a switch of trackers to another one based in Europe that promoted its privacy credentials. Another popular reason to switch is discovering the company behind an app is owned by men — female-founded companies are preferred. While switching apps is common, it is a source of frustration as the data cannot be ported to another app and years of tracking data can be lost. In a competitive market, some apps have capitalised on this by offering to port all the data from another app if the user sends screenshots of calendars.

At a bare minimum cycle tracking apps should not be selling data. But the difference between selling and sharing gets blurry. If it’s in the cloud, it’s being shared with the cloud provider. If advertising on social media, it’s being shared with the platform. Synching with a wearable? It’s being shared. It’s almost impossible to get around this in the digital economy. And the law barely keeps up as Amy Thompson from Moody Month observed, “While anonymisation/pseudonymisation frameworks exist in major privacy laws, enforcement and implementation standards often lag behind evolving privacy risks.”

It can be difficult to comprehend why anyone would be so interested in this info in the first place. As Nat*, 42 from the UK said, “who cares if all the data leaks, who cares if anyone knows my periods, when I have sex, when I go swimming etc?”

A report by the Minderoo Centre for Democracy and Technology outlines the value of knowing if someone is trying to become pregnant as pregnancy is a life event that drastically changes shopping habits. Cycle-based advertising seeks to tailor adverts based on menstrual cycle phases, suggesting that hormone fluctuations can make people susceptible to products at different times, such as clothing and cosmetics in the first half of the cycle when women might be ovulating and feeling good. Either way, someone is commodifying aspects of your body while you are in the process of trying to understand it.

Some may not care deeply about this. For those more likely to be surveilled or face barriers to care — such as people of colour, young people, people on welfare, those living in restrictive U.S. states, menstruating people who do not identify as cis women — they are more guarded about their privacy and what happens to their data. Ana Ramirez from Euki believes these are the people who should be at the forefront in developer’s minds, “Power lies in designing with — not just for — the people most often dismissed as ‘edge cases.’ Centering privacy starts with centering those most impacted.”

Women have always been watched but that is not going to stop us trying to understand what is going on with our bodies. We’ll find workarounds and seek out high privacy standards. We may track our periods for fertility reasons, but there is so much more to it than that. Which makes sense because we, as women and human beings, are much more than that.

*Names have been changed


Lucy Purdon is the founder of Courage Everywhere, a consultancy advising organisations on the responsible development of technology to advance human rights, democracy and gender justice. Lucy has provided strategic advice, policy development and original research for organisations ranging from tech startups to the United Nations. She has worked in civil society roles for over 13 years, including as a Senior Tech Policy Fellow at Mozilla Foundation. She writes the weekly newsletter The Prompt, analysing the latest tech news and trends.

Download Firefox

Take control of your internet

Join us in sharing your act of daily defiance using #dailydefiance and tagging @firefox on social channels to be a part of our movement and remind the world that everyday choices do matter, and we should all choose boldly.

Firefox will be sharing some of the entries with our community and creating mini-challenges for people to follow along. Join us on Instagram, TikTok, Threads, Bluesky and Substack.

The post Young people are outsmarting period tracking apps appeared first on The Mozilla Blog.

The Mozilla BlogFirefox DNS privacy: Faster than ever, now on Android

All web browsing starts with a DNS query to find the IP address for the desired service or website. For much of the internet’s history, this query is sent in the clear. DNS-over-HTTPS (DoH) plugs this privacy leak by encrypting the DNS messages, so no one on the network, not your internet service provider or a free public WiFi provider, can eavesdrop on your browsing.

In 2020, Firefox became the first browser to roll out DoH by default, starting in the United States and in 2023, we announced the Firefox DoH-by-default rollout in Canada, powered by our trusted partner, the Canadian Internet Registration Authority (CIRA).

This year, we’ve built on that foundation and delivered major performance improvements and mobile support, ensuring more Firefox users benefit from privacy without compromise.

Introducing DoH for Android

After bringing encrypted DNS protection to millions of desktop users, we’re now extending the same to mobile. Firefox users who have been waiting for DoH on Android can now turn it on and browse with the same privacy protections as on their desktops.

Starting with this week’s release of Firefox 143 for Android, users can choose to enable DoH in Firefox on their mobile devices by selecting “Increased Protection” DoH configuration. Performance testing with Firefox DoH partners is currently underway. If DoH is as fast as we expect, we plan to enable it by default for Android users in certain regions, similar to desktop users. Until then, these configuration options provide you the choice to opt in early.

<figcaption class="wp-element-caption">Enable DoH in Firefox on Android</figcaption>

DoH performance breakthroughs in 2025

DNS resolution speed is critical to the browsing experience — when web pages involve multiple DNS queries, the speed difference compounds and can cause page loads to be slow. Since we first rolled out DoH in Canada, we’ve worked closely with CIRA for reliability and performance measurements. Through our strong collaboration with them and their technology partner Akamai, Firefox DoH lookups are now 61% faster year-to-date for the 75th percentile.

With these performance improvements, DoH resolution time is now within a millisecond or two of native DNS resolution. This is a big win because Firefox users in Canada now get the privacy of encrypted DNS with no performance penalty.

Although the investigation and analysis started with the desire to improve DoH in Firefox, the benefits didn’t end there. Our collaboration also improved CIRA DoH performance for many of its DNS users, including Canadian universities, as well as other DNS providers relying on CIRA’s or Akamai’s server implementations.

This is a win not just for Firefox users, but for the many other users around the globe.

Robust privacy on your terms

We have always approached DoH with an emphasis on transparency, user choice, and strong privacy safeguards. Firefox gives users meaningful control over how their DNS traffic is handled: Users can opt out, choose their own resolver, or adjust DoH protection levels, and Firefox makes it clear what DoH is doing and why it matters.

Firefox enforces strict requirements for DNS resolvers before trusting them with your browsing. Not every DNS provider can become a DoH provider in Firefox — only those that meet and attest to Mozilla’s rigorous Trusted Recursive Resolver (TRR) policy through a legally binding contract.

Prioritizing your privacy and speed

Our work with DoH this year shows what’s possible when privacy and performance go hand-in-hand. We’ve proven that encrypted DNS can be fast, reliable, and available on desktop and Android. Just as importantly, we’ve shown that partnerships grounded in open standards and accountability can deliver benefits not only to Firefox users but to the wider internet.

As we look forward, our commitment stays the same: Privacy should be the default, speed should never be a compromise, and the web should remain open and accessible to everyone. Choosing Firefox means choosing a browser that is built for you and for a better internet.

Download Firefox

Take control of your internet

The post Firefox DNS privacy: Faster than ever, now on Android appeared first on The Mozilla Blog.

The Mozilla Thunderbird BlogMobile Progress Report – July/August 2025

Hello wonderful community, it has been a while since the last Mobile update.

A lot has happened in the past 2 months, so let’s jump right into a quick overview of current work in progress and primary efforts.

Account Drawer in progress

If you’re rocking the Beta version of Thunderbird for Android, you might have noticed that all your unified folders have disappeared! Don’t panic, that’s just temporary.

We’re still churning through the technical debt and the database inconsistencies in order to create through virtual unified folders for all your accounts.

The final goal is the same as the one we shared in a previous update, which you can see the final mock-ups here:

Expect more updates in the coming releases.

iOS account setup

The work on the iOS version is moving at full speed!

We found ourselves in a bit of a tight spot due to the recent announcements of Apple with their new iOS 26 version, and a somewhat complete redesign of all the SwiftUI and general Human Interface Guidelines.

When will iOS 26 be widely available and adopted?

Will we have our iOS version of Thunderbird ready before that?

If we build it on current iOS 18 design guidelines, how would that look on the new version?

Will we need to update everything right after releasing the first version?

Due to these uncertainties, we decided to focus only on the new iOS 26 user interface and be compatible with the new version right off the bat.

We will need to test and explore carefully how that behaves on iOS 18 and prior, hoping for some available translation layers in order to guarantee compatibility.

For now, here’s a sneak peek of the Account Setup flow for iOS!

Read/Unread status improvements in Android

As we move through an old codebase and we work hard to modernize components and layouts, it is unfortunately inevitable that we accidentally break old features or setups that are familiar to users.

We apologize for the inconvenience, especially in this latest highlighted issue which created some discomfort when it comes to the visual distinction between read and unread messages.

The old UI offered an option to customize the background color of those states. Even if this solution sounds like a good approach, it created multiple problems related to following system themes, light/dark mode variations, and the overall outdated implementation that needed to be removed.

Some users were dissatisfied, and rightly so, due to the less than optimal visual distinction between those states that solely relied on background colors.

We already improved the overall visual consistency and distinction in that area, but we’re working towards implementing a much clearer visual representation for each state that doesn’t just rely on background colors.

We’re implementing a combination of background and foreground colors, font weight variation, and a visual indicator that specifically represents unread and new messages.

This approach will remove any confusion and hopefully completely fix this problem.

Thank you all those involved for your feedback and concerns, and for using the Beta version to provide early feedback and test the new updates.

A new release cadence

Starting from September, we’re switching to a faster and more consistent release cadence.

The first week of every month we will release a new beta version, for example v13b1, followed by a new incremental beta version with improvements and fixes directly from the main branch, being released every week during that month (eg: v13b2, v13b3, etc).

At the end of that month, the current beta, after being deemed reliable and having passed our QA steps, will be promoted as a stable version and at the same time a new beta branch will be released.

In summary, starting from September you can expect a new stable version and a new beta cycle every month.

Changing our cadence will allow us to expose new and work in progress features more quickly to our beta audience, and shorten the waiting time for users on the stable branch, with smaller and consistent incremental improvements.

Cheers,

Alessandro Castellani(he, him)
Director, Desktop and Mobile Apps | Mozilla Thunderbird

The post Mobile Progress Report – July/August 2025 appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogState of the Thunder: Mozilla Connect Updates

Welcome back to the latest season of State of the Thunder! After a short break, we’re back and ready to go. Michael Ellis, our Manager of Community Programs, is helping Alessandro with hosting duties. Along with members of the Thunderbird team and community, they’re answering your questions and keeping everyone updated on our roadmap progress for our projects.

In this episode, we’re talking about our initiatives for regular community feedback, tackling a variety of questions, and providing status updates on the top 20-ish Mozilla Connect Thunderbird suggestions.

Community Questions

Accidental Message Order Sorting

Question: Clearly the number one issue with Thunderbird that breaks for many of my clients is that if they accidentally click on a column header the sorting of the message is changed. “My messages are gone” is what I then hear all the time from my clients. It would be wonderful if the sorting of the message could be locked and not changed through such an easy operation, which often is invoked accidentally.

Answer: This is a great usability question and a complicated one. Alessandro recommends switching to CardsView, as it’s harder to accidentally change. This one one of the reasons we implemented it! However, we can definitely explore options to lock the message order in through enterprise policies. We would want to be mindful of users who wanted to change the order.

Michael discusses the option of a pop-up warning that could inform the user they’re about the change the message sorting order. Increased friction through a pop-up, though, as Alessandro and Jesse Miksic from the design team both point out, can cause its own issues. But this is certainly something we’ll look into more!

Move Focus Keyboard Shortcut

Question: Could there be consideration to add a keystroke to immediately move the focus to the list of messages in the currently open mailbox? Even better if keystrokes that would automatically do this for the inbox folder or the default account.

Answer: Alessandro notes Thunderbird already has this ability, but it’s not super noticeable. The F6 key allows you to switch focuses between the main areas of the application. So we’re approaching this problem from two directions: implementing tabular keyboard navigation and customizable shortcuts. We don’t have an expected delivery date on the latter, but we plan to have a searchable keyboard shortcut hub. We know our interface can be a little daunting, and we’re tackling it from multiple angles.

Option for Simplified Thunderbird?

Question: I work for a company which develops a Raspberry Pi-based computer made specific… specifically for blind consumers. Thunderbird is installed on this device by default. Many of our users are not tech-savvy. and just want a simple email client. I would love to have an easy method for removing some of the clutters with the goal of having a UI with fewer controls. Currently, users often have to press the tab key many times just to move to the list of messages in their inbox. For some users, all they really want is the message list and the list of folders, with the menu bar open, and that’s it. A bit like we once had with Outlook Express.

Answer: Alessandro and Ryan Sipes, our director, have talked about the need for a lighter version of Thunderbird a lot. This would help users who don’t need all the power of Thunderbird, and just want to focus on their messages (not even their folders). However, Ryan doesn’t want a separate version of Thunderbird we’d need to maintain, but to build a better usability curve into Thunderbird. Answering this question means having a Thunderbird that is simple by default, but more powerful and customizable if needed, without upsetting our current users.

Heather Ellsworth from the community team also supports the idea of a user preference for a lighter Thunderbird. At conferences and co-working spaces, she constantly hears the requests for a slightly simpler version of Thunderbird.

Thunderbird PPA

Question: I’m using Linux, one of the Ubuntu-derived flavors. And I have Thunderbird 128.14 ESR installed through the Mozilla Team PPA. I would love to know when the ESR version of 140 will be available in this PPA.

Answer: Heather, who works a lot with Linux packaging, takes this question. This PPA isn’t an official distribution channel for Thunderbird, which leads to some confusion. Our official Linux packages are the Snap and flatpak, and the tarball available on our website. A community member named Rico, whose handle is ricotz, maintains this PPA. In the PPA, you can click on his name to learn how to contact him for question like this.

Top 20-ish Mozilla Connect Posts

If you’ve ever posted an idea to make Thunderbird better in a blog comment, social media post, or a SUMO (Mozilla Support) thread, you’ve probably been prompted to share your suggestion on Mozilla Connect. This helps us keep our community feedback in one place, which helps our team prioritize features the community wants!

Where we’re falling short, however, is keeping the community updated on the progress of their suggestions. With a dedicated community team, this is something we can do better! Right now, we’d like to provide a quick status update on the top 20-ish Mozilla Connect posts related to Thunderbird.

Sync

We implemented this in the Daily build of the desktop app last year, using a staging environment for Firefox Sync. But Firefox Sync is called Firefox Sync because it’s built for Firefox. Thunderbird profiles, in comparison, have a lot more data points. This meant we had to build something completely different.

As we started to spin up Thunderbird Pro, we decided it made more sense to have a Thunderbird account that would manage everything, including Sync. Unfortunately, this meant a lot of delays. So Sync is still on our radar, and we hope to have it next year, barring further complications.

GNOME Desktop Integration

Yes, we’re working on this, starting with native desktop notifications. Ideally, we want to be integrated with more Linux desktop environments through expanded native APIs.

Color for Thunderbird Accounts

We already have it! You can access your account settings and customize the colors of each account.

Show full email address on mouse-over

Already have this too. If this doesn’t happen, it’s a bug, and we’d definitely appreciate a report at Bugzilla.

Don’t save passwords as plain text, but rather integrate with the OS storage system

We’re exploring this as both part of our increased native OS integrations and strengthening and security integrations with Thunderbird.

Thunderbird should, by default, have all telemetry as an opt-in option, or have zero telemetry

We’re already adopting opt-in telemetry for an upcoming release of Thunderbird for Android, and we want to make this the default for desktop in the future. While desktop is currently opt-out, Alessandro stresses we only have a few limited telemetry probes for desktop Thunderbird. And those probes can show how the majority of users are using the app and help us avoid bad UX choices.

Thunderbird for iPhone and iPad

In progress!

JMAP Support

Currently in the works for the upcoming iOS release, with plans for support on desktop and Android. Thundermail will also come with JMAP.

Firefox Translate

Exploring this is low on our list right now. This is both because of performance concerns and we want to be very cautious with anything concerning machine learning, which includes translation.

Watch the Video (Also on Peertube)

Listen on the Thundercast!



Our Next State of the Thunder

Anxious to know the rest of the top 20 Mozilla Connect posts? Join us on Tuesday, September 16 at 3 PM Pacific (22:00 UTC)! Find out how to join on the TB Planning mailing list. We think this will be a great season and who knows, by the end of it, we may even have a jingle. See you next time!

The post State of the Thunder: Mozilla Connect Updates appeared first on The Thunderbird Blog.

Open Policy & AdvocacyMozilla Meetup: “The Future of Competition: How to Save the Open Web”

The promise of an open and competitive internet hangs in the balance. From the future of AI agents to the underappreciated role of browsers and browser engines, the technological landscape continues to evolve. Getting the regulatory and enforcement backdrop right is critical: from competition bills in Congress to the EU’s DMA, the stakes for innovation, privacy and consumer choice have never been higher.




The post Mozilla Meetup: “The Future of Competition: How to Save the Open Web” appeared first on Open Policy & Advocacy.

The Mozilla BlogOn Firefox for iOS, summarize a page with a shake or a tap

On mobile, browsing often means quick checks on small screens, squeezed in between everything else you’re doing. We built Shake to Summarize on iOS to give you a clear summary with one move. That way, you can get what you need more easily and keep going.

How it works

Whether you just want the recipe, need to know something fast, or want to see if a long read is worth the time, Shake to Summarize gives you the key takeaways in seconds. To activate it, you can:

  • Shake your device.
  • Tap the thunderbolt icon in the address bar.
  • Or, from the menu, tap three dots > Summarize Page.

The feature works on webpages with fewer than 5,000 words. (Learn more about content you can summarize here.) 

Here’s an example of a summary:

Three smartphone screens showing Firefox article summarized with Apple Intelligence on translation updates for Chinese, Japanese, and Korean users.

If you have an iPhone 15 Pro or later with iOS 26+, the summary is created on your device using Apple Intelligence. On other devices with earlier iOS versions, the page text is sent securely to Mozilla cloud-based AI, which creates the summary and sends it back. 

Rollout starts Sept. 9

Shake to Summarize starts rolling out this week in the U.S. for English-language Firefox iOS users, then expands from there. 

You’ll see a prompt the first time you come across content that can be summarized, and you can turn the feature on or off in settings anytime.

Summarize a page on desktop

You can also summarize pages in Firefox on desktop with your choice of chatbot provider:

  • Select Summarize Page at the bottom of the chatbot sidebar.
  • Or hold down Control while you click, then choose Ask [chatbot name] > Summarize Page.

See more information here.

Designed for user choice

Sometimes you want the whole story. Sometimes you just need the highlights. Firefox gives you both and leaves the choice to you. 

Let us know what you think once you give it a try.

Take control of your internet

Download Firefox

The post On Firefox for iOS, summarize a page with a shake or a tap appeared first on The Mozilla Blog.

The Mozilla BlogDefending an open web: What the Google search ruling means for the future

The Mozilla logo in green on a black background

Last week, Judge Amit Mehta issued a ruling in the remedies proceedings of the U.S. v. Google LLC search case. Among the issues addressed, one key aspect that stood out for us was the court’s ruling on Google’s search agreements. 

The Court ordered changes to Google’s search agreements to give browsers more flexibility. Under the court’s decision, Google cannot restrict browsers from defaulting to or offering different search engines / generative AI services. They can also not prevent browsers from promoting these services.   

Crucially, the Court considered but ultimately rejected a proposed ban on search payments to small, independent browsers like Firefox. If the ban had been enforced, it would have made it harder for independent browsers to compete, effectively reducing competition in the browser market. 

In his reasoning, Judge Mehta cited Mozilla’s testimony, recognizing that banning payments to smaller browsers would harm innovation, competition, and consumers, and would threaten the pro-competitive role of Mozilla in the ecosystem. Ensuring that Mozilla’s Gecko — the only independent browser engine left — can continue to compete with Google and Apple is vital for the future of the open web.

The court also required a range of data sharing remedies — narrowing the scope of those proposed by the Department of Justice and State Attorneys General, while broadening their access. As Mozilla has discovered first-hand through previous antitrust cases and the implementation of the EU Digital Markets Act, ensuring that such remedies are effective in restoring competition requires careful attention and monitoring. Careful thought must also be given to protecting user privacy and security.

It will also be critical to ensure that these data remedies avoid simply transferring power from one tech giant to another — particularly given the focus on facilitating greater search competition through AI providers.  

This balance is something we’ve stressed throughout the trial. True competition in search starts with a healthy marketplace, one where small and large companies can compete on merit, where consumers have choice, and where the best new products, features, and ideas have a chance. 

As this case continues to unfold, one thing won’t change: Mozilla’s commitment to an internet that’s open, accessible, and built for the public good. We’ve historically met market and regulatory shifts with creativity and care. Each moment has helped us grow and discover new ways to live out our mission, and we’re invigorated about the path forward. 

The post Defending an open web: What the Google search ruling means for the future appeared first on The Mozilla Blog.

The Mozilla Thunderbird BlogVIDEO: Thunderbird Accessibility Study

Welcome back to another edition of the Community Office Hours! This month, we’re taking a closer look at accessibility in the Thunderbird desktop and mobile apps. We’re chatting with Rebecca Taylor and Solange Valverde, members of our designer, about a recent accessibility (often shortened as a11y) study. We wanted to find out where Thunderbird was doing well, and where we could improve. Rebecca and Solange walk us through the study and answer our questions!

We’ll be back next month with the latest Community Office Hours! If you have a suggestion for a topic or team you’d love us to cover, please let us know in the comments!

August Office Hours: Thunderbird Accessibility Study

The Thunderbird Team wants to make desktop and mobile apps that maximizes everyone’s productivity and freedom. This means making Thunderbird accessible for all of our users, and the first step is finding where we can do better. Thanks to our relationship with Mozilla, our design team commissioned a study with Fable, who connects companies building inclusive products to experienced testers with disabilities. We asked participants to evaluate the Thunderbird desktop app using assistive tech, including screen readers, alternative navigation, and magnification. And we also asked a user on the cognitive spectrum to evaluate how our language, layouts, and reminders helped or hindered their use of the app.

Members of the design team then conducted 60 minute moderated interviews with study participants. In these talks, participants pointed out where they struggled with accessibility roadblocks, and what strategies they used to try and work through them.

Screen Reader Users

Screen readers convert on-screen text to either speech or Braille, and help blind or low-vision users navigate and access digital content. Our study participants, many of whom switch between multiple screen readers, let us know where Thunderbird falls short.

Some issues were common to all screen readers. Keyboard shortcuts didn’t follow common norms, and workflows in search and filter results made for a confusing experience. Thunderbird could benefit from a table view with ARIA, a W3C specification created to improve accessibility.

Other issues were specific to the individual screen reader programs. In Narrator, for example, expected confirmation for actions like moving messages was missing, and the screen reader didn’t recognize menu stage changes in submenus. In JAWS, meanwhile, message bodies were unreadable in email and compose windows with Braille display, and filter menus opened silently, not announcing the content or state to the user. Finally, with NVDA, users noted confusing structures and organization that lacked the structure and context they expected, as well as poor content prioritization.

Cognitive Usability

In a previous office hours, we talked about how we wanted to make Thunderbird more cognitively accessible with our work on the Message Context Menu. Cognition relates to how we think, learn, understand, remember, and pay attention, and clear language, regular layouts, and meaningful reminders all improve cognitive accessibility. Our cognitive accessibility tester expressed concerns about a lack of a quick, non-technical setup, imbalances in our whitespace, and unpredictable layout controls, among other issues.

Alternative Navigation and Magnification

Our alternative navigation users tested how well they could use Thunderbird with voice controls and eye tracking software. Our voice control testers found room for improvement with menu action labels, better autofocus shift when scrolling through emails, and a larger font size for more comfortable voice-driven use. Likewise, our eye tracking software tester found issues with font sizes. They also noted concerns with composition workflow and focus, too-small controls, and a drag-and-drop bug.

Our magnification tester found where we could improve visual contrast and pane layouts. They also found off-screen elements could steal focus from new messages, and that folder paths and hierarchies could use more clarification.

Conclusions and Next Steps

We’re incredibly grateful for the insights we learned from this study on the many aspects of accessibility we want to improve in all of our apps. We want to thank Mozilla for their helping us take the next step in accessibility research, and Fable for providing a fantastic platform for accessibility testing. We’re also so grateful to our study participants for all their time and sharing their perspectives, concerns, and insights.

This is far from the end of our accessibility journey. We’re looking forward to working what we learned in this study into deeper research and ultimately our desktop roadmap. We can’t wait to start accessibility research on our mobile apps. And we hope this study can help other open source projects start their own accessibility research to improve their projects.

One way you can get involved is to report accessibility bugs on the desktop app. Go to the Thunderbird section on Bugzilla, and under ‘Component’ select ‘Disability Access.’ Additionally, click ‘Show Advanced Fields’ and enter ‘access’ into the ‘Details > Keywords’ section. Add screenshots when possible. Be sure to describe the bug so others can try and reproduce the it for better troubleshooting.

If you want to learn more about our accessibility efforts, please join our User Experience mailing list! If you think you’re ready to get involved, please join our dedicated Matrix channel. We hope you help us make Thunderbird available, and accessible, everywhere!

VIDEO (Also on Peertube):

Slides:

Resources:

  • Bugzilla Disability Access bugs and enhancement requests: https://mzl.la/41jrnuv
  • Fable: https://makeitfable.com/
  • Thunderbird A11y Matrix channel: https://matrix.to/#/%23tb-a11y:mozilla.org
  • Thunderbird User Experience Mailing List: https://thunderbird.topicbox.com/groups/ux
  • Thunderbird suggested tools and resources for Accessibility: https://bolt.thunderbird.net/8b179dbfd/p/33ddcb-accessibility
  • Config 2024: Pitching accessible design like a pro: https://www.youtube.com/watch?v=NoHIDWF0d6I

The post VIDEO: Thunderbird Accessibility Study appeared first on The Thunderbird Blog.

The Mozilla BlogSpeeding up Firefox Local AI Runtime

Last year we rolled out the Firefox AI Runtime, the engine that quietly powers features such as PDF.js generated alt text and, more recently, our smart tab grouping. The system worked, but not quite at the speed we wanted.

This post explains how we accelerated inference by replacing the default onnxruntime‑web that powers Transformers.js with its native C++ counterpart that now lives inside Firefox.

Where we started

Transformers.js is the JavaScript counterpart to Hugging Face’s Python library. Under the hood it relies on onnxruntime‑web, a WebAssembly (WASM) build of ONNX Runtime.

A typical inference cycle:

  1. Pre‑processing in JavaScript (tokenization, tensor shaping)
  2. Model execution in WASM
  3. Post‑processing back in JavaScript

Even with warm caches, that dance crosses multiple layers. The real hotspot is the matrix multiplications, implemented with generic SIMD when running on CPU.

Why plain WASM wasn’t enough

WASM SIMD is great, but it can’t beat hardware‑specific instructions such as NEON on Apple Silicon or AVX‑512 on modern Intel chips.

Firefox Translations (uses Bergamot) already proves that diving to native code speeds things up: it uses WASM built‑ins which are small hooks that let WASM call into C++ compiled with those intrinsics. The project, nicknamed gemmology, works brilliantly.

We tried porting that trick to ONNX, but the huge number of operators made a one‑by‑one rewrite unmaintainable. And each cold start still paid the JS/WASM warm‑up tax.

Switching to ONNX C++

Transformers.js talks to ONNX Runtime through a tiny surface. It creates a session, pushes a Tensor, and pulls a result. It makes it simple to swap the backend without touching feature code.

Our steps to achieve this were:

  1. Vendor ONNX Runtime C++ directly into the Firefox tree.
  2. Expose it to JavaScript via a thin WebIDL layer.
  3. Wire Transformers.js to the new backend.

From the perspective of a feature like PDF alt‑text, nothing changed, it still calls await pipeline(…). Underneath, tensors now go straight to native code.

Integration of ONNX Runtime to the build system

Upstream ONNX runtime does not support all of our build configuration, and it’s a large amount of code. As a consequence we chose not to add it in-tree. Instead, a configuration flag can be used to provide a compiled version of the ONNX runtime. It is eventually automatically downloaded from Taskcluster (where we build it for a selection of supported configuration) or provided by downstream developers. This provides flexibility while not slowing down our usual build and requiring low maintenance.

Building ONNX on Taskcluster required some configuration changes and upstream patches. The goal was to find a balance between speed and binary size, while being compatible with native code requirements from the Firefox repo. 

Most notably:

  • Building without exception and RTTI support required some patches upstream
  • Default build configuration is set to MinSizeRel, compilation uses LTO

The payoff

Because the native backend is a drop‑in replacement, we can enable it feature by feature and gather real‑world numbers. Early benchmarks shows from 2 to 10 × faster inference, with zero WASM warm‑up overhead.

For example, the Smart Tab Grouping topic suggestion, which can be laggy on first run, is now quite snappy, and this is the first feature we gradually moved to this backend for Firefox 142.

graph showing the difference between WASM and c++ backend. the C++ being way faster

The image to text model used for PDF.js alt-text feature also benefited from this change. On the same hardware the latency went from from 3.5s to 350ms.

What’s next

We’re gradually rolling out this new backend to additional features throughout the summer, so all capabilities built on Transformers.js can take advantage of it. 

And with the C++ API at hand, we’re planning to tackle a few long‑standing pain points, and enable GPU.

Those changes will ship in our vendored ONNX Runtime and offer us the best possible performance for Transformers.js-based features in our runtime in the future.

1. DequantizeLinear goes multi‑threaded

The DequantizeLinear operation is single‑threaded and often dominated inference time. While upstream work recently merged an improvement (PR #24818), we built a patch to spread the work across cores, letting the compiler auto‑vectorize the inner loops. The result is an almost linear speedup, especially on machines with many cores.

2. Matrix transposition goes multi-threaded

Similarly, it is typical to have to transpose very large (multiple dozen megabytes) matrices when performing an inference task. This operation was done naively with nested for loops. Switching to a multi-threaded cache-aware tiled transposition scheme, and leveraging SIMD allowed to take advantage of modern hardware and speed up this operation by a supra-linear factor, typically twice the number of threads allocated to this task, for example a 8x speedup using 4 threads.

This can be explained by the fact that the naive for loop was auto-vectorized, but otherwise did poor usage of CPU caches.

3. Caching the compiled graph

Before an inference can run, ONNX Runtime compiles the model graph for the current platform. On large models such as Qwen 2.5 0.5B this can cost up to five seconds every launch. 

We can cache the compiled graph separately from the weights on the fly, shaving anywhere from a few milliseconds to the full five seconds.

4. Using GPUs

Currently, we’ve integrated only CPU-based providers. The next step is to support GPU-accelerated ONNX backends, which will require more effort. This is because GPU support demands additional sandboxing to safely and securely interact with the underlying hardware.

Conclusion

What is interesting about this migration is the fact that we could improve performance that much, while migrating features gradually, and all that in complete isolation, without having to change any feature code.

While the speed ups are already visible from a UX standpoint, we believe that a lot of improvement can and will happen in the future, further improving the efficiency of the ML-based features, and making them more accessible to a wider audience.

Have ideas, questions or bug reports? Ping us on Discord in the firefox-ai channel (https://discord.gg/TBZXDKnz) or file an issue on Bugzilla, we’re all ears.

The post Speeding up Firefox Local AI Runtime appeared first on The Mozilla Blog.

The Mozilla Thunderbird BlogThunderbird Monthly Release 142 Recap

We’re back with another exciting Monthly Release recap! Thunderbird 142.0 brings a host of user-requested features and important bug fixes that make your email experience smoother and more reliable. From better folder management to smarter PDF handling, this release focuses on the details that matter most to your daily workflow.

A quick reminder – these updates are for users on our monthly Thunderbird Release channel. For our users still on the ESR (Extended Standard Release) channel, these updates won’t land until next July 2026. For more information on the differences between the channels and how to make the switch:

Now let’s dive into what’s new in 142.0!

New Features:

Reset Manual Folder Sorting

Bug 1972710

Ever tweaked your folder order and wished you could start fresh? We hear you! Thunderbird 142 introduces a simple way to reset your folder sorting back to defaults. 

Benefits:

  • The new Reset Folder Order option lets users right‑click an account in the Folder Pane to instantly clear any custom sorting. 
  • Provides a quick clean slate and avoids manually dragging folders back to default positions.

Note: This feature resets sorting order but doesn’t restore folders that were moved inside different parent folders.

PDF Signatures and Attachment Handling

Bug 1970796

Thunderbird now lets you add visual signatures to PDF attachments opened inside the app. This update brings Thunderbird in line with modern PDF functionality, making it easier to handle contracts, forms, and other documents without leaving your inbox.

Benefits:

  • Add a handwritten-style visual signature directly in Thunderbird.
  • No need for external tools to sign simple PDF documents.
  • Keeps everyday document handling faster and more convenient.

Custom OAuth Support for Add-on developers

Bug 1967370

New add-on API support for OAuth client registration now allows developers and organizations to add custom OAuth providers at runtime. Instead of requiring changes in Thunderbird’s core code, an add-on can handle the setup. 

Benefits:

  • Supports custom OAuth providers through add-ons.
  • Works with enterprise policies for organizational deployments.
  • Simplifies integration with unique authentication systems.

Bug Fixes

Respect for “Do Not Disturb”

Bug 1876310

Your focus time is sacred, and Thunderbird now honors that across all operating systems.

Benefits:

  • Native OS notifications now respect the “Do Not Disturb” setting of every operating system, including blocking calendar reminders and chat notification sounds.
  • Delivers protected focus time and consistent behavior with other applications.

Improved Dark Reader Mode Toggle

Bug 1962931

Reading flow is now smoother when switching between light and dark message modes.  An issue was reported where toggling the setting in the message header would reset your scroll position and pull focus away from the message body. 

Benefits:

  • Keep your scroll position in the message when switching between light and dark mode so you can continue reading without interruption.
  • Retain focus on the message body for easier keyboard navigation.
  • Reduce extra clicks and scrolling, making reading more seamless.

Message List Scrolling Fix

Bug 1968967

Unwanted scrolling of the message list that happened when returning to the Mail tab after opening a message is now a thing of the past. Instead of jumping to the top and slowly scrolling back down, the list now stays put.

Benefits:

  • Keep your place in the message list when switching tabs.

PDF Attachments Reload Correctly on Startup

Bug 1970615

Thunderbird now correctly reloads PDF attachments that were left open in tabs when you restart the app. Previously, these tabs would fail to open and display an error, forcing you to reload them manually.

Benefits:

  • Open PDF attachments are restored automatically on startup.
  • No more error messages when resuming work.

The post Thunderbird Monthly Release 142 Recap appeared first on The Thunderbird Blog.

The Mozilla BlogWhat I learned when I stopped posting my life online, from a former influencer

Woman with orange hair in peach coat and floral bag standing by blooming tree.<figcaption class="wp-element-caption">During my influencer and blogging era, 2016. </figcaption>

This essay was originally published on The Sidebar, Mozilla’s Substack.

I was an influencer years before it became mainstream in 2016. I shared my outfits on my fashion blog almost daily, along with recipes, travel itineraries, lifestyle photos, you name it. My blog upheld a twee aesthetic that I stuck to religiously. I made content (it wasn’t called that yet), curated an aesthetic (it also wasn’t called that yet) and blurred the lines between what was real and what was for the curated version of me. I was good at it and made money from sponsored content and paid ads. But I learned how overcurating can affect every part of your life. 

I was always thinking about the shot I needed to get, if a restaurant was going to match my aesthetic, or if I needed to go thrifting to purchase new clothes because I had gone through most of my clothes in my previous blog posts. In the early 2010s, blogs that did well were a one-stop-shop for all lifestyle content. It was a lot of work, but that’s what I strived for.

I was an influencer when the term was just “blogger” and things were slower, but I never felt that. I struggled to keep up even with caffeine pills, being in my early 20s with a lot of energy and finding out that I liked being online and enjoyed it there. But by the time the term “influencer” entered common conversations among coworkers and family, I was burnt out. I was over it, exhausted from overcurating my life. So I decided to stop posting.

Lesson 1: The best photos aren’t staged

I kept my website up for a while, then shut it down completely. Going “offline,” I found that the best photos are the ones that are not staged, and you will find yourself with the most beautiful pictures of yourself. Of course we all know this, we all want those curated photo dumps for Instagram and candid shots of us just looking carefree… but what I’m saying is stop asking for photos altogether. Let people take pictures of you unasked. The best photos of myself were during the years I was offline because I didn’t think about any photos in the same way. These were pictures I didn’t ask for, therefore I wouldn’t have that many to choose from. It felt almost like film pictures I developed, I had to pick from one or two. 

Lesson 2: Hobbies hit different

I also found that you have a lot more free time when you don’t have to be online. I still scrolled sometimes, I still read blogs, I still downloaded TikTok in 2020, but I didn’t feel the need to scroll in the same way. When I was offline, I was only scrolling for pleasure like finding videos of a Furbie cult or Calico Critters collector drama.

Going ‘offline,’ I found that the best photos are the ones that are not staged, and you will find the most beautiful pictures of yourself.

But when I was blogging, and when I got back online for Tiktok and my Substack, I was scrolling for strategy. I needed to know what current trends I should talk about or follow, and I felt if I missed something online it could hurt my credibility. When I stopped blogging, I almost didn’t know what to do with my extra time – I’m a girl with hobbies and friends and I was in my 20s, so this says a lot! I spent so long curating my online presence, picking out outfits, planning photoshoots, and replying to emails (not even to mention actual blogging!) that I had SO much free time. I could actually focus on my hobbies… for me. I didn’t need to take photos of everything nor look at the menu of the restaurant before I went. Over time I got used to it and loved it. I no longer had to collect stamps or postcards, which was just something I did for my blog. I even took up new hobbies, ones that couldn’t be translated into my blog or online, like watching anime and learning how to work a grill. Camping was not aesthetic enough for my blog, though I still went when I was blogging. After quitting I felt like I could go more often, because there was no post being counted on that weekend. I could do whatever I wanted without the fear of “what will I post?” 

Smiling woman in bright yellow dress with sunglasses standing in sunny green field.<figcaption class="wp-element-caption">In 2020, after I had been offline for a few years and before joining TikTok. </figcaption>

Lesson 3: Your personal style will change

It’s been said that people can tell how much screentime you spend by how you dress, and I agree. If you are wearing everything trending, experimenting with the cutting edge micro trends and aesthetics, you are definitely online and probably online a lot. There is nothing wrong with that (besides overconsumption, but that is for a different topic), but when you exit an online space you exit those types of information. While blogging I was wearing tons of layers, everything pre-1980s vintage, and uncomfortable hats and fabrics. I bought my first pair of athletic leggings with pockets after I quit blogging and I wondered why I deprived myself of this type of comfort for so long. You will be dressing for you and those only physically around you, not other people online and not trying to go viral. It will be different and you should embrace that. It’s a luxury not everyone has. 

Lesson 4: You learn the things you actually enjoy, and those you don’t 

It took time to adjust to being offline, but those times might have been my happiest. Nothing felt calculated anymore. Once you stop posting, you’re not in the public eye in the same way. I didn’t worry if someone in my city recognized me at the grocery store in my pjs and hungover. I started being sillier. I decided to use some extra time I had to write more poetry and do readings at local venues. It took a while for me to realize this, but after I took down my blog there was no real trace of me. I could be anyone. I was just Lindsey. Not Lindsey the fashion blogger, just Lindsey.

I started being sillier. I decided to use some extra time I had to write more poetry and do readings at local venues. It took a while for me to realize this, but after I took down my blog there was no real trace of me. I could be anyone. I was just Lindsey. Not Lindsey the fashion blogger, just Lindsey.

Now you have permission to cut out what you don’t really like. I hated selling vintage clothing, which was part of how I made money with my blog. I would buy so many clothes so I could wear new items in my posts. It was very time consuming. Vintage reselling can be exploitative and I didn’t like that. I also really did not like the way I dressed anymore. My readers responded the best to very “true vintage” looks (all items at least 20 years old) and I had been over that for years. I liked vintage band tees, leopard print, and chain link necklaces at this point. When I wore different looks, my views went down. My collabs, how I made money, were usually with vintage-inspired fashion companies, so I couldn’t change my look or I would lose money. I didn’t feel like rebranding myself either. But I changed my style anyway.

When I quit blogging and influencing, I realized how unhappy I was. I was chasing cheap dopamine and working 24/7 to barely make ends meet, and while it was fun for a while, it was only for a while. 

Around December 2023, I went back “online” and started posting regularly on TikTok. I told myself it would always be about the things I say, what I want to wear, and what I want to write – never chasing paid sponsorship or selling clothes to my followers. Although, you cannot escape thinking about the algorithm if you are online and making money and funding a career. But I know the boundaries and what life is like when I’m not creating content. I specifically choose not to do “influencing” when coming online again because when I’m not trying to sell myself to brands, I can truly be myself. For me, creating content is a job, not a lifestyle. Ultimately, I’m building a life I just want to be in — online or not.

Download Firefox

Take control of your internet

The post What I learned when I stopped posting my life online, from a former influencer appeared first on The Mozilla Blog.

The Mozilla Thunderbird BlogThunderbird Pro August 2025 Update

In April of this year we announced Thunderbird Pro, additional subscription services from Thunderbird meant to help you get more done with the app you already use and love. These services include a first ever email service from Thunderbird, called Thundermail. They also include Appointment, for scheduling meetings and appointments and Send, an end-to-end encrypted filesharing tool. Each of these services are open source, repositories are linked down below.

Thunderbird Pro services are being built as part of the broader Thunderbird product ecosystem. These services are enhancements to the current Thunderbird application experience. They are optional, designed to enhance productivity for users who need features like scheduling, file sharing and email hosting, without relying on the alternate platforms. For users who opt in, the goal is for these services to be smoothly integrated into the Thunderbird app, providing a natural extension of the familiar experience they already enjoy, enhanced with additional capabilities they may be looking for. For updates on Thunderbird Pro development and beta access availability, sign up for the mailing list at thundermail.com

Progress So Far

Thundermail

Development has been moving steadily forward and community interest in Thundermail has been strong. The upcoming email hosting service from Thunderbird will support IMAP, SMTP and JMAP out of the box, making it compatible with the Thunderbird app and many other email clients. If you have your own domain, you’ll be able to bring it in and host it with us. Alternatively, grab an email address provided by Thunderbird with your choice of @thundermail.com or @tb.pro as the domains.  The servers hosting Thundermail will initially be located in Germany with more countries to follow in the future. Thunderbird’s investment in offering an email service reflects our broader goal of strengthening support for open standards and giving users the option to keep their entire email experience within Thunderbird. 

Thunderbird Appointment (Repo)

We originally developed the scheduling tool as a standalone web app. On the current roadmap, however, we’re tightly integrating Appointment into the Thunderbird app through the compose window, allowing users to insert scheduling links without leaving the email workflow. It will be easy for organizations and individuals to self-host, fork and adapt the tool to their own needs. The future is for Appointment to support multiple meeting types, like Zoom calls, phone meetings, or in-person coffee chats. Each of these will have its own settings and scheduling rules.

One of the most requested future features is group scheduling, which would allow multiple team members to offer shared availability via a single link. The current calendar protocols don’t fully support this flow, however Thunderbird is participating in discussions around open standards like VPOLL to help move things forward. Usability studies are helping refine the MVP and community feedback is shaping the roadmap.

Thunderbird Send (Repo)

A secure, end-to-end encrypted file sharing tool, built on Thunderbird app’s existing Filelink feature. It supports large file transfers directly from the email client. This allows users to bypass platforms like Google Drive or OneDrive. Pro users will receive 500 GB of storage to start, with no individual file size limit, only constrained by their total quota. We’re planning support for chunked uploads and encryption to ensure reliability and data protection. We’ll deliver Send as a system add-on which lets the team push updates faster. This also avoids locking new capabilities behind major Thunderbird release cycles.

All Thunderbird Pro tools are open source and self-hostable. For users who prefer to run their own infrastructure or work in regulated environments, both Send and Appointment can be deployed independently. Thunderbird will continue to support these users with documentation and open APIs.

A Look Ahead

Thunderbird is exploring additional Pro features beyond the current lineup. While we’ve made no commitments yet, there is strong interest in adding markdown based Notes functionality, especially as lightweight personal knowledge management becomes more popular. Heavier lifts like collaborative docs or spreadsheets may follow, depending on adoption and sustainability.

Another worthy mention: a fourth, previously announced service called Assist, which will eventually enable users to take advantage of AI features in their day-to-day email tasks, is still in the research and development phase. It will not be part of the initial lineup of services. This initiative is a bigger undertaking as we ensure we get it right for user privacy and make sure the features included are actually things our users want. More to come on this as the project progresses.

To improve transparency and invite community collaboration, Thunderbird is also preparing a public roadmap covering desktop, mobile and Pro services. We’re developing the roadmap in collaboration with the Thunderbird Council. Our goal is to encourage participation from contributors and users alike.

Free vs Paid

Adding these additional subscription services will never compromise the features, stability or functionality our users are accustomed to in the free Thunderbird desktop and mobile applications. These services come with real costs, especially storage and bandwidth. Charging for them helps ensure that users who benefit from these tools help cover their cost, instead of donors footing the bill. 

Thunderbird Pro is a completely optional suite of (open source) services designed to provide additional productivity capabilities to the Thunderbird app and never to replace them. The current Thunderbird desktop and mobile applications are, and always will be, free. They will still heavily rely on ongoing donations for both development and independence.

If you haven’t already, join our waiting list to be one of the early beta testers for Thunderbird Pro. While we don’t have a specific timeline just yet, we will be sharing ongoing updates as development progresses.

Ryan Sipes
Managing Director, Product
Mozilla Thunderbird

The post Thunderbird Pro August 2025 Update appeared first on The Thunderbird Blog.

hacks.mozilla.orgCRLite: Fast, private, and comprehensive certificate revocation checking in Firefox

Firefox is now the first and the only browser to deploy fast and comprehensive certificate revocation checking that does not reveal your browsing activity to anyone (not even to Mozilla).

Tens of millions of TLS server certificates are issued each day to secure communications between browsers and websites. These certificates are the cornerstones of ubiquitous encryption and a key part of our vision for the web. While a certificate can be valid for up to 398 days, it can also be revoked at any point in its lifetime. A revoked certificate poses a serious security risk and should not be trusted to authenticate a server.

Identifying a revoked certificate is difficult because information needs to flow from the certificate’s issuer out to each browser. There are basically two ways to handle this. The browser either needs to ask an authority in real time about each certificate that it encounters, or it needs to maintain a frequently-updated list of revoked certificates. Firefox’s new mechanism, CRLite, has made the latter strategy feasible for the first time.

With CRLite, Firefox periodically downloads a compact encoding of the set of all revoked certificates that appear in Certificate Transparency logs. Firefox stores this encoding locally, updates it every 12 hours, and queries it privately every time a new TLS connection is created.

You may have heard that revocation is broken or that revocation doesn’t work. For a long time, the web was stuck with bad tradeoffs between security, privacy, and reliability in this space. That’s no longer the case. We enabled CRLite for all Firefox desktop (Windows, Linux, MacOS) users starting in Firefox 137, and we have seen that it makes revocation checking functional, reliable, and performant. We are hopeful that we can replicate our success in other, more constrained, environments as well.

Better privacy and performance

Prior to version 137, Firefox used the Online Certificate Status Protocol (OCSP) to ask authorities about revocation statuses in real time. Certificate authorities are no longer required to support OCSP, and some major certificate authorities have already announced their intention to wind down their OCSP services. There are several reasons for this, but the foremost is that OCSP is a privacy leak. When a user asks an OCSP server about a certificate, they reveal to the server that they intend to visit a certain domain. Since OCSP requests are typically made over unencrypted HTTP, this information is also leaked to all on-path observers.

Having gained confidence in the robustness, accuracy and performance of our CRLite implementation, we will be disabling OCSP for domain validated certificates in Firefox 142. Sealing the OCSP privacy leak complements our ongoing efforts to encrypt everything on the internet by rolling out HTTPS-First, DNS over HTTPS, and Encrypted Client Hello.

Disabling OCSP also has performance benefits: we have found that OCSP requests block the TLS handshake for 100 ms at the median. As we rolled out CRLite, we saw notable improvements in TLS handshake times.

A graph showing "Median TLS Handshake Time (ms)" and "Revocation mechanism usage" over time. As the percentage of revocation checks performed with CRLite increases from 0% to 80%, the median TLS handshake time decreases from 56.4 ms to 39.9 ms.

Bandwidth requirements of CRLite

Users with CRLite download an average of 300 kB of revocation data per day: a 4 MB snapshot every 45 days and a sequence of “delta updates” in-between. (The exact sizes of snapshots and delta updates fluctuate day by day. You can explore the real data on our dashboard.)

To get a sense for how compact CRLite artifacts are, let’s compare them with Certificate Revocation Lists (CRLs). A CRL is a list of serial numbers that each identify a revoked certificate from a single issuer. Certificate authorities in Mozilla’s root store have disclosed approximately three thousand active CRLs to the Common CA Database. In total, these three thousand CRLs are 300 MB in size, and the only way to keep a copy of them up-to-date is to redownload them regularly. CRLite encodes the same dynamic set of revoked certificates in 300 kB per day. In other words, CRLite is one thousand times more bandwidth-efficient than daily CRL downloads.

Of course, no browser is performing daily downloads of all CRLs. For a more meaningful comparison, we can consider Chrome’s CRLSets. These are hand-picked sets of revocations that are delivered to Chrome users daily. Recent CRLSets weigh in at 600 kB and include about 1% of all revocations (thirty-five thousand of the four million total). Firefox’s CRLite implementation uses half the bandwidth, updates twice as frequently, and includes all revocations.

Including all revocations is essential for security as there is no reliable way today to distinguish security-critical revocations from administrative revocations. Roughly half of all revocations are made without a specified reason code, and some of these revocations are likely due to security concerns that the certificate’s owner did not wish to highlight. When reason codes are used, they are often used in an ambiguous way that does not clearly map to security risk. In this environment, the only secure approach is to check all revocations, which is now possible with CRLite.

State-of-the-art blocklist technology

You may recall a series of blog posts on our experiments with CRLite back in 2020. We followed these experiments with successful deployments to Nightly, Beta, and 1% of Release users. But the bandwidth requirements for this early CRLite design turned out to be prohibitive.

We solved our bandwidth issue by developing a novel data structure—the “Clubcard” set membership test. Where the original CRLite design used a “multi-level cascades of Bloom filters”, Clubcard-based CRLite uses a “partitioned two-level cascade of Ribbon filters”. The “two-level cascade” idea was presented by Mike Hamburg at RWC 2022, and “partitioning” is an innovation of our own that we presented in a paper at IEEE S&P 2025 and a talk at RWC 2025.

Future improvements

We are working on making CRLite even more bandwidth efficient. We are developing new Clubcard partitioning strategies that will compress mass revocation events more efficiently. We are also integrating support for the HTTP compression dictionary transport, which will further compress delta updates. And we have successfully advocated for shorter certificate validity periods, which will reduce the number of CRLite artifacts that need to encode any given revocation. With these enhancements, we expect the bandwidth requirements of CRLite to trend down over the coming years, even as the TLS ecosystem itself continues to grow.

Our Clubcard blocklist library, our instantiation of Clubcards for CRLite, and our CRLite backend are freely available for anyone to use. We hope that our success in building fast, private, and comprehensive revocation checking for Firefox will encourage other software vendors to adopt this technology.

The post CRLite: Fast, private, and comprehensive certificate revocation checking in Firefox appeared first on Mozilla Hacks - the Web developer blog.

Mozilla Add-ons BlogIntroducing the Firefox Extension Developer Awards Program

At Firefox, we deeply value the incredible contributions of our add-ons developer community. Your creativity and innovation are instrumental in making Firefox a more personalized and powerful browsing experience for millions of users worldwide.

Today, we’re thrilled to announce a new program designed to recognize and celebrate the developers who have made an outstanding impact on our ecosystem: the Firefox Extension Developer Awards Program!

Extensions play a vital role in enhancing the Firefox user experience. Almost 40% of Firefox users have installed at least one add-on, making it clear that our thriving ecosystem, supported by 10,000 active developers, is an essential component of the Firefox experience. While all developers contribute to the diversity and depth of the ecosystem, there are a number of popular extensions responsible for significant positive impact. This program aims to acknowledge and reward these developers for their significant contributions.

The Awards: A Token of Our Appreciation

Inspired by programs like YouTube’s creator awards, we’ve partnered with Aparat Design, to create a unique Mozilla inspired trophy for eligible award recipients.Firefox add-on developer award trophyThe award will be engraved with the name of the extension and finished with a different color based on the milestone it has achieved. This is a unique and exclusive opportunity available only to Firefox extension developers.

Milestone Tier Average Daily Active Users
Platinum Over 10 million
Gold Over 5 million
Silver Over 1 million
Bronze Over 500,000

How the program works

All Firefox extensions listed on AMO (addons.mozilla.org) are eligible for an award, so long as requisite user thresholds are reached and the content is compliant with Add-on Policies.

Each quarter, our team will identify new extensions that meet the award criteria and maintain a good standing with Firefox.

We’re incredibly excited about the Firefox Extension Developer Awards Program and look forward to celebrating your achievements! Stay tuned to this very blog for the announcement of our inaugural round of award recipients.

The post Introducing the Firefox Extension Developer Awards Program appeared first on Mozilla Add-ons Community Blog.

Open Policy & AdvocacyIs Germany on the Brink of Banning Ad Blockers? User Freedom, Privacy, and Security Is At Risk.

Across the internet, users rely on browsers and extensions to shape how they experience the web: to protect their privacy, improve accessibility, block harmful or intrusive content, and take control over what they see. But a recent ruling from Germany’s Federal Supreme Court risks turning one of these essential tools, the ad blocker, into a copyright liability — and in doing so, threatens the broader principle of user choice online.

Imagine you are watching television and you go to the kitchen for a snack during an ad break. Or you press the fast-forward button to skip some ads while listening to a podcast. Or perhaps you get a newspaper delivered to your house, and you see that it includes a special section made up of hallucinated AI content, so you drop the inset into the trash before taking the rest of the paper inside. Were these acts of copyright infringement? Of course not. But if you do something like this with a browser extension, a recent decision from the German Federal Supreme Court suggests that maybe you did infringe copyright. This misguided logic risks user freedom, privacy, and security.

There are many reasons, in addition to ad blocking, that users might want their browser or a browser extension to alter a webpage. These include changes to improve accessibility, to evaluate accessibility, or to protect privacy. Indeed, the risks of browsing range from phishing, to malicious code execution, to invasive tracking, to fingerprinting, to more mundane harms like inefficient website elements that waste processing resources. Users should be equipped with browsers and browser extensions that give them both protection and choice in the face of these risks. A browser that inflexibly ran any code served to the user would be an extraordinarily dangerous piece of software. Ad blockers are just one piece of this puzzle, but they are an important way that users can customize their experience and lower risks to their security and privacy.

The recent court ruling is the latest development in a legal battle between publisher Axel Springer and Eyeo (the maker of Adblock Plus) that has been winding its way around the German legal system for more than a decade. The litigation has included both competition and copyright claims. Until now Eyeo has largely prevailed and the legality of ad blockers has been upheld. Most significantly, in 2022, the Hamburg appeal court ruled that Adblock Plus did not infringe the copyright of websites but rather was merely facilitating a choice by users about how they wished their browser to render the page.

Unfortunately, on July 31, the German Federal Supreme Court partially overturned the decision of the Hamburg court and remanded the case for further proceedings. The BGH (as the Federal Supreme Court is known) called for a new hearing so that the Hamburg court can provide more detail regarding which part of the website (such as bytecode or object code) is altered by ad blockers, whether this code is protected by copyright, and under what conditions the interference might be justified.

The full impact of this latest development is still unclear. The BGH will issue a more detailed written ruling explaining its decision. Meanwhile, the case has now returned to the lower court for additional fact-finding. It could be a couple more years until we have a clear answer. We hope that the courts ultimately reach the same sensible conclusion and allow users to install ad blockers.

We sincerely hope that Germany does not become the second jurisdiction (after China) to ban ad blockers. This will significantly limit users’ ability to control their online environment and potentially open the door to similar restrictions elsewhere. Such a precedent could embolden legal challenges against other extensions that protect privacy, enhance accessibility, or improve security. Over time, this could deter innovation in these areas, pressure browser vendors to limit extension functionality, and shift the internet away from its open, user-driven nature toward one with reduced flexibility, innovation, and control for users.

The post Is Germany on the Brink of Banning Ad Blockers? User Freedom, Privacy, and Security Is At Risk. appeared first on Open Policy & Advocacy.

The Mozilla Thunderbird BlogThunderbird Monthly Development Digest – July 2025

Hello again from the Thunderbird development team! As the northern hemisphere rolls into late summer and the last of the vacation photos trickle into our chat channels, the team is balancing maintenance sprints with ongoing feature-related projects. Whether you’re basking in the sun or bundled up for a southern winter, we’ve got plenty to share about what’s been happening behind the scenes, and what’s coming next.

Exchange support

It’s been a whirlwind of progress since our last update and with the expanded team collaborating regularly. It has felt like we’ve hit our stride and the finish line is in sight. Driven by a dramatic increase in automated test coverage, the team has been able to detect gaps and edge cases to help improve many areas of the existing code, and close out a good number of bugs.

As we ready the feature set for wider release, we’ve taken the opportunity to revisit the backlog and feel confident enough with our pace to prioritize a few features and address them sooner than originally planned.

The July roadmap worked out very well, with our planned features landing and a number of bonus items also complete:

  • Automated test coverage
  • Message filtering
  • Setting as Junk/Not Junk
  • Remote content display/blocking
  • Callback modernization/simplification
  • Propagation of certificate and connection errors
  • Archiving
  • Saving Drafts
  • Back-off handling

Items we’ve prioritized for the next few weeks are:

  • Undo/Redo operations for move/copy/delete
  • Status Bar feedback messaging
  • Bug backlog

Keep track of feature delivery here.

Account Hub

A few users have reported issues following end user adoption of this feature, so we’re addressing these while finalizing Account Hub for Address Book items, such as LDAP configuration. The team is also planning the implementation of telemetry which will help us determine areas for improvement in this important part of the application.

Global Message Database [Panorama]

The team has been focused on Exchange implementation and larger scale refactoring which isn’t directly tied to this project, so no updates to note here. The next time I write will be during a work week that has been dedicated to “Conversation View”, which is one of the key drivers for our database overhaul. Stay tuned for updates and decisions coming out of that collaboration.

To follow their progress, take a look at the meta bug dependency tree. The team also maintains documentation in Sourcedocs which are visible here.

Maintenance, Recent Features and Fixes

August is set aside as a focus for maintenance, with half our team dedicated to inglorious yet important items from our roadmap. In addition to these items, we’ve had help from the development community to deliver a variety of improvements over the past month:

If you would like to see new features as they land, and help us squash some early bugs, you can try running daily and check the pushlog to see what has recently landed. This assistance is immensely helpful for catching problems early.

Toby Pilling

Senior Manager, Desktop Engineering

The post Thunderbird Monthly Development Digest – July 2025 appeared first on The Thunderbird Blog.

Open Policy & AdvocacyThe EU’s AI Act at One Year: Continuing to push for open-source AI and transparency

Saturday, August 2, marked the first anniversary of the entry into force of the EU AI Act, the EU’s contested landmark legislation putting in place rules for AI sold and deployed on its internal market. With a staggered timeline for when different rules take effect, Mozilla continues its work to ensure that the law’s implementation is a success. 

Beginning last week, the AI Act imposes new obligations for the developers of so-called “general-purpose AI models” (GPAI), that is, large AI models like OpenAI’s GPT, Google’s Gemini, or xAI’s Grok models (often also refered to as “foundation models”). Mozilla has long advocated for such rules to be included in the AI Act to ensure that large AI labs must play their part in making the technology they develop safer and more transparent and that due diligence obligations are not entirely passed down the value chain to smaller developers and deployers. These new rules include new transparency and disclosure mandates as well as obligations relating to GPAI developers safety and security practices.

To mark the occasion, Mozilla, in partnership with Hugging Face and Linux Foundation, published a guide for open-source AI developers aiming to help them navigate these rules. Amongst other questions, the guide explains what exactly constitutes a GPAI model or a “GPAI model with systemic risk”, what obligations developers need to meet, and when they might benefit from the AI Act’s exemptions for open-source AI. It builds on and synthesizes the recently adopted Code of Practice for GPAI developers as well as the European Commission’ newly published GPAI guidelines. The guide also includes an interactive flowchart meant to help developers on their AI Act “user journey”. This builds on Mozilla’s long-standing work advocating for better conditions for open-source AI development, including our advocacy to ensure that open-source developers receive proportionate treatment under the AI Act.

In addition, in late July, the European Commission also published a template for the “sufficiently detailed summary” that GPAI developers are now mandated to publish about the data used to train their AI models. While the template falls short of expectations in many respects, it does in parts mirror recommendations made by Mozilla building on our work in partnership with Open Future over the past year.

With additional rules taking effect over the course of the coming years and the European Commission building up its capacity to enforce them, work on the AI Act is not over — it is entering a new phase. Amid discussions of regulatory simplification, a potential revision of the AI Act in the context of the EU’s omnibus, and calls to “stop the clock” on enforcing the AI Act, Mozilla will continue its work to help make the AI Act’s implementation a success. This is grounded in our conviction that good regulation and innovation aren’t inherently contradictory, but rather complements when it comes to steering innovation in a direction that is beneficial to all.

The post The EU’s AI Act at One Year: Continuing to push for open-source AI and transparency appeared first on Open Policy & Advocacy.

The Mozilla Thunderbird BlogEngage Your Inbox with ‘Getting Things Done’

David Allen’s “Getting Thing Done” (GTD) system has been around for longer than Thunderbird! First published in a book of the same name in 2001, this approach to productivity is focused on freeing your brain from chaos, giving it “focus, clarity, and confidence” for creativity and new ideas. As I’m also a fan of freedom from chaos, I decided to dive back into our productivity blogs and highlight how to use tags and keyboard shortcuts to use GTD in Thunderbird.

Five Steps to Get Things Done

To start, let’s summarize the GTD system, for anyone who might not be familiar. GTD uses five key steps to go from unorganized to unstoppable, whether in your inbox or elsewhere: Capture, Clarify, Organize, Reflect, and Engage.

Let’s think about these steps in terms of managing your inbox! First, Capturing involves collecting the things that have your attention. In other instances, this could mean brainstorming a to-do list. For email, this means your inbox. Clarifying entails taking those items and figuring out what they mean. For the Getting Things Done system, you need to figure out if you can act on something (for example, an email) or not. If it’s not actionable, where does it needs to go Is this reference? Is this on hold for some reason? Or can it just go in the trash?

Once this clarifying is done, it’s time to Organize, aka putting the things that have your attention or reminders of them in a place you can act on, whether that’s now or later. Reflecting isn’t a one-time step, but something you do consistently to fine-tune your system and make sure it’s still working for you.

All of these steps make the last step, Engaging, possible. You have a system you can trust, honed through reflection. Your inbox management system is like a starship where everything and everyone is working together, efficiently and effectively. This frees up your brain so your brain can soar through a cosmos of deep, interesting, meaningful work. Maybe while drinking a cup of tea, Earl Grey, hot.

Using Tags and Keyboard Shortcuts to Clarify and Organize Your Inbox

Adapting the GTD system to your Thunderbird inbox takes advantages of two features I am coming to love: labels and keyboard shortcuts.

I’m going to suggest three initial labels, and a few possibilities for labels for non-actionable emails, and walk you through how to set up the labels and use the keyboard shortcuts to apply them – with screenshots!

First, go into Settings > General > Tags to create/adjust your tags. The four example tags we set are “Do Now,” “Do,” “Waiting For,” and “Later.”

Wait, why have a “Do Now” and “Do” tag? This tip came from Henk Postma’s blog, who gave me a lot of inspiration. “Do Now” is urgent, and it needs doing without delay. “Do” doesn’t have this urgency, but the email is actionable.

The “Waiting For” label means there’s something you need to act on this email. Maybe it’s more information, or permission. This label can keep hold those emails until you’re ready. The “Later” tag is a bit of a catch-all. Like reference information, or things you’re interested in but can’t pursue yet. Maybe you want to break down your “Later” labels. The choice is yours!

Now that we have our labels set up, and associated with a number, we’re ready to start organizing. Once a message comes in, click the number for the tag you want. If you accidentally press the wrong number, don’t worry! Just press ‘0’ to clear whatever label you applied.

And that’s it! Well, except putting your system into practice, and David Allen has some further advice on using GTD in your inbox. If you have any tips on how you make your email organization a habit and not an afterthought, I’d love to hear them! As always, if there’s a productivity topic you’d like me to explore, let me know in the comments!

The post Engage Your Inbox with ‘Getting Things Done’ appeared first on The Thunderbird Blog.

Mozilla Add-ons BlogWarning: Phishing campaign detected

The developer community should be aware we’ve detected a phishing campaign targeting AMO (addons.mozilla.org) accounts. Add-on developers should exercise extreme caution and scrutiny when receiving emails claiming to be from Mozilla/AMO. Phishing emails typically state some variation of the message “Your Mozilla Add-ons account requires an update to continue accessing developer features.”

In order to protect yourself and keep your AMO account secure, we strongly recommend that you:

  1. Do not click any links in the email.
  2. Verify the email was sent by a Mozilla-owned domain: firefox.com, mozilla.com, mozilla.org, mozillafoundation.org (or their subdomains).
  3. Ensure that the email passes SPF, DKIM, and DMARC checks (consult your email provider and/or email client’s support documentation for details).
  4. Validate that links in the email point to firefox.com, mozilla.com, mozilla.org, mozillafoundation.org (or their subdomains) before opening them; even better, navigate directly to these domains rather than clicking a link via email.
  5. Only enter your Mozilla username and password on Mozilla-owned domains.

For more information on how to detect and report phishing scams, please see these helpful guides from the U.S. Federal Trade Commission and the U.K. National Cyber Security Centre, or consult your local government.

If we uncover more details to share we’ll update this post accordingly.

The post Warning: Phishing campaign detected appeared first on Mozilla Add-ons Community Blog.

The Mozilla Thunderbird BlogMonthly Release 141 Recap

We’re launching a brand new series that will highlight features and improvements with Thunderbird 141.0 – your front row ticket to Thunderbird’s monthly enhancements! (No more waiting in the wings so to speak). Learn what’s new, why it matters, and how it’ll transform your inbox experience.

In March, we introduced a new monthly Release channel and swapped it as the default option on the Thunderbird.net downloads page.

As a quick refresher, Thunderbird now offers two core release channel options:

  1. Release Channel: Updated monthly with new features, performance boosts, and bug fixes as they land.
  2. ESR (Extended Support Release): Receives all of the above in one major annual update, focusing on stability, with point security and stability patches in between.

While both versions are equally stable, the Release channel provides faster access to cutting-edge tools and optimizations, while the ESR channel may provide more stability when using add-ons with Thunderbird.

Feedback on the Release channel has been overwhelmingly positive, with many users transitioning from ESR. To join them:

Now that we’ve gotten the formalities out of the way, let’s jump in to what’s new in 141.0!

New Features

Warning for Expiring PGP Keys

Thunderbird loves PGP like cats adore cardboard boxes! We prioritize user trust by making end-to-end encrypted email simple for everyone, from newcomers to experienced users. To help you get started or refresh your knowledge, our team and volunteers have written an excellent introduction to the topic, as well as a How-to and FAQ.

Key expiration serves as a security safeguard, requiring proactive renewal procedures that reinforce operational encryption competencies.

What changed:

  • Your warning light is lit: If your public key expires in 31 days, Thunderbird now flashes a red alert in the compose window. No post-expiry panic!

Why it matters:

  • Safety net: A key that auto-expires nudges you to refresh it.
  • Piece of mind: Before Thunderbird told you after-the-fact your key died. Now? Your inbox is proactive.

Archive from OS Notifications

The improvements to native notifications keep coming. Now, in addition to deleting a message, marking it as spam, or starring it, you can archive a message directly from your operating system’s notifications. 

By default, the notifications you see include “Mark as Read” and “Delete”, however they can be customized further by going to Thunderbird Settings → General→ Incoming Mails and clicking on Customize.

Here you can select the information you want to see in your notification, as well as the actions you’d like to perform with it.

What changed:

  • New mail notifications have added the ‘Archive’ action.

Why it matters:

  • No need to go into the Thunderbird app to archive an incoming email now. More actions in notifications give you time to do the things you want, instead of managing your inbox.

Bug Fixes

Prioritize Link Hover URL in Status Bar

Thunderbird includes numerous features to protect you from suspicious mail and bad actors. One of these tools involves checking the URL of a link by hovering your mouse over the link text. The status bar would display the link URL, but it could be overwritten in fractions of a second by “Downloading message” and “Opening folder” messages. We’ve fixed this, and now the URL you’re hovering over will get priority in the status bar.

What changed:

  • Hovering over a link in an email will display it in the status bar without being immediately overwritten by other messages.

Why it matters:

  • Knowing where an email wants to send you is a major security boost, especially with the widespread threat of phishing emails.

Dots, Dashes, and Advanced Address Book Search

Three months ago, a community member noted that while the CardBook add-on could find phone numbers that used dots for separators, the Advanced Address Book Search in Thunderbird could not. Since we want users to be able to find contacts, and use the phone number formatting they want as well, we’ve built this ability into Thunderbird.

What changed:

  • The advanced address book in Thunderbird now recognizes phone numbers that use dots for separators.

Why it matters:

  • Saves time: Finds contacts faster and more accurately, no matter their format or storage location, eliminating need for manual cleanup or repeat searches.

Performance Improvements

Message List Scroll

To address message list scrolling performance, we adjusted how new rows are rendered but inadvertently introduced display delays. We’re reverting to the original row-handling method to properly assess performance impact before considering this change for Extended Support Release adoption. This allows precise measurement of optimizations against potential trade-offs, ensuring reliable performance in production environments.

What changed:

  • Reverting back to the previous method for how rows are updated.

Why it matters:

  • To accurately measure how the update affects scrolling performance before considering inclusion in an ESR.

The post Monthly Release 141 Recap appeared first on The Thunderbird Blog.

Mozilla L10NL10n Report: July Edition 2025

Please note some of the information provided in this report may be subject to change as we are sometimes sharing information about projects that are still in early stages and are not final yet. 

Welcome!

New localizers

Are you a locale leader and want us to include new members in our upcoming reports? Contact us!

What’s new or coming up in Firefox desktop

Where’s Firefox Going Next?

Before getting into all the new features that recently landed in Nightly, we’re trying something new and would love your help. Check out this thread over on Mozilla Connect where you can help Firefox’s product managers plan their upcoming AMA (Ask Me Anything) by letting them know what you’ve always wanted to ask the Firefox team and which topics should be covered during the AMA.

Trust Panel

Available to translate and test in Nightly, the trust panel is a new feature designed to communicate to users what Firefox is doing to protect their privacy in friendly and easy to understand language. To check the feature out and review your translations, make sure to update your Nightly to the latest version (143) then navigate to “about:config” by typing it into your URL bar, click past the warning, then search browser.urlbar.trustPanel.featureGate and toggle the value to true.

Navigate to a website and the icon will appear on the side of your URL bar.

Firefox address bar showing a shield icon to access the trust panel.Clicking on it will show you the trust panel with a friendly Firefox letting you know you’re protected!

Screenshot of the new unified trust panel in Firefox, displayed when clicking the shield icon.Profile Icons

Also recently landed was a large number of strings related to icons users can set as part of the recently added profiles feature. While we tried to make the comments as helpful as possible, there’s no substitute for seeing the image in context. You can check the icons out within Nightly yourself by editing or creating a new profile by clicking the Account button on your toolbar and selecting the Profiles menu. Or, you can refer to the following image with a screenshot and the associated name used in the string IDs.

Screenshot of new profile icons and their accessible names.Text Fragments

You can now test the text fragments creation UI (these strings were added a few months back, but they have just been activated in Firefox Nightly). This feature allows you to share/reference a link anchor to any text snippet in a page. See the team’s post about this feature here.

What’s new or coming up in mobile

The menu settings on Firefox for Android and iOS are being redesigned, which requires updates to some strings. Stay tuned as more are coming in!

What’s new or coming up in web projects

Firefox.com

The new Firefox.com site officially launched earlier this month following a soft launch period, which allowed time to identify and resolve any initial issues. Thank you to everyone who reported bugs during that time. Most of the content on the new site was copied from Mozilla.org. However, the team plans to remove duplicated pages over the next few months except for a few that will remain on both sites, such as the Thank You page. More substantial updates are planned for later this year and beyond.

What’s new or coming up in Pontoon

Unified plurals UI

We’ve updated how plural gettext (.po) messages are handled in Pontoon. Specifically, they now use the same UI we’ve already been using for Fluent strings.

We’d really appreciate your feedback! To explore the new plural editor, try searching for strings that include .match, which commonly contain plural forms. We’re especially interested in whether the new experience feels intuitive and “right”, and — most importantly — if you manage to break it.

Screenshot of UI in Pontoon showing a string with plurals in a gettext based projectNew REST API Now Available

We’re excited to announce that Pontoon now offers a new REST API, built with Django REST Framework! This API is designed to provide a more reliable and consistent way to interact with Pontoon programmatically, and it’s already available for use.

You can explore the available endpoints and usage examples in the API README.

GraphQL API Scheduled for Deprecation

As part of this transition, we’ll be deprecating the Pontoon GraphQL API on November 5th, 2025. If you’re currently using the GraphQL API, we strongly encourage you to begin migrating to the new REST API, which will become the only supported interface going forward.

If you have any questions during the transition or run into issues, please don’t hesitate to open a discussion or file an issue. We’re here to help!

Events

Want to showcase an event coming up that your community is participating in? Contact us and we’ll include it.

Friends of the Lion

Image by Elio Qoshi

Know someone in your l10n community who’s been doing a great job and should appear here? Contact us and we’ll make sure they get a shout-out!

Useful Links

Questions? Want to get involved?

If you want to get involved, or have any question about l10n, reach out to:

Did you enjoy reading this report? Let us know how we can improve it.

The Mozilla Thunderbird BlogState of the Thunder: Answering Community Questions!

For the past few months, we’ve been talking about our roadmaps and development and answering community questions in a video and podcast series we call “State of the Thunder.” We’ve decided, after your feedback, to also cover them in a blog, for those who don’t have time to watch or listen to the entire session.

This session is focused on answering inquiries from the community, and we’ve got the questions and summaries of the answers (with helpful links to resources we mentioned)! This series runs every two weeks, and we’ll be creating blogs from here on in. If you have any questions you’d like answered, please feel free to include them in the comments!

Supporting and Sustaining FOSS Projects We Use

Question: As we move toward having more traditionally commercial offerings with services that are built on top of other projects, what is our plan in helping those projects’ maintenance (and financial) sustainability? If we find a good model, can we imagine extending it to our apps, too?

Answer: Right now, the only project we’re using to help build Thunderbird Pro is Stalwart, and we’ll have more details on how we’re using it soon. But we absolutely want to make sure the project gets financial support from us to support its sustainability and well-being. We want to play nice!

Appointment and Assist are from scratch, and Send is from old Firefox code, and so there isn’t another project to support with those. But to go back to a point Ryan Sipes has frequently made, while people can use all of these tools for free by self-hosting, they can subscribe as a way of both simplifying their usage and making sure these projects are supported for regular maintenance and a long life.

Future UI Settings Plans

Question: The interface is difficult to customize but more importantly is difficult to discover all the options available because they’re scattered around settings, account settings, top menu bar, context menus, etc. 140 Introduced the Appearance section in the settings, any plans to continue this effort with some more drastic restructuring of the UI?

Answer: Yes, we do have plans! We know the existing UI isn’t the most welcoming, since it is so powerful and we don’t want to overwhelm users with every option they can configure. We have a roadmap that’s almost ready to share that involves restructuring Account Settings. Right now, individual settings are very scattered, and we want to group things together into related sections that can all be changed at the same time. We want to simplify discoverability to make it easier to customize Thunderbird without digging into the config panel.

Account Setup and Manual Configuration

Question: Using manual configuration during email setup has become more difficult with time with the prioritization of email autoconfiguration.

Answer: Unfortunately, manual setup has confused a lot of casual users, which is why we’ve prioritized autodiscovery and autosetup. We’ve done a lot of exploration and testing with our Design team, and in turn they’ve done a lot of discussion and testing with our community. You can see some of these conversations in our UX mailing list. And even if you have to start the process, there is a link in it to edit the configuration manually. Ultimately, we have to have a balance between less technical and more technical users, and to be as usable and approachable as we can to the former.

Balancing Complexity and Simplicity

Question: Thunderbird is powerful with a lot of options but it should have more. Any plans to integrate ImportExportTools  (and other add-ons) and add more functionalities?

Answer: Thunderbird’s Add-ons are often meant for users who like more complexity! When we tackle this question, there’s two issues that come to mind. First, several developers get financial support from their users, and we want to be mindful of that. Second is the eternal question of how many features are too many features? We already have this issue in feedback between “Thunderbird doesn’t have enough features” and “Thunderbird is too complicated!” Every feature we add gives us more technical debt. If we bring an add-on into core, we can support it for the long term.

We think this question may also come from the fact that Add-ons often “break” with each ESR release. But we’re trying to find ways to support developers to use the API to increase compatibility. We’re also considering how we can financially support Add-on developers to help them maintain their apps. Our core developers are pressed for time, and so we’re beyond grateful to the Add-on developers who can make Thunderbird stronger and more specialized than we could on our own!

Benefits of the New Monthly Release Channel

Question: Is the new Release channel with monthly versions working properly and bringing any benefits?

Answer: Yes, on both counts! Right now, we have 10 to 20 percent of Thunderbird desktop users on the Release channel. While we don’t have hard numbers for the benefits YET, we’d love to get some numbers on improvements in bug reactivity and other indicators. We noticed this year’s ESR had far fewer bugs, which probably owed to Release users testing new features. While we’ve always had Beta users, we have so many more people on Release. So if something went wrong, we could fix it, let it “ride the train,” and have the fix in the next version.

And our developers have stopped wondering when our features will make it to users! Things will be in users’ hands in a month, versus nearly a year for some features.

JMAP Support in Thunderbird

Question: Any plans on supporting JMAP?

Answer: 100% yes. Though JMAP is still something of a niche protocol, with doesn’t yet have widespread support from major providers. But now, with Thundermail we’ll be our own provider, and it will come with JMAP. Also, with the upcoming iOS app, it will be easy to add support for JMAP. First, we’re making the app from scratch so we have no technical debt. Second, we can do things properly from the start and be protocol agnostic.

Also, we’ve taken several lessons from our Exchange implementation, namely how to implement a new protocol properly. This will help us add support for JMAP faster.

Maintaining Backups in Thunderbird

Question: I have used Thunderbird since its first release and I always wondered how to properly and safely maintain backups of local emails. No matter how much I hate Outlook it offers built-in backup archives of .pst files that can be moved to other installations. The closest thing in Thunderbird is to copy the entire profile folder, but that comes with many more unpredictable outcomes.

I might be asking for something uncommon but I manage many projects with a very heavy communication flow between multiple clients, and  when the project is completed I like to export the project folder with all the messages into a single PST file and create a couple of back-ups for safety, so no matter if my email server has problems, or the emails on my server and computer are accidentally deleted, I have that folder back-up as a single file which I can import into a new installation.

Answer: We’d love for anyone with this question to come talk to us about how to improve our Import/Export tools. Unfortunately, there’s no universal email archive format, and a major issue is that Outlook’s backup files are in a proprietary format. We’ve rebuilt the Import/Export UI and done a bit on the backend. Alas, this is all we’ve had time for.

So, if you’d like to help us tackle this problem, come chat with us! You can find us on Matrix and in the Developers and Planning mailing lists. We think there’s definitely room for a standard around email backups.

Watch the Video (also available on TILvids)

Listen to the Podcast

The post State of the Thunder: Answering Community Questions! appeared first on The Thunderbird Blog.

Open Policy & AdvocacyOpen by Design: How Nations Can Compete in the Age of AI

The choices governments make today, about who gets to build, access and benefit from AI, will shape economic competitiveness, national security and digital rights for decades.

A new report by UK think tank, Demos, supported by Mozilla, makes the case that if the UK wants to thrive in the AI era it must embrace openness. And while the report is tailored to the UK context, its implications reach far beyond Westminster.

Unlike the US or China, the UK and many other countries cannot outspend or outscale on AI, but they can out-collaborate. Demos’ report The Open Dividend: Building an AI openness strategy to unlock the UK’s AI potential, argues that making key AI resources – models, datasets, compute and safety tools, more openly accessible can spur innovation, lower the costs of AI adoption, enable safer and more transparent development, boost digital sovereignty and align AI more closely with public value. A recipe, if there ever was one, for ‘winning’ at AI.

The wider market certainly reflects these trends – the AI sector is shifting toward value accruing in smaller, specialised and more efficient models. Developments all spurred on by open source innovation. But this also means open models aren’t just more accessible and customisable, they’re becoming more capable too.

This echoes another recent study Mozilla supported, this time a survey of more than 700 businesses conducted by McKinsey. Among its top findings – 50% of respondents are already leveraging an open source solution across their stack. More than three-quarters reported that they intended to grow this usage. Most significantly, the first movers – organisations that see AI as vital to their future competitive advantage – are more than 40% more likely to use open source models and tools than respondents from other organisations. Similar research just published by the Linux Foundation has also found openness is fast becoming a competitive edge. Demos’s report expands upon these stats – strategically utilising openness in AI is not just about sharing code, it’s about shaping a more resilient and prosperous ecosystem.

The risks of centralisation are well known and global. We have seen it before with the development of the internet. If we let AI ecosystems become concentrated, so that all power remains in the hands of a few firms and their proprietary models, this will make it much harder to ensure AI serves people – rather than the other way around. It also raises more urgent concerns about market dominance, bias, surveillance, and national resilience.

If we want AI to serve humanity, we all have a stake in getting this right.

As the Demos report argues, openness isn’t just a value – it’s a strategy. We were proud to support the development of this timely report – read it here.

The post Open by Design: How Nations Can Compete in the Age of AI appeared first on Open Policy & Advocacy.

The Mozilla Thunderbird BlogWelcoming New Faces to the Thunderbird Community Team

Community First

Thunderbird is (and has always been) powered by the people. The project exists because of the amazing community of passionate code contributors, bug-bashers, content creators, and all-around wonderful humans who have stood behind it and worked to support and maintain it over the years.

And as the Thunderbird community grows, we want to ensure that we [the team supporting you] grow alongside you, so that we can continue to collaborate and build effectively and efficiently together. 

That’s why we’re thrilled to announce a refreshed and growing Thunderbird Community Team here at MZLA! Expect a little more structure, a lot more collaboration, and an open invitation to our users and contributors to join us and help shape what comes next.

Meet the Team

Whether you’re filing your first bug, searching for support, writing documentation, or just dropping into Matrix to say hi, this is the team working hard behind the scenes to make sure your experience is productive, constructive, and superconductive:

Michael Ellis | Manager of Community Programs

Hey there! I’m Michael, and I’m joining the Thunderbird family as Manager of Community Programs to help grow and support our awesome community. I’ll be working on programs that help improve contributor pathways and make it easier for more people to get involved in the work we do and the decisions we make on a day-to-day basis.

I come from a background of managing developer communities and running large-scale programs at organizations like Mozilla, Ionic, and NXP Semiconductors. I believe open-source communities are strongest when they’re welcoming, engaging, and well-supported. I like gifs and memes very much. 

I look forward to seeing you in the Thunderbird community and saying hello to one another on Matrix!  

Until then, Keep on Rocking the Free Web!

Wayne Mery | Senior Community Manager

Greetings everyone.  Wayne here, also known as wsmwk.  I have used open source for forty years, been a user of and contributor to Thunderbird for twenty years, and am a founding member of the Thunderbird Council, and have run several of the council elections. 

I love to mentor and connect to our community members who assist Thunderbird users in Reddit, Connect, matrix (chat), bugzilla, github, topicbox forums, Thunderbird support in SUMO (SUpport MOzilla), and other venues.  And I help manage these venues and assist users, to bring the concerns of the user community to developers.  I also assist in developing content for users (including knowledge base articles in SUMO) and assist in our general communications with users.  

There are many ways you can participate in small ways or large, including through praise or constructive feedback through the venues listed above and those listed on our participate web page – I encourage you to do so at your convenience. And I look forward to connecting with you soon. 

Heather Ellsworth | Senior Developer Relations Engineer

Hi everyone! *waves*

I’ve been part of the Thunderbird family for nearly two years, working with the awesome Desktop team. Now, I’m thrilled to be joining the Community team, led by Michael, where I’ll be focusing on initiatives to support and grow our amazing contributor community.

My work will include creating helpful video content to make it easier for folks to get started, as well as improving our technical documentation at source-docs.thunderbird.net and developer.thunderbird.net.

If you’re interested in contributing or need help getting started, don’t hesitate to reach out to me on Matrix — I’d love to chat!

What’s the Road Ahead?

Community is at the heart of everything Thunderbird does. As our product continues to evolve and improve, we want our community experience to keep pace with that growth. This means not only working to keep Thunderbird open, but striving towards better contributor pathways, clearer communication, and more opportunities to participate.

We’re here to listen, collaborate, and help you succeed. You can expect to see more initiatives, experiments, and outreach from us soon, but you don’t have to wait till then to weigh in.

Have thoughts or suggestions? Drop a comment below to share them directly, or visit our Connect thread to see what others are saying and add your own ideas there. Together, we can help shape the future of the Thunderbird community and product.

After all, Thunderbird is powered by the people, & that includes you.

The post Welcoming New Faces to the Thunderbird Community Team appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogVIDEO: Thunderbird 140.0 ESR “Eclipse”

Welcome back to another edition of the Community Office Hours! This month, we’re taking a closer look at Thunderbird 140.0 ESR “Eclipse,” our latest Extended Support Release! Sr. Manager of Desktop Engineering Toby Pilling (who so helpfully provides the Thunderbird Monthly Development Digest) is walking us through the latest Thunderbird. He’ll let us know what’s in, what’s out, and why you should give the new monthly Release channel a try. We’re also introducing a new member of the Thunderbird Team, Manager of Community Programs Michael Ellis.

Michael (and the Thunderbird team!) are here to listen, collaborate, and help you succeed. You can expect to see more initiatives, experiments, and outreach from us soon, but you don’t have to wait till then to weigh in. Have thoughts or suggestions on how to improve the community? Drop a comment below to share them directly, or visit our Connect thread to see what others are saying and add your own ideas there. Together, we can help shape the future of the Thunderbird community and product.

Next month, we’ll be talking with Product Design Rebecca Taylor and Associate Designer Solange Valverde to talk about our team’s recent efforts to make Thunderbird more accessible. This not only involves seeing where we’re doing well, but finding where we’re falling short. It’s been a while since we’ve talked about Accessibility here, and we’re excited to continue the conversation. If you have questions about Accessibility in either the desktop or Android app you’d like us to ask our guests, please leave them as a comment below!

July Office Hours: Thunderbird 140.0 ESR “Eclipse”

As Toby shows us in his introduction, the major theme of Thunderbird 140.0 ESR “Eclipse” is stability. We took lessons from last year’s ESR, when we introduced code to 128.0 that was a little harder to test than expected given when it landed. We’re also waiting on some major changes in the works, namely the refreshed Calendar UI and the database backend rewrite. This was, every feature that made it to this year’s ESR was fully baked.

What’s In

And there’s a lot of features to discuss! Toby walks through what’s new in 140.0, starting with a trio of visual improvements. Thunderbird now adapts the message window to dark mode, and provides a toggle to switch dark mode off in case of styling issues. In the new Appearance Settings, users can globally take control of their message list, toggling between Cards and Table View, Threaded and Unthreaded, and Grouped by Sort across all their accounts. This feature also allows switching Cards View between a 2 and 3 row preview, and to propagate default sorting orders to all folders. Finally, a community-powered and staff-supported feature allows users to reorder user-created folders by manually dragging and dropping them.

140.0 ESR Also introduces the Account Hub, which we covered in a previous Office Hours! You’ll see this when you add a second account, and it will seamlessly walk you through setting up not only your email, but connected address books and calendars.

To help maximize your time and minimize your clicks, Thunderbird now uses Native Notifications for Linux, Mac, and Windows. While for now you can delete messages and mark them as read directly from notifications, we have more actions up our sleeve, coming soon to the monthly Release channel!

Finally, we close out our new features. Experimental Exchange Support, which can be enabled via preference, introduces native Exchange email support to desktop Thunderbird. Though for a fully supported experience, we encourage you to switch to the monthly Release channel, where more Exchange improvements are coming. Export for Mobile allows you to generate a QR code to import your account configurations and credentials into the Thunderbird Android app. And Horizontal Scroll for Table View allows you to scroll the message list horizontally and read complex tabular data more like a spreadsheet.

What’s Out

But for everything we put in to 140.0 ESR, we had to leave some things out. Experimental Exchange Support only includes email, not calendar or address books. We also don’t yet support Graph API. Additionally, 140.0 ESR doesn’t include a new UI for Tasks, Chat, or Settings. Account Hub won’t be enabled for first-time user experiences in ESR, though this will be coming to monthly Release, as will the new Account Hub for Address Books.

Try the Monthly Release Channel

While we’re excited and proud to introduce Thunderbird 140.0 ESR “Eclipse,” we also hope you’ll try out new monthly Release channel. Read more about it and learn how you can get new features faster in our announcement.

Watch, Read, and Get Involved

Thanks for reading, and as always, you can learn more by watching the video (with handy chapter markers, if you just want to hear about your favorite new feature) and reading the presentation slides. If you’re looking to get involved with the community, from QA to support to helping develop new features, check out our “Get Involved” page on our website. You can also check out the specific resources below! See you all next month.

VIDEO (Also on Peertube):

Slides:

Resources:

  • Thunderbird UX Mailing List: https://thunderbird.topicbox.com/groups/ux
  • Interested in the Thunderbird Accessibility Committee? Email laurel@thunderbird.net
  • Suggest new features: https://connect.mozilla.org
  • Account Hub Office Hours blog: https://blog.thunderbird.net/2025/04/video-the-new-account-hub/
  • Manual Folder Sort Bug (and Community Development): https://bugzilla.mozilla.org/show_bug.cgi?id=1846550
  • Exchange Support Wiki: https://wiki.mozilla.org/Thunderbird:Exchange
  • Get Involved With Exchange: email heather@thunderbird.net
  • Thunderbird + Rust Office Hours Playlist: https://www.youtube.com/playlist?list=PLMY3ZzVsXXyqN6yL9Snm6W19WhBPntj1Z
  • QR Code Import Knowledge Base Article: https://support.mozilla.org/kb/thunderbird-android-import
  • Release Channel Blog: https://blog.thunderbird.net/2025/03/thunderbird-release-channel-update/

The post VIDEO: Thunderbird 140.0 ESR “Eclipse” appeared first on The Thunderbird Blog.

Open Policy & AdvocacyA pivotal moment for the UK in digital competition: Lead from the front or let the opportunity slip?

Mozilla’s open letter to the UK’s Secretary of State for Business and Trade, the Secretary of State for Science, Innovation and Technology, and the CEO of the CMA  

Rt Hon Peter Kyle MP, Department for Science, Innovation and Technology

Rt Hon Jonathan Reynolds MP, Department for Business and Trade

Sarah Cardell, Chief Executive Officer, Competition and Markets Authority

23 July 2025

Dear Secretaries of State and Chief Executive Officer,

At present a small handful of companies dominate our digital lives, limiting our experiences and stifling competition and innovation. Today’s provisional decisions from the Competition and Markets Authority (CMA) to designate Google and Apple as having “Strategic Market Status” in mobile ecosystems is a crucial step towards changing that: giving people genuine choice online and bringing renewed dynamism to the UK’s digital economy via the Digital Markets, Competition and Consumers Act (DMCCA).

Well-designed regulation like the DMCCA can be a boon to economic growth, lowering the barriers to entry and thus facilitating investment and innovation from both domestic and international companies and developers. We have experienced first hand the impact of ex ante competition regulation: since the obligations of the EU’s Digital Markets Act (DMA) came into force over a year ago Mozilla has seen iOS daily active users in the EU grow by 100% with extremely high rates of retention — evidence that when given real choice, people choose independent products like Firefox and they stick with them. Mozilla also saw a 20% increase in daily Firefox Android users, despite a more inconsistent rollout of browser choice screens.

Why This Matters: When Choice Disappears, Innovation Stalls

Challenging seemingly untouchable giants by offering choice and innovation is in Mozilla’s DNA. When Firefox 1.0 was introduced, it gave people tabbed browsing, pop-up blocking and speed that revolutionised their experiences online — all powered by Mozilla’s browser engine, Gecko.

Recent years have seen major operating systems engage in self-preferencing tactics designed to keep out competition. iOS users could not even change their default browser until 2020. Even then, all iOS browsers are still forced to be built on Apple’s WebKit browser engine. On Android, users are not yet able to reap the full browser choice benefits of the EU DMA, with the selected browser not given full default placement. Meanwhile, Windows users are also regularly faced with deceptive tactics designed to undermine their browser choice.

Such tactics mean people cannot easily choose independent options like Firefox. The lack of competition online leads to people losing out through reduced quality, restricted choice, and worse privacy outcomes.

A Moment for UK Leadership

Despite intense lobbying from the largest technology companies, Parliament acted with cross-party support in 2024 to promote digital competition by passing the DMCCA, recognising that it “stimulates innovation across the economy and helps to drive productivity growth, ultimately raising living standards.”

In the CMA, the UK has an expert regulator with specific market knowledge from investigations into mobile ecosystems and browser competition. It has a track record of unlocking innovation by opening markets, such as with open banking. Other jurisdictions are watching closely and can follow the UK’s successes.

We have already seen the impact the EU DMA can have for consumers. The DMCCA has the potential to be even more effective, giving the UK “second mover advantage” with flexible and targeted interventions. We are also now seeing other countries around the world look to follow the UK’s lead in passing new digital competition laws, while in the US there is a clamour from challenger firms and investors to introduce similar frameworks to level the playing field. As such, this is a chance for the UK to lead, delivering surgical remedies, ensuring real choice for consumers and demonstrating that a level playing field for businesses is possible.

A Shared Responsibility

We cannot simply rely on the goodwill of designated firms to deliver these benefits. The experience from the first year of the DMA suggests they will fight to make the DMCCA fail and use it as an example of why intervention does not work.

Without swift action, operating system providers will continue to entrench their positions and squeeze out alternatives. For UK businesses trying to break into digital markets, interventions must be both timely and effective.

As an organisation that exists to create an internet that is open and accessible to all, Mozilla has long supported competitive digital markets. The DMCCA’s success is a shared responsibility: challenger companies, civil society, academics and researchers are playing their part. We ask that the CMA and the government seize this once-in-a-generation opportunity to deliver choice, competition and economic growth for UK consumers.

Yours sincerely,

Linda Griffin, VP Global Policy

Kush Amlani, Director, Global Competition & Regulation

Mozilla is the non-profit backed technology company that champions privacy, human dignity, and an open internet. Our mission is to ensure the internet is a global public resource, open and accessible to all.

The post A pivotal moment for the UK in digital competition: Lead from the front or let the opportunity slip? appeared first on Open Policy & Advocacy.

Mozilla Gfx TeamShipping WebGPU on Windows in Firefox 141

After years in development, we will be releasing WebGPU on Windows in Firefox 141! WebGPU gives web content a modern interface to the user’s graphics processor, enabling high-performance computation and rendering. We’re excited about WebGPU because we believe it will raise the ceiling for games, visualization, and local computation on the web.

You can find a tutorial on WebGPU at webgpufundamentals.org, try out the WebGPU Samples, and read documentation for the API at MDN. WebGPU is defined in two W3C standards, WebGPU and WGSL, whose development Mozilla has participated in since it began in 2017.

WebGPU has been available in Google Chrome since 2023, and is expected to be available in Safari 26 this fall.

Although Firefox 141 enables WebGPU only on Windows, we plan to ship WebGPU on Mac and Linux in the coming months, and finally on Android. Windows was our first priority because that’s where the great majority of our users are, but we are looking forward to enabling it on the other platforms as soon as it is robust and our test coverage is adequate. (Your humble author is strictly a Linux user, so this concern is close to his heart.) Note that WebGPU has been available in Firefox Nightly on all platforms other than Android for quite some time.

Firefox’s WebGPU implementation is based on WGPU, a Rust crate that provides a unified, portable interface to the low-level graphics APIs of the underlying platform: Direct3D 12, Metal, and Vulkan. WGPU is developed as an independent open source project on GitHub, but Mozilla is a major contributor. WGPU is widely used outside Firefox, and has an active community, so if you are a Rust developer interested in contributing to Firefox’s WebGPU support, WGPU is a good place to start.

WebGPU is a large, complex API. We’ve focused our efforts so far on making high-visibility WebGPU applications and demos run smoothly, and we believe it should work well in Firefox 141 for many use cases. However, there is plenty of work remaining to be done to improve our performance and compliance with the specification. In particular:

  • Firefox uses unbuffered inter-process communication to convey web content’s requests to the GPU sandbox process, which introduces significant overhead. We addressed this in Bug 1968122, which improved performance significantly. The fix will appear in Firefox 142.
  • Firefox currently uses an interval timer to tell when the GPU has completed a task, adding significant latency to many applications where the task finishes quickly. There are better ways to do this, we are changing Firefox to use them. You can follow our progress in Bug 1870699.
  • Firefox does not yet support WebGPU’s importExternalTexture method, which lets the GPU read decompressed video content directly from the decoder. You can follow our progress in Bug 1827116.

Please give WebGPU a try in Firefox! If you encounter problems, please report them in the WebGPU component in Bugzilla. As always, provide us with as detailed instructions as you can to make the bug occur, and attach the contents of about:support to the bug so we can see what kind of system you are using.

It’s been a big project, but we’re done tinkering with the engine and taking test drives — we’re finally ready to roll WebGPU out of the garage and hand it over to you for daily use. We’re looking forward to seeing what you can do with WebGPU in Firefox!

The Mozilla Thunderbird BlogMobile Progress Report – June 2025

Welcome back to another update on how things are going on mobile. 

Thunderbird for iOS

We’ve been going back and forth between database and JMAP for Thunderbird for iOS. Most of the visible work has flown into creating an initial JMAP library that we can use to access the parts that we need from Thunderbird for iOS. This work will continue into July as well. Progress so far means making JSON requests and parsing responses and making standard get/set/query requests. There is support for working with sessions as well.

In July we’ll have a few things to show for viewing actual folders and email messages. Very preliminary, but already quite some progress! I’m almost tempted to post the screenshots now but I’ll wait until next month. We’ll also be releasing a new (currently still internal) Testflight version when everything has landed.

Thunderbird for Android

We want to make Thunderbird for Android more accessible to contributors and improve some of our documentation. Part of that is our brand new testing guide which talks about which testing patterns to use, how to adhere to our naming conventions and some guidelines around fakes vs mocks. We’ve recently been talking about making more use of the Maestro testing framework, as it makes it very simple to add tests even for folks without engineering experience. 

Further we’ve made some strides on our overall architecture documentation. If you’ve been reluctant to contribute because of the learning curve, this might be your chance to make another attempt. Even if you are an existing contributor, we believe the docs will help you understand the codebase a bit better. Let us know what you think, if you see a way that our documentation can be improved go ahead and file an issue.

Next up, we’re nearing the end of the drawer updates we’ve been working on. We know a bunch of folks weren’t very happy with the navigation rail given the extra horizontal space it uses, and it being unclear which account you actually have selected. We’re returning the account selector to the top, and sporting a separate “Unified Account” where you can find not just your unified inbox, but also some other unified folders. If you’ve set up custom unified folders previously these will appear there as well. 

Additional updates

  • Ashley has worked on sync debug tooling so we can get a better understanding of any issues related to emails not arriving in time.
  • Jan has switched the EHLO string from 127.0.0.1 to ehlo.thunderbird.net to increase compatibility with email servers that don’t accept 127.0.0.1.
  • João has improved accessibility of the contact pictures in the message view, and fixed an issue where the “Download Complete Message” button was hidden by the navigation bar.
  • Rafael has been working on the foundations of in-app error notifications. He improved swiping actions for when the account does not have an archive folder set, to avoid surprises. Through this work a bunch of files have been migrated from Java to Kotlin, great work!
  • Stefan has fixed an issue where some I/O errors were not correctly caught. I’m particularly excited about this since it smooths over the situation where you change from one network to the next, so that push email will arrive a little more reliably.
  • Wolf has revamped some of our internal logging support to be more consistent. We really don’t need multiple different loggers and might want to change the implementation once in a while 🙂 There has also been a bunch of Java/Kotlin conversion going on, and some refactoring in the local search code. Above mentioned work on the drawer and documentation was also Wolf’s work. 
  • Shamim continues to rock the refactoring. By far the most Java to Kotlin conversion, fixing a crash when adding an account after removal, making threaded view update correctly when in the message list. Notably, the [Gmail] folder placeholder is now no longer visible, you’ll see the subfolders directly.


Philipp Kewisch (he/him)
Thunderbird Mobile Engineering | Mozilla Thunderbird
thunderbird.net

The post Mobile Progress Report – June 2025 appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogThunderbird Monthly Development Digest – June 2025

Hello once more from the Thunderbird development team! For many of our team members, the summer has started with our annual sprint to release ESR and enjoy a little time afk, as our colleagues in the southern hemisphere hunker down for winter and power through a pile of work down under.

Extended Support Release is alive!

For enterprise users (and those who have been using Thunderbird for a long time and found themselves on the Extended Support Release channel), the annual release “ESR 140 Eclipse” has made it to our update servers and will be pushed out over the next few weeks. 

We had initially planned to release within hours or days of the Firefox ESR release, but much of the ESR build process has changed in the last 12 months (largely due to the Firefox mozilla-central Git migration) – so we ended up learning a lot and took pause to release at a time that produced the best experience for the majority of our users. 

In the hours following the initial release, we have another build hot on its heels which includes some important patches and will ship today or tomorrow. Things move fast around here!

If waiting a year doesn’t sound appealing to you, our Monthly release may be better suited. It offers access to the latest features, improvements, and fixes as soon as they’re ready. Watch out for an in-app invitation to upgrade or install over ESR to retain your profile settings.

Exchange support in Daily

The EWS 0.2 milestone has been completed and the feature was turned on by default in Daily release to facilitate more manual QA testing. In order to provide test coverage on a variety of EWS server versions and configurations, we’re tackling in a few ways:

  • Adding a small number of Hosted Exchange 2016 mailboxes to facilitate testing of all existing functionality at endpoints other than O365.
  • Contacting enterprise partners who can help us test on their infrastructure – please get in touch if this might be you!
  • Hosting our own EWS instance that allows us to configure a variety of security and authentication settings to ensure our code works for all
  • Focusing on automated test coverage throughout the month of July

Since my last update, the team has grown even more and made great progress on items in our “Phase 2 operations” and “Phase 2 polish” milestones, with these features delivered recently:

  • EWS-to-EWS move & copy for items and folders
  • Authentication Error handling
  • Server Version handling
  • Threading support
  • Folder updates & deletions during sync operations
  • Folder cache cleanup
  • Folder copy/move
  • Bug fixes!

We plan to temporarily expand the team during July to include two more of our most experienced senior engineers to push this project over the finish line and tackle some remaining complexities:

  • Automated test coverage
  • Message filtering
  • Setting as Junk/Not Junk
  • Bug backlog

Keep track of feature delivery here.

Account Hub

The new email account feature was enabled as the default experience for users adding their second email account. It is now available in all release channels. We’re currently finalizing the UX and associated functionality that detects whether account autodiscovery requires a password, and reacts accordingly – which will hopefully be uplifted once stable.

We’re wrapping up the redesigned Account Hub UI for Address Book account additions this week, which we’ll enable for users on Daily and beta in the coming weeks. Look out for it in our Monthly release 142.

Global Message Database

Since the last update, we’ve landed a landslide of patches. Critical refactoring continues to clean and optimize the code, in many cases clearing the way for new beneficial protocol implementations.

To follow their progress, take a look at the meta bug dependency tree. The team also maintains documentation in Sourcedocs which are visible here.

Recent Features and Fixes

A number of other features and fixes have reached our Daily users this month. We want to give special thanks to the contributors who made the following possible…

If you would like to see new features as they land, and help us squash some early bugs, you can try running daily and check the pushlog to see what has recently landed. This assistance is immensely helpful for catching problems early.

Toby Pilling

Senior Manager, Desktop Engineering

Thunderbird

The post Thunderbird Monthly Development Digest – June 2025 appeared first on The Thunderbird Blog.

SUMO BlogWhat’s up with SUMO – H1 2025

Hi everybody,

It’s been a long overdue since our last update. Previously, we shared these recaps on a quarterly basis, but this time, we’re trying out a slightly new format and cadence to keep things fresh and more in tune with what’s happening across the community.

In this post, we also include a broader set of data to give a clearer picture of how the community performed in H1 2025. We hope it helps highlight both what’s working well and where we have room for improvements.

Without further ado, let’s dive in!

Highlights

  • We started the year strong with the Firefox Address Bar Test Day Event in January 2025, which was a great success. By the end of the campaign, 40% of the average Daily Active Users who tried the feature completed the survey, which is an impressive response rate. The feedback collected gave the product team valuable insights to help refine the feature ahead of a broader launch.
  • In early February, a few of us were headed to Brussels for FOSDEM 2025. It was truly wonderful to finally be able to connect face to face again.
  • In May 2025, we made the difficult decision to shut down the Social Support and Mobile Store Support to focus more on the Community Forums. This wasn’t a decision made lightly. We deeply appreciate the incredible dedication, time, and care that so many of you have invested in these programs over the years. We’re truly grateful for everything you’ve done to support users and represent Mozilla in these spaces that have made users feel heard, supported, and connected to our mission.
  • We released the automatic spam moderation and topic classification to reduce moderation workload in early June. Posts that are clearly spam are now automatically marked as spam. By the end of June, we found that 87.85% of questions marked as spam automatically by this automation. This has significantly reduced the moderation workload previously handled by forum moderators, support agents, and CMs. We also noticed that the average spam rate per ISO week has increased to 40% in June (compared to 19% in the previous period), which may suggest that spam was previously under-reported. Huge kudos to the team who worked on this project. We can’t wait to learn more about what else we can do with this technology.
  • Mozilla’s staff in the Customer Experience (CX) team went through several structural changes this year, with the departure of several members. Make sure to check out the Meet the Team page to see the most up-to-date team structure.

Community stats

Knowledge Base

In the Knowledge Base (KB) space, we saw a moderate increase in activity, with total revisions up by almost 5% and total articles growing by around 14%. Notably, the number of contributors rose to 105 (+14%), and reviewer participation increase

General stats

Total en-US revisions 731 +4.9%
Total articles 226 +14.1%
Total revisions reviewed 621 -4.8%
Total revisions approved 599 -5.1%
Total backlog 110 +144.4%
Total authors 105 +14.1%
Total reviewers 18 +38.5%
Average time to review (in hour) 80.8 -13.4%

Top KB contributors

Contributor name Total revisions Total articles Total reviews
AliceWyman 602 332 365
Pierre Mozinet 132 106
Mark Heijl 109 96
Michele Rodaro 50 46 36
Paul Wright 25 20 5

 

Article Localization

In article localization, overall activity slightly declined, with total non-en-US revisions down 10.5%, and article count down 4.4%. Despite this, the number of authors and reviewers increased by 4.2% and 8%, respectively, showing sustained contributor engagement. Review efficiency notably improved, with average review time down by 41.6%.

General stats

Total non en-US revisions 3287 -10.5%
Total articles 1908 -4.4%
Total revisions reviewed 3015 -10.3%
Total revisions approved 2991 -10.4%
Total backlog 272 -12.3%
Total authors 222 +4.2%
Total reviewers 54 +8%
Average time to review (in hour) 21.3 -41.6%

Emerging localization contributors

Contributor name Total responses Total threads engaged
普莱是袋熊 (zh-CN) 35 32
Rina Ledovskaya (ru) 17 17
aledgx (it) 17 16

Top localization contributors

Contributor name Total revisions Total articles Total reviews
Michele Rodaro (it) 861 360 743
Jim Spentzos (el) 648 445 604
Mark Heijl (nl) 544 349 158
Wxie (zh-CN) 471 296 548
Valery Ledovskoy (ru) 440 302 443

Forum Support

Forum support activity saw a significant uptick, with valid questions rising 24.4% and contributor participation jumping 50%. However, challenges remain: the solve rate dropped by 20.8%, and OP reply rate fell by 24.1%, which may indicate reduced follow-up from users. The spam rate spiked to 23.76%, but reply rates improved slightly, and the average time to first reply dropped by 22.5%.

General stats

Total valid questions 18520 +24.4%
Spam rate 23.76% +67.9%
Reply rate 50.9% +0.77%
Solve rate 5.07% -20.8%
Total questions replied 9422 +26.3%
Total responses 11775 10.2%
Time to First Reply (in hour) 23.88 -22.5%
Total new registration 450k 32.7%
Total contributor 969 +50%
Total new contributor 587 59.1%
Helpful rate 61.30% -1.05%
OP reply rate 23.71% -24.1%

Top forum contributors

Contributor name Total responses Total threads engaged Avg helpful rate
Jefferson Scher (en-US) 1900 1395 76.07%
Jonzn4SUSE (en-US) 1284 924 38.52%
Paul Wright (en-US) 930 871 45.5%
Gerardo (es) 719 651 50.85%
@next (it) 658 538 51.47%
Mark Heijl (nl) 197 159 66.67%
Selim (tr) 164 120 57.14
Poljos-moz (cs) 84 73 42.86%
Ansamb (cs) 79 73 42.86%
Samuel Santos (pt-BR) 118 116 71.43%
Balázs Meskó (hu) 59 55 100%
Vexi (sl) 3 3 100%

Emerging forum contributors

Contributor name Total responses Total threads engaged Avg helpful rate
Denys 544 461 57.5%
Jeff-g 137 124 13.51%
Mutaz Awad 102 96 35.29%
Mark 95 89 45.98%
Logosor 67 60 50%

Stay connected with the community

Join the Conversation

  • Participate in ongoing discussions on the Contributor Forum to catch up on the latest updates and share your input.
  • Drop by our Matrix channel for more casual chats with fellow contributors.

Attend Our Monthly Community Call

  • Every month, we host a community call to share updates about Firefox and community activities. Watch past recordings from 2025!
  • Don’t hesitate to join the call in person if you can. We try our best to provide a safe space for everyone to contribute. Don’t feel pressured to turn on your camera or speak if you’re not comfortable. You can also:
    • Submit your questions ahead of time via the Contributor Forum or Matrix
    • Lurk silently and absorb the updates—your presence is still valued!

Stay Informed

Explore What We’re Building

  • Curious about what the platform team is working on? Visit the SUMO Engineering Board to see what the platform team is cooking in the engine room.
  • You can also view our latest release notes to stay informed about recent changes and improvements.

The Mozilla Thunderbird BlogWelcome to Thunderbird 140 “Eclipse”

The wait is over! Thunderbird 140 “Eclipse” has reached totality. From all of us at the Thunderbird project, from MZLA staff and the Thunderbird Council to our global community of contributors, we’re excited to announce the latest Extended Support Release has arrived.

Eclipse not only builds on Thunderbird 128 “Nebula,” but also the recent features and improvements from the Monthly Release channel. This latest release transforms your email experience with adaptive dark messaging and improved visual controls. Enhanced features keep everyday email tasks light and effortless, while the streamlined new Account Hub ensures adding new accounts is a snap.

Dark Message Mode

Thunderbird’s Dark Mode now automatically adapts your messages when enabled, to ensure your Dark Mode experience stays totally dark. Need to bring your messages back into the light in case of visual problems? Adjust your message view as needed with a quick optional toggle.

Appearance Settings

Make Thunderbird yours across all your folders and accounts with a single click in the Settings (panel). Change your message list layout between Cards and Table view, adjust your Cards View, and set your default sorting order and threading options with ease.

Native OS Notifications

Leverage the speed and ease of your Operating System’s built-in notifications, whether you’re on Windows, Linux, or Mac. Quickly delete, archive, or use customizable actions directly from your notifications and get more done with your day.

Account Hub

Adding a new account to Thunderbird is now easier than ever. Connect all of your emails, address books and calendars in a few easy steps.

Manual Folder Sorting

Don’t like the order for your custom folders? Just click and drag to arrange them exactly how you want.

Don’t like the order for your custom folders? Just click and drag to arrange them exactly how you want.

More Refinements & Updates

Experimental Exchange Support Natively set up a Microsoft Exchange account in Thunderbird by enabling a preference.

Export for Mobile Generate a QR code to quickly transfer your account settings and credentials to your Thunderbird for Android app.

Horizontal Scroll for Table View Lots of tabular data? Let the message list scroll horizontally, like a spreadsheet or file manager.

Bug Fixes and Improvements

Thousands of bug fixes and performance improvements to bring you the smooth, reliable Thunderbird experience you expect.

Looking Forward

Whether you’re waiting for the next Thunderbird ESR or total solar eclipse, we understand that sometimes you want new features, or that cosmic awe, sooner. While we can’t change the universe, you can now get the latest Thunderbird features as they land, instead of once a year. Switch to Thunderbird Release and enjoy monthly updates with the same dependable stability.

Thunderbird 140 Availability For Windows, Linux, and MacOS

Even with QA and beta testing, any major software release may have issues exposed after significant public testing. That’s why we are slowly enabling automatic updates until we’re confident no such issues exist. We do have a known issue where users sending mail through 32bit MAPI will be prompted for a password, unless they use the compose window.

We have enabled manual upgrade to 140 via Help > About, and you can upgrade now or wait to receive automatic updates. Thunderbird version 140.0 is also offered as direct download from thunderbird.net. Be sure to select ‘Thunderbird Extended Support Release’ in the ‘Release Channel’ drop-down menu.

For Linux users running Thunderbird from the snap or flatpak, 140 will be available within the next few weeks. Likewise, Thunderbird 140 will also arrive on the Windows store by mid-July.

The post Welcome to Thunderbird 140 “Eclipse” appeared first on The Thunderbird Blog.

Mozilla L10NReconnecting in Berlin: A Celebration of Mozilla’s Localization Community

Something we’ve long known at Mozilla is that our localization community thrives on personal connections. For years, regional meetups brought volunteers and staff together multiple times a year — forging friendships, sharing knowledge, and collectively advancing the mission of a multilingual, open internet.

After a five-year pause, we’re thrilled to share that in June 2025, we re-ignited that tradition with a pilot localization meetup at the Mozilla Berlin office; it was everything we hoped for, and more.

A Weekend of Community, Collaboration, and Fresh Energy

Fourteen volunteers from 11 different locales gathered for a weekend full of shared ideas, meaningful conversations, and collaborative problem-solving. For many, it was their first time meeting fellow contributors in person, people they’d worked with for years, but only ever known through usernames and chat windows. For others, it was a long-awaited reunion, finally bringing back to life connections that had existed solely online since the last wave of community meetups.

“We now feel more connected and will work together more closely,” shared one participant, reflecting on the emotional impact of finally connecting face-to-face.

Throughout the weekend, we dove into topics ranging from community building to localization tooling. Some standout moments included:

  • Candid discussions about what it means to lead within a localization community, the challenges of maintaining momentum, and what kind of support really makes a difference.
  • David’s lightning talk on the Sicilian language and community, which sparked conversations about linguistic diversity and revitalizing regional languages through digitalization.
  • Collaborative Pontoon brainstorming session, where localizers took the lead in proposing enhancements, suggesting new features, and sharing pain points — and some even supporting each other with development setup and hands-on exploration.

And of course, there was time for laughter, great food, and spontaneous late-night ideas that could only come from being in the same room together.

As one localizer put it: “The event gave me fresh energy and ideas to contribute more actively to Mozilla.”

Behind the Scenes

Organizing this meetup — especially after a multi-year hiatus — was a complex endeavor. Though we were eager to bring people together in the first half of the year, it took nearly nine months of planning. In the end, only two weekends aligned with enough staff availability to make the event possible.

To keep things focused and manageable for a pilot, we made a few strategic decisions:

  • Location: with a local staff member on the ground and access to Mozilla’s Berlin office, we could streamline logistics — from restaurant bookings and lunch deliveries to helping attendees navigate international travel with clear guidance and local support.
  • Participant selection: we prioritized inviting contributors who were highly active in Pontoon, and whose travel would be cost-effective and visa-free. This helped reduce uncertainty and made the event more accessible.
  • Budget-aware planning: we extended invitations to 34 community members and received interest from 27. Due to scheduling overlaps, 14 were ultimately able to attend.

Why This Matters

Events like this don’t just strengthen Mozilla’s localization work, they strengthen Mozilla as a whole. Contributors left Berlin feeling recognized, energized, and motivated, and organizers left with a renewed sense of purpose and clarity about how vital it is to invest in human connection.

It also gave us space to hear directly from contributors — not in surveys or chat threads, but in real time, with nuance and context. Those conversations helped surface both immediate ideas for improvement and deeper questions about what sustainable, meaningful participation looks like in today’s Mozilla. It was a reminder that strong localization doesn’t just come from good tools and processes, but from mutual trust, shared ownership, and space to collaborate openly.

Looking Ahead

We’re now regrouping to reflect on lessons learned and to explore if it’s possible to scale these meetups going forward. That means thinking carefully about aspects like:

  • How do we support communities in regions where Mozilla has no local staff?
  • How do we navigate unknowns, like visa requirements, more complex traveling logistics, etc.?
  • How do we sustainably host more meetups per year and ensure they’re just as impactful?

One thing is certain: this pilot proved once again the value of in-person community building. It re-affirmed something our community has said all along — that being together matters.

We’re incredibly grateful to everyone who participated, and we’re excited about the possibilities ahead. Whether you’re a seasoned localizer or just getting started, we hope this story inspires you. Your contributions make Mozilla possible  and we truly hope we can celebrate that together, in more places around the world.

Mozilla Add-ons BlogUpdated Add-on policies — simplified, clarified

POST UPDATED: 4 August, 2025Updated policies for addons.mozilla.org (AMO) are now in effect. We also added a new section about implicit consent for self-evident, single-use data transmission.


Here’s a summary of the policy changes and their impact on AMO’s publishing process. Our main objective was to simplify and clarify Add-on policies for the developer community. The following policy updates will take effect on 4 August, 2025.

“Closed group” prohibition lifted

Closed group extensions are typically intended for internal or private use among a relatively small group of users. In the past AMO did not allow closed group extensions, but we’re lifting this prohibition to give developers more flexibility to publish restricted access extensions for any number of reasons.

Implicit consent for self-evident, single-use extensions

We’ve added new guidelines around implicit consent for single-use extensions in cases where using the feature obviously requires data transmission (must be apparent to users from the extension description/name and UI). Examples might include image search extensions, cloud-based language or grammar tools, file uploaders, etc. For these single-use, self-evident features, data consent is implied and developers are not required to ask for explicit consent. This policy addition furthers our efforts to streamline the developer experience.

Data consent and control terminology

We’ve updated terminology in an effort to clarify our policies related to user data consent and control.

A core aspect of our data policy is we only permit extensions to transmit data that’s necessary for functionality (and even so users must consent to data transmission). Prior policy language often intermingled the terms collection and transmission of data. This was often confusing for developers who naturally assumed these were two separate aspects of handling data. But in fact we are only concerned with the transmission of data outside of an extension or browser. Thus we’ve removed all references to the collection of user data and framed all data concerns around transmission.

Privacy policy not required to be hosted on AMO

In effort to reduce developer overhead and publishing friction, we are no longer requiring extensions to host privacy policies on AMO. Rather, we encourage developers to link to self-hosted privacy policies. Removing this requirement will allow developers to more easily update their privacy policies without necessitating the submission of an entirely new extension version on AMO.

Data collection transparency is of paramount importance to Firefox users. We’re also working on other changes that will make it easier for developers to select the types of data their extension requires, which will in turn provide enhanced data collection clarity for users.

User scripts API policy added

A user script manager is a type of extension that allows users to inject custom, website-specific scripts that alter a site’s appearance or behavior. These extensions leverage the userScripts API, which our policies now clarify may only be used by user script manager extensions. The userScript API may not be used to extend or modify the functionality of the script manager itself.

Source code submission guidelines

It has been a longtime AMO policy that all extension submissions must provide reviewable source code, regardless if it’s transpiled, minified, or otherwise machine generated. We’ve now amended our policy to more specifically stipulate that all dependencies must either be included in the source code package directly or downloaded only through the respective official package managers during the build process.

Taken together, we hope these policy refinements will make developing Firefox extensions a more straightforward and streamlined process. Let us hear your thoughts in the comments. Happy coding!

The post Updated Add-on policies — simplified, clarified appeared first on Mozilla Add-ons Community Blog.

The Mozilla Thunderbird BlogThunderbird Mobile Progress Report: May 2025

Thunderbird for iOS

We’re growing a few more stars! We’re so happy to hear there is great interest in Thunderbird for iOS, and hope to reach a stage soon where you all can be more involved. Thank you, also, to those of you who’ve submitted an increasing number of ideas via Mozilla Connect.

Todd has been preparing the JMAP implementation for iOS, which will allow us to test the app with real data. We’re exploring the possibility of releasing the first community TestFlight a bit earlier by working directly with in-memory live data instead of syncing everything to a database upfront. The app may crash if your inbox has 30GB of email, but this approach should help us iterate more quickly. We still believe offline-first is the right path, and designing a database that supports this will follow soon after.

Further we’ve set up the initial localization infrastructure. This was surprisingly easy using Weblate’s translation propagation feature. We simply needed to add a new component to our Android localization project that pulls from the iOS repository. While Weblate doesn’t (yet?) auto-propagate when the component is set up, if there are changes across iOS and Android in the future, the strings will automatically apply to both products. 

Thunderbird for Android

We spent a lot of time thinking about the beta and making adjustments. Fast forward to June, we’re still experiencing a number of crashes. If you are running the beta, please report crashes and try to find out how to trigger them. If you are not using Beta, please give it a try and report back on the beta list or issue tracker. We’d greatly appreciate it! Here are a few updates worth noting for the month of May:

  • Some folks on beta may have noticed the “recipient field contains incomplete input” error which kept you from sending emails. We’ve noticed as well, and halted the rollout of 11.0b1 on app stores where supported. Shamim fixed this issue for 11.0b2.
  • Another important issue was when attaching multiple issues, only one image would be attached. This happens all the way back to 10.0, and we’ll release a 10.1 that includes this fix. Again thank you to Shamim!
  • Final round of fixes from Shamim: new mail notifications can be disabled again, we have a bunch of new tests and refactoring, we have a few new UI types for the new preference system that Wolf created.
  • Timur Erofeev solved a crash on Android 7 due to some library changes in dependency updates we didn’t anticipate
  • Wolf is getting closer to finishing the drawer updates that we’re excited to share in a beta soon. He has also been working diligently to remove some of the crashes we’ve been experiencing on beta due to the new drawer and some of the legacy code it needs to fall back to. Finally, as we’re venturing into Thunderbird for iOS, Wolf has been thinking about the KMP (Kotlin Multiplatform) approach and added support to the Thunderbird for Android repository. He will soon separate a simple component and set things up so we can re-use it from Thunderbird for iOS.
  • Rafael and Marcos have fixed some issues with the system bar appearing transparent. The issue has been very persistent, we’re still getting reports of cases where this isn’t yet resolved.
  • Philipp has fixed an issue for our release automation to make sure the changelog doesn’t break on HTML entities.

I also wanted to highlight the new Git Commit Guide that Wolf created to give us a little more stability in our commits and set expectations for pull requests. We have a few more docs coming up in June, stay tuned. 

You could be on this list next month, please get in touch if you’d like to help out!


Philipp Kewisch (he/him)
Thunderbird Mobile Engineering | Mozilla Thunderbird

The post Thunderbird Mobile Progress Report: May 2025 appeared first on The Thunderbird Blog.

Firefox UXHow a UX-Led Approach Shaped Firefox Profiles

An oboarding panel for Firefox profiles with an illustration of three friendly foxes in various outfits on top of a message that reads “say hello to Firefox profiles” and subcopy reads “Easily switch between browsing for work and fun. Profiles keep your browsing info, including search history and passwords, totally separate so you can stay organized.” with a create a profile and not now buttons below. the panel is white and situated on a blue/violet background

Why Firefox needed profiles

We’ve all been there — one minute you’re checking work emails, the next you’re deep into vacation planning, and the next thing you know all of your content is a jumbled mess. Firefox users needed an easy way to keep different online lives separate — work, personal, school, or shopping — without juggling multiple browsers.

While other browsers offer multi-profile support, they lack privacy-first management and quick profile switching. We saw an opportunity to do it better — to give users more control, with fewer headaches.

With hundreds of votes on Mozilla Connect, demand for direct taskbar access to profiles was clear. So, we got to work.

Building profiles

From day one, UX and content design collaborated on every step of the process, ensuring a cohesive experience based on a shared understanding of user needs.

Phase 01: research & early ideas

Before designing anything, we:

  • Studied competitors to find what worked (and what didn’t).
  • Mapped out user journeys to understand pain points.
  • Sketched early ideas — low-fidelity wireframes — to get quick team feedback.
  • Defined how profiles fit into the Firefox ecosystem.
A black and white composite image of 5 photos of wireframes and word lists written in marker on a whiteboard

Phase 02: test, iterate, repeat

We tested profiles at every stage, using:

Moderated & unmoderated user tests (UserTesting.com)
We asked real people to try early versions of the feature and share their thoughts. Sometimes a moderator guided them through tasks and asked follow-up questions (moderated), and other times they completed tasks on their own while we watched recordings later (unmoderated). This helped us understand where users got stuck or confused.

Key learnings:
Positive: Users found the profile creation process simple and intuitive, and appreciated the instant visual feedback like color and icon changes — confirming this flow was working well as designed.

Constructive: Some users had trouble finding where to access profiles within the browser, often looking for them in the account section, suggesting the need for clearer entry points and distinctions in the UI.

Accessibility-focused testing (Fable, DisCoTec)
We partnered with people who use assistive technologies like screen readers or keyboard-only navigation to test the feature. Their feedback helped us make sure profiles would be easy to use for everyone, including users with disabilities.

Key learnings:
Positive: The profiles feature was well-received by participants using assistive technologies. The setup process was described as “pretty easy,” and users appreciated the immediate feedback when choosing themes or avatars. One participant noted, “I like to have all profiles significantly different colors so it’s easy for me to recognize I’m in the right profile without zooming in.”

Constructive: Some users had trouble locating profiles in the menu or understanding what elements were clickable, especially with screen readers. One participant commented, “Alt+P didn’t take me to the profiles part of the app menu as expected — it should be a shortcut.”

Live prototype reviews with Firefox teams
We regularly showed early interactive versions of the feature, also known as prototypes, to different Firefox teams. This let us gather fast, internal feedback and make improvements before we committed to building anything fully.

Key learnings:
Positive: Stakeholders responded positively to the decision to launch each profile in its own window with a separate taskbar icon. This was seen as a clear differentiator from other browsers and aligned with Firefox’s goals around user control and simplicity.

Constructive: Stakeholders identified the lack of a profiles entry point in the account avatar as a key discoverability issue. While this was initially excluded from the MVP to reduce complexity, there was an alignment that it should be prioritized as part of the initial roll out.

Phase 03: refining the experience

Every iteration made profiles simpler, more accessible, and easier to use.
To keep everyone aligned, we took our work company-wide by:

  • Maintaining the smaller cross functional team well informed during weekly syncs.
  • Creating walkthrough videos for a wide range of feedback and perspectives.
  • Sharing during UX leadership reviews
  • Working closely with the design systems team to ensure that the UI was not only accessible and intuitive, but also fit well within the wider Firefox ecosystem.
  • Collaborating with the accessibility team to create an easy handoff for engineers to build a delightfully accessible product.
a snippet of accessibility notations for the “Customize your new profile page” that has a side by side list of focus order and markups on the relevant screen

Phase 04: measuring success with telemetry

A great feature isn’t complete without the right data to evaluate impact and guide business decisions. At Firefox, we believe in collecting only what’s necessary. That’s why we follow lean data practices, minimizing what we track and always keeping it anonymous. This ensures we respect user privacy while answering key product and business questions.

We led a two-part telemetry workshop to make sure:

  • Every button and link was trackable (all this data is of course anonymous).
  • We could measure adoption, switching behavior, and engagement.

These valuable insights will help us improve profiles post-launch.

Phase 05: bringing profiles to life

To ensure a smooth handoff to engineering, we provided:

  • Detailed documentation for all screens and components.
  • Accessibility annotations for keyboard navigation, focus order, and high-contrast mode.
  • Comprehensive user flows covering onboarding, profile creation, switching, and deletion.

Some examples of our final screens:

Unique avatars and themes help users instantly recognize each profile.

A gif of the “Customize your new profile” screen which includes an instructional blurb, profile name field, 10 theme options, link to more themes, and 6 avatar options, followed by a “Done editing” and “Delete” buttons. It’s switching between a light pale lavender theme and a dark mossy green theme.

A startup profile picker makes choosing and managing profiles a breeze.

A startup manager window for selecting, editing, and deleting profiles showing a Firefox logo, a header that reads: “Choose a Firefox profile”, subcopy “Keep your work and personal browsing, including things like passwords and bookmarks, totally separate. Or create profiles for everyone who uses this device”, dark green card with a suitcase icon labeled “Work”, a pale lavender card with a flower icon labeled “Personal” next to a card with a “+” icon that reads “Create a profile” and a checkbox

Easily access and switch between profiles from your dock or taskbar

Windows taskbar showing two Firefox icons, one with a green suitcase icon in the upper right corner and one with a purple flower icon amongst other standard taskbar icons
MacOS dock showing two Firefox icons, one with a green suitcase icon in the upper right corner and one with a purple flower icon amongst other standard dock icons

What’s next?

Profiles are currently rolled out to a small percentage of Firefox users, and early telemetry shows strong engagement. We’re seeing meaningful adoption, encouraging retention signals, and higher engagement across key behaviors like search and customization. Many users are also making use of cross-profile switching, indicating that the feature is resonating with both casual and power users.

This project proved that when UX leads from the start, we build better, more user-friendly features.

This is how we design Firefox, together.


How a UX-Led Approach Shaped Firefox Profiles was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

SeaMonkeySeaMonkey 2.53.21 is out!

Hi All,

The SeaMonkey Project is pleased to announce the immediate release of SeaMonkey 2.53.21.   There are a few security updates and …

*What?  Um.. No,  I didn’t see it.  I did look at the website patch…  Yes, it’s the same as reading the release notes.  It clearly states that it’s a point release and it’s a security patch…   Anyway…. *

Please check out [1] and/or…

*What now?  Look, I’ve been doing and/or for some time…   What do you mean exclusive or?  Ok.. this time, you make sense.*

Please do check out [1] and [2].

:ewong

PS: Did I mention the Updates will be forthcoming…?   Yes, the updates will be forthcoming…if it hasn’t already been done already when you read this.

PPS: Yes, trying to jazz things up…  think of this post being Rik Mayall’d.  (RIP).  The People’s Poet…

[1] – https://www.seamonkey-project.org/releases/seamonkey2.53.21

[2] – https://www.seamonkey-project.org/releases/2.53.21

The Mozilla Thunderbird BlogVIDEO: Thunderbird Pro and Thundermail!

It’s been just over two months (!) since we first announced our upcoming Thunderbird Pro suite and Thundermail email service. We thought it would be a great idea to bring in Chris Aquino, a Software Engineer on our Services team, to chat about these upcoming products. We want our community to get to know the newest members of the Thunderbird family even before they hatch!

We’ll be back later this summer after our upcoming Extended Support Release, Thunderbird 140.0, is out! Members of our desktop team will be here to talk about the newest features. Of course, if you’d like to try the newest features a little sooner, we encourage you to try the monthly Release channel. Just be sure to check if your Add-ons are compatible first!

May Office Hours: Thunderbird Pro and Thundermail

Chris has been a part of the Thunderbird Pro products since we first started developing them. So not only is he a great colleague, he’s an ideal guest to help tell the story about this upcoming chapter in the Thunderbird story. Chris starts with an overview for each product that covers the features we have planned for each of our Thunderbird Pro products and Thundermail. We know how curious our community is about these products, and so our hosts have lots of questions for each product, and Chris is more than up to the challenge in answering them. We also make sure to point out how to get involved with trying, testing, and helping us improve these products by linking you to our repositories.

Watch, Read, and Get Involved

The entire interview with Chris is below, on YouTube and Peertube. There’s a lot of references in the interview, which we’ve handily provided below. We hope you’re enjoying these looks into what we’re doing at Thunderbird as much as we’re enjoying making them, and we’ll see you soon!

We also know some of you might only be interested in a single product, and so we’ve also made separate videos for each product!

COMPLETE VIDEO (Also on Peertube):

Slides:

Individual Videos:

Appointment

YouTube: https://youtu.be/7EOQL750wy8

TILVids: https://tilvids.com/w/sQBce3zn3gAQopCg9EMeBE

Thundermail

YouTube: https://youtu.be/WaycMTC94SA

TILVids: https://tilvids.com/w/hBR4gN5RvmzVv5ugsUx9Cy

Send

YouTube: https://youtu.be/DJWn84loerE

TILVids: https://tilvids.com/w/wm6xW6gzJ5BTRj7AoePaZW

Assist

YouTube: https://youtu.be/hcfERyCnfy8

TILVids: https://tilvids.com/w/27wUtpY4bWkNhLMbC8JnBs

Resources:

The post VIDEO: Thunderbird Pro and Thundermail! appeared first on The Thunderbird Blog.

Mozilla Add-ons BlogCrypto wallet scams — thwarting a new threat

According to the FBI’s 2024 Internet Crime Report, crypto-related scams accounted for nearly $16.6 billion in victim losses last year across the globe ($9.3 billion in the United States alone — a 66% increase from 2023). Crypto thieves employ a variety of tactics to defraud people, but a certain type, known as a crypto wallet drainer, is proliferating and one of the ways scammers find new victims is through malicious browser extensions.

A crypto wallet drainer is basically any type of fraudulent method that gives bad actors unauthorized access to a user’s crypto wallet. In the case of browser extensions, we find malicious extensions masquerading as legitimate extensions from trusted, known crypto wallets. Unfortunately for users who install a scam crypto wallet extension and input their private keys and credentials, the effects are often immediate and devastating. The funds quickly vanish and they’re virtually impossible to recover.

The FBI’s Internet Crime Complaint Center receives an average of 836,000 complaints per year comprising all manner of online scams. (Source: 2024 FBI Crime Report)

According to Add-ons Operations Manager Andreas Wagner, who leads content security and review efforts, AMO (addons.mozilla.org) has uncovered “hundreds” of scam crypto wallets over the past few years. “It’s a constant cat and mouse game,” Wagner explains, as “developers try to work around our detection methods.”

To help protect Firefox users, the Add-ons Operations team developed an early detection system designed to identify and stop crypto scam extensions before they find traction with unsuspecting users. The first layer of defense involves automated indicators that determine a risk profile for wallet extensions submitted to AMO. If a wallet extension reaches a certain risk threshold, human reviewers are alerted to take a deeper look. If found to be malicious, the scam extensions are blocked immediately.

While add-on reviewers are doing everything they can to find and snuff out crypto wallet scams before they can do harm, there are things users should be aware of as well to help protect themselves. “Check your crypto wallet’s website to see if they have an official extension, and only use the one they link to,” advises Wagner, while adding you might also consider reaching out directly to your crypto wallet service to confirm you’re selecting a legitimate extension. You can never be overly cautious when it comes to protecting your digital assets. There are too many disastrous tales out there.

The post Crypto wallet scams — thwarting a new threat appeared first on Mozilla Add-ons Community Blog.

SUMO BlogDecommissioning of the Social Support and Mobile Store Support programs

Hi everyone,

After much thoughtful consideration and evaluation, we’ve made the difficult decision to officially decommission the Social Support and Mobile Store Support programs. This wasn’t a decision made lightly. We recognize the immense dedication, time, and care, that so many of you have poured into these programs over the years. We’re truly grateful for everything you’ve done to support users and represent Mozilla in these spaces that have made users feel heard, supported, and connected to our mission.

The primary reason behind this decision is our team’s choice to discontinue activity on the X platform (formerly known as Twitter). While we value the interaction and connections we’ve had on this channel in the past, the social media landscape has evolved, and we’ve seen a steady decline in the impact of our interactions in this channel.

While we are stepping back from the platform, we have intentionally chosen to maintain ownership of our existing accounts (including @FirefoSupport and @SUMO_Mozilla). This allows us to protect our identity, prevent impersonation and maintain a minimal presence in case an emergency situation arises.

This change also reflects a shift in our overall support strategy, as we’ll be focusing our limited resources on the Mozilla Support Community Forums as our primary support channel. Over the past year, we’ve seen a notable increase in forum activity, but our ability to respond hasn’t been able to keep up with the volume. For comparison, our Q1 2025 total volume increased for almost 120% (exclude those that marked as spam) compared to the same period last year. There’s a growing need and clear opportunity for us to do more here, and your continued involvement will be more valuable than ever.

Although these programs are winding down, the impact you’ve had has been meaningful and deeply appreciated. And to honor your contributions, we’ve issued a set of special SUMO badges to recognize those of you who supported these efforts over the years.

Due to the limited data retention policy from the third-party tool that we’re using, we were only able to retrieve contributor data going back to 2023. Based on this, we’ve issued a total of seven badges:

  • Top 3 Contributors for Social Support (2023, 2024, and 2025)
  • Top 3 Contributors for Mobile Store Support (2023, 2024, and 2025)
  • An Honorary Badge for everyone who made a significant contribution to these programs

Thank you for your passion, commitment, and dedication to these programs throughout the years. Many of you have made a real difference for countless Firefox users around the world. This is a moment to reflect and be proud of everything we’ve done together.

To read our FAQ related to this decision, feel free to check out this Community Discussion thread. If you have additional questions or concerns, you can also share on the same thread.

Blog of DataGlean Memory Usage Reporting

Since Bug 1896609 landed we now have Glean & Firefox on Glean (FOG) memory reporting built into the Firefox Memory Reporter. This allows us to measure the allocated memory in use by Glean and FOG. It currently covers memory allocated by the C++ module of FOG and all instantiated Glean metrics. It does not yet measure the memory used by Glean and its database.

How it works

Firefox has a built-in memory usage reporter, available as about:memory. Components of Firefox can expose their own memory usage by implementing the nsIMemoryReporter interface. FOG implements this interface and delegates the measurement to the firefox-on-glean Rust component.

firefox-on-glean then collects the memory usage of objects under its own control: all user-defined and runtime-instantiated metrics, additional hashmaps used to track metrics & all user-defined and runtime-instantiated pings. It will soon also collect the memory size of the global Glean object, and thus the memory used for built-in metrics as well as the in-memory database.

Memory measurement works by following all heap-allocated pointers, asking the allocator for the memory size of each and summing everything up. Because we do most of this measurement in Rust we use the existing wr_malloc_size_of crate, which already implements the correct measurement for most Rust libstd types as well as some additional library-provided types. Our own types implement the required trait using malloc_size_of_derive for automatically deriving the trait, or manual implementations.

How it looks

The memory measurement is built into Firefox and works in every shipped build. Open up about:memory in a running Firefox, click the “Measure” button and wait for the measurement. Once all data is collected it will show a long tree of measured allocations across all processes. Type fog into the filter box on the right to trim it down to only allocations from the fog component. The exact numbers differ between runs and operating systems.

You will see a view similar to this:

<p><em>about:memory on a freshly launched developer build of Firefox. fog reports 0.35 MB of allocated memory in the main process.</em></p>

about:memory on a freshly launched developer build of Firefox. fog reports 0.35 MB of allocated memory in the main process.

After opening a few tabs and browsing the web a new measurement on about:memory will show a different number, as Glean is instantiating more metrics and therefore allocating more memory. This number will grow as more metrics are instantiated and kept in memory.

This currently does not show the allocations from the global Glean object and its in-memory database. In the future we will be able to measure those allocations as well. In a prototype locally this already works as expected: As more data is recorded and stored the allocated memory grows. Once a ping is assembled, submitted and sent the allocations will be freed and about:memory will report less memory allocated again.

The Mozilla Thunderbird BlogVIDEO: Talking MZLA with Ryan Sipes

In this month’s Community Office Hours, we’re chatting with our director Ryan Sipes. This talk opens with a brief history of Thunderbird and ends on our plans for its future. In between, we explain more about MZLA and its structure, and how this compares to the Mozilla Foundation and Corporation. We’ll also cover the new Thunderbird Pro and Thundermail announcement And we talk about how Thunderbird put the fun in fundraising!

And if you’d like to know even more about Pro, next month we’ll be chatting with Services Software Engineer Chris Aquino about our upcoming products. Chris, who most recently has been working on Assist, is both incredibly knowledgeable and a great person to chat with. We think you’ll enjoythe upcoming Community Office Hours as much as we do.

April Office Hours: Thunderbird and MZLA

The beginning is always a very good place to start. We always love hearing Ryan recount Thunderbird’s history, and we hope you do as well. As one of the key figures in bringing Thunderbird back from the ashes, Ryan is ideal to discuss how Thunderbird landed at MZLA, its new home since 2020. We also appreciate his perspective on our relationship to (and how we differ from) the Mozilla Foundation and Corporation. And as Thunderbird’s community governance model is both one of its biggest strengths and a significant part of its comeback, Ryan has some valuable insights on our working relationship.

Thunderbird’s future, however, is just as exciting a story as how we got here. Ryan gives us a unique look into some of our recent moves, from the decision to develop mobile apps to the recent move into our own email service, Thundermail, and the Thunderbird Pro suite of productivity apps. From barely surviving, we’re glad to see all the ways in which Thunderbird and its community are thriving.

Watch, Read, and Get Involved

The entire interview with Ryan is below, on YouTube and Peertube. There’s a lot of references in the interview, which we’ve handily provided below. We hope you’re enjoying these looks into what we’re doing at Thunderbird as much as we’re enjoying making them, and we’ll see you next month!

VIDEO (Also on Peertube):

Resources

  • The untold history of Thunderbird: https://blog.thunderbird.net/2023/11/the-untold-history-of-thunderbird/
  • The Mozilla Foundation: https://wiki.mozilla.org/Foundation
  • Thunderbird’s New Home at MZLA: https://blog.thunderbird.net/2020/01/thunderbirds-new-home/
  • Community Office Hours with the Thunderbird Council: https://blog.thunderbird.net/2024/09/video-learn-about-the-thunderbird-council/
  • The Mozilla Manifesto: https://www.mozilla.org/about/manifesto/
  • Thundermail and Thunderbird Pro Announcement: https://blog.thunderbird.net/2025/04/thundermail-and-thunderbird-pro-services/
  • Get Involved: https://www.thunderbird.net/participate/

The post VIDEO: Talking MZLA with Ryan Sipes appeared first on The Thunderbird Blog.

SUMO BlogIntroducing Flavius Floare

Hi folks,

I’m so excited to share that Flavius Floare joined our team recently as a Technical Writer. He’s working alongside with Dayani to handle the Knowledge Base articles. Here’s a bit more from Flavius himself:

Hi, everyone. My name is Flavius, and I’m joining the SUMO team as the new Technical Writer. I’m really excited to be here and look forward to collaborating with you. My goal is to be as helpful as possible, so feel free to reach out to me with suggestions or feedback.

Please join me to welcome Flavius into the team. He will also join our community call this week, so please make sure to join us tomorrow to say hi to him!

Web Application SecurityFirefox Security Response to pwn2own 2025

At Mozilla, we consider security to be a paramount aspect of the web. This is why not only does Firefox have a long running bug bounty program but also mature release management and security engineering practices. These practices combined with well-trained and talented Firefox teams are also the reason why we respond to security bugs as quickly as we do. This week at the security hacking competition pwn2own, security researchers demonstrated two new content-process exploits against Firefox. Neither of the attacks managed to break out of our sandbox, which is required to gain control over the user’s system.

Out of abundance of caution, we just released new Firefox versions in response to these attacks – all within the same day of the second exploit announcement. The updated versions are Firefox 138.0.4, Firefox ESR 128.10.1, Firefox ESR 115.23.1 and Firefox for Android. Despite the limited impact of these attacks, all users and administrators are advised to update Firefox as soon as possible.

Just last year at the same security event, we responded to an exploitable security bug within 21 hours, for which we earned an award as the fastest to patch. But this year was special. This year, two security researchers signed up to attack Firefox at pwn2own. We continued the same rapid security response this year too.

Background

Pwn2Own is an annual computer hacking contest where participants aim to find security vulnerabilities in major software such as browsers. This year, the event was held in Berlin, Germany, and a lot of popular software was listed as potential targets for security research. As part of the event preparation, we were informed that Firefox was also listed as a target. But it took until the day before the event when we learned that not just one but two groups signed up to demonstrate their work.

Typically, people attacking a browser require a multi-step exploit. At first, they need to compromise the web browser tab to gain limited control of the user’s system. But due to Firefox’s robust security architecture, another bug (a sandbox escape) is required to break out of the current tab and gain wider system access. Unlike prior years, neither participating group was able to escape our sandbox this year. We have verbal confirmation that this is attributed to the recent architectural improvements to our Firefox sandbox which have neutered a wide range of such attacks. This continues to build confidence in Firefox’s strong security posture.

To review and fix the reported exploits a diverse team of people from all across the world and in various roles (engineering, QA, release management, security and many more) rushed to work. We tested and released a new version of Firefox for all of our supported platforms, operating systems, and configurations with rapid speed.

Our work does not end here. We continue to use opportunities like this to improve our incident response. We will also continue to study the reports to identify new hardening features and security improvements to keep all of our Firefox users across the globe protected.

Related Resources

If you’re interested in learning more about Mozilla’s security initiatives or Firefox security, here are some resources to help you get started:

Mozilla Security
Mozilla Security Blog
Bug Bounty Program

Furthermore, if you want to kickstart your own security research in Firefox, we invite you to follow our deeply technical blog at Attack & Defense – Firefox Security Internals for Engineers, Researchers, and Bounty Hunters .

Update – August 7th, 2025

We are pleased to share that Mozilla was awarded the Vanguard “Speedrunner” Award by the Zero Day Initiative (ZDI). This is in regonition to being consistently fast throghout the last 20 years of Zero Day Initiative’s pwn2own events.

Photo of the trophy. It looks like a big V-letter shaped wooden block, on top of a metal foot. The left side of the V says  Vanguards Awards 2025 and the right side says Speedrunner. There is also text indicating this was awarded by the Trend Micro Zero Day Initiative (ZDI)

“Speedrunner” trophy, awarded to Mozilla Firefox for an outstanding security response during pwn2own.

The post Firefox Security Response to pwn2own 2025 appeared first on Mozilla Security Blog.

The Mozilla Thunderbird BlogThunderbird for Mobile April 2025 Progress Report

Here is an update of what Thunderbird’s mobile community has been up to in April 2025. With a new team member, we’re getting Thunderbird for iOS out in the open and continuing to work on release feedback from Thunderbird for Android.

The Team is Growing

Last month we introduced Todd and Ashley to the MZLA mobile team, and now we have another new face in the team! Rafael Tonholo joins us as a Senior Android Engineer to focus on Thunderbird for Android. He also has much experience with Kotlin Multiplatform, which will be beneficial for Thunderbird for iOS as well.

Thunderbird for iOS

We’ve published the initial repository of Thunderbird for iOS! The application doesn’t really do a lot right this moment, since we intend to work very incrementally and start in the open. You’ll see a familiar welcome screen, slightly nicer than Thunderbird for Android and have the opportunity to make a financial contribution.

Testflight Distribution

We’re planning to distribute Thunderbird for iOS through TestFlight. To support that, we’ve set up an Apple Developer account and completed the required verification steps.

Unlike Android, where we maintain separate release and beta versions, the iOS App Store will have a single “Thunderbird” app. Apple prefers not to list beta versions as separate apps, and their review process tends to be stricter. Once the main app is published, we’ll be able to use TestFlight to offer a beta channel.

Before the App Store listing goes live, we’ll use TestFlight to distribute our builds. Apple provides an internal TestFlight option that doesn’t require a review, but it only works if testers have access to the developer account. That makes it unsuitable for community testing.

Initial Features for the Public Testflight Alpha

To share a public TestFlight link, we need to pass an initial App Store review. Apple expects apps to meet a minimum bar for functionality, so we can’t publish something like a simple welcome screen. Our goal for the first public TestFlight build is to support manual account setup and display emails in the inbox. Here are the specifics:

  • Initial account setup will be manual with hostname/username/password.
  • There will be a simple message list that will only show the INBOX folder messages, with a sender, subject, and maybe 2–3 preview lines.
  • You’ll have the opportunity to pull to refresh your inbox.

That is certainly not what you’d call a fully functional email client, but it could qualify for bare minimum functionality required for the Apple review. We have more details and a feature comparison in this document.

In other exciting news, we’re going to build Thunderbird for iOS with JMAP support first and foremost. While support on the email provider side is limited, we start with a modern email stack. This will allow us to build towards some of the features that email from the late 80’s was missing. We’ll be designing the code architecture in a way that adding IMAP support is very simple, so it will ideally follow soon after.

iOS Release Engineering and Localization

We’ve also gone through a few initial conversations on what the release workflow might look like. We’re currently deciding between:

  • GitHub Actions with Upload Actions (Pro: very open, re-use of some work on the Thunderbird for Android side. Con: Custom work, not many well-supported upload actions)
  • GitHub Actions with Fastlane (Pro: very open, well-supported, uses the same listing metadata structure we already have on Android. Con: Ruby as yet another language, no prior releng work)
  • Xcode Cloud (Pro: built in to Xcode, easy to configure, we’ll probably get by with the free tier for quite some time. Con: Not very open, increasing build cost)
  • Bitrise (Pro: Easy to configure, used by Firefox for iOS, we’ll get some support from Mozilla on this. Con: Can be pricy, not very open)

For now, our release process is pressing a button every once in a while. Xcode makes this very easy, which gives the release operations more time to plan a solution.

For localization, we’re aiming to use Weblate, just as Thunderbird for Android. The strings will mostly be the same, so we don’t need to ask our localizers to do double work.

Thunderbird for Android

We’re still focusing on release feedback by working on the drawer and looking to improve stability. April has very much been focused on onboarding the new team. I’ll keep the updates in this section a bit more brief, as we have less to explore and more to fix 🙂

  • We’ve accepted a new ADR to change the shared modules package from app.k9mail and com.fsck to net.thunderbird. We’ll be doing this gradually when migrating over legacy code.
  • Ashley has fixed a few keyboard accessibility issues to get started. She has also resolved a crash related to duplicate folder ids in the drawer. Her next projects are improving our sync debug tooling and other projects to resolve stability issues in retrieving emails.
  • Clément Rivière added initial support for showing hierarchical folders. The work is behind a feature flag for now, as we need to do some additional refactoring and crash fixes before we can release it. You can however try it out on the beta channel.
  • Fishkin removed a deprecated progress indicator, which provides slightly better support for Android watches.
  • Rafael fixed an issue related to Outlook/Microsoft accounts. If you have received the “Authentication Unsuccessful” message in the past, please try again on our beta channel.
  • Shamim continues on his path to refactor and move over some of our legacy code into the new modular structure. He also added support to attach files from the camera, and has resolved an issue in the drawer where the wrong folder was selected.
  • Timur Erofeev added support for algorithmic darkening where supported. This makes dark mode work better for a wider range of emails, following the same method that is used on web pages.
  • Wolf has been working diligently to improve our settings and drawer infrastructure. He took a number of much needed detours to refactor legacy code, which will make future work easier. Most notably,  we have a new settings system based on Jetpack Compose, where we will eventually migrate all the settings screens to.

That’s a wrap for April! Let us know if you have comments, or see opportunities to help out. See you soon!

The post Thunderbird for Mobile April 2025 Progress Report appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogThunderbird Monthly Developer Digest – April 2025

Hello from the Thunderbird development team! With some of our time spent onboarding new team members and interviewing for open positions, April was a fun and productive month. Our team grew and we were amazed at how smooth the onboarding process has been, with many contributions already boosting the team’s output.

Gearing up for our annual Extended Support Release 

We have now officially entered the release cycle which will become our annual “ESR” at the end of June. The code we’re writing, the features we’re adding, the bugs we’re fixing at the moment should all make their way into the next major update, to be enjoyed by millions of users. This most stable release is used by enterprises, governments and institutions who have specific requirements around consistency, long-term support, and minimized change over time.

If waiting a whole year doesn’t sound appealing to you, our Monthly release may be better suited. It offers access to the latest features, improvements, and fixes as soon as they’re ready. Watch out for an in-app invitation to upgrade or install over ESR to retain your profile settings.

Calendar UI Rebuild

The implementation of the new event dialog hit some challenges in April with the dialog positioning and associated tests causing more than a few headaches when our CI started reporting test failures that were not easy to debug. Not surprising given the 60,000 tests which run for this one patch alone!!

The focus on loading data into the various containers continues, so that we can enable this feature and begin the QA process.

Keep track of feature delivery via the [meta] bug 

Exchange Web Services support in Rust

Our 0.2 release will make it into the hands of Daily and QA testers this month, with only a handful of smaller items left in our current milestone, before the “polish” milestone begins. The following items were completed in April:

  • Connectivity check for EWS accounts
  • Threading support
  • Folder updates & deletions in sync
  • Folder cache cleanup
  • Folder copy/move
  • Bug fixes!

Our hope is to include this feature set to users on beta and monthly release in 140 or 141.

Keep track of feature delivery here.

Account Hub

The new email account feature was “preffed on” as the default experience for the Daily build but recent changes to our Oauth process have required some rework to this user experience. We’re currently working on designing a UX and associated functionality that can detect whether account autodiscovery requires a password, and react accordingly.

The redesigned UI for Address Book account additions is also underway and planned for release to users on 25th May.

Global Message Database

We welcomed a new team member in April so technical onboarding has been a priority. In addition, a long list of patches landed, with the team focused on refactoring core code responsible for the management of common folders such as Drafts or Sent Mail, and significant changes to nsIMsgPluggableStore.

Time was spent to research and plan a path to tackle dangling folders in May.

To follow their progress, the team maintains documentation in Sourcedocs which are visible here.

New Features Landing Soon

A number of requested features and important fixes have reached our Daily users this month. We want to give special thanks to the contributors who made the following possible…

If you would like to see new features as they land, and help us squash some early bugs, you can try running daily and check the pushlog to see what has recently landed. This assistance is immensely helpful for catching problems early.

Toby Pilling

Senior Manager, Desktop Engineering

Thunderbird

The post Thunderbird Monthly Developer Digest – April 2025 appeared first on The Thunderbird Blog.

Blog of DataData and Firefox Suggest

Introduction

Firefox Suggest is a  feature that displays direct links to content on the web based on what users type into the Firefox address bar. Some of the content that appears in these suggestions is provided by partners, and some of the content is sponsored. It may also include locally-stored items from the user’s history or bookmarks.

In building Firefox Suggest, we have followed our long-standing Lean Data Practices and Data Privacy Principles. Practically, this means that we take care to limit what we collect, and to limit what we pass on to our partners. The behavior of the feature is straightforward–suggestions are shown as you type, and are directly relevant to what you type.

We take the security of the datasets needed to provide this feature very seriously. We pursue multi-layered security controls and practices, and strive to make as much of our work as possible publicly verifiable.

In this post, we wanted to give more detail about what data is needed to provide this feature, and about how we handle it.

What is Firefox Suggest?

 

The address bar experience in Firefox has long been a blend of results provided by partners (such as the user’s default search provider) and information local to the client (such as recently visited pages). Firefox Suggest augments these data sources with search completions from Mozilla, which it displays alongside the local and default search engine suggestions.

Firefox Suggest data flow diagram

Suggest is currently available by default to users in the following countries:

  • The United States
  • The United Kingdom
  • France
  • Germany
  • Poland
  • Italy

Data Collected by Mozilla for an improved experience

Users with access to Suggest can choose to enable an expanded version of the feature.  This feature requires access to additional data and is only available to users who have chosen to opt-in (via an opt-in prompt or their Settings menu). When users have opted in to the improved experience, Mozilla collects the following information to power Firefox Suggest.

  • Clicks and impressions: Mozilla receives information about the fact that a suggestion was shared.  When a user clicks on a suggestion, Mozilla receives notice that a suggested link was clicked.
  • Location: Mozilla collects city-level location data along with searches, in order to properly serve location-sensitive queries.
  • Search keywords: Firefox Suggest sends Mozilla information about certain search keywords, which may be shared with partners (after being stripped of any personally identifiable information) to fetch the suggested content and improve the Suggest feature.

How Data is Handled and Shared

Mozilla handles this data conservatively. When passing data on to our partners, we are careful to only provide the partner with the minimum information required to serve the feature.

For example, we only do not share user’s specific search queries (except where the user has signed up for the enhanced experience), and we do not identify which specific user sent the request, or use cookies to track users’ online activity after their search is performed.

Similarly, while a Firefox client’s location can typically be determined from their IP address, we convert a user’s IP address to a more general location immediately after we receive it, and we remove it from all datasets and reports downstream. Access to machines and (temporary, short-lived) datasets that might include the IP address is highly restricted, and limited only to a small number of administrators. We don’t enable or allow analysis on data that includes IP addresses.

We’re excited to be bringing Firefox Suggest to you. See the product announcement to learn more!

EDIT: May 7, 2025: Updated to clarify product details and reflect changes.

 

SeaMonkeySeaMonkey 2.53.21 Beta 1 is out!

Hi All,

The SeaMonkey Project is pleased to announce the immediate release of SeaMonkey 2.53.21 Beta 1.

Please check out [1] and/or [2].

As usual, updates are forthcoming.

:ewong

[1] – https://www.seamonkey-project.org/releases/seamonkey2.53.21

[2] – https://www.seamonkey-project.org/releases/2.53.21b1

Mozilla L10NLost (and Found) in Translation: My Internship Story

If you were to ask my parents or sister what my favourite hobby was as a child, they’d say something along the lines of “sitting in front of our family computer”. I’d spend hours browsing the internet, usually playing Flash games or watching early YouTube videos. Most of my memories of using the computer are now a blur, however, one detail stands out. I distinctly remember that our family computer used Mozilla Firefox as our primary internet browser. So imagine my surprise when I was offered an opportunity to intern here at Mozilla!

In the midst of my third year studying Computer Engineering at the University of Toronto, I had been searching for a 12-month internship to complete our Professional Experience Year (PEY) Co-op credit. Incredibly, I landed the privilege of working at Mozilla for 12 months alongside 17 other students. Coincidentally, one of my closest friends from high school would also be completing his internship at Mozilla too!

As a Software Engineer (SWE) Intern, I had been hired on the Localization (L10N) team, and would be based out of the Toronto office. I had already connected with both my manager, Francesco “Flod” Lodolo, and my mentor, Matjaž Horvat, before my start date. I couldn’t wait to begin my internship, and after I finished my final exam for third year, I began counting the days before my start date.

LGTM! (Onboarding)

From our first day at the office, I knew I was going to love working here. The Toronto office is so vibrant and filled with some truly amazing people! After finishing the office tour with the rest of the interns, we booted up our computers and began installing all our tools. Luckily for me, Ayanaa (who was the previous SWE Intern on the Localization team) was in the office too. She would be here until the end of August, helping to mentor and guide me along the way.

With her help, I got started on some bug fixes in Pontoon, Mozilla’s translation management system. I was mainly using Python (specifically the Django framework) and JavaScript/TypeScript (React) for the duration of the internship. Since I had some prior internship experience with these tools, I was able to hit the ground running, and by the end of my third month I had already completed 12 tickets! Matjaž and Flod were both instrumental in my progress, and with their help, I narrowed down the larger projects I wanted to work on for the rest of my internship.

I also took an interest in web standards within my first few months. Eemeli, the other engineer on our team, was an active contributor to the MessageFormat2 API, a new Unicode standard for localization. With his support, I was able to attend the Working Group’s weekly meetings. These meetings included some of the most influential and experienced people in this domain, spanning across many large companies and organizations.

Our first day tour of the Toronto office!

Coast to Continent to Coast (MozWeek and Work Week)

Around the middle of August, we were given the opportunity to attend MozWeek 2024, which is our annual week-long, company-wide conference. MozWeek 2024 was being held in Dublin, Ireland, so this was my first time ever travelling to Europe! From day one, the atmosphere at The Convention Centre Dublin was electric. I could tell a lot of thought, planning, and care went into creating the best possible experience for all employees. Throughout the week, we attended plenary talks, workshops, and strategic meetings.

Seeing how Mozilla is a remote-first international company, this was the first time I had met any of my full-time colleagues in person. It was so nice to finally see and chat with them outside my laptop screen. We even had our team dinner next to the famous Temple Bar! In our free time, the other interns and I had a blast walking through the streets of Dublin, and exploring what Ireland has to offer.

The interns and I at the MozWeek 2024 Closing Party, hosted at the Guinness Storehouse.

Dublin wasn’t my only travel destination though. Each team meets up once a year in one of Mozilla’s many office spaces across the world. Owing to our remote-first policy, these ‘Work Weeks’ are an opportunity for teams to reflect on the past year and align on OKRs for the coming year. Our Work Week happened in November, in sunny San Mateo, California, marking my first time on the West Coast! The Work Week was a great experience filled with good food, and it was super fun to explore San Francisco in my free time.

L10N team dinner at Porterhouse Restaurant San Mateo!

Building for a Better Web (Projects Overview)

One of my favourite parts of working at Mozilla was that almost all of my work was public-facing. I worked on three major projects during my internship, so here’s a brief description of each:

Pontoon Search

My first major project had me improving Pontoon’s search capabilities. Despite the many filters Pontoon already contained to sift through over 4.5 million strings, there were still no options for common filters like ‘Match Case’ or to limit a search to specific elements, like source text. My job was to create a new full-stack feature to enable users to refine their search queries. By leveraging TypeScript, React, and Django’s ORM capabilities, I created a new search panel with 5 options for users to toggle:

Multiple options

Improving the searching in Pontoon not only made the user experience more streamlined, but also improved Pontoon’s API capabilities, which was later used in the Mozilla Language Portal (see below).

Pontoon Achievement Badges

My second major project involved adding gamification elements into Pontoon. In a nutshell, we wanted to implement achievement badges into Pontoon to recognize contributions made by our vibrant volunteer community, while also further promoting positive behaviours on the platform. Ayanaa had created both the proposal document and technical specification before her term ended, so it was my job to implement the feature. This project mainly involved TypeScript and a bit of Django for counting badge actions, and the initial user feedback was overwhelmingly positive! For more information, check out the blog post I wrote to announce the feature.

Achievement badges

Mozilla Language Portal

My final project, and the one I had the most ownership over, was the creation of the Mozilla Language Portal. For a long time, the localization industry was missing a central hub for sharing knowledge, best practices, and searchable translation memories. We decided it was a good idea to leverage our influence to create the Mozilla Language Portal, in hopes to fill this gap and make localization tools themselves more accessible. We decided to create the Portal using Birdbox, an internal tool created by the websites team to quickly spin up Mozilla-branded web pages. The deployment of the Portal was handled primarily through Google Cloud Services and Terraform, which was a whole new set of tools for me to learn. The website itself was made using Wagtail CMS, built on top of Django. With the help of the Websites and Site Reliability Engineering teams, I was able to both create the MVP and deploy the site.

Closing Thoughts

Since taking an anthropology course in my third year of university, I’ve come to appreciate how important human connection and social interactions are, especially in this day and age. Most people would agree that technology (in particular the internet) has now thoroughly integrated itself into the fabric of our societies, so I believe it’s in our collective best interest to keep the internet in a healthy and open state. In recent years, it sadly seems like many bad actors are increasing their influence and control over what should be a vital and protected resource. As one of my long-term goals, I want to focus my career towards improving the internet and using its influence over society for good.

So naturally with this goal in mind, Mozilla’s position as a non-profit organization dedicated to creating an open and accessible web was a perfect fit for me. Coincidentally, Localization was also the perfect team for me. As a very community-facing team, Localization gave me the unique chance to see the direct results of creating technology to make the internet more accessible, and I was able to explore my burning interests such as web standards.

I think it goes without saying that the lessons I learned at Mozilla, both from an engineering perspective and from a community perspective, will stick with me for the rest of my career. Regardless of if I continue to be a SWE in the future, I want to focus on creating technology to grow and help humanity, and thus I’ve promised myself to only work for organizations whose missions I align with.

To me, my time at Mozilla will always be emblematic of my growth: as a student, as an engineer, and as an individual. They say all good things must come to an end, but I oddly don’t feel as though my time at Mozilla is coming to an end. The lessons instilled in me and the drive to keep fighting for an open web won’t ever leave me.

Team photo with everyone! Taken in August 2024

 

Acknowledgements

I’d like to dedicate this section to my amazing team that has supported me and helped me grow both professionally and personally this past year.

To Ayanaa, thank you for being a great coworker, mentor and friend. I’ve been following the path you carved out, both at Mozilla and beyond, and I’m extremely grateful for all the advice and support you gave me throughout.

To Matjaž, I can’t really put into words how helpful and kind you have been to me. You truly have a talent for mentoring, and I’m so incredibly grateful you were my mentor. I hope you continue to inspire others the way you’ve inspired me. Let’s hope Lebron and Luka can win it all (eventually).

To Flod, your support as my manager has been monumental to my professional development. Thank you for being patient with me, and for supporting all of my interests and endeavors during my term. It sounds cliché, but I truly couldn’t have asked for a better manager.

To Eemeli, thank you for supporting my interest in MessageFormat2. Your great sense of humour will definitely stick with me, and you’ve inspired me to carry on your tradition of taking walks during online meetings.

To Bryan, it was always such a pleasure to speak and work with you. I’m glad I had someone else to nerd-out with about Pokémon! I really appreciate how we could always find something to talk about.

To Peiying, I loved hearing all about your travel anecdotes during MozWeek and our Work Week. I promise to keep my photo blog updated as long as you do too! I hope to see you and Leo again soon.

To Delphine, your enthusiasm and bubbly personality always brought a smile to my face. It was so nice to finally have met you during our Work Week! Congrats again on all your personal achievements in this past year.

And thank you to all the Mozillians I’ve had the privilege to work with this past year, both in the Toronto office and across the globe. I’m sure our paths will cross again! As they say, “once a Mozillian, always a Mozillian”.

*Thanks for reading, and if you’d like to learn more or connect with me, please feel free to add me on LinkedIn*

Mozilla L10NL10n report: April 2025 Edition

Please note some of the information provided in this report may be subject to change as we are sometimes sharing information about projects that are still in early stages and are not final yet. 

Welcome!

Are you a locale leader and want us to include new members in our upcoming reports? Contact us!

What’s new or coming up in Firefox desktop

There are a number of new features launched recently or upcoming in Nightly to look out for.

Smart Tab Grouping

With the recent release of Tab Groups in Firefox 137, we’ll see some additional development on enhancements in the future. Currently only available in English on Nightly, Smart Tab Grouping uses a local AI model to suggest similar tabs to group together.

Link Previews

This feature will be coming to Firefox Labs in 138, Link Previews uses a local AI model to quickly see what’s behind a link, by distilling key points from the page.

Signing in PDFs

You have likely seen these strings while working on Beta, but the ability to add signatures using the built-in PDF editor will be released fully in the upcoming 138 release on April 29.

What’s new or coming up in mobile

We’re adding customization options for Firefox icons on mobile! Some of the icon names may be tricky to localize, so we’ll be sharing a reference sheet that includes each icon along with its visual and contextual usage. This will help you choose the most accurate and user-friendly translations for your locale. Keep an eye out for upcoming Pontoon notifications for more details!

What’s new or coming up in web projects

AMO and AMO Frontend

To enhance user experience, the AMO team has established a minimum translation completion threshold of 80% for locales to remain on production sites. The team will start implementing the new policy in May. Last month, locales with a completion rate of 40% or lower were removed from the production site. However, affected communities can continue making progress in Pontoon, and their status will change once they meet the threshold.

Once this new standard is fully implemented, the addon team will reassess the list of locales on a monthly basis, evaluating those that have met or fallen below the 80% threshold. Based on this review, they will determine which locales to retain and which to remove from the production site. Regardless of your locale’s current status, you can check your work in context using the links to the production, staging, and developer sites which can be found on the top left of the project dashboards.

What’s new or coming up in Pontoon

We’re working on some sizable back-end improvements to how Pontoon internally represents and deals with translatable messages, i.e. source-locale entries and their translations. Thus far we’ve refactored Pontoon’s sync code (how it reads from and writes data to project repositories) and the serialization of our supported file formats; the next step will be replacing our file format parsers.

Mostly this work should remain invisible to users, though it has already allowed us to fix quite a few long-standing bugs and improved sync performance. Eventually, this will make it much easier for us to expand the file formats and features supported by Pontoon.

Events

We are hosting our first localization office hour on Apr 30, 2025 at 3:30pm UTC, it will be live streamed on both AirMozilla and YouTube (recordings can be found at the same links). This session will focus on common errors localizers may encounter and how to overcome them. Feel free to ask questions beforehand via the Google form or reach out directly to delphine at mozilla dot com.

Want to showcase an event coming up that your community is participating in? Contact us and we’ll include it.

Friends of the Lion

Know someone in your l10n community who’s been doing a great job and should appear here? Contact us and we’ll make sure they get a shout-out!

Useful Links

Questions? Want to get involved?

If you want to get involved, or have any question about l10n, reach out to:

Did you enjoy reading this report? Let us know how we can improve it.

Blog of DataComparing data-stewardship at Mozilla with Lauren Maffeo’s book “Designing Data Governance from the Ground Up”

Data Stewardship: A Mozilla Perspective

In Designing Data Governance from the Ground Up, author Lauren Maffeo presents data stewardship as a pivotal role in data governance that is focused on maintaining data quality, consistency, and usability. Data stewards, in her view, are operational experts who ensure that data is of the highest quality, aligns with organizational standards, and supports business objectives.

At Mozilla, rather than taking such a broad role in data governance, a data steward’s responsibilities are deeply intertwined with the organization’s commitment to user privacy and ethical data practices. This approach reflects Mozilla’s mission to promote an open and accessible internet while safeguarding user trust.

Maffeo’s Framework: Operational Excellence

Maffeo outlines data stewards as key players in:

  • Ensuring Data Accuracy: Identifying and correcting data quality issues.
  • Maintaining Metadata: Documenting data definitions and standards.
  • Enforcing Policies: Applying data governance policies consistently.
  • Facilitating Collaboration: Bridging gaps between technical and business teams.

This model emphasizes the importance of data stewards in operationalizing data governance to enhance data quality, decision-making, and organizational efficiency. This work is spread amongst the product, data, data-engineering, and other organizations at Mozilla.

Mozilla’s Approach: Privacy-Centric Stewardship

At Mozilla, data stewards focus on:

  • Evaluating Data Collection Requests: As outlined in Mozilla’s Data Collection documentation, data stewards are responsible for reviewing proposed data collections to ensure they align with Mozilla’s Data Privacy Principles, which emphasize user control, transparency, and minimal data collection.
  • Collaborating Across Teams: Working with engineers, product managers, and legal teams to assess the necessity and impact of data collection and helping to ensure the collection is properly categorized and documented in a public way that is accessible to our users.
  • Advocating for Lean Data Practices: Promoting the collection of only essential data needed to improve user experiences, in line with Mozilla’s commitment to user privacy.
  • Guiding Data Publishing: Ensuring that any data shared publicly adheres to Mozilla’s Data Publishing policies, which categorize data sensitivity and dictate appropriate aggregation levels to protect user anonymity.

This stewardship model is proactive, emphasizing ethical considerations and user trust over data quality and operational efficiency.

Mozilla’s Data Stewardship in Practice

Mozilla’s data stewards operate within a structured framework that includes:

Data Collection Review: Any new data collection undergoes a review process to assess its necessity, potential privacy impact, and alignment with Mozilla’s principles. This includes ensuring data is correctly categorized by its sensitivity in order to ensure it is properly handled.

User Control and Transparency: Mozilla ensures users have meaningful choices regarding data collection, including the ability to opt-out and have their data deleted.

Public Data Sharing: When publishing data, Mozilla applies rigorous standards to prevent the release of sensitive information, following guidelines outlined in their Data Publishing documentation.

This approach ensures that data stewardship at Mozilla is less focused on managing data, but more about upholding the organization’s core values of user privacy and transparency.

Conclusion

Lauren Maffeo’s framework provides a solid foundation for understanding the operational aspects of data governance. Mozilla’s implementation of data stewardship focuses this role on ethical responsibility and user advocacy. At Mozilla, data stewards are less “custodians of data quality” and more “champions of user privacy”, ensuring that every data-related decision aligns with the organization’s mission to foster an open and trustworthy internet.

If you’re interested in learning more about Mozilla’s data practices or becoming involved in data stewardship initiatives, feel free to reach out to the Data Stewardship team.

The Mozilla Thunderbird BlogVIDEO: The New Account Hub

In this month’s Community Office Hours, we’re chatting with Vineet Deo, a Software Engineer on the Desktop team, who walks us through the new Account Hub on the Desktop app. If you want a sneak peak at this new streamlined experience, you can find it in the Daily channel now and the Beta channel towards the end of April.

Next month, we’ll be chatting with our director Ryan Sipes. We’ll be covering the new Thunderbird Pro and Thundermail announcement and the structure of MZLA compared to the Mozilla Foundation and Corporation. And we’ll talk about how Thunderbird put the fun in fundraising!

March Office Hours: The New Account Hub

Setting up a new email account in Thunderbird is already a solid experience, so why the update? Firstly, this is the first thing new users will see in the app. Thus, it’s important it has the same clean, cohesive look that is becoming the new Thunderbird design standard. It’s also helpful for users coming from other email clients to have a familiar, wizard-like experience. While the current account setup works well, it’s browser based. This makes it possible a user could exit out before finishing and get lost before they even started. This is the opposite of what we want for potential users!

Vineet and his team are also working to make the new Account Hub ready for Exchange. Likewise, they also have plans for a similar hub to set up new address books and calendars. We’re proud of the collaboration between back and frontend teams, and designers and engineers, to make the Account Hub.

Watch, Read, and Get Involved

But don’t take our word for it! Watch Vineet’s Account Hub talk and demo, along with a Q&A session. If you’re comfortable testing Daily, you can test this new feature now. (Go to File > New > Email Account to start the experience.) Otherwise, keep an eye on our Beta release channel at the end of April. And if you’re watching this after Account Hub is part of the regular release, now you know the feature’s story!

VIDEO (Also on Peertube):

Get Involved

The post VIDEO: The New Account Hub appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogThunderbird for Android March 2025 Progress Report

Hello, everyone, and welcome to the Thunderbird for Android March 2025 Progress Report. We’re keeping our community updated on everything that’s been happening in the Android team, which is quickly becoming a more general mobile team with some recent hires. In addition to team news, we’re talking about our roadmap board on GitHub.

Team Changes

In March we said goodbye to cketti, the K-9 Mail maintainer who joined the team when Thunderbird first announced plans for an Android app. We’re very grateful for everything he’s created, and for his trust that K-9 Mail and Thunderbird for Android are in good hands. But we also said hello to Todd Heasley, our new iOS engineer, who started March 26. We also have just added Ashley Soucar, an Android/iOS engineer, who joined us on April 7. If all continues to go well, we’ll also be adding another Android engineer in the next couple of weeks.

Our Roadmap Board

Our roadmap board is now available! We’re grateful to the Council for their trust and support in approving it. As the board will reflect any changes in our planning, this is the most up-to-date source for our upcoming development. Each epic will show its objective and what’s in scope – and as importantly, what’s out of scope. The project information on the side will tell you if an epic is in the backlog or work in progress.

If you’d like to know what we’re working on right now, check out our sprint board.

Contribute by Triaging GitHub Issues

One way to contribute to Thunderbird for Android is by triaging open GitHub Issues. In March, we did a major triage with over 150 issues closed as duplicates, marked with ‘works for me,’ or elevating them up to the efforts and features described in the roadmap above. Especially since we’re a small team, triaging issues helps us know where to act on incoming issues. This is a great way to get started as a Thunderbird for Android contributor.


To start triaging bugs, have a look at the ‘unconfirmed’ issues. Try to reproduce the issue  to help verify that the issue exists. Then add a comment with your results and any other information you found that might help narrow down the issue. If you see users generally saying “it doesn’t work”, ask them for more details or to enable logs. This way we know when to remove the unconfirmed label. If you have questions along the way or need someone to confirm a thought you had, feel free to ask in the community support channel.

Account Drawer

Our main engineering focus in March has been the account drawer we shared screenshots on in the January/February update. Given the settings design includes a few non-standard components, we took the opportunity to write a modern settings framework based on Jetpack Compose and make use of it for the new drawer. There will be some opportunities to contribute here in the future, as we’d like to migrate our old settings UI to the new system.

We have a few crashes and rough edges to polish, but are very close to enabling the feature flag in beta. If you aren’t already using it and want to get early access, install our beta today.

I’d also like to call out a pull request by Clément, who contributed support for a folder hierarchy. The amazing thing here—our design folks were working out a proposal because we were interested in this as well, and without knowing, Clément came up with the same idea and came in with a pull request that really hit the spot. Great work!

Community Contributions

In addition to the folder hierarchy mentioned above, here are a few community activities in March:

  • Shamim made sure the Unified Inbox shows up when you add your second account, retained scroll position in the drawer when rotating, removed font size customizations in favor of Android OS controls, flipped the default for being notified about new email and helped out with a few refactorings to make our codebase more modern.
  • Sergio has improved back button navigation when editing drafts.
  • Salkinnoma made our workflow runs more efficient and fixed an issue in the find folders view where a menu item was incorrectly shown.
  • Smatek improved our edge to edge support by making the bottom Android navigation bar background transparent
  • Husain fixed some inconsistencies when toggling “Show Unified Inbox”.
  • Vayun has begun work to update the Thunderbird for Android app widgets to Jetpack compose (including dark theming)
  • SttApollo has made the logo size more dynamic in the onboarding screen.

This is quite a list, great work! When you think about Thunderbird for Android or K-9 Mail, what was the last major annoyance you stumbled upon? If you are an Android developer, now is a good time to fix it. You’ll see your name up here next time as well 🙂

The post Thunderbird for Android March 2025 Progress Report appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogThunderbird Monthly Development Digest – March 2025

Hello again Thunderbird Community! It’s been almost a year since I joined the project and I’ve recently been enjoying the most rewarding and exciting work days in recent memory. The team who works on making Thunderbird better each day is so passionate about their work and truly dedicated to solving problems for users and supporting the broader developer community. If you are reading this and wondering how you might be able to get started and help out, please get in touch and we would love to get you off the ground!

Paddling Upstream

As many of you know, Thunderbird relies heavily on the Firefox platform and other lower-level code that we build upon. We benefit immensely from the constant flow of improvements, fixes, and modernizations, many of which happen behind the scenes without requiring our input. 

The flip side is that changes upstream can sometimes catch us off guard – and from time to time we find ourselves firefighting after changes have been made. This past month has been especially busy as we’ve scrambled to adapt to unexpected shifts, with our team hunting down places to adjust Content Security Policy (CSP) handling and finding ways to integrate a new experimental whitespace normalizer. Very much not part of our plan, but critical nonetheless.

Calendar UI Rebuild

The implementation of the new event dialog is moving along steadily with the following pieces of the puzzle recently landing:

  • Title
  • Border
  • Location Row
  • Join Meeting button
  • Time & Recurrence

The focus has now turned to loading data into the various containers so that we can enable this feature later this month and ask our QA team and Daily users to help us catch early problems.

Keep track of feature delivery via the [meta] bug 

Exchange Web Services support in Rust

We’re aiming to get a 0.2 release into the hands of Daily and QA testers by the end of April so a number of remaining tasks are in the queue – but March saw a number of features completed and pushed to Daily

  • Folder copy/move
  • Sync folder – update
  • Complete composition support (reply/forward)
  • Bug fixes!

Keep track of feature delivery here.

Account Hub

This feature was “preffed on” as the default experience for the Daily build but recent changes to our Oauth process have required some rework to this user experience, so it won’t hit beta until the end of the month. It’s beautiful and well worth considering a switch to Daily if you are currently running beta.

Global Message Database

The New Zealand team completed a successful work week and have since pushed through a significant chunk of the research and refactoring necessary to integrate the new database with existing interfaces.

The patches are pouring in and are enabling data adapters, sorting, testing and message display for the Local Folders Account, with an aim to get all existing tests to pass with the new database enabled. The path to this goal is often meandering and challenging but with our most knowledgeable and experienced team members dedicated to the project, we’re seeing inspiring progress.

The team maintains their documentation in Sourcedocs which are visible here.

In-App Notifications

A few last-minute changes were made and uplifted to our ESR version early this month so if you use the ESR and are in the lucky 2% of users targeted, watch out for an introductory notification!
We’ve also wrapped up work on two significant enhancements which are now on Daily and will make their way to other releases over the course of the month:

  • Granular control of notifications by type via EnterprisePolicy
  • Enhanced triggering mechanism to prevent launch when Thunderbird is in the background

 Meta Bug & progress tracking.

New Features Landing Soon

A number of requested features and important fixes have reached our Daily users this month. We want to give special thanks to the contributors who made the following possible…

As usual, if you want to see and use new features as they land, and help us squash some early bugs, you can try running daily and check the pushlog to see what has recently landed. This assistance is immensely helpful for catching problems early.

Toby Pilling

Senior Manager, Desktop Engineering

The post Thunderbird Monthly Development Digest – March 2025 appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogThundermail and Thunderbird Pro Services

Today we’re pleased to announce what many in our open source contributor community already know. The Thunderbird team is working on an email service called “Thundermail” as well as file sharing, calendar scheduling and other helpful cloud-based services that as a bundle we have been calling “Thunderbird Pro.”

First, a point of clarification: Thunderbird, the email app, is and always will be free. We will never place features that can be delivered through the Thunderbird app behind a paywall. If something can be done directly on your device, it should be. However, there are things that can’t be done on your computer or phone that many people have come to expect from their email suites. This is what we are setting out to solve with our cloud-based services.

All of these new services are (or soon will be) open source software under true open source licenses. That’s how Thunderbird does things and we believe it is our super power. It is also a major reason we exist: to create open source communication and productivity software that respects our users. Because you can see how it works, you can know that it is doing the right thing.

The Why for offering these services is simple. Thunderbird loses users each day to rich ecosystems that are both products and services, such as Gmail and Office365. These ecosystems have both hard vendor lock-ins (through interoperability issues with 3rd-party clients) and soft lock-ins (through convenience and integration between their clients and services). It is our goal to eventually have a similar offering so that a 100% open source, freedom-respecting alternative ecosystem is available for those who want it. We don’t even care if you use our services with Thunderbird apps, go use them with any mail client. No lock-in, no restrictions – all open standards. That is freedom.

What Are The Services?

Thunderbird Appointment

Appointment is a scheduling tool that allows you to send a link to someone, allowing them to pick a time on your calendar to meet. The repository for Appointment has been public for a while and has seen pretty remarkable development so far. It is currently in a closed Beta and we are letting more users in each day.

Appointment has been developed to make meeting with others easier. We weren’t happy with the existing tools as they were either proprietary or too bloated, so we started building Appointment.

Thunderbird Send

Send is an end-to-end encrypted file sharing service that allows you to upload large files to the service and share links to download those files with others. Many Thunderbird users have expressed interest in the ability to share large files in a privacy-respecting way – and it was a problem we were eager to solve.

Thunderbird Send is the rebirth of Firefox Send – well, kind of. At this point, we have a bit of a Ship of Theseus situation – having rebuilt much of the project to allow for a more direct method of sharing files (from user-to-user without the need to share a link). We opened up the repo to the public earlier this week. So we encourage everyone interested to go and check it out.

Thunderbird Send is currently in Alpha testing, and will move to a closed Beta very soon.

Thunderbird Assist

Assist is an experiment, developed in partnership with Flower AI, a flexible open-source framework for scalable, privacy-preserving federated learning, that will enable users to take advantage of AI features. The hope is that processing can be done on devices that can support the models, and for devices that are not powerful enough to run the language models locally, we are making use of Flower Confidential Remote Compute in order to ensure private remote processing (very similar to Apple’s Private Cloud Compute). 

Given some users’ sensitivity to this, these types of features will always be optional and something that users will have to opt into. As a reminder, Thunderbird will never train AI with your data. The repo for Assist is not public yet, but it will be soon.

Thundermail

Thundermail is an email service (with calendars and contacts as well). We want to provide email accounts to those who love Thunderbird, and we believe that we are capable of providing a better service than the other providers out there. Email that aligns with our values of privacy, freedom and respect of our users. No ads, no selling or training AI on your data – just your email and it is your email.

With Thundermail, it is our goal to create a next generation email experience that is completely, 100% open source and built by all of us, our contributors and users. Unlike the other services, there will not be a single repository where this work is done. But we will try and share relevant places to contribute in future posts like this.

The email domain for Thundermail will be Thundermail.com or tb.pro. Additionally, you will be able to bring your own domain on day 1 of the service.

Heading to thundermail.com you will see a sign up page for the beta waitlist. Please join it!

Final Thoughts

Don’t services cost money to run?

You may be thinking: “this all sounds expensive, how will Thunderbird be able to pay for it?” And that’s a great question! Services such as Send are actually quite expensive (storage is costly). So here is the plan: at the beginning, there will be paid subscription plans at a few different tiers. Once we have a sufficiently strong base of paying users to sustainably support our services, we plan to introduce a limited free tier to the public. You see this with other providers: limitations are standard as free email and file sharing are prone to abuse.

It’s also important to highlight again that Thunderbird Pro will be a completely separate offering from the Thunderbird you already use. While Thunderbird and the additional new services may work together and complement each other for those who opt in, they will never replace, compromise, or interfere with the core features or free availability of Thunderbird. Nothing about your current Thunderbird experience will change unless you choose to opt in and sign up with Thunderbird Pro. None of these features will be automatically integrated into Thunderbird desktop or mobile or activated without your knowledge.

The Realization of a Dream

This has been a long time coming. It is my conviction that all of this should have been a part of the Thunderbird universe a decade ago. But it’s better late than never. Just like our Android client has expanded what Thunderbird is (as will our iOS client), so too will these services.

Thunderbird is unique in the world. Our focus on open source, open standards, privacy and respect for our users is something that should be expressed in multiple forms. The absence of Thunderbird web services means that our users must make compromises that are often uncomfortable ones. This is how we correct that.

I hope that all of you will check out this work and share your thoughts and test these things out. What’s exciting is that you can run Send or Appointment today, on your own server. Everything that we do will be out in the open and you can come and help us build it! Together we can create amazing experiences that enhance how we manage our email, calendars, contacts and beyond.

Thank you for being on this journey with us.

Ryan Sipes
Managing Director of Product
Thunderbird

The post Thundermail and Thunderbird Pro Services appeared first on The Thunderbird Blog.

Open Policy & AdvocacyNew Mozilla Research: Civil Liability Along the AI Value Chain

What happens when AI systems fail? Who should be held responsible when they cause harm? And how can we ensure that people harmed by AI can seek redress?

READ THE REPORT HERE

As AI is increasingly integrated in products and services across sectors, these questions will only become more pertinent. In the EU, a proposal for an AI Liability Directive (AILD) in 2022 catalyzed debates around this issue.  Its recent withdrawal by the European Commission leaves a wide range of open questions to linger as businesses and consumers will need to navigate fragmented liability rules across the EU’s 27 member states.

To answer these questions, policymakers will need to ask themselves: what does an effective approach to AI and liability look like?

New research published by Mozilla tackles these thorny issues and explores how liability could and should be assigned across AI’s complex and heterogeneous value chain.

Solving AI’s “problem of many hands” 

The report, commissioned from Beatriz Botero Arcila — a professor at Sciences Po Law School and a Faculty Associate at Harvard’s Berkman Klein Center for Internet and Society — explores how liability law can help solve the “problem of many hands” in AI: that is, determining who is responsible for harm that has been dealt in a value chain in which a variety of different companies and actors might be contributing to the development of any given AI system. This is aggravated by the fact that AI systems are both opaque and technically complex, making their behavior hard to predict.

Why AI Liability Matters

To find meaningful solutions to this problem, different kinds of experts have to come together. This resource is designed for a wide audience, but we indicate how specific audiences can best make use of different sections, overviews, and case studies.

Specifically, the report:

  • Proposes a 3-step analysis to consider how liability should be allocated along the value chain: 1) The choice of liability regime, 2) how liability should be shared amongst actors along the value chain and 3) whether and how information asymmetries will be addressed.
  • Argues that where ex-ante AI regulation is already in place, policymakers should consider how liability rules will interact with these rules.
  • Proposes a baseline liability regime where actors along the AI value chain share responsibility if fault can be demonstrated, paired with measures to alleviate or shift the burden of proof and to enable better access to evidence — which would incentivize companies to act with sufficient care and address information asymmetries between claimants and companies.
  • Argues that in some cases, courts and regulators should extend a stricter regime, such as product liability or strict liability.
  • Analyzes liability rules in the EU based on this framework.

Why Now?

We have already seen examples of AI causing harm, from biased automated recruitment systems to predictive AI tools used in public services and law enforcement generating faulty outputs. As the number of such examples will increase with AI’s diffusion across the economy, affected individuals should have effective ways of seeking redress and justice — as we have already argued in our initial response to the AILD proposal in 2022 — and businesses should be incentivized to take sufficient measures to prevent harm. At the same time, they should not be overburdened with ineffective rules and have legal certainty rather than facing a patchwork of varying rules across different jurisdictions in which they operate. A well-designed, targeted, and robust liability regime for AI could address all of these challenges — and we hope the research released today can contribute to a more grounded debate around this issue.

The post New Mozilla Research: Civil Liability Along the AI Value Chain appeared first on Open Policy & Advocacy.

Web Application SecurityUpdated GPG key for signing Firefox Releases

The GPG key used to sign the Firefox release manifests is expiring soon, and so we’re going to be switching over to a new signing subkey shortly.

The GPG fingerprint is 14F2 6682 D091 6CDD 81E3 7B6D 61B7 B526 D98F 0353. The new signing subkey’s fingerprint is 09BE ED63 F346 2A2D FFAB 3B87 5ECB 6497 C1A2 0256, and it expires 2027-03-13.

The public key can be fetched from KEY files from the latest Firefox Nightly, keys.openpgp.org, or from below. This can be used to validate existing releases signed with the current key, or future releases signed with the new key.

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFWpQAQBEAC+9wVlwGLy8ILCybLesuB3KkHHK+Yt1F1PJaI30X448ttGzxCz
PQpH6BoA73uzcTReVjfCFGvM4ij6qVV2SNaTxmNBrL1uVeEUsCuGduDUQMQYRGxR
tWq5rCH48LnltKPamPiEBzrgFL3i5bYEUHO7M0lATEknG7Iaz697K/ssHREZfuuc
B4GNxXMgswZ7GTZO3VBDVEw5GwU3sUvww93TwMC29lIPCux445AxZPKr5sOVEsEn
dUB2oDMsSAoS/dZcl8F4otqfR1pXg618cU06omvq5yguWLDRV327BLmezYK0prD3
P+7qwEp8MTVmxlbkrClS5j5pR47FrJGdyupNKqLzK+7hok5kBxhsdMsdTZLd4tVR
jXf04isVO3iFFf/GKuwscOi1+ZYeB3l3sAqgFUWnjbpbHxfslTmo7BgvmjZvAH5Z
asaewF3wA06biCDJdcSkC9GmFPmN5DS5/Dkjwfj8+dZAttuSKfmQQnypUPaJ2sBu
blnJ6INpvYgsEZjV6CFG1EiDJDPu2Zxap8ep0iRMbBBZnpfZTn7SKAcurDJptxin
CRclTcdOdi1iSZ35LZW0R2FKNnGL33u1IhxU9HRLw3XuljXCOZ84RLn6M+PBc1eZ
suv1TA+Mn111yD3uDv/u/edZ/xeJccF6bYcMvUgRRZh0sgZ0ZT4b0Q6YcQARAQAB
tC9Nb3ppbGxhIFNvZnR3YXJlIFJlbGVhc2VzIDxyZWxlYXNlQG1vemlsbGEuY29t
PokCTwQTAQIAIgUCValABAIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AAIQkQ
Ybe1JtmPA1MWIQQU8maC0JFs3YHje21ht7Um2Y8DU1CqD/9Gvr9Xu4uqsjDHRQWS
fI0lqxElmFSRjF0awsPXzM7Q1rxV7dCxik4LeiOmpoVTOmqboo2/x5d938q7uPdY
av2Q+RuNk2CG/LpXku9rgmTE7oszEqQliqKoXajUZ91rw19wrTwYXLgLQvzM3CUA
O+Z0yjjfza2Yc0ZtNN+3sF5VpGsT3Fb14aYZDaNg6yPFvkyxp0B1lS4rwgL3lkeV
QNHeAf0qqF9tBankGj3bgqK/5/YlTM2usb3x46bVBvwX2t4/NnYM5hEnI57inwam
X6SiMJc2e2QmBzAnVrXJETrDL1HOl4GUJ6hC4tL3Yw2d7515BlSyRNkWhhdRp1/q
9t1+ovSe48Ip2X2WF5/VA3ATfQhHKa3p+EkIV98VCMZ14x9KIIeBwjyJyFBuvOEE
IYZHdsAdqf1zYRtD6m6obcBrRiNfoNsYmNY4joDrVupI96ksIxVpepXaZkQhplZ1
mQ4eOdGtToIl1cb/4PibVgFnBgzrR4mQ27h4wzAwWdGweJZ/tuGoqm3C6TwfIgan
ajiPyKqsVFUkRsr9y12EDcfUCUq6D182t/AJ+qE0JIGO73tXTdTbqPTgkyf2etnZ
QQZum3L7w41NvfxZfn+gLrUGDBXwqLjovDJvt8iZTPPyMTzemOHuzf40Iq+9sf5V
9PXZ/5X9+ymE3cTAbAk9MLd9fbkCDQRkVUBzARAA1cD3n5ue0sCcZmqX2FbtIFRs
k39rlGkvuxYABsWBTzr0RbRW7h46VzWbOcU5ZmbJrp/bhgkSYRR3drmzT63yUZ62
dnww6e5LJjGSt19zzcber9BHELjqKqfAfLNsuZ7ZQ5p78c6uiJhe8WpbWogbspxJ
20duraLGmK4Kl23fa3tF0Gng1RLhoFcSVK/WtDZyC+elPKpch1Sru6sw/r8ktfuh
NIRGxdbj/lFHNVOzCXb3MTAqpIynNGMocFFnqWLZLtItphHxPUqVr6LKvc3i3aMl
C6IvLNg0Nu8O088Hg3Ah9tRmXKOshLjYjPeXqM9edqoWWqpzxDTNl6JlFMwP+Oac
MKsyX7Wq+ZXC/o3ygC/oclYUKtiuoGg47fSCN2GS3V2GX2zFlT6SEvEQQb2g5yIS
LX9Q/g9AyJdqtfaLe4Fv6vM4P1xhOUDnjmdoulm3FGkC701ZF7eFhMSRUM9QhkGH
6Yz2TvS4ht6Whg7aVt4ErIoJfj9jzJOp6k9vna5Lmgkj8l19NTiUQ7gk98H3wW4m
RrINxZ2yQD47V/LJ+tUamJc5ac+I0VP7c15xmKEJ2rfGCGhiSWQwZZw7Y2/qoADS
BlI28RlBTuRP2i6AdwyJU+75CzxGzMpr/wBLhZT+fNRV4HHd5dgR3YxajpkzZ6wX
L2aaJhznFEmLBLokOwMAEQEAAYkEcgQYAQoAJhYhBBTyZoLQkWzdgeN7bWG3tSbZ
jwNTBQJkVUBzAhsCBQkDwmcAAkAJEGG3tSbZjwNTwXQgBBkBCgAdFiEErdcHlHlw
Dcrf3VM34207E/PZMnQFAmRVQHMACgkQ4207E/PZMnRgdg/+LAha8Vh1SIVpXzUH
Vdx81kPyxBSaXtOtbBw6u9EiPW+xCUiF/pyn7H1lu+hAodeNFADsXmmONKcBjURV
fwO81s60gLKYBXxpcLLQXrfNOLrYMnokr5FfuI3zZ0AoSnEoS9ufnf/7spjba8Rl
dV1q2krdw1KtbiLq3D8v4E3qRfx5SqCA+eJSavaAh3aBi6lvRlUSZmz8RWwq6gP9
Z4BiTTyFp5jQv1ZKJb5OJ+44A0pS+RvGDRq/bAAUQULLIJVOhiTM74sb/BPmeRYU
S++ee10IFW4bsrKJonCoSQTXQexOpH6AAFXeZDakJfyjTxnl3+AtA4VEp1UJIm0Y
we0h6lT0isSJPVp3RFZRPjq0g+/VniBsvYhLE/70ph9ImU4HXdNumZVqXqawmIDR
wv7NbYjpQ8QnzcP3vJ5XQ4/bNU/xWd1eM2gdpbXI9B46ER7fQcIJRNrawbEbfzuH
y5nINAzrznsg+fAC76w2Omrn547QiY2ey7jy7k79tlCXGXWAt9ikkJ95BCLsOu5O
TxPi4/UUS2en1yDbx5ej7Hh79oEZxzubW1+v5O1+tXgMOWd6ZgXwquq50vs+X4mi
7BKE2b1Mi6Zq2Y+Kw7dAEbYYzhsSA+SRPu5vrJgLTNQmGxxbrSA+lCUvQ8dPywXz
00vKiQwI9uRqtK0LX1BLuHKIhg4OgxAAnmFSZgu7wIsE2kBYwabCSIFJZzHu0lgt
RyYrY8Xh7Pg+V9slIiMGG4SIyq5eUfmU8bXjc4vQkE6KHxsbbzN6gFVLX1KDjxRK
h+/nG/RDtfw/ic7iiXZfgkEqzIVgIrtlDb/DK6ZDMeABnJcZZTJMAC4lWpJGgmnZ
xfAIGmtcUOA0CKGT43suyYET7L7HXd0TM+cJRnbEb7m8OexT9Xqqwezfqoi1MGH2
g8lRKQE4Z2eEFvCiuJnCw547wtpJWEQrGw1eqL3AS8Y051YqblbXLbgf5Oa49yo6
30ehq9OxoLd7+GdWwYBlr/0EzPUWezhdIKKvh1RO+FQGAlzYJ6Pq7BPwvu3dC3YY
dN3Ax/8dj5036Y+mHgDsnmlUk8dlziJ0O3h1fke/W81ABx4ASBktXAf1IweRbbxq
W8OgMhG6xHTeiEjjav7SmlD0XVOxjhI+qBoNPovWlChqONxablBkuh0Jd6kdNiaS
EM9cd60kK3GT/dBMyv0yVhhLci6HQZ+Mf4cbn0KtayzuQLOcdRCN3FF/JNQH3v6L
A1MdRfmJlgC4UdiepBb1uCgtVIPizRuXWDjyjzePZRN/AqaUbEoNBHhIz0nKhQGD
bst4ugIzJWIX+6UokwPC3jvJqQQttccjAy6kXBmxfxyRMB5BEeLY0+qVPyvOxpXE
GnlSHYmdIS65Ag0EZ9KQfQEQAOVIyh0sZPPFLWxoFT0WhPzHw8BhgnCBNdZAh9+S
M0Apq2VcQKSjBjKiterOTtc6EVh0K2ikbGKHQ1SvwNdsYL01cSkJSJORig/1Du1e
h+2nlo8nut7xT//V+2FQyWFCLDeQvLlAs3QHMrMYxTcwNk3qi/z1Z5Q4e6Re2aKR
U00LtSomD6CKWy9nAaqTRNzzdndJwIyCyshX4bbUzAzE7Wbgh/E0/FgBGw87LYIT
qyU6US4lvoUXB+89XxwMxO9I74L118gXEyybz+JN0/w87hXAKnaKjasSvobKE4ma
u8SXqmOO66MxiMaF4Xsmr3oIwo8q9W5d+hA+t225ipq2rZZErmPL44deMCeKmepj
LTa9CoxX2oVpDWGOYFRyJRkLDyyH4O3gCo/5qv4rOTJqPFfKPtrjWFJKGf4P4UD0
GSBX2Q+mOf2XHWsMJE4t8T7jxQCSAQUMwt6M18h1auIqcfkuNvdJhcl2GvJyCMIb
kA3AoiuKaSPgoVCmJdbc6Ao9ydmMUB5Q1rYpMNKCMsuVP9OcX8FoHEVMXOvr0f6W
fj+iHytfO2VTqrw/cqoCyuPoSrgxjs1/cRSz5g9fZ0zrOtQyNB5yJ3YPTG3va1/X
LflrjPcT4ZUkej9nkFpCNWdEZVWD/z3vXBGSV11N9Cdy60QbD4yZvDjV2GQ+dwAF
1o1BABEBAAGJBHIEGAEKACYWIQQU8maC0JFs3YHje21ht7Um2Y8DUwUCZ9KQfQIb
AgUJA8JnAAJACRBht7Um2Y8DU8F0IAQZAQoAHRYhBAm+7WPzRiot/6s7h17LZJfB
ogJWBQJn0pB9AAoJEF7LZJfBogJW9I4QAJbv4Rhb4x6Jl75x2Lfp46/e3fZVDhzU
dLjK8A/acRF7JRBuJVJRaijJ5tngdknmlmbzfqlyzsMWUciAwVJRvijNFDeicet5
zJpBRsXEUAug3iVCD1KlVvLzjCi9Eb9s6xCQjSJ8DZE020s41wdqtb1nziDASAkg
+YH2DzpTEaZVNM39uNDKbaJLYIjKA9MV1YHArqUldFsoofBe4zIZRFyvMD7Gmr7X
m0IWYLrfmnenm1JJYIkvGUeVoP8dEonAVhLVwvwwufobV0qdtMfhZsgFwf1XSHI9
MtD4yAVtBqBTkfFeRLnBjJK/ywYxGqbadt1b57I4ywTQ16oXNrlTF1Su0I8i/fo0
i/9ohNl3opN3LbaEbhT37M4xpy4MgL2Fthddc2gWvF/8TFRaXw7LaLSR7HwO+Y0C
pOtV/Ct4RzKEulY5DpV9b1JQJhpLcjMz+pBDAM3KJuiV6Bcfoz5PZowFy74UmE02
Vzk/oyuI/o4KMihy0UzWQVkOZTTu4eONktgGiZOnRFdiLKVgeLEDXTLdhbuwGS2+
wX3I7lLP9AWpK8Ahc81eUwU6MwdbfwfJ1ELtKaa/JmMjaWkr5aGrp88d8ePR9jYA
47Z2q0esB67pRJVe0McVJlu9GQGq05S7lZKs6mi9dHTzeHwua//IXHMK0s3WhMU7
vGwJ3E2+pTstf8AQALSwkezD3QchPV+5CAUYY7CmMXB6zzIU18wCS61Y8QdDvqmt
WHdMVTp4xT14fS6cvB4uFzacGQJ7CVIWeZgwEFzZiev3dKpnUOGg0WQSwmQQA0JC
g6/qS0AeUPINjhWtNcR7voCqAYeRcjo47UJclD/KKNTCn27btHRaEmpTdTtC6sxi
VElFObb3a9tHXqwLWp8gJ+NZ+6mlrvvH2hm1CAyQTDRYC7nN69QJrKHR8HA3AeR5
figQHLwvmfQlV2erZE17GT+L5t0HxX/HKZCim91PApqa+7iY0eKPAG5iacABrBi9
zzh/ex0ovvuxsBDKUFCSu7HIivnAVrdS/kbO1qJ5I3MBMp0dlQ6PS6LeZIRhxts0
aPPZedsXytoL7kFLISfJ55AuhJpskz+55uviJhp/H3zNBYtQ+dmFmp4RRk/Nvu0z
v6OGtaZy6M5X24Pbzb/OApBML84cEmb3iZie9J2ZYW68/D96sP09x6GItCJlCIdQ
ZkRcwmkQwgtq9sJDw92/vSGeYdRn+oCAxJ14eObCsVwcfJARLt45btEnx+zRCAHA
HQHpV6qTGT6nqg57XuM9iNNdyTGKRU+Iklgb9LRxVAQfbn5uXYb5j2ox5pjxtbXT
f9Lbo7RkygcWSKZPWmYgGsKS6jmXkDa/TyOlPxkbaknpPbYMBztRT4Ju0VU4
=8qIP
-----END PGP PUBLIC KEY BLOCK-----

The post Updated GPG key for signing Firefox Releases appeared first on Mozilla Security Blog.

Open Policy & AdvocacyMozilla Mornings: Unleashing PETs – Regulating Online Ads for a Privacy-First Future

Our first edition of Mozilla Mornings in 2025 will explore the state of online advertising and what needs to change to ensure a fairer, healthier, and privacy-respecting ads ecosystem where everyone stands to benefit.

The European regulatory landscape for online advertising is at a turning point. Regulators step up enforcement under the GDPR, the DMA and the DSA and industry players explore alternatives to cookies. Despite these advancements, online advertising remains an area where users do not experience strong privacy protections, and the withdrawal of the ePrivacy Regulation proposal can only exacerbate these concerns.

The industry’s reliance on invasive tracking, excessive profiling, and opaque data practices makes the current model deeply flawed. At the same time, online advertising remains central to the internet economy, supporting access to information, content creators, and journalism.

This Mozilla Mornings session will bring together policymakers, industry experts and civil society to discuss how online advertising can evolve in a way that benefits both users and businesses.

  • How can we move towards a more privacy-respecting and transparent advertising ecosystem while maintaining the economic sustainability of the open web?
  • How can regulatory reforms, combined with developments in the space of Privacy-Enhancing Technologies (PETs) and Privacy-Preserving Technologies (PPTs), provide a viable alternative to today’s surveillance-based advertising?
  • And what are the key challenges in making this shift at both the policy and technological levels?

To discuss these issues, the panel will welcome:

  • Rob van Eijk, Managing Director at Future of Privacy Forum
  • Svea Windwehr, Associate Director Public Policy at Electronic Frontier Foundation
  • Petra Wikström, Senior Director Public Policy at Schibsted
  • Martin Thomson, Distinguished Engineer at Mozilla

The discussion will also feature a fireside chat with Prof. Dr. Max von Grafenstein from Einstein Center Digital Future at the UdK Berlin.

  • Date: Wednesday 9th April 2025
  • Time: 08:45-10:15 CET
  • Venue: L42, Rue de la Loi 42, 1000 Brussels

To register, click here.

The post Mozilla Mornings: Unleashing PETs – Regulating Online Ads for a Privacy-First Future appeared first on Open Policy & Advocacy.

Firefox UXMarshmallows are for team players — A light-hearted, Severance-inspired icebreaker your team will…

Marshmallows are for team players — A light-hearted, Severance-inspired icebreaker

Let’s be real — most icebreakers are cringe with a capital C. But instead of pretending we’re above it, what if we just… leaned into the weird? That’s my plan for our upcoming workweek.
Severance just wrapped (what a finale, am I right?!), and the vibe is spot-on: relevant, bizarre in the best way, and blessedly spoiler-free. So I channeled my inner Milchick, grabbed some marshmallows, and cooked up something that might just be weird enough to stand out from the usual “ugh, another icebreaker” routine.

Here’s how to run your own “Marshmallows Are for Team Players” session:

Two people dressed in matching white winter outfits stand in a dark setting lit dramatically from below. The person on the left holds a tray of neatly arranged marshmallows, looking toward the person on the right, who stares straight ahead with a serious expression. The scene evokes a cult-like, ceremonial vibe.<figcaption>Image via Apple TV+</figcaption>

Set the Mood (2 min)

Start with a little corporate dystopia ambiance:

  1. Play the Severance theme music for 10–15 seconds.
  2. Then roll the iconic clip of Milchick saying:
Close-up of a man lit dramatically from below, wearing a white turtleneck and coat, with a serious expression. On-screen subtitle reads: “Marshmallows are for team players, Dylan.” The scene has an eerie, intense tone.<figcaption>“Marshmallows are for team players, Dylan.”</figcaption>
3. With a grin, tell your team:
“That’s right. Marshmallows are for team players.”

Explain the Rules (1 min)

We’ve got marshmallows — but they’re not free.
To earn one, you need to give a shoutout to a teammate who was a great collaborator this week.

It could be anything — big impact, quiet kindness, or someone who brought great vibes to a meeting.

Tell them:
“Try to keep it to one kudos each so we have time for everyone — but if you really need to sneak in an extra one, I won’t stop you.”

The Kudos Round (5–10 min)

Go popcorn style — whoever goes gives kudos, grabs a marshmallow, then calls on the next person.

Each person:

  1. Shares a kudos
  2. Collects a marshmallow
  3. Picks who goes next

Bonus rule:
If someone gives kudos and gets one, they can take two marshmallows. Double win.

The Marshmallow Club Photo (2 min)

Wrap it up with a team pic:

“Grab your marshmallow, hold it up like it’s your Severance badge, and let’s get a group photo. Smile like Milchick!”

Suggested file name:
team_players_in_marshmallow_mode.jpg

Slack Follow-Up

Post the photo with something like:

Behold: the Marshmallow Club
Everyone here earned their marshmallow by lifting someone else up. True team player behavior.
We’ve also unlocked a new emoji: :milchick-approves:
Use it to celebrate kudos, overachievers, or extreme corporate joy.
Praise Kier.

Try It Yourself

All it takes is a playlist, a clip, a bag of marshmallows — and a bit of satire. Give it a go at your next team meeting or offsite. Just don’t forget the group photo. Milchick is watching.

Have your own twist on this idea? Or another ridiculous icebreaker that weirdly worked? Drop it in the comments or DM me — I’m always collecting ideas.


Marshmallows are for team players — A light-hearted, Severance-inspired icebreaker your team will… was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

Open Policy & AdvocacyMozilla shares 2025 Policy Priorities and Recommendations for Creating an Internet Where Everyone Can Thrive

Mozilla envisions a future where the internet is a truly global public resource that is open, accessible, and safe for all. An internet that benefits people using online services, prioritizes the right to privacy, and enables economic dynamism. Our commitment to this vision stems from Mozilla’s foundational belief that the internet was built by people, for people and that its future should not be dictated by a few powerful organizations.

When technology is developed solely for profit, it risks causing real harm to people. True choice and control for Americans can only be achieved through a competitive ecosystem with a range of services and providers that foster innovation. However, today’s internet is far from this ideal state, and without action, is only set to become increasingly consolidated in the age of AI.

Today, Mozilla is setting out our 2025 – 2026 Policy Vision for the United States as we look to a new administration and a new congress. Our policy vision is anchored in our guiding principles for a healthy internet, and outlines policy priorities that we believe should be the ‘north star’ for U.S. policymakers and regulators. Some recommendations are long overdue, while others seek to ensure the development of a healthy and competitive internet moving forward.

Here’s how we can work together to make this happen.

Priority 1: Openness, Competition, and Accountability in AI

Promoting open source policies and approaches in AI has the potential not just to create technology that benefits individuals, but also to make AI systems safer and more transparent. Open approaches and public investment can spur increased research and development, create products that are more accessible and less vulnerable to cyberattacks, and help to catalyze investment, job creation, and a more competitive ecosystem. Mozilla’s key recommendations include:

  • Increase government use of, and support for, open-source AI. The U.S. federal government procures billions of dollars of software every year. The government should use these resources to promote and leverage open source AI when possible, to drive growth and innovation.
  • Develop and fund public AI infrastructure. Supporting initiatives like the National AI Research Resource (NAIRR) and the Department of Energy’s FASST program is crucial for developing public AI infrastructure that provides researchers and universities with access to AI tools, fosters innovation and ensures benefits for all.
  • Grow the AI talent ecosystem. It is critical that America invests in education programs to grow the domestic AI talent ecosystem. Without this talent, America will face serious difficulties competing globally.
  • Provide access to AI-related resource consumption data. At its current growth trajectory, AI could end up consuming tremendous amounts of natural resources. The government should work with the AI industry (from semiconductor developers to cloud providers to model deployers) to provide open access to resource consumption data and increase industry transparency; this can help to prevent expensive and dangerous grid failures and could lead to lower energy prices for consumers.
  • Clarify a federal position on open source AI export controls that maintains an open door for innovation. By affirming a federal position on open source AI export controls to reflect those of NTIA, and emphasizing the benefits of open models, the administration can spur further advancement in the field.

Priority 2: Protecting Online Privacy and Ensuring Accountability 

Today’s internet economy is powered by people’s information. While this data can deliver massive innovation and new services, it can also put consumers and trust at risk. Unchecked collection and opaque practices can leave people susceptible to deceptive and invasive practices, and discrimination online.  The rise of generative AI makes the issue of online privacy more urgent than ever.

Mozilla believes that privacy and innovation can coexist. With action and collaboration, policymakers can shift the internet economy toward one that prioritizes users’ rights, transparency, and trust — where privacy is not a privilege but a guarantee for all. We recommend that policymakers:

  • Pass strong comprehensive federal privacy legislation and support state efforts. Congress must enact a sufficiently strong comprehensive federal privacy law that addresses AI-specific privacy protections, upholds data minimization, ensures the security protections that encryption provides, and covers children and adults, setting a high bar for meaningful protections. This is how Congress can create an environment where people can truly benefit from the technologies they rely on without paying the premium of exploitation of their personal data. States should also move to enact strong laws to fill the gap and protect their constituents.
  • Support the adoption of privacy-enhancing technologies (PETs). This includes funding NIST and the National Science Foundation to advance fundamental and applied research, while establishing strong privacy protections that incentivize companies to prioritize PETs. The global standards development and consensus process is essential for privacy preserving technologies to develop in a sustainable manner, in particular around areas like advertising. Legislation can also incentivize companies to adopt more privacy-preserving business practices, ultimately benefiting users and supporting their right to privacy online.
  • Provide necessary resources and tools to data privacy regulators. Congress and the administration must enable and empower relevant federal regulators by providing additional resources and authorizations to facilitate privacy-related investigations and enforcement. Efforts should, in particular, target data brokers who traffic sensitive data.
  • Support critical independent research. Policymakers should ensure meaningful access to important data from major platforms for academia and civil society, enabling better research into big tech’s harms and stronger accountability. Transparency efforts like the bipartisan Platform Accountability and Transparency Act (PATA) are essential to advancing transparency while protecting public-interest research. Expanding such legislation to include AI platforms and model providers is critical to addressing privacy-related harms and ensuring accountability in the evolving digital landscape.
  • Respect browser opt-out signals. We encourage lawmakers at the state and federal level to support key privacy tools, like the Global Privacy Control (GPC) that Firefox uses. Mozilla supports bills like California’s AB 566, which would require browsers and mobile operating systems to include an opt-out setting. We encourage lawmakers at the state and federal level to advance this key privacy tool in law and meet the expectations that consumers rightly have about treatment of their personal information.

Priority 3: Increasing Choice for Consumers

Real choice and control for consumers require an open, fair, and competitive ecosystem where diverse services and providers can thrive.

Updated competition laws – and an understanding of the importance of competition at every layer of the ecosystem – are essential for the internet to be private, secure, interoperable, open, transparent, and to balance commercial profit with public benefit. Mozilla is committed to this future. To achieve this, we must advance the below.

  • Update antitrust legislation to address anti-competitive business practices, such as harmful self-preferencing, that stymie innovation and limit consumer choice. Congress must pass antitrust legislation that addresses these practices and provides the necessary resources, expertise, and authority to relevant regulatory agencies.
  • Tackle harmful design practices. Harmful deceptive design practices not only manifest at the interface level, but also deeper at the operating system level – particularly in cases of vertical integration of services and features. Deploying manipulative, coercive, and deceptive tactics such as aggressive and misleading prompts, messages, and pop-ups risk overriding user choice entirely. Policymakers must hold bad actors accountable.
  • Foster competition across the ecosystem. Independent browser and browser engine developers, like Mozilla, have a long history of innovating and offering privacy- and security-conscious users a meaningful alternative to big tech browser engines. Policymakers should recognize the importance of independent browsers and browser engines in maintaining a safe, open, and interoperable web that provides meaningful choice.

So what is the path forward?

We see our vision as a roadmap to a healthier internet. We recognize that achieving this vision means engaging with legislators, regulators, and the wider policy community. Mozilla remains committed to our mission to ensure the internet is a space for innovation, transparency, and openness for all.

Read our Vision for the United States: 2025 – 2026 for a more comprehensive look at our priorities and recommendations to protect the future of the internet. 

The post Mozilla shares 2025 Policy Priorities and Recommendations for Creating an Internet Where Everyone Can Thrive appeared first on Open Policy & Advocacy.

hacks.mozilla.orgImproving Firefox Stability in the Enterprise by Reducing DLL Injection

Beginning in version 138, Firefox will offer an alternative to DLL injection for Data Loss Prevention (DLP) deployments in enterprise environments.

DLL Injection

DLL injection into Firefox is a topic we’ve covered on the Hacks blog before. In 2023, we blogged about the Firefox capability to let users block third-party DLLs from being loaded. We explained what DLL injection is, how we deal with problematic third-party modules, our about:third-party page, and our third-party injection policy. Earlier, in 2019, we released a study of DLL injection Firefox bugs in collaboration with Polytechnique Montréal. We return to this topic now, in the context of enterprise Firefox installations.

First, a reminder of what DLL injection is and why it continues to be problematic. DLL injection is the term we use to describe third-party Windows software injecting its own DLL module code into Firefox. Third parties develop DLLs for injecting into applications to extend their functionality in some way. This is prevalent in the Windows ecosystem. When third-party code is injected, the injected code interacts with the internals of the application. While it is not unusual for software to work together, and the internet is built on software interoperating over documented standards, DLL injection differs in that the undocumented internals of an application are not intended to be a stable interface. As such, they are a poor foundation to build software products on. When the underlying application is changed, it can result in incompatibilities, leading to crashes or other unexpected behavior. In a modern web browser like Firefox, new features and fixes, big and small, are developed and released on a monthly schedule. Normal browser development can therefore cause incompatibilities with injected software, resulting in Firefox crashes, bypassing of security features, or other unpredictable buggy behavior. When these problems arise, they require emergency troubleshooting and engineering of workarounds for users until the problems are addressed by software updates. This often requires collaboration between the browser and the third-party application’s developers. The type of software injected into Firefox varies from small open source projects to widely-deployed enterprise security products. In an attempt to eliminate some of the most difficult DLL injection issues, we’ve turned our attention to Data Loss Prevention enterprise applications.

Data Loss Prevention (DLP) in the Enterprise

Data Loss Prevention (DLP) products are a type of software that is widely deployed by organizations to prevent unintended leaks of private data. Examples of private data include customer records such as names, addresses, credit card information or company secrets. Much like how anti-virus software is deployed across a corporation’s fleet of laptops, so too is DLP software. These deployments have become increasingly common, in large part due to compliance and liability concerns.

How does this relate to Firefox? DLP software typically uses DLL injection to monitor applications such as Firefox for activity that might leak private data. This only applies to specific operations that can leak sensitive information such as file uploads, pasting (as in copy-and-paste), drag-and-drop, and printing.

DLP and Firefox Today

Today, DLP software typically monitors Firefox activity via DLL injection as described above. Firefox and web browsers are not unique in this respect, but they are heavily used and under constant development, making DLL injection more dangerous. DLP software is typically deployed to a fleet of corporate computers that are managed by an IT department. This includes deployment of the software that injects into applications. DLP vendors take efforts to ensure that their products are compatible with the latest version of Firefox by testing beta versions and updating their DLLs as needed, but problems still occur regularly. A common issue is that a problem is encountered by corporate users who report the problem to their IT department. Their IT staff then work to debug the problem. They may file a bug report with Firefox or the DLP vendor. When a Firefox bug is filed, it can be a challenge for Mozilla to determine that the bug was actually caused by external software. When we learn of such problems, we alert the vendor and investigate workarounds. In the interim, users have a poor experience and may have to work around problems or even use another browser. When the browser is not functional, the problem becomes a high severity incident where support teams work as quickly as possible to help restore functionality.

Browsing Privacy

When users browse on company-owned computers, their browsing privacy is often subject to corporate-mandated software. Different regions have different laws about this and the disclosures required, but on a technical level, when the device is controlled by a corporation, that corporation has a number of avenues at its disposal for monitoring activity at whatever level is dictated by corporate policy. Firefox is built on the principle that browsing activity belongs only to the user, but as an application, it cannot reasonably override the wishes of the device administrator. Insofar as that administrator has chosen to deploy DLP software, they will expect it to work with the other software on the device. If a well-supported mechanism is not available, they will either turn to opaque and error-prone methods like DLL injection, or replace Firefox with another browser.

What’s New – Reducing DLL Injection in the Enterprise

Starting with Firefox 138, DLP software can work with Firefox without the use of DLL injection. Firefox 138 integrates the Content Analysis SDK and it can be enabled with Enterprise Policies. The SDK, developed by Google and used in Chrome Enterprise, is a lightweight protocol between the browser and a DLP agent, with the implementation being browser-specific. In other words, Firefox has its own implementation of the protocol. The integration allows Firefox to interact with DLP software while reducing the injection of third-party code. This will improve the stability for Firefox users in the enterprise and, as more DLP vendors adopt the SDK, there will be less third-party code injected into Firefox. With vendors and browsers using the same SDK, vendors can know that a single DLP agent implementation will be compatible with multiple browsers. During development of the Firefox implementation, we’ve been working with some leading DLP vendors to ensure compatibility. In addition to stability, Firefox will display an indicator when the DLP SDK is used, providing more transparency for users.

For Enterprise Use

Firefox will only enable the Content Analysis SDK in configurations where a Firefox Enterprise Policy is used. Firefox Enterprise Policies are used by organizations to configure Firefox settings across a fleet of computers. They allow administrators to configure Firefox, for example, to limit which browser extensions can be installed, set security-related browser settings, configure network proxy settings, and more. You can learn more about Firefox Enterprise Policies on our support article Enforce policies on Firefox for Enterprise.

The post Improving Firefox Stability in the Enterprise by Reducing DLL Injection appeared first on Mozilla Hacks - the Web developer blog.

Open Policy & AdvocacyMozilla Respond to the White House’s RFI on AI

The Future of AI Must Be Open, Competitive, and Accountable

The internet has always thrived on openness, access, and broad participation. But as we enter the AI era, these core principles are at risk. A handful of dominant tech companies are positioned to control major AI systems, threatening both competition and innovation. At Mozilla, we believe AI should serve the public interest—not just corporate bottom lines.

Earlier this month, we responded to the White House Office of Science and Technology Policy’s request for input on AI policy, where we offered a roadmap for a more open and trustworthy AI future (view Mozilla’s full submission here). Here’s what we think should happen.

1. AI Policy Must Prioritize Openness, Competition, and Accountability

Right now, too much AI development stays behind closed doors. Proprietary models dominate, creating a landscape where users and developers have little insight—or control—over the AI systems shaping our digital lives. If we want AI that benefits everyone, we need strong policies that promote:

  • Openness: Encouraging open-source AI development ensures transparency, security, and accessibility.
  • Competition: Preventing monopolistic control keeps AI innovation dynamic and diverse.
  • Accountability: Effective governance can mitigate AI’s risks while fostering responsible development.

By advancing these principles, we can build an AI ecosystem that empowers users rather than locking them into closed, corporate-controlled systems.

2. The Government Should Support Public AI Infrastructure

AI’s future shouldn’t be dictated solely by private companies. Public investment is key to ensuring broad access to AI tools and research. We support initiatives like the National AI Research Resource (NAIRR), which would provide universities, researchers, and small businesses with AI computing power and resources. We hope to see federal, state, and local governments increasingly adopt open source AI models in their workflows, which can help save taxpayers money, increase efficiency, and prevent vendor lock-in. Public AI infrastructure levels the playing field, allowing more voices to shape AI’s future and facilitating innovation across America, not just in a few tech hubs.

3. Open-Source AI Should Be Encouraged, Not Restricted

Discussions about restricting open-source AI through export controls often miss the point about how to ensure national leadership in AI. Open-source AI fosters innovation, improves security, and lowers costs—critical benefits for businesses, researchers, and everyday users around the world. For the United States, promoting open source AI means more global products would be built on top of American AI innovation.

A 2025 McKinsey report, “Open source in the age of AI,” created in collaboration with Mozilla, found that 60% of decision-makers reported lower implementation costs with open-source AI compared to proprietary tools. Restricting open models would stifle progress and put the U.S. at a competitive disadvantage. Instead, we urge policymakers to support the open-source AI ecosystem and resist governance approaches that restrict AI models overall rather than making more targeted and precise interventions for AI harms.

4. AI Energy Consumption Needs Transparency

AI systems consume enormous amounts of energy, and this demand is only growing. To prevent AI from straining our power grids and driving up costs, we need better transparency into AI’s resource consumption so that we can plan infrastructure development more effectively. The federal government should work with the industry to collect and share data on AI energy use. By understanding AI’s impact on infrastructure, we can promote sustainable innovation.

5. The U.S. Must Invest in AI Talent Development

AI leadership isn’t just about technology—it’s about people. To remain competitive, the U.S. needs a strong, diverse workforce of AI researchers and practitioners. That means investing in:

  • Community colleges and public universities to train the next generation of AI professionals.
  • Apprenticeship and retraining programs to help workers adapt to AI-driven industries and adopt AI in every type of business across the economy from manufacturing to retail.
  • Public-private partnerships that create novel education pathways for students, like Dakota State University’s collaboration with ArmyCyber.

By growing the AI talent ecosystem, we ensure that AI works for people—not the other way around.

The Path Forward

AI is one of the most transformative technologies of our time. But without strong policies, it risks becoming yet another tool for big tech consolidation and unchecked corporate power.

At Mozilla, we believe in an AI future that is open, competitive, and accountable. We call on policymakers to take bold steps—supporting open-source AI, investing in public infrastructure, and fostering fair competition—to ensure AI works for everyone.

The post Mozilla Respond to the White House’s RFI on AI appeared first on Open Policy & Advocacy.

The Mozilla Thunderbird BlogVIDEO: The Thunderbird Design System

In this month’s Community Office Hours, Laurel Terlesky, Design Manager, is talking about the new Thunderbird Design System. In her talk from FOSDEM, “Building a Cross-Platform, Scalable, Open-Source Design System,” Laurel describes the Thunderbird design journey. If you are interested in how the desktop and mobile apps have gotten their new look, or in the open source design process (and how to take part), this talk is for you!

Next month, we’ll be chatting with Vineet Deo, a Software Engineer on the Desktop team who will walk us through the new Account Hub on the Desktop app. If you want a sneak peak at this new streamlined experience, you can find it in the Daily channel now and the Beta channel starting March 25.

February Office Hours: The Thunderbird Design System

As Thunderbird has grown over the past few years, so has its design needs. The most recent 115 and 128 releases, Supernova and Nebula, have introduced a more modern, streamlined look to the Thunderbird desktop application. Likewise, the Thunderbird for Android app has incorporated Material 3 in its development from the K-9 Mail app. When we begin working on the iOS app, we’ll need to work with Apple’s Human Interface Guidelines. Thus, Laurel and her team have built a design system that provides consistency across our existing and future products. This system’s underlying principles also embrace user choice and privacy while emphasizing human collaboration and high design standards.

Watch, Read, and Get Involved

We’re so grateful to Laurel for joining us! We hope this video helps explain more about how we design our Thunderbird products. Want to know more about this new Thunderbird design system? Want to find out how to contribute to the design process? Watch the video and check out our resources below!

VIDEO (Also on Peertube):

Thunderbird Design Resources:

The post VIDEO: The Thunderbird Design System appeared first on The Thunderbird Blog.

Web Application SecurityEnhancing CA Practices: Key Updates in Mozilla Root Store Policy, v3.0

Mozilla remains committed to fostering a secure, agile, and transparent Web PKI ecosystem. The new Mozilla Root Store Policy (MRSP) v3.0, effective March 15, 2025, introduces critical updates to strengthen Certificate Authority (CA) practices and enhance compliance.

A major focus of MRSP v3.0 is tackling the long-standing challenge of delayed certificate revocation—an issue that has historically weakened the security and reliability of TLS certificate management. The updated policy establishes clearer revocation expectations, improved incident reporting, subscriber education by CAs, revocation planning, and automated certificate issuance to ensure that certificate replacement and revocation can be handled promptly and at scale.

Beyond improving revocation, MRSP v3.0 also introduces policies to move CA operators toward dedicated hierarchies for TLS and S/MIME certificates and to enhance CA private key security with improved lifecycle tracking. All of these updates raise the bar for CA operations, reinforcing security and trust across the broader internet ecosystem.

Addressing Delayed Certificate Revocation

One of the most persistent challenges in certificate management has been ensuring that TLS server certificates are revoked quickly when necessary. Many website operators struggle to replace certificates efficiently, while security advocates emphasize the need for rapid revocation and automated certificate lifecycle management to reduce risks.

To strike the right balance between security, stability, and operational feasibility, MRSP v3.0 introduces several key changes towards clearer and more comprehensive revocation expectations.

No Exceptions to Revocation Requirements

Previously, some CA operators expressed uncertainty about whether Mozilla could grant exceptions to revocation timelines in certain situations. MRSP v3.0 explicitly reiterates that Mozilla does not grant exceptions to the TLS Baseline Requirements for revocation. This will promote more consistent enforcement of revocation policy.

Stronger Subscriber Communication and Contractual Clarity

CA operators must proactively warn subscribers about the risks of relying on publicly trusted certificates in environments that cannot tolerate timely revocation. Additionally, Subscriber Agreements must explicitly require cooperation with revocation timelines, ensuring CA operators can act without unnecessary delays.

Mass Revocation Preparedness

Historically, large-scale certificate revocations have been challenging, leading to operational slowdowns, and ecosystem-wide risks when urgent action is required. To prevent revocation delays, MRSP v3.0 mandates mass revocation readiness to help ensure that CA operators proactively plan for such scenarios. CA operators will be required to develop, maintain, and test comprehensive plans to revoke large numbers of certificates quickly when necessary. And, to further strengthen mass revocation preparedness, MRSP v3.0 introduces a third-party assessment requirement. Assessors will verify that CA operators:

  • Maintain well-documented, actionable plans for large-scale revocation,
  • Demonstrate feasibility through regular testing, and
  • Continuously improve their approach based on lessons learned.

These measures ensure CA operators are fully prepared for high-impact security events.

By strengthening mass revocation preparedness–and investing in CRLite–Mozilla is working to make certificate revocation a reliable security control.

Enhancing Automation in Certificate Issuance and Renewal

Automation plays a critical role in ensuring certificates can be replaced in a timely manner. To further encourage adoption of automation, MRSP v3.0 introduces new requirements for CA operators seeking root inclusion with the “websites” trust bit enabled, including: offering automation options for Domain Control Validation (DCV), certificate issuance, and renewal (demonstrated by a publicly accessible test website demonstrating automated certificate replacement at least every 30 days). Test website details must be disclosed in the Common CA Database (CCADB), adding transparency to this requirement. This push for more automation aligns with industry best practices, reducing reliance on manual processes, improving security, and minimizing mismanagement risks.

Phasing Out Dual-Purpose (TLS and S/MIME) Root CAs 

A significant change introduced in MRSP v3.0 is the phase-out of dual-purpose root CAs—those with both the “websites” trust bit and the “email” trust bit enabled. The industry is already moving toward separating TLS and S/MIME hierarchies due to their distinct security needs. Keeping these uses separate at the root certificate level ensures more focused compliance, increases CA agility, reduces complexity, and enhances security.  Going forward, Mozilla’s Root Store will require that new root CA certificates are dedicated to either TLS or S/MIME, and CA operators with existing dual-purpose roots will need to submit a transition plan to Mozilla by April 15, 2026, and complete a full migration to separate roots by December 31, 2028. This move enhances clarity and security by ensuring TLS and S/MIME compliance requirements remain distinct and enforceable.

Strengthening CA Key Security with “Cradle-to-Grave” Monitoring

Another major enhancement in MRSP v3.0 is the introduction of stricter key lifecycle monitoring to protect “parked” CA private keys. A “parked” key is a private key that the CA operator has generated for future use, but not yet used in a CA certificate. MRSP v3.0 adds mandatory reporting of parked key public hashes (corresponding to the parked CA private key) in annual audits. By enforcing transparency and accountability, Mozilla strengthens protections against undetected key compromise or misuse.

Conclusion

MRSP v3.0 represents a major step forward in ensuring stronger CA accountability with more reliable certificate revocation processes, better automation and operational resilience, and enhanced security for CA private keys. In all, these changes help modernize the Web PKI and ensure that CA operations will remain transparent, accountable, and secure.  We encourage you to engage with the Mozilla community and to contribute to these efforts and our shared mission of ensuring a secure and trustworthy online experience for all users.

The post Enhancing CA Practices: Key Updates in Mozilla Root Store Policy, v3.0 appeared first on Mozilla Security Blog.

The Mozilla Thunderbird BlogThunderbird Monthly Development Digest – February 2025

Hello again Thunderbird Community! Despite the winter seeming to last forever and the world being in a state of flux, the Thunderbird team has been hard at work both in development and planning strategic projects. Here’s the latest from the team dedicated to making Thunderbird better each day:

Monthly Releases are here!

The concept of a stable monthly release channel has been in discussion for many years and I’m happy to share that we recently changed the default download on Thunderbird.net to point at our most feature-rich and up-to-date stable version. A lot of work went into this release channel, but for good reason – it brings the very latest in performance and UX improvements to users with a frequent cadence of updates. Meaning that you don’t have to wait a year to benefit from features that have been tested and already spent time on our more experimental Daily and Beta release channels. Some examples of features that you’ll find on the monthly release channel (but not on ESR) are:

  • Linux System Tray
  • Dark reader Support
  • Folder compaction improvements
  • Hundreds of UI enhancements
  • ICS Import
  • Calendar printing improvements
  • Appearance settings UI
  • Many, many more

Download it over the top of your ESR installation and get the benefits today!

Developing Standards

As privacy and security legislation evolves, the Thunderbird team often finds itself in the heart of discussions that have the potential to define industry solutions to emerging problems. In addition to the previously-mentioned research underway to develop post-quantum encryption support, we’re also currently considering solutions to EU laws (EU NIS2) that require multi-factor authentication be in place for critical digital infrastructure and services. We’re committed to solving these issues in a way that gives users and system administrators other options besides Google & Microsoft, and we’ll be sharing our thoughts on the matter soon, with the resulting decisions documented in our new ADR process.

For now, you can follow a healthy and colourful discussion on the topic of OAuth2 Dynamic Client Registration here.

Calendar UI Rebuild is underway

The long awaited UI/UX rebuild of the calendar has begun, with our first step being a new event dialog that we’re hoping to get into the hands of users on Daily via a preference switch. Turning the pref on will allow the existing calendar interface to launch the new dialog once complete. The following pieces of work have already landed:

  • Dialog container
  • Generic row container
  • Calendar row
  • Close button
  • Generic subview
  • Title

Keep track of feature delivery via the [meta] bug 

Exchange Web Services support in Rust

A big focus for February has been to grow our team so we’ve been busy interviewing and evaluating the tremendously talented individuals who have stepped forward to show interest in joining the team. In the remaining time, the team has managed to deliver another set of features and is heading toward a release on Daily that will result in most email features being made available for testing. Here’s what landed and started in February:

  • Display refactor
  • Basic testing framework
  • Sync folder – delete
  • Sync folder read/unread
  • Integration testing
  • Complete composition support (reply/forward)

Keep track of feature delivery here.

Account Hub

Since my last update, tasks related to density and font awareness, the exchange add-on and keyboard navigation were completed, with the details of each step available to view in our Meta bug & progress tracking. Watch out for this feature being rolled out as the default experience for the Daily build this week and on beta after the next merge on March 25th!

Global Message Database

The New Zealand team are in the middle of a work week to shout at the code together, have a laugh and console each other plan out work for the next several weeks. Their focus has been a sprint to prototype the integration of the new database with existing interfaces with a positive outcome meaning we’re a little closer to producing a work breakdown that paints a more accurate picture of what lies ahead. Onward!

In-App Notifications

Phase 3 of the project is underway to finalize our uplift stack and add in last-minute features! It is expected that our ESR version will have this new feature enabled for a small percentage of users at some point in April. If you use the ESR release, watch out for an introductory notification!

 Meta Bug & progress tracking.

New Features Landing Soon

Several requested features and fixes have reached our Daily users and include…

As usual, if you want to see things as they land, and help us squash some early bugs, you can always check the pushlog and try running daily, which would be immensely helpful for catching things early.

If you’re interested in joining the technical discussion around Thunderbird development, consider joining one or several of our mailing list groups here.

Toby Pilling
Senior Manager, Desktop Engineering

The post Thunderbird Monthly Development Digest – February 2025 appeared first on The Thunderbird Blog.

The Mozilla Thunderbird BlogThunderbird for Android January/February 2025 Progress Report

Hello, everyone, and welcome to the first Android Progress Report of 2025. We’re ready to hit the ground running improving Thunderbird for Android experience for all of our users. Our January/February update involves a look at improvements to the account drawer and folders on our roadmap, an update on Google and K-9 Mail, and explores our first step towards Thunderbird on iOS.

Account Drawer Improvements

As we noted in our last post on the blog, improving the account drawer experience is one of our top priorities for development in 2025. We heard your feedback and want to make sure we provide an account drawer that lets you navigate between accounts easily and efficiently. Let’s briefly go into the most common feedback:

  • The accounts on the same domains or with similar names are difficult to distinguish from the two letters provided.
  • It isn’t clear how the account name influences the initials.
  • The icons seemed to be jumping around, especially obvious with 3–5 accounts.
  • There is a lot of spacing in the new drawer.
  • Users would like more customization options, such as an account picture or icon.
  • Some users would like to see a broader view that shows the whole account name.
  • With just one account, the accounts sidebar isn’t very useful.

Our design folks are working on some mockups on where the journey is taking us. We’re going to share them on the beta topicbox where you can provide more targeted feedback, but for a sneak peek here is a medium-fidelity mockup of what the new drawer and settings could look like:

On the technical side, we’ve integrated an image loader for the upcoming pictures. We now need to gradually adapt the mockups. We will begin with the settings screen changes and then adapt the drawer itself to follow.

Notifications and Error States

Some of you had the feeling your email was not arriving quick enough. While email delivery is reliable, there are a few settings in Thunderbird for Android and K-9 mail that aren’t obvious leading to confusion. When permissions are not granted, functionality is simply turned off instead of telling the user they actually need to grant the alarms permission for us to do a regular sync. Or maybe the sync interval is simply set to the default of 1 hour.

We’re still in the process of mapping out the best experience here, but will have more updates soon. See the notifications support article in case you are experiencing issues. A few things we’re aiming for this year:

  • Show an indicator in foreground service notification when push isn’t working for all configured folders
  • Show more detailed information when foreground service notification is tapped
  • Move most error messages from the system notifications to an area in-app to clearly identify when there is an error
  • Make authentication errors, certificate errors, and persistent connectivity issues use the new in-app mechanism
  • Make the folder synchronization settings more clear (ever wondered why there is “sync” and “push” and if you should have both enabled or not?)
  • Prompt for permissions when they are needed, such as aforementioned alarms permission
  • Indicate to the user if permissions are missing for their folder settings.
  • Better debug tool in case of notification issues.

Road(map) to the Highway

Our roadmap is currently under review from the Thunderbird council. Once we have their final approval, we’ll update the roadmap documentation. While we’re waiting, we would like to share some of the items we’ve proposed:

  • Listening to community feedback on Mozilla Connect and implementing HTML signatures and quick filter actions, similar to the Thunderbird Desktop
  • Backend refactoring work on the messages database to improve synchronization
  • Improving the message display so that you’ll see fewer prompts to download additional messages
  • Adding Android 15 compatibility, which is mainly Edge to Edge support
  • Improving the QR code import defaults (relates to notification settings as well)
  • Making better product decisions by (re-)introducing a limited amount of opt-in telemetry.

Does that sound exciting to you? Would you like to be a part of this but don’t feel you have the time? Are you good at writing Android apps in Kotlin and have an interest in muti-platform work? Well, do I have a treat for you! We’re hiring an Android Senior Software Engineer to work on Thunderbird for Android!

K-9 Mail Blocked from Gmail

We briefly touched on this in the last update as well: some of our users on K-9 Mail have noticed issues with an “App Blocked” error when trying to log into certain Gmail accounts. Google is asking K-9 Mail to go through a new verification process and has introduced some additional requirements that were not needed before. Users that are already logged in or have logged in recently should not be affected currently.

Meeting these requirements depended on several factors beyond our control, so we weren’t able to resolve this immediately.

If you are experiencing this issue on K-9 Mail, the quickest workaround is to migrate to Thunderbird for Android, or check out one of the other options on the support page. For those interested, more technical details can be found in issue 8598. We’re using keys on this application that have so far not been blocked. Our account import feature will make this transition pretty seamless. 

We’ve been able to make some major progress on this, we have a vendor for the required CASA review and expect the letter of validation to be shared soon. We’re still hitting a wall with Google, as they are giving us inconsistent information on the state of the review, and making some requirements on the privacy policy that sound more like they are intended for web apps. We’ve made an effort to clarify this further and hope that Google will accept our revised policy.

If all goes well we’ll get approval by the end of the month, and then need to make some changes to the key distribution so that Thunderbird and K-9 use the intended keys. 

Our Plans for Thunderbird on iOS

If you watched the Thunderbird Community Office Hours for January, you might have noticed us talking about iOS. You heard right – our plans for the Thunderbird iOS app are getting underway! We’ve been working on some basic architectural decisions and plan to publish a barebones repository on GitHub soon. You can expect a readme and some basic tools, but the real work will begin when we’ve hired a Senior Software Engineer who will lead development of a Thunderbird app for the iPhone and iPad. Interviews for some candidates have started and we wish them all the best!

With this upcoming hire, we plan to have alpha code available on Test Flight by the end of the year. To set expectations up front, functionality will be quite basic. A lof of work goes into writing an email application from scratch. We’re going to be focusing on a basic display of email messages, and then expanding to triage actions. Sending basic emails is also on our list.

FOSDEM

Our team recently attended FOSDEM in Brussels, Belgium. For those unfamiliar with FOSDEM, it’s the Free and Open Source Software Developers’ European Meeting—an event where many open-source enthusiasts come together to connect, share knowledge and ideas, and showcase the projects they’re passionate about.

We received a lot of valuable feedback from the community on Thunderbird for Android. Some key areas of feedback included the need for Exchange support, improvements to the folder drawer, performance enhancements, push notifications (and some confusion around their functionality), and much more.

Our team was highly engaged in listening to this feedback, and we will take all of it into account as we plan our future roadmap. Thunderbird has always been a project developed in tandem with our community and it was exciting for us to be at FOSDEM to connect with our users, contributors and friends.

In other news…

As always, you can join our Android-related mailing lists on TopicBox. And if you want to help us test new features, you can become a beta tester.

This blog post talks a lot about the exciting things we have planned for 2025. We’re also hiring for two positions, and may have a third one later in the year. While our software is free and open source, creating a world class email application isn’t without a cost. If you haven’t already made a contribution in January,  please consider supporting our work with a financial contribution. Thunderbird for Android relies entirely on user funding, so without your support we could likely only get to a fraction of what you see here. Making a contribution is really easy if you have Thunderbird for Android or K-9 Mail installed, just head over to the settings and sign up directly from your device. 

See you next month,

The post Thunderbird for Android January/February 2025 Progress Report appeared first on The Thunderbird Blog.