https://groups.google.com/a/mozilla.org/g/firefox-dev/c/bofYvrfH9vY/m/GrKuzixzAAAJ
https://blog.thunderbird.net/2024/08/plan-less-do-more-introducing-appointment-by-thunderbird/
Thunderbird has a new project under its wing: Appointment. Learn all about our approach to appointment scheduling, and try it yourself.
https://blog.thunderbird.net/2024/08/video-how-to-answer-thunderbird-questions-on-mozilla-support/
In this first of a two-part series, the Thunderbird Team discusses how to get involved with providing Thunderbird support.
https://blog.mozilla.org/netpolicy/2024/08/22/ppa-update/
An update on Mozilla's PPA experiment and how it protects user privacy while testing cutting edge technologies to improve the open web.
https://endler.dev/2024/the-dying-web/
I look left and right, and I'm the only one who…
https://yoric.github.io/post/why-did-mozilla-remove-xul-addons/
TL;DR: Firefox used to have a great extension mechanism based on the XUL and XPCOM. This mechanism served us well for a long time. However, it came at an ever-growing cost in terms of maintenance for both Firefox developers and add-on developers. On one side, this growing cost progressively killed any effort to make Firefox secure, fast or to try new things. On the other side, this growing cost progressively killed the community of add-on developers. Eventually, after spending years trying to protect this old add-on mechanism, Mozilla made the hard choice of removing this extension mechanism and replacing this with the less powerful but much more maintainable WebExtensions API. Thanks to this choice, Firefox developers can once again make the necessary changes to improve security, stability or speed. During the past few days, I’ve been chatting with Firefox users, trying to separate fact from rumor regarding the consequences of the August 2020 Mozilla layoffs. One of the topics that came back a few times was the removal of XUL-based add-ons during the move to Firefox Quantum. I was very surprised to see that, years after it happened, some community members still felt hurt by this choice. And then, as someone pointed out on reddit, I realized that we still haven’t taken the time to explain in-depth why we had no choice but to remove XUL-based add-ons. So, if you’re ready for a dive into some of the internals of add-ons and Gecko, I’d like to take this opportunity to try and give you a bit more detail.
https://www.quippd.com/writing/2024/06/24/mozilla-reddit-ama-2024-firefox-priorities-what-you-missed.html
Mozilla did their biggest Reddit AMA yet on Thursday, June 13, with eight members of the Firefox leadership team. With 400 total comments on the post, they c...
https://www.quippd.com/writing/2024/06/24/mozilla-reddit-ama-2024-firefox-priorities-what-you-missed.html
Mozilla did their biggest Reddit AMA yet on Thursday, June 13, with eight members of the Firefox leadership team. With 400 total comments on the post, they c...
https://www.reddit.com/r/firefox/comments/1de7bu1/were_the_firefox_leadership_team_at_mozilla_ama/
https://hacks.mozilla.org/2024/05/experimenting-with-local-alt-text-generation-in-firefox-nightly/
Firefox 130 will feature an on-device AI model that automatically generates alt-text for images, integrated into its built-in PDF editor.
@yoasif
@fedia.io