<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:planet="http://planet.intertwingly.net/" xmlns:indexing="urn:atom-extension:indexing" indexing:index="no"><access:restriction xmlns:access="http://www.bloglines.com/about/specs/fac-1.0" relationship="deny"/>
  <title>Planet Mozilla</title>
  <updated>2026-11-13T11:58:14Z</updated>
  <generator uri="http://intertwingly.net/code/venus/">Venus</generator>
  <author>
    <name>Planet Mozilla Module Team</name>
    <email>planet@mozilla.org</email>
  </author>
  <id>https://planet.mozilla.org/atom.xml</id>
  <link href="https://planet.mozilla.org/atom.xml" rel="self" type="application/atom+xml"/>
  <link href="https://planet.mozilla.org/" rel="alternate"/>

  <entry>
    <id>discourse.mozilla.org-topic-150216</id>
    <link href="https://discourse.mozilla.org/t/mozphab-2-25-0-released/150216" rel="alternate" type="text/html"/>
    <title>MozPhab 2.25.0 Released</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Bugs resolved in Moz-Phab 2.25.0:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/2086084">bug 2086084</a> Submitting part of a stack with git adds double blank lines after the commit subject of the remaining commits</li>
<li><a href="https://bugzilla.mozilla.org/2088204">bug 2088204</a> Uncommitted changes detected on clean checkout</li>
<li><a href="https://bugzilla.mozilla.org/2088229">bug 2088229</a> Parse Conduit search results into frozen data models</li>
<li><a href="https://bugzilla.mozilla.org/2088739">bug 2088739</a> Use enums and a frozen <code>Transaction</code> for the fixed values moz-phab compares and sends</li>
<li><a href="https://bugzilla.mozilla.org/2089259">bug 2089259</a> Split patch into resolving, planning and applying steps</li>
<li><a href="https://bugzilla.mozilla.org/2090820">bug 2090820</a> <code>moz-phab uplift</code> should be able to post a merge conflict as the first diff of the revision it resolves</li>
</ul>
<p>Discuss these changes in <span class="hashtag-raw">#engineering-workflow</span> on Slack or <span class="hashtag-raw">#Conduit</span> Matrix.</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/mozphab-2-25-0-released/150216">Read full topic</a></p></div>
    </summary>
    <updated>2026-11-12T23:49:30Z</updated>
    <published>2026-11-12T23:49:30Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>sheehan</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/mozphab-2-25-0-released/150216.rss" title="MozPhab 2.25.0 Released"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-150215</id>
    <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261112-1/150215" rel="alternate" type="text/html"/>
    <title>Happy BMO Push Day! (20261112.1)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://github.com/mozilla-bteam/bmo/tree/release-20261112.1" rel="noopener nofollow ugc">Github Link</a></p>
<p>The following changes have been pushed to <a href="https://bugzilla.mozilla.org">bugzilla.mozilla.org</a>:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2088705">Bug 2088705</a> - Record the acting user in flag_activity.who, as a nullable column (first step of bug 2085398)</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2090094">Bug 2090094</a> - Release Management setting a Phab uplift to “abandoned” does not set the corresponding tracking flag to <code>-</code></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2090252">Bug 2090252</a> - 2_test_login_totp.t reads the page before the TOTP enrollment and verification API calls return</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2087012">Bug 2087012</a> - [mentions] <span class="mention">@username</span> mentioniing during when bug is created does not needinfo the person but it should</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2085072">Bug 2085072</a> - Set a cookie when hiding or showing external attachments and use the cookie for all future bug pages save preference</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2088987">Bug 2088987</a> - Bug shouldn’t be closed when github commit and backout arrive on the same message</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2089049">Bug 2089049</a> - REST /bug/2048343/history fails with internal error: Can’t call method “iso8601” on an undefined value at Bugzilla/API/V1/Util.pm line 362</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2089200">Bug 2089200</a> - Enforce unique nicknames with a UNIQUE index on profiles.nickname</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2085141">Bug 2085141</a> - [mentions] Make it more obvious when <span class="mention">@mention</span> is going to needinfo someone</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2085052">Bug 2085052</a> - [mentions] For <span class="mention">@mentions</span> in comments, allow the autocompletion when typing @ like github does</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2091217">Bug 2091217</a> - Avoid stale-element failure in bug-edit Selenium test</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2091218">Bug 2091218</a> - Wait for product details in the Selenium test</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2091196">Bug 2091196</a> - fetch_product_versions is not cached for the request: buglist.cgi makes 42 memcached lookups, and a new HTTP request on every call when the product-details endpoint fails</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2091444">Bug 2091444</a> - TrackingFlags bug_check_can_change_field runs a database query for every custom field on show_bug.cgi, including fields that aren’t tracking flags</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2091129">Bug 2091129</a> - Bugzilla::DB pings MySQL before every query (about 200 pings per show_bug.cgi request)</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2091167">Bug 2091167</a> - SizeLimit plugin parses all of /proc/self/smaps in pure Perl after every request (~3 ms per request)</li>
</ul>
<p>Discuss these changes in the <a href="https://matrix.to/#/#bmo:mozilla.org" rel="noopener nofollow ugc">BMO Matrix Room</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261112-1/150215">Read full topic</a></p></div>
    </summary>
    <updated>2026-11-12T23:25:52Z</updated>
    <published>2026-11-12T23:25:52Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>dkl1</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261112-1/150215.rss" title="Happy BMO Push Day! (20261112.1)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-150212</id>
    <link href="https://discourse.mozilla.org/t/nov-12th-deploy/150212" rel="alternate" type="text/html"/>
    <title>Nov 12th Deploy</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The latest version of<a href="https://perf.compare" rel="noopener nofollow ugc"> PerfCompare</a> is now live!</p>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297876-new-view-alert-1" name="p-297876-new-view-alert-1"/><img alt=":police_car_light:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/police_car_light.png?v=16" title=":police_car_light:" width="20"/> <strong>New view alert!</strong> <img alt=":police_car_light:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/police_car_light.png?v=16" title=":police_car_light:" width="20"/></h3>
<p><strong>The cross-platform view in PerfCompare!</strong></p>
<p><strong>How it started:</strong> Matthew Gaudet sought to answer one question that keeps coming up for engineers looking at a performance change: “Do these improvements or regressions agree across platforms?” Until now, answering that meant opening each platform’s results one at a time and comparing them by hand. He saw that gap and filed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2069050">Bug 2069050</a> asking for an official cross platform view in PerfCompare.</p>
<p><strong>What we have now and how it works:</strong> The new cross-platform subtests view is live now! It shows each subtest as a row and each platform as a column. An Agreement column sums up the result at a glance, like “3/3 improved”, “2/3 regressed” or “Mixed”. Regressions are sorted to the top by default, and you can sort and filter by agreement. You can also click any cell to go to that platform’s detailed results. You get there from the new “Compare across platforms” link in a test’s header, which appears whenever two or more platforms have subtest data.</p>
<p>Please feel free to leave feedback or file bugs through the links below.</p>
<p/><div class="lightbox-wrapper"><a class="lightbox" href="https://us1.discourse-cdn.com/flex001/uploads/mozilla/original/3X/c/2/c2368fe280b5f5055d78b576123a7be1e2b846bc.png" rel="noopener nofollow ugc" title="Screenshot 2026-11-12 at 11.23.26"><img alt="Screenshot 2026-11-12 at 11.23.26" height="216" src="https://us1.discourse-cdn.com/flex001/uploads/mozilla/optimized/3X/c/2/c2368fe280b5f5055d78b576123a7be1e2b846bc_2_690x216.png" width="690"/></a></div><p/>
<p/><div class="lightbox-wrapper"><a class="lightbox" href="https://us1.discourse-cdn.com/flex001/uploads/mozilla/original/3X/e/d/ed1a262622f07590cd4992bd9f31406b8a75f2b3.png" rel="noopener nofollow ugc" title="Screenshot 2026-11-12 at 11.22.45"><img alt="Screenshot 2026-11-12 at 11.22.45" height="393" src="https://us1.discourse-cdn.com/flex001/uploads/mozilla/optimized/3X/e/d/ed1a262622f07590cd4992bd9f31406b8a75f2b3_2_690x393.png" width="690"/></a></div><p/>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297876-check-out-the-change-log-below-to-see-the-updates-2" name="p-297876-check-out-the-change-log-below-to-see-the-updates-2"/>Check out the change-log below to see the updates:</h3>
<p><strong>Highlights:</strong></p>
<p>[kala-moz]:</p>
<ul>
<li>
<p><strong><a href="https://github.com/mozilla/perfcompare/commit/0d97d36e0a50249f5236420235ffef6e87b5ac8b" rel="noopener nofollow ugc">Bug 2069050 - Add a cross-platform subtests view (</a><a href="https://github.com/mozilla/perfcompare/pull/1135" rel="noopener nofollow ugc">#1135</a><a href="https://github.com/mozilla/perfcompare/commit/0d97d36e0a50249f5236420235ffef6e87b5ac8b" rel="noopener nofollow ugc">)</a></strong></p>
</li>
<li>
<h5><a class="anchor" href="https://discourse.mozilla.org#p-297876-bug-2068298-simple-view-match-the-advanced-options-selections-for-both-results-and-subtests-pagehttpsgithubcommozillaperfcomparecommitfbea4d37283986e00ef518c9e728d3f34c178b77-3" name="p-297876-bug-2068298-simple-view-match-the-advanced-options-selections-for-both-results-and-subtests-pagehttpsgithubcommozillaperfcomparecommitfbea4d37283986e00ef518c9e728d3f34c178b77-3"/><strong><a href="https://github.com/mozilla/perfcompare/commit/fbea4d37283986e00ef518c9e728d3f34c178b77" rel="noopener nofollow ugc">Bug 2068298 Simple View: match the advanced options selections for both results and subtests page</a></strong></h5>
</li>
<li>
<p><strong><a href="https://github.com/mozilla/perfcompare/commit/4b4ffbadfe5058c6fcdc13cd38affd5f9260e4ce" rel="noopener nofollow ugc">Bug 2067300 Simple view: Persist advanced options in cookies (with URL taking precedence)</a></strong></p>
</li>
<li>
<h5><a class="anchor" href="https://discourse.mozilla.org#p-297876-bug-2075051-magnitude-filter-medium-option-matches-no-rows-rows-show-moderate-insteadhttpsgithubcommozillaperfcomparecommit17a6618aa6466015f60df3a5963d654fb5309d93-4" name="p-297876-bug-2075051-magnitude-filter-medium-option-matches-no-rows-rows-show-moderate-insteadhttpsgithubcommozillaperfcomparecommit17a6618aa6466015f60df3a5963d654fb5309d93-4"/><strong><a href="https://github.com/mozilla/perfcompare/commit/17a6618aa6466015f60df3a5963d654fb5309d93" rel="noopener nofollow ugc">Bug 2075051 Magnitude filter “Medium” option matches no rows; rows show “Moderate” instead</a></strong></h5>
</li>
<li>
<h5><a class="anchor" href="https://discourse.mozilla.org#p-297876-add-a-fake-treeherder-backend-for-fakedatahttpsgithubcommozillaperfcomparecommit4be335072af7cad408b72311f61a335d620263f7-5" name="p-297876-add-a-fake-treeherder-backend-for-fakedatahttpsgithubcommozillaperfcomparecommit4be335072af7cad408b72311f61a335d620263f7-5"/><strong><a href="https://github.com/mozilla/perfcompare/commit/4be335072af7cad408b72311f61a335d620263f7" rel="noopener nofollow ugc">Add a fake Treeherder backend for ?fakedata</a></strong></h5>
</li>
</ul>
<p>[moijes]:  <strong><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2003889">Bug-2003889</a><a href="https://github.com/mozilla/perfcompare/commit/58ee0f1ff29c93e858c2484d6edf51e423bd12a2" rel="noopener nofollow ugc">: Show Lando try-push status instead of a blank-revision error</a></strong></p>
<p><strong>Other changes:</strong></p>
<p>[kala-moz]:</p>
<ul>
<li>
<h5><a class="anchor" href="https://discourse.mozilla.org#p-297876-bug-2069050-prepare-code-for-cross-platform-subtests-view-httpsgithubcommozillaperfcomparecommit2f4283238516289ea1caf03b1a04a9c0b05798c61134httpsgithubcommozillaperfcomparepull1134httpsgithubcommozillaperfcomparecommit2f4283238516289ea1caf03b1a04a9c0b05798c6-6" name="p-297876-bug-2069050-prepare-code-for-cross-platform-subtests-view-httpsgithubcommozillaperfcomparecommit2f4283238516289ea1caf03b1a04a9c0b05798c61134httpsgithubcommozillaperfcomparepull1134httpsgithubcommozillaperfcomparecommit2f4283238516289ea1caf03b1a04a9c0b05798c6-6"/><strong><a href="https://github.com/mozilla/perfcompare/commit/2f4283238516289ea1caf03b1a04a9c0b05798c6" rel="noopener nofollow ugc">Bug 2069050 - prepare code for cross-platform subtests view (</a><a href="https://github.com/mozilla/perfcompare/pull/1134" rel="noopener nofollow ugc">#1134</a><a href="https://github.com/mozilla/perfcompare/commit/2f4283238516289ea1caf03b1a04a9c0b05798c6" rel="noopener nofollow ugc">)</a></strong></h5>
</li>
<li>
<h5><a class="anchor" href="https://discourse.mozilla.org#p-297876-bug-2082629-remove-unused-and-phantom-fields-from-mann-whitney-u-types-httpsgithubcommozillaperfcomparecommitf410d4268c26b9ca93cb1d6eaaa04e69aafc76f91130httpsgithubcommozillaperfcomparepull1130httpsgithubcommozillaperfcomparecommitf410d4268c26b9ca93cb1d6eaaa04e69aafc76f9-7" name="p-297876-bug-2082629-remove-unused-and-phantom-fields-from-mann-whitney-u-types-httpsgithubcommozillaperfcomparecommitf410d4268c26b9ca93cb1d6eaaa04e69aafc76f91130httpsgithubcommozillaperfcomparepull1130httpsgithubcommozillaperfcomparecommitf410d4268c26b9ca93cb1d6eaaa04e69aafc76f9-7"/><strong><a href="https://github.com/mozilla/perfcompare/commit/f410d4268c26b9ca93cb1d6eaaa04e69aafc76f9" rel="noopener nofollow ugc">Bug 2082629 Remove unused and phantom fields from Mann-Whitney U types (</a><a href="https://github.com/mozilla/perfcompare/pull/1130" rel="noopener nofollow ugc">#1130</a><a href="https://github.com/mozilla/perfcompare/commit/f410d4268c26b9ca93cb1d6eaaa04e69aafc76f9" rel="noopener nofollow ugc">)</a></strong></h5>
</li>
</ul>
<p>Thank you for the contributions!</p>
<p>Bugs or feature requests can be<a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&amp;component=PerfCompare&amp;status_whiteboard=%5Bpcf%5D"> filed on Bugzilla</a>. The team can also be found on<a href="https://matrix.to/#/#perfcompare:mozilla.org" rel="noopener nofollow ugc"> the #perfcompare channel on </a>Matrix. Come and chat!</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/nov-12th-deploy/150212">Read full topic</a></p></div>
    </summary>
    <updated>2026-11-12T19:28:13Z</updated>
    <published>2026-11-12T19:28:13Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>csevere</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/nov-12th-deploy/150212.rss" title="Nov 12th Deploy"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88975</id>
    <link href="https://blog.mozilla.org/en/firefox/set-firefox-default-mobile-browser/" rel="alternate" type="text/html"/>
    <title>An open letter to every family’s designated IT support</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Almost every family has one. They’re the only ones who know which remote turns on the TV and which controls the volume and channels. They know what an HDMI cable actually does and where to plug it in. They’ve even fixed multiple phone issues within seconds through a little-known, well-kept secret procedure (turning it off […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/set-firefox-default-mobile-browser/">An open letter to every family’s designated IT support</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Almost every family has one. They’re the only ones who know which remote turns on the TV and which controls the volume and channels. They know what an HDMI cable actually does and where to plug it in. They’ve even fixed multiple phone issues within seconds through a little-known, well-kept secret procedure (turning it off and back on).</p>



<p>Perhaps they are a parent, tech-savvy sibling, cool aunt or uncle, or close family friend. Whatever the relation, the role stays the same. They are the unpaid, on-call tech specialist for every relative’s forgotten password, printer jam, and device settings update.</p>



<p>If this sounds like you, we would first like to thank you for doing a job you never signed up for. Second, we would like to share a simple way you can help your family and friends protect their privacy and security without adding more to your plate. </p>



<h3><strong>A small settings change that makes a big differenc</strong>e</h3>



<p>With Android and iPhone’s latest releases, and Black Friday deals rapidly approaching, many people are upgrading their current phone to a newer model. As the family’s go-to tech helper, you’ll likely be setting up a few new devices in the near future. You already know the routine: connect to Wi-Fi, choose a language, and transfer data from the old phone to the new one. But beyond the steps you are prompted to take when setting up a new phone lies a quiet decision many people never think twice about: their default browser.</p>



<p>While people in some regions, like Europe and Japan, get to choose their default browser when setting up a new phone, <a href="https://blog.mozilla.org/netpolicy/2026/05/11/six-million-selections-later-how-the-dma-is-giving-people-browser-choice/">this is not the case everywhere</a>. Most phones ship with a browser preinstalled and set as the default, ready to start collecting data and monetizing off user activity the minute it’s opened. Unless deliberately changed, that’s the browser that will be used moving forward. Not because it’s the best option, but because it’s already there.</p>



<p>But remember, everyone can choose the browser they use, and as the designated tech whiz of the family, you can help inspire others to choose the right one.</p>



<p>Choosing Firefox means choosing privacy from the very first tap.</p>



<h3><strong>The browser is where the data lives</strong></h3>



<p>A browser is the door to everything you do online, and depending on how it’s designed, it can see a lot. Every site visited. Every phrase searched. Every link tapped. As we socialize, work, and explore on our phones, the browser can be the biggest funnel of personal data leaving that device, and how it’s built determines who collects that data, who can sell it, and how long it sticks around.</p>



<p>Privacy is the starting point for our browser, not an afterthought. Firefox is built on the<a href="https://firefox-source-docs.mozilla.org/contributing/data-collection.html"> principle</a> that not even Mozilla should know which websites you visit or what you do there.</p>



<h3><strong>Why Firefox is the right call</strong></h3>



<p>Firefox is backed by <a href="https://www.mozilla.org/">Mozilla</a>, a nonprofit-backed company with no shareholders to report to. Instead of chasing financial returns for a small group, Mozilla aims to provide an internet that truly puts people first. This means we limit the data we know about you and give you more choice about what data you share and when.</p>



<p>This <a href="https://www.firefox.com/user-privacy/">commitment to user privacy</a> is built into the browser itself. On both <a href="https://support.mozilla.org/kb/enhanced-tracking-protection-firefox-android">Android</a> and <a href="https://support.mozilla.org/kb/enhanced-tracking-protection-firefox-ios">iOS</a>, Enhanced Tracking Protection (ETP) is enabled by default, blocking known trackers every time you browse. This helps prevent advertisers and data brokers from following people across sites, no setup required. You can also adjust ETP to fit different needs, including turning it off altogether or activating Strict mode for even stronger protection.</p>



<p>Control and choice are built in, too. Firefox has an easily accessible <a href="https://blog.mozilla.org/firefox/how-to-use-ai-controls/">AI controls section</a> where people can customize how AI features show up in the browser, or turn them off entirely – because <a href="https://blog.mozilla.org/firefox/firefox-ai-on-your-terms/">AI should always be a choice</a>, not a requirement.</p>



<p>To carry these principles and protections across every link opened on a new phone, set Firefox as the default mobile browser in just a few taps.</p>



<h3><strong>How to set Firefox as the default browser on Android and iOS</strong></h3>



<p>Downloading the Firefox mobile app isn’t enough on its own, since most phones will keep opening links in whatever browser came preinstalled unless told otherwise. Here’s how to make Firefox the browser that actually opens by default. Make sure <a href="https://www.firefox.com/mobile/">Firefox is installed</a> on the device you’re working with before you begin.<strong><br/><br/>On </strong><a href="https://support.mozilla.org/kb/make-firefox-default-browser-android"><strong>Android</strong></a><strong>: </strong></p>



<ul>
<li>Open Firefox</li>



<li>Tap the three-dot menu button. </li>



<li>Tap Settings. </li>



<li>In the General section, locate the Set default browser<em> </em>option. </li>



<li>Tap the toggle next to Set as default browser to turn it on. </li>



<li>Select Firefox from the listed options.</li>



<li>Tap Set as default. </li>
</ul>



<p><strong>On </strong><a href="https://support.mozilla.org/kb/set-firefox-default-browser-ios"><strong>iOS</strong></a><strong>:</strong></p>



<ul>
<li>Open phone Settings.</li>



<li>Tap Apps. </li>



<li>Tap Default Apps.</li>



<li>Tap Browser App. </li>



<li>Select Firefox from the listed options.</li>
</ul>



<p>Once Firefox has been selected as the default browser, links tapped from messages, email, social media, or anywhere else will open in Firefox automatically. No additional steps required by your less tech-savvy family members and friends, and no relying on them to open the “right” browser every time they want to access the internet.</p>



<h3><strong>A little help on day one, lasting benefits later</strong></h3>



<p>The way a device is initially set up tends to stick. Whichever browser is already selected as default and whatever privacy settings are (or aren’t) adjusted on day one often just…stay that way. That’s a lot of reliance on whatever defaults the phone is purchased with.</p>



<p>So this fall, whether you are setting up a shiny new Google Pixel 11 for your aunt, an iPhone 18 Pro for your brother, or any other model for any one of your non-paying tech support “clients,” take an extra five minutes to help them download <a href="https://www.firefox.com/mobile/">Firefox</a> and set it as their default browser. They can start their new device journey browsing with privacy, choice, and control built in. And you can check one more thing off your unofficial family IT to-do list.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/set-firefox-default-mobile-browser/">An open letter to every family’s designated IT support</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-11-12T14:00:00Z</updated>
    <published>2026-11-12T14:00:00Z</published>
    <category term="Firefox"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/community/?p=2562</id>
    <link href="https://blog.mozilla.org/community/2026/11/12/newsletter-oct-2026/" rel="alternate" type="text/html"/>
    <title>A little Firefox inspo (and a pun)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Hi Mozillian, We’re quite late, but there’s still time to join the fun! In this edition, we’re sharing an online hackathon you can take part in from anywhere, a nostalgic … <a class="go" href="https://blog.mozilla.org/community/2026/11/12/newsletter-oct-2026/">Read more</a></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hi Mozillian,</p>
<p>We’re quite late, but there’s still time to join the fun! In this edition, we’re sharing an online hackathon you can take part in from anywhere, a nostalgic campaign to invite people to come back to Firefox, reminder of what makes Firefox different, and a contributor’s journey to landing three DevTools fixes. As a bonus, we’ve tucked in a little Firefox wordplay to give you something to puzzle over.</p>
<p>Grab your favorite drink and catch up with us!</p>
<p><b>Couldn’t make it to Barcelona? Join Developers Wilding online instead!</b></p>
<p><a href="https://blog.mozilla.org/community/files/2026/11/dev-wilding.jpg"><img alt="" class="alignnone size-full wp-image-2563" height="800" src="https://blog.mozilla.org/community/files/2026/11/dev-wilding.jpg" width="800"/></a></p>
<p>Got a side project you’ve been meaning to finish? Join <b>Developers Wilding: Online</b>, a two-week hackathon running from October 28 to November 11. Build with Otari, Mozilla.ai’s open-source AI platform, using your choice of models and tools.</p>
<p>Compete for <b>up to $1,200 in prizes</b> and opportunities to work directly with Mozilla.ai engineers! The first 200 people to sign up on<a href="https://otari.ai/"> Otari.ai</a> also get $20 in tokens. Ready to join?<a href="https://discord.gg/TqvzGH9mwz"> Join the Discord to grab the devs-wilding role</a> and get started!</p>
<p><a href="https://discord.gg/TqvzGH9mwz">Want to join in?</a></p>
<p><b>Remember how the internet used to feel like?</b></p>
<p>Firefox is bringing familiar faces from the early web together in a new campaign celebrating the creativity, curiosity, and community that made the internet feel personal. It’s an invitation for former users to come back and a reminder that privacy, independence, and a little internet weirdness are still worth celebrating.</p>
<p><a href="https://blog.mozilla.org/firefox/come-back-to-firefox/">Check out the campaign</a></p>
<p><b>Still here, still yours</b></p>
<p>What makes Firefox different? Mozilla’s latest blog post highlights five reasons to choose Firefox, from its nonprofit backing and privacy features to AI controls, its independent browser engine, and Kit, Firefox’s friendly companion. It’s a reminder of the values behind the browser our community helps support: privacy, independence, and choice.</p>
<p><a href="https://blog.mozilla.org/firefox/5-reasons-to-choose-firefox/">Read more</a></p>
<p><b>Firefox wordplay</b></p>
<p>Let’s take a quick break from product and community updates for a little Firefox wordplay to brighten your day. Someone on Reddit shared a question that might put your pun skills to the test: <b>What do you call a large number of Firefox users?</b></p>
<p><a href="https://www.reddit.com/r/firefox/comments/1vv0mmy/a_firefox_joke/">Check out the answer</a></p>
<p><b>Community Spotlight</b></p>
<p>Community spotlight is back in this edition and this time, we want you to meet Ahmed E. In his original post, Ahmed shares how he landed 3 DevTools fixes, including a keyboard accessibility fix for a bug first reported in 2016. This story showed us that you don’t need to understand the entire Firefox codebase to start contributing.</p>
<p><a href="https://www.reddit.com/r/firefox/s/ums6bPbLym">Check out the story</a></p>
<hr/>
<p>P.S.</p>
<p>Enjoyed these updates? Subscribe to the <a href="https://community.mozilla.org/newsletter">Mozilla Community Newsletter</a> and get the latest updates delivered straight to your inbox.</p>
<p> </p></div>
    </content>
    <updated>2026-11-12T07:26:54Z</updated>
    <published>2026-11-12T07:26:54Z</published>
    <category term="Newsletter"/>
    <author>
      <name>Rizki Kelimutu</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/community</id>
      <link href="https://blog.mozilla.org/community/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/community" rel="alternate" type="text/html"/>
      <subtitle>News and notes from and for the Mozilla community.</subtitle>
      <title>about:community</title>
      <updated>2026-11-12T07:27:19Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/</id>
    <link href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/" rel="alternate" title="Announcing Rust 1.100.0" type="text/html"/>
    <title xml:lang="en">Announcing Rust 1.100.0</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><p>The Rust team is happy to announce a new version of Rust, 1.100.0. Rust is a programming language empowering everyone to build reliable and efficient software.</p>
<p>If you have a previous version of Rust installed via <code>rustup</code>, you can get 1.100.0 with:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>$</span><span> rustup update stable</span></span></code></pre>
<p>If you don't have it already, you can get <a href="https://www.rust-lang.org/install.html" rel="external"><code>rustup</code></a> from the appropriate page on our website, and check out the <a href="https://doc.rust-lang.org/stable/releases.html#version-11000-2026-11-12" rel="external">detailed release notes for 1.100.0</a>.</p>
<p>If you'd like to help us out by testing future releases, you might consider updating locally to use the beta channel (<code>rustup default beta</code>) or the nightly channel (<code>rustup default nightly</code>). Please <a href="https://github.com/rust-lang/rust/issues/new/choose" rel="external">report</a> any bugs you might come across!</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#what-s-in-1-100-0-stable"/>
What's in 1.100.0 stable</h3>
<ul>
<li><a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#never-type">Never type</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#allocator-api"><code>Allocator</code> API</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#dropguard-run-a-closure-on-every-exit-path"><code>DropGuard</code> API</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#conjuring-zero-sized-types">Conjuring zero-sized types</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#reporting-unused-dependencies-in-cargo">Reporting unused dependencies in Cargo</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#reducing-cargo-cache-collisions">Reducing Cargo cache collisions</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#cargo-min-publish-age-a-k-a-dependency-cooldowns">Cargo min-publish-age</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#stabilized-apis">Stabilized APIs</a></li>
</ul>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#never-type"/>
Never type</h4>
<p>After 10 years and 5 failed stabilization attempts, <strong>the <a href="https://doc.rust-lang.org/stable/std/primitive.never.html" rel="external">never type</a> is finally stable</strong>! This also completes the <a href="https://goals.rust-lang.org/2026/stabilize-never-type.html" rel="external">project goal</a> for this work.</p>
<p>The never type, spelled <code>!</code> in code, is the canonical uninhabited type. It represents the type of diverging computations – computations which never resolve to any value – where any code that follows is unreachable. Expressions that terminate control flow, such as <code>return</code>, <code>break</code>, and <a href="https://doc.rust-lang.org/stable/std/process/fn.exit.html" rel="external"><code>std::process::exit</code></a>, also have the type <code>!</code>.</p>
<p>Since having a value of the never type is impossible, Rust permits a never-to-any coercion, allowing to turn <code>!</code> into any other type (this is what distinguishes it from any other uninhabited types). This can be used, for example, to not return a value from one of the branches of a <code>match</code> or an <code>if</code>:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span class="z-l-14 z-d-4">fn</span><span class="z-l-4 z-d-16"> mrrrow</span><span>(</span><span class="z-l-4 z-d-9">option</span><span class="z-l-1">:</span><span class="z-d-2"> Option</span><span>&lt;</span><span class="z-d-2">u32</span><span>&gt;</span><span>)</span><span> {</span></span>
<span class="giallo-l"><span class="z-l-14 z-d-4">    let</span><span class="z-l-4 z-d-9"> value</span><span class="z-l-14"> =</span><span class="z-l-14 z-d-11"> match</span><span class="z-l-4 z-d-9"> option</span><span> {</span></span>
<span class="giallo-l"><span class="z-l-13 z-d-7">        //</span><span class="z-l-12 z-d-7"> `x` has type `u32`</span></span>
<span class="giallo-l"><span class="z-d-2">        Some</span><span>(</span><span class="z-l-4 z-d-9">x</span><span>)</span><span class="z-l-1"> =&gt;</span><span class="z-l-4 z-d-9"> x</span><span>,</span></span>
<span class="giallo-l"><span class="z-l-13 z-d-7">        //</span><span class="z-l-12 z-d-7"> `return` has type `!`, which is then coerced to `u32`,</span></span>
<span class="giallo-l"><span class="z-l-13 z-d-7">        //</span><span class="z-l-12 z-d-7"> allowing the `match` to pass type checking.</span></span>
<span class="giallo-l"><span class="z-d-2">        None</span><span class="z-l-1"> =&gt;</span><span class="z-l-14 z-d-11"> return</span><span>,</span></span>
<span class="giallo-l"><span>    }</span><span>;</span></span>
<span class="giallo-l"><span class="z-l-13 z-d-7">    //</span><span class="z-l-12 z-d-7"> ...</span></span>
<span class="giallo-l"><span>}</span></span></code></pre>
<p>While the never type could already be used and observed this way, and even named in the return type of functions (<code>-&gt; !</code>), this release allows naming the never type anywhere:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span class="z-l-14 z-d-4">fn</span><span class="z-l-4 z-d-16"> infallible_unwrap</span><span>&lt;</span><span class="z-d-2">T</span><span>&gt;</span><span>(</span><span class="z-l-4 z-d-9">res</span><span class="z-l-1">:</span><span class="z-d-2"> Result</span><span>&lt;</span><span class="z-d-2">T</span><span>,</span><span class="z-l-14"> !</span><span>&gt;</span><span>)</span><span class="z-l-1"> -&gt;</span><span class="z-d-2"> T</span><span> {</span></span>
<span class="giallo-l"><span class="z-l-13 z-d-7">    //</span><span class="z-l-12 z-d-7"> ^^ writing `Result&lt;_, !&gt;` was not allowed before</span></span>
<span class="giallo-l"><span class="z-l-14 z-d-4">    let</span><span class="z-d-2"> Ok</span><span>(</span><span class="z-l-4 z-d-9">v</span><span>)</span><span class="z-l-14"> =</span><span class="z-l-4 z-d-9"> res</span><span>;</span></span>
<span class="giallo-l"><span class="z-l-4 z-d-9">    v</span></span>
<span class="giallo-l"><span>}</span></span></code></pre>
<p>Additionally this release changes <a href="https://doc.rust-lang.org/stable/std/convert/type.Infallible.html" rel="external"><code>Infallible</code></a> to be an alias to the never type. That makes all old APIs that used <code>Infallible</code> be compatible with using <code>!</code>. This was the plan ever since the introduction of <code>Infallible</code> and is one of the reasons why the never type stabilization was so hard (waffle gave a <a href="https://www.youtube.com/watch?v=3jM4cnEVrLc" rel="external">talk</a> about some of the troubles of the stabilization).</p>
<p>Unfortunately, to allow changing <code>Infallible</code>, we had to introduce a breaking change. This release changes the "never type fallback" from <code>()</code> to <code>!</code> in editions <strong>before</strong> 2024 (i.e. 2015, 2018, and 2021), similarly to what has <a href="https://doc.rust-lang.org/edition-guide/rust-2024/never-type-fallback.html" rel="external">already been done in edition 2024</a>. This should largely be unnoticeable, but can affect code in some rare cases (for example when ignoring a result of a function returning a generic parameter). Note that this change might also make the compiler detect more code as unreachable.</p>
<p>We tried to minimize the impact of this breaking change as much as possible, by providing future compatibility warnings far in advance and releasing fixes to public crates that have been broken by this. If a dependency is failing due to issues with the never type, consider updating it, as a fix might have already been released for it.</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#allocator-api"/>
<code>Allocator</code> API</h4>
<p>This release brings about the stabilization of the core parts of <a href="https://github.com/rust-lang/rust/issues/32838" rel="external"><code>allocator_api</code></a>, enabling library authors to define custom allocators that can be used together with certain standard library types - currently <code>Vec</code> and <code>Box</code>. These are enabled through the newly-stabilized <a href="https://doc.rust-lang.org/std/alloc/trait.Allocator.html" rel="external"><code>Allocator</code></a> trait.</p>
<p>This is the foundation of the <a href="https://goals.rust-lang.org/2026/allocators-1.0.html" rel="external">Allocators 1.0 project goal</a>. A lot remains to be done still, including expanding the API surface usable with custom allocators and stabilizing their use on more collections and pointer types; with the core trait and design out of the way though, expect to see more being stabilized soon!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#dropguard-run-a-closure-on-every-exit-path"/>
<code>DropGuard</code>: run a closure on every exit path</h4>
<p>The <code>Drop</code> trait in Rust makes it possible to run code when a variable goes out of scope, regardless of whether we <code>return</code>, <code>?</code>, or panic. <code>Drop</code> being a part of types means that <a href="https://blog.skylight.io/rust-means-never-having-to-close-a-socket/" rel="external">in Rust you never have to close a socket</a>.</p>
<p>Implementing <code>Drop</code> can however feel a little inconvenient when all you want is to run some code unconditionally when a function exits. This is why we’re introducing <code>core::mem::DropGuard</code>: a new helper type that runs a closure when dropped.</p>
<p><code>DropGuard</code> takes two arguments: a variable and a closure. It implements <code>Deref</code> and <code>DerefMut</code> so you can keep working with the variable as normal. But when dropped it runs the closure and consumes the variable.</p>
<p><code>DropGuard</code> also implements a <code>dismiss</code> method which returns the variable from the guard without running the destructor. This makes it possible to quickly implement all-or-nothing transaction-like APIs with a rollback. Here is an example implementing a parser which uses a guard to roll back mutations in case of failure:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span class="z-l-14 z-d-4">use</span><span class="z-d-2"> std</span><span class="z-l-1">::</span><span class="z-d-2">mem</span><span class="z-l-1">::</span><span class="z-d-2">DropGuard</span><span>;</span></span>
<span class="giallo-l"><span class="z-l-14 z-d-4">use</span><span class="z-d-2"> std</span><span class="z-l-1">::</span><span class="z-d-2">num</span><span class="z-l-1">::</span><span class="z-d-2">ParseIntError</span><span>;</span></span>
<span class="giallo-l"/>
<span class="giallo-l"><span class="z-l-13 z-d-7">///</span><span class="z-l-13 z-d-7"> Attempt to parse all `strings` and push them into `nums`.</span></span>
<span class="giallo-l"><span class="z-l-13 z-d-7">///</span><span class="z-l-13 z-d-7"> If parsing any of them fails, `nums` remains unchanged.</span></span>
<span class="giallo-l"><span class="z-l-14 z-d-4">fn</span><span class="z-l-4 z-d-16"> parse_all</span><span>(</span><span class="z-l-4 z-d-9">nums</span><span class="z-l-1">:</span><span class="z-l-1"> &amp;</span><span class="z-l-14 z-d-4">mut</span><span class="z-d-2"> Vec</span><span>&lt;</span><span class="z-d-2">u32</span><span>&gt;</span><span>,</span><span class="z-l-4 z-d-9"> strings</span><span class="z-l-1">:</span><span class="z-l-1"> &amp;</span><span>[</span><span class="z-l-1">&amp;</span><span class="z-d-2">str</span><span>]</span><span>)</span><span class="z-l-1"> -&gt;</span><span class="z-d-2"> Result</span><span>&lt;</span><span>(</span><span>)</span><span>,</span><span class="z-d-2"> ParseIntError</span><span>&gt;</span><span> {</span></span>
<span class="giallo-l"><span class="z-l-14 z-d-4">    let</span><span class="z-l-4 z-d-9"> len</span><span class="z-l-14"> =</span><span class="z-l-4 z-d-9"> nums</span><span class="z-l-1">.</span><span class="z-l-4 z-d-16">len</span><span>(</span><span>)</span><span>;</span></span>
<span class="giallo-l"><span class="z-l-14 z-d-4">    let</span><span class="z-l-14 z-d-4"> mut</span><span class="z-l-4 z-d-9"> nums</span><span class="z-l-14"> =</span><span class="z-d-2"> DropGuard</span><span class="z-l-1">::</span><span class="z-l-4 z-d-16">new</span><span>(</span><span class="z-l-4 z-d-9">nums</span><span>,</span><span class="z-l-14 z-d-4"> move</span><span class="z-l-14"> |</span><span class="z-l-4 z-d-9">nums</span><span class="z-l-14">|</span><span> {</span></span>
<span class="giallo-l"><span class="z-l-4 z-d-9">        nums</span><span class="z-l-1">.</span><span class="z-l-4 z-d-16">truncate</span><span>(</span><span class="z-l-4 z-d-9">len</span><span>)</span><span>;</span><span class="z-l-13 z-d-7">    //</span><span class="z-l-12 z-d-7"> ← 1. Reset the vec on failure</span></span>
<span class="giallo-l"><span>    }</span><span>)</span><span>;</span></span>
<span class="giallo-l"/>
<span class="giallo-l"><span class="z-l-14 z-d-11">    for</span><span class="z-l-4 z-d-9"> s</span><span class="z-l-14 z-d-4"> in</span><span class="z-l-4 z-d-9"> strings</span><span> {</span></span>
<span class="giallo-l"><span class="z-l-4 z-d-9">        nums</span><span class="z-l-1">.</span><span class="z-l-4 z-d-16">push</span><span>(</span><span class="z-l-4 z-d-9">s</span><span class="z-l-1">.</span><span class="z-l-4 z-d-16">parse</span><span>(</span><span>)</span><span class="z-l-1">?</span><span>)</span><span>;</span><span class="z-l-13 z-d-7"> //</span><span class="z-l-12 z-d-7"> ← 2. If `?` returns an error, roll back</span></span>
<span class="giallo-l"><span>    }</span></span>
<span class="giallo-l"/>
<span class="giallo-l"><span class="z-d-2">    DropGuard</span><span class="z-l-1">::</span><span class="z-l-4 z-d-16">dismiss</span><span>(</span><span class="z-l-4 z-d-9">nums</span><span>)</span><span>;</span><span class="z-l-13 z-d-7">  //</span><span class="z-l-12 z-d-7"> ← 3. Parsing successful, dismiss the guard</span></span>
<span class="giallo-l"><span class="z-d-2">    Ok</span><span>(</span><span>(</span><span>)</span><span>)</span></span>
<span class="giallo-l"><span>}</span></span></code></pre><h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#conjuring-zero-sized-types"/>
Conjuring zero-sized types</h4>
<p>As Rust's <a href="https://github.com/rust-lang/unsafe-code-guidelines" rel="external">unsafe code guidelines</a> are still being decided, it became clear that it would be very useful to decide what exactly it means to create zero-sized types in an unsafe way, and what we should recommend for people to do this.</p>
<p>This question is answered in Rust 1.100 with a single function: <a href="https://doc.rust-lang.org/stable/std/mem/fn.conjure_zst.html" rel="external"><code>std::mem::conjure_zst</code></a>.</p>
<p>Instead of transmuting <code>()</code>, <code>MaybeUninit::uninit().assume_init()</code>, or various other incantations, this is the dedicated way to create a value of a zero-sized type when you know that doing so is safe to do. If an inhabited type has no size, we know exactly what value it must be: nothing.</p>
<p>Of course, APIs often rely on the inability to construct such types for safety, and that's why this function is unsafe. For example, PyO3's <a href="https://docs.rs/pyo3/0.30.1/pyo3/marker/struct.Python.html" rel="external"><code>Python&lt;'py&gt;</code></a> is a zero-sized marker token that represents holding the Python GIL (global interpreter lock). Many of Python's APIs require holding this lock to be safe, but conjuring a token from thin air would allow safe PyO3 calls to violate that precondition.</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#reporting-unused-dependencies-in-cargo"/>
Reporting unused dependencies in Cargo</h4>
<p>Building dependencies that are no longer used or are only needed for specific platforms can slow down builds.
Rustc has the <code>unused_crate_dependencies</code> lint for this but it has false positives when used with Cargo because dependencies may be shared between multiple build targets, e.g. <code>dependencies.tracing-subscriber</code> being available for every <code>bin</code> in a package when only some may use it.</p>
<p>Cargo now reports unused dependencies to users, e.g.</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>warning: unused dependency `tracing-subscriber`</span></span>
<span class="giallo-l"><span>  --&gt; Cargo.toml:23:1</span></span>
<span class="giallo-l"><span>   |</span></span>
<span class="giallo-l"><span>23 | tracing-subscriber.workspace = true</span></span>
<span class="giallo-l"><span>   | ^^^^^^^^^^^^^^^^^^</span></span>
<span class="giallo-l"><span>   |</span></span>
<span class="giallo-l"><span>   = note: `cargo::unused_dependencies` is set to `warn` by default</span></span>
<span class="giallo-l"><span>help: consider removing the dependency on `tracing-subscriber`</span></span></code></pre>
<p>A limitation of this warning is that it will only appear when building every build target that may use an entry in a dependencies table.
For example, running <code>cargo check --bin foo</code> won't show warnings for unused <code>[dependencies]</code> because another <code>bin</code> may be present that uses them.
No warning will be shown for unused <code>dev-dependencies</code> because there isn't a way to ensure every development build target is built.</p>
<p>This warning is being introduced as part of a new linting system for Cargo, controlled by the <code>[lints.cargo]</code> table in <code>Cargo.toml</code>, completing this <a href="https://goals.rust-lang.org/2026/cargo-lints.html" rel="external">project goal</a>. See also the <a href="https://doc.rust-lang.org/stable/cargo/reference/lints.html" rel="external">other lints that have been introduced</a>.</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#reducing-cargo-cache-collisions"/>
Reducing Cargo cache collisions</h4>
<p>Cargo builds all libraries and binaries in the <code>build-dir</code> and then uplifts final artifacts to the <code>target-dir</code>. At this time, these share a common parent directory.
Different build configurations, like <code>--features</code>, can lead to different copies of libraries and binaries in the <code>build-dir</code>.
These copies are kept unique by a build-configuration hash but this hash was not always applied due to platform constraints.
This can lead to extra rebuilds, missed rebuilds, confusion over what binaries or libraries are used, and so on.
These problems get exacerbated when sharing a <code>build-dir</code> across git worktrees.</p>
<p>The <code>build-dir</code> now consistently applies the build-configuration hash to all content by organizing the directories around their build step, rather than their file type, and moving the hash from a file's name to the parent directory.</p>
<p>This work began with the <a href="https://goals.rust-lang.org/2025h2/cargo-build-dir-layout.html" rel="external">build directory layout project goal</a> in 2025, and its stabilization is a milestone toward a new <a href="https://goals.rust-lang.org/2026/cargo-cross-workspace-cache.html" rel="external">project goal</a>, unblocking future improvements such as cache garbage collection, cross-workspace cache de-duplication, cross-workspace caching, and fine grain locking.</p>
<p>We previously published a <a href="https://blog.rust-lang.org/2026/03/13/call-for-testing-build-dir-layout-v2/" rel="external">call for testing</a> for the changes that are now taking effect.
While this is an internal change, this may break build processes and tests that had workarounds for missing or incomplete features.
In some cases, the workaround is no longer needed.
See <a href="https://github.com/rust-lang/cargo/issues/17287" rel="external">cargo#17287</a> for possible solutions and to add any new use cases.</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#cargo-min-publish-age-a-k-a-dependency-cooldowns"/>
Cargo min-publish-age a.k.a. dependency cooldowns</h4>
<p>Malicious versions of packages are often caught within hours or days after being published, by either automated scanners or by the community.
Rust 1.100 stabilizes Cargo's min-publish-age aware dependency resolution, which lets you wait for that window before it picks up newly published versions.
This practice is also known as dependency cooldowns.</p>
<p>You can opt in via <a href="https://doc.rust-lang.org/cargo/reference/config.html#registryglobal-min-publish-age" rel="external"><code>.cargo/config.toml</code></a>:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>[</span><span>registry</span><span>]</span></span>
<span class="giallo-l"><span class="z-l-4 z-d-9">global-min-publish-age</span><span> =</span><span class="z-l-2 z-d-13"> "</span><span class="z-l-19 z-d-13">3 days</span><span class="z-l-2 z-d-13">"</span></span></code></pre>
<p>When selecting versions, Cargo now skips any version published more recently than that, and tells you what it held back:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>$</span><span> cargo update</span></span>
<span class="giallo-l"><span>    Updating crates.io index</span></span>
<span class="giallo-l"><span>     Locking 2 packages to highest compatible version as of min-publish-age</span></span>
<span class="giallo-l"><span>      Adding cc v1.11.0 (available: v1.18.0, published 3 hours ago)</span></span>
<span class="giallo-l"><span>      Adding clap 4.6.7 (available: 4.6.9, published 2 days ago)</span></span></code></pre>
<p>When a new version is needed right away, you can override the check for a single update:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>$</span><span class="z-l-4 z-d-9"> CARGO_RESOLVER_INCOMPATIBLE_PUBLISH_AGE</span><span class="z-l-14">=</span><span class="z-l-4 z-d-13">a</span><span class="z-l-4 z-d-13">l</span><span class="z-l-4 z-d-13">l</span><span class="z-l-4 z-d-13">o</span><span class="z-l-4 z-d-13">w</span><span class="z-l-4 z-d-16"> cargo</span><span class="z-l-4 z-d-13"> update</span><span class="z-l-4 z-d-13"> clap</span><span class="z-l-4 z-d-4"> -</span><span class="z-l-4 z-d-4">-precise</span><span class="z-l-16 z-d-10"> 4.6.9</span></span>
<span class="giallo-l"><span>    Updating crates.io index</span></span>
<span class="giallo-l"><span>    Updating clap 4.6.7 -&gt; clap 4.6.9 (published 2 days ago, minimum age 3 days)</span></span></code></pre>
<p>The newer version will be recorded in <code>Cargo.lock</code> and kept from then on until a later <code>cargo update</code> re-resolves it.</p>
<p>A few things to keep in mind:</p>
<ul>
<li>
<p>This depends on the registry recording when each version was published.
Versions without a <code>pubtime</code> field in the index are never held back.</p>
</li>
<li>
<p><code>cargo install</code> ignores the minimum publish age, for both the installed crate and its dependencies.
Pin a version with <code>cargo install foo@1.2.3</code> if needed.</p>
</li>
<li>
<p>Cooldowns reduce the risk from some supply chain attacks but are not a complete defense on their own.
Please keep reviewing dependency updates as you otherwise would.</p>
</li>
</ul>
<p>Further work to protect the ecosystem is planned under the <a href="https://goals.rust-lang.org/2026/crates-io-supply-chain-hardening.html" rel="external">crates.io supply chain hardening project goal</a>, including quarantine support and automated detection of suspicious releases.</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#stabilized-apis"/>
Stabilized APIs</h4>
<ul>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#impl-PartialEq%3CCow%3C'_,+%5BU%5D%3E%3E-for-Vec%3CT,+A%3E" rel="external"><code>impl PartialEq&lt;Cow&lt;'_, [U]&gt;&gt; for Vec&lt;T, A&gt;</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.slice.html#impl-PartialEq%3CCow%3C'_,+%5BU%5D%3E%3E-for-%26%5BT%5D" rel="external"><code>impl PartialEq&lt;Cow&lt;'_, [U]&gt;&gt; for &amp;[T]</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.slice.html#impl-PartialEq%3CCow%3C'_,+%5BU%5D%3E%3E-for-%26mut+%5BT%5D" rel="external"><code>impl PartialEq&lt;Cow&lt;'_, [U]&gt;&gt; for &amp;mut [T]</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html" rel="external"><code>std::alloc::Allocator</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/struct.Global.html" rel="external"><code>std::alloc::Global</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/struct.System.html" rel="external"><code>std::alloc::System</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-Global" rel="external"><code>impl Allocator for Global</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-System" rel="external"><code>impl Allocator for System</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-%26A" rel="external"><code>impl&lt;A: Allocator&gt; Allocator for &amp;A</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-Box%3CT,+A%3E" rel="external"><code>impl&lt;T: Allocator, A: Allocator&gt; Allocator for Box&lt;T, A&gt;</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-%26mut+A" rel="external"><code>impl&lt;A: Allocator&gt; Allocator for &amp;mut A</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-Arc%3CT,+A%3E" rel="external"><code>impl&lt;T: Allocator, A: Allocator&gt; Allocator for Arc&lt;T, A&gt;</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.html#impl-Allocator-for-Rc%3CT,+A%3E" rel="external"><code>impl&lt;T: Allocator, A: Allocator&gt; Allocator for Rc&lt;T, A&gt;</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.new_in" rel="external"><code>Box::new_in</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.from_raw_in" rel="external"><code>Box::from_raw_in</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.from_non_null_in" rel="external"><code>Box::from_non_null_in</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.into_raw_with_allocator" rel="external"><code>Box::into_raw_with_allocator</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.into_non_null_with_allocator" rel="external"><code>Box::into_non_null_with_allocator</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.allocator" rel="external"><code>Box::allocator</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#method.new_in" rel="external"><code>Vec::new_in</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#method.with_capacity_in" rel="external"><code>Vec::with_capacity_in</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#method.from_raw_parts_in" rel="external"><code>Vec::from_raw_parts_in</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#method.from_parts_in" rel="external"><code>Vec::from_parts_in</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#method.into_raw_parts_with_allocator" rel="external"><code>Vec::into_raw_parts_with_allocator</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#method.into_parts_with_allocator" rel="external"><code>Vec::into_parts_with_allocator</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#method.allocator" rel="external"><code>Vec::allocator</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/os/windows/process/trait.ChildExt.html#tymethod.main_thread_handle" rel="external"><code>Child::main_thread_handle</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/sync/struct.Once.html#impl-Default-for-Once" rel="external"><code>impl Default for std::sync::Once</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.bool.html#method.toggle" rel="external"><code>bool::toggle</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.take" rel="external"><code>Box::take</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/boxed/struct.Box.html#method.map" rel="external"><code>Box::map</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/rc/struct.Rc.html#method.map" rel="external"><code>Rc::map</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/sync/struct.Arc.html#method.map" rel="external"><code>Arc::map</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.never.html#impl-AsRef%3CT%3E-for-!" rel="external"><code>impl AsRef&lt;T&gt; for !</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.never.html#impl-AsMut%3CT%3E-for-!" rel="external"><code>impl AsMut&lt;T&gt; for !</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/core/mem/struct.DropGuard.html" rel="external"><code>core::mem::DropGuard</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/core/mem/fn.conjure_zst.html" rel="external"><code>core::mem::conjure_zst</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/cell/struct.UnsafeCell.html#method.replace" rel="external"><code>UnsafeCell::replace</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/cell/struct.UnsafeCell.html#method.as_ref_unchecked" rel="external"><code>UnsafeCell::as_ref_unchecked</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/cell/struct.UnsafeCell.html#method.as_mut_unchecked" rel="external"><code>UnsafeCell::as_mut_unchecked</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.str.html#method.trim_prefix" rel="external"><code>str::trim_prefix</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.str.html#method.trim_suffix" rel="external"><code>str::trim_suffix</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.slice.html#method.trim_prefix" rel="external"><code>[T]::trim_prefix</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/primitive.slice.html#method.trim_suffix" rel="external"><code>[T]::trim_suffix</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/path/struct.Path.html#method.trim_prefix" rel="external"><code>Path::trim_prefix</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/vec/struct.Vec.html#method.from_fn" rel="external"><code>Vec::from_fn</code></a></li>
<li><a href="https://doc.rust-lang.org/stable/std/os/windows/process/trait.CommandExt.html#tymethod.show_window" rel="external"><code>os::windows::process::CommandExt::show_window</code></a></li>
</ul>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#other-changes"/>
Other changes</h4>
<p>Check out everything that changed in <a href="https://github.com/rust-lang/rust/releases/tag/1.100.0" rel="external">Rust</a>, <a href="https://doc.rust-lang.org/nightly/cargo/CHANGELOG.html#cargo-1100-2026-11-12" rel="external">Cargo</a>, and <a href="https://github.com/rust-lang/rust-clippy/blob/master/CHANGELOG.md#rust-1100" rel="external">Clippy</a>.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/#contributors-to-1-100-0"/>
Contributors to 1.100.0</h3>
<p>Many people came together to create Rust 1.100.0. We couldn't have done it without all of you. <a href="https://thanks.rust-lang.org/rust/1.100.0/" rel="external">Thanks!</a></p></div>
    </content>
    <updated>2026-11-12T00:00:00Z</updated>
    <published>2026-11-12T00:00:00Z</published>
    <author>
      <name>The Rust Release Team</name>
    </author>
    <source>
      <id>https://blog.rust-lang.org/</id>
      <author>
        <name>Maintained by the Rust Teams.</name>
        <uri>https://github.com/rust-lang/blog.rust-lang.org/</uri>
      </author>
      <link href="https://blog.rust-lang.org/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://blog.rust-lang.org/" rel="alternate" type="text/html"/>
      <subtitle xml:lang="en">Empowering everyone to build reliable and efficient software.</subtitle>
      <title xml:lang="en">Rust Blog</title>
      <updated>2026-11-13T09:01:38Z</updated>
    </source>
  </entry>

  <entry>
    <id>tag:this-week-in-rust.org,2026-11-11:/blog/2026/11/11/this-week-in-rust-677/</id>
    <link href="https://this-week-in-rust.org/blog/2026/11/11/this-week-in-rust-677/" rel="alternate" type="text/html"/>
    <title>This Week in Rust 677</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello and welcome to another issue of <em>This Week in Rust</em>!
<a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
This is a weekly summary of its progress and community.
Want something mentioned? Tag us at
<a href="https://bsky.app/profile/thisweekinrust.bsky.social">@thisweekinrust.bsky.social</a> on Bluesky or
<a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social …</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello and welcome to another issue of <em>This Week in Rust</em>!
<a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
This is a weekly summary of its progress and community.
Want something mentioned? Tag us at
<a href="https://bsky.app/profile/thisweekinrust.bsky.social">@thisweekinrust.bsky.social</a> on Bluesky or
<a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social, or
<a href="https://github.com/rust-lang/this-week-in-rust">send us a pull request</a>.
Want to get involved? <a href="https://github.com/rust-lang/rust/blob/main/CONTRIBUTING.md">We love contributions</a>.</p>
<p><em>This Week in Rust</em> is openly developed <a href="https://github.com/rust-lang/this-week-in-rust">on GitHub</a> and archives can be viewed at <a href="https://this-week-in-rust.org/">this-week-in-rust.org</a>.
If you find any errors in this week's issue, <a href="https://github.com/rust-lang/this-week-in-rust/pulls">please submit a PR</a>.</p>
<p>Want TWIR in your inbox? <a href="https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&amp;id=0ed8b72485">Subscribe here</a>.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#updates-from-rust-community">Updates from Rust Community</a></h4>


<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#official">Official</a></h5>
<ul>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results">Google Summer of Code 2026 results</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#newsletters">Newsletters</a></h5>
<ul>
<li><a href="https://www.theembeddedrustacean.com/p/the-embedded-rustacean-issue-84">The Embedded Rustacean Issue #84</a></li>
</ul>


<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#observationsthoughts">Observations/Thoughts</a></h5>
<ul>
<li><a href="https://kerkour.com/rust-supply-chain-security-stdx">Securing Rust's supply chain with an extended standard library</a></li>
<li><a href="https://www.cncf.io/blog/2026/11/09/run-linux-applications-in-hypervisor-isolated-micro-vms-with-hyperlight/">Run Linux applications in hypervisor-isolated micro-VMs with Hyperlight</a></li>
<li>[series] <a href="https://iggy.apache.org/blogs/2026/10/27/vsr-clustering-part-3/">Apache Iggy's migration journey to clustering powered by Viewstamped Replication (part 3)</a></li>
<li><a href="https://rust-lang.zulipchat.com/#narrow/channel/122651-general/topic/I.20snuck.20into.20the.20Rust.20Foundation.27s.20secret.20meeting">I snuck into the Rust Foundation's secret meeting; here's what you need to know.</a></li>
<li><a href="https://heikoseeberger.de/2026-11-09-chaos-verifier/">Breaking a Rust actor cluster on purpose, and what it taught us</a></li>
<li><a href="https://xd009642.github.io/2026/11/10/Catching-Panics-in-Production/">Catching Panics in Production</a></li>
<li><a href="https://opendal.apache.org/blog/2026/11/11/scopedb-on-opendal/">Skipping Cloud Vendor SDKs: How ScopeDB Accesses Object Storage with Apache OpenDAL</a></li>
<li><a href="https://serokell.io/blog/ubuntu-rust-coreutils-jon-seager">Bringing Rust into Ubuntu at Scale: Interview with Jon Seager</a></li>
<li><a href="https://hotpath.rs/blog/rust-performance-benchmarking">Rust Benchmarking: How to Detect Performance Regressions in CI</a></li>
<li>[video] <a href="https://www.youtube.com/watch?v=5D7QPOIZ7gY">Code Matters: Reflections on Rust in the LLM Age — Bryan Cantrill | Rust NYC</a></li>
<li><a href="https://blog.zortax.de/posts/a-critique-of-gpui">A Critique of GPUI</a></li>
<li><a href="https://forge-blog.github.io/posts/rust-std-memory-safety/">Memory Safety Bugs in Rust Standard Library</a></li>
<li><a href="https://sigseis.dev/articles/2026/11/10">Rust Declarative Macros: Organization, Scoping, and Common Use-Cases</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-walkthroughs">Rust Walkthroughs</a></h5>
<ul>
<li><a href="https://scherzer.dev/Blog/20261106-rsphp-bindings">RSPHP Part 1: Bindings</a></li>
<li><a href="https://sofiabelen.github.io/projects/pointer-provenance-in-rust-vs-cpp/">Pointer Provenance in Rust vs C++: Pointers Are Not Just Glorified Ints</a></li>
<li><a href="https://www.reymom.xyz/blog/rust/2026-11-06-tokio-channels-and-poisoned-locks">Tokio, channels and poisoned locks</a></li>
<li>[video] <a href="https://www.youtube.com/watch?v=h3okIDxOZIA">RustCurious lesson 12: Lifetimes</a></li>
</ul>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#crate-of-the-week">Crate of the Week</a></h4>
<p>This week's crate is <a href="https://docs.rs/iddqd">iddqd</a>, a library of maps where keys are borrowed from values.</p>
<p>Thanks to <a href="https://users.rust-lang.org/t/crate-of-the-week/2704/1715">Miro</a> for the suggestion!</p>
<p><a href="https://users.rust-lang.org/t/crate-of-the-week/2704">Please submit your suggestions and votes for next week</a>!</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#calls-for-testing">Calls for Testing</a></h4>
<p>An important step for RFC implementation is for people to experiment with the
implementation and give feedback, especially before stabilization.</p>
<p>If you are a feature implementer and would like your RFC to appear in this list, add a
<code>call-for-testing</code> label to your RFC along with a comment providing testing instructions and/or
guidance on which aspect(s) of the feature need testing.</p>
<p><em>No calls for testing were issued this week by
<a href="https://github.com/rust-lang/rust/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Rust</a>,
<a href="https://github.com/rust-lang/cargo/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Cargo</a>,
<a href="https://github.com/rust-lang/rustup/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Rustup</a> or
<a href="https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing%20state%3Aopen">Rust language RFCs</a>.</em></p>
<p><a href="https://github.com/rust-lang/this-week-in-rust/issues">Let us know</a> if you would like your feature to be tracked as a part of this list.</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rfcs"/><a href="https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing">RFCs</a></h5>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust"/><a href="https://github.com/rust-lang/rust/labels/call-for-testing">Rust</a></h5>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustup"/><a href="https://github.com/rust-lang/rustup/labels/call-for-testing">Rustup</a></h5>
<p>If you are a feature implementer and would like your RFC to appear on the above list, add the new <code>call-for-testing</code>
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
need testing.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers">Call for Participation; projects and speakers</a></h4>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cfp-projects">CFP - Projects</a></h5>
<p>Always wanted to contribute to open-source projects but did not know where to start?
Every week we highlight some tasks from the Rust community for you to pick and get started!</p>
<p>Some of these tasks may also have mentors available, visit the task page for more information.</p>


<ul>
<li><a href="https://github.com/Muneer320/klicky/issues/116">Klicky - Cover silence and signed sample boundaries in audio-normalization tests</a></li>
<li><a href="https://github.com/Muvon/octomind/issues/296">Octomind - <code>parallel = "true"</code> in a workflow step fails with "missing field <code>role</code>"</a></li>
<li><a href="https://github.com/Muvon/octomind/issues/295">Octomind - <code>schedule</code> accepts <code>when="13am"</code> and fires at 13:00</a></li>
<li><a href="https://github.com/Muvon/octomind/issues/299">Octomind - <code>octomind configure</code> saves a pasted API key with spaces around it</a></li>
<li><a href="https://github.com/UmberaAPP/UMBERA/issues/3">Umbera - Fuzz target for pdf_strip_metadata</a></li>
<li><a href="https://github.com/UmberaAPP/UMBERA/issues/2">Umbera - Add NIST ACVP known-answer tests for ML-KEM-1024</a></li>
<li><a href="https://github.com/lacs-project/sysknife/issues/702">sysknife - publish-mcp.yml runs an unpinned mcp-publisher with id-token: write, and pinned-dependencies.test.sh never reads that file</a></li>
<li><a href="https://github.com/lacs-project/sysknife/issues/621">sysknife - MCP plan and execute results do not name the host they came from</a></li>
<li><a href="https://github.com/lacs-project/sysknife/issues/659">sysknife - dev-stories.sh runs the stories against the sysknife on PATH, not the binary it builds</a></li>
<li><a href="https://github.com/MasihMoafi/Elpis/issues/112">Elpis - Add DeepSeek, Mistral or Groq as a built-in provider</a></li>
<li><a href="https://github.com/MasihMoafi/Elpis/issues/113">Elpis - Publish and maintain the elpis-bin package on the AUR</a></li>
</ul>


<p>If you are a Rust project owner and are looking for contributors, please submit tasks <a href="https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines">here</a> or through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a> or by reaching out on <a href="https://bsky.app/profile/thisweekinrust.bsky.social">Bluesky</a> or <a href="https://mastodon.social/@thisweekinrust">Mastodon</a>!</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cfp-events">CFP - Events</a></h5>
<p>Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.</p>



<p>If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a> or by reaching out on <a href="https://bsky.app/profile/thisweekinrust.bsky.social">Bluesky</a> or <a href="https://mastodon.social/@thisweekinrust">Mastodon</a>!</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#updates-from-the-rust-project">Updates from the Rust Project</a></h4>
<p>659 pull requests were <a href="https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2026-11-03..2026-11-10">merged in the last week</a></p>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#compiler">Compiler</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/163241">add enclosing item context when pointing at <code>FnMut</code> bound</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164414">add <code>let_underscore_drop_guard</code> lint</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164014">don't emit no-op <code>&amp;T</code> → <code>&amp;T</code> reborrows</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165539">lint: do not emit <code>unreachable_code</code> on become with diverging callee</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/149245">make inline attributes apply to the generated <code>poll</code> in async fn</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165404">next solver unsize coercion diagnostics</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163284">reborrow: Allow multiple lifetimes</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165672">restore the fast path of <code>QueryTypeOp</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164304">reuse CanonicalVarKinds if no new variables were added</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165161"><code>rustc_builtin_macros</code> cleanup, part 9</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165602">skip <code>reachable_set</code> calculation during metadata encoding when unused</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165571">support mutable captures in move expressions</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#library">Library</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/165569"><code>Move</code> trait feature gate</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163624"><code>String::retain</code>: convert only the untouched UTF-8 tail</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165463">add <code>BTreeMap::allocator</code> and <code>BTreeSet::allocator</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163992">add <code>core::arch::{x86, x86_64}::x87_f80</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165443">add <code>Discriminant::ord</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165697">add <code>LinkedList::allocator</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165037">drop array elements in order after a partial move</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165546">expose <code>str::split_at_[mut_]unchecked</code> and <code>OsStr::split_at_unchecked</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165330">implement <code>read_le/read_be</code> for f16 and f128</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/147696">implement <code>bit</code> and <code>set_bit</code> for integral types</a></li>
<li><a href="https://github.com/rust-lang/compiler-builtins/pull/1333">optimize memset/memcpy size</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cargo">Cargo</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/cargo/pull/17705"><code>config</code>: Expose config merging, reading, and schemas in a crate</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17683"><code>schema</code>: Expose SBOM types</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17702"><code>doc</code>: do not suggest cargo fix for rustdoc warnings</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17678"><code>profile</code>: preserve inherited strip</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17665"><code>registry</code>: handle HTTP 410/451 for missing crates</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17697"><code>schema</code>: Improve deserialization errors and performance</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17701"><code>parse</code>: Trade remote manifest diagnostic quality for performance</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17675">clean <code>/out</code> dir before compilation</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17689">dont strip if any transtive dep has debuginfo on</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17691">strip host deps whose debuginfo was weakened already</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustdoc">Rustdoc</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/163217">Avoid re-HIR-ty-lowering tys &amp; const args where possible</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165726">frontend: Properly clear search state when sidebar link is clicked</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164036">Allow <code>.</code> to be used the same as <code>:</code>: in the search</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163571">Render <code>Deref</code> methods on aliased items</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165357">fix invalid clean of paths when they end with <code>self</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165495">improve performance by skipping unneeded intermediate JSON serializations</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165427">make implementors collapseable if there is more than one line of docs</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165660">suggest reference definitions for unresolved links</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustfmt">Rustfmt</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7220">allow reading args from <code>@path</code></a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7217">fix unclosed trailing block comments with <code>wrap_comments=true</code> or <code>normalize_comments=true</code></a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/6167">formatting empty where clauses when there are return types</a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/5392">remove each comment's leading whitespace in <code>comment::rewrite_comment</code></a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#clippy">Clippy</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17906"><code>while_let_loop</code>: lint only wildcard <code>break</code> patterns and special cases</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17813">add <code>is_lint_allowed</code> to <code>future_not_send</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17961">extend <code>assert_is_empty</code> to support <code>BinaryHeap</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17920">extend <code>unnecessary_to_owned</code> to cover <code>vec.contains(&amp;str.to_string())</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17964">fix <code>collapsible_match</code> suggestion producing non-exhaustive match</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17655">fix false positives on <code>duplicated_attributes</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17849">improve <code>future_not_send</code> for next-solver</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17749">rename <code>large_stack_frames</code> and move it to suspicious</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-analyzer">Rust-Analyzer</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23640">disallow ZSTs in <code>ThinMap</code></a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23478">complete trait <code>dyn</code> prefix in type location</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23620">offer on wildcard pattern for <code>destructure_struct_binding</code></a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23637">add macOS, iOS, Android and musl to cfg completion</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23585">add support for final associated functions</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23631">do not complete dyn Trait in sized location</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23579">do not suggest unreachable path of <code>struct</code> lit</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23636">don't complete transparent after <code>repr(align(...))</code> or <code>repr(packed)</code></a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23583">emit E0158 and E0532 for invalid value items in path patterns</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23606">emit assoc item bound only with generics on builtin derive</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23610">ensure r-a matches rustc coercion logic</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23554">fix where clause position for assoc-type</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23615">i28 should be i128 in completion</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23619">ide-diagnostics: emit error E0220 for unresolved associated types</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23598">match rustc-unicode locations in the rustc problem matcher</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23616">nested cast before <code>&lt;</code> add parens for <code>apply_demorgan</code></a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23592">offer gen doc example on re-exported item</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23608">out-of-bounds crash due to copypasta</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23543">panic on <code>for&lt;'a&gt;</code> on types using <code>#[derive()]</code></a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23600">implement hiding implicit drop hints for types without drop glue</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23591">perf: micro-optimizations for lang items</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage">Rust Compiler Performance Triage</a></h5>
<p>A quiet week performance-wise. The only notable change was a major regression in <a href="https://github.com/rust-lang/rust/pull/165335">#165335</a>, which might get reverted.</p>
<p>Triage done by <strong>@Kobzol</strong>.
Revision range: <a href="https://perf.rust-lang.org/?start=4c46afa63688fb473618f9b3553d70b0c15a88eb&amp;end=54d0b7edad511e84181ad50ec8413ef10f93b367&amp;absolute=false&amp;stat=instructions%3Au">4c46afa6..54d0b7ed</a></p>
<p><strong>Summary</strong>:</p>
<table>
<thead>
<tr>
<th style="text-align: center;">(instructions:u)</th>
<th style="text-align: center;">mean</th>
<th style="text-align: center;">range</th>
<th style="text-align: center;">count</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: center;">Regressions ❌ <br/> (primary)</td>
<td style="text-align: center;">1.0%</td>
<td style="text-align: center;">[0.2%, 3.7%]</td>
<td style="text-align: center;">163</td>
</tr>
<tr>
<td style="text-align: center;">Regressions ❌ <br/> (secondary)</td>
<td style="text-align: center;">1.2%</td>
<td style="text-align: center;">[0.0%, 4.6%]</td>
<td style="text-align: center;">159</td>
</tr>
<tr>
<td style="text-align: center;">Improvements ✅ <br/> (primary)</td>
<td style="text-align: center;">-2.2%</td>
<td style="text-align: center;">[-3.9%, -0.3%]</td>
<td style="text-align: center;">8</td>
</tr>
<tr>
<td style="text-align: center;">Improvements ✅ <br/> (secondary)</td>
<td style="text-align: center;">-0.7%</td>
<td style="text-align: center;">[-1.6%, -0.2%]</td>
<td style="text-align: center;">10</td>
</tr>
<tr>
<td style="text-align: center;">All ❌✅ (primary)</td>
<td style="text-align: center;">0.8%</td>
<td style="text-align: center;">[-3.9%, 3.7%]</td>
<td style="text-align: center;">171</td>
</tr>
</tbody>
</table>
<p>6 Regressions, 5 Improvements, 3 Mixed; 6 of them in rollups
189 artifact comparisons made in total</p>
<p><a href="https://github.com/rust-lang/rustc-perf/blob/119d90a1c7fe399e1ef8cd27f257c5f6dca6f29f/triage/2026/2026-11-08.md">Full report here</a>.</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#approved-rfcs"/><a href="https://github.com/rust-lang/rfcs/commits/main">Approved RFCs</a></h5>
<p>Changes to Rust follow the Rust <a href="https://github.com/rust-lang/rfcs#rust-rfcs">RFC (request for comments) process</a>. These
are the RFCs that were approved for implementation this week:</p>
<ul>
<li><a href="https://github.com/rust-lang/rfcs/pull/3527">RFC: Associated const underscore</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#final-comment-period">Final Comment Period</a></h5>
<p>Every week, <a href="https://www.rust-lang.org/team.html">the team</a> announces the 'final comment period' for RFCs and key PRs
which are reaching a decision. Express your opinions now.</p>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#tracking-issues-prs">Tracking Issues &amp; PRs</a></h6>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust_1"/><a href="https://github.com/rust-lang/rust/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Rust</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/165289">lexer: Update to Unicode 18</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163315">s390x: replace -Ctarget-feature=+backchain with -Cforce-frame-pointers</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163696">Stabilize <code>int_from_ascii</code></a></li>
</ul>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-rfcs"/><a href="https://github.com/rust-lang/rfcs/issues?q=state%3Aopen%20label%3Afinal-comment-period%20state%3Aopen">Rust RFCs</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/rfcs/pull/4015">RFC for limited crates.io self-service version deletion</a></li>
<li>[disposition: close] <a href="https://github.com/rust-lang/rfcs/pull/4021">Deprecate <code>std::env::{vars, args}</code></a></li>
</ul>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cargo_1"/><a href="https://github.com/rust-lang/cargo/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Cargo</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/cargo/pull/17518">perf(compile)!: Switch dev profile to debug=lines-and-tables-only</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17556">fix(trim-paths): sanitize absolute source paths in fingerprint</a></li>
</ul>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#leadership-council"/><a href="https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period%20state%3Aopen">Leadership Council</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/leadership-council/issues/350">T-mods 2026 budget request</a></li>
</ul>
<p><em>No Items entered Final Comment Period this week for
<a href="https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20label%3Afinal-comment-period%20state%3Aopen">Compiler Team</a>,
<a href="https://github.com/rust-lang/lang-team/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Language Team</a>,
<a href="https://github.com/rust-lang/reference/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Language Reference</a> or
<a href="https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Unsafe Code Guidelines</a>.</em>
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#new-and-updated-rfcs"/><a href="https://github.com/rust-lang/rfcs/pulls">New and Updated RFCs</a></h5>
<ul>
<li><em>No New or Updated RFCs were created this week.</em></li>
</ul>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#upcoming-events">Upcoming Events</a></h4>
<p>Rusty Events between 2026-11-11 - 2026-12-09 🦀</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#virtual">Virtual</a></h5>
<ul>
<li>2026-11-12 | Virtual (Nürnberg, DE) | <a href="https://www.meetup.com/rust-noris">Rust Nuremberg</a><ul>
<li><a href="https://www.meetup.com/rust-noris/events/315619619/"><strong>Rust Nürnberg online</strong></a></li>
</ul>
</li>
<li>2026-11-15 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/316563020/"><strong>Rust Deep Learning: Third Sunday</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/2qfai4a8"><strong>Miscompilation in Rust 1.97</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/315719313/"><strong>Lunch &amp; Learn: The Harness Wore a Trenchcoat - Building a Rust MCP Server</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual (Washington, DC, US) | <a href="https://www.meetup.com/rustdc">Rust DC</a><ul>
<li><a href="https://www.meetup.com/rustdc/events/317182776/"><strong>Mid-month Rustful</strong></a></li>
</ul>
</li>
<li>2026-11-18 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210234/"><strong>Writing a firmware for Xteink ereader in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-19 | Virtual (Berlin, DE) | <a href="https://www.meetup.com/rust-berlin">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/316907781/"><strong>Rust Hack and Learn</strong></a></li>
</ul>
</li>
<li>2026-11-24 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/310254769/"><strong>Fourth Tuesday Rust Bookclub</strong></a></li>
</ul>
</li>
<li>2026-11-26 | Virtual | <a href="https://rust.bettercode.eu/">betterCode() Rust</a><ul>
<li><a href="https://rust.bettercode.eu/"><strong>betterCode() Rust 2026</strong></a></li>
</ul>
</li>
<li>2026-12-01 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/omlooqv8"><strong>Cursed Rust</strong></a></li>
</ul>
</li>
<li>2026-12-01 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/316993134/"><strong>Christmas Coding Challenge - Kick Off!</strong></a></li>
</ul>
</li>
<li>2026-12-02 | Virtual (Indianapolis, IN, US) | <a href="https://www.meetup.com/indyrs">Indy Rust</a><ul>
<li><a href="https://www.meetup.com/indyrs/events/wqzhftyjcqbdb/"><strong>Indy.rs - with Social Distancing</strong></a></li>
</ul>
</li>
<li>2026-12-03 | Virtual (Berlin, DE) | <a href="https://www.meetup.com/rust-berlin">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/316907782/"><strong>Rust Hack and Learn</strong></a></li>
</ul>
</li>
<li>2026-12-04 | Hybrid (Moscow, RU) | <a href="https://rustcon.ru/">RustCon RU</a><ul>
<li><a href="https://rustcon.ru/"><strong>RustCon 2026</strong></a></li>
</ul>
</li>
<li>2026-12-06 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/316331278/"><strong>Rust Deep Learning: First Sunday</strong></a></li>
</ul>
</li>
<li>2026-12-08 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/310254767/"><strong>Second Tuesday</strong></a></li>
</ul>
</li>
<li>2026-12-08 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/316993086/"><strong>👋 Community Catch Up</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#asia">Asia</a></h5>
<ul>
<li>2026-11-14 | Bengaluru, IN | <a href="https://hasgeek.com/rustbangalore/">Rust Bangalore</a><ul>
<li><a href="https://hasgeek.com/rustbangalore/november-2026-rustacean-meetup/"><strong>November 2026 Rustacean Meetup</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#europe">Europe</a></h5>
<ul>
<li>2026-11-12 | Frankfurt, DE | <a href="https://www.meetup.com/rust-rhein-main">Rust Rhein-Main</a><ul>
<li><a href="https://www.meetup.com/rust-rhein-main/events/317175844/"><strong>Debugging in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Geneva, CH | <a href="https://www.posttenebraslab.ch/wiki/events/monthly_meeting/rust_meetup">Rust Geneva</a><ul>
<li><a href="https://www.posttenebraslab.ch/wiki/events/monthly_meeting/rust_meetup"><strong>Rust Meetup Geneva</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Milano, MI, IT | <a href="https://www.meetup.com/rust-language-milano/events/">Rust Language Milan</a><ul>
<li><a href="https://www.meetup.com/rust-language-milan/events/317094800/"><strong>From Curiosity to Capability: Build Your Own Device Swarm</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Leipzig, DE | <a href="https://www.meetup.com/rust-modern-systems-programming-in-leipzig">Rust - Modern Systems Programming in Leipzig</a><ul>
<li><a href="https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/313816501/"><strong>Everlock: Everything Is Git, Protocols Are Just Adapters</strong></a></li>
</ul>
</li>
<li>2026-11-19 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus">Rust Aarhus</a><ul>
<li><a href="https://www.meetup.com/rust-aarhus/events/316938696/"><strong>Talk Night at EIVA</strong></a></li>
</ul>
</li>
<li>2026-11-19 | Bergen, NO | <a href="https://www.meetup.com/bergen-rust-new-technology/events/">Rust Bergen</a><ul>
<li><a href="https://www.meetup.com/de-de/bergen-rust-new-technology/events/317045463/"><strong>Rust: FFI with C++, and Intro to Async</strong></a></li>
</ul>
</li>
<li>2026-11-20 - 2026-11-21 | Augsburg, DE | <a href="https://rust-augsburg.github.io/meetup">Rust Meetup Augsburg</a><ul>
<li><a href="https://my.tuxedocomputers.com/event/embedded-rust-mit-embassy-workshop-und-projekttag-28/register"><strong>Embedded Rust mit Embassy - Workshop und Projekttag</strong></a></li>
</ul>
</li>
<li>2026-11-24 | Basel, CH | <a href="https://www.meetup.com/rust-basel">Rust Basel</a><ul>
<li><a href="https://www.meetup.com/rust-basel/events/317258865/"><strong>Rust Meetup #17 @ ERNI</strong></a></li>
</ul>
</li>
<li>2026-11-25 | Amsterdam, NL | <a href="https://www.meetup.com/rust-amsterdam-group">Rust Developers Amsterdam Group</a><ul>
<li><a href="https://www.meetup.com/rust-amsterdam-group/events/317381204/"><strong>Rust Meetup @ Reclamefolder</strong></a></li>
</ul>
</li>
<li>2026-11-26 | Copenhagen, DK | <a href="https://www.meetup.com/copenhagen-rust-community">Copenhagen Rust Community</a><ul>
<li><a href="https://www.meetup.com/copenhagen-rust-community/events/317181792/"><strong>Rust meetup #73 sponsored by Adapt!</strong></a></li>
</ul>
</li>
<li>2026-11-26 | London, UK | <a href="https://www.meetup.com/rust-london-user-group">Rust London User Group</a><ul>
<li><a href="https://www.meetup.com/rust-london-user-group/events/317253958/"><strong>Rust London x Zed</strong></a></li>
</ul>
</li>
<li>2026-11-26 | Manchester, UK | <a href="https://www.meetup.com/rust-manchester">Rust Manchester</a><ul>
<li><a href="https://www.meetup.com/rust-manchester/events/317222338/"><strong>Rust Manchester November Code Night</strong></a></li>
</ul>
</li>
<li>2026-11-26 | Stockholm, SE | <a href="https://www.meetup.com/stockholm-rust">Stockholm Rust</a><ul>
<li><a href="https://www.meetup.com/stockholm-rust/events/317161063/"><strong>Rust Meetup @Lovable</strong></a></li>
</ul>
</li>
<li>2026-12-01 | Paris, FR | <a href="https://www.meetup.com/rust-paris">Rust Paris</a><ul>
<li><a href="https://www.meetup.com/rust-paris/events/316865676/"><strong>Rust meetup #90</strong></a></li>
</ul>
</li>
<li>2026-12-02 | Frankfurt, DE | <a href="https://www.meetup.com/rust-rhein-main">Rust Rhein-Main</a><ul>
<li><a href="https://www.meetup.com/rust-rhein-main/events/317186779/"><strong>From Curiosity to Capability: Build Your Own Device Swarm</strong></a></li>
</ul>
</li>
<li>2026-12-04 | Hybrid (Moscow, RU) | <a href="https://rustcon.ru/">RustCon RU</a><ul>
<li><a href="https://rustcon.ru/"><strong>RustCon 2026</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#north-america">North America</a></h5>
<ul>
<li>2026-11-12 | Lehi, UT, US | <a href="https://www.meetup.com/utah-rust">Utah Rust</a><ul>
<li><a href="https://www.meetup.com/utah-rust/events/317178211/"><strong>Rust Game Jam</strong></a></li>
</ul>
</li>
<li>2026-11-12 | San Diego, CA, US | <a href="https://www.meetup.com/san-diego-rust">San Diego Rust</a><ul>
<li><a href="https://www.meetup.com/san-diego-rust/events/316886787/"><strong>San Diego Rust November Meetup - Back in person!</strong></a></li>
</ul>
</li>
<li>2026-11-14 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924331/"><strong>MIT Rust Lunch, Nov 14</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Los Angeles, CA, US | <a href="https://www.meetup.com/rust-los-angeles">Rust Los Angeles</a><ul>
<li><a href="https://www.meetup.com/rust-los-angeles/events/316859673/"><strong>Rust LA November w/ Hadrian!</strong></a></li>
</ul>
</li>
<li>2026-11-17 | San Francisco, CA, US | <a href="https://www.meetup.com/san-francisco-rust-study-group">San Francisco Rust Study Group</a><ul>
<li><a href="https://www.meetup.com/san-francisco-rust-study-group/events/315783989/"><strong>Rust Hacking in Person</strong></a></li>
</ul>
</li>
<li>2026-11-18 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210234/"><strong>Writing a firmware for Xteink ereader in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-18 | San Francisco, CA, US) | <a href="https://luma.com/bayarearust">Bay Area Rust</a><ul>
<li><a href="https://luma.com/v0mxbgs8"><strong>Bay Area Rust - Social Night</strong></a></li>
</ul>
</li>
<li>2026-11-21 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924366/"><strong>Winter Hill Rust Lunch, Nov 21</strong></a></li>
</ul>
</li>
<li>2026-11-28 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924412/"><strong>South Station Rust Lunch, Nov 28</strong></a></li>
</ul>
</li>
<li>2026-12-04 | New York, NY, US | <a href="https://www.meetup.com/rust-nyc">Rust NYC</a><ul>
<li><a href="https://www.meetup.com/rust-nyc/events/317259308/"><strong>Rust NYC: The UnConf 2026.</strong></a></li>
</ul>
</li>
<li>2026-12-04 | New York, NY, US | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/317383331/"><strong>👋Women in Rust x Rust NYC UnConf 2026</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#oceania">Oceania</a></h5>
<ul>
<li>2026-11-12 | Brisbane City, AU | <a href="https://www.meetup.com/rust-brisbane">Rust Brisbane</a><ul>
<li><a href="https://www.meetup.com/rust-brisbane/events/317296037/"><strong>Rust Brisbane • November 2026</strong></a></li>
</ul>
</li>
<li>2026-11-24 | Barton, AU | <a href="https://www.meetup.com/rust-canberra">Canberra Rust User Group</a><ul>
<li><a href="https://www.meetup.com/rust-canberra/events/316907340/"><strong>November Meetup</strong></a></li>
</ul>
</li>
</ul>
<p>If you are running a Rust event please add it to the <a href="https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com">calendar</a> to get
it mentioned here. Please remember to add a link to the event too.
Email the <a href="mailto:community-team@rust-lang.org">Rust Community Team</a> for access.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#jobs">Jobs</a></h4>
<p>Please see the latest <a href="https://www.reddit.com/r/rust/comments/1wzctie/official_rrust_whos_hiring_thread_for_jobseekers/">Who's Hiring thread on r/rust</a></p>
<h3><a class="toclink" href="https://this-week-in-rust.org/atom.xml#quote-of-the-week">Quote of the Week</a></h3>
<blockquote>
<p>No, actually it is harder. Much harder. Your brain normally runs an error-correction pass on every word you read before that word reaches your conscious attention. This is why it's so easy to miss typos, but the correction doesn't just hide typos from you, it can replace entire phrases with what "ought" to be there. It takes continuous concentration to suppress this effect.</p>
<p>[…]</p>
<p>(Curly brace placement is of course also subject to the error filter, but curly braces go with large changes in indentation, and that's usually a big enough visual flag to get past the filter. In fact that's why Rust requires all blocks to be braced -- the experience with C was that people would think indented statements were braced when they weren't.)</p>
</blockquote>
<p>– <a href="https://internals.rust-lang.org/t/yet-another-performance-footgun-in-rust-multithreading-lock-edition/24726/68">Zack Weinberg on rust-internals</a></p>
<p>Thanks to <a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328/1841">Michael Howell</a> for the suggestion!</p>
<p><a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328">Please submit quotes and vote for next week!</a></p>
<p>This Week in Rust is edited by:</p>
<ul>
<li><a href="https://github.com/nellshamrell">nellshamrell</a></li>
<li><a href="https://github.com/llogiq">llogiq</a></li>
<li><a href="https://github.com/ericseppanen">ericseppanen</a></li>
<li><a href="https://github.com/extrawurst">extrawurst</a></li>
<li><a href="https://github.com/U007D">U007D</a></li>
<li><a href="https://github.com/mariannegoldin">mariannegoldin</a></li>
<li><a href="https://github.com/bdillo">bdillo</a></li>
<li><a href="https://github.com/opeolluwa">opeolluwa</a></li>
<li><a href="https://github.com/bnchi">bnchi</a></li>
<li><a href="https://github.com/KannanPalani57">KannanPalani57</a></li>
<li><a href="https://github.com/tzilist">tzilist</a></li>
</ul>
<p><em>Email list hosting is sponsored by <a href="https://foundation.rust-lang.org/">The Rust Foundation</a></em></p>
<p><small><a href="https://www.reddit.com/r/rust/comments/1xuwet4/this_week_in_rust_677/">Discuss on r/rust</a></small></p></div>
    </content>
    <updated>2026-11-11T05:00:00Z</updated>
    <published>2026-11-11T05:00:00Z</published>
    <category term="This Week in Rust"/>
    <author>
      <name>TWiR Contributors</name>
    </author>
    <source>
      <id>https://this-week-in-rust.org/</id>
      <link href="https://this-week-in-rust.org/" rel="alternate" type="text/html"/>
      <link href="https://this-week-in-rust.org/atom.xml" rel="self" type="application/atom+xml"/>
      <title>This Week in Rust</title>
      <updated>2026-11-11T05:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/</id>
    <link href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/" rel="alternate" title="Google Summer of Code 2026 results" type="text/html"/>
    <title xml:lang="en">Google Summer of Code 2026 results</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><p>The Rust Project <a href="https://blog.rust-lang.org/2026/04/30/gsoc-2026-selected-projects/" rel="external">participated</a> in <a href="https://summerofcode.withgoogle.com" rel="external">Google Summer of Code (GSoC)</a> for the third time this year. This time we had 13 projects, and our dear contributors have been working very hard on them for several months. As usual, the projects had various durations, so while some of them have ended in August, the last one has only finished in November, so we have been waiting until we have all the results before publishing this blog post.</p>
<p><strong>We are very happy to announce that all 13 projects were successful and passed their final evaluation!</strong> We consider it to be a testament to the diligence of our contributors, and the helpfulness of our mentors, that we are able to keep a very high rate<sup class="footnote-reference" id="fr-success-rate-1"><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#fn-success-rate">[1]</a></sup> of successful GSoC projects several years in a row.</p>
<p>At the start of summer, we had a video call with our contributors, so that we could all get to know each other a bit, and learn about their projects. Over the following few months, we continuously communicated with the contributors, provided guidance and answered their questions and reviewed their pull requests. And most importantly, we learned many new things together! It was an overall great experience. We are grateful for all Rust contributions done by our GSoC participants and for the time we spent working together, and we hope that we will continue seeing at least some of them around in the future.</p>
<p><strong>We would like to thank all our Rust GSoC 2026 contributors. You did a great job!</strong></p>
<p>Even though this year we had fewer projects than in 2025, mostly due to limited mentoring capacity, Google Summer of Code 2026 was again a success for the Rust Project. We think that GSoC is a great way of introducing new contributors to our community, and we are looking forward to participating in GSoC (and other mentorship programs, such as <a href="https://blog.rust-lang.org/2026/05/04/outreachy-2026-may/" rel="external">Outreachy</a>) again in the near future. If you are interested in becoming a (GSoC) contributor, check out our <a href="https://github.com/rust-lang/google-summer-of-code" rel="external">GSoC project idea list</a> and our <a href="https://forge.rust-lang.org/how-to-start-contributing.html" rel="external">guide for new contributors</a>.</p>
<p>Below you can find a brief summary of our GSoC 2026 projects. You can find more information about the original goals of the projects <a href="https://github.com/rust-lang/google-summer-of-code/blob/main/gsoc/runs/2026.md" rel="external">here</a>. For easier navigation, here is an index of the project descriptions in alphabetical order:</p>
<ul>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#a-frontend-for-safe-gpu-offloading-in-rust">A Frontend for Safe GPU Offloading in Rust</a> by <a href="https://github.com/sa4dus" rel="external">Marcelo Domínguez</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#adding-webassembly-linking-support-to-wild">Adding WebAssembly Linking Support to Wild</a> by <a href="https://github.com/lapla-cogito" rel="external">Kei Akiyama</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#bringing-autodiff-and-offload-into-rust-ci">Bringing autodiff and offload into Rust CI</a> by <a href="https://github.com/sgasho" rel="external">Shota Sugano</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#debugger-for-miri">Debugger for Miri</a> by <a href="https://github.com/moabo3li" rel="external">Mohamed Ali</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#implementing-impl-and-mut-restrictions">Implementing impl and mut restrictions</a> by <a href="https://github.com/CoCo-Japan-pan" rel="external">Ryosuke Yamano</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#improving-ergonomics-and-safety-of-serialport-rs">Improving Ergonomics and Safety of serialport-rs</a> by <a href="https://github.com/NONnonHere" rel="external">Tanmay</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#libc-transition-differing-bit-width-time-and-offset-variants-and-deprecate-bug-prone-constants">libc: transition differing bit-width time and offset variants and deprecate bug-prone constants</a> by <a href="https://github.com/dybucc" rel="external">Adam Martinez</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#link-linux-kernel-and-its-modules-with-wild">Link Linux kernel and its Modules with Wild</a> by <a href="https://github.com/vishruth-thimmaiah" rel="external">Vishruth Thimmaiah</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#migrating-rust-analyzer-assists-to-syntaxeditor">Migrating rust-analyzer assists to SyntaxEditor</a> by <a href="https://github.com/bit-aloo" rel="external">bit-aloo</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#port-std-arch-test-suite-to-rust-lang-rust">Port std::arch test suite to rust-lang/rust</a> by <a href="https://github.com/xonx4l" rel="external">Sumit Kumar</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#reorganizing-tests-ui-issues">Reorganizing tests/ui/issues</a> by <a href="https://github.com/zedddie" rel="external">zedddie</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#utilize-debugger-apis-to-improve-debug-info-test-accuracy-and-error-reporting">Utilize debugger APIs to improve debug info test accuracy and error reporting</a> by <a href="https://github.com/Walnut356" rel="external">Anthony Bolden</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#xdg-path-support-for-rustup">XDG path support for rustup</a> by <a href="https://github.com/Cloud0310" rel="external">Guicheng Liu</a></li>
</ul>
<p>And now strap in, as there is a ton of great content to read about here!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#a-frontend-for-safe-gpu-offloading-in-rust"/>
A Frontend for Safe GPU Offloading in Rust</h4>
<ul>
<li>Contributor: <a href="https://github.com/sa4dus" rel="external">Marcelo Domínguez</a></li>
<li>Mentor: <a href="https://github.com/ZuseZ4" rel="external">Manuel Drehwald</a></li>
<li><a href="https://sa4dus.github.io/posts/gsoc2026-final-report/" rel="external">Final report</a></li>
</ul>
<p>Marcelo worked on improving the usability of cross-vendor GPU programs in Rust using the <code>std::offload</code> module. At the start of the project, the offload prototype was only a proof of concept. It assumed that the offloaded code was bug-free, and it required users to write a lot of boilerplate code. Marcelo resolved both issues over the summer.</p>
<p>First, he implemented proper type checking. Marcelo extended the compiler to verify that the arguments passed to any offload call are of the correct type, as expected by the GPU kernel. Kernel launches are thus now safe.</p>
<p>After that, he added support for generic kernels. The compiler now collects all generic instantiations launched from the CPU side, and loads that info later when compiling GPU kernels to make sure we instantiate them as needed. Marcelo also added support to select which GPU to use, which is helpful for laptops with both an integrated and a dedicated GPU, as well as for servers with multiple GPUs. He also added two macros that removed the need for any boilerplate when writing and launching GPU kernels.</p>
<p>The hardest part of this project by far was dealing with references. Due to Rust semantics, we cannot just map types containing mutable references to GPUs and then process them using multiple threads. Previous Rust GPU projects used raw pointers as a workaround, but we obviously wanted to avoid those. Marcelo managed to implement a sound abstraction so that users can now safely declare how their kernels will access mutable arguments.</p>
<p>As a cherry on top, Marcelo also ported the <a href="https://github.com/llnl/rajaperf" rel="external">RajaPerf</a> performance suite from C++ to Rust and used it to benchmark his pull requests. His safe Rust version matches the performance of the original C++ code, and is now described in a <a href="https://arxiv.org/abs/2608.13759" rel="external">GPU offload paper</a> that he is working on together with his mentor, Manuel. This was Marcelo's <a href="https://blog.rust-lang.org/2025/11/18/gsoc-2025-results/#abi-layout-handling-for-the-automatic-differentiation-feature" rel="external">second</a> Rust GSoC project, and same as last year, we are very happy with the results. Great job!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#adding-webassembly-linking-support-to-wild"/>
Adding WebAssembly Linking Support to Wild</h4>
<ul>
<li>Contributor: <a href="https://github.com/lapla-cogito" rel="external">Kei Akiyama</a></li>
<li>Mentor: <a href="https://github.com/davidlattimore" rel="external">David Lattimore</a></li>
<li><a href="https://lapla.dev/posts/gsoc_final2" rel="external">Final report</a></li>
</ul>
<p>The goal of this project was simple on paper: teach the <a href="https://github.com/davidlattimore/wild" rel="external">Wild</a> linker to link WebAssembly (Wasm) programs. However, adding support for a new linker target is of course far from simple. Luckily, Kei already had a lot of experience with Wild, as this was his second <a href="https://blog.rust-lang.org/2025/11/18/gsoc-2025-results/#improve-wild-linker-test-suites" rel="external">GSoC project</a> working on the Wild linker.</p>
<p>And as expected, Kei did a great job! Prior to GSoC 2026, Wild had no Wasm output support. Now, the Wasm support is sufficiently good that Wild can link a range of complex programs to Wasm. For example, it is able to link itself, SQLite, ripgrep, CPython and even the SpiderMonkey JavaScript engine.</p>
<p>And the linking performance is excellent! When compared to <code>wasm-ld</code>, the de-facto standard Wasm linker, which is based on the LLD linker, Wild is 2-15x faster, and uses 2-5x less memory. You can find more benchmarks in his <a href="https://lapla.dev/posts/gsoc_final2#link-performance" rel="external">final report</a>, where he also explains that achieving this performance took quite some work, because Wild's ELF linking performance did not immediately translate to being fast when linking Wasm.</p>
<p>Even after this GSoC project ended, Kei has continued improving Wild's Wasm support, as well as contributing to other parts of Wild. Thank you for bringing fast linking to a new set of use-cases, Kei! You are a valued member of the Wild team.</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#bringing-autodiff-and-offload-into-rust-ci"/>
Bringing autodiff and offload into Rust CI</h4>
<ul>
<li>Contributor: <a href="https://github.com/sgasho" rel="external">Shota Sugano</a></li>
<li>Mentor: <a href="https://github.com/ZuseZ4" rel="external">Manuel Drehwald</a></li>
<li><a href="https://sgasho.github.io/posts/gsoc-2026-final-report/" rel="external">Final report</a></li>
</ul>
<p>The goal of this project was to build the experimental <code>std::autodiff</code> module, which implements automatic differentiation of Rust code, and the <code>std::offload</code> module, which allows offloading Rust code to GPUs, in the CI of the Rust compiler.</p>
<p>Shota has already been contributing to this area in the months leading up to this year's GSoC, so he had no issues getting started. After valiantly fighting with our CI, he made both modules available in the official <code>nightly</code> compiler channel. Rust users can thus now simply install them with a single rustup command, rather than having to compile rustc from source! This is a huge benefit for gathering feedback on these features in the wild, as it makes it much easier to experiment with them.</p>
<p>Beyond making these projects available via rustup, he also worked on making it simpler to build projects that use <code>std::offload</code>. The original compilation pipeline was derived from Clang's support for GPU offload, so it involved calling clang helper binaries. That is clearly not optimal, so Shota worked on replacing it by directly calling the underlying LLVM APIs from rustc.</p>
<p>The last piece of his project was enabling testing in CI for both offload and autodiff, which already helped prevent multiple regressions. Right now, the GPU offload pipeline only tests the CPU setup side, but his work allowed us to talk to GPU hardware vendors, two of which already agreed to provide the Rust Project with GPU hardware so that in the future we can also run those tests on dedicated GPUs.</p>
<p>Overall, the project was a success. Shota had to show a lot of patience and endurance when working with various CMake quirks and CI challenges. We would like to extend a special thank you for that!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#debugger-for-miri"/>
Debugger for Miri</h4>
<ul>
<li>Contributor: <a href="https://github.com/moabo3li" rel="external">Mohamed Ali</a></li>
<li>Mentor: <a href="https://github.com/oli-obk" rel="external">Oli Scherer</a></li>
<li><a href="https://gist.github.com/moabo3li/10b6ca701cb998ab36781e81ac0f100d" rel="external">Final report</a></li>
</ul>
<p>miri is a tool that can detect undefined behavior (UB) in unsafe Rust code. It used to have a prototype of an interactive debugger called <code>priroda</code>, but it became unmaintained some time ago. The goal of this project was to re-establish <code>priroda</code>, to make it easier to use miri interactively, debug how and why is UB introduced in Rust programs, and also help rustc developers analyse MIR, one of the intermediate representations of Rust programs.</p>
<p>Mohamed successfully reached both main goals of this project. He created a miri interface for the gdb debugger, which allows debugging programs executed by miri. You can set breakpoints, step through individual instructions, analyse MIR local variables and inspect the debugged program's state, with miri acting as a "virtual CPU". So when you encounter your next miri UB report, you can actually debug the program state that caused UB by running <code>priroda</code>! Mohamed also created a command-line interface for <code>priroda</code>, which is used to test it in miri's CI. This will ensure that it keeps working properly and will not bitrot again.</p>
<p>Mohamed also added basic support for the Debugger Adapter Protocol, which allows using <code>priroda</code> together with IDEs such as Visual Studio Code. Currently, connecting priroda to an IDE is a bit involved, so the next step would be to build a plugin for an IDE that would allow showing all the extra state that miri has, which gdb doesn't know how to interpret.</p>
<p>Debugging programs executed by miri is very exciting. Thank you for all your work!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#implementing-impl-and-mut-restrictions"/>
Implementing impl and mut restrictions</h4>
<ul>
<li>Contributor: <a href="https://github.com/CoCo-Japan-pan" rel="external">Ryosuke Yamano</a></li>
<li>Mentors: <a href="https://github.com/jhpratt" rel="external">Jacob Pratt</a>, <a href="https://github.com/Urgau" rel="external">Urgau</a></li>
<li><a href="https://gist.github.com/CoCo-Japan-pan/ced54db688080b94ec777bd750e87b34" rel="external">Final report</a></li>
</ul>
<p>The goal of this project was to implement two new language features that were accepted in <a href="https://rust-lang.github.io/rfcs/3323-restrictions.html" rel="external">RFC 3323</a>:</p>
<ul>
<li>Impl restrictions (<code>impl(crate) trait Foo {}</code>), which allow restricting in which modules you are able to implement a given trait.</li>
<li>Mut restrictions (<code>struct Foo { pub mut(crate) bar: u8 }</code>), which allow restricting in which modules you are able to mutate a given field.</li>
</ul>
<p>Ryosuke had to familiarize himself with the compiler's codebase and do a lot of implementation work to get both features working. This included implementing parsing of the new syntax, recording its metadata in the compiler's Abstract Syntax Tree, implementing resolution of the restricted crate paths, and finally adding checks to enforce both restriction rules. This all amounted to around five thousand lines of Rust code!</p>
<p>Once the new features were implemented and available on nightly, Ryosuke wrote a <a href="https://blog.rust-lang.org/inside-rust/2026/08/10/call-for-testing-impl-and-mut-restrictions/" rel="external">Call for Testing</a> blog post. It had to be very exciting to announce to the world that he implemented two new features from scratch, and people can now play with them on the nightly channel! After the blog post was published, users reported a few issues, which Ryosuke promptly fixed. He also contributed to rustdoc to improve how the impl and mut restrictions are rendered in the generated documentation pages.</p>
<p>Now that the features are available on nightly, feedback is being gathered on them, with the plan being to stabilize them in 2027. If you would like to provide feedback on the impl and mut restrictions, you can do so in <a href="https://github.com/rust-lang/rust/issues/160614" rel="external">this issue</a>.</p>
<p>The goal of this project was clear, and Ryosuke achieved it completely. Awesome work!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#improving-ergonomics-and-safety-of-serialport-rs"/>
Improving Ergonomics and Safety of serialport-rs</h4>
<ul>
<li>Contributor: <a href="https://github.com/NONnonHere" rel="external">Tanmay</a></li>
<li>Mentor: <a href="https://github.com/sirhcel" rel="external">Christian Meusel</a></li>
<li><a href="https://nonnonhere.github.io/posts/gsoc2026-report/" rel="external">Final report</a></li>
</ul>
<p>The goal of this project, which was done in collaboration with the <a href="https://rust-embedded.org" rel="external">Rust Embedded Working Group</a>, was to improve the API ergonomics and type safety of the <a href="https://github.com/serialport/serialport-rs" rel="external">serialport-rs</a> crate.</p>
<p>The serialport project is a bit different from some other projects which participated in this year's Google Summer of Code. It is more on the side of "facility management" than rocket science. Its challenges are taming finicky operating system APIs and making good abstractions, rather than full-blown software engineering.</p>
<p>Tanmay led many fruitful discussions about potential design decisions, and did a lot of field research on how other crates that depend on serialport actually use its API, to figure out how to make the upcoming breaking API changes less disruptive and painful for them.</p>
<p>Tanmay also worked on sanding off some rough edges of the serialport API, such as replacing Boxed trait objects with enums, and making errors explicit in places where the legacy API used to panic. Some of the work still waits for integration. It is targeting the upcoming serialport 5.0 release.</p>
<p>Christian (Tanmay's mentor) found working alongside Tanmay very motivational, and he was able to catch up with a lot of other unrelated work in order to integrate Tanmay's changes. He noted that working with Tanmay was fun and productive, and that it was pure joy to see him grow from his first contribution in the bonding phase to seasoned contributions. Thank you, Tanmay!</p>
<blockquote>
<p>This was my first Google Summer of Code as well. It was challenging, motivating, fun and definitely worth it. I would show up again.</p>
<p>Christian Meusel</p>
</blockquote>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#libc-transition-differing-bit-width-time-and-offset-variants-and-deprecate-bug-prone-constants"/>
libc: transition differing bit-width time and offset variants and deprecate bug-prone constants</h4>
<ul>
<li>Contributor: <a href="https://github.com/dybucc" rel="external">Adam Martinez</a></li>
<li>Mentor: <a href="https://github.com/tgross35" rel="external">Trevor Gross</a></li>
<li><a href="https://dybucc.github.io/gsoc-2026-report/" rel="external">Final report</a></li>
</ul>
<p><a href="https://github.com/rust-lang/libc" rel="external"><code>libc</code></a> is a foundational crate that is used by thousands of other crates across the Rust ecosystem. For the past several years, its maintainers have been attempting to publish a stable 1.0 release of the crate. Because this crate has to support interoperating with C on many compilation targets with weird quirks, this requires an enormous amount of work. We already had a GSoC project for moving <code>libc</code> towards 1.0 <a href="https://blog.rust-lang.org/2025/11/18/gsoc-2025-results/#modernising-the-libc-crate" rel="external">last year</a>, and the goal of Adam's project was to make more progress in that direction.</p>
<p>And we can happily say that progress was indeed made! The original goal of Adam's project was to deprecate a number of constants that were difficult to maintain and cleanup inconsistencies in handling 32-bit/64-bit variants of file and time handling functions<sup class="footnote-reference" id="fr-2038-1"><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#fn-2038">[2]</a></sup>. Adam was able to resolve that in a few weeks, and then he moved on to resolve a number of various issues blocking the <a href="https://github.com/rust-lang/libc/issues/3248" rel="external">1.0 milestone</a>.</p>
<p>Saying that Adam was productive would be… an understatement. We could follow his work in real-time, because he was posting <a href="https://dybucc.github.io/gsoc-2026-report/daily-reports/" rel="external">daily GSoC reports</a> for <em>116 days (!) in a row</em>. The diligence and consistency with which he tackled so many complicated issues was an inspiration to us. In fact, sometimes the <code>libc</code> reviewers were not able to keep up!</p>
<p>You can find all Adam's <code>libc</code> pull requests <a href="https://github.com/rust-lang/libc/pulls?q=is%3Apr+author%3Adybucc" rel="external">here</a>. You might notice that many of them have lots of comments, and even more discussions happened in GitHub issues and on Zulip. In addition to implementing the necessary code, making changes that affect interesting C platforms and architectures also required him to do a ton of research, and a lot of considerations of edge cases and possible backwards compatibility breakages. His work also took him on a whirlwind tour of diverse platforms; Adam's contributions spanned FreeBSD, NetBSD, Android, Hurd, NuttX, AIX, VxWorks, Fuchsia, L4Re and more.</p>
<p>Even though more work will still be required to get <code>libc</code> to 1.0, Adam's contributions made a significant dent in this effort. Thank you very much for all your work!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#link-linux-kernel-and-its-modules-with-wild"/>
Link Linux kernel and its Modules with Wild</h4>
<ul>
<li>Contributor: <a href="https://github.com/vishruth-thimmaiah" rel="external">Vishruth Thimmaiah</a></li>
<li>Mentor: <a href="https://github.com/davidlattimore" rel="external">David Lattimore</a></li>
<li><a href="https://vishthimmaiah.dev/blog/gsoc-26/" rel="external">Final report</a></li>
</ul>
<p>Linker scripts are arcane commands that can be used to instruct a linker to construct the final binary in a custom way. The <a href="https://github.com/davidlattimore/wild" rel="external">Wild</a> linker used to implement only basic linker script functionality, which Vishruth greatly expanded during his GSoC project.</p>
<p>Thanks to that, Wild can now successfully link Linux kernel modules, and it's even close to being able to link the Linux kernel itself! Vishruth's work involved greatly expanding expression evaluation support, location counters, program headers, etc. In addition to adding support for many missing bits of linker script support, Vishruth implemented support for partial linking (-r) as this is needed in order to link Linux kernel modules. You can find all the linker script features that he implemented <a href="https://github.com/wild-linker/wild/blob/main/LINKER_SCRIPT_SUPPORT.md" rel="external">here</a>.</p>
<p>Adding all those peculiar features to Wild required performing many cross-cutting changes to its codebase, which Vishruth managed to do really well. And it was not at the cost of performance! Wild now manages to link Linux kernel modules such as <code>btrfs</code> or <code>amdgpu</code> 2-4x faster than the BFD (GNU ld) or LLD linkers<sup class="footnote-reference" id="fr-mold-1"><a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#fn-mold">[3]</a></sup>. You can find more benchmarks in his <a href="https://vishthimmaiah.dev/blog/gsoc-26#benchmarks" rel="external">final report</a>.</p>
<p>Vishruth has continued to contribute to Wild even after his GSoC project ended and has become a valued contributor to the project. Thank you very much for making Wild better, Vishruth!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#migrating-rust-analyzer-assists-to-syntaxeditor"/>
Migrating rust-analyzer assists to SyntaxEditor</h4>
<ul>
<li>Contributor: <a href="https://github.com/bit-aloo" rel="external">bit-aloo</a></li>
<li>Mentors: <a href="https://github.com/ChayimFriedman2" rel="external">Chayim Refael Friedman</a>, <a href="https://github.com/Veykril" rel="external">Lukas Wirth</a></li>
<li><a href="https://gist.github.com/bit-aloo/b960133f349ab8a63de63bfbc35d3b8e" rel="external">Final report</a></li>
</ul>
<p>rust-analyzer uses <a href="https://github.com/rust-analyzer/rowan" rel="external">rowan</a> for its syntax trees, a library for Concrete Syntax Trees. <code>rowan</code> has served us well over the years, but it has some downsides that cause major performance problems and also smaller convenience issues. In particular, memory fragmentation causes rust-analyzer to consume much more memory than it actually needs (in the order of redundant gigabytes).</p>
<p>We wanted to rewrite <code>rowan</code> to change that. The problem was that many parts in rust-analyzer touch syntax trees, and in particular assists (code actions) of which we have a lot. They also use mutable tree editing, a feature of <code>rowan</code> that can be convenient but was a major obstacle in rewriting it to be more efficient.</p>
<p>During his project, bit-aloo first migrated all rust-analyzer code from mutable tree editing to <code>SyntaxEditor</code>, a new abstraction that was created specifically to avoid mutation. After that, he removed mutable editing from <code>rowan</code> altogether.</p>
<p>The migration process is incremental and <code>rowan</code> is still inefficient in various aspects. However, we believe that the parts which required changes to large amounts of code are behind us, and we can complete the migration with more focused changes. bit-aloo is continuing to work on that even after his GSoC project ended. And he was also accepted as a member of the rust-analyzer team, so congratulations! We would like to thank him for his work, and hope to continue working with him to improve rust-analyzer for everyone.</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#port-std-arch-test-suite-to-rust-lang-rust"/>
Port std::arch test suite to rust-lang/rust</h4>
<ul>
<li>Contributor: <a href="https://github.com/xonx4l" rel="external">Sumit Kumar</a></li>
<li>Mentors: <a href="https://github.com/Kobzol" rel="external">Jakub Beránek</a>, <a href="https://github.com/folkertdev" rel="external">Folkert de Vries</a></li>
<li><a href="https://hackmd.io/@7qtUS4O9Qqadcel1SvxXiQ/BySYQX7vMe" rel="external">Final report</a></li>
</ul>
<p>The <code>std::arch</code> module of the Rust standard library contains various intrinsic functions that provide architecture and vendor-specific functionality. Their implementation lives in the <a href="https://github.com/rust-lang/stdarch" rel="external">stdarch</a> repository, which is included as a <a href="https://blog.rust-lang.org/inside-rust/2026/06/04/how-josh-helps-rust-manage-code-across-multiple-repositories/" rel="external">Josh</a> subtree in the main compiler repo (<code>rust-lang/rust</code>).</p>
<p>When someone changes the intrinsics in the main repo, breakages can silently creep in, because the main repo does not execute all the <code>stdarch</code> tests in its CI. That can cause friction when we synchronize the changes between the two repositories. Ideally, we would run all of <code>stdarch</code>'s tests in the main repo to detect any issues as soon as possible.</p>
<p>And that is where Sumit came in! Over the course of his GSoC project, he examined the (very!) complex ways the intrinsics are tested in <code>stdarch</code>, and started porting them over to the main repo. But this was not a matter of copying over a few lines of YAML. The compiler repo uses its own build system (called <code>bootstrap</code>) and a CI workflow structure that is quite different from the <code>stdarch</code> repository. Sumit thus had to first understand what is each test suite doing, reimplement it as a part of bootstrap and finally integrate it into the compiler's CI workflows.</p>
<p>We run ~90 CI jobs across several hardware architectures, operating systems and <em>OS versions</em>. Getting all that to work while testing <em>vendor-specific</em> intrinsics required a lot of diligent work… and a lot of patience. It took <em>five months</em> for <a href="https://github.com/rust-lang/rust/pull/156674" rel="external">one</a> of the test suites to finally succeed on the main repo's CI, and it required Sumit to completely refactor how the suite worked, for it to be more compatible with bootstrap. As another example, a <a href="https://github.com/rust-lang/rust/pull/156356" rel="external">different</a> test suite that Sumit also got to work required running the tests in an Intel CPU emulator on CI.</p>
<p>Sumit ported most of the <code>stdarch</code> test suites to <code>bootstrap</code>, including intrinsics verification against reference <em>C</em> implementations, checks for automatically generated source code being up-to-date, and various unit tests for individual intrinsics and CPU feature detection logic. There is one <a href="https://github.com/rust-lang/rust/pull/160850" rel="external">remaining</a> test suite to port, but the ported tests are already helping us find issues, which is great.</p>
<p>You can check Sumit's <code>rust-lang</code> PRs <a href="https://github.com/search?q=author%3Axonx4l+org%3Arust-lang&amp;type=pullrequests" rel="external">here</a>; notice that he was also contributing to other parts of Rust in the meantime! Sumit's work will help us make LLVM upgrades and land intrinsics changes more easily. Thank you, Sumit!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#reorganizing-tests-ui-issues"/>
Reorganizing tests/ui/issues</h4>
<ul>
<li>Contributor: <a href="https://github.com/zedddie" rel="external">zedddie</a></li>
<li>Mentors: <a href="https://github.com/Teapot4195" rel="external">Teapot</a>, <a href="https://github.com/Kivooeo" rel="external">Kivooeo</a></li>
<li><a href="https://gist.github.com/zedddie/7170d2280bc9e19da84cd7eb4e3b32e0" rel="external">Final report</a></li>
</ul>
<p>The goal of this project was to get rid of a very scary place in the Rust compiler's test suite: a directory called <code>tests/ui/issues</code>. It contained thousands of test files based on historical Rust issues, dating back all the way to 2012. The problem with those tests was that they were named only with an issue number (e.g. <code>issue-37291</code>). When such a test would break, it was quite difficult to figure out what was it even supposed to test, because there was little context attached to it.</p>
<p>Even though we already had a GSoC project to tackle this problem <a href="https://blog.rust-lang.org/2025/11/18/gsoc-2025-results/#mapping-the-maze-of-rust-s-ui-test-suite-with-established-continuous-integration-practices" rel="external">last year</a>, due to the sheer amount of uncategorized tests, there were still over four hundred tests left in this directory by the time zedddie started working on this project.</p>
<p>For each test in this directory, zedddie had to first understand what was the test doing and dig through its original GitHub issue and any other related issues and pull requests. Then they had to figure out what would be the best location to move the test under, search for any possible duplicates, come up with a descriptive name for the test (that tends to be very difficult!), and finally add a short description to the test that explains the context of why the test was added in the first place. Rinse and repeat, for hundreds of tests.</p>
<p>zedddie rolled up their sleeves, and categorized over 300 tests in 30 pull requests. Together with other contributors helping out over this summer, zedddie was finally able to remove the last batch of <a href="https://github.com/rust-lang/rust/pull/160176" rel="external">uncategorized tests</a> at the start of August. As zedddie said in their <a href="https://gist.github.com/zedddie/7170d2280bc9e19da84cd7eb4e3b32e0" rel="external">final report</a>: "What is left to do: nothing, tests/ui/issues is gone".</p>
<p>While this work might sound a bit bland, its positive effect on the maintainability of our test suite, and improving the lives of Rust compiler contributors, is considerable. It is also apparently a great way to learn about cool niche edge cases of Rust that most Rust developers might not know about! After migrating the remaining uncategorized UI tests, zedddie continued contributing to the next trait solver and const generics. Thank you very much for helping us finally get rid of <code>tests/ui/issues</code>, zedddie!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#utilize-debugger-apis-to-improve-debug-info-test-accuracy-and-error-reporting"/>
Utilize debugger APIs to improve debug info test accuracy and error reporting</h4>
<ul>
<li>Contributor: <a href="https://github.com/Walnut356" rel="external">Anthony Bolden</a></li>
<li>Mentors: <a href="https://github.com/Kobzol" rel="external">Jakub Beránek</a>, <a href="https://github.com/jieyouxu" rel="external">Jieyou Xu</a></li>
<li><a href="https://walnut356.github.io/posts/gsoc-2026-final-report/" rel="external">Final report</a></li>
</ul>
<p>The Rust debugging experience leaves a <a href="https://blog.rust-lang.org/2026/09/07/rust-debugging-survey-2026-results/" rel="external">lot to be desired</a>. One reason why we struggled to improve it is that many of our debuginfo test suites did not even run in CI for the past few years, as they were difficult to maintain. When something changed in the type visualizers, the implementation details of a standard library type or in debugger internals, someone had to go through tens of tests and manually update them. This was not sustainable, so the test suite rotted.</p>
<p>Luckily for us, Anthony took that affront personally. Even before his GSoC project, he spent considerable effort on improving the quality of debug visualizers of various Rust standard library types, and gained an impressive amount of knowledge about debuggers.</p>
<p>During his GSoC project, he completely overhauled how our debuginfo test infrastructure works, both for <a href="https://github.com/rust-lang/rust/pull/158298" rel="external">LLDB</a> and <a href="https://github.com/rust-lang/rust/pull/160377" rel="external">GDB</a>. Thanks to his improvements, we can now easily "rebless" the reference output when something changes, which makes it much easier to keep our test suite up-to-date. The new tests also record much more information about the internal state of the debugger recorded during the test, which helps with diagnosing issues that cause type visualizers to stop working.</p>
<p>In addition to redesigning the test suite, Anthony also actually managed to re-enable the LLDB tests on both Windows and Linux in our CI again (after several years of being skipped there!). This will allow us to avoid debuginfo regressions and make it easier to improve the Rust debugging experience. Oh, and it goes without saying that while doing all that, he also made numerous improvements to Rust type visualizers. You can find his PRs <a href="https://github.com/rust-lang/rust/pulls?q=is%3Apr+state%3Amerged+author%3Awalnut356" rel="external">here</a>.</p>
<p>Anthony's amazing contributions and his deep expertise in debuggers led to him being invited to the Rust <a href="https://rust-lang.org/governance/teams/compiler/#team-compiler" rel="external">Compiler team</a>, which was much deserved. What else can we add, other than: thank you for your awesome work!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#xdg-path-support-for-rustup"/>
XDG path support for rustup</h4>
<ul>
<li>Contributor: <a href="https://github.com/Cloud0310" rel="external">Guicheng Liu</a></li>
<li>Mentor: <a href="https://github.com/rami3l" rel="external">rami3l</a></li>
<li><a href="https://cloud0310.github.io/posts/2026-GSoC-project-report.html" rel="external">Final report</a></li>
</ul>
<p>The support for platform-specific directories (platformdirs) has been a long-standing feature request for rustup, to have more fine-grained filesystem directory choices. This project investigated how that issue could be resolved.</p>
<p>The real complexity of this feature request lies within a decade worth of different assumptions that previous iterations of rustup and cargo have made: it turns out that quite a lot of them are no longer true if we were to implement platformdirs support truly faithfully.</p>
<p>Guicheng first worked on cleaning up the interactions between <code>rustup self uninstall</code> and <code>$CARGO_HOME/bin</code> as a warmup. This issue itself is a very good demonstration of all that compatibility baggage: somehow <code>$CARGO_HOME/bin</code> has become the default binary directory for all things Rust, so rustup ended up installing itself and all its proxies into it. As a result, it has been super annoying to many that everything in <code>$CARGO_HOME</code> is gone with <code>rustup self uninstall</code>.</p>
<p>After that, he started the actual implementation of platformdirs support in rustup. This was no easy task! Not because the code itself was hard to write, but because it takes a lot of effort to figure out what should be the desired behavior in the first place. Also, in order to determine the appropriate platformdirs semantics, some prior research is often required to see how things became what they are today, so the decoupling of different concerns could proceed, and migration paths could be designed accordingly. It was in this sense that this is different from a typical GSoC project, and luckily thanks to the effort he has put into this project, we have not only come up with the final patch, but also discovered and fixed some tiny preexisting issues with this long-untouched aspect of the rustup codebase along the way.</p>
<p>Thank you for digging into this complex topic, Guicheng!</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#conclusion"/>
Conclusion</h3>
<p>We would like to thank all contributors who have participated in Google Summer of Code 2026 with us! Your contributions helped make Rust better, and introduced you as new members of our community, which is a reason to celebrate. We are looking forward to participating in GSoC again next year!</p>
<p>We would also like to thank Google for organizing the Google Summer of Code program and for allowing us to host a large number of projects every year. And last, but not least, we would like to thank all the Rust mentors who were tirelessly helping our contributors to complete their projects. Without you, Rust GSoC would not be possible.</p>
<section class="footnotes">
<ol class="footnotes-list">
<li id="fn-success-rate">
<p>97.5% over a three-year period, if you are wondering (40 out of 41 projects were successful so far). <a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#fr-success-rate-1">↩</a></p>
</li>
<li id="fn-2038">
<p>If you were wondering, then yes, this is actually related to the famous <a href="https://en.wikipedia.org/wiki/Year_2038_problem" rel="external">2038 problem</a> :) <a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#fr-2038-1">↩</a></p>
</li>
<li id="fn-mold">
<p>In case you were wondering, the <code>mold</code> linker does not support linker scripts required to link Linux kernel modules at the moment, so Vishruth did not compare the performance of Wild against <code>mold</code> here. <a href="https://blog.rust-lang.org/2026/11/11/gsoc-2026-results/#fr-mold-1">↩</a></p>
</li>
</ol>
</section></div>
    </content>
    <updated>2026-11-11T00:00:00Z</updated>
    <published>2026-11-11T00:00:00Z</published>
    <author>
      <name>Jakub Beránek</name>
    </author>
    <source>
      <id>https://blog.rust-lang.org/</id>
      <author>
        <name>Maintained by the Rust Teams.</name>
        <uri>https://github.com/rust-lang/blog.rust-lang.org/</uri>
      </author>
      <link href="https://blog.rust-lang.org/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://blog.rust-lang.org/" rel="alternate" type="text/html"/>
      <subtitle xml:lang="en">Empowering everyone to build reliable and efficient software.</subtitle>
      <title xml:lang="en">Rust Blog</title>
      <updated>2026-11-13T09:01:38Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/security/?p=2935</id>
    <link href="https://blog.mozilla.org/security/2026/11/10/open-research-stronger-privacy-making-firefox-users-harder-to-fingerprint/" rel="alternate" type="text/html"/>
    <title>Open research, stronger privacy: Making Firefox users harder to fingerprint</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Firefox is strengthening protection against trackers that recognize you across websites, even when they don’t use cookies. The latest fingerprinting protections shipped in Firefox reduce the extractable distinguishing details, making … <a class="go" href="https://blog.mozilla.org/security/2026/11/10/open-research-stronger-privacy-making-firefox-users-harder-to-fingerprint/">Read more</a></p>
<p>The post <a href="https://blog.mozilla.org/security/2026/11/10/open-research-stronger-privacy-making-firefox-users-harder-to-fingerprint/">Open research, stronger privacy: Making Firefox users harder to fingerprint</a> appeared first on <a href="https://blog.mozilla.org/security">Mozilla Security Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Firefox is strengthening protection against trackers that recognize you across websites, even when they don’t use cookies. The latest fingerprinting protections shipped in Firefox reduce the extractable distinguishing details, making more Firefox users look alike to tracking scripts and strengthening individuals’ privacy in everyday browsing.</p>
<p>These protections build on our research into browser and device fingerprinting, a technique that combines details about your browser and device to identify you across websites. We investigated which details contribute most to make users uniquely identifiable, turned those findings into practical protections for Firefox users, and shared our results openly so the wider web security and privacy community can build stronger defenses.</p>
<p>Our findings are documented in the research paper <a href="https://research.mozilla.org/files/2026/11/large-Scale_measurement_and_real-world_mitigation_of_web_browser_fingerprinting_in_the_wild_extended_version.pdf"><i>Large-Scale Measurement and Real-World Mitigation of Web Browser Fingerprinting in the Wild</i>,</a> which has been accepted for publication at <a href="https://www.sigsac.org/ccs/CCS2026/">Computer and Communications Security (CCS) 2026</a>, a leading international conference on computer security and privacy. We’ve also created an easier-to-digest website<a href="https://fingerprinting.study/"> and browser test suite</a> to help explore the findings in the paper.</p>
<h3><b>Cookie-less Tracking</b></h3>
<p>Browser fingerprinting combines details about your browser and device, such as available fonts, screen dimensions, and graphics hardware, to build a uniquely recognizable profile. Each piece may seem ordinary, but together, they can enable trackers to single you out across websites, even without storing a cookie.</p>
<p>Effective fingerprinting protection starts with understanding which browser details trackers rely on most. Our research found that protecting just a handful of browser features can significantly weaken popular fingerprinting techniques. That finding enabled us to focus on Firefox’s protections where they can make the biggest difference and bring those benefits to all Firefox users.</p>
<p>To evaluate these techniques, we simulated the browser measurements collected by fingerprinting scripts from Fingerprint Pro, Signifyd, and Akamai and examined how their combinations distinguish users. The study used measurements collected from nearly 25 million Firefox users, with additional privacy safeguards beyond Mozilla’s existing<a href="https://docs.telemetry.mozilla.org/"> data collection policies</a>.</p>
<p>Those safeguards included<a href="https://support.mozilla.org/en-US/kb/ohttp-explained"> OHTTP</a>, which routed encrypted requests through a relay. The relay sees the user’s IP address but not the request contents, while Mozilla receives the contents without the user’s IP address. We also tightly limited data access and retention: individual telemetry records were deleted several months ago and only aggregate results were retained and published for open science. Our research paper explains the method, safeguards and ethical considerations in detail.</p>
<h3><b>Less distinctive, more private</b></h3>
<p>Our approach reduces unnecessary differences in the information Firefox exposes to websites. For example, Firefox limits the information exposed through screen resolution APIs to hide the size and position of the system taskbar or dock, preventing that desktop layout detail from contributing to a fingerprint. As another example, it can report processor counts as either 4 or 8 instead of exposing the exact count, which can make a browser more distinctive.</p>
<p>Our goal is to make more users’ browsers look similar to fingerprinting scripts while preserving the information websites need to function correctly, like language and timezone settings. Firefox also uses randomization to make other fingerprinting signals less useful to trackers, though the benefits of these techniques are harder to quantify and fall outside the measurements reported here.</p>
<p>In our evaluation, these protections (the most recent of which shipped in<a href="https://blog.mozilla.org/en/firefox/fingerprinting-protections/"> Firefox 145</a>) substantially degraded the precision of fingerprinting in Firefox both by reducing the number of users with unique fingerprints and increasing the size of the groups of users that share a fingerprint.</p>
<p>The research also enabled us to identify why certain measurements differed between users. Addressing these differences produced more consistent outputs for <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2046791">image rendering</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2036977">Web Audio</a>, and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2037094">mathematical operations on Android</a>, reducing the distinguishing details available to fingerprinters.</p>
<p>These results show that substantial reductions in browser fingerprint uniqueness are achievable and provide meaningful progress toward stronger online privacy. These do not make fingerprinting impossible as trackers can surely adapt. But our research provides a concrete, measurable improvement in browser defenses against online tracking.</p>
<p>The built-in privacy protections in Firefox are complemented with capabilities and options to further strengthen the protection against online fingerprinters. Built-in and always-on <a href="https://www.firefox.com/en-US/features/total-cookie-protection/">Total Cookie Protection</a> in Firefox segments stateful identifiers and prevents trackers from following you across your browsing using cookies. <a href="https://relay.firefox.com/">Firefox Relay</a> provides you with unique email masks, preventing websites from linking your subscriptions to other sites via data brokers. And <a href="https://www.firefox.com/en-US/features/browser-with-built-in-vpn-secure-browsing/">Firefox now integrates a free VPN</a> that masks your IP address to protect against tracking and fingerprinting. Together with Firefox’s enhanced fingerprinting protections, these capabilities provide everyone a very strong foundation to take back control of their privacy online.</p>
<h3><b>Research that improves everyday browsing</b></h3>
<p><a href="https://blog.mozilla.org/en/firefox/privacy-security/mozilla-anti-tracking-milestones-timeline/">Privacy protections need to work on the websites people use every day.</a> These findings allow us to prioritize changes that deliver measurable privacy benefits while keeping those websites working.</p>
<p>Some of Firefox’s fingerprinting protections, such as hiding the size of your taskbar or dock, are on by default in all browsing modes. Others are introduced first in <a href="https://support.mozilla.org/en-US/kb/private-browsing-use-firefox-without-history">Private Browsing</a> and <a href="https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop">Strict Enhanced Tracking Protection (ETP) mode</a>, while we work toward enabling them by default, following the <a href="https://blog.mozilla.org/en/mozilla/firefox-rolls-out-total-cookie-protection-by-default-to-all-users-worldwide/">same strategy</a> we’ve used for years. To enable these additional protections in all your Firefox windows, select Strict in the Enhanced Tracking Protection settings. Follow the steps <a href="https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop#w_what-to-do-if-a-site-seems-broken">here</a> if the “Strict” protections get in the way of any website functionality.</p>
<p>Want to explore browser fingerprinting yourself? Visit the<a href="https://fingerprinting.study/"> research project page</a> to try the fingerprinting test and learn more about our findings. For a closer look at what we measured and how we turned those insights into Firefox protections, explore our paper:<a href="https://research.mozilla.org/files/2026/11/large-Scale_measurement_and_real-world_mitigation_of_web_browser_fingerprinting_in_the_wild_extended_version.pdf"> <i>Large-Scale Measurement and Real-World Mitigation of Web Browser Fingerprinting in the Wild</i></a>.</p>
<p>We’ll keep strengthening Firefox’s privacy protections while continuing to work in the open. By sharing our research, our code, and what we learn, we’re shaping the web we envision: free, private, secure, and accessible to all.</p>
<p>The post <a href="https://blog.mozilla.org/security/2026/11/10/open-research-stronger-privacy-making-firefox-users-harder-to-fingerprint/">Open research, stronger privacy: Making Firefox users harder to fingerprint</a> appeared first on <a href="https://blog.mozilla.org/security">Mozilla Security Blog</a>.</p></div>
    </content>
    <updated>2026-11-10T18:36:02Z</updated>
    <published>2026-11-10T18:36:02Z</published>
    <category term="Privacy"/>
    <category term="fingerprinting"/>
    <category term="Research"/>
    <author>
      <name>Tom Ritter, Frederik Braun and Christoph Kerschbaumer</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/security/</id>
      <link href="https://blog.mozilla.org/security/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/security/" rel="alternate" type="text/html"/>
      <title>Mozilla Security Blog</title>
      <updated>2026-11-10T18:36:02Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.thunderbird.net/?p=4695</id>
    <link href="https://blog.thunderbird.net/2026/11/from-research-to-prototype-testing-the-new-desktop-settings/" rel="alternate" type="text/html"/>
    <title>From Research to Prototype: Testing the New Desktop Settings</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>In the last update, the team shared ongoing work around removing technical jargon and adopting plain language so everyone can navigate settings with ease. Those initial content refinements have rolled out into Thunderbird already (v160). Following those copy updates, the team ran research to evaluate how settings information is structured. Below is a breakdown of […]</p>
<p>The post <a href="https://blog.thunderbird.net/2026/11/from-research-to-prototype-testing-the-new-desktop-settings/">From Research to Prototype: Testing the New Desktop Settings</a> appeared first on <a href="https://blog.thunderbird.net">The Thunderbird Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="New appearance settings page, changing the accent colour" class="attachment-640x360 size-640x360 wp-post-image" height="360" src="https://blog.thunderbird.net/files/2026/11/Hero-image-3-768x432.jpg" width="640"/></p>
<p>In the last update, the team shared ongoing work around removing technical jargon and adopting plain language so everyone can navigate settings with ease. Those initial content refinements have rolled out into Thunderbird already (v160).</p>



<p>Following those <a href="https://blog.thunderbird.net/2026/09/desktop-settings-removing-technical-jargon/">copy updates</a>, the team ran research to evaluate how settings information is structured. Below is a breakdown of what the data revealed, how those findings shaped an interactive prototype, and the plan for incremental rollout.</p>



<p>If you don’t have time to read the full research summary, here are the key points. We had an overwhelming response to the research study, so we have feedback from many different perspectives and use cases. Some of the new organization of categories weren’t as easy to find because of the language or because it was too hidden, so we’ve updated those and it’s reflected in the new prototype linked below.</p>



<figure class="wp-block-image size-full is-resized"><a href="https://blog.thunderbird.net/files/2026/11/Blog-inline-image_2-1-scaled.jpg"><img alt="" class="wp-image-4708" height="1440" src="https://blog.thunderbird.net/files/2026/11/Blog-inline-image_2-1-scaled.jpg" style="width: 840px; height: auto;" width="2560"/></a><figcaption class="wp-element-caption">Tree testing survey for the new information structure </figcaption></figure>



<h3>Research overview</h3>



<p><strong>Who took part in the study</strong></p>



<ul>
<li>381 community members </li>



<li>42 countries represented </li>



<li>88% use Thunderbird on a daily basis</li>
</ul>



<p><strong>About the structure of the study </strong></p>



<p>To evaluate the proposed information architecture, the team conducted a tree test. </p>



<p>A tree test evaluates a text-only hierarchy with no visual styling. It isolates structure from visual design, reveals the exact navigation paths taken to complete a task, and saves development effort by validating organization before code is written. The scenarios that we tested alongside the tree test focused on key areas users have been bringing up as things they change often or have been confused about in the past. </p>



<p>However, there are trade-offs: without visual cues (icons, layout, color), success rates in tree tests are often artificially lower than in a functional app. Crucially, a tree test cannot simulate an active search bar, a primary navigation method for many participants. That is why testing an interactive prototype is the next step.</p>



<p/>



<div class="wp-block-group is-layout-constrained wp-block-group-is-layout-constrained"><div class="wp-block-group__inner-container">
<h3><strong>Key research insights </strong></h3>
</div></div>



<p><strong>What worked well</strong></p>



<ul>
<li><strong>Appearance:</strong> Locating appearance-level preferences was straightforward for roughly 60% of respondents (though some initially checked <em>Themes</em>, expecting menu and button colors there).</li>
</ul>



<p/>



<ul>
<li><strong>App updates:</strong> Update controls were well understood within the test, with most participants noting they typically check version details via Help &gt; About.</li>
</ul>



<p/>



<ul>
<li><strong>Set up mobile:</strong> Located successfully by most participants. However, those looking for account sync preferences frequently navigated to <em>Synchronization &amp; Storage.</em></li>
</ul>



<p><strong>What needs improvement</strong></p>



<ul>
<li><strong>Global vs. Account settings:</strong> Participants voiced frustration with a rigid divide between Global Preferences and Account Settings. Switching back and forth depending on whether an option applies to one account or the whole app feels disjointed.
<ul>
<li><em>“My only concern is that you seem to be keeping ‘Settings’ and ‘Accounts’ separate… they should be merged or use a separator on the same page.”</em></li>



<li><em>“I continue to be bemused by the strong separation of settings and account settings.”</em></li>
</ul>
</li>
</ul>



<ul>
<li><strong>Category naming misalignment:</strong> Having dedicated top-level categories for <em>Calendar</em> and <em>Chat</em>, while categorizing core email behavior under <em>Composition</em>, created confusion. High confusion also surfaced with  the difference between <em>Appearance</em>, <em>Themes</em>, and <em>Add-ons &amp; Themes</em> as there is overlap.
<ul>
<li><em>“Calendar setting seems a bit odd, as there isn’t ‘Mail’, ‘Contacts’, or ‘News’ sections. Where are their settings?”</em></li>
</ul>
</li>
</ul>



<ul>
<li><strong>Ambiguous Labels:</strong> Labeling a section “New Features” left participants unsure whether it contained release notes or experimental settings. Suggestions strongly favored clearer, purpose-driven labels like Thunderbird Labs or Experimental Features. </li>
</ul>



<p/>



<ul>
<li><strong>Search dependency:</strong> A significant group, particularly power users and Linux desktop users, noted that manual category browsing is a secondary option. The primary workflow is jumping straight to the search bar. While search cannot be tested within a tree test framework, this reinforces search as a first-class feature in modern settings.</li>
</ul>



<p>Feedback from participants who provided <strong>detailed qualitative comments</strong>:</p>



<ul>
<li>~35% shared positive reactions, citing intuitive grouping and clearer organization.</li>



<li>~20% expressed resistance to change, emphasizing the need for stability, preservation of traditional menu workflows, reliable dark mode support, and caution against redesigning elements without functional improvement.</li>
</ul>



<p/>



<h3><strong>Turning feedback into design decisions</strong></h3>



<figure class="wp-block-image size-full is-resized"><a href="https://blog.thunderbird.net/files/2026/11/3-2-scaled.jpg"><img alt="" class="wp-image-4729" height="1440" src="https://blog.thunderbird.net/files/2026/11/3-2-scaled.jpg" style="width: 840px; height: auto;" width="2560"/></a><figcaption class="wp-element-caption">Preview of the desktop settings prototype </figcaption></figure>



<p>We’ve taken all that feedback into consideration and designed a lightweight prototype that uses a new way to structure the information. Some folks might not notice the new changes, but we hope this makes discovery easy for new users while maintaining the flexibility our user base values. </p>



<p>You’ll also notice the prototype doesn’t have all the functionality built in so some things might not work, nor does it adapt to your operating system so it displays specific language appropriate for macOS, Windows or Linux.</p>



<p><img alt="&#x27A1;" class="wp-smiley" src="https://s.w.org/images/core/emoji/14.0.0/72x72/27a1.png" style="height: 1em;"/> <a href="https://usabi.li/do/fnrcxedsajnr/yfbgff"><strong>Test the prototype</strong></a></p>



<h3><strong>What’s next</strong></h3>



<p>One area deliberately not tackled in this prototype is the split between Account Settings and Global Settings. Bridging that gap requires deeper architectural changes. To avoid over-complicating this iteration, changes are being kept incremental.</p>



<p>Overhauling settings across a mature application cannot happen in a single, disruptive release. Each functional piece will include direct avenues for testing and feedback before graduating to beta and stable channels.</p>



<p>Thank you to everyone who took part and contributed such thoughtful feedback.</p>
<p>The post <a href="https://blog.thunderbird.net/2026/11/from-research-to-prototype-testing-the-new-desktop-settings/">From Research to Prototype: Testing the New Desktop Settings</a> appeared first on <a href="https://blog.thunderbird.net">The Thunderbird Blog</a>.</p></div>
    </content>
    <updated>2026-11-10T15:10:23Z</updated>
    <published>2026-11-10T15:10:23Z</published>
    <category term="Community"/>
    <category term="Product"/>
    <category term="Thunderbird"/>
    <category term="Desktop"/>
    <category term="Research"/>
    <category term="Settings"/>
    <author>
      <name>Aly Blenkin</name>
    </author>
    <source>
      <id>https://blog.thunderbird.net/</id>
      <logo>https://blog.thunderbird.net/files/2024/01/cropped-Thunderbird_Logo_512-32x32.png</logo>
      <link href="https://blog.thunderbird.net/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.thunderbird.net/" rel="alternate" type="text/html"/>
      <subtitle>News, previews, and guides from the Thunderbird Team</subtitle>
      <title>The Thunderbird Blog</title>
      <updated>2026-11-10T23:12:16Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88959</id>
    <link href="https://blog.mozilla.org/en/firefox/built-in-vpn-unlimited-data/" rel="alternate" type="text/html"/>
    <title>Firefox’s free built-in VPN uncaps data limit through January 2027</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Whether you’re heading home to see family this winter or taking a well-earned break before the year wraps up, we want you to browse with a little more peace of mind. That’s why, as our gift to you, everyone using Firefox’s free built-in VPN gets unlimited data starting today, November 10, through January 31, 2027. […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/built-in-vpn-unlimited-data/">Firefox’s free built-in VPN uncaps data limit through January 2027</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Whether you’re heading home to see family this winter or taking a well-earned break before the year wraps up, we want you to browse with a little more peace of mind. That’s why, as our gift to you, everyone using Firefox’s <a href="https://www.firefox.com/landing/vpn/">free built-in VPN</a> gets unlimited data starting today, November 10, through January 31, 2027. Sign in with a <a href="https://www.mozilla.org/account/">Mozilla account</a> and unlock extra privacy for all that shopping, travel planning, and everyday browsing, no gift receipt required. </p>



<p>Using Firefox’s free built-in VPN makes it harder for websites to use your IP address to determine where you are, or connect your visits across the web. Most importantly, you’re not trading your browsing data for that protection: Firefox doesn’t sell your browsing data, interrupt you with ads, or keep a record of the websites you visit. </p>



<p>You can use VPN to:</p>



<ul>
<li><strong>Keep the sites you visit private on shared Wi-Fi.</strong> You might use café Wi-Fi to check your itinerary, or look up something you’d prefer to keep to yourself while at a relative’s house. Turning on VPN helps hide the sites you’re visiting from whoever runs those Wi-Fi networks so your browsing habits stay your own.</li>



<li><strong>Change your browsing location.</strong> Firefox’s built-in VPN lets you change where your connection appears to come from, making it easy to check news from home while abroad.</li>
</ul>



<p>Two things to remember:</p>



<ol>
<li><strong>VPN doesn’t make you anonymous online or hide browsing history on your device.</strong> Websites can recognize you through cookies or when you sign into an account. Use <a href="https://www.firefox.com/features/private-browsing/">Private Window</a> to browse without logging new visits in your Firefox history.</li>



<li><strong>Firefox’s built-in VPN only covers browsing within Firefox.</strong> For protection across other apps on your device, check out<a href="https://www.mozilla.org/products/vpn/"> Mozilla VPN</a> (a separate, paid subscription service).</li>
</ol>



<p>Firefox’s free built-in VPN is available to people using Firefox on desktop and Android (iOS is coming soon!). To start using the service:</p>



<ul>
<li>Sign up for a <a href="https://www.mozilla.org/account/">Mozilla account</a> if you don’t yet have one. </li>



<li>Select the VPN icon in Firefox’s toolbar on desktop or open the three-dot menu and go to Settings &gt; VPN on your Android device. </li>



<li>Follow the setup prompts, turn on VPN, and start browsing. </li>
</ul>



<p>You can check for<a href="https://support.mozilla.org/kb/built-in-vpn"> availability in your region</a> and review full instructions for using VPN on<a href="https://support.mozilla.org/en-US/kb/built-in-vpn"> desktop</a> and<a href="https://support.mozilla.org/kb/mobile-android-vpn"> Android</a> in our Help Center.</p>



<p><a href="https://www.firefox.com/">Download Firefox</a> to try it out today.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/built-in-vpn-unlimited-data/">Firefox’s free built-in VPN uncaps data limit through January 2027</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-11-10T14:00:00Z</updated>
    <published>2026-11-10T14:00:00Z</published>
    <category term="Firefox"/>
    <category term="Firefox Features"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry>
    <id>https://servo.org/blog/2026/11/05/september-in-servo/</id>
    <link href="https://servo.org/blog/2026/11/05/september-in-servo/" rel="alternate" type="text/html"/>
    <title>September in Servo: &lt;progress&gt;, rounded rectangles, and more!</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://github.com/servo/servo/releases/tag/v0.7.0"><strong>Servo 0.7.0</strong></a> contains all of the changes we landed in September, spanning 527 commits!</p>
<figure>
    <a href="https://servo.org/img/blog/2026-10-gary-banner.png"><img alt="a black and white cat named Gary showing off new visual web platform features" src="https://servo.org/img/blog/2026-10-gary-banner.png"/></a>
</figure>
<p>The developer tools console now <strong>eagerly evaluates</strong> JS inputs, allowing faster feedback (<a href="https://github.com/freyacodes">@freyacodes</a>, <a href="https://github.com/servo/servo/pull/47527">#47527</a>).</p>
<p>We’ve shipped new web platform features:</p>
<ul>
<li>the <strong>:checked</strong> pseudoclass (<a href="https://github.com/skyz1">@skyz1</a>, <a href="https://github.com/servo/servo/pull/47987">#47987</a>)</li>
<li>the <strong>user-select</strong> property (<a href="https://github.com/SimonSapin">@SimonSapin</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48137">#48137</a>, <a href="https://github.com/servo/servo/pull/48242">#48242</a>)</li>
<li>the <strong>&lt;progress&gt;</strong> element (<a href="https://github.com/rayguo17">@rayguo17</a>, <a href="https://github.com/servo/servo/pull/46974">#46974</a>)</li>
<li>CSS <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Values_and_units/Using_typed_arithmetic">typed arithmetic</a> (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/48338">#48338</a>)</li>
<li>the <strong>alpha()</strong> CSS function (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/48344">#48344</a>)</li>
<li>the <strong>font-width</strong> property (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/47914">#47914</a>)</li>
</ul>
<p>Plus a bunch of new DOM APIs:</p>
<ul>
<li><strong>parentRule</strong> on <strong>CSSRule</strong> and <strong>CSSStyleDeclaration</strong> (<a href="https://github.com/skyz1">@skyz1</a>, <a href="https://github.com/servo/servo/pull/47743">#47743</a>)</li>
<li><strong>version</strong> on <strong>HTMLHtmlElement</strong> (<a href="https://github.com/SilvioPilato">@SilvioPilato</a>, <a href="https://github.com/servo/servo/pull/47786">#47786</a>)</li>
<li><strong>getComposedRanges()</strong> and <strong>direction</strong> on <strong>Selection</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47683">#47683</a>)</li>
<li><strong>baseURL</strong> on <strong>CSSStyleSheet</strong> (<a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/servo/servo/pull/47783">#47783</a>)</li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules#loading_non-javascript_resources"><strong>CSS modules</strong></a>(<a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/servo/servo/pull/47813">#47813</a>) and <strong>text modules</strong> (<a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/servo/servo/pull/47863">#47863</a>)</li>
<li><strong>getContextAttributes()</strong> on <strong>CanvasRenderingContext2D</strong> and <strong>OffscreenCanvasRenderingContext2D</strong> (<a href="https://github.com/Taym95">@Taym95</a>, <a href="https://github.com/servo/servo/pull/47868">#47868</a>)</li>
<li>the <strong>Content-Language</strong> header (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/47930">#47930</a>)</li>
<li><strong>dir</strong> on <strong>Document</strong> (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/48170">#48170</a>)</li>
<li><strong>SVGAElement</strong>, <strong>SVGPatternElement</strong>, <strong>SVGTSpanElement</strong>, <strong>SVGTextContentElement</strong>, <strong>SVGTextElement</strong>, <strong>SVGTextPositioningElement</strong> (<a href="https://github.com/mu-mostafa98">@mu-mostafa98</a>, <a href="https://github.com/servo/servo/pull/48174">#48174</a>)</li>
<li>the <strong>MLKEM768-X25519</strong> algorithm for <strong>WebCrypto</strong> (<a href="https://github.com/kkoyung">@kkoyung</a>, <a href="https://github.com/servo/servo/pull/48240">#48240</a>, <a href="https://github.com/servo/servo/pull/48282">#48282</a>, <a href="https://github.com/servo/servo/pull/48313">#48313</a>, <a href="https://github.com/servo/servo/pull/48350">#48350</a>)</li>
<li><strong>roundRect()</strong> on <strong>CanvasRenderingContext2D</strong> (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/48293">#48293</a>)</li>
<li><strong>paintTime</strong> and <strong>presentationTime</strong> on <strong>PerformancePaintTiming</strong> (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/47926">#47926</a>)</li>
<li><strong>getCueAsHTML()</strong> on <strong>VTTCue</strong> (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48146">#48146</a>)</li>
</ul>
<h3>Security <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#security">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>We upgraded to <strong>SpiderMonkey v153.3</strong> and <strong>mozangle v0.7</strong>, both of which included fixes for security bugs reported upstream (<a href="https://github.com/sagudev">@sagudev</a>, <a href="https://github.com/servo/servo/pull/48176">#48176</a>, <a href="https://github.com/servo/servo/pull/47655">#47655</a>, <a href="https://github.com/servo/servo/pull/48259">#48259</a>).</p>
<h3>Real world compat <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#real-world-compat">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>The <a href="https://www.egui.rs/">egui.rs</a> demo now works as expected with <code>--pref dom._webegpu_enabled</code>.</p>
<figure>
    <a href="https://servo.org/img/blog/2026-10-egui.png"><img alt="http://egui.rs rendering in Servo" src="https://servo.org/img/blog/2026-10-egui.png"/></a>
</figure>
<p>This <a href="https://jooyouss.github.io/candy-crush/">Candy Crush</a> game is now playable.</p>
<figure>
    <a href="https://servo.org/img/blog/2026-10-candycrush.png"><img alt="A Candy Crush game rendering in Servo" src="https://servo.org/img/blog/2026-10-candycrush.png"/></a>
</figure>
<p>We’re interested to hear how well your favourite websites run in Servo! Report successes in <a href="https://servo.zulipchat.com/#narrow/channel/263398-general/topic/Servo.20web.20compat.20success.20stories/with/612898341">this Zulip thread</a> or <a href="https://github.com/servo/servo/discussions/49037">this Github discussion</a>, and failures <a href="https://github.com/servo/servo/issues">in our GitHub issues</a>.</p>
<h3>Work in progress <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#work-in-progress">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>Our accessibility tree (<code>--pref accessibility_enabled</code>) now <strong>reports geometry bounds</strong> for inline elements (<a href="https://github.com/alice">@alice</a>, <a href="https://github.com/servo/servo/pull/47905">#47905</a>) and does much less work when responding to DOM changes (<a href="https://github.com/alice">@alice</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47690">#47690</a>).
Additionally, elements with <code>display: none</code> are reported as hidden (<a href="https://github.com/alice">@alice</a>, <a href="https://github.com/servo/servo/pull/47772">#47772</a>).</p>
<p>We had lots of conformance improvements for our <strong>WebGL2 implementation</strong> (<code>--pref dom_webgl2_enabled</code>) (<a href="https://github.com/mxmgorin">@mxmgorin</a>, <a href="https://github.com/servo/servo/pull/48423">#48423</a>, <a href="https://github.com/servo/servo/pull/48441">#48441</a>, <a href="https://github.com/servo/servo/pull/48470">#48470</a>, <a href="https://github.com/servo/servo/pull/48479">#48479</a>, <a href="https://github.com/servo/servo/pull/48495">#48495</a>, <a href="https://github.com/servo/servo/pull/48473">#48473</a>, <a href="https://github.com/servo/servo/pull/48536">#48536</a>).</p>
<p>Support for WSIWYG editors (which rely heavily on <strong><code>contenteditable</code></strong>) is going very well: keyboard inputs are now hooked up when <code>--pref dom_exec_command_enabled</code> is present, so many editors are now usable (<a href="https://www.tiny.cloud/docs/tinymce/latest/basic-example/">example</a>).</p>
<p><strong>Closed captioning</strong> for video elements is making progress.
Text tracks now fire <code>enter</code>, <code>exit</code>, and <code>cuechange</code> events (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/47725">#47725</a>).
Media elements now return the full sorted list of text tracks (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/47785">#47785</a>), and adding cues to a text track now sets that track correctly (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48012">#48012</a>).
Text track objects now reflect the attributes of the associated <code>&lt;track&gt;</code> element.
Text track URLs are fetched at the correct time (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48325">#48325</a>), and active cues are computed correctly (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48305">#48305</a>), while text track cues are ordered as expected (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48368">#48368</a>).
Additionally, WebVTT parsing can now recover from errors (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48391">#48391</a>).</p>
<p>The <strong>Sanitizer API</strong> (<code>--pref dom_sanitizer_enabled</code>) now accepts the <code>javascriptURLs</code> property (<a href="https://github.com/skyz1">@skyz1</a>, <a href="https://github.com/servo/servo/pull/47867">#47867</a>).</p>
<p><strong>IndexedDB</strong> continues to improve: tables no longer error if unrelated tables contain duplicate index names (<code>--pref dom_indexeddb_enabled</code>) (<a href="https://github.com/leowatts">@leowatts</a>, <a href="https://github.com/servo/servo/pull/47936">#47936</a>).
Additionally, we implemented <strong>openCursor()</strong> and <strong>openKeyCursor()</strong> on <strong>IDBIndex</strong> (<a href="https://github.com/kuntal-devrat">@kuntal-devrat</a>, <a href="https://github.com/servo/servo/pull/48281">#48281</a>), as well as <strong>advance()</strong>, <strong>continue()</strong>, and <strong>continuePrimaryKey()</strong> on <strong>IDBCursor</strong> (<a href="https://github.com/kuntal-devrat">@kuntal-devrat</a>, <a href="https://github.com/servo/servo/pull/48400">#48400</a>).</p>
<p>We implemented the <strong>getTimeline()</strong> and <strong>setTimeline()</strong> methods for the <strong>Animation</strong> interface (<code>--pref dom_web_animations_enabled</code>) (<a href="https://github.com/simonwuelker">@simonwuelker</a>, <a href="https://github.com/servo/servo/pull/48122">#48122</a>).</p>
<h3>Embedding API <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#embedding-api">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>There’s a new API for events originating from accessibility tools: <a href="https://doc.servo.org/servo/struct.Servo.html"><code>Servo</code></a>::<a href="https://doc.servo.org/servo/struct.Servo.html#method.forward_accessibility_action"><code>forward_accessibility_action</code></a> (<a href="https://github.com/alice">@alice</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48512">#48512</a>).</p>
<p>There is also an API to clear session history: <a href="https://doc.servo.org/servo/struct.WebView.html"><code>WebView</code></a>::<a href="https://doc.servo.org/servo/struct.WebView.html#method.clear_session_history"><code>clear_session_history</code></a> (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/47483">#47483</a>).</p>
<p>The <a href="https://doc.servo.org/servo/struct.WebView.html"><code>WebView</code></a>::<code>set_throttled</code> API has been removed (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/39923">#39923</a>).
Throttling automatically occurs when a WebView is <a href="https://doc.servo.org/servo/struct.WebView.html#method.hide">hidden</a> and is stopped when <a href="https://doc.servo.org/servo/struct.WebView.html#method.show">shown</a>.</p>
<p>The <a href="https://doc.servo.org/servo/trait.WebViewDelegate.html"><code>WebViewDelegate</code></a>::<code>notify_focus_changed</code> method was removed, along with the <a href="https://doc.servo.org/servo/struct.Servo.html"><code>Servo</code></a> methods <code>focus</code> and <code>blur</code> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48364">#48364</a>).
Embedders must call <a href="https://doc.servo.org/servo/struct.WebView.html"><code>WebView</code></a>::<a href="https://doc.servo.org/servo/struct.WebView.html#method.set_focused"><code>set_focused</code></a> whenever a WebView has gained or lost system focus.</p>
<p>The <code>webgl</code> feature has been added to the <code>default_web_features</code> feature (<a href="https://github.com/janeoa">@janeoa</a>, <a href="https://github.com/servo/servo/pull/47866">#47866</a>).
If an embedding does not want to ship with WebGL support they will now need to disable default features.</p>
<p>Multiprocess mode is enabled at build time with the new Cargo feature <code>multprocess</code> (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/47360">#47360</a>).
To remove support for this feature (reducing binary size by ~2MB), build Servo with default features disabled.</p>
<p>Two new preferences exist to tune garbage collector behaviour: <code>js_mem_gc_malloc_threshold_base_mb</code> and <code>js_mem_gc_urgent_threshold_mb</code> (<a href="https://github.com/mxmgorin">@mxmgorin</a>, <a href="https://github.com/servo/servo/pull/47999">#47999</a>).
These can help on memory-constrained devices, and more information is available in the SpiderMonkey source (<a href="https://searchfox.org/firefox-main/rev/28b7a7bffb5f82828143d9ad63839ad263b598be/js/src/gc/Scheduling.h#425-429">base</a>, <a href="https://searchfox.org/firefox-main/rev/28b7a7bffb5f82828143d9ad63839ad263b598be/js/src/gc/Scheduling.h#440-445">urgent</a>).</p>
<p>The JVM compatibility target was raised to 11 on Android (<a href="https://github.com/veyndan">@veyndan</a>, <a href="https://github.com/servo/servo/pull/48414">#48414</a>).</p>
<h3>For users and developers <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#for-users-and-developers">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>It is now possible to cross-compile the OpenHarmony build from Windows hosts (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/48392">#48392</a>).</p>
<p>Unhandled promise rejections are reported to the JS console (<a href="https://github.com/TTyChud">@TTyChud</a>, <a href="https://github.com/servo/servo/pull/48486">#48486</a>), making it easier to narrow down web compatibility issues in Servo.</p>
<p>The OpenHarmony SDK was updated to API level 23 (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/48505">#48505</a>).</p>
<p>Pressing Control+A (or Command+A on macOS) now selects all the content in a document (<a href="https://github.com/dzfrias">@dzfrias</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48025">#48025</a>).
It is no longer possible to copy text inside of password inputs (<a href="https://github.com/dzfrias">@dzfrias</a>, <a href="https://github.com/servo/servo/pull/48404">#48404</a>).</p>
<p>Embedder-originating JS (e.g. devtools console or embedding APIs) will always execute, even in documents that disable scripting via sandboxing or CSP (<a href="https://github.com/derdilla">@derdilla</a>, <a href="https://github.com/servo/servo/pull/48394">#48394</a>).</p>
<h3>Performance and stability <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#performance-and-stability">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>We improved performance by removing <strong>unnecessary allocations</strong> (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/47689">#47689</a>, <a href="https://github.com/servo/servo/pull/47839">#47839</a>, <a href="https://github.com/servo/servo/pull/47838">#47838</a>, <a href="https://github.com/servo/servo/pull/47982">#47982</a>, <a href="https://github.com/servo/servo/pull/48006">#48006</a>, <a href="https://github.com/servo/servo/pull/48036">#48036</a>, <a href="https://github.com/servo/servo/pull/48099">#48099</a>, <a href="https://github.com/servo/servo/pull/48204">#48204</a>, <a href="https://github.com/servo/servo/pull/48127">#48127</a>, <a href="https://github.com/servo/servo/pull/48218">#48218</a>, <a href="https://github.com/servo/servo/pull/48357">#48357</a>, <a href="https://github.com/servo/servo/pull/48386">#48386</a>, <a href="https://github.com/servo/servo/pull/48422">#48422</a>, <a href="https://github.com/servo/servo/pull/48440">#48440</a>, <a href="https://github.com/servo/servo/pull/48452">#48452</a>, <a href="https://github.com/servo/servo/pull/48508">#48508</a>), <strong>preallocating more</strong> when building vectors (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/sagudev">@sagudev</a>, <a href="https://github.com/webbeef">@webbeef</a>, <a href="https://github.com/servo/servo/pull/47455">#47455</a>, <a href="https://github.com/servo/servo/pull/47613">#47613</a>, <a href="https://github.com/servo/servo/pull/48026">#48026</a>, <a href="https://github.com/servo/servo/pull/48398">#48398</a>), and <strong>avoiding IPC</strong> in single process mode (<a href="https://github.com/leowatts">@leowatts</a>, <a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/Uiniel">@Uiniel</a>, <a href="https://github.com/TTyChud">@TTyChud</a>, <a href="https://github.com/servo/servo/pull/47691">#47691</a>, <a href="https://github.com/servo/servo/pull/47718">#47718</a>, <a href="https://github.com/servo/servo/pull/48002">#48002</a>, <a href="https://github.com/servo/servo/pull/48073">#48073</a>, <a href="https://github.com/servo/servo/pull/48476">#48476</a>, <a href="https://github.com/servo/servo/pull/48435">#48435</a>).</p>
<p>We also sped up Servo by reducing interactions with the GC (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/47818">#47818</a>, <a href="https://github.com/servo/servo/pull/48257">#48257</a>, <a href="https://github.com/servo/servo/pull/48396">#48396</a>), and doing less work when modifying selections (<a href="https://github.com/SimonSapin">@SimonSapin</a>, <a href="https://github.com/servo/servo/pull/47579">#47579</a>), dispatching events (<a href="https://github.com/webbeef">@webbeef</a>, <a href="https://github.com/servo/servo/pull/48078">#48078</a>), calculating font metrics (<a href="https://github.com/RichardTjokroutomo">@RichardTjokroutomo</a>, <a href="https://github.com/servo/servo/pull/48238">#48238</a>), and indexing window frames (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47832">#47832</a>).</p>
<p>We <strong>reduced memory usage</strong> in common cases by reusing buffers (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/47751">#47751</a>), clearing more page-specific data (<a href="https://github.com/Radeonares32">@Radeonares32</a>, <a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/mxmgorin">@mxmgorin</a>, <a href="https://github.com/servo/servo/pull/47651">#47651</a>, <a href="https://github.com/servo/servo/pull/47806">#47806</a>, <a href="https://github.com/servo/servo/pull/47805">#47805</a>, <a href="https://github.com/servo/servo/pull/48166">#48166</a>, <a href="https://github.com/servo/servo/pull/48295">#48295</a>, <a href="https://github.com/servo/servo/pull/48297">#48297</a>, <a href="https://github.com/servo/servo/pull/48016">#48016</a>), compacting data structures (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/webbeef">@webbeef</a>, <a href="https://github.com/SimonSapin">@SimonSapin</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47776">#47776</a>, <a href="https://github.com/servo/servo/pull/48039">#48039</a>, <a href="https://github.com/servo/servo/pull/48050">#48050</a>, <a href="https://github.com/servo/servo/pull/47742">#47742</a>, <a href="https://github.com/servo/servo/pull/48301">#48301</a>, <a href="https://github.com/servo/servo/pull/48296">#48296</a>, <a href="https://github.com/servo/servo/pull/48105">#48105</a>), and sharing more buffers (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47998">#47998</a>).
We also fixed a memory leak involving <code>&lt;audio&gt;</code> and <code>&lt;video&gt;</code> elements (<a href="https://github.com/TTyChud">@TTyChud</a>, <a href="https://github.com/servo/servo/pull/48371">#48371</a>).</p>
<p>We turned on <strong>thread affinity boosting</strong> on Linux, which can improve performance on some CPU architectures (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47058">#47058</a>).</p>
<p>We’re working on statically preventing <a href="https://github.com/servo/servo/issues/39139">a footgun</a> that can lead to uncollectible GC cycles and leaking memory (<a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/lumiscosity">@lumiscosity</a>, <a href="https://github.com/SilvioPilato">@SilvioPilato</a>, <a href="https://github.com/sahilnyk">@sahilnyk</a>, <a href="https://github.com/TTyChud">@TTyChud</a>, <a href="https://github.com/kuntal-devrat">@kuntal-devrat</a>, <a href="https://github.com/MohamedAli00949">@MohamedAli00949</a>, <a href="https://github.com/servo/servo/pull/47941">#47941</a>, <a href="https://github.com/servo/servo/pull/48013">#48013</a>, <a href="https://github.com/servo/servo/pull/48021">#48021</a>, <a href="https://github.com/servo/servo/pull/48035">#48035</a>, <a href="https://github.com/servo/servo/pull/48033">#48033</a>, <a href="https://github.com/servo/servo/pull/48051">#48051</a>, <a href="https://github.com/servo/servo/pull/48072">#48072</a>, <a href="https://github.com/servo/servo/pull/48171">#48171</a>, <a href="https://github.com/servo/servo/pull/48209">#48209</a>, <a href="https://github.com/servo/servo/pull/48248">#48248</a>, <a href="https://github.com/servo/servo/pull/48246">#48246</a>, <a href="https://github.com/servo/servo/pull/48264">#48264</a>, <a href="https://github.com/servo/servo/pull/48285">#48285</a>, <a href="https://github.com/servo/servo/pull/48311">#48311</a>, <a href="https://github.com/servo/servo/pull/48408">#48408</a>, <a href="https://github.com/servo/servo/pull/48053">#48053</a>, <a href="https://github.com/servo/servo/pull/48156">#48156</a>, <a href="https://github.com/servo/servo/pull/48186">#48186</a>, <a href="https://github.com/servo/servo/pull/48223">#48223</a>, <a href="https://github.com/servo/servo/pull/48315">#48315</a>, <a href="https://github.com/servo/servo/pull/47872">#47872</a>, <a href="https://github.com/servo/servo/pull/47698">#47698</a>, <a href="https://github.com/servo/servo/pull/47682">#47682</a>, <a href="https://github.com/servo/servo/pull/47735">#47735</a>, <a href="https://github.com/servo/servo/pull/47816">#47816</a>, <a href="https://github.com/servo/servo/pull/47817">#47817</a>, <a href="https://github.com/servo/servo/pull/47794">#47794</a>, <a href="https://github.com/servo/servo/pull/47909">#47909</a>, <a href="https://github.com/servo/servo/pull/47934">#47934</a>, <a href="https://github.com/servo/servo/pull/47935">#47935</a>, <a href="https://github.com/servo/servo/pull/47954">#47954</a>, <a href="https://github.com/servo/servo/pull/48022">#48022</a>, <a href="https://github.com/servo/servo/pull/47955">#47955</a>, <a href="https://github.com/servo/servo/pull/48058">#48058</a>, <a href="https://github.com/servo/servo/pull/48228">#48228</a>, <a href="https://github.com/servo/servo/pull/48247">#48247</a>, <a href="https://github.com/servo/servo/pull/48261">#48261</a>, <a href="https://github.com/servo/servo/pull/48280">#48280</a>, <a href="https://github.com/servo/servo/pull/48302">#48302</a>, <a href="https://github.com/servo/servo/pull/48316">#48316</a>, <a href="https://github.com/servo/servo/pull/48328">#48328</a>, <a href="https://github.com/servo/servo/pull/48346">#48346</a>, <a href="https://github.com/servo/servo/pull/48355">#48355</a>, <a href="https://github.com/servo/servo/pull/48262">#48262</a>, <a href="https://github.com/servo/servo/pull/48377">#48377</a>, <a href="https://github.com/servo/servo/pull/48304">#48304</a>, <a href="https://github.com/servo/servo/pull/48378">#48378</a>, <a href="https://github.com/servo/servo/pull/48388">#48388</a>, <a href="https://github.com/servo/servo/pull/48432">#48432</a>).</p>
<p>We fixed panics in <strong>WebRTC</strong> (<a href="https://github.com/MunishMummadi">@MunishMummadi</a>, <a href="https://github.com/servo/servo/pull/4772">#4772</a>), <strong>execCommand()</strong> on <strong>Document</strong> (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/47784">#47784</a>), <code>&lt;video&gt;</code> (<a href="https://github.com/calvaris">@calvaris</a>, <a href="https://github.com/servo/servo/pull/46148">#46148</a>), <code>&lt;iframe&gt;</code> (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/48465">#48465</a>), <strong>SharedWorker</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47940">#47940</a>), <strong>ancestorOrigins</strong> on <strong>Document</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48009">#48009</a>), <code>about:memory</code> (<a href="https://github.com/mxmgorin">@mxmgorin</a>, <a href="https://github.com/servo/servo/pull/47686">#47686</a>, <a href="https://github.com/servo/servo/pull/48001">#48001</a>), and EGL 1.4 configurations (<a href="https://github.com/mxmgorin">@mxmgorin</a>, <a href="https://github.com/servo/servo/pull/47803">#47803</a>).</p>
<p>We also fixed a very ironic panic triggered by the <code>about:crash</code> page that loads when a normal page triggers a panic (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48055">#48055</a>)</p>
<p>The JS console no longer hangs when primitive values as thrown as exceptions (<a href="https://github.com/FatCat560">@FatCat560</a>, <a href="https://github.com/servo/servo/pull/47629">#47629</a>).
Servo no longer hangs on shutdown in multiprocess mode (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/48523">#48523</a>), when certain pages use <strong>IntersectionObserver</strong> (<a href="https://github.com/mxmgorin">@mxmgorin</a>, <a href="https://github.com/servo/servo/pull/47693">#47693</a>), when closing a browsing context with pending WebDriver commands (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/48131">#48131</a>, <a href="https://github.com/servo/servo/pull/48172">#48172</a>), or when closing <strong>SharedWorker</strong>s (<a href="https://github.com/nicoburns">@nicoburns</a>, <a href="https://github.com/servo/servo/pull/48477">#48477</a>).</p>
<p><code>about:memory</code> got more improvements: we measure more memory for SVG rendering (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47061">#47061</a>), WebAudio (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47996">#47996</a>), and identify globals that have been leaked (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/48237">#48237</a>).</p>
<h3>More on the web platform <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#more-on-the-web-platform">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>CSS images now <strong>delay the <code>load</code> event</strong>, leading to more consistent behaviour for engine users performing visual rendering (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48199">#48199</a>).</p>
<p>Interactive selections in documents continued to improve!
They now can span shadow trees (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/SimonSapin">@SimonSapin</a>, <a href="https://github.com/servo/servo/pull/47931">#47931</a>, <a href="https://github.com/servo/servo/pull/47694">#47694</a>, <a href="https://github.com/servo/servo/pull/47895">#47895</a>), and have consistent heights and positions (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47937">#47937</a>), plus there are new context menu entries to copy and select all (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48101">#48101</a>).
Additionally, image-based content shows when it is part of a selection (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48149">#48149</a>).</p>
<p><code>Window.open()</code> respects sandbox flags that prevent popups (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47653">#47653</a>).</p>
<p><strong>LargestContentfulPaint</strong> now reports the <strong>loadTime</strong> for image content (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/48286">#48286</a>), ignores cross-origin frames (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/48094">#48094</a>), ignores invisible text (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/48010">#48010</a>), and reports null elements when they are removed from the tree (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/48125">#48125</a>).</p>
<p><strong>select()</strong> on a text input now focuses the control (<a href="https://github.com/dzfrias">@dzfrias</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48475">#48475</a>).</p>
<p>Our WebDriver server now automates setting permissions (<a href="https://github.com/xbwwj">@xbwwj</a>, <a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/47623">#47623</a>), while sending click events and keyboard actions uses fewer delays (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/48066">#48066</a>).</p>
<p>There are more useful error messages for methods on <strong>Document</strong> (<a href="https://github.com/eachra-bawn">@eachra-bawn</a>, <a href="https://github.com/servo/servo/pull/47835">#47835</a>) and <strong>CSS</strong>-related interfaces (<a href="https://github.com/eachra-bawn">@eachra-bawn</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47746">#47746</a>).</p>
<p>We upgraded our <a href="https://crates.io/crates/stylo">stylo</a> dependency, which improves compatibility with <strong>contrast-color()</strong>, <strong>color-mix()</strong>, <strong>vertical-align</strong>, <strong>list-style</strong>, <strong>place-items</strong>, <strong>at-rule()</strong>, <strong>calc()</strong>, <strong>alpha()</strong>, <strong>attr()</strong>, <strong>content: attr()</strong>, and <strong>named-feature()</strong> (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/46987">#46987</a>, <a href="https://github.com/servo/servo/pull/47942">#47942</a>).</p>
<p>We also fixed bugs related to <strong>visibilityState</strong> on <strong>Document</strong> (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/47908">#47908</a>), <strong>containsNode()</strong> on <strong>Selection</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47938">#47938</a>), <strong>setKeyframes</strong> on <strong>KeyframeEffect</strong> (<a href="https://github.com/simonwuelker">@simonwuelker</a>, <a href="https://github.com/servo/servo/pull/48103">#48103</a>), selections when focusing a text input (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48107">#48107</a>), <strong>AudioParam</strong> clamping and automation (<a href="https://github.com/kevlu93">@kevlu93</a>, <a href="https://github.com/servo/servo/pull/48351">#48351</a>, <a href="https://github.com/servo/servo/pull/48347">#48347</a>), <strong>PannerNode</strong> outputs (<a href="https://github.com/kevlu93">@kevlu93</a>, <a href="https://github.com/servo/servo/pull/48510">#48510</a>), the <strong>muted</strong> attribute on <strong>HTMLMediaElement</strong> (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48403">#48403</a>), placeholders in text inputs (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47761">#47761</a>, <a href="https://github.com/servo/servo/pull/47797">#47797</a>), animations when modifying document stylesheets (<a href="https://github.com/SharanRP">@SharanRP</a>, <a href="https://github.com/servo/servo/pull/48000">#48000</a>), gradient color stops (<a href="https://github.com/BudiArb">@BudiArb</a>, <a href="https://github.com/servo/servo/pull/48288">#48288</a>), sticky table rows (<a href="https://github.com/TTyChud">@TTyChud</a>, <a href="https://github.com/servo/servo/pull/48380">#48380</a>), <strong>::first-letter</strong> (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/48307">#48307</a>), <strong>text-wrap-mode</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48469">#48469</a>), OTF fonts (<a href="https://github.com/wood-ghost">@wood-ghost</a>, <a href="https://github.com/servo/servo/pull/47904">#47904</a>), CSS and nosniff (<a href="https://github.com/sahvx655-wq">@sahvx655-wq</a>, <a href="https://github.com/servo/servo/pull/45481">#45481</a>), <strong>Sec-Fetch-</strong> headers and redirects (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48203">#48203</a>), <strong>moveBefore()</strong> on <strong>Node</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47692">#47692</a>), <strong>supports()</strong> on <strong>WebCrypto</strong> (<a href="https://github.com/kkoyung">@kkoyung</a>, <a href="https://github.com/servo/servo/pull/47768">#47768</a>, <a href="https://github.com/servo/servo/pull/47891">#47891</a>, <a href="https://github.com/servo/servo/pull/47953">#47953</a>, <a href="https://github.com/servo/servo/pull/47984">#47984</a>, <a href="https://github.com/servo/servo/pull/48410">#48410</a>, <a href="https://github.com/servo/servo/pull/47545">#47545</a>), cross-origin windows (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47632">#47632</a>, <a href="https://github.com/servo/servo/pull/48411">#48411</a>, <a href="https://github.com/servo/servo/pull/48038">#48038</a>), origins of <code>about:blank</code> and <code>about:srcdoc</code> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47630">#47630</a>), <code>keypress</code> events (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/48324">#48324</a>), text and media documents (<a href="https://github.com/SilvioPilato">@SilvioPilato</a>, <a href="https://github.com/servo/servo/pull/47823">#47823</a>), <strong>body()</strong> on <strong>Response</strong> (<a href="https://github.com/TTyChud">@TTyChud</a>, <a href="https://github.com/servo/servo/pull/48409">#48409</a>), <code>&lt;details&gt;</code> with <code>&lt;summary&gt;</code> (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/48224">#48224</a>), editing hidden inputs (<a href="https://github.com/dzfrias">@dzfrias</a>, <a href="https://github.com/servo/servo/pull/48165">#48165</a>), attribute nodes in XPath (<a href="https://github.com/leowatts">@leowatts</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47912">#47912</a>), absolutely positioned boxes (<a href="https://github.com/mxmgorin">@mxmgorin</a>, <a href="https://github.com/servo/servo/pull/48081">#48081</a>), CSS Grid containers with absolutely positioned nodes (<a href="https://github.com/nicoburns">@nicoburns</a>, <a href="https://github.com/servo/servo/pull/47519">#47519</a>), <strong>WebDriver</strong> wheel/pointer actions (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/48143">#48143</a>), and <strong>blob:</strong> URLs (<a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/servo/servo/pull/47910">#47910</a>).</p>
<h3>New contributors <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#new-contributors">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>A special thanks to the following people for landing their first patch in Servo:</p>
<ul>
<li>Arnau Camprubí (<a href="https://github.com/Arnau478">@Arnau478</a>, <a href="https://github.com/servo/servo/pull/47726">#47726</a>)</li>
<li>Silvio Pilato (<a href="https://github.com/SilvioPilato">@SilvioPilato</a>, <a href="https://github.com/servo/servo/pull/47786">#47786</a>)</li>
<li>Radeonares32 (<a href="https://github.com/Radeonares32">@Radeonares32</a>, <a href="https://github.com/servo/servo/pull/47651">#47651</a>)</li>
<li>derdilla (<a href="https://github.com/derdilla">@derdilla</a>, <a href="https://github.com/servo/servo/pull/47828">#47828</a>)</li>
<li>pr3pony (<a href="https://github.com/pr3pony">@pr3pony</a>, <a href="https://github.com/servo/servo/pull/48030">#48030</a>)</li>
<li>Mario (<a href="https://github.com/Fatcat560">@Fatcat560</a>, <a href="https://github.com/servo/servo/pull/47629">#47629</a>)</li>
<li>TtyChud (<a href="https://github.com/TTyChud">@TTyChud</a>, <a href="https://github.com/servo/servo/pull/48228">#48228</a>)</li>
<li>Devrate Kuntal (<a href="https://github.com/kuntal-devrat">@kuntal-devrat</a>, <a href="https://github.com/servo/servo/pull/48247">#48247</a>)</li>
<li>Diego Frias (<a href="https://github.com/dzfrias">@dzfrias</a>, <a href="https://github.com/servo/servo/pull/48025">#48025</a>)</li>
<li>LiamillionSS (<a href="https://github.com/LiamillionSS">@LiamillionSS</a>, <a href="https://github.com/servo/servo/pull/48424">#48424</a>)</li>
</ul>
<p>Interested in helping build a web browser?
Take a look at our <a href="https://starters.servo.org/">curated list</a> of issues that are good for new contributors!</p>
<h3>Donations <a class="header-anchor" href="https://servo.org/blog/2026/11/05/september-in-servo/#donations">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>Thanks again for your generous support!
We are now receiving <strong>8144 USD/month</strong> (+1% from August) in recurring donations.
This helps us cover the cost of our <strong><a href="https://ci0.servo.org/">speedy</a> <a href="https://ci1.servo.org/">CI</a> <a href="https://ci2.servo.org/">and</a> <a href="https://ci3.servo.org/">benchmarking</a> <a href="https://ci4.servo.org/">servers</a></strong>, one of our latest <strong><a href="https://www.outreachy.org/alums/2026-05/#:~:text=Servo">Outreachy interns</a></strong>, and funding <strong><a href="https://servo.org/blog/2026/09/15/one-year-of-sponsorship/">maintainer work</a></strong> that helps more people contribute to Servo.</p>
<p>Servo is also on <a href="https://thanks.dev/">thanks.dev</a>, and already <strong>37 GitHub users</strong> (+1 from August) that depend on Servo are sponsoring us there.
If you use Servo libraries like <a href="https://crates.io/crates/url/reverse_dependencies">url</a>, <a href="https://crates.io/crates/html5ever/reverse_dependencies">html5ever</a>, <a href="https://crates.io/crates/selectors/reverse_dependencies">selectors</a>, or <a href="https://crates.io/crates/cssparser/reverse_dependencies">cssparser</a>, signing up for <a href="https://thanks.dev/">thanks.dev</a> could be a good way for you (or your employer) to give back to the community.</p>
<p>We now have <a href="https://servo.org/blog/2025/11/21/sponsorship-tiers/"><strong>sponsorship tiers</strong></a> that allow you or your organisation to donate to the Servo project with public acknowlegement of your support.
If you’re interested in this kind of sponsorship, please contact us at <a href="mailto:join@servo.org">join@servo.org</a>.</p>
<figure class="_fig" style="width: 100%; margin: 1em 0;"><div class="_flex">
    <div style="text-align: right;">
        <div><strong>8128</strong> USD/month</div>
        <div/>
        <div/>
        <div style="padding-right: 1em;"><strong>10000</strong></div>
    </div>
    <progress max="10000" value="7824"/>
</div></figure>
<p>Use of donations is decided transparently via the Technical Steering Committee’s public <strong><a href="https://github.com/servo/project/blob/main/FUNDING_REQUEST.md">funding request process</a></strong>, and active proposals are tracked in <a href="https://github.com/servo/project/issues/187">servo/project#187</a>.
For more details, head to our <a href="https://servo.org/sponsorship/">Sponsorship page</a>.</p></div>
    </content>
    <updated>2026-11-05T00:00:00Z</updated>
    <source>
      <id>https://servo.org</id>
      <author>
        <name>Servo Team</name>
        <email>info@servo.org</email>
      </author>
      <link href="https://servo.org/blog/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://servo.org" rel="alternate" type="text/html"/>
      <subtitle>All the entries in the Servo blog.</subtitle>
      <title>Servo Blog</title>
      <updated>2026-11-05T00:00:00Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-150080</id>
    <link href="https://discourse.mozilla.org/t/firefox-profiler-deployment-november-4-2026/150080" rel="alternate" type="text/html"/>
    <title>Firefox Profiler Deployment (November 4, 2026)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The latest version of the <a href="https://profiler.firefox.com/" rel="noopener nofollow ugc">Firefox Profiler</a> is now live! Check out the full changelog below to see what’s changed:</p>
<p><strong>Changes:</strong></p>
<ul>
<li>[Markus Stange] Some FlameGraph changes, for the function list flame graphs (<a href="https://github.com/firefox-devtools/profiler/pull/6402" rel="noopener nofollow ugc">#6402</a>)</li>
<li>[Markus Stange] Match source-mapped original filenames in call tree search (<a href="https://github.com/firefox-devtools/profiler/pull/6431" rel="noopener nofollow ugc">#6431</a>)</li>
<li>[fatadel] Automate production deployments (<a href="https://github.com/firefox-devtools/profiler/pull/6304" rel="noopener nofollow ugc">#6304</a>)</li>
<li>[Markus Stange] Fix source map symbolication in the presence of path collisions (<a href="https://github.com/firefox-devtools/profiler/pull/6432" rel="noopener nofollow ugc">#6432</a>)</li>
<li>[Markus Stange] Apply the 30s timeout to CLI integration tests (<a href="https://github.com/firefox-devtools/profiler/pull/6434" rel="noopener nofollow ugc">#6434</a>)</li>
<li>[Nazım Can Altınova] Add functionality to profiler-edit to merge two profiles, one with samples and one with markers (<a href="https://github.com/firefox-devtools/profiler/pull/5448" rel="noopener nofollow ugc">#5448</a>)</li>
<li>[fatadel] Bump profiler-cli version to 0.13.0 (<a href="https://github.com/firefox-devtools/profiler/pull/6440" rel="noopener nofollow ugc">#6440</a>)</li>
</ul>
<p>Find out more about the Firefox Profiler on <a href="https://profiler.firefox.com" rel="noopener nofollow ugc">profiler.firefox.com</a>! If you have any questions, join the discussion on our <a href="https://chat.mozilla.org/#/room/#profiler:mozilla.org" rel="noopener nofollow ugc">Matrix channel</a>!</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/firefox-profiler-deployment-november-4-2026/150080">Read full topic</a></p></div>
    </summary>
    <updated>2026-11-04T13:13:40Z</updated>
    <published>2026-11-04T13:13:40Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>fatadel</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/firefox-profiler-deployment-november-4-2026/150080.rss" title="Firefox Profiler Deployment (November 4, 2026)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry>
    <id>tag:this-week-in-rust.org,2026-11-04:/blog/2026/11/04/this-week-in-rust-676/</id>
    <link href="https://this-week-in-rust.org/blog/2026/11/04/this-week-in-rust-676/" rel="alternate" type="text/html"/>
    <title>This Week in Rust 676</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello and welcome to another issue of <em>This Week in Rust</em>!
<a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
This is a weekly summary of its progress and community.
Want something mentioned? Tag us at
<a href="https://bsky.app/profile/thisweekinrust.bsky.social">@thisweekinrust.bsky.social</a> on Bluesky or
<a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social …</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello and welcome to another issue of <em>This Week in Rust</em>!
<a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
This is a weekly summary of its progress and community.
Want something mentioned? Tag us at
<a href="https://bsky.app/profile/thisweekinrust.bsky.social">@thisweekinrust.bsky.social</a> on Bluesky or
<a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social, or
<a href="https://github.com/rust-lang/this-week-in-rust">send us a pull request</a>.
Want to get involved? <a href="https://github.com/rust-lang/rust/blob/main/CONTRIBUTING.md">We love contributions</a>.</p>
<p><em>This Week in Rust</em> is openly developed <a href="https://github.com/rust-lang/this-week-in-rust">on GitHub</a> and archives can be viewed at <a href="https://this-week-in-rust.org/">this-week-in-rust.org</a>.
If you find any errors in this week's issue, <a href="https://github.com/rust-lang/this-week-in-rust/pulls">please submit a PR</a>.</p>
<p>Want TWIR in your inbox? <a href="https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&amp;id=0ed8b72485">Subscribe here</a>.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#updates-from-rust-community">Updates from Rust Community</a></h4>


<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#official">Official</a></h5>
<ul>
<li><a href="https://blog.rust-lang.org/inside-rust/2026/11/02/maintainer-spotlight-anthony-bolden-walnut356/">Maintainer spotlight: Anthony Bolden (@Walnut356)</a></li>
<li><a href="https://blog.rust-lang.org/2026/11/03/Rustup-1.29.3/">Announcing rustup 1.29.3</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#foundation">Foundation</a></h5>
<ul>
<li><a href="https://rustfoundation.org/media/update-on-rust-foundation-staffing/">Update on Rust Foundation Staffing</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#newsletters">Newsletters</a></h5>
<ul>
<li><a href="https://rust-trends.com/newsletter/systemd-opens-the-door-to-rust/">Rust Trends Issue 86 - systemd Opens the Door to Rust</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#projecttooling-updates">Project/Tooling Updates</a></h5>


<ul>
<li><a href="https://amutable.com/blog/systemd-loves-rust">systemd ❤️ Rust</a></li>
<li><a href="https://blog.guillaume-gomez.fr/articles/2026-10-30+sysinfo%3A+fixing+performance+to+retrieve+process+GPU+usage">sysinfo: fixing performance to retrieve process GPU usage</a></li>
<li><a href="https://m-compressors.github.io/2026/formal-verification-mbrotli-mzstd/">Towards formal verification: mbrotli and mzstd</a></li>
<li><a href="https://ruffle.rs/blog/2026/11/04/stable-releases-and-everything-else">Ruffle: Stable Releases, API, Text... and Everything Else!</a></li>
<li><a href="https://blog.antoyo.xyz/rustc_codegen_gcc-progress-report-44">Progress Report #44: rustc_codegen_gcc can now bootstrap rustc on Aarch64!</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#observationsthoughts">Observations/Thoughts</a></h5>
<ul>
<li><a href="https://corrode.dev/blog/thinking-in-traits/">Thinking in Traits</a></li>
<li><a href="https://nnethercote.github.io/2026/11/04/how-to-speed-up-the-rust-compiler-in-november-2026.html">How to speed up the Rust compiler in November 2026</a></li>
<li><a href="https://pivotlake.io/blog/its-the-memory-latency-stupid/">It's the memory latency, stupid · Pivot blog</a></li>
<li><a href="https://blog.yoshuawuyts.com/the-future-trait-has-a-missing-state">The Missing Future State</a></li>
<li><a href="https://kerkour.com/secure-rust-projects">Everything you need to know to secure your Rust projects against the wave of cyberattacks</a></li>
<li>[audio] <a href="https://netstack.fm/episodes/small-crates-behind-big-rust-systems">Small Crates Behind Big Rust Systems</a></li>
<li>[audio] <a href="https://rustacean-station.org/episode/jonas-kruckenberg/">Migrating C to Rust with Jonas Kruckenberg</a></li>
<li><a href="https://delta.dev/blog/fine-grained-version-control-for-agents">Building fine-grained version control for agents with Rust and Durable Objects</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-walkthroughs">Rust Walkthroughs</a></h5>
<ul>
<li>[series] <a href="https://kapteko.com/userland-linux-scheduler-in-rust/">Userland Linux scheduler in Rust - faster than time</a></li>
<li><a href="https://medium.com/@potto_94870/who-are-you-versus-who-owns-you-what-rust-memory-safety-and-wireless-addressing-have-in-common-b876a81468d5">Who Are You? versus Who Owns You? — What Rust Memory Safety and Wireless Addressing Have in Common</a></li>
<li>[video] <a href="https://www.youtube.com/watch?v=R8IeTvTHlxU">Rust Atomics Demystified</a></li>
<li>[video] <a href="https://www.youtube.com/watch?v=X5Bf_Udenys">Fix Your Rust Functions</a></li>
</ul>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#crate-of-the-week">Crate of the Week</a></h4>
<p>This week's crate is <a href="https://crates.io/crates/tellus">tellus</a>, a tokio-based actor framework that can be used without writing async code.</p>
<p>Thanks to <a href="https://users.rust-lang.org/t/crate-of-the-week/2704/1708">Sean Kwak</a> for the partial-self-suggestion!</p>
<p><a href="https://users.rust-lang.org/t/crate-of-the-week/2704">Please submit your suggestions and votes for next week</a>!</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#calls-for-testing">Calls for Testing</a></h4>
<p>An important step for RFC implementation is for people to experiment with the
implementation and give feedback, especially before stabilization.</p>
<p>If you are a feature implementer and would like your RFC to appear in this list, add a
<code>call-for-testing</code> label to your RFC along with a comment providing testing instructions and/or
guidance on which aspect(s) of the feature need testing.</p>
<p><em>No calls for testing were issued this week by
<a href="https://github.com/rust-lang/rust/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Rust</a>,
<a href="https://github.com/rust-lang/cargo/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Cargo</a>,
<a href="https://github.com/rust-lang/rustup/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Rustup</a> or
<a href="https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing%20state%3Aopen">Rust language RFCs</a>.</em></p>
<p><a href="https://github.com/rust-lang/this-week-in-rust/issues">Let us know</a> if you would like your feature to be tracked as a part of this list.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers">Call for Participation; projects and speakers</a></h4>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cfp-projects">CFP - Projects</a></h5>
<p>Always wanted to contribute to open-source projects but did not know where to start?
Every week we highlight some tasks from the Rust community for you to pick and get started!</p>
<p>Some of these tasks may also have mentors available, visit the task page for more information.</p>



<ul>
<li><a href="https://github.com/Ramesh-35/invar/issues/2">INVAR - Turn the HELLTEST hostile-input probes into committed regression tests</a></li>
<li><a href="https://github.com/endlessGold/Plastor/issues/6">Plastor - Port the tracing step from Python to Rust</a></li>
<li><a href="https://github.com/endlessGold/Plastor/issues/2">Plastor - Read depth from tone bands and cross-contours (fix flat heads on real drawings)</a></li>
<li><a href="https://github.com/endlessGold/Plastor/issues/8">Plastor - CI: build and run the Blender-free checks on Linux, macOS and Windows</a></li>
<li><a href="https://github.com/endlessGold/Plastor/issues/10">Plastor - <code>mh score</code>: report watertight and Euler characteristic</a></li>
<li><a href="https://github.com/shinycake/quill/issues/1351">Quill - Show the service message for chats started through a free messages link</a></li>
<li><a href="https://github.com/shinycake/quill/issues/1352">Quill - Apply the free messages token when opening a link that carries one</a></li>
<li><a href="https://github.com/shinycake/quill/issues/1353">Quill - Try Quill on real Windows and Linux machines and report what breaks</a></li>
</ul>
<p>If you are a Rust project owner and are looking for contributors, please submit tasks <a href="https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines">here</a> or through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a> or by reaching out on <a href="https://bsky.app/profile/thisweekinrust.bsky.social">Bluesky</a> or <a href="https://mastodon.social/@thisweekinrust">Mastodon</a>!</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cfp-events">CFP - Events</a></h5>
<p>Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.</p>


<ul>
<li><a href="https://rust-fosdem.github.io/">**FOSDEM'27 Rust Devroom</a> | 2026-11-20 23:59 CET | Brussels, Belgium | 2027-01-31</li>
</ul>
<p>If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a> or by reaching out on <a href="https://bsky.app/profile/thisweekinrust.bsky.social">Bluesky</a> or <a href="https://mastodon.social/@thisweekinrust">Mastodon</a>!</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#updates-from-the-rust-project">Updates from the Rust Project</a></h4>
<p>597 pull requests were <a href="https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2026-10-27..2026-11-03">merged in the last week</a></p>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#compiler">Compiler</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/165184">GCI: check where-clauses of associated constants for well-formedness</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163359">MIR move elimination (1.5/6): Ensure ZSTs are always initialized</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163339">MIR move elimination (5/6): Storage reconstruction</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/161131">check associated const binding types</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164607">destringlyfy lint infrastructure</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164341">expand an early return case in <code>coerce_unsized</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164234">new solver opts for <code>diesel</code> (part 2)</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165160">new solver opts for diesel (part 3)</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164726">perf: emit field names as a concatenated string in <code>derive(Debug)</code> for structs</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#library">Library</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/165214">add <code>MaybeUninit::from_ref</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165248">add {<code>Receiver</code>, <code>Sender</code>, <code>SyncSender</code>}<code>::</code>{<code>is_empty,len</code>}</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164848">add <code>strict_</code> methods to <code>NonZero</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165103">add <code>TrySendError::into_inner</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164608">core: constify <code>resumable_breakpoint</code> and re-export it in <code>std</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165284">ensure the display impl of uXX is small with <code>optimize_for_size</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165181">implement <code>Duration::display_seconds</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/160186">implement <code>Fn</code> traits for safe functions of any ABI</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164155">implement <code>Vec::retain_unstable</code> ACP</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/165132">implement <code>advance_back_by</code> on <code>Fuse</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/144090">make <code>IoSlice</code> and <code>IoSliceMut</code> methods unstably const</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163525">move lang item collection to the resolver</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163757">specialize vec <code>extend_with</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162754">optimize large elements for slice rotating</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cargo">Cargo</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/cargo/pull/17623">windows: Delay-load system DLLs that most commands don't use</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17660">fix manifest schema generation: <code>TomlOptLevel</code> and <code>StringOrVec</code></a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17641">warn about conflicting proc-macro manifest settings</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustdoc">Rustdoc</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/138143">add unstable option <code>--crate-list-heading</code> to customize the sidebar crate list</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162916">improve <code>ItemKind</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/160370">notable trait badge and popover enhancements</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustfmt">Rustfmt</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7214">have <code>cfg_select!</code> double-brace concise formatting respect <code>control_brace_style</code></a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#clippy">Clippy</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17051">don't report missing safety doc for <code>#[target_feature(enable)]</code> attributed functions</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17941">fix ICE in <code>arbitrary_source_item_ordering</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17950">fix <code>assert_is_empty</code> false positive with constant context</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17794">fix <code>borrowed_box</code> suggestion for trait objects to mention <code>.as_ref()</code> at call sites</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17741">fix <code>manual_inspect</code> suggestions for mutating closures</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17963">fix: signed abs rounding error in remainder identity check</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-analyzer">Rust-Analyzer</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23602">fix LSP panic on unbound function when generics are present</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23586">fix lowering of <code>yield</code> in <code>async gen</code></a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23562">fix: suggest reference after dereferences</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23495">panic <code>Expr not in lookup</code> due to projection types</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23228">perf: provide <code>ThinMap</code>, a map that uses <code>ThinVec</code> when the length is small</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage">Rust Compiler Performance Triage</a></h5>
<p>This week a 0.4% increase in instructions is traded for a 33% reduction in <code>rmeta</code> size on some real benchmarks.
Even with that regression, this week's average is still very positive thanks to a refactoring around <code>AttrTokenStream</code>,
by using <code>Symbol</code>s instead of <code>String</code>s in the lint infrastructure,
and by avoiding an extra AST walk for lang item collection, among other things.
A lot of noise this week, which is mostly caused by two large rollups whose base PR was noise.</p>
<p>Triage done by <strong>@JonathanBrouwer</strong>.
Revision range: <a href="https://perf.rust-lang.org/?start=019b59d8101bb3e141f1b880684747b4217beeb6&amp;end=4c46afa63688fb473618f9b3553d70b0c15a88eb&amp;absolute=false&amp;stat=instructions%3Au">019b59d8..4c46afa6</a></p>
<p>3 Regressions, 11 Improvements, 27 Mixed; 2 of them in rollups
195 artifact comparisons made in total</p>
<p><a href="https://github.com/rust-lang/rustc-perf/blob/87c69dbbcdc5f571ebe50dc0107c846b6a102422/triage/2026/2026-11-02.md">Full report here</a></p>


<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#approved-rfcs"/><a href="https://github.com/rust-lang/rfcs/commits/main">Approved RFCs</a></h5>
<p>Changes to Rust follow the Rust <a href="https://github.com/rust-lang/rfcs#rust-rfcs">RFC (request for comments) process</a>. These
are the RFCs that were approved for implementation this week:</p>
<ul>
<li><a href="https://github.com/rust-lang/rfcs/pull/4013">RFC: Add <code>required-targets</code> for workspace package selection</a></li>
<li><a href="https://github.com/rust-lang/rfcs/pull/4026">Update actions/deploy-pages action to v5.0.1</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#final-comment-period">Final Comment Period</a></h5>
<p>Every week, <a href="https://www.rust-lang.org/team.html">the team</a> announces the 'final comment period' for RFCs and key PRs
which are reaching a decision. Express your opinions now.</p>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#tracking-issues-prs">Tracking Issues &amp; PRs</a></h6>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust"/><a href="https://github.com/rust-lang/rust/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Rust</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/164582">Properly feature gate doc(rust_logo)</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164731">core: Stabilize <code>abort_immediate</code> as <code>crash</code></a></li>
</ul>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#compiler-team-mcps-only"/><a href="https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20label%3Afinal-comment-period%20state%3Aopen">Compiler Team</a> <a href="https://forge.rust-lang.org/compiler/mcp.html">(MCPs only)</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/compiler-team/issues/1047">Add bootstrap tool to analyze compiler tests code coverage</a></li>
<li><a href="https://github.com/rust-lang/compiler-team/issues/1004">Add testing for lint machinery at runtime</a></li>
</ul>
<p><em>No Items entered Final Comment Period this week for
<a href="https://github.com/rust-lang/rfcs/issues?q=state%3Aopen%20label%3Afinal-comment-period%20state%3Aopen">Rust RFCs</a>,
<a href="https://github.com/rust-lang/cargo/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Cargo</a>,
<a href="https://github.com/rust-lang/lang-team/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Language Team</a>,
<a href="https://github.com/rust-lang/reference/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Language Reference</a>,
<a href="https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period%20state%3Aopen">Leadership Council</a> or
<a href="https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Unsafe Code Guidelines</a>.</em>
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#new-and-updated-rfcs"/><a href="https://github.com/rust-lang/rfcs/pulls">New and Updated RFCs</a></h5>
<ul>
<li><a href="https://github.com/rust-lang/rfcs/pull/4027">Crate list heading RFC</a></li>
</ul>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#upcoming-events">Upcoming Events</a></h4>
<p>Rusty Events between 2026-11-04 - 2026-12-02 🦀</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#virtual">Virtual</a></h5>
<ul>
<li>2026-11-04 | Virtual (Indianapolis, IN, US) | <a href="https://www.meetup.com/indyrs">Indy Rust</a><ul>
<li><a href="https://www.meetup.com/indyrs/events/wqzhftyjcpbgb/"><strong>Indy.rs - with Social Distancing</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Virtual (Berlin, DE) | <a href="https://www.meetup.com/rust-berlin">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/316907780/"><strong>Rust Hack and Learn</strong></a></li>
</ul>
</li>
<li>2026-11-10 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/310254770/"><strong>Second Tuesday</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Virtual (Nürnberg, DE) | <a href="https://www.meetup.com/rust-noris">Rust Nuremberg</a><ul>
<li><a href="https://www.meetup.com/rust-noris/events/315619619/"><strong>Rust Nürnberg online</strong></a></li>
</ul>
</li>
<li>2026-11-15 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/omlooqv8"><strong>Cursed Rust</strong></a></li>
</ul>
</li>
<li>2026-11-15 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/316563020/"><strong>Rust Deep Learning: Third Sunday</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/2qfai4a8"><strong>Miscompilation in Rust 1.97</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/315719313/"><strong>Lunch &amp; Learn: The Harness Wore a Trenchcoat - Building a Rust MCP Server</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual (Washington, DC, US) | <a href="https://www.meetup.com/rustdc">Rust DC</a><ul>
<li><a href="https://www.meetup.com/rustdc/events/fhvsztyjcpbwb/"><strong>Mid-month Rustful</strong></a></li>
</ul>
</li>
<li>2026-11-18 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210234/"><strong>Writing a firmware for Xteink ereader in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-19 | Virtual (Berlin, DE) | <a href="https://www.meetup.com/rust-berlin/events/">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/316907781/"><strong>Rust Hack and Learn</strong></a></li>
</ul>
</li>
<li>2026-11-24 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/events/">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/310254769/"><strong>Fourth Tuesday Rust Bookclub</strong></a></li>
</ul>
</li>
<li>2026-12-01 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust/events/">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/316993134/"><strong>Christmas Coding Challenge - Kick Off!</strong></a></li>
</ul>
</li>
<li>2026-12-02 | Virtual (Indianapolis, IN, US) | <a href="https://www.meetup.com/indyrs/events/">Indy Rust</a><ul>
<li><a href="https://www.meetup.com/indyrs/events/wqzhftyjcqbdb/"><strong>Indy.rs - with Social Distancing</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#asia">Asia</a></h5>
<ul>
<li>2026-11-14 | Bengaluru, IN | <a href="https://hasgeek.com/rustbangalore/">Rust Bangalore</a><ul>
<li><a href="https://hasgeek.com/rustbangalore/november-2026-rustacean-meetup/"><strong>November 2026 Rustacean Meetup</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#europe">Europe</a></h5>
<ul>
<li>2026-11-04 | Dublin, IE | <a href="https://www.meetup.com/rust-dublin">Rust Dublin</a><ul>
<li><a href="https://www.meetup.com/rust-dublin/events/316898325/"><strong>Rust 263: Getting Started with the New Rust Driver for Oracle AI Database</strong></a></li>
</ul>
</li>
<li>2026-11-04 | Köln, DE | <a href="https://www.meetup.com/rust-cologne-bonn/events/">Rust Cologne</a><ul>
<li><a href="https://www.meetup.com/rustcologne/events/317183850/"><strong>Rust in November: std discovery tour</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Milano, IT | <a href="https://www.meetup.com/rust-language-milano">Rust Language Milan</a><ul>
<li><a href="https://www.meetup.com/rust-language-milan/events/316213872/"><strong>Digital Model Trains &amp; Rust: Bare-Metal DCC Command Station on ESP32</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Oxford, UK | <a href="https://www.meetup.com/oxford-rust-meetup-group/events/">Oxford ACCU/Rust Meetup.</a><ul>
<li><a href="https://www.meetup.com/oxford-rust-meetup-group/events/317158298/"><strong>Epitome of synaptic excellence</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Frankfurt, DE | <a href="https://www.meetup.com/rust-rhein-main/events/">Rust Rhein-Main</a><ul>
<li><a href="https://www.meetup.com/rust-rhein-main/events/317175844/"><strong>Debugging in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Geneva, CH | <a href="https://www.posttenebraslab.ch/wiki/events/monthly_meeting/rust_meetup">Rust Geneva</a><ul>
<li><a href="https://www.posttenebraslab.ch/wiki/events/monthly_meeting/rust_meetup"><strong>Rust Meetup Geneva</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Milano, MI, IT | <a href="https://www.meetup.com/rust-language-milano/events/">Rust Language Milan</a><ul>
<li><a href="https://www.meetup.com/rust-language-milan/events/317094800/"><strong>From Curiosity to Capability: Build Your Own Device Swarm</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Leipzig, DE | <a href="https://www.meetup.com/rust-modern-systems-programming-in-leipzig">Rust - Modern Systems Programming in Leipzig</a><ul>
<li><a href="https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/313816501/"><strong>Everlock: Everything Is Git, Protocols Are Just Adapters</strong></a></li>
</ul>
</li>
<li>2026-11-19 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus/events/">Rust Aarhus</a><ul>
<li><a href="https://www.meetup.com/rust-aarhus/events/316938696/"><strong>Talk Night at EIVA</strong></a></li>
</ul>
</li>
<li>2026-11-19 | Bergen, NO | <a href="https://www.meetup.com/bergen-rust-new-technology/events/">Rust Bergen</a><ul>
<li><a href="https://www.meetup.com/de-de/bergen-rust-new-technology/events/317045463/"><strong>Rust: FFI with C++, and Intro to Async</strong></a></li>
</ul>
</li>
<li>2026-11-20 and 2026-11-21 | Augsburg, DE | <a href="https://rust-augsburg.github.io/meetup">Rust Meetup Augsburg</a><ul>
<li><a href="https://my.tuxedocomputers.com/event/embedded-rust-mit-embassy-workshop-und-projekttag-28/register"><strong>Embedded Rust mit Embassy - Workshop und Projekttag</strong></a></li>
</ul>
</li>
<li>2026-11-26 | Copenhagen, DK | <a href="https://www.meetup.com/copenhagen-rust-community/events/">Copenhagen Rust Community</a><ul>
<li><a href="https://www.meetup.com/copenhagen-rust-community/events/317181792/"><strong>Rust meetup #73 sponsored by Adapt!</strong></a></li>
</ul>
</li>
<li>2026-11-26 | London, UK | <a href="https://www.meetup.com/rust-london-user-group/events/">Rust London User Group</a><ul>
<li><a href="https://www.meetup.com/rust-london-user-group/events/317253958/"><strong>Rust London x Zed</strong></a></li>
</ul>
</li>
<li>2026-11-26 | Manchester, UK | <a href="https://www.meetup.com/rust-manchester/events/">Rust Manchester</a><ul>
<li><a href="https://www.meetup.com/rust-manchester/events/317222338/"><strong>Rust Manchester November Code Night</strong></a></li>
</ul>
</li>
<li>2026-11-26 | Stockholm, SE | <a href="https://www.meetup.com/stockholm-rust/events/">Stockholm Rust</a><ul>
<li><a href="https://www.meetup.com/stockholm-rust/events/317161063/"><strong>Rust Meetup @Lovable</strong></a></li>
</ul>
</li>
<li>2026-12-01 | Paris, FR | <a href="https://www.meetup.com/rust-paris/events/">Rust Paris</a><ul>
<li><a href="https://www.meetup.com/rust-paris/events/316865676/"><strong>Rust meetup #90</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#north-america">North America</a></h5>
<ul>
<li>2026-11-05 | Montréal, CA | <a href="https://www.meetup.com/rust-montreal">Rust Montréal</a><ul>
<li><a href="https://www.meetup.com/rust-montreal/events/316919004/"><strong>November Monthly Social</strong></a></li>
</ul>
</li>
<li>2026-11-05 | San Francisco, CA | <a href="https://luma.com/user/usr-eWgtha6CHSTma7v/">Rust LA: NVIDIA</a><ul>
<li><a href="https://luma.com/iqe7wng1"><strong>NVIDIA x Lawrence Harvey | CUDA Rust</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Saint Louis, MO, US | <a href="https://www.meetup.com/stl-rust">STL Rust</a><ul>
<li><a href="https://www.meetup.com/stl-rust/events/316896797/"><strong>HTMX and Rust</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Lehi, UT, US | <a href="https://www.meetup.com/utah-rust/events/">Utah Rust</a><ul>
<li><a href="https://www.meetup.com/utah-rust/events/317178211/"><strong>Rust Game Jam</strong></a></li>
</ul>
</li>
<li>2026-11-12 | San Diego, CA, US | <a href="https://www.meetup.com/san-diego-rust">San Diego Rust</a><ul>
<li><a href="https://www.meetup.com/san-diego-rust/events/316886787/"><strong>San Diego Rust November Meetup - Back in person!</strong></a></li>
</ul>
</li>
<li>2026-11-14 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924331/"><strong>MIT Rust Lunch, Nov 14</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Los Angeles, CA, US | <a href="https://www.meetup.com/rust-los-angeles">Rust Los Angeles</a><ul>
<li><a href="https://www.meetup.com/rust-los-angeles/events/316859673/"><strong>Rust LA November w/ Hadrian!</strong></a></li>
</ul>
</li>
<li>2026-11-17 | San Francisco, CA, US | <a href="https://www.meetup.com/san-francisco-rust-study-group">San Francisco Rust Study Group</a><ul>
<li><a href="https://www.meetup.com/san-francisco-rust-study-group/events/315783989/"><strong>Rust Hacking in Person</strong></a></li>
</ul>
</li>
<li>2026-11-18 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210234/"><strong>Writing a firmware for Xteink ereader in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-18 | San Francisco, CA, US) | <a href="https://luma.com/bayarearust">Bay Area Rust</a><ul>
<li><a href="https://luma.com/v0mxbgs8"><strong>Bay Area Rust - Social Night</strong></a></li>
</ul>
</li>
<li>2026-11-21 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust/events/">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924366/"><strong>Winter Hill Rust Lunch, Nov 21</strong></a></li>
</ul>
</li>
<li>2026-11-28 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust/events/">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924412/"><strong>South Station Rust Lunch, Nov 28</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#south-america">South America</a></h5>
<ul>
<li>2026-11-07 | Planalto Paulista, BR | <a href="https://www.meetup.com/rust-sao-paulo-meetup">Rust São Paulo Meetup</a><ul>
<li><a href="https://www.meetup.com/rust-sao-paulo-meetup/events/316812852/"><strong>Encontro do Rust-SP - Agora no Luma</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#oceania">Oceania:</a></h5>
<ul>
<li>2026-11-24 | Barton, AU | <a href="https://www.meetup.com/rust-canberra/events/">Canberra Rust User Group</a><ul>
<li><a href="https://www.meetup.com/rust-canberra/events/316907340/"><strong>November Meetup</strong></a></li>
</ul>
</li>
</ul>
<p>If you are running a Rust event please add it to the <a href="https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com">calendar</a> to get
it mentioned here. Please remember to add a link to the event too.
Email the <a href="mailto:community-team@rust-lang.org">Rust Community Team</a> for access.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#jobs">Jobs</a></h4>
<p>Please see the latest <a href="https://www.reddit.com/r/rust/comments/1wzctie/official_rrust_whos_hiring_thread_for_jobseekers/">Who's Hiring thread on r/rust</a></p>
<h3><a class="toclink" href="https://this-week-in-rust.org/atom.xml#quote-of-the-week">Quote of the Week</a></h3>
<blockquote>
<p>Think about how your contributions may be received before you send them. This kind of thought, true thought, with real emotion and reasoning, is the only thing that you, a human, are guaranteed to be able to contribute.</p>
</blockquote>
<p>– <a href="https://users.rust-lang.org/t/tips-for-your-first-pull-request/143356/3">Jubilee on rust-users</a></p>
<p>Thanks to <a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328/1838">Jonas Fassbender</a> for the suggestion!</p>
<p><a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328">Please submit quotes and vote for next week!</a></p>
<p>This Week in Rust is edited by:</p>
<ul>
<li><a href="https://github.com/nellshamrell">nellshamrell</a></li>
<li><a href="https://github.com/llogiq">llogiq</a></li>
<li><a href="https://github.com/ericseppanen">ericseppanen</a></li>
<li><a href="https://github.com/extrawurst">extrawurst</a></li>
<li><a href="https://github.com/U007D">U007D</a></li>
<li><a href="https://github.com/mariannegoldin">mariannegoldin</a></li>
<li><a href="https://github.com/bdillo">bdillo</a></li>
<li><a href="https://github.com/opeolluwa">opeolluwa</a></li>
<li><a href="https://github.com/bnchi">bnchi</a></li>
<li><a href="https://github.com/KannanPalani57">KannanPalani57</a></li>
<li><a href="https://github.com/tzilist">tzilist</a></li>
</ul>
<p><em>Email list hosting is sponsored by <a href="https://foundation.rust-lang.org/">The Rust Foundation</a></em></p>
<p><small><a href="https://www.reddit.com/r/rust/comments/1xo7mbb/this_week_in_rust_676/">Discuss on r/rust</a></small></p></div>
    </content>
    <updated>2026-11-04T05:00:00Z</updated>
    <published>2026-11-04T05:00:00Z</published>
    <category term="This Week in Rust"/>
    <author>
      <name>TWiR Contributors</name>
    </author>
    <source>
      <id>https://this-week-in-rust.org/</id>
      <link href="https://this-week-in-rust.org/" rel="alternate" type="text/html"/>
      <link href="https://this-week-in-rust.org/atom.xml" rel="self" type="application/atom+xml"/>
      <title>This Week in Rust</title>
      <updated>2026-11-11T05:00:00Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-150075</id>
    <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261103-1/150075" rel="alternate" type="text/html"/>
    <title>Happy BMO Push Day! (20261103.1)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://github.com/mozilla-bteam/bmo/tree/release-20261103.1" rel="noopener nofollow ugc">Github Link</a></p>
<p>The following changes have been pushed to <a href="https://bugzilla.mozilla.org">bugzilla.mozilla.org</a>:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2087000">Bug 2087000</a> - Sometimes phab “last modified” timestamp updates without actual changes to the revision</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2081860">Bug 2081860</a> - Migrate Bug REST resource to native Mojo API: bug objects (get, search, create, update, possible_duplicates, history)</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2070239">Bug 2070239</a> - Add DB-backed tests for flag-event bugmail recipient selection (prev-status tie-break, flag-type cc_list)</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2082543">Bug 2082543</a> - Clean up after the REST-to-Mojo migration: shared helpers in Bugzilla::API::V1::Util</li>
</ul>
<p>Discuss these changes in the <a href="https://matrix.to/#/#bmo:mozilla.org" rel="noopener nofollow ugc">BMO Matrix Room</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261103-1/150075">Read full topic</a></p></div>
    </summary>
    <updated>2026-11-03T22:05:48Z</updated>
    <published>2026-11-03T22:05:48Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>dkl1</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261103-1/150075.rss" title="Happy BMO Push Day! (20261103.1)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-150074</id>
    <link href="https://discourse.mozilla.org/t/mozphab-2-24-0-released/150074" rel="alternate" type="text/html"/>
    <title>MozPhab 2.24.0 Released</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Bugs resolved in Moz-Phab 2.24.0:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/2078583">bug 2078583</a> moz-phab reorg --force can fail part way and leave the Phabricator stack tangled</li>
<li><a href="https://bugzilla.mozilla.org/2082342">bug 2082342</a> Move lando warnings knowable at submit time to moz-phab</li>
<li><a href="https://bugzilla.mozilla.org/2086803">bug 2086803</a> Resolve each command’s flags and config into a frozen options object</li>
<li><a href="https://bugzilla.mozilla.org/2087605">bug 2087605</a> moz-phab will break with upcoming jj release 0.47</li>
<li><a href="https://bugzilla.mozilla.org/2087877">bug 2087877</a> Remove <code>args</code> from the VCS layer</li>
<li><a href="https://bugzilla.mozilla.org/2088194">bug 2088194</a> Update hard-coded Lando-dev urls to point to Fastly WAF fronted domains</li>
</ul>
<p>Discuss these changes in <span class="hashtag-raw">#engineering-workflow</span> on Slack or <span class="hashtag-raw">#Conduit</span> Matrix.</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/mozphab-2-24-0-released/150074">Read full topic</a></p></div>
    </summary>
    <updated>2026-11-03T14:49:08Z</updated>
    <published>2026-11-03T14:49:08Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>sheehan</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/mozphab-2-24-0-released/150074.rss" title="MozPhab 2.24.0 Released"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>https://blog.rust-lang.org/2026/11/03/Rustup-1.29.3/</id>
    <link href="https://blog.rust-lang.org/2026/11/03/Rustup-1.29.3/" rel="alternate" title="Announcing rustup 1.29.3" type="text/html"/>
    <title xml:lang="en">Announcing rustup 1.29.3</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><p>The rustup team has published a new point release of rustup, 1.29.3.</p>
<p><a href="https://rustup.rs" rel="external">Rustup</a> is the recommended tool to install <a href="https://www.rust-lang.org" rel="external">Rust</a>, a
programming language that empowers everyone to build reliable and efficient
software.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/11/03/Rustup-1.29.3/#what-s-new-in-rustup-1-29-3"/>
What's new in rustup 1.29.3</h3>
<p>This new patch release has fixed some minor regressions over the previous one:</p>
<ul>
<li>
<p>Fixed "Illegal instruction" error on certain x86_64 CPUs without SSE4.1.
<a href="https://github.com/rust-lang/rustup/pull/5162" rel="external">pr#5162</a></p>
</li>
<li>
<p>Fixed "<code>lock()</code> not supported" error on Solaris. <a href="https://github.com/rust-lang/rustup/pull/5167" rel="external">pr#5167</a></p>
</li>
</ul>
<p>Further details are available in the <a href="https://github.com/rust-lang/rustup/blob/stable/CHANGELOG.md" rel="external">changelog</a>!</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/11/03/Rustup-1.29.3/#how-to-update"/>
How to update</h3>
<p>If you have a previous version of rustup installed, getting the new one is as easy as stopping
any programs which may be using rustup (e.g. closing your IDE) and running:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>$ rustup self update</span></span></code></pre>
<p>Rustup will also automatically update itself at the end of a normal toolchain update:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>$ rustup update</span></span></code></pre>
<p>For this particular release, if you have encountered any issues during
self-update, you may try to update rustup manually by following the steps below:</p>
<ol>
<li><a href="https://rust-lang.github.io/rustup/installation/other.html#manual-installation" rel="external">Download</a> the corresponding <code>rustup-init</code> binary for
your platform.</li>
<li>Make double sure that no other <code>rustup</code> processes are running.</li>
<li>Replace your existing <code>rustup</code> binary with the downloaded <code>rustup-init</code>
renamed to <code>rustup</code>.
<ul>
<li>As a reminder, this binary is often located at <code>$HOME/.cargo/bin/rustup</code>, or
<code>$CARGO_HOME/bin/rustup</code> if you have overridden the <code>$CARGO_HOME</code> environment
variable.</li>
</ul>
</li>
</ol>
<p>If you don't have it already, you can <a href="https://rustup.rs" rel="external">get rustup</a> from the appropriate page on our website.</p>
<p>Rustup's documentation is also available in <a href="https://rust-lang.github.io/rustup/" rel="external">the rustup book</a>.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/11/03/Rustup-1.29.3/#caveats"/>
Caveats</h3>
<p>Rustup releases can come with problems not caused by rustup itself but just due to having a new release.</p>
<p>In particular, anti-malware scanners might block rustup or stop it from creating or copying
files, especially when installing <code>rust-docs</code> which contains many small files.</p>
<p>Issues like this should be automatically resolved in a few weeks when the anti-malware scanners are updated
to be aware of the new rustup release.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/11/03/Rustup-1.29.3/#thanks"/>
Thanks</h3>
<p>Thanks again to all the <a href="https://github.com/rust-lang/rustup/blob/stable/CHANGELOG.md#detailed-changes" rel="external">contributors</a> who made this rustup release possible!</p></div>
    </content>
    <updated>2026-11-03T00:00:00Z</updated>
    <published>2026-11-03T00:00:00Z</published>
    <author>
      <name>The Rustup Team</name>
    </author>
    <source>
      <id>https://blog.rust-lang.org/</id>
      <author>
        <name>Maintained by the Rust Teams.</name>
        <uri>https://github.com/rust-lang/blog.rust-lang.org/</uri>
      </author>
      <link href="https://blog.rust-lang.org/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://blog.rust-lang.org/" rel="alternate" type="text/html"/>
      <subtitle xml:lang="en">Empowering everyone to build reliable and efficient software.</subtitle>
      <title xml:lang="en">Rust Blog</title>
      <updated>2026-11-13T09:01:38Z</updated>
    </source>
  </entry>

  <entry>
    <id>https://attackanddefense.dev/2026/11/02/firefox-security-and-privacy-newsletter-q3</id>
    <link href="https://attackanddefense.dev/2026/11/02/firefox-security-and-privacy-newsletter-q3.html" rel="alternate" title="Firefox Security &amp;amp; Privacy Newsletter 2026 Q3" type="text/html"/>
    <title>Firefox Security &amp; Privacy Newsletter 2026 Q3</title>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Welcome to the Q3 2026 edition of the Firefox Security &amp; Privacy Newsletter.</p>

<p>Security and privacy are core principles of <a href="https://www.mozilla.org/en-US/about/manifesto/">Mozilla’s Manifesto</a> and remain at the heart of Firefox’s development. This edition highlights key initiatives from Q3 2026 across three areas:</p>

<ul>
  <li><strong>Firefox Security:</strong> New security features, platform improvements, hardening efforts, and security integrations in Firefox.</li>
  <li><strong>Firefox Privacy:</strong> New privacy features, enhanced protections, and privacy integrations in Firefox.</li>
  <li><strong>Community Engagement:</strong> Highlights from our security research community and bug bounty program.</li>
</ul>

<h3>Preface</h3>

<p>Note: Some of the bugs linked below might not be accessible to the general public and restricted to specific work groups. <a href="https://firefox-source-docs.mozilla.org/bug-mgmt/processes/fixing-security-bugs.html#keeping-private-information-private">We de-restrict fixed security bugs after a grace-period</a>, until the majority of our user population have received Firefox updates. If a link does not work for you, please accept this as a precaution for the safety of all Firefox users.</p>

<h3>Firefox Security</h3>

<p><strong>Rapid Releases, Now Even Faster:</strong> Since September 2026, Firefox has followed a faster release cycle, bringing improvements, including security fixes, to users more quickly. We also invite you to <a href="https://www.firefox.com/en-US/whatsnext/">see and shape what’s next for Firefox</a>, including upcoming security and privacy features.</p>

<p>Many recent releases have included more <a href="https://www.mozilla.org/security/announce">security fixes</a>. We continue to use frontier LLMs to identify and fix security bugs in Firefox to always keep you safe online. We have also changed how we publish advisories: instead of grouping internally identified memory safety vulnerabilities under a single CVE, we now publish a separate advisory for each bug, anticipating a <a href="https://github.com/CVEProject/cve-documents/issues/47#issuecomment-5587294133">potential change to the CVE Numbering Rules</a>. CVE counts alone are not a reliable measure of security, as software vendors are not required to assign CVEs to vulnerabilities they discover internally.</p>

<p><strong>Know when your TLS is broken:</strong> Starting with Firefox 157, you will see <a href="https://www.firefox.com/en-US/firefox/157.0/releasenotes/">warnings in the site information panel</a> (the shield icon in the address bar) and in Settings when your connection may not be completely private. For example, if an administrator configures your Firefox to record its encryption keys, you will be able to catch that. Recording these keys could allow another software to read all of your encrypted web traffic without your knowledge.</p>

<p><strong>Mozilla Root Store Policy v3.1</strong>: We are strengthening transparency and assurance in the WebPKI with <a href="https://blog.mozilla.org/security/2026/06/29/improving-transparency-and-assurance-in-the-web-pki-mozilla-root-store-policy-v3-1/">Root Store Policy v3.1</a>, which introduces stricter transparency, documentation, and audit requirements for public certificate authorities.</p>

<p><strong>Email Client Spam Prevention:</strong> Firefox now <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=299116">treats mailto: links as popups</a>, requiring explicit user action before opening the email client. This prevents websites from repeatedly opening email composition windows through JavaScript and overwhelming the user.</p>

<p><strong>Restricting Local File Access for Extensions:</strong>  Starting in Firefox 153, <a href="https://blog.mozilla.org/addons/2026/07/23/firefox-153-webextensions-api-updates/">extensions need your explicit permission to access local files</a> through `file://` URLs. Access is off by default for all extensions, including those already installed, so you decide which extensions can access files on your device.</p>

<h3>Firefox Privacy</h3>

<p><strong>Fingerprinting Protections:</strong> Following a <a href="https://blog.laserphile.com/2026/08/aliexpress-webpage-keeping-multipoint.html">report on Alibaba’s use of audio fingerprinting</a>, <a href="https://ritter.vg/blog-webaudio_alibaba.html">Tom Ritter published a data-backed analysis</a> explaining how Firefox’s protections reduce the accuracy of fingerprinting through the Web Audio API. The story received coverage from <a href="https://arstechnica.com/security/2026/08/aliexpress-caught-fingerprinting-visitors-after-sending-inaudible-sounds-to-browsers/">Ars Technica</a>, <a href="https://www.theregister.com/security/2026/08/24/aliexpress-accused-of-fingerprinting-shoppers-with-silent-audio-trick-that-also-muted-a-devs-headphones/5291662">The Register</a>, and others.</p>

<p><strong>Preventing Link Tracking:</strong> Right-clicking a link and selecting <a href="https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings">Copy Clean Link</a> will now strip tracking parameters across arbitrary subdomains, along with 130 additional tracking parameters.</p>

<p><strong>Bringing Containers Directly into Firefox:</strong> Previously available as extension, <a href="https://blog.mozilla.org/en/firefox/firefox-containers-preview/">Firefox 153 introduces built-in Containers</a>, helping you keep work, personal browsing, and other activities separate. Each container maintains its own cookies and login sessions, so you could use containers for multiple accounts on the same site, or to limit online tracking by isolating certain websites in their respective containers. Firefox 155 also adds the ability to reorder containers.</p>

<p><strong>Tracker Blocking Information on Android:</strong> Starting in Firefox 153, the Privacy Dashboard on Android shows which types of trackers Firefox blocks, giving you a clearer view of how Firefox protects your privacy as you browse.</p>

<p><strong>Built-in Ad Blocking to iOS</strong>: Introduced on September 1, <a href="https://blog.mozilla.org/en/firefox/ad-blocker-on-ios/">Firefox’s built-in Ad Blocker on iOS</a> blocks many third-party ads and ad-related trackers, reducing clutter and distractions. It works alongside Enhanced Tracking Protection and can be enabled in the ‘Browsing’ settings in your Firefox on iOS.</p>

<h3>Community Engagement</h3>

<p><strong>Advancing Web Security at Dagstuhl:</strong> Firefox security experts joined researchers and other browser vendors at the <a href="https://www.dagstuhl.de/de/seminars/seminar-calendar/seminar-details/26291">Dagstuhl Seminar on Web Application Security</a> in July, presenting on LLM-assisted vulnerability detection, XSS protections, and web-scale security measurements.</p>

<p><strong>Mozilla Security Research Summit:</strong> Mozilla’s Security-Engineering University Relationship Framework (SURF) is back. On November 20, 2026, we will host another invitation-only summit at TU Delft in the Netherlands, bringing together Mozilla engineers and academic researchers to explore security and privacy challenges and spark new collaborations. The summit takes place immediately after the <a href="https://www.sigsac.org/ccs/CCS2026/">ACM Conference on Computer and Communications Security (CCS)</a>.</p>

<p><strong>TLS, QUIC, HTTP/3, and Happy Eyeballs:</strong> Max Inden gave a guest lecture at TU Dresden on <a href="https://mxinden-bot.github.io/slides/01-tu-dresden/">modern networking protocols</a>, covering the technologies behind fast, secure web connections.</p>

<h3>Looking Ahead</h3>

<p><em>Firefox users receive the security and privacy improvements highlighted in this newsletter through regular updates. If you haven’t tried Firefox yet, download it to experience a fast, secure browser and support Mozilla’s mission to keep the web open, safe, healthy, and accessible to everyone.</em></p>

<p><em>Thank you to everyone who helps make Firefox and the web more secure and privacy-focused, by reporting bugs, conducting research, contributing code, or sharing feedback.</em></p>

<p><em>We look forward to sharing more updates in the Q4 2026 edition.</em></p>

<p><em>— The Firefox Security &amp; Privacy Teams</em></p></div>
    </content>
    <updated>2026-11-02T23:00:00Z</updated>
    <published>2026-11-02T23:00:00Z</published>
    <author>
      <name>Frederik Braun, Christoph Kerschbaumer</name>
    </author>
    <source>
      <id>https://attackanddefense.dev/feed.xml</id>
      <link href="https://attackanddefense.dev/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://attackanddefense.dev/" rel="alternate" type="text/html"/>
      <subtitle>A blog from the Firefox Application Security Team</subtitle>
      <title>Attack &amp; Defense</title>
      <updated>2026-11-03T07:56:10Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>https://smallcultfollowing.com/babysteps/blog/2026/10/30/trust-but-verify/</id>
    <link href="https://smallcultfollowing.com/babysteps/blog/2026/10/30/trust-but-verify/?utm_source=atom_feed" rel="alternate" type="text/html"/>
    <title xml:lang="en-us">'Trust but verify'; or, 'the correctness ratchet'</title>
    <content type="xhtml" xml:lang="en-us"><div xmlns="http://www.w3.org/1999/xhtml"><p>The name of the game in agentic development is figuring out how to clearly tell agents what you want– and then how to be sure they follow through. Lately I’ve been tinkering with an interesting technique around this that I’d like to share.<sup id="fnref:1"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:1">1</a></sup> I call it “trust but verify”<sup id="fnref:2"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:2">2</a></sup>.</p>
<p>The basic idea is that sometimes you have things you want to “verify” but they can’t really be <em>mechanistically</em> checked. In that case, you let your agent do its best. But you also have it create an <em>evidence</em> file that contains the <em>inputs</em> it drew on to make that decision along with its <em>rationale</em>. Then you gate your CI on checking that these evidence files exist and that the inputs are accurate. Those checks are deterministic and cheap. The <em>rationale</em> itself is natural language and can’t be checked.</p>
<p>Doing this “trust but verify” technique on its own is helpful. It creates a kind of <em>hill-climbing towards correctness</em> that is stronger than (e.g.) tests alone. It helps to check meta-reasoning like “is the set of tests sufficient to show this requirement is true”. Documenting the input also means that if any input should change, the CI check will start to fail, and the agent will be forced to revalidate its reasoning.</p>
<p>What I find <em>most</em> interesting though is that “trust but verify” can be used to create a kind of <em>correctness ratchet</em> over time. The idea is that, now that the inputs + rationale are documented, you can have other agents come back and double-check that reasoning, even when the inputs have not otherwise changed. As agents naturally improve, or just due to the randomness inherent in how agents work, they will naturally find things the original rationale overlooked, and you’ll be able to address them.</p>
<h3>When you say “hill climbing towards correctness”, what do you mean by “hill-climbing”?</h3>
<p>Agents are none too smart, but they can be awfully dogged and persistent. If you ask them to climb a hill, they are going to find a way to do it. The tricky bit of course is that they don’t always climb that hill <a href="https://en.wikipedia.org/wiki/OpenAI_rogue_agent_breach_of_Hugging_Face">in the way you intended</a>. Also, they may not exactly <em>climb</em> it so much as find a route to the top: they may be persistent, but they are also lazy <span style="white-space: nowrap;">f!@#kers</span><sup id="fnref:4"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:4">4</a></sup>, and they love to take shortcuts.</p>
<h3>What if the <em>hills</em> are propositions about your program?</h3>
<p>The fact that agents are good at climbing hills has got a lot of people in the automated reasoning community<sup id="fnref:5"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:5">5</a></sup> very excited. After all, what better way could there be to make sure your program does what you expect than to formally prove that it is true? And we’ve seen that when you set a model loose with a Lean theorem, it can be quite adept at proving things<sup id="fnref:6"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:6">6</a></sup>.</p>
<h3>But there are a few caveats…</h3>
<p>Myself, I’m quite excited about tools like <a href="https://lean-lang.org">Lean</a> but also <a href="https://verus-lang.github.io/verus/guide/">Verus</a>, <a href="https://github.com/AeneasVerif/aeneas">Aeneas</a>, and <a href="https://github.com/creusot-rs/creusot">Creusot</a>. I think we’re going to be using them a lot more. And yet, I also think that proving propositions is not the end of the story.</p>
<h4>Who writes those propositions?</h4>
<p>Let’s start with the obvious problem. <strong>An agent may be good at <em>proving</em> a proposition, but who is actually <em>writing</em> it?</strong> Even when something can be formalized, doing that formalization is a fair bit of work. Consider this random example of a requirement from a project I am working on<sup id="fnref:7"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:7">7</a></sup>:</p>
<blockquote>
<p>A Fleet using Functionality A must be attributed to every Functionality reachable through any number of recorded deprecation steps, while being counted only once when routes converge.</p>
</blockquote>
<p>This is part of a project that is analyzing fleets across Amazon and looking at how much DRAM they consume. Our goal is to make sure that every large fleet at Amazon has Rust versions of every library it would need to be rewritten into Rust. We want to be able to go to the maintainers of those libraries and say, “there are fleets accounting for X% of Amazon’s total DRAM consumption that use your library; you should make a Rust version”.</p>
<p>The point is, while the <em>concept</em> of this DRAM accounting is not complex, formulating it in a precise, mathematical way is not at all trivial. You have to have some notion of transitive closure, talk about the graph of dependencies, etc. There is no way that the lazy, spoiled programmers of the future are going to write a formula like that by hand.</p>
<p>Much more likely is that they are going to give high-level direction to the agent and ask it to connect the dots. After all, this is what agents are good for! And in this case, I would trust an agent to get it right. As I said, it’s not really <em>complex</em>, just… tedious.</p>
<h4>Can they say what you want?</h4>
<p>And of course this leaves aside that there are many things that are just plain hard to formalize. Consider a requirement like, “a warning must be displayed on every relevant form in a prominent fashion”. Checking this requirement requires a notion of what is “prominent”, which is unlikely to be a mathematical property one can write down. And while I would not trust an agent’s judgment over an actual graphic designer, it is also the kind of thing where the agent can likely do a “good enough” job to catch many failures.</p>
<h4>And what does it cost to do the proof?</h4>
<p>The other point is that while agents are good at authoring proofs, it still takes them tokens – and more importantly, <em>time</em> – to do it. And sometimes quite a bit. If developers have to wait a while for the agent to find a proof to a complex property, that better be worth it. If the property you are proving is key to your system, it probably is. But if the cost of a mistake is less than the cost of a proof, people won’t bother, so it’s worth thinking about leaner, easier ways to gain confidence.</p>
<h4>And what about when you are iterating?</h4>
<p>One final point is that applying too much rigor too early in the process can be a real problem. This one is tricky because rigor can surface problems earlier, too. But it’s often helpful to start by defining your requirements and things at a higher level and gradually get more precise as you go, tolerating a bit of “looseness” early on when you know there are details you have to nail down, but it’s not important to do so <em>yet</em>.<sup id="fnref:8"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:8">8</a></sup></p>
<p>A key point for me is that just because you haven’t formalized your requirement all the way to a mathematical proposition doesn’t mean that you’ve got nothing at all. You can often phrase a high-level version of what you want, perhaps one that is overly simplified. In fact, it’s pretty useful to do so, because when you find that your rule doesn’t quite work, that helps you figure out how to refine it into the more precise rule you actually want.</p>
<h3>Evidence and “trust but verify”</h3>
<p>The key idea of the “trust but verify” technique is that leaning on agentic reasoning is good, fine actually. <strong>But when you do so, you should have the agent explain itself and also have it lay out what inputs and evidence it used to reach that conclusion.</strong> Basically, leave yourself a trail so that you (or another agent…) can come back and audit what decisions were reached and on what basis.</p>
<p>Following this approach helps in two ways:</p>
<ol>
<li>In the short term, it forces the agent to at least acknowledge your requirement, which generally means they will do a better job at meeting it.</li>
<li>In the long term, it lets you go back and double-check the agent’s reasoning, leading to a kind of “correctness ratchet” in which you are generally improving the alignment of “what you have” with “what you asked for”.</li>
</ol>
<h3>One example: Habeas Codicem</h3>
<p>Probably the simplest example of this “trust but verify” technique is <a href="https://github.com/nikomatsakis/habeas-codicem/">Habeas Codicem</a>. This is a small project I made in part as an experiment. The idea is that you write <strong>requirements</strong> into your docs and then Habeas Codicem adds a test into your system that can only be passed if an agent has written an explanation of why each of those requirements is satisfied. Those explanations are recorded as <strong>evidence files</strong> that are committed into your repository along with the code.</p>
<p>The interesting bit about Habeas Codicem is that the evidence files contain not only the agent’s rationale and judgement, but also a list of the inputs it used to reach that conclusion. And these inputs have to have certain contents. For example, if you have a function that is labeled as part of the requirement’s implementation, or a test that is tied to a requirement, then the agent must include that function or that test in its evidence.</p>
<p>The final part of Habeas is some skills that instruct the agent to always check with you, the human, before editing requirements, and to confirm agreement on requirements before implementing.</p>
<h3>Another example: an internal data store</h3>
<p>Early in the post I mentioned an internal project I am working on at Amazon to analyze which missing dependencies might block fleets from migrating to Rust. This system involves a lot of agent-driven investigation. For example, perhaps there is a Rust version of a Java library, but it only handles <em>some</em> of the features (this is pretty common). Then we need to know whether the fleet’s code cares about those features that aren’t included.</p>
<p>My early attempts at gathering this data were pretty crude. I basically just sat there telling Amazon Quick “try harder, make no mistakes”. Not great. I didn’t really trust the result.</p>
<p>My newer attempts are much more thorough. I ask the agents to produce an evidence record of what data points they looked at and to include a written rationale for how those data points connect. I then test that the data points hold. For example, to determine if the method <code>convertData</code> in some library is called, the agent might register specific lines from <code>.java</code> files showing a call like <code>value.convertData()</code>. Or it might show the results from a grep that show no matches for <code>convertData</code>.</p>
<p>The interesting bit is that while the <em>rationale</em> from the agent can’t really be evaluated in an automated fashion, the <strong>evidence</strong> can be. So before we accept any agent-created conclusion, we run a deterministic checker that ensures the evidence is valid (those lines really do appear where the agent said they would) and then records a <strong>receipt</strong> that the check was done. So the agent cannot just hallucinate evidence.</p>
<h3>What we are asserting: the agent has done work</h3>
<p>Habeas Codicem does not prove your code obeys its requirements; nor does my inventory system prove that a given Java feature is used. But it <strong>does</strong> prove that the agent actually considered the question enough to write out some evidence + a justification. And assuming your agent is not actively malicious, that’s actually quite a bit.</p>
<p>One thing that we’ve seen is that <a href="https://www.forbes.com/councils/forbestechcouncil/2026/09/11/ai-agents-will-take-shortcuts-the-solution-is-to-design-better-paths/">agents often “lie” about what work they did</a>. They’ll claim to have carefully read through a document when an examination of their tool invocations shows that they’ve just looked at a few random bytes.</p>
<h3>Tightening and revalidating rationale</h3>
<p>One of the ideas I find most interesting in this space is the idea of <em>revalidating</em> rationale. Now that we have evidence files committed to git, we can absolutely have another adversarial agent that periodically pulls up those files and gives them another look. That agent can go looking for holes in the original logic and produce modified and improved proofs or counterexamples. I find this particularly compelling when you think about new and better models that might be more adept at finding holes.</p>
<h3>Applying this idea to propositions</h3>
<p>I think this technique suggests how we can begin to tackle the problem of converting “high-level requirements” into formal theorems. Instead of expecting humans to write and review logical formulae, we can ask an agent to do the conversion – and to record its thinking process (with verifiable evidence). Then we keep that evidence around and we periodically revisit it, looking for potential edge cases. We wind up with a kind of ‘confidence score’ – the more reviews that have approved a given “requirement-&gt;formula” translation, the more likely it is to be accurate.</p>
<h3>The risk of ping-ponging and what it means</h3>
<p>That said, I’ve not really put this into practice yet, and I anticipate it may be tricky to get it working right. People have told me to expect that agents may ping-pong a bit: for example, maybe one of them translates your plain English into logic, and then another says “that translation doesn’t look right” and takes a new approach. But then yet another agent reverts that and goes back to the original. This seems very plausible– I suspect it can be resolved by adding enough history to recognize that it actually reflects ambiguity in your original statement, and to surface the problem up to you.</p>
<div class="footnotes">
<hr/>
<ol>
<li id="fn:1">
<p>I do not claim this technique is novel. I am quite sure people have been doing variants of it forever. But it’s novel to me, and I don’t think I’ve heard people talk about some of the potential long-term implications around “the correctness ratchet”. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:1">↩︎</a></p>
</li>
<li id="fn:2">
<p>I know this phrase from Reagan, of course, but when I started reading into its background I found it had a more interesting history than I expected. Apparently it is a Russian proverb and was suggested to Reagan as a way to communicate with Gorbachev in familiar idioms. As with “less is more”, it’s always had that delightfully contradictory feeling (“if you have to verify, are you really trusting?”) – and at least the way I interpret it, it’s really more like “trust through verification”. In other words, I know I can trust you because we’ve set up the means for me to verify your logic. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:2">↩︎</a></p>
</li>
<li id="fn:3">
<p>I had written, “I don’t usually curse at computers”, but my daughter (reading over my shoulder) told me, <em>“That is not true, you curse at computers all the time”</em>. And she’s right! But I realized that it feels different. When I am using some restaurant website that seems purposefully designed not to tell me their opening hours or show me a menu, I certainly say <em>“oh <span style="white-space: nowrap;">f!@#k</span> you!”</em>, but in that case, I am actually cursing at the person who designed that website. I am not cursing at <em>the website itself</em>; it’s just an inert vessel. In contrast, when I curse at a model, I am not cursing at the people who trained it. I am cursing at the dang model, because it just seems to be going out of its way to be annoying. Anthropomorphizing is a pain. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:3">↩︎</a></p>
</li>
<li id="fn:4">
<p>God, agents have gotten me so frustrated lately. I’m not usually prone to cursing when sober<sup id="fnref:3"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:3">3</a></sup> but more than once lately I’ve found myself typing, <em>“I have no idea what the <span style="white-space: nowrap;">f!#!</span> you are talking about”</em>. This seems to happen slightly more often with Claude than GPT. Claude really likes to develop a kind of <a href="https://en.wikipedia.org/wiki/Cryptophasia">cryptophasic</a> shorthand where it drops random words that I used 3 weeks ago as if that will mean anything to me now. “You still have to handle the first-cut case!” <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:4">↩︎</a></p>
</li>
<li id="fn:5">
<p><em>Automated reasoning</em> is the same thing as <em>formal methods</em>, just more appealingly branded. As an aside, lately I’ve been hearing people talk about <em>Neurosymbolic AI</em>, which I believe is a shameless (and brilliant) way for your SAT solver to jump on the LLM hype train. I suppose it’s also a reasonable way to push back against “AI scope creep”. While I’m on the topic: it seems to me that John McCarthy’s quip (<a href="https://quoteinvestigator.com/2024/06/20/not-ai/"><em>“as soon as it works, no one calls it AI anymore”</em></a>) has been proven false. I would rather people stopped saying “AI” and just said “LLM”, but nobody really cares what I want, do they? <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:5">↩︎</a></p>
</li>
<li id="fn:6">
<p><a href="https://leodemoura.github.io/blog/2026-8-1-postmortem-for-kernel-soundness-bug-14576/">Even if they aren’t actually true</a>. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:6">↩︎</a></p>
</li>
<li id="fn:7">
<p>I did not actually write this text, of course, an agent did. It’s pretty convoluted. Sigh. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:7">↩︎</a></p>
</li>
<li id="fn:8">
<p>This feels reminiscent of <a href="https://terrytao.wordpress.com/career-advice/theres-more-to-mathematics-than-rigour-and-proofs/">Terry Tao’s classic post outlining how an experienced mathematician leans on instinct informed by rigor</a> rather than just one or just the other. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:8">↩︎</a></p>
</li>
</ol>
</div></div>
    </content>
    <updated>2026-10-30T09:40:38Z</updated>
    <published>2026-10-30T00:00:00Z</published>
    <source>
      <id>https://smallcultfollowing.com/babysteps/</id>
      <author>
        <name>Niko Matsakis</name>
        <email>rust@nikomatsakis.com</email>
      </author>
      <link href="https://smallcultfollowing.com/babysteps/" rel="alternate" title="html" type="text/html"/>
      <link href="https://smallcultfollowing.com/babysteps/index.xml" rel="alternate" title="rss" type="application/rss+xml"/>
      <link href="https://smallcultfollowing.com/babysteps/atom.xml" rel="self" title="atom" type="application/atom+xml"/>
      <title xml:lang="en-us">baby steps</title>
      <updated>2026-10-30T10:48:25Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149997</id>
    <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261028-1/149997" rel="alternate" type="text/html"/>
    <title>Happy BMO Push Day! (20261028.1)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://github.com/mozilla-bteam/bmo/tree/release-20261028.1" rel="noopener nofollow ugc">Github Link</a></p>
<p>The following changes have been pushed to <a href="https://bugzilla.mozilla.org">bugzilla.mozilla.org</a>:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2081856">Bug 2081856</a> - Migrate Bug REST resource to native Mojo API: attachments (attachments, add_attachment, update_attachment)</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2080901">Bug 2080901</a> - [BMO-ETL] When any table fails to export, the entire snapshot should be rolled back to avoid incorrect results in charts/dashboards</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2085028">Bug 2085028</a> - log_user_request logs empty request_url/user_agent and server “web” for native Mojo API routes</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2067852">Bug 2067852</a> - Migrate rst docs to markdown and host inside of bugzilla itself</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2085553">Bug 2085553</a> - Github logins are failing with JSON error after recent changes to Bugzilla</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078938">Bug 2078938</a> - Message/Banner for people creating tickets under <a href="http://mozilla.org">mozilla.org</a> :: GitHub: Administration</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2086615">Bug 2086615</a> - Change the ability to see groups a user is a member of via /rest/user?names= to the group can_see_groups</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883428">Bug 1883428</a> - Improve the needinfo email situation (use HTML, drop unnecessary emails)</li>
</ul>
<p>Discuss these changes in the <a href="https://matrix.to/#/#bmo:mozilla.org" rel="noopener nofollow ugc">BMO Matrix Room</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261028-1/149997">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-28T21:15:08Z</updated>
    <published>2026-10-28T21:15:08Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>dkl1</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261028-1/149997.rss" title="Happy BMO Push Day! (20261028.1)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/addons/?p=9312</id>
    <link href="https://blog.mozilla.org/addons/2026/10/28/introducing-enterprise-add-on-policies/" rel="alternate" type="text/html"/>
    <title>Introducing enterprise add-on policies</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>We are thrilled to announce that enterprise add-ons will launch on addons.mozilla.org (AMO) on December 1, 2026. In response to input from enterprise organizations that distribute add-ons strictly via Firefox … <a class="go" href="https://blog.mozilla.org/addons/2026/10/28/introducing-enterprise-add-on-policies/">Read more</a></p>
<p>The post <a href="https://blog.mozilla.org/addons/2026/10/28/introducing-enterprise-add-on-policies/">Introducing enterprise add-on policies</a> appeared first on <a href="https://blog.mozilla.org/addons">Mozilla Add-ons Community Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>We are thrilled to announce that enterprise add-ons will launch on addons.mozilla.org (AMO) on December 1, 2026.</p>
<p>In response to input from enterprise organizations that distribute add-ons strictly via Firefox enterprise policies, we are establishing a dedicated enterprise release channel.</p>
<p>This tailored channel directly serves enterprise developers’ requirements while freeing up resources to continue supporting non-enterprise developers.</p>
<h3><b>Why enterprise add-ons need their own policies</b></h3>
<p>Many organizations rely on Firefox add-ons to keep their people and data safe: security tools, data loss prevention, identity and access management, and internal productivity tools. These add-ons work very differently from the ones most people install from AMO:</p>
<ul>
<li><b>They are deployed, not discovered.</b> IT administrators install them across managed fleets using Firefox enterprise policies.</li>
<li><b>Their reach is large.</b> A single enterprise developer can serve thousands of managed browsers inside one organization.</li>
<li><b>Their release cycle matters.</b> When a security vendor ships a fix, customers expect it to reach their fleet quickly and predictably.</li>
</ul>
<p>Until now, these add-ons went through the same manual review queue as everyone else, under rules written for consumer add-ons. That slowed organizations relying on Firefox and took reviewer time away from the rest of the community without making a meaningful impact.</p>
<h3><b>What is changing on December 1</b></h3>
<ul>
<li><b>A new enterprise channel: </b>Versions submitted in the enterprise channel <a href="https://extensionworkshop.com/documentation/publish/add-on-policies-for-enterprise-preview-2026-12/">follow the new enterprise add-on policies</a>.</li>
<li><b>Enterprise versions stay in the enterprise channel: </b>Versions submitted through the enterprise channel are only available through that channel. They won’t appear on AMO or be distributed by Mozilla in any other way.</li>
<li><b>A lighter manual review queue:</b> With a limited set of policies applying to enterprise add-ons, reviewers can spend more of their time on other add-ons.</li>
<li><b>An updated agreement for everyone: </b>To adopt the new policies, all developers must accept the updated Firefox Add-on Distribution Agreement.</li>
<li><b>The same bar for safety:</b> Enterprise add-ons are still Add-ons are subject to Mozilla’s<a href="https://www.mozilla.org/about/legal/acceptable-use/"> Acceptable Use Policy</a>.</li>
</ul>
<p>The full policy text will be published on <a href="https://extensionworkshop.com/documentation/publish/add-on-policies-for-enterprise-preview-2026-12/">Extension Workshop</a>. Until December 1, the current policies remain in effect.</p>
<h3><b>How to take advantage of it</b></h3>
<p><b>If you build add-ons for organizations:</b> Read the <a href="https://extensionworkshop.com/documentation/publish/add-on-policies-for-enterprise-preview-2026-12/">enterprise add-on policies</a>, and get ready to submit your enterprise versions through the enterprise channel from December 1.</p>
<p>In a nutshell, you must self-declare the enterprise status via the specific manifest key</p>
<pre>"browser_specific_settings": {
   "gecko": {
      "admin_install_only": true
   }
}
</pre>
<p><b>If you build public add-ons:</b> Nothing changes in how you submit or how your add-on is reviewed. The only thing you need to do is accept the updated agreement when prompted.</p>
<h3><b>Quick Q&amp;A: Who is this for?</b></h3>
<p><b>Who are the enterprise add-on policies for?</b></p>
<p>Developers whose add-ons are built for organizations and deployed to managed Firefox installations through enterprise policies.</p>
<p><b>I’m an individual developer with a public add-on on AMO. Does this affect me?</b></p>
<p>Your submission process doesn’t change, but you will need to accept the updated developer agreement.</p>
<p><b>My add-on is used by companies, but people also install it themselves from AMO. Is it an enterprise add-on?</b></p>
<p>Only versions you submit through the enterprise channel are enterprise versions, and those are available only through that channel. To keep your add-on listed on AMO, keep submitting it the usual way.</p>
<p><b>I only build an add-on for my own company’s employees. Is this for me?</b></p>
<p>It can be. You can use the enterprise channel, or choose <a href="https://extensionworkshop.com/documentation/publish/self-distribution/">self-distribution</a>, which is often the simplest route for add-ons meant for a smaller population.</p>
<p><b>I’m an IT administrator, not a developer. Do I need to do anything?</b></p>
<p>No. You keep deploying add-ons with Firefox enterprise policies as you do today.</p>
<p><b>Do I really need to accept the updated agreement?</b></p>
<p>Yes. Every developer on AMO, enterprise or not, needs to accept it, because the new policies are part of it.</p>
<p><b>When does this take effect?</b></p>
<p>December 1, 2026.</p>
<p> </p>
<p>The post <a href="https://blog.mozilla.org/addons/2026/10/28/introducing-enterprise-add-on-policies/">Introducing enterprise add-on policies</a> appeared first on <a href="https://blog.mozilla.org/addons">Mozilla Add-ons Community Blog</a>.</p></div>
    </content>
    <updated>2026-10-28T17:14:37Z</updated>
    <published>2026-10-28T17:14:37Z</published>
    <category term="developers"/>
    <author>
      <name>cbacharakis</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/addons/</id>
      <link href="https://blog.mozilla.org/addons/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/addons/" rel="alternate" type="text/html"/>
      <title>Mozilla Add-ons Community Blog</title>
      <updated>2026-10-28T21:47:25Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149991</id>
    <link href="https://discourse.mozilla.org/t/firefox-devtools-mcp-v0-10-7-released/149991" rel="alternate" type="text/html"/>
    <title>Firefox DevTools MCP v0.10.7 released</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>New release of Firefox DevTools MCP. Available on npm at <a href="https://www.npmjs.com/package/@mozilla/firefox-devtools-mcp" rel="noopener nofollow ugc">https://www.npmjs.com/package/@mozilla/firefox-devtools-mcp</a></p>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297465-added-1" name="p-297465-added-1"/>Added</h3>
<ul>
<li>New <code>--idle-timeout</code> option (<code>IDLE_TIMEOUT</code>). It sets how many seconds a <code>--connect-existing</code> session waits without tool calls before it releases Firefox. The default stays 1800 seconds (30 minutes). Firefox accepts one client at a time, so a shorter delay lets other clients connect sooner</li>
</ul>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297465-fixed-2" name="p-297465-fixed-2"/>Fixed</h3>
<ul>
<li><code>upload_file_by_uid</code> works again. Since 0.10.5 it did not set any file. It now uses WebDriver BiDi <code>input.setFiles</code>, and no longer changes the style of a hidden file input</li>
<li><code>--connect-existing</code> now fails at once with a clear error when another WebDriver session already holds Firefox. Before, it failed after about 60 seconds with “unknown error”</li>
<li><code>--connect-existing</code> now gives up after 45 seconds when Firefox asks the user to allow the session and nobody answers. Before, it waited forever. The error points at the prompt</li>
<li>Shutting down the server while Firefox waits for the user to allow the session no longer leaves geckodriver running</li>
<li><code>set_viewport_size</code> now only changes the viewport of the selected tab, instead of resizing the whole window. With <code>--connect-existing</code>, the resized tabs are reset when the session closes</li>
<li><code>evaluate_script</code> with a <code>timeout</code> above 10 seconds no longer stops after 10 seconds with a generic BiDi timeout error</li>
</ul>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297465-changed-3" name="p-297465-changed-3"/>Changed</h3>
<ul>
<li><code>navigate_history</code> now uses WebDriver BiDi</li>
<li>BiDi command errors now include the message sent by Firefox</li>
<li>The README explains how to run a <code>--connect-existing</code> Firefox in a dedicated profile, next to your everyday Firefox</li>
</ul>
<p>Full changelog: <a class="inline-onebox" href="https://github.com/mozilla/firefox-devtools-mcp/releases/tag/v0.10.7" rel="noopener nofollow ugc">Release v0.10.7 · mozilla/firefox-devtools-mcp · GitHub</a><br/>
Repository and issues: <a class="inline-onebox" href="https://github.com/mozilla/firefox-devtools-mcp" rel="noopener nofollow ugc">GitHub - mozilla/firefox-devtools-mcp: Model Context Protocol server for Firefox DevTools - enables AI assistants to inspect and control Firefox browser through WebDriver BiDi · GitHub</a><br/>
Public chatroom: <a href="https://chat.mozilla.org/#/room/#firefox-devtools-mcp:mozilla.org" rel="noopener nofollow ugc">https://chat.mozilla.org/#/room/#firefox-devtools-mcp:mozilla.org</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/firefox-devtools-mcp-v0-10-7-released/149991">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-28T11:28:29Z</updated>
    <published>2026-10-28T11:28:29Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>jdescottes</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/firefox-devtools-mcp-v0-10-7-released/149991.rss" title="Firefox DevTools MCP v0.10.7 released"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry>
    <id>tag:this-week-in-rust.org,2026-10-28:/blog/2026/10/28/this-week-in-rust-675/</id>
    <link href="https://this-week-in-rust.org/blog/2026/10/28/this-week-in-rust-675/" rel="alternate" type="text/html"/>
    <title>This Week in Rust 675</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello and welcome to another issue of <em>This Week in Rust</em>!
<a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
This is a weekly summary of its progress and community.
Want something mentioned? Tag us at
<a href="https://bsky.app/profile/thisweekinrust.bsky.social">@thisweekinrust.bsky.social</a> on Bluesky or
<a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social …</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello and welcome to another issue of <em>This Week in Rust</em>!
<a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
This is a weekly summary of its progress and community.
Want something mentioned? Tag us at
<a href="https://bsky.app/profile/thisweekinrust.bsky.social">@thisweekinrust.bsky.social</a> on Bluesky or
<a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social, or
<a href="https://github.com/rust-lang/this-week-in-rust">send us a pull request</a>.
Want to get involved? <a href="https://github.com/rust-lang/rust/blob/main/CONTRIBUTING.md">We love contributions</a>.</p>
<p><em>This Week in Rust</em> is openly developed <a href="https://github.com/rust-lang/this-week-in-rust">on GitHub</a> and archives can be viewed at <a href="https://this-week-in-rust.org/">this-week-in-rust.org</a>.
If you find any errors in this week's issue, <a href="https://github.com/rust-lang/this-week-in-rust/pulls">please submit a PR</a>.</p>
<p>Want TWIR in your inbox? <a href="https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&amp;id=0ed8b72485">Subscribe here</a>.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#updates-from-rust-community">Updates from Rust Community</a></h4>


<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#official">Official</a></h5>
<ul>
<li><a href="https://blog.rust-lang.org/inside-rust/2026/10/27/variadic-generics-micro-survey-results/">Variadic Generics Micro Survey results</a></li>
<li><a href="https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/">How to fund Rust contributors</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#newsletters">Newsletters</a></h5>
<ul>
<li><a href="https://www.theembeddedrustacean.com/p/the-embedded-rustacean-issue-83">The Embedded Rustacean Issue #83</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#projecttooling-updates">Project/Tooling Updates</a></h5>
<ul>
<li><a href="https://www.redox-os.org/news/nlnet-rb-summary/">Ring Buffers Project Summary - Redox - Your Next(Gen) OS</a></li>
<li><a href="https://astral.sh/blog/tar-codec">tar-codec: a fast and secure tar parser for the Rust ecosystem</a></li>
</ul>


<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#observationsthoughts">Observations/Thoughts</a></h5>
<ul>
<li><a href="https://ieeexplore.ieee.org/abstract/document/11723159">Rust Without Shortcuts: What Safety Actually Costs</a></li>
<li><a href="https://kivooeo.github.io/blog/what-stable-rust-stands-on/">What stable Rust stands on</a></li>
<li><a href="https://shieldify.ee/research/where-a-flood-goes/">Where a Flood Goes</a></li>
<li><a href="https://lwn.net/SubscriberLink/1100520/2e0f0241deef5804/">Discussing a rewrite of XArray</a></li>
<li><a href="https://lwn.net/SubscriberLink/1099606/0fe2b8d731fd167f/">Rust features in the future</a></li>
<li><a href="https://lwn.net/SubscriberLink/1100873/0934a9a322c6df4c/">Guidelines for panics in kernel code</a></li>
<li><a href="https://kerkour.com/rust-crdt-love">What distributed systems and end-to-end encrypted apps have in common? CRDTs and Rust!</a></li>
<li>[video] <a href="https://www.youtube.com/watch?v=2j6BzKaODUk">P99 CONF 2026 | Building Ultra-Performant Message Streaming by Piotr Gankiewicz</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-walkthroughs">Rust Walkthroughs</a></h5>
<ul>
<li><a href="https://bitfieldconsulting.com/posts/heat-is-on">The heat is on: handling units in Rust</a></li>
<li><a href="https://tweedegolf.nl/en/blog/242/finding-panics-with-call-graph-analyzer/">Finding panics with Call Graph Analyzer</a></li>
<li>[video] <a href="https://www.youtube.com/watch?v=P9xCUmjkPUM">Beyond Vibe Coding: Formal Verification for AI-Generated Python &amp; Rust Software</a></li>
<li>[video] <a href="https://www.youtube.com/watch?v=LnxuQKoxvFM">Rust and the GPU from Native to Web: An Introduction to <code>wgpu</code> by Liam Rust</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#miscellaneous">Miscellaneous</a></h5>
<ul>
<li>[uz] <a href="https://doc.ferris.uz/">Announcing Rust Uzbekistan &amp; The Official Uzbek Translation of The Rust Book</a></li>
</ul>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#crate-of-the-week">Crate of the Week</a></h4>
<p>This week's crate is <a href="https://crates.io/crates/offline-protocol">offline-protocol</a>, a crate that supplies mesh-networking/peer discovery for a variety of networks, under AGPL/proprietary license.</p>
<p>Thanks to <a href="https://users.rust-lang.org/t/crate-of-the-week/2704/1702">Gokul</a> for the self-suggestion!</p>
<p><a href="https://users.rust-lang.org/t/crate-of-the-week/2704">Please submit your suggestions and votes for next week</a>!</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#calls-for-testing">Calls for Testing</a></h4>
<p>An important step for RFC implementation is for people to experiment with the
implementation and give feedback, especially before stabilization.</p>
<p>If you are a feature implementer and would like your RFC to appear in this list, add a
<code>call-for-testing</code> label to your RFC along with a comment providing testing instructions and/or
guidance on which aspect(s) of the feature need testing.</p>
<p><em>No calls for testing were issued this week by
<a href="https://github.com/rust-lang/rust/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Rust</a>,
<a href="https://github.com/rust-lang/cargo/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Cargo</a>,
<a href="https://github.com/rust-lang/rustup/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Rustup</a> or
<a href="https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing%20state%3Aopen">Rust language RFCs</a>.</em></p>
<p><a href="https://github.com/rust-lang/this-week-in-rust/issues">Let us know</a> if you would like your feature to be tracked as a part of this list.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers">Call for Participation; projects and speakers</a></h4>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cfp-projects">CFP - Projects</a></h5>
<p>Always wanted to contribute to open-source projects but did not know where to start?
Every week we highlight some tasks from the Rust community for you to pick and get started!</p>
<p>Some of these tasks may also have mentors available, visit the task page for more information.</p>


<ul>
<li><a href="https://github.com/lacs-project/sysknife/issues/559">sysknife - SetSshdOption reports success while an earlier sshd_config.d drop-in overrides the value it wrote</a></li>
<li><a href="https://github.com/lacs-project/sysknife/issues/558">sysknife - On Postgres the daemon anchors the audit chain but every reader reports the anchor unsupported and exits 2</a></li>
<li><a href="https://github.com/lacs-project/sysknife/issues/591">sysknife - ci-local.test.sh stays green when the #555 exit fix, the missing-tool default or the opt-out flag is reverted</a></li>
<li><a href="https://github.com/TabularisDB/tabularis/issues/1309">Tabularis - [Feat]: Import connections from pgAdmin 4</a></li>
<li><a href="https://git.keepword.net/keepword/keepword/issues/49">Keepword - Say how many networks have observed a node that isn't located yet</a></li>
<li><a href="https://github.com/Muvon/octomind/issues/242">Octomind - <code>octomind workflow docs</code> fails with "Is a directory" when <code>./docs/</code> exists</a></li>
<li><a href="https://github.com/Muvon/octomind/issues/241">Octomind - Workflow loop with <code>max_iterations = 0</code> passes validation and never runs</a></li>
<li><a href="https://github.com/Muvon/octomind/issues/166">Octomind - ACP: send tool kind, file locations and diffs with tool calls</a></li>
</ul>


<p>If you are a Rust project owner and are looking for contributors, please submit tasks <a href="https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines">here</a> or through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a> or by reaching out on <a href="https://bsky.app/profile/thisweekinrust.bsky.social">Bluesky</a> or <a href="https://mastodon.social/@thisweekinrust">Mastodon</a>!</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cfp-events">CFP - Events</a></h5>
<p>Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.</p>



<p>If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a> or by reaching out on <a href="https://bsky.app/profile/thisweekinrust.bsky.social">Bluesky</a> or <a href="https://mastodon.social/@thisweekinrust">Mastodon</a>!</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#updates-from-the-rust-project">Updates from the Rust Project</a></h4>
<p>609 pull requests were <a href="https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2026-10-20..2026-10-27">merged in the last week</a></p>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#compiler">Compiler</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/159689">account for missing turbofish in resolve errors</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163845">add various <code>#[inline]</code> annotations for simple functions on hot paths that don't get inlined</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164300">deduplicate DefId encodings in the query cache</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162460"><code>#[inline(always)] + #[target_feature(enable = "....")]</code> #2</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163338">MIR move elimination [4/6]: MoveElimination</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163485"><code>rustc_builtin_macros</code> cleanup, part 8</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163971">optimize Span operations, especially the hot <code>Span::to</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164330">skip redundant monomorphization checks</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164849">use the span of the doctest code block fence for figuring out the line number</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#library">Library</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/164643">const-stabilize {<code>BinaryHeap</code>, <code>BTreeMap</code>, <code>BTreeSet</code>, <code>LinkedList</code>, <code>VecDeque</code>)<code>::</code>{<code>len</code>, <code>is_empty</code>}</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164474">core: implement <code>char::is_xid_</code>{<code>start</code>, <code>continue</code>}</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164488">don't try to skip anything in <code>Skip::advance_by(0)</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/161253">implement <code>AsMut&lt;T&gt;</code> and <code>AsRef&lt;T&gt;</code> for <code>!</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164611">improve bit permutation codegen</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163510">process: improve the output of <code>Debug</code> for <code>ExitStatus</code> on Unix</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164656">stabilize ExitCodeExt for Windows</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163499">stabilize allocators for <code>Vec::into_iter</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163816">stabilize <code>String::into_chars</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162927">stabilize <code>ptr_cast_slice</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164641">stabilize <code>slice_split_once</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163458">stabilize {Rc, <code>Arc}::is_unique</code></a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cargo">Cargo</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/cargo/pull/17631"><code>timings</code>: peak memory as a column in unit table</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17621">stop uplifting rlibs on nightly</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17624">exclude abspath of path deps from <code>-Cmetadata</code> hash</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17617">test: simplify file content assertions</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17637">use build-rs for buildscripts</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustdoc">Rustdoc</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/164733">include <code>deprecated</code> attributes in <code>rustc_resolve</code> intra-doc link resolution</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164594">correctly handle inner <code>deprecated</code> attribute on modules</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164883">don't panic on a nested use group with no path prefix</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustfmt">Rustfmt</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/164815">prevent more comment loss in <code>cfg_select!</code></a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7211">don't lose comments and attributes between <code>cfg_select!</code> predicates, outer/inner blocks, arm body and trailing commas</a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7195">fix <code>cfg_if!</code> error count leaks</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#clippy">Clippy</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17898"><code>wildcard_imports</code>: no longer lint in automatically derives and proc macro expansions</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/14904">add <code>ifs_as_logical_ops</code> lint</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17847">add lint for <code>map_or_else</code> to <code>map_or</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17892">fix <code>missing_const_for_fn</code> false positives in <code>const impl</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17907">fix <code>double_comparisons</code> suggestion dropping required parentheses</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17835">perf: optimise <code>unconditional_recursion</code> lint</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-analyzer">Rust-Analyzer</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23484">automated sync of target feature implications</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23424">fix NamedTempFile issues on windows</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23529">complete 'main' 'lib' module in sub module</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23489">compute ref-match on undotted self</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23231">do not panic when inline call param usages in macro</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23534">fix <code>fetch_semantic</code> logic bug introduced in #22272</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23552">fix status message for clients not supporting <code>experimental/serverStatusNotification</code></a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23540">use absolute path in <code>format_smolstr</code></a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23296">search manifest ancestors for the lockfile when fetching cargo metadata</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage">Rust Compiler Performance Triage</a></h5>
<p>Another week of positive changes. Few unexpected improvements from cleanups and a handful of targeted optimizations.
Apart from instruction count improvements, we also merged a large reduction of query cache size in <a href="https://github.com/rust-lang/rust/pull/164300">#164300</a>.
Negative changes come mostly from unexpected <code>doc</code> regression, which is currently under investigation.</p>
<p>Triage done by <strong>@panstromek</strong>.
Revision range: <a href="https://perf.rust-lang.org/?start=bd4c6cc4aeef0eb9919c6f73c1e690677e9c6b38&amp;end=019b59d8101bb3e141f1b880684747b4217beeb6&amp;absolute=false&amp;stat=instructions%3Au">bd4c6cc4..019b59d8</a></p>
<p><strong>Summary</strong>:</p>
<table>
<thead>
<tr>
<th style="text-align: center;">(instructions:u)</th>
<th style="text-align: center;">mean</th>
<th style="text-align: center;">range</th>
<th style="text-align: center;">count</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: center;">Regressions ❌ <br/> (primary)</td>
<td style="text-align: center;">0.8%</td>
<td style="text-align: center;">[0.2%, 6.8%]</td>
<td style="text-align: center;">25</td>
</tr>
<tr>
<td style="text-align: center;">Regressions ❌ <br/> (secondary)</td>
<td style="text-align: center;">6.8%</td>
<td style="text-align: center;">[0.0%, 189.1%]</td>
<td style="text-align: center;">34</td>
</tr>
<tr>
<td style="text-align: center;">Improvements ✅ <br/> (primary)</td>
<td style="text-align: center;">-0.8%</td>
<td style="text-align: center;">[-12.6%, -0.1%]</td>
<td style="text-align: center;">195</td>
</tr>
<tr>
<td style="text-align: center;">Improvements ✅ <br/> (secondary)</td>
<td style="text-align: center;">-1.2%</td>
<td style="text-align: center;">[-10.6%, -0.1%]</td>
<td style="text-align: center;">157</td>
</tr>
<tr>
<td style="text-align: center;">All ❌✅ (primary)</td>
<td style="text-align: center;">-0.6%</td>
<td style="text-align: center;">[-12.6%, 6.8%]</td>
<td style="text-align: center;">220</td>
</tr>
</tbody>
</table>
<p>3 Regressions, 6 Improvements, 3 Mixed
32 artifact comparisons made in total</p>
<p><a href="https://github.com/rust-lang/rustc-perf/blob/5080585bb0dc997cd8aeca17eff036e0c5ddf713/triage/2026/2026-10-26.md">Full report here</a></p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#approved-rfcs"/><a href="https://github.com/rust-lang/rfcs/commits/main">Approved RFCs</a></h5>
<p>Changes to Rust follow the Rust <a href="https://github.com/rust-lang/rfcs#rust-rfcs">RFC (request for comments) process</a>. These
are the RFCs that were approved for implementation this week:</p>
<ul>
<li><a href="https://github.com/rust-lang/rfcs/pull/4024">2052-epochs.md: typo</a></li>
<li><a href="https://github.com/rust-lang/rfcs/pull/4023">3722-explicit-extern-abis.md: typo</a></li>
<li><a href="https://github.com/rust-lang/rfcs/pull/4022">Fix libs nominated triagebot.toml</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#final-comment-period">Final Comment Period</a></h5>
<p>Every week, <a href="https://www.rust-lang.org/team.html">the team</a> announces the 'final comment period' for RFCs and key PRs
which are reaching a decision. Express your opinions now.</p>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#tracking-issues-prs">Tracking Issues &amp; PRs</a></h6>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust"/><a href="https://github.com/rust-lang/rust/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Rust</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/164414">Add <code>let_underscore_drop_guard</code> lint.</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164653">Deprecate internal function <code>vec::from_elem</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164328">core: Add <code>assert_matches</code> and <code>debug_assert_matches</code> to the next prelude</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164258">clarify when <code>Vec::into_boxed_slice()</code> is in-place</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/153261">Partially stabilize <code>ptr_alignment_type</code> as <code>alignment_type</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/158368">std: make <code>Instant</code> a signed <code>Duration</code> on all platforms</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/159374">Lower #[no_mangle] to #[symbol_name]/#[link_name]</a></li>
<li><a href="https://github.com/rust-lang/rust/issues/164701">lang team review for new trait solver</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/160186">Implement <code>Fn</code> traits for safe functions of any ABI</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/147697">cmse: lint on unions crossing the secure boundary</a></li>
</ul>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-rfcs"/><a href="https://github.com/rust-lang/rfcs/issues?q=state%3Aopen%20label%3Afinal-comment-period%20state%3Aopen">Rust RFCs</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/rfcs/pull/4013">RFC: Add <code>required-targets</code> for workspace package selection</a></li>
</ul>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#compiler-team-mcps-only"/><a href="https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20label%3Afinal-comment-period%20state%3Aopen">Compiler Team</a> <a href="https://forge.rust-lang.org/compiler/mcp.html">(MCPs only)</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/compiler-team/issues/1045">Add support for <code>annotate-snippets</code>'s <code>no-graphics</code> output format</a></li>
</ul>
<p><em>No Items entered Final Comment Period this week for
<a href="https://github.com/rust-lang/cargo/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Cargo</a>,
<a href="https://github.com/rust-lang/lang-team/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Language Team</a>,
<a href="https://github.com/rust-lang/reference/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Language Reference</a> or
<a href="https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Unsafe Code Guidelines</a>.</em>
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#new-and-updated-rfcs"/><a href="https://github.com/rust-lang/rfcs/pulls">New and Updated RFCs</a></h5>
<ul>
<li><em>No New or Updated RFCs were created this week.</em></li>
</ul>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#upcoming-events">Upcoming Events</a></h4>
<p>Rusty Events between 2026-10-28 - 2026-11-25 🦀</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#virtual">Virtual</a></h5>
<ul>
<li>2026-10-28 | Virtual (Cardiff, UK) | <a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/events/">Rust and C++ Cardiff</a><ul>
<li><a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/events/316880405/"><strong>Operating Systems Book Club: Paging Mechanisms</strong></a></li>
</ul>
</li>
<li>2026-10-29 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/q8i3385k"><strong>Creating a hexadecimal editor in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-01 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/316331277/"><strong>Rust Deep Learning: First Sunday</strong></a></li>
</ul>
</li>
<li>2026-11-03 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/rfbzk3ae"><strong>Solving Real-World Planning Problems in Rust with SolverForge</strong></a></li>
</ul>
</li>
<li>2026-11-03 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/315773682/"><strong>👋 Community Catch Up</strong></a></li>
</ul>
</li>
<li>2026-11-04 | Virtual (Indianapolis, IN, US) | <a href="https://www.meetup.com/indyrs">Indy Rust</a><ul>
<li><a href="https://www.meetup.com/indyrs/events/wqzhftyjcpbgb/"><strong>Indy.rs - with Social Distancing</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Virtual (Berlin, DE) | <a href="https://www.meetup.com/rust-berlin">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/316907780/"><strong>Rust Hack and Learn</strong></a></li>
</ul>
</li>
<li>2026-11-10 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/310254770/"><strong>Second Tuesday</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Virtual (Nürnberg, DE) | <a href="https://www.meetup.com/rust-noris">Rust Nuremberg</a><ul>
<li><a href="https://www.meetup.com/rust-noris/events/315619619/"><strong>Rust Nürnberg online</strong></a></li>
</ul>
</li>
<li>2026-11-15 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/omlooqv8"><strong>Cursed Rust</strong></a></li>
</ul>
</li>
<li>2026-11-15 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/316563020/"><strong>Rust Deep Learning: Third Sunday</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/2qfai4a8"><strong>Miscompilation in Rust 1.97</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/315719313/"><strong>Lunch &amp; Learn: The Harness Wore a Trenchcoat - Building a Rust MCP Server</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual (Washington, DC, US) | <a href="https://www.meetup.com/rustdc">Rust DC</a><ul>
<li><a href="https://www.meetup.com/rustdc/events/fhvsztyjcpbwb/"><strong>Mid-month Rustful</strong></a></li>
</ul>
</li>
<li>2026-11-18 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210234/"><strong>Writing a firmware for Xteink ereader in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-19 | Virtual (Berlin, DE) | <a href="https://www.meetup.com/rust-berlin/events/">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/316907781/"><strong>Rust Hack and Learn</strong></a></li>
</ul>
</li>
<li>2026-11-24 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/events/">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/310254769/"><strong>Fourth Tuesday Rust Bookclub</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#asia">Asia</a></h5>
<ul>
<li>2026-11-03 | Tel Aviv-Yafo, IL | <a href="https://www.meetup.com/rust-tlv">Rust 🦀 TLV</a><ul>
<li><a href="https://www.meetup.com/rust-tlv/events/316440864/"><strong>In person Rust November 2026 at AWS in Tel Aviv</strong></a></li>
</ul>
</li>
<li>2026-11-14 | Bengaluru, IN | <a href="https://hasgeek.com/rustbangalore/">Rust Bangalore</a><ul>
<li><a href="https://hasgeek.com/rustbangalore/november-2026-rustacean-meetup/"><strong>November 2026 Rustacean Meetup</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#europe">Europe</a></h5>
<ul>
<li>2026-10-28 | Copenhagen, DK | <a href="https://www.meetup.com/copenhagen-rust-community">Copenhagen Rust Community</a><ul>
<li><a href="https://www.meetup.com/copenhagen-rust-community/events/316545936/"><strong>Rust meetup #72 sponsored by Google!</strong></a></li>
</ul>
</li>
<li>2026-10-29 | Berlin, DE | <a href="https://www.meetup.com/rust-berlin/events/">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/317130457/"><strong>Rust Berlin on location 🏳️‍🌈 – Edition 019</strong></a></li>
</ul>
</li>
<li>2026-10-31 | Stockholm, SE | <a href="https://www.meetup.com/stockholm-rust">Stockholm Rust</a><ul>
<li><a href="https://www.meetup.com/stockholm-rust/events/316721062/"><strong>Ferris' Fika Forum #31</strong></a></li>
</ul>
</li>
<li>2026-11-01 - 2026-11-03 | Italy, IN | <a href="https://rustlab.it/">RustLab</a><ul>
<li><a href="https://rustlab.it/schedule"><strong>RustLab - The International Conference on Rust in Italy</strong></a></li>
</ul>
</li>
<li>2026-11-02 | Berlin, DE | <a href="https://www.meetup.com/rust-berlin/events/">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/317103436/"><strong>Rust Berlin Talks: The next generation</strong></a></li>
</ul>
</li>
<li>2026-11-04 | Dublin, IE | <a href="https://www.meetup.com/rust-dublin">Rust Dublin</a><ul>
<li><a href="https://www.meetup.com/rust-dublin/events/316898325/"><strong>Rust 263: Getting Started with the New Rust Driver for Oracle AI Database</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Milano, IT | <a href="https://www.meetup.com/rust-language-milano">Rust Language Milan</a><ul>
<li><a href="https://www.meetup.com/rust-language-milan/events/316213872/"><strong>Digital Model Trains &amp; Rust: Bare-Metal DCC Command Station on ESP32</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Oxford, UK | <a href="https://www.meetup.com/oxford-rust-meetup-group/events/">Oxford ACCU/Rust Meetup.</a><ul>
<li><a href="https://www.meetup.com/oxford-rust-meetup-group/events/317158298/"><strong>Epitome of synaptic excellence</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Geneva, CH | <a href="https://www.posttenebraslab.ch/wiki/events/monthly_meeting/rust_meetup">Rust Geneva</a><ul>
<li><a href="https://www.posttenebraslab.ch/wiki/events/monthly_meeting/rust_meetup"><strong>Rust Meetup Geneva</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Milano, MI, IT | <a href="https://www.meetup.com/rust-language-milano/events/">Rust Language Milan</a><ul>
<li><a href="https://www.meetup.com/rust-language-milan/events/317094800/"><strong>From Curiosity to Capability: Build Your Own Device Swarm</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Leipzig, DE | <a href="https://www.meetup.com/rust-modern-systems-programming-in-leipzig">Rust - Modern Systems Programming in Leipzig</a><ul>
<li><a href="https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/313816501/"><strong>Everlock: Everything Is Git, Protocols Are Just Adapters</strong></a></li>
</ul>
</li>
<li>2026-11-19 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus/events/">Rust Aarhus</a><ul>
<li><a href="https://www.meetup.com/rust-aarhus/events/316938696/"><strong>Talk Night at EIVA</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#north-america">North America</a></h5>
<ul>
<li>2026-10-28 | Austin, TX, US | <a href="https://www.meetup.com/rust-atx/events/">Rust ATX</a><ul>
<li><a href="https://www.meetup.com/rust-atx/events/316655403/"><strong>Rust Lunch - Fareground</strong></a></li>
</ul>
</li>
<li>2026-10-31 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924288/"><strong>North End Rust Lunch, Oct 31</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Montréal, CA | <a href="https://www.meetup.com/rust-montreal">Rust Montréal</a><ul>
<li><a href="https://www.meetup.com/rust-montreal/events/316919004/"><strong>November Monthly Social</strong></a></li>
</ul>
</li>
<li>2026-11-05 | San Francisco, CA | <a href="https://luma.com/user/usr-eWgtha6CHSTma7v/">Rust LA: NVIDIA</a><ul>
<li><a href="https://luma.com/iqe7wng1"><strong>NVIDIA x Lawrence Harvey | CUDA Rust</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Saint Louis, MO, US | <a href="https://www.meetup.com/stl-rust">STL Rust</a><ul>
<li><a href="https://www.meetup.com/stl-rust/events/316896797/"><strong>HTMX and Rust</strong></a></li>
</ul>
</li>
<li>2026-11-12 | San Diego, CA, US | <a href="https://www.meetup.com/san-diego-rust">San Diego Rust</a><ul>
<li><a href="https://www.meetup.com/san-diego-rust/events/316886787/"><strong>San Diego Rust November Meetup - Back in person!</strong></a></li>
</ul>
</li>
<li>2026-11-14 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924331/"><strong>MIT Rust Lunch, Nov 14</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Los Angeles, CA, US | <a href="https://www.meetup.com/rust-los-angeles">Rust Los Angeles</a><ul>
<li><a href="https://www.meetup.com/rust-los-angeles/events/316859673/"><strong>Rust LA November w/ Hadrian!</strong></a></li>
</ul>
</li>
<li>2026-11-17 | San Francisco, CA, US | <a href="https://www.meetup.com/san-francisco-rust-study-group">San Francisco Rust Study Group</a><ul>
<li><a href="https://www.meetup.com/san-francisco-rust-study-group/events/315783989/"><strong>Rust Hacking in Person</strong></a></li>
</ul>
</li>
<li>2026-11-18 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210234/"><strong>Writing a firmware for Xteink ereader in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-21 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust/events/">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924366/"><strong>Winter Hill Rust Lunch, Nov 21</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#south-america">South America</a></h5>
<ul>
<li>2026-11-07 | Planalto Paulista, BR | <a href="https://www.meetup.com/rust-sao-paulo-meetup">Rust São Paulo Meetup</a><ul>
<li><a href="https://www.meetup.com/rust-sao-paulo-meetup/events/316812852/"><strong>Encontro do Rust-SP - Agora no Luma</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#oceania">Oceania:</a></h5>
<ul>
<li>2026-11-24 | Barton, AU | <a href="https://www.meetup.com/rust-canberra/events/">Canberra Rust User Group</a><ul>
<li><a href="https://www.meetup.com/rust-canberra/events/316907340/"><strong>November Meetup</strong></a></li>
</ul>
</li>
</ul>
<p>If you are running a Rust event please add it to the <a href="https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com">calendar</a> to get
it mentioned here. Please remember to add a link to the event too.
Email the <a href="mailto:community-team@rust-lang.org">Rust Community Team</a> for access.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#jobs">Jobs</a></h4>
<p>Please see the latest <a href="https://www.reddit.com/r/rust/comments/1wzctie/official_rrust_whos_hiring_thread_for_jobseekers/">Who's Hiring thread on r/rust</a></p>
<h3><a class="toclink" href="https://this-week-in-rust.org/atom.xml#quote-of-the-week">Quote of the Week</a></h3>
<blockquote>
<p>we're at the 25 minute mark and still bikeshedding tabs vs spaces</p>
</blockquote>
<p>– <a href="https://hackmd.io/RUHqJ5InQkCBRs5d0WpFBA">Josh Triplett in a Library Team meeting</a></p>
<p>Thanks to <a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328/1836">Theemathas</a> for the suggestion!</p>
<p><a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328">Please submit quotes and vote for next week!</a></p>
<p>This Week in Rust is edited by:</p>
<ul>
<li><a href="https://github.com/nellshamrell">nellshamrell</a></li>
<li><a href="https://github.com/llogiq">llogiq</a></li>
<li><a href="https://github.com/ericseppanen">ericseppanen</a></li>
<li><a href="https://github.com/extrawurst">extrawurst</a></li>
<li><a href="https://github.com/U007D">U007D</a></li>
<li><a href="https://github.com/mariannegoldin">mariannegoldin</a></li>
<li><a href="https://github.com/bdillo">bdillo</a></li>
<li><a href="https://github.com/opeolluwa">opeolluwa</a></li>
<li><a href="https://github.com/bnchi">bnchi</a></li>
<li><a href="https://github.com/KannanPalani57">KannanPalani57</a></li>
<li><a href="https://github.com/tzilist">tzilist</a></li>
</ul>
<p><em>Email list hosting is sponsored by <a href="https://foundation.rust-lang.org/">The Rust Foundation</a></em></p>
<p><small><a href="https://www.reddit.com/r/rust/comments/1xi7826/this_week_in_rust_675/">Discuss on r/rust</a></small></p></div>
    </content>
    <updated>2026-10-28T04:00:00Z</updated>
    <published>2026-10-28T04:00:00Z</published>
    <category term="This Week in Rust"/>
    <author>
      <name>TWiR Contributors</name>
    </author>
    <source>
      <id>https://this-week-in-rust.org/</id>
      <link href="https://this-week-in-rust.org/" rel="alternate" type="text/html"/>
      <link href="https://this-week-in-rust.org/atom.xml" rel="self" type="application/atom+xml"/>
      <title>This Week in Rust</title>
      <updated>2026-11-11T05:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88806</id>
    <link href="https://blog.mozilla.org/en/firefox/skip-the-busywork-with-smart-window/" rel="alternate" type="text/html"/>
    <link href="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Firefox_FillFormsFaster.mp4" length="1244173" rel="enclosure" type="video/mp4"/>
    <title>Skip the busywork with Smart Window</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The days might be getting shorter, but your to-do list is only getting longer. Whether you’re getting a head start on holiday shopping or planning your next career move, Smart Window’s newest features will help you keep up.  Firefox’s opt-in AI browsing experience can now use information from tabs you choose to help fill out […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/skip-the-busywork-with-smart-window/">Skip the busywork with Smart Window</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The days might be getting shorter, but your to-do list is only getting longer. Whether you’re getting a head start on holiday shopping or planning your next career move, Smart Window’s newest features will help you keep up. </p>



<p>Firefox’s opt-in AI browsing experience can now use information from tabs you choose to help fill out forms. It can also watch web pages and notify you about specific changes you’ve asked it to track.</p>



<h3>Let your open tabs fill in the blanks</h3>



<p>Job applications ask for your work history; event registrations ask for a professional bio. If those details are already in your open tabs, Smart Window can now use pages you choose to suggest what to enter, saving you extra clicks and some Ctrl+C, Ctrl+V.</p>



<figure class="wp-block-video"><video controls="controls" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Firefox_FillFormsFaster.mp4"/></figure>



<p/>



<p>For example, Smart Window could use information from your online portfolio or professional profile to fill in your work history, or draw on those details to draft an answer to a question like “Tell me about a time when…” Firefox’s regular autofill still handles saved information such as your name and address, which can be entered directly into forms without relying on AI models.</p>



<p>To get started, click into a form field. If the form has at least four text fields that Smart Window can help fill, you’ll see “Fill from sources” appear in the dropdown, along with a recommended source page. Select “Fill from sources” to continue, or click the pencil icon to open “Edit sources” if you want to change or add tabs. Once you’ve chosen your sources, review the suggestions before filling out the form. You can edit the results before submitting; Smart Window won’t submit the form for you.</p>



<p>When you choose to use this feature, information from your selected source pages is shared with Gemini 3.1 Flash Lite, the AI model used for detecting the fields and extracting relevant information from your selected tabs. Your model choice for Smart Window chat stays the same, and saved autofill values stay on your device.<a href="https://support.mozilla.org/en-US/kb/smart-form-fill"> Learn more about how form filling works</a>.</p>



<p>This feature currently supports text fields on web forms and does not save any generated form fill data. We’re exploring support for more field types, including dropdown menus, as well as PDF forms and ways to save and manage generated  information for future forms.</p>



<h3>Give your refresh button a break</h3>



<p>A watched pot never boils, and refreshing a web page won’t make an update appear any sooner.</p>



<p>Smart Window can now watch a page for a specific update, whether that’s an item going on sale or a new job listing that includes a job title or company name that you’re following. Each task can follow up to five pages, so you can keep an eye on several stores or job boards at the same time. </p>


<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img alt="" class="wp-image-88871" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Blog_post_price_drop-1024x576.png" style="width: 675px; height: auto;" width="1024"/></figure></div>


<p>Type “/watch” in the Smart Window chat to set up a task. Describe what you’re looking for, add the pages to watch, and choose whether Firefox should check for updates on a daily or weekly basis. Those checks run only while the browser is open. </p>



<p>When there’s a match, you’ll see an update through the Tasks button in the toolbar. With desktop notifications enabled, Firefox can also notify you directly; click the notification to open the watched pages. You can have up to 15 active tasks at a time, and you can edit, pause or delete tasks. Smart Window will automatically pause tasks after 60 days without a matching change. If 90 days pass without a change, it will stop checking altogether. </p>



<p>Page monitoring uses the Qwen AI model to identify changes that match what you’re looking for. Your model choice for Smart Window chat stays the same. <a href="https://support.mozilla.org/en-US/kb/create-tasks-smart-window">Learn more about creating and managing tasks</a>.</p>



<h3>Try the latest additions</h3>



<p>These two new features are available in the Smart Window beta on desktop, in English in the U.S. and Canada, and will roll out to additional markets in the coming months.</p>



<p><a href="https://www.firefox.com/smart-window/">Try Smart Window</a> and share your experience on<a href="https://connect.mozilla.org/"> Mozilla Connect</a>. We’d love to hear how you’re using Smart Window to get things done and what you’d like it to help with next.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/skip-the-busywork-with-smart-window/">Skip the busywork with Smart Window</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-27T13:00:00Z</updated>
    <published>2026-10-27T13:00:00Z</published>
    <category term="Firefox"/>
    <category term="Firefox Features"/>
    <category term="export"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88805</id>
    <link href="https://blog.mozilla.org/en/firefox/firefox-roadmap/" rel="alternate" type="text/html"/>
    <title>Five Firefox updates you might have missed, and a look ahead</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Some of our latest Firefox updates have had big moments of their own, from the launch of our new design and built-in ad blocking on iOS to Firefox Enterprise and our partnership with NVIDIA GeForce NOW. You might’ve even spotted a few familiar internet OGs in our latest campaign. Other improvements might’ve flown under the […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/firefox-roadmap/">Five Firefox updates you might have missed, and a look ahead</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Some of our latest Firefox updates have had big moments of their own, from the launch of our <a href="https://blog.mozilla.org/en/firefox/new-firefox-design-is-here/">new design</a> and <a href="https://blog.mozilla.org/en/firefox/ad-blocker-on-ios/">built-in ad blocking on iOS</a> to <a href="https://blog.mozilla.org/en/firefox/introducing-firefox-enterprise/">Firefox Enterprise</a> and our<a href="https://blog.mozilla.org/en/firefox/firefox-nvidia-geforce-now-partnership/"> partnership with NVIDIA GeForce NOW</a>. You might’ve even spotted a few familiar internet OGs in our <a href="https://blog.mozilla.org/en/firefox/come-back-to-firefox/">latest campaign</a>. Other improvements might’ve flown under the radar until you open a PDF or move your tabs around.</p>



<p>We wanted to take a moment to highlight some of the features and improvements we’ve been working on, from recent additions you might have missed to a look at <a href="http://firefox.com/whatsnext">what’s coming next</a>.</p>



<h3>What’s new in Firefox</h3>



<ol>
<li><strong>Open PDFs faster.</strong> Firefox’s built-in PDF viewer now starts up to 45% faster on desktop, so there’s less waiting when you open a document in your browser.</li>



<li><strong>Put your Android tabs where you want them.</strong> Prefer your tabs at the bottom of the screen? You now have the option to move Firefox’s tab bar there. Go to Settings &gt; Customize to choose.</li>



<li><strong>Find your spot in a video faster.</strong> We’ve made it quicker to jump to a different point in a video on desktop, whether you’re skipping ahead in a tutorial or going back to catch something you missed.</li>



<li><strong>Keep your favorite wallpapers handy.</strong> Firefox now saves a collection of your custom wallpapers under “Your images” on New Tab on desktop, so you can switch between favorites without uploading them again.</li>



<li><strong>Save time filling out forms and keeping up with page changes. </strong>Smart Window can now help fill out online forms using information from your chosen tabs, so you don’t have to copy details back and forth. You can also ask it to watch a page and notify you when something changes, like a price drop or a new job listing, saving you from manually checking for updates. Both capabilities are available in English in the U.S. and Canada as part of the Smart Window beta. Learn more about the new features <a href="https://blog.mozilla.org/en/firefox/skip-the-busywork-with-smart-window/">here</a>.</li>
</ol>



<h3>What’s next on the <a href="https://www.firefox.com/en-US/whatsnext/">Firefox roadmap</a></h3>



<p>When we <a href="https://blog.mozilla.org/en/firefox/firefox-roadmap-152/">launched</a> our public roadmap in June, we shared plans to make everyday browsing more useful, flexible and private. We’ve now updated it with more of what’s ahead. We’re developing these features in the open, in close partnership with our contributors, and will share more about release timing as each feature gets ready for more people to try. </p>



<p>Here’s a look at what’s in the works:</p>



<ul>
<li><strong>Keep what you need in view.</strong> We heard your request for a way to keep a page visible while browsing. Mini Window will let you pop a tab, or part of a page, into a small floating window, so recipes or instructions stay in view while you work in another tab.</li>



<li><strong>Listen to pages.</strong> Give your eyes a break. Firefox will soon read articles and other web content aloud on desktop and Android, so you can listen while doing other things – even with your phone’s screen off. </li>



<li><strong>Take your reading offline.</strong> No connection? No problem. Offline mode on Android will let you save articles ahead of time to read or listen to without internet access, perfect for flights and commutes with spotty service.</li>



<li><strong>Turn speech into text on desktop.</strong> We’re bringing speech recognition to Firefox on desktop, so websites that use Firefox’s built-in capability can offer voice input and captions without sending your audio to a server. Those sites receive the text, while your audio stays on your device. After downloading the speech recognition model, transcription will work offline, too.</li>



<li><strong>Choose how VPN works for each site.</strong> Since bringing <a href="https://blog.mozilla.org/en/firefox/built-in-vpn/">free built-in VPN</a> to Firefox on desktop and Android (iOS coming soon), we’re now adding the ability to set website rules so you can choose how VPN works on a site-by-site basis.</li>



<li><strong>Clear browsing data directly from your toolbar.</strong> We’re bringing Private Window’s familiar <img alt="&#x1F525;" class="wp-smiley" src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f525.png" style="height: 1em;"/> button to Classic Window on desktop, so you can quickly choose what browsing data to delete without digging through settings.</li>
</ul>



<h3>Keep shaping Firefox with us</h3>



<p>Try the latest updates and explore the<a href="https://www.firefox.com/en-US/whatsnext/"> Firefox roadmap</a> for more of what we’re working on. If there’s something you’re looking forward to, or something you’d like us to improve, tell us on<a href="https://connect.mozilla.org/"> Mozilla Connect</a>. Your feedback helps shape what comes next.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/firefox-roadmap/">Five Firefox updates you might have missed, and a look ahead</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-27T13:00:00Z</updated>
    <published>2026-10-27T13:00:00Z</published>
    <category term="Firefox"/>
    <category term="Firefox Features"/>
    <category term="export"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/netpolicy/?p=2633</id>
    <link href="https://blog.mozilla.org/netpolicy/2026/10/26/a-reason-for-optimism-on-us-competition-policy/" rel="alternate" type="text/html"/>
    <title>A Reason for Optimism on US Competition Policy</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Mozilla has long called for US antitrust reform in digital markets. After several false starts, real change has yet to materialize. In the meantime, dominant tech players have further entrenched … <a class="go" href="https://blog.mozilla.org/netpolicy/2026/10/26/a-reason-for-optimism-on-us-competition-policy/">Read more</a></p>
<p>The post <a href="https://blog.mozilla.org/netpolicy/2026/10/26/a-reason-for-optimism-on-us-competition-policy/">A Reason for Optimism on US Competition Policy</a> appeared first on <a href="https://blog.mozilla.org/netpolicy">Open Policy &amp; Advocacy</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Mozilla has <a href="https://blog.mozilla.org/en/mozilla/calling-for-antitrust-reform/">long</a> <a href="https://blog.mozilla.org/netpolicy/2026/06/11/a-handful-of-companies-control-the-web-aicoa-can-change-that/">called</a> for US antitrust reform in digital markets. After several false starts, real change has yet to materialize. In the meantime, dominant tech players have further entrenched their hold, limiting choice and degrading people’s experiences. Integration of new AI services into existing ecosystems is enabling those same companies to perpetuate and accelerate that power.</p>
<p>But, there’s reason for optimism. Momentum is again building toward antitrust reform, and this time feels different. With support from start ups, middle tech challengers, civil society, and think tanks across the political spectrum – and most importantly, legislative champions in Congress – it’s clear that the time is coming.</p>
<p>This is a debate about how the largest tech companies control the products and innovations in the market, and access to the services the people use every day. At the center are questions about user choice, interoperability, privacy, security and whether independent innovators have an opportunity to compete on merit.</p>
<p>These topics were the focus of a <a href="https://www.youtube.com/watch?v=JQJ79eFuvCo&amp;">recent Senate briefing hosted by Bull Moose Project and Public Knowledge</a>, diving in on three competition bills before the Senate Judiciary Committee: <a href="https://www.judiciary.senate.gov/press/rep/releases/grassley-klobuchar-introduce-bipartisan-legislation-to-lower-prices-expand-consumer-choice-and-restore-online-competition-in-the-digital-marketplace">The American Innovation and Choice Online Act (AICOA)</a>, the Open App Markets Act (OAMA), and the America Act. The discussion brought together policy experts and industry voices, including Mozilla, to explore how competition policy can improve people’s experiences online and the ability of challenger companies to succeed.</p>
<p>The conversation covered a range of issues, from whether existing antitrust laws are equipped to address today’s digital markets, to misguided claims about what might happen if we pass antitrust reform, and the ways that dominant platforms dictate how people discover and use competing products. For Mozilla, an important part of the conversation is what meaningful user choice looks like in practice. People should be able to choose alternatives, and those choices should be respected. But structural barriers can make it harder for independent players to compete on merit, and for people to access options, including independent products that innovate in areas like privacy and security. Competition creates stronger incentives for companies to build better, and to give people the protections and products that they deserve.</p>
<p>Antitrust reform is not about punishing companies for being successful. It’s about ensuring that independent players can provide the best possible versions of their products, and that people can truly benefit from those innovations. That’s why Mozilla, alongside many others, has long <a href="https://www.mozillafoundation.org/en/blog/mozilla-community-places-full-page-washington-post-ad-supporting-aicoa/">championed</a> AICOA and worked to tackle longstanding anticompetitive practices. We’re excited to see newly energized support across the public and private sector, and for the next steps in advancing legislation.</p>
<p>The post <a href="https://blog.mozilla.org/netpolicy/2026/10/26/a-reason-for-optimism-on-us-competition-policy/">A Reason for Optimism on US Competition Policy</a> appeared first on <a href="https://blog.mozilla.org/netpolicy">Open Policy &amp; Advocacy</a>.</p></div>
    </content>
    <updated>2026-10-27T00:05:42Z</updated>
    <published>2026-10-27T00:05:42Z</published>
    <category term="Uncategorized"/>
    <author>
      <name>Jenn Taylor Hodges</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/netpolicy/</id>
      <link href="https://blog.mozilla.org/netpolicy/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/netpolicy/" rel="alternate" type="text/html"/>
      <subtitle>Mozilla's official blog on open Internet policy initiatives and developments</subtitle>
      <title>Open Policy &amp; Advocacy</title>
      <updated>2026-10-27T00:05:42Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/addons/?p=9309</id>
    <link href="https://blog.mozilla.org/addons/2026/10/26/developer-spotlight-profile-manager-pro/" rel="alternate" type="text/html"/>
    <title>Developer Spotlight: Profile Manager Pro</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>If your online activities involve logging in and out of a lot of different accounts — often on the same website — Profile Manager Pro can be a time-saving game … <a class="go" href="https://blog.mozilla.org/addons/2026/10/26/developer-spotlight-profile-manager-pro/">Read more</a></p>
<p>The post <a href="https://blog.mozilla.org/addons/2026/10/26/developer-spotlight-profile-manager-pro/">Developer Spotlight: Profile Manager Pro</a> appeared first on <a href="https://blog.mozilla.org/addons">Mozilla Add-ons Community Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>If your online activities involve logging in and out of a lot of different accounts — often on the same website —<a href="https://addons.mozilla.org/en-US/firefox/addon/profile-manager-pro/"> Profile Manager Pro</a> can be a time-saving game changer. The extension provides a one-click login process for multiple online accounts, so you can effortlessly jump between profiles. From social media management to web development, QA testing and more, Profile Manager Pro removes the painstaking friction of constant account switching.</p>
<div class="wp-caption alignleft" id="attachment_9310" style="width: 410px;"><a href="https://addons.mozilla.org/en-US/firefox/addon/profile-manager-pro/"><img alt="" class="wp-image-9310" height="597" src="https://blog.mozilla.org/addons/files/2026/10/blog_a-580x866.png" width="400"/></a><p class="wp-caption-text" id="caption-attachment-9310">Simple UI makes it easy to jump between multiple accounts across various sites.</p></div>
<p>“One of the most interesting aspects of developing Profile Manager Pro is realizing how many different workflows can benefit from efficient account switching,” explains its creator, Islam Elsayed. Consider developers who need to save sessions for different roles, such as admins, moderators or regular users, to test functionality; freelancers working across multiple client dashboards; or support professionals investigating account-specific behavior. The potential uses for Profile Manager Pro are practically limitless.</p>
<p>Elsayed makes clear that Profile Manager Pro isn’t intended to replace Firefox’s full browser profiles; rather, the aim is to make it easier to save, organize, and restore individual website sessions within a browser environment. “I think that distinction is important because it illustrates how browser extensions can complement existing browser capabilities by addressing very specific everyday frustrations.”</p>
<p>While the extension provides a fairly straightforward function, its design and development were anything but simple. Elsayed says his biggest development hurdle was creating a reliable account-switching experience across websites that handle authentication and session management differently. Modern websites often use tangled combinations of cookies, browser storage, authentication tokens and other complex security mechanisms. A technical solution that works perfectly on one website may not function at all on another. “These challenges taught me an important lesson: The best productivity tools often hide considerable technical complexity behind a simple user experience.”</p>
<p>Another challenge is balancing functionality with user privacy and security. Session-management extensions interact with sensitive browser data, so Elsayed goes to great lengths to ensure user protection — starting with a local-first approach to development. Saved session information stays within the user’s browser environment by default. Users don’t need to create a Profile Manager Pro account or send their browsing sessions to a third-party server. The extension also offers optional encrypted Google Drive sync, providing even more control over stored data.</p>
<p>“Responsible session management is essential,” says Elsayed. “This is why I believe privacy should be considered throughout the design process rather than an afterthought. Ultimately, my goal is to give users convenience without requiring them to surrender unnecessary control over their data.”</p>
<p>As for future development plans, Elsayed frames Profile Manager Pro as an “evolving project.” He intends to focus on optimizing the profile management system and improving backup and sync experiences.</p>
<p>“My long-term vision for Profile Manager Pro is to become an increasingly powerful yet lightweight tool for managing online identities and workflows,” says Elsayed. “I believe thoughtful improvements based on real user needs are more valuable than adding features simply for the sake of adding them. For me, the most rewarding part of development is solving those complex problems so users don’t have to think about them.”</p>
<hr/>
<p><i>Do you have an intriguing extension development story? Do tell! Maybe your story should appear on this blog. Contact us at </i><b><i>amo-featured [at] mozilla [dot] org</i></b><i> and let us know a bit about your extension development journey.</i></p>
<p>The post <a href="https://blog.mozilla.org/addons/2026/10/26/developer-spotlight-profile-manager-pro/">Developer Spotlight: Profile Manager Pro</a> appeared first on <a href="https://blog.mozilla.org/addons">Mozilla Add-ons Community Blog</a>.</p></div>
    </content>
    <updated>2026-10-26T22:24:16Z</updated>
    <published>2026-10-26T22:24:16Z</published>
    <category term="developers"/>
    <category term="featured addons"/>
    <category term="spotlight"/>
    <author>
      <name>Scott DeVaney</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/addons/</id>
      <link href="https://blog.mozilla.org/addons/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/addons/" rel="alternate" type="text/html"/>
      <title>Mozilla Add-ons Community Blog</title>
      <updated>2026-10-28T21:47:25Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/</id>
    <link href="https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/" rel="alternate" title="How to fund Rust contributors" type="text/html"/>
    <title xml:lang="en">How to fund Rust contributors</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><blockquote>
<p>TLDR:</p>
<ul>
<li>To fund general maintenance, donate to the <a href="https://github.com/sponsors/rustfoundation" rel="external">Rust Foundation Maintainers Fund</a> or sponsor the <a href="https://rustnl.org/maintainers/" rel="external">RustNL Maintainers Team</a></li>
<li>To fund specific features and improvements, sponsor <a href="https://goals.rust-lang.org/2026/funding.html" rel="external">fundable Rust Project Goals</a></li>
<li>To fund individual contributors, donate to their <a href="https://rust-lang.org/funding/#people" rel="external">GitHub Sponsors</a> accounts</li>
</ul>
</blockquote>
<p>There is always so much to do in the Rust Project! New features to implement, bugs to fix, performance optimizations to make, issues to triage… It takes a lot of work to keep our high bar of quality while also shipping new features and improvements. And the workload keeps increasing with the continuous growth of Rust adoption.</p>
<p>As is unfortunately common in open source projects, a large fraction of that work is currently done by volunteers. That causes various issues, such as people burning out or complex features taking many years to ship.</p>
<p>Unsurprisingly, one of the best ways to help improve that is to get more people who work on Rust funded! This year, several funding initiatives started ramping up, and we already experience many positive effects. They helped us improve the maintenance status of critical Rust projects and make significant progress on several long-awaited features, such as allocators, the never type, the next trait solver or the Polonius borrow checker. However, only a fraction of people working on Rust are currently funded for their work.</p>
<p>We know that there are Rust users, both individuals and companies, who would like to help improve Rust by funding it, but it might not always be obvious <em>how exactly</em> to do that. This post thus provides suggestions on how you can support the development of Rust in three ways.</p>
<p>If you're unsure which option fits, or would like to discuss funding on behalf of your company, please contact the <a href="mailto:funding@rust-lang.org">Funding team</a>.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/#fund-general-maintenance"/>
Fund general maintenance</h3>
<p><a href="https://blog.rust-lang.org/inside-rust/2026/01/12/what-is-maintenance-anyway/" rel="external">Maintenance</a> is a continuous process required to keep Rust (or any software project for that matter) working. It consists of two main activities. The first is general housekeeping, such as ensuring that Continuous Integration works, dependencies are kept up-to-date and issues, bugs and security incidents are promptly triaged and resolved. The second is performing refactorings and code reviews, which ensures that the codebase will be able to evolve and continuously ship new features, without accruing extensive technical debt.</p>
<p>Having quality maintenance is crucial for the long-term health of Rust, yet it is typically very difficult to find funding for it; funders often want to sponsor specific new features, rather than just "keeping the lights on". However, without sufficient maintenance, it becomes much more difficult, and much slower, to ship new features. Improving the maintenance of Rust thus also helps us ship features and improvements faster, though the effects are sometimes only observable over longer periods of time.</p>
<p>Funding maintenance is a great choice if you want to let us decide how best to improve Rust. The Rust <a href="https://www.rust-lang.org/governance/teams/launching-pad#team-funding" rel="external">Funding team</a> continuously looks for Rust teams and projects that require help with their maintenance efforts, and allocates available funds to Rust maintainers who could help improve the situation.</p>
<p><strong>To fund Rust maintainers, consider donating to the <a href="https://github.com/sponsors/rustfoundation" rel="external">Rust Foundation Maintainers Fund</a> or sponsoring the <a href="https://rustnl.org/maintainers/" rel="external">RustNL Maintainers Team</a>.</strong></p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/#fund-specific-features-and-improvements"/>
Fund specific features and improvements</h3>
<p>There are always many Rust improvements and new features that are in progress. We track some of those initiatives through <a href="https://goals.rust-lang.org/2026/goals.html" rel="external">Rust Project Goals</a>. Each Goal describes a specific improvement to Rust: what it is, who is going to develop and drive it forward and which Rust teams are willing to help reviewing and maintaining it.</p>
<p>Some of those Goals are looking for funding. Either to help their owner dedicate time and focus to push the given feature forward, or to fund maintainers who will perform refactorings necessary to unblock that feature and review its implementation. Often funding is required for both. When a Goal is properly funded, the probability that it will achieve its milestones is much higher, which then translates in the given improvement being shipped sooner to Rust users.</p>
<p>Funding Project Goals is a great choice if you want to help push forward specific Rust features or Rust toolchain improvements that will benefit you or your company.</p>
<p><strong>To fund contributors working on Project Goals, consider taking a look at <a href="https://goals.rust-lang.org/2026/funding.html" rel="external">Goals that need funding</a> and reaching out to their funding contact.</strong> If in doubt how to proceed, reach out to the Rust <a href="mailto:funding@rust-lang.org">Funding team</a>.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/#fund-individual-contributors"/>
Fund individual contributors</h3>
<p>There are <a href="https://rust-lang.org/governance/people/" rel="external">hundreds</a> of people in the Rust Project who continuously work on improving Rust. Some of them have personal fundraising profiles (e.g. on GitHub Sponsors), which allows you to support them directly.</p>
<p>There might be various reasons for supporting a specific person. Maybe they are maintaining a crate that you love to use, maybe you like reading their blog posts, or maybe you are simply a fan of the work that they do. Whatever the reason, we are sure that they would appreciate your support!</p>
<p>Funding individual contributors is a great choice if you want to directly support Rust contributors whose work you appreciate.</p>
<p><strong>To fund individual Rust contributors, check out their GitHub profile or personal website to see what options there are for supporting them.</strong> You can also examine our <a href="https://rust-lang.org/funding/#people" rel="external">list</a> of Rust Project members who can be supported through GitHub Sponsors<sup class="footnote-reference" id="fr-non-exhaustive-1"><a href="https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/#fn-non-exhaustive">[1]</a></sup>.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/#conclusion"/>
Conclusion</h3>
<p>We hope that this post is useful to anyone who would potentially like to invest funds into making Rust better. You can also find a shortened version of the "how to fund Rust guide" at the <a href="http://rust-lang.org/funding" rel="external">Funding page</a> of the Rust website, or check out a RustConf 2026 talk by <a href="https://www.youtube.com/watch?v=-VLo5g-AfJ8" rel="external">Niko Matsakis</a> about how Project Goals and their funding works.</p>
<p>If you are a company looking to fund the development of Rust, consider joining the <a href="https://rustfoundation.org/rust-commercial-network/" rel="external">Rust Commercial Network</a>. Joining the network is free, and Rust Foundation membership is not required. It can help you find opportunities for funding improvements in specific areas related to Rust usage (e.g. user interfaces, language interop, supply chain security, etc.) and collaborate on funding Rust development with other companies.</p>
<p>There are of course other ways of helping Rust other than donating funds. For example, you can check out Project Goals that are <a href="https://goals.rust-lang.org/2026/contributors.html" rel="external">looking for contributors</a> or more generally check our <a href="https://forge.rust-lang.org/how-to-start-contributing.html" rel="external">contributor onboarding guide</a>. Companies can also help by giving employees paid time to contribute upstream, or by hiring Rust contributors to do that work. One possible model is the <a href="https://rustfoundation.org/media/welcoming-jess-izen-as-engineer-in-residence-at-the-rust-foundation/" rel="external">Engineer in Residence</a> role, that was recently established in the Rust Foundation.</p>
<section class="footnotes">
<ol class="footnotes-list">
<li id="fn-non-exhaustive">
<p>Note that this list is not exhaustive; there are some Project members who accept donations through GitHub Sponsors (or another fundraising platform), but did not opt into being listed on this page. <a href="https://blog.rust-lang.org/2026/10/26/how-to-fund-rust-contributors/#fr-non-exhaustive-1">↩</a></p>
</li>
</ol>
</section></div>
    </content>
    <updated>2026-10-26T00:00:00Z</updated>
    <published>2026-10-26T00:00:00Z</published>
    <author>
      <name>Jakub Beránek</name>
    </author>
    <source>
      <id>https://blog.rust-lang.org/</id>
      <author>
        <name>Maintained by the Rust Teams.</name>
        <uri>https://github.com/rust-lang/blog.rust-lang.org/</uri>
      </author>
      <link href="https://blog.rust-lang.org/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://blog.rust-lang.org/" rel="alternate" type="text/html"/>
      <subtitle xml:lang="en">Empowering everyone to build reliable and efficient software.</subtitle>
      <title xml:lang="en">Rust Blog</title>
      <updated>2026-11-13T09:01:38Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88394</id>
    <link href="https://blog.mozilla.org/en/firefox/come-back-to-firefox/" rel="alternate" type="text/html"/>
    <title>Firefox reunites meme royalty to remind you what the internet used to feel like</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>A group of familiar faces from the early web just got back together to ask an important question: What happened to the internet? Sure, there was a time when it was a little less polished, and a lot less speedy, but it was yours. Overly Attached Girlfriend may have wanted to know everything about you, […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/come-back-to-firefox/">Firefox reunites meme royalty to remind you what the internet used to feel like</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>A group of familiar faces from the early web just got back together to ask an important question: What happened to the internet?</p>



<p>Sure, there was a time when it was a little less polished, and a lot less speedy, but it was <em>yours</em>. Overly Attached Girlfriend may have wanted to know everything about you, but your browser didn’t need to. Dancing Matt boogied all over the world, without any corporations tracking him or selling his personal data. And while Annoying Orange is incredibly annoying, he’s not as annoying as forced AI features.</p>



<p>These beloved early internet personalities remind us of a time when surfing the web felt open, organic, and most importantly, personal. And good news: With Firefox, it still can.</p>



<p>That’s why we’re teaming up with these icons to remind people what our browser offers, and show those who wandered off why now is the time to come back.</p>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">

</div></figure>



<h3><strong><strong>The team behind the comeback</strong></strong></h3>



<p>For Mozilla Chief Marketing Officer John Solomon, the aim of the campaign started with winning back people who originally loved and used Firefox.</p>



<p>“I kept going back to Firefox’s heyday, when the internet was really fun, weird, and interesting. The challenge was: how do you lean on nostalgia and heritage, but not be stuck in the past?”</p>



<p>The campaign was created by <a href="https://www.webelievers.com/home">We Believers</a>, one of the world’s most awarded independent agencies, with production handled by <a href="https://nobodys.film/">nobodys</a> and direction by the <a href="https://www.sunnysixteen.com/">Sunny Sixteen</a> collective.</p>



<p>“We wanted to create an idea that truly belongs to Firefox — a challenger browser that helped shape the internet’s golden years and stayed independent as Big Tech took over. The goal? Remind former users that what they loved about Firefox matters more than ever now,” said Gustavo Lauria, Founder and CCO at We Believers.</p>



<p>Solomon said the finished campaign achieves the goal of embracing Firefox’s history without living in it: “Our partners really cracked it. We wanted to remind people of what made the internet so wonderful in the first place. These are people who helped make it strange, creative, surprising, and fun. None of them were trying to go viral. They were normal, everyday people who were using the internet. That’s the way the internet should be and why we feel it’s a great moment for Firefox. Always independent and unlike big tech, not trying to extract more from everyday people.”</p>



<h3><strong>The internet you remember is still out there</strong></h3>



<p>Whether you used Firefox back in the day, or are simply looking for a better browsing experience, we’re still here, staying true to the <a href="https://www.mozilla.org/about/manifesto/">values we were built on</a>. We believe the internet should be open, accessible, and shaped by the people who use it, not just the platforms that profit from their attention and data.</p>



<p>This means a web where you can explore without feeling tracked or used for profit, where you decide for yourself how new technology fits into your life, and you can trust that your browser protects you by default. Firefox has <a href="https://www.firefox.com/user-privacy/">built-in privacy protections</a> to help limit tracking, lets you decide <a href="https://blog.mozilla.org/firefox/firefox-ai-on-your-terms/">if AI features appear and customize how they behave</a>, and uses open source code that <a href="https://firefox-source-docs.mozilla.org/contributing/index.html">anyone can see</a>. To learn more about what sets Firefox apart, check out <a href="https://blog.mozilla.org/en/firefox/5-reasons-to-choose-firefox/">five reasons to choose the browser that puts you first</a>.</p>



<p>We know a better internet isn’t built by finding new ways to capture your attention or information. It’s about giving you more freedom to make the web your own.</p>



<h3><strong>The web is yours to explore</strong></h3>



<p>The internet has changed a lot since Numa Numa Guy first danced his way into our collective memory. But the things that made it magical – creativity, curiosity, community, and the freedom to explore – are still worth protecting.</p>



<p>Firefox has championed those values since the beginning, and we’re not giving up on them now. That’s why we’re celebrating the people who helped make the early web what it was, while reminding everyone that a more open, human internet is still an option.</p>



<p>The early days of the internet may be behind us, but the spirit doesn’t have to be. Experience it for yourself. Now more than ever: <a href="https://mzl.la/welcomebackfirefox">come back to Firefox</a>.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/come-back-to-firefox/">Firefox reunites meme royalty to remind you what the internet used to feel like</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-25T11:58:00Z</updated>
    <published>2026-10-25T11:58:00Z</published>
    <category term="Firefox"/>
    <category term="export"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149916</id>
    <link href="https://discourse.mozilla.org/t/firefox-profiler-deployment-october-22-2026/149916" rel="alternate" type="text/html"/>
    <title>Firefox Profiler Deployment (October 22, 2026)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The latest version of the <a href="https://profiler.firefox.com/" rel="noopener nofollow ugc">Firefox Profiler</a> is now live! Check out the full changelog below to see what’s changed:</p>
<p><strong>Highlights:</strong></p>
<ul>
<li>[fatadel] Make CompositorScreenshot markers schema-based (<span class="hashtag-raw">#6261</span>)</li>
<li>[fatadel] Expose and clear URL-imported call tree search in the CLI (<span class="hashtag-raw">#6387</span>)</li>
<li>[Markus Stange] Make the scrollable editor view in the source view cover the full height of the panel, even if the source code is short. (<span class="hashtag-raw">#6405</span>)</li>
<li>[Nazım Can Altınova] Add `–js-sources-from-func-names` to `profiler-edit` (<span class="hashtag-raw">#6394</span>)</li>
<li>[fatadel] Use fractional seconds with adaptive precision for CLI marker timestamps (<span class="hashtag-raw">#6384</span>)</li>
<li>[Markus Stange] Switch to TypeScript 7 (tsgo) and replace ESLint with oxlint (<span class="hashtag-raw">#6354</span>)</li>
</ul>
<p><strong>Other Changes:</strong></p>
<ul>
<li>[Nazım Can Altınova] Fix the upload progress bar not showing in light mode (<span class="hashtag-raw">#6348</span>)</li>
<li>[fatadel] Bump profiler-cli version to 0.12.0 (<span class="hashtag-raw">#6416</span>)</li>
<li>[fatadel] <img alt=":clockwise_vertical_arrows:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/clockwise_vertical_arrows.png?v=15" title=":clockwise_vertical_arrows:" width="20"/> Sync: l10n → main (October 22, 2026) (<span class="hashtag-raw">#6415</span>)</li>
<li>[Markus Stange] Some preparations for a function list panel (<span class="hashtag-raw">#6401</span>)</li>
<li>[Nazım Can Altınova] Look for a source file’s address proof in all of its frames (<span class="hashtag-raw">#6407</span>)</li>
<li>[Nazım Can Altınova] Silence profile loader logs in profile-querier-url tests (<span class="hashtag-raw">#6409</span>)</li>
<li>[Markus Stange] Use inverted transforms in the tests for inverted call node paths. (<span class="hashtag-raw">#6393</span>)</li>
<li>[Markus Stange] Accept more fields from symbolication. (<span class="hashtag-raw">#6373</span>)</li>
<li>[Markus Stange] Support index source maps. (<span class="hashtag-raw">#6399</span>)</li>
</ul>
<p>Big thanks to our amazing localizers for making this release possible:</p>
<ul>
<li>el: Jim Spentzos</li>
<li>uk: Lobodzets, uya2521, Іhor Hordiichuk</li>
</ul>
<p>Find out more about the Firefox Profiler on <a href="https://profiler.firefox.com" rel="noopener nofollow ugc">profiler.firefox.com</a>! If you have any questions, join the discussion on our <a href="https://chat.mozilla.org/#/room/#profiler:mozilla.org" rel="noopener nofollow ugc">Matrix channel</a>!</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/firefox-profiler-deployment-october-22-2026/149916">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-22T17:01:29Z</updated>
    <published>2026-10-22T17:01:29Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>fatadel</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/firefox-profiler-deployment-october-22-2026/149916.rss" title="Firefox Profiler Deployment (October 22, 2026)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.nightly.mozilla.org/?p=2149</id>
    <link href="https://blog.nightly.mozilla.org/2026/10/22/three-cheers-for-volunteers-these-weeks-in-firefox-issue-211/" rel="alternate" type="text/html"/>
    <title>Three Cheers for Volunteers! – These Weeks in Firefox: Issue 211</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Highlights Here are some big-ticket volunteer contributions this week: Thank you to volunteer contributor Cornelius, who made console evaluation able to re-declare let and const variables in our DevTools! Thank … <a class="go" href="https://blog.nightly.mozilla.org/2026/10/22/three-cheers-for-volunteers-these-weeks-in-firefox-issue-211/">Read more</a></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><h3>Highlights</h3>
<ul>
<li>Here are some big-ticket volunteer contributions this week:
<ul>
<li>Thank you to volunteer contributor <a href="https://bugzilla.mozilla.org/user_profile?user_id=790857">Cornelius</a>, who <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1257088">made console evaluation able to re-declare let and const variables</a> in our DevTools!</li>
<li>Thank you to F3tch, who landed several patches to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2070577">allow setting of camera and microphone permissions</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1492357">reject zero-sized screenshots</a>, and add a vendor-specific <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2068045">WebDriver BiDi command for listing installed extensions</a>, as well as <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1917288">update cookie test expirations</a>.</li>
<li>Thank you to SMRehan, who landed a (disabled by default) mode that lets Picture-in-Picture open when the browsing window is occluded (as opposed to when changing tabs).
<ul>
<li>This can be tested by setting media.videocontrols.picture-in-picture.enable-when-occluded.enabled to true</li>
</ul>
</li>
<li>In Nightly 160, we have <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2070673">enabled the playback speed feature for Picture-in-Picture by default</a>:</li>
<li><img alt="New playback speed settings in the Picture-in-Picture player, including a slider and five different presets to select from." class="aligncenter size-full wp-image-2146" height="964" src="https://blog.nightly.mozilla.org/files/2026/10/image1.png" width="1538"/>Thank you to volunteer contributor Simon Rosen for the bulk of the initial work on this!</li>
</ul>
</li>
<li>The custom wallpaper library for newtab is now available, starting in Firefox 158, so you can now store multiple custom wallpapers:</li>
</ul>
<p><img alt="Four preset images in the NewTab custom wallpaper library. plus an option to upload your own image." class="aligncenter size-full wp-image-2142" height="299" src="https://blog.nightly.mozilla.org/files/2026/10/image5.png" width="401"/></p>
<h3>Friends of the Firefox team</h3>
<h3><a href="https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20(excluding%20employees)&amp;quicksearch=2070237%2C1992418%2C2043208%2C2066209%2C2070732%2C2072055%2C1719394%2C1979386%2C2067180%2C2072520%2C2066620%2C2069768%2C2068045%2C2071752%2C2068108%2C2072519%2C1987276%2C2069781%2C2071442%2C2070873%2C2035151%2C2072275%2C2070204%2C1973441%2C2051745%2C2062651%2C1917288%2C1957843%2C2070577%2C1492357%2C1918041%2C2072737%2C1933992%2C2058364%2C2072596%2C2072513%2C2073700%2C2073314%2C2069438%2C1973071%2C2075069%2C1773060%2C1257088%2C2068828%2C2069726%2C1666654%2C2078151%2C2050219%2C2057771%2C2077441%2C2076831%2C2032256%2C2071844%2C2073572%2C2080007%2C1877223%2C1986064%2C2080080%2C2080310%2C2076779">Resolved bugs (excluding employees)</a></h3>
<p><a href="https://github.com/niklasbaumgardner/NewContributorScraper">Script to find new contributors from bug list</a></p>
<h4>Volunteers that fixed more than one bug</h4>
<ul>
<li>:Vincent</li>
<li>Amadi</li>
<li>any1here</li>
<li>Duncan McIntosh [:dmcintosh]</li>
<li>f3tch [:f3tchcodes]</li>
<li>ianlewisuk1</li>
<li>Ivan Smagin</li>
<li>Khalid AlHaddad</li>
<li>Logan Rosen [:Logan]</li>
<li>Mayank Bansal</li>
<li>Vir Patel</li>
</ul>
<h4>New contributors (🌟 = first patch)</h4>
<ul>
<li>Ahmed ElGendy: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2076779">Add a `(inline-)grid-lanes` badge in the markup view for element with display: (inline-)grid-lanes</a></li>
<li>Mubashshir: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072519">Extension icon missing in old sidebar switcher</a></li>
<li>Anton Bershanskyi: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2080310">Introduce browser.runtime.PlatformArch.ARM64</a></li>
<li>Amadi:
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1918041">Clicking the New Tab button does not show pressed appearance with vertical tabs</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2035151">Not localized search matches in Devtools</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2067180">Remove unused WebsiteFilter module getter from browser.js</a></li>
</ul>
</li>
<li>Caleb Pickard: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2058364">New sidebar revision does not have “By Most Visited” as a sort option for History</a></li>
<li>Daniel mungai chege: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072513">Add autocomplete for CSS random()</a></li>
<li>dchen705: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1877223">syntax and handling of async runtime.onMessage listeners is confusing</a></li>
<li>Diego: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2068108">Pressing ctrl+shift+numpad1 causes tab to be moved to end of tab list regardless of NumLock</a></li>
<li>f3tch [:f3tchcodes]:
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1492357">“WebDriver:TakeScreenshot” doens’t throw “unable to capture screen” error if height or width of captured image is 0</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1917288">Increase expiry date range for network cookie tests</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1957843">[wdspec] ValueError: “list.remove(x): x not in list” for “self.event_listeners[name].remove(fn)”</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2068045">[firefox-devtools-mcp] Support webextensions.moz:listExtensions command in WebDriver BiDi</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2070577">Allow “permissions.setPermission” and “WebDriver:SetPermission” to set camera and microphone permissions</a></li>
</ul>
</li>
<li>Ole Baumann [:darkintaqt]:
<ul>
<li>🌟 <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2070873">Drop the redundant level from UrlbarUtils.getBackspaceBlock’s return value</a></li>
</ul>
</li>
<li>ianlewisuk1:
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2032256">Add Nova icons for Firefox :: Messaging System</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072737">The corrupt_file telemetry metric counts session files with an incompatible format version as healthy files</a></li>
</ul>
</li>
<li>Jakub Stasiak [:jstasiak]: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1719394">Early WebSocket messages can be missing in the Network tab</a></li>
<li>Jaron: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2069726">Show the remote control stripe on the address bar only</a></li>
<li>🌟 Lavindeep: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2069768">Subprocess fcntl binding is not variadic, causing incorrect pipe flags and possible native-host launch failures on Apple silicon</a></li>
<li>🌟 Sho Sakuma: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072520">Fix WP_WIN and WP_MACOSX typos in LaunchChild’s #endif comments</a></li>
<li>Raúl: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2062651">Remove dead PanelUI-fxa-menu-setup-sync-container from the account menu</a></li>
<li>🌟 Jason Salerno: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2076831">Remove the unused tooltip attribute from the urlbar view markup</a></li>
<li>Ivan Smagin:
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1986064">Improve pref-handling in xpcshell test ‘test_ext_contentscript_module_import.js’</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1987276">Add test for unknown content dialog for downloads with a mimetype that doesn’t have an associated file extension</a></li>
</ul>
</li>
<li>Nazeer Ahmed Shaikh: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2050219">Instrumentation tests on artifact builds do not check `object` metric schema</a></li>
<li>Vir Patel:
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2073572">Make DisplayMenuBar pass a string to runOncePerModification</a></li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2073700">Handle the “cleared” perm-changed notification in the permission exceptions dialogs</a></li>
</ul>
</li>
<li>Valerie Racine (:v-racine): <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2071442">The corrupt_file telemetry metric counts unrecognised session file read errors as healthy files</a></li>
<li>🌟 Yeet: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1973441">Saved tab groups not actually saved if browser crashes</a></li>
</ul>
<h3>Project Updates</h3>
<h4>Add-ons / Web Extensions</h4>
<h5>Addon Manager &amp; about:addons</h5>
<ul>
<li>Removed the colorway migration code and the about:addons UI informing users about colorways on AMO –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1990883"> Bug 1990883</a>
<ul>
<li>Thanks to Jason Birchall (from AMO engineering) for collaborating with us on this.</li>
</ul>
</li>
<li>As part of about:addons Nova restyling followups
<ul>
<li>Parameterized the built-in theme preview images, and fixed the default theme previews rendering with the wrong colors when about:addons uses the opposite color scheme (regression introduced and fixed within Firefox 158) –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2070289"> Bug 2070289</a> /<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074428"> Bug 2074428</a>
<ul>
<li>Thanks to Emilio Cobos Álvarez for driving the theme preview parameterization.</li>
</ul>
</li>
<li>Fixed the Nova theme preview gradients being mirrored in RTL locales –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2073245"> Bug 2073245</a></li>
<li>Hid the (non-localized) theme card descriptions in the about:addons themes list view, fixed in Firefox 158 and uplifted to Firefox 157 –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2071337"> Bug 2071337</a></li>
<li>Fixed the per-add-on-card message bar styling in about:addons to better match the Nova designs –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2079672"> Bug 2079672</a></li>
</ul>
</li>
<li>Avoided redundant AMO metadata update checks when the app locale is unchanged –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2052032"> Bug 2052032</a></li>
<li>Added options to AddonManager.getInstallForURL to validate the add-on type, id and/or version before installing –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1973071"> Bug 1973071</a></li>
<li>Dictionary add-ons are now required to be signed, starting in Firefox 160 –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1753276"> Bug 1753276</a></li>
</ul>
<h5>WebExtensions Framework</h5>
<ul>
<li>As part of work to refactor about:newtab built-in widgets in their own privileged extensions, allowed about:newtab pages to load extension pages as subframes without listing them in web_accessible_resources –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2070235"> Bug 2070235</a></li>
<li>Improved pref handling in the test_ext_contentscript_module_import.js xpcshell test by using pref_set –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1986064"> Bug 1986064</a>
<ul>
<li>Thanks to Ivan Smagin for the cleanup in the content script module import test.</li>
</ul>
</li>
</ul>
<h5>WebExtension APIs</h5>
<ul>
<li>Fixed publicSuffix.isKnownSuffix to throw for invalid host names, in line with the API proposal, MDN and Chromium –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2066620"> Bug 2066620</a></li>
<li>Added runtime.getVersion() –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1992418"> Bug 1992418</a>
<ul>
<li>Thanks to Carlos for implementing the new runtime API method.</li>
</ul>
</li>
<li>Introduced runtime.PlatformArch.ARM64 (replacing AARCH64) to match Chromium, landing in Firefox 160 –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2080310"> Bug 2080310</a>
<ul>
<li>Thanks to Anton Bershanskyi for the runtime.PlatformArch rename.</li>
</ul>
</li>
<li>Stopped exposing non-browser windows in windows.onFocusChanged, fixing a “gBrowserInit is undefined” error hit through tabs.query –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1634240"> Bug 1634240</a></li>
<li>Fixed sessions.forgetClosedTab() forgetting the wrong tab when the window has a closed tab group –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2076684"> Bug 2076684</a>
<ul>
<li>Thanks to Dão Gottwald for investigating and fixing this bug hit by the sessions API.</li>
</ul>
</li>
<li>Fixed extension menu items being unreachable by accesskey, including items with Chinese, Japanese or Korean labels –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074182"> Bug 2074182</a> /<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2075142"> Bug 2075142</a>
<ul>
<li>Thanks to Dão Gottwald for driving these menus accesskey fixes.</li>
</ul>
</li>
<li>Added a warning when sendResponse is called by an async runtime.onMessage listener, landing in Firefox 160 –<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1877223"> Bug 1877223</a>
<ul>
<li>Thanks to dchen705 for the runtime.onMessage warning.</li>
</ul>
</li>
</ul>
<h4>DevTools</h4>
<h5>External contributions</h5>
<ul>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=663950">Jakub Stasiak</a> fixed an issue in the Netmonitor where we could miss early WebSocket messages (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1719394">#1719394</a>)</li>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=786063">Amadi</a> localized string in Debugger search panel (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2035151">#2035151</a>)</li>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=786709">Daniel mungai chege</a> added autocomplete in the Rules view for the random() function (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072513">#2072513</a>)</li>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=797242">Ahmed ElGendy</a> added (inline-)grid-lanes badges in the markup view for element with display: (inline-)grid-lanes (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2076779">#2076779</a>)</li>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=775052">Khalid AlHaddad</a> removed an unused argument in the KeyShortcuts constructor (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1979386">#1979386</a>)</li>
</ul>
<h5>Team/Project Update</h5>
<ul>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=149052">Florian Quèze [:florian]</a> made DevTools splitters keyboard accessible (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1860733">#1860733</a>) and fixed numerous other accessibility issues across the toolbox (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2071228">#2071228</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2071230">#2071230</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2071232">#2071232</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2071233">#2071233</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2071236">#2071236</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2075809">#2075809</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2075820">#2075820</a>)</li>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=347081">Leo McArdle [:leo]</a> started modernizing the DevTools Settings panel (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072146">#2072146</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072216">#2072216</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074393">#2074393</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074399">#2074399</a>)</li>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=557153">Nicolas Chevobbe [:nchevobbe]</a> Handle percentage in CSS explainers tooltip (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2041621">#2041621</a>) and show the tooltip for single non-pixels values (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074405">#2074405</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2064400">#2064400</a>)</li>
</ul>
<p><img alt="Tooltip displayed in DevTools for a height property with a value of 33%, equalling to about 165 pixels." class="aligncenter size-full wp-image-2143" height="162" src="https://blog.nightly.mozilla.org/files/2026/10/image4.png" width="282"/></p>
<ul>
<li>
<ul>
<li>(pref: devtools.inspector.css-explainers)</li>
</ul>
</li>
<li><a href="https://bugzilla.mozilla.org/user_profile?user_id=656417">Hubert Boma Manilla (:bomsy)</a> is working on adding support for speculation rules in DevTools. Prefetched requests can now be identified in the Netmonitor (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2077519">#2077519</a>) and he plans to add more information about speculations rules in a dedicated tab in the Application panel (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2077995">#2077995</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078853">#2078853</a>)</li>
</ul>
<p><img alt="A table of four GET requests in Netmonitor, with two identified as prefetched requests." class="aligncenter size-full wp-image-2140" height="360" src="https://blog.nightly.mozilla.org/files/2026/10/image7.png" width="1057"/></p>
<h4>WebDriver</h4>
<ul>
<li>Beatriz Rizental improved the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072753">Marionette harness to accept multiple –tag arguments</a> similar to other in-tree harnesses.</li>
<li>Khalid AlHaddad improved the <a href="https://bugzilla.mozilla.org/attachment.cgi?id=9640463">PollPromise to throw an error by default</a> and not only log a warning when it times out.</li>
<li>Alexandra Borovova added support for <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2069002">the imageSize argument to the browsingContext.captureScreenshot command</a>, which allows clients to specify the maximum size of the resulting screenshot image.</li>
<li>Alexandra Borovova added support for <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2072616">the destinationFolder argument to the browsingContext.startScreencast command</a>, which allows clients to choose the folder where the recorded video file is saved.</li>
<li>Alexandra Borovova implemented <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2064354">the support for the prefers-color-scheme parameter in the emulation.setMediaFeaturesOverride command</a>, which lets clients emulate dark or light mode on a website.</li>
<li>Henrik Skupin improved the handling of <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074275">recommended preferences for automation</a> to use the default branch, preventing them from leaking into subsequent Firefox sessions.</li>
<li>Henrik Skupin fixed a bug where <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2046878">accepted server sockets still had Nagle’s algorithm enabled</a>, causing up to 40ms delays for back-to-back writes on Linux.</li>
<li>Henrik Skupin improved <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1443922">geckodriver’s shutdown handling</a> by <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2075298">waiting for Firefox’s hang monitor to terminate hung processes</a> before force-killing them.</li>
<li>Henrik Skupin added a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078189">temporary workaround to prevent Glean from causing shutdown hangs</a> for short-lived Firefox processes.</li>
<li>Holger Benl added <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2057588">machine-readable CDDL for all Firefox WebDriver BiDi vendor extensions</a> (“moz:” commands, events, parameters, capabilities…).</li>
<li>Privileged context support was added to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2007067">browsingContext.locateNodes</a> and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1966217">input.performActions</a> by Holger Benl, and to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2071800">browsingContext.captureScreenshot</a> by Julian Descottes.</li>
<li>Julian Descottes fixed the network.getData command to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2077785">handle 304 – Not Modified responses with no timeouts</a>.</li>
</ul>
<h4>Fluent</h4>
<ul>
<li>Shout out to flod who’s <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2080569">started</a> to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2080184">chip</a> <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2080165">away</a> <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2079623">again</a> at migrating .properties files to Fluent!
<ul>
<li><a href="https://www.arewefluentyet.com/">For the first time since we started tracking</a>, there are fewer than 4000 .properties strings in the Firefox source code!</li>
</ul>
</li>
</ul>
<h4>Migration Improvements</h4>
<ul>
<li>spohl is <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078922">working on a stack of patches that’ll update the migration workflow for macOS 27</a> to reduce the number of data access permission warnings that users see</li>
</ul>
<h4>New Tab Page</h4>
<ul>
<li>We’re testing a few different layout variations in the wild – one of them is a few different takes on “spaces”:</li>
</ul>
<p><img alt="An experimental layout for the New Tab page showing the &quot;Popular Today&quot; category on the left and the &quot;Widgets&quot; category on the right." class="aligncenter size-full wp-image-2144" height="731" src="https://blog.nightly.mozilla.org/files/2026/10/image3.png" width="1229"/></p>
<ul>
<li>The MCAB search input is currently being deployed to a small population in the wild to see how it works / is received</li>
</ul>
<p><img alt="A glimpse of the MCAB search input with various results for &quot;mozil&quot;" class="aligncenter size-full wp-image-2141" height="565" src="https://blog.nightly.mozilla.org/files/2026/10/image6.png" width="811"/></p>
<ul>
<li>A train-hop is scheduled to be deployed this week which should make widgets available for all users (though for most users, these will be disabled by default – they’ll be available to enable in the customize panel).</li>
</ul>
<p><img alt="A list of widgets in the Customize panel. Each widget can be enabled or disabled." class="aligncenter size-full wp-image-2145" height="295" src="https://blog.nightly.mozilla.org/files/2026/10/image2.png" width="324"/></p>
<ul>
<li>Reem Hamoui<a href="https://bugzil.la/2024073"> removed the Enzyme/Karma test infrastructure from the New Tab Page</a>, which is a CI/dev tooling change with no direct runtime user impact but should reduce test maintenance and flakiness for future user-facing fixes.</li>
<li>Jack Brown<a href="https://bugzil.la/2057021"> switched New Tab message visibility checks to an IntersectionObserver</a> so messages below the fold are no longer marked as activeNotifications, preventing offscreen messages from being targeted and avoiding unnecessary JS evaluation when not visible.</li>
<li>Jack Brown<a href="https://bugzil.la/2057030"> cleared activeNotification targeting when navigating away from about:newtab</a> so message targeting no longer persists after leaving the page, preventing carry‑over interactions and incorrect metrics attribution.</li>
<li>akulyk<a href="https://bugzil.la/2059852"> [a11y] fixed dialog focus containment on the New Tab Page</a> by enforcing a focus trap and proper Tab/Shift-Tab handling, restoring expected keyboard and screenreader workflows for modal dialogs.</li>
<li>Scott<a href="https://bugzil.la/2060322"> fixed pocket.click and topsite.click to trigger context menus correctly</a>, restoring right-click/long-press context menus on Pocket tiles and Top Sites so users can access actions like open-in-new-window and remove.</li>
<li>Maxx Crawford updated per-widget Jest fixtures for Stocks, Privacy and Picture of the Day to omit the widgets.enabled flag in test setups<a href="https://bugzil.la/2063320"> Per-widget Jest fixtures for Stocks, Privacy and Picture of the Day omit widgets.enabled</a>, which aligns test fixtures with runtime enablement behavior and reduces CI flakes and regression risk for those widgets; there is no runtime UI change for end users but widget rendering tests should be more reliable.</li>
<li>Maxx Crawford <a href="https://bugzil.la/2063656">removed the Sports widget from the New Tab Page and widget picker</a>, which directly removes sports headline/cards from users’ NTP experience (users who had Sports selected will no longer see it) and slightly reduces client-side DOM/paint work and widget surface area for future NTP changes. It also removed about 1MB of image / video assets from the <a href="http://omni.ja">omni.ja</a> / newtab XPI.</li>
<li>Maxx Crawford<a href="https://bugzil.la/2066243"> added region/locales dynamic control for the Weather widget</a>, allowing users to change the Weather card’s region/locale on New Tab so forecasts and localized labels update immediately.</li>
<li>Herraj Luhano<a href="https://bugzil.la/2066556"> updated the POTD API contract to return the previous day’s POTD</a>, enabling the New Tab image module to fetch and display yesterday’s Picture of the Day to avoid empty or stale image slots.</li>
<li>Nina Pypchenko [:nina-py]<a href="https://bugzil.la/2068721"> re-ordered New Tab settings in about:preferences</a>, improving discoverability by placing New Tab controls in a more consistent, prominent location for users managing Start Page options.</li>
<li>Dre<a href="https://bugzil.la/2070272"> standardized context menu button UI across all widgets</a>, unifying markup, CSS variables and ARIA to make context-menu hit areas and keyboard focus consistent across widget surfaces.</li>
<li>Dre<a href="https://bugzil.la/2070276"> standardized header typography across all widgets</a>, aligning font sizes, line-heights and tokens so widget headers render consistently on New Tab pages.</li>
<li>Maxx Crawford<a href="https://bugzil.la/2070368"> updated WallpaperFeatureHighlight to allow for alternate strings to be injected</a> so the New Tab wallpaper feature highlight UI can show injected copy variants (for localization or experiments), which directly changes the text users see in the wallpaper picker/highlight flow and should be monitored for clarification/regression in impressions and CTA click rates.</li>
<li>David Durfee<a href="https://bugzil.la/2072355"> landed a meta change to enable score-based selection for sponsored tiles in the New Tab experiment</a>, which replaces the previous selection heuristic with a ranking/scoring pipeline so experiment cohorts may see different sponsored tiles on New Tab (affects which ads/content are shown, sponsored impressions/CTR, and A/B metrics for desktop and mobile New Tab surfaces).</li>
<li>Nina Pypchenko<a href="https://bugzil.la/2074257"> renamed the Stocks widget to “Finance” on the New Tab Page, updating the activity-stream UI/i18n label users see in the widget header</a>.</li>
<li>Brendan Birdsong<a href="https://bugzil.la/2075410"> adjusted the newtab score-based selection to sum day counts from remote-settings config, which can change which cards/tiles are selected and their ordering for users depending on remote config values</a>.</li>
<li>Scott Downe <a href="https://bugzil.la/2076867">removed the discoverystream.optIn-region-weather-config pref</a> from newtab, a config cleanup that does not change runtime New Tab UI or user-visible weather opt-in behavior.</li>
<li>Irene Ni <a href="https://bugzil.la/2076873">normalized the layout_name value in New Tab DSCard impression telemetry</a>, ensuring consistent impression records for analytics and A/B experiments without altering the UI seen by users.</li>
<li>Scott Downe <a href="https://bugzil.la/2076877">removed the telemetry.structuredIngestion.endpoint pref</a> from newtab, removing a pref-based override for structured-ingestion endpoints (affects developer/testing overrides, not regular user behavior).</li>
<li>Irene Ni<a href="https://bugzil.la/2076883"> removed unused ImpressionStats dispatches from New Tab DSCard clicks</a>, eliminating redundant telemetry dispatches on DSCard click paths with no UI change.</li>
<li>Irene Ni<a href="https://bugzil.la/2076893"> normalized Top Sites telemetry keys to their Glean extra names</a>, stabilizing telemetry naming for Top Sites without changing user-visible behavior.</li>
<li>Dre<a href="https://bugzil.la/2077225"> fixed a slight flash when reusing a previously uploaded wallpaper</a> in the New Tab Page, removing a visible flicker for users who set custom uploaded wallpapers.</li>
<li>Maxx Crawford<a href="https://bugzil.la/2077234"> added a debug pref/setting to revert region controls</a>, enabling targeted rollbacks/enabled testing for affected-region UI behaviors when the pref is toggled.</li>
<li>Jared Wein<a href="https://bugzil.la/2077260"> fixed TypeScript errors in newtab/lib blocking inclusion in newtab’s tsconfig.json</a>, resolving a build/tooling blocker (developer-only change; no direct user impact).</li>
<li>Irene Ni<a href="https://bugzil.la/2077268"> made the Spaces arrow-buttons variant background panel occupy the full page height on the New Tab Page, removing a visual gap and ensuring arrow controls stay aligned with page scroll</a>.</li>
<li>Alexandre Hanot<a href="https://bugzil.la/2078317"> fixed Ads client initialization on Firefox 157 and older so the Ads client now initializes instead of throwing errors on legacy builds, restoring ad content on affected users’ New Tab Pages</a>.</li>
<li>Dre<a href="https://bugzil.la/2078497"> prevented the Clocks widget menu button from overlapping clocks on hover by adjusting z-index and hover layout, restoring visibility and correct hit targets on the New Tab Page</a>.</li>
<li>Irene Ni<a href="https://bugzil.la/2078816"> enabled a widget in the first content position of New Tab sections</a>, updating New Tab rendering logic so a prioritized widget slot is populated in the first content position and becomes visible by default to users.</li>
<li>Jared Wein<a href="https://bugzil.la/2078895"> enabled type checking for newtab/lib with exception for failing files</a>, adding incremental static-analysis/CI checks to catch regressions in newtab code without changing UI behavior today.</li>
<li>Maxx Crawford<a href="https://bugzil.la/2078974"> set default enabled value to false for all existing widgets</a>, changing widget metadata/prefs so existing widgets are opt-in and will no longer render for users unless explicitly enabled.</li>
<li>David Durfee<a href="https://bugzil.la/2079014"> added differential privacy noise to scores in newtab score-based selection</a>, anonymizing per-user signals which will alter ranking/discovery behavior on the New Tab page while underscoring privacy guarantees.</li>
<li>Brendan Birdsong<a href="https://bugzil.la/2079018"> moved newtab score storage to PersistentCache</a>, persisting scores across sessions and reducing recompute/lookup latency so personalized selections are more stable and faster to load.</li>
<li>Jared Wein<a href="https://bugzil.la/2079376"> fixed more newtab/lib TypeScript errors so 11 more files can be type-checked</a>, enabling type-checking across newtab/lib (11 files) and lowering regression risk for New Tab Page behavior.</li>
<li>Dre<a href="https://bugzil.la/2079542"> used useWidgetTelemetry in the Weather widget</a> to standardize telemetry for the Weather widget (New Tab Page), improving diagnostic signals that help us find and fix user-facing widget issues faster.</li>
<li>Maxx Crawford<a href="https://bugzil.la/2079939"> turned off all New Tab widgets in automation with one pref</a>, allowing automation to run with widgets disabled to reduce flakiness in tests that interact with New Tab UI.</li>
<li>Dre<a href="https://bugzil.la/2079953"> updated the Focus Timer widget to use useWidgetTelemetry</a>, so Focus Timer telemetry now respects widget-level prefs and will avoid sending unguarded pings—privacy impact only, no UI change.</li>
<li>Nina Pypchenko [:nina-py]<a href="https://bugzil.la/2080654"> fixed transparent New Tab dialogs when the train-hop is applied to Firefox 158 and 159</a>, restoring dialog opacity/CSS so newtab overlays are readable again when train-hop is enabled on those releases.</li>
</ul>
<h4>Picture-in-Picture</h4>
<ul>
<li>kpatenio fixed a bug on Windows and Linux where <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2055092">clicking a previous control overrides the Space play/pause shortcut</a>.</li>
<li>kpatenio landed a few patches to make keyboard navigation better when the playback speed control is enabled (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2055070">Bug 2055070</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074319">Bug 2074319</a>).</li>
<li>As of Nightly 159, the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2055065">PiP player UI has been updated for Nova</a>. Aside from being visually consistent with Nova, scrubbers and settings panels now have better contrast on High Contrast Mode.</li>
</ul>
<h4>Search and Urlbar</h4>
<h5>Urlbar</h5>
<ul>
<li>Dao landed a patch to show the “Search tabs” keyboard shortcut in the search mode switcher menu: <a href="http://bugzilla.mozilla.org/2078113">2078113</a></li>
</ul>
<p><img alt="The &quot;Search tabs&quot; shortcut displayed in the search mode switcher menu among others, like Bookmarks and History." class="aligncenter size-full wp-image-2139" height="495" src="https://blog.nightly.mozilla.org/files/2026/10/image8.png" width="375"/></p>
<ul>
<li>Logan Rosen changed the Accel+Shift+A shortcut from the Add-ons Manager to Search Tabs: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1666654">1666654</a>. Dao followed up by notifying people who used the old shortcut that it moved and revised the wording of that message: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2077823">2077823</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2079208">2079208</a></li>
<li>James added an option to skip the menu when tabbing through the address bar, in both the address bar and the preferences page: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2064708">2064708</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2068609">2068609</a></li>
<li>Dao fixed a bug so that entering an address in search mode now navigates to that URL: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2036347">2036347</a></li>
<li>Dao fixed two urlbar.bounce telemetry bugs: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2069403">2069403</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2076827">2076827</a></li>
<li>Caleb fixed a bug where the address bar results dropdown covered the calculator tail150 game: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2077358">2077358</a></li>
<li>Daisuke fixed a bug where search terms in the address bar moved when pressing Enter or when edited: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074921">2074921</a></li>
<li>Dao fixed the search engine button being cut off in the Search dropdown with Nova enabled: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074871">2074871</a></li>
<li>Daisuke fixed the search switcher’s active button color being too strong with low text contrast in Nova: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2068504">2068504</a></li>
<li>Emilio fixed the Quick Actions background button missing in the Light theme on Ubuntu in Nova: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2076191">2076191</a></li>
<li>Moritz continued with MCAB (multi-context address bar) follow-on work: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078231">2078231</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078658">2078658</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078672">2078672</a>.</li>
<li>Moritz also enabled TypeScript type checking for UrlbarView and UrlbarBaseInput: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2077545">2077545</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2077543">2077543</a></li>
<li>Dao significantly improved the address bar docs, including how to add a new search surface end to end, how results and providers work across the process boundary, and how to debug and log the address bar:</li>
</ul>
<h5> Search</h5>
<ul>
<li>Caleb fixed a bug where the address bar swallowed the first character typed into it if you typed too quickly: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1953361">1953361</a></li>
<li>Mark continued working on the new search config, search-config-v3: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2063279">2063279</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2063264">2063264</a></li>
</ul>
<h5>Places</h5>
<ul>
<li>Dao fixed a bug where the bookmark creation/editing panel had no keyboard shortcut mnemonic for the Save button: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1877510">1877510</a></li>
</ul>
<h4>Storybook/Reusable Components/Acorn Design System</h4>
<ul>
<li>Dialogs in about: pages now match Nova designs more closely</li>
<li>Moz- widgets should now have types found when querying the element with document.querySelector(“moz-button”) and TS is configured</li>
<li>A11y fixes for profiles dialog, page nav keyboard handling (no longer steals Ctrl+arrows)</li>
</ul>
<ul>
<li/>
</ul></div>
    </content>
    <updated>2026-10-22T16:56:55Z</updated>
    <published>2026-10-22T16:56:55Z</published>
    <category term="News"/>
    <author>
      <name>Katherine Patenio</name>
    </author>
    <source>
      <id>https://blog.nightly.mozilla.org</id>
      <logo>https://blog.nightly.mozilla.org/files/2024/04/cropped-Fx-Browser-Nightly-icon-fullColor-512-32x32.png</logo>
      <link href="https://blog.nightly.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.nightly.mozilla.org" rel="alternate" type="text/html"/>
      <subtitle>Let's improve quality, build after build!</subtitle>
      <title>Firefox Nightly News</title>
      <updated>2026-10-22T16:56:55Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/l10n/?p=1934</id>
    <link href="https://blog.mozilla.org/l10n/2026/10/22/l10n-report-october-edition-2026/" rel="alternate" type="text/html"/>
    <title>L10n Report: October Edition 2026</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">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 … <a class="go" href="https://blog.mozilla.org/l10n/2026/10/22/l10n-report-october-edition-2026/">Read more</a></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><i>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. </i></p>
<h3>Welcome!</h3>
<p>New localizers</p>
<ul>
<li>Welcome <a href="https://pontoon.mozilla.org/contributors/samin-yasar/">Samin Yasar</a>, a new contributor who took the initiative to restart localization and is bringing a renewed energy to the Bengali community.</li>
</ul>
<p>Are you a locale leader and want us to include new members in our upcoming reports? <a href="mailto:l10n-drivers@mozilla.org">Contact us!</a></p>
<h3>New community/locales added</h3>
<p>Persian (fa) is now enabled on addons.mozilla.org (AMO). Congratulations and thank you to the Persian localization community for reaching 100% on both AMO projects in Pontoon.</p>
<h3>What’s new or coming up in Firefox desktop</h3>
<h4>Felt privacy and protection</h4>
<p>In upcoming versions of Firefox, there will be a number of updates focused making the privacy protection features of Firefox felt by the user, in addition to communicating those features in an easy to understand way. Translation has been ongoing and some of these will be released from Firefox 159.</p>
<p><b>Private Window redesign</b></p>
<p>A redesigned Private Window experience when opening a new Private Window will be rolled out in an experiment to users starting in Firefox 159, but can be viewed by opening about:config and setting the browser.privateWindowRedesign.enabled flag to true, then opening a new Private Window.</p>
<p><a href="https://blog.mozilla.org/l10n/files/2026/10/Private-Window.png"><img alt="" class="alignnone size-large wp-image-1936" height="564" src="https://blog.mozilla.org/l10n/files/2026/10/Private-Window-600x564.png" width="600"/></a></p>
<p><b>Fire button in Classic Mode</b></p>
<p>A button that allows users to start fresh in a browsing session, they can clear browsing data in a single click. Strings for this will mostly involve updated wording for existing strings around what data to clear. This is one of many features mentioned in the <a href="https://www.firefox.com/whatsnext/?tags=desktop">Firefox roadmap</a>.</p>
<p><b>Privacy Panel</b></p>
<p>The privacy panel that shows your protection status for a website (accessible by clicking the shield icon in your address bar) will be getting a complete redesign to more prominently display the number of trackers blocked, important security warnings, and critical site issues. This is still in progress but expect to see strings soon.</p>
<h4>Mini Window</h4>
<p>An early version of this feature is coming up in Firefox 160 and strings are landing now. The Mini Window gives you the ability to detach a tab or custom section into an always-on-top, scaled-down frame. It expands on the familiar Picture-in-Picture functionality for general web content, making it effortless to keep documentation, messaging apps, or references visible as you work. You can find additional details and a demo of Mini Window on <a href="https://connect.mozilla.org/t5/discussions/mini-window-beta-is-going-live-in-firefox-160-and-we-want-your/m-p/144137">Mozilla Connect</a>.</p>
<h3>What’s new or coming up in mobile</h3>
<p>With our recent switch to releases in 2-week cadence, mobile will see a slew of small but mighty features pop-up in short succession. Some of the recently launched or soon-to-be revealed features include:</p>
<p><b>Firefox for Android</b></p>
<ul>
<li>Read aloud [AI feature]: Catch up on your reading list on the go by having Firefox read your articles out loud. In reader mode, you will be able to activate the listening feature, select your preferred reading voice and adjust the playback speed, as well as scrub backwards and forwards, so you can skip to the juicy bits quicker.</li>
<li>Data consent for extensions: We always want to make sure users know exactly what privacy and data collection settings are required when updating their installed extensions. We are making updates to give you even more visibility and control when reviewing which privacy settings are being modified in an update. That way you can decide whether or not to grant permissions and proceed with confidence.</li>
</ul>
<p><b>Firefox for iOS</b></p>
<ul>
<li>Quick Answers [AI feature]: use your voice to ask a question straight from your Firefox homepage and get a quick answer backed by sources in just a few seconds! Your voice, your questions and the generated answer stay totally private.</li>
<li>Transfer Your Data between Browsers: move to Firefox in a snap by importing your bookmarks, history and reading lists from another browser, all in a few simple clicks! You can also export your Firefox data to other browsers.</li>
<li>Built-in VPN: After making its grand debut in desktop and Android, built-in VPN is coming to Firefox for iOS! Navigate with extra protection on known networks and public wifi. Select from a large selection of locations, or let Firefox choose the fastest one for you. It’s always free and signing up with a Mozilla Account gets you extra bandwidth.</li>
</ul>
<h3>What’s new or coming up in web projects</h3>
<p>Firefox Enterprise is here! It launched on October 13 alongside Firefox 158: Firefox with enterprise controls and a management console that organizations run on their own infrastructure. Read the<a href="https://blog.mozilla.org/firefox/introducing-firefox-enterprise/"> announcement</a> and explore the <a href="https://www.firefox.com/enterprise/">website</a>.</p>
<p>The launch starts in France, Germany, Austria and Switzerland, so the website is live in English, French and German. Our translation agency handled these pages, so you won’t find them in Pontoon. Thank you to everyone who has helped with firefox.com so far. If you’re curious about how localization works for firefox.com and Firefox Enterprise, or have thoughts on it, you’re always welcome to get in touch.</p>
<p>Strings for the main firefox.com website continue to land in the firefox.com project in Pontoon, for the locales that have it enabled.</p>
<p><a href="https://blog.mozilla.org/l10n/files/2026/10/Firefox-Enterprise.png"><img alt="" class="alignnone size-large wp-image-1937" height="449" src="https://blog.mozilla.org/l10n/files/2026/10/Firefox-Enterprise-600x449.png" width="600"/></a></p>
<h3>What’s new or coming up in SUMO</h3>
<p>Semantic search is now live! It was officially launched with<a href="https://github.com/mozilla/kitsune/releases/tag/1.8.0"> Kitsune 1.8.0</a> on October 6, 2026. This initial rollout is limited to Knowledge Base articles, with broader search improvements still to come. A big thank-you to everyone who participated in the<a href="https://support.mozilla.org/forums/contributors/717753?last=91150"> testing phase</a> and helped us improve the experience!</p>
<p>Dark mode is coming to SUMO! You can get an early look by watching the demo in the previous <a href="https://support.mozilla.org/en-US/forums/contributors/717787?last=91193">Monthly Community Call</a> or you can also try it yourself on our<a href="https://support.allizom.org/en-US/"> staging site</a>.</p>
<h3>What’s new or coming up in Pontoon</h3>
<p><b>Monthly health reports.</b> Following the Community Health Score introduced in the <a href="https://blog.mozilla.org/l10n/2026/08/13/l10n-report-august-edition-2026/">August report</a>, teams can now <a href="https://pontoon.mozilla.org/settings/">opt into a monthly health report</a>, delivered as both an email and an in-app notification, with a new toggle in contributor settings. The feature was developed by our intern Jamie (<a href="https://github.com/functionzz">functionzz</a>).</p>
<p><b>Editor and Machinery.</b> The editor can autofill from composed Machinery matches, the 100% match indicator moved into the editor menu, and leaving an autofilled 100% TM match no longer triggers an unsaved-changes warning.</p>
<p><b>New contributors.</b> We’re happy to welcome another group of contributors who made their first patches to Pontoon in the past few months: <a href="https://github.com/mozilla/pontoon/commits?author=baha-bouali">baha-bouali</a> (6 patches), <a href="https://github.com/mozilla/pontoon/commits?author=scottcampbelldata">scottcampbelldata</a> (4), <a href="https://github.com/mozilla/pontoon/commits?author=tahakotil">tahakotil</a> (2), <a href="https://github.com/mozilla/pontoon/commits?author=nyomanjyotisa">nyomanjyotisa</a> (2), <a href="https://github.com/mozilla/pontoon/commits?author=kwy404">kwy404</a> (2), <a href="https://github.com/mozilla/pontoon/commits?author=annki">annki</a>, <a href="https://github.com/mozilla/pontoon/commits?author=Goudarz">Goudarz</a>, <a href="https://github.com/mozilla/pontoon/commits?author=Hanabi9248">Hanabi9248</a>, <a href="https://github.com/mozilla/pontoon/commits?author=HarshRajSinghania">HarshRajSinghania</a>, and <a href="https://github.com/mozilla/pontoon/commits?author=MaxFreedomPollard">MaxFreedomPollard</a>. Their work spans terminology, search and dropdown behavior, the API, plural handling, theming, insights, right-to-left support, and documentation — thank you all!</p>
<h3>Friends of the Lion</h3>
<div class="wp-caption aligncenter" id="attachment_1131" style="width: 262px;"><img alt="" class="wp-image-1131 size-medium" height="232" src="https://blog.mozilla.org/l10n/files/2017/07/2-Lions-01-252x232.png" width="252"/><p class="wp-caption-text" id="caption-attachment-1131">Image by Elio Qoshi</p></div>
<p>Know someone in your l10n community who’s been doing a great job and should appear here? <a href="mailto:l10n-drivers@mozilla.org">Contact us</a> and we’ll make sure they get a shout-out!</p>
<h3>Useful Links</h3>
<ul>
<li><a href="https://chat.mozilla.org/#/room/#l10n-community:mozilla.org">#l10n-community channel on Element (chat.mozilla.org)</a></li>
<li><a href="https://discourse.mozilla.org/c/l10n/547">Localization category on Discourse</a></li>
<li><a href="https://fosstodon.org/@mozilla_l10n">Mastodon</a></li>
<li><a href="https://blog.mozilla.org/l10n/">L10n blog</a></li>
</ul>
<h3>Questions? Want to get involved?</h3>
<p>If you want to get involved, or have any question about l10n, reach out to:</p>
<ul>
<li><a href="https://pontoon.mozilla.org/contributors/CMLZ_n1lNNSfQScLGE2yBmlS55w/">Bryan</a> – Project Manager (Firefox, Mozilla Accounts)</li>
<li><a href="https://pontoon.mozilla.org/contributors/camiparker/">Camila</a> – Project Manager (Firefox for Android, Firefox for iOS)</li>
<li><a href="https://pontoon.mozilla.org/contributors/edie/">Eda</a> – Project Manager (Web projects)</li>
<li><a href="https://pontoon.mozilla.org/contributors/mZuzEFP7EcmgBBTbvtgJP2LFFTY/">Francesco (flod)</a> – Project Manager, L10n Team Manager</li>
<li><a href="https://pontoon.mozilla.org/contributors/m6r3HOfoijMdyeJNKKFHchjjRbw/">Francis</a> – Project Manager (Common Voice, Mozilla Foundation)</li>
<li><a href="https://pontoon.mozilla.org/contributors/lY_FTvtnYcVoDP7JYZjMsm6tRno/">Théo</a> – Project Manager (Mozilla Foundation)</li>
<li><a href="https://pontoon.mozilla.org/contributors/9rSAS6h8LlBD9DQQtHgdCwvVen0/">Kiki</a> – Project Manager (SUMO)</li>
<li><a href="https://pontoon.mozilla.org/contributors/pmz0uSCe_Mk9Td1cksHLI1y471k/">Eemeli</a> – Developer (Pontoon, Infrastructure)</li>
<li><a href="https://pontoon.mozilla.org/contributors/ewerybody/">Eric</a> – Developer (Pontoon, Infrastructure)</li>
<li><a href="https://pontoon.mozilla.org/contributors/dvgiVCmoeidF2xcqSnBHtpzLTFU/">Matjaž (mathjazz)</a> – Developer (Pontoon)</li>
</ul>
<p>Did you enjoy reading this report? <a href="mailto:l10n-drivers@mozilla.org">Let us know</a> how we can improve it.</p></div>
    </content>
    <updated>2026-10-22T16:41:27Z</updated>
    <published>2026-10-22T16:41:27Z</published>
    <category term="L10n Reports"/>
    <category term="Planet"/>
    <author>
      <name>ebinen</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/l10n</id>
      <link href="https://blog.mozilla.org/l10n/category/planet/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/l10n" rel="alternate" type="text/html"/>
      <subtitle>Users first, no matter where they are</subtitle>
      <title>Planet – Mozilla L10N</title>
      <updated>2026-11-12T11:07:05Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149906</id>
    <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261021-1/149906" rel="alternate" type="text/html"/>
    <title>Happy BMO Push Day! (20261021.1)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://github.com/mozilla-bteam/bmo/tree/release-20261021.1" rel="noopener nofollow ugc">Github Link</a></p>
<p>The following changes have been pushed to <a href="https://bugzilla.mozilla.org">bugzilla.mozilla.org</a>:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2064523">Bug 2064523</a> - [meta] tracking bug for BMO dependency upgrades</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2081849">Bug 2081849</a> - Migrate Bug REST resource to native Mojo API: field metadata (fields, legal_values, flag_types)</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2082654">Bug 2082654</a> - 2_test_flags2.t picks a component before the bug page has loaded the new product’s components</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2083156">Bug 2083156</a> - Add an alert for excessive lag in the <code>phab-bot</code> feed processing queue</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2083532">Bug 2083532</a> - Webhook bug.modify payload has empty bug.flags when flags are set at bug creation</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2020752">Bug 2020752</a> - [PHABBUGZ] Improve testing of phabricator and bmo integration</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2079840">Bug 2079840</a> - allow <span class="mention">@username</span> in the textarea like github</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2081859">Bug 2081859</a> - Migrate Bug REST resource to native Mojo API: comments (comments, add_comment, render_comment, reactions, tags)</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078770">Bug 2078770</a> - Migrate User REST resource to native Mojo API: MFA (enroll, verify_totp_code)</li>
</ul>
<p>Discuss these changes in the <a href="https://matrix.to/#/#bmo:mozilla.org" rel="noopener nofollow ugc">BMO Matrix Room</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261021-1/149906">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-21T22:23:47Z</updated>
    <published>2026-10-21T22:23:47Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>dkl1</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261021-1/149906.rss" title="Happy BMO Push Day! (20261021.1)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88541</id>
    <link href="https://blog.mozilla.org/en/firefox/5-reasons-to-choose-firefox/" rel="alternate" type="text/html"/>
    <title>Still here, still yours: 5 reasons to choose Firefox</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The internet used to feel like a community, not a commodity. Browsers were tools for exploration, and you could wander the web without feeling tracked everywhere. Today, as the web becomes increasingly surveilled and commercialized, Firefox preserves the magic, freedom, and fun of the early internet. Still open source, still independent, still privacy-focused. No billionaire […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/5-reasons-to-choose-firefox/">Still here, still yours: 5 reasons to choose Firefox</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The internet used to feel like a community, not a commodity. Browsers were tools for exploration, and you could wander the web without feeling tracked everywhere.<br/><br/>Today, as the web becomes increasingly surveilled and commercialized, Firefox preserves the magic, freedom, and fun of the early internet. Still open source, still independent, still privacy-focused. No billionaire owner, no hidden agenda.<br/><br/>So, whether you’re new here, back after a break, or just curious, here are five reasons to choose the browser that puts you first.</p>



<h3><strong>Backed by a non-profit, not billionaires</strong></h3>



<p>Firefox is backed by the <a href="https://www.mozilla.org/">Mozilla</a> Foundation, a non-profit committed to an open internet. Unlike other big tech companies, we’re built with <a href="https://www.mozilla.org/privacy/faq/">privacy as the default</a>. Our open source code is visible, reviewable, and continuously stress-tested by a global community, truly putting power in the hands of the people it’s built for.</p>



<h3><strong>Private and fast by design</strong></h3>



<figure class="wp-block-image size-large"><img alt="" class="wp-image-88553" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Control-02-Clone-1024x576.png" width="1024"/></figure>



<p>While other browsers allow third-party trackers to profile you, Firefox’s <a href="https://support.mozilla.org/kb/enhanced-tracking-protection-firefox-desktop">Enhanced Tracking Protection (ETP)</a> helps stop cross-site tracking before it starts, letting your browser work faster. Plus, when you <a href="https://www.firefox.com/features/sync/">sync</a> information like history and bookmarks across devices, it’s encrypted locally, meaning only you can access it.</p>



<p>Learn about some of our other privacy-focused features like <a href="https://www.firefox.com/features/password-manager/?_gl=1*1fox7s3*_ga*Nzk5Mzk1OTA0LjE3ODQ1NTM5OTA.*_ga_X4N05QV93S*czE3OTE0OTQ2NjEkbzI1MSRnMSR0MTc5MTQ5NDkyNiRqNjAkbDAkaDA.">password manager</a>, <a href="https://www.firefox.com/landing/vpn/">built-in VPN</a>, and <a href="https://relay.firefox.com/">Relay</a> in our guide to <a href="https://blog.mozilla.org/firefox/free-firefox-cybersecurity-features/">strengthening your online security for free with Firefox</a>.</p>



<h3><strong>AI on your terms</strong></h3>



<figure class="wp-block-image size-full"><img alt="" class="wp-image-84444" height="2160" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/02/Blocking-AI-features-manually-enabling-a-feature-in-Firefox-AI-controls2.gif" width="3840"/></figure>



<p>We believe the only person who should decide <a href="https://blog.mozilla.org/en/firefox/firefox-ai-on-your-terms/">how you interact with AI features</a> in your browser is you. Firefox offers a clear, easily accessible <a href="https://blog.mozilla.org/en/firefox/how-to-use-ai-controls/">AI controls section</a> where you can turn off AI features entirely — or decide which ones stay on depending on your workflow and preferences.</p>



<p>For those wanting a little more help getting things done, <a href="https://support.mozilla.org/kb/smart-window">Smart Window</a> is Firefox’s most integrated AI experience. With your permission, its built-in, AI-powered assistant can work directly with your open tabs and browsing history to connect the dots. This means it can compare information, summarize pages, and help plan projects without requiring you to provide context from your past and current browsing activity every time you start a new prompt.</p>



<p><a href="https://blog.mozilla.org/firefox/firefox-smart-window/">Newer feature additions</a> to Smart Window include the ability to group related tabs together and visual history previews that help you find a page you visited earlier when you can’t remember the exact URL or phrase searched. Also, our partnership with <a href="https://blog.mozilla.org/firefox/firefox-exa-partnership/">Exa</a> enables Smart Window to find current web information to include in responses while also displaying the sources behind these answers, so you can verify what you’re seeing without interrupting your workflow.</p>



<p>Smart Window remains in beta as we continue to learn and improve from our community’s feedback. Try it yourself <a href="https://www.firefox.com/smart-window">here</a>.</p>



<h3><strong>Not just Chrome in disguise</strong></h3>



<p>Firefox is not built on Chromium, the open source browser project that supports Google Chrome and many other browsers. As a matter of fact, we are one of the last major browsers that isn’t.</p>



<p>Instead, Firefox runs on Mozilla’s independent <a href="https://blog.mozilla.org/netpolicy/2026/03/23/competition-innovation-and-the-future-of-the-web/">Gecko</a> browser engine, which was developed specifically to uphold our strong privacy standards and give people more control over their data and browsing experience.</p>



<p>This independence also impacts how Firefox handles <a href="https://addons.mozilla.org/firefox/">browser add-ons</a>, particularly ad blockers. Unlike Chromium-based browsers that now limit how powerful ad-blocking tools can be, Firefox still allows ad blockers like uBlock Origin to work at full strength. This means people who use Firefox can enjoy stronger, more reliable ad and tracker blocking without compromise, something increasingly difficult on Chromium-based browsers due to imposed limitations.</p>



<h3><strong>Plus, we have a really cute Firefox</strong></h3>



<figure class="wp-block-image size-large"><img alt="" class="wp-image-88565" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Frame-2147229953-Clone-Clone-Clone-Clone-French-1024x576.png" width="1024"/></figure>



<p>Firefox is constantly building features and solutions to help you navigate the web on your own terms, and we wanted to make this support visible. Enter <a href="https://blog.mozilla.org/firefox/meet-kit/">Kit</a>, Firefox’s companion to the internet.  </p>



<p>Kit isn’t an AI assistant or chatbot, just a friendly face that you might see during moments that are meant to feel friendly and supportive, like when you’re just getting set up, exploring a new feature, or celebrating a win such as successfully adjusting a setting.</p>



<h3><strong>Rooted in values, built for you</strong></h3>



<p>While the internet is ever-changing, Firefox remains rooted in the values that defined its beginning. Our browser was created on the principles of privacy, independence, and choice,and we continue to uphold them as we innovate and evolve.</p>



<p>In a web landscape dominated by profit, surveillance, and sameness, our browser preserves the open and human spirit of the early internet. New, returning, or loyal for years, there’s always a place for you here.</p>



<p><a href="https://www.firefox.com/download/">Download Firefox</a> and make the web yours again.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/5-reasons-to-choose-firefox/">Still here, still yours: 5 reasons to choose Firefox</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-21T16:00:00Z</updated>
    <published>2026-10-21T16:00:00Z</published>
    <category term="Firefox"/>
    <category term="Firefox Features"/>
    <category term="export"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149888</id>
    <link href="https://discourse.mozilla.org/t/perfcompare-deployed-oct-21st-2026/149888" rel="alternate" type="text/html"/>
    <title>PerfCompare deployed (Oct 21st, 2026)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The latest version of<a href="https://perf.compare" rel="noopener nofollow ugc"> PerfCompare</a> is now live!</p>
<p>Check out the change-log below to see the updates:</p>
<p>[kala-moz]:</p>
<ul>
<li>
<h4><a class="anchor" href="https://discourse.mozilla.org#p-297326-bug-2058236-show-a-notice-when-column-filters-hide-result-rowshttpsgithubcomkala-mozperfcomparecommitd20a5d02716e87345f00975219eae0a79b54d249-1" name="p-297326-bug-2058236-show-a-notice-when-column-filters-hide-result-rowshttpsgithubcomkala-mozperfcomparecommitd20a5d02716e87345f00975219eae0a79b54d249-1"/><strong><a href="https://github.com/kala-moz/perfcompare/commit/d20a5d02716e87345f00975219eae0a79b54d249" rel="noopener nofollow ugc">Bug 2058236: Show a notice when column filters hide result rows</a></strong></h4>
</li>
<li>
<h4><a class="anchor" href="https://discourse.mozilla.org#p-297326-bug-2075044-significance-filter-and-sort-selections-dont-persisthttpsgithubcomkala-mozperfcomparecommit9076f0ca07e329e0d163d335c48f164042650c67-2" name="p-297326-bug-2075044-significance-filter-and-sort-selections-dont-persisthttpsgithubcomkala-mozperfcomparecommit9076f0ca07e329e0d163d335c48f164042650c67-2"/><strong><a href="https://github.com/kala-moz/perfcompare/commit/9076f0ca07e329e0d163d335c48f164042650c67" rel="noopener nofollow ugc">Bug: 2075044 Significance filter and sort selections don’t persist</a></strong></h4>
</li>
</ul>
<p>[gopar]:</p>
<ul>
<li>
<h4><a class="anchor" href="https://discourse.mozilla.org#p-297326-bug-2039589-add-caching-to-ttestmwu-viewshttpsgithubcomkala-mozperfcomparecommit1a2265702a470e12ac67b2a6788c8a043a833038-3" name="p-297326-bug-2039589-add-caching-to-ttestmwu-viewshttpsgithubcomkala-mozperfcomparecommit1a2265702a470e12ac67b2a6788c8a043a833038-3"/><strong><a href="https://github.com/kala-moz/perfcompare/commit/1a2265702a470e12ac67b2a6788c8a043a833038" rel="noopener nofollow ugc">Bug-2039589 - Add caching to ttest/mwu views</a></strong></h4>
</li>
<li>
<h4><a class="anchor" href="https://discourse.mozilla.org#p-297326-bug-1846013-add-ability-to-display-multiple-framework-resultshttpsgithubcomkala-mozperfcomparecommit66d6d6e3913ec31027baf3ac3a23d8db5c196d57-4" name="p-297326-bug-1846013-add-ability-to-display-multiple-framework-resultshttpsgithubcomkala-mozperfcomparecommit66d6d6e3913ec31027baf3ac3a23d8db5c196d57-4"/><strong><a href="https://github.com/kala-moz/perfcompare/commit/66d6d6e3913ec31027baf3ac3a23d8db5c196d57" rel="noopener nofollow ugc">Bug 1846013 Add ability to display multiple framework results</a></strong></h4>
</li>
<li>
<h4><a class="anchor" href="https://discourse.mozilla.org#p-297326-bug-1941337-add-new-formatter-for-delta-valueshttpsgithubcomkala-mozperfcomparecommit08c565736d1e7f0dc28da3774ed1be95ec76adf9-5" name="p-297326-bug-1941337-add-new-formatter-for-delta-valueshttpsgithubcomkala-mozperfcomparecommit08c565736d1e7f0dc28da3774ed1be95ec76adf9-5"/><strong>B<a href="https://github.com/kala-moz/perfcompare/commit/08c565736d1e7f0dc28da3774ed1be95ec76adf9" rel="noopener nofollow ugc">ug-1941337 - Add new formatter for delta values</a></strong></h4>
</li>
</ul>
<p>[moijes]</p>
<ul>
<li>
<h4><a class="anchor" href="https://discourse.mozilla.org#p-297326-bug-1982588-align-breadcrumbs-and-replicates-button-in-subtests-viewhttpsgithubcomkala-mozperfcomparecommiteaf5faf1e448fe2a26e1adf04bb81e930fffd170-6" name="p-297326-bug-1982588-align-breadcrumbs-and-replicates-button-in-subtests-viewhttpsgithubcomkala-mozperfcomparecommiteaf5faf1e448fe2a26e1adf04bb81e930fffd170-6"/><strong><a href="https://github.com/kala-moz/perfcompare/commit/eaf5faf1e448fe2a26e1adf04bb81e930fffd170" rel="noopener nofollow ugc">Bug-1982588: Align breadcrumbs and replicates button in Subtests View</a></strong></h4>
</li>
</ul>
<p>Thank you for the contributions!</p>
<p>Bugs or feature requests can be<a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&amp;component=PerfCompare&amp;status_whiteboard=%5Bpcf%5D"> filed on Bugzilla</a>. The team can also be found on<a href="https://matrix.to/#/#perfcompare:mozilla.org" rel="noopener nofollow ugc"> the #perfcompare channel on </a>Matrix. Come and chat!</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/perfcompare-deployed-oct-21st-2026/149888">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-21T15:20:28Z</updated>
    <published>2026-10-21T15:20:28Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>csevere</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/perfcompare-deployed-oct-21st-2026/149888.rss" title="PerfCompare deployed (Oct 21st, 2026)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry>
    <id>tag:this-week-in-rust.org,2026-10-21:/blog/2026/10/21/this-week-in-rust-674/</id>
    <link href="https://this-week-in-rust.org/blog/2026/10/21/this-week-in-rust-674/" rel="alternate" type="text/html"/>
    <title>This Week in Rust 674</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello and welcome to another issue of <em>This Week in Rust</em>!
<a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
This is a weekly summary of its progress and community.
Want something mentioned? Tag us at
<a href="https://bsky.app/profile/thisweekinrust.bsky.social">@thisweekinrust.bsky.social</a> on Bluesky or
<a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social …</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello and welcome to another issue of <em>This Week in Rust</em>!
<a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
This is a weekly summary of its progress and community.
Want something mentioned? Tag us at
<a href="https://bsky.app/profile/thisweekinrust.bsky.social">@thisweekinrust.bsky.social</a> on Bluesky or
<a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social, or
<a href="https://github.com/rust-lang/this-week-in-rust">send us a pull request</a>.
Want to get involved? <a href="https://github.com/rust-lang/rust/blob/main/CONTRIBUTING.md">We love contributions</a>.</p>
<p><em>This Week in Rust</em> is openly developed <a href="https://github.com/rust-lang/this-week-in-rust">on GitHub</a> and archives can be viewed at <a href="https://this-week-in-rust.org/">this-week-in-rust.org</a>.
If you find any errors in this week's issue, <a href="https://github.com/rust-lang/this-week-in-rust/pulls">please submit a PR</a>.</p>
<p>Want TWIR in your inbox? <a href="https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&amp;id=0ed8b72485">Subscribe here</a>.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#updates-from-rust-community">Updates from Rust Community</a></h4>


<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#official">Official</a></h5>
<ul>
<li><a href="https://blog.rust-lang.org/2026/10/15/Rust-1.99.1/">Announcing Rust 1.99.1</a></li>
<li><a href="https://blog.rust-lang.org/inside-rust/2026/10/20/gpu-target-notification-group/">Announcing the GPU notification group and Linker Working Area</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#newsletters">Newsletters</a></h5>
<ul>
<li><a href="https://rust-trends.com/newsletter/if-it-compiles-the-agent-got-it-right/">Rust Trends Issue 85 - If It Compiles, the Agent Got It Right</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#projecttooling-updates">Project/Tooling Updates</a></h5>
<ul>
<li><a href="https://blog.cloudflare.com/typescript-rust-port/">Introducing tsrs: a Port of TypeScript to Rust</a></li>
</ul>


<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#observationsthoughts">Observations/Thoughts</a></h5>
<ul>
<li><a href="https://kerkour.com/rust-at-cloudflare">Cloudflare is rewriting everything in Rust</a></li>
<li><a href="https://smallcultfollowing.com/babysteps/blog/2026/10/14/agentic-dev-and-rust/">What agents mean for Rust (and vice versa)</a></li>
<li><a href="https://orlp.net/blog/black-box-hashdos/">Black-Box HashDoS: Attacking Hash Tables Without Knowing the Hash Function</a></li>
<li><a href="https://yoyo-code.com/2026-is-exciting-year-for-rust-compiler-and-me/">2026 is an exciting year for the Rust compiler (and me)</a></li>
<li><a href="https://tensorust.com/articles/crates-io-download-count/">What the crates.io download count really measures: 90 days of daily data from 69 crates</a></li>
<li><a href="https://lwn.net/SubscriberLink/1099224/54c55e87a0828522/">Safe self-referential data structures in kernel Rust</a></li>
<li><a href="https://lwn.net/SubscriberLink/1099596/7bfb3ee846a5f102/">Cross-crate forward declarations in Rust</a></li>
<li><a href="https://heikoseeberger.de/2026-10-18-why-sync-handlers/">Why tellus message handlers are synchronous</a></li>
<li><a href="https://www.collabora.com/news-and-blog/blog/2026/10/21/upstreaming-tyr-rust-drm-and-the-linux-kernel/">Upstreaming Tyr: Rust, DRM, and the Linux Kernel</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-walkthroughs">Rust Walkthroughs</a></h5>
<ul>
<li><a href="https://altunenes.github.io/posts/reuse/">I forced a speech model onto the GPU for months. The CPU was faster.</a></li>
<li><a href="https://purplesyringa.moe/blog/superoptimizing-an-fpu-emulator/">Superoptimizing an FPU emulator</a></li>
<li><a href="https://hlcfan.github.io/gpui-canvas-spinner.html">Draw and Animate Loading Spinner with GPUI</a></li>
<li>[series] <a href="https://noahkawaguchi.com/blog/typenet-post-1/">Encoding TCP in Rust's Type System, Part 1: A Sequence Number Is Not a <code>u32</code></a></li>
<li>[series] <a href="https://kapteko.com/running-10-million-codex-clis-on-one-server-lfi-processes/">Running 10 million Codex CLIs on one server - LFI processes</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#research">Research</a></h5>
<ul>
<li><a href="https://doi.org/10.1145/3830440.3832304">An Incremental Approach to JIT Construction</a></li>
<li>[video] <a href="https://www.youtube.com/watch?v=8qwXgappTWQ">[Scheme'26] An Incremental Approach to JIT Construction</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#miscellaneous">Miscellaneous</a></h5>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#crate-of-the-week">Crate of the Week</a></h4>
<p>This week's crate is <a href="https://crates.io/crates/eilmeldung">eilmeldung</a>, a TUI RSS reader.</p>
<p>llogiq is pretty pleased with his choice, despite a lamentable lack of suggestions.</p>
<p><a href="https://users.rust-lang.org/t/crate-of-the-week/2704">Please submit your suggestions and votes for next week</a>!</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#calls-for-testing">Calls for Testing</a></h4>
<p>An important step for RFC implementation is for people to experiment with the
implementation and give feedback, especially before stabilization.</p>
<p>If you are a feature implementer and would like your RFC to appear in this list, add a
<code>call-for-testing</code> label to your RFC along with a comment providing testing instructions and/or
guidance on which aspect(s) of the feature need testing.</p>
<p><em>No calls for testing were issued this week by
<a href="https://github.com/rust-lang/rust/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Rust</a>,
<a href="https://github.com/rust-lang/cargo/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Cargo</a>,
<a href="https://github.com/rust-lang/rustup/issues?q=state%3Aopen%20label%3Acall-for-testing%20state%3Aopen">Rustup</a> or
<a href="https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing%20state%3Aopen">Rust language RFCs</a>.</em></p>
<p><a href="https://github.com/rust-lang/this-week-in-rust/issues">Let us know</a> if you would like your feature to be tracked as a part of this list.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers">Call for Participation; projects and speakers</a></h4>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cfp-projects">CFP - Projects</a></h5>
<p>Always wanted to contribute to open-source projects but did not know where to start?
Every week we highlight some tasks from the Rust community for you to pick and get started!</p>
<p>Some of these tasks may also have mentors available, visit the task page for more information.</p>
<p>ScreenCue</p>
<ul>
<li><a href="https://github.com/CrioNIK/ScreenCue/issues/1">ScreenCue - Add a reproducible desktop bug-report issue form</a></li>
</ul>



<p>sysknife</p>
<ul>
<li><a href="https://github.com/lacs-project/sysknife/issues/560">sysknife - README says the CLI's approval gate is sysknife approve; the CLI approves in-process after its own prompt</a></li>
<li><a href="https://github.com/lacs-project/sysknife/issues/561">sysknife - --dry-run exits 0 for a plan that breaks --max-risk or that this distro cannot run</a></li>
<li><a href="https://github.com/lacs-project/sysknife/issues/563">sysknife - Re-running sysknife-setup while the daemon runs fails with ETXTBSY and can leave mismatched binaries</a></li>
</ul>


<p>Manguebyte</p>
<ul>
<li><a href="https://github.com/alessonqueirozdev-hub/manguebyte/issues/22">Manguebyte - Put ParamSmoother under the allocation guard</a></li>
<li><a href="https://github.com/alessonqueirozdev-hub/manguebyte/issues/23">Manguebyte - Treat a NaN delay as the shortest delay in DelayLine::read and Delay::set_time</a></li>
<li><a href="https://github.com/alessonqueirozdev-hub/manguebyte/issues/24">Manguebyte - Check security advisories in the cargo deny job</a></li>
<li><a href="https://github.com/alessonqueirozdev-hub/manguebyte/issues/25">Manguebyte - Let a plugin report its tail to hosts</a></li>
<li><a href="https://github.com/alessonqueirozdev-hub/manguebyte/issues/7">Manguebyte - Add audio widgets, starting with an on-screen keyboard</a></li>
</ul>
<p>krate</p>
<ul>
<li><a href="https://github.com/incyashraj/krate/issues/32">krate - Fix two warnings on the wasm32 and Windows targets (easy)</a></li>
<li><a href="https://github.com/incyashraj/krate/issues/28">krate - Linux: follow the person's dark mode and text size (medium)</a></li>
<li><a href="https://github.com/incyashraj/krate/issues/29">krate - krate pack: add a --keep-debug flag (medium)</a></li>
</ul>
<p>If you are a Rust project owner and are looking for contributors, please submit tasks <a href="https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines">here</a> or through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a> or by reaching out on <a href="https://bsky.app/profile/thisweekinrust.bsky.social">Bluesky</a> or <a href="https://mastodon.social/@thisweekinrust">Mastodon</a>!</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cfp-events">CFP - Events</a></h5>
<p>Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.</p>



<p>If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a> or by reaching out on <a href="https://bsky.app/profile/thisweekinrust.bsky.social">Bluesky</a> or <a href="https://mastodon.social/@thisweekinrust">Mastodon</a>!</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#updates-from-the-rust-project">Updates from the Rust Project</a></h4>
<p>601 pull requests were <a href="https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2026-10-13..2026-10-20">merged in the last week</a></p>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#compiler">Compiler</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/164486">improve diagnostic for literals in lint attributes</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162432">improve diagnostics for non-well-formed associated items</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164178">fix <code>diagnostic::on_unknown</code> format placeholder for paths in expressions and type paths</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164236">move <code>fully_perform</code> early return earlier</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163857">overhaul span compression</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164059">perf: drop error in <code>unwrap_failed</code> instead of <code>unwrap</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162811">port lint attributes</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163383">provide context span pointing at trait/item when talking about assoc items</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164114">restore the old behavior for <code>derive(Default)</code> on fieldless types</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164332">skip move checks when the size limit is zero</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163436">stabilize <code>-Zembed-metadata</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162727">support function args const generics</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#library">Library</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/160285">add <code>codeview_annotation</code> intrinsic</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163611">add <code>core::process::resumable_breakpoint</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162444">make <code>std::fs::{File, ReadDir, DirEntry}</code> always <code>needs_drop</code> even when unsupported</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164369">make tuple <code>PartialOrd</code> chaining easier on mir-opt</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/161163">windows: stabilise <code>inherit_handles</code></a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#cargo">Cargo</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/cargo/pull/17602"><code>build-std</code>: Add build.build-std.when and crates config keys</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17613"><code>prerelease</code>: support <code>[patch]</code> with <code>-Zprerelease</code></a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17594"><code>config</code>: Apply dotted tuple support for rustflags</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17599"><code>config</code>: Don't load registry config from credentials.toml</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17521"><code>fingerprint</code>: choose a stable path when source mtimes tie</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17600"><code>util-schemas</code>: compile out the file-path hint where url can't build it</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17574">shell completion show all the packages having the feature</a></li>
<li><a href="https://github.com/rust-lang/cargo/pull/17589">check crate type when pruning <code>-L</code> paths</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustfmt">Rustfmt</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7179">config: fix lookup of global config files</a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7181">don't remove empty generic args when formatting in a macro context</a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7174">enforce comment width in item lists</a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7171">fix <code>cfg_select!</code> parser recovery handling and parser session error count leak</a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7170">fix statement comment wrapping</a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7192">prevent rustfmt from removing expression attrs when removing nested parens</a></li>
<li><a href="https://github.com/rust-lang/rustfmt/pull/7183">prevent rustfmt from removing necessary blocks in <code>cfg_select!</code> arms</a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rustdoc">Rustdoc</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/162778">add disambiguators for identically named method in sidebar</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164266">improvements for <code>rustc_must_implement_one_of</code></a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#clippy">Clippy</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17863">allow <code>allow_attributes</code> from inside macros</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17866">bail all doc lints when attributes come from external macro expansion</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/16549">clear collection reassignment</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17715">extend <code>from_str_radix_10</code> to NonZero types</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17881">fix <code>try_from_instead_of_from_str</code> lint suggestion causes error when <code>TryFrom::try_from</code> parameter is not named <code>value</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17828">fix <code>wildcard_imports</code> infinite loop on macro generated glob imports</a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17879">fix trailing semicolon with <code>nonstandard_macro_braces</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17029">new lint: <code>bufreader_stdin</code></a></li>
<li><a href="https://github.com/rust-lang/rust-clippy/pull/17865"><code>useless_attribute</code>: no longer lint <code>clippy::allow_attributes</code></a></li>
</ul>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-analyzer">Rust-Analyzer</a></h6>
<ul>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23513"><code>viewMir</code> panicking in code containing field projections</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23504">bail out of <code>struct_tail_erasing_lifetimes</code> on infinite structs</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23173">build non-ambiguous monikers in crates with multiple targets</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23533">emit E0029 for range patterns with inferred invalid types</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23518">escape keyword module name completions</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23523">improve attribute completions without snippet</a></li>
<li><a href="https://github.com/rust-lang/rust-analyzer/pull/23488">ops: resolve <code>ref-version-mismatch</code>, <code>stale-action-refs</code>, and <code>unpinned-uses</code></a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage">Rust Compiler Performance Triage</a></h5>
<p>A week dominated by changes of small magnitude. However, a number of
improvements landed that results in an overall average improvement of 1.4%,
which is a quite nice to see.</p>
<p>Triage done by <strong>@simulacrum</strong>.
Revision range: <a href="https://perf.rust-lang.org/?start=7211ea594cbf137ef6118b1752b959dea7cb9088&amp;end=bd4c6cc4aeef0eb9919c6f73c1e690677e9c6b38&amp;absolute=false&amp;stat=instructions%3Au">7211ea59..bd4c6cc4</a></p>
<p>6 Regressions, 9 Improvements, 8 Mixed; 0 of them in rollups
43 artifact comparisons made in total</p>
<p><a href="https://github.com/rust-lang/rustc-perf/blob/main/triage/2026/2026-10-19.md">Full report here</a></p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#approved-rfcs"/><a href="https://github.com/rust-lang/rfcs/commits/main">Approved RFCs</a></h5>
<p>Changes to Rust follow the Rust <a href="https://github.com/rust-lang/rfcs#rust-rfcs">RFC (request for comments) process</a>. These
are the RFCs that were approved for implementation this week:</p>
<ul>
<li><a href="https://github.com/rust-lang/rfcs/pull/4022">Fix libs nominated triagebot.toml</a></li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#final-comment-period">Final Comment Period</a></h5>
<p>Every week, <a href="https://www.rust-lang.org/team.html">the team</a> announces the 'final comment period' for RFCs and key PRs
which are reaching a decision. Express your opinions now.</p>
<h6><a class="toclink" href="https://this-week-in-rust.org/atom.xml#tracking-issues-prs">Tracking Issues &amp; PRs</a></h6>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#rust"/><a href="https://github.com/rust-lang/rust/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Rust</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/rust/pull/164328">core: Add <code>assert_matches</code> and <code>debug_assert_matches</code> to the next prelude</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/159374">Lower #[no_mangle] to #[symbol_name]/#[link_name]</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163816">stabilize String::into_chars</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163458">stabilize {Rc, Arc}::is_unique</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163499">vec: stabilise allocators for into_iter</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/161771">Don't require <code>unsafe</code> for struct and array patterns against union fields</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164028">Add a future incompat warning for #[no_link]</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/162597">raise ambiguity error on attribute macro that could be tool attribute</a></li>
<li><a href="https://github.com/rust-lang/rust/pull/164209">stabilize <code>-Znext-solver=globally</code></a></li>
<li><a href="https://github.com/rust-lang/rust/pull/163895">Stabilize <code>--remap-path-scope</code> in rustdoc and the <code>documentation</code> scope</a></li>
</ul>
<h7><a class="toclink" href="https://this-week-in-rust.org/atom.xml#compiler-team-mcps-only"/><a href="https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20label%3Afinal-comment-period%20state%3Aopen">Compiler Team</a> <a href="https://forge.rust-lang.org/compiler/mcp.html">(MCPs only)</a></h7>
<ul>
<li><a href="https://github.com/rust-lang/compiler-team/issues/1045">Add support for <code>annotate-snippets</code>'s <code>no-graphics</code> output format</a></li>
</ul>
<p><em>No Items entered Final Comment Period this week for
<a href="https://github.com/rust-lang/rfcs/issues?q=state%3Aopen%20label%3Afinal-comment-period%20state%3Aopen">Rust RFCs</a>,
<a href="https://github.com/rust-lang/cargo/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Cargo</a>,
<a href="https://github.com/rust-lang/lang-team/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Language Team</a>,
<a href="https://github.com/rust-lang/reference/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Language Reference</a>,
<a href="https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period%20state%3Aopen">Leadership Council</a> or
<a href="https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen%20label%3Afinal-comment-period%20sort%3Aupdated-desc%20state%3Aopen">Unsafe Code Guidelines</a>.</em>
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#new-and-updated-rfcs"/><a href="https://github.com/rust-lang/rfcs/pulls">New and Updated RFCs</a></h5>
<ul>
<li><a href="https://github.com/rust-lang/rfcs/pull/4021">Deprecate <code>std::env::{vars, args}</code></a></li>
<li><a href="https://github.com/rust-lang/rfcs/pull/4019">RFC: document a strict <code>Future</code> contract that forbids snoozing</a></li>
<li><a href="https://github.com/rust-lang/rfcs/pull/4018">RFC: extern "Rust_manyregs" ABI</a></li>
<li><a href="https://github.com/rust-lang/rfcs/pull/4020">RFC: add <code>poll_progress</code> to <code>AsyncIterator</code></a></li>
</ul>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#upcoming-events">Upcoming Events</a></h4>
<p>Rusty Events between 2026-10-21 - 2026-11-18 🦀</p>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#virtual">Virtual</a></h5>
<ul>
<li>2026-10-21 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210233/"><strong>Rust Study/Hack/Hang-out</strong></a></li>
</ul>
</li>
<li>2026-10-21 | Virtual (Cardiff, UK) | <a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff">Rust and C++ Cardiff</a><ul>
<li><a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/events/316880405/"><strong>Operating Systems Book Club: Paging Mechanisms</strong></a></li>
</ul>
</li>
<li>2026-10-22 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/k1978ath"><strong>Rust and the GPU from Native to Web: An Introduction to <code>wgpu</code></strong></a></li>
</ul>
</li>
<li>2026-10-22 | Virtual (Berlin, DE) | <a href="https://www.meetup.com/rust-berlin">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/316272609/"><strong>Rust Hack and Learn</strong></a></li>
</ul>
</li>
<li>2026-10-26 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/1byfc495"><strong>No Python was harmed: teaching a tiny MCU to learn as it goes</strong></a></li>
</ul>
</li>
<li>2026-10-27 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/310254771/"><strong>Fourth Tuesday Rust Bookclub</strong></a></li>
</ul>
</li>
<li>2026-10-27 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/315297195/"><strong>Lunch &amp; Learn: Reasoning with Async Rust</strong></a></li>
</ul>
</li>
<li>2026-10-29 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/q8i3385k"><strong>Creating a hexadecimal editor in Rust</strong></a></li>
</ul>
</li>
<li>2026-11-01 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/316331277/"><strong>Rust Deep Learning: First Sunday</strong></a></li>
</ul>
</li>
<li>2026-11-03 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/rfbzk3ae"><strong>Solving Real-World Planning Problems in Rust with SolverForge</strong></a></li>
</ul>
</li>
<li>2026-11-03 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/315773682/"><strong>👋 Community Catch Up</strong></a></li>
</ul>
</li>
<li>2026-11-04 | Virtual (Indianapolis, IN, US) | <a href="https://www.meetup.com/indyrs">Indy Rust</a><ul>
<li><a href="https://www.meetup.com/indyrs/events/wqzhftyjcpbgb/"><strong>Indy.rs - with Social Distancing</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Virtual (Berlin, DE) | <a href="https://www.meetup.com/rust-berlin">Rust Berlin</a><ul>
<li><a href="https://www.meetup.com/rust-berlin/events/316907780/"><strong>Rust Hack and Learn</strong></a></li>
</ul>
</li>
<li>2026-11-10 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/310254770/"><strong>Second Tuesday</strong></a></li>
</ul>
</li>
<li>2026-11-12 | Virtual (Nürnberg, DE) | <a href="https://www.meetup.com/rust-noris">Rust Nuremberg</a><ul>
<li><a href="https://www.meetup.com/rust-noris/events/315619619/"><strong>Rust Nürnberg online</strong></a></li>
</ul>
</li>
<li>2026-11-15 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/omlooqv8"><strong>Cursed Rust</strong></a></li>
</ul>
</li>
<li>2026-11-15 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust">Dallas Rust User Meetup</a><ul>
<li><a href="https://www.meetup.com/dallasrust/events/316563020/"><strong>Rust Deep Learning: Third Sunday</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual | <a href="https://luma.com/rust-maven">Rust 🦀 Maven</a><ul>
<li><a href="https://luma.com/2qfai4a8"><strong>Miscompilation in Rust 1.97</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust">Women in Rust</a><ul>
<li><a href="https://www.meetup.com/women-in-rust/events/315719313/"><strong>Lunch &amp; Learn: The Harness Wore a Trenchcoat - Building a Rust MCP Server</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Virtual (Washington, DC, US) | <a href="https://www.meetup.com/rustdc">Rust DC</a><ul>
<li><a href="https://www.meetup.com/rustdc/events/fhvsztyjcpbwb/"><strong>Mid-month Rustful</strong></a></li>
</ul>
</li>
<li>2026-11-18 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210234/"><strong>Writing a firmware for Xteink ereader in Rust</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#asia">Asia</a></h5>
<ul>
<li>2026-11-03 | Tel Aviv-Yafo, IL | <a href="https://www.meetup.com/rust-tlv">Rust 🦀 TLV</a><ul>
<li><a href="https://www.meetup.com/rust-tlv/events/316440864/"><strong>In person Rust November 2026 at AWS in Tel Aviv</strong></a></li>
</ul>
</li>
<li>2026-11-14 | Bengaluru, IN | <a href="https://hasgeek.com/rustbangalore/">Rust Bangalore</a><ul>
<li><a href="https://hasgeek.com/rustbangalore/november-2026-rustacean-meetup/"><strong>November 2026 Rustacean Meetup</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#europe">Europe</a></h5>
<ul>
<li>2026-10-22 | Karlsruhe, DE | <a href="https://www.meetup.com/rust-hack-learn-karlsruhe">Rust Hack &amp; Learn Karlsruhe</a><ul>
<li><a href="https://www.meetup.com/rust-hack-learn-karlsruhe/events/316799366/"><strong>Karlsruhe Rust Hack and Learn Meetup bei BlueYonder</strong></a></li>
</ul>
</li>
<li>2026-10-22 | Toulouse, FR | <a href="https://www.meetup.com/rust-community-toulouse">Rust Toulouse</a><ul>
<li><a href="https://www.meetup.com/rust-community-toulouse/events/316880185/"><strong>Rust Toulouse Meetup - Rust &amp; Python interoperability</strong></a></li>
</ul>
</li>
<li>2026-10-27 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus">Rust Aarhus</a><ul>
<li><a href="https://www.meetup.com/rust-aarhus/events/316796329/"><strong>Hack Night: Rust meets AI</strong></a></li>
</ul>
</li>
<li>2026-10-27 | Paris, FR | <a href="https://www.meetup.com/rust-paris">Rust Paris</a><ul>
<li><a href="https://www.meetup.com/rust-paris/events/316865643/"><strong>Rust meetup #89</strong></a></li>
</ul>
</li>
<li>2026-10-28 | Copenhagen, DK | <a href="https://www.meetup.com/copenhagen-rust-community">Copenhagen Rust Community</a><ul>
<li><a href="https://www.meetup.com/copenhagen-rust-community/events/316545936/"><strong>Rust meetup #72 sponsored by Google!</strong></a></li>
</ul>
</li>
<li>2026-10-31 | Stockholm, SE | <a href="https://www.meetup.com/stockholm-rust">Stockholm Rust</a><ul>
<li><a href="https://www.meetup.com/stockholm-rust/events/316721062/"><strong>Ferris' Fika Forum #31</strong></a></li>
</ul>
</li>
<li>2026-11-01 - 2026-11-03 | Italy, IN | <a href="https://rustlab.it/">RustLab</a><ul>
<li><a href="https://rustlab.it/schedule"><strong>RustLab - The International Conference on Rust in Italy</strong></a></li>
</ul>
</li>
<li>2026-11-04 | Dublin, IE | <a href="https://www.meetup.com/rust-dublin">Rust Dublin</a><ul>
<li><a href="https://www.meetup.com/rust-dublin/events/316898325/"><strong>Rust 263: Getting Started with the New Rust Driver for Oracle AI Database</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Milano, IT | <a href="https://www.meetup.com/rust-language-milano">Rust Language Milan</a><ul>
<li><a href="https://www.meetup.com/rust-language-milan/events/316213872/"><strong>Digital Model Trains &amp; Rust: Bare-Metal DCC Command Station on ESP32</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Leipzig, DE | <a href="https://www.meetup.com/rust-modern-systems-programming-in-leipzig">Rust - Modern Systems Programming in Leipzig</a><ul>
<li><a href="https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/313816501/"><strong>Everlock: Everything Is Git, Protocols Are Just Adapters</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#north-america">North America</a></h5>
<ul>
<li>2026-10-21 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210233/"><strong>Rust Study/Hack/Hang-out</strong></a></li>
</ul>
</li>
<li>2026-10-21 | San Francisco, CA, US | <a href="https://luma.com/bayarearust">Bay Area Rust</a><ul>
<li><a href="https://luma.com/ur4pm34i"><strong>Bay Area Rust - Embedded Meetup</strong></a></li>
</ul>
</li>
<li>2026-10-22 | New York, NY, US | <a href="https://www.meetup.com/rust-nyc">Rust NYC</a><ul>
<li><a href="https://www.meetup.com/rust-nyc/events/316901518/"><strong>Rust NYC w/Bryan Cantrill - Code Matters: Reflections on Rust in the LLM Age</strong></a></li>
</ul>
</li>
<li>2026-10-24 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924143/"><strong>Davis Square Rust Lunch, Oct 24</strong></a></li>
</ul>
</li>
<li>2026-10-28 | Austin, TX, US | <a href="https://www.meetup.com/rust-atx/events/">Rust ATX</a><ul>
<li><a href="https://www.meetup.com/rust-atx/events/316655403/"><strong>Rust Lunch - Fareground</strong></a></li>
</ul>
</li>
<li>2026-10-31 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924288/"><strong>North End Rust Lunch, Oct 31</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Montréal, CA | <a href="https://www.meetup.com/rust-montreal">Rust Montréal</a><ul>
<li><a href="https://www.meetup.com/rust-montreal/events/316919004/"><strong>November Monthly Social</strong></a></li>
</ul>
</li>
<li>2026-11-05 | San Francisco, CA | Rust LA: NVIDIA!<ul>
<li><a href="https://luma.com/iqe7wng1"><strong>NVIDIA x Lawrence Harvey | CUDA Rust</strong></a></li>
</ul>
</li>
<li>2026-11-05 | Saint Louis, MO, US | <a href="https://www.meetup.com/stl-rust">STL Rust</a><ul>
<li><a href="https://www.meetup.com/stl-rust/events/316896797/"><strong>HTMX and Rust</strong></a></li>
</ul>
</li>
<li>2026-11-12 | San Diego, CA, US | <a href="https://www.meetup.com/san-diego-rust">San Diego Rust</a><ul>
<li><a href="https://www.meetup.com/san-diego-rust/events/316886787/"><strong>San Diego Rust November Meetup - Back in person!</strong></a></li>
</ul>
</li>
<li>2026-11-14 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust">Boston Rust Meetup</a><ul>
<li><a href="https://www.meetup.com/bostonrust/events/316924331/"><strong>MIT Rust Lunch, Nov 14</strong></a></li>
</ul>
</li>
<li>2026-11-17 | Los Angeles, CA, US | <a href="https://www.meetup.com/rust-los-angeles">Rust Los Angeles</a><ul>
<li><a href="https://www.meetup.com/rust-los-angeles/events/316859673/"><strong>Rust LA November w/ Hadrian!</strong></a></li>
</ul>
</li>
<li>2026-11-17 | San Francisco, CA, US | <a href="https://www.meetup.com/san-francisco-rust-study-group">San Francisco Rust Study Group</a><ul>
<li><a href="https://www.meetup.com/san-francisco-rust-study-group/events/315783989/"><strong>Rust Hacking in Person</strong></a></li>
</ul>
</li>
<li>2026-11-18 | Hybrid (Vancouver, CA) | <a href="https://www.meetup.com/vancouver-rust">Vancouver Rust</a><ul>
<li><a href="https://www.meetup.com/vancouver-rust/events/315210234/"><strong>Writing a firmware for Xteink ereader in Rust</strong></a></li>
</ul>
</li>
</ul>
<h5><a class="toclink" href="https://this-week-in-rust.org/atom.xml#south-america">South America</a></h5>
<ul>
<li>2026-11-07 | Planalto Paulista, BR | <a href="https://www.meetup.com/rust-sao-paulo-meetup">Rust São Paulo Meetup</a><ul>
<li><a href="https://www.meetup.com/rust-sao-paulo-meetup/events/316812852/"><strong>Encontro do Rust-SP - Agora no Luma</strong></a></li>
</ul>
</li>
</ul>
<p>If you are running a Rust event please add it to the <a href="https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com">calendar</a> to get
it mentioned here. Please remember to add a link to the event too.
Email the <a href="mailto:community-team@rust-lang.org">Rust Community Team</a> for access.</p>
<h4><a class="toclink" href="https://this-week-in-rust.org/atom.xml#jobs">Jobs</a></h4>
<p>Please see the latest <a href="https://www.reddit.com/r/rust/comments/1wzctie/official_rrust_whos_hiring_thread_for_jobseekers/">Who's Hiring thread on r/rust</a></p>
<h3><a class="toclink" href="https://this-week-in-rust.org/atom.xml#quote-of-the-week">Quote of the Week</a></h3>
<blockquote>
<p>To me it seems the same things that make Rust a desirable target for LLM generated code are the same things that make it desirable for me as a human writing code, that being the fantastic compiler feedback and the first class tooling.</p>
</blockquote>
<p>– <a href="https://users.rust-lang.org/t/recent-explosion-in-rust-rewrites-and-reimplementations-with-llms-thoughts/142939/33">Christian Haynes on rust-users</a></p>
<p>Thanks to <a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328/1829">Moy2010</a> for the suggestion!</p>
<p><a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328">Please submit quotes and vote for next week!</a></p>
<p>This Week in Rust is edited by:</p>
<ul>
<li><a href="https://github.com/nellshamrell">nellshamrell</a></li>
<li><a href="https://github.com/llogiq">llogiq</a></li>
<li><a href="https://github.com/ericseppanen">ericseppanen</a></li>
<li><a href="https://github.com/extrawurst">extrawurst</a></li>
<li><a href="https://github.com/U007D">U007D</a></li>
<li><a href="https://github.com/mariannegoldin">mariannegoldin</a></li>
<li><a href="https://github.com/bdillo">bdillo</a></li>
<li><a href="https://github.com/opeolluwa">opeolluwa</a></li>
<li><a href="https://github.com/bnchi">bnchi</a></li>
<li><a href="https://github.com/KannanPalani57">KannanPalani57</a></li>
<li><a href="https://github.com/tzilist">tzilist</a></li>
</ul>
<p><em>Email list hosting is sponsored by <a href="https://foundation.rust-lang.org/">The Rust Foundation</a></em></p>
<p><small><a href="https://www.reddit.com/r/rust/comments/1xc54av/this_week_in_rust_674/">Discuss on r/rust</a></small></p></div>
    </content>
    <updated>2026-10-21T04:00:00Z</updated>
    <published>2026-10-21T04:00:00Z</published>
    <category term="This Week in Rust"/>
    <author>
      <name>TWiR Contributors</name>
    </author>
    <source>
      <id>https://this-week-in-rust.org/</id>
      <link href="https://this-week-in-rust.org/" rel="alternate" type="text/html"/>
      <link href="https://this-week-in-rust.org/atom.xml" rel="self" type="application/atom+xml"/>
      <title>This Week in Rust</title>
      <updated>2026-11-11T05:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/security/?p=2931</id>
    <link href="https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/" rel="alternate" type="text/html"/>
    <title>Protecting Firefox users following the compromise of eMudhra intermediate certificates</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>On Saturday, October 17, at 20:06 UTC, Mozilla received a report that private keys associated with eight eMudhra intermediate certificates had been compromised. These keys could allow attackers to issue … <a class="go" href="https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/">Read more</a></p>
<p>The post <a href="https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/">Protecting Firefox users following the compromise of eMudhra intermediate certificates</a> appeared first on <a href="https://blog.mozilla.org/security">Mozilla Security Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>On Saturday, October 17, at 20:06 UTC, Mozilla received a report that private keys associated with eight eMudhra intermediate certificates had been compromised. These keys could allow attackers to issue fraudulent HTTPS certificates for websites they do not control. An attacker who could intercept a user’s connection could use those certificates to impersonate websites and potentially read or modify traffic.</p>
<p>Mozilla engineers responded immediately, blocking the affected certificates in Firefox using<a href="https://blog.mozilla.org/security/2015/03/03/revoking-intermediate-certificates-introducing-onecrl/"> OneCRL</a>, Mozilla’s centralized list of revoked certificates. OneCRL delivers this protection without requiring users to update or restart Firefox.</p>
<p>By 22:59 UTC that same day, in less than 3 hours after we received the report, the updated OneCRL distribution was complete for all Firefox users with standard configurations.</p>
<p>Today, we are also releasing <a href="https://www.firefox.com/en-US/firefox/158.0.1/releasenotes/">Firefox 158.0.1</a> for Desktop and Android, along with <a href="https://www.firefox.com/en-US/firefox/115.43.1/releasenotes/">Firefox ESR 115.43.1</a> and <a href="https://www.firefox.com/en-US/firefox/153.5.1/releasenotes/">Firefox ESR 153.5.1</a>. These releases will distribute this protection for a minority of users whose custom settings may have prevented them from receiving the OneCRL update.</p>
<p>We are also updating the trusted certificate list in NSS (<a href="https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/vSxZxnOMMvs">NSS 3.131.1</a>) to remove the root certificate that signed the affected intermediates. Firefox is already protected through OneCRL, but this additional update helps protect other applications that use Mozilla’s trust store or versions derived from it and do not receive OneCRL updates.</p>
<p>Mozilla believes everyone has a fundamental right to security and privacy online. We remain committed to defending those rights and acting quickly to protect users.</p>
<p>Transparency is essential to trust. We will share more information as soon as circumstances allow.</p>
<p><b>Update added October 21:</b> On Wednesday, October 21, at 08:29 UTC, we released an additional update for Firefox for Android (<a href="https://www.firefox.com/en-US/firefox/android/158.0.2/releasenotes/">158.0.2</a>) to fix an issue where some clients were not applying changes to the bundled OneCRL blocklist immediately after startup.</p>
<p>The post <a href="https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/">Protecting Firefox users following the compromise of eMudhra intermediate certificates</a> appeared first on <a href="https://blog.mozilla.org/security">Mozilla Security Blog</a>.</p></div>
    </content>
    <updated>2026-10-20T12:54:54Z</updated>
    <published>2026-10-20T12:54:54Z</published>
    <category term="Security"/>
    <author>
      <name>Firefox Security Team</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/security/</id>
      <link href="https://blog.mozilla.org/security/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/security/" rel="alternate" type="text/html"/>
      <title>Mozilla Security Blog</title>
      <updated>2026-11-10T18:36:02Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88620</id>
    <link href="https://blog.mozilla.org/en/mozilla/internet-policy/uk-cma-browser-choice-screens/" rel="alternate" type="text/html"/>
    <title>Why is the CMA asking us to choose the furniture before the house? The UK’s search choice screens need browser choice screens alongside them</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Mobile browsers are a key gateway to the internet for 56 million people in the UK. Smartphone users spend around half an hour a day in these apps, and opening a browser is the most common way they look up information online. Yet most people are using a smartphone browser that was preinstalled and set […]</p>
<p>The post <a href="https://blog.mozilla.org/en/mozilla/internet-policy/uk-cma-browser-choice-screens/">Why is the CMA asking us to choose the furniture before the house? The UK’s search choice screens need browser choice screens alongside them</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Mobile browsers are a key gateway to the internet for <a href="https://assets.publishing.service.gov.uk/media/67d1abd1a005e6f9841a1d94/Final_decision_report1.pdf">56 million people</a> in the UK. Smartphone users spend around half an hour a day in these apps, and <a href="https://assets.publishing.service.gov.uk/media/66b47c8afc8e12ac3edb0c3e/Verian_Mobile_Browsers_Research_Final_Report.pdf">opening a browser</a> is the most common way they look up information online.</p>



<p>Yet most people are using a smartphone browser that was preinstalled and set as the default for them, without ever being asked which browser they would actually prefer.</p>



<p>Mozilla believes people deserve an active choice in the tools they depend on every day, which is why the latest proposals from the UK Competition and Markets Authority (CMA) matter.<strong> We welcome the CMA’s plans to give people a choice of search service and are asking it to consult on browser choice now, so both screens can launch together.</strong></p>



<p>On September 23rd, the CMA<a href="https://www.gov.uk/government/news/cma-strengthens-proposals-allowing-people-choice-over-their-search-service"> published updated plans</a> that would require Google to show people in the UK a choice of search service on new Android devices, covering the default search app and home-screen search widget as well as Chrome. Search choice screens would also appear in Chrome on other platforms, including through a major update for existing users. Some AI assistants would also be eligible to appear alongside search engines.</p>



<h3><strong>The proposals are well designed, but solve only half the problem</strong></h3>



<p>The CMA’s mobile browser investigation found that preinstallation, prominent placement and default settings restrict browser competition. <a href="https://research.mozilla.org/browser-competition/choicescreen/">Mozilla’s innovative 2023 experiment</a> showed that properly designed browser choice screens can help people choose a browser they expect to keep using, and can be an effective tool for giving people agency over their online life. It also showed that an overwhelming majority of people (98%!) want to see them. </p>



<p>The EU Digital Markets Act has since <a href="https://blog.mozilla.org/netpolicy/2026/05/11/six-million-selections-later-how-the-dma-is-giving-people-browser-choice/">demonstrated their impact in practice.</a> We welcome the CMA’s work on search choice, but people in the UK deserve browser choice too. Asking people to pick a search service inside a browser that most of them never actively chose in the first place leaves some of the biggest issues identified in the CMA’s own mobile browser investigation unaddressed.</p>



<p>The CMA commissioned <a href="https://www.gov.uk/government/consultations/googles-general-search-services-proposed-user-choice-conduct-requirement">user research</a> on search choice screens to refine and improve the proposals it first consulted on in January. Providers’ positions on the choice screen would be fully randomised. Users would have to scroll to the bottom before confirming, and could “test drive” a search provider for at least a week.</p>



<p>The CMA has also recognized that search is changing. Its research found that many people were already using AI assistants to search alongside traditional search services. Under the revised, more technology-neutral eligibility criteria, an AI assistant could also qualify to appear on the search choice screen if it meets the requirements, including being able to search the web and attribute its sources. But browser choice should not be left behind.</p>



<h3><strong>Why the two choices belong together</strong></h3>



<ul>
<li><strong>Less confusion.</strong> The CMA’s new research found that participants often confused browsers with search services and were unsure what their search choice would change. Mozilla’s research has revealed similar confusion. These findings support designing and testing the two screens together, with clear explanations of each decision.<br/></li>



<li><strong>Less duplication.</strong> The CMA’s work on search choice can also inform browser choice. Developing the two together would allow the design, order and timing to be tested as one journey, helping to avoid separate rounds of changes and interruptions for users.<br/></li>



<li><strong>Order matters.</strong> Nobody chooses the furniture before the house. Browsers have their own search defaults, which is why we recommend showing the browser choice screen first, followed by the search screen, with wording that makes clear these are two separate decisions. </li>
</ul>



<h3><strong>The EU and Japan already show both screens</strong></h3>



<p>The EU’s Digital Markets Act introduced browser choice screens on iOS for the first time and brought <a href="https://android.com/choicescreen/dma">browser and search choice together</a> during Android set-up.</p>



<p>Browser first, then search, so the relationship between the two makes sense. In Japan, search and browser choice screens are presented on both Android and iOS.</p>



<p>And people are making use of the browser screen to select alternatives. In May,<a href="https://blog.mozilla.org/netpolicy/2026/05/11/six-million-selections-later-how-the-dma-is-giving-people-browser-choice/"> we reported</a> <strong>Firefox is selected through a DMA choice screen once every ten seconds</strong>, with retention five times higher than for organic downloads. Other independent browsers have also reported substantial growth. </p>



<h3><strong>Choice matters more as AI moves into the browser</strong></h3>



<p>The CMA’s proposals recognize that AI is changing how people search. AI is also changing what browsers offer, adding to the ways they compete on features, privacy and user control. Firefox already lets people on desktop<a href="https://support.mozilla.org/en-US/kb/ai-chatbot"> pick which AI assistant sits in the sidebar</a>, and our<a href="https://blog.mozilla.org/en/firefox/firefox-smart-window/"> Smart Window beta</a> extends that choice to the model behind the browser’s own assistant. There are meaningful differences between browsers. AI is the latest example of why giving people an active choice matters.</p>



<p>When people aren’t offered an active browser choice, they may be choosing search and AI services within a browser someone else picked. One decision taken at the factory can end up shaping the ones that follow. A search choice screen gives people a say over their search provider; offering browser choice alongside it would give them a say over that first decision too.</p>



<h3><strong>Our ask of the CMA</strong></h3>



<p>We’re asking the CMA to consult now on browser choice screens for Apple’s and Google’s mobile platforms, so they can launch alongside the search screens. Apple and Google already offer browser choice screens in the EU and Japan. The CMA can draw on that experience and its own research to give people in the UK an active choice of both browser and search service.</p>



<p>Mozilla’s response to the consultation is available <a href="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Google-Search-User-Choice-CR-Response-October-2026-1.pdf">here</a>.<br/><br/> </p>
<p>The post <a href="https://blog.mozilla.org/en/mozilla/internet-policy/uk-cma-browser-choice-screens/">Why is the CMA asking us to choose the furniture before the house? The UK’s search choice screens need browser choice screens alongside them</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-20T07:00:00Z</updated>
    <published>2026-10-20T07:00:00Z</published>
    <category term="Internet Policy"/>
    <category term="Our Work"/>
    <category term="homepage"/>
    <author>
      <name>Gemma Petrie</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>https://blog.rust-lang.org/2026/10/20/Rustup-1.29.2/</id>
    <link href="https://blog.rust-lang.org/2026/10/20/Rustup-1.29.2/" rel="alternate" title="Announcing rustup 1.29.2" type="text/html"/>
    <title xml:lang="en">Announcing rustup 1.29.2</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><p>The rustup team is happy to announce the release of rustup version 1.29.2.</p>
<p><a href="https://rustup.rs" rel="external">Rustup</a> is the recommended tool to install <a href="https://www.rust-lang.org" rel="external">Rust</a>, a
programming language that empowers everyone to build reliable and efficient
software.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/20/Rustup-1.29.2/#what-s-new-in-rustup-1-29-2"/>
What's new in rustup 1.29.2</h3>
<p>This is a small release which only updates the rustls-webpki and
webpki-root-certs dependencies to address the problematic eMudhra
intermediate certificates issue described in <a href="https://www.cve.org/CVERecord?id=CVE-2026-111943" rel="external">CVE-2026-111943</a>.</p>
<p>See also <a href="https://rustsec.org/advisories/RUSTSEC-2026-0382.html" rel="external">RUSTSEC-2026-0382</a>.</p>
<p>Further details are available in the <a href="https://github.com/rust-lang/rustup/blob/stable/CHANGELOG.md" rel="external">changelog</a>!</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/20/Rustup-1.29.2/#how-to-update"/>
How to update</h3>
<p>If you have a previous version of rustup installed, getting the new one is as easy as stopping
any programs which may be using rustup (e.g. closing your IDE) and running:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>$ rustup self update</span></span></code></pre>
<p>Rustup will also automatically update itself at the end of a normal toolchain update:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>$ rustup update</span></span></code></pre>
<p>If you don't have it already, you can <a href="https://rustup.rs" rel="external">get rustup</a> from the appropriate page on our website.</p>
<p>Rustup's documentation is also available in <a href="https://rust-lang.github.io/rustup/" rel="external">the rustup book</a>.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/20/Rustup-1.29.2/#caveats"/>
Caveats</h3>
<p>Rustup releases can come with problems not caused by rustup itself but just due to having a new release.</p>
<p>In particular, anti-malware scanners might block rustup or stop it from creating or copying
files, especially when installing <code>rust-docs</code> which contains many small files.</p>
<p>Issues like this should be automatically resolved in a few weeks when the anti-malware scanners are updated
to be aware of the new rustup release.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/20/Rustup-1.29.2/#thanks"/>
Thanks</h3>
<p>Thanks again to all the <a href="https://github.com/rust-lang/rustup/blob/stable/CHANGELOG.md#detailed-changes" rel="external">contributors</a> who made this rustup release possible!</p></div>
    </content>
    <updated>2026-10-20T00:00:00Z</updated>
    <published>2026-10-20T00:00:00Z</published>
    <author>
      <name>The Rustup Team</name>
    </author>
    <source>
      <id>https://blog.rust-lang.org/</id>
      <author>
        <name>Maintained by the Rust Teams.</name>
        <uri>https://github.com/rust-lang/blog.rust-lang.org/</uri>
      </author>
      <link href="https://blog.rust-lang.org/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://blog.rust-lang.org/" rel="alternate" type="text/html"/>
      <subtitle xml:lang="en">Empowering everyone to build reliable and efficient software.</subtitle>
      <title xml:lang="en">Rust Blog</title>
      <updated>2026-11-13T09:01:38Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>http://chuttenblog.wordpress.com/?p=6611</id>
    <link href="https://chuttenblog.wordpress.com/2026/10/19/eleven-year-moziversary/" rel="alternate" type="text/html"/>
    <title>Eleven-Year Moziversary</title>
    <summary>I’ve been working at Mozilla for eleven years, my golly. I’m still on my third hardware refresh (a Dell XPS I continue to dislike), I’m up to my fourth CEO, and 76 reorgs have happened (well, I know that quite a few things that would normally have counted haven’t been counted there, so it’s probably […]</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p class="wp-block-paragraph">I’ve been working at Mozilla for eleven years, my golly. I’m still on my third hardware refresh (a Dell XPS I continue to dislike), I’m up to my fourth CEO, and <a href="https://arewereorganizedyet.com/">76 reorgs</a> have happened (well, I know that quite a few things that would normally have counted haven’t been counted there, so it’s probably a higher number than that).</p>



<p class="wp-block-paragraph">I’m still getting Firefox Desktop to use Glean instead of Legacy Telemetry. We’re <a href="https://arewegleanyet.com/">more than two-thirds of the way done</a> with removing the legacy system, with concrete plans about what to do with the rest. I’m still not blogging as much as I’d like, but I have some honest hope that I might change that in no small part thanks to <a href="https://mastodon.social/@chutten/117411459230748946">someone who mentioned in passing that they liked my posts</a>.</p>



<p class="wp-block-paragraph">Looking back at <a href="https://chuttenblog.wordpress.com/2025/11/03/ten-year-moziversary/">last year’s predictions</a>, I did indeed requisition a second work monitor, which is working out well.</p>



<p class="wp-block-paragraph">I was right that FOG Migration hasn’t completely removed all of Legacy Telemetry, though we’re a lot closer than I thought we’d be. I do have a little time to think about doing other things, but not all that much, so the part of the prediction where I’d do something else is a “maybe”.</p>



<p class="wp-block-paragraph">My desire to push for a sensible user population measurement did not have a chance to be acted upon. We might be shifting what the business counts, but not to anything I’ve had a say in. At least one of the reorgs that happened changed the organizational distance between my team and the other parts of Data that would be involved in such a measurement, other non-work things took way too much time and resulted in slower overall work velocity, and FOG Migration kept taking priority.</p>



<p class="wp-block-paragraph">I didn’t think there’d be an All Hands, and in the off-change there were, it’d be a multi-city “Summit style” affair. I was half wrong twice: there wasn’t an All Hands but there was indeed an all-Engineering Summit; it wasn’t in multiple cities but just one. I was right that Toronto finally got its chance. I enjoyed the heck out of it as it really reminded me of some of the things I really missed about the All Hands of yore. It could’ve been a day longer, it could’ve been a little more of a polished experience like Brianna-era events were… but for not having done anything like this for two years, what an accomplishment. I was initially skeptical about spending hours of the first day making small talk deliberately with people you don’t know on the subject of the work you do and how you do it, but once it was framed as an effort to scale-up and operationalize <a href="https://en.wiktionary.org/wiki/hallway_track">The Hallway Track</a> I suddenly understood it.</p>



<p class="wp-block-paragraph">I had wishful, hopeful thinking that the genAI bubble would have burst or a new shiny late-stage capitalist exploitation mechanism would be draining focus away from it by now. Alas neither. Though <a href="https://www.theverge.com/ai-artificial-intelligence/1009802/character-ai-files-for-bankruptcy-disney">maybe things are beginning</a>? I can dream.</p>



<p class="wp-block-paragraph">I was also half-wrong about there being a new CEO but not yet sworn in. I didn’t account for the candidate coming from within the org, meaning it could be quick. We’ve had Anthony hired and active for nearly a year now and he’s… fine? So far the changes he’s made to MoCo haven’t been to any of the things I feel we need to change, so I can’t really evaluate him. (Assuming that, since he (well, his reports) are able to evaluate my performance, it’s only fair that I get to evaluate his in turn. That’s how this works, right?)</p>



<p class="wp-block-paragraph">Predictions for the coming year:</p>



<ul class="wp-block-list">
<li>We’re going to stick with Anthony as CEO, keeping my count stable</li>



<li>Firefox Enterprise is going to be a runaway success, finally giving MoCo that revenue diversification we’ve been aiming for</li>



<li>Maybe the genAI bubble will have burst? (Yes, this is a duplicate from last year)</li>



<li>I’ll read <a href="https://bookpile.org/b/9781032963389">The Psychology of Software Teams</a>. It will frustrate me to finally be able to name and cite sources for how badly this industry treats its workers.</li>



<li>FOG Migration will be “complete” (Legacy Telemetry probes will be gone, code will have been removed) and I’ll move on to working on… maybe data consent management? Developing a way to find out which metrics are unused, and removing them? I have a few ideas.</li>



<li>I’ll still be complaining about this Dell XPS laptop, and considering what I’ll be refreshing to the following February. Maybe I’ll finally leave Windows behind?</li>



<li>I will have blogged at least three times (setting my prediction deliberately and achievably low), probably mostly video game musings in my ongoing <a href="https://chuttenblog.wordpress.com/tag/sif/">So I’ve Finished</a> series. But I do have a draft of a work post about the history of public data tooling at Mozilla that I’ve been meaning to finish…</li>
</ul>



<p class="wp-block-paragraph">To another year of supporting <a href="https://www.mozilla.org/mission/">The Mission</a>!</p></div>
    </content>
    <updated>2026-10-19T13:43:35Z</updated>
    <published>2026-10-19T13:43:35Z</published>
    <category term="mozilla"/>
    <category term="anniversary"/>
    <category term="data"/>
    <category term="firefox"/>
    <category term="if this were a marriage the traditional gift would be steel"/>
    <category term="work"/>
    <author>
      <name>chuttenc</name>
    </author>
    <source>
      <id>https://chuttenblog.wordpress.com</id>
      <logo>https://s2.wp.com/i/webclip.png</logo>
      <link href="https://chuttenblog.wordpress.com/category/mozilla/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://chuttenblog.wordpress.com" rel="alternate" type="text/html"/>
      <link href="https://chuttenblog.wordpress.com/osd.xml" rel="search" title="chuttenblog" type="application/opensearchdescription+xml"/>
      <link href="https://chuttenblog.wordpress.com/?pushpress=hub" rel="hub" type="text/html"/>
      <title>mozilla – chuttenblog</title>
      <updated>2026-10-19T13:43:35Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149833</id>
    <link href="https://discourse.mozilla.org/t/mozphab-2-23-0-released/149833" rel="alternate" type="text/html"/>
    <title>MozPhab 2.23.0 Released</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Bugs resolved in Moz-Phab 2.23.0:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/2068797">bug 2068797</a> Local test suite runs read and write the real <code>user_info.json</code></li>
<li><a href="https://bugzilla.mozilla.org/2076869">bug 2076869</a> Record a profile of each moz-phab run, and open it in the Firefox Profiler</li>
</ul>
<p>Discuss these changes in <span class="hashtag-raw">#engineering-workflow</span> on Slack or <span class="hashtag-raw">#Conduit</span> Matrix.</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/mozphab-2-23-0-released/149833">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-16T17:32:57Z</updated>
    <published>2026-10-16T17:32:57Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>sheehan</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/mozphab-2-23-0-released/149833.rss" title="MozPhab 2.23.0 Released"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149832</id>
    <link href="https://discourse.mozilla.org/t/firefox-devtools-mcp-0-10-6-released/149832" rel="alternate" type="text/html"/>
    <title>Firefox DevTools MCP 0.10.6 released</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>New release of Firefox DevTools MCP. Available on npm at <a href="https://www.npmjs.com/package/@mozilla/firefox-devtools-mcp" rel="noopener nofollow ugc">https://www.npmjs.com/package/@mozilla/firefox-devtools-mcp</a></p>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297245-added-1" name="p-297245-added-1"/>Added</h3>
<ul>
<li>New <code>print_page</code> tool. It saves the current page as a PDF file and has optional <code>landscape</code> and <code>background</code> options. It uses print CSS, so you can use it to check print styles</li>
</ul>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297245-fixed-2" name="p-297245-fixed-2"/>Fixed</h3>
<ul>
<li><code>--profile-path</code> now reuses a profile that the server created, instead of creating a new profile inside it. The server marks its profiles with a <code>.firefox-devtools-mcp</code> file. Paths without this marker still use the <code>firefox_devtools_mcp_profile</code> subfolder</li>
<li><code>list_pages</code>, <code>select_page</code>, <code>close_page</code>, <code>navigate_page</code> and <code>new_page</code> no longer bring every tab to the front. They now read the tab list with WebDriver BiDi</li>
<li><code>select_page</code> and <code>close_page</code> now act on the tab from the last tab list, even if tabs were opened or closed since then</li>
</ul>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297245-changed-3" name="p-297245-changed-3"/>Changed</h3>
<ul>
<li><code>list_pages</code> no longer lists tabs that are not loaded yet, for example restored tabs that were never opened</li>
<li>If the title of a tab cannot be read within 1 second, the tab is listed with the title <code>(unknown)</code></li>
</ul>
<p>Full changelog: <a class="inline-onebox" href="https://github.com/mozilla/firefox-devtools-mcp/releases/tag/v0.10.6" rel="noopener nofollow ugc">Release v0.10.6 · mozilla/firefox-devtools-mcp · GitHub</a><br/>
Repository and issues: <a class="inline-onebox" href="https://github.com/mozilla/firefox-devtools-mcp" rel="noopener nofollow ugc">GitHub - mozilla/firefox-devtools-mcp: Model Context Protocol server for Firefox DevTools - enables AI assistants to inspect and control Firefox browser through WebDriver BiDi · GitHub</a><br/>
Public chatroom: <a href="https://chat.mozilla.org/#/room/#firefox-devtools-mcp:mozilla.org" rel="noopener nofollow ugc">https://chat.mozilla.org/#/room/#firefox-devtools-mcp:mozilla.org</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/firefox-devtools-mcp-0-10-6-released/149832">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-16T16:08:47Z</updated>
    <published>2026-10-16T16:08:47Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>jdescottes</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/firefox-devtools-mcp-0-10-6-released/149832.rss" title="Firefox DevTools MCP 0.10.6 released"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88484</id>
    <link href="https://blog.mozilla.org/en/mozilla/ai/trustworthy-ai-map/" rel="alternate" type="text/html"/>
    <title>This map shows the most important asset that VC-backed companies need right now</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>What’s the most vital asset for an AI company today?  For venture backed AI business, it might be “funding” or “revenue”. But, there’s another asset that’s just as critical: trust.  At Mozilla, building technology that people and businesses can genuinely trust has been a long-standing, guiding principle. That’s why we’re supporting the launch of the Trustworthy […]</p>
<p>The post <a href="https://blog.mozilla.org/en/mozilla/ai/trustworthy-ai-map/">This map shows the most important asset that VC-backed companies need right now  </a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>What’s the most vital asset for an AI company today?  For venture backed AI business, it might be “funding” or “revenue”. But, there’s another asset that’s just as critical: <em>trust</em>. </p>



<p>At Mozilla, building technology that people and businesses can genuinely trust has been a <a href="https://www.mozilla.org/en-CA/about/manifesto/">long-standing, guiding principle</a>. That’s why we’re supporting the launch of the <a href="http://trustworthyaimap.org">Trustworthy AI Map</a>, a market map of VC-backed companies building the infrastructure for trustworthy AI. </p>



<p>Supported by seven organizations, including Mozilla, the Trustworthy AI Map features 79 companies across 15 countries, from early to later-stage venture. It maps companies building products for AI deployment across seven layers of the AI stack, including identity, data control, interoperability and evaluation. </p>



<p>The map connects the products with the companies and capital behind them, helping investors, founders and businesses explore commercial opportunities. To be featured, trust must be baked into its product or business model through human agency, trust by design or aligned business models. </p>



<p>This initiative aligns with much of our work over the past year. We’ve invested in companies through Mozilla Ventures, launched Otari, an open source enterprise tool which allows you to control your LLM infrastructure from a single layer, and published landmark research in our <a href="https://stateofopensource.ai/">State of Open Source AI report</a> that’s demystifying the open source AI landscape and shows that the capability gap between open and closed models is closing. </p>



<p>We’ve also partnered with Mila: the Quebec AI Institute, <a href="https://blog.mozilla.org/en/mozilla/mila-canada-open-source-ai-initiative/">to build an open source AI foundation layer</a> that enables organizations and institutions to own and operate their own advanced AI systems locally, ensuring full control over their technology and data. The project has the backing of the Canadian government, and industry leaders like Hypertec. </p>



<p>At a time when fear and uncertainty about AI are on the rise, trust is not just a virtue; it’s a path towards profitability. Explore the <a href="http://trustworthyaimap.org">Trustworthy AI Map</a> to see how. </p>



<p><em>Learn more at </em><a href="http://trustworthyaimap.org"><em>trustworthyaimap.org</em></a><em>.</em></p>
<p>The post <a href="https://blog.mozilla.org/en/mozilla/ai/trustworthy-ai-map/">This map shows the most important asset that VC-backed companies need right now  </a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-16T13:00:00Z</updated>
    <published>2026-10-16T13:00:00Z</published>
    <category term="AI"/>
    <category term="Our Work"/>
    <category term="homepage"/>
    <author>
      <name>Mark Surman</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=87700</id>
    <link href="https://blog.mozilla.org/en/firefox/new-firefox-sounds/" rel="alternate" type="text/html"/>
    <link href="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/09/Firefox-Logo-Sonic-2.mp4" length="638202" rel="enclosure" type="video/mp4"/>
    <link href="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/09/Firefox-Sound-Hero1.mp4" length="1972739" rel="enclosure" type="video/mp4"/>
    <link href="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/09/Firefox-Notification-Sound-1.mp4" length="484186" rel="enclosure" type="video/mp4"/>
    <title>What does the (Fire)fox say?</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>It all started with a question: What does Firefox sound like to you? Over the past year, Mozilla developed a small but meaningful set of sounds to add a sonic dimension to the Firefox experience. When we started this process, we knew we wanted something warm, human, and representative of our open source identity. We […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/new-firefox-sounds/">What does the (Fire)fox say?</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>It all started with a question: What does Firefox sound like to you?<br/><br/>Over the past year, Mozilla developed a small but meaningful set of sounds to add a sonic dimension to the Firefox experience. When we started this process, we knew we wanted something warm, human, and representative of our open source identity. We also knew we didn’t want to invent these sounds in a vacuum. So we did what we’ve always done and turned to our community.<br/><br/>With the help of creative audio company <a href="https://soundslikethese.com/">Sounds Like These</a>, we <a href="https://connect.mozilla.org/t5/discussions/call-for-participation-what-does-firefox-sound-like-to-you/m-p/122440/highlight/true#M48122">reached out</a> to Firefox users, contributors, and team members across the globe asking them to send us audio and written descriptions of what Firefox sounds like to them. This feedback became our compass.<br/><br/>From there, we began building three new sounds that bring to life our logo, mascot <a href="https://blog.mozilla.org/en/firefox/meet-kit/">Kit</a>, and Firefox notifications. The logo and Kit sound have already begun rolling out across the Firefox brand (check them out in our <a href="https://www.youtube.com/watch?v=l7tQ1v4TCeY">new design launch announcement</a>) – and we’re excited to bring the notification sound to the browser in a future update.<br/><br/>Not only did we want these new sounds to reflect Mozilla’s mission and values, we also wanted to ensure they felt connected to one another. This is the story of how they came to be.</p>



<h3><strong>The logo sound: A human chorus rooted in nature</strong></h3>



<figure class="wp-block-video"><video controls="controls" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/09/Firefox-Logo-Sonic-2.mp4"/></figure>



<p><a href="https://brand.mozilla.com/d/5UkPdpbtt8LS/audio-library/show/eyJpZCI6NDY2MDksInNjb3BlIjoiYXNzZXQ6dmlldyIsInRpbWVzdGFtcCI6IjE3ODk1ODY5MDcifQ:mozilla:a-PDXI-5NSLURC0D3TH5s7tXIbYF-J5qsvLyvdX7lQo"/></p>



<p>Because Mozilla uses a community-based approach to create world-class open source software, we wanted Firefox’s audio logo to share this same spirit. This meant creating something built by many and rooted in real human experience.<br/><br/>Inspired by early community feedback that associated Firefox with nature, we started with delicate organic textures, including bird song and the thump of wood being struck to evoke the feeling of Kit moving through different environments. <br/><br/>We also knew we wanted to utilize the voices of real Mozilla employees, or “Mozillians.” As Sounds Like These Co-founder Sam Heath reflected, “What better way to represent the brand than the sound of the people behind it?”<br/><br/>At first, we considered setting up a professional recording session in a large city where multiple Mozillians could drop in to be recorded. However, we quickly realized this would limit the voices we would be able to include to one geographic location. It was then suggested: Why not just let people record wherever they are? After all, Firefox is used in family living rooms, shared offices, and really most places one can access the internet.<br/><br/>The final result includes the voices of 23 real Mozillians saying “Firefox!”, in which you can hear their subtle differences in accent, tone, and timing. Sam shared that some of these employee submissions included the echoes of distant chatter, families, and all the other subtle sounds of Mozillians’ real life playing out as they recorded. He explained that Sounds Like These did not deliberately edit out the entirety of this ambient sound to preserve the texture and authenticity that comes from real people living their real lives.<br/><br/>“That was something that was very clear from Mozilla from the start. We don’t want to be this shiny, distracting tech brand. We wanted this to feel real, natural, and human,” said Sam.</p>



<h3><strong>The Kit sound: Friendly, familiar, and uniquely Firefox</strong></h3>



<figure class="wp-block-video"><video controls="controls" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/09/Firefox-Sound-Hero1.mp4"/></figure>



<p/>



<p>Kit holds the prestigious title of VP of Mascoting at Firefox, and we worked hard to ensure their sound properly reflects such an important position. <br/><br/>Kit’s not an AI assistant, nor a chatbot. They’re not an actual fox, or a red panda either. They’re a Firefox, its own creature not of this world. Kit may appear in your Firefox browser during moments that are meant to feel welcoming and encouraging, like when you’re getting started, trying out a new feature, or successfully making a settings change. <br/><br/>Our goal when creating the Kit sound was to convey Kit’s friendly, familiar, and trustworthy presence without mimicking any real animal. The sound had to be flexible enough to express movement and emotion across animations and videos, while also remaining instantly recognizable.<br/><br/>Early experiments ranged from pure animal sounds to abstract musical expressions. Foxes were considered, but as Sam noted, “Foxes are incredibly difficult to record, and they do make cute sounds, but never around people. You only really seem to hear them literally screaming – and we definitely didn’t want anyone screaming.”<br/><br/>We also explored a more feline route, specifically a cat purr. As Oli Slack, Co-Founder and Head of Audio at Sounds Like These, explains, “The cat purr was almost kind of perfect…other than the fact that it sounded just like a cat purring. So we asked, ‘How do we recreate the feeling of what the purr sounds like, without it being an actual cat purr?’”<br/><br/>This is where the process really got interesting. While brainstorming cat purr alternatives, the Sounds Like These team researched the psychology behind what makes certain sounds more comforting and familiar. Soft tones and warmth from other humans instinctively register as more reassuring and honest, and this also crosses over into animals, particularly animals we keep as companions. This validated our initial draw toward the cat purr, and confirmed we were heading in the right direction sonically.<br/><br/>The breakthrough came when Sounds Like These stopped looking at animal sounds as a starting point, instead using a human voice as the basis of a custom purr. This wasn’t someone imitating a cat or “purring” themselves, it served as a foundation vocalization that was then uniquely shaped and layered to convey Kit’s friendly and encouraging presence. And thus, the Kit sound was born.</p>



<h3><strong>The notification sound: A gentle whoosh of helpfulness, coming soon to Firefox</strong></h3>



<figure class="wp-block-video"><video controls="controls" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/09/Firefox-Notification-Sound-1.mp4"/></figure>



<p/>



<p>Notifications don’t have to be jarring or intrusive, and that’s exactly what we wanted to avoid when creating one for Firefox.<br/><br/>Our new notification sound – which we look forward to rolling out in a future Firefox update –  was carefully crafted to gently alert, not interrupt. It draws inspiration from community feedback that described the feeling of using Firefox like a door opening and referenced moments of quiet discovery filled with gentle wonderment and joy.<br/><br/>This sense of seamless exploration is reflected in the sound’s design: a soft whoosh, like a door swinging open, followed by a subtle click, all in an airy, rounded tone to feel helpful, not demanding.<br/><br/>The result is a sound that softly notifies rather than disrupts or controls, staying true to the feeling of joyful curiosity that many users associate with browsing the web through Firefox.</p>



<h3><strong>A family of sounds shaped by community</strong></h3>



<p>From the very beginning of this process, we leaned into Mozilla’s values of openness and community.<br/><br/>We consulted our fans and team members. We used real voices. We embraced the imperfections of being human.<br/><br/>These sounds are now a part of Firefox’s story, and we hope every time you hear them, they remind you that you’re using a browser built by the people, for the people.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/new-firefox-sounds/">What does the (Fire)fox say?</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-15T16:00:00Z</updated>
    <published>2026-10-15T16:00:00Z</published>
    <category term="Firefox"/>
    <category term="export"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149814</id>
    <link href="https://discourse.mozilla.org/t/mozphab-2-22-1-released/149814" rel="alternate" type="text/html"/>
    <title>MozPhab 2.22.1 Released</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Bugs resolved in Moz-Phab 2.22.1:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/2078299">bug 2078299</a> Allow overriding base url and repo call sign for development purposes</li>
</ul>
<p>Discuss these changes in <span class="hashtag-raw">#engineering-workflow</span> on Slack or <span class="hashtag-raw">#Conduit</span> Matrix.</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/mozphab-2-22-1-released/149814">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-15T03:01:57Z</updated>
    <published>2026-10-15T03:01:57Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>sheehan</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/mozphab-2-22-1-released/149814.rss" title="MozPhab 2.22.1 Released"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149813</id>
    <link href="https://discourse.mozilla.org/t/mozphab-2-22-0-released/149813" rel="alternate" type="text/html"/>
    <title>MozPhab 2.22.0 Released</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Bugs resolved in Moz-Phab 2.22.0:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/1501077">bug 1501077</a> moz-phab does not update the reviewers list in Phabricator to match local changes</li>
<li><a href="https://bugzilla.mozilla.org/2074122">bug 2074122</a> moz-phab --apply-to here --no-branch changed my tree and branch without prompting</li>
<li><a href="https://bugzilla.mozilla.org/2077318">bug 2077318</a> moz-phab should block submitting patches that still contain conflict markers</li>
<li><a href="https://bugzilla.mozilla.org/2078249">bug 2078249</a> use threading.Event().wait() rather than time.sleep() in moz-phab spinner/wait message</li>
<li><a href="https://bugzilla.mozilla.org/2078366">bug 2078366</a> AttributeError fetching revision with Jujutsu</li>
<li><a href="https://bugzilla.mozilla.org/2079200">bug 2079200</a> Moz-phab patch doesn’t commit new files when not automatically tracked by jujutsu</li>
<li><a href="https://bugzilla.mozilla.org/2082222">bug 2082222</a> Fix some formatting issues after Bug 2074122</li>
</ul>
<p>Discuss these changes in <span class="hashtag-raw">#engineering-workflow</span> on Slack or <span class="hashtag-raw">#Conduit</span> Matrix.</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/mozphab-2-22-0-released/149813">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-15T02:13:28Z</updated>
    <published>2026-10-15T02:13:28Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>sheehan</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/mozphab-2-22-0-released/149813.rss" title="MozPhab 2.22.0 Released"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>https://blog.rust-lang.org/2026/10/15/Rust-1.99.1/</id>
    <link href="https://blog.rust-lang.org/2026/10/15/Rust-1.99.1/" rel="alternate" title="Announcing Rust 1.99.1" type="text/html"/>
    <title xml:lang="en">Announcing Rust 1.99.1</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><p>The Rust team has published a new point release of Rust, 1.99.1. Rust is a programming language that is empowering everyone to build reliable and efficient software.</p>
<p>If you have a previous version of Rust installed via rustup, getting Rust 1.99.1 is as easy as:</p>
<pre class="giallo z-l-code z-d-code"><code><span class="giallo-l"><span>rustup update stable</span></span></code></pre>
<p>If you don't have it already, you can <a href="https://www.rust-lang.org/install.html" rel="external">get <code>rustup</code></a> from the appropriate page on our website.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/15/Rust-1.99.1/#what-s-in-1-99-1"/>
What's in 1.99.1</h3>
<p>Rust 1.99.1 fixes the following regressions from prior releases:</p>
<ul>
<li>
<p><a href="https://github.com/rust-lang/rust/issues/163614" rel="external">Missing symbol <code>wcslen</code></a>: Some Rust targets were getting link errors for missing <code>wcslen</code>, and that function is now present in Rust's compiler-builtins library as a fallback.</p>
<p>The LLVM <code>loop-idiom-wcslen</code> pass may introduce calls to <code>wcslen</code> as an optimization, and some Rust targets did not have that function readily available in <code>libc</code> or elsewhere. The UEFI targets in particular were broken for any project using <code>std</code>, as some of these calls were introduced in the precompiled standard library, but the issue was also reproducible for similar user code patterns.</p>
</li>
<li>
<p><a href="https://github.com/rust-lang/rust/issues/163911" rel="external">Miscompilation of FFI <code>bool</code> return values on x86_64</a>: Rust functions returning <code>bool</code> through FFI could leave bits 1-7 of the return register unspecified, causing callers to observe raw values other than <code>0</code> or <code>1</code>. This return type is now marked for zero-extension again, as required by the ABI.</p>
</li>
<li>
<p><a href="https://github.com/rust-lang/rust/issues/163947" rel="external"><code>rust-lld</code> failed to load <code>libLLVM</code> on macOS</a>: This linker could fail to run if the compiler was invoked without the <code>rustup</code> proxy, as there was no direct setting for the appropriate library search path. Now <code>rust-lld</code> is built with an <code>rpath</code> entry for the directory containing <code>libLLVM.dylib</code>.</p>
</li>
</ul>
<p>If you'd like to help us out by testing future releases, you might consider using the beta (<code>rustup default beta</code>) and nightly (<code>rustup default nightly</code>) channels locally and in your CI. Please <a href="https://github.com/rust-lang/rust/issues/new/choose" rel="external">report</a> any bugs you might come across!</p>
<h4><a class="anchor" href="https://blog.rust-lang.org/2026/10/15/Rust-1.99.1/#contributors-to-1-99-1"/>
Contributors to 1.99.1</h4>
<p>Many people came together to create Rust 1.99.1. We couldn't have done it without all of you. <a href="https://thanks.rust-lang.org/rust/1.99.1/" rel="external">Thanks!</a></p></div>
    </content>
    <updated>2026-10-15T00:00:00Z</updated>
    <published>2026-10-15T00:00:00Z</published>
    <author>
      <name>The Rust Release Team</name>
    </author>
    <source>
      <id>https://blog.rust-lang.org/</id>
      <author>
        <name>Maintained by the Rust Teams.</name>
        <uri>https://github.com/rust-lang/blog.rust-lang.org/</uri>
      </author>
      <link href="https://blog.rust-lang.org/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://blog.rust-lang.org/" rel="alternate" type="text/html"/>
      <subtitle xml:lang="en">Empowering everyone to build reliable and efficient software.</subtitle>
      <title xml:lang="en">Rust Blog</title>
      <updated>2026-11-13T09:01:38Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>https://smallcultfollowing.com/babysteps/blog/2026/10/14/agentic-dev-and-rust/</id>
    <link href="https://smallcultfollowing.com/babysteps/blog/2026/10/14/agentic-dev-and-rust/?utm_source=atom_feed" rel="alternate" type="text/html"/>
    <title xml:lang="en-us">What agents mean for Rust (and vice versa)</title>
    <content type="xhtml" xml:lang="en-us"><div xmlns="http://www.w3.org/1999/xhtml"><figure class="float-figure float-right">
  <img alt="Sheldon breathing into a paper bag." src="https://smallcultfollowing.com/babysteps/ assets/2026-10-14-agentic-dev-and-rust/sheldon.gif"/>
  <figcaption>Me, calmly assessing the implications of LLMs for programming language design(ers).</figcaption>
</figure>
<p>As someone who has made a career of programming language design, I definitely have moments of existential dread about the rise of LLMs. I started coding in 5th grade on an x86<sup id="fnref:1"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:1">1</a></sup> that ran at 5MHz, had something like a 5MB hard-disk and 512K of RAM<sup id="fnref:2"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:2">2</a></sup>. Computers were really, really different back then. But honestly, programming wasn’t. For all the advances in IDEs and programming languages and so forth, the basic act of entering code into a file has remained surprisingly constant<sup id="fnref:3"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:3">3</a></sup> – right up until a few years ago, when everything kinda turned on its head. That’s been exciting and empowering at times<sup id="fnref:4"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:4">4</a></sup> but also scary and disorienting. <em>Will my skills in programming matter? What about my skills in programming language <strong>design</strong> (such as they are)?</em> This blog post is my attempt to answer those questions.</p>
<p>So as not to keep you in suspense, let me just give you the conclusion. In short, <strong>yes, I believe there will still be a role for humans in programming</strong>. And <strong>yes, I think that programming language design is still relevant</strong>. And, naturally, I also happen to think Rust is a <strong>really good fit</strong> for agentic development – but that’s not to say we can’t make it a <strong>better fit</strong>. And that’s what this post is ultimately about: what makes Rust and agentic development work well, and where we could double down on those strengths.</p>
<blockquote>
<p><em>This is a kind of “blog post companion version” of a <a href="https://1drv.ms/p/c/fc6238e2c825ad8e/IQAicCGAOWyUSoas_zx8h6FwAX4K-qU23eeypjxQwXlNBF4?e=BkH84j">talk I gave this week at REBASE, part of SPLASH</a>. You might also enjoy the slides from the talk I gave at IWACO, <a href="https://1drv.ms/p/c/fc6238e2c825ad8e/IQAyyfEu4SdnSaW2Qnlc82wCATs6-S3dGrni0DB3NjpNrkQ?e=rOLmkW">IWACO and Rust: hidden links revealed</a>, which was a bit more of a retrospective (no soundtrack for those, though). In any case, this turned out to be a great conference! <a href="https://conf.researchr.org/profile/splash-issta-2026/jackhuey">Jack Huey presented on the Rust Vision Doc</a> and, quite to my surprise, Steve Klabnik and Dorian Scheidt presented <a href="https://conf.researchr.org/details/splash-issta-2026/plss-2026/7/LLMs-as-Collaborators-in-Language-Specification-and-Design">“LLMs as Collaborators in Language Specification and Design”</a>, talking about their process in building out <a href="https://steveklabnik.com/writing/thirteen-years-of-rust-and-the-birth-of-rue/">Rue</a>. It was fun to see Steve again. On top of that, there was a ton of great research presented at IWACO in particular. I was particularly taken by the work on <a href="https://dl.acm.org/doi/10.1145/3485516">Reachability Types</a> and <a href="https://conf.researchr.org/home/splash-issta-2026/iwaco-2026#program">Information Borrowing</a>. I also really liked learning about <a href="https://hylo-lang.org/">Hylo Lang</a>, particularly their approach to projections. Clever and cool.</em></p>
</blockquote>
<h3>Rust is popular in the agentic era</h3>
<figure class="float-figure float-right">
  <img alt="Meme dialogue: &#x201C;I wrote this in Rust!&#x201D; &#x201C;Be honest.&#x201D; &#x201C;I am being honest!&#x201D; &#x201C;An agent wrote it.&#x201D; &#x201C;Thank you.&#x201D;" src="https://smallcultfollowing.com/babysteps/ assets/2026-10-14-agentic-dev-and-rust/be-honest.png"/>
  <figcaption>From the most important Slack channel at Amazon, #aws-memes.</figcaption>
</figure>
<p>Rust is popular right now. <a href="https://x-thread.org/t/2087229652293337160">Very popular:</a></p>
<blockquote>
<p>Stratospheric among the breakout languages is TypeScript, cropped from the chart and sitting currently at +1200% growth from the prior year. [..]</p>
<p>The second most rapid recent growth is in Rust. <strong>Meta engineers have written twice as much first-party Rust code so far this year than in the previous 9 years combined.</strong></p>
<p>—  David Tolnay (emphasis mine)</p>
</blockquote>
<p>Some of that is because agents make it very easy to try out new things. And some of that is because Rust has a reputation for being performant and, if it’s just as easy to pick any language, why not pick one that will yield faster execution times?</p>
<p><strong>But I think Rust is popular for another reason: because Rust happens to be a really good fit for agentic coding</strong><sup id="fnref:6"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:6">6</a></sup>. Of course, I would, wouldn’t I? The point of this post is (1) to argue for why that is and then (2) to discuss what we might change about Rust to make it work even better.</p>
<h3>Foundational Software construction with agents</h3>
<p>It seems to me that an effective “software factory” will have three pillars:</p>
<ul>
<li><em>Design:</em> figure out and specify clearly what the code is supposed to do.</li>
<li><em>Construction:</em> author code that does what it is supposed to do.</li>
<li><em>Optimization:</em> optimize the code so that it runs efficiently.</li>
</ul>
<p>None of these pillars are solved, but some have made more progress than others.</p>
<h3>Rust and optimization: fast by default, knobs when you need ’em</h3>
<p>Rust is designed to give “good performance by default”, making the idiomatic thing typically also be the fastest thing. But another key part of Rust is that you have the knobs to eke out better performance when you need it. You control when something is stack- or heap-allocated and where pointer indirection occurs. If you want to, you can force the layout of your structs to be done in a particular way, or decide where to introduce boxing into your async stack frames. In the limit, you can put in inline assembly.</p>
<p>In the past, learning how to “tune the performance knobs” could be a bit of a black art: but agents are making that much easier.<sup id="fnref:7"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:7">7</a></sup> It turns out that agents are <em>really good</em> at fine-tuning the performance of existing code. For example, people who work on super high-performance cryptographic algorithms used to do so by hand-tuning assembly code. But those people tell me that they are now turning to agents for that same job. More prosaicly, a lot of people building network services are finding that, using a profiler like <a href="https://github.com/dial9-rs/dial9">dial9</a>, agents can quite effectively diagnose async performance pitfalls, like long polls or blocking.</p>
<p>Therefore, I think the task for Rust is clear. We keep on with our goal of <a href="https://smallcultfollowing.com/babysteps/blog/2025/10/13/ergonomic-explicit-handles/">“low-level enough for a kernel, high level enough for a GUI”</a>. If anything, I think the shift around agents means we can tolerate a bit more “noise” in the form of explicit calls to <code>clone()</code> or <code>share()</code> – but not too much, since we still want the “happy path” of the code to be clear and evident<sup id="fnref:8"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:8">8</a></sup>, even as we surface details that are important in specific scenarios (like tracking precisely how many clones you have of a channel endpoint). Combined with a profiler, you get an effective feedback loop to get your code running fast:</p>
<pre class="mermaid">flowchart LR
    Code -- Benchmark --&gt; Profile
    Profile -- Analyzed by --&gt; Agent
    Agent -- Propose --&gt; PR
    PR -- Improve --&gt; Code
  </pre>
<h3>Reliability is king, as always</h3>
<p>As usual though, while a reputation for good performance is what brings people to Rust, what makes them want to <em>stay</em> is a sense that using Rust “just seems to work better”. The basic theory is that Rust’s type system and guardrails <a href="https://x.com/gdb/status/2007228511363444905">help keep agents on track</a>:</p>
<center>
<blockquote class="twitter-tweet"><p dir="ltr" lang="en">rust is a perfect language for agents, given that if it compiles it's ~correct</p>— Greg Brockman (@gdb) <a href="https://x.com/gdb/status/2007228511363444905?ref_src=twsrc%5Etfw">January 2, 2026</a></blockquote>

</center>
<p>I think there’s truth in that: languages like Rust, Ocaml, or Haskell all share this “if it compiles, it works” feeling, and I think that agents will benefit from that.</p>
<h3>Testing is not enough, type systems help</h3>
<blockquote>
<p><em>Testing can show the presence of bugs, but not their absence.</em></p>
<p>— Edsger W. Dijkstra, 1970</p>
</blockquote>
<figure class="float-figure float-right">
  <img alt="A woman presents a lopsided cake with the words &#x201C;Nailed it!&#x201D;" src="https://smallcultfollowing.com/babysteps/ assets/2026-10-14-agentic-dev-and-rust/nailed-it.gif"/>
  <figcaption>Agents presenting their work.</figcaption>
</figure>
<p>Writing tests has never been enough to show that your program is correct – but, with agents, it’s not even close. It happens so often that my first few tests seem great and then the next one goes completely bonkers. Usually bonkers in a way where I cannot even imagine how that bug could have come about. Then I dig in and I realize the agent completely missed the boat on the logic I was trying to express.<sup id="fnref:9"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:9">9</a></sup></p>
<p>This is where a type systems really shines – particularly an advanced one like Rust. Type systems give you some guardrails that keep the agent on track. In Rust, those guardrails extend beyond simple stuff like “do all fields have the correct names” and to stuff like <a href="https://blog.skylight.io/rust-means-never-having-to-close-a-socket/">never having to close a socket</a>.</p>
<h3>Type systems are not enough either</h3>
<blockquote>
<p><em>Type systems can show the absence of bugs, but not the presence of correctness.</em></p>
<p>— Me, failing to coin a phrase of equal eloquence<sup id="fnref:10"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:10">10</a></sup>, 2026</p>
</blockquote>
<p>So yeah, type systems are helpful! But they have inherent limits. A type system is a simple set of rules that, if you follow them, make sure that you avoid (certain kinds of) mistakes. But they don’t tell you that you do the <em>right</em> thing – only that you <em>don’t</em> do (certain kinds of) <em>wrong things</em>. <strong>If you want to go further, you need a proof system</strong> – something that will let you show that richer properties are actively true, not just that you’re avoiding bugs.</p>
<p>As it happens, there are a lot of interesting proof tools for Rust, like <a href="https://github.com/verus-lang/verus">Verus</a>, <a href="https://creusot.rs/">Creusot</a>, <a href="https://aeneasverif.github.io">Aeneas</a>, and <a href="https://github.com/model-checking/kani">Kani</a>. As a starting point, you can prove that your code is panic-free, which will eliminate a lot of bugs, though it is still fundamentally a “type-checker-like” property (i.e., you avoid doing things wrong). But you can also go further and add assertions that show your code is computing the results you expect.</p>
<h3>Strong guardrails give better performance</h3>
<p>Deplying proofs is not just good for getting code <em>right</em> – it’s good for getting code <em>fast</em>. This is somewhat counterintuitive, but it’s true. Earlier I mentioned how optimized cryptographic algorithms were now being written by <em>agents</em>. Part of what makes that possible is that cryptographic algorithms have a very clear mathematical definition. This means that you can basically tell the agent “do whatever you want, as long as you can prove that the code still computes the correct result”. These proofs can be done with theorem provers like <a href="https://lean-lang.org/">Lean</a> or <a href="https://rocq-prover.org/">Rocq</a>. The blog post <a href="https://kim-em.github.io/blog/2026-7-24-why-lean-is-faster-than-rust/">“Why Lean is faster than Rust”</a> makes the point quite well.</p>
<p>For Rust, a good example of this would be around unsafe code. Right now, people are sometimes reluctant to deploy unsafe code even if it might make their code faster because it’s not worth the risk of getting it wrong. And I applaud that effort. But what if you could use a prover to show that your unsafe code is, in fact, safe (i.e., incapable of causing undefined behavior)? Then you’d be free to optimize to your heart’s content.</p>
<h3>If we are going to prove things, do we need type systems?</h3>
<p>You might wonder: if we’re deploying a proof system on our code, do we still need type systems? I think the answer is definitely yes. Type systems are infinitely simpler to work with, which is why they are much more popular. Using a type system lets you rule out all kinds of annoying bugs so that you can focus your “proof energy” only on the important stuff.</p>
<p>As a simple example of this, consider the following Java code:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-java"><span class="line"><span class="cl"><span class="kt">void</span><span class="w"> </span><span class="nf">setFoo</span><span class="p">(</span><span class="n">Bar</span><span class="w"> </span><span class="n">bar</span><span class="p">)</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="k">this</span><span class="p">.</span><span class="na">foo</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">bar</span><span class="p">;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="k">assert</span><span class="w"> </span><span class="k">this</span><span class="p">.</span><span class="na">foo</span><span class="w"> </span><span class="o">==</span><span class="w"> </span><span class="n">bar</span><span class="p">;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>Without seeing more code, it is impossible to prove whether this assertion is true or not! This is because there could be any number of other threads running around mutating <code>this</code>. In contrast, the following Rust code <em>must</em> be true (at least, so long as the <code>Eq</code> operator is reflexive for <code>Bar</code>):</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">set_foo</span><span class="p">(</span><span class="o">&amp;</span><span class="k">mut</span><span class="w"> </span><span class="bp">self</span><span class="p">,</span><span class="w"> </span><span class="n">bar</span>: <span class="nc">Bar</span><span class="p">)</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="bp">self</span><span class="p">.</span><span class="n">foo</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">bar</span><span class="p">;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="fm">assert_eq!</span><span class="p">(</span><span class="bp">self</span><span class="p">.</span><span class="n">foo</span><span class="p">,</span><span class="w"> </span><span class="n">bar</span><span class="p">);</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>We know this because the <em>type system of Rust</em> guarantees that <code>&amp;mut self</code> implies a <em>unique</em> reference.</p>
<p>This is in fact exactly how Verus works. By trusting the Rust borrow checker to track uniqueness etc, it simplifies the job of the SMT solver, making proof checking must faster and more reliable than it would be otherwise.</p>
<h3>Where I think Rust should go on reliability</h3>
<p>So my take is that Rust should double down on <em>if it compiles, it works</em>. As expressive as Rust’s type system is, there are plenty of things that it cannot capture. This includes fairly common things, like <a href="https://smallcultfollowing.com/babysteps/blog/2026/03/21/view-types-max-min/">this method only reads one particular field</a> or <a href="https://smallcultfollowing.com/babysteps/blog/2024/06/02/the-borrow-checker-within/">internal references</a>, but also fancy things like “no logging of personally identifiable information”. We should work to lift those limits, giving agents room to prove more complex properties.</p>
<p>We also need to improve the experience of integrating a proof tool by working towards an <em>extensible compiler</em>. As cool as the existing Rust-based proof tools are, using them is a janky experience involing annoying macros and pinned compiler versions. We can do better.</p>
<h3>A north star: No more unsafe code</h3>
<p>I’d like to propose a north star for Rust: <strong>no more unsafe code</strong>. By that, I don’t mean that we never use the <code>unsafe</code> <em>keyword</em>. Rather, I mean that we have the power to prove that all the unsafe code we write is correct and cannot cause undefined behavior. Don’t get me wrong: knowing exactly what code needs to be vetted is a huge step forward, as is normalizing the idea that libraries need to be responsible for protecting their users from undefined behavior via safe API boundaries<sup id="fnref:11"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:11">11</a></sup>. But given agents’ ability to find vulnerabilities, I think we need to up-our-game if we want to stop the steady stream of CVEs.<sup id="fnref:12"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:12">12</a></sup></p>
<h3>Design is an open problem</h3>
<p>But before you go about proving things or optimizing them, you need to have a clear idea of what you are building. As far as I can tell the state of the art here is basically variations on “markdown-driven-development”, developing docs and hoping that agents pay attention.</p>
<p>I don’t know how much of a role for Rust there is in this space. I think there are some steps we might wind up taking that could be helpful here – for example, having ways to separate out <em>interface</em> from <em>implementation</em> so that it’s easier to review the interface in isolation or to see when the agent made changes there.<sup id="fnref:13"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:13">13</a></sup> Or perhaps just providing betters tools to review that.</p>
<p>I also think there’s space for dedicated “modeling languages”, something that let you iterate quickly with agents on the high-level designs and invariants without having to get into the weeds and read the code. I have more thoughts on this but it merits many blog posts all of its own. For the moment, I’ll start by pointing you all at this post by Kari Wilhelm, <a href="https://nappingtoheavymetal.com/post/2026-09-15-principles-of-anchor-engineering/">“Principles of Anchor Engineering”</a>, which I think does a nice job of describing what it means to pull out the key elements of a design and drive the coding from there.</p>
<h3>Conclusion</h3>
<p>We covered a lot of ground here, so let me put this all together. What makes Rust a good choice for developing with agents?</p>
<ul>
<li>It offers good default perf (why pay more?) and, in conjunction with a profiler, can be tuned as much as you want.</li>
<li>The type system gives stronger guardrails, and if you setup your agents right, you can strengthen those guardrails through techniques like new types.</li>
</ul>
<p>And what could make it better, from a language design perspective? Overall, I think it’s very similar to what we were doing, except that the way we weight the tradeoffs is tweaked to account for agents doing the code authoring, and humans focused more on code comprehension:</p>
<ul>
<li><em>If it compiles, it works</em> – our type system is our big advantage, we need to make it more expressive and more functional so that agents don’t get stuck trying to work around it!
<ul>
<li>And as an adjunct, establish a North Star: Enable <em>Unsafe code without unsafety</em> by supporting proof, and see the most widely used Rust libraries proven sound.</li>
</ul>
</li>
<li><em>Low-level enough for a kernel, high-level enough for a GUI</em> – make sure we expose the knobs needed to tune for performance, while also making the code’s intent clear (but don’t worry about golfing the code down to an absolute minimum number of characters).</li>
<li><em>Extensible and versatile</em> – one of Rust’s great strengths is that, with macros + our type system, we support DSLs and a wide variety of targets. We need to bring that spirit of extensibility into the compiler so we can target more styles of development (e.g., GPU, deep language interop, etc) and also integrate theorem provers and other tools that require more than just tokens.</li>
</ul>
<p>As a final close, let me point you at this interesting article by Marc Brooker, <a href="https://brooker.co.za/blog/2026/05/18/whats-easy-whats-hard.html">“What’s easy now? What’s hard now?”</a>. He posits that the more it is possible to clearly specify success criteria for a task, the easier it is, and that we may find that tasks we traditionally think of as ‘hard’ (e.g., building out an efficient implementation of a cryptographic algorithm) may soon become automated, whereas tasks that we have thoght of as ’easy’ (e.g., making a unique, compelling website) may become more valued.</p>
<p>Looking at it from a PL point-of-view, I think Marc’s point reinforces my sense that the biggest action is going to come from <em>design languages</em>, things that let you capture the <em>architecture</em> and <em>intended behavior</em> at a very high-level. The goal would be to let humans intuitively specify a design that gets translated into effective guardrails, whether that’s type system checks, lints, or theorems to be proven. Agents would then take on the task of translating the design into code written in a traditional PL like Rust, with humans looking at it only rarely. This doesn’t make the design of traditional PLs less interesting, but it definitely makes the tradeoffs very different than they were before.</p>
<div class="footnotes">
<hr/>
<ol>
<li id="fn:1">
<p>Secretly I have always been jealous of people that coded using punchcards and stored things on gigantic rolls of tape or whatever. I just want to be world weary so badly! I am kinda delighted that I’m finally old enough that I can say things like “I remember when we had to edit CONFIG.SYS before we could play a computer game!” and younger programmers will gasp in horror.<sup id="fnref:5"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:5">5</a></sup> But I still feel like I must sound like a silly kid to folks who were around “back in the day”. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:1">↩︎</a></p>
</li>
<li id="fn:2">
<p>I still remember when my dad told me he had bought me a 10MB disk and <em>secretly</em> he had bought a <strong>40MB</strong> disk to surprise me. It seemed absurdly large. “I’ll never need a new disk again!” <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:2">↩︎</a></p>
</li>
<li id="fn:3">
<p>I mean my god, we’re even using <code>vi</code> again! My first editor! <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:3">↩︎</a></p>
</li>
<li id="fn:4">
<p>I built an electron app! And it was so easy to do! And reading weird papers and things is so much more accessible now that I can ask an LLM to translate all the math jargon for me. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:4">↩︎</a></p>
</li>
<li id="fn:5">
<p>I remember once trying to tell Alex Crichton how I used to “order shareware from a paper catalog by putting a check in the mail” and he was like “I do not understand any of the nouns in that sentence”. Highlight of my life, right after Rust 1.0. Oh, and maybe the birth of my child and getting married. I guess. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:5">↩︎</a></p>
</li>
<li id="fn:6">
<p>I’m not saying Rust is the <em>only</em> language that’s a good fit. I’m not even saying that the way that Rust is a good fit is the only way to be a good fit. I have heard for example that Go is a really good fit for agentic coding and I believe it: I think it hits a different sweet spot, one that helps agents iterate quickly (although I do suspect agents will let data races and subtle bugs slip through that Rust would have prevented). <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:6">↩︎</a></p>
</li>
<li id="fn:7">
<p>The fact that agentic development makes more room for knobs is good for Rust performance, but it is quite likely an even better fit for performance in other languages. Tuning a GC has traditionally been a job that really requires a GC expert, but agents can likely fill that role pretty well these days. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:7">↩︎</a></p>
</li>
<li id="fn:8">
<p>On this pont, I’m even more convinced of the importance of ergonomic RC now that I work with agents. Agents are good at introducing the extra clones and things you need to deal with capturing around async tasks, but the resulting code is so annoying to read, it really hides what’s going on. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:8">↩︎</a></p>
</li>
<li id="fn:9">
<p>“Claude, this is <em>not</em> what we talked about!” – me, all too often. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:9">↩︎</a></p>
</li>
<li id="fn:10">
<p>So close though, right? I just .. couldn’t land the plane. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:10">↩︎</a></p>
</li>
<li id="fn:11">
<p>All too often, C++ libraries consider it adequate to tell users <a href="https://www.wired.com/2010/06/iphone-4-holding-it-wrong/">“you’re holding it wrong”</a> – i.e., that they are responsible for causing undefined behavior by misusing the API. Rust takes a clear position that a safe API has to protect its users, no matter how much they abuse it. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:11">↩︎</a></p>
</li>
<li id="fn:12">
<p>To be fair, if Rust is encountering a stream of CVEs, other languages like C++ and Java are encountering a veritable flood, since they lack the protection of Rust’s type system.
st takes a clear position that a safe API has to protect its users, no matter how much they abuse it. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:12">↩︎</a></p>
</li>
<li id="fn:13">
<p>The revenge of <code>.h</code> files? <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:13">↩︎</a></p>
</li>
</ol>
</div></div>
    </content>
    <updated>2026-10-14T04:19:44Z</updated>
    <published>2026-10-14T00:00:00Z</published>
    <source>
      <id>https://smallcultfollowing.com/babysteps/</id>
      <author>
        <name>Niko Matsakis</name>
        <email>rust@nikomatsakis.com</email>
      </author>
      <link href="https://smallcultfollowing.com/babysteps/" rel="alternate" title="html" type="text/html"/>
      <link href="https://smallcultfollowing.com/babysteps/index.xml" rel="alternate" title="rss" type="application/rss+xml"/>
      <link href="https://smallcultfollowing.com/babysteps/atom.xml" rel="self" title="atom" type="application/atom+xml"/>
      <title xml:lang="en-us">baby steps</title>
      <updated>2026-10-30T10:48:25Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149795</id>
    <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261013-2/149795" rel="alternate" type="text/html"/>
    <title>Happy BMO Push Day! (20261013.2)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://github.com/mozilla-bteam/bmo/tree/release-20261013.2" rel="noopener nofollow ugc">Github Link</a></p>
<p>The following changes have been pushed to <a href="https://bugzilla.mozilla.org">bugzilla.mozilla.org</a>:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2079152">Bug 2079152</a> - Unable to select content-type when creating attachment</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2079453">Bug 2079453</a> - Upgrade devbridge-autocomplete to 2.0.1 and fix autocomplete dropdown reopening after the field loses focus</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2065173">Bug 2065173</a> - Migrate Group REST resource to native Mojo API</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078690">Bug 2078690</a> - Migrate User REST resource to native Mojo API: user objects (get, create, update, suggest, whoami, offer_account_by_email)</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2079991">Bug 2079991</a> - When one update requests needinfo from several users , the webhook’s <code>event.changes</code> has a single <code>flag.needinfo</code> entry for the last requestee only; the others are dropped.</li>
</ul>
<p>Discuss these changes in the <a href="https://matrix.to/#/#bmo:mozilla.org" rel="noopener nofollow ugc">BMO Matrix Room</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261013-2/149795">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-13T22:21:16Z</updated>
    <published>2026-10-13T22:21:16Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>dkl1</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261013-2/149795.rss" title="Happy BMO Push Day! (20261013.2)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://fxdx.dev/?p=568</id>
    <link href="https://fxdx.dev/firefox-webdriver-newsletter-158/" rel="alternate" type="text/html"/>
    <title>Firefox WebDriver Newsletter 158</title>
    <summary>Final Firefox 158 WebDriver newsletter.</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p class="has-primary-color has-background-background-color has-text-color has-background">With the WebDriver related release notes part of the MDN developer release notes and having a 2-week cycle for new Firefox releases now we are going to stop publishing this newsletter. This one will be the last one of the series of blog posts that we did since Firefox 114.<br/><br/>Thank you to everyone who followed these posts and provided feedback over the past releases.</p>



<p id="block-625ec41a-ebba-4559-8294-ab8d43d24728"><em>WebDriver is a remote control interface that enables introspection and control of user agents. As such, it can help developers to verify that their websites are working and performing well with all major browsers. The protocol is standardized by the<a href="https://www.w3.org/"> W3C</a> and consists of two separate specifications:<a href="https://w3c.github.io/webdriver/"> WebDriver classic</a> (HTTP) and the new<a href="https://w3c.github.io/webdriver-bidi/"> WebDriver BiDi</a> (Bi-Directional).</em></p>



<p id="block-dae47e7f-6eed-4378-93bf-87f83964774b"><em>This newsletter gives an overview of the work we’ve done as part of the Firefox 158 release cycle</em>.</p>



<h3>Contributions</h3>



<p id="block-0cd229aa-56a4-4acd-88c9-6c0aed1f91ef">Firefox is an open source project, and we are always happy to receive external code contributions to our WebDriver implementation. We want to give special thanks to everyone who filed issues, bugs, and submitted patches.</p>



<p id="block-90d46142-b130-4359-9a16-b2e82ef91416">In Firefox 158, multiple WebDriver bugs were fixed by contributors:</p>



<ul>
<li>F3tch landed several patches to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2070577">allow setting of camera and microphone permissions</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1492357">reject zero-sized screenshots</a>, add a vendor-specific <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2068045">WebDriver BiDi command for listing installed extensions</a>, and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1917288">update cookie test expirations</a>. </li>



<li>Khalid AlHaddad improved the <a href="https://bugzilla.mozilla.org/attachment.cgi?id=9640463">PollPromise to throw an error by default</a> and not only log a warning when it times out.</li>
</ul>



<p id="block-1dca3827-38c3-478d-a4b2-a1e39af880f5">WebDriver code is written in JavaScript, Python, and Rust, so any web developer can contribute! Read <a href="https://firefox-source-docs.mozilla.org/setup/index.html">how to set up the work environment</a> and check<a href="https://codetribute.mozilla.org/projects/automation"> the list of mentored issues</a> for Marionette or the <a href="https://codetribute.mozilla.org/languages/javascript?project%3DWebDriver%2520BiDi">list of mentored JavaScript bugs for WebDriver BiDi</a>. Join <a href="https://chat.mozilla.org/#/room/#webdriver:mozilla.org">our chatroom</a> if you need any help to get started!</p>



<h3>All Changes</h3>



<p>A complete list of developer-facing changes included in this Firefox release is available in the <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/158#webdriver_conformance_webdriver_bidi_marionette">MDN Firefox 158 Release Notes</a>.</p>



<p/></div>
    </content>
    <updated>2026-10-13T18:02:28Z</updated>
    <published>2026-10-13T18:02:28Z</published>
    <category term="Release Notes"/>
    <category term="Remote Protocols"/>
    <category term="WebDriver BiDi"/>
    <category term="WebDriver Classic"/>
    <author>
      <name>Henrik Skupin</name>
    </author>
    <source>
      <id>https://fxdx.dev</id>
      <logo>https://fxdx.dev/files/2023/04/cropped-Fx-Browser-Developer-icon-fullColor-512-32x32.png</logo>
      <link href="https://fxdx.dev/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://fxdx.dev" rel="alternate" type="text/html"/>
      <subtitle>Your Go-To Resource for Web Development &amp; Compatibility</subtitle>
      <title>Firefox Developer Experience</title>
      <updated>2026-10-13T18:04:41Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149776</id>
    <link href="https://discourse.mozilla.org/t/firefox-profiler-deployment-october-13-2026/149776" rel="alternate" type="text/html"/>
    <title>Firefox Profiler Deployment (October 13, 2026)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>The latest version of the <a href="https://profiler.firefox.com/" rel="noopener nofollow ugc">Firefox Profiler</a> is now live! Check out the full changelog below to see what’s changed:</p>
<p><strong>Highlights:</strong></p>
<ul>
<li>[Markus Stange] Speed up activity graph drawing (<span class="hashtag-raw">#5888</span>)</li>
<li>[Florian Quèze] profiler-cli: accept several marker handles and ranges in marker info (<span class="hashtag-raw">#6277</span>)</li>
<li>[Nazım Can Altınova] Add “profiler-cli profile save ” (<span class="hashtag-raw">#6340</span>)</li>
<li>[Nazım Can Altınova] Add global `–permalink` and `–short-permalink` flags to profiler-cli (<span class="hashtag-raw">#6338</span>)</li>
<li>[Markus Stange] Serve production build by default during local development (<span class="hashtag-raw">#6353</span>)</li>
<li>[Nazım Can Altınova] Add global `–permalink` and `–short-permalink` flags to profiler-cli (<span class="hashtag-raw">#6338</span>)</li>
<li>[Nazım Can Altınova] Add the ability to apply source maps to the profiles using `profiler-edit` (<span class="hashtag-raw">#6382</span>)</li>
</ul>
<p><strong>Other Changes:</strong></p>
<ul>
<li>[Nazım Can Altınova] Fix the upload progress bar not showing in light mode (<span class="hashtag-raw">#6348</span>)</li>
<li>[Nazım Can Altınova] Fix the variable name passed to the malformed response error strings (<span class="hashtag-raw">#6351</span>)</li>
<li>[Markus Stange] Add missing await when calling Chrome importer (<span class="hashtag-raw">#6346</span>)</li>
<li>[Markus Stange] Use “falls through” for all fallthrough comments (<span class="hashtag-raw">#6344</span>)</li>
<li>[Markus Stange] Move source map related profile logic files into profile-logic/source-maps/ (<span class="hashtag-raw">#6349</span>)</li>
<li>[Markus Stange] Make the source view actually read-only. (<span class="hashtag-raw">#6313</span>)</li>
<li>[Markus Stange] Run CI on merge queue branches (<span class="hashtag-raw">#6352</span>)</li>
<li>[Nazım Can Altınova] Fix “… was not wrapped in act” warnings in tests (<span class="hashtag-raw">#6362</span>)</li>
<li>[Nazım Can Altınova] Add a scope tree test for shorthand destructuring defaults (<span class="hashtag-raw">#6367</span>)</li>
<li>[fatadel] Accept --session before subcommands in profiler-cli (<span class="hashtag-raw">#6358</span>)</li>
<li>[Nazım Can Altınova] Replace the deprecated loose option with Babel assumptions (<span class="hashtag-raw">#6366</span>)</li>
<li>[fatadel] Clarify how to save profiles for later access (<span class="hashtag-raw">#6355</span>)</li>
<li>[Nazım Can Altınova] Make `yarn test-cli` and `yarn test-all` faster (<span class="hashtag-raw">#6369</span>)</li>
<li>[Nazım Can Altınova] Use a profile with tab information in the tab selector URL tests (<span class="hashtag-raw">#6370</span>)</li>
<li>[fatadel] Move FileIO table labels into the Gecko profile upgrader (<span class="hashtag-raw">#6375</span>)</li>
<li>[fatadel] Clear preview selections when zooming out in the CLI (<span class="hashtag-raw">#6380</span>)</li>
<li>[fatadel] <img alt=":clockwise_vertical_arrows:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/clockwise_vertical_arrows.png?v=15" title=":clockwise_vertical_arrows:" width="20"/> Sync: l10n → main (October 13, 2026) (<span class="hashtag-raw">#6389</span>)</li>
</ul>
<p>Big thanks to our amazing localizers for making this release possible:</p>
<ul>
<li>de: Ralf Duehnfahr</li>
<li>el: Jim Spentzos</li>
<li>en-GB: Ian Neal</li>
<li>es-CL: ravmn</li>
<li>fr: Théo Chevalier</li>
<li>fy-NL: Fjoerfoks</li>
<li>ia: Melo46</li>
<li>it: Francesco Lodolo</li>
<li>nl: Fjoerfoks</li>
<li>ro: IulianArian</li>
<li>ro: robbp</li>
<li>ru: Valery Ledovskoy</li>
<li>sv-SE: Andreas Pettersson</li>
<li>tr: Selim Şumlu</li>
<li>tr: Sena nur</li>
<li>zh-TW: Pin-guang Chen</li>
</ul>
<p>Find out more about the Firefox Profiler on <a href="https://profiler.firefox.com" rel="noopener nofollow ugc">profiler.firefox.com</a>! If you have any questions, join the discussion on our <a href="https://chat.mozilla.org/#/room/#profiler:mozilla.org" rel="noopener nofollow ugc">Matrix channel</a>!</p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/firefox-profiler-deployment-october-13-2026/149776">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-13T15:10:11Z</updated>
    <published>2026-10-13T15:10:11Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>fatadel</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/firefox-profiler-deployment-october-13-2026/149776.rss" title="Firefox Profiler Deployment (October 13, 2026)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=87828</id>
    <link href="https://blog.mozilla.org/en/firefox/introducing-firefox-enterprise/" rel="alternate" type="text/html"/>
    <link href="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Enterprise-Product-Video.mp4" length="4124132" rel="enclosure" type="video/mp4"/>
    <title>Mozilla introduces Firefox Enterprise</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Institutions are recalculating who controls the technology they rely on. Mozilla has an independent option to offer. For years, organizations consolidated technology around a small number of providers to make things simpler. Fewer systems. Tighter integrations. More economies of scale. But that consolidation went well beyond technology. It consolidated dependency, too. The resulting risks have […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/introducing-firefox-enterprise/">Mozilla introduces Firefox Enterprise</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><figure class="wp-block-image size-large"><img alt="" class="wp-image-88257" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Enterprise-Distilled-Thumbnail1-1-1024x576.png" width="1024"/></figure>



<p><em>Institutions are recalculating who controls the technology they rely on. Mozilla has an independent option to offer.</em></p>



<p>For years, organizations consolidated technology around a small number of providers to make things simpler. Fewer systems. Tighter integrations. More economies of scale. But that consolidation went well beyond technology. It consolidated dependency, too. The resulting risks have been debated, studied, and challenged along the way, but concentration continued. More work, data and critical infrastructure kept moving to the same few providers, while credible alternatives narrowed.<br/><br/>The deeper that dependency runs, the harder and more costly it becomes to change course. When something fails, changes or falls outside an institution’s control, that dependency becomes a risk for CIOs and CISOs to manage.</p>



<p>Nowhere are these stakes more visible than in Europe. Now institutions are re-assessing. Governments are pushing for greater digital autonomy, while regulated industries face growing pressure to find and manage their dependencies. </p>



<p>There’s a name for much of this debate about technological control: “sovereignty.” </p>



<p>What digital sovereignty means in practice varies. Across Europe, governments are investing in the security and resilience of critical IT infrastructure, reducing strategic dependencies and putting technological autonomy higher on national agendas. Different approaches, same underlying concern. Strip away the regional policy definitions and industry distinctions and a pretty practical, universal question emerges: how much technological dependency should we risk?</p>



<p>And a very specific, very important layer has been largely missing from that conversation: the browser.</p>



<h3>The overlooked layer of modern business</h3>



<p>The browser. Applications run there. Employees authenticate in it. Sensitive data transits through it. Files are uploaded and downloaded and AI tools are increasingly used through it. That raises the same questions of dependency and control: whose browser technology are you relying on, and who controls the infrastructure used to manage it?</p>



<h3>Introducing Firefox Enterprise</h3>


<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img alt="" class="wp-image-88304" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Data-Control-Hero1-1024x576.png" style="width: 696px; height: auto;" width="1024"/></figure></div>


<p><a href="https://www.firefox.com/enterprise/">Firefox Enterprise</a> is built for organizations with strict security, governance, and compliance requirements. It pairs the Firefox browser, built on Mozilla’s independent <a href="https://blog.mozilla.org/netpolicy/2026/03/23/competition-innovation-and-the-future-of-the-web/">Gecko</a> engine, with a management console organizations can run on their own infrastructure. From that console, IT teams can centrally manage browser policy and access, govern how data moves through the browser and set controls around AI use.</p>



<p>IT and security teams get more control over their data, IT infrastructure and browser environment — helping strengthen technological independence and operational resilience.</p>



<p>“If all your options are built with the same technology underneath, ‘choice’ is a lie. So is control,” said Anthony Enzor-DeMeo, CEO of Mozilla. “We built Firefox differently. And we’re bringing its independent architecture to institutions that are ready to rethink their dependencies and risk.”</p>



<h3>Bringing the browser under control</h3>



<p/>



<figure class="wp-block-video"><video controls="controls" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Enterprise-Product-Video.mp4"/></figure>



<p/>



<p>We’re starting with the browser because we see it as a key, but under-governed, layer. Firefox Enterprise gives institutions more control over the browser and the infrastructure managing it.</p>



<p>And because Firefox runs on Gecko, the only major browser engine developed outside Google and Apple, institutions have another path towards reducing dependence on a single architecture.</p>



<p>Finally, Firefox Enterprise is built to live alongside the systems that IT operations already use. Keep your identity provider. Keep your SIEM. Keep your MDM. Just add a browser whose management infrastructure you operate, so you decide where data lives and have greater visibility into how it moves.</p>



<p>For us, supporting the goal of technological sovereignty comes down to four things: More control. More transparency. More choice. More resilience.</p>



<p><a href="https://www.firefox.com/enterprise/firefox-enterprise/">Learn more</a> about Firefox Enterprise.</p>



<h3>A big bet on familiar ground</h3>



<p>We know this territory. Independence isn’t a new direction for Mozilla. We’ve spent more than 25 years building and securing browser technology that intentionally works outside of the dominant architecture of the day. Firefox is used by roughly 200 million people every month and is already deployed across thousands of organizations.<br/><br/>That independence has always mattered to the web. Now it has practical value for institutions looking to reduce technological concentration — and dependency — in their own environments. </p>



<h3>This is the beginning</h3>



<p>Our ambition is big but simple: make technology independence practical.</p>



<p>That means putting institutions in real control of the infrastructure and data they depend on, without asking them to rebuild or start over. Closing blind spots. Defining where policies, access and data live. Keeping core management within the institution’s environment. And bringing an overlooked layer — the browser — under institutional control. </p>



<p>Firefox Enterprise is unveiling across Europe with an initial sales focus on France, Germany, Austria and Switzerland, with more markets to follow. Thunderbird Enterprise is also in development, extending this customer-controlled approach to email and communications. We’ll have more to share as that work progresses.</p>



<p>If your organization wants greater control over its browser infrastructure, we’d like to <a href="https://www.firefox.com/enterprise/contact/">work with you</a>.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/introducing-firefox-enterprise/">Mozilla introduces Firefox Enterprise</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-13T04:01:00Z</updated>
    <published>2026-10-13T04:01:00Z</published>
    <category term="Firefox"/>
    <category term="export"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>https://smallcultfollowing.com/babysteps/blog/2026/10/10/modular-vs-external-proofs/</id>
    <link href="https://smallcultfollowing.com/babysteps/blog/2026/10/10/modular-vs-external-proofs/?utm_source=atom_feed" rel="alternate" type="text/html"/>
    <title xml:lang="en-us">Why 'externalized' proofs of cyclic trait impls does not work</title>
    <content type="xhtml" xml:lang="en-us"><div xmlns="http://www.w3.org/1999/xhtml"><p>For this post, I wanted to talk about two different approaches to handling supertraits. I’m calling them <em>modular</em> proofs vs <em>external</em> proofs. The key idea of this post is that, if we want to have cyclic trait impls, we really need to use a <em>modular</em> proof strategy, where the impl establishes all supertraits hold. Previously we had considered an <em>external</em> strategy, where the piece of code <em>using</em> the impl has the obligation to prove the supertraits hold. Modular proofs always seemed better but I did not think they were workable in the past. But I have become convinced that external proofs are incompatible with Rust as designed, and hence modular proofs are really the only option<sup id="fnref:1"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:1">1</a></sup>. This post dives into that reasoning, and also gives a bit of explanation of what I mean by proofs in the first place.</p>
<h3>Traits and supertraits</h3>
<p>So what do I mean by <em>modular</em> vs <em>external</em> proofs? Well, it all comes down to <strong>who is responsible for proving that supertrait obligations hold</strong>. Consider a trait like <code>Magic</code>:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">trait</span><span class="w"> </span><span class="n">Magic</span>: <span class="nb">Copy</span> <span class="p">{</span><span class="w"> </span><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>The supertrait declaration means that, whenever <code>X: Magic</code> for some type <code>X</code>, it should be true that <code>X: Copy</code>. We make use of this in generic functions:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">is_copy</span><span class="o">&lt;</span><span class="n">T</span>: <span class="nb">Copy</span><span class="o">&gt;</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">is_magic</span><span class="o">&lt;</span><span class="n">T</span>: <span class="nc">Magic</span><span class="o">&gt;</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// Legal, because `T: Magic` implies `T: Copy`
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="n">is_copy</span>::<span class="o">&lt;</span><span class="n">T</span><span class="o">&gt;</span><span class="p">();</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>The trick is that the compiler has to make sure that this implication holds – i.e., for every type <code>X</code> that implements <code>Magic</code>, <code>X</code> also implements <code>Copy</code>. So how does it do it?</p>
<h3>Modular proofs: the impl must show supertraits hold</h3>
<p>The obvious answer is to make proving supertraits part of deciding whether an impl is valid. For any impl of <code>Magic</code>, we can require that the <code>Copy</code> supertrait holds. So an impl like this would be illegal:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="c1">// In a modular system, this impl is *illegal*
</span></span></span><span class="line"><span class="cl"><span class="k">impl</span><span class="w"> </span><span class="n">Magic</span><span class="w"> </span><span class="k">for</span><span class="w"> </span><span class="nb">String</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>This impl is illegal because it would require that <code>String: Copy</code>, and that does not hold. Seems good.</p>
<h3>Modular proofs are a bit tricky</h3>
<p>I am calling these proofs <em>modular</em> because the idea is that we can prove an entire program is valid by proving each part of it separately. In “programming language” theory, this is typically called a “modular” check, as it works by breaking up the entire program into modules that can be independently checked.</p>
<p>The idea with a <em>modular proof</em> is that we can <em>trust impls to show that the supertrait relationships hold</em>, we don’t have to go and re-prove them over and over. If the impl is wrong, the impl will be invalid, but our code is fine. So if we have <code>impl Magic for String</code>, that implies the rest of the program can prove that <code>String: Magic</code>:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">string_is_magic</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// Legal, because there is an impl for `String: Magic`:
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="n">is_magic</span>::<span class="o">&lt;</span><span class="nb">String</span><span class="o">&gt;</span><span class="p">();</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>In fact, since we know that <code>Magic</code> implies <code>Copy</code>, the rest of the program can even rely on <code>impl Magic for String</code> to conclude that <code>String: Copy</code>:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">string_is_copy</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// Legal, because there is an impl for `String: Magic`,
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// and `Magic` implies `Copy`:
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="n">is_copy</span>::<span class="o">&lt;</span><span class="nb">String</span><span class="o">&gt;</span><span class="p">();</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>So long as <code>impl Magic for String</code> is invalid, none of this poses a problem to soundness, since the program overall doesn’t type-check.</p>
<h3>Comparison with functions</h3>
<p>An easy way to understand the idea of modular checks is to think of functions. Imagine you have a function like this one:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">compute_sum</span><span class="p">(</span><span class="n">a</span>: <span class="kt">i32</span><span class="p">,</span><span class="w"> </span><span class="n">b</span>: <span class="kt">i32</span><span class="p">)</span><span class="w"> </span>-&gt; <span class="kt">i32</span> <span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="fm">format!</span><span class="p">(</span><span class="s">"</span><span class="si">{a}</span><span class="s"> + </span><span class="si">{b}</span><span class="s">"</span><span class="p">)</span><span class="w"> </span><span class="c1">// &lt;-- Error
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>Clearly, this function is not legal. It takes two integers and promises to return a third integer, but in fact it returns a <code>String</code>. So the function is illegal. But if you have a call to that function from elsewhere, we consider that other call to be legal:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">use_sum</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="kd">let</span><span class="w"> </span><span class="n">c</span>: <span class="kt">i32</span> <span class="o">=</span><span class="w"> </span><span class="n">compute_sum</span><span class="p">(</span><span class="mi">2</span><span class="p">,</span><span class="w"> </span><span class="mi">20</span><span class="p">);</span><span class="w"> </span><span class="c1">// OK
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>Here, <code>use_sum</code> is relying on <code>compute_sum</code> to obey its contract. It’s not the job of <code>use_sum</code> to check that, it can just assume it is true.</p>
<h3>The catch: how do we decide the impl is invalid</h3>
<p>There is a bit of a catch though. How do we decide if the impl is invalid? The basic idea was that <code>impl Magic for String</code> would have to prove that <code>String: Copy</code>. But we just saw that it could, in fact, do that <em>by using itself</em>. In other words, if we aren’t careful, we can provide a proof that <code>String: Copy</code> like…</p>
<ul>
<li><code>String: Copy</code> because <code>Magic</code> implies <code>Copy</code> and
<ul>
<li><code>String: Magic</code> because <code>impl Magic for String</code> exists</li>
</ul>
</li>
</ul>
<p>and then we would (incorrectly) conclude that the impl is valid. So clearly we need to do something to rule that out. <strong>We need a rule that says, when we are proving that an impl is valid, that proof cannot recursively rely on the impl itself.</strong>[^termination] I’ll come back in a future post to ways we might do that, but for now, I want to explore another alternative.</p>
<h3>External proofs: the user of the impl must show supertraits hold</h3>
<p>When we first looked at this problem, way back in 2018 or so, we thought of another approach. What if we said that an <code>impl</code> is <em>not</em> responsible for proving supertraits. Instead, the idea would be that <code>impl Magic for String</code> is not enough to say that <code>String: Magic</code>. It only says that <code>Shallow(String: Magic)</code> – i.e., <code>String</code> implements <code>Magic</code> in a <em>shallow</em> way, but not in a <em>deep</em> way that includes the full supertraits. <strong>To prove
that <code>String: Magic</code>, we have to show that <code>Shallow(String: Magic)</code> <em>and</em> <code>Shallow(String: Copy)</code>:</strong><sup id="fnref:2"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:2">2</a></sup></p>
<pre tabindex="0"><code>Shallow(String: Magic)
Shallow(String: Copy)
---------------------------- Magic fully implemented
String: Magic
</code></pre><p>This has the somewhat counterintuitive implication that <code>impl Magic for String</code> is actually <em>legal</em> in an “external proof” approach:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="c1">// In an external system, this impl is LEGAL
</span></span></span><span class="line"><span class="cl"><span class="c1">// (but unusable)
</span></span></span><span class="line"><span class="cl"><span class="k">impl</span><span class="w"> </span><span class="n">Magic</span><span class="w"> </span><span class="k">for</span><span class="w"> </span><span class="nb">String</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>The saving grace is that, while this impl is legal, you can’t actually <strong>use</strong> it. This function for example does not compile:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">string_is_magic</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// NOT legal in an external system:
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// * We can prove that `Shallow(String: Magic)`
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// * We CANNOT prove that `Shallow(String: Copy)`.
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="n">is_magic</span>::<span class="o">&lt;</span><span class="nb">String</span><span class="o">&gt;</span><span class="p">();</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>Here, <code>String: Magic</code> doesn’t hold even though there is an <code>impl</code> of <code>Magic</code> for <code>String</code>, because the caller <em>also</em> has to check that <code>String: Copy</code> is implemented, and it is not. Huh, interesting.</p>
<h3>Comparison to functions: external is awkward</h3>
<p>the “external proof” approach for impls is clearly a bit awkward. If we make the comparison to functions, it’s as if the caller has to double check that the callee’s body matches its return type, it can’t actually <em>trust</em> the declared signature. But, awkward or not, it does resolve our problem: given <code>impl Magic for String</code>, we cannot prove <code>String: Copy</code>, and hence we cannot prove that <code>String: Magic</code>. We can only prove that <code>Shallow(Magic: String)</code>, which doesn’t imply that the supertraits hold.</p>
<h3>But external doesn’t work with unsafe traits</h3>
<p>Based on the above, for a long time, I was working with the assumption that, weird as they are, we would go with the “external proof” approach. However, as Ralf Jung and lcnr pointed out to me recently, this is very challenging to reconcile with unsafe traits. Consider an unsafe trait like <code>Nullable</code>:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="c1">// A type that can be safely transmuted from `0_usize`.
</span></span></span><span class="line"><span class="cl"><span class="k">unsafe</span><span class="w"> </span><span class="k">trait</span><span class="w"> </span><span class="n">NullWord</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>The way that Rust works, when we write an <code>unsafe impl</code>, it is the job of that impl to prove that the unsafe conditions hold. Other parts of the program get to trust the impl. So if I write a function like this one, it should be considered safe:<sup id="fnref:3"><a class="footnote-ref" href="https://smallcultfollowing.com/babysteps/atom.xml#fn:3">3</a></sup></p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">foo</span><span class="o">&lt;</span><span class="n">T</span>: <span class="nc">NullWord</span><span class="o">&gt;</span><span class="p">()</span><span class="w"> </span>-&gt; <span class="nc">T</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">   </span><span class="n">std</span>::<span class="n">mem</span>::<span class="n">transmute</span><span class="p">(</span><span class="mi">0_</span><span class="k">usize</span><span class="p">)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>Now imagine that I wrote an invalid impl like this one:</p>
<div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="c1">// INVALID: We are asserting that `Box` can be null,
</span></span></span><span class="line"><span class="cl"><span class="c1">// which is not true!
</span></span></span><span class="line"><span class="cl"><span class="k">unsafe</span><span class="w"> </span><span class="k">impl</span><span class="o">&lt;</span><span class="n">T</span><span class="o">&gt;</span><span class="w"> </span><span class="n">Nullable</span><span class="w"> </span><span class="k">for</span><span class="w"> </span><span class="nb">Box</span><span class="o">&lt;</span><span class="n">T</span><span class="o">&gt;</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>Given this program I could clearly call <code>foo::&lt;Box&lt;u32&gt;&gt;()</code>, but that would “go wrong” (cause “undefined behavior”). I think we would all agree that the fault lies in the impl. <strong>And yet, that is inconsistent: we say that the impl alone cannot be trusted to figure out if the supertraits are implemented, but it can be trusted to figure out if the unsafe impl is valid?</strong></p>
<h3>Conclusion</h3>
<p>I definitely believe that we want to treat the “extra conditions indicated by unsafe” as a more general version of the other obligations that an impl has to establish to show that the trait holds– and therefore that we must have modular proofs. That’s kind of a relief, because something always felt <em>wrong</em> about external proofs, but it was hard to put my finger on a concrete problem. In the next post in this series (whenever that may be…), I expect to cover the approach to coinductive modular proofs that I landed on. Then I expect to talk about an alternative that was proposed to me that I find quite appealing.</p>
<div class="footnotes">
<hr/>
<ol>
<li id="fn:1">
<p>I think this was obvious to Ralf Jung from the start. But it took me a bit. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:1">↩︎</a></p>
</li>
<li id="fn:2">
<p>This notation is called an <em>inference rule</em>. The conditions above the line are the <em>premises</em> and the bottom line is the <em>conclusion</em>. It says that, if you know the premises are true, you can infer that the conclusion holds. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:2">↩︎</a></p>
</li>
<li id="fn:3">
<p>In point of fact, I believe this will not compile because of special rules about unsafe, but that’s not relevant to the point I’m trying to make. <a class="footnote-backref" href="https://smallcultfollowing.com/babysteps/atom.xml#fnref:3">↩︎</a></p>
</li>
</ol>
</div></div>
    </content>
    <updated>2026-10-10T15:23:35Z</updated>
    <published>2026-10-10T00:00:00Z</published>
    <category label="Cyclic trait impls" scheme="https://smallcultfollowing.com/babysteps/series/cyclic-trait-impls" term="cyclic-trait-impls"/>
    <source>
      <id>https://smallcultfollowing.com/babysteps/</id>
      <author>
        <name>Niko Matsakis</name>
        <email>rust@nikomatsakis.com</email>
      </author>
      <link href="https://smallcultfollowing.com/babysteps/" rel="alternate" title="html" type="text/html"/>
      <link href="https://smallcultfollowing.com/babysteps/index.xml" rel="alternate" title="rss" type="application/rss+xml"/>
      <link href="https://smallcultfollowing.com/babysteps/atom.xml" rel="self" title="atom" type="application/atom+xml"/>
      <title xml:lang="en-us">baby steps</title>
      <updated>2026-10-30T10:48:25Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149725</id>
    <link href="https://discourse.mozilla.org/t/firefox-devtools-mcp-0-10-5-released/149725" rel="alternate" type="text/html"/>
    <title>Firefox DevTools MCP 0.10.5 released</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>New release of Firefox DevTools MCP. Available on npm at <a href="https://www.npmjs.com/package/@mozilla/firefox-devtools-mcp" rel="noopener nofollow ugc">https://www.npmjs.com/package/@mozilla/firefox-devtools-mcp</a></p>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297010-fixed-1" name="p-297010-fixed-1"/>Fixed</h3>
<ul>
<li><code>set_firefox_prefs</code> and <code>get_firefox_prefs</code> work again. They now use WebDriver BiDi to run in the privileged context</li>
<li><code>list_pages</code> no longer fails when the URL or title of a tab cannot be read. That tab is listed with <code>(unknown)</code> values instead</li>
</ul>
<h3><a class="anchor" href="https://discourse.mozilla.org#p-297010-changed-2" name="p-297010-changed-2"/>Changed</h3>
<ul>
<li><code>take_snapshot</code> and the UID-based input tools now use WebDriver BiDi instead of WebDriver Classic</li>
<li>The snapshot script now runs in a sandbox, so page scripts cannot interfere with it and it does not add globals to the page</li>
<li>The Cursor plugin manifest is replaced by the root <code>plugin.json</code> and <code>mcp.json</code> files from the Agent Plugins 1.0 standard, which cursor.directory reads</li>
</ul>
<p>Full changelog: <a class="inline-onebox" href="https://github.com/mozilla/firefox-devtools-mcp/releases/tag/v0.10.5" rel="noopener nofollow ugc">Release v0.10.5 · mozilla/firefox-devtools-mcp · GitHub</a><br/>
Repository and issues: <a class="inline-onebox" href="https://github.com/mozilla/firefox-devtools-mcp" rel="noopener nofollow ugc">GitHub - mozilla/firefox-devtools-mcp: Model Context Protocol server for Firefox DevTools - enables AI assistants to inspect and control Firefox browser through WebDriver BiDi · GitHub</a><br/>
Public chatroom: <a href="https://chat.mozilla.org/#/room/#firefox-devtools-mcp:mozilla.org" rel="noopener nofollow ugc">https://chat.mozilla.org/#/room/#firefox-devtools-mcp:mozilla.org</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/firefox-devtools-mcp-0-10-5-released/149725">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-09T14:03:21Z</updated>
    <published>2026-10-09T14:03:21Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>jdescottes</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/firefox-devtools-mcp-0-10-5-released/149725.rss" title="Firefox DevTools MCP 0.10.5 released"/>
      <updated>2026-11-13T11:58:12Z</updated>
    </source>
  </entry>

  <entry>
    <id>https://servo.org/blog/2026/10/09/august-in-servo/</id>
    <link href="https://servo.org/blog/2026/10/09/august-in-servo/" rel="alternate" type="text/html"/>
    <title>August in Servo: CSS Grid, text selection, and more!</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://github.com/servo/servo/releases/tag/v0.6.0"><strong>Servo 0.6.0</strong></a> contains all of the changes we landed in August, which came out to <strong>417 commits</strong>!</p>
<p>The big news is that we’ve turned on support for <strong>CSS Grid</strong> by default (<a href="https://github.com/nicoburns">@nicoburns</a>, <a href="https://github.com/servo/servo/pull/45621">#45621</a>).
This has had a huge positive impact on the visual appearance of many websites!</p>
<figure>
    <a href="https://servo.org/img/blog/2026-10-gary.png"><img alt="a black and white cat named Gary showing off new visual web platform features" src="https://servo.org/img/blog/2026-10-gary.png"/></a>
</figure>
<p>We’ve shipped several new web platform features:</p>
<ul>
<li><strong>touch-action</strong> (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/47043">#47043</a>)</li>
<li><strong>animation-composition</strong> (<a href="https://github.com/nicoburns">@nicoburns</a>, <a href="https://github.com/servo/servo/pull/47405">#47405</a>)</li>
<li><strong>color-scheme</strong> (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/47042">#47042</a>)</li>
<li><strong>full-width</strong>, <strong>math-auto</strong>, <strong>full-size-kana</strong> values for <strong>text-transform</strong> (<a href="https://github.com/SimonSapin">@SimonSapin</a>, <a href="https://github.com/servo/servo/pull/47160">#47160</a>, <a href="https://github.com/servo/servo/pull/47160">#47160</a>, <a href="https://github.com/servo/servo/pull/47225">#47225</a>)</li>
</ul>
<p>Plus a bunch of new DOM APIs:</p>
<ul>
<li><strong>requestAnimationFrame()</strong> on <strong>DedicatedWorkerGlobalScope</strong> (<a href="https://github.com/Taym95">@Taym95</a>, <a href="https://github.com/servo/servo/pull/46232">#46232</a>)</li>
<li><strong>ancestorOrigins</strong> on <strong>Location</strong> (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/46056">#46056</a>)</li>
<li><strong>imagesrcset</strong> and <strong>imagesizes</strong> on <code>&lt;link rel=preload as=image&gt;</code> (<a href="https://github.com/lumiscosity">@lumiscosity</a>, <a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/47103">#47103</a>)</li>
<li><strong>style</strong> on <strong>CSSFontFaceRule</strong> (<a href="https://github.com/simonwuelker">@simonwuelker</a>, <a href="https://github.com/servo/servo/pull/47388">#47388</a>)</li>
<li><strong>isReloadNavigation</strong> and <strong>isHistoryNavigation</strong> on <strong>Request</strong> (<a href="https://github.com/Taym95">@Taym95</a>, <a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/46917">#46917</a>)</li>
<li><strong>name=color-scheme</strong> on <code>&lt;meta&gt;</code> (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/46993">#46993</a>)</li>
<li><strong>focusin</strong> and <strong>focusout</strong> events (<a href="https://github.com/RichardTjokroutomo">@RichardTjokroutomo</a>, <a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/46980">#46980</a>)</li>
<li><strong>new TextEvent()</strong> (<a href="https://github.com/moamenhesham0">@moamenhesham0</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47391">#47391</a>)</li>
<li><strong>PeriodicWave</strong> and <strong>createPeriodicWave</strong> on <strong>BaseAudioContext</strong> (<a href="https://github.com/kevlu93">@kevlu93</a>, <a href="https://github.com/servo/servo/pull/47492">#47492</a>)</li>
</ul>
<p>This release also contains significant improvements to <strong>navigation</strong>, <strong>document loading</strong>, and <strong>session history</strong>, which are some of the <a href="https://html.spec.whatwg.org/multipage/browsing-the-web.html#navigation-and-session-history">gnarliest</a> parts of the HTML specification. Who knew that loading <code>about:blank</code> was <a href="https://hsivonen.fi/about-blank/">so complicated</a>? The upshot to all this work is that pages that open additional windows or include iframes work much more reliably.</p>
<p>This is another big update, so here’s an outline:</p>
<ul>
<li>
<p><a href="https://servo.org/blog/2026/10/09/august-in-servo/#security"><strong>Security</strong></a></p>
</li>
<li>
<p><a href="https://servo.org/blog/2026/10/09/august-in-servo/#real-world-compat"><strong>Real world compat</strong></a></p>
</li>
<li>
<p><a href="https://servo.org/blog/2026/10/09/august-in-servo/#work-in-progress"><strong>Work in progress</strong></a></p>
</li>
<li>
<p><a href="https://servo.org/blog/2026/10/09/august-in-servo/#embedding-api"><strong>Embedding API</strong></a></p>
</li>
<li>
<p><a href="https://servo.org/blog/2026/10/09/august-in-servo/#for-users-and-developers"><strong>For users and developers</strong></a></p>
</li>
<li>
<p><a href="https://servo.org/blog/2026/10/09/august-in-servo/#more-on-the-web-platform"><strong>More on the web platform</strong></a></p>
</li>
<li>
<p><a href="https://servo.org/blog/2026/10/09/august-in-servo/#performance-and-stability"><strong>Performance and stability</strong></a></p>
</li>
<li>
<p><a href="https://servo.org/blog/2026/10/09/august-in-servo/#new-contributors"><strong>New contributors</strong></a></p>
</li>
</ul>
<h3>Security <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#security">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>We upgraded to <strong>SpiderMonkey v153</strong>, which brings many new security and crash fixes to Servo’s JavaScript engine integration (<a href="https://github.com/sagudev">@sagudev</a>, <a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/servo/servo/pull/47489">#47489</a>).</p>
<p>Navigating away from a document that <strong>activated fullscreen mode</strong> now exits fullscreen mode (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47123">#47123</a>).</p>
<h3>Real world compat <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#real-world-compat">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>CSS Grid enabled by default means that many websites with traditional grid layouts now look correct, like <a href="https://rustweek.org/">rustweek.org</a>.</p>
<figure class="_spaced">
    <div class="_peel">
        <div class="_line">
            <div class="_left"><div>v0.5.0</div></div>
            <div class="_right"><div>v0.6.0</div></div>
        </div>
        <img src="https://servo.org/img/blog/2026-10-grid2-before.png"/>
        <img src="https://servo.org/img/blog/2026-10-grid2-after.png"/>
    </div>
    <figcaption><a href="https://2026.rustweek.org/">2026.rustweek.org</a></figcaption>
</figure>
<p>It also makes a lot of websites look better that you wouldn’t assume rely on CSS Grid:</p>
<figure class="_spaced">
    <div class="_peel">
        <div class="_line">
            <div class="_left"><div>v0.5.0</div></div>
            <div class="_right"><div>v0.6.0</div></div>
        </div>
        <img src="https://servo.org/img/blog/2026-10-grid-before.png"/>
        <img src="https://servo.org/img/blog/2026-10-grid-after.png"/>
    </div>
    <figcaption><a href="https://labs.jensimmons.com/">labs.jensimmons.com</a></figcaption>
</figure>


<p>Panning gestures initiated by touch inputs now lock to the dominant axis (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/46983">#46983</a>).
This results in more predictable panning when interacting with pages in Servo.</p>
<p>We fixed a crash affecting <a href="https://gumroad.com.au/">gumroad.com.au</a> (<a href="https://github.com/lumiscosity">@lumiscosity</a>, <a href="https://github.com/servo/servo/pull/47266">#47266</a>).</p>
<p>We’re interested to hear how well your favourite websites run in Servo! Report successes in <a href="https://servo.zulipchat.com/#narrow/channel/263398-general/topic/Servo.20web.20compat.20success.20stories/with/612898341">this Zulip thread</a> or <a href="https://github.com/servo/servo/discussions/49037">this Github discussion</a>, and failures <a href="https://github.com/servo/servo/issues">in our GitHub issues</a>.</p>
<h3>Work in progress <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#work-in-progress">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p><strong>Accessibility support</strong> in Servo continues to make great strides; it can be enabled with the <code>--pref accessibility_enabled</code> command line argument.
Servo now reports <strong>positions and sizes</strong> for items in the content accessibility tree (<a href="https://github.com/philocalyst">@philocalyst</a>, <a href="https://github.com/alice">@alice</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/46996">#46996</a>), allowing macOS VoiceOver to work more reliably.
We also report many <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles"><strong>ARIA roles</strong></a> for web content elements to accessibility toolkits (<a href="https://github.com/mukilan">@mukilan</a>, <a href="https://github.com/servo/servo/pull/47318">#47318</a>).</p>
<details>
Full list of supported roles
<ul>
<li>alert</li>
<li>banner</li>
<li>blockquote</li>
<li>caption</li>
<li>code</li>
<li>complementary</li>
<li>contentinfo</li>
<li>definition</li>
<li>deletion</li>
<li>directory</li>
<li>document</li>
<li>emphasis</li>
<li>feed</li>
<li>figure</li>
<li>generic</li>
<li>insertion</li>
<li>list</li>
<li>log</li>
<li>main</li>
<li>math</li>
<li>navigation</li>
<li>none</li>
<li>note</li>
<li>paragraph</li>
<li>presentation</li>
<li>rowgroup</li>
<li>search</li>
<li>status</li>
<li>strong</li>
<li>term</li>
<li>time</li>
<li>timer</li>
</ul>
</details><br/>
<p>Servo’s support for <strong>Document.execCommand()</strong> is rapidly improving, and can be enabled with <code>--pref dom_exec_command_enabled</code>.
We fixed issues with the <strong>inserttext</strong> command (<a href="https://github.com/Psychpsyo">@Psychpsyo</a>, <a href="https://github.com/servo/servo/pull/47224">#47224</a>, <a href="https://github.com/servo/servo/pull/47306">#47306</a>), editing uneditable content (<a href="https://github.com/Psychpsyo">@Psychpsyo</a>, <a href="https://github.com/servo/servo/pull/47362">#47362</a>), computing contained nodes (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/47429">#47429</a>), adjusting selections in <strong>contenteditable</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47393">#47393</a>, <a href="https://github.com/servo/servo/pull/47581">#47581</a>, <a href="https://github.com/servo/servo/pull/47581">#47581</a>), and implemented the <strong>indent</strong> and <strong>insertLineBreak</strong> commands (<a href="https://github.com/Psychpsyo">@Psychpsyo</a>, <a href="https://github.com/servo/servo/pull/47416">#47416</a>, <a href="https://github.com/servo/servo/pull/47445">#47445</a>).</p>
<p>We made a lot of progress on the <strong>LargestContentfulPaint</strong> performance metric, implemented behind the <code>--pref largest_contentful_paint_enabled</code> argument.
Servo now supports the <strong>element</strong> and <strong>loadTime</strong> attributes, (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/46553">#46553</a>, <a href="https://github.com/servo/servo/pull/47475">#47475</a>), URLs for video element posters (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/43376">#43376</a>), accurate size information (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/43378">#43378</a>), and painting text nodes (<a href="https://github.com/shubhamg13">@shubhamg13</a>, <a href="https://github.com/servo/servo/pull/47212">#47212</a>).</p>
<p>There was preparatory work for a future <a href="https://developer.mozilla.org/en-US/docs/Web/API/AudioWorklet"><strong>AudioWorklet</strong></a> implementation (<a href="https://github.com/niyabits">@niyabits</a>, <a href="https://github.com/servo/servo/pull/46856">#46856</a>, <a href="https://github.com/servo/servo/pull/47016">#47016</a>, <a href="https://github.com/servo/servo/pull/47199">#47199</a>).
See Niya’s <a href="https://text.tchncs.de/niya/wrapping-up-my-work-on-servos-audioworklet">blog post</a> about her Outreachy project for more details!</p>
<p>We’re continuing work on the <strong>ServiceWorker</strong> feature, which can be enabled with <code>--pref dom_serviceworker_enabled</code>.
This month we implemented the <strong>CookieStore</strong> interface behind the <code>--pref dom_cookiestore_enabled</code> command line argument (<a href="https://github.com/Taym95">@Taym95</a>, <a href="https://github.com/servo/servo/pull/47044">#47044</a>) as well as the <strong>Cache</strong> interface (<a href="https://github.com/gterzian">@gterzian</a>, <a href="https://github.com/servo/servo/pull/47220">#47220</a>).</p>
<p>Servo now supports a <strong>disk-backed HTTP cache</strong> that can be enabled with <code>--pref network_http_disk_cache</code> (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/43819">#43819</a>).
This cache persists between runs, but there is not yet any way to clear it.</p>
<h3>Embedding API <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#embedding-api">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p><strong>Breaking change:</strong> <a href="https://doc.servo.org/servo/struct.WebView.html"><code>WebView</code></a>::<code>toggle_sampling_profiler</code> has been removed (<a href="https://github.com/lumiscosity">@lumiscosity</a>, <a href="https://github.com/servo/servo/pull/47014">#47014</a>).
To perform sampling profiling on Servo, follow the instructions in <a href="https://book.servo.org/contributing/profiling.html">the book</a>.</p>
<p><strong>Breaking change:</strong> The variants of <a href="https://doc.servo.org/servo/enum.MouseButton.html"><code>MouseButton</code></a> have been renamed to <code>Primary</code>, <code>Secondary</code>, and <code>Auxiliary</code> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/SimonSapin">@SimonSapin</a>, <a href="https://github.com/servo/servo/pull/47327">#47327</a>).</p>
<p>We’ve added several new Cargo features reflecting common usage patterns:</p>
<ul>
<li><code>default_web_features</code>, to include optional web platform features in the build (e.g. WebXR and WebGPU) (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/44032">#44032</a>)</li>
<li><code>bundled</code>, to include required resources in the binary (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/44032">#44032</a>)</li>
<li><code>brotli-compression-stream</code>, enabling support for <code>brotli</code> content in the <code>CompressionStream</code>/<code>DecompressionStream</code> web APIs (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47197">#47197</a>)</li>
<li><code>webcrypto</code>, to enable support for the Crypto and WebCrypto web APIs (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/47198">#47198</a>)</li>
<li><code>webgl</code>, to enable support for WebGL (<a href="https://github.com/janeoa">@janeoa</a>, <a href="https://github.com/servo/servo/pull/47200">#47200</a>)</li>
</ul>
<h3>For users and developers <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#for-users-and-developers">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>One visible change is that interactive <strong>text selection</strong> now works!
This is the result of lots of work across our script and layout code to ensure it respects the actual geometry of the page content (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/SimonSapin">@SimonSapin</a>, <a href="https://github.com/servo/servo/pull/47022">#47022</a>, <a href="https://github.com/servo/servo/pull/47025">#47025</a>, <a href="https://github.com/servo/servo/pull/47329">#47329</a>, <a href="https://github.com/servo/servo/pull/47358">#47358</a>, <a href="https://github.com/servo/servo/pull/46982">#46982</a>, <a href="https://github.com/servo/servo/pull/47425">#47425</a>, <a href="https://github.com/servo/servo/pull/47438">#47438</a>, <a href="https://github.com/servo/servo/pull/47437">#47437</a>, <a href="https://github.com/servo/servo/pull/47581">#47581</a>, <a href="https://github.com/servo/servo/pull/47070">#47070</a>, <a href="https://github.com/servo/servo/pull/47048">#47048</a>, <a href="https://github.com/servo/servo/pull/46963">#46963</a>).</p>
<figure>
    <a href="https://servo.org/img/blog/2026-10-select.png"><img alt="servoshell 0.6.0 showing text selection on an element using CSS perspective" src="https://servo.org/img/blog/2026-10-select.png"/></a>
</figure>
<p>Building Servo now requires at least <strong>Clang 19</strong> on all platforms (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47421">#47421</a>).
Additionally, the <code>cargo-ohos</code> tool is now required for building for OpenHarmony (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47334">#47334</a>).</p>
<p>Debug builds on Windows can now complete successfully (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47372">#47372</a>).</p>
<p>Linux arm64 builds have been customized to work on <strong>Raspberry Pi 5</strong> (<a href="https://github.com/mukilan">@mukilan</a>, <a href="https://github.com/servo/servo/pull/47113">#47113</a>).
Any libservo embedders targeting the same platform will require a similar change if they are using jemalloc.</p>
<h4>servoshell <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#servoshell">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h4>
<p>Under <strong>Wayland</strong> and <strong>OpenHarmony</strong>, we now integrate with the system clipboard (<a href="https://github.com/TheZoq2">@TheZoq2</a>, <a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/46938">#46938</a>, <a href="https://github.com/servo/servo/pull/47177">#47177</a>).</p>
<p>The macOS command key and Windows logo key is now reported as <code>Meta</code> instead of <code>Super</code> (<a href="https://github.com/eachra-bawn">@eachra-bawn</a>, <a href="https://github.com/servo/servo/pull/47330">#47330</a>).</p>
<p>The <strong>Android</strong> port has had many rough edges filed off as part of modernizing it for the <strong>Compose UI</strong> (<a href="https://github.com/veyndan">@veyndan</a>, <a href="https://github.com/servo/servo/pull/47656">#47656</a>, <a href="https://github.com/servo/servo/pull/47491">#47491</a>, <a href="https://github.com/servo/servo/pull/47494">#47494</a>, <a href="https://github.com/servo/servo/pull/47697">#47697</a>, <a href="https://github.com/servo/servo/pull/46955">#46955</a>, <a href="https://github.com/servo/servo/pull/47644">#47644</a>, <a href="https://github.com/servo/servo/pull/47652">#47652</a>, <a href="https://github.com/servo/servo/pull/47276">#47276</a>, <a href="https://github.com/servo/servo/pull/47277">#47277</a>, <a href="https://github.com/servo/servo/pull/47299">#47299</a>, <a href="https://github.com/servo/servo/pull/47439">#47439</a>) and converting its implementation to Kotlin (<a href="https://github.com/veyndan">@veyndan</a>, <a href="https://github.com/servo/servo/pull/46926">#46926</a>, <a href="https://github.com/servo/servo/pull/46925">#46925</a>, <a href="https://github.com/servo/servo/pull/46951">#46951</a>, <a href="https://github.com/servo/servo/pull/46965">#46965</a>).
Library consumers are no longer responsible for implementing <strong>pause and resume</strong> support (<a href="https://github.com/veyndan">@veyndan</a>, <a href="https://github.com/servo/servo/pull/47555">#47555</a>).</p>
<p>Meanwhile, the <strong>OpenHarmony</strong> port now supports external keyboards with US keyboard layouts (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47359">#47359</a>).
Additionally, there are now better fallback font selections for CJK characters (<a href="https://github.com/RichardTjokroutomo">@RichardTjokroutomo</a>, <a href="https://github.com/servo/servo/pull/47116">#47116</a>, <a href="https://github.com/servo/servo/pull/47664">#47664</a>).</p>
<p>Setting the <code>device_pixel_ratio_override</code> preference is no longer ignored on Android and OpenHarmony (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47081">#47081</a>).</p>
<h3>Performance and stability <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#performance-and-stability">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>There were many small changes this month that <strong>removed unnecessary allocations</strong> (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/47264">#47264</a>, <a href="https://github.com/servo/servo/pull/47147">#47147</a>, <a href="https://github.com/servo/servo/pull/47066">#47066</a>, <a href="https://github.com/servo/servo/pull/47249">#47249</a>, <a href="https://github.com/servo/servo/pull/47249">#47249</a>, <a href="https://github.com/servo/servo/pull/47285">#47285</a>, <a href="https://github.com/servo/servo/pull/47307">#47307</a>, <a href="https://github.com/servo/servo/pull/47343">#47343</a>, <a href="https://github.com/servo/servo/pull/47361">#47361</a>, <a href="https://github.com/servo/servo/pull/47395">#47395</a>, <a href="https://github.com/servo/servo/pull/47427">#47427</a>, <a href="https://github.com/servo/servo/pull/47454">#47454</a>, <a href="https://github.com/servo/servo/pull/47474">#47474</a>, <a href="https://github.com/servo/servo/pull/47506">#47506</a>, <a href="https://github.com/servo/servo/pull/47479">#47479</a>, <a href="https://github.com/servo/servo/pull/47530">#47530</a>, <a href="https://github.com/servo/servo/pull/47541">#47541</a>, <a href="https://github.com/servo/servo/pull/47566">#47566</a>, <a href="https://github.com/servo/servo/pull/47509">#47509</a>, <a href="https://github.com/servo/servo/pull/47622">#47622</a>).</p>
<p>We also <strong>reduced GC interactions</strong> leading to better JS performance (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/webbeef">@webbeef</a>, <a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47513">#47513</a>, <a href="https://github.com/servo/servo/pull/47250">#47250</a>, <a href="https://github.com/servo/servo/pull/47158">#47158</a>, <a href="https://github.com/servo/servo/pull/47165">#47165</a>, <a href="https://github.com/servo/servo/pull/47049">#47049</a>, <a href="https://github.com/servo/servo/pull/47251">#47251</a>, <a href="https://github.com/servo/servo/pull/47510">#47510</a>, <a href="https://github.com/servo/servo/pull/46981">#46981</a>).</p>
<p>On platforms that memory map font data (such as OpenHarmony and macOS), we can now save time that would otherwise be spent loading font files from disk (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47029">#47029</a>).
Similarly, reading system fonts is no longer in the critical path of starting up the engine (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/46476">#46476</a>).</p>
<p>There were were also a number of savings in the final binary size (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/kkoyung">@kkoyung</a>, <a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47211">#47211</a>, <a href="https://github.com/servo/servo/pull/47214">#47214</a>, <a href="https://github.com/servo/servo/pull/47210">#47210</a>, <a href="https://github.com/servo/servo/pull/46950">#46950</a>).</p>
<p>We <strong>fixed crashes</strong> related to media playback (<a href="https://github.com/calvaris">@calvaris</a>, <a href="https://github.com/servo/servo/pull/46891">#46891</a>), the 2d canvas renderer (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/46915">#46915</a>), fonts with negative line gaps (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/47374">#47374</a>), and resolving fonts variants (<a href="https://github.com/simonwuelker">@simonwuelker</a>, <a href="https://github.com/servo/servo/pull/47356">#47356</a>).</p>
<p>Canvas renderer worker threads can now be adjusted by the <code>thread_pool_canvas_workers</code> preference, allowing more performance granularity according to embedder needs. (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/servo/servo/pull/46691">#46691</a>, <a href="https://github.com/servo/servo/pull/47018">#47018</a>)</p>
<p>We’ve continued our long-running effort to use the Rust type system to make Servo’s integration with SpiderMonkey <strong>safer and more reliable</strong> (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/treetmitterglad">@treetmitterglad</a>, <a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/servo/servo/pull/47398">#47398</a>, <a href="https://github.com/servo/servo/pull/47296">#47296</a>, <a href="https://github.com/servo/servo/pull/47051">#47051</a>, <a href="https://github.com/servo/servo/pull/47005">#47005</a>, <a href="https://github.com/servo/servo/pull/47323">#47323</a>, <a href="https://github.com/servo/servo/pull/47297">#47297</a>, <a href="https://github.com/servo/servo/pull/47322">#47322</a>, <a href="https://github.com/servo/servo/pull/47368">#47368</a>, <a href="https://github.com/servo/servo/pull/47446">#47446</a>, <a href="https://github.com/servo/servo/pull/47317">#47317</a>). We’re also working on statically preventing <a href="https://github.com/servo/servo/issues/39139">a footgun</a> that can lead to uncollectible GC cycles and leaking memory (<a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/servo/servo/pull/47355">#47355</a>, <a href="https://github.com/servo/servo/pull/47650">#47650</a>).</p>
<p>Historically, <strong>about:memory</strong> has reported all memory usage by Rust implementations of JS APIs as one undifferentiated <code>js/malloc-heap</code> number.
We now break it down by memory usage of nodes in document trees (<a href="https://github.com/pylbrecht">@pylbrecht</a>, <a href="https://github.com/servo/servo/pull/46931">#46931</a>) and interfaces that are not part of the DOM (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47531">#47531</a>). We also report memory usage for the network stack’s cookie database (<a href="https://github.com/Narfinger">@Narfinger</a>, <a href="https://github.com/servo/servo/pull/47248">#47248</a>) and the canvas renderer backend (<a href="https://github.com/janeoa">@janeoa</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/46958">#46958</a>).</p>
<p>We’ve added an <strong>experimental threadboost</strong> mechanism (<a href="https://github.com/jschwe">@jschwe</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/46843">#46843</a>, <a href="https://github.com/servo/servo/pull/47027">#47027</a>) that has been observed to improve Speedometer results by <strong>50%</strong> and allow canvas rendering to reach 60 FPS.
This is initially enabled for OpenHarmony, but future expansion to other Linux-based platforms is expected.</p>
<h3>More on the web platform <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#more-on-the-web-platform">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>We upgraded to <a href="https://github.com/linebender/resvg/blob/main/CHANGELOG.md#0480-2026-07-31">resvg 0.48</a>, fixing <strong>many issues with SVG images</strong> with missing width/height attributes that specified a <code>viewBox</code> (<a href="https://github.com/nicoburns">@nicoburns</a>, <a href="https://github.com/servo/servo/pull/46937">#46937</a>).</p>
<p>Upgrading to <a href="https://github.com/DioxusLabs/taffy/blob/main/CHANGELOG.md#0130">Taffy 0.14</a> fixed a number of <strong>CSS grid-related crashes</strong>, support for grid names, better intrinsic sizing, and improved performance (<a href="https://github.com/nicoburns">@nicoburns</a>, <a href="https://github.com/servo/servo/pull/47031">#47031</a>, <a href="https://github.com/servo/servo/pull/47493">#47493</a>).
We also fixed some issues in the Taffy grid integration for more accurate baselines (<a href="https://github.com/nicoburns">@nicoburns</a>, <a href="https://github.com/servo/servo/pull/47518">#47518</a>).</p>
<p>Session history traversals (i.e. navigating backwards or forwards in history) now wait for any outstanding traversal to complete (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47293">#47293</a>, <a href="https://github.com/servo/servo/pull/47485">#47485</a>).
Meanwhile, navigations to <code>about:blank</code> are skipped if the initial about:blank document is present (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47074">#47074</a>).</p>
<p><code>about:blank</code> documents no longer use the asynchronous HTML parser (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47050">#47050</a>), and no longer report a <code>readyState</code> of <code>LOADING</code> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47450">#47450</a>).
Opening auxiliary windows will wait to dispatch the load event until the initial <code>about:blank</code> document has <a href="https://html.spec.whatwg.org/multipage/document-sequences.html#windows%3Awindow">been replaced</a> (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47442">#47442</a>, <a href="https://github.com/servo/servo/pull/46975">#46975</a>).</p>
<p>For non-about:blank content, we also made the document loading phases more reliable (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47426">#47426</a>), improved conformance of <code>javascript:</code> URL evaluation and navigation target selection (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47486">#47486</a>, <a href="https://github.com/servo/servo/pull/47516">#47516</a>), and addressed longstanding compatibility issues with cross-origin <code>Window</code> and <code>Location</code> objects (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47549">#47549</a>).</p>
<p>Our media playback has improved; we fixed several issues around <strong>canPlayType()</strong> on <strong>HTMLMediaElement</strong> that allow Servo to report that <strong>MP4 content is playable</strong> (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47612">#47612</a>, <a href="https://github.com/servo/servo/pull/47641">#47641</a>, <a href="https://github.com/servo/servo/pull/47670">#47670</a>).</p>
<p>Input elements with the <code>autofocus</code> property inside of a <code>&lt;dialog&gt;</code> now receive focus when that dialog is opened (<a href="https://github.com/skyz1">@skyz1</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/45826">#45826</a>).</p>
<p>We improved the exception error text for numerous web APIs (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/eachra-bawn">@eachra-bawn</a>, <a href="https://github.com/servo/servo/pull/46960">#46960</a>, <a href="https://github.com/servo/servo/pull/47124">#47124</a>, <a href="https://github.com/servo/servo/pull/47168">#47168</a>, <a href="https://github.com/servo/servo/pull/47580">#47580</a>, <a href="https://github.com/servo/servo/pull/47430">#47430</a>, <a href="https://github.com/servo/servo/pull/47127">#47127</a>).</p>
<p>We also fixed issues related to many other APIs, including:</p>
<ul>
<li>matching other browsers’ treatment of <strong>Access-Control-Allow-Headers</strong> (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/47600">#47600</a>)</li>
<li>WebCrypto <strong>CryptoKey</strong> usage checks (<a href="https://github.com/kkoyung">@kkoyung</a>, <a href="https://github.com/servo/servo/pull/47112">#47112</a>, <a href="https://github.com/servo/servo/pull/47141">#47141</a>, <a href="https://github.com/servo/servo/pull/47178">#47178</a>) and key lengths (<a href="https://github.com/kkoyung">@kkoyung</a>, <a href="https://github.com/servo/servo/pull/47452">#47452</a>, <a href="https://github.com/servo/servo/pull/47453">#47453</a>)</li>
<li>determining referrers when navigating (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47487">#47487</a>)</li>
<li>reading <strong>name</strong> on <strong>Window</strong> inside of iframes (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/47270">#47270</a>)</li>
<li>many edge cases around determining dirty roots for incremental layout (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/46906">#46906</a>)</li>
<li>edge cases around <strong>compareDocumentPosition</strong> on <strong>Node</strong> (<a href="https://github.com/SimonSapin">@SimonSapin</a>, <a href="https://github.com/servo/servo/pull/46886">#46886</a>)</li>
<li>resolving ties in web font matching (<a href="https://github.com/simonwuelker">@simonwuelker</a>, <a href="https://github.com/servo/servo/pull/47449">#47449</a>)</li>
<li>Range.<strong>getClientBoundingRect()</strong>/<strong>getClientRects</strong>() for empty ranges (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/47143">#47143</a>)</li>
<li>JS module fetching failures can now be retried (<a href="https://github.com/Gae24">@Gae24</a>, <a href="https://github.com/servo/servo/pull/46919">#46919</a>)</li>
<li><code>KeyEvent.keyCode</code> values for many <strong>nonprintable keys</strong> now match other browsers (<a href="https://github.com/eachra-bawn">@eachra-bawn</a>, <a href="https://github.com/servo/servo/pull/47461">#47461</a>)</li>
<li>making <strong>timing</strong> on <strong>Performance</strong> return a <code>PerformanceTiming</code> object (<a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/aniebietafia">@aniebietafia</a>, <a href="https://github.com/servo/servo/pull/46990">#46990</a>)</li>
<li>synthesizing font variations from <code>font-style</code> (<a href="https://github.com/simonwuelker">@simonwuelker</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/46918">#46918</a>, <a href="https://github.com/servo/servo/pull/47364">#47364</a>)</li>
<li>the <strong>Get Element Tag Name</strong> WebDriver command (<a href="https://github.com/yezhizhen">@yezhizhen</a>, <a href="https://github.com/servo/servo/pull/47216">#47216</a>)</li>
<li>removed nonstandard WebDriver-related properties on the global object (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47542">#47542</a>)</li>
<li>sniffing RAR responses correctly (<a href="https://github.com/wood-ghost">@wood-ghost</a>, <a href="https://github.com/servo/servo/pull/47366">#47366</a>)</li>
<li><code>Attribute</code> nodes created during parsing now have the expected namespace prefix (<a href="https://github.com/Ms2ger">@Ms2ger</a>, <a href="https://github.com/servo/servo/pull/47030">#47030</a>)</li>
<li>improving <strong>text-transform: capitalize</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/46910">#46910</a>)</li>
<li>zero-sized margins inside of inline boxes (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/47020">#47020</a>)</li>
<li>incorrect <code>buttons</code> values in pointer capture transitions (<a href="https://github.com/steigeo">@steigeo</a>, <a href="https://github.com/servo/servo/pull/45628">#45628</a>)</li>
<li>empty lists returned by <strong>load()</strong> on <strong>FontFaceSet</strong> (<a href="https://github.com/simonwuelker">@simonwuelker</a>, <a href="https://github.com/servo/servo/pull/47564">#47564</a>)</li>
<li>cancelling more ongoing network requests when performing a navigation (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/47576">#47576</a>)</li>
<li>shaping text across inline boxes (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/46829">#46829</a>)</li>
<li>scrollable overflow for <code>position: sticky</code> (<a href="https://github.com/rayguo17">@rayguo17</a>, <a href="https://github.com/servo/servo/pull/43766">#43766</a>)</li>
<li>fixing hyperlinks for blob: URLs (<a href="https://github.com/TimvdLippe">@TimvdLippe</a>, <a href="https://github.com/servo/servo/pull/47226">#47226</a>)</li>
<li>firing the error callback for <strong>decodeAudioData</strong> on <strong>BaseAudioContext</strong> (<a href="https://github.com/amittenak47">@amittenak47</a>, <a href="https://github.com/jdm">@jdm</a>, <a href="https://github.com/servo/servo/pull/46870">#46870</a>)</li>
</ul>
<h3>New contributors <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#new-contributors">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>A special thanks to the following people for landing their first patch in Servo:</p>
<ul>
<li>Frans Skarman (<a href="https://github.com/TheZoq2">@TheZoq2</a>, <a href="https://github.com/servo/servo/pull/46938">#46938</a>)</li>
<li>Moamen Hesham (<a href="https://github.com/moamenhesham0">@moamenhesham0</a>, <a href="https://github.com/servo/servo/pull/47391">#47391</a>)</li>
<li>Miles Wirht (<a href="https://github.com/philocalyst">@philocalyst</a>, <a href="https://github.com/servo/servo/pull/46996">#46996</a>)</li>
<li>Vaibhav Srivastava (<a href="https://github.com/vaibhav8a">@vaibhav8a</a>, <a href="https://github.com/servo/servo/pull/47626">#47626</a>)</li>
<li>wood-ghost (<a href="https://github.com/wood-ghost">@wood-ghost</a>, <a href="https://github.com/servo/servo/pull/47366">#47366</a>)</li>
<li>禾可 (<a href="https://github.com/Lfan-ke">@Lfan-ke</a>, <a href="https://github.com/servo/servo/pull/47514">#47514</a>)</li>
</ul>
<p>Interested in helping build a web browser?
Take a look at our <a href="https://starters.servo.org/">curated list</a> of issues that are good for new contributors!</p>
<h3>Donations <a class="header-anchor" href="https://servo.org/blog/2026/10/09/august-in-servo/#donations">
        <span class="icon hashlink"><i class="fas fa-link"/></span>
      </a></h3>
<p>Thanks again for your generous support!
We are now receiving <strong>8128 USD/month</strong> (+3% from July) in recurring donations.
This helps us cover the cost of our <strong><a href="https://ci0.servo.org/">speedy</a> <a href="https://ci1.servo.org/">CI</a> <a href="https://ci2.servo.org/">and</a> <a href="https://ci3.servo.org/">benchmarking</a> <a href="https://ci4.servo.org/">servers</a></strong>, one of our latest <strong><a href="https://www.outreachy.org/alums/2026-05/#:~:text=Servo">Outreachy interns</a></strong>, and funding <strong><a href="https://servo.org/blog/2026/09/15/one-year-of-sponsorship/">maintainer work</a></strong> that helps more people contribute to Servo.</p>
<p>Servo is also on <a href="https://thanks.dev/">thanks.dev</a>, and already <strong>36 GitHub users</strong> (+1 from July) that depend on Servo are sponsoring us there.
If you use Servo libraries like <a href="https://crates.io/crates/url/reverse_dependencies">url</a>, <a href="https://crates.io/crates/html5ever/reverse_dependencies">html5ever</a>, <a href="https://crates.io/crates/selectors/reverse_dependencies">selectors</a>, or <a href="https://crates.io/crates/cssparser/reverse_dependencies">cssparser</a>, signing up for <a href="https://thanks.dev/">thanks.dev</a> could be a good way for you (or your employer) to give back to the community.</p>
<p>We now have <a href="https://servo.org/blog/2025/11/21/sponsorship-tiers/"><strong>sponsorship tiers</strong></a> that allow you or your organisation to donate to the Servo project with public acknowlegement of your support.
If you’re interested in this kind of sponsorship, please contact us at <a href="mailto:join@servo.org">join@servo.org</a>.</p>
<figure class="_fig" style="width: 100%; margin: 1em 0;"><div class="_flex">
    <div style="text-align: right;">
        <div><strong>8128</strong> USD/month</div>
        <div/>
        <div/>
        <div style="padding-right: 1em;"><strong>10000</strong></div>
    </div>
    <progress max="10000" value="7824"/>
</div></figure>
<p>Use of donations is decided transparently via the Technical Steering Committee’s public <strong><a href="https://github.com/servo/project/blob/main/FUNDING_REQUEST.md">funding request process</a></strong>, and active proposals are tracked in <a href="https://github.com/servo/project/issues/187">servo/project#187</a>.
For more details, head to our <a href="https://servo.org/sponsorship/">Sponsorship page</a>.</p></div>
    </content>
    <updated>2026-10-09T00:00:00Z</updated>
    <source>
      <id>https://servo.org</id>
      <author>
        <name>Servo Team</name>
        <email>info@servo.org</email>
      </author>
      <link href="https://servo.org/blog/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://servo.org" rel="alternate" type="text/html"/>
      <subtitle>All the entries in the Servo blog.</subtitle>
      <title>Servo Blog</title>
      <updated>2026-11-05T00:00:00Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/netpolicy/?p=2626</id>
    <link href="https://blog.mozilla.org/netpolicy/2026/10/08/canadas-bill-c-22-threatens-encryption-users-privacy-and-the-security-of-digital-economies/" rel="alternate" type="text/html"/>
    <title>Canada’s bill C-22 threatens encryption, users’ privacy and the security of digital economies</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Encryption is woven into everyday digital life. It protects our messages and passwords, but also banking and payments, health data, government services and the digital infrastructure societies rely on every … <a class="go" href="https://blog.mozilla.org/netpolicy/2026/10/08/canadas-bill-c-22-threatens-encryption-users-privacy-and-the-security-of-digital-economies/">Read more</a></p>
<p>The post <a href="https://blog.mozilla.org/netpolicy/2026/10/08/canadas-bill-c-22-threatens-encryption-users-privacy-and-the-security-of-digital-economies/">Canada’s bill C-22 threatens encryption, users’ privacy and the security of digital economies </a> appeared first on <a href="https://blog.mozilla.org/netpolicy">Open Policy &amp; Advocacy</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Encryption is woven into everyday digital life. It protects our messages and passwords, but also banking and payments, health data, government services and the digital infrastructure societies rely on every day. Yet across jurisdictions, governments are increasingly considering laws that expand lawful access to data for law enforcement and national security purposes. In practice, this can mean requiring companies to create new ways to access encrypted data, introduce technical capabilities that bypass existing protections, or make otherwise secure systems insecure. These measures can weaken the very security encryption is designed to provide, with consequences for cybersecurity, privacy, fundamental rights and the wider economy. Canada’s Bill C-22 is the latest example of this trend, raising serious concerns about the security and privacy consequences of expanding government access to data.</p>
<p>For Mozilla, protecting that security is fundamental to both the products we build and the principles we advocate for. One of the <a href="https://www.mozilla.org/en-US/about/manifesto/#principles-04">foundational principles</a> that guide Mozilla’s mission and work holds that individuals’ security and privacy on the internet are fundamental and must not be treated as optional. Protecting people’s privacy and security is not an aspiration for us, but shapes the products we build every day: Firefox <a href="https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop?utm_source=www.firefox.com&amp;utm_medium=referral&amp;utm_campaign=user-privacy">blocks trackers</a>, protects you from <a href="https://support.mozilla.org/en-US/kb/introducing-total-cookie-protection-standard-mode?utm_source=www.firefox.com&amp;utm_medium=referral&amp;utm_campaign=user-privacy">profiling via cookies</a> and <a href="https://www.firefox.com/de/features/block-fingerprinting/">fingerprinting</a>, comes with <a href="https://support.mozilla.org/en-US/kb/how-does-phishing-and-malware-protection-work">malware protection</a> and a <a href="https://www.firefox.com/en-US/features/browser-with-built-in-vpn-secure-browsing/">built-in VPN</a>, offers <a href="https://support.mozilla.org/en-US/kb/https-only-prefs">HTTPs-only mode</a> and protects your passwords and credit card information by <a href="https://support.mozilla.org/en-US/kb/how-firefox-securely-saves-passwords">encrypting</a> them.</p>
<p>Some of these protections are being threatened by <a href="https://www.parl.ca/documentviewer/en/45-1/bill/C-22/first-reading">Canada’s Lawful Access Act, also known as bill C-22</a>. Part two of the bill, the “Supporting Authorized Access to Information Act” (SAAIA) would introduce sweeping new powers to require electronic service providers to build and maintain capabilities that facilitate government access to information. If passed in its current form, companies could be asked to introduce vulnerabilities, build backdoors, bypass, weaken or otherwise defeat encryption, access data before encryption or decrypt encrypted data to provide access to law enforcement. Service providers could also be compelled to retain and access data they have purposefully chosen not to collect.</p>
<p>Let us be clear: there is no safe way to create exceptional access to encrypted data that only the intended actor can use. An access mechanism created for law enforcement can also be discovered, exploited or abused by potentially bad actors.</p>
<p>Such vulnerabilities and backdoors do not only undermine people’s fundamental rights to privacy and data protection, but also the trust and security premises societies everywhere depend on. The same encryption that protects a private conversation also protects financial transactions, sensitive health information, business systems and critical digital services.</p>
<p>Expanding capabilities of AI systems are only exacerbating these risks – governments should encourage the disclosure and patching of vulnerabilities, not compel companies to introduce insecurities deliberately. Only trustworthy and transparently governed digital infrastructures can be the basis for digitally sovereign societies.</p>
<p>We are also concerned by C-22’s scope, which does not stop at Canadian services or users. C-22 expansive surveillance capabilities and data retention obligations would undermine people’s privacy and security everywhere, and the bill’s confidentiality requirements would make it impossible for services to inform their users about security breaches or backdoors introduced.</p>
<p>Guided by our <a href="https://surveillance.mozilla.org/">Surveillance Principles for a Secure, Trusted Internet</a>, we call on Canadian policymakers not to rush the legislative process to take experts’ feedback into account in amending C-22 to protect everyone’s security and privacy. Canada’s interests are best served by regulation that protects encryption, strengthens cybersecurity and emphasizes transparency, checks and balances.</p>
<p>The post <a href="https://blog.mozilla.org/netpolicy/2026/10/08/canadas-bill-c-22-threatens-encryption-users-privacy-and-the-security-of-digital-economies/">Canada’s bill C-22 threatens encryption, users’ privacy and the security of digital economies </a> appeared first on <a href="https://blog.mozilla.org/netpolicy">Open Policy &amp; Advocacy</a>.</p></div>
    </content>
    <updated>2026-10-08T09:35:34Z</updated>
    <published>2026-10-08T09:35:34Z</published>
    <category term="privacy"/>
    <category term="Surveillance"/>
    <category term="Encryption"/>
    <author>
      <name>Svea Windwehr and Tasos Stampelos</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/netpolicy/</id>
      <link href="https://blog.mozilla.org/netpolicy/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/netpolicy/" rel="alternate" type="text/html"/>
      <subtitle>Mozilla's official blog on open Internet policy initiatives and developments</subtitle>
      <title>Open Policy &amp; Advocacy</title>
      <updated>2026-10-27T00:05:42Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=87764</id>
    <link href="https://blog.mozilla.org/en/firefox/firefox-aeg-uber-arena-partnership/" rel="alternate" type="text/html"/>
    <title>Firefox partners with Anschutz Entertainment Group at the Uber Arena and Uber Eats Music Hall in Berlin</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Firefox is teaming up with AEG and taking to the main stage at Berlin’s biggest and best indoor arenas. Starting this October, as the indoor music scene heats up and the basketball and ice hockey seasons are in full swing, fans flocking to the Uber Arena, Uber Eats Music Hall, and Uber Platz will see […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/firefox-aeg-uber-arena-partnership/">Firefox partners with Anschutz Entertainment Group at the Uber Arena and Uber Eats Music Hall in Berlin</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Firefox is teaming up with AEG and taking to the main stage at Berlin’s biggest and best indoor arenas. Starting this October, as the indoor music scene heats up and the basketball and ice hockey seasons are in full swing, fans flocking to the Uber Arena, Uber Eats Music Hall, and Uber Platz will see Firefox highly visible around the venue. They may even bump into <a href="https://blog.mozilla.org/en/firefox/meet-kit/">our very own mascot, Kit</a>, who will be on hand to help them skip the main queues courtesy of Firefox. </p>



<p>We know that the experiences people care about often begin online. The internet is the gateway to how they discover, plan, and navigate their way to concerts, sports events, and nights out before they happen in real life. </p>



<p>Firefox’s presence will help make every step of that journey simple and smoother, starting at the door. </p>



<figure class="wp-block-image size-large"><img alt="" class="wp-image-88036" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/2026-Firefox-InsGluck-Uber_T635353-highres_&#xA9;-Holger-Talinski-1-1024x576.jpg" width="1024"/></figure>



<p>People with Firefox downloaded on their phone will have access to a dedicated Firefox Fast Lane that allows them to skip the main line at the Uber Arena. To ensure the smoothest possible entry, a QR code for downloading Firefox will also be available at the Fast Lane.</p>



<p>“People who use Firefox tend to choose things deliberately, their browser, their music, their nights out. This partnership is for them. A first for Firefox. Most browsers want more of your time online. We want you at the show, faster. Berlin is where we are starting, right across the river from our office. See you there,” said John Solomon, Mozilla-Firefox Chief Marketing Officer.</p>



<p>We are excited to bring what we stand for to Berlin’s premier entertainment venue — choice, control, and a better experience to the moments that people want to enjoy and truly care about.</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/firefox-aeg-uber-arena-partnership/">Firefox partners with Anschutz Entertainment Group at the Uber Arena and Uber Eats Music Hall in Berlin</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-08T07:00:00Z</updated>
    <published>2026-10-08T07:00:00Z</published>
    <category term="Firefox"/>
    <category term="News"/>
    <category term="export"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=88058</id>
    <link href="https://blog.mozilla.org/en/mozilla/palaniappan-parry-jones/" rel="alternate" type="text/html"/>
    <title>Jambu Palaniappan and David Parry-Jones join the Mozilla Corporation Board of Directors</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Today, we are very pleased to announce two new additions to the Mozilla Corporation Board of Directors: Jambu Palaniappan and David Parry-Jones. As we build the next chapter of Mozilla, we’ve been focused on bringing people onto our Board who combine deep operating experience with a real commitment to the values Mozilla stands for. Jambu […]</p>
<p>The post <a href="https://blog.mozilla.org/en/mozilla/palaniappan-parry-jones/">Jambu Palaniappan and David Parry-Jones join the Mozilla Corporation Board of Directors</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Today, we are very pleased to announce two new additions to the Mozilla Corporation Board of Directors: Jambu Palaniappan and David Parry-Jones.</p>



<p>As we build the next chapter of Mozilla, we’ve been focused on bringing people onto our Board who combine deep operating experience with a real commitment to the values Mozilla stands for. Jambu and David bring deep experience building and leading technology businesses, and each brings a unique perspective to our Board.</p>



<figure class="wp-block-image size-large"><img alt="" class="wp-image-88171" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Jambu-thumnail-1024x576.png" width="1024"/></figure>



<p><strong>Jambu Palaniappan</strong> is the Chief Executive Officer of Checkatrade, where he drives the company’s mission of Powering Great Work. The home improvement platform connects consumers across the UK with quality tradespeople — every year, Checkatrade improves millions of homes and delivers billions of pounds of work to small and medium-sized businesses.</p>



<p>Before joining Checkatrade, Jambu was Managing Partner and Head of Europe at OMERS Ventures, where he invested in and supported high-growth technology companies. Earlier in his career, he spent several years at Uber and Uber Eats, joining as one of the first 100 employees and leading expansion across Europe, the Middle East, and Africa. Jambu holds a degree in Public Policy and Economics from Vanderbilt University.</p>



<figure class="wp-block-image size-large"><img alt="" class="wp-image-88204" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/David-thumbnail-1-1024x576.png" width="1024"/></figure>



<p><strong>David Parry-Jones</strong> is a board director and former Chief Revenue Officer (CRO) with more than 30 years of experience scaling technology businesses internationally. Most recently, he served as CRO at DeepL and previously held senior leadership roles at Microsoft, VMware, and Twilio. He has led large teams across diverse markets and cultures, working with both early-stage companies and global enterprises. </p>



<p>As a board member and adviser, he brings a practical perspective on growth, international expansion, and building strong teams that turn strategy into results.</p>



<p>Please join me in welcoming Jambu and David to the Mozilla Corporation Board of Directors.</p>
<p>The post <a href="https://blog.mozilla.org/en/mozilla/palaniappan-parry-jones/">Jambu Palaniappan and David Parry-Jones join the Mozilla Corporation Board of Directors</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-07T18:37:41Z</updated>
    <published>2026-10-07T18:37:41Z</published>
    <category term="From the Team"/>
    <category term="Our Work"/>
    <category term="homepage"/>
    <author>
      <name>Anthony Enzor-DeMeo</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=87761</id>
    <link href="https://blog.mozilla.org/en/mozilla/over-the-edge-2-100-days-later/" rel="alternate" type="text/html"/>
    <title>100 days later: Microsoft still steers Windows and Copilot users to Edge, everywhere the law lets it</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>One hundred days ago, Mozilla released Over The Edge 2.0, the second independent report from leading experts on deceptive design Dr. Harry Brignull and Cennydd Bowles, on how Windows, Edge, Bing, and Copilot are designed to steer people away from the browser they chose.  We published the report, and the researchers published the evidence for […]</p>
<p>The post <a href="https://blog.mozilla.org/en/mozilla/over-the-edge-2-100-days-later/">100 days later: Microsoft still steers Windows and Copilot users to Edge, everywhere the law lets it</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>One hundred days ago, Mozilla released Over The Edge 2.0, the second independent report from leading experts on deceptive design Dr. Harry Brignull and Cennydd Bowles, on how Windows, Edge, Bing, and Copilot are designed to steer people away from the browser they chose. </p>



<p>We published the <a href="https://research.mozilla.org/browser-competition/over-the-edge-2/">report</a>, and the researchers published the <a href="https://edge.brignull.com/J01/">evidence</a> for anyone to analyze. </p>



<p>Browsers are a powerful tool. So it’s no surprise that the history of the web <a href="http://www.justice.gov/atr/us-v-microsoft-courts-findings-fact">has</a> <a href="https://blog.mozilla.org/press/2015/07/safeguarding-choice-and-control-online/">many</a> <a href="https://arstechnica.com/tech-policy/2024/04/report-people-are-bailing-on-safari-after-dma-makes-changing-defaults-easier/#page-2:~:text=You%20can,not,-%2E">examples</a> of powerful platforms trying to deny people browser choice. Now, as AI reshapes our online experiences, the stakes couldn’t be higher. Browsers are a key distribution layer for AI tools and services, while still determining many of the privacy and security functionality people rely on every day. Steering people toward one browser can therefore shape which AI services reach users and the protections that come with it. </p>



<p>We also shared the report with Microsoft and talked to them about the issues raised in the report. We knew that an immediate change was unlikely, but we hoped that, when faced with independent evidence of harmful design practices impacting Windows users, they would also want better for people.</p>



<p>Instead, it became clear that Microsoft will respect user choice only when it is forced to. It is important to think about what that means for a company whose operating system runs on more than a billion machines. Microsoft’s standard for respecting people’s choices is legal compliance. Not what’s best for its users. Not its own published principles. Not what’s technically feasible. Not even what it already does for users in Europe. </p>



<p>That’s the most shocking part. Not that Microsoft engages in such tactics – <a href="https://blog.mozilla.org/press/2015/07/safeguarding-choice-and-control-online">we’ve seen that before.</a> It’s the fact that a better version of Windows already exists, and it is already available today – but only if you live in the European Economic Area (EEA), where the Digital Markets Act (DMA) forced the issue. If you live in the United States, India, the United Kingdom, or most other locations around the world, your experience and your freedom to choose for yourself are worse.</p>



<p>One hundred days later, here is what people outside of the EEA still get: </p>



<ul>
<li>The Windows 10 message “You’re almost done setting up your PC” uses tricky wording to pull people off the default they picked. </li>



<li>Windows Search and Widgets open links in Edge instead of the browser set as default. </li>



<li>Windows keeps Edge as the default for common browser file types like PDFs and SVG images, even after another browser has been set as default.<br/></li>
</ul>



<p>And people in the EEA also deserve better: </p>



<ul>
<li>Edge remains pre-pinned to the taskbar; this seems to directly violate the “principled approach to app pinning and app defaults.” </li>



<li>Copilot, Microsoft’s AI tool opens web links in a side-panel instead of the browser people chose, in every region tested, Europe included.</li>



<li>Windows Backup, the tool Microsoft uses to guide people through the migration to Windows 11, silently tries to set Edge as the default when it restores a PC and fails to properly bring the user’s own browser along. </li>
</ul>



<p>Most of the 2024 patterns are still <a href="https://research.mozilla.org/files/2024/01/Over-the-Edge-Report-January-2024.pdf">there.</a> The 2026 patterns are worse. Microsoft is using new surfaces like Copilot and the migration to Windows 11 to further undermine user choice.</p>



<p>Our ask has always been simple: First, give all Windows users the fairer designs that are live in the EEA – regardless of where they are located. Second, stop the remaining harmful design practices that persist in the EEA. That means:</p>



<ul>
<li>Stopping the remaining harmful design tactics in the EEA and ship that standard worldwide.</li>



<li>Honoring people’s browser choice everywhere it is currently ignored, including Windows Search, Widgets, Copilot, and Windows Backup restoration. </li>



<li>Applying Microsoft’s own <a href="https://blogs.windows.com/windowsexperience/2023/03/17/a-principled-approach-to-app-pinning-and-app-defaults-in-windows/">2023 app pinning principles</a> to Edge itself. </li>
</ul>



<p>The Mozilla-commissioned report has never been about intent. It’s about accountability and Microsoft’s responsibility to stop undermining people’s choices. The practices we documented need to change. Statements about intent are not a substitute for action.</p>



<p>In the past 100 days, we’ve stopped waiting for Microsoft to act. Instead, we’ve stepped up public pressure on the company to respect people’s choices.</p>



<p>We are also taking the report’s findings to regulators and policymakers. In Europe, the DMA is the only thing that has moved Microsoft. Everywhere else, the lesson is the same: Microsoft ships only when a regulator requires fairer design. </p>



<p>We hope that regulators in the US, the UK, India, and Brazil are paying attention. </p>



<p>Microsoft can do better. It already has, for people in the EEA.</p>



<p>Until it does the same in all jurisdictions, we will keep pointing out the company’s choices and the impact they have on hundreds of millions of users who want something different.</p>
<p>The post <a href="https://blog.mozilla.org/en/mozilla/over-the-edge-2-100-days-later/">100 days later: Microsoft still steers Windows and Copilot users to Edge, everywhere the law lets it</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-07T10:00:00Z</updated>
    <published>2026-10-07T10:00:00Z</published>
    <category term="Internet Policy"/>
    <category term="Our Work"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry>
    <id>discourse.mozilla.org-topic-149687</id>
    <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261006-1/149687" rel="alternate" type="text/html"/>
    <title>Happy BMO Push Day! (20261006.1)</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://github.com/mozilla-bteam/bmo/tree/release-20261006.1" rel="noopener nofollow ugc">Github Link</a></p>
<p>The following changes have been pushed to <a href="https://bugzilla.mozilla.org">bugzilla.mozilla.org</a>:</p>
<ul>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2075358">Bug 2075358</a> - Native Mojo REST endpoints serve anonymous requests when requirelogin is enabled</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2074690">Bug 2074690</a> - BMO REST API cannot set any DATE-type custom field</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2059957">Bug 2059957</a> - Reject Mojolicious-truncated request bodies before native routes dispatch</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1273193">Bug 1273193</a> - Get Comments webservice docs don’t mention author</li>
<li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2078352">Bug 2078352</a> - Selenium test 4_test_votes.t fails with Firefox ESR 153 because go_to_bug doesn’t wait for the module expand animation</li>
</ul>
<p>Discuss these changes in the <a href="https://matrix.to/#/#bmo:mozilla.org" rel="noopener nofollow ugc">BMO Matrix Room</a></p>
            <p><small>1 post - 1 participant</small></p>
            <p><a href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261006-1/149687">Read full topic</a></p></div>
    </summary>
    <updated>2026-10-06T21:43:42Z</updated>
    <published>2026-10-06T21:43:42Z</published>
    <category term="Firefox Tooling Announcements"/>
    <author>
      <name>dkl1</name>
    </author>
    <source>
      <link href="https://discourse.mozilla.org/t/happy-bmo-push-day-20261006-1/149687.rss" title="Happy BMO Push Day! (20261006.1)"/>
      <updated>2026-11-13T11:58:13Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://blog.mozilla.org/?p=87765</id>
    <link href="https://blog.mozilla.org/en/firefox/free-firefox-cybersecurity-features/" rel="alternate" type="text/html"/>
    <title>Strengthen your online security for free with Firefox</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Every October, Cybersecurity Awareness Month reminds us the importance of protecting our digital lives. The theme for 2026 is ‘Don’t Make It Easy for Them,’ with the National Cybersecurity Alliance (NCA) and the Cybersecurity and Infrastructure Security Agency (CISA) providing simple, actionable steps users can take to make it harder for cybercriminals to attack. Everyone […]</p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/free-firefox-cybersecurity-features/">Strengthen your online security for free with Firefox</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Every October, Cybersecurity Awareness Month reminds us the importance of protecting our digital lives.<br/><br/>The theme for 2026 is ‘<em>Don’t Make It Easy for Them,</em>’ with the <a href="https://www.staysafeonline.org/">National Cybersecurity Alliance</a> (NCA) and the <a href="https://www.cisa.gov/">Cybersecurity and Infrastructure Security Agency</a> (CISA) providing <a href="https://www.staysafeonline.org/cybersecurity-awareness-month">simple, actionable steps</a> users can take to make it harder for cybercriminals to attack.<br/><br/>Everyone <em>wants</em> to be safe online, but one of the most common excuses we hear is “I don’t have the time or the money to invest in it right now.” Well, we have good news: you can improve your online security easily, for the low price of $0.<br/><br/>Firefox provides several free features designed to make it easier to protect your online life and harder for cybercriminals to target you.  </p>



<h3><strong>Password manager: Use a unique password for every account</strong></h3>



<figure class="wp-block-image size-large"><img alt="" class="wp-image-87777" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Password-Manager-1024x576.png" width="1024"/></figure>



<p>Reused passwords are one of the easiest ways attackers break into multiple accounts. If one site is breached, your login details could be tested on many others.<br/><br/>Firefox’s <a href="https://www.firefox.com/en-US/features/password-manager/">free password manager</a> can generate and securely store a <a href="https://support.mozilla.org/en-US/kb/how-generate-secure-password-firefox?utm_source=www.firefox.com&amp;utm_medium=referral&amp;utm_campaign=password-manager">strong, unique password</a> per site, which is the single highest-leverage fix against password stuffing. For convenience, Firefox can automatically fill in your saved login information the next time you access a previously visited site. However, you still have the option to turn off password saving for specific websites, or completely if you’re using a shared device or simply prefer to enter it each time.<br/><br/>You can <a href="https://support.mozilla.org/en-US/kb/manage-your-logins-firefox-password-manager">manage</a> your stored logins on a singular device at any time. To get a head start, you also have the option to <a href="https://support.mozilla.org/en-US/kb/import-data-another-browser">import passwords</a> saved on several other popular browsers. In addition, you can create a <a href="https://www.mozilla.org/en-US/account/?utm_source=www.firefox.com&amp;utm_medium=referral&amp;utm_campaign=sync">free Mozilla account </a>to safely <a href="https://www.firefox.com/en-US/features/sync/">sync</a> them across your signed-in devices. </p>



<h3><strong>VPN: Privacy built into the browser</strong></h3>



<figure class="wp-block-image size-large"><img alt="" class="wp-image-87789" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/VPN-1024x576.png" width="1024"/></figure>



<p>Imagine you’re settling into a corner table at a bustling airport cafe, checking some emails on your phone before you board your flight. Or perhaps you took your laptop to the campus library to finally start that research paper you’ve been putting off. Maybe you’re polishing off that last presentation slide between sessions at an out-of-state conference.<br/><br/>While these moments are routine, connecting to public Wi-Fi anywhere can open a small window of risk – as your IP address, approximate location, and browsing activity can be more exposed on networks you don’t control.<br/><br/>That’s where Firefox’s <a href="https://www.firefox.com/landing/vpn/">free built-in, browser-based VPN</a> steps in. While Firefox already encrypts your traffic with HTTPS, the built-in VPN feature routes your browsing traffic through a proxy network, hiding your IP address before it reaches a website. This means the sites you visit will see a proxy IP address instead of your own. It offers an industry-leading 50 gigabytes of free VPN-browsing each month, with no extension or extra app to install. Simply sign in, turn it on, and start browsing.<br/><br/>Firefox’s free built-in VPN first launched on desktop in March, later <a href="https://support.mozilla.org/en-US/kb/mobile-android-vpn">expanding to Android</a> in July. Unlike a standalone or full-service VPN, it’s designed specifically to protect your browsing traffic within Firefox, not your entire device. This means apps, downloads, and other system traffic are not routed through the browser-based VPN. For people who need broader, device-wide VPN protection, Mozilla also offers a separate <a href="https://www.mozilla.org/products/vpn/">paid VPN service</a>.<br/><br/>You can check the full list of regions where built-in VPN in Firefox is currently available <a href="https://support.mozilla.org/en-US/kb/unable-find-built-vpn-firefox">here</a>, and learn more about the differences between Firefox’s free built-in VPN and Mozilla VPN <a href="https://support.mozilla.org/en-US/kb/built-in-vpn">here</a>. </p>



<h3><strong>Relay: Contain the damage of any one breach</strong></h3>



<figure class="wp-block-image size-large"><img alt="" class="wp-image-87800" height="576" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2026/10/Relay-1024x576.png" width="1024"/></figure>



<p>Think about how often you give out your personal email address – for an online purchase, RSVPing to an event, or signing up to a new app. Each time, you trust the site owner will protect your information, but, spam piles up and breaches can still happen – even when you think you’re being careful.<br/><br/><a href="https://relay.firefox.com/">Firefox Relay</a> gives you a smarter way to share. Instead of handing out your real email address, this feature provides secure, random <a href="http://support.mozilla.org/en-US/kb/create-email-mask-through-firefox-relay">email masks</a> to use any time a website, store, or app asks you for your information. It forwards messages to your real email, while keeping your identity hidden to senders. This means if one service gets compromised, your other accounts stay safe.<br/><br/>You can also use Relay in the U.S. and Canada to <a href="https://support.mozilla.org/en-US/kb/mask-your-phone-number-relay-phone-masking">shield your phone number</a>, so you can receive calls and texts through masks and reply without exposing your real number.<br/><br/>The best part? To make protecting your privacy even easier, Firefox increased its limit to 50 free email masks earlier this year, allowing you to shield dozens of logins at no cost. </p>



<h3><strong>Browse freely: Firefox protects you by default</strong></h3>



<p>Even if you sometimes forget to use Firefox protection tools like password manager, VPN, and Relay, there are multiple always-on features operating within the browser to help keep your session secure and private. These include <a href="https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop">enhanced tracking protection</a> to block hidden scripts and known trackers that follow you across the web, <a href="https://www.firefox.com/en-US/features/block-fingerprinting/">browser fingerprinting protection</a> to prevent sites from building a unique profile of your device, and <a href="https://support.mozilla.org/en-US/kb/how-does-phishing-and-malware-protection-work">warnings</a> about deceptive or malicious websites.<br/><br/>Together, Firefox’s individual and always-on security features work to help keep your browsing safe and your data private. So, this Cybersecurity Awareness Month, take a moment to build new habits, try out our free cybersecurity tools, and make life more difficult for cybercriminals. Small steps add up, and we are here to help. Stay safe, stay smart, and keep exploring the web with confidence on Firefox. </p>
<p>The post <a href="https://blog.mozilla.org/en/firefox/free-firefox-cybersecurity-features/">Strengthen your online security for free with Firefox</a> appeared first on <a href="https://blog.mozilla.org/en/">The Mozilla Blog</a>.</p></div>
    </content>
    <updated>2026-10-06T16:00:00Z</updated>
    <published>2026-10-06T16:00:00Z</published>
    <category term="Firefox"/>
    <category term="Firefox Features"/>
    <category term="Privacy &amp; Security"/>
    <category term="Tips and Tricks"/>
    <category term="cybersecurity"/>
    <category term="export"/>
    <category term="homepage"/>
    <author>
      <name>Mozilla</name>
    </author>
    <source>
      <id>https://blog.mozilla.org/en/</id>
      <link href="https://blog.mozilla.org/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://blog.mozilla.org/en/" rel="alternate" type="text/html"/>
      <subtitle>News and Updates about Mozilla</subtitle>
      <title>The Mozilla Blog</title>
      <updated>2026-11-12T13:56:23Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-us">
    <id>https://eqrion.net/wasm-stack-switching-talk/</id>
    <link href="https://eqrion.net/wasm-stack-switching-talk/" rel="alternate" type="text/html"/>
    <title>Wasm Stack Switching in SpiderMonkey</title>
    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>WebAssembly <a href="https://github.com/WebAssembly/stack-switching">stack switching</a> in SpiderMonkey is the most complex feature I’ve ever implemented.</p>
<p>It’s one of those projects where you get lost and start rethinking the basics, like “what is the stack even really?”</p>
<p>It was fun to give a talk on it. Check out the recording below, or <a href="https://www.youtube.com/watch?v=OvYFHH9AxOw">on YouTube</a>.</p>
<div style="padding-bottom: 56.25%; height: 0; overflow: hidden;">
			
		</div></div>
    </summary>
    <updated>2026-10-06T15:00:00Z</updated>
    <published>2026-10-06T15:00:00Z</published>
    <source>
      <id>https://eqrion.net/tags/mozilla/</id>
      <author>
        <name>Ryan Hunt</name>
      </author>
      <link href="https://eqrion.net/tags/mozilla/" rel="alternate" type="text/html"/>
      <link href="https://eqrion.net/tags/mozilla/index.xml" rel="self" type="application/rss+xml"/>
      <subtitle>Recent content in Mozilla on Ryan Hunt's Blog</subtitle>
      <title>Mozilla on Ryan Hunt's Blog</title>
      <updated>2026-10-06T15:00:00Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:kDQYPzzMuIY</id>
    <link href="https://www.youtube.com/watch?v=kDQYPzzMuIY" rel="alternate" type="text/html"/>
    <title>Towards a Telemetry Taxonomy</title>
    <summary>Leif Oines talks about an effort to define a more complete taxonomy for Mozilla's data.</summary>
    <updated>2026-10-05T18:47:43Z</updated>
    <published>2020-12-11T15:15:10Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:Y3IOY-kmk70</id>
    <link href="https://www.youtube.com/watch?v=Y3IOY-kmk70" rel="alternate" type="text/html"/>
    <title>Data Club Talk: Jan-Erik Rediger - The Glean UniFFI migration and how no one noticed</title>
    <summary>Given at the Mozilla Data Club on August 12th, 2022.</summary>
    <updated>2026-10-05T15:53:26Z</updated>
    <published>2022-08-15T12:01:56Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry xml:lang="en-US">
    <id>https://fxdx.dev/?p=566</id>
    <link href="https://fxdx.dev/firefox-webdriver-newsletter-157/" rel="alternate" type="text/html"/>
    <title>Firefox WebDriver Newsletter 157</title>
    <summary>WebDriver is a remote control interface that enables introspection and control of user agents. As such, it can help developers...</summary>
    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p id="block-625ec41a-ebba-4559-8294-ab8d43d24728"><em>WebDriver is a remote control interface that enables introspection and control of user agents. As such, it can help developers to verify that their websites are working and performing well with all major browsers. The protocol is standardized by the<a href="https://www.w3.org/"> W3C</a> and consists of two separate specifications:<a href="https://w3c.github.io/webdriver/"> WebDriver classic</a> (HTTP) and the new<a href="https://w3c.github.io/webdriver-bidi/"> WebDriver BiDi</a> (Bi-Directional).</em></p>



<p id="block-dae47e7f-6eed-4378-93bf-87f83964774b"><em>This newsletter gives an overview of the work we’ve done as part of the Firefox 157 release cycle</em>.</p>



<h3>Contributions</h3>



<p id="block-0cd229aa-56a4-4acd-88c9-6c0aed1f91ef">Firefox is an open source project, and we are always happy to receive external code contributions to our WebDriver implementation. We want to give special thanks to everyone who filed issues, bugs, and submitted patches.</p>



<p id="block-90d46142-b130-4359-9a16-b2e82ef91416">In Firefox 157, multiple WebDriver bugs were fixed by contributors:</p>



<ul id="block-b10e4a7c-ea74-4805-9e31-4bb37551e682">
<li>Sameem <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1958852">merged two internal helpers</a> (remote/shared/Sync.sys.mjs and remote/marionette/sync.sys.mjs), which removed some code duplication.</li>



<li>Khalid AlHaddad <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2044153">unified the navigation commands in Marionette and WebDriver BiDi</a> to always initiate navigations via browsingContext.loadURI().</li>



<li>Khalid AlHaddad updated the WebDriver BiDi client used by WebDriver tests <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2046450">so that browsing_context.locate_nodes returns the nodes array directly</a> instead of the enclosing result object, matching the updated command response.</li>
</ul>



<p id="block-1dca3827-38c3-478d-a4b2-a1e39af880f5">WebDriver code is written in JavaScript, Python, and Rust, so any web developer can contribute! Read <a href="https://firefox-source-docs.mozilla.org/setup/index.html">how to set up the work environment</a> and check<a href="https://codetribute.mozilla.org/projects/automation"> the list of mentored issues</a> for Marionette or the <a href="https://codetribute.mozilla.org/languages/javascript?project%3DWebDriver%2520BiDi">list of mentored JavaScript bugs for WebDriver BiDi</a>. Join <a href="https://chat.mozilla.org/#/room/#webdriver:mozilla.org">our chatroom</a> if you need any help to get started!</p>



<h3>All Changes</h3>



<p>A complete list of developer-facing changes included in this Firefox release is available in the <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/157#webdriver_conformance_webdriver_bidi_marionette">MDN Firefox 157 Release Notes</a>.</p></div>
    </content>
    <updated>2026-10-05T14:21:23Z</updated>
    <published>2026-10-05T14:21:23Z</published>
    <category term="Release Notes"/>
    <category term="Remote Protocols"/>
    <category term="WebDriver BiDi"/>
    <category term="WebDriver Classic"/>
    <author>
      <name>Alexandra Borovova</name>
    </author>
    <source>
      <id>https://fxdx.dev</id>
      <logo>https://fxdx.dev/files/2023/04/cropped-Fx-Browser-Developer-icon-fullColor-512-32x32.png</logo>
      <link href="https://fxdx.dev/feed/" rel="self" type="application/rss+xml"/>
      <link href="https://fxdx.dev" rel="alternate" type="text/html"/>
      <subtitle>Your Go-To Resource for Web Development &amp; Compatibility</subtitle>
      <title>Firefox Developer Experience</title>
      <updated>2026-10-13T18:04:41Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:tzDQSnK45dA</id>
    <link href="https://www.youtube.com/watch?v=tzDQSnK45dA" rel="alternate" type="text/html"/>
    <title>Outreachy Mentorship: A Retrospective</title>
    <summary>Will Lachance does a retrospective on the Glean Dictionary outreachy internship. 

See also "Linh's Outreachy Internship Highlights" https://www.youtube.com/watch?v=UJdIkHDPgGQ

To learn more about Outreachy, see https://www.outreachy.org/</summary>
    <updated>2026-10-05T10:59:51Z</updated>
    <published>2021-03-29T20:25:24Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:myHH89j0JQU</id>
    <link href="https://www.youtube.com/watch?v=myHH89j0JQU" rel="alternate" type="text/html"/>
    <title>Responsible Data Collection is Good, Actually (Ubisoft Data Summit 2021)</title>
    <summary>Firefox Telemetry Engineer and Data Steward Chris H-C (:chutten) gives a talk at Ubisoft's Data Summit 2021 about how Responsible Data Collection as practised at Mozilla makes cataloguing easy, stops instrumentation mistakes before they ship, and allows you to build self-serve analysis tooling that gets everyone invested in data quality. Oh, and it's cheaper, too.</summary>
    <updated>2026-10-04T23:55:36Z</updated>
    <published>2021-07-06T19:54:22Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:nZupfJy6I0A</id>
    <link href="https://www.youtube.com/watch?v=nZupfJy6I0A" rel="alternate" type="text/html"/>
    <title>Data Club: Jan-Erik Rediger - Little Bobby Tables - from metrics.yaml to data-filled columns</title>
    <summary>A short story about Little Bobby Tables and how we know what data to fill in where.</summary>
    <updated>2026-10-04T19:17:37Z</updated>
    <published>2024-02-05T15:18:38Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:V5FgVbxm-cc</id>
    <link href="https://www.youtube.com/watch?v=V5FgVbxm-cc" rel="alternate" type="text/html"/>
    <title>Data Club Lightning Talk: Jan-Erik Rediger - Your personal Glean data pipeline</title>
    <summary>This talk was given as part of the Data Club Lightning Talk Session on February 11th, 2022.
More on https://blog.mozilla.org/data/2022/02/25/this-week-in-glean-your-personal-glean-data-pipeline
Information about Glean: https://mozilla.github.io/glean/book/index.html</summary>
    <updated>2026-10-04T16:52:51Z</updated>
    <published>2022-02-25T13:41:22Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:k1cvnVKOmM8</id>
    <link href="https://www.youtube.com/watch?v=k1cvnVKOmM8" rel="alternate" type="text/html"/>
    <title>GLAM Datasets</title>
    <summary>Marina Samuel and Anthony Miyaguchi talk about the ETL pipeline created for the GLAM project (https://github.com/mozilla/glam).</summary>
    <updated>2026-10-04T07:56:23Z</updated>
    <published>2021-01-15T16:09:41Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:wlRaTHhctrA</id>
    <link href="https://www.youtube.com/watch?v=wlRaTHhctrA" rel="alternate" type="text/html"/>
    <title>Data Club: Jeff Silverman - Data Science &amp; Astronomy: AAS 243 &amp; ATDS 6</title>
    <updated>2026-10-04T05:05:34Z</updated>
    <published>2024-02-05T15:18:38Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:aGjrXhXNRq8</id>
    <link href="https://www.youtube.com/watch?v=aGjrXhXNRq8" rel="alternate" type="text/html"/>
    <title>Introducing Glean Annotations</title>
    <summary>Leif Oines and Will Lachance introduce Glean Annotations: a process and technology for curating and communicating knowledge about the data we collect in Mozilla's products.</summary>
    <updated>2026-10-03T19:51:35Z</updated>
    <published>2021-04-19T18:05:52Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:y7msgjoLjNk</id>
    <link href="https://www.youtube.com/watch?v=y7msgjoLjNk" rel="alternate" type="text/html"/>
    <title>Mozillians sharing the 2021 SciPy Conference experience</title>
    <summary>The 2021 SciPy conference (https://www.scipy2021.scipy.org/) involved the showcasing of the latest open source Python projects for advancement in scientific computing. Mozilla was a diversity sponsor and a few Mozillians attended and shared their experience of the event.</summary>
    <updated>2026-10-02T04:24:13Z</updated>
    <published>2021-09-21T19:58:42Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry>
    <id>yt:video:E5j6BoxZ-7w</id>
    <link href="https://www.youtube.com/watch?v=E5j6BoxZ-7w" rel="alternate" type="text/html"/>
    <title>Last Lecture: Writing the Data Docs</title>
    <summary>Will Lachance gives a last lecture on writing data documentation at Mozilla.</summary>
    <updated>2026-10-02T03:38:29Z</updated>
    <published>2021-12-20T14:58:29Z</published>
    <author>
      <name>Mozilla Data</name>
      <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
    </author>
    <source>
      <id>yt:channel:S1zp4AVNvykWzPC-vB_Daw</id>
      <author>
        <name>Mozilla Data</name>
        <uri>https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw</uri>
      </author>
      <link href="http://www.youtube.com/feeds/videos.xml?channel_id=UCS1zp4AVNvykWzPC-vB_Daw" rel="self" type="application/atom+xml"/>
      <link href="https://www.youtube.com/channel/UCS1zp4AVNvykWzPC-vB_Daw" rel="alternate" type="text/html"/>
      <title>Mozilla Data</title>
      <updated>2020-03-03T15:46:33Z</updated>
    </source>
  </entry>

  <entry xml:lang="en">
    <id>https://blog.rust-lang.org/2026/10/02/demoting-i686-windows-targets-to-std-only/</id>
    <link href="https://blog.rust-lang.org/2026/10/02/demoting-i686-windows-targets-to-std-only/" rel="alternate" title="Demoting i686 Windows targets to std-only" type="text/html"/>
    <title xml:lang="en">Demoting i686 Windows targets to std-only</title>
    <content type="xhtml" xml:lang="en"><div xmlns="http://www.w3.org/1999/xhtml"><p>With Rust 1.100.0, the following changes to 32-bit Windows targets will happen:</p>
<ul>
<li><code>i686-pc-windows-msvc</code> Tier 1 <em>with</em> host tools target will be demoted to Tier 1 <em>without</em> host tools.</li>
<li><code>i686-pc-windows-gnu</code> Tier 2 <em>with</em> host tools target will be demoted to Tier 2 <em>without</em> host tools.</li>
</ul>
<p>Builds of the standard library will continue to be distributed, but host tools such as the compiler will be no longer available. <code>i686-pc-windows-msvc</code> as a Tier 1 target still undergoes CI testing.</p>
<p>To build 32-bit Windows binaries, cross-compiling from a still-supported host toolchain (such as a 64-bit Windows ones) will be required from now on.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/02/demoting-i686-windows-targets-to-std-only/#background"/>
Background</h3>
<p>Desktop and Server 32-bit only x86 CPUs are no longer sold for over 15 years, and general 32-bit Windows support has ended in October 2025. This means that the development platforms these targets are meant for hardly exist these days, and even if they do exist they typically aren't capable enough for development.</p>
<p>Even on the modern x86_64 hardware, building i686 Windows toolchains has proven to be problematic. We have encountered compiler binaries crashing when built with the i686 MSVC target, and the GNU C++ toolchain failing with OOMs during LLVM build.</p>
<p>Considering all these things, cross-compiling these targets from a better supported one is what we have found to be the best solution forward. As part of that, we stopped producing host tools for these targets. For the time being, the prebuilt standard library is still available, and in case of <code>i686-pc-windows-msvc</code> still tested on CI.</p>
<h3><a class="anchor" href="https://blog.rust-lang.org/2026/10/02/demoting-i686-windows-targets-to-std-only/#what-changes"/>
What Changes?</h3>
<p>After Rust 1.100, it will no longer be possible to install toolchains on 32-bit Windows hosts. We recommend cross-compiling from a still-supported host (such as a 64-bit Windows toolchain) instead. Other 32-bit platforms are not impacted by this change.</p>
<p>For more details about these demotions, see <a href="https://github.com/rust-lang/rfcs/blob/51783df9a76c355de7ceebeae101cba47f8ca463/text/3999-std-only-i686-msvc.md" rel="external">RFC 3999</a> for <code>i686-pc-windows-msvc</code> demotion, and <a href="https://github.com/rust-lang/compiler-team/issues/1020" rel="external">MCP 1020</a> for <code>i686-pc-windows-gnu</code> demotion.</p></div>
    </content>
    <updated>2026-10-02T00:00:00Z</updated>
    <published>2026-10-02T00:00:00Z</published>
    <author>
      <name>Mateusz Mikuła, Ralf Jung</name>
    </author>
    <source>
      <id>https://blog.rust-lang.org/</id>
      <author>
        <name>Maintained by the Rust Teams.</name>
        <uri>https://github.com/rust-lang/blog.rust-lang.org/</uri>
      </author>
      <link href="https://blog.rust-lang.org/feed.xml" rel="self" type="application/atom+xml"/>
      <link href="https://blog.rust-lang.org/" rel="alternate" type="text/html"/>
      <subtitle xml:lang="en">Empowering everyone to build reliable and efficient software.</subtitle>
      <title xml:lang="en">Rust Blog</title>
      <updated>2026-11-13T09:01:38Z</updated>
    </source>
  </entry>
</feed>
