Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://planet.mozilla.org/rss20.xml

  1. <?xml version="1.0"?>
  2. <rss version="2.0"
  3. xmlns:dc="http://purl.org/dc/elements/1.1/"
  4. xmlns:atom="http://www.w3.org/2005/Atom"
  5. >
  6.  
  7. <channel>
  8. <title>Planet Mozilla</title>
  9. <link>https://planet.mozilla.org/</link>
  10. <language>en</language>
  11. <description>Planet Mozilla - https://planet.mozilla.org/</description>
  12. <atom:link rel="self" href="https://planet.mozilla.org/rss20.xml" type="application/rss+xml"/>
  13.  
  14. <item>
  15. <title>Mike Taylor: A new, new logo for the W3C</title>
  16. <guid isPermaLink="true">https://miketaylr.com/posts/2025/10/new-new-logo-for-w3c.html</guid>
  17. <link>https://miketaylr.com/posts/2025/10/new-new-logo-for-w3c.html</link>
  18. <description>&lt;p&gt;In an effort to pivot this site into a full on graphic design side business after 2 blog posts about logos in a row (hit me up exclusivly on &lt;a href=&quot;https://fishbrain.com/anglers/miketaylr&quot;&gt;FB&lt;/a&gt; to request a consultation), I thought I would reveal my new, new logo for the W3C.&lt;/p&gt;
  19.  
  20. &lt;p&gt;It turns out they recently launched a new one, but &lt;a href=&quot;https://lists.w3.org/Archives/Public/www-archive/2025Oct/thread.html&quot;&gt;some folks don’t love it&lt;/a&gt;. As an artist, it’s not my job to critique other art, but instead to offer my own compelling vision for the web.&lt;/p&gt;
  21.  
  22. &lt;p&gt;&lt;img alt=&quot;a shitty drawing of a w, the word three spelled out, and followed by a period and the letter c&quot; src=&quot;https://miketaylr.com/posts/assets/w3c.png&quot; style=&quot;border: 1px solid gray;&quot; /&gt;&lt;/p&gt;
  23.  
  24. &lt;p&gt;I shouldn’t have to explain why I went with the classic dark blue and asparagus colors—that much is obvious. And of course, turning c into a file extension as a reminder that NCSA Mosaic was written in C (I didn’t go with &lt;a href=&quot;https://en.wikipedia.org/wiki/WorldWideWeb&quot;&gt;WorldWideWeb&lt;/a&gt; because that was written in Objective C and &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;.m&lt;/code&gt; kinda messes it all up).&lt;/p&gt;</description>
  25. <pubDate>Sat, 25 Oct 2025 04:00:00 +0000</pubDate>
  26. <dc:creator>Mike Taylor</dc:creator>
  27. </item>
  28. <item>
  29. <title>Mozilla Localization (L10N): Localizer spotlight: Bogo</title>
  30. <guid isPermaLink="false">https://blog.mozilla.org/l10n/?p=1789</guid>
  31. <link>https://blog.mozilla.org/l10n/2025/10/24/localizer-spotlight-bogo/</link>
  32. <description>&lt;p&gt;&lt;strong&gt;About you&lt;/strong&gt;&lt;/p&gt;
  33. &lt;p&gt;My name is &lt;a href=&quot;https://pontoon.mozilla.org/contributors/bogomil/&quot;&gt;Bogomil&lt;/a&gt; but people call me Bogo, and I am a translator for the Bulgarian locale. I think I got involved with the Mozilla project back in 2005 when I wrote a small search add-on/script. I became more active around 2008-2009 and with just a few gaps until this day.&lt;/p&gt;
  34. &lt;p&gt;I am European. I was born in Bulgaria, but I have been living for a long time in the Czech Republic. Bulgarian is my main language, but sometimes I contribute to localization projects in Turkish, Romanian, Macedonian and Czech.&lt;/p&gt;
  35. &lt;p&gt;&lt;a href=&quot;https://blog.mozilla.org/l10n/files/2025/10/image2.jpg&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;aligncenter wp-image-1790 size-large&quot; height=&quot;338&quot; src=&quot;https://blog.mozilla.org/l10n/files/2025/10/image2-600x338.jpg&quot; width=&quot;600&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
  36. &lt;p&gt;&lt;strong&gt;Q&amp;amp;A&lt;/strong&gt;&lt;/p&gt;
  37. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; What inspired you to join the Mozilla localization community?&lt;/em&gt;&lt;/p&gt;
  38. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; As I mentioned &lt;a href=&quot;https://www.thunderbird.net/participate/&quot;&gt;here&lt;/a&gt; I decided to start localizing software because I knew some people had trouble using it in other languages. I believe everyone deserves the right to use software in a language they understand which helps them to get the maximum value out of it. As for Mozilla in particular I believe in &lt;a href=&quot;https://www.mozilla.org/mission/&quot;&gt;the mission&lt;/a&gt; and this is the most efficient way for me to contribute.&lt;/p&gt;
  39. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; How do you solve challenges like bugs or workflow hiccups, especially when collaborating virtually?&lt;/em&gt;&lt;/p&gt;
  40. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; Since we are a small team for the Bulgarian localizations we are almost always in sync on how to translate the strings. &lt;span class=&quot;notranslate&quot;&gt;We are following some basic rules, such as using a common dictionary and instructions on how to localize software in Bulgarian (shared across multiple FOSS projects),&lt;/span&gt; set 15+ years ago and that are still relevant. When we have a conflict, I usually count on the team managers to share their wisdom, because they have a bit more knowledge than the rest of us.&lt;/p&gt;
  41. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; Which projects or new product features were you most excited about this year, and why?&lt;/em&gt;&lt;/p&gt;
  42. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; In the last year I contributed mainly to the Thunderbird project. The items that are most exciting to me are:&lt;/p&gt;
  43. &lt;ul&gt;
  44. &lt;li&gt;That finally we decided to remove the word “Junk” and replace it with “Spam”, I think this is self-explanatory 🙂&lt;/li&gt;
  45. &lt;li&gt;The new &lt;a href=&quot;https://blog.thunderbird.net/2025/04/video-the-new-account-hub/&quot;&gt;Account Hub&lt;/a&gt; which improves significantly the consumer’s experience and their onboarding into the beautiful world of the free email. Free as in Freedom.&lt;/li&gt;
  46. &lt;li&gt;I am also excited about all the things in the &lt;a href=&quot;https://developer.thunderbird.net/planning/roadmap&quot;&gt;roadmap&lt;/a&gt; to come.&lt;/li&gt;
  47. &lt;/ul&gt;
  48. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; What tips, tools, or habits help you succeed as a localizer?&lt;/em&gt;&lt;/p&gt;
  49. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; If you look at my Pontoon &lt;a href=&quot;https://pontoon.mozilla.org/contributors/bogomil/&quot;&gt;profile&lt;/a&gt;, you will see that for the last 2 months I contributed every day. I find this habit very useful for me, because it keeps me focused on my goal for consistently improving the localized experience.&lt;/p&gt;
  50. &lt;p&gt;Another item is that I like to provide a better experience to the mobile users. I often test and fix labels in &lt;a href=&quot;https://play.google.com/store/apps/details?id=net.thunderbird.android&quot;&gt;Thunderbird for Android&lt;/a&gt; which, even translated correctly, are too long for a mobile phone UI.&lt;/p&gt;
  51. &lt;p&gt;And lastly, I love to engage with the community and ask them for help when we finish a section or a product. Last year we asked the Bulgarian community to help us validate a localization available in the beta version and we got some very helpful feedback.&lt;/p&gt;
  52. &lt;p&gt;&lt;strong&gt;Something fun&lt;/strong&gt;&lt;/p&gt;
  53. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; Could you share a few fun or unexpected facts about yourself that people might not know?&lt;/em&gt;&lt;/p&gt;
  54. &lt;ul&gt;
  55. &lt;li&gt;I ran for the European Parliament in 2009 with the intention to fight for our digital rights.&lt;/li&gt;
  56. &lt;li&gt;I was on almost every media in the world in 2012 when I bought the data of millions of users for $5! &lt;a href=&quot;https://www.forbes.com/sites/andygreenberg/2012/10/25/facebook-investigating-how-bulgarian-man-bought-1-1-million-users-email-addresses-for-five-dollars/&quot;&gt;This&lt;/a&gt; is the Forbes article.&lt;/li&gt;
  57. &lt;li&gt;I am a heavy metal fan and you can find me in underground clubs, enjoying bands you have never heard of.&lt;/li&gt;
  58. &lt;li&gt;Apart from technology I am an artist – I produced and performed my own theater play and shot a movie in Prague.&lt;/li&gt;
  59. &lt;li&gt;I realized my dream to have an opening talk at &lt;a href=&quot;https://fosdem.org/&quot;&gt;FOSDEM&lt;/a&gt;. I was opening the Sunday session… but still!&lt;/li&gt;
  60. &lt;/ul&gt;
  61. &lt;p&gt;&lt;a href=&quot;https://blog.mozilla.org/l10n/files/2025/10/image3.jpg&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;aligncenter wp-image-1791 size-large&quot; height=&quot;338&quot; src=&quot;https://blog.mozilla.org/l10n/files/2025/10/image3-600x338.jpg&quot; width=&quot;600&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description>
  62. <pubDate>Fri, 24 Oct 2025 20:54:52 +0000</pubDate>
  63. <dc:creator>Delphine</dc:creator>
  64. </item>
  65. <item>
  66. <title>Mozilla Thunderbird: Your Workflow, Supercharged</title>
  67. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3983</guid>
  68. <link>https://blog.thunderbird.net/2025/10/your-workflow-supercharged/</link>
  69. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;319&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Screenshot-2025-10-24-at-12.46.53 PM.png&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  70. &lt;p&gt;Extensions make &lt;a href=&quot;https://www.thunderbird.net/en-US/&quot;&gt;Thunderbird&lt;/a&gt; truly yours, moving at your pace and reflecting your priorities. Thunderbird’s flexibility means you can tailor the app to how you actually work. We’ll cover tools for efficiency, consistency, and visibility so every send is faster and better informed, your future self will thank you.  &lt;/p&gt;
  71.  
  72.  
  73.  
  74. &lt;h3&gt;&lt;strong&gt;Clippings&lt;/strong&gt;&lt;/h3&gt;
  75.  
  76.  
  77.  
  78. &lt;p&gt;We’ve all been there, retyping the same line for the hundredth time and wondering if there’s a better way. &lt;a href=&quot;https://services.addons.thunderbird.net/eN-US/thunderbird/addon/clippings-tb/&quot;&gt;Clippings&lt;/a&gt; lets you save text once and reuse it anywhere you compose in Thunderbird. You can organize by folders, apply color labels, and search by name with autocomplete, so the right text is always a couple of keystrokes away.&lt;/p&gt;
  79.  
  80.  
  81.  
  82. &lt;p&gt;When you paste a clipping, you can include fill‑in prompts for names, dates, or custom notes, and even keep simple HTML formatting and images when needed. It’s like a spellbook for your inbox–summon, swap, send. &lt;/p&gt;
  83.  
  84.  
  85.  
  86. &lt;p&gt;Below is a quick glance at how Clippings can help you: &lt;/p&gt;
  87.  
  88.  
  89.  
  90. &lt;ul&gt;
  91. &lt;li&gt;Save and paste reusable snippets anywhere you write—no more repeat typing.&lt;br /&gt;&lt;/li&gt;
  92.  
  93.  
  94.  
  95. &lt;li&gt;Include prompts for names, dates, or custom notes; HTML and inline images.&lt;br /&gt;&lt;/li&gt;
  96.  
  97.  
  98.  
  99. &lt;li&gt;Organize with folders and labels; find snippets fast with autocomplete.&lt;br /&gt;&lt;/li&gt;
  100.  
  101.  
  102.  
  103. &lt;li&gt;Paste instantly with keyboard shortcuts; import, export, or sync your library.&lt;/li&gt;
  104. &lt;/ul&gt;
  105.  
  106.  
  107. &lt;div class=&quot;wp-block-image is-style-default&quot;&gt;
  108. &lt;figure class=&quot;alignleft size-large is-resized&quot;&gt;&lt;a href=&quot;https://services.addons.thunderbird.net/eN-US/thunderbird/addon/clippings-tb/&quot;&gt;&lt;img alt=&quot;Link to Thunderbird Add-on library.&quot; class=&quot;wp-image-4000&quot; height=&quot;217&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Screenshot-2025-10-24-at-12.40.49 PM-1-600x217.png&quot; style=&quot;width: 144px; height: auto;&quot; title=&quot;TB Add-on Link&quot; width=&quot;600&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;&lt;/div&gt;
  109.  
  110.  
  111. &lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;With the content process streamlined, now for a sign‑off that keeps your tone on track. &lt;br /&gt;&lt;/p&gt;
  112.  
  113.  
  114.  
  115. &lt;h3&gt;&lt;strong&gt;Signature Switch&lt;/strong&gt;&lt;/h3&gt;
  116.  
  117.  
  118.  
  119. &lt;p&gt;We rotate hats as we write: buttoned‑up for clients, warm for teammates, and careful punctuation for legal. &lt;a href=&quot;https://addons.thunderbird.net/en-US/thunderbird/addon/signature-switch/&quot;&gt;Signature Switch&lt;/a&gt; helps you with that. Keep multiple signatures, and swap them in with a click or shortcut right from the composer. Turn a signature off entirely, pick from your saved set, or append a different one without retyping a thing.&lt;br /&gt;&lt;br /&gt;Use plain text for simplicity, or HTML with images and links for a more professional finish. Because everything is accessible while you write, choosing the right signature doesn’t break your flow—and it helps keep branding and tone consistent across messages. One click and your signature goes from handshake to high‑five.&lt;/p&gt;
  120.  
  121.  
  122.  
  123. &lt;p&gt;Below is a quick glance at how Signature Switch can help you: &lt;/p&gt;
  124.  
  125.  
  126.  
  127. &lt;ul&gt;
  128. &lt;li&gt;Switch signatures on/off or choose from your saved set, no retyping.&lt;br /&gt;&lt;/li&gt;
  129.  
  130.  
  131.  
  132. &lt;li&gt;Match by recipient, account, or context; keep tone aligned.&lt;br /&gt;&lt;/li&gt;
  133.  
  134.  
  135.  
  136. &lt;li&gt;Use plain text or polished HTML with images and links.&lt;br /&gt;&lt;/li&gt;
  137.  
  138.  
  139.  
  140. &lt;li&gt;Access quickly from the composer toolbar or menu while you write.&lt;/li&gt;
  141. &lt;/ul&gt;
  142.  
  143.  
  144. &lt;div class=&quot;wp-block-image is-style-default&quot;&gt;
  145. &lt;figure class=&quot;alignleft size-large is-resized&quot;&gt;&lt;a href=&quot;https://addons.thunderbird.net/en-US/thunderbird/addon/signature-switch/&quot;&gt;&lt;img alt=&quot;Link to Thunderbird Add-on library.&quot; class=&quot;wp-image-4000&quot; height=&quot;217&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Screenshot-2025-10-24-at-12.40.49 PM-1-600x217.png&quot; style=&quot;width: 144px; height: auto;&quot; title=&quot;TB Add-on Link&quot; width=&quot;600&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;&lt;/div&gt;
  146.  
  147.  
  148. &lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;With the sign‑off sorted, now let’s measure the results. &lt;/p&gt;
  149.  
  150.  
  151.  
  152. &lt;h3&gt;&lt;strong&gt;ThirdStat&lt;/strong&gt;s&lt;/h3&gt;
  153.  
  154.  
  155.  
  156. &lt;p&gt;Looking for a way to interpret email trends on more than just vibes alone? &lt;a href=&quot;https://addons.thunderbird.net/en-US/thunderbird/addon/thirdstats/&quot;&gt;ThirdStats&lt;/a&gt; turns your mailbox into clear, local analytics that reveal how your email work actually behaves, when volume spikes, which hours are busiest, how response times trend, and which folders see the most activity. Interactive charts make patterns easy to spot at a glance. &lt;/p&gt;
  157.  
  158.  
  159.  
  160. &lt;p&gt;You can compare accounts side by side, adjust date ranges to see changes over time, and focus on a specific folder for deeper context. All processing happens on your device with read‑only access, so your data isn’t transmitted elsewhere. It’s a simple, private way to understand your workload and time your effort better. &lt;/p&gt;
  161.  
  162.  
  163.  
  164. &lt;p&gt;Below is a quick glance at how ThirdStats can help you: &lt;/p&gt;
  165.  
  166.  
  167.  
  168. &lt;ul&gt;
  169. &lt;li&gt;Visualize volume, peak hours, response times, and folder activity with interactive charts.&lt;br /&gt;&lt;/li&gt;
  170.  
  171.  
  172.  
  173. &lt;li&gt;Compare accounts side by side; filter by date ranges; view by folder.&lt;br /&gt;&lt;/li&gt;
  174.  
  175.  
  176.  
  177. &lt;li&gt;Keep it private: analysis runs locally with read‑only access, no external transmission.&lt;/li&gt;
  178. &lt;/ul&gt;
  179.  
  180.  
  181. &lt;div class=&quot;wp-block-image is-style-default&quot;&gt;
  182. &lt;figure class=&quot;alignleft size-large is-resized&quot;&gt;&lt;a href=&quot;https://addons.thunderbird.net/en-US/thunderbird/addon/thirdstats/&quot;&gt;&lt;img alt=&quot;Link to Thunderbird Add-on library.&quot; class=&quot;wp-image-4000&quot; height=&quot;217&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Screenshot-2025-10-24-at-12.40.49 PM-1-600x217.png&quot; style=&quot;width: 144px; height: auto;&quot; title=&quot;TB Add-on Link&quot; width=&quot;600&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;&lt;/div&gt;
  183.  
  184.  
  185. &lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Do you have a favorite extension? Share it with us in the comments below. &lt;/p&gt;
  186.  
  187.  
  188.  
  189. &lt;p&gt;To learn more about add-ons check out &lt;a href=&quot;http://Maximize Your Day: Extend Your Productivity with Add-ons&quot;&gt;Maximize Your Day: Extend Your Productivity with Add-ons&lt;/a&gt;.&lt;/p&gt;
  190.  
  191.  
  192.  
  193. &lt;p&gt;Your workflow deserves a client that adapts to it. Add what accelerates you, trim the rest, and keep improving. When you’re ready to go further, the &lt;a href=&quot;https://addons.thunderbird.net/en-US/thunderbird/&quot;&gt;Thunderbird Add-ons Catalog &lt;/a&gt;is the fastest path to new features. Check what’s popular, discover up‑and‑coming tools, and install directly from the page with built‑in version compatibility checks. Thanks for reading.&lt;/p&gt;
  194. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/10/your-workflow-supercharged/&quot;&gt;Your Workflow, Supercharged&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  195. <pubDate>Fri, 24 Oct 2025 20:00:11 +0000</pubDate>
  196. <dc:creator>David Hathaway</dc:creator>
  197. </item>
  198. <item>
  199. <title>The Servo Blog: This month in Servo: experimental mode, Trusted Types, strokeText(), and more!</title>
  200. <guid isPermaLink="true">https://servo.org/blog/2025/10/24/this-month-in-servo/</guid>
  201. <link>https://servo.org/blog/2025/10/24/this-month-in-servo/</link>
  202. <description>&lt;p&gt;September was another busy month for Servo, with a bunch of new features landing in our nightly builds:&lt;/p&gt;
  203. &lt;ul&gt;
  204. &lt;li&gt;the &lt;strong&gt;Trusted Types&lt;/strong&gt; API is now stable (&lt;a href=&quot;https://github.com/TimvdLippe&quot;&gt;@TimvdLippe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39281&quot;&gt;#39281&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39263&quot;&gt;#39263&lt;/a&gt;)&lt;/li&gt;
  205. &lt;li&gt;&lt;strong&gt;strokeText()&lt;/strong&gt; on CanvasRenderingContext2D (&lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39183&quot;&gt;#39183&lt;/a&gt;)&lt;/li&gt;
  206. &lt;li&gt;&lt;strong&gt;invertSelf()&lt;/strong&gt; on DOMMatrix (&lt;a href=&quot;https://github.com/lumiscosity&quot;&gt;@lumiscosity&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39148&quot;&gt;#39148&lt;/a&gt;)&lt;/li&gt;
  207. &lt;li&gt;&lt;strong&gt;getType()&lt;/strong&gt; and &lt;strong&gt;supports()&lt;/strong&gt; on ClipboardItem (&lt;a href=&quot;https://github.com/Gae24&quot;&gt;@Gae24&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39296&quot;&gt;#39296&lt;/a&gt;)&lt;/li&gt;
  208. &lt;li&gt;&lt;strong&gt;getAll()&lt;/strong&gt; and &lt;strong&gt;getAllKeys()&lt;/strong&gt; on IDBObjectStore (&lt;a href=&quot;https://github.com/arihant2math&quot;&gt;@arihant2math&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38885&quot;&gt;#38885&lt;/a&gt;)&lt;/li&gt;
  209. &lt;li&gt;&lt;strong&gt;scrollParent&lt;/strong&gt; property on HTMLElement (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39110&quot;&gt;#39110&lt;/a&gt;)&lt;/li&gt;
  210. &lt;li&gt;&lt;strong&gt;sizes&lt;/strong&gt; property on HTMLImageElement (&lt;a href=&quot;https://github.com/tharkum&quot;&gt;@tharkum&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39466&quot;&gt;#39466&lt;/a&gt;)&lt;/li&gt;
  211. &lt;/ul&gt;
  212. &lt;figure&gt;
  213.    &lt;img alt=&quot;servoshell nightly showing new support for the strokeText() method on CanvasRenderingContext2D&quot; src=&quot;https://servo.org/img/blog/2025-10-diffie.jpg&quot; /&gt;
  214. &lt;/figure&gt;
  215. &lt;p&gt;servoshell now has a new &lt;strong&gt;experimental mode button&lt;/strong&gt; (☢).
  216. Turning on experimental mode has the same effect as running Servo with &lt;code&gt;--enable-experimental-web-platform-features&lt;/code&gt;: it enables all engine features, even those that may not be stable or complete.
  217. This works much like Chromium’s option with the same name, and it can be useful when a page is not functioning correctly, since it may allow the page to make further progress.&lt;/p&gt;
  218. &lt;figure&gt;
  219.    &lt;img alt=&quot;servoshell nightly showing the new experimental mode button (☢), which enables experimental web platform features&quot; src=&quot;https://servo.org/img/blog/2025-10-experimental.png&quot; /&gt;
  220.    &amp;lt;figcaption&amp;gt;Top to bottom: experimental mode off, experimental mode on.&amp;lt;/figcaption&amp;gt;
  221. &lt;/figure&gt;
  222. &lt;p&gt;&lt;strong&gt;Viewport meta&lt;/strong&gt; tags are now enabled on mobile devices only, fixing a bug where they were enabled on desktop (&lt;a href=&quot;https://github.com/shubhamg13&quot;&gt;@shubhamg13&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39133&quot;&gt;#39133&lt;/a&gt;).
  223. You can still enable them if needed with &lt;code&gt;--pref viewport_meta_enabled&lt;/code&gt; (&lt;a href=&quot;https://github.com/shubhamg13&quot;&gt;@shubhamg13&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39207&quot;&gt;#39207&lt;/a&gt;).&lt;/p&gt;
  224. &lt;p&gt;Servo now supports &lt;strong&gt;‘&lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Encoding&quot;&gt;Content-Encoding&lt;/a&gt;: &lt;a href=&quot;https://en.wikipedia.org/wiki/Zstd&quot;&gt;zstd&lt;/a&gt;’&lt;/strong&gt; (&lt;a href=&quot;https://github.com/webbeef&quot;&gt;@webbeef&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/36530&quot;&gt;#36530&lt;/a&gt;), and we’ve fixed a bug causing spurious credentials prompts when a HTTP 401 has no ‘WWW-Authenticate’ header (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39215&quot;&gt;#39215&lt;/a&gt;).
  225. We’ve also made a bunch of progress on &lt;strong&gt;AbortController&lt;/strong&gt; (&lt;a href=&quot;https://github.com/TimvdLippe&quot;&gt;@TimvdLippe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39290&quot;&gt;#39290&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39295&quot;&gt;#39295&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39374&quot;&gt;#39374&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39406&quot;&gt;#39406&lt;/a&gt;) and &lt;strong&gt;&amp;lt;link rel=preload&amp;gt;&lt;/strong&gt; (&lt;a href=&quot;https://github.com/TimvdLippe&quot;&gt;@TimvdLippe&lt;/a&gt;, &lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39033&quot;&gt;#39033&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39034&quot;&gt;#39034&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39052&quot;&gt;#39052&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39146&quot;&gt;#39146&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39167&quot;&gt;#39167&lt;/a&gt;).&lt;/p&gt;
  226. &lt;p&gt;&lt;strong&gt;‘Content-Security-Policy: sandbox’&lt;/strong&gt; now &lt;strong&gt;disables scripting&lt;/strong&gt; unless &lt;strong&gt;‘allow-scripts’&lt;/strong&gt; is given (&lt;a href=&quot;https://github.com/TimvdLippe&quot;&gt;@TimvdLippe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39163&quot;&gt;#39163&lt;/a&gt;), and &lt;strong&gt;crypto.subtle.exportKey()&lt;/strong&gt; can now export HMAC keys in &lt;code&gt;raw&lt;/code&gt; format (&lt;a href=&quot;https://github.com/arihant2math&quot;&gt;@arihant2math&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39059&quot;&gt;#39059&lt;/a&gt;).&lt;/p&gt;
  227. &lt;p&gt;The &lt;strong&gt;scrollIntoView()&lt;/strong&gt; method on Element now works with shadow DOM (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39144&quot;&gt;#39144&lt;/a&gt;), and recurses to parent iframes if they are same origin (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39475&quot;&gt;#39475&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39397&quot;&gt;#39397&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39153&quot;&gt;#39153&lt;/a&gt;).&lt;/p&gt;
  228. &lt;p&gt;Several types of &lt;strong&gt;DOM exceptions can now have error messages&lt;/strong&gt; (&lt;a href=&quot;https://github.com/arihant2math&quot;&gt;@arihant2math&lt;/a&gt;, &lt;a href=&quot;https://github.com/rodio&quot;&gt;@rodio&lt;/a&gt;, &lt;a href=&quot;https://github.com/excitablesnowball&quot;&gt;@excitablesnowball&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39056&quot;&gt;#39056&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39394&quot;&gt;#39394&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39535&quot;&gt;#39535&lt;/a&gt;), and we’ve also fixed a bug where links often need to be clicked twice (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39326&quot;&gt;#39326&lt;/a&gt;), and fixed bugs affecting &amp;lt;img&amp;gt; attribute changes (&lt;a href=&quot;https://github.com/tharkum&quot;&gt;@tharkum&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39483&quot;&gt;#39483&lt;/a&gt;), the ‘:defined’ selector (&lt;a href=&quot;https://github.com/mukilan&quot;&gt;@mukilan&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39325&quot;&gt;#39325&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39390&quot;&gt;#39390&lt;/a&gt;), invertSelf() on DOMMatrix (&lt;a href=&quot;https://github.com/lumiscosity&quot;&gt;@lumiscosity&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39113&quot;&gt;#39113&lt;/a&gt;), and the ‘href’ setter on Location (&lt;a href=&quot;https://github.com/arihant2math&quot;&gt;@arihant2math&lt;/a&gt;, &lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39051&quot;&gt;#39051&lt;/a&gt;).&lt;/p&gt;
  229. &lt;p&gt;One complex part of Servo isn’t even written in Rust, it’s written in Python!
  230. &lt;a href=&quot;https://github.com/servo/servo/blob/25d3c5a157e781db8813071a5ba647463546d0cd/components/script_bindings/codegen/codegen.py&quot;&gt;&lt;strong&gt;codegen.py&lt;/strong&gt;&lt;/a&gt;, which describes how to generate Rust code with bindings for every known DOM interface from the WebIDL, is now &lt;strong&gt;fully type annotated&lt;/strong&gt; (&lt;a href=&quot;https://github.com/jerensl&quot;&gt;@jerensl&lt;/a&gt;, &lt;a href=&quot;https://github.com/mukilan&quot;&gt;@mukilan&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39070&quot;&gt;#39070&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38998&quot;&gt;#38998&lt;/a&gt;).&lt;/p&gt;
  231. &lt;h3&gt;Embedding and automation &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/10/24/this-month-in-servo/#embedding-and-automation&quot;&gt;
  232.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  233.      &lt;/a&gt;&lt;/h3&gt;
  234. &lt;p&gt;Servo now requires &lt;strong&gt;Rust 1.86&lt;/strong&gt; to build (&lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39185&quot;&gt;#39185&lt;/a&gt;).&lt;/p&gt;
  235. &lt;p&gt;&lt;strong&gt;Keyboard scrolling&lt;/strong&gt; is now automatically implemented by Servo (&lt;a href=&quot;https://github.com/delan&quot;&gt;@delan&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39371&quot;&gt;#39371&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39469&quot;&gt;#39469&lt;/a&gt;), so embedders &lt;a href=&quot;https://github.com/servo/servo/pull/39371/files#diff-24ced12025398fd76b233d19f4507362ae8b3848157577d8041effc4c4a229ae&quot;&gt;no longer&lt;/a&gt; need to translate &lt;strong&gt;arrow keys&lt;/strong&gt;, &lt;strong&gt;Home&lt;/strong&gt;, &lt;strong&gt;End&lt;/strong&gt;, &lt;strong&gt;Page Up&lt;/strong&gt;, and &lt;strong&gt;Page Down&lt;/strong&gt; to WebView API calls.
  236. This change also improves the behaviour of those keys, scrolling the element or &amp;lt;iframe&amp;gt; that was focused or most recently clicked (or a nearby ancestor).&lt;/p&gt;
  237. &lt;p&gt;&lt;code&gt;&lt;a href=&quot;https://doc.servo.org/servo_config/opts/struct.DebugOptions.html&quot;&gt;DebugOptions&lt;/a&gt;::convert_mouse_to_touch&lt;/code&gt; (&lt;code&gt;-Z convert-mouse-to-touch&lt;/code&gt;) has been removed (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39352&quot;&gt;#39352&lt;/a&gt;), with no replacement.
  238. Touch event simulation continues to be available in servoshell as &lt;code&gt;--simulate-touch-events&lt;/code&gt;.&lt;/p&gt;
  239. &lt;p&gt;&lt;code&gt;&lt;a href=&quot;https://doc.servo.org/servo_config/opts/struct.DebugOptions.html&quot;&gt;DebugOptions&lt;/a&gt;::webrender_stats&lt;/code&gt; (&lt;code&gt;-Z wr-stats&lt;/code&gt; in servoshell) has been removed (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39331&quot;&gt;#39331&lt;/a&gt;); instead call &lt;code&gt;&lt;a href=&quot;https://doc.servo.org/servo/struct.WebView.html#method.toggle_webrender_debugging&quot;&gt;toggle_webrender_debugging&lt;/a&gt;(&lt;a href=&quot;https://doc.servo.org/servo/enum.WebRenderDebugOption.html#variant.Profiler&quot;&gt;Profiler&lt;/a&gt;)&lt;/code&gt; on a WebView (or press &lt;strong&gt;Ctrl&lt;/strong&gt;+&lt;strong&gt;F12&lt;/strong&gt; in servoshell).&lt;/p&gt;
  240. &lt;p&gt;&lt;code&gt;&lt;a href=&quot;https://doc.servo.org/servo_config/opts/struct.DebugOptions.html&quot;&gt;DebugOptions&lt;/a&gt;::trace_layout&lt;/code&gt; (&lt;code&gt;-Z trace-layout&lt;/code&gt;) has been removed (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39332&quot;&gt;#39332&lt;/a&gt;), since it had no effect.&lt;/p&gt;
  241. &lt;p&gt;We’ve improved the docs for &lt;code&gt;&lt;a href=&quot;https://doc.servo.org/servo/trait.WebViewDelegate.html&quot;&gt;WebViewDelegate&lt;/a&gt;::&lt;a href=&quot;https://doc.servo.org/servo/trait.WebViewDelegate.html#method.notify_history_changed&quot;&gt;notify_history_changed&lt;/a&gt;&lt;/code&gt; (&lt;a href=&quot;https://github.com/Narfinger&quot;&gt;@Narfinger&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39134&quot;&gt;#39134&lt;/a&gt;).&lt;/p&gt;
  242. &lt;p&gt;When automating servoshell with &lt;strong&gt;WebDriver&lt;/strong&gt;, commands &lt;strong&gt;targeting elements&lt;/strong&gt; now correctly &lt;strong&gt;scroll into view&lt;/strong&gt; if needed (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38508&quot;&gt;#38508&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39265&quot;&gt;#39265&lt;/a&gt;), allowing &lt;strong&gt;Element Click&lt;/strong&gt;, &lt;strong&gt;Element Send Keys&lt;/strong&gt;, &lt;strong&gt;Element Clear&lt;/strong&gt;, and &lt;strong&gt;Take Element Screenshot&lt;/strong&gt; to work properly when the element is outside the viewport.&lt;/p&gt;
  243. &lt;p&gt;&lt;strong&gt;WebDriver mouse inputs&lt;/strong&gt; now work correctly with &lt;strong&gt;HiDPI scaling&lt;/strong&gt; on more platforms (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39472&quot;&gt;#39472&lt;/a&gt;), and we’ve improved the reliability of &lt;strong&gt;Take Screenshot&lt;/strong&gt;, &lt;strong&gt;Take Element Screenshot&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39499&quot;&gt;#39499&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39539&quot;&gt;#39539&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39543&quot;&gt;#39543&lt;/a&gt;), &lt;strong&gt;Switch To Frame&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39086&quot;&gt;#39086&lt;/a&gt;), &lt;strong&gt;Switch To Window&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39241&quot;&gt;#39241&lt;/a&gt;), and &lt;strong&gt;New Session&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39040&quot;&gt;#39040&lt;/a&gt;).&lt;/p&gt;
  244. &lt;p&gt;These improvements have enabled us to run the &lt;strong&gt;WebDriver conformance tests&lt;/strong&gt; in CI by default (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39087&quot;&gt;#39087&lt;/a&gt;), and also mean we’re closer than ever to running &lt;a href=&quot;https://web-platform-tests.org/writing-tests/testdriver.html&quot;&gt;WebDriver-based Web Platform Tests&lt;/a&gt;.&lt;/p&gt;
  245. &lt;h3&gt;servoshell &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/10/24/this-month-in-servo/#servoshell&quot;&gt;
  246.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  247.      &lt;/a&gt;&lt;/h3&gt;
  248. &lt;p&gt;&lt;strong&gt;Favicons&lt;/strong&gt; now update correctly when you &lt;strong&gt;navigate back and forward&lt;/strong&gt; (&lt;a href=&quot;https://github.com/webbeef&quot;&gt;@webbeef&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39575&quot;&gt;#39575&lt;/a&gt;), not just when you load a new page.&lt;/p&gt;
  249. &lt;p&gt;servoshell’s &lt;strong&gt;command line argument parsing&lt;/strong&gt; has been reworked (&lt;a href=&quot;https://github.com/Narfinger&quot;&gt;@Narfinger&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37194&quot;&gt;#37194&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39316&quot;&gt;#39316&lt;/a&gt;), which should fix the confusing behaviour of some options.&lt;/p&gt;
  250. &lt;p&gt;On mobile devices, servoshell now resizes the webview correctly when the available space changes (&lt;a href=&quot;https://github.com/blueguy1&quot;&gt;@blueguy1&lt;/a&gt;, &lt;a href=&quot;https://github.com/yjx&quot;&gt;@yjx&lt;/a&gt;, &lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39507&quot;&gt;#39507&lt;/a&gt;).&lt;/p&gt;
  251. &lt;p&gt;On macOS, telling servoshell to &lt;a href=&quot;https://w3c.github.io/webdriver/#screen-capture&quot;&gt;&lt;strong&gt;take a screenshot&lt;/strong&gt;&lt;/a&gt; no longer hides the window (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39500&quot;&gt;#39500&lt;/a&gt;).
  252. This does not affect taking a screenshot in headless mode (&lt;code&gt;--headless&lt;/code&gt;), where there continues to be no window at all.&lt;/p&gt;
  253. &lt;h3&gt;Performance &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/10/24/this-month-in-servo/#performance&quot;&gt;
  254.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  255.      &lt;/a&gt;&lt;/h3&gt;
  256. &lt;p&gt;Servo currently runs in &lt;strong&gt;single-process mode&lt;/strong&gt; unless you opt in to &lt;code&gt;--multiprocess&lt;/code&gt; mode, and we’ve landed a few perf improvements in that default mode.
  257. For one, in single-process mode, script can now &lt;strong&gt;communicate with the embedder directly&lt;/strong&gt; for reduced latency (&lt;a href=&quot;https://github.com/jschwe&quot;&gt;@jschwe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39039&quot;&gt;#39039&lt;/a&gt;).
  258. We also create one thread pool for the image cache now, rather than one pool per origin (&lt;a href=&quot;https://github.com/rodio&quot;&gt;@rodio&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38783&quot;&gt;#38783&lt;/a&gt;).&lt;/p&gt;
  259. &lt;p&gt;Many components of Servo that &lt;em&gt;would&lt;/em&gt; be &lt;a href=&quot;https://book.servo.org/architecture/overview.html#architecture&quot;&gt;separated by a process boundary&lt;/a&gt; in multiprocess mode, now use &lt;a href=&quot;https://docs.rs/crossbeam-channel/0.5.15/crossbeam_channel/&quot;&gt;crossbeam channels&lt;/a&gt; in single-process mode, rather than using &lt;a href=&quot;https://docs.rs/ipc-channel/0.20.2/ipc_channel/&quot;&gt;IPC channels&lt;/a&gt; in both modes (&lt;a href=&quot;https://github.com/jschwe&quot;&gt;@jschwe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39073&quot;&gt;#39073&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39076&quot;&gt;#39076&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39345&quot;&gt;#39345&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39347&quot;&gt;#39347&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39348&quot;&gt;#39348&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39074&quot;&gt;#39074&lt;/a&gt;).
  260. &lt;a href=&quot;https://docs.rs/ipc-channel/0.20.2/ipc_channel/&quot;&gt;IPC channels&lt;/a&gt; are required when communicating with another process, but they’re more expensive, because they require serialising and deserialising each message, plus resources from the operating system.&lt;/p&gt;
  261. &lt;p&gt;We’ve started working on an optimisation for string handling in Servo’s DOM layer (&lt;a href=&quot;https://github.com/Narfinger&quot;&gt;@Narfinger&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39480&quot;&gt;#39480&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39481&quot;&gt;#39481&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39504&quot;&gt;#39504&lt;/a&gt;).
  262. Strings in our DOM have historically been represented as &lt;a href=&quot;https://doc.rust-lang.org/std/string/struct.String.html&quot;&gt;ordinary Rust strings&lt;/a&gt;, but they often come from SpiderMonkey, where they use &lt;a href=&quot;https://searchfox.org/firefox-main/rev/8e5d58cfed616cb90586c614e53d8ab1ffc8af27/js/src/vm/StringType.h#83&quot;&gt;a variety of representations&lt;/a&gt;, none of which are entirely compatible.
  263. SpiderMonkey strings would continue to need conversion to Servo strings, but the idea we’re working towards is to &lt;strong&gt;make the conversion lazy&lt;/strong&gt;, in the hope that many strings will never end up being converted at all.&lt;/p&gt;
  264. &lt;p&gt;We now use a faster hash algorithm for internal hashmaps that are not security-critical (&lt;a href=&quot;https://github.com/Narfinger&quot;&gt;@Narfinger&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39106&quot;&gt;#39106&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39166&quot;&gt;#39166&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39202&quot;&gt;#39202&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39233&quot;&gt;#39233&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39244&quot;&gt;#39244&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39168&quot;&gt;#39168&lt;/a&gt;).
  265. These changes also switch that faster algorithm from &lt;a href=&quot;https://en.wikipedia.org/wiki/Fowler%E2%80%93Noll%E2%80%93Vo_hash_function&quot;&gt;FNV&lt;/a&gt; to an &lt;a href=&quot;https://docs.rs/rustc-hash/2.1.1/rustc_hash/&quot;&gt;even simpler polynomial hash&lt;/a&gt;, following in the footsteps of &lt;a href=&quot;https://github.com/rust-lang/rust/pull/37229&quot;&gt;Rust&lt;/a&gt; and &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1477628&quot;&gt;Stylo&lt;/a&gt;.&lt;/p&gt;
  266. &lt;p&gt;We’ve also landed a few more self-contained perf improvements:&lt;/p&gt;
  267. &lt;ul&gt;
  268. &lt;li&gt;speeding up accesses to the event loop (&lt;a href=&quot;https://github.com/Narfinger&quot;&gt;@Narfinger&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39274&quot;&gt;#39274&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39275&quot;&gt;#39275&lt;/a&gt;)&lt;/li&gt;
  269. &lt;li&gt;avoviding new display lists while loading CSS images (&lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39201&quot;&gt;#39201&lt;/a&gt;)&lt;/li&gt;
  270. &lt;li&gt;reducing memory usage (&lt;a href=&quot;https://github.com/ritoban23&quot;&gt;@ritoban23&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39351&quot;&gt;#39351&lt;/a&gt;)&lt;/li&gt;
  271. &lt;li&gt;reducing binary size (&lt;a href=&quot;https://github.com/lumiscosity&quot;&gt;@lumiscosity&lt;/a&gt;, &lt;a href=&quot;https://github.com/Narfinger&quot;&gt;@Narfinger&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39437&quot;&gt;#39437&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39567&quot;&gt;#39567&lt;/a&gt;)&lt;/li&gt;
  272. &lt;/ul&gt;
  273. &lt;h3&gt;Donations &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/10/24/this-month-in-servo/#donations&quot;&gt;
  274.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  275.      &lt;/a&gt;&lt;/h3&gt;
  276. &lt;p&gt;Thanks again for your generous support!
  277. We are now receiving &lt;strong&gt;5654 USD/month&lt;/strong&gt; (+1.8% over August) in recurring donations.&lt;/p&gt;
  278. &lt;p&gt;This helps us cover the cost of our &lt;strong&gt;&lt;a href=&quot;https://ci0.servo.org/&quot;&gt;speedy&lt;/a&gt; &lt;a href=&quot;https://ci1.servo.org/&quot;&gt;CI&lt;/a&gt; &lt;a href=&quot;https://ci2.servo.org/&quot;&gt;and&lt;/a&gt; &lt;a href=&quot;https://ci3.servo.org/&quot;&gt;benchmarking&lt;/a&gt; &lt;a href=&quot;https://ci4.servo.org/&quot;&gt;servers&lt;/a&gt;&lt;/strong&gt;, one of our latest &lt;strong&gt;&lt;a href=&quot;https://www.outreachy.org/alums/2025-06/#:~:text=Servo&quot;&gt;Outreachy interns&lt;/a&gt;&lt;/strong&gt;, and funding &lt;strong&gt;&lt;a href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/&quot;&gt;maintainer work&lt;/a&gt;&lt;/strong&gt; that helps more people contribute to Servo.
  279. Keep an eye out for &lt;a href=&quot;https://github.com/servo/servo/issues/38141&quot;&gt;further CI improvements&lt;/a&gt; in the coming months, including &lt;a href=&quot;https://github.com/servo/servo/pull/39900&quot;&gt;faster pull request checks&lt;/a&gt; and &lt;a href=&quot;https://github.com/servo/ci-runners/issues/21&quot;&gt;ten-minute WPT builds&lt;/a&gt;.&lt;/p&gt;
  280. &lt;p&gt;Servo is also on &lt;a href=&quot;https://thanks.dev/&quot;&gt;thanks.dev&lt;/a&gt;, and already &lt;strong&gt;28 GitHub users&lt;/strong&gt; (±13 from August) that depend on Servo are sponsoring us there.
  281. If you use Servo libraries like &lt;a href=&quot;https://crates.io/crates/url/reverse_dependencies&quot;&gt;url&lt;/a&gt;, &lt;a href=&quot;https://crates.io/crates/html5ever/reverse_dependencies&quot;&gt;html5ever&lt;/a&gt;, &lt;a href=&quot;https://crates.io/crates/selectors/reverse_dependencies&quot;&gt;selectors&lt;/a&gt;, or &lt;a href=&quot;https://crates.io/crates/cssparser/reverse_dependencies&quot;&gt;cssparser&lt;/a&gt;, signing up for &lt;a href=&quot;https://thanks.dev/&quot;&gt;thanks.dev&lt;/a&gt; could be a good way for you (or your employer) to give back to the community.&lt;/p&gt;
  282. &lt;figure class=&quot;_fig&quot; style=&quot;width: 100%; margin: 1em 0;&quot;&gt;&lt;div class=&quot;_flex&quot;&gt;
  283.    &lt;div style=&quot;text-align: right;&quot;&gt;
  284.        &lt;div&gt;&lt;strong&gt;5654&lt;/strong&gt; USD/month&lt;/div&gt;
  285.        &lt;div&gt;&lt;/div&gt;
  286.        &lt;div&gt;&lt;/div&gt;
  287.        &lt;div style=&quot;padding-right: 1em;&quot;&gt;&lt;strong&gt;10000&lt;/strong&gt;&lt;/div&gt;
  288.    &lt;/div&gt;
  289.    &lt;progress max=&quot;10000&quot; value=&quot;5654&quot;&gt;&lt;/progress&gt;
  290. &lt;/div&gt;&lt;/figure&gt;
  291. &lt;p&gt;Use of donations is decided transparently via the Technical Steering Committee’s public &lt;strong&gt;&lt;a href=&quot;https://github.com/servo/project/blob/main/FUNDING_REQUEST.md&quot;&gt;funding request process&lt;/a&gt;&lt;/strong&gt;, and active proposals are tracked in &lt;a href=&quot;https://github.com/servo/project/issues/187&quot;&gt;servo/project#187&lt;/a&gt;.
  292. For more details, head to our &lt;a href=&quot;https://servo.org/sponsorship/&quot;&gt;Sponsorship page&lt;/a&gt;.&lt;/p&gt;
  293. &lt;h3&gt;Conference talks &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/10/24/this-month-in-servo/#conference-talks&quot;&gt;
  294.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  295.      &lt;/a&gt;&lt;/h3&gt;
  296. &lt;p&gt;&lt;strong&gt;&lt;a href=&quot;https://ke.segmentfault.com/course/1650000043885605/section/1500000047216580&quot;&gt;MiniApps Design and Servo&lt;/a&gt;&lt;/strong&gt; (starting at ~2:37:00; &lt;a href=&quot;https://www.w3.org/2024/01/webevolve-series-events/annual-2025/slides/gregory-terzian.pdf&quot;&gt;slides&lt;/a&gt;) — Gregory Terzian (&lt;a href=&quot;https://github.com/gterzian&quot;&gt;@gterzian&lt;/a&gt;) spoke about how Servo can be used as a web engine for mini-app platforms at &lt;a href=&quot;https://www.w3.org/2024/01/webevolve-series-events/annual-2025/high-perf.en.html&quot;&gt;WebEvolve 2025&lt;/a&gt;&lt;/p&gt;
  297. &lt;p&gt;&lt;strong&gt;&lt;a href=&quot;https://ke.segmentfault.com/course/1650000043885605/section/1500000047216580&quot;&gt;独⽴的，轻量级，模块化与并⾏处理架构的Web引擎开发&lt;/a&gt;&lt;/strong&gt; [zh] / &lt;strong&gt;Developing an independent, light-weight, modular and parallel web-engine&lt;/strong&gt; [en] (starting at ~5:49:00; &lt;a href=&quot;https://www.w3.org/2024/01/webevolve-series-events/annual-2025/slides/jonathan-schwender.pdf&quot;&gt;slides&lt;/a&gt;) — Jonathan Schwender (&lt;a href=&quot;https://github.com/jschwe&quot;&gt;@jschwe&lt;/a&gt;) spoke about Servo’s goals and status at &lt;a href=&quot;https://www.w3.org/2024/01/webevolve-series-events/annual-2025/high-perf.en.html&quot;&gt;WebEvolve 2025&lt;/a&gt;&lt;/p&gt;
  298. &lt;p&gt;&lt;strong&gt;Servo: A new web engine written in Rust&lt;/strong&gt;* (&lt;a href=&quot;https://docs.google.com/presentation/d/1t15UKit4UPkZ-4ankkvsTJdpQWdBCmeTXLALeLk9n34&quot;&gt;slides&lt;/a&gt;; &lt;a href=&quot;https://blogs.igalia.com/mrego/servo-a-new-web-engine-written-in-rust/&quot;&gt;transcript&lt;/a&gt;) — Manuel Rego (&lt;a href=&quot;https://github.com/rego&quot;&gt;@rego&lt;/a&gt;) spoke about the Servo project at &lt;a href=&quot;https://hangzhou2025.gosim.org/&quot;&gt;GOSIM Hangzhou 2025&lt;/a&gt;&lt;/p&gt;
  299. &lt;p&gt;&lt;strong&gt;Driving Innovation with Servo and OpenHarmony: Unified Rendering and WebDriver&lt;/strong&gt;* (&lt;a href=&quot;https://servo.org/files/2025-09-13-driving-innovation-with-servo-and-openharmony-unified-rendering-and-webdriver.pdf&quot;&gt;slides&lt;/a&gt;) — Jingshi Shangguan &amp;amp; Zhizhen Ye (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;) spoke about a new OpenHarmony rendering backend and WebDriver support in Servo at &lt;a href=&quot;https://hangzhou2025.gosim.org/&quot;&gt;GOSIM Hangzhou 2025&lt;/a&gt;&lt;/p&gt;
  300. &lt;p&gt;&lt;strong&gt;The Joy and Value of Embedded Servo Systems&lt;/strong&gt;* (&lt;a href=&quot;https://servo.org/files/2025-09-13-the-joy-and-value-of-embedded-servo-systems.pdf&quot;&gt;slides&lt;/a&gt;) — Gregory Terzian (&lt;a href=&quot;https://github.com/gterzian&quot;&gt;@gterzian&lt;/a&gt;) spoke about embedding Servo at &lt;a href=&quot;https://hangzhou2025.gosim.org/&quot;&gt;GOSIM Hangzhou 2025&lt;/a&gt;&lt;/p&gt;
  301. &lt;p&gt;&lt;strong&gt;A Dive Into the Servo Layout System&lt;/strong&gt;* (&lt;a href=&quot;https://servo.org/files/2025-09-13-a-dive-into-the-servo-layout-system.pdf&quot;&gt;slides&lt;/a&gt;) — Martin Robinson (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;) &amp;amp; Oriol Brufau (&lt;a href=&quot;https://github.com/obrufau&quot;&gt;@obrufau&lt;/a&gt;) spoke about the architecture of Servo’s parallel and incremental layout system at &lt;a href=&quot;https://hangzhou2025.gosim.org/&quot;&gt;GOSIM Hangzhou 2025&lt;/a&gt;&lt;/p&gt;
  302. &lt;p&gt;&lt;small&gt;* video coming soon; go to our &lt;a href=&quot;https://servo.org/about/&quot;&gt;About page&lt;/a&gt; for updates&lt;/small&gt;&lt;/p&gt;</description>
  303. <pubDate>Fri, 24 Oct 2025 00:00:00 +0000</pubDate>
  304. </item>
  305. <item>
  306. <title>Mozilla Addons Blog: Announcing data collection consent changes for new Firefox extensions</title>
  307. <guid isPermaLink="false">https://blog.mozilla.org/addons/?p=9265</guid>
  308. <link>https://blog.mozilla.org/addons/2025/10/23/data-collection-consent-changes-for-new-firefox-extensions/</link>
  309. <description>&lt;p&gt;As of November 3rd 2025, all &lt;b&gt;new&lt;/b&gt; Firefox extensions will be required to &lt;a href=&quot;https://extensionworkshop.com/documentation/develop/firefox-builtin-data-consent/#specifying-data-types&quot;&gt;specify if they collect or transmit personal data&lt;/a&gt; in their &lt;code&gt;manifest.json&lt;/code&gt; file using the &lt;code&gt;browser_specific_settings.gecko.data_collection_permissions key&lt;/code&gt;. This will apply to new extensions only, and &lt;b&gt;not new versions of existing extensions&lt;/b&gt;. Extensions that do not collect or transmit any personal data are required to specify this by setting the none required data collection permission in this property.&lt;/p&gt;
  310. &lt;p&gt;This information will then be displayed to the user when they start to install the extension, alongside any permissions it requests.&lt;/p&gt;
  311. &lt;p&gt;&lt;a href=&quot;https://blog.mozilla.org/addons/files/2025/10/data-collection-permissions-prompt-install.460b7848.webp&quot;&gt;&lt;img alt=&quot;Screenshot of example Firefox extension installation prompt showing data that the extension collects&quot; class=&quot;size-medium wp-image-9267 aligncenter&quot; height=&quot;418&quot; src=&quot;https://blog.mozilla.org/addons/files/2025/10/data-collection-permissions-prompt-install.460b7848-580x418.webp&quot; width=&quot;580&quot; /&gt;&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/addons/files/2025/10/data-collection-permissions-prompt-install-no-transmission.66cdd978.webp&quot;&gt;&lt;img alt=&quot;Screenshot of example Firefox extension installation prompt showing that the extension claims it collects no data&quot; class=&quot;size-medium wp-image-9266 aligncenter&quot; height=&quot;402&quot; src=&quot;https://blog.mozilla.org/addons/files/2025/10/data-collection-permissions-prompt-install-no-transmission.66cdd978-580x402.webp&quot; width=&quot;580&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
  312. &lt;p&gt;This information will also be displayed on the &lt;a href=&quot;http://addons.mozilla.org&quot;&gt;addons.mozilla.org&lt;/a&gt; page, if it is publicly listed, and in the &lt;i&gt;Permissions and Data&lt;/i&gt; section of the Firefox about:addons page for that extension. If an extension supports versions of Firefox prior to 140 for Desktop, or 142 for Android, then the developer will need to continue to provide the user with a clear way to control the add-on’s data collection and transmission immediately after installation of the add-on.&lt;/p&gt;
  313. &lt;p&gt;Once any extension starts using these &lt;code&gt;data_collection_permissions&lt;/code&gt; keys in a new version, it will need to continue using them for all subsequent versions. Extensions that do not have this property set correctly, and are required to use it, will be prevented from being submitted to &lt;a href=&quot;http://addons.mozilla.org&quot;&gt;addons.mozilla.org&lt;/a&gt; for signing with a message explaining why.&lt;/p&gt;
  314. &lt;p&gt;In the first half of 2026, Mozilla will require all extensions to adopt this framework. But don’t worry, we’ll give plenty of notice via the add-ons blog. We’re also developing some new features to ease this transition for both extension developers and users, which we will announce here.&lt;/p&gt;
  315. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/addons/2025/10/23/data-collection-consent-changes-for-new-firefox-extensions/&quot;&gt;Announcing data collection consent changes for new Firefox extensions&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/addons&quot;&gt;Mozilla Add-ons Community Blog&lt;/a&gt;.&lt;/p&gt;</description>
  316. <pubDate>Thu, 23 Oct 2025 10:57:39 +0000</pubDate>
  317. <dc:creator>Alan Byrne</dc:creator>
  318. </item>
  319. <item>
  320. <title>Niko Matsakis: Explicit capture clauses</title>
  321. <guid isPermaLink="false">https://smallcultfollowing.com/babysteps/blog/2025/10/22/explicit-capture-clauses/</guid>
  322. <link>https://smallcultfollowing.com/babysteps/blog/2025/10/22/explicit-capture-clauses/?utm_source=atom_feed</link>
  323. <description>&lt;p&gt;In my previous post about Ergonomic Ref Counting, I talked about how, whatever else we do, we need a way to have explicit handle creation that is ergonomic. The next few posts are going to explore a few options for how we might do that.&lt;/p&gt;
  324. &lt;p&gt;This post focuses on &lt;strong&gt;explicit capture clauses&lt;/strong&gt;, which would permit closures to be annotated with an explicit set of captured places. My take is that explicit capture clauses are a no brainer, for reasons that I’ll cover below, and we should definitely do them; but they may not be enough to be considered &lt;em&gt;ergonomic&lt;/em&gt;, so I’ll explore more proposals afterwards.&lt;/p&gt;
  325. &lt;h3&gt;Motivation&lt;/h3&gt;
  326. &lt;p&gt;Rust closures today work quite well but I see a few problems:&lt;/p&gt;
  327. &lt;ul&gt;
  328. &lt;li&gt;Teaching and understanding closure desugaring is difficult because it lacks an explicit form. Users have to learn to desugar in their heads to understand what’s going on.&lt;/li&gt;
  329. &lt;li&gt;Capturing the “clone” of a value (or possibly other transformations) has no concise syntax.&lt;/li&gt;
  330. &lt;li&gt;For long closure bodies, it is hard to determine precisely which values are captured and how; you have to search the closure body for references to external variables, account for shadowing, etc.&lt;/li&gt;
  331. &lt;li&gt;It is hard to develop an intuition for when &lt;code&gt;move&lt;/code&gt; is required. I find myself adding it when the compiler tells me to, but that’s annoying.&lt;/li&gt;
  332. &lt;/ul&gt;
  333. &lt;h3&gt;Let’s look at a strawperson proposal&lt;/h3&gt;
  334. &lt;p&gt;Some time ago, I wrote a proposal for explicit capture clauses. I actually see a lot of flaws with this proposal, but I’m still going to explain it: right now it’s the only solid proposal I know of, and it’s good enough to explain how an explicit capture clause &lt;em&gt;could be seen&lt;/em&gt; as a solution to the “explicit &lt;em&gt;and&lt;/em&gt; ergonomic” goal. I’ll then cover some of the things I like about the proposal and what I don’t.&lt;/p&gt;
  335. &lt;h3&gt;Begin with &lt;code&gt;move&lt;/code&gt;&lt;/h3&gt;
  336. &lt;p&gt;The proposal begins by extending the &lt;code&gt;move&lt;/code&gt; keyword with a list of places to capture:&lt;/p&gt;
  337. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  338. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;do_something&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;d&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  339. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  340. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The closure will then take ownership of those two places; references to those places in the closure body will be replaced by accesses to these captured fields. So that example would desugar to something like&lt;/p&gt;
  341. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  342. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;struct&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;MyClosure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  343. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b_c&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Foo&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  344. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x_y&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Bar&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  345. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  346. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  347. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;FnOnce&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;MyClosure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  348. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;call_once&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-&amp;gt; &lt;span class=&quot;nc&quot;&gt;Baz&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  349. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;            &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;do_something&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b_c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;d&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x_y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  350. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;            &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//           ----------    --------
  351. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;            &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//   The place `a.b.c` is      |
  352. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;            &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//   rewritten to the field    |
  353. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;            &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//   `self.a_b_c`              |
  354. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;            &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//                  Same here but for `x.y`
  355. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  356. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  357. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  358. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;MyClosure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  359. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b_c&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  360. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x_y&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  361. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  362. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  363. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;When using a simple list like this, attempts to reference other places that were not captured result in an error:&lt;/p&gt;
  364. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  365. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;do_something&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;d&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;z&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  366. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//           -------  ---
  367. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//           OK       Error: `x.z` not captured
  368. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  369. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3&gt;Capturing with rewrites&lt;/h3&gt;
  370. &lt;p&gt;It is also possible to capture a custom expression by using an &lt;code&gt;=&lt;/code&gt; sign. So for example, you could rewrite the above closure as follows:&lt;/p&gt;
  371. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  372. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(),&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  373. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  374. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  375. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;do_something&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;d&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;z&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  376. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  377. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;and it would desugar to:&lt;/p&gt;
  378. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  379. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;struct&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;MyClosure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* as before */&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  380. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;FnOnce&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;MyClosure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* as before */&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  381. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  382. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;MyClosure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  383. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b_c&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(),&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  384. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//     ------------------
  385. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x_y&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  386. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  387. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  388. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;When using this form, the expression assigned to &lt;code&gt;a.b.c&lt;/code&gt; must have the same type as &lt;code&gt;a.b.c&lt;/code&gt; in the surrounding scope. So this would be an error:&lt;/p&gt;
  389. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  390. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;22&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// Error: `i32` is not `Foo`
  391. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  392. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  393. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* ... */&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  394. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  395. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3&gt;Shorthands and capturing by reference&lt;/h3&gt;
  396. &lt;p&gt;You can understand &lt;code&gt;move(a.b)&lt;/code&gt; as sugar for &lt;code&gt;move(a.b = a.b)&lt;/code&gt;. We support other convenient shorthands too, such as&lt;/p&gt;
  397. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;())&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  398. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// == anything that ends in a method call becomes ==&amp;gt;
  399. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;())&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  400. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;and two kinda special shorthands:&lt;/p&gt;
  401. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  402. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  403. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;These are special because the captured value is indeed &lt;code&gt;&amp;amp;a.b&lt;/code&gt; and &lt;code&gt;&amp;amp;mut a.b&lt;/code&gt; – but that by itself wouldn’t work, because the type doesn’t match. So we rewrite each access to &lt;code&gt;a.b&lt;/code&gt; to desugar to a dereference of the &lt;code&gt;a_b&lt;/code&gt; field, like &lt;code&gt;*self.a_b&lt;/code&gt;:&lt;/p&gt;
  404. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;foo&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  405. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  406. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// desugars to
  407. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  408. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;struct&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;MyStruct&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;'l&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  409. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b&lt;/span&gt;: &lt;span class=&quot;kp&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;'l&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;Foo&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  410. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  411. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  412. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;FnOnce&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;MyStruct&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;'_&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  413. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;call_once&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  414. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;foo&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;*&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  415. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//  ---------
  416. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//  we insert the `*` too
  417. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  418. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  419. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  420. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;MyStruct&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  421. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b&lt;/span&gt;: &lt;span class=&quot;kp&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;nc&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  422. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  423. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  424. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;foo&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;*&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  425. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;There’s a lot of precedence for this sort of transform: it’s precisely what we do for the &lt;code&gt;Deref&lt;/code&gt; trait and for existing closure captures.&lt;/p&gt;
  426. &lt;h3&gt;Fresh variables&lt;/h3&gt;
  427. &lt;p&gt;We should also allow you to define fresh variables. These can have arbitrary types. The values are evaluated at closure creation time and stored in the closure metadata:&lt;/p&gt;
  428. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  429. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;load_data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(),&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  430. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  431. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  432. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;take&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  433. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  434. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3&gt;Open-ended captures&lt;/h3&gt;
  435. &lt;p&gt;All of our examples so far fully enumerated the captured variables. But Rust closures today infer the set of captures (and the style of capture) based on the paths that are used. We should permit that as well. I’d permit that with a &lt;code&gt;..&lt;/code&gt; sugar, so these two closures are equivalent:&lt;/p&gt;
  436. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c2&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* closure */&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  437. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//       ---- capture anything that is used,
  438. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;//            taking ownership
  439. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  440. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c1&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* closure */&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  441. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//           ---- capture anything else that is used,
  442. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;//                taking ownership
  443. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Of course you can combine:&lt;/p&gt;
  444. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(),&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  445. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  446. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  447. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;And you could write &lt;code&gt;ref&lt;/code&gt; to get the equivalent of &lt;code&gt;||&lt;/code&gt; closures:&lt;/p&gt;
  448. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c2&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* closure */&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  449. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//       -- capture anything that is used,
  450. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;//          using references if possible
  451. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c1&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;ref&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* closure */&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  452. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//            --- capture anything else that is used,
  453. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;//                using references if possible
  454. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This lets you&lt;/p&gt;
  455. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  456. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(),&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  457. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  458. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;ref&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  459. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  460. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;combine&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;z&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  461. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//       ---   -   -
  462. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//        |    |   |
  463. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//        |    | This will be captured by reference
  464. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//        |    | since it is used by reference
  465. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//        |    | and is not explicitly named.
  466. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//        |    |
  467. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//        |   This will be captured by value
  468. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//        |   since it is explicitly named.
  469. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//        |
  470. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// We will capture a clone of this because
  471. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// the user wrote `a.b.clone()`
  472. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  473. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3&gt;Frequently asked questions&lt;/h3&gt;
  474. &lt;h4&gt;How does this help with our motivation?&lt;/h4&gt;
  475. &lt;p&gt;Let’s look at the motivations I named:&lt;/p&gt;
  476. &lt;h5&gt;Teaching and understanding closure desugaring is difficult&lt;/h5&gt;
  477. &lt;p&gt;There’s a lot of syntax there, but it also gives you an explicit form that you can use to do explanations. To see what I mean, consider the difference between these two closures (&lt;a href=&quot;http://smallcultfollowing.com/babysteps/atom.xml&quot;&gt;playground&lt;/a&gt;).&lt;/p&gt;
  478. &lt;p&gt;The first closure uses &lt;code&gt;||&lt;/code&gt;:&lt;/p&gt;
  479. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;main&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  480. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;3&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  481. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c_attached&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  482. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;j&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;+&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;1&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  483. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;replace&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;j&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  484. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  485. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  486. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  487. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;While the second closure uses &lt;code&gt;move&lt;/code&gt;:&lt;/p&gt;
  488. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;main&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  489. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;3&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  490. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c_detached&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  491. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;j&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;+&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;1&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  492. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;replace&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;j&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  493. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  494. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;These are in fact pretty different, &lt;a href=&quot;https://play.rust-lang.org/?version=stable&amp;amp;mode=debug&amp;amp;edition=2024&amp;amp;gist=fec374e4055a99aa3dda9e66a5c03495&quot;&gt;as you can see in this playground&lt;/a&gt;. But why? Well, the first closure desugars to capture a reference:&lt;/p&gt;
  495. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;3&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  496. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c_attached&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  497. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;and the second captures by value:&lt;/p&gt;
  498. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;3&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  499. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c_attached&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;i&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  500. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Before, to explain that, I had to resort to desugaring to structs.&lt;/p&gt;
  501. &lt;h5&gt;Capturing a clone is painful&lt;/h5&gt;
  502. &lt;p&gt;If you have a closure that wants to capture the clone of something today, you have to introduce a fresh variable. So something like this:&lt;/p&gt;
  503. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  504. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;begin_actor&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;tx&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;())&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  505. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  506. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;becomes&lt;/p&gt;
  507. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  508. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;self_tx&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;tx&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;();&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  509. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  510. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;begin_actor&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;self_tx&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;())&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  511. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  512. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  513. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is awkward. Under this proposal, it’s possible to point-wise replace specific items:&lt;/p&gt;
  514. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;tx&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(),&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  515. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;begin_actor&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;tx&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;())&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  516. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  517. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h5&gt;For long closure bodies, it is hard to determine precisely which values are captured and how&lt;/h5&gt;
  518. &lt;p&gt;Quick! What variables does this closure use from the environment?&lt;/p&gt;
  519. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;flat_map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;severity&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lints&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  520. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;parse_tt_as_comma_sep_paths&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lints&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;edition&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  521. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;into_iter&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  522. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;flat_map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lints&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  523. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// Rejoin the idents with `::`, so we have no spaces in between.
  524. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lints&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;into_iter&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;().&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lint&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  525. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;            &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  526. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;                &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lint&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;segments&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;().&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;filter_map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  527. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;                    &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;segment&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;segment&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;name_ref&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  528. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;                &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;).&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;join&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;&quot;::&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;).&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;into&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(),&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  529. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;                &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;severity&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  530. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;            &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  531. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;})&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  532. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;})&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  533. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;})&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  534. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;No idea? Me either. What about this one?&lt;/p&gt;
  535. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;flat_map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;edition&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;severity&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lints&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  536. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* same as above */&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  537. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;})&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  538. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Ah, pretty clear! I find that once a closure moves beyond a couple of lines, it can make a function kind of hard to read, because it’s hard to tell what variables it may be accessing. I’ve had functions where it’s important to correctness for one reason or another that a particular closure only accesses a subset of the values around it, but I have no way to indicate that right now. Sometimes I make separate functions, but it’d be nicer if I could annotate the closure’s captures explicitly.&lt;/p&gt;
  539. &lt;h5&gt;It is hard to develop an intuition for when &lt;code&gt;move&lt;/code&gt; is required&lt;/h5&gt;
  540. &lt;p&gt;Hmm, actually, I don’t think this notation helps with that at all! More about this below.&lt;/p&gt;
  541. &lt;p&gt;Let me cover some of the questions you may have about this design.&lt;/p&gt;
  542. &lt;h4&gt;Why allow the “capture clause” to specify an entire place, like &lt;code&gt;a.b.c&lt;/code&gt;?&lt;/h4&gt;
  543. &lt;p&gt;Today you can write closures that capture places, like &lt;code&gt;self.context&lt;/code&gt; below:&lt;/p&gt;
  544. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  545. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;send_data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;context&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;other_field&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  546. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  547. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;My goal was to be able to take such a closure and to add annotations that change how particular places are captured, without having to do deep rewrites in the body:&lt;/p&gt;
  548. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;closure&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;context&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(),&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  549. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//            --------------------------
  550. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//            the only change
  551. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;send_data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;context&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;other_field&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  552. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;};&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  553. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This definitely adds some complexity, because it means we have to be able to “remap” a place like &lt;code&gt;a.b.c&lt;/code&gt; that has multiple parts. But it makes the explicit capture syntax far more powerful and convenient.&lt;/p&gt;
  554. &lt;h4&gt;Why do you keep the type the same for places like &lt;code&gt;a.b.c&lt;/code&gt;?&lt;/h4&gt;
  555. &lt;p&gt;I want to ensure that the type of &lt;code&gt;a.b.c&lt;/code&gt; is the same wherever it is type-checked, it’ll simplify the compiler somewhat and just generally makes it easier to move code into and out of a closure.&lt;/p&gt;
  556. &lt;h4&gt;Why the move keyword?&lt;/h4&gt;
  557. &lt;p&gt;Because it’s there? To be honest, I don’t like the choice of &lt;code&gt;move&lt;/code&gt; because it’s so &lt;em&gt;operational&lt;/em&gt;. I think if I could go back, I would try to refashion our closures around two concepts&lt;/p&gt;
  558. &lt;ul&gt;
  559. &lt;li&gt;&lt;em&gt;Attached&lt;/em&gt; closures (what we now call &lt;code&gt;||&lt;/code&gt;) would &lt;em&gt;always&lt;/em&gt; be tied to the enclosing stack frame. They’d always have a lifetime even if they don’t capture anything.&lt;/li&gt;
  560. &lt;li&gt;&lt;em&gt;Detached&lt;/em&gt; closures (what we now call &lt;code&gt;move ||&lt;/code&gt;) would capture by-value, like &lt;code&gt;move&lt;/code&gt; today.&lt;/li&gt;
  561. &lt;/ul&gt;
  562. &lt;p&gt;I think this would help to build up the intuition of “use &lt;code&gt;detach ||&lt;/code&gt; if you are going to return the closure from the current stack frame and use &lt;code&gt;||&lt;/code&gt; otherwise”.&lt;/p&gt;
  563. &lt;h4&gt;What would a max-min explicit capture proposal look like?&lt;/h4&gt;
  564. &lt;p&gt;A maximally minimal explicit capture close proposal would probably &lt;em&gt;just&lt;/em&gt; let you name specific variables and not “subplaces”:&lt;/p&gt;
  565. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  566. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b_c&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  567. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x_y&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;y&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  568. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;||&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  569. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;*&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x_y&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;+&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a_b_c&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  570. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  571. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;I think you can see though that this makes introducing an explicit form a lot less pleasant to use and hence isn’t really going to do anything to support ergonomic RC.&lt;/p&gt;
  572. &lt;h3&gt;Conclusion: Explicit closure clauses make things better, but not great&lt;/h3&gt;
  573. &lt;p&gt;I think doing explicit capture clauses is a good idea – I generally think we should have explicit syntax for everything in Rust, for teaching and explanatory purposes if nothing else; I didn’t always think this way, but it’s something I’ve come to appreciate over time.&lt;/p&gt;
  574. &lt;p&gt;I’m not sold on this specific proposal – but I think working through it is useful, because it (a) gives you an idea of what the benefits would be and (b) gives you an idea of how much hidden complexity there is.&lt;/p&gt;
  575. &lt;p&gt;I think the proposal shows that adding explicit capture clauses goes &lt;em&gt;some&lt;/em&gt; way towards making things explicit &lt;em&gt;and&lt;/em&gt; ergonomic. Writing &lt;code&gt;move(a.b.c.clone())&lt;/code&gt; is definitely better than having to create a new binding.&lt;/p&gt;
  576. &lt;p&gt;But for me, it’s not really nice &lt;em&gt;enough&lt;/em&gt;. It’s still quite a mental distraction to have to find the start of the closure, insert the &lt;code&gt;a.b.c.clone()&lt;/code&gt; call, and it makes the closure header very long and unwieldy. Particularly for short closures the overhead is very high.&lt;/p&gt;
  577. &lt;p&gt;This is why I’d like to look into other options. Nonetheless, it’s useful to have discussed a proposal for an explicit form: if nothing else, it’ll be useful to explain the precise semantics of other proposals later on.&lt;/p&gt;</description>
  578. <pubDate>Wed, 22 Oct 2025 10:08:27 +0000</pubDate>
  579. </item>
  580. <item>
  581. <title>This Week In Rust: This Week in Rust 622</title>
  582. <guid isPermaLink="false">tag:this-week-in-rust.org,2025-10-22:/blog/2025/10/22/this-week-in-rust-622/</guid>
  583. <link>https://this-week-in-rust.org/blog/2025/10/22/this-week-in-rust-622/</link>
  584. <description>&lt;p&gt;Hello and welcome to another issue of &lt;em&gt;This Week in Rust&lt;/em&gt;!
  585. &lt;a href=&quot;https://www.rust-lang.org/&quot;&gt;Rust&lt;/a&gt; is a programming language empowering everyone to build reliable and efficient software.
  586. This is a weekly summary of its progress and community.
  587. Want something mentioned? Tag us at
  588. &lt;a href=&quot;https://bsky.app/profile/thisweekinrust.bsky.social&quot;&gt;@thisweekinrust.bsky.social&lt;/a&gt; on Bluesky or
  589. &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;@ThisWeekinRust&lt;/a&gt; on mastodon.social, or
  590. &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;send us a pull request&lt;/a&gt;.
  591. Want to get involved? &lt;a href=&quot;https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md&quot;&gt;We love contributions&lt;/a&gt;.&lt;/p&gt;
  592. &lt;p&gt;&lt;em&gt;This Week in Rust&lt;/em&gt; is openly developed &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;on GitHub&lt;/a&gt; and archives can be viewed at &lt;a href=&quot;https://this-week-in-rust.org/&quot;&gt;this-week-in-rust.org&lt;/a&gt;.
  593. If you find any errors in this week's issue, &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust/pulls&quot;&gt;please submit a PR&lt;/a&gt;.&lt;/p&gt;
  594. &lt;p&gt;Want TWIR in your inbox? &lt;a href=&quot;https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&amp;amp;id=0ed8b72485&quot;&gt;Subscribe here&lt;/a&gt;.&lt;/p&gt;
  595. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#updates-from-rust-community&quot;&gt;Updates from Rust Community&lt;/a&gt;&lt;/h4&gt;
  596.  
  597.  
  598. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#official&quot;&gt;Official&lt;/a&gt;&lt;/h5&gt;
  599. &lt;ul&gt;
  600. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/10/15/announcing-the-new-rust-project-directors-2025/&quot;&gt;Announcing the New Rust Project Directors&lt;/a&gt;&lt;/li&gt;
  601. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/10/16/docsrs-changed-default-targets/&quot;&gt;docs.rs: changed default targets&lt;/a&gt;&lt;/li&gt;
  602. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/inside-rust/2025/10/16/infrastructure-team-q3-recap-and-q4-plan/&quot;&gt;Infrastructure Team 2025 Q3 Recap and Q4 Plan&lt;/a&gt;&lt;/li&gt;
  603. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/inside-rust/2025/10/16/renaming-the-default-branch-of-rust-langrust/&quot;&gt;Renaming the default branch of rust-lang/rust&lt;/a&gt;&lt;/li&gt;
  604. &lt;/ul&gt;
  605. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#newsletters&quot;&gt;Newsletters&lt;/a&gt;&lt;/h5&gt;
  606. &lt;ul&gt;
  607. &lt;li&gt;&lt;a href=&quot;https://scientificcomputing.rs/monthly/2025-10&quot;&gt;Scientific Computing in Rust #11 (October 2025)&lt;/a&gt;&lt;/li&gt;
  608. &lt;/ul&gt;
  609. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#projecttooling-updates&quot;&gt;Project/Tooling Updates&lt;/a&gt;&lt;/h5&gt;
  610. &lt;ul&gt;
  611. &lt;li&gt;&lt;a href=&quot;https://www.sea-ql.org/blog/2025-10-20-sea-orm-2.0/&quot;&gt;SeaORM 2.0: new entity format and relational capabilities&lt;/a&gt;&lt;/li&gt;
  612. &lt;li&gt;&lt;a href=&quot;https://slint.dev/blog/slint-1.14-released&quot;&gt;Slint 1.14 Released&lt;/a&gt;&lt;/li&gt;
  613. &lt;li&gt;&lt;a href=&quot;https://danube-docs.dev-state.com/architecture/persistence/&quot;&gt;Danube Messaging - new topic persistence architecture (Wal + Cloud)&lt;/a&gt;&lt;/li&gt;
  614. &lt;li&gt;&lt;a href=&quot;https://tqwewe.com/blog/building-sierradb/&quot;&gt;SierraDB: A Distributed Event Store Built in Rust&lt;/a&gt;&lt;/li&gt;
  615. &lt;li&gt;&lt;a href=&quot;https://immunant.com/blog/2025/10/c2rust_release/&quot;&gt;Announcing C2Rust v0.21&lt;/a&gt;&lt;/li&gt;
  616. &lt;li&gt;&lt;a href=&quot;https://maguire.tech/posts/shove/&quot;&gt;&lt;code&gt;Shove&lt;/code&gt; Project Writeup&lt;/a&gt;&lt;/li&gt;
  617. &lt;li&gt;&lt;a href=&quot;https://news.ycombinator.com/item?id=45624186&quot;&gt;ServiceRadar - Open Source Network Management and Observability&lt;/a&gt; &lt;/li&gt;
  618. &lt;li&gt;&lt;a href=&quot;https://github.com/kyu08/fzf-make/releases/tag/v0.65.0&quot;&gt;fzf-make v0.65.0 is released! (A command line tool that executes commands using fuzzy finder)&lt;/a&gt;&lt;/li&gt;
  619. &lt;li&gt;&lt;a href=&quot;https://diesel.rs/assets/NGICore%20Diesel%20penetration%20test%20report%202025%201.0.pdf&quot;&gt;Diesel Code Audit Report&lt;/a&gt;&lt;/li&gt;
  620. &lt;/ul&gt;
  621. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#observationsthoughts&quot;&gt;Observations/Thoughts&lt;/a&gt;&lt;/h5&gt;
  622. &lt;ul&gt;
  623. &lt;li&gt;&lt;a href=&quot;https://lwn.net/SubscriberLink/1042172/c7e1cdef4a518cc3/&quot;&gt;Git considers SHA-256, Rust, LLMs, and more&lt;/a&gt;&lt;/li&gt;
  624. &lt;li&gt;&lt;a href=&quot;https://lwn.net/SubscriberLink/1041095/2ef0281b0fec4d9d/&quot;&gt;DebugFS on Rust&lt;/a&gt;&lt;/li&gt;
  625. &lt;li&gt;&lt;a href=&quot;https://medium.com/google-cloud/python-and-rust-interoperability-a-walkthrough-for-building-a-high-performance-mcp-server-56c04e4b651b&quot;&gt;Python and Rust interoperability&lt;/a&gt;&lt;/li&gt;
  626. &lt;li&gt;&lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2025/10/21/move-destruct-leak/&quot;&gt;Controlled Destruction in Rust: Towards Async Drop and Safer Resource Management&lt;/a&gt;&lt;/li&gt;
  627. &lt;li&gt;&lt;a href=&quot;https://daymare.net/blogs/everbody-so-creative/&quot;&gt;Everybody's so Creative!&lt;/a&gt;&lt;/li&gt;
  628. &lt;li&gt;&lt;a href=&quot;https://blog.goose.love/posts/organizing-a-feature-freeze/&quot;&gt;How we organized the Rust Clippy feature freeze&lt;/a&gt;&lt;/li&gt;
  629. &lt;li&gt;&lt;a href=&quot;https://alexsaveau.dev/blog/tips/generalizing-over-mutability-in-rust&quot;&gt;Generalizing over mutability in Rust&lt;/a&gt;&lt;/li&gt;
  630. &lt;li&gt;[audio] &lt;a href=&quot;https://netstack.fm/#episode-10&quot;&gt;Netstack.FM Episode 10 – zerocopy with Joshua Liebow-Feeser&lt;/a&gt;&lt;/li&gt;
  631. &lt;/ul&gt;
  632. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-walkthroughs&quot;&gt;Rust Walkthroughs&lt;/a&gt;&lt;/h5&gt;
  633. &lt;ul&gt;
  634. &lt;li&gt;&lt;a href=&quot;https://blog.vega.io/posts/partial_stream/&quot;&gt;Real-Time Results in a Federated Query Engine&lt;/a&gt;&lt;/li&gt;
  635. &lt;li&gt;&lt;a href=&quot;https://crustyengineer.com/blog/axum-multi-tenancy-abstract-repository-layer/&quot;&gt;Axum: Multi-tenancy (with Hexarch) and Abstracting the Repository&lt;/a&gt;&lt;/li&gt;
  636. &lt;li&gt;&lt;a href=&quot;https://tweedegolf.nl/en/blog/196/fixing-rust-lang-stdarch-issues-in-llvm&quot;&gt;Fixing rust-lang stdarch issues in LLVM - Blog - Tweede golf&lt;/a&gt;&lt;/li&gt;
  637. &lt;li&gt;&lt;a href=&quot;https://jorgeortiz.dev/posts/rust_unit_testing_test_doubles_spy/&quot;&gt;Rust unit testing: spies and dummy test doubles&lt;/a&gt;&lt;/li&gt;
  638. &lt;li&gt;&lt;a href=&quot;https://blog.0xshadow.dev/posts/backend-engineering-with-axum/axum-refresh-token-rotation/&quot;&gt;Axum Backend Series: Refresh Token Rotation and Reuse Detection&lt;/a&gt;&lt;/li&gt;
  639. &lt;li&gt;&lt;a href=&quot;https://medium.com/@carlmkadie/vibe-validation-with-lean-chatgpt-5-claude-4-5-part-1-c57b430b3d7a&quot;&gt;Vibe Validation with Lean, ChatGPT-5, &amp;amp; Claude 4.5: Nine Rules for Proving (Rust) Algorithms Correct Without Knowing Formal Methods (Part 1)&lt;/a&gt;&lt;/li&gt;
  640. &lt;li&gt;&lt;a href=&quot;https://rvarago.github.io/typed-evaluator-in-rust/&quot;&gt;A Typed Evaluator in Rust&lt;/a&gt;&lt;/li&gt;
  641. &lt;li&gt;&lt;a href=&quot;https://orxfun.github.io/orxfun-notes/#/zero-cost-composition-2025-10-15&quot;&gt;Zero Cost Composition and the Power of GATs&lt;/a&gt;&lt;/li&gt;
  642. &lt;li&gt;&lt;a href=&quot;https://www.unwoundstack.com/blog/integration-testing-rust-binaries.html&quot;&gt;Integration Testing Rust Binary Crates&lt;/a&gt;&lt;/li&gt;
  643. &lt;li&gt;[video] &lt;a href=&quot;https://www.youtube.com/watch?v=hpGDCbO31Rg&quot;&gt;Build with Naz : How to speed up Rust compiler for different workflows&lt;/a&gt;&lt;/li&gt;
  644. &lt;/ul&gt;
  645. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#miscellaneous&quot;&gt;Miscellaneous&lt;/a&gt;&lt;/h5&gt;
  646. &lt;ul&gt;
  647. &lt;li&gt;&lt;a href=&quot;https://filtra.io/rust/jobs-report/sep-25&quot;&gt;September 2025 Rust Jobs Report&lt;/a&gt;&lt;/li&gt;
  648. &lt;/ul&gt;
  649. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#crate-of-the-week&quot;&gt;Crate of the Week&lt;/a&gt;&lt;/h4&gt;
  650. &lt;p&gt;This week's crate is &lt;a href=&quot;https://docs.rs/extend_mut&quot;&gt;extend_mut&lt;/a&gt;, a library to safely extend the lifetime of an exclusive reference under some constraints.P&lt;/p&gt;
  651. &lt;p&gt;Thanks to &lt;a href=&quot;https://users.rust-lang.org/t/crate-of-the-week/2704/1482&quot;&gt;Oleksandr Babak&lt;/a&gt; for the self-suggestion!&lt;/p&gt;
  652. &lt;p&gt;&lt;a href=&quot;https://users.rust-lang.org/t/crate-of-the-week/2704&quot;&gt;Please submit your suggestions and votes for next week&lt;/a&gt;!&lt;/p&gt;
  653. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#calls-for-testing&quot;&gt;Calls for Testing&lt;/a&gt;&lt;/h4&gt;
  654. &lt;p&gt;An important step for RFC implementation is for people to experiment with the
  655. implementation and give feedback, especially before stabilization.&lt;/p&gt;
  656. &lt;p&gt;If you are a feature implementer and would like your RFC to appear in this list, add a
  657. &lt;code&gt;call-for-testing&lt;/code&gt; label to your RFC along with a comment providing testing instructions and/or
  658. guidance on which aspect(s) of the feature need testing.&lt;/p&gt;
  659. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/labels/call-for-testing&quot;&gt;Cargo&lt;/a&gt;
  660. * &lt;a href=&quot;https://github.com/rust-lang/cargo/issues/12207&quot;&gt;Tracking Issue for cargo-script RFC 3424&lt;/a&gt;
  661.  * &lt;a href=&quot;https://github.com/rust-lang/cargo/issues/12207#issuecomment-3412997290&quot;&gt;Testing Steps&lt;/a&gt;&lt;/p&gt;
  662. &lt;ul&gt;
  663. &lt;li&gt;&lt;em&gt;No calls for testing were issued this week by
  664.  &lt;a href=&quot;https://github.com/rust-lang/rust/labels/call-for-testing&quot;&gt;Rust&lt;/a&gt;,
  665.  &lt;a href=&quot;https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing&quot;&gt;Rust language RFCs&lt;/a&gt; or
  666.  &lt;a href=&quot;https://github.com/rust-lang/rustup/labels/call-for-testing&quot;&gt;Rustup&lt;/a&gt;.&lt;/em&gt;&lt;/li&gt;
  667. &lt;/ul&gt;
  668. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust/issues&quot;&gt;Let us know&lt;/a&gt; if you would like your feature to be tracked as a part of this list.&lt;/p&gt;
  669. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing&quot;&gt;RFCs&lt;/a&gt;&lt;/h5&gt;
  670. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/labels/call-for-testing&quot;&gt;Rust&lt;/a&gt;&lt;/h5&gt;
  671. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rustup&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rustup/labels/call-for-testing&quot;&gt;Rustup&lt;/a&gt;&lt;/h5&gt;
  672. &lt;p&gt;If you are a feature implementer and would like your RFC to appear on the above list, add the new &lt;code&gt;call-for-testing&lt;/code&gt;
  673. label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
  674. need testing.&lt;/p&gt;
  675. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers&quot;&gt;Call for Participation; projects and speakers&lt;/a&gt;&lt;/h4&gt;
  676. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cfp-projects&quot;&gt;CFP - Projects&lt;/a&gt;&lt;/h5&gt;
  677. &lt;p&gt;Always wanted to contribute to open-source projects but did not know where to start?
  678. Every week we highlight some tasks from the Rust community for you to pick and get started!&lt;/p&gt;
  679. &lt;p&gt;Some of these tasks may also have mentors available, visit the task page for more information.&lt;/p&gt;
  680.  
  681.  
  682.  
  683.  
  684. &lt;ul&gt;
  685. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/issues/4764&quot;&gt;Diesel - Improve documentation for Postgres loading modes&lt;/a&gt;&lt;/li&gt;
  686. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/issues/4216&quot;&gt;Diesel - Add support for currently unsupported postgres json/jsonb functions&lt;/a&gt;&lt;/li&gt;
  687. &lt;/ul&gt;
  688. &lt;p&gt;If you are a Rust project owner and are looking for contributors, please submit tasks &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines&quot;&gt;here&lt;/a&gt; or through a &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;PR to TWiR&lt;/a&gt; or by reaching out on &lt;a href=&quot;https://bsky.app/profile/thisweekinrust.bsky.social&quot;&gt;Bluesky&lt;/a&gt; or &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;Mastodon&lt;/a&gt;!&lt;/p&gt;
  689. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cfp-events&quot;&gt;CFP - Events&lt;/a&gt;&lt;/h5&gt;
  690. &lt;p&gt;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.&lt;/p&gt;
  691.  
  692.  
  693.  
  694. &lt;ul&gt;
  695. &lt;li&gt;&lt;a href=&quot;https://tokio.rs/blog/2025-09-26-announcing-tokio-conf-cfp&quot;&gt;&lt;strong&gt;TokioConf 2026&lt;/strong&gt;&lt;/a&gt;| CFP closes 2025-12-08 | Portland, Oregon, USA | 2026-04-20&lt;/li&gt;
  696. &lt;/ul&gt;
  697. &lt;p&gt;If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;PR to TWiR&lt;/a&gt; or by reaching out on &lt;a href=&quot;https://bsky.app/profile/thisweekinrust.bsky.social&quot;&gt;Bluesky&lt;/a&gt; or &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;Mastodon&lt;/a&gt;!&lt;/p&gt;
  698. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#updates-from-the-rust-project&quot;&gt;Updates from the Rust Project&lt;/a&gt;&lt;/h4&gt;
  699. &lt;p&gt;369 pull requests were &lt;a href=&quot;https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2025-10-14..2025-10-21&quot;&gt;merged in the last week&lt;/a&gt;&lt;/p&gt;
  700. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#compiler&quot;&gt;Compiler&lt;/a&gt;&lt;/h6&gt;
  701. &lt;ul&gt;
  702. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147619&quot;&gt;add a &lt;code&gt;!=&lt;/code&gt; check to &lt;code&gt;ChunkedBitSet::union&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  703. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147630&quot;&gt;bitset cleanups&lt;/a&gt;&lt;/li&gt;
  704. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147695&quot;&gt;&lt;code&gt;deduced_param_attrs&lt;/code&gt;: check Freeze on monomorphic types&lt;/a&gt;&lt;/li&gt;
  705. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146167&quot;&gt;deny-by-default never type lints&lt;/a&gt;&lt;/li&gt;
  706. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147577&quot;&gt;improve error message for ambiguous numeric types in closure parameters&lt;/a&gt;&lt;/li&gt;
  707. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146221&quot;&gt;remove boxes from AST list elements&lt;/a&gt;&lt;/li&gt;
  708. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147508&quot;&gt;&lt;code&gt;TaskDeps&lt;/code&gt; improvements&lt;/a&gt;&lt;/li&gt;
  709. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147382&quot;&gt;&lt;code&gt;unused_must_use&lt;/code&gt;: Don't warn on &lt;code&gt;Result&amp;lt;(), Uninhabited&amp;gt;&lt;/code&gt; or &lt;code&gt;ControlFlow&amp;lt;Uninhabited, ()&amp;gt;&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  710. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147644&quot;&gt;use regular Vec in BitSet&lt;/a&gt;&lt;/li&gt;
  711. &lt;/ul&gt;
  712. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#library&quot;&gt;Library&lt;/a&gt;&lt;/h6&gt;
  713. &lt;ul&gt;
  714. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147708&quot;&gt;const &lt;code&gt;mem::drop&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  715. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146976&quot;&gt;constify basic Clone impls&lt;/a&gt;&lt;/li&gt;
  716. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147258&quot;&gt;iter repeat: panic on last&lt;/a&gt;&lt;/li&gt;
  717. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146841&quot;&gt;stabilise &lt;code&gt;rotate_left&lt;/code&gt; and &lt;code&gt;rotate_right&lt;/code&gt; in &lt;code&gt;[_]&lt;/code&gt; as &lt;code&gt;const fn&lt;/code&gt; items&lt;/a&gt;&lt;/li&gt;
  718. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/143191&quot;&gt;stabilize &lt;code&gt;rwlock_downgrade&lt;/code&gt; library feature&lt;/a&gt;&lt;/li&gt;
  719. &lt;/ul&gt;
  720. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cargo&quot;&gt;Cargo&lt;/a&gt;&lt;/h6&gt;
  721. &lt;ul&gt;
  722. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16127&quot;&gt;&lt;code&gt;check&lt;/code&gt;: Fix suggested command for bin package&lt;/a&gt;&lt;/li&gt;
  723. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16120&quot;&gt;&lt;code&gt;script&lt;/code&gt;: Remove name sanitiztion outside what is strictly required&lt;/a&gt;&lt;/li&gt;
  724. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16086&quot;&gt;&lt;code&gt;script&lt;/code&gt;: Tweak cargo script build-dir / target-dir&lt;/a&gt;&lt;/li&gt;
  725. &lt;/ul&gt;
  726. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rustdoc&quot;&gt;Rustdoc&lt;/a&gt;&lt;/h6&gt;
  727. &lt;ul&gt;
  728. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147660&quot;&gt;search: stringdex 0.0.2&lt;/a&gt;&lt;/li&gt;
  729. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147809&quot;&gt;fix passes order so intra-doc links are collected after stripping passes&lt;/a&gt;&lt;/li&gt;
  730. &lt;/ul&gt;
  731. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#clippy&quot;&gt;Clippy&lt;/a&gt;&lt;/h6&gt;
  732. &lt;ul&gt;
  733. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15911&quot;&gt;&lt;code&gt;empty_enum&lt;/code&gt;: don't lint if all variants happen to be &lt;code&gt;cfg&lt;/code&gt;-d out&lt;/a&gt;&lt;/li&gt;
  734. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15870&quot;&gt;&lt;code&gt;option_option&lt;/code&gt;: split part of diagnostic message into help message&lt;/a&gt;&lt;/li&gt;
  735. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15678&quot;&gt;&lt;code&gt;unnecessary_safety_comment&lt;/code&gt; Some fixes regarding comments above attributes&lt;/a&gt;&lt;/li&gt;
  736. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15862&quot;&gt;allow &lt;code&gt;explicit_write&lt;/code&gt; in tests&lt;/a&gt;&lt;/li&gt;
  737. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15706&quot;&gt;dereference argument of &lt;code&gt;manual_div_ceil()&lt;/code&gt; if needed&lt;/a&gt;&lt;/li&gt;
  738. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15402&quot;&gt;&lt;code&gt;manual_rotate&lt;/code&gt;: also recognize non-consts&lt;/a&gt;&lt;/li&gt;
  739. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15632&quot;&gt;overhaul &lt;code&gt;mutex_{atomic,integer}&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  740. &lt;/ul&gt;
  741. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-analyzer&quot;&gt;Rust-Analyzer&lt;/a&gt;&lt;/h6&gt;
  742. &lt;ul&gt;
  743. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20854&quot;&gt;parser: Don't error on frontmatter&lt;/a&gt;&lt;/li&gt;
  744. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20855&quot;&gt;improve fixture support&lt;/a&gt;&lt;/li&gt;
  745. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20880&quot;&gt;fix invalid RestPat for &lt;code&gt;convert_tuple_struct_to_named_struct&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  746. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20872&quot;&gt;fix missing RestPat for &lt;code&gt;convert_named_struct_to_tuple_struct&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  747. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20838&quot;&gt;don't make &lt;code&gt;convert_to_guarded_return&lt;/code&gt; applicable on &lt;code&gt;let-else&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  748. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20876&quot;&gt;fix &lt;code&gt;signature_help&lt;/code&gt; to proto conversion creating invalid utf16 offsets&lt;/a&gt;&lt;/li&gt;
  749. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20673&quot;&gt;support &lt;code&gt;break&lt;/code&gt; with value in completions&lt;/a&gt;&lt;/li&gt;
  750. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20758&quot;&gt;support &lt;code&gt;else&lt;/code&gt; blocks with &lt;code&gt;!&lt;/code&gt; return type in &lt;code&gt;convert_to_guarded_return&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  751. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20772&quot;&gt;support &lt;code&gt;match&lt;/code&gt; inside &lt;code&gt;if&lt;/code&gt; in &lt;code&gt;pull_assignment_up&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  752. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20841&quot;&gt;migrate more stuff to the next solver&lt;/a&gt;&lt;/li&gt;
  753. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20867&quot;&gt;migrate variance to the next solver and remove lint allows from its stuff&lt;/a&gt;&lt;/li&gt;
  754. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20873&quot;&gt;rip Chalk out of the codebase 🎉&lt;/a&gt;&lt;/li&gt;
  755. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20858&quot;&gt;support underscore suffix parameter hide inlayHints&lt;/a&gt;&lt;/li&gt;
  756. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20757&quot;&gt;use &lt;code&gt;FileId::MAX&lt;/code&gt; for id assertion in &lt;code&gt;PathInterner::intern&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  757. &lt;/ul&gt;
  758. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage&quot;&gt;Rust Compiler Performance Triage&lt;/a&gt;&lt;/h5&gt;
  759. &lt;p&gt;Fairly busy week, with lots of mixed results. However, overall we ended with a
  760. slight improvement on average.&lt;/p&gt;
  761. &lt;p&gt;Triage done by &lt;strong&gt;@simulacrum&lt;/strong&gt;.
  762. Revision range: &lt;a href=&quot;https://perf.rust-lang.org/?start=956f47c32f1bd97b22cd702d7ccf78f0f0d42c34&amp;amp;end=4068bafedd8ba724e332a5221c06a6fa531a30d2&amp;amp;absolute=false&amp;amp;stat=instructions%3Au&quot;&gt;956f47c3..4068bafe&lt;/a&gt;&lt;/p&gt;
  763. &lt;p&gt;2 Regressions, 5 Improvements, 10 Mixed; 5 of them in rollups&lt;/p&gt;
  764. &lt;p&gt;39 artifact comparisons made in total&lt;/p&gt;
  765. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/rustc-perf/blob/master/triage/2025/2025-10-20.md&quot;&gt;Full report here&lt;/a&gt;&lt;/p&gt;
  766. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#approved-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/commits/master&quot;&gt;Approved RFCs&lt;/a&gt;&lt;/h5&gt;
  767. &lt;p&gt;Changes to Rust follow the Rust &lt;a href=&quot;https://github.com/rust-lang/rfcs#rust-rfcs&quot;&gt;RFC (request for comments) process&lt;/a&gt;. These
  768. are the RFCs that were approved for implementation this week:&lt;/p&gt;
  769. &lt;ul&gt;
  770. &lt;li&gt;&lt;em&gt;No RFCs were approved this week.&lt;/em&gt;&lt;/li&gt;
  771. &lt;/ul&gt;
  772. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#final-comment-period&quot;&gt;Final Comment Period&lt;/a&gt;&lt;/h5&gt;
  773. &lt;p&gt;Every week, &lt;a href=&quot;https://www.rust-lang.org/team.html&quot;&gt;the team&lt;/a&gt; announces the 'final comment period' for RFCs and key PRs
  774. which are reaching a decision. Express your opinions now.&lt;/p&gt;
  775. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#tracking-issues-prs&quot;&gt;Tracking Issues &amp;amp; PRs&lt;/a&gt;&lt;/h6&gt;
  776. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust_1&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Rust&lt;/a&gt;
  777. &lt;ul&gt;
  778. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/136306&quot;&gt;Tracking Issue for NEON fp16 intrinsics&lt;/a&gt;&lt;/li&gt;
  779. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146561&quot;&gt;Change &lt;code&gt;Location&amp;lt;'_&amp;gt;&lt;/code&gt; lifetime to &lt;code&gt;'static&lt;/code&gt; in &lt;code&gt;Panic[Hook]Info&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  780. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/126769&quot;&gt;Tracking Issue for &lt;code&gt;substr_range&lt;/code&gt; and related methods&lt;/a&gt;&lt;/li&gt;
  781. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147185&quot;&gt;repr(transparent): do not consider repr(C) types to be 1-ZST&lt;/a&gt;&lt;/li&gt;
  782. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145665&quot;&gt;Don't require &lt;code&gt;T: RefUnwindSafe&lt;/code&gt; for &lt;code&gt;vec::IntoIter&amp;lt;T&amp;gt;: UnwindSafe&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  783. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145974&quot;&gt;Stabilize -Zno-jump-tables into -Cjump-tables=bool&lt;/a&gt;&lt;/li&gt;
  784. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/55724&quot;&gt;Tracking issue for alloc_layout_extra&lt;/a&gt;&lt;/li&gt;
  785. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147136&quot;&gt;Add warn-by-default lint for visibility on &lt;code&gt;const _&lt;/code&gt; declarations&lt;/a&gt;&lt;/li&gt;
  786. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/117729&quot;&gt;Tracking Issue for &lt;code&gt;debug_closure_helpers&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  787. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146882&quot;&gt;fully deprecate the legacy integral modules&lt;/a&gt;&lt;/li&gt;
  788. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/146705&quot;&gt;Tracking Issue for &lt;code&gt;fmt_from_fn&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  789. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/144090&quot;&gt;Make &lt;code&gt;IoSlice&lt;/code&gt; and &lt;code&gt;IoSliceMut&lt;/code&gt; methods unstably const&lt;/a&gt;&lt;/li&gt;
  790. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/135889&quot;&gt;Tracking Issue for &lt;code&gt;VecDeque::pop_front_if&lt;/code&gt; &amp;amp; &lt;code&gt;VecDeque::pop_back_if&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  791. &lt;li&gt;[disposition: unspecified] &lt;a href=&quot;https://github.com/rust-lang/rust/pull/145628&quot;&gt;[std][BTree] Fix behavior of &lt;code&gt;::append&lt;/code&gt; to match documentation, &lt;code&gt;::insert&lt;/code&gt;, and &lt;code&gt;::extend&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  792. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/144113&quot;&gt;Impls and impl items inherit &lt;code&gt;dead_code&lt;/code&gt; lint level of the corresponding traits and trait items&lt;/a&gt;&lt;/li&gt;
  793. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/140463&quot;&gt;Document MaybeUninit bit validity&lt;/a&gt;&lt;/li&gt;
  794. &lt;/ul&gt;
  795. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#compiler-team-mcps-only&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20%20label%3Afinal-comment-period&quot;&gt;Compiler Team&lt;/a&gt; &lt;a href=&quot;https://forge.rust-lang.org/compiler/mcp.html&quot;&gt;(MCPs only)&lt;/a&gt;
  796. &lt;ul&gt;
  797. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/compiler-team/issues/931&quot;&gt;Move unreachable code lint from HIR type check to a proper lint&lt;/a&gt;&lt;/li&gt;
  798. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/compiler-team/issues/930&quot;&gt;Rename &lt;code&gt;//@ add-core-stubs&lt;/code&gt; to &lt;code&gt;//@ add-minicore&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  799. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/compiler-team/issues/928&quot;&gt;Move annotation for profiling compiler-generated moves and copies.&lt;/a&gt;&lt;/li&gt;
  800. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/compiler-team/issues/927&quot;&gt;Use &lt;code&gt;llvm-bitcode-linker&lt;/code&gt; as the default linker for nvptx64-nvidia-cuda&lt;/a&gt;&lt;/li&gt;
  801. &lt;/ul&gt;
  802. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#leadership-council&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period&quot;&gt;Leadership Council&lt;/a&gt;
  803. &lt;ul&gt;
  804. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/leadership-council/issues/232&quot;&gt;Delegate GSoC money spending to the t-mentorship team&lt;/a&gt;&lt;/li&gt;
  805. &lt;/ul&gt;
  806. &lt;p&gt;&lt;em&gt;No Items entered Final Comment Period this week for
  807. &lt;a href=&quot;https://github.com/rust-lang/rfcs/labels/final-comment-period&quot;&gt;Rust RFCs&lt;/a&gt;,
  808. &lt;a href=&quot;https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Cargo&lt;/a&gt;,
  809. &lt;a href=&quot;https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+&quot;&gt;Language Team&lt;/a&gt;,
  810. &lt;a href=&quot;https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Language Reference&lt;/a&gt; or
  811. &lt;a href=&quot;https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Unsafe Code Guidelines&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
  812. &lt;p&gt;Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.&lt;/p&gt;
  813. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#new-and-updated-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/pulls&quot;&gt;New and Updated RFCs&lt;/a&gt;&lt;/h6&gt;
  814. &lt;ul&gt;
  815. &lt;li&gt;&lt;em&gt;No New or Updated RFCs were created this week.&lt;/em&gt;&lt;/li&gt;
  816. &lt;/ul&gt;
  817. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#upcoming-events&quot;&gt;Upcoming Events&lt;/a&gt;&lt;/h4&gt;
  818. &lt;p&gt;Rusty Events between 2025-10-22 - 2025-11-19 🦀&lt;/p&gt;
  819. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#virtual&quot;&gt;Virtual&lt;/a&gt;&lt;/h5&gt;
  820. &lt;ul&gt;
  821. &lt;li&gt;2025-10-22 | Virtual (Boulder, CO, US) | &lt;a href=&quot;https://www.meetup.com/boulder-elixir/events/&quot;&gt;Boulder Elixir&lt;/a&gt;&lt;ul&gt;
  822. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/boulder-elixir/events/310996627/&quot;&gt;&lt;strong&gt;Integrating Elixir and Apache DataFusion with Rustler&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  823. &lt;/ul&gt;
  824. &lt;/li&gt;
  825. &lt;li&gt;2025-10-22 | Virtual (Buenos Aires, AR) | &lt;a href=&quot;https://www.meetup.com/es-ES/net-baires/&quot;&gt;[Net-Baires] Comunidad de .NET en Buenos Aires&lt;/a&gt;&lt;ul&gt;
  826. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/es-ES/net-baires/events/311365783/&quot;&gt;&lt;strong&gt;Rust para devs .NET | Community Standup #10&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  827. &lt;/ul&gt;
  828. &lt;/li&gt;
  829. &lt;li&gt;2025-10-23 | Hybrid (Seattle/Bellevue, WA, US) | &lt;a href=&quot;https://www.meetup.com/join-srug&quot;&gt;Seattle Rust User Group&lt;/a&gt;&lt;ul&gt;
  830. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/seattle-rust-user-group/events/311351020/&quot;&gt;&lt;strong&gt;October, 2025 SRUG (Seattle Rust User Group) Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  831. &lt;/ul&gt;
  832. &lt;/li&gt;
  833. &lt;li&gt;2025-10-23 | Virtual (Berlin, DE) | &lt;a href=&quot;https://www.meetup.com/rust-berlin&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  834. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/306046641/&quot;&gt;&lt;strong&gt;Rust Hack and Learn&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  835. &lt;/ul&gt;
  836. &lt;/li&gt;
  837. &lt;li&gt;2025-10-23 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  838. &lt;li&gt;&lt;a href=&quot;https://luma.com/zyc3touy&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  839. &lt;/ul&gt;
  840. &lt;/li&gt;
  841. &lt;li&gt;2025-10-26 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  842. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109171/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  843. &lt;/ul&gt;
  844. &lt;/li&gt;
  845. &lt;li&gt;2025-10-28 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  846. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/305361444/&quot;&gt;&lt;strong&gt;Fourth Tuesday&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  847. &lt;/ul&gt;
  848. &lt;/li&gt;
  849. &lt;li&gt;2025-10-30 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  850. &lt;li&gt;&lt;a href=&quot;https://luma.com/t8yovmmm&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  851. &lt;/ul&gt;
  852. &lt;/li&gt;
  853. &lt;li&gt;2025-11-01 | Virtual (Kampala, UG) | &lt;a href=&quot;https://www.eventbrite.com/o/rust-circle-kampala-65249289033&quot;&gt;Rust Circle Meetup&lt;/a&gt;&lt;ul&gt;
  854. &lt;li&gt;&lt;a href=&quot;https://www.eventbrite.com/e/rust-circle-meetup-tickets-628763868657&quot;&gt;&lt;strong&gt;Rust Circle Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  855. &lt;/ul&gt;
  856. &lt;/li&gt;
  857. &lt;li&gt;2025-11-02 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  858. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109173/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  859. &lt;/ul&gt;
  860. &lt;/li&gt;
  861. &lt;li&gt;2025-11-05 | Virtual (Buffalo, NY, US) | &lt;a href=&quot;https://www.meetup.com/buffalo-rust-meetup&quot;&gt;Buffalo Rust Meetup&lt;/a&gt;&lt;ul&gt;
  862. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/buffalo-rust-meetup/events/305304242/&quot;&gt;&lt;strong&gt;Buffalo Rust User Group&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  863. &lt;/ul&gt;
  864. &lt;/li&gt;
  865. &lt;li&gt;2025-11-05 | Virtual (Indianapolis, IN, US) | &lt;a href=&quot;https://www.meetup.com/indyrs&quot;&gt;Indy Rust&lt;/a&gt;&lt;ul&gt;
  866. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/indyrs/events/311574520/&quot;&gt;&lt;strong&gt;Indy.rs - with Social Distancing&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  867. &lt;/ul&gt;
  868. &lt;/li&gt;
  869. &lt;li&gt;2025-11-05 | Virtual | &lt;a href=&quot;https://www.eventbrite.com/o/ardan-labs-7092394651&quot;&gt;Ardan Labs&lt;/a&gt;&lt;ul&gt;
  870. &lt;li&gt;&lt;a href=&quot;https://www.eventbrite.com/e/mastering-error-handling-in-rust-from-panics-to-thiserror-anyhow-tickets-1849030121869&quot;&gt;&lt;strong&gt;Mastering Error Handling in Rust: From Panics to thiserror &amp;amp; anyhow&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  871. &lt;/ul&gt;
  872. &lt;/li&gt;
  873. &lt;li&gt;2025-11-06 | Virtual (Berlin, DE) | &lt;a href=&quot;https://www.meetup.com/rust-berlin/events/&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  874. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/305646021/&quot;&gt;&lt;strong&gt;Rust Hack and Learn&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  875. &lt;/ul&gt;
  876. &lt;/li&gt;
  877. &lt;li&gt;2025-11-06 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  878. &lt;li&gt;&lt;a href=&quot;https://luma.com/xkd84gfz&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  879. &lt;/ul&gt;
  880. &lt;/li&gt;
  881. &lt;li&gt;2025-11-09 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust/events/&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  882. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109175/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  883. &lt;/ul&gt;
  884. &lt;/li&gt;
  885. &lt;li&gt;2025-11-10 || &lt;a href=&quot;https://www.bettercode.eu/&quot;&gt;BetterCode&lt;/a&gt;&lt;ul&gt;
  886. &lt;li&gt;$&lt;a href=&quot;https://dev.events/conferences/better-code-rust-i6inve6t&quot;&gt;&lt;strong&gt;betterCode() Industrielle Anwendungen mit Rust&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  887. &lt;/ul&gt;
  888. &lt;/li&gt;
  889. &lt;li&gt;2025-11-11 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust/events/&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  890. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/305361536/&quot;&gt;&lt;strong&gt;Second Tuesday&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  891. &lt;/ul&gt;
  892. &lt;/li&gt;
  893. &lt;li&gt;2025-11-11 | Virtual (London, GB) | &lt;a href=&quot;https://www.meetup.com/women-in-rust/events/&quot;&gt;Women in Rust&lt;/a&gt;&lt;ul&gt;
  894. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/women-in-rust/events/311068632/&quot;&gt;&lt;strong&gt;👋 Community Catch Up&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  895. &lt;/ul&gt;
  896. &lt;/li&gt;
  897. &lt;li&gt;2025-11-13 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  898. &lt;li&gt;&lt;a href=&quot;https://luma.com/yhe1xrhe&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  899. &lt;/ul&gt;
  900. &lt;/li&gt;
  901. &lt;li&gt;2025-11-13 | Virtual (Nürnberg, DE) | &lt;a href=&quot;https://www.meetup.com/rust-noris/events/&quot;&gt;Rust Nuremberg&lt;/a&gt;&lt;ul&gt;
  902. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-noris/events/310849154/&quot;&gt;&lt;strong&gt;Rust Nürnberg online&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  903. &lt;/ul&gt;
  904. &lt;/li&gt;
  905. &lt;li&gt;2025-11-16 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust/events/&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  906. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109181/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  907. &lt;/ul&gt;
  908. &lt;/li&gt;
  909. &lt;li&gt;2025-11-18 | Virtual (Washington, DC, US) | &lt;a href=&quot;https://www.meetup.com/rustdc/events/&quot;&gt;Rust DC&lt;/a&gt;&lt;ul&gt;
  910. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rustdc/events/310002262/&quot;&gt;&lt;strong&gt;Mid-month Rustful&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  911. &lt;/ul&gt;
  912. &lt;/li&gt;
  913. &lt;li&gt;2025-11-19 | Virtual (Vancouver, BC, CA) | &lt;a href=&quot;https://www.meetup.com/vancouver-rust/events/&quot;&gt;Vancouver Rust&lt;/a&gt;&lt;ul&gt;
  914. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/vancouver-rust/events/309926564/&quot;&gt;&lt;strong&gt;Rust Study/Hack/Hang-out&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  915. &lt;/ul&gt;
  916. &lt;/li&gt;
  917. &lt;/ul&gt;
  918. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#asia&quot;&gt;Asia&lt;/a&gt;&lt;/h5&gt;
  919. &lt;ul&gt;
  920. &lt;li&gt;2025-11-15 | Bangalore, IN | &lt;a href=&quot;https://hasgeek.com/rustbangalore&quot;&gt;Rust Bangalore&lt;/a&gt;&lt;ul&gt;
  921. &lt;li&gt;&lt;a href=&quot;https://hasgeek.com/rustbangalore/november-2025-rustacean-meetup//&quot;&gt;&lt;strong&gt;November 2025 Rustacean meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  922. &lt;/ul&gt;
  923. &lt;/li&gt;
  924. &lt;/ul&gt;
  925. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#europe&quot;&gt;Europe&lt;/a&gt;&lt;/h5&gt;
  926. &lt;ul&gt;
  927. &lt;li&gt;2025-10-23 | Edinburgh, UK | &lt;a href=&quot;https://www.meetup.com/rust-edi/events/&quot;&gt;Rust and Friends&lt;/a&gt;&lt;ul&gt;
  928. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-and-friends/events/311501254/&quot;&gt;&lt;strong&gt;Rust and Friends (evening pub)&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  929. &lt;/ul&gt;
  930. &lt;/li&gt;
  931. &lt;li&gt;2025-10-24 | Edinburgh, UK | &lt;a href=&quot;https://www.meetup.com/rust-edi/events/&quot;&gt;Rust and Friends&lt;/a&gt;&lt;ul&gt;
  932. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-and-friends/events/311501249/&quot;&gt;&lt;strong&gt;Rust and Friends (daytime coffee)&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  933. &lt;/ul&gt;
  934. &lt;/li&gt;
  935. &lt;li&gt;2025-10-28 | Manchester, UK | &lt;a href=&quot;https://www.meetup.com/rust-manchester&quot;&gt;Rust Manchester&lt;/a&gt;&lt;ul&gt;
  936. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-manchester/events/307919171/&quot;&gt;&lt;strong&gt;Rust Manchester October Code Night&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  937. &lt;/ul&gt;
  938. &lt;/li&gt;
  939. &lt;li&gt;2025-10-29 | Dortmund, DE | &lt;a href=&quot;https://www.meetup.com/rust-dortmund/events/&quot;&gt;Rust Dortmund&lt;/a&gt;&lt;ul&gt;
  940. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-dortmund/events/311251545/&quot;&gt;&lt;strong&gt;Rust Dortmund Meetup October 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  941. &lt;/ul&gt;
  942. &lt;/li&gt;
  943. &lt;li&gt;2025-10-30 | Copenhagen, DK | &lt;a href=&quot;https://www.meetup.com/copenhagen-rust-community&quot;&gt;Copenhagen Rust Community&lt;/a&gt;&lt;ul&gt;
  944. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/copenhagen-rust-community/events/311405044/&quot;&gt;&lt;strong&gt;Rust meetup #62 sponsored by Google!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  945. &lt;/ul&gt;
  946. &lt;/li&gt;
  947. &lt;li&gt;2025-10-30 | Prague, CZ | &lt;a href=&quot;https://www.meetup.com/rust-prague&quot;&gt;Rust Prague&lt;/a&gt;&lt;ul&gt;
  948. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-prague/events/310967094/&quot;&gt;&lt;strong&gt;Rust Meetup Prague (October 2025)&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  949. &lt;/ul&gt;
  950. &lt;/li&gt;
  951. &lt;li&gt;2025-11-01 | Stockholm, SE | &lt;a href=&quot;https://www.meetup.com/stockholm-rust/events/&quot;&gt;Stockholm Rust&lt;/a&gt;&lt;ul&gt;
  952. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/stockholm-rust/events/311582259/&quot;&gt;&lt;strong&gt;Ferris' Fika Forum #19&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  953. &lt;/ul&gt;
  954. &lt;/li&gt;
  955. &lt;li&gt;2025-11-02 - 2025-11-04 | Florence, IT | &lt;a href=&quot;https://rustlab.it/&quot;&gt;Rustlab 2025&lt;/a&gt;&lt;ul&gt;
  956. &lt;li&gt;$&lt;a href=&quot;https://rustlab.it/&quot;&gt;&lt;strong&gt;Rustlab 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  957. &lt;/ul&gt;
  958. &lt;/li&gt;
  959. &lt;li&gt;2025-11-03 | Bern, CH | &lt;a href=&quot;https://www.meetup.com/it-IT/guild42ch/&quot;&gt;Guild42&lt;/a&gt;&lt;ul&gt;
  960. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/it-IT/guild42ch/events/307260207/&quot;&gt;&lt;strong&gt;Moving out of systems programming into Kubernetes: is it time to adopt Rust ?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  961. &lt;/ul&gt;
  962. &lt;/li&gt;
  963. &lt;li&gt;2025-11-04 | Manchester, UK | &lt;a href=&quot;https://www.meetup.com/rust-manchester&quot;&gt;Rust Manchester&lt;/a&gt;&lt;ul&gt;
  964. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-manchester/events/310921632/&quot;&gt;&lt;strong&gt;Rust Manchester November Talk&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  965. &lt;/ul&gt;
  966. &lt;/li&gt;
  967. &lt;li&gt;2025-11-04 | Trondheim, NO | &lt;a href=&quot;https://www.meetup.com/rust-trondheim/events/&quot;&gt;Rust Trondheim&lt;/a&gt;&lt;ul&gt;
  968. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-trondheim/events/311595023/&quot;&gt;&lt;strong&gt;Optimizing matrix multiplication and building Python packages with Rust&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  969. &lt;/ul&gt;
  970. &lt;/li&gt;
  971. &lt;li&gt;2025-11-05 | Girona, ES | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  972. &lt;li&gt;&lt;a href=&quot;https://luma.com/xl8ob0tn&quot;&gt;&lt;strong&gt;Rust Girona Hack &amp;amp; Learn 11 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  973. &lt;/ul&gt;
  974. &lt;/li&gt;
  975. &lt;li&gt;2025-11-05 | Oslo, NO | &lt;a href=&quot;https://www.meetup.com/rust-oslo&quot;&gt;Rust Oslo&lt;/a&gt;&lt;ul&gt;
  976. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-oslo/events/310601872/&quot;&gt;&lt;strong&gt;Rust Hack'n'Learn at Kampen Bistro&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  977. &lt;/ul&gt;
  978. &lt;/li&gt;
  979. &lt;li&gt;2025-11-05 | Oxford, UK | &lt;a href=&quot;https://www.meetup.com/oxford-rust-meetup-group&quot;&gt;Oxford ACCU/Rust Meetup.&lt;/a&gt;&lt;ul&gt;
  980. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/oxford-rust-meetup-group/events/nnrkttyhcpbhb/&quot;&gt;&lt;strong&gt;Rust/ACCU meetup.&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  981. &lt;/ul&gt;
  982. &lt;/li&gt;
  983. &lt;li&gt;2025-11-06 | Gdansk, PL | &lt;a href=&quot;https://www.meetup.com/rust-gdansk/events/&quot;&gt;Rust Gdansk&lt;/a&gt;&lt;ul&gt;
  984. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-gdansk/events/310924266/&quot;&gt;&lt;strong&gt;Rust Gdansk Meetup #11&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  985. &lt;/ul&gt;
  986. &lt;/li&gt;
  987. &lt;li&gt;2025-11-12 | Reading, UK | &lt;a href=&quot;https://www.meetup.com/reading-rust-workshop/events/&quot;&gt;Reading Rust Workshop&lt;/a&gt;&lt;ul&gt;
  988. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/reading-rust-workshop/events/308944050/&quot;&gt;&lt;strong&gt;Reading Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  989. &lt;/ul&gt;
  990. &lt;/li&gt;
  991. &lt;li&gt;2025-11-13 | Geneva, CH | &lt;a href=&quot;https://www.posttenebraslab.ch/wiki/events/monthly_meeting/rust_meetup&quot;&gt;Rust Geneva&lt;/a&gt;&lt;ul&gt;
  992. &lt;li&gt;&lt;a href=&quot;https://www.posttenebraslab.ch/wiki/events/monthly_meeting/rust_meetup&quot;&gt;&lt;strong&gt;Rust Meetup Geneva&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  993. &lt;/ul&gt;
  994. &lt;/li&gt;
  995. &lt;li&gt;2025-11-13 | Paris, FR | &lt;a href=&quot;https://www.meetup.com/rust-paris/events/&quot;&gt;Rust Paris&lt;/a&gt;&lt;ul&gt;
  996. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-paris/events/311461594/&quot;&gt;&lt;strong&gt;Rust meetup #80&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  997. &lt;/ul&gt;
  998. &lt;/li&gt;
  999. &lt;li&gt;2025-11-18 | Leipzig, SN, DE | &lt;a href=&quot;https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/&quot;&gt;Rust - Modern Systems Programming in Leipzig&lt;/a&gt;&lt;ul&gt;
  1000. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/308592257/&quot;&gt;&lt;strong&gt;Topic TBD&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1001. &lt;/ul&gt;
  1002. &lt;/li&gt;
  1003. &lt;/ul&gt;
  1004. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#north-america&quot;&gt;North America&lt;/a&gt;&lt;/h5&gt;
  1005. &lt;ul&gt;
  1006. &lt;li&gt;2025-10-22 | Austin, TX, US | &lt;a href=&quot;https://www.meetup.com/rust-atx&quot;&gt;Rust ATX&lt;/a&gt;&lt;ul&gt;
  1007. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-atx/events/310457307/&quot;&gt;&lt;strong&gt;Rust Lunch - Fareground&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1008. &lt;/ul&gt;
  1009. &lt;/li&gt;
  1010. &lt;li&gt;2025-10-23 | Nashville, TN, US | &lt;a href=&quot;https://www.meetup.com/music-city-rust-developers&quot;&gt;Music City Rust Developers&lt;/a&gt;&lt;ul&gt;
  1011. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/music-city-rust-developers/events/304333267/&quot;&gt;&lt;strong&gt;Year In Review&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1012. &lt;/ul&gt;
  1013. &lt;/li&gt;
  1014. &lt;li&gt;2025-10-23 | Hybrid (Seattle/Bellevue, WA, US) | &lt;a href=&quot;https://www.meetup.com/join-srug&quot;&gt;Seattle Rust User Group&lt;/a&gt;&lt;ul&gt;
  1015. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/seattle-rust-user-group/events/311351020/&quot;&gt;&lt;strong&gt;October, 2025 SRUG (Seattle Rust User Group) Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1016. &lt;/ul&gt;
  1017. &lt;/li&gt;
  1018. &lt;li&gt;2025-10-23 | Spokane, WA, US | &lt;a href=&quot;https://www.meetup.com/spokane-rust&quot;&gt;Spokane Rust&lt;/a&gt;&lt;ul&gt;
  1019. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/spokane-rust/events/311346444/&quot;&gt;&lt;strong&gt;October Rust Meetup: A Special Presentation and Monthly Meetups are Back!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1020. &lt;/ul&gt;
  1021. &lt;/li&gt;
  1022. &lt;li&gt;2025-10-25 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  1023. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/310983712/&quot;&gt;&lt;strong&gt;Porter Square Rust Lunch, Oct 25&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1024. &lt;/ul&gt;
  1025. &lt;/li&gt;
  1026. &lt;li&gt;2025-10-25 | Dallas, TX, US | &lt;a href=&quot;https://www.meetup.com/dallasrust/events/&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  1027. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311562607/&quot;&gt;&lt;strong&gt;In-person Meetup with Collin College Software Engineering Club!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1028. &lt;/ul&gt;
  1029. &lt;/li&gt;
  1030. &lt;li&gt;2025-10-28 | Chicago, IL, US | &lt;a href=&quot;https://www.meetup.com/chicago-rust-meetup/events/&quot;&gt;Chicago Rust Meetup&lt;/a&gt;&lt;ul&gt;
  1031. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/chicago-rust-meetup/events/311603282/&quot;&gt;&lt;strong&gt;Rust Happy Hour&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1032. &lt;/ul&gt;
  1033. &lt;/li&gt;
  1034. &lt;li&gt;2025-10-29 | New York, NY, US | &lt;a href=&quot;https://www.meetup.com/rust-nyc/events/&quot;&gt;Rust NYC&lt;/a&gt;&lt;ul&gt;
  1035. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-nyc/events/311541108/&quot;&gt;&lt;strong&gt;Rust NYC: Scalable static analysis: confronting the halting problem&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1036. &lt;/ul&gt;
  1037. &lt;/li&gt;
  1038. &lt;li&gt;2025-10-30 | Atlanta, GA, US | &lt;a href=&quot;https://www.meetup.com/rust-atl&quot;&gt;Rust Atlanta&lt;/a&gt;&lt;ul&gt;
  1039. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-atl/events/308675988/&quot;&gt;&lt;strong&gt;Rust-Atl&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1040. &lt;/ul&gt;
  1041. &lt;/li&gt;
  1042. &lt;li&gt;2025-10-30 | Mountain View, CA, US | &lt;a href=&quot;https://www.meetup.com/hackerdojo/events/&quot;&gt;Hacker Dojo&lt;/a&gt;&lt;ul&gt;
  1043. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/hackerdojo/events/311273832/&quot;&gt;&lt;strong&gt;RUST MEETUP at HACKER DOJO&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1044. &lt;/ul&gt;
  1045. &lt;/li&gt;
  1046. &lt;li&gt;2025-11-01 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  1047. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/311039492/&quot;&gt;&lt;strong&gt;Chinatown Rust Lunch, Nov 1&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1048. &lt;/ul&gt;
  1049. &lt;/li&gt;
  1050. &lt;li&gt;2025-11-06 | Saint Louis, MO, US | &lt;a href=&quot;https://www.meetup.com/stl-rust/events/&quot;&gt;STL Rust&lt;/a&gt;&lt;ul&gt;
  1051. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/stl-rust/events/307251982/&quot;&gt;&lt;strong&gt;SIUE students on wasm 3D animations&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1052. &lt;/ul&gt;
  1053. &lt;/li&gt;
  1054. &lt;li&gt;2025-11-08 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust/events/&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  1055. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/311039501/&quot;&gt;&lt;strong&gt;Winter Hill Rust Lunch, Nov 8&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1056. &lt;/ul&gt;
  1057. &lt;/li&gt;
  1058. &lt;li&gt;2025-11-13 | Lehi, UT, US | &lt;a href=&quot;https://www.meetup.com/utah-rust/events/&quot;&gt;Utah Rust&lt;/a&gt;&lt;ul&gt;
  1059. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/utah-rust/events/311613658/&quot;&gt;&lt;strong&gt;Ipmap: Building Desktop Apps with Tauri&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1060. &lt;/ul&gt;
  1061. &lt;/li&gt;
  1062. &lt;li&gt;2025-11-18 | San Francisco, CA, US | &lt;a href=&quot;https://www.meetup.com/san-francisco-rust-study-group/events/&quot;&gt;San Francisco Rust Study Group&lt;/a&gt;&lt;ul&gt;
  1063. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/san-francisco-rust-study-group/events/308865806/&quot;&gt;&lt;strong&gt;Rust Hacking in Person&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1064. &lt;/ul&gt;
  1065. &lt;/li&gt;
  1066. &lt;/ul&gt;
  1067. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#oceania&quot;&gt;Oceania&lt;/a&gt;&lt;/h5&gt;
  1068. &lt;ul&gt;
  1069. &lt;li&gt;2025-10-22 | Perth, AU | &lt;a href=&quot;https://www.meetup.com/perth-rust-meetup-group&quot;&gt;Rust Perth Meetup Group&lt;/a&gt;&lt;ul&gt;
  1070. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/perth-rust-meetup-group/events/310847099/&quot;&gt;&lt;strong&gt;October Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1071. &lt;/ul&gt;
  1072. &lt;/li&gt;
  1073. &lt;li&gt;2025-10-28 | Barton, AU | &lt;a href=&quot;https://www.meetup.com/rust-canberra&quot;&gt;Canberra Rust User Group&lt;/a&gt;&lt;ul&gt;
  1074. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-canberra/events/311234237/&quot;&gt;&lt;strong&gt;October Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1075. &lt;/ul&gt;
  1076. &lt;/li&gt;
  1077. &lt;/ul&gt;
  1078. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#south-america&quot;&gt;South America&lt;/a&gt;&lt;/h5&gt;
  1079. &lt;ul&gt;
  1080. &lt;li&gt;2025-10-22 | Montevideo, UY | &lt;a href=&quot;https://www.meetup.com/rust-uruguay/events/&quot;&gt;Rust Meetup Uruguay&lt;/a&gt;&lt;ul&gt;
  1081. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-uruguay/events/311475675/&quot;&gt;&lt;strong&gt;Rust Uruguay meetup de Octubre&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1082. &lt;/ul&gt;
  1083. &lt;/li&gt;
  1084. &lt;li&gt;2025-10-25 | São Paulo, BR | &lt;a href=&quot;https://www.meetup.com/rust-sao-paulo-meetup&quot;&gt;Rust São Paulo Meetup&lt;/a&gt;&lt;ul&gt;
  1085. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-sao-paulo-meetup/events/311084440/&quot;&gt;&lt;strong&gt;Encontro do Rust-SP na Amazon Web Services&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1086. &lt;/ul&gt;
  1087. &lt;/li&gt;
  1088. &lt;li&gt;2025-10-30 | Florianopolis, BR | &lt;a href=&quot;https://luma.com/calendar/cal-iOloL5ZqswCO5Mm&quot;&gt;Rust Brasil&lt;/a&gt;&lt;ul&gt;
  1089. &lt;li&gt;&lt;a href=&quot;https://luma.com/lky7an18&quot;&gt;&lt;strong&gt;Rust Floripa&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  1090. &lt;/ul&gt;
  1091. &lt;/li&gt;
  1092. &lt;/ul&gt;
  1093. &lt;p&gt;If you are running a Rust event please add it to the &lt;a href=&quot;https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com&quot;&gt;calendar&lt;/a&gt; to get
  1094. it mentioned here. Please remember to add a link to the event too.
  1095. Email the &lt;a href=&quot;mailto:community-team@rust-lang.org&quot;&gt;Rust Community Team&lt;/a&gt; for access.&lt;/p&gt;
  1096. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#jobs&quot;&gt;Jobs&lt;/a&gt;&lt;/h4&gt;
  1097. &lt;p&gt;Please see the latest &lt;a href=&quot;https://www.reddit.com/r/rust/comments/1nknaii/official_rrust_whos_hiring_thread_for_jobseekers/&quot;&gt;Who's Hiring thread on r/rust&lt;/a&gt;&lt;/p&gt;
  1098. &lt;h3&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#quote-of-the-week&quot;&gt;Quote of the Week&lt;/a&gt;&lt;/h3&gt;
  1099. &lt;blockquote&gt;
  1100. &lt;p&gt;There used to be recurring questions about mod vs use in the user forum, until I've added a note to the error message [...] and I think it largely solved the problem&lt;/p&gt;
  1101. &lt;/blockquote&gt;
  1102. &lt;p&gt;– &lt;a href=&quot;https://internals.rust-lang.org/t/curly-brace-support-for-mod/23437/51&quot;&gt;Kornel on rust-internals&lt;/a&gt;&lt;/p&gt;
  1103. &lt;p&gt;Thanks to &lt;a href=&quot;https://users.rust-lang.org/t/twir-quote-of-the-week/328/1722&quot;&gt;Noratrieb&lt;/a&gt; for the suggestion!&lt;/p&gt;
  1104. &lt;p&gt;&lt;a href=&quot;https://users.rust-lang.org/t/twir-quote-of-the-week/328&quot;&gt;Please submit quotes and vote for next week!&lt;/a&gt;&lt;/p&gt;
  1105. &lt;p&gt;&lt;em&gt;This Week in Rust is edited by: &lt;a href=&quot;https://github.com/nellshamrell&quot;&gt;nellshamrell&lt;/a&gt;, &lt;a href=&quot;https://github.com/llogiq&quot;&gt;llogiq&lt;/a&gt;, &lt;a href=&quot;https://github.com/cdmistman&quot;&gt;cdmistman&lt;/a&gt;, &lt;a href=&quot;https://github.com/ericseppanen&quot;&gt;ericseppanen&lt;/a&gt;, &lt;a href=&quot;https://github.com/extrawurst&quot;&gt;extrawurst&lt;/a&gt;, &lt;a href=&quot;https://github.com/U007D&quot;&gt;U007D&lt;/a&gt;, &lt;a href=&quot;https://github.com/joelmarcey&quot;&gt;joelmarcey&lt;/a&gt;, &lt;a href=&quot;https://github.com/mariannegoldin&quot;&gt;mariannegoldin&lt;/a&gt;, &lt;a href=&quot;https://github.com/bennyvasquez&quot;&gt;bennyvasquez&lt;/a&gt;, &lt;a href=&quot;https://github.com/bdillo&quot;&gt;bdillo&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  1106. &lt;p&gt;&lt;em&gt;Email list hosting is sponsored by &lt;a href=&quot;https://foundation.rust-lang.org/&quot;&gt;The Rust Foundation&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  1107. &lt;p&gt;&lt;small&gt;&lt;a href=&quot;https://www.reddit.com/r/rust/comments/1odqrri/this_week_in_rust_622/&quot;&gt;Discuss on r/rust&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;</description>
  1108. <pubDate>Wed, 22 Oct 2025 04:00:00 +0000</pubDate>
  1109. <dc:creator>TWiR Contributors</dc:creator>
  1110. </item>
  1111. <item>
  1112. <title>Niko Matsakis: Move, Destruct, Forget, and Rust</title>
  1113. <guid isPermaLink="false">https://smallcultfollowing.com/babysteps/blog/2025/10/21/move-destruct-leak/</guid>
  1114. <link>https://smallcultfollowing.com/babysteps/blog/2025/10/21/move-destruct-leak/?utm_source=atom_feed</link>
  1115. <description>&lt;p&gt;This post presents a proposal to extend Rust to support a number of different kinds of destructors. This means we could async drop, but also prevent “forgetting” (leaking) values, enabling async scoped tasks that run in parallel à la rayon/libstd. We’d also be able to have types whose “destructors” require arguments. This proposal – an evolution of &lt;a href=&quot;https://smallcultfollowing.com/babysteps/ /blog/2023/03/16/must-move-types.html&quot;&gt;“must move”&lt;/a&gt; that I’ll call “controlled destruction” – is, I think, needed for Rust to live up to its goal of giving safe versions of critical patterns in systems programming. As such, it is needed to complete the “async dream”, in which async Rust and sync Rust work roughly the same.&lt;/p&gt;
  1116. &lt;p&gt;Nothing this good comes for free. The big catch of the proposal is that it introduces more “core splits” into Rust’s types. I believe these splits are well motivated and reasonable – they reflect &lt;em&gt;inherent complexity&lt;/em&gt;, in other words, but they are something we’ll want to think carefully about nonetheless.&lt;/p&gt;
  1117. &lt;h3&gt;Summary&lt;/h3&gt;
  1118. &lt;p&gt;The TL;DR of the proposal is that we should:&lt;/p&gt;
  1119. &lt;ul&gt;
  1120. &lt;li&gt;Introduce a new “default trait bound” &lt;code&gt;Forget&lt;/code&gt; and an associated trait hierarchy:
  1121. &lt;ul&gt;
  1122. &lt;li&gt;&lt;code&gt;trait Forget: Drop&lt;/code&gt;, representing values that can be forgotten&lt;/li&gt;
  1123. &lt;li&gt;&lt;code&gt;trait Destruct: Move&lt;/code&gt;, representing values with a destructor&lt;/li&gt;
  1124. &lt;li&gt;&lt;code&gt;trait Move: Pointee&lt;/code&gt;, representing values that can be moved&lt;/li&gt;
  1125. &lt;li&gt;&lt;code&gt;trait Pointee&lt;/code&gt;, the base trait that represents &lt;em&gt;any value&lt;/em&gt;&lt;/li&gt;
  1126. &lt;/ul&gt;
  1127. &lt;/li&gt;
  1128. &lt;li&gt;Use the “opt-in to weaker defaults” scheme proposed for sizedness by &lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3729&quot;&gt;RFC #3729 (Hierarchy of Sized Traits)&lt;/a&gt;
  1129. &lt;ul&gt;
  1130. &lt;li&gt;So &lt;code&gt;fn foo&amp;lt;T&amp;gt;(t: T)&lt;/code&gt; defaults to “a &lt;code&gt;T&lt;/code&gt; that can be forgotten/destructed/moved”&lt;/li&gt;
  1131. &lt;li&gt;And &lt;code&gt;fn foo&amp;lt;T: Destruct&amp;gt;(t: T)&lt;/code&gt; means “a &lt;code&gt;T&lt;/code&gt; that can be destructed, but not necessarily forgotten”&lt;/li&gt;
  1132. &lt;li&gt;And &lt;code&gt;fn foo&amp;lt;T: Move&amp;gt;(t: T)&lt;/code&gt; means “a &lt;code&gt;T&lt;/code&gt; that can be moved, but not necessarily forgotten”&lt;/li&gt;
  1133. &lt;li&gt;…and so forth.&lt;/li&gt;
  1134. &lt;/ul&gt;
  1135. &lt;/li&gt;
  1136. &lt;li&gt;Integrate and enforce the new traits:
  1137. &lt;ul&gt;
  1138. &lt;li&gt;The bound on &lt;code&gt;std::mem::forget&lt;/code&gt; will already require &lt;code&gt;Forget&lt;/code&gt;, so that’s good.&lt;/li&gt;
  1139. &lt;li&gt;Borrow check can enforce that any dropped value must implement &lt;code&gt;Destruct&lt;/code&gt;; in fact, we already do this to enforce &lt;code&gt;const Destruct&lt;/code&gt; bounds in &lt;code&gt;const fn&lt;/code&gt;.&lt;/li&gt;
  1140. &lt;li&gt;Borrow check can be extended to require a &lt;code&gt;Move&lt;/code&gt; bound on any moved value.&lt;/li&gt;
  1141. &lt;/ul&gt;
  1142. &lt;/li&gt;
  1143. &lt;li&gt;Adjust the trait bound on closures (luckily this works out fairly nicely)&lt;/li&gt;
  1144. &lt;/ul&gt;
  1145. &lt;h3&gt;Motivation&lt;/h3&gt;
  1146. &lt;p&gt;In a &lt;a href=&quot;https://nikomatsakis.github.io/rust-latam-2019/#1&quot;&gt;talk I gave some years back at Rust LATAM in Uruguay&lt;/a&gt;&lt;sup id=&quot;fnref:1&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:1&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;, I &lt;a href=&quot;https://nikomatsakis.github.io/rust-latam-2019/#81&quot;&gt;said this&lt;/a&gt;:&lt;/p&gt;
  1147. &lt;ul&gt;
  1148. &lt;li&gt;It’s easy to &lt;strong&gt;expose&lt;/strong&gt; a high-performance API.&lt;/li&gt;
  1149. &lt;li&gt;But it’s hard to &lt;strong&gt;help users control it&lt;/strong&gt; – and this is what Rust’s type system does.&lt;/li&gt;
  1150. &lt;/ul&gt;
  1151. &lt;img alt=&quot;Person casting a firespell and burning themselves&quot; src=&quot;https://smallcultfollowing.com/babysteps/ /assets/2025-movedestructleak/firespell.gif&quot; /&gt;
  1152. &lt;p&gt;Rust currently does a pretty good job with preventing parts of your program from interfering with one another, but we don’t do as good a job when it comes to guaranteeing that cleaup happens&lt;sup id=&quot;fnref:2&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:2&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;. We have destructors, of course, but they have two critical limitations:&lt;/p&gt;
  1153. &lt;ul&gt;
  1154. &lt;li&gt;All destructors must meet the same signature, &lt;code&gt;fn drop(&amp;amp;mut self)&lt;/code&gt;, which isn’t always adequate.&lt;/li&gt;
  1155. &lt;li&gt;There is no way to guarantee a destructor once you give up ownership of a value.&lt;/li&gt;
  1156. &lt;/ul&gt;
  1157. &lt;h4&gt;Making it concrete.&lt;/h4&gt;
  1158. &lt;p&gt;That motivation was fairly abstract, so let me give some concrete examples of things that tie back to this limitation:&lt;/p&gt;
  1159. &lt;ul&gt;
  1160. &lt;li&gt;The ability to have &lt;code&gt;async&lt;/code&gt; or &lt;code&gt;const&lt;/code&gt; drop, both of which require a distinct drop signature.&lt;/li&gt;
  1161. &lt;li&gt;The ability to have a “drop” operation that takes arguments, such as e.g. a message that must be sent, or a result code that must be provided before the program terminates.&lt;/li&gt;
  1162. &lt;li&gt;The ability to have async scopes that can access the stack, which requires a way to guarantee that a parallel thread will be joined even in an async context.&lt;/li&gt;
  1163. &lt;li&gt;The ability to integrate at maximum efficiency with WebAssembly async tasks, which require guaranteed cleanup.&lt;sup id=&quot;fnref:3&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:3&quot;&gt;3&lt;/a&gt;&lt;/sup&gt;&lt;/li&gt;
  1164. &lt;/ul&gt;
  1165. &lt;p&gt;The goal of this post is to outline an approach that could solve all of the above problems and which is backwards compatible with Rust today.&lt;/p&gt;
  1166. &lt;h4&gt;The “capabilities” of value disposal&lt;/h4&gt;
  1167. &lt;p&gt;The core problem is that Rust today assumes that every &lt;code&gt;Sized&lt;/code&gt; value can be moved, dropped, and forgotten:&lt;/p&gt;
  1168. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// Without knowing anything about `T` apart
  1169. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// from the fact that it's `Sized`, we can...
  1170. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;demonstration&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1171. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ...drop `a`, running its destructor immediately.
  1172. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;nb&quot;&gt;drop&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1173. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  1174. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ...forget `b`, skipping its destructor
  1175. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;forget&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1176. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  1177. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ...move `c` into `x`
  1178. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1179. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ...and then have `x` get dropped automatically,
  1180. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// as exit the block.
  1181. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h4&gt;Destructors are like “opt-out methods”&lt;/h4&gt;
  1182. &lt;p&gt;The way I see, most methods are “opt-in” – they don’t execute unless you call them. But destructors are different. They are effectively a method that runs by default – unless you opt-out, e.g., by calling &lt;code&gt;forget&lt;/code&gt;. But the ability to opt-out means that they don’t fundamentally add any power over regular methods, they just make for a more ergonomic API.&lt;/p&gt;
  1183. &lt;p&gt;The implication is that the only way in Rust today to &lt;em&gt;guarantee&lt;/em&gt; that a destructor will run is to retain ownership of the value. This can be important to unsafe code – APIs that permit scoped threads, for example, need to &lt;em&gt;guarantee&lt;/em&gt; that those parallel threads will be joined before the function returns. The only way they have to do that is to use a closure which gives &lt;code&gt;&amp;amp;&lt;/code&gt;-borrowed access to a &lt;code&gt;scope&lt;/code&gt;:&lt;/p&gt;
  1184. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;n&quot;&gt;scope&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;s&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;|&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1185. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//     -  --- ...which ensures that this
  1186. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;//     |      fn body cannot &quot;forget&quot; it.
  1187. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;//     |  
  1188. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// This value has type `&amp;amp;Scope`...
  1189. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Because the API nevers gives up ownership of the scope, it can ensure that it is never “forgotten” and thus that its destructor runs.&lt;/p&gt;
  1190. &lt;p&gt;The scoped thread approach works for sync code, but it doesn’t work for async code. The problem is that async functions return a future, which is a value. Users can therefore decide to “forget” this value, just like any other value, and thus the destructor may never run.&lt;/p&gt;
  1191. &lt;h4&gt;Guaranteed cleanup is common in systems programming&lt;/h4&gt;
  1192. &lt;p&gt;When you start poking around, you find that &lt;em&gt;guaranteed&lt;/em&gt; destructors turn up quite a bit in systems programming. Scoped APIs in futures are one example, but DMA (direct memory access) is another. Many embedded devices have a mode where you begin a DMA transfer that causes memory to be written into memory asynchronously. But you need to ensure that this DMA is terminated &lt;em&gt;before&lt;/em&gt; that memory is freed. If that memory is on your stack, that means you need a destructor that will either cancel or block until the DMA finishes.&lt;sup id=&quot;fnref:4&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:4&quot;&gt;4&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
  1193. &lt;h3&gt;So what can we do about it?&lt;/h3&gt;
  1194. &lt;p&gt;This situation is very analogous to the challenge of revisiting the default &lt;code&gt;Sized&lt;/code&gt; bound, and I think the same basic approach that I outlined in [this blog post][sized] will work.&lt;/p&gt;
  1195. &lt;p&gt;The core of the idea is simple: have a “special” set of traits arranged in a hierarchy:&lt;/p&gt;
  1196. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;trait&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Forget&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Destruct&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// Can be &quot;forgotten&quot;
  1197. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;trait&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Destruct&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;   &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// Can be &quot;destructed&quot; (dropped)
  1198. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;trait&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Move&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Pointee&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// Can be &quot;moved&quot;
  1199. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;trait&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Pointee&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;          &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// Can be referenced by pointer
  1200. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;By default, generic parameters get a &lt;code&gt;Forget&lt;/code&gt; bound, so &lt;code&gt;fn foo&amp;lt;T&amp;gt;()&lt;/code&gt; is equivalent to &lt;code&gt;fn foo&amp;lt;T: Forget&amp;gt;()&lt;/code&gt;. But if the parameter &lt;em&gt;opts in&lt;/em&gt; to a weaker bound, then the default is suppressed, so &lt;code&gt;fn bar&amp;lt;T: Destruct&amp;gt;()&lt;/code&gt; means that &lt;code&gt;T&lt;/code&gt; is assumed by “destructible” but &lt;em&gt;not&lt;/em&gt; forgettable. And &lt;code&gt;fn baz&amp;lt;T: Move&amp;gt;()&lt;/code&gt; indicates that &lt;code&gt;T&lt;/code&gt; can &lt;em&gt;only&lt;/em&gt; be moved.&lt;/p&gt;
  1201. &lt;h3&gt;Impact of these bounds&lt;/h3&gt;
  1202. &lt;p&gt;Let me explain briefly how these bounds would work.&lt;/p&gt;
  1203. &lt;h4&gt;The default can forget, drop, move etc&lt;/h4&gt;
  1204. &lt;p&gt;Given a default type &lt;code&gt;T&lt;/code&gt;, or one that writes &lt;code&gt;Forget&lt;/code&gt; explicitly, the function can do anything that is possible today:&lt;/p&gt;
  1205. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;just_forget&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Forget&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1206. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//         --------- this bound is the default
  1207. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;nb&quot;&gt;drop&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;   &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// OK
  1208. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;forget&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// OK
  1209. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;           &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// OK
  1210. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1211. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h4&gt;The forget function requires &lt;code&gt;T: Forget&lt;/code&gt;&lt;/h4&gt;
  1212. &lt;p&gt;The &lt;code&gt;std::mem::forget&lt;/code&gt; function would require &lt;code&gt;T: Forget&lt;/code&gt; as well:&lt;/p&gt;
  1213. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;pub&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;forget&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Forget&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;value&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* magic intrinsic */&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1214. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This means that if you have only &lt;code&gt;Destruct&lt;/code&gt;, the function can only drop or move, it can’t “forget”:&lt;/p&gt;
  1215. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;just_destruct&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Destruct&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1216. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//           -----------
  1217. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// This function only requests &quot;Destruct&quot; capability.
  1218. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1219. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;nb&quot;&gt;drop&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;   &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// OK
  1220. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;forget&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ERROR: `T: Forget` required
  1221. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;           &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// OK
  1222. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1223. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h4&gt;The borrow checker would require “dropped” values implement &lt;code&gt;Destruct&lt;/code&gt;&lt;/h4&gt;
  1224. &lt;p&gt;We would modify the &lt;code&gt;drop&lt;/code&gt; function to require only &lt;code&gt;T: Destruct&lt;/code&gt;:&lt;/p&gt;
  1225. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;drop&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Destruct&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;t&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1226. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;We would also extend the borrow checker so that when it sees a value being dropped (i.e., because it went out of scope), it would require the &lt;code&gt;Destruct&lt;/code&gt; bound.&lt;/p&gt;
  1227. &lt;p&gt;That means that if you have a value whose type is only &lt;code&gt;Move&lt;/code&gt;, you cannot “drop” it:&lt;/p&gt;
  1228. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;just_move&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Move&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1229. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//           -----------
  1230. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// This function only requests &quot;Move&quot; capability.
  1231. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1232. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;nb&quot;&gt;drop&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;   &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ERROR: `T: Destruct` required
  1233. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;mem&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;forget&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;b&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ERROR: `T: Forget` required
  1234. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;x&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;c&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;           &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// OK
  1235. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;                        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ERROR: `x` is being dropped, but `T: Destruct`
  1236. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This means that if you have only a &lt;code&gt;Move&lt;/code&gt; bound, you &lt;em&gt;must&lt;/em&gt; move anything you own if you want to return from the function. For example:&lt;/p&gt;
  1237. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;return_ok&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Move&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-&amp;gt; &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1238. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// OK
  1239. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1240. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If you have a function that does not move, you’ll get an error:&lt;/p&gt;
  1241. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;return_err&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Move&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-&amp;gt; &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1242. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ERROR: `a` does not implement `Destruct`
  1243. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;It’s worth pointing out that this will be annoying as all get out in the face of panics:&lt;/p&gt;
  1244. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;return_err&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Move&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-&amp;gt; &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1245. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ERROR: If a panic occurs, `a` would be dropped, but `T` not implement `Destruct`
  1246. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;forbid_env_var&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;();&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1247. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  1248. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1249. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1250. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  1251. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;forbid_env_var&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1252. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;if&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;std&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;env&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;var&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;&quot;BAD&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;).&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;is_ok&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1253. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;fm&quot;&gt;panic!&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;&quot;Uh oh: BAD cannot be set&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1254. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1255. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1256. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;I’m ok with this, but it is going to put pressure on better ways to rule out panics statically.&lt;/p&gt;
  1257. &lt;h4&gt;Const (and later async) variants of &lt;code&gt;Destruct&lt;/code&gt;&lt;/h4&gt;
  1258. &lt;p&gt;In fact, we are already doing something much like this destruct check for const functions. Right now if you have a const fn and you try to drop a value, you get an error:&lt;/p&gt;
  1259. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;const&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;test&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;t&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1260. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ERROR!
  1261. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Compiling that gives you the error:&lt;/p&gt;
  1262. &lt;pre tabindex=&quot;0&quot;&gt;&lt;code&gt;error[E0493]: destructor of `T` cannot be evaluated at compile-time
  1263. --&amp;gt; src/lib.rs:1:18
  1264.  |
  1265. 1 | const fn test&amp;lt;T&amp;gt;(t: T) { }
  1266.  |                  ^       - value is dropped here
  1267.  |                  |
  1268.  |                  the destructor for this type cannot be evaluated in constant functions
  1269. &lt;/code&gt;&lt;/pre&gt;&lt;p&gt;This check is not presently taking place in borrow check but it could be.&lt;/p&gt;
  1270. &lt;h4&gt;The borrow checker would require “moved” values implement &lt;code&gt;Move&lt;/code&gt;&lt;/h4&gt;
  1271. &lt;p&gt;The final part of the check would be requiring that “moved” values implement &lt;code&gt;Move&lt;/code&gt;:&lt;/p&gt;
  1272. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;return_err&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Pointee&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-&amp;gt; &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1273. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// ERROR: `a` does not implement `Move`
  1274. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1275. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;You might think that having types that are &lt;code&gt;!Move&lt;/code&gt; would replace the need for pin, but this is not the case. A &lt;em&gt;pinned&lt;/em&gt; value is one that can &lt;em&gt;never move again&lt;/em&gt;, whereas a value that is not &lt;code&gt;Move&lt;/code&gt; can never be moved in the first place – at least once it is stored into a place.&lt;/p&gt;
  1276. &lt;p&gt;I’m not sure if this part of the proposal makes sense, we could start by just having all types be &lt;code&gt;Move&lt;/code&gt;, &lt;code&gt;Destruct&lt;/code&gt;, or (the default) &lt;code&gt;Forget&lt;/code&gt;.&lt;/p&gt;
  1277. &lt;h4&gt;Opting out from forget etc&lt;/h4&gt;
  1278. &lt;p&gt;The other part of the proposal is that you should be able to explicit “opt out” from being forgettable, e.g. by doing&lt;/p&gt;
  1279. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;struct&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;MyType&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1280. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Destruct&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;MyType&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1281. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Doing this will limit the generics that can accept your type, of course.&lt;/p&gt;
  1282. &lt;h4&gt;Associated type bounds&lt;/h4&gt;
  1283. &lt;p&gt;The tough part with these “default bound” proposals is always associated type bounds. For backwards compatibility, we’d have to default to &lt;code&gt;Forget&lt;/code&gt; but a lot of associated types that exist in the wild today shouldn’t really &lt;em&gt;require&lt;/em&gt; &lt;code&gt;Forget&lt;/code&gt;. For example a trait like &lt;code&gt;Add&lt;/code&gt; should &lt;em&gt;really&lt;/em&gt; just require &lt;code&gt;Move&lt;/code&gt; for its return type:&lt;/p&gt;
  1284. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;trait&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Add&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Rhs&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;Self&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1285. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;type&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;Output&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;cm&quot;&gt;/* : Move */&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1286. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1287. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;I am basically not too worried about this. It’s possible that we can weaken these bounds over time or through editions. Or, perhaps, add in some kind of edition-specific “alias” like&lt;/p&gt;
  1288. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;trait&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Add2025&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Rhs&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;Self&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1289. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;type&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;Output&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Move&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1290. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1291. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;where &lt;code&gt;Add2025&lt;/code&gt; is implemented for everything that implements &lt;code&gt;Add&lt;/code&gt;.&lt;/p&gt;
  1292. &lt;p&gt;I am not sure exactly how to manage it, but we’ll figure it out – and in the meantime, most of the types that should not be forgettable are really just “guard” types that don’t have to flow through quite so many places.&lt;/p&gt;
  1293. &lt;h5&gt;Associated type bounds in closures&lt;/h5&gt;
  1294. &lt;p&gt;The one place that I think it is &lt;em&gt;really imporatnt&lt;/em&gt; that we weaken the associated type bounds is with closures– and, fortunately, that’s a place we can get away with due to the way our “closure trait bound” syntax works. I feel like I wrote a post on this before, but I can’t find it now, but the short version is that, today, when you write &lt;code&gt;F: Fn()&lt;/code&gt;, that means that the closure must return &lt;code&gt;()&lt;/code&gt;. If you write &lt;code&gt;F: Fn() -&amp;gt; T&lt;/code&gt;, then this type &lt;code&gt;T&lt;/code&gt; must have been declared somewhere else, and so &lt;code&gt;T&lt;/code&gt; will (independently from the associated type of the &lt;code&gt;Fn&lt;/code&gt; trait) get a default &lt;code&gt;Forget&lt;/code&gt; bound. So since the &lt;code&gt;Fn&lt;/code&gt; associated type is not independently nameable in stable Rust, we can change its bounds, and code like this would continue to work unchanged:&lt;/p&gt;
  1295. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;foo&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;F&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1296. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;where&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1297. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;F&lt;/span&gt;: &lt;span class=&quot;nb&quot;&gt;Fn&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-&amp;gt; &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1298. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//         - `T: Forget` still holds by default
  1299. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1300. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3&gt;Frequently asked questions&lt;/h3&gt;
  1301. &lt;h4&gt;How does this relate to the recent thread on internals?&lt;/h4&gt;
  1302. &lt;p&gt;Recently I was pointed at &lt;a href=&quot;https://internals.rust-lang.org/t/pre-rfc-substructural-type-system/23614&quot;&gt;this internals thread&lt;/a&gt; for a “substructural type system” which likely has very similar capabilities. To be totally honest, though, I haven’t had time to read and digest it yet! I had this blog post like 95% done though so I figured I’d post it first and then go try and compare.&lt;/p&gt;
  1303. &lt;h4&gt;What would it mean for a struct to opt out of &lt;code&gt;Move&lt;/code&gt; (e.g., by being only &lt;code&gt;Pointee&lt;/code&gt;)?&lt;/h4&gt;
  1304. &lt;p&gt;So, the system as I described &lt;em&gt;would&lt;/em&gt; allow for ‘unmoveable’ types (i.e., a struct that opts out from everything and only permits &lt;code&gt;Pointee&lt;/code&gt;), but such a struct would only really be something you could store in a static memory location. You couldn’t put it on the stack because the stack must eventually get popped. And you couldn’t move it from place to place because, well, it’s immobile.&lt;/p&gt;
  1305. &lt;p&gt;This seems like something that could be useful – e.g., to model “video RAM” or something that lives in a specific location in memory and cannot live anywhere else – but it’s not a widespread need.&lt;/p&gt;
  1306. &lt;h4&gt;How would you handle destructors with arguments?&lt;/h4&gt;
  1307. &lt;p&gt;I imagine something like this:&lt;/p&gt;
  1308. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;struct&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;Transaction&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1309. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;: &lt;span class=&quot;nb&quot;&gt;Vec&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;kt&quot;&gt;u8&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1310. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1311. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  1312. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sd&quot;&gt;/// Opt out from destruct
  1313. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;sd&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Move&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Transaction&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1314. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  1315. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Transaction&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1316. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// This is effectively a &quot;destructor&quot;
  1317. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;pub&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;complete&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1318. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1319. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;connection&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Connection&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1320. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1321. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Transaction&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1322. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1323. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  1324. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;With this setup, any function that owns a &lt;code&gt;Transaction&lt;/code&gt; must eventually invoke &lt;code&gt;transaction.complete()&lt;/code&gt;. This is because no values of this type can be dropped, so they must be moved.&lt;/p&gt;
  1325. &lt;h4&gt;How does this relate to async drop?&lt;/h4&gt;
  1326. &lt;p&gt;This setup provides attacks a key problem that has blocked async drop in my mind, which is that types that are “async drop” do not have to implement “sync drop”. This gives the type system the ability to prevent them from being dropped in sync code, then, and it would mean that they can only be dropped in async drop. But there’s still lots of design work to be done there.&lt;/p&gt;
  1327. &lt;h4&gt;Why is the trait &lt;code&gt;Destruct&lt;/code&gt; and not &lt;code&gt;Drop&lt;/code&gt;?&lt;/h4&gt;
  1328. &lt;p&gt;This comes from the const generifs work. I don’t love it. But there is a logic to it. Right now, when you drop a struct or other value, that actually does a whole sequence of things, only one of which is running any &lt;code&gt;Drop&lt;/code&gt; impl – it also (for example) drops all the fields in the struct recursively, etc. The idea is that “destruct” refers to this whole sequence.&lt;/p&gt;
  1329. &lt;h4&gt;How hard would this to be to prototype?&lt;/h4&gt;
  1330. &lt;p&gt;I…don’t actually think it would be very hard. I’ve thought somewhat about it and all of the changes seem pretty straightforward. I would be keen to support a &lt;a href=&quot;https://lang-team.rust-lang.org/how_to/experiment.html&quot;&gt;lang-team experiment&lt;/a&gt; on this.&lt;/p&gt;
  1331. &lt;h4&gt;Does this mean we should have had leak?&lt;/h4&gt;
  1332. &lt;p&gt;The whole topic of destructors and leaks and so forth datesback to approximately Rust 1.0, when we discovered that, in fact, our abstraction for threads was unsound when combined with cyclic ref-counted boxes. Before that we hadn’t fully internalized that destructors are “opt-out methods”. You can read &lt;a href=&quot;https://smallcultfollowing.com/babysteps/ /blog/2015/04/29/on-reference-counting-and-leaks/&quot;&gt;this blog post I wrote at the time&lt;/a&gt;. At the time, the primary idea was to have some kind of &lt;code&gt;?Leak&lt;/code&gt; bounds and it was tied to the idea of references (so that all &lt;code&gt;'static&lt;/code&gt; data was assumed to be “leakable”, and hence something you could put into an &lt;code&gt;Rc&lt;/code&gt;). I… mostly think we made the right call at the time. I think it’s good that most of the ecosystem is interoperable and that &lt;code&gt;Rc&lt;/code&gt; doesn’t require &lt;code&gt;static&lt;/code&gt; bounds, and certainly I think it’s good that we moved to 1.0 with minimal disruption. In any case, though, I rather prefer this design to the ones that were under discussion at the time, in part because it also addresses the need for different kinds of destructors and for destructors with many arguments and so forth, which wasn’t something we thought about then.&lt;/p&gt;
  1333. &lt;h4&gt;Isn’t it confusing to have these “magic” traits that “opt out” from default bounds?&lt;/h4&gt;
  1334. &lt;p&gt;I think that specifying the &lt;em&gt;bounds you want&lt;/em&gt; is inherently better than today’s &lt;code&gt;?&lt;/code&gt; design, both because it’s easier to understand and because it allows us to backwards compatibly add traits in between in ways that are not possible with the &lt;code&gt;?&lt;/code&gt; design.&lt;/p&gt;
  1335. &lt;p&gt;However, I do see that having &lt;code&gt;T: Move&lt;/code&gt; mean that &lt;code&gt;T: Destruct&lt;/code&gt; does not hold is subtle. I wonder if we should adopt some kind of sigil or convention on these traits, like &lt;code&gt;T: @Move&lt;/code&gt; or something. I don’t know! Something to consider.&lt;/p&gt;
  1336. &lt;div class=&quot;footnotes&quot;&gt;
  1337. &lt;hr /&gt;
  1338. &lt;ol&gt;
  1339. &lt;li id=&quot;fn:1&quot;&gt;
  1340. &lt;p&gt;That was a great conference. Also, interestingly, this is one of my favorite of all my talks, but for some reason, I rarely reuse this material. I should change that. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:1&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  1341. &lt;/li&gt;
  1342. &lt;li id=&quot;fn:2&quot;&gt;
  1343. &lt;p&gt;Academics distinguish “safety” from “liveness properties”, where safety means “bad things don’t happen” and “liveness” means “good things eventually happen”. Another way of saying this is that Rust’s type system helps with a lot of safety properties but struggles with liveness properties. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:2&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  1344. &lt;/li&gt;
  1345. &lt;li id=&quot;fn:3&quot;&gt;
  1346. &lt;p&gt;Uh, citation needed. I know this is true but I can’t find the relevant WebAssembly issue where it is discussed. Help, internet! &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:3&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  1347. &lt;/li&gt;
  1348. &lt;li id=&quot;fn:4&quot;&gt;
  1349. &lt;p&gt;Really the DMA problem is the same as scoped threads. If you think about it, the embedded device writing to memory is basically the same as a parallel thread writing to memory. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:4&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  1350. &lt;/li&gt;
  1351. &lt;/ol&gt;
  1352. &lt;/div&gt;</description>
  1353. <pubDate>Wed, 22 Oct 2025 01:45:02 +0000</pubDate>
  1354. </item>
  1355. <item>
  1356. <title>Mozilla Addons Blog: Developer Spotlight: Fox Recap</title>
  1357. <guid isPermaLink="false">https://blog.mozilla.org/addons/?p=9262</guid>
  1358. <link>https://blog.mozilla.org/addons/2025/10/21/developer-spotlight-fox-recap/</link>
  1359. <description>&lt;div class=&quot;wp-caption alignleft&quot; id=&quot;attachment_9263&quot; style=&quot;width: 590px;&quot;&gt;&lt;a href=&quot;https://addons.mozilla.org/en-US/firefox/addon/fox-recap/&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;size-medium wp-image-9263&quot; height=&quot;435&quot; src=&quot;https://blog.mozilla.org/addons/files/2025/10/blog_FoxRecap-580x435.png&quot; width=&quot;580&quot; /&gt;&lt;/a&gt;&lt;p class=&quot;wp-caption-text&quot; id=&quot;caption-attachment-9263&quot;&gt;The Fox Recap team (pictured left to right): Taimur Hasan, Mozilla community manager Matt Cool, Kate Sawtell, Diego Valdez (not pictured: Peter Mitchell).&lt;/p&gt;&lt;/div&gt;
  1360. &lt;p&gt;“What if we did a Spotify Wrapped for your browser?” wondered a group of Cal State Monterey Bay computer science students. That was the initial spark of an idea that became &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/fox-recap/&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;Fox Recap&lt;/a&gt; — a Firefox extension that leverages machine learning to give Firefox users fascinating insights into their browsing habits, like peak usage hours, types of websites commonly visited (news, entertainment, shopping, etc.), navigation patterns, and more.&lt;/p&gt;
  1361. &lt;p&gt;&lt;a href=&quot;https://www.linkedin.com/in/taimurhasan1/&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;Taimur Hasan&lt;/a&gt; was one of four CSMB students who built Fox Recap as part of a Mozilla-supported &lt;a href=&quot;https://sites.google.com/csumb.edu/cscapstone-s2025/cs-projects/firefox-ai-platform?authuser=0&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;Capstone project&lt;/a&gt;. We spoke with Taimur about his experience building an AI-centered extension from scratch.&lt;/p&gt;
  1362. &lt;p&gt;&lt;b&gt;What makes Fox Recap an “AI” project?&lt;/b&gt;&lt;/p&gt;
  1363. &lt;p&gt;Taimur Hasan: &lt;i&gt;Fox Recap uses Machine Learning behind the scenes to classify sites and generate higher level insights, like top/trending categories and transition patterns. I kept the “AI” messaging light on the listing page to avoid hype and focus on the experience. Ideally the AI features feel seamless and natural rather than front and center.&lt;/i&gt;&lt;/p&gt;
  1364. &lt;p&gt;&lt;b&gt;What was your most challenging development hurdle?  &lt;/b&gt;&lt;/p&gt;
  1365. &lt;p&gt;TH: &lt;i&gt;For me, the most challenging part of development was creating the inference pipeline, which means the part where you actually use the AI model to do something useful. It took careful optimization to run well on a typical laptop as load times were a priority.&lt;/i&gt;&lt;/p&gt;
  1366. &lt;p&gt;&lt;b&gt;What is your perception of young emergent developers like yourself and their regard for privacy on the web?&lt;/b&gt;&lt;/p&gt;
  1367. &lt;p&gt;TH: &lt;i&gt;With data collection on the rise, privacy and security matter more than ever. Among dedicated and enthusiastic young developers, privacy will always be in mind.&lt;/i&gt;&lt;/p&gt;
  1368. &lt;p&gt;&lt;b&gt;How do you see AI and browser extensions interrelating in the coming years? Do you have a sense of mutual direction? &lt;/b&gt;&lt;/p&gt;
  1369. &lt;p&gt;TH: &lt;i&gt;I expect wider use of small, task specific models that quietly improve the user experience in most browser extensions. For mutual direction in the browser and add-on space I can see the use of AI in manipulating the DOM being done pretty heavily in the future.&lt;/i&gt;&lt;/p&gt;
  1370. &lt;p&gt;&lt;b&gt;Any advice for other extension developers curious about AI integration?  &lt;/b&gt;&lt;/p&gt;
  1371. &lt;p&gt;TH: &lt;i&gt;Be clear about the use case and model choice before investing in training or fine tuning. Start simple, validate the value, then add complexity only if it clearly improves the experience.&lt;/i&gt;&lt;/p&gt;
  1372. &lt;p&gt;To learn even more about Fox Recap’s development process, please see &lt;a href=&quot;https://blog.mozilla.org/en/firefox/firefox-recap/&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;Fox Recap: A student-built tool that analyzes your browsing habits&lt;/a&gt;.&lt;/p&gt;
  1373. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/addons/2025/10/21/developer-spotlight-fox-recap/&quot;&gt;Developer Spotlight: Fox Recap&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/addons&quot;&gt;Mozilla Add-ons Community Blog&lt;/a&gt;.&lt;/p&gt;</description>
  1374. <pubDate>Tue, 21 Oct 2025 17:36:13 +0000</pubDate>
  1375. <dc:creator>Scott DeVaney</dc:creator>
  1376. </item>
  1377. <item>
  1378. <title>Mozilla Open Policy &amp; Advocacy Blog: Behind the Manifesto: Standing up for encryption to keep the internet safe</title>
  1379. <guid isPermaLink="false">https://blog.mozilla.org/netpolicy/?p=2512</guid>
  1380. <link>https://blog.mozilla.org/netpolicy/2025/10/21/behind-the-manifesto-standing-up-for-encryption-to-keep-the-internet-safe/</link>
  1381. <description>&lt;p&gt;&lt;i&gt;Welcome to the first blog of the series “Behind the Manifesto,” where we unpack core issues that are critical to Mozilla’s mission. The &lt;/i&gt;&lt;a href=&quot;https://www.mozilla.org/en-US/about/manifesto/&quot;&gt;&lt;i&gt;Mozilla Manifesto &lt;/i&gt;&lt;/a&gt;&lt;i&gt;represents Mozilla’s commitment to advancing an open, global internet. This blog series digs deeper on our vision for the web and the people who use it, and how these goals are advanced in policymaking and technology. &lt;/i&gt;&lt;/p&gt;
  1382. &lt;p&gt;At Mozilla, we’ve &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/help-us-spread-the-word-encryption-matters/#:~:text=This%20is%20why%20Mozilla%20has,alone%20will%20not%20be%20enough.&quot;&gt;long said&lt;/a&gt; the internet is one of the world’s most important public resources, something that only thrives when guided by core principles. One of those principles is that individual security and privacy online are fundamental.&lt;/p&gt;
  1383. &lt;p&gt;&lt;a href=&quot;https://support.mozilla.org/en-US/products/firefox/privacy-and-security/encryption&quot;&gt;Encryption&lt;/a&gt; is the technology that makes secure and private online interactions possible. It protects our messages, our data, and our privacy, sitting in the center of security and trust on the internet. Given its critical role in online privacy, it can be a focal point for policymakers.&lt;/p&gt;
  1384. &lt;table&gt;
  1385. &lt;tbody&gt;
  1386. &lt;tr&gt;
  1387. &lt;td&gt;&lt;b&gt;The truth is, encryption is integral to digital trust and safety. Strong encryption keeps us safe while weak encryption puts our personal, financial, and health data at risk. &lt;/b&gt;&lt;/td&gt;
  1388. &lt;/tr&gt;
  1389. &lt;/tbody&gt;
  1390. &lt;/table&gt;
  1391. &lt;p&gt;In recent years, we’ve seen &lt;a href=&quot;https://www.globalencryption.org/blog/&quot;&gt;governments around the world&lt;/a&gt; test ways to undermine encryption to access private conversations and data, often framing it as critical to combating crime. From proposals in the EU that could allow law enforcement to read messages before they are encrypted, to the UK Government’s pushback on Apple’s rollout of iCloud end-to-end encryption, or U.S. legislation that would require platforms to provide access to encrypted data, the pressure to weaken encryption is growing globally.&lt;/p&gt;
  1392. &lt;p&gt;Governments and law enforcement agencies face complex and legitimate challenges in protecting the public from serious crime and emerging online threats. Their work is critical to ensuring safety in an increasingly digital world. But weakening encryption is not the solution. Strong encryption is what keeps everyone safe — it protects citizens, officials, and infrastructure alike. It is the foundation that safeguards people from intrusive surveillance and shields their most sensitive data from those who would exploit it for harm. We must work together to find solutions that both uphold public safety and prevent the erosion of the privacy and security that strong encryption provides.&lt;/p&gt;
  1393. &lt;p&gt;With encryption increasingly under threat, this year’s Global Encryption Day (October 21) is the perfect moment to reflect on why strong encryption matters for every internet user.&lt;/p&gt;
  1394. &lt;p&gt;At Mozilla, we believe encryption isn’t a luxury or privilege. It is a necessity for protecting data against unauthorized access. Our commitment to end-to-end encryption is strong because it is essential to protecting people and ensuring the internet remains open and secure.&lt;/p&gt;
  1395. &lt;p&gt;That’s why Mozilla has taken action for years to protect and advance encryption. In 2023, we joined the &lt;a href=&quot;https://www.globalencryption.org/2023/04/mozilla-and-internet-freedom-foundation-join-global-encryption-coalition-steering-committee/&quot;&gt;Global Encryption Coalition&lt;/a&gt; &lt;a href=&quot;https://www.globalencryption.org/about/members/&quot;&gt;Steering Committee&lt;/a&gt;, working with partners around the world to promote encryption and push back on proposals for backdoor access.&lt;/p&gt;
  1396. &lt;p&gt;In the U.S., we’ve advanced encryption in our &lt;a href=&quot;https://blog.mozilla.org/netpolicy/files/2025/03/US_Vision-25-26-1.pdf&quot;&gt;2025 U.S. policy priorities&lt;/a&gt;, &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2025/02/24/mozilla-joins-amicus-brief-in-support-of-law-that-protects-your-private-messages/&quot;&gt;joined amicus briefs&lt;/a&gt;, and raised concerns with &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2020/03/05/mozilla-statement-on-earn-it-act/&quot;&gt;bills like the U.S. EARN IT Act&lt;/a&gt;. In the EU, we ran a multi-year &lt;a href=&quot;https://securityriskahead.eu/&quot;&gt;campaign&lt;/a&gt; on the &lt;a href=&quot;https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation&quot;&gt;eIDAS Regulation&lt;/a&gt; working alongside civil society, academics, and industry experts to address concerns that Article 45 threatened to undermine the encryption and authentication technologies used on the web. With such a massive risk to web security, Mozilla, with allies, took action, releasing &lt;a href=&quot;https://blog.mozilla.org/netpolicy/files/2021/11/eIDAS-Position-paper-Mozilla-.pdf&quot;&gt;detailed position papers and&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/netpolicy/files/2023/11/eIDAS-Industry-Letter.pdf&quot;&gt;joint statements&lt;/a&gt;.  All of our efforts have been to safeguard encryption, privacy, and digital rights. Why? Because the bottom line is simple: backdoor policies diminish the trust that allows the web to be a safe and reliable public resource.&lt;/p&gt;
  1397. &lt;p&gt;Mozilla’s strong commitment to protecting privacy isn’t just a policy priority; it’s the foundation of our products and initiatives. Below, we’d like to share some of the ways in which Mozilla partnered with allies to make encryption a reality and a core function of the open internet ecosystem.&lt;/p&gt;
  1398. &lt;ul&gt;
  1399. &lt;li&gt;Mozilla is among the co-founders of &lt;a href=&quot;https://letsencrypt.org/&quot;&gt;Let’s Encrypt&lt;/a&gt;, a nonprofit Certificate Authority run by the Internet Security Research Group (ISRG), alongside partners like the EFF and the University of Michigan. This project made HTTPS certificates free and automatically renewable, transforming HTTPS from a costly, complex setup into a default expectation across the web. As a result, the share of encrypted traffic skyrocketed &lt;a href=&quot;https://news.engin.umich.edu/2019/11/how-lets-encrypt-doubled-the-percentage-of-secure-websites-in-four-years/&quot;&gt;from less than 40% in 2016 to around 80% by 2019&lt;/a&gt;.&lt;/li&gt;
  1400. &lt;li&gt;Mozilla closely collaborated with Cloudflare to roll-out &lt;a href=&quot;https://blog.mozilla.org/en/firefox/encrypted-hello/&quot;&gt;Encrypted Client Hello (ECH) in Firefox&lt;/a&gt; in 2023, which encrypts the first “Hello” message of a user’s TLS connection so that even the website name is hidden from network observers.&lt;/li&gt;
  1401. &lt;li&gt;Mozilla has most recently set a new standard for certificate revocation on the web, advancing encryption and security. In April 2025, &lt;a class=&quot;c-link&quot; href=&quot;https://hacks.mozilla.org/2025/08/crlite-fast-private-and-comprehensive-certificate-revocation-checking-in-firefox/&quot; rel=&quot;noopener noreferrer&quot; target=&quot;_blank&quot;&gt;Firefox became the first (and is still the only) browser&lt;/a&gt; that has &lt;a class=&quot;c-link&quot; href=&quot;https://blog.mozilla.org/en/firefox/crlite/&quot; rel=&quot;noopener noreferrer&quot; target=&quot;_blank&quot;&gt;deployed CRLite&lt;/a&gt;, the technology invented by a group of researchers that ensures revoked HTTPS certificates are identified quickly and privately without leaking unencrypted browsing activity to third parties.&lt;/li&gt;
  1402. &lt;li&gt;In 2024, Firefox became the first browser to &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1884140&quot;&gt;support DTLS 1.3 &lt;/a&gt;providing the most robust end-to-end encryption of real-time audio and video data, including all your web conferencing.&lt;/li&gt;
  1403. &lt;/ul&gt;
  1404. &lt;p&gt;It’s easy to say we care about encryption, but it only works if the commitment is shared by the policymakers writing our laws and the engineers designing our systems.&lt;/p&gt;
  1405. &lt;blockquote&gt;&lt;p&gt;As Neha Kochar, Director of Firefox Security and Privacy puts it: “Whether you’re visiting your bank’s website or sending a family photo, Firefox works behind the scenes to keep your browsing secure. With no shareholders to answer to, we serve only you — open-source and transparent by design, with verifiable guarantees that not even Mozilla knows which websites you visit or what you do online.”&lt;/p&gt;&lt;/blockquote&gt;
  1406. &lt;p&gt;That is why Global Encryption Day is such an important moment. If a system is weakened or broken, it opens vulnerabilities that anyone with the right tools can exploit. By standing up for encryption and the policies that protect it, we help ensure the internet remains safe, open, and fair for everyone.&lt;/p&gt;
  1407. &lt;p&gt;To dig deeper on encryption, check out these partner resources: &lt;a href=&quot;https://www.globalencryption.org/blog/&quot;&gt;Global Encryption Coalition&lt;/a&gt;, &lt;a href=&quot;https://www.internetsociety.org/action-plan/encryption/&quot;&gt;Internet Society&lt;/a&gt; and &lt;a href=&quot;https://www.gp-digital.org/world-map-of-encryption/&quot;&gt;Global Partners Digital&lt;/a&gt;.&lt;/p&gt;
  1408. &lt;p&gt;&lt;i&gt;This blog is part of a larger series. Be sure to follow &lt;/i&gt;&lt;a href=&quot;https://www.linkedin.com/authwall?trk=bf&amp;amp;trkInfo=AQG0ar_qcB8EBgAAAZoGzJxA4eFE_J5_aXXVy4XpoJaAGTPKMJZb6_q_yZbXt5vGjo9d80W8v1AWGYVTeF0DYt10NEXEk3U-6LtLf3ygQUMMT818X4ZZca59KKtwzaMNYEIJEzk=&amp;amp;original_referer=&amp;amp;sessionRedirect=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fjennifer-taylor-hodges%2F&quot;&gt;&lt;i&gt;Jenn Taylor Hodges&lt;/i&gt;&lt;/a&gt;&lt;i&gt; and &lt;/i&gt;&lt;a href=&quot;https://it.linkedin.com/in/sema-karaman-0a9b988a&quot;&gt;&lt;i&gt;Sema Karaman&lt;/i&gt;&lt;/a&gt;&lt;i&gt; on LinkedIn for further insights into Mozilla’s policy priorities. &lt;/i&gt;&lt;/p&gt;
  1409. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2025/10/21/behind-the-manifesto-standing-up-for-encryption-to-keep-the-internet-safe/&quot;&gt;Behind the Manifesto: Standing up for encryption to keep the internet safe&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/netpolicy&quot;&gt;Open Policy &amp;amp; Advocacy&lt;/a&gt;.&lt;/p&gt;</description>
  1410. <pubDate>Tue, 21 Oct 2025 16:37:43 +0000</pubDate>
  1411. <dc:creator>Jenn Taylor Hodges and Sema Karaman</dc:creator>
  1412. </item>
  1413. <item>
  1414. <title>Mozilla Thunderbird: Thunderbird Monthly Release 144 Recap</title>
  1415. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3902</guid>
  1416. <link>https://blog.thunderbird.net/2025/10/thunderbird-monthly-release-144-recap/</link>
  1417. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/blog-banner-desktop-month-release-series1-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  1418. &lt;p&gt;We’re back with our Monthly Release recap! Thunderbird 144.0 readies the way for Exchange Web Services support, makes reordering your folders easier, and adds a new UI for TLS certificate handling. Additionally, we’ve fixed a dark mode toggle bug for High Contrast Mode users.&lt;/p&gt;
  1419.  
  1420.  
  1421.  
  1422. &lt;p&gt;&lt;strong&gt;A quick reminder&lt;/strong&gt; – these updates are for users on our &lt;strong&gt;monthly Thunderbird Release channel&lt;/strong&gt;. For our users still on the ESR (Extended Standard Release) channel, these updates won’t land until next July 2026. For more information on the differences between the channels and how to make the switch:&lt;/p&gt;
  1423.  
  1424.  
  1425.  
  1426. &lt;ul&gt;
  1427. &lt;li&gt;Visit the Release download portal:&lt;a href=&quot;https://updates.thunderbird.net/thunderbird/128.0/monthly/&quot;&gt; Thunderbird Release Page&lt;/a&gt;.&lt;/li&gt;
  1428.  
  1429.  
  1430.  
  1431. &lt;li&gt;&lt;a href=&quot;https://support.mozilla.org/en-US/kb/thunderbird-release&quot;&gt;Explore detailed comparisons&lt;/a&gt; and migration guides.&lt;/li&gt;
  1432. &lt;/ul&gt;
  1433.  
  1434.  
  1435.  
  1436. &lt;p&gt;Now let’s dive into &lt;strong&gt;what’s new in 144.0!&lt;/strong&gt;&lt;/p&gt;
  1437.  
  1438.  
  1439.  
  1440. &lt;h3&gt;New Features:&lt;/h3&gt;
  1441.  
  1442.  
  1443.  
  1444. &lt;h4&gt;Support for Exchange Web Service (EWS) Email in Account Hub&lt;/h4&gt;
  1445.  
  1446.  
  1447.  
  1448. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/ExchangeAccountHub.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3958&quot; height=&quot;891&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/ExchangeAccountHub.png&quot; width=&quot;1191&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  1449.  
  1450.  
  1451.  
  1452. &lt;p&gt;As part of our preparation for EWS support officially landing next month in Thunderbird 145.0, you’ll notice EWS accounts as an option in the Account Hub. We will have more detailed blog posts and support articles available next month describing what is and isn’t supported. &lt;/p&gt;
  1453.  
  1454.  
  1455.  
  1456. &lt;p&gt;Benefits:&lt;/p&gt;
  1457.  
  1458.  
  1459.  
  1460. &lt;ul&gt;
  1461. &lt;li&gt;This gives us a chance to gradually ready the app and users for our newest protocol&lt;/li&gt;
  1462. &lt;/ul&gt;
  1463.  
  1464.  
  1465.  
  1466. &lt;h4&gt;Improve UX of folder reordering&lt;/h4&gt;
  1467.  
  1468.  
  1469.  
  1470. &lt;p&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1957486&quot;&gt;Bug 1957486&lt;/a&gt;&lt;/p&gt;
  1471.  
  1472.  
  1473.  
  1474. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/FolderReordering.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3952&quot; height=&quot;278&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/FolderReordering.png&quot; width=&quot;399&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  1475.  
  1476.  
  1477.  
  1478. &lt;p&gt;We recently introduced drag and drop folder reordering, and in 144, we’re making it better. A new widget shows where your folder is going. We also fixed an issue that prevented the visual from showing. We removed the jitters when positioning between folders, and Improved consistency by using the same indicator used to reorder tabs and attachments.&lt;/p&gt;
  1479.  
  1480.  
  1481.  
  1482. &lt;p&gt;Benefits:&lt;/p&gt;
  1483.  
  1484.  
  1485.  
  1486. &lt;ul&gt;
  1487. &lt;li&gt;More control over drag-and- performance with fewer folders going to the wrong location&lt;/li&gt;
  1488.  
  1489.  
  1490.  
  1491. &lt;li&gt;More visual consistency&lt;/li&gt;
  1492. &lt;/ul&gt;
  1493.  
  1494.  
  1495.  
  1496. &lt;h4&gt;New UI for TLS Certificate Handling&lt;/h4&gt;
  1497.  
  1498.  
  1499.  
  1500. &lt;p&gt;While power users might be comfortable handling TLS certificates, average Thunderbird users might not know what to do when Thunderbird doesn’t trust a server’s certificate. This UI makes these issues, when they occur, harder to ignore and easier to diagnose and fix, even for less tech-savvy users. &lt;/p&gt;
  1501.  
  1502.  
  1503.  
  1504. &lt;p&gt;The new UI will mark the server red, with a clickable icon that takes users to an updated server settings. There, users can view certificates and add or remove certificate override exceptions.&lt;/p&gt;
  1505.  
  1506.  
  1507.  
  1508. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/image-1.jpeg&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3928&quot; height=&quot;253&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/image-1.jpeg&quot; width=&quot;504&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  1509.  
  1510.  
  1511.  
  1512. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  1513.  
  1514.  
  1515.  
  1516. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/Monthly-Release-Update-1442.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3964&quot; height=&quot;280&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Monthly-Release-Update-1442.png&quot; width=&quot;1190&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  1517.  
  1518.  
  1519.  
  1520. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  1521.  
  1522.  
  1523.  
  1524. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/Monthly-Release-Update-1441.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3970&quot; height=&quot;280&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Monthly-Release-Update-1441.png&quot; width=&quot;1190&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  1525.  
  1526.  
  1527.  
  1528. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  1529.  
  1530.  
  1531.  
  1532. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/Monthly-Release-Update-144.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3976&quot; height=&quot;280&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Monthly-Release-Update-144.png&quot; width=&quot;1190&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  1533.  
  1534.  
  1535.  
  1536. &lt;p&gt;Benefits:&lt;/p&gt;
  1537.  
  1538.  
  1539.  
  1540. &lt;ul&gt;
  1541. &lt;li&gt;Increased security for the average Thunderbird user&lt;/li&gt;
  1542.  
  1543.  
  1544.  
  1545. &lt;li&gt;Easier access, via the server settings, to certificate actions&lt;/li&gt;
  1546. &lt;/ul&gt;
  1547.  
  1548.  
  1549.  
  1550. &lt;h3&gt;Bug Fixes:&lt;/h3&gt;
  1551.  
  1552.  
  1553.  
  1554. &lt;h4&gt;Dark mode won’t go away for messages in High Contrast Mode&lt;/h4&gt;
  1555.  
  1556.  
  1557.  
  1558. &lt;p&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1976900&quot;&gt;Bug 1976900&lt;/a&gt;&lt;/p&gt;
  1559.  
  1560.  
  1561.  
  1562. &lt;p&gt;Our High Contrast Mode users noticed the new toggle for messages in dark mode wasn’t appearing. Starting in Thunderbird 144, dark message mode will not be activated when in High Contrast mode, respecting the colors and priority of that accessibility setting.&lt;/p&gt;
  1563.  
  1564.  
  1565.  
  1566. &lt;p&gt;Benefits:&lt;/p&gt;
  1567.  
  1568.  
  1569.  
  1570. &lt;ul&gt;
  1571. &lt;li&gt;Consistent use of system colors when in High Contrast Mode&lt;/li&gt;
  1572.  
  1573.  
  1574.  
  1575. &lt;li&gt;More respectful of user settings&lt;/li&gt;
  1576. &lt;/ul&gt;
  1577.  
  1578.  
  1579.  
  1580. &lt;p&gt;You can find a complete list of updates and bug fixes that went into Thunderbird 144.0 in our &lt;a href=&quot;https://www.thunderbird.net/en-US/thunderbird/144.0/releasenotes/&quot;&gt;Release Notes&lt;/a&gt;.&lt;/p&gt;
  1581.  
  1582.  
  1583.  
  1584. &lt;p&gt;Thank you for using Thunderbird and for supporting our mission to bring a truly independent, open‑source email experience. Your feedback and enthusiasm drive every improvement we make — and we can’t wait to share more with you in the next release.&lt;/p&gt;
  1585. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/10/thunderbird-monthly-release-144-recap/&quot;&gt;Thunderbird Monthly Release 144 Recap&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  1586. <pubDate>Tue, 21 Oct 2025 14:16:13 +0000</pubDate>
  1587. <dc:creator>Monica Ayhens-Madon</dc:creator>
  1588. </item>
  1589. <item>
  1590. <title>The Servo Blog: Servo 0.0.1 Release</title>
  1591. <guid isPermaLink="true">https://servo.org/blog/2025/10/20/servo-0.0.1-release/</guid>
  1592. <link>https://servo.org/blog/2025/10/20/servo-0.0.1-release/</link>
  1593. <description>&lt;p&gt;Today, the Servo team has released new versions of the &lt;code&gt;servoshell&lt;/code&gt; binaries for all our supported platforms, tagged &lt;a href=&quot;https://github.com/servo/servo/releases/tag/v0.0.1&quot;&gt;v0.0.1&lt;/a&gt;. These binaries are essentially the same nightly builds that were already available from the &lt;a href=&quot;https://servo.org/download&quot;&gt;download page&lt;/a&gt; with additional manual testing, now tagging them explicitly as releases for future reference.&lt;/p&gt;
  1594. &lt;p&gt;We plan to publish such a tagged release every month. For now, we are adopting a simple release process where we will use a recent nightly build and perform additional manual testing to identify issues and regressions before tagging and publishing the binaries.&lt;/p&gt;
  1595. &lt;p&gt;There are currently no plans to publish these releases on &lt;a href=&quot;https://crates.io/&quot;&gt;crates.io&lt;/a&gt; or platform-specific app stores. The goal is just to publish &lt;a href=&quot;https://github.com/servo/servo/releases&quot;&gt;tagged releases on GitHub&lt;/a&gt;.&lt;/p&gt;</description>
  1596. <pubDate>Mon, 20 Oct 2025 00:00:00 +0000</pubDate>
  1597. </item>
  1598. <item>
  1599. <title>Mozilla Thunderbird: Thunderbird Monthly Development Digest: September 2025</title>
  1600. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3894</guid>
  1601. <link>https://blog.thunderbird.net/2025/10/thunderbird-monthly-development-digest-september-2025/</link>
  1602. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/blog-banner-developer2-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  1603. &lt;p&gt;Hello again from the Thunderbird development team! This month’s sprints have been about focus and follow-through, as we’ve tightened up our new Account Hub experience and continued the deep work on Exchange Web Services (EWS) support. While those two areas have taken centre stage, we’ve also been busy adapting to a wave of upstream platform changes that demanded careful attention to keep everything stable and our continuous integration systems happy. Alongside this, our developers have been lending extra support to the Services team to ensure a smooth path for upcoming releases. It’s been a month of steady, detail-oriented progress – the kind that doesn’t always make headlines, but lays the groundwork for the next leaps forward.&lt;/p&gt;
  1604.  
  1605.  
  1606.  
  1607. &lt;h4&gt;&lt;strong&gt;Exchange Web Services support announcement for 145&lt;/strong&gt;&lt;/h4&gt;
  1608.  
  1609.  
  1610.  
  1611. &lt;p&gt;While support for Microsoft Exchange via EWS landed in Thunderbird 144, the new “Account Hub” setup interface had a few outstanding priorities which required our attention. Considering that the announcement of EWS support will likely generate a large spike in secondary account additions, we felt it important enough to delay the announcement in order to polish the setup interface and make the experience better for the users taking advantage of the new features. The team working on the “back end” took the opportunity to deliver more features that had been in our backlog and address some bugs that were reported by users who are already using EWS on Beta and Daily:&lt;/p&gt;
  1612.  
  1613.  
  1614.  
  1615. &lt;ul&gt;
  1616. &lt;li&gt;Offline message policy&lt;/li&gt;
  1617.  
  1618.  
  1619.  
  1620. &lt;li&gt;Soft delete / copy to Trash&lt;/li&gt;
  1621.  
  1622.  
  1623.  
  1624. &lt;li&gt;Empty Trash&lt;/li&gt;
  1625.  
  1626.  
  1627.  
  1628. &lt;li&gt;Notifications with message preview&lt;/li&gt;
  1629.  
  1630.  
  1631.  
  1632. &lt;li&gt;Reply-to multiple recipients bug&lt;/li&gt;
  1633.  
  1634.  
  1635.  
  1636. &lt;li&gt;Mark Folder as read&lt;/li&gt;
  1637.  
  1638.  
  1639.  
  1640. &lt;li&gt;Experimental tenant-specific configuration options (behind a preference) now being tested with early adopters&lt;/li&gt;
  1641. &lt;/ul&gt;
  1642.  
  1643.  
  1644.  
  1645. &lt;p&gt;Looking ahead, the team is already focused on our work week where we’ll have chance to put plans in place to tackle some architectural refactoring and the next major milestones in our EWS implementation for Calendar and Address Book.&lt;/p&gt;
  1646.  
  1647.  
  1648.  
  1649. &lt;p&gt;We were also delighted to work with a community contributor who has been hard at work on adding &lt;a href=&quot;https://github.com/thunderbird/ews-rs/pull/64&quot;&gt;&lt;u&gt;support for the FindItem operation&lt;/u&gt;&lt;/a&gt;. We know some of our workflows are tricky so we very much appreciate the support and patience required!&lt;/p&gt;
  1650.  
  1651.  
  1652.  
  1653. &lt;p&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1847846&quot;&gt;&lt;u&gt;Keep track of feature delivery here.&lt;/u&gt;&lt;/a&gt; &lt;/p&gt;
  1654.  
  1655.  
  1656.  
  1657. &lt;h4&gt;&lt;strong&gt;Account Hub&lt;/strong&gt;&lt;/h4&gt;
  1658.  
  1659.  
  1660.  
  1661. &lt;p&gt;We’ve now added the ability to manually edit any configuration from the first screen. This effectively bypasses the simpler detection methods which don’t work for every configuration. Upon detection failure, a user is now able to switch between protocols and choose EWS configuration.&lt;/p&gt;
  1662.  
  1663.  
  1664.  
  1665. &lt;p&gt;Other notable items being rolled into 145 are:&lt;/p&gt;
  1666.  
  1667.  
  1668.  
  1669. &lt;ul&gt;
  1670. &lt;li&gt;Redirect warning and handling to prevent a hang for platforms using autodiscover on a 3rd party server&lt;/li&gt;
  1671.  
  1672.  
  1673.  
  1674. &lt;li&gt;Authentication step added for Exchange discovery requiring credentials&lt;/li&gt;
  1675.  
  1676.  
  1677.  
  1678. &lt;li&gt;Ability to cancel the account configuration detection process&lt;/li&gt;
  1679.  
  1680.  
  1681.  
  1682. &lt;li&gt;Improvements to the experience for users with screen reading technology&lt;/li&gt;
  1683. &lt;/ul&gt;
  1684.  
  1685.  
  1686.  
  1687. &lt;p&gt;The creation of address books through the Account Hub is now the experience by default on 145 which is coming to Beta release users this week and monthly Release users before I write next.&lt;/p&gt;
  1688.  
  1689.  
  1690.  
  1691. &lt;p&gt;Follow progress in the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1981786&quot;&gt;&lt;u&gt;Meta Bug&lt;/u&gt;&lt;/a&gt;&lt;/p&gt;
  1692.  
  1693.  
  1694.  
  1695. &lt;h4&gt;&lt;strong&gt;Calendar UI Rebuild&lt;/strong&gt;&lt;/h4&gt;
  1696.  
  1697.  
  1698.  
  1699. &lt;p&gt;With the front end team mainly focused on Account Hub, the Calendar UI project has moved slowly this past month. We’ve concentrated the continued work in the following areas:&lt;/p&gt;
  1700.  
  1701.  
  1702.  
  1703. &lt;ul&gt;
  1704. &lt;li&gt;Acceptance widget&lt;/li&gt;
  1705.  
  1706.  
  1707.  
  1708. &lt;li&gt;Title and close button&lt;/li&gt;
  1709.  
  1710.  
  1711.  
  1712. &lt;li&gt;Dialog repositioning on resize&lt;/li&gt;
  1713.  
  1714.  
  1715.  
  1716. &lt;li&gt;Migrating calendar strings from legacy .dtd files into modern .ftl files and preserving translations to avoid repeat work for our translation community.&lt;/li&gt;
  1717. &lt;/ul&gt;
  1718.  
  1719.  
  1720.  
  1721. &lt;h4&gt;&lt;strong&gt;Maintenance, Upstream adaptations, Recent Features and Fixes&lt;/strong&gt;&lt;/h4&gt;
  1722.  
  1723.  
  1724.  
  1725. &lt;p&gt;With our focused maintenance sprint over, the team kept the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1492751&quot;&gt;&lt;u&gt;Fluent Migration&lt;/u&gt;&lt;/a&gt; and &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979960&quot;&gt;&lt;u&gt;moz-src migration&lt;/u&gt;&lt;/a&gt; projects moving in the background. They also handled another surge of upstream changes requiring triage. In addition to these items, the development community has helped us deliver a variety of improvements over the past month:&lt;/p&gt;
  1726.  
  1727.  
  1728.  
  1729. &lt;ul&gt;
  1730. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1831713&quot;&gt;&lt;u&gt;Unified toolbar fix to toggle Spam/Not Spam&lt;/u&gt;&lt;/a&gt;&lt;/li&gt;
  1731.  
  1732.  
  1733.  
  1734. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=382977&quot;&gt;&lt;u&gt;An 18 year-old bug to enable full path display&lt;/u&gt;&lt;/a&gt;&lt;/li&gt;
  1735.  
  1736.  
  1737.  
  1738. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1851875&quot;&gt;&lt;u&gt;Fix a regression to allow remote content in .eml file&lt;/u&gt;&lt;/a&gt;&lt;/li&gt;
  1739.  
  1740.  
  1741.  
  1742. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1988718&quot;&gt;&lt;u&gt;Support for DNS over HTTPS&lt;/u&gt;&lt;/a&gt;&lt;/li&gt;
  1743.  
  1744.  
  1745.  
  1746. &lt;li&gt;and many more which we list in &lt;a href=&quot;https://www.thunderbird.net/en-US/thunderbird/145.0beta/releasenotes/&quot;&gt;&lt;u&gt;release notes for beta&lt;/u&gt;&lt;/a&gt;.&lt;/li&gt;
  1747. &lt;/ul&gt;
  1748.  
  1749.  
  1750.  
  1751. &lt;p&gt;If you would like to see new features as they land, and help us find some early bugs, you can try running &lt;a href=&quot;https://archive.mozilla.org/pub/thunderbird/nightly/latest-comm-central/&quot;&gt;&lt;u&gt;daily&lt;/u&gt;&lt;/a&gt; and check the pushlog to see what has recently landed. This assistance is immensely helpful for catching problems early.&lt;/p&gt;
  1752.  
  1753.  
  1754.  
  1755. &lt;h3&gt;—&lt;/h3&gt;
  1756.  
  1757.  
  1758.  
  1759. &lt;p&gt;&lt;strong&gt;Toby Pilling&lt;/strong&gt;&lt;/p&gt;
  1760.  
  1761.  
  1762.  
  1763. &lt;p&gt;Senior Manager, Desktop Engineering&lt;/p&gt;
  1764. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/10/thunderbird-monthly-development-digest-september-2025/&quot;&gt;Thunderbird Monthly Development Digest: September 2025&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  1765. <pubDate>Fri, 17 Oct 2025 16:35:31 +0000</pubDate>
  1766. <dc:creator>Toby Pilling</dc:creator>
  1767. </item>
  1768. <item>
  1769. <title>Firefox Add-on Reviews: Reddit revolutionized — use a browser extension to enhance your favorite forum</title>
  1770. <guid isPermaLink="true">https://addons.mozilla.org/blog/reddit-revolutionized-use-a-browser-extension-to-enhance-your-favorite-forum/</guid>
  1771. <link>https://addons.mozilla.org/blog/reddit-revolutionized-use-a-browser-extension-to-enhance-your-favorite-forum/</link>
  1772. <description>&lt;p&gt;Reddit is awash with great conversation (well, &lt;a href=&quot;https://www.reddit.com/r/notinteresting/&quot; rel=&quot;noreferrer noopener&quot;&gt;not all the time)&lt;/a&gt;. There’s a Reddit forum for just about everybody —&lt;a href=&quot;https://www.reddit.com/subreddits/leaderboard/sports/&quot; rel=&quot;noreferrer noopener&quot;&gt; sports fans&lt;/a&gt;, &lt;a href=&quot;https://www.reddit.com/subreddits/leaderboard/gaming/&quot; rel=&quot;noreferrer noopener&quot;&gt;gamers&lt;/a&gt;, &lt;a href=&quot;https://www.reddit.com/r/FoodHaikus/&quot; rel=&quot;noreferrer noopener&quot;&gt;poets inspired by food&lt;/a&gt;, &lt;a href=&quot;https://www.reddit.com/r/birdswitharms/&quot; rel=&quot;noreferrer noopener&quot;&gt;people who like arms on birds&lt;/a&gt; — you get the idea. &lt;/p&gt;
  1773.  
  1774.  
  1775.  
  1776. &lt;p&gt;If you spend time on Reddit, there are ways to augment your experience with a browser extension… &lt;/p&gt;
  1777.  
  1778.  
  1779.  
  1780. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Reddit Enhancement Suite&lt;/h3&gt;
  1781.  
  1782.  
  1783.  
  1784. &lt;p&gt;Used by millions of Redditors across various browsers, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/reddit-enhancement-suite/&quot; rel=&quot;noreferrer noopener&quot;&gt;Reddit Enhancement Suite&lt;/a&gt; is optimized to work with the beloved “old Reddit”. &lt;/p&gt;
  1785.  
  1786.  
  1787.  
  1788. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1789.  
  1790.  
  1791.  
  1792. &lt;p&gt;Key features: &lt;/p&gt;
  1793.  
  1794.  
  1795.  
  1796. &lt;ul class=&quot;wp-block-list&quot;&gt;
  1797. &lt;li&gt;&lt;strong&gt;Subreddit manager&lt;/strong&gt;. Customize the top nav bar with your own subreddit shortcuts. &lt;/li&gt;
  1798.  
  1799.  
  1800.  
  1801. &lt;li&gt;&lt;strong&gt;Account switcher&lt;/strong&gt;. Easily manage multiple Reddit accounts with a couple quick clicks. &lt;/li&gt;
  1802.  
  1803.  
  1804.  
  1805. &lt;li&gt;&lt;strong&gt;Show “parent” comment on hover&lt;/strong&gt;. When you mouse over a comment, its “parent” comment displays. &lt;/li&gt;
  1806.  
  1807.  
  1808.  
  1809. &lt;li&gt;&lt;strong&gt;Dashboard&lt;/strong&gt;. Fully customizable dashboard showcases content from subreddits, your message inbox &amp;amp; more. &lt;/li&gt;
  1810.  
  1811.  
  1812.  
  1813. &lt;li&gt;&lt;strong&gt;Tag&lt;/strong&gt; specific users and subreddits so their activity appears more prominently&lt;/li&gt;
  1814.  
  1815.  
  1816.  
  1817. &lt;li&gt;&lt;strong&gt;Custom filters&lt;/strong&gt;. Select words, subreddits, or even certain users you want filtered out of your scrolling experience. &lt;/li&gt;
  1818.  
  1819.  
  1820.  
  1821. &lt;li&gt;&lt;strong&gt;New comment count&lt;/strong&gt;. See the number of new comments on a thread since your last visit. &lt;/li&gt;
  1822.  
  1823.  
  1824.  
  1825. &lt;li&gt;&lt;strong&gt;Neverending Reddit&lt;/strong&gt;. Just keep scrolling. Never stop!&lt;/li&gt;
  1826. &lt;/ul&gt;
  1827.  
  1828.  
  1829.  
  1830. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Old Reddit Redirect&lt;/h3&gt;
  1831.  
  1832.  
  1833.  
  1834. &lt;p&gt;Speaking of the former design, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/old-reddit-redirect/&quot; rel=&quot;noreferrer noopener&quot;&gt;Old Reddit Redirect&lt;/a&gt; provides a straightforward function. It simply ensures that every Reddit page you visit will redirect to the &lt;em&gt;old.reddit.com&lt;/em&gt; domain. &lt;/p&gt;
  1835.  
  1836.  
  1837.  
  1838. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1839.  
  1840.  
  1841.  
  1842. &lt;p&gt;Sure, if you have a Reddit account the site gives you the option of using the old design, but with the browser extension you’ll get the old site regardless of being logged in or not. It’s also great for when you click Reddit links shared from the new domain. &lt;/p&gt;
  1843.  
  1844.  
  1845.  
  1846. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Sink It for Reddit&lt;/h3&gt;
  1847.  
  1848.  
  1849.  
  1850. &lt;p&gt;Designed to “make Reddit’s web version actually usable,” &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/sink-it-for-reddit/&quot;&gt;Sink It for Reddit&lt;/a&gt; is built for people craving a minimalist discussion platform. &lt;/p&gt;
  1851.  
  1852.  
  1853.  
  1854. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1855.  
  1856.  
  1857.  
  1858. &lt;p&gt;Color coded comments are much simpler to navigate, especially with Sink It’s brilliant Adaptive Dark Mode feature. Give this privacy respecting extension a try if you desire a laser focused Reddit experience. &lt;/p&gt;
  1859.  
  1860.  
  1861.  
  1862. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Reddit Comment Collapser&lt;/strong&gt;&lt;/h3&gt;
  1863.  
  1864.  
  1865.  
  1866. &lt;p&gt;No more getting lost in confusing comment threads for users of &lt;strong&gt;old.reddt.com&lt;/strong&gt;. &lt;a href=&quot;https://addons.mozilla.org/en-US/firefox/addon/reddit_comment_collapser/&quot; rel=&quot;noreferrer noopener&quot;&gt;Reddit Comment Collapser&lt;/a&gt; cleans up your commentary view with a simple mouse click.&lt;/p&gt;
  1867.  
  1868.  
  1869.  
  1870. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1871.  
  1872.  
  1873.  
  1874. &lt;p&gt;Compatible with &lt;a href=&quot;https://addons.mozilla.org/en-US/firefox/addon/reddit-enhancement-suite/&quot; rel=&quot;noreferrer noopener&quot;&gt;Reddit Enhancement Suite&lt;/a&gt; and &lt;a href=&quot;https://addons.mozilla.org/en-US/firefox/addon/old-reddit-redirect/&quot; rel=&quot;noreferrer noopener&quot;&gt;Old Reddit Redirect&lt;/a&gt;, this single-use extension is beloved by many seeking a minimalist view of the classic Reddit.&lt;/p&gt;
  1875.  
  1876.  
  1877.  
  1878. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Reddit on YouTube&lt;/h3&gt;
  1879.  
  1880.  
  1881.  
  1882. &lt;p&gt;Bring Reddit with you to YouTube. Whenever you’re on a YouTube page, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/reddit-on-youtube/&quot; rel=&quot;noreferrer noopener&quot;&gt;Reddit on YouTube&lt;/a&gt; searches for Reddit posts that link to the video and embeds those comments into the YouTube comment area. &lt;/p&gt;
  1883.  
  1884.  
  1885.  
  1886. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1887.  
  1888.  
  1889.  
  1890. &lt;p&gt;You can easily toggle between Reddit and YouTube comments and select either one to be your default preference. &lt;/p&gt;
  1891.  
  1892.  
  1893.  
  1894. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-178&quot; height=&quot;716&quot; src=&quot;https://mozamo.wpengine.com/wp-content/uploads/2021/07/blog_reddit_comment-1-1024x716.png&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;If there are multiple Reddit threads about the video you’re watching, the extension will display them in tab form in the YouTube comment section.  &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  1895.  
  1896.  
  1897.  
  1898. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Reddit Ad Remover&lt;/h3&gt;
  1899.  
  1900.  
  1901.  
  1902. &lt;p&gt;Sick of seeing so many “Promoted” posts and paid advertisements in the feed and sidebar? &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/reddit-ad-remover/&quot; rel=&quot;noreferrer noopener&quot;&gt;Reddit Ad Remover&lt;/a&gt; silences the noise. &lt;/p&gt;
  1903.  
  1904.  
  1905.  
  1906. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1907.  
  1908.  
  1909.  
  1910. &lt;p&gt;The extension even blocks auto-play video ads, which is great for people who don’t appreciate sudden bursts of commercial sound. Hey, somebody should &lt;a href=&quot;https://www.reddit.com/r/badads/&quot; rel=&quot;noreferrer noopener&quot;&gt;create a subreddit about this&lt;/a&gt;! &lt;/p&gt;
  1911.  
  1912.  
  1913.  
  1914. &lt;p&gt;Happy redditing, folks. Feel free to explore more &lt;a href=&quot;https://addons.mozilla.org/firefox/extensions/category/feeds-news-blogging/&quot; rel=&quot;noreferrer noopener&quot;&gt;news and media extensions&lt;/a&gt; on &lt;em&gt;addons.mozilla.org&lt;/em&gt;.&lt;/p&gt;</description>
  1915. <pubDate>Thu, 16 Oct 2025 21:29:46 +0000</pubDate>
  1916. <dc:creator>Scott DeVaney</dc:creator>
  1917. </item>
  1918. <item>
  1919. <title>Firefox Add-on Reviews: Boost your writing skills with a browser extension</title>
  1920. <guid isPermaLink="true">https://addons.mozilla.org/blog/boost-your-writing-skills-with-a-browser-extension/</guid>
  1921. <link>https://addons.mozilla.org/blog/boost-your-writing-skills-with-a-browser-extension/</link>
  1922. <description>&lt;p&gt;Whatever kind of writing you do — technical documentation, corporate communications, Harry Potter-vampire crossover fan fiction — it probably happens online. Here are some fabulous browser extensions that will benefit anyone who writes on the web. Get grammar help, productivity tools, and other strong writing aids… &lt;/p&gt;
  1923.  
  1924.  
  1925.  
  1926. &lt;h3 class=&quot;wp-block-heading&quot;&gt;LanguageTool&lt;/h3&gt;
  1927.  
  1928.  
  1929.  
  1930. &lt;p&gt;It’s like having your own copy editor with you wherever you write on the web. &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/languagetool/&quot; rel=&quot;noreferrer noopener&quot;&gt;Language Tool – Grammar and Spell Checker&lt;/a&gt; will make you a better writer in 25+ languages. &lt;/p&gt;
  1931.  
  1932.  
  1933.  
  1934. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1935.  
  1936.  
  1937.  
  1938. &lt;p&gt;More than just a spell checker, LanguageTool also…&lt;/p&gt;
  1939.  
  1940.  
  1941.  
  1942. &lt;ul class=&quot;wp-block-list&quot;&gt;
  1943. &lt;li&gt;Recognizes common misuses of similar sounding words (e.g. &lt;em&gt;there/their&lt;/em&gt; or &lt;em&gt;your/you’re&lt;/em&gt;)&lt;/li&gt;
  1944.  
  1945.  
  1946.  
  1947. &lt;li&gt;Works on social media sites and email&lt;/li&gt;
  1948.  
  1949.  
  1950.  
  1951. &lt;li&gt;Offers alternate phrasing and style suggestions for brevity and clarity&lt;/li&gt;
  1952. &lt;/ul&gt;
  1953.  
  1954.  
  1955.  
  1956. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Dictionary Anywhere&lt;/h3&gt;
  1957.  
  1958.  
  1959.  
  1960. &lt;p&gt;Need a quick word definition? With &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/dictionary-anyvhere/&quot; rel=&quot;noreferrer noopener&quot;&gt;Dictionary Anywhere&lt;/a&gt; just double-click any word you find on the web and get an instant pop-up definition. &lt;/p&gt;
  1961.  
  1962.  
  1963.  
  1964. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1965.  
  1966.  
  1967.  
  1968. &lt;p&gt;You can even save and download words and their definitions for later offline reference. &lt;/p&gt;
  1969.  
  1970.  
  1971.  
  1972. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-232&quot; height=&quot;724&quot; src=&quot;https://mozamo.wpengine.com/wp-content/uploads/2021/08/blog_write_DictAnywhere-1024x724.jpg&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;Dictionary Anywhere — no more navigating away from a page just to get a word check.&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  1973.  
  1974.  
  1975.  
  1976. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Yomitan&lt;/h3&gt;
  1977.  
  1978.  
  1979.  
  1980. &lt;p&gt;Think of &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/yomitan/&quot;&gt;Yomitan&lt;/a&gt; as a dictionary extension that doubles as a language learning tool. Decipher and define text in 20+ languages. &lt;/p&gt;
  1981.  
  1982.  
  1983.  
  1984. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  1985.  
  1986.  
  1987.  
  1988. &lt;p&gt;As you navigate foreign language websites, Yomitan is right there with you to not only help define unfamiliar words and phrases, but also provide audio pronunciation guidance, flashcard creation for future study, offline support and more — all within a privacy protective framework. &lt;/p&gt;
  1989.  
  1990.  
  1991.  
  1992. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Power Thesaurus&lt;/h3&gt;
  1993.  
  1994.  
  1995.  
  1996. &lt;p&gt;Every writer occasionally struggle to find the perfect word. Bring &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/power-thesaurus/&quot;&gt;Power Thesaurus&lt;/a&gt; with you wherever you write on the web to gain instant access to alternative phrasing. &lt;/p&gt;
  1997.  
  1998.  
  1999.  
  2000. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2001.  
  2002.  
  2003.  
  2004. &lt;p&gt;Simply highlight any word and pop up a handy thesaurus (also includes word definitions and antonyms). Power Thesaurus is a priceless tool for writers who labor over every word. &lt;/p&gt;
  2005.  
  2006.  
  2007.  
  2008. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Dark Background and Light Text&lt;/h3&gt;
  2009.  
  2010.  
  2011.  
  2012. &lt;p&gt;Give your eyes a break. &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/dark-background-light-text/&quot; rel=&quot;noreferrer noopener&quot;&gt;Dark Background and Light Text&lt;/a&gt; makes staring at blinking words all day a whole lot easier on your lookers. &lt;/p&gt;
  2013.  
  2014.  
  2015.  
  2016. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2017.  
  2018.  
  2019.  
  2020. &lt;p&gt;Really simple to use out of the box. Once installed, the extension’s default settings automatically flip the colors of every web page you visit. But if you’d like more granular control of color settings, just click the extension’s toolbar button to access a pop-up menu that lets you customize color schemes, set page exceptions for sites you don’t want colors inverted, and more simple controls. &lt;/p&gt;
  2021.  
  2022.  
  2023.  
  2024. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-233&quot; height=&quot;551&quot; src=&quot;https://mozamo.wpengine.com/wp-content/uploads/2021/08/blog_write_dblt-1024x551.jpg&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;Dark Background and Light Text goes easy on the eyes.&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  2025.  
  2026.  
  2027.  
  2028. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Clippings&lt;/h3&gt;
  2029.  
  2030.  
  2031.  
  2032. &lt;p&gt;If your online writing requires the repeated use of certain phrases (for example, work email templates or customer support responses), &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/clippings/&quot; rel=&quot;noreferrer noopener&quot;&gt;Clippings&lt;/a&gt; can be a huge time saver. &lt;/p&gt;
  2033.  
  2034.  
  2035.  
  2036. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2037.  
  2038.  
  2039.  
  2040. &lt;p&gt;Key features…&lt;/p&gt;
  2041.  
  2042.  
  2043.  
  2044. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2045. &lt;li&gt;Create a practically limitless library of saved phrases&lt;/li&gt;
  2046.  
  2047.  
  2048.  
  2049. &lt;li&gt;Paste your clippings anywhere via context menu&lt;/li&gt;
  2050.  
  2051.  
  2052.  
  2053. &lt;li&gt;Organize batches of clippings with folders and color coded labels&lt;/li&gt;
  2054.  
  2055.  
  2056.  
  2057. &lt;li&gt;Shortcut keys for power users&lt;/li&gt;
  2058.  
  2059.  
  2060.  
  2061. &lt;li&gt;Extension supported in English, Dutch, French, German, and Portuguese (Brazil)&lt;/li&gt;
  2062. &lt;/ul&gt;
  2063.  
  2064.  
  2065.  
  2066. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-234&quot; height=&quot;789&quot; src=&quot;https://mozamo.wpengine.com/wp-content/uploads/2021/08/blog_write_clippings-1024x789.jpg&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;Clippings handles bulk cutting/pasting. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  2067.  
  2068.  
  2069.  
  2070. &lt;p&gt;We hope these extensions take your prose to the next level. Some writers may also be interested in this collection of &lt;a href=&quot;https://addons.mozilla.org/blog/supercharge-your-productivity-with-a-browser-extension/&quot; rel=&quot;noreferrer noopener&quot;&gt;great productivity extensions&lt;/a&gt; to help organize your writing projects. Feel free to explore thousands of other useful extensions on &lt;em&gt;addons.mozilla.org&lt;/em&gt;. &lt;/p&gt;</description>
  2071. <pubDate>Thu, 16 Oct 2025 19:54:02 +0000</pubDate>
  2072. <dc:creator>Scott DeVaney</dc:creator>
  2073. </item>
  2074. <item>
  2075. <title>Firefox Add-on Reviews: Extension starter pack</title>
  2076. <guid isPermaLink="true">https://addons.mozilla.org/blog/extension-starter-pack/</guid>
  2077. <link>https://addons.mozilla.org/blog/extension-starter-pack/</link>
  2078. <description>&lt;p&gt;You’ve probably heard about “ad blockers,” “tab managers,” “anti-trackers” or any number of browser customization tools commonly known as &lt;em&gt;extensions.&lt;/em&gt; And maybe you’re intrigued to try one, but you’ve never installed an extension before and the whole notion just seems a bit vague. &lt;/p&gt;
  2079.  
  2080.  
  2081.  
  2082. &lt;p&gt;Let’s demystify extensions. &lt;/p&gt;
  2083.  
  2084.  
  2085.  
  2086. &lt;p&gt;An extension is simply an app that runs on a browser like Firefox. From serious productivity and privacy enhancing features to fun stuff like changing the way the web looks and feels, extensions give you the power to completely personalize your browsing experience. &lt;/p&gt;
  2087.  
  2088.  
  2089.  
  2090. &lt;p&gt;&lt;a href=&quot;https://addons.mozilla.org/firefox/&quot; rel=&quot;noreferrer noopener&quot;&gt;&lt;em&gt;Addons.mozilla.org&lt;/em&gt;&lt;/a&gt; (AMO) is a discovery site that hosts thousands of independently developed Firefox extensions. It’s a vast and eclectic ecosystem of features, so we’ve hand-picked a small collection of great extensions to get you started…&lt;/p&gt;
  2091.  
  2092.  
  2093.  
  2094. &lt;h3&gt;&lt;em&gt;I’ve always wanted an ad blocker!&lt;/em&gt;&lt;/h3&gt;
  2095.  
  2096.  
  2097.  
  2098. &lt;h4&gt;uBlock Origin&lt;/h4&gt;
  2099.  
  2100.  
  2101.  
  2102. &lt;p&gt;Works beautifully “right out of the box.” Just add it to Firefox and &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/ublock-origin/&quot; rel=&quot;noreferrer noopener&quot;&gt;uBlock Origin&lt;/a&gt; will automatically start blocking all types of advertising — display ads, banners, video pre-rolls, pop-ups — you name it. &lt;/p&gt;
  2103.  
  2104.  
  2105.  
  2106. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2107.  
  2108.  
  2109.  
  2110. &lt;p&gt;Of course, if you prefer deeper content blocking customization, uBlock Origin allows for fine control as well, like the ability to import your own custom block filters or access a data display that shows how much of a web page was blocked by the extension. More than just an ad blocker, uBlock Origin also effectively thwarts some websites that may be infected with malware. &lt;/p&gt;
  2111.  
  2112.  
  2113.  
  2114. &lt;p&gt;For more insights about this excellent ad blocker, please see &lt;a href=&quot;https://addons.mozilla.org/blog/ublock-origin-everything-you-need-to-know-about-the-ad-blocker/&quot; rel=&quot;noreferrer noopener&quot;&gt;uBlock Origin — everything you need to know about the ad blocker&lt;/a&gt;, or to explore even more ad blocker options, check out &lt;a href=&quot;https://addons.mozilla.org/blog/whats-the-best-ad-blocker-for-you/&quot; rel=&quot;noreferrer noopener&quot;&gt;What’s the best ad blocker for you?&lt;/a&gt;&lt;/p&gt;
  2115.  
  2116.  
  2117.  
  2118. &lt;h3&gt;&lt;em&gt;I’m concerned about my privacy and tracking around the web&lt;/em&gt;&lt;/h3&gt;
  2119.  
  2120.  
  2121.  
  2122. &lt;h4&gt;Privacy Badger&lt;/h4&gt;
  2123.  
  2124.  
  2125.  
  2126. &lt;p&gt;The flagship anti-tracking extension from privacy proponents at the &lt;a href=&quot;https://www.eff.org/&quot;&gt;Electronic Frontier Foundation&lt;/a&gt;, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/privacy-badger17/&quot; rel=&quot;noreferrer noopener&quot;&gt;Privacy Badger&lt;/a&gt; is programmed to look for tracking heuristics (i.e. specific actions that indicate someone is trying to track you). &lt;/p&gt;
  2127.  
  2128.  
  2129.  
  2130. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2131.  
  2132.  
  2133.  
  2134. &lt;p&gt;Zero set up required. Just install Privacy Badger and it will automatically search for third-party cookies, HTML5 local storage “supercookies,” canvas fingerprinting, and other sneaky tracking methods. &lt;/p&gt;
  2135.  
  2136.  
  2137.  
  2138. &lt;h4&gt;Consent-O-Matic&lt;/h4&gt;
  2139.  
  2140.  
  2141.  
  2142. &lt;p&gt;Not only will &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/consent-o-matic/&quot;&gt;Consent-O-Matic&lt;/a&gt; automatically handle pop-up data consent forms (per &lt;a href=&quot;https://gdpr-info.eu/&quot;&gt;GDPR&lt;/a&gt; regulations), but it’s brilliantly designed to interpret the often intentionally confusing language of consent pop-ups trying to trick you into agreeing to invasive tracking. &lt;/p&gt;
  2143.  
  2144.  
  2145.  
  2146. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2147.  
  2148.  
  2149.  
  2150. &lt;p&gt;Developed by internet privacy researchers at Aarhus University in Denmark who grew sick of seeing so many deceptive consent pop-ups, Consent-O-Matic’s decision-making logic is built upon studying hundreds of pop-ups and identifying duplicitous patterns. So using this extension not only gives you a great ally in the fight against intrusive tracking, but you’re spared the annoyance of constantly clicking consent forms all over the internet. &lt;/p&gt;
  2151.  
  2152.  
  2153.  
  2154. &lt;h3&gt;&lt;em&gt;I need an easier way to translate languages&lt;/em&gt;&lt;/h3&gt;
  2155.  
  2156.  
  2157.  
  2158. &lt;h4&gt;Simple Translate&lt;/h4&gt;
  2159.  
  2160.  
  2161.  
  2162. &lt;p&gt;Do you do a lot of language translations on the web? If so, it’s a hassle always copying text and navigating away from the page you’re on just to translate a word or phrase. &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/simple-translate/&quot; rel=&quot;noreferrer noopener&quot;&gt;Simple Translate&lt;/a&gt; solves this problem by giving you the power to perform translations right there on the page. &lt;/p&gt;
  2163.  
  2164.  
  2165.  
  2166. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2167.  
  2168.  
  2169.  
  2170. &lt;p&gt;Just highlight the text you want translated and right-click to get instant translations in a handy pop-up display, so you never have to leave the page again. &lt;/p&gt;
  2171.  
  2172.  
  2173.  
  2174. &lt;h3&gt;&lt;em&gt;My grammar in speling is bad!&lt;/em&gt;&lt;/h3&gt;
  2175.  
  2176.  
  2177.  
  2178. &lt;h4&gt;&lt;strong&gt;LanguageTool&lt;/strong&gt;&lt;/h4&gt;
  2179.  
  2180.  
  2181.  
  2182. &lt;p&gt;Anywhere you write on the web, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/languagetool/&quot; rel=&quot;noreferrer noopener&quot;&gt;LanguageTool&lt;/a&gt; will be there to lend a guiding editorial hand. It helps fix typos, grammar problems, and even recognizes common word mix-ups like the there/their/they’re. &lt;/p&gt;
  2183.  
  2184.  
  2185.  
  2186. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2187.  
  2188.  
  2189.  
  2190. &lt;p&gt;Available in 25 languages, LanguageTool automatically works on any web-based publishing platform like Gmail, web docs, social media sites, etc. The clever extension will even spot words you’re possibly overusing and suggest alternatives to spruce up your prose. &lt;/p&gt;
  2191.  
  2192.  
  2193.  
  2194. &lt;h3&gt;&lt;em&gt;YouTube your way&lt;/em&gt;&lt;/h3&gt;
  2195.  
  2196.  
  2197.  
  2198. &lt;h4&gt;Improve YouTube!&lt;/h4&gt;
  2199.  
  2200.  
  2201.  
  2202. &lt;p&gt;Boasting 175+ customization features, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/youtube-addon/&quot;&gt;Improve YouTube!&lt;/a&gt; is simple to grasp while providing a huge variety of ways to radically alter YouTube functionality. &lt;/p&gt;
  2203.  
  2204.  
  2205.  
  2206. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2207.  
  2208.  
  2209.  
  2210. &lt;p&gt;Key features include… &lt;/p&gt;
  2211.  
  2212.  
  2213.  
  2214. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2215. &lt;li&gt;Customize YouTube’s layout with different color schemes&lt;/li&gt;
  2216.  
  2217.  
  2218.  
  2219. &lt;li&gt;Create shortcuts for common actions like skipping to next video, scrolling back/forward 10 seconds, volume control &amp;amp; more&lt;/li&gt;
  2220.  
  2221.  
  2222.  
  2223. &lt;li&gt;Filter out unwanted elements like Related Videos, Shorts, Comments, etc. &lt;/li&gt;
  2224.  
  2225.  
  2226.  
  2227. &lt;li&gt;Ad blocking (with ability to allow ads from channels you choose to support)&lt;/li&gt;
  2228.  
  2229.  
  2230.  
  2231. &lt;li&gt;Simple screenshot and save features&lt;/li&gt;
  2232.  
  2233.  
  2234.  
  2235. &lt;li&gt;Playlist shuffle&lt;/li&gt;
  2236.  
  2237.  
  2238.  
  2239. &lt;li&gt;Frame by frame scrolling&lt;/li&gt;
  2240.  
  2241.  
  2242.  
  2243. &lt;li&gt;High-def default video quality&lt;/li&gt;
  2244. &lt;/ul&gt;
  2245.  
  2246.  
  2247.  
  2248. &lt;h3&gt;&lt;em&gt;I’m drowning in browser tabs! Send help! &lt;/em&gt;&lt;/h3&gt;
  2249.  
  2250.  
  2251.  
  2252. &lt;h4&gt;OneTab&lt;/h4&gt;
  2253.  
  2254.  
  2255.  
  2256. &lt;p&gt;You’ve got an overwhelming number of open tabs. You can’t close them. You need them. But you can’t organize them all right now either. You’re too busy. What to do?! &lt;/p&gt;
  2257.  
  2258.  
  2259.  
  2260. &lt;p&gt;If you have &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/onetab/&quot; rel=&quot;noreferrer noopener&quot;&gt;OneTab&lt;/a&gt; on Firefox you just click the toolbar button and suddenly all those open tabs become a clean list of text links listed on a single page. Ahhh serenity.&lt;/p&gt;
  2261.  
  2262.  
  2263.  
  2264. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2265.  
  2266.  
  2267.  
  2268. &lt;p&gt;Not only will you create browser breathing room for yourself, but with all those previously open tabs now closed and converted to text links, you’ve also freed up a bunch of CPU and memory, which should improve browser speed and performance. &lt;/p&gt;
  2269.  
  2270.  
  2271.  
  2272. &lt;p&gt;If you’ve never installed a browser extension before, we hope you found something here that piques your interest to try. To continue exploring ways to personalize Firefox through the power of extensions, please see our collection of 100+ &lt;a href=&quot;https://addons.mozilla.org/firefox/search/?promoted=recommended&amp;amp;sort=random&amp;amp;type=extension&quot; rel=&quot;noreferrer noopener&quot;&gt;Recommended Extensions&lt;/a&gt;. &lt;/p&gt;</description>
  2273. <pubDate>Thu, 16 Oct 2025 19:22:03 +0000</pubDate>
  2274. <dc:creator>Scott DeVaney</dc:creator>
  2275. </item>
  2276. <item>
  2277. <title>The Mozilla Blog: Windows 10 updates are ending. Here’s what it means for Firefox users.</title>
  2278. <guid isPermaLink="false">https://blog.mozilla.org/?p=82297</guid>
  2279. <link>https://blog.mozilla.org/en/firefox/windows-10-updates-support/</link>
  2280. <description>&lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;Firefox logo with orange fox wrapped around purple globe.&quot; class=&quot;wp-image-82299&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/Press_Firefox_Brand_1920x1080_2-1024x576.png&quot; width=&quot;1024&quot; /&gt;&lt;/figure&gt;
  2281.  
  2282.  
  2283.  
  2284. &lt;p&gt;This week Microsoft released the final free monthly update to Windows 10. While this marks the end of support from Microsoft, &lt;strong&gt;Firefox will continue to support Windows 10 for the foreseeable future&lt;/strong&gt;. &lt;/p&gt;
  2285.  
  2286.  
  2287.  
  2288. &lt;p&gt;If you remain on Windows 10, you will &lt;a href=&quot;https://support.mozilla.org/en-US/kb/firefox-support-windows-10-end-support&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;continue to get the same updates&lt;/a&gt; to Firefox you do today, with all of our latest feature improvements and bug fixes. This includes our commitment to resolve security vulnerabilities as rapidly as we can, &lt;a href=&quot;https://blog.mozilla.org/security/2024/04/04/rapidly-leveling-up-firefox-security/&quot;&gt;sometimes in less than 24 hours&lt;/a&gt;, with special security updates. Windows 10 remains a primary platform for Firefox users. Unlike older versions of Windows like Windows 7 and 8, where Mozilla is only offering security updates to Firefox, Windows 10 will get the latest and greatest features and bug fixes just like users on Windows 11. &lt;/p&gt;
  2289.  
  2290.  
  2291.  
  2292. &lt;h3&gt;&lt;strong&gt;Should you upgrade to Windows 11?&lt;/strong&gt;&lt;/h3&gt;
  2293.  
  2294.  
  2295.  
  2296. &lt;p&gt;While Mozilla will continue to deliver the latest updates to Firefox on Windows 10, security online also requires continued updates from Microsoft to Windows 10 itself, and to the many other software and devices that you use on your Windows 10 computer. That’s why &lt;strong&gt;we recommend upgrading to Windows 11 if your computer supports it&lt;/strong&gt;. You can find out if your PC can run Windows 11 and upgrade to it for free from your Windows update settings. With this option, when you start up Windows 11 for the first time you’ll find that Firefox is still installed, and all of your data and settings are just like you left them. &lt;/p&gt;
  2297.  
  2298.  
  2299.  
  2300. &lt;p&gt;If your computer &lt;em&gt;cannot&lt;/em&gt; run Windows 11, or you wish to remain on Windows 10 for other reasons, your next best option is to &lt;strong&gt;make sure you’re getting “extended security updates”&lt;/strong&gt; from Microsoft. While these updates won’t deliver new Windows features or non-security bug fixes, they will fix security vulnerabilities that are found in Windows 10 in the future. You should see an option to “enroll” in these updates in your Windows update settings, and if you choose the “Windows Backup” option you’ll get the updates for free. Microsoft has more information on &lt;a href=&quot;https://www.microsoft.com/windows/extended-security-updates&quot;&gt;Windows 10 extended security updates&lt;/a&gt; if you have other questions. &lt;/p&gt;
  2301.  
  2302.  
  2303.  
  2304. &lt;h3&gt;&lt;strong&gt;Preparing for a device upgrade or new PC&lt;/strong&gt;&lt;/h3&gt;
  2305.  
  2306.  
  2307.  
  2308. &lt;p&gt;If you get a new Windows 11 PC you might be surprised to see that even if you used Windows Backup, non-Microsoft apps like Firefox haven’t migrated with you. You will typically get a link in your start menu or on your desktop to re-install Firefox, and after it’s installed you’ll find that everything is “fresh” — without your bookmarks, saved passwords, browsing history, or any of your other data and settings. &lt;/p&gt;
  2309.  
  2310.  
  2311.  
  2312. &lt;p&gt;This can be frustrating, but we do have a solution for you if you prepare in advance and &lt;strong&gt;back up your data using &lt;/strong&gt;&lt;a href=&quot;https://support.mozilla.org/en-US/kb/how-do-i-set-sync-my-computer&quot;&gt;&lt;strong&gt;Firefox sync&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt; through a &lt;/strong&gt;&lt;a href=&quot;https://www.mozilla.org/account/&quot;&gt;&lt;strong&gt;Mozilla account&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;.&lt;/strong&gt; To get started with sync, just choose “sign in” from the Firefox toolbar or menu, and we’ll walk you through the quick process of creating a Mozilla account and enabling sync. &lt;/p&gt;
  2313.  
  2314.  
  2315.  
  2316. &lt;h3&gt;&lt;strong&gt;Firefox sync helps transfer your data securely&lt;/strong&gt;&lt;/h3&gt;
  2317.  
  2318.  
  2319.  
  2320. &lt;p&gt;Sync isn’t just for people who have Firefox running on more than one computer. It’s also a safe way to back up your data and protect yourself against a lost laptop, a computer that breaks down or is damaged, or your own excited forgetfulness if you get rid of your old PC the moment you get a new one. And what many Firefox users may not realize is that Firefox sync is “end-to-end encrypted,” which is a fancy way of saying that not even Mozilla can read your data. Without your password, which we don’t know, your data is an indecipherable scramble even to us. But it’s safe on our servers nonetheless, which means that if you find yourself with a new PC and a “fresh” Firefox, all you need to do is log in and all your bookmarks, passwords, history and more will quickly load in. &lt;/p&gt;
  2321.  
  2322.  
  2323.  
  2324. &lt;p&gt;Meanwhile, you can also rest assured that if you continue to use Firefox on Windows 10 over the next few years, we’ll let you know through messages in Firefox if there is new information about staying secure and whether our stance regarding our support for Windows 10 needs to change. &lt;br /&gt;&lt;br /&gt;Thanks for using Firefox, and know that you can always reach us at &lt;a href=&quot;https://connect.mozilla.org/&quot;&gt;Mozilla Connect&lt;/a&gt;. We’re eager for your feedback and questions.&lt;/p&gt;
  2325.  
  2326.  
  2327.  
  2328. &lt;a class=&quot;ft-c-inline-cta&quot; href=&quot;https://www.mozilla.org/firefox/new/?utm_source=blog.mozilla.org&amp;amp;utm_medium=referral&amp;amp;utm_campaign=blog-nav&quot;&gt;
  2329.  &lt;div class=&quot;ft-c-inline-cta__media&quot;&gt;
  2330.  &lt;img alt=&quot;&quot; class=&quot;attachment-1x1 size-1x1&quot; height=&quot;800&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2021/10/Visual-Guidelines-800x800.png&quot; width=&quot;800&quot; /&gt;  &lt;/div&gt;
  2331.  &lt;div class=&quot;ft-c-inline-cta__content&quot;&gt;
  2332.     &lt;h4&gt;Take control of your internet&lt;/h4&gt;      &lt;span&gt;Download Firefox&lt;/span&gt;   &lt;/div&gt;
  2333. &lt;/a&gt;
  2334. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/firefox/windows-10-updates-support/&quot;&gt;Windows 10 updates are ending. Here’s what it means for Firefox users.&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  2335. <pubDate>Thu, 16 Oct 2025 17:14:25 +0000</pubDate>
  2336. <dc:creator>David Rubino</dc:creator>
  2337. </item>
  2338. <item>
  2339. <title>The Rust Programming Language Blog: docs.rs: changed default targets</title>
  2340. <guid isPermaLink="true">https://blog.rust-lang.org/2025/10/16/docsrs-changed-default-targets/</guid>
  2341. <link>https://blog.rust-lang.org/2025/10/16/docsrs-changed-default-targets/</link>
  2342. <description>&lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/10/16/docsrs-changed-default-targets/#changes-to-default-build-targets-on-docs-rs&quot;&gt;&lt;/a&gt;
  2343. Changes to default build targets on docs.rs&lt;/h3&gt;
  2344. &lt;p&gt;This post announces two changes to the list of default targets used to build
  2345. documentation on docs.rs.&lt;/p&gt;
  2346. &lt;p&gt;Crate authors can specify a custom list of targets using
  2347. &lt;a href=&quot;https://docs.rs/about/metadata&quot;&gt;docs.rs metadata in &lt;code&gt;Cargo.toml&lt;/code&gt;&lt;/a&gt;. If this
  2348. metadata is not provided, docs.rs falls back to a default list. We are updating
  2349. this list to better reflect the current state of the Rust ecosystem.&lt;/p&gt;
  2350. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/10/16/docsrs-changed-default-targets/#apple-silicon-arm64-replaces-x86-64&quot;&gt;&lt;/a&gt;
  2351. Apple silicon (ARM64) replaces x86_64&lt;/h4&gt;
  2352. &lt;p&gt;Reflecting Apple's transition from x86_64 to its own ARM64 silicon, the Rust
  2353. project has updated its platform support tiers. The &lt;code&gt;aarch64-apple-darwin&lt;/code&gt;
  2354. target is now Tier 1, while &lt;code&gt;x86_64-apple-darwin&lt;/code&gt; has moved to Tier 2. You can
  2355. read more about this in &lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3671&quot;&gt;RFC 3671&lt;/a&gt;
  2356. and &lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3841&quot;&gt;RFC 3841&lt;/a&gt;.&lt;/p&gt;
  2357. &lt;p&gt;To align with this, docs.rs will now use &lt;code&gt;aarch64-apple-darwin&lt;/code&gt; as the default
  2358. target for Apple platforms instead of &lt;code&gt;x86_64-apple-darwin&lt;/code&gt;.&lt;/p&gt;
  2359. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/10/16/docsrs-changed-default-targets/#linux-arm64-replaces-32-bit-x86&quot;&gt;&lt;/a&gt;
  2360. Linux ARM64 replaces 32-bit x86&lt;/h4&gt;
  2361. &lt;p&gt;Support for 32-bit &lt;code&gt;i686&lt;/code&gt; architectures is declining, and major Linux
  2362. distributions have begun to phase it out.&lt;/p&gt;
  2363. &lt;p&gt;Consequently, we are replacing the &lt;code&gt;i686-unknown-linux-gnu&lt;/code&gt; target with
  2364. &lt;code&gt;aarch64-unknown-linux-gnu&lt;/code&gt; in our default set.&lt;/p&gt;
  2365. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/10/16/docsrs-changed-default-targets/#new-default-target-list&quot;&gt;&lt;/a&gt;
  2366. New default target list&lt;/h4&gt;
  2367. &lt;p&gt;The updated list of default targets is:&lt;/p&gt;
  2368. &lt;ul&gt;
  2369. &lt;li&gt;&lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt;&lt;/li&gt;
  2370. &lt;li&gt;&lt;code&gt;aarch64-apple-darwin&lt;/code&gt; (replaces &lt;code&gt;x86_64-apple-darwin&lt;/code&gt;)&lt;/li&gt;
  2371. &lt;li&gt;&lt;code&gt;x86_64-pc-windows-msvc&lt;/code&gt;&lt;/li&gt;
  2372. &lt;li&gt;&lt;code&gt;aarch64-unknown-linux-gnu&lt;/code&gt; (replaces &lt;code&gt;i686-unknown-linux-gnu&lt;/code&gt;)&lt;/li&gt;
  2373. &lt;li&gt;&lt;code&gt;i686-pc-windows-msvc&lt;/code&gt;&lt;/li&gt;
  2374. &lt;/ul&gt;
  2375. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/10/16/docsrs-changed-default-targets/#opting-out&quot;&gt;&lt;/a&gt;
  2376. Opting out&lt;/h4&gt;
  2377. &lt;p&gt;If your crate requires the previous default target list, you can explicitly
  2378. define it in your &lt;code&gt;Cargo.toml&lt;/code&gt;:&lt;/p&gt;
  2379. &lt;pre class=&quot;language-toml z-code&quot;&gt;&lt;code class=&quot;language-toml&quot;&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-table z-begin z-toml&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;z-meta z-tag z-table z-toml&quot;&gt;&lt;span class=&quot;z-entity z-name z-table z-toml&quot;&gt;package&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-table z-toml&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;z-entity z-name z-table z-toml&quot;&gt;metadata&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-table z-toml&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;z-entity z-name z-table z-toml&quot;&gt;docs&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-table z-toml&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;z-entity z-name z-table z-toml&quot;&gt;rs&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-definition z-table z-end z-toml&quot;&gt;]&lt;/span&gt;
  2380. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;&lt;span class=&quot;z-meta z-tag z-key z-toml&quot;&gt;&lt;span class=&quot;z-entity z-name z-tag z-toml&quot;&gt;targets&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;z-punctuation z-definition z-key-value z-toml&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;z-punctuation z-definition z-array z-begin z-toml&quot;&gt;[&lt;/span&gt;
  2381. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;    &lt;span class=&quot;z-string z-quoted z-double z-basic z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-string z-begin z-toml&quot;&gt;&quot;&lt;/span&gt;x86_64-unknown-linux-gnu&lt;span class=&quot;z-punctuation z-definition z-string z-end z-toml&quot;&gt;&quot;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-array z-toml&quot;&gt;,&lt;/span&gt;
  2382. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;    &lt;span class=&quot;z-string z-quoted z-double z-basic z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-string z-begin z-toml&quot;&gt;&quot;&lt;/span&gt;x86_64-apple-darwin&lt;span class=&quot;z-punctuation z-definition z-string z-end z-toml&quot;&gt;&quot;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-array z-toml&quot;&gt;,&lt;/span&gt;
  2383. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;    &lt;span class=&quot;z-string z-quoted z-double z-basic z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-string z-begin z-toml&quot;&gt;&quot;&lt;/span&gt;x86_64-pc-windows-msvc&lt;span class=&quot;z-punctuation z-definition z-string z-end z-toml&quot;&gt;&quot;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-array z-toml&quot;&gt;,&lt;/span&gt;
  2384. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;    &lt;span class=&quot;z-string z-quoted z-double z-basic z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-string z-begin z-toml&quot;&gt;&quot;&lt;/span&gt;i686-unknown-linux-gnu&lt;span class=&quot;z-punctuation z-definition z-string z-end z-toml&quot;&gt;&quot;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-array z-toml&quot;&gt;,&lt;/span&gt;
  2385. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;    &lt;span class=&quot;z-string z-quoted z-double z-basic z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-string z-begin z-toml&quot;&gt;&quot;&lt;/span&gt;i686-pc-windows-msvc&lt;span class=&quot;z-punctuation z-definition z-string z-end z-toml&quot;&gt;&quot;&lt;/span&gt;&lt;/span&gt;
  2386. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-array z-end z-toml&quot;&gt;]&lt;/span&gt;
  2387. &lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
  2388. &lt;p&gt;Note that docs.rs continues to support any target available in the Rust
  2389. toolchain; only the &lt;em&gt;default&lt;/em&gt; list has changed.&lt;/p&gt;</description>
  2390. <pubDate>Thu, 16 Oct 2025 00:00:00 +0000</pubDate>
  2391. <dc:creator>Denis Cornehl</dc:creator>
  2392. </item>
  2393. <item>
  2394. <title>Firefox Add-on Reviews: Translate the web easily with a browser extension</title>
  2395. <guid isPermaLink="true">https://addons.mozilla.org/blog/translate-the-web-easily-with-a-browser-extension/</guid>
  2396. <link>https://addons.mozilla.org/blog/translate-the-web-easily-with-a-browser-extension/</link>
  2397. <description>&lt;p&gt;At Mozilla, of course we’re fans of &lt;a href=&quot;https://www.firefox.com/features/translate/&quot;&gt;Firefox’s built-in, privacy-focused translation feature&lt;/a&gt;, but the beauty of browser extensions is the vast array of niche tools and customization features they can provide. Sometimes finding the right extension for your personal needs can profoundly change the way you interact with the web. So if you do a lot of translating on the internet, you might consider using a specialized extension translator. Here are some great options…&lt;/p&gt;
  2398.  
  2399.  
  2400.  
  2401. &lt;h3&gt;&lt;em&gt;&lt;span class=&quot;has-inline-color has-light-green-cyan-color&quot;&gt;I just want a simple, efficient way to translate. I don’t need fancy features.&lt;/span&gt;&lt;/em&gt;&lt;/h3&gt;
  2402.  
  2403.  
  2404.  
  2405. &lt;h4&gt;Simple Translate&lt;/h4&gt;
  2406.  
  2407.  
  2408.  
  2409. &lt;p&gt;It doesn’t get much simpler than this. Highlight the text you want to translate and click the extension’s toolbar icon to activate a streamlined pop-up. Your highlighted text automatically appears in the pop-up’s translation field and a drop-down menu lets you easily select your target language. &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/simple-translate/&quot; rel=&quot;noreferrer noopener&quot;&gt;Simple Translate&lt;/a&gt; also features a handy one-click “Translate this page” button. &lt;/p&gt;
  2410.  
  2411.  
  2412.  
  2413. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2414.  
  2415.  
  2416.  
  2417. &lt;h4&gt;Translate Web Pages&lt;/h4&gt;
  2418.  
  2419.  
  2420.  
  2421. &lt;p&gt;Maybe you just need to translate full web pages, like when reading news articles, how-to guides, or job related sites. If so, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/traduzir-paginas-web/&quot; rel=&quot;noreferrer noopener&quot;&gt;Translate Web Pages&lt;/a&gt; might be the ideal solution for you with its sharp focus on full-page utility. &lt;/p&gt;
  2422.  
  2423.  
  2424.  
  2425. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2426.  
  2427.  
  2428.  
  2429. &lt;p&gt;The extension includes a handy feature if you commonly translate a few languages — you can select up to three languages to easily access with a single-click popup menu. TWP also gives you the option to designate specific websites you always want translated without prompt. &lt;/p&gt;
  2430.  
  2431.  
  2432.  
  2433. &lt;h4&gt;S3.Translator&lt;/h4&gt;
  2434.  
  2435.  
  2436.  
  2437. &lt;p&gt;Supporting 100+ languages, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/s3_translator/&quot; rel=&quot;noreferrer noopener&quot;&gt;S3.Translator&lt;/a&gt; serves up a full feature set of language tools, like the ability to translate full or select portions of a page, text-to-speech translation, YouTube subtitle translations, and more.&lt;/p&gt;
  2438.  
  2439.  
  2440.  
  2441. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2442.  
  2443.  
  2444.  
  2445. &lt;p&gt;There’s even a nifty Learning Language mode, which allows you to turn any text into the language you’re studying. Toggle between languages so you can conveniently learn as you naturally browse the web.&lt;/p&gt;
  2446.  
  2447.  
  2448.  
  2449. &lt;h4&gt;To Google Translate&lt;/h4&gt;
  2450.  
  2451.  
  2452.  
  2453. &lt;p&gt;Very popular, very simple translation extension that exclusively uses Google’s translation services, including text-to-speech. &lt;/p&gt;
  2454.  
  2455.  
  2456.  
  2457. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2458.  
  2459.  
  2460.  
  2461. &lt;p&gt;Simply highlight any text on a web page and right-click to pull up a &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/to-google-translate/&quot; rel=&quot;noreferrer noopener&quot;&gt;To Google Translate&lt;/a&gt; context menu that allows three actions: 1) translate into your preferred language; 2) listen to audio of the text; 3) Translate the entire page&lt;/p&gt;
  2462.  
  2463.  
  2464.  
  2465. &lt;figure class=&quot;wp-block-image&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-142&quot; height=&quot;619&quot; src=&quot;https://mozamo.wpengine.com/wp-content/uploads/2021/06/blogTGT-1024x619.png&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;Right-click any highlighted text to activate To Google Translate.&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  2466.  
  2467.  
  2468.  
  2469. &lt;h3&gt;&lt;em&gt;I do a ton of translating. I need power features to save me time and trouble.&lt;/em&gt;&lt;/h3&gt;
  2470.  
  2471.  
  2472.  
  2473. &lt;h4&gt;ImTranslator&lt;/h4&gt;
  2474.  
  2475.  
  2476.  
  2477. &lt;p&gt;Striking a balance between out-of-the-box ease and deep customization potential, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/imtranslator/&quot; rel=&quot;noreferrer noopener&quot;&gt;ImTranslator&lt;/a&gt; leverages three top translation engines (Google, Bing, Translator) to cover 100+ languages. &lt;/p&gt;
  2478.  
  2479.  
  2480.  
  2481. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2482.  
  2483.  
  2484.  
  2485. &lt;p&gt;Other strong features include text-to-speech, dictionary and spell check in eight languages, hotkey customization, and a huge assortment of ways to customize the look of ImTranslator’s interface — from light and dark themes to font size and more. &lt;/p&gt;
  2486.  
  2487.  
  2488.  
  2489. &lt;h4&gt;Immersive Translate&lt;/h4&gt;
  2490.  
  2491.  
  2492.  
  2493. &lt;p&gt;One of the most feature packed translation extensions you’ll find, &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/immersive-translate/&quot;&gt;Immersive Translate&lt;/a&gt; goes beyond the web to capably handle PDF’s, eBooks and much more. &lt;/p&gt;
  2494.  
  2495.  
  2496.  
  2497. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2498.  
  2499.  
  2500.  
  2501. &lt;p&gt;With more features than we have space to list, here are some of the most uniquely compelling capabilities of Immersive Translate.&lt;/p&gt;
  2502.  
  2503.  
  2504.  
  2505. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2506. &lt;li&gt;Smartly identifies the main content portions of a web page to provide elegant side-by-side bilingual translations while avoiding page clutter&lt;/li&gt;
  2507.  
  2508.  
  2509.  
  2510. &lt;li&gt;Mouse hover translations&lt;/li&gt;
  2511.  
  2512.  
  2513.  
  2514. &lt;li&gt;Input translation box, so you can enter text to be translated (an ideal tool for real-time bilingual conversations)&lt;/li&gt;
  2515.  
  2516.  
  2517.  
  2518. &lt;li&gt;Video subtitle translations&lt;/li&gt;
  2519.  
  2520.  
  2521.  
  2522. &lt;li&gt;Strong Desktop and mobile support&lt;/li&gt;
  2523. &lt;/ul&gt;
  2524.  
  2525.  
  2526.  
  2527. &lt;h4&gt;Mate Translate&lt;/h4&gt;
  2528.  
  2529.  
  2530.  
  2531. &lt;p&gt;A slick, intuitive extension that performs all basic translation functions very well, but it’s &lt;a href=&quot;https://addons.mozilla.org/firefox/addon/instant-translate/&quot; rel=&quot;noreferrer noopener&quot;&gt;Mate Translate&lt;/a&gt;’s paid tier that unlocks some unique features, such as Sync (saved translations can appear across devices and browsers, including iPhones and Mac). &lt;/p&gt;
  2532.  
  2533.  
  2534.  
  2535. &lt;div class=&quot;addon-card&quot;&gt;&lt;/div&gt;
  2536.  
  2537.  
  2538.  
  2539. &lt;p&gt;There’s also a neat Phrasebook feature, which lets you build custom word and phrase lists so you can return to common translations you frequently need. It works offline, too, so it’s ideal for travellers who need quick reference to common foreign phrases. &lt;/p&gt;
  2540.  
  2541.  
  2542.  
  2543. &lt;p&gt;These are some of our favorites, but there are plenty &lt;a href=&quot;https://addons.mozilla.org/firefox/search/?q=translate&quot; rel=&quot;noreferrer noopener&quot;&gt;more translation extensions to explore&lt;/a&gt; on &lt;em&gt;addons.mozilla.org&lt;/em&gt;.&lt;/p&gt;</description>
  2544. <pubDate>Wed, 15 Oct 2025 23:14:16 +0000</pubDate>
  2545. <dc:creator>Scott DeVaney</dc:creator>
  2546. </item>
  2547. <item>
  2548. <title>The Mozilla Blog: Fox Recap: A student-built tool that analyzes your browsing habits</title>
  2549. <guid isPermaLink="false">https://blog.mozilla.org/?p=81518</guid>
  2550. <link>https://blog.mozilla.org/en/firefox/firefox-recap/</link>
  2551. <description>&lt;p&gt;What would your browser history say about you? Whether you were getting things done this week or just collecting tabs, a new Firefox extension helps you reflect on your digital habits. &lt;/p&gt;
  2552.  
  2553.  
  2554.  
  2555. &lt;p&gt;Designed as a personal productivity tool, &lt;a href=&quot;https://addons.mozilla.org/en-US/firefox/addon/fox-recap/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Fox Recap&lt;/a&gt; is a &lt;a href=&quot;https://sites.google.com/csumb.edu/cscapstone-s2025/cs-projects/firefox-ai-platform?authuser=0&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;capstone project&lt;/a&gt; from a group of college seniors at California State University, Monterey Bay. It categorizes your browsing history, shows how much time you’re spending on different sites, and turns that data into simple visual reports. Everything happens locally on your device, so your information stays private.&lt;/p&gt;
  2556.  
  2557.  
  2558.  
  2559. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Related story: &lt;a href=&quot;https://blog.mozilla.org/addons/2025/10/21/developer-spotlight-fox-recap/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Developer Spotlight: Fox Recap&lt;/a&gt;&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
  2560.  
  2561.  
  2562.  
  2563. &lt;p&gt;&lt;/p&gt;
  2564.  
  2565.  
  2566.  
  2567. &lt;div class=&quot;wp-block-group is-content-justification-space-between is-nowrap is-layout-flex wp-container-1 wp-block-group-is-layout-flex&quot;&gt;
  2568. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;Gradient intro card inviting a dive into today’s browser activity overview&quot; class=&quot;wp-image-81539&quot; height=&quot;1024&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/08/2-607x1024.png&quot; width=&quot;607&quot; /&gt;&lt;/figure&gt;
  2569.  
  2570.  
  2571.  
  2572. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;Browser activity stat card showing Technology as most-clicked with 37 visits&quot; class=&quot;wp-image-81529&quot; height=&quot;1024&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/08/1-607x1024.png&quot; width=&quot;607&quot; /&gt;&lt;/figure&gt;
  2573. &lt;/div&gt;
  2574.  
  2575.  
  2576.  
  2577. &lt;p&gt;&lt;/p&gt;
  2578.  
  2579.  
  2580.  
  2581. &lt;h3&gt;How Fox Recap works&lt;/h3&gt;
  2582.  
  2583.  
  2584.  
  2585. &lt;p&gt;Once you &lt;a href=&quot;https://addons.mozilla.org/en-US/firefox/addon/fox-recap/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;download&lt;/a&gt; and open the extension on Firefox for desktop, click on settings and grant permission to run the ML engine. From there, you can choose to view your browsing history for today, this week or this month. &lt;/p&gt;
  2586.  
  2587.  
  2588.  
  2589. &lt;p&gt;Fox Recap then lays out your activity in simple charts and categories like technology, shopping, education and entertainment.&lt;/p&gt;
  2590.  
  2591.  
  2592.  
  2593. &lt;p&gt;“It’s really a tool for you to know how you use your browser,” said one of the student developers, Taimur Hasan. “Maybe you want to lessen the amount of time you spend on entertainment, and see that you use more education sites.”&lt;/p&gt;
  2594.  
  2595.  
  2596.  
  2597. &lt;p&gt;Kate Sawtell wanted to create a tool that helps people see how they spend their time on the internet. “As a busy mom with a bunch of side projects, I love how it shows where my time online actually goes,” Kate said. “Am I researching, streaming shows or slipping into online shopping holes? It’s not super serious or judgmental, just a quick snapshot of my habits. Sometimes it makes me feel productive, other times it’s like, wow okay maybe I should chill on the shopping tab.”&lt;/p&gt;
  2598.  
  2599.  
  2600. &lt;div class=&quot;wp-block-image&quot;&gt;
  2601. &lt;figure class=&quot;aligncenter size-large is-resized&quot;&gt;&lt;img alt=&quot;Four people standing in front of a Firefox Recap project display at California State University, Monterey Bay. From left to right: Taimur Hasan, Mozilla community manager Matt Cool, Kate Sawtell, and Diego Valdez.&quot; class=&quot;wp-image-81594&quot; height=&quot;768&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/08/firefox_recap_2025-1024x768.jpg&quot; style=&quot;width: 650px;&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;Members of the Fox Recap team at California State University, Monterey Bay, presenting their capstone project. Pictured (left to right): Taimur Hasan, Mozilla community manager Matt Cool, Kate Sawtell, and Diego Valdez. Not pictured: Peter Mitchell.&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;&lt;/div&gt;
  2602.  
  2603.  
  2604. &lt;h3&gt;‘Useful AI and strong privacy can coexist’&lt;/h3&gt;
  2605.  
  2606.  
  2607.  
  2608. &lt;p&gt;Firefox machine learning engineer Tarek Ziadé served as a mentor for the project. He was struck by how quickly Taimur, Kate, Diego and Peter internalized both the technical challenges of building AI features and their privacy implications. &lt;/p&gt;
  2609.  
  2610.  
  2611.  
  2612. &lt;p&gt;“I had assumed younger developers might treat privacy as an afterthought,” Tarek said. “I was wrong. They pushed for privacy by design from the start.”&lt;/p&gt;
  2613.  
  2614.  
  2615.  
  2616. &lt;p&gt;Taimur, who trained the model himself rather than using an existing one, explained: “It’s not an off-the-shelf model that I pulled off the internet. I trained it myself using my gaming computer.”&lt;/p&gt;
  2617.  
  2618.  
  2619.  
  2620. &lt;div class=&quot;wp-block-group is-nowrap is-layout-flex wp-container-2 wp-block-group-is-layout-flex&quot;&gt;&lt;div class=&quot;wp-block-image&quot;&gt;
  2621. &lt;figure class=&quot;aligncenter size-large is-resized&quot;&gt;&lt;img alt=&quot;&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/08/categories-1.gif&quot; style=&quot;width: 416px;&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  2622.  
  2623.  
  2624. &lt;figure class=&quot;wp-block-image size-large is-resized&quot;&gt;&lt;img alt=&quot;Browser activity stat card showing Technology as most-clicked with 37 visits&quot; class=&quot;wp-image-81529&quot; height=&quot;1024&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/08/1-607x1024.png&quot; style=&quot;width: 416px;&quot; width=&quot;607&quot; /&gt;&lt;/figure&gt;
  2625. &lt;/div&gt;
  2626.  
  2627.  
  2628.  
  2629. &lt;p&gt;&lt;/p&gt;
  2630.  
  2631.  
  2632.  
  2633. &lt;p&gt;Tarek believes that what the group built reflects the direction in which privacy-focused technology is headed.&lt;/p&gt;
  2634.  
  2635.  
  2636.  
  2637. &lt;p&gt;“Intelligence should be local by default, data should be minimized, and anything that needs to leave the device should be explicit and consented,” Tarek said. “As AI capabilities become a commodity, the differentiator will be trust.”&lt;/p&gt;
  2638.  
  2639.  
  2640.  
  2641. &lt;p&gt;That’s exactly where Mozilla should be leading, Tarek added: “making high-quality, on-device AI the default, and proving that useful AI and strong privacy can coexist.”&lt;/p&gt;
  2642.  
  2643.  
  2644.  
  2645. &lt;h3&gt;A glimpse of the next generation of web builders&lt;/h3&gt;
  2646.  
  2647.  
  2648.  
  2649. &lt;p&gt;For team member Diego Valdez, the project’s value is personal and practical: “I hope people who use Fox Recap can learn about their browsing activity in an engaging way, in hopes [of helping them] improve their productivity.”&lt;/p&gt;
  2650.  
  2651.  
  2652.  
  2653. &lt;p&gt;Mozilla community manager Matt Cool sees it in a larger frame. “It’s a scary and exciting time to enter the tech industry,” &lt;a href=&quot;https://mattcool.tech/posts/csumb-student-capstones-2025&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Matt said&lt;/a&gt;. “The next generation of open web builders is already stepping up. Right here in Monterey, they’re building real-world projects, contributing to open-source, and tackling some of the toughest problems facing the future of the web.”&lt;/p&gt;
  2654.  
  2655.  
  2656.  
  2657. &lt;p&gt;Fox Recap is one of several student projects showcased at this spring’s Capstone Festival by the School of Computing and Design at Cal State Monterey Bay. Professor Bude Su, who chairs the department, emphasized the value of mentorship as students prepare for what comes next.&lt;/p&gt;
  2658.  
  2659.  
  2660.  
  2661. &lt;p&gt;“Mozilla’s involvement brought an added layer of motivation for our students,” Professor Su said. “The opportunity to work on a real-world project under industry mentorship has been invaluable for our students’ learning and professional growth.”&lt;/p&gt;
  2662.  
  2663.  
  2664.  
  2665. &lt;p&gt;The collaboration shows what can happen when education, mentorship and Mozilla’s values of openness and trust come together. Fox Recap helps make sense of the tabs we collect, but it also points to something bigger: a new wave of developers building tools that respect the people who use them.&lt;/p&gt;
  2666.  
  2667.  
  2668.  
  2669. &lt;a class=&quot;ft-c-inline-cta&quot; href=&quot;https://www.mozilla.org/firefox/new/?utm_source=blog.mozilla.org&amp;amp;utm_medium=referral&amp;amp;utm_campaign=blog-nav&quot;&gt;
  2670.  &lt;div class=&quot;ft-c-inline-cta__media&quot;&gt;
  2671.  &lt;img alt=&quot;&quot; class=&quot;attachment-1x1 size-1x1&quot; height=&quot;800&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2021/10/Visual-Guidelines-800x800.png&quot; width=&quot;800&quot; /&gt;  &lt;/div&gt;
  2672.  &lt;div class=&quot;ft-c-inline-cta__content&quot;&gt;
  2673.     &lt;h4&gt;Take control of your internet&lt;/h4&gt;      &lt;span&gt;Download Firefox&lt;/span&gt;   &lt;/div&gt;
  2674. &lt;/a&gt;
  2675. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/firefox/firefox-recap/&quot;&gt;Fox Recap: A student-built tool that analyzes your browsing habits &lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  2676. <pubDate>Wed, 15 Oct 2025 17:53:49 +0000</pubDate>
  2677. <dc:creator>Kristina Bravo</dc:creator>
  2678. </item>
  2679. <item>
  2680. <title>The Mozilla Blog: The social media director who helps make Merriam-Webster go viral</title>
  2681. <guid isPermaLink="false">https://blog.mozilla.org/?p=82268</guid>
  2682. <link>https://blog.mozilla.org/en/internet-culture/interviews/merriam-webster-social/</link>
  2683. <description>&lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;A bearded man in a denim shirt over a dark T-shirt, against a green background with a layered pixel effect.&quot; class=&quot;wp-image-82269&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/MCOTI_John-Sabine-Merriam-Webster-1024x576.png&quot; width=&quot;1024&quot; /&gt;&lt;/figure&gt;
  2684.  
  2685.  
  2686.  
  2687. &lt;p&gt;&lt;em&gt;Here at Mozilla, we are the first to admit the internet isn’t perfect, but we know the internet is pretty darn magical. The internet opens up doors and opportunities, allows for human connection, and lets everyone find where they belong — their corners of the internet. We all have an internet story worth sharing. In &lt;/em&gt;&lt;a href=&quot;https://blog.mozilla.org/tag/my-corner-of-the-internet/&quot;&gt;&lt;em&gt;My Corner Of The Internet&lt;/em&gt;&lt;/a&gt;&lt;em&gt;, we talk with people about the online spaces they can’t get enough of, the sites and forums that shaped them, and how they would design their own corner of the web.&lt;/em&gt;&lt;/p&gt;
  2688.  
  2689.  
  2690.  
  2691. &lt;p&gt;&lt;em&gt;We caught up with John Sabine, the social media director of Merriam-Webster and Encyclopedia Britannica. He talks about his favorite subreddit, silly deep dives and why his job makes him hopeful about the internet.&lt;/em&gt;&lt;br /&gt;&lt;/p&gt;
  2692.  
  2693.  
  2694.  
  2695. &lt;h3&gt;&lt;strong&gt;What is your favorite corner of the internet?&lt;/strong&gt;&lt;/h3&gt;
  2696.  
  2697.  
  2698.  
  2699. &lt;p&gt;Honestly, it’s the &lt;a href=&quot;https://www.reddit.com/r/AskHistorians/&quot;&gt;“AskHistorians” subreddit&lt;/a&gt;. It’s one of my few internet habits that I have that has kept up. I can’t recommend it enough. I wish more things were curated with such level of scrutiny and scholarship. If people disagree, they disagree as Ph.D. people disagree. I don’t have a Ph.D., but I imagine it’s respectful. There’s profiles and avatars, but those feel very secondary to the content. You lead with the “what,” and then you can look up the “who” afterwards. I don’t post on Reddit at all; I’m a lurker in general on the internet. So I’m shocked by how many people weigh in on things.&lt;/p&gt;
  2700.  
  2701.  
  2702.  
  2703. &lt;h3&gt;&lt;strong&gt;What is an internet deep dive that you can’t wait to jump back into?&lt;/strong&gt;&lt;/h3&gt;
  2704.  
  2705.  
  2706.  
  2707. &lt;p&gt;I have a bunch of articles that I have bookmarked… and my goal is to read one of the 400 articles I have saved. What I’m looking forward to specifically is just to read an article for joy, that’s not doomscrolling or part of my job. I do feel like when you have this job, you kind of get &lt;em&gt;internet-ed&lt;/em&gt; out every day. And also: crosswords. I want to get better at crosswords, if that counts. We have one on &lt;a href=&quot;http://merriam-webster.com&quot;&gt;merriam-webster.com&lt;/a&gt;, and I also do The New York Times, though I rarely finish it.&lt;/p&gt;
  2708.  
  2709.  
  2710.  
  2711. &lt;h3&gt;&lt;strong&gt;What’s the last great story that you read?&lt;/strong&gt;&lt;/h3&gt;
  2712.  
  2713.  
  2714.  
  2715. &lt;p&gt;It was on &lt;a href=&quot;http://ringer.com&quot;&gt;ringer.com&lt;/a&gt;. A writer named &lt;a href=&quot;https://www.theringer.com/2025/10/06/nba/best-nba-player-names-ranked-21st-century&quot;&gt;Tyler Parker went through NBA names&lt;/a&gt;. He just ranked their names, had nothing to do with basketball. I started it before bed, and I was like, “Oh, I’ll skim.” I read every single word. He really thought about the names and how they make people feel. And it’s truly just how they sound like. That’s it. It was written beautifully. That’s a silly one, but I think silly deep dives are probably good for the soul right now.&lt;/p&gt;
  2716.  
  2717.  
  2718.  
  2719. &lt;h3&gt;&lt;strong&gt;What is the one tab you always regret closing?&lt;/strong&gt;&lt;/h3&gt;
  2720.  
  2721.  
  2722.  
  2723. &lt;p&gt;Probably my calendar… And honestly, I always have Merriam-Webster and Britannica up. And I rarely do close them because I always need them for my work.&lt;/p&gt;
  2724.  
  2725.  
  2726.  
  2727. &lt;h3&gt;&lt;strong&gt;What can you not stop talking about on the internet right now?&lt;/strong&gt;&lt;/h3&gt;
  2728.  
  2729.  
  2730.  
  2731. &lt;p&gt;So Merriam-Webster is releasing &lt;a href=&quot;https://www.merriam-webster.com/collegiate-dictionary-twelfth-edition&quot;&gt;its first print dictionary&lt;/a&gt; in over 20 years. And they made it really pretty, and it feels like a really cool book that you would display. I’m very excited because I’m doing deep dives of old ads for an almost 200-year-old company. There’s a lot of stuff to go through. Some of it we have in the archives, some of it is just out there. So just going through the old print stuff, finding old paper dictionaries. So, like, selfishly, I’m excited for the new collegiate 12th edition.&lt;/p&gt;
  2732.  
  2733.  
  2734.  
  2735. &lt;h3&gt;&lt;strong&gt;What was the first online community you engaged with?&lt;/strong&gt;&lt;/h3&gt;
  2736.  
  2737.  
  2738.  
  2739. &lt;p&gt;I’m a lurker, so engagement is a lot for me. The first time I probably posted was on a forum when I moved to Chicago to do improv comedy. There’s a Chicago improv forum and I think I was like, “What show should I see?”&lt;/p&gt;
  2740.  
  2741.  
  2742.  
  2743. &lt;h3&gt;&lt;strong&gt;What articles and/or videos are you waiting to read/watch right now?&lt;/strong&gt;&lt;/h3&gt;
  2744.  
  2745.  
  2746.  
  2747. &lt;p&gt;I’m waiting for the next [recommendation] from my &lt;a href=&quot;https://mozillasidebar.substack.com/p/gen-z-algorithm&quot;&gt;group chats&lt;/a&gt;. There are some people that will just send you anything, and you’re like, “OK, thank you for sending me this. I’ll watch 30% of the things you sent.” But there’s the ones that you’re like, “Oh, yeah, gotta watch that.” So I’ve got a couple friends like that, so I hope they send me stuff because Lord knows, the internet’s huge.&lt;/p&gt;
  2748.  
  2749.  
  2750.  
  2751. &lt;h3&gt;&lt;strong&gt;Is there anything about the way people engage with Merriam-Webster online that makes you feel hopeful about the internet?&lt;/strong&gt;&lt;/h3&gt;
  2752.  
  2753.  
  2754.  
  2755. &lt;p&gt;Oh, 4,000%. Yes, doomscrolling is a reality of being online now. I know a lot of people who just step away and go outside and touch grass.&lt;/p&gt;
  2756.  
  2757.  
  2758.  
  2759. &lt;p&gt;But there’s still good stuff happening. The comment sections on our &lt;a href=&quot;https://www.instagram.com/merriamwebster/&quot;&gt;Instagram&lt;/a&gt; and &lt;a href=&quot;https://www.tiktok.com/@merriamwebster&quot;&gt;TikTok&lt;/a&gt; can actually be really fun. People have genuine, kind, often funny conversations. It’s rarely mean. Seeing that makes me hopeful, because people clearly want wholesome, thoughtful interactions.&lt;br /&gt;&lt;br /&gt;People have a personal connection to language. Over time, I’ve seen our audience expand to include all kinds of people who care deeply about words, even if they wouldn’t call themselves “word nerds.” Language is personal, and I think our work celebrates that.&lt;/p&gt;
  2760.  
  2761.  
  2762.  
  2763. &lt;p&gt;And honestly, I feel more hopeful doing this job on the internet than I think I would if I weren’t doing this work and was just online as a regular user.&lt;/p&gt;
  2764.  
  2765.  
  2766.  
  2767. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  2768.  
  2769.  
  2770.  
  2771. &lt;p&gt;&lt;em&gt;John Sabine is the social media director for Merriam-Webster and Encyclopedia Britannica. He is originally from Dallas, Texas, and he’s never once spelled “definitely” correctly on the first try.&lt;/em&gt;&lt;/p&gt;
  2772. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/internet-culture/interviews/merriam-webster-social/&quot;&gt;The social media director who helps make Merriam-Webster go viral&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  2773. <pubDate>Wed, 15 Oct 2025 13:00:00 +0000</pubDate>
  2774. <dc:creator>Kristina Bravo</dc:creator>
  2775. </item>
  2776. <item>
  2777. <title>Mozilla Performance Blog: Firefox 144 ships interactionId for INP</title>
  2778. <guid isPermaLink="false">https://blog.mozilla.org/performance/?p=531</guid>
  2779. <link>https://blog.mozilla.org/performance/2025/10/15/firefox-144-ships-interactionid-for-inp/</link>
  2780. <description>&lt;hr /&gt;
  2781. &lt;h3&gt;TL;DR&lt;/h3&gt;
  2782. &lt;p&gt;&lt;b&gt;Firefox 144&lt;/b&gt; ships &lt;code&gt;PerformanceEventTiming.interactionId&lt;/code&gt;, which lets browsers and tools group events that belong to the same user interaction. This property is used to calculate &lt;b&gt;Interaction to Next Paint (INP)&lt;/b&gt;, one of the &lt;a href=&quot;https://web.dev/articles/inp&quot;&gt;Core Web Vitals&lt;/a&gt;.&lt;/p&gt;
  2783. &lt;hr /&gt;
  2784. &lt;p&gt;&lt;b&gt;Firefox 144&lt;/b&gt; ships support for the &lt;code&gt;PerformanceEventTiming.interactionId&lt;/code&gt; property. It helps browsers and tools identify which input events belong to a single user interaction, such as a &lt;code&gt;pointerdown&lt;/code&gt;, &lt;code&gt;pointerup&lt;/code&gt;, and &lt;code&gt;click&lt;/code&gt; triggered by the same tap.&lt;/p&gt;
  2785. &lt;p&gt;The &lt;b&gt;Interaction to Next Paint (INP)&lt;/b&gt; metric, part of the &lt;a href=&quot;https://web.dev/articles/inp&quot;&gt;Core Web Vitals&lt;/a&gt;, relies on this grouping to measure how responsive a page feels during real user interactions. INP represents how long it takes for the next frame to paint after a user input. Instead of looking at a single event, it captures the worst interaction latency during the page’s lifetime, giving a more complete view of responsiveness.&lt;/p&gt;
  2786. &lt;h3&gt;Why this matters&lt;/h3&gt;
  2787. &lt;p&gt;Before &lt;code&gt;interactionId&lt;/code&gt;, each event had to be measured separately, which made it hard to connect related events as part of the same interaction.&lt;br /&gt;
  2788. With this property, performance tools and developers can now:&lt;/p&gt;
  2789. &lt;ul&gt;
  2790. &lt;li&gt;Group related input events into a single interaction&lt;/li&gt;
  2791. &lt;li&gt;Measure interaction latency more accurately&lt;/li&gt;
  2792. &lt;li&gt;Identify and debug slow interactions more easily&lt;/li&gt;
  2793. &lt;/ul&gt;
  2794. &lt;h3&gt;Using interactionId&lt;/h3&gt;
  2795. &lt;p&gt;If you use the&lt;a href=&quot;https://developer.mozilla.org/docs/Web/API/PerformanceObserver&quot;&gt; PerformanceObserver API&lt;/a&gt; to collect &lt;code&gt;PerformanceEventTiming&lt;/code&gt; entries, you’ll start seeing an &lt;code&gt;interactionId&lt;/code&gt; field in Firefox 144. Events that share a non-zero &lt;code&gt;interactionId&lt;/code&gt; belong to the same interaction group, which can be used to calculate latency or understand where delays occur.&lt;/p&gt;
  2796. &lt;pre style=&quot;background: #2d2d2d; color: #ccc; padding: 10px; border-radius: 6px; overflow: auto; margin-top: 0; line-height: 1.4;&quot;&gt;&lt;code&gt;&lt;span style=&quot;color: #999;&quot;&gt;// The key is the interaction ID.&lt;/span&gt;
  2797. &lt;span style=&quot;color: #cc99cd;&quot;&gt;let&lt;/span&gt; &lt;span style=&quot;color: #f99157;&quot;&gt;eventLatencies&lt;/span&gt; = {};
  2798.  
  2799. &lt;span style=&quot;color: #cc99cd;&quot;&gt;const&lt;/span&gt; &lt;span style=&quot;color: #f99157;&quot;&gt;observer&lt;/span&gt; = &lt;span style=&quot;color: #6699cc;&quot;&gt;new&lt;/span&gt; &lt;span style=&quot;color: #6699cc;&quot;&gt;PerformanceObserver&lt;/span&gt;((&lt;span style=&quot;color: #f99157;&quot;&gt;list&lt;/span&gt;) =&amp;gt; {
  2800.  list.&lt;span style=&quot;color: #f2777a;&quot;&gt;getEntries&lt;/span&gt;().&lt;span style=&quot;color: #f2777a;&quot;&gt;forEach&lt;/span&gt;((&lt;span style=&quot;color: #f99157;&quot;&gt;entry&lt;/span&gt;) =&amp;gt; {
  2801.    &lt;span style=&quot;color: #cc99cd;&quot;&gt;if&lt;/span&gt; (entry.&lt;span style=&quot;color: #f99157;&quot;&gt;interactionId&lt;/span&gt; &amp;gt; 0) {
  2802.      &lt;span style=&quot;color: #cc99cd;&quot;&gt;const&lt;/span&gt; &lt;span style=&quot;color: #f99157;&quot;&gt;interactionId&lt;/span&gt; = entry.&lt;span style=&quot;color: #f99157;&quot;&gt;interactionId&lt;/span&gt;;
  2803.      &lt;span style=&quot;color: #cc99cd;&quot;&gt;if&lt;/span&gt; (!eventLatencies[interactionId]) {
  2804.        eventLatencies[interactionId] = [];
  2805.      }
  2806.      eventLatencies[interactionId].&lt;span style=&quot;color: #f2777a;&quot;&gt;push&lt;/span&gt;(entry.&lt;span style=&quot;color: #f99157;&quot;&gt;duration&lt;/span&gt;);
  2807.    }
  2808.  });
  2809. });
  2810.  
  2811. observer.&lt;span style=&quot;color: #f2777a;&quot;&gt;observe&lt;/span&gt;({ &lt;span style=&quot;color: #f99157;&quot;&gt;type&lt;/span&gt;: &lt;span style=&quot;color: #99cc99;&quot;&gt;&quot;event&quot;&lt;/span&gt;, &lt;span style=&quot;color: #f99157;&quot;&gt;buffered&lt;/span&gt;: &lt;span style=&quot;color: #cc99cd;&quot;&gt;true&lt;/span&gt; });
  2812.  
  2813. &lt;span style=&quot;color: #999;&quot;&gt;// Log events with maximum event duration for a user interaction&lt;/span&gt;
  2814. &lt;span style=&quot;color: #6699cc;&quot;&gt;Object&lt;/span&gt;.&lt;span style=&quot;color: #f2777a;&quot;&gt;entries&lt;/span&gt;(eventLatencies).&lt;span style=&quot;color: #f2777a;&quot;&gt;forEach&lt;/span&gt;(([&lt;span style=&quot;color: #f99157;&quot;&gt;k&lt;/span&gt;, &lt;span style=&quot;color: #f99157;&quot;&gt;v&lt;/span&gt;]) =&amp;gt; {
  2815.  &lt;span style=&quot;color: #6699cc;&quot;&gt;console&lt;/span&gt;.&lt;span style=&quot;color: #f2777a;&quot;&gt;log&lt;/span&gt;(&lt;span style=&quot;color: #6699cc;&quot;&gt;Math&lt;/span&gt;.&lt;span style=&quot;color: #f2777a;&quot;&gt;max&lt;/span&gt;(...v));
  2816. });
  2817. &lt;/code&gt;&lt;/pre&gt;
  2818. &lt;p&gt;If you use external tools and libraries like &lt;a href=&quot;https://github.com/GoogleChrome/web-vitals&quot;&gt;web-vitals&lt;/a&gt;, they should already collect the INP value for you.&lt;/p&gt;</description>
  2819. <pubDate>Wed, 15 Oct 2025 12:44:26 +0000</pubDate>
  2820. <dc:creator>Nazim Can Altinova</dc:creator>
  2821. </item>
  2822. <item>
  2823. <title>This Week In Rust: This Week in Rust 621</title>
  2824. <guid isPermaLink="false">tag:this-week-in-rust.org,2025-10-15:/blog/2025/10/15/this-week-in-rust-621/</guid>
  2825. <link>https://this-week-in-rust.org/blog/2025/10/15/this-week-in-rust-621/</link>
  2826. <description>&lt;p&gt;Hello and welcome to another issue of &lt;em&gt;This Week in Rust&lt;/em&gt;!
  2827. &lt;a href=&quot;https://www.rust-lang.org/&quot;&gt;Rust&lt;/a&gt; is a programming language empowering everyone to build reliable and efficient software.
  2828. This is a weekly summary of its progress and community.
  2829. Want something mentioned? Tag us at
  2830. &lt;a href=&quot;https://bsky.app/profile/thisweekinrust.bsky.social&quot;&gt;@thisweekinrust.bsky.social&lt;/a&gt; on Bluesky or
  2831. &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;@ThisWeekinRust&lt;/a&gt; on mastodon.social, or
  2832. &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;send us a pull request&lt;/a&gt;.
  2833. Want to get involved? &lt;a href=&quot;https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md&quot;&gt;We love contributions&lt;/a&gt;.&lt;/p&gt;
  2834. &lt;p&gt;&lt;em&gt;This Week in Rust&lt;/em&gt; is openly developed &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;on GitHub&lt;/a&gt; and archives can be viewed at &lt;a href=&quot;https://this-week-in-rust.org/&quot;&gt;this-week-in-rust.org&lt;/a&gt;.
  2835. If you find any errors in this week's issue, &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust/pulls&quot;&gt;please submit a PR&lt;/a&gt;.&lt;/p&gt;
  2836. &lt;p&gt;Want TWIR in your inbox? &lt;a href=&quot;https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&amp;amp;id=0ed8b72485&quot;&gt;Subscribe here&lt;/a&gt;.&lt;/p&gt;
  2837. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#updates-from-rust-community&quot;&gt;Updates from Rust Community&lt;/a&gt;&lt;/h4&gt;
  2838.  
  2839.  
  2840. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#official&quot;&gt;Official&lt;/a&gt;&lt;/h5&gt;
  2841. &lt;ul&gt;
  2842. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/inside-rust/2025/10/14/program-management-update-2025-09/&quot;&gt;Program management update — September 2025&lt;/a&gt;&lt;/li&gt;
  2843. &lt;/ul&gt;
  2844. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#foundation&quot;&gt;Foundation&lt;/a&gt;&lt;/h5&gt;
  2845. &lt;ul&gt;
  2846. &lt;li&gt;&lt;a href=&quot;https://rustfoundation.org/media/introducing-the-rust-foundations-newest-project-directors-october-2025/&quot;&gt;Rust Foundation Board Updates&lt;/a&gt;&lt;/li&gt;
  2847. &lt;/ul&gt;
  2848. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#newsletters&quot;&gt;Newsletters&lt;/a&gt;&lt;/h5&gt;
  2849. &lt;ul&gt;
  2850. &lt;li&gt;&lt;a href=&quot;https://rust-osdev.com/this-month/2025-09/&quot;&gt;This Month in Rust OSDev: September 2025&lt;/a&gt;&lt;/li&gt;
  2851. &lt;/ul&gt;
  2852. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#projecttooling-updates&quot;&gt;Project/Tooling Updates&lt;/a&gt;&lt;/h5&gt;
  2853. &lt;ul&gt;
  2854. &lt;li&gt;&lt;a href=&quot;https://lwn.net/SubscriberLink/1040197/0733825193ca1f04/&quot;&gt;Gccrs after libcore&lt;/a&gt;&lt;/li&gt;
  2855. &lt;li&gt;&lt;a href=&quot;https://lwn.net/SubscriberLink/1039374/664ea18bb8a3c1a8/&quot;&gt;A new API for interrupt-aware spinlocks&lt;/a&gt;&lt;/li&gt;
  2856. &lt;li&gt;&lt;a href=&quot;https://www.rustydonkey.dev/blog/2025.10.08_introduction_to_heave/&quot;&gt;Announcing Heave 0.1.0: an EAV data model rust library that can persist custom structs onto a SQLite DB with no friction at all!&lt;/a&gt;&lt;/li&gt;
  2857. &lt;li&gt;&lt;a href=&quot;https://www.willsearch.com.br/?page_id=19&quot;&gt;GuardianDB 0.10.15 - Introducing: the embedded iroh node&lt;/a&gt;&lt;/li&gt;
  2858. &lt;li&gt;&lt;a href=&quot;https://linebender.org/blog/tmil-21/&quot;&gt;Linebender in September 2025&lt;/a&gt;&lt;/li&gt;
  2859. &lt;li&gt;&lt;a href=&quot;https://github.com/emilk/egui/releases/tag/0.33.0&quot;&gt;egui 0.33.0 - &lt;code&gt;egui::Plugin&lt;/code&gt;, better kerning, kitdiff viewer&lt;/a&gt;&lt;/li&gt;
  2860. &lt;li&gt;&lt;a href=&quot;https://slint.dev/blog/making-slint-desktop-ready&quot;&gt;Making Slint Desktop-Ready&lt;/a&gt;&lt;/li&gt;
  2861. &lt;li&gt;&lt;a href=&quot;https://joonaa.dev/blog/09/avian-0-4&quot;&gt;Avian Physics 0.4&lt;/a&gt;&lt;/li&gt;
  2862. &lt;li&gt;&lt;a href=&quot;https://blog.antoyo.xyz/rustc_codegen_gcc-progress-report-38&quot;&gt;rustc_codegen_gcc: Progress Report #38&lt;/a&gt;&lt;/li&gt;
  2863. &lt;li&gt;&lt;a href=&quot;https://contextgeneric.dev/blog/v0-5-0-release/&quot;&gt;CGP v0.5.0 Release - Auto dispatchers, extensible datatype improvements, monadic computation, RTN emulation, modular serde, and more&lt;/a&gt;&lt;/li&gt;
  2864. &lt;li&gt;&lt;a href=&quot;https://blog.weiznich.de/blog/diesel-async-0-7/&quot;&gt;Diesel-Async 0.7&lt;/a&gt;&lt;/li&gt;
  2865. &lt;/ul&gt;
  2866. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#observationsthoughts&quot;&gt;Observations/Thoughts&lt;/a&gt;&lt;/h5&gt;
  2867. &lt;ul&gt;
  2868. &lt;li&gt;&lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2025/10/13/ergonomic-explicit-handles/&quot;&gt;We need (at least) ergonomic, explicit handles&lt;/a&gt;&lt;/li&gt;
  2869. &lt;li&gt;&lt;a href=&quot;https://www.ncameron.org/blog/to-panic-or-not-to-panic/&quot;&gt;To panic or not to panic&lt;/a&gt;&lt;/li&gt;
  2870. &lt;li&gt;&lt;a href=&quot;https://www.jessestuart.ca/posts/2025-10-10-recursive-type-state-in-rust/&quot;&gt;Recursive type state in Rust&lt;/a&gt;&lt;/li&gt;
  2871. &lt;li&gt;&lt;a href=&quot;https://tweedegolf.nl/en/blog/195/talk-about-memory-safety-at-one-conference&quot;&gt;Talk about memory safety at ONE Conference&lt;/a&gt;&lt;/li&gt;
  2872. &lt;li&gt;&lt;a href=&quot;https://www.thecodedmessage.com/posts/rust-trait-limitation/&quot;&gt;A Little Rust Trait Limitation&lt;/a&gt;&lt;/li&gt;
  2873. &lt;li&gt;&lt;a href=&quot;https://aloso.foo/blog/2025-10-10-effects/&quot;&gt;Effects in Rust (and Koka)&lt;/a&gt;&lt;/li&gt;
  2874. &lt;li&gt;[video] &lt;a href=&quot;https://www.youtube.com/playlist?list=PLilpJp3WAOvcn5_VDv3VIkQzniMWl_BfO&quot;&gt;Oxidize Conference 2025&lt;/a&gt;&lt;/li&gt;
  2875. &lt;li&gt;[video] &lt;a href=&quot;https://www.youtube.com/watch?v=nOSxuaDgl3s&quot;&gt;Rust 2025: 400K Salaries, AI, Defence &amp;amp; Borrow Checker — Jon Gjengset on Rust &amp;amp; the Future of Coding&lt;/a&gt;&lt;/li&gt;
  2876. &lt;li&gt;[audio] &lt;a href=&quot;https://netstack.fm/#episode-9&quot;&gt;Netstack.FM Episode 9 – gRPC with Lucio Franco&lt;/a&gt;&lt;/li&gt;
  2877. &lt;/ul&gt;
  2878. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-walkthroughs&quot;&gt;Rust Walkthroughs&lt;/a&gt;&lt;/h5&gt;
  2879. &lt;ul&gt;
  2880. &lt;li&gt;&lt;a href=&quot;https://kerkour.com/sqlite-extension-rust&quot;&gt;Building SQLite extensions in Rust&lt;/a&gt;&lt;/li&gt;
  2881. &lt;li&gt;&lt;a href=&quot;https://blog.0xshadow.dev/posts/backend-engineering-with-axum/axum-jwt-refresh-token/&quot;&gt;Axum Backend Series: JWT with Refresh Token&lt;/a&gt;&lt;/li&gt;
  2882. &lt;li&gt;[series] &lt;a href=&quot;https://aibodh.com/posts/bevy-rust-game-development-chapter-1/&quot;&gt;The Impatient Programmer's Guide to Bevy and Rust: Chapter 1 - Let There Be a Player&lt;/a&gt;&lt;/li&gt;
  2883. &lt;li&gt;[series] &lt;a href=&quot;https://aibodh.com/posts/bevy-rust-game-development-chapter-2/&quot;&gt;The Impatient Programmer's Guide to Bevy and Rust: Chapter 2 - Let There Be a World&lt;/a&gt;&lt;/li&gt;
  2884. &lt;li&gt;[video] &lt;a href=&quot;https://www.youtube.com/watch?v=F04kQMKwrwQ&quot;&gt;Building Embedded TUIs with Rust &amp;amp; Ratatui — Tokyo Rust Meetup 2025&lt;/a&gt;&lt;/li&gt;
  2885. &lt;li&gt;[video] &lt;a href=&quot;https://www.youtube.com/watch?v=IkCUhGAyS9U&quot;&gt;Build with Naz : Eliminate off by one errors with Rust type system design&lt;/a&gt;&lt;/li&gt;
  2886. &lt;/ul&gt;
  2887. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#research&quot;&gt;Research&lt;/a&gt;&lt;/h5&gt;
  2888. &lt;ul&gt;
  2889. &lt;li&gt;&lt;a href=&quot;https://hjaem.info/c-to-rust-papers&quot;&gt;Papers on C-to-Rust Translation&lt;/a&gt;&lt;/li&gt;
  2890. &lt;/ul&gt;
  2891. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#miscellaneous&quot;&gt;Miscellaneous&lt;/a&gt;&lt;/h5&gt;
  2892. &lt;ul&gt;
  2893. &lt;li&gt;&lt;a href=&quot;https://rustnl.org/fund/&quot;&gt;Rust Maintainers Fund - RustNL&lt;/a&gt;&lt;/li&gt;
  2894. &lt;li&gt;&lt;a href=&quot;https://github.com/MariaLetta/free-ferris-pack&quot;&gt;🦀 Pack of 50+ Free (CC0 license) Ferris illustrations with different emotions, poses and situations in PNG and SVG 🦀&lt;/a&gt;&lt;/li&gt;
  2895. &lt;/ul&gt;
  2896. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#crate-of-the-week&quot;&gt;Crate of the Week&lt;/a&gt;&lt;/h4&gt;
  2897. &lt;p&gt;This week's crate is &lt;a href=&quot;https://github.com/olson-sean-k/mitsein&quot;&gt;mitsein&lt;/a&gt;, a library of non-empty collections.&lt;/p&gt;
  2898. &lt;p&gt;Thanks to &lt;a href=&quot;https://users.rust-lang.org/t/crate-of-the-week/2704/1481&quot;&gt;Nik Revenco&lt;/a&gt; for the suggestion!&lt;/p&gt;
  2899. &lt;p&gt;&lt;a href=&quot;https://users.rust-lang.org/t/crate-of-the-week/2704&quot;&gt;Please submit your suggestions and votes for next week&lt;/a&gt;!&lt;/p&gt;
  2900. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#calls-for-testing&quot;&gt;Calls for Testing&lt;/a&gt;&lt;/h4&gt;
  2901. &lt;p&gt;An important step for RFC implementation is for people to experiment with the
  2902. implementation and give feedback, especially before stabilization.&lt;/p&gt;
  2903. &lt;p&gt;If you are a feature implementer and would like your RFC to appear in this list, add a
  2904. &lt;code&gt;call-for-testing&lt;/code&gt; label to your RFC along with a comment providing testing instructions and/or
  2905. guidance on which aspect(s) of the feature need testing.&lt;/p&gt;
  2906. &lt;ul&gt;
  2907. &lt;li&gt;&lt;em&gt;No calls for testing were issued this week by
  2908.  &lt;a href=&quot;https://github.com/rust-lang/rust/labels/call-for-testing&quot;&gt;Rust&lt;/a&gt;,
  2909.  &lt;a href=&quot;https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing&quot;&gt;Rust language RFCs&lt;/a&gt;,
  2910.  &lt;a href=&quot;https://github.com/rust-lang/cargo/labels/call-for-testing&quot;&gt;Cargo&lt;/a&gt; or
  2911.  &lt;a href=&quot;https://github.com/rust-lang/rustup/labels/call-for-testing&quot;&gt;Rustup&lt;/a&gt;.&lt;/em&gt;&lt;/li&gt;
  2912. &lt;/ul&gt;
  2913. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust/issues&quot;&gt;Let us know&lt;/a&gt; if you would like your feature to be tracked as a part of this list.&lt;/p&gt;
  2914. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers&quot;&gt;Call for Participation; projects and speakers&lt;/a&gt;&lt;/h4&gt;
  2915. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cfp-projects&quot;&gt;CFP - Projects&lt;/a&gt;&lt;/h5&gt;
  2916. &lt;p&gt;Always wanted to contribute to open-source projects but did not know where to start?
  2917. Every week we highlight some tasks from the Rust community for you to pick and get started!&lt;/p&gt;
  2918. &lt;p&gt;Some of these tasks may also have mentors available, visit the task page for more information.&lt;/p&gt;
  2919.  
  2920.  
  2921.  
  2922.  
  2923. &lt;ul&gt;
  2924. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/discussions/4805&quot;&gt;Diesel - View Support - Show me your view definitions&lt;/a&gt;&lt;/li&gt;
  2925. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/issues/4760&quot;&gt;Diesel - Add &lt;code&gt;#[diagnostic::do_not_recommend]&lt;/code&gt; to &lt;code&gt;impl AsExpression for T: Expression&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2926. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/issues/4764&quot;&gt;Diesel - Improve documentation for Postgres loading modes&lt;/a&gt;&lt;/li&gt;
  2927. &lt;/ul&gt;
  2928. &lt;p&gt;If you are a Rust project owner and are looking for contributors, please submit tasks &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines&quot;&gt;here&lt;/a&gt; or through a &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;PR to TWiR&lt;/a&gt; or by reaching out on &lt;a href=&quot;https://x.com/ThisWeekInRust&quot;&gt;X (formerly Twitter)&lt;/a&gt; or &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;Mastodon&lt;/a&gt;!&lt;/p&gt;
  2929. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cfp-events&quot;&gt;CFP - Events&lt;/a&gt;&lt;/h5&gt;
  2930. &lt;p&gt;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.&lt;/p&gt;
  2931.  
  2932.  
  2933.  
  2934. &lt;ul&gt;
  2935. &lt;li&gt;&lt;a href=&quot;https://tokio.rs/blog/2025-09-26-announcing-tokio-conf-cfp&quot;&gt;&lt;strong&gt;TokioConf 2026&lt;/strong&gt;&lt;/a&gt; | CFP closes 2025-12-08 | Portland, Oregon, USA | 2026-04-20&lt;/li&gt;
  2936. &lt;/ul&gt;
  2937. &lt;p&gt;If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;PR to TWiR&lt;/a&gt; or by reaching out on &lt;a href=&quot;https://x.com/ThisWeekInRust&quot;&gt;X (formerly Twitter)&lt;/a&gt; or &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;Mastodon&lt;/a&gt;!&lt;/p&gt;
  2938. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#updates-from-the-rust-project&quot;&gt;Updates from the Rust Project&lt;/a&gt;&lt;/h4&gt;
  2939. &lt;p&gt;420 pull requests were &lt;a href=&quot;https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2025-10-07..2025-10-14&quot;&gt;merged in the last week&lt;/a&gt;&lt;/p&gt;
  2940. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#compiler&quot;&gt;Compiler&lt;/a&gt;&lt;/h6&gt;
  2941. &lt;ul&gt;
  2942. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147205&quot;&gt;add a new &lt;code&gt;wasm32-wasip3&lt;/code&gt; target to Rust&lt;/a&gt;&lt;/li&gt;
  2943. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146869&quot;&gt;Global Variable Naming: evaluate constants lazily&lt;/a&gt;&lt;/li&gt;
  2944. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147423&quot;&gt;&lt;code&gt;DepNodeColor&lt;/code&gt; tweaks&lt;/a&gt;&lt;/li&gt;
  2945. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147483&quot;&gt;perform InstSimplify before ReferencePropagation&lt;/a&gt;&lt;/li&gt;
  2946. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147477&quot;&gt;refactor AddCallGuards in two loops&lt;/a&gt;&lt;/li&gt;
  2947. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147502&quot;&gt;split &lt;code&gt;overlapping_{inherent,trait}_impls&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2948. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145513&quot;&gt;validate &lt;code&gt;CopyForDeref&lt;/code&gt; and &lt;code&gt;DerefTemps&lt;/code&gt; better and remove them from runtime MIR&lt;/a&gt;&lt;/li&gt;
  2949. &lt;/ul&gt;
  2950. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#library&quot;&gt;Library&lt;/a&gt;&lt;/h6&gt;
  2951. &lt;ul&gt;
  2952. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147124&quot;&gt;move more code to &lt;code&gt;RawVec::finish_grow&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2953. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146568&quot;&gt;port the implemention of SIMD intrinsics from Miri to const-eval&lt;/a&gt;&lt;/li&gt;
  2954. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147457&quot;&gt;specialize &lt;code&gt;slice::fill&lt;/code&gt; to use memset when possible&lt;/a&gt;&lt;/li&gt;
  2955. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147562&quot;&gt;stabilize &lt;code&gt;NonZero&amp;lt;u*&amp;gt;::div_ceil&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2956. &lt;/ul&gt;
  2957. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cargo&quot;&gt;Cargo&lt;/a&gt;&lt;/h6&gt;
  2958. &lt;ul&gt;
  2959. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/15947&quot;&gt;Reorganize build-dir layout&lt;/a&gt;&lt;/li&gt;
  2960. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16063&quot;&gt;add: Report a missing source error for workspace dependencies&lt;/a&gt;&lt;/li&gt;
  2961. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16064&quot;&gt;script: Default bin.name to package.name&lt;/a&gt;&lt;/li&gt;
  2962. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16087&quot;&gt;script: Store cargo script lockfiles in build-dir&lt;/a&gt;&lt;/li&gt;
  2963. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16081&quot;&gt;tree: Switch from &lt;code&gt;--depth public&lt;/code&gt; to &lt;code&gt;--edges public&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2964. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16082&quot;&gt;allow to rustfix &lt;code&gt;unused_variables&lt;/code&gt; lint&lt;/a&gt;&lt;/li&gt;
  2965. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16075&quot;&gt;fix regression that swallowed json diagnostic explanations&lt;/a&gt;&lt;/li&gt;
  2966. &lt;/ul&gt;
  2967. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rustdoc&quot;&gt;Rustdoc&lt;/a&gt;&lt;/h6&gt;
  2968. &lt;ul&gt;
  2969. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147402&quot;&gt;rustdoc: Don't serialize &amp;amp; deserialize data that doesn't go over the wire&lt;/a&gt;&lt;/li&gt;
  2970. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147443&quot;&gt;rustdoc: a small performance improvement: only allocate new string if there are DOS backlines in highlight.rs&lt;/a&gt;&lt;/li&gt;
  2971. &lt;/ul&gt;
  2972. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#clippy&quot;&gt;Clippy&lt;/a&gt;&lt;/h6&gt;
  2973. &lt;ul&gt;
  2974. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15843&quot;&gt;&lt;code&gt;multiple_inherent_impl&lt;/code&gt;: Add config option to target specific scope&lt;/a&gt;&lt;/li&gt;
  2975. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15826&quot;&gt;&lt;code&gt;zero_repeat_side_effects&lt;/code&gt;: don't suggest unnecessary braces around stmts&lt;/a&gt;&lt;/li&gt;
  2976. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15740&quot;&gt;&lt;code&gt;clone_on_ref_ptr&lt;/code&gt;: only name the generic type if possible&lt;/a&gt;&lt;/li&gt;
  2977. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15608&quot;&gt;&lt;code&gt;collapsible_match&lt;/code&gt;: exclude binding modes from &lt;code&gt;struct&lt;/code&gt; field pattern suggestions&lt;/a&gt;&lt;/li&gt;
  2978. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15815&quot;&gt;&lt;code&gt;zero_repeat_side_effects&lt;/code&gt;: don't suggest unsuggestable types&lt;/a&gt;&lt;/li&gt;
  2979. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15816&quot;&gt;&lt;code&gt;legacy_numeric_constants&lt;/code&gt;: add ctxt check for internal macro&lt;/a&gt;&lt;/li&gt;
  2980. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15812&quot;&gt;&lt;code&gt;manual_unwrap_or&lt;/code&gt;: fix false positive edge case&lt;/a&gt;&lt;/li&gt;
  2981. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15847&quot;&gt;&lt;code&gt;get_unwrap&lt;/code&gt;: avoid calling &lt;code&gt;is_type_diagnostic_item&lt;/code&gt; multiple times&lt;/a&gt;&lt;/li&gt;
  2982. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/14953&quot;&gt;add &lt;code&gt;replace_box&lt;/code&gt; lint&lt;/a&gt;&lt;/li&gt;
  2983. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/14662&quot;&gt;add lint &lt;code&gt;unnecessary_option_map_or_else&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2984. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15566&quot;&gt;check structs and enums for &lt;code&gt;use_self&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2985. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15547&quot;&gt;fix &lt;code&gt;needless_continue&lt;/code&gt; false positive when match type is not unit or never&lt;/a&gt;&lt;/li&gt;
  2986. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15849&quot;&gt;honor &lt;code&gt;allow&lt;/code&gt;/&lt;code&gt;expect&lt;/code&gt; attributes on ADT and &lt;code&gt;impl Clone&lt;/code&gt; nodes&lt;/a&gt;&lt;/li&gt;
  2987. &lt;/ul&gt;
  2988. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-analyzer&quot;&gt;Rust-Analyzer&lt;/a&gt;&lt;/h6&gt;
  2989. &lt;ul&gt;
  2990. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/19771&quot;&gt;add ide-assist: generate blanket trait impl&lt;/a&gt;&lt;/li&gt;
  2991. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20812&quot;&gt;add self param completions for trait assoc fn&lt;/a&gt;&lt;/li&gt;
  2992. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20804&quot;&gt;build rust-analyzer with &lt;code&gt;--target&lt;/code&gt; for install/pgo xtask&lt;/a&gt;&lt;/li&gt;
  2993. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20526&quot;&gt;fix .let completion not working for let-chain&lt;/a&gt;&lt;/li&gt;
  2994. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20816&quot;&gt;fix closure coerced return type for &lt;code&gt;add_return_type&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2995. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20824&quot;&gt;fix empty closure completion analysis&lt;/a&gt;&lt;/li&gt;
  2996. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20788&quot;&gt;fix not applicable c-str and byte-str for &lt;code&gt;raw_string&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2997. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20817&quot;&gt;fix not applicable on param in let-stmt for &lt;code&gt;add_explicit_type&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2998. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20805&quot;&gt;improve parsing error for &lt;code&gt;static&lt;/code&gt; and &lt;code&gt;const&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  2999. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20803&quot;&gt;replace &lt;code&gt;--show-output&lt;/code&gt; task defaults with &lt;code&gt;--nocapture&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  3000. &lt;/ul&gt;
  3001. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage&quot;&gt;Rust Compiler Performance Triage&lt;/a&gt;&lt;/h5&gt;
  3002. &lt;p&gt;This week saw small wins across the board from some microoptimizations of the incremental query
  3003. system (&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147423&quot;&gt;#147423&lt;/a&gt;). There have also been a couple of
  3004. regressions. &lt;a href=&quot;https://github.com/rust-lang/rust/pull/142390&quot;&gt;#142390&lt;/a&gt; introduced regressions of &lt;code&gt;check&lt;/code&gt;
  3005. builds across the board. The largest regression (18%) is from an incremental opt build of a secondary
  3006. artificial stress test, so we deemed it acceptable.&lt;/p&gt;
  3007. &lt;p&gt;Triage done by &lt;strong&gt;@kobzol&lt;/strong&gt;.&lt;/p&gt;
  3008. &lt;p&gt;Revision range: &lt;a href=&quot;https://perf.rust-lang.org/?start=1a3cdd34629306fa67624eaa60d73687e7fcf855&amp;amp;end=956f47c32f1bd97b22cd702d7ccf78f0f0d42c34&amp;amp;absolute=false&amp;amp;stat=instructions%3Au&quot;&gt;1a3cdd34..956f47c3&lt;/a&gt;&lt;/p&gt;
  3009. &lt;p&gt;&lt;strong&gt;Summary&lt;/strong&gt;:&lt;/p&gt;
  3010. &lt;table&gt;
  3011. &lt;thead&gt;
  3012. &lt;tr&gt;
  3013. &lt;th align=&quot;center&quot;&gt;(instructions:u)&lt;/th&gt;
  3014. &lt;th align=&quot;center&quot;&gt;mean&lt;/th&gt;
  3015. &lt;th align=&quot;center&quot;&gt;range&lt;/th&gt;
  3016. &lt;th align=&quot;center&quot;&gt;count&lt;/th&gt;
  3017. &lt;/tr&gt;
  3018. &lt;/thead&gt;
  3019. &lt;tbody&gt;
  3020. &lt;tr&gt;
  3021. &lt;td align=&quot;center&quot;&gt;Regressions ❌ &lt;br /&gt; (primary)&lt;/td&gt;
  3022. &lt;td align=&quot;center&quot;&gt;0.7%&lt;/td&gt;
  3023. &lt;td align=&quot;center&quot;&gt;[0.1%, 2.0%]&lt;/td&gt;
  3024. &lt;td align=&quot;center&quot;&gt;65&lt;/td&gt;
  3025. &lt;/tr&gt;
  3026. &lt;tr&gt;
  3027. &lt;td align=&quot;center&quot;&gt;Regressions ❌ &lt;br /&gt; (secondary)&lt;/td&gt;
  3028. &lt;td align=&quot;center&quot;&gt;0.8%&lt;/td&gt;
  3029. &lt;td align=&quot;center&quot;&gt;[0.1%, 18.6%]&lt;/td&gt;
  3030. &lt;td align=&quot;center&quot;&gt;65&lt;/td&gt;
  3031. &lt;/tr&gt;
  3032. &lt;tr&gt;
  3033. &lt;td align=&quot;center&quot;&gt;Improvements ✅ &lt;br /&gt; (primary)&lt;/td&gt;
  3034. &lt;td align=&quot;center&quot;&gt;-0.6%&lt;/td&gt;
  3035. &lt;td align=&quot;center&quot;&gt;[-1.6%, -0.1%]&lt;/td&gt;
  3036. &lt;td align=&quot;center&quot;&gt;119&lt;/td&gt;
  3037. &lt;/tr&gt;
  3038. &lt;tr&gt;
  3039. &lt;td align=&quot;center&quot;&gt;Improvements ✅ &lt;br /&gt; (secondary)&lt;/td&gt;
  3040. &lt;td align=&quot;center&quot;&gt;-0.4%&lt;/td&gt;
  3041. &lt;td align=&quot;center&quot;&gt;[-1.6%, -0.1%]&lt;/td&gt;
  3042. &lt;td align=&quot;center&quot;&gt;76&lt;/td&gt;
  3043. &lt;/tr&gt;
  3044. &lt;tr&gt;
  3045. &lt;td align=&quot;center&quot;&gt;All ❌✅ (primary)&lt;/td&gt;
  3046. &lt;td align=&quot;center&quot;&gt;-0.1%&lt;/td&gt;
  3047. &lt;td align=&quot;center&quot;&gt;[-1.6%, 2.0%]&lt;/td&gt;
  3048. &lt;td align=&quot;center&quot;&gt;184&lt;/td&gt;
  3049. &lt;/tr&gt;
  3050. &lt;/tbody&gt;
  3051. &lt;/table&gt;
  3052. &lt;p&gt;2 Regressions, 7 Improvements, 3 Mixed; 3 of them in rollups
  3053. 35 artifact comparisons made in total&lt;/p&gt;
  3054. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/rustc-perf/blob/b4b30e719c7083141669f79edfdf20e685cf918f/triage/2025/2025-10-13.md&quot;&gt;Full report here&lt;/a&gt;.&lt;/p&gt;
  3055. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#approved-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/commits/master&quot;&gt;Approved RFCs&lt;/a&gt;&lt;/h5&gt;
  3056. &lt;p&gt;Changes to Rust follow the Rust &lt;a href=&quot;https://github.com/rust-lang/rfcs#rust-rfcs&quot;&gt;RFC (request for comments) process&lt;/a&gt;. These
  3057. are the RFCs that were approved for implementation this week:&lt;/p&gt;
  3058. &lt;ul&gt;
  3059. &lt;li&gt;&lt;em&gt;No RFCs were approved this week.&lt;/em&gt;&lt;/li&gt;
  3060. &lt;/ul&gt;
  3061. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#final-comment-period&quot;&gt;Final Comment Period&lt;/a&gt;&lt;/h5&gt;
  3062. &lt;p&gt;Every week, &lt;a href=&quot;https://www.rust-lang.org/team.html&quot;&gt;the team&lt;/a&gt; announces the 'final comment period' for RFCs and key PRs
  3063. which are reaching a decision. Express your opinions now.&lt;/p&gt;
  3064. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#tracking-issues-prs&quot;&gt;Tracking Issues &amp;amp; PRs&lt;/a&gt;&lt;/h6&gt;
  3065. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Rust&lt;/a&gt;
  3066. &lt;ul&gt;
  3067. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147258&quot;&gt;iter repeat: panic on last&lt;/a&gt;&lt;/li&gt;
  3068. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/146939&quot;&gt;Tracking Issue (take 2) for &lt;code&gt;more_float_constants&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  3069. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146098&quot;&gt;Temporary lifetime extension for blocks&lt;/a&gt;&lt;/li&gt;
  3070. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/140463&quot;&gt;Document MaybeUninit bit validity&lt;/a&gt;&lt;/li&gt;
  3071. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147382&quot;&gt;unused_must_use: Don't warn on &lt;code&gt;Result&amp;lt;(), Uninhabited&amp;gt;&lt;/code&gt; or &lt;code&gt;ControlFlow&amp;lt;Uninhabited, ()&amp;gt;&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  3072. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146961&quot;&gt;Allow passing &lt;code&gt;expr&lt;/code&gt; metavariable to &lt;code&gt;cfg&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  3073. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147022&quot;&gt;Remove current code for embedding command-line args in PDB&lt;/a&gt;&lt;/li&gt;
  3074. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146725&quot;&gt;&lt;code&gt;-Znext-solver&lt;/code&gt; instantiate predicate binder without recanonicalizing goal&lt;/a&gt;&lt;/li&gt;
  3075. &lt;/ul&gt;
  3076. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cargo_1&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Cargo&lt;/a&gt;
  3077. &lt;ul&gt;
  3078. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/issues/7614&quot;&gt;Should build-plans be deleted?&lt;/a&gt;&lt;/li&gt;
  3079. &lt;/ul&gt;
  3080. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/labels/final-comment-period&quot;&gt;Rust RFCs&lt;/a&gt;
  3081. &lt;ul&gt;
  3082. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3848&quot;&gt;Pass pointers to &lt;code&gt;const&lt;/code&gt; in assembly&lt;/a&gt;&lt;/li&gt;
  3083. &lt;/ul&gt;
  3084. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#leadership-council&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period&quot;&gt;Leadership Council&lt;/a&gt;
  3085. &lt;ul&gt;
  3086. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/leadership-council/issues/232&quot;&gt;Delegate GSoC money spending to the t-mentorship team&lt;/a&gt;&lt;/li&gt;
  3087. &lt;/ul&gt;
  3088. &lt;p&gt;&lt;em&gt;No Items entered Final Comment Period this week for
  3089.  &lt;a href=&quot;https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+&quot;&gt;Language Team&lt;/a&gt;,
  3090.  &lt;a href=&quot;https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Language Reference&lt;/a&gt; or
  3091.  &lt;a href=&quot;https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Unsafe Code Guidelines&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
  3092. &lt;p&gt;Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.&lt;/p&gt;
  3093. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#new-and-updated-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/pulls&quot;&gt;New and Updated RFCs&lt;/a&gt;&lt;/h6&gt;
  3094. &lt;ul&gt;
  3095. &lt;li&gt;&lt;em&gt;No New or Updated RFCs were created this week.&lt;/em&gt;&lt;/li&gt;
  3096. &lt;/ul&gt;
  3097. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#upcoming-events&quot;&gt;Upcoming Events&lt;/a&gt;&lt;/h4&gt;
  3098. &lt;p&gt;Rusty Events between 2025-10-15 - 2025-11-12 🦀&lt;/p&gt;
  3099. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#virtual&quot;&gt;Virtual&lt;/a&gt;&lt;/h5&gt;
  3100. &lt;ul&gt;
  3101. &lt;li&gt;2025-10-15 | Hybrid (Vancouver, BC, CA) | &lt;a href=&quot;https://www.meetup.com/vancouver-rust&quot;&gt;Vancouver Rust&lt;/a&gt;&lt;ul&gt;
  3102. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/vancouver-rust/events/307731034/&quot;&gt;&lt;strong&gt;indielinks&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3103. &lt;/ul&gt;
  3104. &lt;/li&gt;
  3105. &lt;li&gt;2025-10-16 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  3106. &lt;li&gt;&lt;a href=&quot;https://luma.com/o8fh3fh7&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3107. &lt;/ul&gt;
  3108. &lt;/li&gt;
  3109. &lt;li&gt;2025-10-16 | Virtual (Nürnberg, DE) | &lt;a href=&quot;https://www.meetup.com/rust-noris&quot;&gt;Rust Nuremberg&lt;/a&gt;&lt;ul&gt;
  3110. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-noris/events/306046668/&quot;&gt;&lt;strong&gt;Rust Nürnberg online&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3111. &lt;/ul&gt;
  3112. &lt;/li&gt;
  3113. &lt;li&gt;2025-10-18 | Virtual (Gdansk/Kraków/Wroclaw, PL) | &lt;a href=&quot;https://www.meetup.com/stacja-it-trojmiasto/&quot;&gt;Stacja IT Trójmiasto&lt;/a&gt;&lt;ul&gt;
  3114. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/stacja-it-trojmiasto/events/310935164/&quot;&gt;&lt;strong&gt;[BEZPŁATNIE] Programowanie w języku Rust&lt;/strong&gt;&lt;/a&gt; | &lt;a href=&quot;https://www.meetup.com/stacja-it-krakow/events/310935157/&quot;&gt;Kraków Mirror&lt;/a&gt; | &lt;a href=&quot;https://www.meetup.com/stacja-it-wroclaw/events/310935159/&quot;&gt;Wroclaw Mirror&lt;/a&gt;&lt;/li&gt;
  3115. &lt;/ul&gt;
  3116. &lt;/li&gt;
  3117. &lt;li&gt;2025-10-19 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  3118. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109167/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3119. &lt;/ul&gt;
  3120. &lt;/li&gt;
  3121. &lt;li&gt;2025-10-21 | Virtual (London, UK) | &lt;a href=&quot;https://www.meetup.com/women-in-rust&quot;&gt;Women in Rust&lt;/a&gt;&lt;ul&gt;
  3122. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/women-in-rust/events/311068625/&quot;&gt;&lt;strong&gt;👋 Community Catch Up&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3123. &lt;/ul&gt;
  3124. &lt;/li&gt;
  3125. &lt;li&gt;2025-10-21 | Virtual (Washington, DC, US) | &lt;a href=&quot;https://www.meetup.com/rustdc&quot;&gt;Rust DC&lt;/a&gt;&lt;ul&gt;
  3126. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rustdc/events/310002307/&quot;&gt;&lt;strong&gt;Mid-month Rustful&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3127. &lt;/ul&gt;
  3128. &lt;/li&gt;
  3129. &lt;li&gt;2025-10-22 | Virtual (Boulder, CO, US) | &lt;a href=&quot;https://www.meetup.com/boulder-elixir/events/&quot;&gt;Boulder Elixir&lt;/a&gt;&lt;ul&gt;
  3130. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/boulder-elixir/events/310996627/&quot;&gt;&lt;strong&gt;Integrating Elixir and Apache DataFusion with Rustler&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3131. &lt;/ul&gt;
  3132. &lt;/li&gt;
  3133. &lt;li&gt;2025-10-22 | Virtual (Buenos Aires, AR) | &lt;a href=&quot;https://www.meetup.com/es-ES/net-baires/&quot;&gt;[Net-Baires] Comunidad de .NET en Buenos Aires&lt;/a&gt;&lt;ul&gt;
  3134. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/es-ES/net-baires/events/311365783/&quot;&gt;&lt;strong&gt;Rust para devs .NET | Community Standup #10&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3135. &lt;/ul&gt;
  3136. &lt;/li&gt;
  3137. &lt;li&gt;2025-10-23 | Hybrid (Seattle/Bellevue, WA, US) | &lt;a href=&quot;https://www.meetup.com/join-srug&quot;&gt;Seattle Rust User Group&lt;/a&gt;&lt;ul&gt;
  3138. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/seattle-rust-user-group/events/311351020/&quot;&gt;&lt;strong&gt;October, 2025 SRUG (Seattle Rust User Group) Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3139. &lt;/ul&gt;
  3140. &lt;/li&gt;
  3141. &lt;li&gt;2025-10-23 | Virtual (Berlin, DE) | &lt;a href=&quot;https://www.meetup.com/rust-berlin&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  3142. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/306046641/&quot;&gt;&lt;strong&gt;Rust Hack and Learn&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3143. &lt;/ul&gt;
  3144. &lt;/li&gt;
  3145. &lt;li&gt;2025-10-23 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  3146. &lt;li&gt;&lt;a href=&quot;https://luma.com/zyc3touy&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3147. &lt;/ul&gt;
  3148. &lt;/li&gt;
  3149. &lt;li&gt;2025-10-26 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  3150. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109171/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3151. &lt;/ul&gt;
  3152. &lt;/li&gt;
  3153. &lt;li&gt;2025-10-28 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  3154. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/305361444/&quot;&gt;&lt;strong&gt;Fourth Tuesday&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3155. &lt;/ul&gt;
  3156. &lt;/li&gt;
  3157. &lt;li&gt;2025-10-30 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  3158. &lt;li&gt;&lt;a href=&quot;https://luma.com/t8yovmmm&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3159. &lt;/ul&gt;
  3160. &lt;/li&gt;
  3161. &lt;li&gt;2025-11-01 | Virtual (Kampala, UG) | &lt;a href=&quot;https://www.eventbrite.com/o/rust-circle-kampala-65249289033&quot;&gt;Rust Circle Meetup&lt;/a&gt;&lt;ul&gt;
  3162. &lt;li&gt;&lt;a href=&quot;https://www.eventbrite.com/e/rust-circle-meetup-tickets-628763868657&quot;&gt;&lt;strong&gt;Rust Circle Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3163. &lt;/ul&gt;
  3164. &lt;/li&gt;
  3165. &lt;li&gt;2025-11-02 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  3166. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109173/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3167. &lt;/ul&gt;
  3168. &lt;/li&gt;
  3169. &lt;li&gt;2025-11-05 | Virtual (Buffalo, NY, US) | &lt;a href=&quot;https://www.meetup.com/buffalo-rust-meetup&quot;&gt;Buffalo Rust Meetup&lt;/a&gt;&lt;ul&gt;
  3170. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/buffalo-rust-meetup/events/305304242/&quot;&gt;&lt;strong&gt;Buffalo Rust User Group&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3171. &lt;/ul&gt;
  3172. &lt;/li&gt;
  3173. &lt;li&gt;2025-11-05 | Virtual (Indianapolis, IN, US) | &lt;a href=&quot;https://www.meetup.com/indyrs&quot;&gt;Indy Rust&lt;/a&gt;&lt;ul&gt;
  3174. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/indyrs/events/wqzhftyhcpbhb/&quot;&gt;&lt;strong&gt;Indy.rs - with Social Distancing&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3175. &lt;/ul&gt;
  3176. &lt;/li&gt;
  3177. &lt;li&gt;2025-11-06 | Virtual (Berlin, DE) | &lt;a href=&quot;https://www.meetup.com/rust-berlin/events/&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  3178. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/305646021/&quot;&gt;&lt;strong&gt;Rust Hack and Learn&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3179. &lt;/ul&gt;
  3180. &lt;/li&gt;
  3181. &lt;li&gt;2025-11-06 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  3182. &lt;li&gt;&lt;a href=&quot;https://luma.com/xkd84gfz&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3183. &lt;/ul&gt;
  3184. &lt;/li&gt;
  3185. &lt;li&gt;2025-11-09 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust/events/&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  3186. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109175/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3187. &lt;/ul&gt;
  3188. &lt;/li&gt;
  3189. &lt;li&gt;2025-11-11 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust/events/&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  3190. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/305361536/&quot;&gt;&lt;strong&gt;Second Tuesday&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3191. &lt;/ul&gt;
  3192. &lt;/li&gt;
  3193. &lt;li&gt;2025-11-11 | Virtual (London, GB) | &lt;a href=&quot;https://www.meetup.com/women-in-rust/events/&quot;&gt;Women in Rust&lt;/a&gt;&lt;ul&gt;
  3194. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/women-in-rust/events/311068632/&quot;&gt;&lt;strong&gt;👋 Community Catch Up&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3195. &lt;/ul&gt;
  3196. &lt;/li&gt;
  3197. &lt;/ul&gt;
  3198. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#asia&quot;&gt;Asia&lt;/a&gt;&lt;/h5&gt;
  3199. &lt;ul&gt;
  3200. &lt;li&gt;2025-10-20 | Tel Aviv-yafo, IL | &lt;a href=&quot;https://www.meetup.com/rust-tlv&quot;&gt;Rust 🦀 TLV&lt;/a&gt;&lt;ul&gt;
  3201. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-tlv/events/310628902/&quot;&gt;&lt;strong&gt;In person Rust October 2025 at AWS in Tel Aviv&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3202. &lt;/ul&gt;
  3203. &lt;/li&gt;
  3204. &lt;/ul&gt;
  3205. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#europe&quot;&gt;Europe&lt;/a&gt;&lt;/h5&gt;
  3206. &lt;ul&gt;
  3207. &lt;li&gt;2025-10-21 | Aarhus, DK | &lt;a href=&quot;https://www.meetup.com/rust-aarhus&quot;&gt;Rust Aarhus&lt;/a&gt;&lt;ul&gt;
  3208. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-aarhus/events/311035141/&quot;&gt;&lt;strong&gt;Hack Night&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3209. &lt;/ul&gt;
  3210. &lt;/li&gt;
  3211. &lt;li&gt;2025-10-21 | Bergen, NO | &lt;a href=&quot;https://www.meetup.com/bergen-rust-new-technology/events/&quot;&gt;Rust Bergen&lt;/a&gt;&lt;ul&gt;
  3212. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bergen-rust-new-technology/events/311153821/&quot;&gt;&lt;strong&gt;Rust Meetup #01 @ Zrch&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3213. &lt;/ul&gt;
  3214. &lt;/li&gt;
  3215. &lt;li&gt;2025-10-21 | Leipzig, DE | &lt;a href=&quot;https://www.meetup.com/rust-modern-systems-programming-in-leipzig&quot;&gt;Rust - Modern Systems Programming in Leipzig&lt;/a&gt;&lt;ul&gt;
  3216. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/308592252/&quot;&gt;&lt;strong&gt;Topic TBD&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3217. &lt;/ul&gt;
  3218. &lt;/li&gt;
  3219. &lt;li&gt;2025-10-21 | London, UK | &lt;a href=&quot;https://www.meetup.com/london-rust-project-group&quot;&gt;London Rust Project Group&lt;/a&gt;&lt;ul&gt;
  3220. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/london-rust-project-group/events/310813952/&quot;&gt;&lt;strong&gt;Rust in Surgery: Powering the Data Pipelines&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3221. &lt;/ul&gt;
  3222. &lt;/li&gt;
  3223. &lt;li&gt;2025-10-23 | Edinburgh, UK | &lt;a href=&quot;https://www.meetup.com/rust-edi/events/&quot;&gt;Rust and Friends&lt;/a&gt;&lt;ul&gt;
  3224. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-and-friends/events/311501254/&quot;&gt;&lt;strong&gt;Rust and Friends (evening pub)&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3225. &lt;/ul&gt;
  3226. &lt;/li&gt;
  3227. &lt;li&gt;2025-10-24 | Edinburgh, UK | &lt;a href=&quot;https://www.meetup.com/rust-edi/events/&quot;&gt;Rust and Friends&lt;/a&gt;&lt;ul&gt;
  3228. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-and-friends/events/311501249/&quot;&gt;&lt;strong&gt;Rust and Friends (daytime coffee)&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3229. &lt;/ul&gt;
  3230. &lt;/li&gt;
  3231. &lt;li&gt;2025-10-28 | Manchester, UK | &lt;a href=&quot;https://www.meetup.com/rust-manchester&quot;&gt;Rust Manchester&lt;/a&gt;&lt;ul&gt;
  3232. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-manchester/events/307919171/&quot;&gt;&lt;strong&gt;Rust Manchester October Code Night&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3233. &lt;/ul&gt;
  3234. &lt;/li&gt;
  3235. &lt;li&gt;2025-10-29 | Dortmund, DE | &lt;a href=&quot;https://www.meetup.com/rust-dortmund/events/&quot;&gt;Rust Dortmund&lt;/a&gt;&lt;ul&gt;
  3236. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-dortmund/events/311251545/&quot;&gt;&lt;strong&gt;Rust Dortmund Meetup October 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3237. &lt;/ul&gt;
  3238. &lt;/li&gt;
  3239. &lt;li&gt;2025-10-30 | Copenhagen, DK | &lt;a href=&quot;https://www.meetup.com/copenhagen-rust-community&quot;&gt;Copenhagen Rust Community&lt;/a&gt;&lt;ul&gt;
  3240. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/copenhagen-rust-community/events/311405044/&quot;&gt;&lt;strong&gt;Rust meetup #62 sponsored by Google!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3241. &lt;/ul&gt;
  3242. &lt;/li&gt;
  3243. &lt;li&gt;2025-10-30 | Prague, CZ | &lt;a href=&quot;https://www.meetup.com/rust-prague&quot;&gt;Rust Prague&lt;/a&gt;&lt;ul&gt;
  3244. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-prague/events/310967094/&quot;&gt;&lt;strong&gt;Rust Meetup Prague (October 2025)&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3245. &lt;/ul&gt;
  3246. &lt;/li&gt;
  3247. &lt;li&gt;2025-11-02 - 2025-11-04 | Florence, IT | &lt;a href=&quot;https://rustlab.it/&quot;&gt;Rustlab 2025&lt;/a&gt;&lt;ul&gt;
  3248. &lt;li&gt;&lt;a href=&quot;https://rustlab.it/&quot;&gt;&lt;strong&gt;Rustlab 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3249. &lt;/ul&gt;
  3250. &lt;/li&gt;
  3251. &lt;li&gt;2025-11-04 | Manchester, UK | &lt;a href=&quot;https://www.meetup.com/rust-manchester&quot;&gt;Rust Manchester&lt;/a&gt;&lt;ul&gt;
  3252. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-manchester/events/310921632/&quot;&gt;&lt;strong&gt;Rust Manchester November Talk&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3253. &lt;/ul&gt;
  3254. &lt;/li&gt;
  3255. &lt;li&gt;2025-11-05 | Girona, ES | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  3256. &lt;li&gt;&lt;a href=&quot;https://luma.com/xl8ob0tn&quot;&gt;&lt;strong&gt;Rust Girona Hack &amp;amp; Learn 11 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3257. &lt;/ul&gt;
  3258. &lt;/li&gt;
  3259. &lt;li&gt;2025-11-05 | Oslo, NO | &lt;a href=&quot;https://www.meetup.com/rust-oslo&quot;&gt;Rust Oslo&lt;/a&gt;&lt;ul&gt;
  3260. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-oslo/events/310601872/&quot;&gt;&lt;strong&gt;Rust Hack'n'Learn at Kampen Bistro&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3261. &lt;/ul&gt;
  3262. &lt;/li&gt;
  3263. &lt;li&gt;2025-11-05 | Oxford, UK | &lt;a href=&quot;https://www.meetup.com/oxford-rust-meetup-group&quot;&gt;Oxford ACCU/Rust Meetup.&lt;/a&gt;&lt;ul&gt;
  3264. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/oxford-rust-meetup-group/events/nnrkttyhcpbhb/&quot;&gt;&lt;strong&gt;Rust/ACCU meetup.&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3265. &lt;/ul&gt;
  3266. &lt;/li&gt;
  3267. &lt;li&gt;2025-11-06 | Gdansk, PL | &lt;a href=&quot;https://www.meetup.com/rust-gdansk/events/&quot;&gt;Rust Gdansk&lt;/a&gt;&lt;ul&gt;
  3268. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-gdansk/events/310924266/&quot;&gt;&lt;strong&gt;Rust Gdansk Meetup #11&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3269. &lt;/ul&gt;
  3270. &lt;/li&gt;
  3271. &lt;li&gt;2025-11-12 | Reading, UK | &lt;a href=&quot;https://www.meetup.com/reading-rust-workshop/events/&quot;&gt;Reading Rust Workshop&lt;/a&gt;&lt;ul&gt;
  3272. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/reading-rust-workshop/events/308944050/&quot;&gt;&lt;strong&gt;Reading Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3273. &lt;/ul&gt;
  3274. &lt;/li&gt;
  3275. &lt;/ul&gt;
  3276. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#north-america&quot;&gt;North America&lt;/a&gt;&lt;/h5&gt;
  3277. &lt;ul&gt;
  3278. &lt;li&gt;2025-10-15 | Hybrid (Vancouver, BC, CA) | &lt;a href=&quot;https://www.meetup.com/vancouver-rust&quot;&gt;Vancouver Rust&lt;/a&gt;&lt;ul&gt;
  3279. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/vancouver-rust/events/307731034/&quot;&gt;&lt;strong&gt;indielinks&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3280. &lt;/ul&gt;
  3281. &lt;/li&gt;
  3282. &lt;li&gt;2025-10-16 | Mountain View, CA, US | &lt;a href=&quot;https://www.meetup.com/hackerdojo/events/&quot;&gt;Hacker Dojo&lt;/a&gt;&lt;ul&gt;
  3283. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/hackerdojo/events/311012947/&quot;&gt;&lt;strong&gt;RUST MEETUP at HACKER DOJO&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3284. &lt;/ul&gt;
  3285. &lt;/li&gt;
  3286. &lt;li&gt;2025-10-16 | San Francisco, CA, US | &lt;a href=&quot;https://luma.com/calendar/cal-Cnmn4RR2n4fRUNZ&quot;&gt;Svix&lt;/a&gt;&lt;ul&gt;
  3287. &lt;li&gt;&lt;a href=&quot;https://luma.com/tp6w7tc9&quot;&gt;&lt;strong&gt;San Francisco Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3288. &lt;/ul&gt;
  3289. &lt;/li&gt;
  3290. &lt;li&gt;2025-10-21 | San Francisco, CA, US | &lt;a href=&quot;https://luma.com/events-by-vara-gear&quot;&gt;Vara &amp;amp; Gear&lt;/a&gt;&lt;ul&gt;
  3291. &lt;li&gt;&lt;a href=&quot;https://luma.com/kbs2os1c&quot;&gt;&lt;strong&gt;Rust Workshop by Vara Network&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3292. &lt;/ul&gt;
  3293. &lt;/li&gt;
  3294. &lt;li&gt;2025-10-21 | San Francisco, CA, US | &lt;a href=&quot;https://www.meetup.com/san-francisco-rust-study-group&quot;&gt;San Francisco Rust Study Group&lt;/a&gt;&lt;ul&gt;
  3295. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/san-francisco-rust-study-group/events/308284343/&quot;&gt;&lt;strong&gt;Rust Hacking in Person&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3296. &lt;/ul&gt;
  3297. &lt;/li&gt;
  3298. &lt;li&gt;2025-10-22 | Austin, TX, US | &lt;a href=&quot;https://www.meetup.com/rust-atx&quot;&gt;Rust ATX&lt;/a&gt;&lt;ul&gt;
  3299. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-atx/events/310457307/&quot;&gt;&lt;strong&gt;Rust Lunch - Fareground&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3300. &lt;/ul&gt;
  3301. &lt;/li&gt;
  3302. &lt;li&gt;2025-10-23 | Hybrid (Seattle/Bellevue, WA, US) | &lt;a href=&quot;https://www.meetup.com/join-srug&quot;&gt;Seattle Rust User Group&lt;/a&gt;&lt;ul&gt;
  3303. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/seattle-rust-user-group/events/311351020/&quot;&gt;&lt;strong&gt;October, 2025 SRUG (Seattle Rust User Group) Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3304. &lt;/ul&gt;
  3305. &lt;/li&gt;
  3306. &lt;li&gt;2025-10-23 | Nashville, TN, US | &lt;a href=&quot;https://www.meetup.com/music-city-rust-developers&quot;&gt;Music City Rust Developers&lt;/a&gt;&lt;ul&gt;
  3307. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/music-city-rust-developers/events/304333267/&quot;&gt;&lt;strong&gt;Year In Review&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3308. &lt;/ul&gt;
  3309. &lt;/li&gt;
  3310. &lt;li&gt;2025-10-23 | Spokane, WA, US | &lt;a href=&quot;https://www.meetup.com/spokane-rust&quot;&gt;Spokane Rust&lt;/a&gt;&lt;ul&gt;
  3311. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/spokane-rust/events/311346444/&quot;&gt;&lt;strong&gt;October Rust Meetup: A Special Presentation and Monthly Meetups are Back!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3312. &lt;/ul&gt;
  3313. &lt;/li&gt;
  3314. &lt;li&gt;2025-10-25 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  3315. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/310983712/&quot;&gt;&lt;strong&gt;Porter Square Rust Lunch, Oct 25&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3316. &lt;/ul&gt;
  3317. &lt;/li&gt;
  3318. &lt;li&gt;2025-10-29 | New York, NY, US | &lt;a href=&quot;https://www.meetup.com/rust-nyc/events/&quot;&gt;Rust NYC&lt;/a&gt;&lt;ul&gt;
  3319. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-nyc/events/311541108/&quot;&gt;&lt;strong&gt;Rust NYC: Scalable static analysis: confronting the halting problem&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3320. &lt;/ul&gt;
  3321. &lt;/li&gt;
  3322. &lt;li&gt;2025-10-30 | Atlanta, GA, US | &lt;a href=&quot;https://www.meetup.com/rust-atl&quot;&gt;Rust Atlanta&lt;/a&gt;&lt;ul&gt;
  3323. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-atl/events/308675988/&quot;&gt;&lt;strong&gt;Rust-Atl&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3324. &lt;/ul&gt;
  3325. &lt;/li&gt;
  3326. &lt;li&gt;2025-10-30 | Mountain View, CA, US | &lt;a href=&quot;https://www.meetup.com/hackerdojo/events/&quot;&gt;Hacker Dojo&lt;/a&gt;&lt;ul&gt;
  3327. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/hackerdojo/events/311273832/&quot;&gt;&lt;strong&gt;RUST MEETUP at HACKER DOJO&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3328. &lt;/ul&gt;
  3329. &lt;/li&gt;
  3330. &lt;li&gt;2025-11-01 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  3331. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/311039492/&quot;&gt;&lt;strong&gt;Chinatown Rust Lunch, Nov 1&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3332. &lt;/ul&gt;
  3333. &lt;/li&gt;
  3334. &lt;li&gt;2025-11-06 | Saint Louis, MO, US | &lt;a href=&quot;https://www.meetup.com/stl-rust/events/&quot;&gt;STL Rust&lt;/a&gt;&lt;ul&gt;
  3335. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/stl-rust/events/307251982/&quot;&gt;&lt;strong&gt;SIUE students on wasm 3D animations&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3336. &lt;/ul&gt;
  3337. &lt;/li&gt;
  3338. &lt;li&gt;2025-11-08 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust/events/&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  3339. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/311039501/&quot;&gt;&lt;strong&gt;Winter Hill Rust Lunch, Nov 8&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3340. &lt;/ul&gt;
  3341. &lt;/li&gt;
  3342. &lt;/ul&gt;
  3343. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#oceania&quot;&gt;Oceania&lt;/a&gt;&lt;/h5&gt;
  3344. &lt;ul&gt;
  3345. &lt;li&gt;2025-10-22 | Perth, AU | &lt;a href=&quot;https://www.meetup.com/perth-rust-meetup-group&quot;&gt;Rust Perth Meetup Group&lt;/a&gt;&lt;ul&gt;
  3346. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/perth-rust-meetup-group/events/310847099/&quot;&gt;&lt;strong&gt;October Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3347. &lt;/ul&gt;
  3348. &lt;/li&gt;
  3349. &lt;li&gt;2025-10-28 | Barton, AU | &lt;a href=&quot;https://www.meetup.com/rust-canberra&quot;&gt;Canberra Rust User Group&lt;/a&gt;&lt;ul&gt;
  3350. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-canberra/events/311234237/&quot;&gt;&lt;strong&gt;October Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3351. &lt;/ul&gt;
  3352. &lt;/li&gt;
  3353. &lt;/ul&gt;
  3354. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#south-america&quot;&gt;South America&lt;/a&gt;&lt;/h5&gt;
  3355. &lt;ul&gt;
  3356. &lt;li&gt;2025-10-22 | Montevideo, UY | &lt;a href=&quot;https://www.meetup.com/rust-uruguay/events/&quot;&gt;Rust Meetup Uruguay&lt;/a&gt;&lt;ul&gt;
  3357. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-uruguay/events/311475675/&quot;&gt;&lt;strong&gt;Rust Uruguay meetup de Octubre&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3358. &lt;/ul&gt;
  3359. &lt;/li&gt;
  3360. &lt;li&gt;2025-10-25 | São Paulo, BR | &lt;a href=&quot;https://www.meetup.com/rust-sao-paulo-meetup&quot;&gt;Rust São Paulo Meetup&lt;/a&gt;&lt;ul&gt;
  3361. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-sao-paulo-meetup/events/311084440/&quot;&gt;&lt;strong&gt;Encontro do Rust-SP na Amazon Web Services&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3362. &lt;/ul&gt;
  3363. &lt;/li&gt;
  3364. &lt;li&gt;2025-10-30 | Florianopolis, BR | &lt;a href=&quot;https://luma.com/calendar/cal-iOloL5ZqswCO5Mm&quot;&gt;Rust Brasil&lt;/a&gt;&lt;ul&gt;
  3365. &lt;li&gt;&lt;a href=&quot;https://luma.com/lky7an18&quot;&gt;&lt;strong&gt;Rust Floripa&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  3366. &lt;/ul&gt;
  3367. &lt;/li&gt;
  3368. &lt;/ul&gt;
  3369. &lt;p&gt;If you are running a Rust event please add it to the &lt;a href=&quot;https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com&quot;&gt;calendar&lt;/a&gt; to get
  3370. it mentioned here. Please remember to add a link to the event too.
  3371. Email the &lt;a href=&quot;mailto:community-team@rust-lang.org&quot;&gt;Rust Community Team&lt;/a&gt; for access.&lt;/p&gt;
  3372. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#jobs&quot;&gt;Jobs&lt;/a&gt;&lt;/h4&gt;
  3373.  
  3374.  
  3375. &lt;p&gt;Please see the latest &lt;a href=&quot;https://www.reddit.com/r/rust/comments/1nknaii/official_rrust_whos_hiring_thread_for_jobseekers/&quot;&gt;Who's Hiring thread on r/rust&lt;/a&gt;&lt;/p&gt;
  3376. &lt;h3&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#quote-of-the-week&quot;&gt;Quote of the Week&lt;/a&gt;&lt;/h3&gt;
  3377. &lt;blockquote&gt;
  3378. &lt;p&gt;Pointers are quite hard.&lt;/p&gt;
  3379. &lt;/blockquote&gt;
  3380. &lt;p&gt;– Tim McNamara&lt;/p&gt;
  3381. &lt;blockquote&gt;
  3382. &lt;p&gt;And, as the name implies, pointy.&lt;/p&gt;
  3383. &lt;/blockquote&gt;
  3384. &lt;p&gt;– &lt;a href=&quot;https://www.linkedin.com/feed/update/urn:li:activity:7381109081857724416?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7381109081857724416%2C7381113605926166528%29&amp;amp;dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287381113605926166528%2Curn%3Ali%3Aactivity%3A7381109081857724416%29&quot;&gt;llogiq on LinkedIn&lt;/a&gt;&lt;/p&gt;
  3385. &lt;p&gt;Thanks to &lt;a href=&quot;https://users.rust-lang.org/t/twir-quote-of-the-week/328/1721&quot;&gt;llogiq&lt;/a&gt; for the self-suggestion!&lt;/p&gt;
  3386. &lt;p&gt;&lt;a href=&quot;https://users.rust-lang.org/t/twir-quote-of-the-week/328&quot;&gt;Please submit quotes and vote for next week!&lt;/a&gt;&lt;/p&gt;
  3387. &lt;p&gt;&lt;em&gt;This Week in Rust is edited by: &lt;a href=&quot;https://github.com/nellshamrell&quot;&gt;nellshamrell&lt;/a&gt;, &lt;a href=&quot;https://github.com/llogiq&quot;&gt;llogiq&lt;/a&gt;, &lt;a href=&quot;https://github.com/cdmistman&quot;&gt;cdmistman&lt;/a&gt;, &lt;a href=&quot;https://github.com/ericseppanen&quot;&gt;ericseppanen&lt;/a&gt;, &lt;a href=&quot;https://github.com/extrawurst&quot;&gt;extrawurst&lt;/a&gt;, &lt;a href=&quot;https://github.com/U007D&quot;&gt;U007D&lt;/a&gt;, &lt;a href=&quot;https://github.com/joelmarcey&quot;&gt;joelmarcey&lt;/a&gt;, &lt;a href=&quot;https://github.com/mariannegoldin&quot;&gt;mariannegoldin&lt;/a&gt;, &lt;a href=&quot;https://github.com/bennyvasquez&quot;&gt;bennyvasquez&lt;/a&gt;, &lt;a href=&quot;https://github.com/bdillo&quot;&gt;bdillo&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  3388. &lt;p&gt;&lt;em&gt;Email list hosting is sponsored by &lt;a href=&quot;https://foundation.rust-lang.org/&quot;&gt;The Rust Foundation&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  3389. &lt;p&gt;&lt;small&gt;&lt;a href=&quot;https://www.reddit.com/r/rust/comments/1o7upmn/this_week_in_rust_621/&quot;&gt;Discuss on r/rust&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;</description>
  3390. <pubDate>Wed, 15 Oct 2025 04:00:00 +0000</pubDate>
  3391. <dc:creator>TWiR Contributors</dc:creator>
  3392. </item>
  3393. <item>
  3394. <title>The Rust Programming Language Blog: Announcing the New Rust Project Directors</title>
  3395. <guid isPermaLink="true">https://blog.rust-lang.org/2025/10/15/announcing-the-new-rust-project-directors-2025/</guid>
  3396. <link>https://blog.rust-lang.org/2025/10/15/announcing-the-new-rust-project-directors-2025/</link>
  3397. <description>&lt;p&gt;We are happy to announce that we have completed the annual process to elect new Project Directors.&lt;/p&gt;
  3398. &lt;p&gt;The new Project Directors are:&lt;/p&gt;
  3399. &lt;ul&gt;
  3400. &lt;li&gt;&lt;a href=&quot;https://github.com/davidtwco/&quot;&gt;David Wood&lt;/a&gt;&lt;/li&gt;
  3401. &lt;li&gt;&lt;a href=&quot;https://github.com/jackh726/&quot;&gt;Jack Huey&lt;/a&gt;&lt;/li&gt;
  3402. &lt;li&gt;&lt;a href=&quot;https://github.com/nikomatsakis/&quot;&gt;Niko Matsakis&lt;/a&gt;&lt;/li&gt;
  3403. &lt;/ul&gt;
  3404. &lt;p&gt;They will join &lt;a href=&quot;https://github.com/rylev&quot;&gt;Ryan Levick&lt;/a&gt; and &lt;a href=&quot;https://github.com/carols10cents&quot;&gt;Carol Nichols&lt;/a&gt; to make up the five members of the Rust Foundation Board of Directors who represent the Rust Project.&lt;/p&gt;
  3405. &lt;p&gt;We would also like to thank the outgoing going Project Directors for contributions and service:&lt;/p&gt;
  3406. &lt;ul&gt;
  3407. &lt;li&gt;&lt;a href=&quot;https://github.com/JakobDegen&quot;&gt;Jakob Degen&lt;/a&gt;&lt;/li&gt;
  3408. &lt;li&gt;&lt;a href=&quot;https://github.com/spastorino&quot;&gt;Santiago Pastorino&lt;/a&gt;&lt;/li&gt;
  3409. &lt;li&gt;&lt;a href=&quot;https://github.com/scottmcm&quot;&gt;Scott McMurray&lt;/a&gt;&lt;/li&gt;
  3410. &lt;/ul&gt;
  3411. &lt;p&gt;The board is made up of Project Directors, who come from and represent the Rust Project, and Member Directors, who represent the corporate members of the Rust Foundation. Both of these director groups have equal voting power.&lt;/p&gt;
  3412. &lt;p&gt;We look forward to working with and being represented by this new group of project directors.&lt;/p&gt;
  3413. &lt;p&gt;We were fortunate to have a number of excellent candidates and this was a difficult decision. We wish to express our gratitude to all of the candidates who were considered for this role! We also extend our thanks to the project as a whole who participated by nominating candidates and providing additional feedback once the nominees were published.&lt;/p&gt;
  3414. &lt;p&gt;Finally, we want to share our appreciation for &lt;a href=&quot;https://github.com/tomassedovic&quot;&gt;Tomas Sedovic&lt;/a&gt; for facilitating the election process. An overview of the election process can be found in a previous blog post &lt;a href=&quot;https://blog.rust-lang.org/2023/08/30/electing-new-project-directors/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
  3415. <pubDate>Wed, 15 Oct 2025 00:00:00 +0000</pubDate>
  3416. <dc:creator>Leadership Council</dc:creator>
  3417. </item>
  3418. <item>
  3419. <title>Firefox Developer Experience: Firefox WebDriver Newsletter 144</title>
  3420. <guid isPermaLink="false">https://fxdx.dev/?p=515</guid>
  3421. <link>https://fxdx.dev/firefox-webdriver-newsletter-144/</link>
  3422. <description>&lt;p&gt;W&lt;em&gt;ebDriver is a remote control interface that enables introspection and control of user agents.&lt;/em&gt; &lt;em&gt;As such it&lt;/em&gt; &lt;em&gt;can&lt;/em&gt; &lt;em&gt;help developers to verify that their websites are working and performing well with all major browsers. The protocol is standardized by the&lt;/em&gt;&lt;a href=&quot;https://www.w3.org/&quot;&gt;&lt;em&gt; W3C&lt;/em&gt;&lt;/a&gt;&lt;em&gt; and consists of two separate specifications:&lt;/em&gt;&lt;a href=&quot;https://w3c.github.io/webdriver/&quot;&gt;&lt;em&gt; WebDriver classic&lt;/em&gt;&lt;/a&gt;&lt;em&gt; (HTTP) and the new&lt;/em&gt;&lt;a href=&quot;https://w3c.github.io/webdriver-bidi/&quot;&gt;&lt;em&gt; WebDriver BiDi&lt;/em&gt;&lt;/a&gt;&lt;em&gt; (Bi-Directional).&lt;/em&gt;&lt;/p&gt;
  3423.  
  3424.  
  3425.  
  3426. &lt;p&gt;&lt;em&gt;This newsletter gives an overview of the work we’ve done as part of the Firefox 144 release cycle&lt;/em&gt;.&lt;/p&gt;
  3427.  
  3428.  
  3429.  
  3430. &lt;h3&gt;Contributions&lt;/h3&gt;
  3431.  
  3432.  
  3433.  
  3434. &lt;p&gt;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.&lt;/p&gt;
  3435.  
  3436.  
  3437.  
  3438. &lt;p&gt;WebDriver code is written in JavaScript, Python, and Rust so any web developer can contribute! Read&lt;a href=&quot;https://firefox-source-docs.mozilla.org/devtools/getting-started/README.html&quot;&gt; how to setup the work environment&lt;/a&gt; and check&lt;a href=&quot;https://codetribute.mozilla.org/projects/automation&quot;&gt; the list of mentored issues&lt;/a&gt; for Marionette, or the&lt;a href=&quot;https://codetribute.mozilla.org/languages/javascript?project%3DWebDriver%2520BiDi&quot;&gt; list of mentored JavaScript bugs for WebDriver BiDi&lt;/a&gt;. Join&lt;a href=&quot;https://chat.mozilla.org/#/room/#webdriver:mozilla.org&quot;&gt; our chatroom&lt;/a&gt; if you need any help to get started!&lt;/p&gt;
  3439.  
  3440.  
  3441.  
  3442. &lt;h3&gt;WebDriver BiDi&lt;/h3&gt;
  3443.  
  3444.  
  3445.  
  3446. &lt;ul&gt;
  3447. &lt;li&gt;Implemented the new &lt;a href=&quot;https://bugzil.la/1874365&quot;&gt;&lt;code&gt;browsingContext.downloadWillBegin&lt;/code&gt; event&lt;/a&gt;, which is emitted when a new download is initiated, either by clicking a link with the &lt;code&gt;download&lt;/code&gt; attribute, or in response to a network request with a &lt;code&gt;Content-Disposition&lt;/code&gt; header indicating a file attachment.&lt;/li&gt;
  3448.  
  3449.  
  3450.  
  3451. &lt;li&gt;Implemented the new &lt;a href=&quot;https://bugzil.la/1974167&quot;&gt;&lt;code&gt;emulation.setScreenOrientationOverride&lt;/code&gt; command&lt;/a&gt;, which allows clients to emulate different screen orientations. This command is not limited to mobile devices, but also works for desktop applications.&lt;/li&gt;
  3452.  
  3453.  
  3454.  
  3455. &lt;li&gt;Implemented the new &lt;a href=&quot;https://bugzil.la/1978027&quot;&gt;&lt;code&gt;emulation.setTimezoneOverride&lt;/code&gt; command&lt;/a&gt;, which allows clients to simulate a specific timezone setting.&lt;/li&gt;
  3456.  
  3457.  
  3458.  
  3459. &lt;li&gt;Enhanced the &lt;a href=&quot;https://bugzil.la/1983807&quot;&gt;&lt;code&gt;emulation.setLocaleOverride&lt;/code&gt; command&lt;/a&gt; to also apply the specified settings to sandboxes previously created via WebDriver BiDi.&lt;/li&gt;
  3460.  
  3461.  
  3462.  
  3463. &lt;li&gt;Fixed a bug where &lt;a href=&quot;https://bugzil.la/1980211&quot;&gt;the locale override set via &lt;code&gt;emulation.setLocaleOverride&lt;/code&gt; was sometimes incorrectly shared between different browsing contexts within the same process&lt;/a&gt;.&lt;/li&gt;
  3464.  
  3465.  
  3466.  
  3467. &lt;li&gt;&lt;a href=&quot;https://bugzil.la/1914407&quot;&gt;Enhanced the &lt;code&gt;browsingContext.navigate&lt;/code&gt; command to avoid &lt;code&gt;NS_BINDING_ABORTED&lt;/code&gt; errors&lt;/a&gt; caused by redirects or interruptions occurring after the navigation was already committed.&lt;/li&gt;
  3468. &lt;/ul&gt;
  3469.  
  3470.  
  3471.  
  3472. &lt;h3&gt;Marionette&lt;/h3&gt;
  3473.  
  3474.  
  3475.  
  3476. &lt;ul&gt;
  3477. &lt;li&gt;&lt;a href=&quot;https://bugzil.la/1986238&quot;&gt;Reverted the &lt;code&gt;Scroll Into View&lt;/code&gt; WebDriver algorithm as used by several WebDriver classic commands in Marionette to always use the &lt;code&gt;instant&lt;/code&gt; scroll behavior&lt;/a&gt;. This undoes the change introduced in Firefox 97, which had switched the behavior to &lt;code&gt;auto&lt;/code&gt;. The reversion addresses potential race conditions when scrolling elements that use &lt;code&gt;smooth&lt;/code&gt; behavior.&lt;/li&gt;
  3478. &lt;/ul&gt;</description>
  3479. <pubDate>Tue, 14 Oct 2025 13:25:20 +0000</pubDate>
  3480. <dc:creator>Henrik Skupin</dc:creator>
  3481. </item>
  3482. <item>
  3483. <title>The Mozilla Blog: Choose how you search and stay organized with Firefox</title>
  3484. <guid isPermaLink="false">https://blog.mozilla.org/?p=82237</guid>
  3485. <link>https://blog.mozilla.org/en/firefox/firefox-144/</link>
  3486. <description>&lt;figure class=&quot;wp-block-image size-large is-style-default&quot;&gt;&lt;img alt=&quot;llustration showing Firefox’s browser interface with a focus on search options. A bar labeled “Use visual search” overlaps an image of a floral painting, while another option labeled “with the Perplexity icon” appears below it. A small browser window shows a cropped view of the same artwork. The Firefox toolbar is visible at the bottom with a highlighted smiley face icon. The background is a gradient of purple and blue with grid lines and sparkles, conveying a playful, tech-inspired design.&quot; class=&quot;wp-image-82258&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/Firefox-ProfileManagement-1920x1080-Static-v1.3-Dark2-1024x576.png&quot; width=&quot;1024&quot; /&gt;&lt;/figure&gt;
  3487.  
  3488.  
  3489.  
  3490. &lt;p&gt;At Mozilla, we build Firefox around one principle: putting you in control. With today’s release, we’re introducing new features that make browsing smarter and more personal while staying true to the values you care about most: privacy and choice.&lt;/p&gt;
  3491.  
  3492.  
  3493.  
  3494. &lt;h3&gt;&lt;strong&gt;A new option for search, still on your terms.&lt;/strong&gt;&lt;/h3&gt;
  3495.  
  3496.  
  3497.  
  3498. &lt;p&gt;Earlier this year, we gave you more choice in how you search by &lt;a href=&quot;https://connect.mozilla.org/t5/discussions/try-out-perplexity-ai-search-in-firefox-139/m-p/98352&quot;&gt;testing&lt;/a&gt; &lt;a href=&quot;https://www.perplexity.ai/&quot;&gt;Perplexity&lt;/a&gt;, an AI-powered answer engine, as a search option on Firefox. Now, after positive feedback, we’re making it a fixture, rolling it out to more users for desktop. Perplexity provides conversational answers with citations, so you can validate information without digging through pages of results.&lt;/p&gt;
  3499.  
  3500.  
  3501.  
  3502. &lt;p&gt;This addition reflects our shared commitment to choice: You decide when to use an AI answer engine, or if you want to use it at all. Available globally, Perplexity can be found in the unified search button in the address bar. We’ll be bringing Perplexity to mobile in the coming months. And as always, privacy matters – &lt;a href=&quot;https://www.perplexity.ai/hub/legal/privacy-policy&quot;&gt;Perplexity&lt;/a&gt; maintains strict prohibitions against selling or sharing personal data.&lt;/p&gt;
  3503.  
  3504.  
  3505.  
  3506. &lt;h3&gt;&lt;strong&gt;Organize your life with profiles&lt;/strong&gt;&lt;/h3&gt;
  3507.  
  3508.  
  3509.  
  3510. &lt;p class=&quot;has-text-align-left&quot;&gt;At the beginning of the year, we started &lt;a href=&quot;https://connect.mozilla.org/t5/discussions/try-out-firefox-profiles-in-nightly/m-p/84223&quot;&gt;testing&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/en/firefox/profile-management/&quot;&gt;profiles&lt;/a&gt; — a way to create and switch between different browsing setups. After months of gradual rollout and &lt;a href=&quot;https://blog.mozilla.org/en/firefox/shifting-left-for-better-accessibility/&quot;&gt;community feedback&lt;/a&gt;, profiles are now &lt;a href=&quot;https://blog.mozilla.org/en/firefox/profile-management/&quot;&gt;available&lt;/a&gt; to everyone.&lt;/p&gt;
  3511.  
  3512.  
  3513. &lt;div class=&quot;wp-block-image is-style-default&quot;&gt;
  3514. &lt;figure class=&quot;aligncenter size-large is-resized&quot;&gt;&lt;img alt=&quot;Firefox Profiles feature shown with an illustration of three foxes and a setup screen for creating and customizing browser profiles.&quot; class=&quot;wp-image-82095&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/firefox-profiles-1024x576.png&quot; style=&quot;width: 675px;&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;&lt;em&gt;Create and switch between different browsing setups&lt;/em&gt;&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;&lt;/div&gt;
  3515.  
  3516.  
  3517. &lt;p&gt;Profiles let you keep work tabs distinct from personal browsing, or dedicate a setup to testing extensions or managing a specific project. Each profile runs independently, giving you flexibility and focus. Feedback from students, professionals and contributors helped us refine this feature into the version you see today.&lt;/p&gt;
  3518.  
  3519.  
  3520.  
  3521. &lt;h3&gt;&lt;strong&gt;Discover more with visual search&lt;/strong&gt;&lt;/h3&gt;
  3522.  
  3523.  
  3524.  
  3525. &lt;p&gt;In September, we &lt;a href=&quot;https://connect.mozilla.org/t5/discussions/new-in-firefox-desktop-only-visual-search/m-p/106216&quot;&gt;announced&lt;/a&gt; visual search on &lt;a href=&quot;https://connect.mozilla.org/&quot;&gt;Mozilla Connect&lt;/a&gt; and began rolling it out for testing. Powered by Google Lens, it lets you search what you see with a simple right-click on any image.&lt;/p&gt;
  3526.  
  3527.  
  3528. &lt;div class=&quot;wp-block-image&quot;&gt;
  3529. &lt;figure class=&quot;aligncenter size-full&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-82248&quot; height=&quot;396&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/image.png&quot; width=&quot;464&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;&lt;em&gt;Search what you see with a simple right-click on an image&lt;/em&gt;&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;&lt;/div&gt;
  3530.  
  3531.  
  3532. &lt;p&gt;You can:&lt;/p&gt;
  3533.  
  3534.  
  3535.  
  3536. &lt;ul&gt;
  3537. &lt;li&gt;Find similar products, places or objects &lt;/li&gt;
  3538.  
  3539.  
  3540.  
  3541. &lt;li&gt;Copy, translate or search text from images&lt;/li&gt;
  3542.  
  3543.  
  3544.  
  3545. &lt;li&gt;Get inspiration for learning, travel or research&lt;/li&gt;
  3546. &lt;/ul&gt;
  3547.  
  3548.  
  3549.  
  3550. &lt;p&gt;This desktop-only feature makes searching more intuitive and curiosity-driven. For now, it requires Google as your default search engine. Tell us what you think. Your feedback will guide where visual search appears next, from the address bar to mobile.&lt;/p&gt;
  3551.  
  3552.  
  3553.  
  3554. &lt;h3&gt;&lt;strong&gt;Evolving to meet your needs&lt;/strong&gt;&lt;/h3&gt;
  3555.  
  3556.  
  3557.  
  3558. &lt;p&gt;Today’s release brings more ways to browse on your terms — from smarter search with Perplexity, to profiles that let you separate work from play, to visual search.&lt;/p&gt;
  3559.  
  3560.  
  3561.  
  3562. &lt;p&gt;Each of these features reflects what matters most to us: putting you in control of your online experience and building alongside the community that inspires Firefox. With your feedback, we’ll keep shaping a browser that not only keeps pace with the future of the web but also stays true to the open values you trust.&lt;/p&gt;
  3563.  
  3564.  
  3565.  
  3566. &lt;p&gt;We’re excited to see how you use what’s new, and can’t wait to share what’s next.&lt;/p&gt;
  3567.  
  3568.  
  3569.  
  3570. &lt;a class=&quot;ft-c-inline-cta&quot; href=&quot;https://www.mozilla.org/firefox/new/?utm_source=blog.mozilla.org&amp;amp;utm_medium=referral&amp;amp;utm_campaign=blog-nav&quot;&gt;
  3571.  &lt;div class=&quot;ft-c-inline-cta__media&quot;&gt;
  3572.  &lt;img alt=&quot;&quot; class=&quot;attachment-1x1 size-1x1&quot; height=&quot;800&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2021/10/Visual-Guidelines-800x800.png&quot; width=&quot;800&quot; /&gt;  &lt;/div&gt;
  3573.  &lt;div class=&quot;ft-c-inline-cta__content&quot;&gt;
  3574.     &lt;h4&gt;Take control of your internet&lt;/h4&gt;      &lt;span&gt;Download Firefox&lt;/span&gt;   &lt;/div&gt;
  3575. &lt;/a&gt;
  3576. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/firefox/firefox-144/&quot;&gt;Choose how you search and stay organized with Firefox&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  3577. <pubDate>Tue, 14 Oct 2025 13:00:00 +0000</pubDate>
  3578. <dc:creator>Jenifer Boscacci</dc:creator>
  3579. </item>
  3580. <item>
  3581. <title>Niko Matsakis: We need (at least) ergonomic, explicit handles</title>
  3582. <guid isPermaLink="false">https://smallcultfollowing.com/babysteps/blog/2025/10/13/ergonomic-explicit-handles/</guid>
  3583. <link>https://smallcultfollowing.com/babysteps/blog/2025/10/13/ergonomic-explicit-handles/?utm_source=atom_feed</link>
  3584. <description>&lt;p&gt;Continuing my discussion on Ergonomic RC, I want to focus on the core question: &lt;strong&gt;should users have to explicitly invoke handle/clone, or not?&lt;/strong&gt; This whole “Ergonomic RC” work was originally proposed by &lt;a href=&quot;https://dioxuslabs.com/&quot;&gt;Dioxus&lt;/a&gt; and their answer is simple: &lt;strong&gt;definitely not&lt;/strong&gt;. For the kind of high-level GUI applications they are building, having to call &lt;code&gt;cx.handle()&lt;/code&gt; to clone a ref-counted value is pure noise. For that matter, for a lot of Rust apps, even cloning a string or a vector is no big deal. On the other hand, for a lot of applications, the answer is &lt;strong&gt;definitely yes&lt;/strong&gt; – knowing where handles are created can impact performance, memory usage, and even correctness (don’t worry, I’ll give examples later in the post). So how do we reconcile this?&lt;/p&gt;
  3585. &lt;p&gt;&lt;strong&gt;This blog argues that we should make it ergonomic to be explicit&lt;/strong&gt;. This wasn’t always my position, but after an impactful conversation with Josh Triplett, I’ve come around. I think it aligns with what I once called the &lt;a href=&quot;https://smallcultfollowing.com/babysteps//blog/2022/09/18/dyn-async-traits-part-8-the-soul-of-rust/&quot;&gt;soul of Rust&lt;/a&gt;: we want to be ergonomic, yes, but we want to be &lt;strong&gt;ergonomic while giving control&lt;/strong&gt;&lt;sup id=&quot;fnref:1&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:1&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
  3586. &lt;p&gt;I like Tyler Mandry’s &lt;a href=&quot;https://tmandry.gitlab.io/blog/posts/the-main-thing/&quot;&gt;&lt;em&gt;Clarity of purpose&lt;/em&gt;&lt;/a&gt; contruction, &lt;em&gt;“Great code brings only the important characteristics of your application to your attention”&lt;/em&gt;. The key point is that &lt;em&gt;there is great code in which cloning and handles are important characteristics&lt;/em&gt;, so we need to make that code possible to express nicely. This is particularly true since Rust is one of the very few languages that really targets that kind of low-level, foundational code.&lt;/p&gt;
  3587. &lt;p&gt;&lt;strong&gt;This does not mean we cannot (later) support automatic clones and handles.&lt;/strong&gt; It’s inarguable that this would benefit clarity of purpose for a lot of Rust code. But I think we should focus &lt;em&gt;first&lt;/em&gt; on the harder case, the case where explicitness is needed, and &lt;strong&gt;get that as nice as we can&lt;/strong&gt;; then we can circle back and decide whether to also support something automatic. One of the questions for me, in fact, is whether we can get “fully explicit” to be &lt;em&gt;nice enough&lt;/em&gt; that we don’t really need the automatic version. There are benefits from having “one Rust”, where all code follows roughly the same patterns, where those patterns are perfect some of the time, and don’t suck too bad&lt;sup id=&quot;fnref:2&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:2&quot;&gt;2&lt;/a&gt;&lt;/sup&gt; when they’re overkill.&lt;/p&gt;
  3588. &lt;h3&gt;“Rust should not surprise you.” (hat tip: Josh Triplett)&lt;/h3&gt;
  3589. &lt;p&gt;I mentioned this blog post resulted from a long conversation with Josh Triplett&lt;sup id=&quot;fnref:3&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:3&quot;&gt;3&lt;/a&gt;&lt;/sup&gt;. The key phrase that stuck with me from that conversation was: &lt;em&gt;Rust should not surprise you&lt;/em&gt;. The way I think of it is like this. Every programmer knows what its like to have a marathon debugging session – to sit and state at code for days and think, &lt;em&gt;but… how is this even POSSIBLE?&lt;/em&gt; Those kind of bug hunts can end in a few different ways. Occasionally you uncover a deeply satisfying, subtle bug in your logic. More often, you find that you wrote &lt;code&gt;if foo&lt;/code&gt; and not &lt;code&gt;if !foo&lt;/code&gt;. And &lt;em&gt;occasionally&lt;/em&gt; you find out that your language was doing something that you didn’t expect. That some simple-looking code concealed a subltle, complex interaction. People often call this kind of a &lt;em&gt;footgun&lt;/em&gt;.&lt;/p&gt;
  3590. &lt;p&gt;Overall, Rust is &lt;em&gt;remarkably&lt;/em&gt; good at avoiding footguns&lt;sup id=&quot;fnref:4&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:4&quot;&gt;4&lt;/a&gt;&lt;/sup&gt;. And part of how we’ve achieved that is by making sure that things you might need to know are visible – like, explicit in the source. Every time you see a Rust match, you don’t have to ask yourself “what cases might be missing here” – the compiler guarantees you they are all there. And when you see a call to a Rust function, you don’t have to ask yourself if it is fallible – you’ll see a &lt;code&gt;?&lt;/code&gt; if it is.&lt;sup id=&quot;fnref:5&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:5&quot;&gt;5&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
  3591. &lt;h4&gt;Creating a handle can definitely “surprise” you&lt;/h4&gt;
  3592. &lt;p&gt;So I guess the question is: &lt;em&gt;would you ever have to know about a ref-count increment&lt;/em&gt;? The trick part is that the answer here is application dependent. For some low-level applications, definitely yes: an atomic reference count is a measurable cost. To be honest, I would wager that the set of applications where this is true are vanishingly small. And even in those applications, Rust already improves on the state of the art by giving you the ability to choose between &lt;code&gt;Rc&lt;/code&gt; and &lt;code&gt;Arc&lt;/code&gt; &lt;em&gt;and then proving that you don’t mess it up&lt;/em&gt;.&lt;/p&gt;
  3593. &lt;p&gt;But there are other reasons you might want to track reference counts, and those are less easy to dismiss. One of them is memory leaks. Rust, unlike GC’d languages, has &lt;em&gt;deterministic destruction&lt;/em&gt;. This is cool, because it means that you can leverage destructors to manage all kinds of resources, as Yehuda wrote about long ago in his classic ode-to-&lt;a href=&quot;https://en.wikipedia.org/wiki/Resource_acquisition_is_initialization&quot;&gt;RAII&lt;/a&gt; entitled &lt;a href=&quot;https://blog.skylight.io/rust-means-never-having-to-close-a-socket/&quot;&gt;“Rust means never having to close a socket”&lt;/a&gt;. But although the points where handles are created and destroyed is deterministic, the nature of reference-counting can make it much harder to predict when the underlying resource will actually get freed. And if those increments are not visible in your code, it is that much harder to track them down.&lt;/p&gt;
  3594. &lt;p&gt;Just recently, I was debugging &lt;a href=&quot;http://smallcultfollowing.com/babysteps/atom.xml&quot;&gt;Symposium&lt;/a&gt;, which is written in Swift. Somehow I had two &lt;code&gt;IPCManager&lt;/code&gt; instances when I only expected one, and each of them was responding to every IPC message, wreaking havoc. Poking around I found stray references floating around in some surprising places, which was causing the problem. Would this bug have still occurred if I had to write &lt;code&gt;.handle()&lt;/code&gt; explicitly to increment the ref count? Definitely, yes. Would it have been easier to find after the fact? Also yes.&lt;sup id=&quot;fnref:6&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:6&quot;&gt;6&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
  3595. &lt;p&gt;Josh gave me a similar example from &lt;a href=&quot;https://docs.rs/bytes/latest/bytes/&quot;&gt;the “bytes” crate&lt;/a&gt;. A &lt;a href=&quot;https://docs.rs/bytes/latest/bytes/struct.Bytes.html&quot;&gt;&lt;code&gt;Bytes&lt;/code&gt;&lt;/a&gt; type is a &lt;a href=&quot;https://smallcultfollowing.com/babysteps/ /blog/2025/10/07/the-handle-trait/&quot;&gt;handle&lt;/a&gt; to a slice of some underlying memory buffer. When you clone that handle, it will keep the entire backing buffer around. Sometimes you might prefer to copy your slice out into a separate buffer so that the underlying buffer can be freed. It’s not that hard for me to imagine trying to hunt down an errant handle that is keeping some large buffer alive and being very frustrated that I can’t see explicitly in the where those handles are created.&lt;/p&gt;
  3596. &lt;p&gt;A similar case occurs with APIs like like &lt;code&gt;Arc::get_mut&lt;/code&gt;&lt;sup id=&quot;fnref:7&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:7&quot;&gt;7&lt;/a&gt;&lt;/sup&gt;. &lt;code&gt;get_mut&lt;/code&gt; takes an &lt;code&gt;&amp;amp;mut Arc&amp;lt;T&amp;gt;&lt;/code&gt; and, if the ref-count is 1, returns an &lt;code&gt;&amp;amp;mut T&lt;/code&gt;. This lets you take a &lt;em&gt;shareable&lt;/em&gt; handle that &lt;em&gt;you&lt;/em&gt; know is not actually &lt;em&gt;being&lt;/em&gt; shared and recover uniqueness. This kind of API is not frequently used – but when you need it, it’s so nice it’s there.&lt;/p&gt;
  3597. &lt;h3&gt;“What I love about Rust is its versatility: low to high in one language” (hat tip: Alex Crichton)&lt;/h3&gt;
  3598. &lt;p&gt;Entering the conversation with Josh, I was leaning towards a design where you had some form of automated cloning of handles and an allow-by-default lint that would let crates which &lt;em&gt;don’t&lt;/em&gt; want that turn it off. But Josh convinced me that there is a significant class of applications that want handle creation to be ergonomic AND visible (i.e., explicit in the source). Low-level network services and even things like Rust For Linux likely fit this description, but any Rust application that uses &lt;code&gt;get_mut&lt;/code&gt; or &lt;code&gt;make_mut&lt;/code&gt; might also.&lt;/p&gt;
  3599. &lt;p&gt;And this reminded me of something Alex Crichton once said to me. Unlike the other quotes here, it wasn’t in the context of ergonomic ref-counting, but rather when I was working on my first attempt at the &lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2021/09/08/rustacean-principles/&quot;&gt;“Rustacean Principles”&lt;/a&gt;. Alex was saying that he loved how Rust was great for low-level code but also worked well high-level stuff like CLI tools and simple scripts.&lt;/p&gt;
  3600. &lt;p&gt;I feel like you can interpret Alex’s quote in two ways, depending on what you choose to emphasize. You could hear it as, “It’s important that Rust is good for high-level use cases”. That is true, and it is what leads us to ask whether we should even make handles visible at all.&lt;/p&gt;
  3601. &lt;p&gt;But you can also read Alex’s quote as, “It’s important that there’s one language that works well enough for &lt;em&gt;both&lt;/em&gt;” – and I think that’s true too. The “true Rust gestalt” is when we manage to &lt;em&gt;simultaneously&lt;/em&gt; give you the low-level control that grungy code needs but wrapped in a high-level package. This is the promise of zero-cost abstractions, of course, and Rust (in its best moments) delivers.&lt;/p&gt;
  3602. &lt;h4&gt;The “soul of Rust”: low-level enough for a kernel, usable enough for a GUI&lt;/h4&gt;
  3603. &lt;p&gt;Let’s be honest. High-level GUI programming is not Rust’s bread-and-butter, and it never will be; users will never confuse Rust for TypeScript. But then, TypeScript will never be in the Linux kernel.&lt;/p&gt;
  3604. &lt;p&gt;The goal of Rust is to be a single language that can, by and large, be “good enough” for &lt;em&gt;both&lt;/em&gt; extremes. &lt;strong&gt;The goal is make enough low-level details visible for kernel hackers but do so in a way that is usable enough for a GUI.&lt;/strong&gt; It ain’t easy, but it’s the job.&lt;/p&gt;
  3605. &lt;p&gt;This isn’t the first time that Josh has pulled me back to this realization. The last time was in the context of async fn in dyn traits, and it led to a blog post talking about the &lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2022/09/18/dyn-async-traits-part-8-the-soul-of-rust/&quot;&gt;“soul of Rust”&lt;/a&gt; and a &lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2022/09/19/what-i-meant-by-the-soul-of-rust/&quot;&gt;followup going into greater detail&lt;/a&gt;. I think the catchphrase “low-level enough for a Kernel, usable enough for a GUI” kind of captures it.&lt;/p&gt;
  3606. &lt;h4&gt;Conclusion: Explicit handles should be the first step, but it doesn’t have to be the final step&lt;/h4&gt;
  3607. &lt;p&gt;There is a slight caveat I want to add. I think another part of Rust’s soul is &lt;em&gt;preferring nuance to artificial simplicity&lt;/em&gt; (“as simple as possible, but no simpler”, as they say). And I think the reality is that there’s a huge set of applications that make new handles left-and-right (particularly but not exclusively in async land&lt;sup id=&quot;fnref:8&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:8&quot;&gt;8&lt;/a&gt;&lt;/sup&gt;) and where explicitly creating new handles is noise, not signal. This is why e.g. Swift&lt;sup id=&quot;fnref:9&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:9&quot;&gt;9&lt;/a&gt;&lt;/sup&gt; makes ref-count increments invisible – and they get a big lift out of that!&lt;sup id=&quot;fnref:10&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:10&quot;&gt;10&lt;/a&gt;&lt;/sup&gt; I’d wager most Swift users don’t even realize that Swift is not garbage-collected&lt;sup id=&quot;fnref:11&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:11&quot;&gt;11&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
  3608. &lt;p&gt;But the key thing here is that even if we do add some way to make handle creation automatic, we ALSO want a mode where it is explicit and visible. So we might as well do that one first.&lt;/p&gt;
  3609. &lt;p&gt;OK, I think I’ve made this point 3 ways from Sunday now, so I’ll stop. The next few blog posts in the series will dive into (at least) two options for how we might make handle creation and closures more ergonomic while retaining explicitness.&lt;/p&gt;
  3610. &lt;div class=&quot;footnotes&quot;&gt;
  3611. &lt;hr /&gt;
  3612. &lt;ol&gt;
  3613. &lt;li id=&quot;fn:1&quot;&gt;
  3614. &lt;p&gt;I see a potential candidate for a design axiom… &lt;em&gt;rubs hands with an evil-sounding cackle and a look of glee&lt;/em&gt; &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:1&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3615. &lt;/li&gt;
  3616. &lt;li id=&quot;fn:2&quot;&gt;
  3617. &lt;p&gt;&lt;a href=&quot;https://youtu.be/JMFS9lrVd64?si=BdaDNm7rIueS0Jlx&amp;amp;t=71&quot;&gt;It’s an industry term&lt;/a&gt;. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:2&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3618. &lt;/li&gt;
  3619. &lt;li id=&quot;fn:3&quot;&gt;
  3620. &lt;p&gt;Actually, by the standards of the conversations Josh and I often have, it was’t really all that long – an hour at most. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:3&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3621. &lt;/li&gt;
  3622. &lt;li id=&quot;fn:4&quot;&gt;
  3623. &lt;p&gt;Well, at least &lt;em&gt;sync&lt;/em&gt; Rust is. I think async Rust has more than its share, particularly around cancellation, but that’s a topic for another blog post. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:4&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3624. &lt;/li&gt;
  3625. &lt;li id=&quot;fn:5&quot;&gt;
  3626. &lt;p&gt;Modulo panics, of course – and no surprise that accounting for panics is a major pain point for some Rust users. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:5&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3627. &lt;/li&gt;
  3628. &lt;li id=&quot;fn:6&quot;&gt;
  3629. &lt;p&gt;In this particular case, it was fairly easy for me to find regardless, but this application is very simple. I can definitely imagine ripgrep’ing around a codebase to find all increments being useful, and that would be much harder to do without an explicit signal they are occurring. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:6&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3630. &lt;/li&gt;
  3631. &lt;li id=&quot;fn:7&quot;&gt;
  3632. &lt;p&gt;Or &lt;code&gt;Arc::make_mut&lt;/code&gt;, which is one of my favorite APIs. It takes an &lt;code&gt;Arc&amp;lt;_&amp;gt;&lt;/code&gt; and gives you back mutable (i.e., unique) access to the internals, always! How is that possible, given that the ref count may not be 1? Answer: if the ref-count is not 1, then it clones it. This is perfect for copy-on-write-style code. So beautiful. 😍 &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:7&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3633. &lt;/li&gt;
  3634. &lt;li id=&quot;fn:8&quot;&gt;
  3635. &lt;p&gt;My experience is that, due to language limitations we really should fix, many async constructs force you into &lt;code&gt;'static&lt;/code&gt; bounds which in turn force you into &lt;code&gt;Rc&lt;/code&gt; and &lt;code&gt;Arc&lt;/code&gt; where you’d otherwise have been able to use &lt;code&gt;&amp;amp;&lt;/code&gt;. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:8&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3636. &lt;/li&gt;
  3637. &lt;li id=&quot;fn:9&quot;&gt;
  3638. &lt;p&gt;I’ve been writing more Swift and digging it. I have to say, I love how they are not afraid to “go big”. I admire the ambition I see in designs like SwiftUI and their approach to async. I don’t think they bat 100, but it’s cool they’re swinging for the stands. I want Rust to &lt;a href=&quot;https://smallcultfollowing.com/babysteps/ /blog/2022/02/09/dare-to-ask-for-more-rust2024/&quot;&gt;dare to ask for more&lt;/a&gt;! &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:9&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3639. &lt;/li&gt;
  3640. &lt;li id=&quot;fn:10&quot;&gt;
  3641. &lt;p&gt;Well, not &lt;em&gt;only&lt;/em&gt; that. They also allow class fields to be assigned when aliased which, to avoid stale references and iterator invalidation, means you have to move everything into ref-counted boxes and adopt persistent collections, which in turn comes at a performance cost and makes Swift a harder sell for lower-level foundational systems (though by no means a non-starter, in my opinion). &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:10&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3642. &lt;/li&gt;
  3643. &lt;li id=&quot;fn:11&quot;&gt;
  3644. &lt;p&gt;Though I’d also wager that many eventually find themselves scratching their heads about a ref-count cycle. I’ve not dug into how Swift handles those, but I see references to “weak handles” flying around, so I assume they’ve not (yet?) adopted a cycle collector. To be clear, you can get a ref-count cycle in Rust too! It’s harder to do since we discourage interior mutability, but not that hard. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:11&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  3645. &lt;/li&gt;
  3646. &lt;/ol&gt;
  3647. &lt;/div&gt;</description>
  3648. <pubDate>Mon, 13 Oct 2025 11:39:16 +0000</pubDate>
  3649. </item>
  3650. <item>
  3651. <title>Mozilla Thunderbird: State of the Thunder 13: How We Make Our Roadmap</title>
  3652. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3885</guid>
  3653. <link>https://blog.thunderbird.net/2025/10/state-of-the-thunder-13-how-we-make-our-roadmap/</link>
  3654. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Blog-banner-State-of-the-Thunder-768x432.png&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  3655. &lt;p&gt;Welcome back to our thirteenth episode of State of the Thunder! Nothing unlucky about this latest installment, as Managing Director Ryan Sipes walks us through how Thunderbird creates its roadmap. Unlike other companies where roadmaps are driven solely by business needs, Thunderbird is working with our community governance and feedback from the wider user community to keep us honest even as we move forward. &lt;/p&gt;
  3656.  
  3657.  
  3658.  
  3659. &lt;p&gt;Want to find out how to join future State of the Thunders? Be sure to join our &lt;a href=&quot;https://thunderbird.topicbox.com/groups/planning&quot;&gt;Thunderbird planning mailing list&lt;/a&gt; for all the details. &lt;/p&gt;
  3660.  
  3661.  
  3662.  
  3663. &lt;h3&gt;Open Source, Open Roadmaps&lt;/h3&gt;
  3664.  
  3665.  
  3666.  
  3667. &lt;p&gt;In other companies, product managers tend to draft roadmaps based on business needs. Publishing that roadmap might be an afterthought, or might not happen at all. Thunderbird, however, is open source, so that’s not our process.&lt;/p&gt;
  3668.  
  3669.  
  3670.  
  3671. &lt;p&gt;A quick history lesson provides some needed context. Eight years ago, Thunderbird was solely a community project driven by a community council. We didn’t have a roadmap like we do today. With the earlier loss of funding and support, the project was in triage mode. Since then, thanks to a wonderful user community who has donated their skill, time, and money, we’ve changed our roadmap process.&lt;/p&gt;
  3672.  
  3673.  
  3674.  
  3675. &lt;p&gt;The Supernova release (Thunderbird 115) was where we first really focused on making a roadmap with a coherent product vision: a modernized app in performance and appearance. We developed this roadmap with input from the community, even if there was pushback to a UI change.&lt;/p&gt;
  3676.  
  3677.  
  3678.  
  3679. &lt;h3&gt;The 2026 Roadmap Process&lt;/h3&gt;
  3680.  
  3681.  
  3682.  
  3683. &lt;p&gt;At this point, the project has bylaws for the roadmap process, which unites the Thunderbird Council, MZLA staff, and user feedback. Over the past year we’ve added two new roadmaps: one for the Android app and another for ThunderbirdPro. (Note, iOS doesn’t have a roadmap yet. Our current goal is: let’s be able to receive email!) But even with these changes and additions, the &lt;a href=&quot;https://www.mozilla.org/en-US/about/manifesto/&quot;&gt;Mozilla Manifesto&lt;/a&gt; is still at the heart of everything we do. We firmly believe that making roadmaps with community governance and feedback from the larger community keeps us honest and helps us make products that genuinely improve people’s lives.&lt;/p&gt;
  3684.  
  3685.  
  3686.  
  3687. &lt;p&gt;Want to see how our 2025-2026 Roadmaps are taking shape? Check out the &lt;a href=&quot;https://developer.thunderbird.net/planning/roadmap&quot;&gt;Desktop Roadmap&lt;/a&gt;, as well the mobile roadmaps for &lt;a href=&quot;https://developer.thunderbird.net/planning/android-roadmap&quot;&gt;Android&lt;/a&gt; and &lt;a href=&quot;https://developer.thunderbird.net/planning/ios-roadmap&quot;&gt;iOS&lt;/a&gt;.&lt;/p&gt;
  3688.  
  3689.  
  3690.  
  3691. &lt;h3&gt;Questions&lt;/h3&gt;
  3692.  
  3693.  
  3694.  
  3695. &lt;h4&gt;Integrating Community Contributions&lt;/h4&gt;
  3696.  
  3697.  
  3698.  
  3699. &lt;p&gt;In the past, community contributors have picked up “nice to have” issues and developed them alongside us. Or people want to pursue problems or challenges that affect them the most. Sometimes, either of these scenarios coincide with our roadmap, and we get features like the new drag and drop folders! &lt;/p&gt;
  3700.  
  3701.  
  3702.  
  3703. &lt;p&gt;Needless to say, we love when the community helps us get the product where we hope it will go. Sometimes, we have to pause development because of shifted priorities, and we’re trying to get better at updating contributors when these shifts happen on places like the &lt;a href=&quot;https://thunderbird.topicbox.com/groups/planning&quot;&gt;tb-planning&lt;/a&gt; and &lt;a href=&quot;https://thunderbird.topicbox.com/groups/mobile-planning&quot;&gt;mobile-planning&lt;/a&gt; mailing lists.&lt;/p&gt;
  3704.  
  3705.  
  3706.  
  3707. &lt;p&gt;And these community contributions aren’t just code! Testing is a crucial way to help make Thunderbird shine on desktop and mobile. Community suggestions on Mozilla Connect help us dream big, as we discussed in the last two episodes. Reporting bugs, either on &lt;a href=&quot;https://bugzilla.mozilla.net&quot;&gt;Bugzilla&lt;/a&gt; for the desktop app or &lt;a href=&quot;https://github.com/thunderbird/thunderbird-android/issues/&quot;&gt;GitHub&lt;/a&gt; for the Android app, help us know when things aren’t working. We encourage our community to learn more &lt;a href=&quot;https://council.thunderbird.net/&quot;&gt;about the Council&lt;/a&gt;, and don’t be afraid to get in touch with them at council@thunderbird.net.&lt;/p&gt;
  3708.  
  3709.  
  3710.  
  3711. &lt;h4&gt;Telemetry and the Roadmap&lt;/h4&gt;
  3712.  
  3713.  
  3714.  
  3715. &lt;p&gt;While we know there are passionate debates on telemetry in the open source community, we want to mention how respectful telemetry can make Thunderbird better. Our telemetry helps us see what features are important, and which ones just clutter up the UI. We don’t collect Personally Identifying Information (PII), and our code is open so you can check us on this. Unlike Outlook, who shares their data with 801 partners, we don’t. You can read all about what we use and how we use it &lt;a href=&quot;https://www.thunderbird.net/privacy/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
  3716.  
  3717.  
  3718.  
  3719. &lt;p&gt;So if you have telemetry turned off, please, we ask you to turn it on, and if it’s already on, to keep it on! Especially if you’re a Linux user, enabling telemetry helps us have a better gauge of our Linux user base and how to best support you.&lt;/p&gt;
  3720.  
  3721.  
  3722.  
  3723. &lt;h4&gt;Roadmap Categories and Organizing&lt;/h4&gt;
  3724.  
  3725.  
  3726.  
  3727. &lt;p&gt;Should we try to ‘bucket’ similar items on our roadmap and spread development evenly between them, or should we concentrate on the bucket that needs it most? The answer to this question depends on who you ask! Sometimes we’re focused on a particular area of focus, like UI work in Supernova and current UX work in Calendar. Sometimes we’re working to pay down tech debt across our code. That effort in reducing tech debt can pave the way for future work, like the current efforts to modernize our database so we can have a true Conversation View and other features. Sometimes roadmaps reveal obstacles you have to overcome, and Ryan thinks we’re getting faster at this.&lt;/p&gt;
  3728.  
  3729.  
  3730.  
  3731. &lt;h3&gt;Where to see the roadmaps&lt;/h3&gt;
  3732.  
  3733.  
  3734.  
  3735. &lt;p&gt;The current desktop roadmap is &lt;a href=&quot;https://developer.thunderbird.net/planning/roadmap&quot;&gt;here&lt;/a&gt;, while the current Android roadmap is on our &lt;a href=&quot;https://github.com/orgs/thunderbird/projects/19&quot;&gt;GitHub repo&lt;/a&gt;. In the future, we’re hoping to update where these roadmaps live, how they look, and how you can interact with them. (Ryan is particularly partial to &lt;a href=&quot;https://obsidian.md/roadmap/&quot;&gt;Obsidian’s roadmap.&lt;/a&gt;) We ultimately want our roadmaps to be storytelling devices, and to keep them more updated to any recent changes.&lt;/p&gt;
  3736.  
  3737.  
  3738.  
  3739. &lt;h3&gt;Current Calls for Involvement&lt;/h3&gt;
  3740.  
  3741.  
  3742.  
  3743. &lt;p&gt;Join us for the last few days of &lt;a href=&quot;https://thunderbird.topicbox.com/groups/planning/T00a28d546ed1b7d1/ews-in-thunderbird-144-0b1-call-for-testing&quot;&gt;testing EWS mail support&lt;/a&gt;! Also, we had a fantastic time with the Ask a Fox replython, and would love if you helped us &lt;a href=&quot;https://blog.thunderbird.net/2024/08/video-how-to-answer-thunderbird-questions-on-mozilla-support/&quot;&gt;answer support questions&lt;/a&gt; on &lt;a href=&quot;https://support.mozilla.org&quot;&gt;SUMO&lt;/a&gt;.&lt;/p&gt;
  3744.  
  3745.  
  3746.  
  3747. &lt;h3&gt;Watch the Video (also on &lt;a href=&quot;https://tilvids.com/w/mvHZHm2JXzbrxwMBvLDorc&quot;&gt;PeerTube&lt;/a&gt;)&lt;/h3&gt;
  3748.  
  3749.  
  3750.  
  3751. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  3752.  
  3753. &lt;/div&gt;&lt;/figure&gt;
  3754.  
  3755.  
  3756.  
  3757. &lt;h3&gt;Listen to the Podcast&lt;/h3&gt;
  3758.  
  3759.  
  3760.  
  3761. &lt;p&gt;&lt;/p&gt;
  3762. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/10/state-of-the-thunder-13-how-we-make-our-roadmap/&quot;&gt;State of the Thunder 13: How We Make Our Roadmap&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  3763. <pubDate>Fri, 10 Oct 2025 18:37:37 +0000</pubDate>
  3764. <dc:creator>Monica Ayhens-Madon</dc:creator>
  3765. </item>
  3766. <item>
  3767. <title>The Mozilla Blog: Shake to Summarize recognized with special mention in TIME’s Best Inventions of 2025</title>
  3768. <guid isPermaLink="false">https://blog.mozilla.org/?p=82133</guid>
  3769. <link>https://blog.mozilla.org/en/firefox/shake-to-summarize-time-best-inventions/</link>
  3770. <description>&lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;Illustration featuring a TIME magazine cover titled “Best Inventions of 2025,” showing a humanoid robot folding clothes, alongside a smartphone displaying the Firefox logo and a screen reading “Summarizing…” with a dessert recipe below it.&quot; class=&quot;wp-image-82134&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/Blog-Header-3-1024x576.png&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;Cover credit: Photography by Spencer Lowell for TIME
  3771. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  3772.  
  3773.  
  3774.  
  3775. &lt;p&gt;&lt;em&gt;Shake to Summarize has been recognized with a &lt;a href=&quot;https://time.com/collections/best-inventions-special-mentions/7320805/firefox-shake-to-summarize/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;strong&gt;Special Mention&lt;/strong&gt;&lt;/a&gt; in&lt;strong&gt; &lt;/strong&gt;&lt;a href=&quot;https://time.com/collections/best-inventions-2025/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;strong&gt;TIME’s Best Inventions of 2025&lt;/strong&gt;&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
  3776.  
  3777.  
  3778.  
  3779. &lt;p&gt;Each year TIME&lt;strong&gt; &lt;/strong&gt;spotlights a range of new industry-defining innovations across consumer electronics, health tech, apps and beyond. This year, &lt;a href=&quot;https://blog.mozilla.org/firefox/shake-to-summarize/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Firefox’s Shake to Summarize feature&lt;/a&gt; made the list for bringing a smart solution to a modern user problem: information overload. &lt;/p&gt;
  3780.  
  3781.  
  3782.  
  3783. &lt;p&gt;With a single shake or tap, users on iOS devices can get to the heart of an article in seconds. The cool part? Summaries adapt to what you’re reading: recipes pull out the steps for cooking, sports focus on game scores and stats, and news highlights the key takeaways from a story.&lt;/p&gt;
  3784.  
  3785.  
  3786.  
  3787. &lt;p&gt;“We’re thrilled to see Firefox earn a TIME Best Inventions 2025 Special Mention! Our work on Shake to Summarize reflects how Firefox is evolving,” said &lt;a href=&quot;https://blog.mozilla.org/en/firefox/promoted/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Anthony Enzor-DeMeo&lt;/a&gt;, general manager of Firefox. “We’re reimagining our browser to fit seamlessly into modern life, helping people browse with less clutter and more focus. The feature is also part of our efforts to give mobile users a cleaner UI and smarter tools that make browsing on the go fast, seamless, and even fun.”&lt;/p&gt;
  3788.  
  3789.  
  3790.  
  3791. &lt;figure class=&quot;wp-block-embed aligncenter is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  3792.  
  3793. &lt;/div&gt;&lt;/figure&gt;
  3794.  
  3795.  
  3796.  
  3797. &lt;p&gt;Launched in September 2025 and currently available to English-language users in the U.S., Shake to Summarize generates summaries using Apple Intelligence on iPhone 15 Pro or later running iOS 26 or above, and Mozilla-hosted AI for other devices running iOS 16 or above.&lt;/p&gt;
  3798.  
  3799.  
  3800.  
  3801. &lt;p&gt;“This recognition is a testament to the incredible work of our UX, design, product, and engineering teams who brought this innovation to life, showcasing that Firefox continues to lead with purpose, creativity, and a deep commitment to user-centric design. Big thank you!” added Enzor-DeMeo.&lt;/p&gt;
  3802.  
  3803.  
  3804.  
  3805. &lt;p&gt;The Firefox team is working on making the feature available to more users and for those on Android. In the meantime, iOS users can already make the most of Shake to Summarize available in the &lt;a href=&quot;https://apps.apple.com/us/app/firefox-private-web-browser/id989804926?ppid=908b3bb9-aa78-4a60-8f7f-2407cd3227bc&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Apple app store&lt;/a&gt; now.&lt;/p&gt;
  3806.  
  3807.  
  3808.  
  3809. &lt;a class=&quot;ft-c-inline-cta&quot; href=&quot;https://www.mozilla.org/firefox/new/?utm_source=blog.mozilla.org&amp;amp;utm_medium=referral&amp;amp;utm_campaign=blog-nav&quot;&gt;
  3810.  &lt;div class=&quot;ft-c-inline-cta__media&quot;&gt;
  3811.  &lt;img alt=&quot;&quot; class=&quot;attachment-1x1 size-1x1&quot; height=&quot;800&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2021/10/Visual-Guidelines-800x800.png&quot; width=&quot;800&quot; /&gt;  &lt;/div&gt;
  3812.  &lt;div class=&quot;ft-c-inline-cta__content&quot;&gt;
  3813.     &lt;h3&gt;Take control of your internet&lt;/h3&gt;      &lt;span&gt;Download Firefox&lt;/span&gt;   &lt;/div&gt;
  3814. &lt;/a&gt;
  3815. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/firefox/shake-to-summarize-time-best-inventions/&quot;&gt;Shake to Summarize recognized with special mention in TIME’s Best Inventions of 2025&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  3816. <pubDate>Thu, 09 Oct 2025 14:28:43 +0000</pubDate>
  3817. <dc:creator>Christina Petrova</dc:creator>
  3818. </item>
  3819. <item>
  3820. <title>Mozilla Thunderbird: State Of The Bird 2024/25</title>
  3821. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3844</guid>
  3822. <link>https://blog.thunderbird.net/2025/10/state-of-the-bird-2024-25/</link>
  3823. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Annual-Report4-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  3824. &lt;p&gt;The past twelve months have been another remarkable chapter in Thunderbird’s journey. Together, we started expanding Thunderbird beyond its strong desktop roots, introducing it to smartphones and web browsers to make it more accessible to more people. Thunderbird for Android arrived in the fall and has been steadily improving thanks to our growing mobile team, as well as feedback and contributions from our growing global family. A few months later, in December 2024, we celebrated an extraordinary milestone: 20 years of Thunderbird! We also looked toward a sustainable future with the announcement of Thunderbird Pro, with one of its first services, Appointment, already finding an audience in closed beta. &lt;/p&gt;
  3825.  
  3826.  
  3827.  
  3828. &lt;p&gt;The past year also saw a shift in how Thunderbird evolves. Although we recently released our latest annual ESR update (codenamed Eclipse), the bigger news is that our team built the new Monthly Release channel, which is now the default for most of you. This change means you’ll see more frequent updates that make Thunderbird feel fresher, more responsive, and more in tune with your personalized needs. &lt;br /&gt;Before diving into all the details, I want to pause and express our deepest gratitude to the incredible global community that makes all of this possible. To the hundreds of thousands of people who donated financially, the volunteers who contributed their time and expertise, and the beta testers who carefully helped us polish each update: thank you! Thunderbird &lt;em&gt;thrives&lt;/em&gt; because of you. Every milestone we celebrate is a shared achievement, and a shining example of the power of community-driven, open source software development.&lt;/p&gt;
  3829.  
  3830.  
  3831.  
  3832. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 59px;&quot;&gt;&lt;/div&gt;
  3833.  
  3834.  
  3835.  
  3836. &lt;h3&gt;&lt;strong&gt;Team and Product Updates&lt;/strong&gt;&lt;/h3&gt;
  3837.  
  3838.  
  3839.  
  3840. &lt;h4&gt;&lt;strong&gt;Desktop and release updates&lt;/strong&gt;&lt;/h4&gt;
  3841.  
  3842.  
  3843.  
  3844. &lt;p&gt;In December 2024, we celebrated Thunderbird’s 20th anniversary. Two decades of proving that email software can be both powerful and principled was not without its ups and downs, but that milestone reaffirmed something we hear so often from our community: Thunderbird continues to matter deeply to people all over the world. &lt;/p&gt;
  3845.  
  3846.  
  3847.  
  3848. &lt;p&gt;One of the biggest changes this year was the introduction of a new monthly release channel, simply called “Thunderbird Release.” Making this shift required an enormous amount of coordination and care across our desktop and release teams. Unlike the long-standing Extended Support Release (ESR), which provides a single major update every July, the new Thunderbird Release delivers monthly updates. This approach means we can bring you useful improvements and new features significantly faster, while keeping the stability and reliability you rely on.&lt;/p&gt;
  3849.  
  3850.  
  3851.  
  3852. &lt;p&gt;Over the past year, our desktop team focused heavily on introducing changes that people have been asking for. Specifically, changes that make Thunderbird feel more efficient, intuitive, and modern. We improved visual consistency across system themes, gave you more ways to control the appearance of your message lists and how they’re organized, modernized notifications with native OS integration and quick actions, and moved closer to full Microsoft Exchange support. &lt;/p&gt;
  3853.  
  3854.  
  3855.  
  3856. &lt;p&gt;Many of you who switched from the ESR to the new Thunderbird Release channel started seeing these updates as early as April. For those who stuck with the ESR, the annual update, codenamed Eclipse, arrived in July. Thanks to the solid foundation established in those smaller monthly updates, Eclipse enjoyed the smoothest rollout of any annual release in Thunderbird’s history. &lt;/p&gt;
  3857.  
  3858.  
  3859.  
  3860. &lt;p&gt;&lt;em&gt;In-depth details on Desktop development can be found in our monthly &lt;/em&gt;&lt;a href=&quot;https://blog.thunderbird.net/tag/development-digest/&quot;&gt;&lt;em&gt;Developer Digest&lt;/em&gt;&lt;/a&gt;&lt;em&gt; updates on our blog. &lt;/em&gt;&lt;/p&gt;
  3861.  
  3862.  
  3863.  
  3864. &lt;h4&gt;&lt;strong&gt;Thunderbird Mobile&lt;/strong&gt;&lt;/h4&gt;
  3865.  
  3866.  
  3867.  
  3868. &lt;h5&gt;Android&lt;/h5&gt;
  3869.  
  3870.  
  3871.  
  3872. &lt;p&gt;It took longer than we originally anticipated, but Thunderbird has finally arrived as a true smartphone app. The launch of Thunderbird for Android in October 2024 was one of our most exciting steps forward in years. Releasing it took more than two years of active development, beta testing, and invaluable community feedback. &lt;/p&gt;
  3873.  
  3874.  
  3875.  
  3876. &lt;p&gt;​​This milestone was made possible by transforming the much-loved K-9 Mail app into something we could proudly call Thunderbird. That process included a full redesign of the interface, including bringing it up to modern design standards, and building an easy way for people to bring their existing Thunderbird desktop accounts directly into the Android app.&lt;/p&gt;
  3877.  
  3878.  
  3879.  
  3880. &lt;p&gt;We’ve been encouraged by the enthusiastic response to Thunderbird on Android, but we’re also listening closely to your feedback. Our team, together with community contributors, has one very focused goal: to make Thunderbird the best Android email app available. &lt;/p&gt;
  3881.  
  3882.  
  3883.  
  3884. &lt;h5&gt;iOS&lt;/h5&gt;
  3885.  
  3886.  
  3887.  
  3888. &lt;p&gt;We’ve also seen the overwhelming demand to build a version of Thunderbird for the iOS community. Unlike the Android app, the iOS app is being built from the ground up. &lt;/p&gt;
  3889.  
  3890.  
  3891.  
  3892. &lt;p&gt;Fortunately, Thunderbird for iOS took some major steps forward this year. We published the initial repository (a central location for open-source project files and code) for the Thunderbird mobile team and contributors to work together, and we’re laying the groundwork for public testing. &lt;/p&gt;
  3893.  
  3894.  
  3895.  
  3896. &lt;p&gt;Our goal for the first public alpha will be to support manual account setup and basic inbox viewing to meet Apple’s minimum review standards. These early pre-release versions will be distributed through TestFlight, allowing Thunderbird for iOS to benefit from your real-world feedback. &lt;/p&gt;
  3897.  
  3898.  
  3899.  
  3900. &lt;p&gt;When we started building Thunderbird for iOS, a core decision was made to use a modern foundation (JMAP) designed for mobile devices. This will allow for, among other advantages, faster mail synchronization and more efficient resource usage. The first pieces of that foundation are already in place, with the basic ability to view folders and messages. We’ve also set up internal tools that will make regular updates, language translations, and community testing possible. &lt;/p&gt;
  3901.  
  3902.  
  3903.  
  3904. &lt;p&gt;Thunderbird for iOS is still in the early stages of development, but momentum is strong, our team is growing, and we’re confidently moving toward the first community-accessible release. &lt;/p&gt;
  3905.  
  3906.  
  3907.  
  3908. &lt;p&gt;&lt;em&gt;In depth details on mobile development can be found in our monthly &lt;/em&gt;&lt;a href=&quot;https://blog.thunderbird.net/tag/android-progress-report/&quot;&gt;&lt;em&gt;Mobile Progress Report&lt;/em&gt;&lt;/a&gt;&lt;em&gt; on our blog. &lt;/em&gt;&lt;/p&gt;
  3909.  
  3910.  
  3911.  
  3912. &lt;h4&gt;&lt;strong&gt;Thundermail and Thunderbird Pro services&lt;/strong&gt;&lt;/h4&gt;
  3913.  
  3914.  
  3915.  
  3916. &lt;p&gt;It’s no secret we’ve been building additional web services under the Thunderbird Pro name, and 2025 marked a pivotal moment in our vision for a complete, open-source Thunderbird ecosystem. &lt;/p&gt;
  3917.  
  3918.  
  3919.  
  3920. &lt;p&gt;This year we announced Thundermail, a dedicated email service by Thunderbird. During the past decade, we’ve seen a large move away from dedicated email clients to products like Gmail, partially because of the robust ecosystem around them. The plan for Thundermail is to eventually offer an alternative webmail solution that protects your privacy, and doesn’t use your messages to train AI or show you ads. &lt;/p&gt;
  3921.  
  3922.  
  3923.  
  3924. &lt;p&gt;Here’s what else we’ve been working on in addition to Thundermail: &lt;/p&gt;
  3925.  
  3926.  
  3927.  
  3928. &lt;p&gt;During its current beta, Thunderbird Appointment saw great improvements in managing your schedule, with many of the changes focused on reliability and visual polish.&lt;/p&gt;
  3929.  
  3930.  
  3931.  
  3932. &lt;p&gt;Thunderbird Send, an app for securely sharing encrypted files, also saw forward momentum. Together, these services are steadily moving toward a wider beta launch this fall, and we’re excited to see how you’ll use them to improve your personal and professional lives. &lt;/p&gt;
  3933.  
  3934.  
  3935.  
  3936. &lt;p&gt;All of the work going into Thundermail and Thunderbird Pro services is guided by a clear goal: providing you with an ethical alternative to the closed-off “walled gardens” that dominate our digital communication. You shouldn’t have to sacrifice your values and give up your personal data to enjoy convenience and powerful features. &lt;/p&gt;
  3937.  
  3938.  
  3939.  
  3940. &lt;p&gt;&lt;em&gt;In depth details on Thunderbird Pro development can be found in our &lt;/em&gt;&lt;a href=&quot;https://blog.thunderbird.net/tag/tbpro/&quot;&gt;&lt;em&gt;Thunderbird Pro&lt;/em&gt;&lt;/a&gt;&lt;em&gt; updates on our blog. &lt;/em&gt;&lt;/p&gt;
  3941.  
  3942.  
  3943.  
  3944. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 52px;&quot;&gt;&lt;/div&gt;
  3945.  
  3946.  
  3947.  
  3948. &lt;h3&gt;&lt;strong&gt;2024 Financial Picture&lt;/strong&gt;&lt;/h3&gt;
  3949.  
  3950.  
  3951.  
  3952. &lt;p&gt;The generosity of our donors continues to power everything we do, and the importance of these financial contributions cannot be understated. In 2024, the Thunderbird project once again saw continued growth in donations which paved the way for Thundermail and the Thunderbird Pro services you just read about. It also gave us the opportunity to grow our mobile development team, improve our user support outreach, and expand our connections to the community. &lt;/p&gt;
  3953.  
  3954.  
  3955.  
  3956. &lt;p&gt;Here’s a detailed breakdown of our donation revenue in 2024, and why many of these statistics are so meaningful. &lt;/p&gt;
  3957.  
  3958.  
  3959.  
  3960. &lt;h4&gt;&lt;strong&gt;Contribution Revenue&lt;/strong&gt;&lt;/h4&gt;
  3961.  
  3962.  
  3963.  
  3964. &lt;p&gt;In 2024, financial contributions to Thunderbird reached $10.3 million, representing a 19% increase over the previous year. This support came courtesy of more than 539,000 transactions from more than 335,000 individual donors. A healthy 25% of these contributions were given as recurring monthly support.&lt;/p&gt;
  3965.  
  3966.  
  3967.  
  3968. &lt;p&gt;What makes this so meaningful to us isn’t the total revenue, or the scale of the donations. It’s how those donations break down. The average contribution was $18.88, with a median of $16.66. Among our recurring donors, the average monthly gift was only $6.25. In fact, 53% of all donations were $20 or less, and 94% were $35 or less. Only 17 contributions were $1,000 or more. &lt;/p&gt;
  3969.  
  3970.  
  3971.  
  3972. &lt;p&gt;What does this represent when we go beyond the numbers? It means Thunderbird isn’t sustained by a handful of wealthy benefactors or corporate sponsors. Rather, it is sustained by a global community of people who believe in what we’ve built and what we’re still building, and they come together to keep it moving forward.&lt;/p&gt;
  3973.  
  3974.  
  3975.  
  3976. &lt;p&gt;And that global reach continues to inspire us. We received contributions from more than 200 countries. The top ten contributing countries – Germany, the United States, France, the United Kingdom, Switzerland, the Netherlands, Japan, Italy, Austria, and Canada – accounted for 83% of our total revenue.&lt;/p&gt;
  3977.  
  3978.  
  3979.  
  3980. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/Annual-Report1.jpg&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3862&quot; height=&quot;1041&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Annual-Report1.jpg&quot; width=&quot;2000&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  3981.  
  3982.  
  3983.  
  3984. &lt;p&gt;But products aren’t just numbers and code. Products are the people that work on them. To support the ambitions of our expanding roadmap, our team grew significantly in 2024. We added 14 new team members throughout the year, closing out 2024 with 43 full-time staff members. Much of this growth strengthened our mobile development, web services, and desktop + release teams. 80% of our staff focuses on technical work – things like product development and infrastructure – but we also added more roles to actively support users, improve community outreach, and smooth out internal operations. &lt;/p&gt;
  3985.  
  3986.  
  3987.  
  3988. &lt;h4&gt;&lt;strong&gt;Expenses&lt;/strong&gt;&lt;/h4&gt;
  3989.  
  3990.  
  3991.  
  3992. &lt;p&gt;When we talk about how we use financial contributions, we’re really talking about &lt;a href=&quot;https://www.thunderbird.net/en-US/about/&quot;&gt;investments in our shared values&lt;/a&gt;. The majority of our spending goes to personnel; the talented individuals who write code, design interfaces, test features, and support our users. Infrastructure is the next largest expense, followed by administrative costs to keep operations running smoothly. &lt;/p&gt;
  3993.  
  3994.  
  3995.  
  3996. &lt;p&gt;Below is a breakdown of our 2024 expenses:&lt;/p&gt;
  3997.  
  3998.  
  3999.  
  4000. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/Annual-Report.jpg&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3856&quot; height=&quot;1480&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Annual-Report.jpg&quot; width=&quot;2000&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  4001.  
  4002.  
  4003.  
  4004. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 58px;&quot;&gt;&lt;/div&gt;
  4005.  
  4006.  
  4007.  
  4008. &lt;h3&gt;&lt;strong&gt;Community Snapshot&lt;/strong&gt;&lt;/h3&gt;
  4009.  
  4010.  
  4011.  
  4012. &lt;h4&gt;&lt;strong&gt;Contributor &amp;amp; Community Growth&lt;/strong&gt;&lt;/h4&gt;
  4013.  
  4014.  
  4015.  
  4016. &lt;p&gt;For two decades, Thunderbird has survived and thrived because of its dedicated open-source community. In 2024, we continued using our&lt;a href=&quot;https://thunderbird.biterg.io&quot;&gt; Bitergia dashboard&lt;/a&gt; to give our community a clear view of the project’s overall activity across the board. (You can read more about how we collaborated on and use this beneficial tool&lt;a href=&quot;https://blog.thunderbird.net/2024/12/visualizing-the-thunderbird-community-with-bitergia/&quot;&gt; here&lt;/a&gt;.)&lt;br /&gt;&lt;/p&gt;
  4017.  
  4018.  
  4019.  
  4020. &lt;p&gt;This dashboard helps us track participation, identify and celebrate successes, and find areas to improve, which is especially important as we expand the Thunderbird ecosystem with new products and services. &lt;/p&gt;
  4021.  
  4022.  
  4023.  
  4024. &lt;p&gt;For this report, we’ve highlighted some of the most notable community metrics and growth milestones from 2024. &lt;/p&gt;
  4025.  
  4026.  
  4027.  
  4028. &lt;p&gt;For reference, &lt;strong&gt;Github&lt;/strong&gt; and &lt;strong&gt;Bugzilla&lt;/strong&gt; measure developer contributions. &lt;strong&gt;TopicBox&lt;/strong&gt; measures activity across our many mailing lists. &lt;strong&gt;Pontoon&lt;/strong&gt; measures the activity from volunteers who help us translate and localize Thunderbird. &lt;strong&gt;SUMO&lt;/strong&gt; (the Mozilla support website) measures the impact of Thunderbird’s support volunteers who engage with our users and respond to their varied support questions.&lt;/p&gt;
  4029.  
  4030.  
  4031.  
  4032. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/Annual-Report2-scaled.jpg&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3849&quot; height=&quot;2560&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/Annual-Report2-scaled.jpg&quot; width=&quot;1502&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  4033.  
  4034.  
  4035.  
  4036. &lt;p&gt;We estimate that in 2024, the total number of people who contributed to Thunderbird – by writing code, answering support questions, providing translations, or other meaningful areas – is more than 20,000. &lt;/p&gt;
  4037.  
  4038.  
  4039.  
  4040. &lt;p&gt;It’s especially encouraging to see the number of translation locales increase from 58 to 70, as Thunderbird continues to find new users around the world. &lt;/p&gt;
  4041.  
  4042.  
  4043.  
  4044. &lt;p&gt;But there are areas of opportunity, too. For example, making it less complicated for people who want to start contributing to Thunderbird. We’ve started addressing this by recording two Community Office Hours videos, talking about how to write Knowledge Base articles, and how to effectively answer questions on the Mozilla Support website. &lt;/p&gt;
  4045.  
  4046.  
  4047.  
  4048. &lt;p&gt;&lt;strong&gt;Mozilla Connect&lt;/strong&gt; is another portal that lets anyone interested in the betterment of Thunderbird suggest ideas, openly discuss them, and vote on them. In 2024, four desktop ideas as well as four of your ideas in our relatively new mobile space were implemented, and we saw more than 500 new thoughtful ideas suggested across mobile and desktop. Our staff and community are watching for your ideas, so &lt;a href=&quot;https://connect.mozilla.org&quot;&gt;keep them coming! &lt;/a&gt;&lt;/p&gt;
  4049.  
  4050.  
  4051.  
  4052. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 57px;&quot;&gt;&lt;/div&gt;
  4053.  
  4054.  
  4055.  
  4056. &lt;h3&gt;&lt;strong&gt;Thank you&lt;/strong&gt;&lt;/h3&gt;
  4057.  
  4058.  
  4059.  
  4060. &lt;p&gt;As we close out this year’s &lt;em&gt;State of the Bird&lt;/em&gt;, we want to once again shine a light on the incredible global community of Thunderbird supporters. Whether you’ve contributed your valuable time, financial donations, or simply shared Thunderbird with colleagues, friends, and family, your support continues to brighten Thunderbird’s future. &lt;/p&gt;
  4061.  
  4062.  
  4063.  
  4064. &lt;p&gt;After all, products aren’t just numbers on a chart. Products are the people who create them, support them, improve them, and believe in crucial concepts like privacy, digital wellbeing, and open standards. &lt;/p&gt;
  4065.  
  4066.  
  4067.  
  4068. &lt;p&gt;We’re so very grateful to you.&lt;/p&gt;
  4069. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/10/state-of-the-bird-2024-25/&quot;&gt;State Of The Bird 2024/25&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  4070. <pubDate>Wed, 08 Oct 2025 10:02:00 +0000</pubDate>
  4071. <dc:creator>Ryan Sipes</dc:creator>
  4072. </item>
  4073. <item>
  4074. <title>Niko Matsakis: SymmACP: extending Zed's ACP to support Composable Agents</title>
  4075. <guid isPermaLink="false">https://smallcultfollowing.com/babysteps/blog/2025/10/08/symmacp/</guid>
  4076. <link>https://smallcultfollowing.com/babysteps/blog/2025/10/08/symmacp/?utm_source=atom_feed</link>
  4077. <description>&lt;p&gt;This post describes &lt;strong&gt;SymmACP&lt;/strong&gt; – a proposed extension to Zed’s &lt;a href=&quot;https://agentclientprotocol.com/overview/introduction&quot;&gt;Agent Client Protocol&lt;/a&gt; that lets you build AI tools like Unix pipes or browser extensions. Want a better TUI? Found some cool slash commands on GitHub? Prefer a different backend? With SymmACP, you can mix and match these pieces and have them all work together without knowing about each other.&lt;/p&gt;
  4078. &lt;p&gt;This is pretty different from how AI tools work today, where everything is a monolith – if you want to change one piece, you’re stuck rebuilding the whole thing from scratch. SymmACP allows you to build out new features and modes of interactions in a layered, interoperable way. This post explains how SymmACP would work by walking through a series of examples.&lt;/p&gt;
  4079. &lt;p&gt;Right now, SymmACP is just a thought experiment. I’ve sketched these ideas to the Zed folks, and they seemed interested, but we still have to discuss the details in this post. My plan is to start prototyping in &lt;a href=&quot;https://symposium-dev.github.io/symposium/&quot;&gt;Symposium&lt;/a&gt; – if you think the ideas I’m discussing here are exciting, please join the &lt;a href=&quot;https://symposium-dev.zulipchat.com/&quot;&gt;Symposium Zulip&lt;/a&gt; and let’s talk!&lt;/p&gt;
  4080. &lt;h3&gt;“Composable agents” let you build features independently and then combine them&lt;/h3&gt;
  4081. &lt;p&gt;I’m going to explain the idea of “composable agents” by walking through a series of features. We’ll start with a basic CLI agent&lt;sup id=&quot;fnref:1&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:1&quot;&gt;1&lt;/a&gt;&lt;/sup&gt; tool – basically a chat loop with access to some MCP servers so that it can read/write files and execute bash commands. Then we’ll show how you could add several features on top:&lt;/p&gt;
  4082. &lt;ol&gt;
  4083. &lt;li&gt;Addressing time-blindness by helping the agent know what time it is.&lt;/li&gt;
  4084. &lt;li&gt;Injecting context and “personality” to the agent.&lt;/li&gt;
  4085. &lt;li&gt;Spawning long-running, asynchronous tasks.&lt;/li&gt;
  4086. &lt;li&gt;A copy of Q CLI’s &lt;code&gt;/tangent&lt;/code&gt; mode that lets you do a bit of “off the books” work that gets removed from your history later.&lt;/li&gt;
  4087. &lt;li&gt;Implementing &lt;a href=&quot;https://symposium-dev.github.io/symposium/get-started/walkthroughs.html&quot;&gt;Symposium’s interactive walkthroughs&lt;/a&gt;, which give the agent a richer vocabulary for communicating with you than just text.&lt;/li&gt;
  4088. &lt;li&gt;Smarter tool delegation.&lt;/li&gt;
  4089. &lt;/ol&gt;
  4090. &lt;p&gt;&lt;strong&gt;The magic trick is that each of these features will be developed as separate repositories.&lt;/strong&gt; What’s more, they could be applied to any base tool you want, so long as it speaks SymmACP. And you could also combine them with different front-ends, such as a TUI, a web front-end, builtin support from &lt;a href=&quot;https://zed.dev/&quot;&gt;Zed&lt;/a&gt; or &lt;a href=&quot;https://zed.dev/blog/jetbrains-on-acp&quot;&gt;IntelliJ&lt;/a&gt;, etc. Pretty neat.&lt;/p&gt;
  4091. &lt;p&gt;My hope is that if we can centralize on SymmACP, or something like it, then we could move from everybody developing their own bespoke tools to an interoperable ecosystem of ideas that can build off of one another.&lt;/p&gt;
  4092. &lt;h3&gt;let mut SymmACP = ACP&lt;/h3&gt;
  4093. &lt;p&gt;SymmACP begins with ACP, so let’s explain what ACP is. ACP is a wonderfully simple protocol that lets you abstract over CLI agents. Imagine if you were using an agentic CLI tool except that, instead of communication over the terminal, the CLI tool communicates with a front-end over JSON-RPC messages, currently sent via stdin/stdout.&lt;/p&gt;
  4094. &lt;pre class=&quot;mermaid&quot;&gt;flowchart LR
  4095.    Editor &amp;lt;-.-&amp;gt;|JSON-RPC via stdin/stdout| Agent[CLI Agent]
  4096.  &lt;/pre&gt;
  4097. &lt;p&gt;When you type something into the GUI, the editor sends a JSON-RPC message to the agent with what you typed. The agent responds with a stream of messages containing text and images. If the agent decides to invoke a tool, it can request permission by sending a JSON-RPC message back to the editor. And when the agent has completed, it responds to the editor with an “end turn” message that says “I’m ready for you to type something else now”.&lt;/p&gt;
  4098. &lt;pre class=&quot;mermaid&quot;&gt;sequenceDiagram
  4099.    participant E as Editor
  4100.    participant A as Agent
  4101.    participant T as Tool (MCP)
  4102.    
  4103.    E-&amp;gt;&amp;gt;A: prompt(&quot;Help me debug this code&quot;)
  4104.    A-&amp;gt;&amp;gt;E: request_permission(&quot;Read file main.rs&quot;)
  4105.    E-&amp;gt;&amp;gt;A: permission_granted
  4106.    A-&amp;gt;&amp;gt;T: read_file(&quot;main.rs&quot;)
  4107.    T-&amp;gt;&amp;gt;A: file_contents
  4108.    A-&amp;gt;&amp;gt;E: text_chunk(&quot;I can see the issue...&quot;)
  4109.    A-&amp;gt;&amp;gt;E: text_chunk(&quot;The problem is on line 42...&quot;)
  4110.    A-&amp;gt;&amp;gt;E: end_turn
  4111.  &lt;/pre&gt;
  4112. &lt;h3&gt;Telling the agent what time it is&lt;/h3&gt;
  4113. &lt;p&gt;OK, let’s tackle our first feature. If you’ve used a CLI agent, you may have noticed that they don’t know what time it is – or even what &lt;em&gt;year&lt;/em&gt; it is. This may sound trivial, but it can lead to some real mistakes. For example, they may not realize that some information is outdated. Or when they do web searches for information, they can search for the wrong thing: I’ve seen CLI agents search the web for “API updates in 2024” for example, even though it is 2025.&lt;/p&gt;
  4114. &lt;p&gt;To fix this, many CLI agents will inject some extra text along with your prompt, something like &lt;code&gt;&amp;lt;current-date date=&quot;2025-10-08&quot; time=&quot;HH:MM:SS&quot;/&amp;gt;&lt;/code&gt;. This gives the LLM the context it needs.&lt;/p&gt;
  4115. &lt;p&gt;So how could use ACP to build that? The idea is to create a &lt;strong&gt;proxy&lt;/strong&gt;. This proxy would wrap the original ACP server:&lt;/p&gt;
  4116. &lt;pre class=&quot;mermaid&quot;&gt;flowchart LR
  4117.    Editor[Editor/VSCode] &amp;lt;--&amp;gt;|ACP| Proxy[Datetime Proxy] &amp;lt;--&amp;gt;|ACP| Agent[CLI Agent]
  4118.  &lt;/pre&gt;
  4119. &lt;p&gt;This proxy will take every “prompt” message it receives and decorate it with the date and time:&lt;/p&gt;
  4120. &lt;pre class=&quot;mermaid&quot;&gt;sequenceDiagram
  4121.    participant E as Editor
  4122.    participant P as Proxy
  4123.    participant A as Agent
  4124.    
  4125.    E-&amp;gt;&amp;gt;P: prompt(&quot;What day is it?&quot;)
  4126.    P-&amp;gt;&amp;gt;A: prompt(&quot;&amp;lt;current-date .../&amp;gt; What day is it?&quot;)
  4127.    A-&amp;gt;&amp;gt;P: text_chunk(&quot;It is 2025-10-08.&quot;)
  4128.    P-&amp;gt;&amp;gt;E: text_chunk(&quot;It is 2025-10-08.&quot;)
  4129.    A-&amp;gt;&amp;gt;P: end_turn
  4130.    P-&amp;gt;&amp;gt;E: end_turn
  4131.  &lt;/pre&gt;
  4132. &lt;p&gt;Simple, right? And of course this can be used with any editor and any ACP-speaking tool.&lt;/p&gt;
  4133. &lt;h3&gt;Next feature: Injecting “personality” to the agent&lt;/h3&gt;
  4134. &lt;p&gt;Let’s look at another feature that basically “falls out” from ACP: injecting personality. Most agents give you the ability to configure “context” in various ways – or what Claude Code calls &lt;a href=&quot;https://docs.claude.com/en/docs/claude-code/memory&quot;&gt;memory&lt;/a&gt;. This is useful, but I and others have noticed that if what you want is to change how Claude “behaves” – i.e., to make it more collaborative – it’s not really enough. You really need to kick off the conversation by reinforcing that pattern.&lt;/p&gt;
  4135. &lt;p&gt;In Symposium, &lt;a href=&quot;https://github.com/symposium-dev/symposium/blob/7f437fdf02ab52cd0bd3070d25feaad387b6d23f/symposium/mcp-server/src/server.rs#L885&quot;&gt;the “yiasou” prompt&lt;/a&gt; (also available as “hi”, for those of you who don’t speak Greek 😛) is meant to be run as the first thing in the conversation. But there’s nothing an MCP server can do to &lt;em&gt;ensure&lt;/em&gt; that the user kicks off the conversation with &lt;code&gt;/symposium:hi&lt;/code&gt; or something similar. Of course, if Symposium were implemented as an ACP Server, we absolutely could do that:&lt;/p&gt;
  4136. &lt;pre class=&quot;mermaid&quot;&gt;sequenceDiagram
  4137.    participant E as Editor
  4138.    participant P as Proxy
  4139.    participant A as Agent
  4140.    
  4141.    E-&amp;gt;&amp;gt;P: prompt(&quot;I'd like to work on my document&quot;)
  4142.    P-&amp;gt;&amp;gt;A: prompt(&quot;/symposium:hi&quot;)
  4143.    A-&amp;gt;&amp;gt;P: end_turn
  4144.    P-&amp;gt;&amp;gt;A: prompt(&quot;I'd like to work on my document&quot;)
  4145.    A-&amp;gt;&amp;gt;P: text_chunk(&quot;Sure! What document is that?&quot;)
  4146.    P-&amp;gt;&amp;gt;E: text_chunk(&quot;Sure! What document is that?&quot;)
  4147.    A-&amp;gt;&amp;gt;P: end_turn
  4148.    P-&amp;gt;&amp;gt;E: end_turn
  4149.  &lt;/pre&gt;
  4150. &lt;h3&gt;Proxies are a better version of hooks&lt;/h3&gt;
  4151. &lt;p&gt;Some of you may be saying, “hmm, isn’t that what &lt;a href=&quot;https://docs.claude.com/en/docs/claude-code/hooks&quot;&gt;hooks&lt;/a&gt; are for?” And yes, you could do this with hooks, but there’s two problems with that. First, hooks are non-standard, so you have to do it differently for every agent.&lt;/p&gt;
  4152. &lt;p&gt;The second problem with hooks is that they’re &lt;strong&gt;fundamentally limited&lt;/strong&gt; to what the hook designer envisioned you might want. You only get hooks at the places in the workflow that the tool gives you, and you can only control what the tool lets you control. The next feature starts to show what I mean: as far as I know, it cannot readily be implemented with hooks the way I would want it to work.&lt;/p&gt;
  4153. &lt;h3&gt;Next feature: long-running, asynchronous tasks&lt;/h3&gt;
  4154. &lt;p&gt;Let’s move on to our next feature, long-running asynchronous tasks. This feature is going to have to go beyond the current capabilities of ACP into the expanded “SymmACP” feature set.&lt;/p&gt;
  4155. &lt;p&gt;Right now, when the server invokes an MCP tool, it executes in a blocking way. But sometimes the task it is performing might be long and complicated. What you would really like is a way to “start” the task and then go back to working. When the task is complete, you (and the agent) could be notified.&lt;/p&gt;
  4156. &lt;p&gt;This comes up for me a lot with “deep research”. A big part of my workflow is that, when I get stuck on something I don’t understand, I deploy a research agent to scour the web for information. Usually what I will do is ask the agent I’m collaborating with to prepare a research prompt summarizing the things we tried, what obstacles we hit, and other details that seem relevant. Then I’ll pop over to &lt;a href=&quot;https://claude.ai/&quot;&gt;claude.ai&lt;/a&gt; or &lt;a href=&quot;https://gemini.google.com/&quot;&gt;Gemini Deep Research&lt;/a&gt; and paste in the prompt. This will run for 5-10 minutes and generate a markdown report in response. I’ll download that and give it to my agent. Very often this lets us solve the problem.&lt;sup id=&quot;fnref:2&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:2&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
  4157. &lt;p&gt;This research flow works well but it is tedious and requires me to copy-and-paste. What I would ideally want is an MCP tool that does the search for me and, when the results are done, hands them off to the agent so it can start processing immediately. But in the meantime, I’d like to be able to continue working with the agent while we wait. Unfortunately, the protocol for tools provides no mechanism for asynchronous notifications like this, from what I can tell.&lt;/p&gt;
  4158. &lt;h3&gt;SymmACP += tool invocations + unprompted sends&lt;/h3&gt;
  4159. &lt;p&gt;So how would I do it with SymmACP? Well, I would want to extend the ACP protocol as it is today in two ways:&lt;/p&gt;
  4160. &lt;ol&gt;
  4161. &lt;li&gt;I’d like the ACP proxy to be able to provide tools that &lt;em&gt;the proxy&lt;/em&gt; will execute. Today, the agent is responsible for executing all tools; the ACP protocol only comes into play when requesting &lt;em&gt;permission&lt;/em&gt;. But it’d be trivial to have MCP tools where, to execute the tool, the agent sends back a message over ACP instead.&lt;/li&gt;
  4162. &lt;li&gt;I’d like to have a way for the &lt;em&gt;agent&lt;/em&gt; to initiate responses to the &lt;em&gt;editor&lt;/em&gt;. Right now, the editor always initiatives each communication session with a prompt; but, in this case, the agent might want to send messages back unprompted.&lt;/li&gt;
  4163. &lt;/ol&gt;
  4164. &lt;p&gt;In that case, we could implement our Research Proxy like so:&lt;/p&gt;
  4165. &lt;pre class=&quot;mermaid&quot;&gt;sequenceDiagram
  4166.    participant E as Editor
  4167.    participant P as Proxy
  4168.    participant A as Agent
  4169.    
  4170.    E-&amp;gt;&amp;gt;P: prompt(&quot;Why is Rust so great?&quot;)
  4171.    P-&amp;gt;&amp;gt;A: prompt(&quot;Why is Rust so great?&quot;)
  4172.    A-&amp;gt;&amp;gt;P: invoke tool(&quot;begin_research&quot;)
  4173.    activate P
  4174.    P-&amp;gt;&amp;gt;A: ok
  4175.    A-&amp;gt;&amp;gt;P: &quot;I'm looking into it!&quot;
  4176.    P-&amp;gt;&amp;gt;E: &quot;I'm looking into it!&quot;
  4177.    A-&amp;gt;&amp;gt;P: end_turn
  4178.    P-&amp;gt;&amp;gt;E: end_turn
  4179.  
  4180.    Note over E,A: Time passes (5-10 minutes) and the user keeps working...
  4181.    Note over P: Research completes in background
  4182.    
  4183.    P-&amp;gt;&amp;gt;A: &amp;lt;research-complete/&amp;gt;
  4184.    deactivate P
  4185.    A-&amp;gt;&amp;gt;P: &quot;Research says Rust is fast&quot;
  4186.    P-&amp;gt;&amp;gt;E: &quot;Research says Rust is fast&quot;
  4187.    A-&amp;gt;&amp;gt;P: end_turn
  4188.    P-&amp;gt;&amp;gt;E: end_turn
  4189.  &lt;/pre&gt;
  4190. &lt;p&gt;What’s cool about this is that the proxy encapsulates the entire flow: it knows how to do the research, and it manages notifying the various participants when the research completes. (Also, this leans on one detail I left out, which is that )&lt;/p&gt;
  4191. &lt;h3&gt;Next feature: tangent mode&lt;/h3&gt;
  4192. &lt;p&gt;Let’s explore our next feature, &lt;a href=&quot;https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-experimental-features.html&quot;&gt;Q CLI’s &lt;code&gt;/tangent&lt;/code&gt; mode&lt;/a&gt;. This feature is interesting because it’s a simple (but useful!) example of history editing. The way &lt;code&gt;/tangent&lt;/code&gt; works is that, when you first type &lt;code&gt;/tangent&lt;/code&gt;, Q CLI saves your current state. You can then continue as normal but when you &lt;em&gt;next&lt;/em&gt; type &lt;code&gt;/tangent&lt;/code&gt;, your state is restored to where you were. This, as the name suggests, lets you explore a side conversation without polluting your main context.&lt;/p&gt;
  4193. &lt;p&gt;The basic idea for supporting tangent in SymmACP is that the proxy is going to (a) intercept the tangent prompt and remember where it began; (b) allow the conversation to continue as normal; and then (c) when it’s time to end the tangent, create a new session and replay the history up until the point of the tangent&lt;sup id=&quot;fnref:3&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:3&quot;&gt;3&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
  4194. &lt;h3&gt;SymACP += replay&lt;/h3&gt;
  4195. &lt;p&gt;You can &lt;em&gt;almost&lt;/em&gt; implement “tangent” in ACP as it is, but not quite. In ACP, the agent always owns the session history. The editor can create a new session or load an older one; when loading an older one, the agent “replays” “replays” the events so that the editor can reconstruct the GUI. But there is no way for the &lt;em&gt;editor&lt;/em&gt; to “replay” or construct a session to the &lt;em&gt;agent&lt;/em&gt;. Instead, the editor can only send prompts, which will cause the agent to reply. In this case, what we want is to be able to say “create a new chat in which I said this and you responded that” so that we can setup the initial state. This way we could easily create a new session that contains the messages from the old one.&lt;/p&gt;
  4196. &lt;p&gt;So how this would work:&lt;/p&gt;
  4197. &lt;pre class=&quot;mermaid&quot;&gt;sequenceDiagram
  4198.    participant E as Editor
  4199.    participant P as Proxy
  4200.    participant A as Agent
  4201.    
  4202.    E-&amp;gt;&amp;gt;P: prompt(&quot;Hi there!&quot;)
  4203.    P-&amp;gt;&amp;gt;A: prompt(&quot;Hi there!&quot;)
  4204.  
  4205.    Note over E,A: Conversation proceeds
  4206.    
  4207.    E-&amp;gt;&amp;gt;P: prompt(&quot;/tangent&quot;)
  4208.    Note over P: Proxy notes conversation state
  4209.    P-&amp;gt;&amp;gt;E: end_turn
  4210.    E-&amp;gt;&amp;gt;P: prompt(&quot;btw, ...&quot;)
  4211.    P-&amp;gt;&amp;gt;A: prompt(&quot;btw, ...&quot;)
  4212.  
  4213.    Note over E,A: Conversation proceeds
  4214.    
  4215.    E-&amp;gt;&amp;gt;P: prompt(&quot;/tangent&quot;)
  4216.    
  4217.    P-&amp;gt;&amp;gt;A: new_session
  4218.    P-&amp;gt;&amp;gt;A: prompt(&quot;Hi there!&quot;)    
  4219.    Note over P,A: ...Proxy replays conversation...
  4220.  &lt;/pre&gt;
  4221. &lt;h3&gt;Next feature: interactive walkthroughs&lt;/h3&gt;
  4222. &lt;p&gt;One of the nicer features of Symposium is the ability to do &lt;a href=&quot;https://symposium-dev.github.io/symposium/get-started/walkthroughs.html&quot;&gt;interactive walkthroughs&lt;/a&gt;. These consist of an HTML sidebar as well as inline comments in the code:&lt;/p&gt;
  4223. &lt;img alt=&quot;Walkthrough screenshot&quot; src=&quot;https://smallcultfollowing.com/babysteps/ /assets/2025-symmacp/walkthrough.png&quot; width=&quot;100%&quot; /&gt;
  4224. &lt;p&gt;Right now, this is implemented by a kind of hacky dance:&lt;/p&gt;
  4225. &lt;ul&gt;
  4226. &lt;li&gt;The agent invokes an MCP tool and sends it the walkthrough in markdown. This markdown includes commands meant to be placed on particular lines, identified not by line number (agents are bad at line numbers) but by symbol names or search strings.&lt;/li&gt;
  4227. &lt;li&gt;The MCP tool parses the markdown, determines the line numbers for comments, and creates HTML. It sends that HTML over IPC to the VSCode extension.&lt;/li&gt;
  4228. &lt;li&gt;The VSCode receives the IPC message, displays the HTML in the sidebar, and creates the comments in the code.&lt;/li&gt;
  4229. &lt;/ul&gt;
  4230. &lt;p&gt;It works, but it’s a giant Rube Goldberg machine.&lt;/p&gt;
  4231. &lt;h3&gt;SymmACP += Enriched conversation history&lt;/h3&gt;
  4232. &lt;p&gt;With SymmACP, we would structure the passthrough mechanism as a proxy. Just as today, it would provide an MCP tool to the agent to receive the walkthrough markdown. It would then convert that into the HTML to display on the side along with the various comments to embed in the code. But this is where things are different.&lt;/p&gt;
  4233. &lt;p&gt;Instead of sending that content over IPC, what I would want to do is to make it possible for proxies to deliver extra information along with the chat. This is relatively easy to do in ACP as is, since it provides for various capabilities, but I think I’d want to go one step further&lt;/p&gt;
  4234. &lt;p&gt;I would have a proxy layer that manages walkthroughs. As we saw before, it would provide a tool. But there’d be one additional thing, which is that, beyond just a chat history, it would be able to convey additional state. I think the basic conversation structure is like:&lt;/p&gt;
  4235. &lt;ul&gt;
  4236. &lt;li&gt;Conversation
  4237. &lt;ul&gt;
  4238. &lt;li&gt;Turn
  4239. &lt;ul&gt;
  4240. &lt;li&gt;User prompt(s) – could be zero or more&lt;/li&gt;
  4241. &lt;li&gt;Response(s) – could be zero or more&lt;/li&gt;
  4242. &lt;li&gt;Tool use(s) – could be zero or more&lt;/li&gt;
  4243. &lt;/ul&gt;
  4244. &lt;/li&gt;
  4245. &lt;/ul&gt;
  4246. &lt;/li&gt;
  4247. &lt;/ul&gt;
  4248. &lt;p&gt;but I think it’d be useful to (a) be able to attach metadata to any of those things, e.g., to add extra context &lt;em&gt;about the conversation&lt;/em&gt; or &lt;em&gt;about a specific turn&lt;/em&gt; (or even a specific &lt;em&gt;prompt&lt;/em&gt;), but also additional kinds of events. For example, tool approvals are an &lt;em&gt;event&lt;/em&gt;. And presenting a walkthrough and adding annotations are an event too.&lt;/p&gt;
  4249. &lt;p&gt;The way I imagine it, one of the core things in SymmACP would be the ability to serialize your state to JSON. You’d be able to ask a SymmACP paricipant to summarize a session. They would in turn ask any delegates to summarize and then add their own metadata along the way. You could also send the request in the &lt;em&gt;other&lt;/em&gt; direction – e.g., the agent might present its state to the editor and ask it to augment it.&lt;/p&gt;
  4250. &lt;h3&gt;Enriched history would let walkthroughs be extra metadata&lt;/h3&gt;
  4251. &lt;p&gt;This would mean a walkthrough proxy could add extra metadata into the chat transcript like “the current walkthrough” and “the current comments that are in place”. Then the &lt;em&gt;editor&lt;/em&gt; would either &lt;em&gt;know&lt;/em&gt; about that metadata or not. If it doesn’t, you wouldn’t see it in your chat. Oh well – or perhaps we do something HTML like, where there’s a way to “degrade gracefully” (e.g., the walkthrough could be presented as a regular “response” but with some metadata that, if you know to look, tells you to interpret it differently). But if the editor DOES know about the metadata, it interprets it specially, throwing the walkthrough up in a panel and adding the comments into the code.&lt;/p&gt;
  4252. &lt;p&gt;With enriched histories, I think we can even say that in SymmACP, the ability to load, save, and persist sessions &lt;em&gt;itself&lt;/em&gt; becomes an extension, something that can be implemented by a proxy; the base protocol only needs the ability to conduct and serialize a conversation.&lt;/p&gt;
  4253. &lt;h3&gt;Final feature: Smarter tool delegation.&lt;/h3&gt;
  4254. &lt;p&gt;Let me sketch out another feature that I’ve been noodling on that I think would be pretty cool. It’s well known that there’s a problem that LLMs get confused when there are too many MCP tools available. They get distracted. And that’s sensible, so would I, if I were given a phonebook-size list of possible things I could do and asked to figure something out. I’d probably just ignore it.&lt;/p&gt;
  4255. &lt;p&gt;But how do humans deal with this? Well, we don’t take the whole phonebook – we got a shorter list of &lt;em&gt;categories&lt;/em&gt; of options and then we drill down. So I go to the File Menu and &lt;em&gt;then&lt;/em&gt; I get a list of options, not a flat list of commands.&lt;/p&gt;
  4256. &lt;p&gt;I wanted to try building an MCP tool for IDE capabilities that was similar. There’s a bajillion set of things that a modern IDE can “do”. It can find references. It can find definitions. It can get type hints. It can do renames. It can extract methods. In fact, the list is even open-ended, since extensions can provide their &lt;em&gt;own&lt;/em&gt; commands. I don’t know what all those things &lt;em&gt;are&lt;/em&gt; but I have a sense for the &lt;em&gt;kinds of things&lt;/em&gt; an IDE can do – and I suspect models do too.&lt;/p&gt;
  4257. &lt;p&gt;What if you gave them a single tool, “IDE operation”, and they could use plain English to describe what they want? e.g., &lt;code&gt;ide_operation(&quot;find definition for the ProxyHandler that referes to HTTP proxies&quot;)&lt;/code&gt;. Hmm, this is sounding a lot like a delegate, or a sub-agent. Because now you need to use a second LLM to interpret that request – you probably want to do something like, give it a list of sugested IDE capabilities and the ability to find out full details and ask it to come up with a plan (or maybe directly execute the tools) to find the answer.&lt;/p&gt;
  4258. &lt;p&gt;As it happens, MCP &lt;em&gt;has&lt;/em&gt; a capability to enable tools to do this – it’s called (somewhat oddly, in my opinion) “sampling”. It allows for “callbacks” from the MCP tool to the LLM. But literally &lt;em&gt;nobody&lt;/em&gt; implements it, from what I can tell.&lt;sup id=&quot;fnref:4&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:4&quot;&gt;4&lt;/a&gt;&lt;/sup&gt; But sampling is kind of limited anyway. With SymmACP, I think you could do much more interesting things.&lt;/p&gt;
  4259. &lt;h3&gt;SymmACP.contains(simultaneous_sessions)&lt;/h3&gt;
  4260. &lt;p&gt;The key is that ACP already permits a single agent to “serve up” many simultaneous sessions. So that means that if I have a proxy, perhaps one supplying an MCP tool definition, I could use it to start &lt;em&gt;fresh&lt;/em&gt; sessions – combine that with the “history replay” capability I mentioned above, and the tool can control exactly what context to bring over into that session to start from, as well, which is very cool (that’s a challenge for MCP servers today, they don’t get access to the conversation history).&lt;/p&gt;
  4261. &lt;pre class=&quot;mermaid&quot;&gt;sequenceDiagram
  4262.    participant E as Editor
  4263.    participant P as Proxy
  4264.    participant A as Agent
  4265.    
  4266.    A-&amp;gt;&amp;gt;P: ide_operation(&quot;...&quot;)
  4267.    activate P
  4268.    P-&amp;gt;&amp;gt;A: new_session
  4269.    activate P
  4270.    activate A
  4271.    P-&amp;gt;&amp;gt;A: prompt(&quot;Using these primitive operations, suggest a way to do '...'&quot;)
  4272.    A-&amp;gt;&amp;gt;P: ...
  4273.    A-&amp;gt;&amp;gt;P: end_turn
  4274.    deactivate P
  4275.    deactivate A
  4276.    Note over P: performs the plan
  4277.    P-&amp;gt;&amp;gt;A: result from tool
  4278.    deactivate P
  4279.  &lt;/pre&gt;
  4280. &lt;h3&gt;Conclusion&lt;/h3&gt;
  4281. &lt;p&gt;Ok, this post sketched a variant on &lt;a href=&quot;https://agentclientprotocol.com/overview/introduction&quot;&gt;ACP&lt;/a&gt; that I call SymmACP. SymmACP extends ACP with&lt;/p&gt;
  4282. &lt;ul&gt;
  4283. &lt;li&gt;the ability for either side to provide the initial state of a conversation, not just the server&lt;/li&gt;
  4284. &lt;li&gt;the ability for an “editor” to provide an MCP tool to the “agent”&lt;/li&gt;
  4285. &lt;li&gt;the ability for agents to respond without an initial prompt&lt;/li&gt;
  4286. &lt;li&gt;the ability to serialize conversations and attach extra state (already kind of present)&lt;/li&gt;
  4287. &lt;/ul&gt;
  4288. &lt;p&gt;Most of these are modest extensions to ACP, in my opinion, and easily doable in a backwards fashion just by adding new capabilities. &lt;strong&gt;But together they unlock the ability for anyone to craft extensions to agents and deploy them in a composable way.&lt;/strong&gt; I am super excited about this. This is exactly what I wanted Symposium to be all about.&lt;/p&gt;
  4289. &lt;p&gt;It’s worth noting the old adage: “with great power, comes great responsibility”. These proxies and ACP layers I’ve been talking about are really like IDE extensions. They can effectively do &lt;em&gt;anything&lt;/em&gt; you could do. There are obvious security concerns. Though I think that approaches like Microsoft’s &lt;a href=&quot;https://opensource.microsoft.com/blog/2025/08/06/introducing-wassette-webassembly-based-tools-for-ai-agents/&quot;&gt;Wassette&lt;/a&gt; are key here – it’d be awesome to have a “capability-based” notion of what a “proxy layer” is, where everything compiles to WASM, and where users can tune what a given proxy can actually &lt;em&gt;do&lt;/em&gt;.&lt;/p&gt;
  4290. &lt;p&gt;I plan to start sketching a plan to drive this work in &lt;a href=&quot;https://symposium-dev.github.io/symposium/&quot;&gt;Symposium&lt;/a&gt; and elsewhere. My goal is to have a completely open and interopable client, one that can be based on any agent (including local ones) and where you can pick and choose which parts you want to use. I expect to build out lots of custom functionality to support Rust development (e.g., explaining and diagnosting trait errors using the new trait solver is high on my list…and macro errors…) but also to have other features like walkthroughs, collaborative interaction style, etc that are all language independent – and I’d love to see language-focused features for other langauges, especially Python and TypeScript (because &lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2025/07/31/rs-py-ts-trifecta/&quot;&gt;“the new trifecta”&lt;/a&gt;) and Swift and Kotlin (because mobile). If that vision excites you, come join the &lt;a href=&quot;https://symposium-dev.zulipchat.com/&quot;&gt;Symposium Zulip&lt;/a&gt; and let’s chat!&lt;/p&gt;
  4291. &lt;h3&gt;Appendix: A guide to the agent protocols I’m aware of&lt;/h3&gt;
  4292. &lt;p&gt;One question I’ve gotten when discussing this is how it compares to the other host of protocols out there. Let me give a brief overview of the related work and how I understand its pros and cons:&lt;/p&gt;
  4293. &lt;ul&gt;
  4294. &lt;li&gt;&lt;em&gt;&lt;a href=&quot;https://modelcontextprotocol.io/docs/getting-started/intro&quot;&gt;Model context protocol (MCP)&lt;/a&gt;:&lt;/em&gt; The queen of them all. A protocol that provides a set of tools, prompts, and resources up to the agent. Agents can invoke tools by supplying appropriate parameters, which are JSON. Prompts are shorthands that users can invoke using special commands like &lt;code&gt;/&lt;/code&gt; or &lt;code&gt;@&lt;/code&gt;, they are essentially macros that expand “as if the user typed it” (but they can also have parameters and be dynamically constructed). &lt;em&gt;Resources&lt;/em&gt; are just data that can be requested. MCP servers can either be local or hosted remotely. Remote MCP has only recently become an option and auth in particular is limited.
  4295. &lt;ul&gt;
  4296. &lt;li&gt;Comparison to SymmACP: MCP provides tools that the agent can invoke. SymmACP builds on it by allowing those tools to be provided by outer layers in the proxy chain. SymmACP is oriented at controlling the whole chat “experience”.&lt;/li&gt;
  4297. &lt;/ul&gt;
  4298. &lt;/li&gt;
  4299. &lt;li&gt;&lt;em&gt;&lt;a href=&quot;https://agentclientprotocol.com/overview/introduction&quot;&gt;Zed’s Agent Client Protocol (ACP)&lt;/a&gt;:&lt;/em&gt; The basis for SymmACP. Allows editors to create and manage sessions. Focused only on local sessions, since your editor runs locally.
  4300. &lt;ul&gt;
  4301. &lt;li&gt;Comparison to SymmACP: That’s what this post is all about! SymmACP extends ACP with new capabilities that let intermediate layers manipulate history, provide tools, and provide extended data upstream to support richer interaction patterns than jus chat. PS I expect we may want to support more remote capabilities, but it’s kinda orthogonal in my opinion (e.g., I’d like to be able to work with an agent running over in a cloud-hosted workstation, but I’d probably piggyback on ssh for that).&lt;/li&gt;
  4302. &lt;/ul&gt;
  4303. &lt;/li&gt;
  4304. &lt;li&gt;&lt;em&gt;&lt;a href=&quot;https://developers.googleblog.com/en/a2a-a-new-era-of-agent-interoperability/&quot;&gt;Google’s Agent-to-Agent Protocol (A2A)&lt;/a&gt; and &lt;a href=&quot;https://www.ibm.com/think/topics/agent-communication-protocol&quot;&gt;IBM’s Agent Communication Protocol (ACP)&lt;/a&gt;&lt;sup id=&quot;fnref:5&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:5&quot;&gt;5&lt;/a&gt;&lt;/sup&gt;:&lt;/em&gt; From what I can tell, Google’s “agent-to-agent” protocol is &lt;em&gt;kinda&lt;/em&gt; like a mix of MCP and OpenAPI. You can ping agents that are running remotely and get them to send you “agent cards”, which describe what operations they can perform, how you authenticate, and other stuff like that. It looks to me quite similar to MCP except that it has richer support for remote execution and in particular supports things like long-running communication, where an agent may need to go off and work for a while and then ping you back on a webhook.
  4305. &lt;ul&gt;
  4306. &lt;li&gt;&lt;em&gt;Comparison to MCP:&lt;/em&gt; To me, A2A looks like a variant of MCP that is more geared to remote execution. MCP has a method for tool discovery where you ping the server to get a list of tools; A2A has a similar mechanism with Agent Cards. MCP can run locally, which A2A cannot afaik, but A2A has more options about auth. MCP can only be invoked synchronously, whereas A2A supports long-running operations, progress updates, and callbacks. It seems like the two could be merged to make a single whole.&lt;/li&gt;
  4307. &lt;li&gt;&lt;em&gt;Comparison to SymmACP:&lt;/em&gt; I think A2A is orthogonal from SymmACP. A2A is geared to agents that provide services to one another. SymmACP is geared towards building new development tools for interacting with agents. It’s possible you could build something like SymmACP &lt;em&gt;on&lt;/em&gt; A2A but I don’t know what you would really gain by it (and I think it’d be easy to do later).&lt;/li&gt;
  4308. &lt;/ul&gt;
  4309. &lt;/li&gt;
  4310. &lt;/ul&gt;
  4311. &lt;div class=&quot;footnotes&quot;&gt;
  4312. &lt;hr /&gt;
  4313. &lt;ol&gt;
  4314. &lt;li id=&quot;fn:1&quot;&gt;
  4315. &lt;p&gt;Everybody uses agents in various ways. I like Simon Willison’s &lt;a href=&quot;https://simonwillison.net/2025/May/22/tools-in-a-loop/&quot;&gt;“agents are models using tools in a loop”&lt;/a&gt; definition; I feel that an “agentic CLI tool” fits that definition, it’s just that part of the loop is reading input from the user. I think “fully autonomous” agents are a subset of all agents – many agent processes interact with the outside world via tools etc. From a certain POV, you can view the agent “ending the turn” as invoking a tool for “gimme the next prompt”. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:1&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  4316. &lt;/li&gt;
  4317. &lt;li id=&quot;fn:2&quot;&gt;
  4318. &lt;p&gt;Research reports are a &lt;strong&gt;major&lt;/strong&gt; part of how I avoid hallucination. You can see an example of one such report I commissioned on the &lt;a href=&quot;https://symposium-dev.github.io/symposium/research/lsp-overview/index.html&quot;&gt;details of the Language Server Protocol here&lt;/a&gt;; if we were about to embark on something that required detailed knowledge of LSP, I would ask the agent to read that report first. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:2&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  4319. &lt;/li&gt;
  4320. &lt;li id=&quot;fn:3&quot;&gt;
  4321. &lt;p&gt;Alternatively: clear the session history and rebuild it, but I kind of prefer the functional view of the world, where a given session never changes. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:3&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  4322. &lt;/li&gt;
  4323. &lt;li id=&quot;fn:4&quot;&gt;
  4324. &lt;p&gt;I started an implementation for Q CLI but got distracted – and, for reasons that should be obvious, I’ve started to lose interest. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:4&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  4325. &lt;/li&gt;
  4326. &lt;li id=&quot;fn:5&quot;&gt;
  4327. &lt;p&gt;Yes, you read that right. There is another ACP. Just a mite confusing when you google search. =) &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:5&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  4328. &lt;/li&gt;
  4329. &lt;/ol&gt;
  4330. &lt;/div&gt;</description>
  4331. <pubDate>Wed, 08 Oct 2025 08:54:08 +0000</pubDate>
  4332. </item>
  4333. <item>
  4334. <title>This Week In Rust: This Week in Rust 620</title>
  4335. <guid isPermaLink="false">tag:this-week-in-rust.org,2025-10-08:/blog/2025/10/08/this-week-in-rust-620/</guid>
  4336. <link>https://this-week-in-rust.org/blog/2025/10/08/this-week-in-rust-620/</link>
  4337. <description>&lt;p&gt;Hello and welcome to another issue of &lt;em&gt;This Week in Rust&lt;/em&gt;!
  4338. &lt;a href=&quot;https://www.rust-lang.org/&quot;&gt;Rust&lt;/a&gt; is a programming language empowering everyone to build reliable and efficient software.
  4339. This is a weekly summary of its progress and community.
  4340. Want something mentioned? Tag us at
  4341. &lt;a href=&quot;https://bsky.app/profile/thisweekinrust.bsky.social&quot;&gt;@thisweekinrust.bsky.social&lt;/a&gt; on Bluesky or
  4342. &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;@ThisWeekinRust&lt;/a&gt; on mastodon.social, or
  4343. &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;send us a pull request&lt;/a&gt;.
  4344. Want to get involved? &lt;a href=&quot;https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md&quot;&gt;We love contributions&lt;/a&gt;.&lt;/p&gt;
  4345. &lt;p&gt;&lt;em&gt;This Week in Rust&lt;/em&gt; is openly developed &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;on GitHub&lt;/a&gt; and archives can be viewed at &lt;a href=&quot;https://this-week-in-rust.org/&quot;&gt;this-week-in-rust.org&lt;/a&gt;.
  4346. If you find any errors in this week's issue, &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust/pulls&quot;&gt;please submit a PR&lt;/a&gt;.&lt;/p&gt;
  4347. &lt;p&gt;Want TWIR in your inbox? &lt;a href=&quot;https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&amp;amp;id=0ed8b72485&quot;&gt;Subscribe here&lt;/a&gt;.&lt;/p&gt;
  4348. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#updates-from-rust-community&quot;&gt;Updates from Rust Community&lt;/a&gt;&lt;/h4&gt;
  4349.  
  4350.  
  4351. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#projecttooling-updates&quot;&gt;Project/Tooling Updates&lt;/a&gt;&lt;/h5&gt;
  4352. &lt;ul&gt;
  4353. &lt;li&gt;&lt;a href=&quot;https://www.sea-ql.org/blog/2025-10-08-seaography/&quot;&gt;Seaography 2.0: A Powerful and Extensible GraphQL Framework&lt;/a&gt;&lt;/li&gt;
  4354. &lt;li&gt;&lt;a href=&quot;https://github.com/redis-rs/redis-rs/blob/redis-1.0.0-rc.0/version1.md&quot;&gt;Announcing redis-rs 1.0.0 release candidate&lt;/a&gt;&lt;/li&gt;
  4355. &lt;li&gt;&lt;a href=&quot;https://github.com/libbpf/blazesym/discussions/1318&quot;&gt;blazesym 0.2 stable release: batteries included address symbolization&lt;/a&gt;&lt;/li&gt;
  4356. &lt;li&gt;&lt;a href=&quot;https://lwn.net/SubscriberLink/1039784/d2548814efb78046/&quot;&gt;Kernel hackers at Cauldron, 2025 edition&lt;/a&gt;&lt;/li&gt;
  4357. &lt;li&gt;&lt;a href=&quot;https://lwn.net/SubscriberLink/1038757/d613acbb48f20a20/&quot;&gt;Progress on defeating lifetime-end pointer zapping&lt;/a&gt;&lt;/li&gt;
  4358. &lt;li&gt;&lt;a href=&quot;https://lwn.net/SubscriberLink/1039073/abf96f38b178f988/&quot;&gt;Upcoming Rust language features for kernel development&lt;/a&gt;&lt;/li&gt;
  4359. &lt;li&gt;&lt;a href=&quot;https://github.com/VincentVerdynanta/utsuru/releases/tag/v0.2.1&quot;&gt;utsuru: &quot;Go Live&quot; on Discord using OBS, FFmpeg, or anything that supports WHIP.&lt;/a&gt;&lt;/li&gt;
  4360. &lt;li&gt;&lt;a href=&quot;https://aladin.cds.unistra.fr/AladinLite/doc/&quot;&gt;Aladin Lite - navigate into TBs of astronomical data coming from various space missions&lt;/a&gt;&lt;/li&gt;
  4361. &lt;/ul&gt;
  4362. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#observationsthoughts&quot;&gt;Observations/Thoughts&lt;/a&gt;&lt;/h5&gt;
  4363. &lt;ul&gt;
  4364. &lt;li&gt;&lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2025/10/07/the-handle-trait/&quot;&gt;The Handle trait&lt;/a&gt;&lt;/li&gt;
  4365. &lt;li&gt;&lt;a href=&quot;https://www.wakunguma.com/blog/variadic-generics&quot;&gt;Variadic generics&lt;/a&gt;&lt;/li&gt;
  4366. &lt;li&gt;&lt;a href=&quot;https://tritium.legal/blog/word&quot;&gt;Thoughts on the Word Spec in Rust&lt;/a&gt;&lt;/li&gt;
  4367. &lt;li&gt;&lt;a href=&quot;https://medium.com/agoda-engineering/why-we-bet-on-rust-to-supercharge-feature-store-at-agoda-ed4a70d2efb7&quot;&gt;Why We Bet on Rust to Supercharge Feature Store at Agoda&lt;/a&gt;&lt;/li&gt;
  4368. &lt;li&gt;&lt;a href=&quot;https://nubskr.com/2025/10/06/walrus.html&quot;&gt;walrus: ingesting data at memory speeds&lt;/a&gt;&lt;/li&gt;
  4369. &lt;li&gt;&lt;a href=&quot;https://blog.inkreas.ing/realtime-concurrency&quot;&gt;Realtime concurrency primitives&lt;/a&gt;&lt;/li&gt;
  4370. &lt;li&gt;&lt;a href=&quot;https://databento.com/blog/why-we-didnt-rewrite-our-feed-handler-in-rust&quot;&gt;Why we didn't rewrite our feed handler in Rust&lt;/a&gt;&lt;/li&gt;
  4371. &lt;li&gt;[audio] &lt;a href=&quot;https://netstack.fm/#episode-7&quot;&gt;Netstack.FM Episode 7 – Rustls with Dirkjan Ochtman&lt;/a&gt;&lt;/li&gt;
  4372. &lt;li&gt;[audio] &lt;a href=&quot;https://netstack.fm/#episode-8&quot;&gt;Netstack.FM Episode 8 – Fuchsia's Netstack3 with Bruno Dal Bo Silva&lt;/a&gt;&lt;/li&gt;
  4373. &lt;/ul&gt;
  4374. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-walkthroughs&quot;&gt;Rust Walkthroughs&lt;/a&gt;&lt;/h5&gt;
  4375. &lt;ul&gt;
  4376. &lt;li&gt;&lt;a href=&quot;https://blog.0xshadow.dev/posts/backend-engineering-with-axum/axum-reset-password/&quot;&gt;Axum Backend Series: Implementing Password Reset&lt;/a&gt;&lt;/li&gt;
  4377. &lt;li&gt;&lt;a href=&quot;https://blog.0xshadow.dev/posts/backend-engineering-with-axum/axum-email-verification/&quot;&gt;Axum Backend Series: Email Verification After Registration&lt;/a&gt;&lt;/li&gt;
  4378. &lt;li&gt;&lt;a href=&quot;https://vaktibabat.github.io/posts/hyperloglog/&quot;&gt;Fun With HyperLogLog and SIMD&lt;/a&gt;&lt;/li&gt;
  4379. &lt;li&gt;&lt;a href=&quot;https://pawelurbanek.com/rust-optimize-performance&quot;&gt;How to automatically Profile Performance of Rust Applications&lt;/a&gt;&lt;/li&gt;
  4380. &lt;li&gt;&lt;a href=&quot;https://biriukov.dev/docs/async-rust-tokio-io/1-async-rust-with-tokio-io-streams-backpressure-concurrency-and-ergonomics/&quot;&gt;Async Rust with Tokio I/O Streams: Backpressure, Concurrency, and Ergonomics&lt;/a&gt;&lt;/li&gt;
  4381. &lt;li&gt;&lt;a href=&quot;https://www.svix.com/blog/preventing-db-misuse-at-compile-time/&quot;&gt;Preventing Invalid Database Access At Compile Time&lt;/a&gt;&lt;/li&gt;
  4382. &lt;li&gt;&lt;a href=&quot;https://jorgeortiz.dev/posts/rust_unit_testing_test_doubles_stub/&quot;&gt;Rust unit testing: test doubles &amp;amp; stubs&lt;/a&gt;&lt;/li&gt;
  4383. &lt;li&gt;&lt;a href=&quot;https://sunshowers.io/posts/cancelling-async-rust/&quot;&gt;Cancelling async Rust&lt;/a&gt;&lt;/li&gt;
  4384. &lt;li&gt;&lt;a href=&quot;https://kerkour.com/rust-pingoo-high-performance-allocations-mimalloc-heapless&quot;&gt;Behind the Scenes of Pingoo: Slashing allocations with mimalloc and heapless to build the fastest reverse proxy&lt;/a&gt;&lt;/li&gt;
  4385. &lt;li&gt;&lt;a href=&quot;https://michaelmauderer.com/blog/generic-numeric-computations/&quot;&gt;Generic Numeric Computations in Rust &lt;/a&gt;&lt;/li&gt;
  4386. &lt;li&gt;&lt;a href=&quot;https://hackeryarn.com/post/rust-macros-3/&quot;&gt;Let's write a macro in Rust - Part 3&lt;/a&gt;&lt;/li&gt;
  4387. &lt;li&gt;&lt;a href=&quot;https://tylerjw.dev/posts/20251003-rust-cpp-interop-2025-update/&quot;&gt;Rust/C++ Interop Part 5 - Interop in 2025: A Complete Example&lt;/a&gt;&lt;/li&gt;
  4388. &lt;/ul&gt;
  4389. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#miscellaneous&quot;&gt;Miscellaneous&lt;/a&gt;&lt;/h5&gt;
  4390. &lt;ul&gt;
  4391. &lt;li&gt;[videos] &lt;a href=&quot;https://www.youtube.com/playlist?list=PL2b0df3jKKiRFEuVNk76ufXagOgEJ9sBZ&quot;&gt;RustConf 2025&lt;/a&gt;&lt;/li&gt;
  4392. &lt;li&gt;[audio] &lt;a href=&quot;https://corrode.dev/podcast/s05e01-prime-video/&quot;&gt;Prime Video - Alexandru Ene, Principal Engineer&lt;/a&gt;&lt;/li&gt;
  4393. &lt;/ul&gt;
  4394. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#crate-of-the-week&quot;&gt;Crate of the Week&lt;/a&gt;&lt;/h4&gt;
  4395. &lt;p&gt;This week's crate is &lt;a href=&quot;https://crates.io/crates/tokio-netem&quot;&gt;tokio-netem&lt;/a&gt;, a toolbox of Tokio AsyncRead /AsyncWrite adapters to emulate latency, throttling, slicing, termination, forced shutdown, data injection and data corruption.&lt;/p&gt;
  4396. &lt;p&gt;Thanks to &lt;a href=&quot;https://users.rust-lang.org/t/crate-of-the-week/2704/1478&quot;&gt;Viacheslav Biriukov&lt;/a&gt; for the self-suggestion!&lt;/p&gt;
  4397. &lt;p&gt;&lt;a href=&quot;https://users.rust-lang.org/t/crate-of-the-week/2704&quot;&gt;Please submit your suggestions and votes for next week&lt;/a&gt;!&lt;/p&gt;
  4398. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#calls-for-testing&quot;&gt;Calls for Testing&lt;/a&gt;&lt;/h4&gt;
  4399. &lt;p&gt;An important step for RFC implementation is for people to experiment with the
  4400. implementation and give feedback, especially before stabilization.&lt;/p&gt;
  4401. &lt;p&gt;If you are a feature implementer and would like your RFC to appear in this list, add a
  4402. &lt;code&gt;call-for-testing&lt;/code&gt; label to your RFC along with a comment providing testing instructions and/or
  4403. guidance on which aspect(s) of the feature need testing.&lt;/p&gt;
  4404. &lt;ul&gt;
  4405. &lt;li&gt;&lt;em&gt;No calls for testing were issued this week by
  4406.  &lt;a href=&quot;https://github.com/rust-lang/rust/labels/call-for-testing&quot;&gt;Rust&lt;/a&gt;,
  4407.  &lt;a href=&quot;https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing&quot;&gt;Rust language RFCs&lt;/a&gt;,
  4408.  &lt;a href=&quot;https://github.com/rust-lang/cargo/labels/call-for-testing&quot;&gt;Cargo&lt;/a&gt; or
  4409.  &lt;a href=&quot;https://github.com/rust-lang/rustup/labels/call-for-testing&quot;&gt;Rustup&lt;/a&gt;.&lt;/em&gt;&lt;/li&gt;
  4410. &lt;/ul&gt;
  4411. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust/issues&quot;&gt;Let us know&lt;/a&gt; if you would like your feature to be tracked as a part of this list.&lt;/p&gt;
  4412. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing&quot;&gt;RFCs&lt;/a&gt;&lt;/h5&gt;
  4413. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/labels/call-for-testing&quot;&gt;Rust&lt;/a&gt;&lt;/h5&gt;
  4414. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rustup&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rustup/labels/call-for-testing&quot;&gt;Rustup&lt;/a&gt;&lt;/h5&gt;
  4415. &lt;p&gt;If you are a feature implementer and would like your RFC to appear on the above list, add the new &lt;code&gt;call-for-testing&lt;/code&gt;
  4416. label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
  4417. need testing.&lt;/p&gt;
  4418. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers&quot;&gt;Call for Participation; projects and speakers&lt;/a&gt;&lt;/h4&gt;
  4419. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cfp-projects&quot;&gt;CFP - Projects&lt;/a&gt;&lt;/h5&gt;
  4420. &lt;p&gt;Always wanted to contribute to open-source projects but did not know where to start?
  4421. Every week we highlight some tasks from the Rust community for you to pick and get started!&lt;/p&gt;
  4422. &lt;p&gt;Some of these tasks may also have mentors available, visit the task page for more information.&lt;/p&gt;
  4423.  
  4424.  
  4425. &lt;p&gt;&lt;em&gt;No Calls for participation were submitted this week.&lt;/em&gt;&lt;/p&gt;
  4426. &lt;p&gt;If you are a Rust project owner and are looking for contributors, please submit tasks &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines&quot;&gt;here&lt;/a&gt; or through a &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;PR to TWiR&lt;/a&gt; or by reaching out on &lt;a href=&quot;https://x.com/ThisWeekInRust&quot;&gt;X (formerly Twitter)&lt;/a&gt; or &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;Mastodon&lt;/a&gt;!&lt;/p&gt;
  4427. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cfp-events&quot;&gt;CFP - Events&lt;/a&gt;&lt;/h5&gt;
  4428. &lt;p&gt;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.&lt;/p&gt;
  4429. &lt;ul&gt;
  4430. &lt;li&gt;&lt;a href=&quot;https://tokio.rs/blog/2025-09-26-announcing-tokio-conf-cfp&quot;&gt;&lt;strong&gt;TokioConf 2026&lt;/strong&gt;&lt;/a&gt;| CFP closes 2025-12-08 | Portland, Oregon, USA | 2026-04-20&lt;/li&gt;
  4431. &lt;/ul&gt;
  4432.  
  4433.  
  4434.  
  4435. &lt;p&gt;If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;PR to TWiR&lt;/a&gt; or by reaching out on &lt;a href=&quot;https://x.com/ThisWeekInRust&quot;&gt;X (formerly Twitter)&lt;/a&gt; or &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;Mastodon&lt;/a&gt;!&lt;/p&gt;
  4436. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#updates-from-the-rust-project&quot;&gt;Updates from the Rust Project&lt;/a&gt;&lt;/h4&gt;
  4437. &lt;p&gt;398 pull requests were &lt;a href=&quot;https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2025-09-30..2025-10-07&quot;&gt;merged in the last week&lt;/a&gt;&lt;/p&gt;
  4438. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#compiler&quot;&gt;Compiler&lt;/a&gt;&lt;/h6&gt;
  4439. &lt;ul&gt;
  4440. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146596&quot;&gt;add a dummy codegen backend&lt;/a&gt;&lt;/li&gt;
  4441. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147299&quot;&gt;don't normalize higher-ranked assumptions if they're not used&lt;/a&gt;&lt;/li&gt;
  4442. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147231&quot;&gt;extending &lt;code&gt;#[rustc_force_inline]&lt;/code&gt; to be applicable to inherent methods&lt;/a&gt;&lt;/li&gt;
  4443. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147184&quot;&gt;fix the bevy implied bounds hack for the next solver&lt;/a&gt;&lt;/li&gt;
  4444. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146355&quot;&gt;Global Value Numbering: support unions&lt;/a&gt;&lt;/li&gt;
  4445. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/144477&quot;&gt;Global Value Numbering: use a VnIndex in Address projection&lt;/a&gt;&lt;/li&gt;
  4446. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/miri/pull/4611&quot;&gt;miri: add support for temporal mixing of atomic and non-atomic accesses in GenMC mode&lt;/a&gt;&lt;/li&gt;
  4447. &lt;/ul&gt;
  4448. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#library&quot;&gt;Library&lt;/a&gt;&lt;/h6&gt;
  4449. &lt;ul&gt;
  4450. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145685&quot;&gt;add &lt;code&gt;CloneFromCell&lt;/code&gt; and &lt;code&gt;Cell::get_cloned&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4451. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/142506&quot;&gt;add &lt;code&gt;Path::has_trailing_sep&lt;/code&gt; and related methods&lt;/a&gt;&lt;/li&gt;
  4452. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146479&quot;&gt;add &lt;code&gt;mem::conjure_zst&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4453. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/143069&quot;&gt;add fast-path for accessing the current thread id&lt;/a&gt;&lt;/li&gt;
  4454. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147227&quot;&gt;implement &lt;code&gt;Box::take&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4455. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147328&quot;&gt;implement non-poisoning &lt;code&gt;Mutex::with_mut&lt;/code&gt;, &lt;code&gt;RwLock::with&lt;/code&gt; and &lt;code&gt;RwLock::with_mut&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4456. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/hashbrown/pull/523&quot;&gt;hashbrown: recognize and use over sized allocations&lt;/a&gt;&lt;/li&gt;
  4457. &lt;/ul&gt;
  4458. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cargo&quot;&gt;Cargo&lt;/a&gt;&lt;/h6&gt;
  4459. &lt;ul&gt;
  4460. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16027&quot;&gt;&lt;code&gt;fix(run)&lt;/code&gt;: Override arg0 for cargo scripts&lt;/a&gt;&lt;/li&gt;
  4461. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16055&quot;&gt;&lt;code&gt;fix(timings)&lt;/code&gt;: compute codegen start time to draw dep lines&lt;/a&gt;&lt;/li&gt;
  4462. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16026&quot;&gt;&lt;code&gt;fix(toml)&lt;/code&gt;: Prevent non-script fields in Cargo scripts&lt;/a&gt;&lt;/li&gt;
  4463. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/15891&quot;&gt;accessing each build script's &lt;code&gt;OUT_DIR&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4464. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16041&quot;&gt;add panic=immediate-abort support to Cargo&lt;/a&gt;&lt;/li&gt;
  4465. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/15966&quot;&gt;consider public dependencies when choosing a version in cargo add (#1…&lt;/a&gt;&lt;/li&gt;
  4466. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16035&quot;&gt;convert a multi-part diagnostic to a report&lt;/a&gt;&lt;/li&gt;
  4467. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16046&quot;&gt;feat (publish): deprecate &lt;code&gt;--token&lt;/code&gt; option&lt;/a&gt;&lt;/li&gt;
  4468. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16036&quot;&gt;fix FileLock path tracking after rename in package operation&lt;/a&gt;&lt;/li&gt;
  4469. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16058&quot;&gt;fix &lt;code&gt;unsafe_op_in_unsafe_fn&lt;/code&gt; for Windows&lt;/a&gt;&lt;/li&gt;
  4470. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16025&quot;&gt;fix: remove FIXME comment that's no longer a problem&lt;/a&gt;&lt;/li&gt;
  4471. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16039&quot;&gt;lockfile schemas error cleanup&lt;/a&gt;&lt;/li&gt;
  4472. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16002&quot;&gt;public in private manifest errors&lt;/a&gt;&lt;/li&gt;
  4473. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/15806&quot;&gt;recommend &lt;code&gt;package.rust-version&lt;/code&gt; in the Rust version section of &lt;code&gt;reference/semver.md&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4474. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16052&quot;&gt;test: null-terminated path for reserved windows name detection&lt;/a&gt;&lt;/li&gt;
  4475. &lt;/ul&gt;
  4476. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rustdoc&quot;&gt;Rustdoc&lt;/a&gt;&lt;/h6&gt;
  4477. &lt;ul&gt;
  4478. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147189&quot;&gt;replace &lt;code&gt;rustc_span::Span&lt;/code&gt; with a stripped down version for librustdoc's highlighter&lt;/a&gt;&lt;/li&gt;
  4479. &lt;/ul&gt;
  4480. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#clippy&quot;&gt;Clippy&lt;/a&gt;&lt;/h6&gt;
  4481. &lt;ul&gt;
  4482. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15774&quot;&gt;&lt;code&gt;assertions_on_constants&lt;/code&gt;: Suggest using a const block when using a named constant&lt;/a&gt;&lt;/li&gt;
  4483. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15814&quot;&gt;&lt;code&gt;zero_repeat_side_effects&lt;/code&gt;: better identify exprs with side effects&lt;/a&gt;&lt;/li&gt;
  4484. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15773&quot;&gt;const eval changes&lt;/a&gt;&lt;/li&gt;
  4485. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15746&quot;&gt;do not suggest using a &lt;code&gt;if let&lt;/code&gt; chain if it is not supported&lt;/a&gt;&lt;/li&gt;
  4486. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15729&quot;&gt;do not trigger &lt;code&gt;inefficient_to_string&lt;/code&gt; after Rust 1.82&lt;/a&gt;&lt;/li&gt;
  4487. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15701&quot;&gt;extend &lt;code&gt;while_let_loop&lt;/code&gt; to &lt;code&gt;loop { let else }&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4488. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15783&quot;&gt;fix &lt;code&gt;if_then_some_else_none&lt;/code&gt; false positive when return exists in block expr&lt;/a&gt;&lt;/li&gt;
  4489. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15791&quot;&gt;fix &lt;code&gt;let_unit_value&lt;/code&gt; suggests wrongly for field init shorthand&lt;/a&gt;&lt;/li&gt;
  4490. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15786&quot;&gt;fix &lt;code&gt;mem_replace_with_default&lt;/code&gt; wrongly unmangled macros&lt;/a&gt;&lt;/li&gt;
  4491. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15686&quot;&gt;implement &lt;code&gt;volatile_composites&lt;/code&gt; lint&lt;/a&gt;&lt;/li&gt;
  4492. &lt;/ul&gt;
  4493. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-analyzer&quot;&gt;Rust-Analyzer&lt;/a&gt;&lt;/h6&gt;
  4494. &lt;ul&gt;
  4495. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/141839&quot;&gt;make rust-analyzer use a dedicated build directory&lt;/a&gt;&lt;/li&gt;
  4496. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20794&quot;&gt;deduplicate sort+dedup calls&lt;/a&gt;&lt;/li&gt;
  4497. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20806&quot;&gt;log flycheck stdout and stderr to files&lt;/a&gt;&lt;/li&gt;
  4498. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20793&quot;&gt;fix missing parentheses for &lt;code&gt;missing_unsafe&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4499. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20777&quot;&gt;fix panic when using analysis-stats&lt;/a&gt;&lt;/li&gt;
  4500. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20787&quot;&gt;fix erroneous diagnostic &lt;code&gt;incorrect_generics_len&lt;/code&gt; when there are generics on &lt;code&gt;enum&lt;/code&gt; variant used through type alias&lt;/a&gt;&lt;/li&gt;
  4501. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20770&quot;&gt;ignore impl trait safety errors when the trait is unresolved&lt;/a&gt;&lt;/li&gt;
  4502. &lt;/ul&gt;
  4503. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage&quot;&gt;Rust Compiler Performance Triage&lt;/a&gt;&lt;/h5&gt;
  4504. &lt;p&gt;Largely a positive week. Big win coming from avoiding unnecessary work for debug log in &lt;a href=&quot;https://github.com/rust-lang/rust/pull/147293&quot;&gt;#147293&lt;/a&gt;, and another one for rustdoc from optimized span representation for highlighter &lt;a href=&quot;https://github.com/rust-lang/rust/pull/147189&quot;&gt;#147189&lt;/a&gt;. Lots of noisy results otherwise.&lt;/p&gt;
  4505. &lt;p&gt;Triage done by &lt;strong&gt;@panstromek&lt;/strong&gt;.
  4506. Revision range: &lt;a href=&quot;https://perf.rust-lang.org/?start=8d72d3e1e96f58ca10059a6bb6e8aecba4a0e9cd&amp;amp;end=1a3cdd34629306fa67624eaa60d73687e7fcf855&amp;amp;absolute=false&amp;amp;stat=instructions%3Au&quot;&gt;8d72d3e1..1a3cdd34&lt;/a&gt;&lt;/p&gt;
  4507. &lt;p&gt;&lt;strong&gt;Summary&lt;/strong&gt;:&lt;/p&gt;
  4508. &lt;table&gt;
  4509. &lt;thead&gt;
  4510. &lt;tr&gt;
  4511. &lt;th align=&quot;center&quot;&gt;(instructions:u)&lt;/th&gt;
  4512. &lt;th align=&quot;center&quot;&gt;mean&lt;/th&gt;
  4513. &lt;th align=&quot;center&quot;&gt;range&lt;/th&gt;
  4514. &lt;th align=&quot;center&quot;&gt;count&lt;/th&gt;
  4515. &lt;/tr&gt;
  4516. &lt;/thead&gt;
  4517. &lt;tbody&gt;
  4518. &lt;tr&gt;
  4519. &lt;td align=&quot;center&quot;&gt;Regressions ❌ &lt;br /&gt; (primary)&lt;/td&gt;
  4520. &lt;td align=&quot;center&quot;&gt;0.5%&lt;/td&gt;
  4521. &lt;td align=&quot;center&quot;&gt;[0.2%, 2.0%]&lt;/td&gt;
  4522. &lt;td align=&quot;center&quot;&gt;10&lt;/td&gt;
  4523. &lt;/tr&gt;
  4524. &lt;tr&gt;
  4525. &lt;td align=&quot;center&quot;&gt;Regressions ❌ &lt;br /&gt; (secondary)&lt;/td&gt;
  4526. &lt;td align=&quot;center&quot;&gt;0.4%&lt;/td&gt;
  4527. &lt;td align=&quot;center&quot;&gt;[0.0%, 0.8%]&lt;/td&gt;
  4528. &lt;td align=&quot;center&quot;&gt;50&lt;/td&gt;
  4529. &lt;/tr&gt;
  4530. &lt;tr&gt;
  4531. &lt;td align=&quot;center&quot;&gt;Improvements ✅ &lt;br /&gt; (primary)&lt;/td&gt;
  4532. &lt;td align=&quot;center&quot;&gt;-1.3%&lt;/td&gt;
  4533. &lt;td align=&quot;center&quot;&gt;[-5.3%, -0.2%]&lt;/td&gt;
  4534. &lt;td align=&quot;center&quot;&gt;147&lt;/td&gt;
  4535. &lt;/tr&gt;
  4536. &lt;tr&gt;
  4537. &lt;td align=&quot;center&quot;&gt;Improvements ✅ &lt;br /&gt; (secondary)&lt;/td&gt;
  4538. &lt;td align=&quot;center&quot;&gt;-1.3%&lt;/td&gt;
  4539. &lt;td align=&quot;center&quot;&gt;[-12.7%, -0.1%]&lt;/td&gt;
  4540. &lt;td align=&quot;center&quot;&gt;111&lt;/td&gt;
  4541. &lt;/tr&gt;
  4542. &lt;tr&gt;
  4543. &lt;td align=&quot;center&quot;&gt;All ❌✅ (primary)&lt;/td&gt;
  4544. &lt;td align=&quot;center&quot;&gt;-1.2%&lt;/td&gt;
  4545. &lt;td align=&quot;center&quot;&gt;[-5.3%, 2.0%]&lt;/td&gt;
  4546. &lt;td align=&quot;center&quot;&gt;157&lt;/td&gt;
  4547. &lt;/tr&gt;
  4548. &lt;/tbody&gt;
  4549. &lt;/table&gt;
  4550. &lt;p&gt;6 Regressions, 3 Improvements, 6 Mixed; 8 of them in rollups
  4551. 40 artifact comparisons made in total&lt;/p&gt;
  4552. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/rustc-perf/blob/33d1d2f6103c22772c45562aa159d1e1257c228e/triage/2025/2025-10-06.md&quot;&gt;Full report here&lt;/a&gt;&lt;/p&gt;
  4553. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#approved-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/commits/master&quot;&gt;Approved RFCs&lt;/a&gt;&lt;/h5&gt;
  4554. &lt;p&gt;Changes to Rust follow the Rust &lt;a href=&quot;https://github.com/rust-lang/rfcs#rust-rfcs&quot;&gt;RFC (request for comments) process&lt;/a&gt;. These
  4555. are the RFCs that were approved for implementation this week:&lt;/p&gt;
  4556. &lt;ul&gt;
  4557. &lt;li&gt;&lt;em&gt;No RFCs were approved this week.&lt;/em&gt;&lt;/li&gt;
  4558. &lt;/ul&gt;
  4559. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#final-comment-period&quot;&gt;Final Comment Period&lt;/a&gt;&lt;/h5&gt;
  4560. &lt;p&gt;Every week, &lt;a href=&quot;https://www.rust-lang.org/team.html&quot;&gt;the team&lt;/a&gt; announces the 'final comment period' for RFCs and key PRs
  4561. which are reaching a decision. Express your opinions now.&lt;/p&gt;
  4562. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#tracking-issues-prs&quot;&gt;Tracking Issues &amp;amp; PRs&lt;/a&gt;&lt;/h6&gt;
  4563. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust_1&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Rust&lt;/a&gt;
  4564. &lt;ul&gt;
  4565. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145924&quot;&gt;Uplifts and extends &lt;code&gt;clippy::needless-maybe-sized&lt;/code&gt; into rustc&lt;/a&gt;&lt;/li&gt;
  4566. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/144064&quot;&gt;prefer alias candidates for sizedness + auto trait goals&lt;/a&gt;&lt;/li&gt;
  4567. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145722&quot;&gt;implement Extend&amp;lt;{Group, Literal, Punct, Ident}&amp;gt; for TokenStream&lt;/a&gt;&lt;/li&gt;
  4568. &lt;/ul&gt;
  4569. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cargo_1&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Cargo&lt;/a&gt;
  4570. &lt;ul&gt;
  4571. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/issues/13051&quot;&gt;Add &lt;code&gt;target=&quot;host&quot;&lt;/code&gt; meaning the current host&lt;/a&gt;&lt;/li&gt;
  4572. &lt;/ul&gt;
  4573. &lt;p&gt;&lt;em&gt;No Items entered Final Comment Period this week for
  4574.  &lt;a href=&quot;https://github.com/rust-lang/rfcs/labels/final-comment-period&quot;&gt;Rust RFCs&lt;/a&gt;,
  4575.  &lt;a href=&quot;https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+&quot;&gt;Language Team&lt;/a&gt;,
  4576.  &lt;a href=&quot;https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Language Reference&lt;/a&gt;,
  4577.  &lt;a href=&quot;https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period&quot;&gt;Leadership Council&lt;/a&gt; or
  4578.  &lt;a href=&quot;https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Unsafe Code Guidelines&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
  4579. &lt;p&gt;Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.&lt;/p&gt;
  4580. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#new-and-updated-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/pulls&quot;&gt;New and Updated RFCs&lt;/a&gt;&lt;/h6&gt;
  4581. &lt;ul&gt;
  4582. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3869&quot;&gt;RFC: Allow &lt;code&gt;#[ignore(Trait)]&lt;/code&gt; on field to ignore it when deriving &lt;code&gt;Trait&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  4583. &lt;/ul&gt;
  4584. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#upcoming-events&quot;&gt;Upcoming Events&lt;/a&gt;&lt;/h4&gt;
  4585. &lt;p&gt;Rusty Events between 2025-10-08 - 2025-11-05 🦀&lt;/p&gt;
  4586. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#virtual&quot;&gt;Virtual&lt;/a&gt;&lt;/h5&gt;
  4587. &lt;ul&gt;
  4588. &lt;li&gt;2025-10-08 | Virtual (Boulder, CO, US) | &lt;a href=&quot;https://www.meetup.com/boulder-elixir/events/&quot;&gt;Boulder Elixir&lt;/a&gt;&lt;ul&gt;
  4589. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/boulder-elixir/events/310996627/&quot;&gt;&lt;strong&gt;Integrating Elixir and Apache DataFusion with Rustler&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4590. &lt;/ul&gt;
  4591. &lt;/li&gt;
  4592. &lt;li&gt;2025-10-09 - 2025-10-10 | Hybrid (Paris, FR) | &lt;a href=&quot;https://eurorust.eu/&quot;&gt;EuroRust&lt;/a&gt;&lt;ul&gt;
  4593. &lt;li&gt;&lt;a href=&quot;https://eurorust.eu/schedule/&quot;&gt;&lt;strong&gt;EuroRust 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4594. &lt;/ul&gt;
  4595. &lt;/li&gt;
  4596. &lt;li&gt;2025-10-09 | Virtual (Berlin, DE) | &lt;a href=&quot;https://www.meetup.com/rust-berlin&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  4597. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/306046639/&quot;&gt;&lt;strong&gt;Rust Hack and Learn&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4598. &lt;/ul&gt;
  4599. &lt;/li&gt;
  4600. &lt;li&gt;2025-10-09 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  4601. &lt;li&gt;&lt;a href=&quot;https://luma.com/jotnli2g&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4602. &lt;/ul&gt;
  4603. &lt;/li&gt;
  4604. &lt;li&gt;2025-10-09 | Virtual (San Diego, CA, US) | &lt;a href=&quot;https://www.meetup.com/san-diego-rust&quot;&gt;San Diego Rust&lt;/a&gt;&lt;ul&gt;
  4605. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/san-diego-rust/events/311359525/&quot;&gt;&lt;strong&gt;San Diego Rust October 2025 Online Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4606. &lt;/ul&gt;
  4607. &lt;/li&gt;
  4608. &lt;li&gt;2025-10-12 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  4609. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109160/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4610. &lt;/ul&gt;
  4611. &lt;/li&gt;
  4612. &lt;li&gt;2025-10-14 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  4613. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/305361534/&quot;&gt;&lt;strong&gt;Second Tuesday&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4614. &lt;/ul&gt;
  4615. &lt;/li&gt;
  4616. &lt;li&gt;2025-10-15 | Hybrid (Vancouver, BC, CA) | &lt;a href=&quot;https://www.meetup.com/vancouver-rust&quot;&gt;Vancouver Rust&lt;/a&gt;&lt;ul&gt;
  4617. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/vancouver-rust/events/307731034/&quot;&gt;&lt;strong&gt;indielinks&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4618. &lt;/ul&gt;
  4619. &lt;/li&gt;
  4620. &lt;li&gt;2025-10-16 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  4621. &lt;li&gt;&lt;a href=&quot;https://luma.com/o8fh3fh7&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4622. &lt;/ul&gt;
  4623. &lt;/li&gt;
  4624. &lt;li&gt;2025-10-16 | Virtual (Nürnberg, DE) | &lt;a href=&quot;https://www.meetup.com/rust-noris&quot;&gt;Rust Nuremberg&lt;/a&gt;&lt;ul&gt;
  4625. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-noris/events/306046668/&quot;&gt;&lt;strong&gt;Rust Nürnberg online&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4626. &lt;/ul&gt;
  4627. &lt;/li&gt;
  4628. &lt;li&gt;2025-10-18 | Virtual (Gdansk, PL) | &lt;a href=&quot;https://www.meetup.com/stacja-it-trojmiasto/&quot;&gt;Stacja IT Trójmiasto&lt;/a&gt;&lt;ul&gt;
  4629. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/stacja-it-trojmiasto/events/310935164/&quot;&gt;&lt;strong&gt;[BEZPŁATNIE] Programowanie w języku Rust&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4630. &lt;/ul&gt;
  4631. &lt;/li&gt;
  4632. &lt;li&gt;2025-10-19 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  4633. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109167/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4634. &lt;/ul&gt;
  4635. &lt;/li&gt;
  4636. &lt;li&gt;2025-10-21 | Virtual (London, UK) | &lt;a href=&quot;https://www.meetup.com/women-in-rust&quot;&gt;Women in Rust&lt;/a&gt;&lt;ul&gt;
  4637. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/women-in-rust/events/311068625/&quot;&gt;&lt;strong&gt;👋 Community Catch Up&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4638. &lt;/ul&gt;
  4639. &lt;/li&gt;
  4640. &lt;li&gt;2025-10-21 | Virtual (Washington, DC, US) | &lt;a href=&quot;https://www.meetup.com/rustdc&quot;&gt;Rust DC&lt;/a&gt;&lt;ul&gt;
  4641. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rustdc/events/310002307/&quot;&gt;&lt;strong&gt;Mid-month Rustful&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4642. &lt;/ul&gt;
  4643. &lt;/li&gt;
  4644. &lt;li&gt;2025-10-23 | Hybrid (Seattle, WA, US) | &lt;a href=&quot;https://www.meetup.com/join-srug&quot;&gt;Seattle Rust User Group&lt;/a&gt;&lt;ul&gt;
  4645. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/seattle-rust-user-group/events/311351020/&quot;&gt;&lt;strong&gt;October, 2025 SRUG (Seattle Rust User Group) Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4646. &lt;/ul&gt;
  4647. &lt;/li&gt;
  4648. &lt;li&gt;2025-10-23 | Virtual (Berlin, DE) | &lt;a href=&quot;https://www.meetup.com/rust-berlin&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  4649. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/306046641/&quot;&gt;&lt;strong&gt;Rust Hack and Learn&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4650. &lt;/ul&gt;
  4651. &lt;/li&gt;
  4652. &lt;li&gt;2025-10-23 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  4653. &lt;li&gt;&lt;a href=&quot;https://luma.com/zyc3touy&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4654. &lt;/ul&gt;
  4655. &lt;/li&gt;
  4656. &lt;li&gt;2025-10-26 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  4657. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109171/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4658. &lt;/ul&gt;
  4659. &lt;/li&gt;
  4660. &lt;li&gt;2025-10-28 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  4661. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/305361444/&quot;&gt;&lt;strong&gt;Fourth Tuesday&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4662. &lt;/ul&gt;
  4663. &lt;/li&gt;
  4664. &lt;li&gt;2025-10-30 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  4665. &lt;li&gt;&lt;a href=&quot;https://luma.com/t8yovmmm&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4666. &lt;/ul&gt;
  4667. &lt;/li&gt;
  4668. &lt;li&gt;2025-11-01 | Virtual (Kampala, UG) | &lt;a href=&quot;https://www.eventbrite.com/o/rust-circle-kampala-65249289033&quot;&gt;Rust Circle Meetup&lt;/a&gt;&lt;ul&gt;
  4669. &lt;li&gt;&lt;a href=&quot;https://www.eventbrite.com/e/rust-circle-meetup-tickets-628763868657&quot;&gt;&lt;strong&gt;Rust Circle Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4670. &lt;/ul&gt;
  4671. &lt;/li&gt;
  4672. &lt;li&gt;2025-11-02 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  4673. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109173/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4674. &lt;/ul&gt;
  4675. &lt;/li&gt;
  4676. &lt;li&gt;2025-11-05 | Virtual (Buffalo, NY, US) | &lt;a href=&quot;https://www.meetup.com/buffalo-rust-meetup&quot;&gt;Buffalo Rust Meetup&lt;/a&gt;&lt;ul&gt;
  4677. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/buffalo-rust-meetup/events/305304242/&quot;&gt;&lt;strong&gt;Buffalo Rust User Group&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4678. &lt;/ul&gt;
  4679. &lt;/li&gt;
  4680. &lt;li&gt;2025-11-05 | Virtual (Indianapolis, IN, US) | &lt;a href=&quot;https://www.meetup.com/indyrs&quot;&gt;Indy Rust&lt;/a&gt;&lt;ul&gt;
  4681. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/indyrs/events/wqzhftyhcpbhb/&quot;&gt;&lt;strong&gt;Indy.rs - with Social Distancing&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4682. &lt;/ul&gt;
  4683. &lt;/li&gt;
  4684. &lt;/ul&gt;
  4685. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#asia&quot;&gt;Asia&lt;/a&gt;&lt;/h5&gt;
  4686. &lt;ul&gt;
  4687. &lt;li&gt;2025-10-08 | Kuala Lumpur, MY | &lt;a href=&quot;https://t.me/rustlangmalaysia&quot;&gt;Rust Malaysia&lt;/a&gt;&lt;ul&gt;
  4688. &lt;li&gt;&lt;a href=&quot;https://docs.google.com/forms/d/e/1FAIpQLScESY4eHc5lzZznAHZmFxI85CYaOKCYTQASRwXxC2y0KpI6zw/viewform&quot;&gt;&lt;strong&gt;Malaysia Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4689. &lt;/ul&gt;
  4690. &lt;/li&gt;
  4691. &lt;li&gt;2025-10-09 | Tokyo, JP | &lt;a href=&quot;https://www.meetup.com/tokyo-rust-meetup&quot;&gt;Tokyo Rust Meetup&lt;/a&gt;&lt;ul&gt;
  4692. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/tokyo-rust-meetup/events/310899137/&quot;&gt;&lt;strong&gt;Building Pocket-Sized Terminal UIs with Rust&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4693. &lt;/ul&gt;
  4694. &lt;/li&gt;
  4695. &lt;li&gt;2025-10-20 | Tel Aviv-yafo, IL | &lt;a href=&quot;https://www.meetup.com/rust-tlv&quot;&gt;Rust 🦀 TLV&lt;/a&gt;&lt;ul&gt;
  4696. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-tlv/events/310628902/&quot;&gt;&lt;strong&gt;In person Rust October 2025 at AWS in Tel Aviv&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4697. &lt;/ul&gt;
  4698. &lt;/li&gt;
  4699. &lt;/ul&gt;
  4700. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#europe&quot;&gt;Europe&lt;/a&gt;&lt;/h5&gt;
  4701. &lt;ul&gt;
  4702. &lt;li&gt;2025-10-08 | Girona, ES | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt;&lt;ul&gt;
  4703. &lt;li&gt;&lt;a href=&quot;https://luma.com/8u55jo0h&quot;&gt;&lt;strong&gt;Rust Girona Hack &amp;amp; Learn 10 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4704. &lt;/ul&gt;
  4705. &lt;/li&gt;
  4706. &lt;li&gt;2025-10-08 | Paris, FR | &lt;a href=&quot;https://www.meetup.com/rust-paris&quot;&gt;Rust Paris&lt;/a&gt;&lt;ul&gt;
  4707. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-paris/events/310424476/&quot;&gt;&lt;strong&gt;Rust meetup #79&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4708. &lt;/ul&gt;
  4709. &lt;/li&gt;
  4710. &lt;li&gt;2025-10-08 | Reading, UK | &lt;a href=&quot;https://www.meetup.com/reading-rust-workshop&quot;&gt;Reading Rust Workshop&lt;/a&gt;&lt;ul&gt;
  4711. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/reading-rust-workshop/events/308944041/&quot;&gt;&lt;strong&gt;Reading Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4712. &lt;/ul&gt;
  4713. &lt;/li&gt;
  4714. &lt;li&gt;2025-10-09 - 2025-10-10 | Hybrid (Paris, FR) | &lt;a href=&quot;https://eurorust.eu/&quot;&gt;EuroRust&lt;/a&gt;&lt;ul&gt;
  4715. &lt;li&gt;&lt;a href=&quot;https://eurorust.eu/schedule/&quot;&gt;&lt;strong&gt;EuroRust 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4716. &lt;/ul&gt;
  4717. &lt;/li&gt;
  4718. &lt;li&gt;2025-10-14 | Basel, CH | &lt;a href=&quot;https://www.meetup.com/rust-basel&quot;&gt;Rust Basel&lt;/a&gt;&lt;ul&gt;
  4719. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-basel/events/310827834/&quot;&gt;&lt;strong&gt;Rust Meetup #13 @ letsboot&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4720. &lt;/ul&gt;
  4721. &lt;/li&gt;
  4722. &lt;li&gt;2025-10-21 | Aarhus, DK | &lt;a href=&quot;https://www.meetup.com/rust-aarhus&quot;&gt;Rust Aarhus&lt;/a&gt;&lt;ul&gt;
  4723. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-aarhus/events/311035141/&quot;&gt;&lt;strong&gt;Hack Night&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4724. &lt;/ul&gt;
  4725. &lt;/li&gt;
  4726. &lt;li&gt;2025-10-21 | Bergen, No | &lt;a href=&quot;https://www.meetup.com/bergen-rust-new-technology/events/&quot;&gt;Rust Bergen&lt;/a&gt;&lt;ul&gt;
  4727. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bergen-rust-new-technology/events/311153821/&quot;&gt;&lt;strong&gt;Rust Meetup #01 @ Zrch&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4728. &lt;/ul&gt;
  4729. &lt;/li&gt;
  4730. &lt;li&gt;2025-10-21 | Leipzig, DE | &lt;a href=&quot;https://www.meetup.com/rust-modern-systems-programming-in-leipzig&quot;&gt;Rust - Modern Systems Programming in Leipzig&lt;/a&gt;&lt;ul&gt;
  4731. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/308592252/&quot;&gt;&lt;strong&gt;Topic TBD&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4732. &lt;/ul&gt;
  4733. &lt;/li&gt;
  4734. &lt;li&gt;2025-10-21 | London, UK | &lt;a href=&quot;https://www.meetup.com/london-rust-project-group&quot;&gt;London Rust Project Group&lt;/a&gt;&lt;ul&gt;
  4735. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/london-rust-project-group/events/310813952/&quot;&gt;&lt;strong&gt;Rust in Surgery: Powering the Data Pipelines&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4736. &lt;/ul&gt;
  4737. &lt;/li&gt;
  4738. &lt;li&gt;2025-10-28 | Manchester, UK | &lt;a href=&quot;https://www.meetup.com/rust-manchester&quot;&gt;Rust Manchester&lt;/a&gt;&lt;ul&gt;
  4739. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-manchester/events/307919171/&quot;&gt;&lt;strong&gt;Rust Manchester October Code Night&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4740. &lt;/ul&gt;
  4741. &lt;/li&gt;
  4742. &lt;li&gt;2025-10-30 | Copenhagen, DK | &lt;a href=&quot;https://www.meetup.com/copenhagen-rust-community&quot;&gt;Copenhagen Rust Community&lt;/a&gt;&lt;ul&gt;
  4743. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/copenhagen-rust-community/events/311405044/&quot;&gt;&lt;strong&gt;Rust meetup #62 sponsored by Google!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4744. &lt;/ul&gt;
  4745. &lt;/li&gt;
  4746. &lt;li&gt;2025-10-30 | Prague, CZ | &lt;a href=&quot;https://www.meetup.com/rust-prague&quot;&gt;Rust Prague&lt;/a&gt;&lt;ul&gt;
  4747. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-prague/events/310967094/&quot;&gt;&lt;strong&gt;Rust Meetup Prague (October 2025)&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4748. &lt;/ul&gt;
  4749. &lt;/li&gt;
  4750. &lt;li&gt;2025-11-02 - 2025-11-04 | Florence, IT | &lt;a href=&quot;https://rustlab.it/&quot;&gt;Rustlab 2025&lt;/a&gt;&lt;ul&gt;
  4751. &lt;li&gt;&lt;a href=&quot;https://rustlab.it/&quot;&gt;&lt;strong&gt;Rustlab 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4752. &lt;/ul&gt;
  4753. &lt;/li&gt;
  4754. &lt;li&gt;2025-11-04 | Manchester, UK | &lt;a href=&quot;https://www.meetup.com/rust-manchester&quot;&gt;Rust Manchester&lt;/a&gt;&lt;ul&gt;
  4755. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-manchester/events/310921632/&quot;&gt;&lt;strong&gt;Rust Manchester November Talk&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4756. &lt;/ul&gt;
  4757. &lt;/li&gt;
  4758. &lt;li&gt;2025-11-05 | Oslo, NO | &lt;a href=&quot;https://www.meetup.com/rust-oslo&quot;&gt;Rust Oslo&lt;/a&gt;&lt;ul&gt;
  4759. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-oslo/events/310601872/&quot;&gt;&lt;strong&gt;Rust Hack'n'Learn at Kampen Bistro&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4760. &lt;/ul&gt;
  4761. &lt;/li&gt;
  4762. &lt;li&gt;2025-11-05 | Oxford, UK | &lt;a href=&quot;https://www.meetup.com/oxford-rust-meetup-group&quot;&gt;Oxford ACCU/Rust Meetup.&lt;/a&gt;&lt;ul&gt;
  4763. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/oxford-rust-meetup-group/events/nnrkttyhcpbhb/&quot;&gt;&lt;strong&gt;Rust/ACCU meetup.&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4764. &lt;/ul&gt;
  4765. &lt;/li&gt;
  4766. &lt;/ul&gt;
  4767. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#north-america&quot;&gt;North America&lt;/a&gt;&lt;/h5&gt;
  4768. &lt;ul&gt;
  4769. &lt;li&gt;2025-10-08 | Phoenix, AZ, US | &lt;a href=&quot;https://www.meetup.com/desert-rustaceans&quot;&gt;Desert Rust&lt;/a&gt;&lt;ul&gt;
  4770. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/desert-rustaceans/events/311365791/&quot;&gt;&lt;strong&gt;Rust &amp;lt;&amp;gt; C++&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4771. &lt;/ul&gt;
  4772. &lt;/li&gt;
  4773. &lt;li&gt;2025-10-09 | Lehi, UT, US | &lt;a href=&quot;https://www.meetup.com/utah-rust&quot;&gt;Utah Rust&lt;/a&gt;&lt;ul&gt;
  4774. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/utah-rust/events/311145663/&quot;&gt;&lt;strong&gt;Aya the Beholder: Writing an eBPF Firewall with the Aya Crate&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4775. &lt;/ul&gt;
  4776. &lt;/li&gt;
  4777. &lt;li&gt;2025-10-14 | New York, NY, US | &lt;a href=&quot;https://www.meetup.com/rust-nyc&quot;&gt;Rust NYC&lt;/a&gt;&lt;ul&gt;
  4778. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-nyc/events/311328171/&quot;&gt;&lt;strong&gt;Rust NYC: Rust in Robotics &amp;amp; Isograph&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4779. &lt;/ul&gt;
  4780. &lt;/li&gt;
  4781. &lt;li&gt;2025-10-15 | Hybrid (Vancouver, BC, CA) | &lt;a href=&quot;https://www.meetup.com/vancouver-rust&quot;&gt;Vancouver Rust&lt;/a&gt;&lt;ul&gt;
  4782. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/vancouver-rust/events/307731034/&quot;&gt;&lt;strong&gt;indielinks&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4783. &lt;/ul&gt;
  4784. &lt;/li&gt;
  4785. &lt;li&gt;2025-10-16 | Mountain View, CA, US | &lt;a href=&quot;https://www.meetup.com/hackerdojo/events/&quot;&gt;Hacker Dojo&lt;/a&gt;&lt;ul&gt;
  4786. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/hackerdojo/events/311012947/&quot;&gt;&lt;strong&gt;RUST MEETUP at HACKER DOJO&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4787. &lt;/ul&gt;
  4788. &lt;/li&gt;
  4789. &lt;li&gt;2025-10-16 | San Francisco, CA, US | &lt;a href=&quot;https://luma.com/calendar/cal-Cnmn4RR2n4fRUNZ&quot;&gt;Svix&lt;/a&gt;&lt;ul&gt;
  4790. &lt;li&gt;&lt;a href=&quot;https://luma.com/tp6w7tc9&quot;&gt;&lt;strong&gt;San Francisco Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4791. &lt;/ul&gt;
  4792. &lt;/li&gt;
  4793. &lt;li&gt;2025-10-21 | San Francisco, CA, US | &lt;a href=&quot;https://luma.com/events-by-vara-gear&quot;&gt;Vara &amp;amp; Gear&lt;/a&gt;&lt;ul&gt;
  4794. &lt;li&gt;&lt;a href=&quot;https://luma.com/kbs2os1c&quot;&gt;&lt;strong&gt;Rust Workshop by Vara Network&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4795. &lt;/ul&gt;
  4796. &lt;/li&gt;
  4797. &lt;li&gt;2025-10-21 | San Francisco, CA, US | &lt;a href=&quot;https://www.meetup.com/san-francisco-rust-study-group&quot;&gt;San Francisco Rust Study Group&lt;/a&gt;&lt;ul&gt;
  4798. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/san-francisco-rust-study-group/events/308284343/&quot;&gt;&lt;strong&gt;Rust Hacking in Person&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4799. &lt;/ul&gt;
  4800. &lt;/li&gt;
  4801. &lt;li&gt;2025-10-22 | Austin, TX, US | &lt;a href=&quot;https://www.meetup.com/rust-atx&quot;&gt;Rust ATX&lt;/a&gt;&lt;ul&gt;
  4802. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-atx/events/310457307/&quot;&gt;&lt;strong&gt;Rust Lunch - Fareground&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4803. &lt;/ul&gt;
  4804. &lt;/li&gt;
  4805. &lt;li&gt;2025-10-23 | Hybrid (Seattle, WA, US) | &lt;a href=&quot;https://www.meetup.com/join-srug&quot;&gt;Seattle Rust User Group&lt;/a&gt;&lt;ul&gt;
  4806. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/seattle-rust-user-group/events/311351020/&quot;&gt;&lt;strong&gt;October, 2025 SRUG (Seattle Rust User Group) Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4807. &lt;/ul&gt;
  4808. &lt;/li&gt;
  4809. &lt;li&gt;2025-10-23 | Nashville, TN, US | &lt;a href=&quot;https://www.meetup.com/music-city-rust-developers&quot;&gt;Music City Rust Developers&lt;/a&gt;&lt;ul&gt;
  4810. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/music-city-rust-developers/events/304333267/&quot;&gt;&lt;strong&gt;Year In Review&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4811. &lt;/ul&gt;
  4812. &lt;/li&gt;
  4813. &lt;li&gt;2025-10-23 | Spokane, WA, US | &lt;a href=&quot;https://www.meetup.com/spokane-rust&quot;&gt;Spokane Rust&lt;/a&gt;&lt;ul&gt;
  4814. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/spokane-rust/events/311346444/&quot;&gt;&lt;strong&gt;October Rust Meetup: A Special Presentation and Monthly Meetups are Back!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4815. &lt;/ul&gt;
  4816. &lt;/li&gt;
  4817. &lt;li&gt;2025-10-25 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  4818. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/310983712/&quot;&gt;&lt;strong&gt;Porter Square Rust Lunch, Oct 25&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4819. &lt;/ul&gt;
  4820. &lt;/li&gt;
  4821. &lt;li&gt;2025-10-30 | Atlanta, GA, US | &lt;a href=&quot;https://www.meetup.com/rust-atl&quot;&gt;Rust Atlanta&lt;/a&gt;&lt;ul&gt;
  4822. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-atl/events/308675988/&quot;&gt;&lt;strong&gt;Rust-Atl&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4823. &lt;/ul&gt;
  4824. &lt;/li&gt;
  4825. &lt;li&gt;2025-11-01 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  4826. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/311039492/&quot;&gt;&lt;strong&gt;Chinatown Rust Lunch, Nov 1&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4827. &lt;/ul&gt;
  4828. &lt;/li&gt;
  4829. &lt;/ul&gt;
  4830. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#oceania&quot;&gt;Oceania&lt;/a&gt;&lt;/h5&gt;
  4831. &lt;ul&gt;
  4832. &lt;li&gt;2025-10-22 | Perth, AU | &lt;a href=&quot;https://www.meetup.com/perth-rust-meetup-group&quot;&gt;Rust Perth Meetup Group&lt;/a&gt;&lt;ul&gt;
  4833. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/perth-rust-meetup-group/events/310847099/&quot;&gt;&lt;strong&gt;October Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4834. &lt;/ul&gt;
  4835. &lt;/li&gt;
  4836. &lt;li&gt;2025-10-28 | Barton, AU | &lt;a href=&quot;https://www.meetup.com/rust-canberra&quot;&gt;Canberra Rust User Group&lt;/a&gt;&lt;ul&gt;
  4837. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-canberra/events/311234237/&quot;&gt;&lt;strong&gt;October Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4838. &lt;/ul&gt;
  4839. &lt;/li&gt;
  4840. &lt;/ul&gt;
  4841. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#south-america&quot;&gt;South America&lt;/a&gt;&lt;/h5&gt;
  4842. &lt;ul&gt;
  4843. &lt;li&gt;2025-10-08 | Buenos Aires, AR | &lt;a href=&quot;https://www.meetup.com/rust-argentina&quot;&gt;Rust en Español&lt;/a&gt;&lt;ul&gt;
  4844. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-argentina/events/311276950/&quot;&gt;&lt;strong&gt;Octubre Async - Escribimos un Runtime desde Cero!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4845. &lt;/ul&gt;
  4846. &lt;/li&gt;
  4847. &lt;li&gt;2025-10-25 | São Paulo, BR | &lt;a href=&quot;https://www.meetup.com/rust-sao-paulo-meetup&quot;&gt;Rust São Paulo Meetup&lt;/a&gt;&lt;ul&gt;
  4848. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-sao-paulo-meetup/events/311084440/&quot;&gt;&lt;strong&gt;Encontro do Rust-SP na Amazon Web Services&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4849. &lt;/ul&gt;
  4850. &lt;/li&gt;
  4851. &lt;li&gt;2025-10-30 | Florianopolis, BR | &lt;a href=&quot;https://luma.com/calendar/cal-iOloL5ZqswCO5Mm&quot;&gt;Rust Brasil&lt;/a&gt;&lt;ul&gt;
  4852. &lt;li&gt;&lt;a href=&quot;https://luma.com/lky7an18&quot;&gt;&lt;strong&gt;Rust Floripa&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  4853. &lt;/ul&gt;
  4854. &lt;/li&gt;
  4855. &lt;/ul&gt;
  4856. &lt;p&gt;If you are running a Rust event please add it to the &lt;a href=&quot;https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com&quot;&gt;calendar&lt;/a&gt; to get
  4857. it mentioned here. Please remember to add a link to the event too.
  4858. Email the &lt;a href=&quot;mailto:community-team@rust-lang.org&quot;&gt;Rust Community Team&lt;/a&gt; for access.&lt;/p&gt;
  4859. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#jobs&quot;&gt;Jobs&lt;/a&gt;&lt;/h4&gt;
  4860.  
  4861.  
  4862. &lt;p&gt;Please see the latest &lt;a href=&quot;https://www.reddit.com/r/rust/comments/1nknaii/official_rrust_whos_hiring_thread_for_jobseekers/&quot;&gt;Who's Hiring thread on r/rust&lt;/a&gt;&lt;/p&gt;
  4863. &lt;h3&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#quote-of-the-week&quot;&gt;Quote of the Week&lt;/a&gt;&lt;/h3&gt;
  4864. &lt;blockquote&gt;
  4865. &lt;p&gt;For me personally, the best thing about becoming successful at anything is you gain the ability to lift others up.&lt;/p&gt;
  4866. &lt;/blockquote&gt;
  4867. &lt;p&gt;– &lt;a href=&quot;https://youtu.be/nEHLIUWO78I?t=1175&quot;&gt;Nell Shamrell-Harrington at RustConf&lt;/a&gt; (youtube video link, the rest of the talk is great, too!)&lt;/p&gt;
  4868. &lt;p&gt;Thanks to &lt;a href=&quot;https://users.rust-lang.org/t/twir-quote-of-the-week/328/1720&quot;&gt;llogiq&lt;/a&gt; for the suggestion!&lt;/p&gt;
  4869. &lt;p&gt;&lt;a href=&quot;https://users.rust-lang.org/t/twir-quote-of-the-week/328&quot;&gt;Please submit quotes and vote for next week!&lt;/a&gt;&lt;/p&gt;
  4870. &lt;p&gt;&lt;em&gt;This Week in Rust is edited by: &lt;a href=&quot;https://github.com/nellshamrell&quot;&gt;nellshamrell&lt;/a&gt;, &lt;a href=&quot;https://github.com/llogiq&quot;&gt;llogiq&lt;/a&gt;, &lt;a href=&quot;https://github.com/cdmistman&quot;&gt;cdmistman&lt;/a&gt;, &lt;a href=&quot;https://github.com/ericseppanen&quot;&gt;ericseppanen&lt;/a&gt;, &lt;a href=&quot;https://github.com/extrawurst&quot;&gt;extrawurst&lt;/a&gt;, &lt;a href=&quot;https://github.com/U007D&quot;&gt;U007D&lt;/a&gt;, &lt;a href=&quot;https://github.com/joelmarcey&quot;&gt;joelmarcey&lt;/a&gt;, &lt;a href=&quot;https://github.com/mariannegoldin&quot;&gt;mariannegoldin&lt;/a&gt;, &lt;a href=&quot;https://github.com/bennyvasquez&quot;&gt;bennyvasquez&lt;/a&gt;, &lt;a href=&quot;https://github.com/bdillo&quot;&gt;bdillo&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  4871. &lt;p&gt;&lt;em&gt;Email list hosting is sponsored by &lt;a href=&quot;https://foundation.rust-lang.org/&quot;&gt;The Rust Foundation&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  4872. &lt;p&gt;&lt;small&gt;&lt;a href=&quot;https://www.reddit.com/r/rust/comments/1o1uqur/this_week_in_rust_620/&quot;&gt;Discuss on r/rust&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;</description>
  4873. <pubDate>Wed, 08 Oct 2025 04:00:00 +0000</pubDate>
  4874. <dc:creator>TWiR Contributors</dc:creator>
  4875. </item>
  4876. <item>
  4877. <title>The Mozilla Blog: Firefox profiles: Private, focused spaces for all the ways you browse</title>
  4878. <guid isPermaLink="false">https://blog.mozilla.org/?p=82094</guid>
  4879. <link>https://blog.mozilla.org/en/firefox/profile-management/</link>
  4880. <description>&lt;p&gt;Every part of your life has its own rhythm: work, school, family, personal projects. Beginning Oct. 14, we’re rolling out a new &lt;a href=&quot;https://support.mozilla.org/kb/profile-management#w_is-this-feature-available-on-android-or-ios&quot;&gt;profile management feature in Firefox&lt;/a&gt; so you can keep them separate and create distinct spaces — each with its own bookmarks, logins, history, extensions and themes. It’s an easy way to stay organized, focused and private.&lt;/p&gt;
  4881.  
  4882.  
  4883. &lt;div class=&quot;wp-block-image&quot;&gt;
  4884. &lt;figure class=&quot;aligncenter size-large is-resized&quot;&gt;&lt;a href=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/firefox-profiles.png&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;img alt=&quot;Firefox Profiles feature shown with an illustration of three foxes and a setup screen for creating and customizing browser profiles.&quot; class=&quot;wp-image-82095&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/firefox-profiles-1024x576.png&quot; style=&quot;width: 675px;&quot; width=&quot;1024&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;&lt;/div&gt;
  4885.  
  4886.  
  4887. &lt;h3&gt;&lt;strong&gt;Spaces that lighten your load&lt;/strong&gt;&lt;/h3&gt;
  4888.  
  4889.  
  4890.  
  4891. &lt;p&gt;Profiles don’t just keep you organized; they also reduce data mixing and &lt;a href=&quot;https://blog.mozilla.org/firefox/multitasking/&quot;&gt;ease cognitive load&lt;/a&gt;. By keeping your different roles online neatly separate, you spend less mental energy juggling contexts and avoid awkward surprises (like your weekend plans popping up in a work presentation). And, like everything in Firefox, profiles are built on our &lt;a href=&quot;https://blog.mozilla.org/privacy-security/mozilla-anti-tracking-milestones-timeline/&quot;&gt;strong privacy foundation&lt;/a&gt;.&lt;/p&gt;
  4892.  
  4893.  
  4894.  
  4895. &lt;p&gt;We also &lt;a href=&quot;https://blog.mozilla.org/firefox/shifting-left-for-better-accessibility/&quot;&gt;worked with disabled people&lt;/a&gt; to make profiles not only compliant, but genuinely delightful to use for everyone. That collaboration shaped everything from the visual design (avatars, colors, naming) to the way profiles keep sensitive data (like medical information) private. It’s an example of how designing for accessibility boundaries benefits all of us.&lt;/p&gt;
  4896.  
  4897.  
  4898.  
  4899. &lt;h3&gt;&lt;strong&gt;What makes profiles in Firefox different&lt;/strong&gt;&lt;/h3&gt;
  4900.  
  4901.  
  4902.  
  4903. &lt;p&gt;Other browsers offer profiles mainly for convenience. Firefox goes further by making them part of our mission to put you in control of your online life.&lt;/p&gt;
  4904.  
  4905.  
  4906.  
  4907. &lt;ul&gt;
  4908. &lt;li&gt;&lt;strong&gt;Privacy first:&lt;/strong&gt; Firefox is built with privacy as a default. We don’t know your age, gender, precise location, name of your profile, or other information Big Tech collects and profits from. Each profile keeps its own browsing data separate. No mixing, no surprise leaks.&lt;br /&gt;&lt;/li&gt;
  4909.  
  4910.  
  4911.  
  4912. &lt;li&gt;&lt;strong&gt;Custom spaces:&lt;/strong&gt; Pick colors and themes to make each profile easy to spot at a glance. You can even upload your own avatar. Your work profile can feel buttoned-up, while your personal profile reflects your style.&lt;/li&gt;
  4913. &lt;/ul&gt;
  4914.  
  4915.  
  4916. &lt;div class=&quot;wp-block-image&quot;&gt;
  4917. &lt;figure class=&quot;aligncenter size-large is-resized&quot;&gt;&lt;a href=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/profiles-1.png&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;img alt=&quot;Firefox Profile Manager showing Work and Personal profiles, with an option to create a new one, on a desktop with a forest background.&quot; class=&quot;wp-image-82118&quot; height=&quot;533&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/profiles-1-1024x533.png&quot; style=&quot;width: 675px;&quot; width=&quot;1024&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;&lt;/div&gt;
  4918.  
  4919.  
  4920. &lt;p&gt;Profiles in Firefox aren’t just a way to clean up your tabs. They’re a way to set boundaries, protect your information and make the internet a little calmer. Because when your browser respects your focus and your privacy, it frees you up to do what actually matters — work, connect, create, explore — on your own terms.&lt;/p&gt;
  4921.  
  4922.  
  4923.  
  4924. &lt;a class=&quot;ft-c-inline-cta&quot; href=&quot;https://www.mozilla.org/firefox/new/?utm_source=blog.mozilla.org&amp;amp;utm_medium=referral&amp;amp;utm_campaign=blog-nav&quot;&gt;
  4925.  &lt;div class=&quot;ft-c-inline-cta__media&quot;&gt;
  4926.  &lt;img alt=&quot;&quot; class=&quot;attachment-1x1 size-1x1&quot; height=&quot;800&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2021/10/Visual-Guidelines-800x800.png&quot; width=&quot;800&quot; /&gt;  &lt;/div&gt;
  4927.  &lt;div class=&quot;ft-c-inline-cta__content&quot;&gt;
  4928.     &lt;h4&gt;Take control of your internet&lt;/h4&gt;      &lt;span&gt;Download Firefox&lt;/span&gt;   &lt;/div&gt;
  4929. &lt;/a&gt;
  4930. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/firefox/profile-management/&quot;&gt;Firefox profiles: Private, focused spaces for all the ways you browse&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  4931. <pubDate>Tue, 07 Oct 2025 14:11:44 +0000</pubDate>
  4932. <dc:creator>Susmitha Burra</dc:creator>
  4933. </item>
  4934. <item>
  4935. <title>Niko Matsakis: The Handle trait</title>
  4936. <guid isPermaLink="false">https://smallcultfollowing.com/babysteps/blog/2025/10/07/the-handle-trait/</guid>
  4937. <link>https://smallcultfollowing.com/babysteps/blog/2025/10/07/the-handle-trait/?utm_source=atom_feed</link>
  4938. <description>&lt;p&gt;There’s been a lot of discussion lately around ergonomic ref-counting. We had a lang-team design meeting and then a quite impactful discussion at the RustConf Unconf. I’ve been working for weeks on a follow-up post but today I realized what should’ve been obvious from the start – that if I’m taking that long to write a post, it means the post is too damned long. So I’m going to work through a series of smaller posts focused on individual takeaways and thoughts. And for the first one, I want to (a) bring back some of the context and (b) talk about an interesting question, &lt;strong&gt;what should we call the trait&lt;/strong&gt;. My proposal, as the title suggests, is &lt;code&gt;Handle&lt;/code&gt; – but I get ahead of myself.&lt;/p&gt;
  4939. &lt;h3&gt;The story thus far&lt;/h3&gt;
  4940. &lt;p&gt;For those of you who haven’t been following, there’s been an ongoing discussion about how best to have ergonomic ref counting:&lt;/p&gt;
  4941. &lt;ul&gt;
  4942. &lt;li&gt;It began with the first Rust Project Goals program in 2024H2, where Jonathan Kelley from Dioxus wrote a &lt;a href=&quot;https://dioxus.notion.site/Dioxus-Labs-High-level-Rust-5fe1f1c9c8334815ad488410d948f05e&quot;&gt;thoughtful blog post about a path to high-level Rust&lt;/a&gt; that eventually became a 2024H2 &lt;a href=&quot;https://rust-lang.github.io/rust-project-goals/2024h2/ergonomic-rc.html&quot;&gt;project goal towards ergonomic ref-counting&lt;/a&gt;.&lt;/li&gt;
  4943. &lt;li&gt;I wrote a &lt;a href=&quot;https://smallcultfollowing.com/babysteps/series/claim/&quot;&gt;series of blog posts about a trait I called &lt;code&gt;Claim&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;
  4944. &lt;li&gt;Josh and I talked and Josh opened &lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3680&quot;&gt;RFC #3680&lt;/a&gt;, which proposed a &lt;code&gt;use&lt;/code&gt; keyword and &lt;code&gt;use ||&lt;/code&gt; closures. Reception, I would say, was mixed; yes, this is tackling a real problem, but there were lots of concerns on the approach. &lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3680#issuecomment-2625526944&quot;&gt;I summarized the key points here&lt;/a&gt;.&lt;/li&gt;
  4945. &lt;li&gt;Santiago implemented experimental support for (a variant of) &lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3680&quot;&gt;RFC #3680&lt;/a&gt; as part of the &lt;a href=&quot;https://rust-lang.github.io/rust-project-goals/2025h1/ergonomic-rc.html&quot;&gt;2025H1 project goal&lt;/a&gt;.&lt;/li&gt;
  4946. &lt;li&gt;I authored a &lt;a href=&quot;https://rust-lang.github.io/rust-project-goals/2025h2/ergonomic-rc.html&quot;&gt;2025H2 project goal proposing that we create an alternative RFC focused on higher-level use-cases&lt;/a&gt; which prompted Josh and I have to have a long and fruitful conversation in which he convinced me that this was not the right approach.&lt;/li&gt;
  4947. &lt;li&gt;We had a lang-team design meeting on 2025-08-27 in which I presented this &lt;a href=&quot;https://hackmd.io/@rust-lang-team/B12TpGhKle&quot;&gt;survey and summary of the work done thus far&lt;/a&gt;.&lt;/li&gt;
  4948. &lt;li&gt;And then at the &lt;a href=&quot;https://2025.rustweek.org/unconf/&quot;&gt;RustConf 2025 Unconf&lt;/a&gt; we had a big group discussion on the topic that I found very fruitful, as well as various follow-up conversations with smaller groups.&lt;/li&gt;
  4949. &lt;/ul&gt;
  4950. &lt;h3&gt;This blog post is about “the trait”&lt;/h3&gt;
  4951. &lt;p&gt;The focus of this blog post is on one particular question: what should we call “The Trait”. In virtually every design, there has been &lt;em&gt;some kind&lt;/em&gt; of trait that is meant to identify &lt;em&gt;something&lt;/em&gt;. But it’s been hard to get a handle&lt;sup id=&quot;fnref:1&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:1&quot;&gt;1&lt;/a&gt;&lt;/sup&gt; on what precisely that &lt;em&gt;something&lt;/em&gt; is. What is this trait for and what types should implement it? Some things are clear: whatever The Trait is, &lt;code&gt;Rc&amp;lt;T&amp;gt;&lt;/code&gt; and &lt;code&gt;Arc&amp;lt;T&amp;gt;&lt;/code&gt; should implement it, for example, but that’s about it.&lt;/p&gt;
  4952. &lt;p&gt;My original proposal was for a trait named &lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2024/06/21/claim-auto-and-otherwise/&quot;&gt;&lt;code&gt;Claim&lt;/code&gt;&lt;/a&gt; that was meant to convey a “lightweight clone” – but really the trait was &lt;a href=&quot;https://smallcultfollowing.com/babysteps/blog/2024/06/26/claim-followup-1/#what-i-really-proposed&quot;&gt;meant to replace &lt;code&gt;Copy&lt;/code&gt; as the definition of which clones ought to be explicit&lt;/a&gt;&lt;sup id=&quot;fnref:2&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:2&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;. Jonathan Kelley had a similar proposal but called it &lt;code&gt;Capture&lt;/code&gt;. In &lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3680&quot;&gt;RFC #3680&lt;/a&gt; the proposal was to call the trait &lt;code&gt;Use&lt;/code&gt;.&lt;/p&gt;
  4953. &lt;p&gt;The details and intent varied, but all of these attempts had one thing in common: they were very &lt;em&gt;operational&lt;/em&gt;. That is, the trait was always being defined in terms of &lt;em&gt;what&lt;/em&gt; it does (or doesn’t do) but not &lt;em&gt;why&lt;/em&gt; it does it. And that I think will always be a weak grounding for a trait like this, prone to confusion and different interpretations. For example, what is a “lightweight” clone? Is it O(1)? But what about things that are O(1) with very high probability? And of course, O(1) doesn’t mean &lt;em&gt;cheap&lt;/em&gt; – it might copy 22GB of data every call. That’s O(1).&lt;/p&gt;
  4954. &lt;p&gt;What you want is a trait where it’s fairly clear when it should and should not be implemented and not based on taste or subjective criteria. And &lt;code&gt;Claim&lt;/code&gt; and friends did not meet the bar: in the Unconf, several new Rust users spoke up and said they found it very hard, based on my explanations, to judge whether their types ought to implement The Trait (whatever we call it). That has also been a persitent theme from the RFC and elsewhere.&lt;/p&gt;
  4955. &lt;h3&gt;“Shouldn’t we call it &lt;em&gt;share&lt;/em&gt;?” (hat tip: Jack Huey)&lt;/h3&gt;
  4956. &lt;p&gt;But really there &lt;em&gt;is&lt;/em&gt; a semantic underpinning here, and it was Jack Huey who first suggested it. Consider this question. What are the differences between cloning a &lt;code&gt;Mutex&amp;lt;Vec&amp;lt;u32&amp;gt;&amp;gt;&lt;/code&gt; and a &lt;code&gt;Arc&amp;lt;Mutex&amp;lt;Vec&amp;lt;u32&amp;gt;&amp;gt;&amp;gt;&lt;/code&gt;?&lt;/p&gt;
  4957. &lt;p&gt;One difference, of course, is cost. Cloning the &lt;code&gt;Mutex&amp;lt;Vec&amp;lt;u32&amp;gt;&amp;gt;&lt;/code&gt; will deep-clone the vector, cloning the &lt;code&gt;Arc&lt;/code&gt; will just increment a referece count.&lt;/p&gt;
  4958. &lt;p&gt;But the more important difference is what I call &lt;em&gt;“entanglement”&lt;/em&gt;. When you clone the &lt;code&gt;Arc&lt;/code&gt;, you don’t get a new value – you get back a &lt;em&gt;second handle to the same value&lt;/em&gt;.&lt;sup id=&quot;fnref:3&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:3&quot;&gt;3&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
  4959. &lt;h3&gt;Entanglement changes the meaning of the program&lt;/h3&gt;
  4960. &lt;p&gt;Knowing which values are “entangled” is key to understanding what your program does. A big part of how the borrow checker&lt;sup id=&quot;fnref:4&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:4&quot;&gt;4&lt;/a&gt;&lt;/sup&gt; achieves reliability is by reducing “entaglement”, since it becomes a relative pain to work with in Rust.&lt;/p&gt;
  4961. &lt;p&gt;Consider the following code. What will be the value of &lt;code&gt;l_before&lt;/code&gt; and &lt;code&gt;l_after&lt;/code&gt;?&lt;/p&gt;
  4962. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;l_before&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;v1&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;len&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;();&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4963. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;v2&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;v1&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;();&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4964. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;v2&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;push&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;new_value&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4965. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;kd&quot;&gt;let&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;l_after&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;v1&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;len&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;();&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4966. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The answer, of course, is “depends on the type of &lt;code&gt;v1&lt;/code&gt;”. If &lt;code&gt;v1&lt;/code&gt; is a &lt;code&gt;Vec&lt;/code&gt;, then &lt;code&gt;l_after == l_before&lt;/code&gt;. But if &lt;code&gt;v1&lt;/code&gt; is, say, a struct like this one:&lt;/p&gt;
  4967. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;struct&lt;/span&gt; &lt;span class=&quot;nc&quot;&gt;SharedVec&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4968. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;Arc&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Mutex&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;Vec&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&amp;gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4969. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4970. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  4971. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;SharedVec&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4972. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;pub&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;push&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;value&lt;/span&gt;: &lt;span class=&quot;nc&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4973. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lock&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;().&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;unwrap&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;().&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;push&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;value&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;);&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4974. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4975. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;
  4976. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;pub&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;len&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-&amp;gt; &lt;span class=&quot;kt&quot;&gt;usize&lt;/span&gt; &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4977. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;lock&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;().&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;unwrap&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;().&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;len&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;()&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4978. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4979. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4980. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;then &lt;code&gt;l_after == l_before + 1&lt;/code&gt;.&lt;/p&gt;
  4981. &lt;p&gt;There are many types that act like a &lt;code&gt;SharedVec&lt;/code&gt;: it’s true for &lt;code&gt;Rc&lt;/code&gt; and &lt;code&gt;Arc&lt;/code&gt;, of course, but also for things like &lt;a href=&quot;https://docs.rs/bytes/latest/bytes/struct.Bytes.html&quot;&gt;&lt;code&gt;Bytes&lt;/code&gt;&lt;/a&gt; and channel endpoints like &lt;a href=&quot;https://doc.rust-lang.org/std/sync/mpsc/struct.Sender.html&quot;&gt;&lt;code&gt;Sender&lt;/code&gt;&lt;/a&gt;. All of these are examples of “handles” to underlying values and, when you clone them, you get back a second handle that is indistinguishable from the first one.&lt;/p&gt;
  4982. &lt;h3&gt;We have a name for this concept already: handles&lt;/h3&gt;
  4983. &lt;p&gt;Jack’s insight was that we should focus on the &lt;em&gt;semantic concept&lt;/em&gt; (sharing) and not on the operational details (how it’s implemented). This makes it clear when the trait ought to be implemented. I liked this idea a lot, although I eventually decided I didn’t like the name &lt;code&gt;Share&lt;/code&gt;. The word isn’t specific enough, I felt, and users might not realize it referred to a specific concept: “shareable types” doesn’t really sound right. But in fact there &lt;em&gt;is&lt;/em&gt; a name already in common use for this concept: handles (see e.g. &lt;a href=&quot;https://docs.rs/tokio/latest/tokio/runtime/struct.Handle.html&quot;&gt;&lt;code&gt;tokio::runtime::Handle&lt;/code&gt;&lt;/a&gt;).&lt;/p&gt;
  4984. &lt;p&gt;This is how I arrived at my proposed name and definition for The Trait, which is &lt;code&gt;Handle&lt;/code&gt;:&lt;sup id=&quot;fnref:5&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:5&quot;&gt;5&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
  4985. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;sd&quot;&gt;/// Indicates that this type is a *handle* to some
  4986. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;sd&quot;&gt;/// underlying resource. The `handle` method is
  4987. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;sd&quot;&gt;/// used to get a fresh handle.
  4988. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;sd&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;trait&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Handle&lt;/span&gt;: &lt;span class=&quot;nb&quot;&gt;Clone&lt;/span&gt; &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4989. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;kr&quot;&gt;final&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;handle&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-&amp;gt; &lt;span class=&quot;nc&quot;&gt;Self&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4990. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;Clone&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4991. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4992. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4993. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3&gt;We would lint and advice people to call &lt;code&gt;handle&lt;/code&gt;&lt;/h3&gt;
  4994. &lt;p&gt;The &lt;code&gt;Handle&lt;/code&gt; trait includes a method &lt;code&gt;handle&lt;/code&gt; which is &lt;em&gt;always&lt;/em&gt; equivalent to &lt;code&gt;clone&lt;/code&gt;. The purpose of this method is to signal to the reader that the result is a second handle to the same underlying value.&lt;/p&gt;
  4995. &lt;p&gt;Once the &lt;code&gt;Handle&lt;/code&gt; trait exists, we should lint on calls to &lt;code&gt;clone&lt;/code&gt; when the receiver is known to implement &lt;code&gt;Handle&lt;/code&gt; and encourage folks to call &lt;code&gt;handle&lt;/code&gt; instead:&lt;/p&gt;
  4996. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;DataStore&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4997. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;store_map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;map&lt;/span&gt;: &lt;span class=&quot;kp&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;nc&quot;&gt;Arc&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;HashMap&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4998. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;stored_map&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;clone&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;();&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  4999. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//                    -----
  5000. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;//
  5001. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// Lint: convert `clone` to `handle` for
  5002. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;c1&quot;&gt;// greater clarity.
  5003. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5004. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5005. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Compare the above to the version that the lint suggests, using &lt;code&gt;handle&lt;/code&gt;, and I think you will get an idea for how &lt;code&gt;handle&lt;/code&gt; increases clarity of what is happening:&lt;/p&gt;
  5006. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;DataStore&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5007. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;fn&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;store_map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;mut&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;map&lt;/span&gt;: &lt;span class=&quot;kp&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;nc&quot;&gt;Arc&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;HashMap&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;..&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5008. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;        &lt;/span&gt;&lt;span class=&quot;bp&quot;&gt;self&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;stored_map&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;map&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;handle&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;();&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5009. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5010. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5011. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3&gt;What it means to be a &lt;em&gt;handle&lt;/em&gt;&lt;/h3&gt;
  5012. &lt;p&gt;The defining characteristic of a &lt;em&gt;handle&lt;/em&gt; is that it, when cloned, results in a second value that accesses the same underlying value. This means that the two handles are “entangled”, with interior mutation that affects one handle showing up in the other. Reflecting this, most handles have APIs that consist exclusively or almost exclusively of &lt;code&gt;&amp;amp;self&lt;/code&gt; methods, since having unique access to the &lt;em&gt;handle&lt;/em&gt; does not necessarily give you unique access to the &lt;em&gt;value&lt;/em&gt;.&lt;/p&gt;
  5013. &lt;p&gt;Handles are generally only significant, semantically, when interior mutability is involved. There’s nothing &lt;em&gt;wrong&lt;/em&gt; with having two handles to an immutable value, but it’s not generally distinguishable from two copies of the same value. This makes persistent collections an interesting grey area: I would probably implement &lt;code&gt;Handle&lt;/code&gt; for something like &lt;code&gt;im::Vec&amp;lt;T&amp;gt;&lt;/code&gt;, particularly since something like a &lt;code&gt;im::Vec&amp;lt;Cell&amp;lt;u32&amp;gt;&amp;gt;&lt;/code&gt; &lt;em&gt;would&lt;/em&gt; make entaglement visible, but I think there’s an argument against it.&lt;/p&gt;
  5014. &lt;h3&gt;Handles in the stdlib&lt;/h3&gt;
  5015. &lt;p&gt;In the stdlib, handle would be implemented for exactly one &lt;code&gt;Copy&lt;/code&gt; type (the others are values):&lt;/p&gt;
  5016. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// Shared references, when cloned (or copied),
  5017. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// create a second reference:
  5018. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;o&quot;&gt;?&lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;Sized&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Handle&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5019. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;It would be implemented for ref-counted pointers (but not &lt;code&gt;Box&lt;/code&gt;):&lt;/p&gt;
  5020. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// Ref-counted pointers, when cloned,
  5021. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// create a second reference:
  5022. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;o&quot;&gt;?&lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;Sized&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Handle&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Rc&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5023. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;w&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;o&quot;&gt;?&lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;Sized&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Handle&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Arc&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5024. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;And it would be implemented for types like channel endpoints, that are implemented with a ref-counted value under the hood:&lt;/p&gt;
  5025. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-rust&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// mpsc &quot;senders&quot;, when cloned, create a
  5026. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;// second sender to the same underlying channel:
  5027. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;c1&quot;&gt;&lt;/span&gt;&lt;span class=&quot;k&quot;&gt;impl&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;T&lt;/span&gt;: &lt;span class=&quot;o&quot;&gt;?&lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;Sized&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;Handle&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;k&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;n&quot;&gt;mpsc&lt;/span&gt;::&lt;span class=&quot;n&quot;&gt;Sender&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
  5028. &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3&gt;Conclusion: a design axiom emerges&lt;/h3&gt;
  5029. &lt;p&gt;OK, I’m going to stop there with this “byte-sized” blog post. More to come! But before I go, let me layout what I believe to be a useful “design axiom” that we should adopt for this design:&lt;/p&gt;
  5030. &lt;blockquote&gt;
  5031. &lt;p&gt;&lt;strong&gt;Expose entanglement.&lt;/strong&gt; Understanding the difference between a &lt;em&gt;handle&lt;/em&gt; to an underlying value and the value itself is necessary to understand how Rust works.&lt;/p&gt;
  5032. &lt;/blockquote&gt;
  5033. &lt;p&gt;The phrasing feels a bit awkward, but I think it is the key bit anyway.&lt;/p&gt;
  5034. &lt;div class=&quot;footnotes&quot;&gt;
  5035. &lt;hr /&gt;
  5036. &lt;ol&gt;
  5037. &lt;li id=&quot;fn:1&quot;&gt;
  5038. &lt;p&gt;That. my friends,  is &lt;em&gt;foreshadowing&lt;/em&gt;. Damn I’m good. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:1&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  5039. &lt;/li&gt;
  5040. &lt;li id=&quot;fn:2&quot;&gt;
  5041. &lt;p&gt;I described &lt;code&gt;Claim&lt;/code&gt; as a kind of “lightweight clone” but in the Unconf someone pointed out that “heavyweight copy” was probably a better description of what I was going for. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:2&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  5042. &lt;/li&gt;
  5043. &lt;li id=&quot;fn:3&quot;&gt;
  5044. &lt;p&gt;And, not coincidentally, the types where cloning leads to entanglement tend to also be the types where cloning is cheap. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:3&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  5045. &lt;/li&gt;
  5046. &lt;li id=&quot;fn:4&quot;&gt;
  5047. &lt;p&gt;and functional programming… &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:4&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  5048. &lt;/li&gt;
  5049. &lt;li id=&quot;fn:5&quot;&gt;
  5050. &lt;p&gt;The “final” keyword was proposed by Josh Triplett in RFC 3678. It means that impls cannot change the definition of &lt;code&gt;Handle::handle&lt;/code&gt;. There’s been some back-and-forth on whether it ought to be renamed or made more general or what have you; all I know is, I find it an incredibly useful concept for cases like this, where you want users to be able to opt-in to a method being &lt;em&gt;available&lt;/em&gt; but &lt;em&gt;not&lt;/em&gt; be able to change what it does. You can do this in other ways, they’re just weirder. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:5&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  5051. &lt;/li&gt;
  5052. &lt;/ol&gt;
  5053. &lt;/div&gt;</description>
  5054. <pubDate>Tue, 07 Oct 2025 14:04:55 +0000</pubDate>
  5055. </item>
  5056. <item>
  5057. <title>Firefox Nightly: Smarter Search, Smoother Tools – These Weeks in Firefox: Issue 190</title>
  5058. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1908</guid>
  5059. <link>https://blog.nightly.mozilla.org/2025/10/06/smarter-search-smoother-tools-these-weeks-in-firefox-issue-190/</link>
  5060. <description>&lt;h3&gt;Highlights&lt;/h3&gt;
  5061. &lt;ul&gt;
  5062. &lt;li&gt;Google Lens support has been &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1990369&quot;&gt;turned on by default&lt;/a&gt; in the latest nightly builds.
  5063. &lt;ul&gt;
  5064. &lt;li&gt;When Google is your default search engine, and you right click an image you’ll see a new context menu entry:&lt;/li&gt;
  5065. &lt;/ul&gt;
  5066. &lt;/li&gt;
  5067. &lt;/ul&gt;
  5068. &lt;p&gt;&lt;img alt=&quot;Context menu entry: Search Image with Google Lens&quot; class=&quot;alignnone size-large wp-image-1907&quot; height=&quot;328&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/10/headlines190_3-600x328.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  5069. &lt;ul&gt;
  5070. &lt;li&gt;Semantic history search has now also been &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1988990&quot;&gt;enabled&lt;/a&gt; in the latest nightly and beta builds.
  5071. &lt;ul&gt;
  5072. &lt;li&gt;This uses a local machine learning model to suggest entries from history that are related to your searches based on natural language understanding in the address bar.&lt;/li&gt;
  5073. &lt;/ul&gt;
  5074. &lt;/li&gt;
  5075. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot [:ochameau]&lt;/a&gt; improved the editor by displaying an editor widget where you can navigate between the different calls to a given function (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1908889&quot;&gt;#1908889&lt;/a&gt;)&lt;/li&gt;
  5076. &lt;/ul&gt;
  5077. &lt;p&gt;&lt;img alt=&quot;DevTools is displaying an editor widget&quot; class=&quot;alignnone size-large wp-image-1906&quot; height=&quot;493&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/10/headlines190_2-600x493.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  5078. &lt;ul&gt;
  5079. &lt;li&gt;The WebExtension cookies.set API method rejection on invalid cookies is riding the Firefox 145 release train (after it has been kept as a nightly only behavior for 3 nightly cycles) – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1976509&quot;&gt;Bug 1976509&lt;/a&gt;&lt;/li&gt;
  5080. &lt;/ul&gt;
  5081. &lt;p&gt; &lt;/p&gt;
  5082. &lt;h3&gt;Friends of the Firefox team&lt;/h3&gt;
  5083. &lt;h4&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20(excluding%20employees)&amp;amp;quicksearch=1892101%2C1969417%2C1979919%2C1689380%2C1982968%2C1984296%2C1982767%2C1981384%2C1984788%2C1813675%2C1583902%2C1956493%2C1984661%2C1679997%2C1787457%2C1984872&quot;&gt;Resolved bugs (excluding employees)&lt;/a&gt;&lt;/h4&gt;
  5084. &lt;h4&gt;Volunteers that fixed more than one bug&lt;/h4&gt;
  5085. &lt;ul&gt;
  5086. &lt;li&gt;Isaac Briandt&lt;/li&gt;
  5087. &lt;/ul&gt;
  5088. &lt;h4&gt;New contributors (🌟 = first patch)&lt;/h4&gt;
  5089. &lt;ul&gt;
  5090. &lt;li&gt;David [:david-loe] &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986237&quot;&gt;improved accessibility of timepicker&lt;/a&gt;&lt;/li&gt;
  5091. &lt;li&gt;Isaac Briandt updated&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1981244&quot;&gt; build-bergamot.py and upload-bergamot.py to utilize zstd compression&lt;/a&gt; and &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982594&quot;&gt;updated Translations RemoteSettings schemas&lt;/a&gt;&lt;/li&gt;
  5092. &lt;li&gt;🌟 Vlad L &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1881524&quot;&gt;updated ipv6 representation algorithm&lt;/a&gt;&lt;/li&gt;
  5093. &lt;/ul&gt;
  5094. &lt;h3&gt;Project Updates&lt;/h3&gt;
  5095. &lt;h4&gt;Add-ons / Web Extensions&lt;/h4&gt;
  5096. &lt;h5&gt;Addon Manager &amp;amp; about:addons&lt;/h5&gt;
  5097. &lt;ul&gt;
  5098. &lt;li&gt;As part of finalizing the Add-ons telemetry migration from legacy telemetry to Glean, the EnvironmentAddonBuilder (responsible for collecting the activeAddons/Theme/GMPlugins metrics in Glean and mirror it in the legacy telemetry environment) has been refactored out of the TelemetryEnvironment ES module – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1981496&quot;&gt;Bug 1981496&lt;/a&gt;&lt;/li&gt;
  5099. &lt;/ul&gt;
  5100. &lt;h4&gt;DevTools&lt;/h4&gt;
  5101. &lt;ul&gt;
  5102. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=446518&quot;&gt;Sebastian Zartner [:sebo]&lt;/a&gt; added inactive CSS icon when overflow* properties are used in non-block, non-flex, non-grid containers (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1583898&quot;&gt;#1583898&lt;/a&gt;)&lt;/li&gt;
  5103. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=750915&quot;&gt;Artem Manushenkov&lt;/a&gt; fixed a memory leak in the Inspector (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986144&quot;&gt;#1986144&lt;/a&gt;)&lt;/li&gt;
  5104. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=763731&quot;&gt;Holger Benl [:hbenl]&lt;/a&gt; fixed an issue where screenshots taken in Responsive Design Mode could have unexpected dimensions (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979518&quot;&gt;#1979518&lt;/a&gt;)&lt;/li&gt;
  5105. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=557153&quot;&gt;Nicolas Chevobbe [:nchevobbe]&lt;/a&gt; made the Accessibility panel color simulation persist on page reload (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1770707&quot;&gt;#1770707&lt;/a&gt;)&lt;/li&gt;
  5106. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot [:ochameau]&lt;/a&gt; fixed a Debugger crash that could happen when clicking on stacktrace frames from the console (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985446&quot;&gt;#1985446&lt;/a&gt;)&lt;/li&gt;
  5107. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=656417&quot;&gt;Hubert Boma Manilla (:bomsy)&lt;/a&gt; fixed Debugger pretty printing of sources containing characters represented by more than one code unit (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985689&quot;&gt;#1985689&lt;/a&gt;)&lt;/li&gt;
  5108. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=656417&quot;&gt;Hubert Boma Manilla (:bomsy)&lt;/a&gt; updated the version of Babel which we’re using to handle top level await detection, which fixed a few issues (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1900314&quot;&gt;#1900314&lt;/a&gt;)&lt;/li&gt;
  5109. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot [:ochameau]&lt;/a&gt; fixed an issue in the Network pane (reported by Jake), where the search would never complete (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983792&quot;&gt;#1983792&lt;/a&gt;)&lt;/li&gt;
  5110. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=559949&quot;&gt;Julian Descottes [:jdescottes]&lt;/a&gt; fixed a Network Monitor crash that was occurring when setting network override on requests requiring CORS preflight (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986615&quot;&gt;#1986615&lt;/a&gt;)&lt;/li&gt;
  5111. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=557153&quot;&gt;Nicolas Chevobbe [:nchevobbe]&lt;/a&gt; fixed an issue that was affecting the Changes panel on pages with multiple documents (that includes the Browser Toolbox) (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1798774&quot;&gt;#1798774&lt;/a&gt;)&lt;/li&gt;
  5112. &lt;/ul&gt;
  5113. &lt;h4&gt;WebDriver BiDi&lt;/h4&gt;
  5114. &lt;ul&gt;
  5115. &lt;li&gt;Henrik &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1988250&quot;&gt;disabled the BackupService component by default for the Remote Protocol&lt;/a&gt; (Marionette / WebDriver BiDi), as it isn’t required for web automation tasks.&lt;/li&gt;
  5116. &lt;li&gt;Julian &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1970293&quot;&gt;implemented the `browsingContext.downloadEnd` event&lt;/a&gt;, which is emitted either when a download is completed or canceled.&lt;/li&gt;
  5117. &lt;li&gt;Sasha implemented the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1987935&quot;&gt;“emulation.setUserAgentOverride” command&lt;/a&gt; for WebDriver BiDi, allowing clients to override the user agent string per browsing context, user context, or globally in Firefox + also fixed &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1705326&quot;&gt;Bug 1705326 – navigator.userAgent still returns custom UA after clearing browsingContext.customUserAgent if a reload happened while the custom UA was set&lt;/a&gt;&lt;/li&gt;
  5118. &lt;li&gt;Bug fixes
  5119. &lt;ul&gt;
  5120. &lt;li&gt;Julian &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986938&quot;&gt;updated the browsingContext.downloadWillBegin event to emit the correct `navigation` id&lt;/a&gt;, either the same one as the corresponding `browsingContext.navigationStarted` event, or null if the download was started by a link with a `download` attribute.&lt;/li&gt;
  5121. &lt;li&gt;Julian fixed a &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986615&quot;&gt;crash occurring when `network.provideResponse` was used&lt;/a&gt; to override a response requiring a CORS preflight.&lt;/li&gt;
  5122. &lt;li&gt;Julian fixed a &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1989919&quot;&gt;bug with network events incorrectly flagged as blocked&lt;/a&gt; (`isBlocked=true`), even if they were not blocked for technical reasons – eg. coming from memory cache or using `data` scheme.&lt;/li&gt;
  5123. &lt;li&gt;Julian updated the `network.beforeRequestSent` events to have &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985552&quot;&gt;`destination` set to “document” for top-level loads&lt;/a&gt;.&lt;/li&gt;
  5124. &lt;li&gt;Julian fixed an encoding issue with `network.getData` which will now &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986022&quot;&gt;always use utf-8 when serializing as text&lt;/a&gt;.&lt;/li&gt;
  5125. &lt;li&gt;Julian also updated `network.getData` to &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986025&quot;&gt;no longer throw if the response body is empty&lt;/a&gt;.&lt;/li&gt;
  5126. &lt;/ul&gt;
  5127. &lt;/li&gt;
  5128. &lt;/ul&gt;
  5129. &lt;h4&gt;Lint, Docs and Workflow&lt;/h4&gt;
  5130. &lt;ul&gt;
  5131. &lt;li&gt;&lt;a href=&quot;https://blog.nightly.mozilla.org/2025/09/19/add-ons-fixes-and-devtools-snacks-these-weeks-in-firefox-issue-188/#:~:text=We%E2%80%99re,reviewbot,-%2E&quot;&gt;First mentioned a month ago&lt;/a&gt;, the tier-3 TypeScript linter has &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1990475&quot;&gt;now been fixed&lt;/a&gt; so that it runs when the components it watches are touched. Previously it would only be run when the type information was changed.&lt;/li&gt;
  5132. &lt;li&gt;ESLint
  5133. &lt;ul&gt;
  5134. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1991124&quot;&gt;We discovered&lt;/a&gt; the &lt;a href=&quot;https://searchfox.org/firefox-main/source/tools/lint/eslint/eslint-plugin-mozilla/lib/configs/require-jsdoc.mjs&quot;&gt;require-jsdoc rules&lt;/a&gt; were not being applied due to a mistake when upgrading to flat config or ESLint v9. These have now been re-enabled, with follow-ups being landed to fix the new issues raised since the mistake was introduced.&lt;/li&gt;
  5135. &lt;li&gt;The &lt;a href=&quot;https://firefox-source-docs.mozilla.org/code-quality/lint/linters/eslint-plugin-mozilla/rules/no-browser-refs-in-toolkit.html&quot;&gt;no-browser-refs-in-toolkit rule&lt;/a&gt; has now &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1990309&quot;&gt;been promoted to an error&lt;/a&gt;, except for cases where it currently fails (stays as a warning). Please avoid introducing new cases.&lt;/li&gt;
  5136. &lt;li&gt;The &lt;a href=&quot;https://github.com/eslint/config-inspector&quot;&gt;ESLint configuration inspector&lt;/a&gt; should &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1990241&quot;&gt;now be working&lt;/a&gt; when run against firefox-main. This is a very useful tool for inspecting the configuration and determining which globals and rules are applied to which files.&lt;/li&gt;
  5137. &lt;li&gt;Gijs &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1971088&quot;&gt;updated&lt;/a&gt; our documentation for &lt;a href=&quot;https://firefox-source-docs.mozilla.org/code-quality/lint/linters/eslint.html#i-have-valid-code-that-is-failing-the-no-undef-rule-or-can-t-be-parsed&quot;&gt;ESLint environments&lt;/a&gt;, which no longer work in the same way with v9.
  5138. &lt;ul&gt;
  5139. &lt;li&gt;/** eslint-env foo */ no longer works.&lt;/li&gt;
  5140. &lt;li&gt;The files either need the correct extensions, or adding to eslint-file-globals.config.mjs. See &lt;a href=&quot;https://searchfox.org/firefox-main/rev/9140dac1eab834541a75792a78a5ed2fbee39142/eslint-file-globals.config.mjs#5-21&quot;&gt;the comments at the top of the file&lt;/a&gt; for more information.&lt;/li&gt;
  5141. &lt;/ul&gt;
  5142. &lt;/li&gt;
  5143. &lt;/ul&gt;
  5144. &lt;/li&gt;
  5145. &lt;/ul&gt;
  5146. &lt;h4&gt;Information Management/Sidebar&lt;/h4&gt;
  5147. &lt;ul&gt;
  5148. &lt;li&gt;There’s been a few fixes for the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1970666&quot;&gt;drag-to-pin work&lt;/a&gt; that’s in 143; these will be in the dot release.
  5149. &lt;ul&gt;
  5150. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1988996&quot;&gt;Add a check for promo card to ensure we don’t show it prematurely&lt;/a&gt;&lt;/li&gt;
  5151. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1989344&quot;&gt;1989344 – Adjust interaction cue timing for drag to pin&lt;/a&gt;&lt;/li&gt;
  5152. &lt;/ul&gt;
  5153. &lt;/li&gt;
  5154. &lt;li&gt;Nikki has improved tab animation for vertical and horizontal tabs with &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983124&quot;&gt;tab stacking&lt;/a&gt;&lt;/li&gt;
  5155. &lt;li&gt;Split View work is still early days but the meta bug is &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980370&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
  5156. &lt;li&gt;We’re aiming to get sidebar.revamp turned on by default in Nightly only in 145 so we’re greening up a few tests then work on some old sidebar parity bugs before enabling this in release.&lt;/li&gt;
  5157. &lt;/ul&gt;
  5158. &lt;h4&gt;Profile Management&lt;/h4&gt;
  5159. &lt;ul&gt;
  5160. &lt;li&gt;Jared fixed bug 1941854, [Windows] Additional window (skeleton UI) opens with Profile Selector on Firefox startup&lt;/li&gt;
  5161. &lt;li&gt;Maile fixed bug 1955173, The favicons of the Profiles about: pages are not displayed properly in the List all tabs menu&lt;/li&gt;
  5162. &lt;li&gt;Niklas fixed bug 1965598, The Usage Profile Group ID should be shared by all profiles in a group&lt;/li&gt;
  5163. &lt;li&gt;Jaws fixed bug 1987317, Firefox won’t launch a profile if the library of that profile is open&lt;/li&gt;
  5164. &lt;li&gt;Jaws fixed bug 1988882, SelectableProfileService uses the wrong value for the rgb color property&lt;/li&gt;
  5165. &lt;li&gt;Jaws fixed bug 1990020, Small fixes in SelectableProfileService&lt;/li&gt;
  5166. &lt;/ul&gt;
  5167. &lt;h4&gt;Search and Navigation&lt;/h4&gt;
  5168. &lt;ul&gt;
  5169. &lt;li&gt;Work continues on modularising and re-using the address bar code to &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1974218&quot;&gt;replace the existing search bar&lt;/a&gt;.
  5170. &lt;ul&gt;
  5171. &lt;li&gt;This will allow us to simplify the existing code, remove dependence on the toolkit autocomplete widget, and bring more features to the separate search bar.&lt;/li&gt;
  5172. &lt;/ul&gt;
  5173. &lt;/li&gt;
  5174. &lt;li&gt;&lt;/li&gt;
  5175. &lt;li&gt;Search Engines identifiers and telemetry.
  5176. &lt;ul&gt;
  5177. &lt;li&gt;We’ve now &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1877721&quot;&gt;removed&lt;/a&gt; nsISearchEngine.identifier, and deprecated nsISearchEngine.telemetryId. nsISearchEngine.id still exists.
  5178. &lt;ul&gt;
  5179. &lt;li&gt;These are fields that would contain a mixture of information about a search engine (an identifier, partner code and sometimes more). This would analysis via telemetry more difficult.&lt;/li&gt;
  5180. &lt;/ul&gt;
  5181. &lt;/li&gt;
  5182. &lt;li&gt;If you’re reporting search engine information either via telemetry or to other systems, please use the separate id / partnerCode fields on nsISearchEngine or check with the search team for your case.&lt;/li&gt;
  5183. &lt;/ul&gt;
  5184. &lt;/li&gt;
  5185. &lt;/ul&gt;
  5186. &lt;h4&gt;Storybook/Reusable Components/Acorn Design System&lt;/h4&gt;
  5187. &lt;ul&gt;
  5188. &lt;li&gt;moz-button supports type=”split”(&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1858811&quot;&gt;Bug 1858811&lt;/a&gt;). Setting menuId on the split button links its “More options” button to a panel-list with the same id. (&lt;a href=&quot;https://firefoxux.github.io/firefox-desktop-components/?path=/story/ui-widgets-button--split-button&quot;&gt;Storybook&lt;/a&gt;)&lt;/li&gt;
  5189. &lt;/ul&gt;
  5190. &lt;p&gt;&lt;img alt=&quot;Split button component&quot; class=&quot;alignnone size-large wp-image-1905&quot; height=&quot;308&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/10/headlines190_1-600x308.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  5191. &lt;ul&gt;
  5192. &lt;li&gt;Support for the support-page attribute was added to the moz-box-item (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1990839&quot;&gt;Bug 1990839&lt;/a&gt;)&lt;/li&gt;
  5193. &lt;li&gt;New –font-size-xxlarge (2.2rem – 33px) token was added. (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1961988&quot;&gt;Bug 1961988&lt;/a&gt;)&lt;/li&gt;
  5194. &lt;li&gt;Usage of border-radius was updated to use design tokens values (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983938&quot;&gt;Bug 1983938&lt;/a&gt;)&lt;/li&gt;
  5195. &lt;/ul&gt;</description>
  5196. <pubDate>Mon, 06 Oct 2025 20:11:37 +0000</pubDate>
  5197. <dc:creator>Anna Kulyk</dc:creator>
  5198. </item>
  5199. <item>
  5200. <title>Mozilla Thunderbird: VIDEO: Conversation View</title>
  5201. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3830</guid>
  5202. <link>https://blog.thunderbird.net/2025/10/video-conversation-view/</link>
  5203. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/10/blog-banner-community-hours2-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  5204. &lt;p&gt;Welcome back to another edition of the Community Office Hours! This month, we’re showing you our first steps towards a long awaited feature: a genuine Conversation View! Our guests are Alessandro Castellani, Director of Desktop and Mobile Apps and Geoff Lankow, Sr. Staff Software Engineer on the Desktop team. They recently attended a work week in Vancouver that brought together developers and designers to create our initial vision and plan to bring Conversation View from dream to reality. Before Geoff flew home, he joined Alessandro and us to discuss his backend database work that will make Conversation View possible. We also had a peek at the workweek itself, other features possible with our new database, and our tentative delivery timeline.&lt;/p&gt;
  5205.  
  5206.  
  5207.  
  5208. &lt;p&gt;We’ll be back next month with an Office Hours all about Exchange Support for email, which is landing soon in our monthly Release channel. &lt;/p&gt;
  5209.  
  5210.  
  5211.  
  5212. &lt;h3&gt;September Office Hours: Conversation View&lt;/h3&gt;
  5213.  
  5214.  
  5215.  
  5216. &lt;p&gt;Some of you might be asking, “what IS Conversation View?” Basically, it’s a Gmail-like visualization of a message thread when reading emails. So, in contrast to the current threaded view, you have all the messages in a thread. This both includes your replies and any other messages that may have been moved to a different folder.&lt;/p&gt;
  5217.  
  5218.  
  5219.  
  5220. &lt;p&gt;So, why hasn’t Thunderbird been able to do this already? The short answer is that our code is old. Netscape Navigator old. Our current ‘database,’ Mork, makes a mail folder summary (an .msf file) per folder. These files are text-based unicode and are NOT human readable. In Thunderbird 3, we introduced Gloda, our Global Search and Indexer, to try and work around Mork’s limitations. It indexes what’s in the .msf file and stores the data in a SQLite file. But as you might already know, Gloda itself is clunky and slow.&lt;/p&gt;
  5221.  
  5222.  
  5223.  
  5224. &lt;h3&gt;Modern Solutions for Modern Problems&lt;/h3&gt;
  5225.  
  5226.  
  5227.  
  5228. &lt;p&gt;If we want Conversation View (and other features users now expect), we need to bring Thunderbird further into the 21st century. Hence, our work on a new database, which we’re calling Panorama. It’s a single SQLite database with all your messages. Panorama indexes emails as soon as they’re received, and since it’s SQLite, it’s not only fast, but it can be read by so many tools.&lt;/p&gt;
  5229.  
  5230.  
  5231.  
  5232. &lt;p&gt;Since all of your messages will be in a single SQLite database, we can do more than enable a true Conversation view. Panorama will improve global search, enable improved filters, and more. Needless to say, we’re excited about all the possibilities!&lt;/p&gt;
  5233.  
  5234.  
  5235.  
  5236. &lt;h3&gt;Conversation View Workweek&lt;/h3&gt;
  5237.  
  5238.  
  5239.  
  5240. &lt;p&gt;To get these possibilities started, we decided to bring developers and designers together for a Conversation View Workweek in Vancouver in early September. This brought people out of Zoom calls, emails, and Matrix messages, and across the Pacific Ocean in Geoff’s case, into one place to discuss technical and design challenges. &lt;/p&gt;
  5241.  
  5242.  
  5243.  
  5244. &lt;p&gt;We’ve spoken previously about our design system and how we’ve collaborated between &lt;a href=&quot;https://blog.thunderbird.net/2025/03/video-the-thunderbird-design-system/&quot;&gt;design and development&lt;/a&gt; on features like &lt;a href=&quot;https://blog.thunderbird.net/2025/04/video-the-new-account-hub/&quot;&gt;Account Hub&lt;/a&gt;. In-person collaboration, especially for something as complicated as a new database and message view, was invaluable. By the end of the week, developers and designers alike had plenty to show for their efforts.&lt;/p&gt;
  5245.  
  5246.  
  5247.  
  5248. &lt;h3&gt;Next Steps&lt;/h3&gt;
  5249.  
  5250.  
  5251.  
  5252. &lt;p&gt;Before you get too excited, the new database and Conversation view won’t land until after next year’s ESR release. There’s a lot of work to do, including testing Panorama in a standalone space until we’re ready to run Mork and Panorama alongside each other, along with the old and new code referencing each database. We need the migration to be seamless and easily reversible, and so we want to take the time to get this absolutely right.&lt;/p&gt;
  5253.  
  5254.  
  5255.  
  5256. &lt;p&gt;Want to stay up to date on our progress? We recommend subscribing to our Planning and &lt;a href=&quot;https://thunderbird.topicbox.com/groups/ux&quot;&gt;UX&lt;/a&gt; mailing lists, State of the Thunder &lt;a href=&quot;https://www.youtube.com/playlist?list=PLMY3ZzVsXXyqSVZHS10hold60Uqb97xzD&quot;&gt;videos&lt;/a&gt; and &lt;a href=&quot;https://blog.thunderbird.net/tag/state-of-the-thunder/&quot;&gt;blog posts&lt;/a&gt;, and the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1920833&quot;&gt;meta bug on Bugzilla&lt;/a&gt;.&lt;/p&gt;
  5257.  
  5258.  
  5259.  
  5260. &lt;h4&gt;VIDEO (Also &lt;a href=&quot;https://tilvids.com/w/h1KPSVsB7BfL5LxtEU4PB6&quot;&gt;on Peertube&lt;/a&gt;):&lt;/h4&gt;
  5261.  
  5262.  
  5263.  
  5264. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  5265.  
  5266. &lt;/div&gt;&lt;/figure&gt;
  5267.  
  5268.  
  5269.  
  5270. &lt;h3&gt;Slides:&lt;/h3&gt;
  5271.  
  5272.  
  5273.  
  5274. &lt;div class=&quot;wp-block-file&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/10/Conversation-View-Community-Office-Hours-Presentation.pdf&quot; id=&quot;wp-block-file--media-2d726133-12fc-4117-a5e6-734962ae66d2&quot;&gt;Conversation-View-Community-Office-Hours-Presentation&lt;/a&gt;&lt;a class=&quot;wp-block-file__button wp-element-button&quot; href=&quot;https://blog.thunderbird.net/files/2025/10/Conversation-View-Community-Office-Hours-Presentation.pdf&quot;&gt;Download&lt;/a&gt;&lt;/div&gt;
  5275.  
  5276.  
  5277.  
  5278. &lt;h3&gt;Resources:&lt;/h3&gt;
  5279. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/10/video-conversation-view/&quot;&gt;VIDEO: Conversation View&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  5280. <pubDate>Mon, 06 Oct 2025 18:08:18 +0000</pubDate>
  5281. <dc:creator>Monica Ayhens-Madon</dc:creator>
  5282. </item>
  5283. <item>
  5284. <title>The Mozilla Blog: Building a fairer future for digital advertising: Mozilla partners with Index Exchange</title>
  5285. <guid isPermaLink="false">https://blog.mozilla.org/?p=82082</guid>
  5286. <link>https://blog.mozilla.org/en/advertising/index-exchange-partnership/</link>
  5287. <description>&lt;figure class=&quot;wp-block-image size-large is-resized&quot;&gt;&lt;img alt=&quot;Black background featuring two white logos: ‘Mozilla Ads’ on the left and ‘Index Exchange’ on the right, separated by a thin vertical line.&quot; class=&quot;wp-image-82083&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/MozillaAds_AWNYFireside_10_03.006-1024x576.jpeg&quot; style=&quot;width: 840px; height: auto;&quot; width=&quot;1024&quot; /&gt;&lt;/figure&gt;
  5288.  
  5289.  
  5290.  
  5291. &lt;p&gt;Advertising can and should work better — for people, for publishers, and for brands. That belief is what drives Mozilla’s growing investment in rebuilding digital advertising around trust, transparency and fairness.&lt;/p&gt;
  5292.  
  5293.  
  5294.  
  5295. &lt;p&gt;For too long, the web’s primary funding model has relied on hidden data collection and opaque ad systems that work around users instead of with them. Mozilla’s approach is different: We’re building an alternative that aligns commercial success with user respect, giving advertisers new ways to show up responsibly in environments people actually trust.&lt;br /&gt;&lt;br /&gt;“Advertising funds the open internet, but it needs a new foundation,” said Suba Vasudevan, COO of Mozilla.org and SVP at Mozilla Corp. “Advertisers have always cared about brand safety. The missing piece has been trust in the platforms where ads run. That’s the gap Mozilla is closing; making the advertising environment itself something that both brands and users can trust. And we do this all while protecting the privacy of our users’ data.”&lt;br /&gt;&lt;br /&gt;This week at Advertising Week New York 2025, Mozilla announced a key step in that journey — a partnership with Index Exchange, one of the world’s largest independent ad exchanges. Together, we’re proving that trusted environments can also deliver trusted performance.&lt;br /&gt;&lt;br /&gt;“Our partnership with Mozilla demonstrates how programmatic can evolve to create stronger outcomes for brands and better experiences for consumers,” said Lori Goode, CMO of Index Exchange. “By uniting Mozilla’s trusted environment with Index’s infrastructure, we’re building a model of programmatic rooted in quality, accountability, and long-term value.”&lt;/p&gt;
  5296.  
  5297.  
  5298.  
  5299. &lt;h3&gt;Creating a new model for responsible advertising&lt;/h3&gt;
  5300.  
  5301.  
  5302.  
  5303. &lt;p&gt;The collaboration between Mozilla and Index Exchange is part of a larger effort to evolve how advertising supports the open web. It’s about expanding options for marketers who want to reach audiences in ways that are both effective and ethical — replacing tracking-heavy systems with transparent, trust-centered design.&lt;/p&gt;
  5304.  
  5305.  
  5306.  
  5307. &lt;p&gt;• &lt;strong&gt;Scale where it matters.&lt;/strong&gt; For marketers committed to building on trusted platforms, curated PMP deals with Mozilla and Index Exchange offer a way to connect with engaged audiences in respectful, brand-safe environments — aligning performance goals with user trust in the fastest-growing programmatic channel (~88% of global spend).&lt;/p&gt;
  5308.  
  5309.  
  5310.  
  5311. &lt;p&gt;• &lt;strong&gt;No personal identifiers. &lt;/strong&gt;Mozilla and Index Exchange ensure that no personal identifiers or cross-site tracking are ever used — reflecting our shared commitment to respect users and create ad experiences people can trust.&lt;/p&gt;
  5312.  
  5313.  
  5314.  
  5315. &lt;p&gt;• &lt;strong&gt;Future-ready monetization. &lt;/strong&gt;Firefox research shows that even privacy-minded users welcome thoughtful personalization when it improves their experience — but only when delivered responsibly and with clear user control.&lt;br /&gt;&lt;br /&gt;• &lt;strong&gt;A unique audience opportunity. &lt;/strong&gt;Firefox reaches hundreds of millions of people worldwide, offering marketers the chance to build connections in a trusted, brand-safe environment with engaged audiences often underrepresented on other platforms.&lt;/p&gt;
  5316.  
  5317.  
  5318.  
  5319. &lt;h3&gt;On stage at Advertising Week New York&lt;/h3&gt;
  5320.  
  5321.  
  5322.  
  5323. &lt;p&gt;Mozilla and Index Exchange will debut the partnership during a keynote conversation, “Adding Trust to Your Ad Buy: The Smartest Spend in Marketing Today,” on the Advertising Week Innovation Stage, Monday, Oct. 6. The session will explore how advertisers can drive performance by investing in trust — not just in creative or campaigns, but in the platforms that power them.&lt;br /&gt;&lt;br /&gt;At Mozilla, we’ve always believed that advertising, done responsibly, can help sustain the open web. This partnership is proof of that belief — a tangible example of how innovation and trust can go hand in hand, delivering value for advertisers and for the internet itself. For more about Mozilla Ads, visit: &lt;a href=&quot;https://www.mozilla.org/en-US/advertising/&quot;&gt;https://www.mozilla.org/en-US/advertising/&lt;/a&gt;.&lt;/p&gt;
  5324. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/advertising/index-exchange-partnership/&quot;&gt;Building a fairer future for digital advertising: Mozilla partners with Index Exchange&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  5325. <pubDate>Mon, 06 Oct 2025 16:53:52 +0000</pubDate>
  5326. <dc:creator>Jennifer Guerra</dc:creator>
  5327. </item>
  5328. <item>
  5329. <title>The Mozilla Blog: Anonym and Snap partner to unlock increased performance for advertisers</title>
  5330. <guid isPermaLink="false">https://blog.mozilla.org/?p=82070</guid>
  5331. <link>https://blog.mozilla.org/en/advertising/anonym/anonym-snap-partnership/</link>
  5332. <description>&lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;The Anonym wordmark and the Snap, Inc. logo are shown side by side.&quot; class=&quot;wp-image-82071&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/10/Distilled_SnapAnonym@2x-1024x576.png&quot; width=&quot;1024&quot; /&gt;&lt;/figure&gt;
  5333.  
  5334.  
  5335.  
  5336. &lt;p&gt;&lt;em&gt;&lt;strong&gt;An ads milestone in marketing reach without data risk.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
  5337.  
  5338.  
  5339.  
  5340. &lt;p&gt;The ad industry is shifting, and with it comes a clear need for advertisers to use data responsibly while still proving impact. Advertisers face a false choice between protecting privacy and proving performance. Anonym exists to prove they can have both — and this week marks a major milestone in that mission.&lt;/p&gt;
  5341.  
  5342.  
  5343.  
  5344. &lt;p&gt;Today we announced a new partnership with Snap Inc., giving advertisers a way to use more of their first-party data safely and effectively. This collaboration shows what’s possible when privacy and performance go hand in hand: Marketers can unlock real insights into how campaigns drive results, without giving up data control.&lt;/p&gt;
  5345.  
  5346.  
  5347.  
  5348. &lt;h3&gt;Unleashing first-party data that’s often untapped&lt;/h3&gt;
  5349.  
  5350.  
  5351.  
  5352. &lt;p&gt;Unlocking value while maintaining privacy of advertisers’ sensitive first-party (1P) data has long been a challenge for advertisers concerned with exposure or technical friction. We set out to change this equation, enabling brands to safely activate data sets to measure conversion lift and attribution.&lt;/p&gt;
  5353.  
  5354.  
  5355.  
  5356. &lt;p&gt;With Snapchat campaigns, advertisers can now bring first-party data that’s typically been inaccessible into play and understand how ads on the platform drive real-world actions — from product discovery to purchase. Instead of relying only on proxy signals or limited datasets, brands can generate more complete, incrementality-based insights on their Snapchat performance, gaining a clearer picture of the channel’s true contribution to business outcomes.&lt;/p&gt;
  5357.  
  5358.  
  5359.  
  5360. &lt;p&gt;“Marketers possess deep reserves of first-party data that too often sits idle because it’s seen as difficult or risky to use,” said Graham Mudd, Senior Vice President, Product, Mozilla and Anonym co-founder. “Our partnership with Snap gives advertisers the power to prove outcomes with confidence, and do it in a way that is both tightly controlled and insight-rich.”&lt;/p&gt;
  5361.  
  5362.  
  5363.  
  5364. &lt;h3&gt;Snapchat audience scale: Reach meets relevance&lt;/h3&gt;
  5365.  
  5366.  
  5367.  
  5368. &lt;p&gt;With a reach of over 930 million monthly active users globally (MAUs), including 469 million daily active users — Snap’s rapidly growing audience makes it a uniquely powerful marketing channel. This breadth of reach is especially appealing to advertisers who previously avoided activating sensitive data—knowing they can now connect securely with high-value Snapchatters at scale.&lt;/p&gt;
  5369.  
  5370.  
  5371.  
  5372. &lt;p&gt;Our solution is designed for ease of use, requiring minimal technical resources and enabling advertisers to go from kickoff to measurement reporting within weeks. Our collaboration with Snap furthers the mission of lowering barriers to entry in advertising, and enables brands of all sizes to confidently activate their competitive insights on Snapchat.&lt;/p&gt;
  5373.  
  5374.  
  5375.  
  5376. &lt;p&gt;“Snapchat is where people make real choices, and advertisers need simple, clear insights into how their campaigns perform,” said Elena Bond, Head of Marketing Science, Snap Inc. “By working with Anonym, we’re making advanced measurement accessible to more brands — helping them broaden their reach, uncover deeper insights, and prove results, all while maintaining strict control of their data.”&lt;/p&gt;
  5377.  
  5378.  
  5379.  
  5380. &lt;h3&gt;How Anonym works: Simple, secure, scalable&lt;/h3&gt;
  5381.  
  5382.  
  5383.  
  5384. &lt;p&gt;Using end-to-end encryption, trusted execution environments (TEE), and differential privacy to guarantee protection and streamline compliance, Anonym helps advertisers connect with new, high-value customers and analyze campaign effectiveness without giving up data control. Strategic reach and actionable measurement are achieved with:&lt;/p&gt;
  5385.  
  5386.  
  5387.  
  5388. &lt;ul&gt;
  5389. &lt;li&gt;Advertiser-controlled: First-party data is never transferred to the ad platform.&lt;/li&gt;
  5390.  
  5391.  
  5392.  
  5393. &lt;li&gt;Minimal technical lift: From campaign start to measurement, reporting can be completed in weeks—no heavy engineering or data science overhead.&lt;/li&gt;
  5394.  
  5395.  
  5396.  
  5397. &lt;li&gt;Performance-focused: The outcome is clear insights into campaign lift and attribution, powering better investment decisions.&lt;/li&gt;
  5398.  
  5399.  
  5400.  
  5401. &lt;li&gt;Regulation-ready: Provides advertisers with tools to help meet evolving privacy requirements, supporting responsible data use as rules change.&lt;/li&gt;
  5402. &lt;/ul&gt;
  5403.  
  5404.  
  5405.  
  5406. &lt;p&gt;Anonym and Snap’s collaboration coincides with &lt;a href=&quot;https://advertisingweek.com/event/awnewyork-2025&quot;&gt;Advertising Week New York 2025&lt;/a&gt;, where measurement and data innovation will be in sharp focus. &lt;/p&gt;
  5407.  
  5408.  
  5409.  
  5410. &lt;a class=&quot;ft-c-inline-cta&quot; href=&quot;https://www.anonymco.com/&quot;&gt;
  5411.  &lt;div class=&quot;ft-c-inline-cta__media&quot;&gt;
  5412.  &lt;img alt=&quot;A teal lock icon next to the bold text &amp;quot;Anonym&amp;quot; on a black background.&quot; class=&quot;attachment-1x1 size-1x1&quot; height=&quot;800&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/10/Blog_Anonym_Thumbnail-800x800.png&quot; width=&quot;800&quot; /&gt;  &lt;/div&gt;
  5413.  &lt;div class=&quot;ft-c-inline-cta__content&quot;&gt;
  5414.     &lt;h4&gt;Performance, powered by privacy&lt;/h4&gt;      &lt;span&gt;Learn more about Anonym&lt;/span&gt;   &lt;/div&gt;
  5415. &lt;/a&gt;
  5416. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/advertising/anonym/anonym-snap-partnership/&quot;&gt;Anonym and Snap partner to unlock increased performance for advertisers&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  5417. <pubDate>Thu, 02 Oct 2025 23:12:10 +0000</pubDate>
  5418. <dc:creator>Jennifer Guerra</dc:creator>
  5419. </item>
  5420. <item>
  5421. <title>Support.Mozilla.Org: Ask a Fox: A full week celebration of community power</title>
  5422. <guid isPermaLink="false">https://blog.mozilla.org/sumo/?p=4185</guid>
  5423. <link>https://blog.mozilla.org/sumo/2025/10/02/ask-a-fox/</link>
  5424. <description>&lt;p&gt;From September 22–28, the Mozilla Support team ran our first-ever &lt;a href=&quot;http://community.mozilla.org/campaigns/ask-a-fox/&quot;&gt;&lt;b&gt;Mozilla – Ask a Fox&lt;/b&gt;&lt;/a&gt; virtual hackathon. In collaboration with the Thunderbird team, we invited contributors, community members, and staff to jump into the Mozilla Community Forums, lend a hand to Firefox and Thunderbird users, and experience the power of Mozillians coming together.&lt;/p&gt;
  5425. &lt;h3&gt;Rallying the Community&lt;/h3&gt;
  5426. &lt;p&gt;The idea was simple: we want to bring not only our long time community members, but newcomers and Mozilla staff together for one-week of focused engagement. The result was extraordinary.&lt;/p&gt;
  5427. &lt;ul&gt;
  5428. &lt;li&gt;The event generated strong momentum for both new and returning community members. This was reflected in the &lt;b&gt;significant growth in total contributors, which rose by 41.6 %&lt;/b&gt;.&lt;/li&gt;
  5429. &lt;li&gt;For the past year, our Community Forum had been struggling to maintain a strong reply rate as inbound questions grew. During the event, however, we achieved our &lt;b&gt;highest weekly reply rate of the year&lt;/b&gt;, which was more than 50% above our daily average from the first half of 2025.&lt;/li&gt;
  5430. &lt;li&gt;&lt;b&gt;Time to first response (TTFR) also improved by 44.6%&lt;/b&gt;, which signal significant improvement in community responsiveness. The event also highlighted the importance of time to first response (TTFR) not just for users, but for the community as a whole. We saw a clear correlation: &lt;i&gt;the faster users received their first reply, the more likely they were to return and continue the conversation.&lt;/i&gt;&lt;/li&gt;
  5431. &lt;/ul&gt;
  5432. &lt;p&gt;Together, we showed just how responsive and effective our community can be when we rally around a common goal.&lt;/p&gt;
  5433. &lt;h3&gt;More Than Answering Forum Questions&lt;/h3&gt;
  5434. &lt;p&gt;Ask a Fox wasn’t only about answering questions—it was about connection. Throughout the week, we hosted special AMAs with the &lt;a href=&quot;https://www.youtube.com/watch?v=GFF5NBSN-8I&amp;amp;t=2980s&quot;&gt;&lt;b&gt;WebCompat&lt;/b&gt;&lt;/a&gt;, &lt;a href=&quot;https://www.youtube.com/watch?v=apYYhHJINFY&amp;amp;t=3249s&quot;&gt;&lt;b&gt;Web Performance&lt;/b&gt;&lt;/a&gt;, and &lt;a href=&quot;https://www.youtube.com/watch?v=ldnv11tF6iY&amp;amp;t=245s&quot;&gt;&lt;b&gt;Thunderbird&lt;/b&gt;&lt;/a&gt; teams, giving contributors the chance to engage directly with product experts. We also ran two Community Get Together calls to gather, share stories, and celebrate the spirit of collaboration.&lt;/p&gt;
  5435. &lt;p&gt;For some added fun, we also launched a and ⚡ emoji hunt accross our Knowledge Base articles.&lt;/p&gt;
  5436. &lt;h3&gt;Recognizing contributors&lt;/h3&gt;
  5437. &lt;p&gt;We’re grateful for the incredible participation during the event and want to recognize the contributors who went above and beyond. Those who participated in our challenges should receive exclusive &lt;a href=&quot;https://support.mozilla.org/badges/&quot;&gt;SUMO badges&lt;/a&gt; in their profile by now. And the following top five contributors for each product will soon receive a $25 swag voucher from us to shop our limited-edition Ask a Fox swag collection, available in the &lt;a href=&quot;https://mozilla-na.myspreadshop.com/ask+a+fox?collection=NfnWgqXmlH&quot;&gt;NA&lt;/a&gt;/&lt;a href=&quot;https://mozilla-europe.myspreadshop.ie/ask+a+fox?collection=MHMWMgYnoP&quot;&gt;EU&lt;/a&gt; swag store.&lt;/p&gt;
  5438. &lt;p&gt;&lt;b&gt;Firefox desktop (including Enterprise)&lt;/b&gt;&lt;/p&gt;
  5439. &lt;p&gt;Congrats to &lt;a href=&quot;https://support.mozilla.org/user/plwt/&quot;&gt;Paul&lt;/a&gt;&lt;b&gt;, &lt;/b&gt;&lt;a href=&quot;https://support.mozilla.org/user/denyshon/&quot;&gt;Denyshon&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/jonzn4SUSE/&quot;&gt;Jonz4SUSE&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/@next/&quot;&gt;@next&lt;/a&gt;, and &lt;a href=&quot;https://support.mozilla.org/user/jscher2000/&quot;&gt;jscher2000&lt;/a&gt;.&lt;/p&gt;
  5440. &lt;p&gt;&lt;b&gt;Firefox for Android&lt;/b&gt;&lt;/p&gt;
  5441. &lt;p&gt;Congrats to &lt;a href=&quot;https://support.mozilla.org/user/plwt/&quot;&gt;Paul&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/en-US/user/TyDraniu/&quot;&gt;TyDraniu&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/pcp04/&quot;&gt;GerardoPcp04&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/Mad_Maks/&quot;&gt;Mad_Maks&lt;/a&gt;, and &lt;a href=&quot;https://support.mozilla.org/user/sjohnn/&quot;&gt;sjohnn&lt;/a&gt;.&lt;/p&gt;
  5442. &lt;p&gt;&lt;b&gt;Firefox for iOS &lt;/b&gt;&lt;/p&gt;
  5443. &lt;p&gt;Congratulations to &lt;a href=&quot;https://support.mozilla.org/user/plwt/&quot;&gt;Paul&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/simon.c.lord/&quot;&gt;Simon.c.lord&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/en-US/user/TyDraniu/&quot;&gt;TyDraniu&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/Mad_Maks/&quot;&gt;Mad_Maks&lt;/a&gt;, and &lt;a href=&quot;https://support.mozilla.org/user/Mozilla-assistent/&quot;&gt;Mozilla-assistent&lt;/a&gt;.&lt;/p&gt;
  5444. &lt;p&gt;&lt;b&gt;Thunderbird (including Thunderbird for Android)&lt;/b&gt;&lt;/p&gt;
  5445. &lt;p&gt;Congratulations to &lt;a href=&quot;https://support.mozilla.org/user/davidsk/&quot;&gt;Davidsk&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/sfhowes/&quot;&gt;Sfhowes&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/mozilla98/&quot;&gt;Mozilla98&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/MattAuSupport/&quot;&gt;MattAuSupport&lt;/a&gt;, and &lt;a href=&quot;https://support.mozilla.org/user/christ1/&quot;&gt;Christ1&lt;/a&gt;.&lt;/p&gt;
  5446. &lt;p&gt; &lt;/p&gt;
  5447. &lt;p&gt;We also want to extend a warm welcome to newcomers who made impressive impact during the event: &lt;a href=&quot;https://support.mozilla.org/user/mozilla98/&quot;&gt;mozilla98&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/starretreat/&quot;&gt;starretreat&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/sjohnn/&quot;&gt;sjohnn&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/Vexi/&quot;&gt;Vexi&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/Mark/&quot;&gt;Mark&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/Mapenzi/&quot;&gt;Mapenzi&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/cartdaniel437/&quot;&gt;cartdaniel437&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/user/hariiee1277/&quot;&gt;hariiee1277&lt;/a&gt;, and &lt;a href=&quot;https://support.mozilla.org/user/thisisharsh7/&quot;&gt;thisisharsh7&lt;/a&gt;.&lt;/p&gt;
  5448. &lt;p&gt;And finally, congratulations to &lt;a href=&quot;https://support.mozilla.org/user/Vinnl/&quot;&gt;Vincent&lt;/a&gt;, winner of the staff award for the highest number of replies during the week.&lt;/p&gt;
  5449. &lt;hr /&gt;
  5450. &lt;p&gt;Ask a Fox was more than a campaign—it was a celebration of what makes Mozilla unique: a global community of people who care deeply about helping others and shaping a better web. Whether you answered one question or one hundred, your contribution mattered.&lt;/p&gt;
  5451. &lt;p&gt;This event reminded us that when Mozillians come together, we can amplify our impact in powerful ways. And this is just the beginning—we’re excited to carry this momentum forward, continue improving the Community Forums, and build an even stronger, more responsive Mozilla community for everyone.&lt;/p&gt;</description>
  5452. <pubDate>Thu, 02 Oct 2025 09:57:47 +0000</pubDate>
  5453. <dc:creator>Rizki Kelimutu</dc:creator>
  5454. </item>
  5455. <item>
  5456. <title>The Mozilla Blog: Celebrate the power of browser choice with Firefox. Join us live.</title>
  5457. <guid isPermaLink="false">https://blog.mozilla.org/?p=81994</guid>
  5458. <link>https://blog.mozilla.org/en/firefox/firefox-celebrates-browser-choice-house-blend-events/</link>
  5459. <description>&lt;p&gt;Firefox is celebrating 21 years of Firefox by hosting four global events celebrating the power of browser choice this fall. &lt;/p&gt;
  5460.  
  5461.  
  5462.  
  5463. &lt;p&gt;We are inviting people to join us in Berlin, Chicago, Los Angeles and Munich as part of Open What You Want, Firefox’s campaign to celebrate choice and the freedom to show up exactly as you are — whether that’s in your coffee order, the music you dance to, or the browser you use. These events are an opportunity to highlight why browser choice matters and why Firefox stands apart as the last major independent option.&lt;/p&gt;
  5464.  
  5465.  
  5466.  
  5467. &lt;p&gt;Firefox is built differently with a &lt;a href=&quot;https://blog.mozilla.org/en/firefox/firefox-wants-you-join-daily-defiance/&quot;&gt;history of defiance&lt;/a&gt;. It is built in a way to best push back against the defaults of Big Tech. Firefox is the only major browser not backed by a billionaire or built on Chromium’s browser engine. Instead, Firefox is backed by a non-profit, and maintains and runs on Gecko, a flexible, independent, open-source browser engine.&lt;/p&gt;
  5468.  
  5469.  
  5470.  
  5471. &lt;p&gt;So, it makes sense that we are celebrating differently too. We are inviting people to join us at four community-driven “House Blend” coffee rave events. What is a coffee rave? A caffeine-fueled day rave celebrating choice, freedom, and doing things your own way – online and off. These events are open to everyone and in partnership with local coffee shops.&lt;/p&gt;
  5472.  
  5473.  
  5474.  
  5475. &lt;p&gt;Each event will have free coffee, exclusive merch, sets by two great, local DJs, a lot of dancing, and an emphasis on how individuals should &lt;a href=&quot;https://www.mozilla.org/en-US/about/manifesto/details/&quot;&gt;get to shape their online experience and feel control online&lt;/a&gt; — and you can’t feel in control without choice.&lt;/p&gt;
  5476.  
  5477.  
  5478.  
  5479. &lt;p&gt;We are kicking off the celebrations this Saturday, Oct. 4 in both Chicago and Berlin, will move to Munich the following Saturday, Oct. 11 and will end in Los Angeles Saturday, Nov. 8, for Firefox’s actual birthday weekend.&lt;/p&gt;
  5480.  
  5481.  
  5482.  
  5483. &lt;p&gt;&lt;strong&gt;Berlin&lt;/strong&gt; &lt;strong&gt;(RSVP &lt;/strong&gt;&lt;a href=&quot;https://docs.google.com/forms/d/e/1FAIpQLSfbBkfWTNH-xyVASvi4rK_B6z1H2G2wTH7aKk7v-2-gjzWyEA/viewform&quot;&gt;&lt;strong&gt;here&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;)&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;When:&lt;/strong&gt; Saturday, Oct. 4, 2025 | 13:00 – 16:00 CEST&lt;br /&gt;&lt;strong&gt;Where:&lt;/strong&gt; Café Bravo, Auguststraße 69, 10117 Berlin-Mitte&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Chicago (RSVP &lt;/strong&gt;&lt;a href=&quot;https://partiful.com/e/TCXRsuTjct4cHHhrdCUN&quot;&gt;&lt;strong&gt;here&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;)&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;When:&lt;/strong&gt; Saturday, Oct. 4, 2025 | 10:00AM – 2:00PM CT&lt;br /&gt;&lt;strong&gt;Where:&lt;/strong&gt; Drip Collective, 172 N Racine Ave, Chicago Illinois &lt;/p&gt;
  5484.  
  5485.  
  5486.  
  5487. &lt;p&gt;&lt;strong&gt;Munich (RSVP &lt;/strong&gt;&lt;a href=&quot;https://docs.google.com/forms/d/e/1FAIpQLSeEV81Hq9j1apb60kjZ3qoMQQ0fgKrt9w-aicfxL7fIZKgFzQ/viewform&quot;&gt;&lt;strong&gt;here&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;)&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;When:&lt;/strong&gt; Saturday, Oct. 11, 2025 | 13:00 – 16:00 CEST&lt;br /&gt;&lt;strong&gt;Where:&lt;/strong&gt; ORNO Café, Fraunhoferstraße 11, 80469 München&lt;/p&gt;
  5488.  
  5489.  
  5490.  
  5491. &lt;p&gt;&lt;strong&gt;Los Angeles &lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;When:&lt;/strong&gt; Saturday, Nov. 8, 2025 &lt;br /&gt;More information to come&lt;/p&gt;
  5492.  
  5493.  
  5494.  
  5495. &lt;p&gt;We hope you will join our celebration this year, in person at a coffee rave, or at one of our digital-first activations &lt;a href=&quot;https://blog.mozilla.org/en/firefox/billionaire-blas-off/&quot;&gt;celebrating internet independence&lt;/a&gt;.  As Firefox reflects on another year, it’s a good reminder that the most important choice you can make online is your browser. And browser choice is something that we should all celebrate and not take for granted&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;
  5496.  
  5497.  
  5498. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/firefox/firefox-celebrates-browser-choice-house-blend-events/&quot;&gt;Celebrate the power of browser choice with Firefox. Join us live.&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  5499. <pubDate>Wed, 01 Oct 2025 17:02:44 +0000</pubDate>
  5500. <dc:creator>Rebecca Smith</dc:creator>
  5501. </item>
  5502. <item>
  5503. <title>The Mozilla Blog: Blast off! Firefox turns data power plays into a game</title>
  5504. <guid isPermaLink="false">https://blog.mozilla.org/?p=81851</guid>
  5505. <link>https://blog.mozilla.org/en/firefox/billionaire-blast-off/</link>
  5506. <description>&lt;p&gt;We’re celebrating Firefox’s 21st anniversary this November, marking more than two decades of building a web that reflects creativity, independence and trust. While other major browsers are backed by billionaires, Firefox exists to ensure that the internet works for you — not for those cashing in on your data.&lt;/p&gt;
  5507.  
  5508.  
  5509.  
  5510. &lt;p&gt;That’s the idea behind &lt;a href=&quot;http://billionaireblastoff.firefox.com/?utm_medium=mozilla-websites&amp;amp;utm_source=blog.mozilla.org&amp;amp;utm_campaign=fx-owyw&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Billionaire Blast Off (BBO)&lt;/a&gt;, an interactive experience where you design a fictional, over-the-top billionaire and launch them on a one-way trip to space. It’s a playful way to flip Big Tech’s power dynamics and remind people that choice belongs in our hands.&lt;/p&gt;
  5511.  
  5512.  
  5513.  
  5514. &lt;p&gt;BBO lives online at &lt;a href=&quot;http://billionaireblastoff.firefox.com/?utm_medium=mozilla-websites&amp;amp;utm_source=blog.mozilla.org&amp;amp;utm_campaign=fx-owyw&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;billionaireblastoff.firefox.com&lt;/a&gt;, where you can build avatars, share memes and join in the joke. Offline, we’re bringing the fun to &lt;a href=&quot;https://blog.twitch.tv/en/2025/09/24/the-ultimate-guide-to-10-years-of-twitchcon/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;TwitchCon&lt;/a&gt;, with life-size games and our card game &lt;em&gt;Data War&lt;/em&gt;, where data is currency and space is the prize.&lt;/p&gt;
  5515.  
  5516.  
  5517.  
  5518. &lt;a class=&quot;ft-c-inline-cta&quot; href=&quot;http://billionaireblastoff.firefox.com/?utm_medium=mozilla-websites&amp;amp;utm_source=blog.mozilla.org&amp;amp;utm_campaign=fx-owyw&quot;&gt;
  5519.  &lt;div class=&quot;ft-c-inline-cta__media&quot;&gt;
  5520.  &lt;img alt=&quot;Cartoon man riding rocket through space holding Earth with colorful galaxy background.&quot; class=&quot;attachment-1x1 size-1x1&quot; height=&quot;800&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/09/Chaz-Cropped1-800x800.png&quot; width=&quot;800&quot; /&gt;  &lt;/div&gt;
  5521.  &lt;div class=&quot;ft-c-inline-cta__content&quot;&gt;
  5522.     &lt;h3&gt;Create your own billionaire avatar&lt;/h3&gt;      &lt;span&gt;Play Billionaire Blast Off&lt;/span&gt;   &lt;/div&gt;
  5523. &lt;/a&gt;
  5524.  
  5525.  
  5526.  
  5527. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;The billionaire playbook for your data, served with satire &lt;/strong&gt;&lt;/h3&gt;
  5528.  
  5529.  
  5530.  
  5531. &lt;p&gt;The goal of Billionaire Blast Off isn’t finger-wagging — it’s satire you can play. It makes the hidden business of your data tangible, and instead of just reading about the problem, you get to laugh at it, remix it and send it into space.&lt;/p&gt;
  5532.  
  5533.  
  5534.  
  5535. &lt;p&gt;The game is a safe, silly and shareable way to talk about something serious: who really holds the power over your data.&lt;/p&gt;
  5536.  
  5537.  
  5538.  
  5539. &lt;p&gt;Two ways to join the fun online:&lt;/p&gt;
  5540.  
  5541.  
  5542.  
  5543. &lt;ul&gt;
  5544. &lt;li&gt;&lt;strong&gt;Build a billionaire:&lt;/strong&gt; Create your own billionaire to send off-planet for good. Customize your avatar with an origin story, core drive and legacy plan.&lt;/li&gt;
  5545.  
  5546.  
  5547.  
  5548. &lt;li&gt;&lt;strong&gt;Blast off:&lt;/strong&gt; We’re not just making little billionaires. We’re launching them into space on a real rocket. Share your creation on social media for a chance to secure a seat for your avatar on the official launch.&lt;/li&gt;
  5549. &lt;/ul&gt;
  5550.  
  5551.  
  5552. &lt;div class=&quot;wp-block-image is-style-default&quot;&gt;
  5553. &lt;figure class=&quot;aligncenter size-large is-resized&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-81912&quot; height=&quot;522&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/09/Origin-Story-1024x522.png&quot; style=&quot;width: 675px;&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;&lt;em&gt; Customize your billionaire avatar at &lt;a href=&quot;http://billionaireblastoff.firefox.com/?utm_medium=mozilla-websites&amp;amp;utm_source=blog.mozilla.org&amp;amp;utm_campaign=fx-owyw&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;billionaireblastoff.firefox.com.&lt;/a&gt;&lt;/em&gt;&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;&lt;/div&gt;
  5554.  
  5555.  
  5556. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Next stop: TwitchCon&lt;/strong&gt;&lt;/h3&gt;
  5557.  
  5558.  
  5559.  
  5560. &lt;p&gt;At &lt;a href=&quot;https://billionaireblastoff.firefox.com/twitchcon&quot;&gt;TwitchCon&lt;/a&gt;, you’ll find us sending billionaires into space (for real), playing &lt;em&gt;Data War &lt;/em&gt;and putting the spotlight on the power of choice. &lt;/p&gt;
  5561.  
  5562.  
  5563.  
  5564. &lt;p&gt;Visit the Firefox booth #2805 (near Exhibit Hall F) to play &lt;em&gt;Data War&lt;/em&gt;, a fast-paced card game where players compete to send egomaniacal, tantrum-prone little billionaires on a one-way ticket to space. &lt;/p&gt;
  5565.  
  5566.  
  5567.  
  5568. &lt;p&gt;Step into an AR holobox to channel your billionaire villain era, create a life-size avatar and make it perform for your amusement in 3D.&lt;/p&gt;
  5569.  
  5570.  
  5571. &lt;div class=&quot;wp-block-image is-style-default&quot;&gt;
  5572. &lt;figure class=&quot;aligncenter size-large is-resized&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-81942&quot; height=&quot;576&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2025/09/Booth-16_9-1-1024x576.png&quot; style=&quot;width: 675px;&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;&lt;em&gt;Try out your billionaire in our AR holobox at TwitchCon booth #2805&lt;/em&gt;&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;&lt;/div&gt;
  5573.  
  5574.  
  5575. &lt;p&gt;On Saturday, Oct. 18, swing by the Firefox Lounge at the block party to snag some swag. Then stick around at 8:30 p.m. PT to cheer as we send billionaire avatars into space on a rocket built by &lt;a href=&quot;https://www.sentintospace.com/&quot;&gt;Sent Into Space&lt;/a&gt;. &lt;/p&gt;
  5576.  
  5577.  
  5578.  
  5579. &lt;p&gt;Online, the fun continues anytime at &lt;a href=&quot;http://billionaireblastoff.firefox.com&quot;&gt;billionaireblastoff.firefox.com&lt;/a&gt;. Because when the billionaires leave, the web opens up for you.&lt;/p&gt;
  5580. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/firefox/billionaire-blast-off/&quot;&gt;Blast off! Firefox turns data power plays into a game&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/en/&quot;&gt;The Mozilla Blog&lt;/a&gt;.&lt;/p&gt;</description>
  5581. <pubDate>Wed, 01 Oct 2025 15:40:59 +0000</pubDate>
  5582. <dc:creator>Jenifer Boscacci</dc:creator>
  5583. </item>
  5584. <item>
  5585. <title>This Week In Rust: This Week in Rust 619</title>
  5586. <guid isPermaLink="false">tag:this-week-in-rust.org,2025-10-01:/blog/2025/10/01/this-week-in-rust-619/</guid>
  5587. <link>https://this-week-in-rust.org/blog/2025/10/01/this-week-in-rust-619/</link>
  5588. <description>&lt;p&gt;Hello and welcome to another issue of &lt;em&gt;This Week in Rust&lt;/em&gt;!
  5589. &lt;a href=&quot;https://www.rust-lang.org/&quot;&gt;Rust&lt;/a&gt; is a programming language empowering everyone to build reliable and efficient software.
  5590. This is a weekly summary of its progress and community.
  5591. Want something mentioned? Tag us at
  5592. &lt;a href=&quot;https://bsky.app/profile/thisweekinrust.bsky.social&quot;&gt;@thisweekinrust.bsky.social&lt;/a&gt; on Bluesky or
  5593. &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;@ThisWeekinRust&lt;/a&gt; on mastodon.social, or
  5594. &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;send us a pull request&lt;/a&gt;.
  5595. Want to get involved? &lt;a href=&quot;https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md&quot;&gt;We love contributions&lt;/a&gt;.&lt;/p&gt;
  5596. &lt;p&gt;&lt;em&gt;This Week in Rust&lt;/em&gt; is openly developed &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;on GitHub&lt;/a&gt; and archives can be viewed at &lt;a href=&quot;https://this-week-in-rust.org/&quot;&gt;this-week-in-rust.org&lt;/a&gt;.
  5597. If you find any errors in this week's issue, &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust/pulls&quot;&gt;please submit a PR&lt;/a&gt;.&lt;/p&gt;
  5598. &lt;p&gt;Want TWIR in your inbox? &lt;a href=&quot;https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&amp;amp;id=0ed8b72485&quot;&gt;Subscribe here&lt;/a&gt;.&lt;/p&gt;
  5599. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#updates-from-rust-community&quot;&gt;Updates from Rust Community&lt;/a&gt;&lt;/h4&gt;
  5600.  
  5601.  
  5602. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#official&quot;&gt;Official&lt;/a&gt;&lt;/h5&gt;
  5603. &lt;ul&gt;
  5604. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/inside-rust/2025/09/30/all-hands-2026/&quot;&gt;The next Rust All Hands&lt;/a&gt;&lt;/li&gt;
  5605. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/inside-rust/2025/10/01/this-development-cycle-in-cargo-1.90/&quot;&gt;This Development-cycle in Cargo: 1.90&lt;/a&gt;&lt;/li&gt;
  5606. &lt;/ul&gt;
  5607. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#newsletters&quot;&gt;Newsletters&lt;/a&gt;&lt;/h5&gt;
  5608. &lt;ul&gt;
  5609. &lt;li&gt;&lt;a href=&quot;https://www.theembeddedrustacean.com/p/the-embedded-rustacean-issue-55&quot;&gt;The Embedded Rustacean Issue #55&lt;/a&gt;&lt;/li&gt;
  5610. &lt;/ul&gt;
  5611. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#projecttooling-updates&quot;&gt;Project/Tooling Updates&lt;/a&gt;&lt;/h5&gt;
  5612. &lt;ul&gt;
  5613. &lt;li&gt;&lt;a href=&quot;https://bevy.org/news/bevy-0-17/&quot;&gt;Bevy 0.17&lt;/a&gt;&lt;/li&gt;
  5614. &lt;li&gt;&lt;a href=&quot;https://lwn.net/SubscriberLink/1038750/6aa9769e0b875235/&quot;&gt;Linting Rust code in the kernel&lt;/a&gt;&lt;/li&gt;
  5615. &lt;li&gt;&lt;a href=&quot;https://max-inden.de/post/fast-udp-io-in-firefox/&quot;&gt;Fast UDP I/O for Firefox in Rust&lt;/a&gt;&lt;/li&gt;
  5616. &lt;li&gt;&lt;a href=&quot;https://github.com/feldroop/genedex&quot;&gt;genedex: A Small and Fast FM-Index for Rust&lt;/a&gt;&lt;/li&gt;
  5617. &lt;li&gt;&lt;a href=&quot;https://github.com/bahdotsh/blogr/releases/tag/v0.3.0&quot;&gt;blogr v0.3.0 - Fast, lightweight static site generator with built in newsletter manager&lt;/a&gt;&lt;/li&gt;
  5618. &lt;li&gt;&lt;a href=&quot;https://github.com/bahdotsh/feedr/releases/tag/v0.2.0&quot;&gt;Feedr v0.2.0 - A feature-rich terminal-based RSS feed reader with a clean and intuitive TUI&lt;/a&gt;&lt;/li&gt;
  5619. &lt;li&gt;&lt;a href=&quot;https://github.com/gluesql/glues/releases/tag/v0.8.1&quot;&gt;Glues v0.8.1 adds a browser TUI, proxy support, and redb storage&lt;/a&gt;&lt;/li&gt;
  5620. &lt;li&gt;&lt;a href=&quot;https://www.sea-ql.org/blog/2025-09-30-sea-orm-rbac/&quot;&gt;Role Based Access Control in SeaORM 2.0&lt;/a&gt;&lt;/li&gt;
  5621. &lt;/ul&gt;
  5622. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#observationsthoughts&quot;&gt;Observations/Thoughts&lt;/a&gt;&lt;/h5&gt;
  5623. &lt;ul&gt;
  5624. &lt;li&gt;&lt;a href=&quot;https://endler.dev/2025/choosing-rust/&quot;&gt;On Choosing Rust&lt;/a&gt;&lt;/li&gt;
  5625. &lt;li&gt;&lt;a href=&quot;https://purplesyringa.moe/blog/the-expression-problem-and-rust/&quot;&gt;The expression problem and Rust&lt;/a&gt;&lt;/li&gt;
  5626. &lt;li&gt;&lt;a href=&quot;https://kerkour.com/proton-apps-rust&quot;&gt;Case Study: How Proton uses Rust to build cross-platform applications for millions of people&lt;/a&gt;&lt;/li&gt;
  5627. &lt;li&gt;&lt;a href=&quot;https://blog.vermeilsoft.com/2025-09-rust-game-engine&quot;&gt;The Game Engine that would not have been made without Rust&lt;/a&gt;&lt;/li&gt;
  5628. &lt;li&gt;&lt;a href=&quot;https://filtra.io/rust/interviews/volvo-sep-25&quot;&gt;Introducing Rust To The Automotive Stack: A Conversation With Julius Gustavsson Of Volvo Cars&lt;/a&gt;&lt;/li&gt;
  5629. &lt;li&gt;&lt;a href=&quot;https://www.youtube.com/playlist?list=PLiOc9_WF8i8vVy5Qn6I9TxkBjsofzLcaH&quot;&gt;Rust in Paris 2025 – Full Talks Playlist&lt;/a&gt;&lt;/li&gt;
  5630. &lt;li&gt;[video] &lt;a href=&quot;https://www.youtube.com/watch?v=ec-ucXJ4x-0&quot;&gt;How to Optimize Rust for Slowness: Inspired by New Turing Machine Results&lt;/a&gt;&lt;/li&gt;
  5631. &lt;/ul&gt;
  5632. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-walkthroughs&quot;&gt;Rust Walkthroughs&lt;/a&gt;&lt;/h5&gt;
  5633. &lt;ul&gt;
  5634. &lt;li&gt;&lt;a href=&quot;https://marma.dev/articles/2025/under-the-hood-vec-t&quot;&gt;Under the hood: Vec\&amp;lt;T&amp;gt;&lt;/a&gt;&lt;/li&gt;
  5635. &lt;li&gt;&lt;a href=&quot;https://blog.0xshadow.dev/posts/backend-engineering-with-axum/axum-jwt-access-token/&quot;&gt;Axum Backend Series: Implement JWT Access Token&lt;/a&gt;&lt;/li&gt;
  5636. &lt;li&gt;&lt;a href=&quot;https://blog.cuongle.dev/p/level-up-your-rust-pattern-matching&quot;&gt;Level Up your Rust pattern matching&lt;/a&gt;&lt;/li&gt;
  5637. &lt;li&gt;[video] &lt;a href=&quot;https://www.youtube.com/watch?v=kESBAiTYMoQ&quot;&gt;Sguaba: Type-safe spatial math in Rust&lt;/a&gt;&lt;/li&gt;
  5638. &lt;/ul&gt;
  5639. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#miscellaneous&quot;&gt;Miscellaneous&lt;/a&gt;&lt;/h5&gt;
  5640. &lt;ul&gt;
  5641. &lt;li&gt;&lt;a href=&quot;https://blog.cloudflare.com/20-percent-internet-upgrade/&quot;&gt;Cloudflare just got faster and more secure, powered by Rust&lt;/a&gt;&lt;/li&gt;
  5642. &lt;li&gt;&lt;a href=&quot;https://ferrous-systems.com/blog/rust-who-what-why/&quot;&gt;Rust: Who, What and Why for ESA SW PA Workshop&lt;/a&gt;&lt;/li&gt;
  5643. &lt;/ul&gt;
  5644. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#crate-of-the-week&quot;&gt;Crate of the Week&lt;/a&gt;&lt;/h4&gt;
  5645. &lt;p&gt;This week's crate is &lt;a href=&quot;https://github.com/bahdotsh/blogr&quot;&gt;blogr&lt;/a&gt;, a fast, lightweight static site generator.&lt;/p&gt;
  5646. &lt;p&gt;Thanks to &lt;a href=&quot;https://users.rust-lang.org/t/crate-of-the-week/2704/1472&quot;&gt;Gokul&lt;/a&gt; for the self-suggestion!&lt;/p&gt;
  5647. &lt;p&gt;&lt;a href=&quot;https://users.rust-lang.org/t/crate-of-the-week/2704&quot;&gt;Please submit your suggestions and votes for next week&lt;/a&gt;!&lt;/p&gt;
  5648. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#calls-for-testing&quot;&gt;Calls for Testing&lt;/a&gt;&lt;/h4&gt;
  5649. &lt;p&gt;An important step for RFC implementation is for people to experiment with the
  5650. implementation and give feedback, especially before stabilization.&lt;/p&gt;
  5651. &lt;p&gt;If you are a feature implementer and would like your RFC to appear in this list, add a
  5652. &lt;code&gt;call-for-testing&lt;/code&gt; label to your RFC along with a comment providing testing instructions and/or
  5653. guidance on which aspect(s) of the feature need testing.&lt;/p&gt;
  5654. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/labels/call-for-testing&quot;&gt;Rust&lt;/a&gt;&lt;/p&gt;
  5655. &lt;ul&gt;
  5656. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/142859&quot;&gt;FR: Add a --fail-fast option to libtest&lt;/a&gt;&lt;/li&gt;
  5657. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/142859#issuecomment-3339090064&quot;&gt;Testing instructions&lt;/a&gt;&lt;/li&gt;
  5658. &lt;/ul&gt;
  5659. &lt;p&gt;&lt;em&gt;No calls for testing were issued this week by
  5660.  &lt;a href=&quot;https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing&quot;&gt;Rust language RFCs&lt;/a&gt;,
  5661.  &lt;a href=&quot;https://github.com/rust-lang/cargo/labels/call-for-testing&quot;&gt;Cargo&lt;/a&gt; or
  5662.  &lt;a href=&quot;https://github.com/rust-lang/rustup/labels/call-for-testing&quot;&gt;Rustup&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
  5663. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust/issues&quot;&gt;Let us know&lt;/a&gt; if you would like your feature to be tracked as a part of this list.&lt;/p&gt;
  5664. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers&quot;&gt;Call for Participation; projects and speakers&lt;/a&gt;&lt;/h4&gt;
  5665. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cfp-projects&quot;&gt;CFP - Projects&lt;/a&gt;&lt;/h5&gt;
  5666. &lt;p&gt;Always wanted to contribute to open-source projects but did not know where to start?
  5667. Every week we highlight some tasks from the Rust community for you to pick and get started!&lt;/p&gt;
  5668. &lt;p&gt;Some of these tasks may also have mentors available, visit the task page for more information.&lt;/p&gt;
  5669.  
  5670.  
  5671.  
  5672.  
  5673. &lt;ul&gt;
  5674. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/discussions/4786&quot;&gt;Diesel - Feedback on an All About Select guide&lt;/a&gt;&lt;/li&gt;
  5675. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/issues/4764&quot;&gt;Diesel - Incomplete explanation for PgConnection loading modes&lt;/a&gt;&lt;/li&gt;
  5676. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/issues/4787&quot;&gt;Diesel - FromSqlRow derive macro fails when in scope where Ok is not the one from the standard library&lt;/a&gt;&lt;/li&gt;
  5677. &lt;li&gt;&lt;a href=&quot;https://github.com/diesel-rs/diesel/issues/4780&quot;&gt;Diesel - fk_related_tables not working correctly with two foreign keys to same table&lt;/a&gt;&lt;/li&gt;
  5678. &lt;/ul&gt;
  5679. &lt;p&gt;If you are a Rust project owner and are looking for contributors, please submit tasks &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines&quot;&gt;here&lt;/a&gt; or through a &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;PR to TWiR&lt;/a&gt; or by reaching out on &lt;a href=&quot;https://x.com/ThisWeekInRust&quot;&gt;X (formerly Twitter)&lt;/a&gt; or &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;Mastodon&lt;/a&gt;!&lt;/p&gt;
  5680. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cfp-events&quot;&gt;CFP - Events&lt;/a&gt;&lt;/h5&gt;
  5681. &lt;p&gt;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.&lt;/p&gt;
  5682.  
  5683.  
  5684. &lt;ul&gt;
  5685. &lt;li&gt;&lt;a href=&quot;https://tokio.rs/blog/2025-09-26-announcing-tokio-conf-cfp&quot;&gt;&lt;strong&gt;TokioConf 2026&lt;/strong&gt;&lt;/a&gt;| 2025-12-08 | Portland, Oregon, USA | 2026-04-20&lt;/li&gt;
  5686. &lt;/ul&gt;
  5687. &lt;p&gt;If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a &lt;a href=&quot;https://github.com/rust-lang/this-week-in-rust&quot;&gt;PR to TWiR&lt;/a&gt; or by reaching out on &lt;a href=&quot;https://x.com/ThisWeekInRust&quot;&gt;X (formerly Twitter)&lt;/a&gt; or &lt;a href=&quot;https://mastodon.social/@thisweekinrust&quot;&gt;Mastodon&lt;/a&gt;!&lt;/p&gt;
  5688. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#updates-from-the-rust-project&quot;&gt;Updates from the Rust Project&lt;/a&gt;&lt;/h4&gt;
  5689. &lt;p&gt;473 pull requests were &lt;a href=&quot;https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2025-09-23..2025-09-30&quot;&gt;merged in the last week&lt;/a&gt;&lt;/p&gt;
  5690. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#compiler&quot;&gt;Compiler&lt;/a&gt;&lt;/h6&gt;
  5691. &lt;ul&gt;
  5692. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146667&quot;&gt;add an attribute to check the number of lanes in a SIMD vector after monomorphization&lt;/a&gt;&lt;/li&gt;
  5693. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146317&quot;&gt;add panic=immediate-abort&lt;/a&gt;&lt;/li&gt;
  5694. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147090&quot;&gt;skip stack overflow handler for panic=immediate-abort&lt;/a&gt;&lt;/li&gt;
  5695. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/141469&quot;&gt;allow &lt;code&gt;&amp;amp;raw [mut | const]&lt;/code&gt; for union field in safe code&lt;/a&gt;&lt;/li&gt;
  5696. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146376&quot;&gt;debuginfo: add an unstable flag to write split DWARF to an explicit directory&lt;/a&gt;&lt;/li&gt;
  5697. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/133477&quot;&gt;detect tuple structs that are unconstructable due to re-export&lt;/a&gt;&lt;/li&gt;
  5698. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147092&quot;&gt;do not compute optimized MIR if code does not type-check&lt;/a&gt;&lt;/li&gt;
  5699. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145277&quot;&gt;do not materialise X in &lt;code&gt;[X; 0]&lt;/code&gt; when X is unsizing a const&lt;/a&gt;&lt;/li&gt;
  5700. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146653&quot;&gt;improve diagnostics for empty attributes&lt;/a&gt;&lt;/li&gt;
  5701. &lt;/ul&gt;
  5702. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#library&quot;&gt;Library&lt;/a&gt;&lt;/h6&gt;
  5703. &lt;ul&gt;
  5704. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146859&quot;&gt;BTreeMap: don't leak allocators when initializing nodes&lt;/a&gt;&lt;/li&gt;
  5705. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146904&quot;&gt;constify {&lt;code&gt;Mutex&lt;/code&gt;, &lt;code&gt;RwLock&lt;/code&gt;, &lt;code&gt;ReentrantLock&lt;/code&gt;}&lt;code&gt;::data_ptr&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5706. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146979&quot;&gt;constify Default on Nanoseconds&lt;/a&gt;&lt;/li&gt;
  5707. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146818&quot;&gt;constify &lt;code&gt;{float}::total_cmp()&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5708. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146735&quot;&gt;unstably constify float &lt;code&gt;mul_add&lt;/code&gt; methods&lt;/a&gt;&lt;/li&gt;
  5709. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146293&quot;&gt;non-panicking &lt;code&gt;Vec::try_remove&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5710. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146958&quot;&gt;fix infinite recursion in &lt;code&gt;Path::eq&lt;/code&gt; with String&lt;/a&gt;&lt;/li&gt;
  5711. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146937&quot;&gt;implement &lt;code&gt;hostname&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5712. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147042&quot;&gt;remove most &lt;code&gt;#[track_caller]&lt;/code&gt; from allocating Vec methods&lt;/a&gt;&lt;/li&gt;
  5713. &lt;/ul&gt;
  5714. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#cargo&quot;&gt;Cargo&lt;/a&gt;&lt;/h6&gt;
  5715. &lt;ul&gt;
  5716. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16004&quot;&gt;config: combine key error context into one&lt;/a&gt;&lt;/li&gt;
  5717. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16019&quot;&gt;shell: Use a distinct style for transient status&lt;/a&gt;&lt;/li&gt;
  5718. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16016&quot;&gt;add retry for &lt;code&gt;git fetch&lt;/code&gt; failures in &lt;code&gt;CARGO_NET_GIT_FETCH_WITH_CLI&lt;/code&gt; path&lt;/a&gt;&lt;/li&gt;
  5719. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16021&quot;&gt;better error message for rust version incompatibility&lt;/a&gt;&lt;/li&gt;
  5720. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/15990&quot;&gt;sparse URLs in &lt;code&gt;TomlLockfileSourceId&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5721. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/cargo/pull/16003&quot;&gt;use &lt;code&gt;host-tuple&lt;/code&gt; for host target subsitution&lt;/a&gt;&lt;/li&gt;
  5722. &lt;/ul&gt;
  5723. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rustdoc&quot;&gt;Rustdoc&lt;/a&gt;&lt;/h6&gt;
  5724. &lt;ul&gt;
  5725. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/135771&quot;&gt;Add support for associated items in &quot;jump to def&quot; feature&lt;/a&gt;&lt;/li&gt;
  5726. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/138907&quot;&gt;add rustdoc &lt;code&gt;doc_cfg&lt;/code&gt; features&lt;/a&gt; (RFC &lt;a href=&quot;https://rust-lang.github.io/rfcs/3631-rustdoc-cfgs-handling.html&quot;&gt;#3631&lt;/a&gt;)&lt;/li&gt;
  5727. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147045&quot;&gt;search: use the same ID for entry and path to same item&lt;/a&gt;&lt;/li&gt;
  5728. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/116882&quot;&gt;hide &lt;code&gt;#[repr]&lt;/code&gt; if it isn't part of the public ABI&lt;/a&gt;&lt;/li&gt;
  5729. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/147047&quot;&gt;put the toolbar on the all item index&lt;/a&gt;&lt;/li&gt;
  5730. &lt;/ul&gt;
  5731. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#clippy&quot;&gt;Clippy&lt;/a&gt;&lt;/h6&gt;
  5732. &lt;ul&gt;
  5733. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15420&quot;&gt;&lt;code&gt;double_parens&lt;/code&gt;: add structured suggestions, fix bug&lt;/a&gt;&lt;/li&gt;
  5734. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15748&quot;&gt;&lt;code&gt;filter_next&lt;/code&gt;: check for &lt;code&gt;filter().next_back()&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5735. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15647&quot;&gt;&lt;code&gt;collapsible&lt;/code&gt;(&lt;code&gt;_else&lt;/code&gt;)&lt;code&gt;_if&lt;/code&gt;: respect &lt;code&gt;#[expect]&lt;/code&gt; on inner &lt;code&gt;if&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5736. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15788&quot;&gt;&lt;code&gt;let_unit_value&lt;/code&gt;: create the suggestion &quot;differentially&quot;&lt;/a&gt;&lt;/li&gt;
  5737. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15720&quot;&gt;&lt;code&gt;new_without_default&lt;/code&gt;: if &lt;code&gt;new&lt;/code&gt; has &lt;code&gt;#[cfg]&lt;/code&gt;, copy that onto &lt;code&gt;impl Default&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5738. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15756&quot;&gt;&lt;code&gt;or_fun_call&lt;/code&gt;: respect MSRV for &lt;code&gt;Result::unwrap_or_default&lt;/code&gt; suggestion&lt;/a&gt;&lt;/li&gt;
  5739. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15776&quot;&gt;&lt;code&gt;should_implement_trait&lt;/code&gt;: only suggest traits that are in the prelude&lt;/a&gt;&lt;/li&gt;
  5740. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15731&quot;&gt;&lt;code&gt;unnecessary_mut_passed&lt;/code&gt;: retain parens around the arguments&lt;/a&gt;&lt;/li&gt;
  5741. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15628&quot;&gt;check for proc macros from within &lt;code&gt;explicit_deref_methods&lt;/code&gt; and do not lint on proc macro expansions&lt;/a&gt;&lt;/li&gt;
  5742. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15782&quot;&gt;fix &lt;code&gt;new_without_default&lt;/code&gt; false positive on private type with trait impl&lt;/a&gt;&lt;/li&gt;
  5743. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15417&quot;&gt;overhaul &lt;code&gt;mut_mut&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5744. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/15469&quot;&gt;refactor &lt;code&gt;module_style&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5745. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-clippy/pull/13800&quot;&gt;rename &lt;code&gt;unchecked_duration_subtraction&lt;/code&gt; to &lt;code&gt;unchecked_time_subtraction&lt;/code&gt; and check for &lt;code&gt;Duration - Duration&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5746. &lt;/ul&gt;
  5747. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-analyzer&quot;&gt;Rust-Analyzer&lt;/a&gt;&lt;/h6&gt;
  5748. &lt;ul&gt;
  5749. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20760&quot;&gt;add &lt;code&gt;all&lt;/code&gt;, &lt;code&gt;any&lt;/code&gt; and &lt;code&gt;not&lt;/code&gt; completions in &lt;code&gt;#[cfg]&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5750. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20604&quot;&gt;add &lt;code&gt;cfg_attr&lt;/code&gt; predicate completion&lt;/a&gt;&lt;/li&gt;
  5751. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20599&quot;&gt;add applicable on bang &lt;code&gt;!&lt;/code&gt; for &lt;code&gt;apply_demorgan&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5752. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20729&quot;&gt;add const parameter keyword completion&lt;/a&gt;&lt;/li&gt;
  5753. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20598&quot;&gt;add let-chain support for &lt;code&gt;convert_to_guarded_return&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5754. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/19867&quot;&gt;allow &lt;code&gt;&amp;amp;raw&lt;/code&gt; {&lt;code&gt;mut&lt;/code&gt;, &lt;code&gt;const&lt;/code&gt;} for union field&lt;/a&gt;&lt;/li&gt;
  5755. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20543&quot;&gt;fix &quot;Replace match with if let&quot; not to trigger when invalid transformations occur&lt;/a&gt;&lt;/li&gt;
  5756. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20735&quot;&gt;fix SCIP panicking due to salsa not attaching&lt;/a&gt;&lt;/li&gt;
  5757. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20736&quot;&gt;fix applicable on if-let-chain for &lt;code&gt;invert_if&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5758. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20731&quot;&gt;fix expand rest pattern in tuple and slice pattern&lt;/a&gt;&lt;/li&gt;
  5759. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20611&quot;&gt;fix precedence parenthesis for &lt;code&gt;replace_arith_op&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5760. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20742&quot;&gt;don't turn unused variables into raw identifier&lt;/a&gt;&lt;/li&gt;
  5761. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20721&quot;&gt;implement fallback properly&lt;/a&gt;&lt;/li&gt;
  5762. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20745&quot;&gt;support negative integer literals in const generics in declarative macros&lt;/a&gt;&lt;/li&gt;
  5763. &lt;/ul&gt;
  5764. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage&quot;&gt;Rust Compiler Performance Triage&lt;/a&gt;&lt;/h5&gt;
  5765. &lt;p&gt;A relatively quiet week. Most of the improvements are to doc builds, driven by
  5766. continued packing of the search index in rustdoc-search: stringdex update with
  5767. more packing &lt;a href=&quot;https://github.com/rust-lang/rust/pull/147002&quot;&gt;#147002&lt;/a&gt; and
  5768. simplifications to doc(cfg) in Implement RFC 3631: add rustdoc doc_cfg features
  5769. &lt;a href=&quot;https://github.com/rust-lang/rust/pull/138907&quot;&gt;#138907&lt;/a&gt;.&lt;/p&gt;
  5770. &lt;p&gt;Triage done by &lt;strong&gt;@simulacrum&lt;/strong&gt;.
  5771. Revision range: &lt;a href=&quot;https://perf.rust-lang.org/?start=ce4beebecb77821734079cff47d8af08f9f27f11&amp;amp;end=8d72d3e1e96f58ca10059a6bb6e8aecba4a0e9cd&amp;amp;absolute=false&amp;amp;stat=instructions%3Au&quot;&gt;ce4beebe..8d72d3e1&lt;/a&gt;&lt;/p&gt;
  5772. &lt;p&gt;1 Regressions, 6 Improvements, 4 Mixed; 2 of them in rollups
  5773. 29 artifact comparisons made in total&lt;/p&gt;
  5774. &lt;p&gt;&lt;a href=&quot;https://github.com/rust-lang/rustc-perf/blob/master/triage/2025/2025-09-28.md&quot;&gt;Full report here&lt;/a&gt;&lt;/p&gt;
  5775. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#approved-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/commits/master&quot;&gt;Approved RFCs&lt;/a&gt;&lt;/h5&gt;
  5776. &lt;p&gt;Changes to Rust follow the Rust &lt;a href=&quot;https://github.com/rust-lang/rfcs#rust-rfcs&quot;&gt;RFC (request for comments) process&lt;/a&gt;. These
  5777. are the RFCs that were approved for implementation this week:&lt;/p&gt;
  5778. &lt;ul&gt;
  5779. &lt;li&gt;&lt;em&gt;No RFCs were approved this week.&lt;/em&gt;&lt;/li&gt;
  5780. &lt;/ul&gt;
  5781. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#final-comment-period&quot;&gt;Final Comment Period&lt;/a&gt;&lt;/h5&gt;
  5782. &lt;p&gt;Every week, &lt;a href=&quot;https://www.rust-lang.org/team.html&quot;&gt;the team&lt;/a&gt; announces the 'final comment period' for RFCs and key PRs
  5783. which are reaching a decision. Express your opinions now.&lt;/p&gt;
  5784. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#tracking-issues-prs&quot;&gt;Tracking Issues &amp;amp; PRs&lt;/a&gt;&lt;/h6&gt;
  5785. &lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#rust&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Rust&lt;/a&gt;
  5786. &lt;ul&gt;
  5787. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/143812&quot;&gt;Tracking Issue for &lt;code&gt;const_slice_rotate&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5788. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145722&quot;&gt;implement Extend&amp;lt;{Group, Literal, Punct, Ident}&amp;gt; for TokenStream&lt;/a&gt;&lt;/li&gt;
  5789. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145610&quot;&gt;Stabilize &lt;code&gt;char_max_len&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5790. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/146013&quot;&gt;Add &lt;code&gt;From&lt;/code&gt; impls for wrapper types&lt;/a&gt;&lt;/li&gt;
  5791. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/144064&quot;&gt;prefer alias candidates for sizedness + auto trait goals&lt;/a&gt;&lt;/li&gt;
  5792. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/132968&quot;&gt;Tracking Issue for &lt;code&gt;NonZero&amp;lt;u*&amp;gt;::div_ceil&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5793. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/issues/146660&quot;&gt;Tracking issue for release notes of #146410: Iterator repeat: no infinite loop for &lt;code&gt;last&lt;/code&gt; and &lt;code&gt;count&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5794. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/143191&quot;&gt;Stabilize &lt;code&gt;rwlock_downgrade&lt;/code&gt; library feature&lt;/a&gt;&lt;/li&gt;
  5795. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145608&quot;&gt;Prevent downstream &lt;code&gt;impl DerefMut for Pin&amp;lt;LocalType&amp;gt;&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  5796. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/136776&quot;&gt;Forbid freely casting lifetime bounds of dyn-types&lt;/a&gt;&lt;/li&gt;
  5797. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/140283&quot;&gt;Fix accidental type inference in array coercion&lt;/a&gt;&lt;/li&gt;
  5798. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/145617&quot;&gt;docs(style): Specify the frontmatter style&lt;/a&gt;&lt;/li&gt;
  5799. &lt;li&gt;&lt;a href=&quot;https://github.com/rust-lang/rust/pull/138799&quot;&gt;core: simplify &lt;code&gt;Extend&lt;/code&gt; for tuples&lt;/a&gt;&lt;/li&gt;
  5800. &lt;/ul&gt;
  5801. &lt;p&gt;&lt;em&gt;No Items entered Final Comment Period this week for
  5802.  &lt;a href=&quot;https://github.com/rust-lang/rfcs/labels/final-comment-period&quot;&gt;Rust RFCs&lt;/a&gt;,
  5803.  &lt;a href=&quot;https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Cargo&lt;/a&gt;,
  5804.  &lt;a href=&quot;https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+&quot;&gt;Language Team&lt;/a&gt;,
  5805.  &lt;a href=&quot;https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Language Reference&lt;/a&gt;,
  5806.  &lt;a href=&quot;https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period&quot;&gt;Leadership Council&lt;/a&gt; or
  5807.  &lt;a href=&quot;https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc&quot;&gt;Unsafe Code Guidelines&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
  5808. &lt;p&gt;Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.&lt;/p&gt;
  5809. &lt;h6&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#new-and-updated-rfcs&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://github.com/rust-lang/rfcs/pulls&quot;&gt;New and Updated RFCs&lt;/a&gt;&lt;/h6&gt;
  5810. &lt;ul&gt;
  5811. &lt;li&gt;&lt;em&gt;No New or Updated RFCs were created this week.&lt;/em&gt;&lt;/li&gt;
  5812. &lt;/ul&gt;
  5813. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#upcoming-events&quot;&gt;Upcoming Events&lt;/a&gt;&lt;/h4&gt;
  5814. &lt;p&gt;Rusty Events between 2025-10-01 - 2025-10-29 🦀&lt;/p&gt;
  5815. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#virtual&quot;&gt;Virtual&lt;/a&gt;&lt;/h5&gt;
  5816. &lt;ul&gt;
  5817. &lt;li&gt;2025-10-01 | Virtual (Indianapolis, IN, US) | &lt;a href=&quot;https://www.meetup.com/indyrs/events/&quot;&gt;Indy Rust&lt;/a&gt;&lt;ul&gt;
  5818. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/indyrs/events/wqzhftyhcnbcb&quot;&gt;&lt;strong&gt;Indy.rs - with Social Distancing&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5819. &lt;/ul&gt;
  5820. &lt;/li&gt;
  5821. &lt;li&gt;2025-10-02 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  5822. &lt;li&gt;&lt;a href=&quot;https://luma.com/ekgdex6j&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5823. &lt;/ul&gt;
  5824. &lt;/li&gt;
  5825. &lt;li&gt;2025-10-04 | Virtual (Kampala, UG) | &lt;a href=&quot;https://www.eventbrite.com/o/rust-circle-kampala-65249289033&quot;&gt;Rust Circle Meetup&lt;/a&gt;&lt;ul&gt;
  5826. &lt;li&gt;&lt;a href=&quot;https://www.eventbrite.com/e/rust-circle-meetup-tickets-628763858627&quot;&gt;&lt;strong&gt;Rust Circle Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5827. &lt;/ul&gt;
  5828. &lt;/li&gt;
  5829. &lt;li&gt;2025-10-05 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  5830. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311062530/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5831. &lt;/ul&gt;
  5832. &lt;/li&gt;
  5833. &lt;li&gt;2025-10-07 | Virtual (Beijing, CN) | &lt;a href=&quot;https://www.meetup.com/wasm-rust-meetup/events/&quot;&gt;WebAssembly and Rust Meetup (Wasm Empowering AI)&lt;/a&gt;&lt;ul&gt;
  5834. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/wasm-rust-meetup/events/310831771/&quot;&gt;&lt;strong&gt;Monthly WasmEdge Community Meeting, the runtime for LLM/AGI&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5835. &lt;/ul&gt;
  5836. &lt;/li&gt;
  5837. &lt;li&gt;2025-10-09 - 2025-10-10 | Hybrid (Paris, FR) | &lt;a href=&quot;https://eurorust.eu/&quot;&gt;EuroRust&lt;/a&gt;&lt;ul&gt;
  5838. &lt;li&gt;&lt;a href=&quot;https://eurorust.eu/schedule/&quot;&gt;&lt;strong&gt;EuroRust 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5839. &lt;/ul&gt;
  5840. &lt;/li&gt;
  5841. &lt;li&gt;2025-10-09 | Virtual (Berlin, DE) | &lt;a href=&quot;https://www.meetup.com/rust-berlin&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  5842. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/306046639/&quot;&gt;&lt;strong&gt;Rust Hack and Learn&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5843. &lt;/ul&gt;
  5844. &lt;/li&gt;
  5845. &lt;li&gt;2025-10-09 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  5846. &lt;li&gt;&lt;a href=&quot;https://luma.com/jotnli2g&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5847. &lt;/ul&gt;
  5848. &lt;/li&gt;
  5849. &lt;li&gt;2025-10-12 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  5850. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109160/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5851. &lt;/ul&gt;
  5852. &lt;/li&gt;
  5853. &lt;li&gt;2025-10-14 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  5854. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/305361534/&quot;&gt;&lt;strong&gt;Second Tuesday&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5855. &lt;/ul&gt;
  5856. &lt;/li&gt;
  5857. &lt;li&gt;2025-10-15 | Hybrid (Vancouver, BC, CA) | &lt;a href=&quot;https://www.meetup.com/vancouver-rust&quot;&gt;Vancouver Rust&lt;/a&gt;&lt;ul&gt;
  5858. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/vancouver-rust/events/307731034/&quot;&gt;&lt;strong&gt;Rust Study/Hack/Hang-out&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5859. &lt;/ul&gt;
  5860. &lt;/li&gt;
  5861. &lt;li&gt;2025-10-16 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  5862. &lt;li&gt;&lt;a href=&quot;https://luma.com/o8fh3fh7&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5863. &lt;/ul&gt;
  5864. &lt;/li&gt;
  5865. &lt;li&gt;2025-10-16 | Virtual (Nürnberg, DE) | &lt;a href=&quot;https://www.meetup.com/rust-noris&quot;&gt;Rust Nuremberg&lt;/a&gt;&lt;ul&gt;
  5866. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-noris/events/306046668/&quot;&gt;&lt;strong&gt;Rust Nürnberg online&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5867. &lt;/ul&gt;
  5868. &lt;/li&gt;
  5869. &lt;li&gt;2025-10-18 | Virtual (Gdansk, PL) | &lt;a href=&quot;https://www.meetup.com/stacja-it-trojmiasto/&quot;&gt;Stacja IT Trójmiasto&lt;/a&gt;&lt;ul&gt;
  5870. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/stacja-it-trojmiasto/events/310935164/&quot;&gt;&lt;strong&gt;[BEZPŁATNIE] Programowanie w języku Rust&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5871. &lt;/ul&gt;
  5872. &lt;/li&gt;
  5873. &lt;li&gt;2025-10-19 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  5874. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109167/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5875. &lt;/ul&gt;
  5876. &lt;/li&gt;
  5877. &lt;li&gt;2025-10-21 | Virtual (London, UK) | &lt;a href=&quot;https://www.meetup.com/women-in-rust&quot;&gt;Women in Rust&lt;/a&gt;&lt;ul&gt;
  5878. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/women-in-rust/events/311068625/&quot;&gt;&lt;strong&gt;👋 Community Catch Up&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5879. &lt;/ul&gt;
  5880. &lt;/li&gt;
  5881. &lt;li&gt;2025-10-21 | Virtual (Washington, DC, US) | &lt;a href=&quot;https://www.meetup.com/rustdc&quot;&gt;Rust DC&lt;/a&gt;&lt;ul&gt;
  5882. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rustdc/events/310002307/&quot;&gt;&lt;strong&gt;Mid-month Rustful&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5883. &lt;/ul&gt;
  5884. &lt;/li&gt;
  5885. &lt;li&gt;2025-10-23 | Virtual (Berlin, DE) | &lt;a href=&quot;https://www.meetup.com/rust-berlin&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  5886. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/306046641/&quot;&gt;&lt;strong&gt;Rust Hack and Learn&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5887. &lt;/ul&gt;
  5888. &lt;/li&gt;
  5889. &lt;li&gt;2025-10-23 | Virtual (Girona, ES) | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt; | &lt;a href=&quot;https://silicongirona.club&quot;&gt;Silicon Girona&lt;/a&gt;&lt;ul&gt;
  5890. &lt;li&gt;&lt;a href=&quot;https://luma.com/zyc3touy&quot;&gt;&lt;strong&gt;Sessió setmanal de codificació / Weekly coding session&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5891. &lt;/ul&gt;
  5892. &lt;/li&gt;
  5893. &lt;li&gt;2025-10-26 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  5894. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/311109171/&quot;&gt;&lt;strong&gt;Rust Readers Discord Discussion: Macros&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5895. &lt;/ul&gt;
  5896. &lt;/li&gt;
  5897. &lt;li&gt;2025-10-28 | Virtual (Dallas, TX, US) | &lt;a href=&quot;https://www.meetup.com/dallasrust&quot;&gt;Dallas Rust User Meetup&lt;/a&gt;&lt;ul&gt;
  5898. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/dallasrust/events/305361444/&quot;&gt;&lt;strong&gt;Fourth Tuesday&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5899. &lt;/ul&gt;
  5900. &lt;/li&gt;
  5901. &lt;/ul&gt;
  5902. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#asia&quot;&gt;Asia&lt;/a&gt;&lt;/h5&gt;
  5903. &lt;ul&gt;
  5904. &lt;li&gt;2025-10-02 | Seoul, KR | &lt;a href=&quot;https://www.meetup.com/rust-seoul-meetup&quot;&gt;Seoul Rust (Programming Language) Meetup&lt;/a&gt;&lt;ul&gt;
  5905. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-seoul-meetup/events/310824483/&quot;&gt;&lt;strong&gt;Seoul Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5906. &lt;/ul&gt;
  5907. &lt;/li&gt;
  5908. &lt;li&gt;2025-10-04 | Bangalore, IN | &lt;a href=&quot;https://hasgeek.com/rustbangalore&quot;&gt;Rust Bangalore&lt;/a&gt;&lt;ul&gt;
  5909. &lt;li&gt;&lt;a href=&quot;https://hasgeek.com/rustbangalore/october-2025-rustacean-meetup/&quot;&gt;&lt;strong&gt;October 2025 Rustacean meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5910. &lt;/ul&gt;
  5911. &lt;/li&gt;
  5912. &lt;li&gt;2025-10-08 | Kuala Lumpur, MY | &lt;a href=&quot;https://t.me/rustlangmalaysia&quot;&gt;Rust Malaysia&lt;/a&gt;&lt;ul&gt;
  5913. &lt;li&gt;&lt;a href=&quot;https://docs.google.com/forms/d/e/1FAIpQLScESY4eHc5lzZznAHZmFxI85CYaOKCYTQASRwXxC2y0KpI6zw/viewform&quot;&gt;&lt;strong&gt;Malaysia Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5914. &lt;/ul&gt;
  5915. &lt;/li&gt;
  5916. &lt;li&gt;2025-10-09 | Tokyo, JP | &lt;a href=&quot;https://www.meetup.com/tokyo-rust-meetup&quot;&gt;Tokyo Rust Meetup&lt;/a&gt;&lt;ul&gt;
  5917. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/tokyo-rust-meetup/events/310899137/&quot;&gt;&lt;strong&gt;Building Pocket-Sized Terminal UIs with Rust&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5918. &lt;/ul&gt;
  5919. &lt;/li&gt;
  5920. &lt;li&gt;2025-10-20 | Tel Aviv-Yafo, IL | &lt;a href=&quot;https://www.meetup.com/rust-tlv&quot;&gt;Rust 🦀 TLV&lt;/a&gt;&lt;ul&gt;
  5921. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-tlv/events/310628902/&quot;&gt;&lt;strong&gt;In person Rust October 2025 at AWS in Tel Aviv&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5922. &lt;/ul&gt;
  5923. &lt;/li&gt;
  5924. &lt;/ul&gt;
  5925. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#europe&quot;&gt;Europe&lt;/a&gt;&lt;/h5&gt;
  5926. &lt;ul&gt;
  5927. &lt;li&gt;2025-10-01 | Köln, DE | &lt;a href=&quot;https://www.meetup.com/rust-cologne-bonn&quot;&gt;Rust Cologne&lt;/a&gt;&lt;ul&gt;
  5928. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rustcologne/events/311209846/&quot;&gt;&lt;strong&gt;Rust in October: Undefined Rust&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5929. &lt;/ul&gt;
  5930. &lt;/li&gt;
  5931. &lt;li&gt;2025-10-01 | Olomouc, CZ | &lt;a href=&quot;https://www.meetup.com/rust-moravia&quot;&gt;Rust Moravia&lt;/a&gt;&lt;ul&gt;
  5932. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-moravia/events/310743282/&quot;&gt;&lt;strong&gt;4. Rust Moravia Meetup (In the capital!)&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5933. &lt;/ul&gt;
  5934. &lt;/li&gt;
  5935. &lt;li&gt;2025-10-01 | Oxford, UK | &lt;a href=&quot;https://www.meetup.com/oxford-rust-meetup-group&quot;&gt;Oxford ACCU/Rust Meetup.&lt;/a&gt;&lt;ul&gt;
  5936. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/oxford-rust-meetup-group/events/311170808/&quot;&gt;&lt;strong&gt;Building AI chatbots with Webassembly, Rust, and Leptos&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5937. &lt;/ul&gt;
  5938. &lt;/li&gt;
  5939. &lt;li&gt;2025-10-01 | Paris, FR | &lt;a href=&quot;https://www.eventbrite.fr/e/rust-meetup-in-paris-tickets-1686673127729&quot;&gt;Paris Rustaceans&lt;/a&gt;&lt;ul&gt;
  5940. &lt;li&gt;&lt;a href=&quot;https://www.eventbrite.fr/e/rust-meetup-in-paris-tickets-1686673127729&quot;&gt;&lt;strong&gt;Rust Meetup in Paris&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5941. &lt;/ul&gt;
  5942. &lt;/li&gt;
  5943. &lt;li&gt;2025-10-02 | Berlin, DE | &lt;a href=&quot;https://www.meetup.com/rust-berlin&quot;&gt;Rust Berlin&lt;/a&gt;&lt;ul&gt;
  5944. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-berlin/events/311202886/&quot;&gt;&lt;strong&gt;Rust Berlin on location 🏳️‍🌈 - Edition 007&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5945. &lt;/ul&gt;
  5946. &lt;/li&gt;
  5947. &lt;li&gt;2025-10-02 | Oslo, NO | &lt;a href=&quot;https://www.meetup.com/rust-oslo&quot;&gt;Rust Oslo&lt;/a&gt;&lt;ul&gt;
  5948. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-oslo/events/310062134/&quot;&gt;&lt;strong&gt;Rust Hack'n'Learn at Kampen Bistro&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5949. &lt;/ul&gt;
  5950. &lt;/li&gt;
  5951. &lt;li&gt;2025-10-08 | Girona, ES | &lt;a href=&quot;https://lu.ma/rust-girona&quot;&gt;Rust Girona&lt;/a&gt;&lt;ul&gt;
  5952. &lt;li&gt;&lt;a href=&quot;https://luma.com/8u55jo0h&quot;&gt;&lt;strong&gt;Rust Girona Hack &amp;amp; Learn 10 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5953. &lt;/ul&gt;
  5954. &lt;/li&gt;
  5955. &lt;li&gt;2025-10-08 | Paris, FR | &lt;a href=&quot;https://www.meetup.com/rust-paris&quot;&gt;Rust Paris&lt;/a&gt;&lt;ul&gt;
  5956. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-paris/events/310424476/&quot;&gt;&lt;strong&gt;Rust meetup #79&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5957. &lt;/ul&gt;
  5958. &lt;/li&gt;
  5959. &lt;li&gt;2025-10-08 | Reading, UK | &lt;a href=&quot;https://www.meetup.com/reading-rust-workshop&quot;&gt;Reading Rust Workshop&lt;/a&gt;&lt;ul&gt;
  5960. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/reading-rust-workshop/events/308944041/&quot;&gt;&lt;strong&gt;Reading Rust Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5961. &lt;/ul&gt;
  5962. &lt;/li&gt;
  5963. &lt;li&gt;2025-10-09 - 2025-10-10 | Hybrid (Paris, FR) | &lt;a href=&quot;https://eurorust.eu/&quot;&gt;EuroRust&lt;/a&gt;&lt;ul&gt;
  5964. &lt;li&gt;&lt;a href=&quot;https://eurorust.eu/schedule/&quot;&gt;&lt;strong&gt;EuroRust 2025&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5965. &lt;/ul&gt;
  5966. &lt;/li&gt;
  5967. &lt;li&gt;2025-10-14 | Basel, CH | &lt;a href=&quot;https://www.meetup.com/rust-basel&quot;&gt;Rust Basel&lt;/a&gt;&lt;ul&gt;
  5968. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-basel/events/310827834/&quot;&gt;&lt;strong&gt;Rust Meetup #13 @ letsboot&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5969. &lt;/ul&gt;
  5970. &lt;/li&gt;
  5971. &lt;li&gt;2025-10-21 | Aarhus, DK | &lt;a href=&quot;https://www.meetup.com/rust-aarhus&quot;&gt;Rust Aarhus&lt;/a&gt;&lt;ul&gt;
  5972. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-aarhus/events/311035141/&quot;&gt;&lt;strong&gt;Hack Night&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5973. &lt;/ul&gt;
  5974. &lt;/li&gt;
  5975. &lt;li&gt;2025-10-21 | Leipzig, DE | &lt;a href=&quot;https://www.meetup.com/rust-modern-systems-programming-in-leipzig&quot;&gt;Rust - Modern Systems Programming in Leipzig&lt;/a&gt;&lt;ul&gt;
  5976. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-modern-systems-programming-in-leipzig/events/308592252/&quot;&gt;&lt;strong&gt;Topic TBD&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5977. &lt;/ul&gt;
  5978. &lt;/li&gt;
  5979. &lt;li&gt;2025-10-21 | London, UK | &lt;a href=&quot;https://www.meetup.com/london-rust-project-group&quot;&gt;London Rust Project Group&lt;/a&gt;&lt;ul&gt;
  5980. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/london-rust-project-group/events/310813952/&quot;&gt;&lt;strong&gt;Rust in Surgery: Powering the Data Pipelines&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5981. &lt;/ul&gt;
  5982. &lt;/li&gt;
  5983. &lt;li&gt;2025-10-21 | Bergen, No | &lt;a href=&quot;https://www.meetup.com/bergen-rust-new-technology/events/&quot;&gt;Rust Bergen&lt;/a&gt;&lt;ul&gt;
  5984. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bergen-rust-new-technology/events/311153821/&quot;&gt;&lt;strong&gt;Rust Meetup #01 @ Zrch&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5985. &lt;/ul&gt;
  5986. &lt;/li&gt;
  5987. &lt;li&gt;2025-10-28 | Manchester, UK | &lt;a href=&quot;https://www.meetup.com/rust-manchester&quot;&gt;Rust Manchester&lt;/a&gt;&lt;ul&gt;
  5988. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-manchester/events/307919171/&quot;&gt;&lt;strong&gt;Rust Manchester October Code Night&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5989. &lt;/ul&gt;
  5990. &lt;/li&gt;
  5991. &lt;/ul&gt;
  5992. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#north-america&quot;&gt;North America&lt;/a&gt;&lt;/h5&gt;
  5993. &lt;ul&gt;
  5994. &lt;li&gt;2025-10-01 | Los Angeles, CA, US | &lt;a href=&quot;https://www.meetup.com/rust-los-angeles&quot;&gt;Rust Los Angeles&lt;/a&gt;&lt;ul&gt;
  5995. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-los-angeles/events/311243690/&quot;&gt;&lt;strong&gt;Web3 Developer Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  5996. &lt;/ul&gt;
  5997. &lt;/li&gt;
  5998. &lt;li&gt;2025-10-02 | Montréal, QC, CA | &lt;a href=&quot;https://www.meetup.com/rust-montreal&quot;&gt;Rust Montréal&lt;/a&gt;&lt;ul&gt;
  5999. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-montreal/events/311242811/&quot;&gt;&lt;strong&gt;October Monthly Social&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6000. &lt;/ul&gt;
  6001. &lt;/li&gt;
  6002. &lt;li&gt;2025-10-02 | Mountain View, CA, US | &lt;a href=&quot;https://www.meetup.com/hackerdojo/events/&quot;&gt;Hacker Dojo&lt;/a&gt;&lt;ul&gt;
  6003. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/hackerdojo/events/311004898&quot;&gt;&lt;strong&gt;RUST MEETUP at HACKER DOJO&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6004. &lt;/ul&gt;
  6005. &lt;/li&gt;
  6006. &lt;li&gt;2025-10-02 | Saint Louis, MO, US | &lt;a href=&quot;https://www.meetup.com/stl-rust&quot;&gt;STL Rust&lt;/a&gt;&lt;ul&gt;
  6007. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/stl-rust/events/310279407/&quot;&gt;&lt;strong&gt;🚁 Rust in Flight: Lessons from Designing a 3D‑Printed Quadcopter with Embedded&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6008. &lt;/ul&gt;
  6009. &lt;/li&gt;
  6010. &lt;li&gt;2025-10-04 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  6011. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/310983705/&quot;&gt;&lt;strong&gt;North End Rust Lunch, Oct 4&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6012. &lt;/ul&gt;
  6013. &lt;/li&gt;
  6014. &lt;li&gt;2025-10-09 | Lehi, UT, US | &lt;a href=&quot;https://www.meetup.com/utah-rust&quot;&gt;Utah Rust&lt;/a&gt;&lt;ul&gt;
  6015. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/utah-rust/events/311145663/&quot;&gt;&lt;strong&gt;Aya the Beholder: Writing an eBPF Firewall with the Aya Crate&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6016. &lt;/ul&gt;
  6017. &lt;/li&gt;
  6018. &lt;li&gt;2025-10-15 | Hybrid (Vancouver, BC, CA) | &lt;a href=&quot;https://www.meetup.com/vancouver-rust&quot;&gt;Vancouver Rust&lt;/a&gt;&lt;ul&gt;
  6019. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/vancouver-rust/events/307731034/&quot;&gt;&lt;strong&gt;Rust Study/Hack/Hang-out&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6020. &lt;/ul&gt;
  6021. &lt;/li&gt;
  6022. &lt;li&gt;2025-10-16 | Mountain View, CA, US | &lt;a href=&quot;https://www.meetup.com/hackerdojo/events/&quot;&gt;Hacker Dojo&lt;/a&gt;&lt;ul&gt;
  6023. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/hackerdojo/events/311012947/&quot;&gt;&lt;strong&gt;RUST MEETUP at HACKER DOJO&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6024. &lt;/ul&gt;
  6025. &lt;/li&gt;
  6026. &lt;li&gt;2025-10-21 | San Francisco, CA, US | &lt;a href=&quot;https://luma.com/events-by-vara-gear&quot;&gt;Vara &amp;amp; Gear&lt;/a&gt;&lt;ul&gt;
  6027. &lt;li&gt;&lt;a href=&quot;https://luma.com/kbs2os1c&quot;&gt;&lt;strong&gt;Rust Workshop by Vara Network&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6028. &lt;/ul&gt;
  6029. &lt;/li&gt;
  6030. &lt;li&gt;2025-10-21 | San Francisco, CA, US | &lt;a href=&quot;https://www.meetup.com/san-francisco-rust-study-group&quot;&gt;San Francisco Rust Study Group&lt;/a&gt;&lt;ul&gt;
  6031. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/san-francisco-rust-study-group/events/308284343/&quot;&gt;&lt;strong&gt;Rust Hacking in Person&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6032. &lt;/ul&gt;
  6033. &lt;/li&gt;
  6034. &lt;li&gt;2025-10-22 | Austin, TX, US | &lt;a href=&quot;https://www.meetup.com/rust-atx&quot;&gt;Rust ATX&lt;/a&gt;&lt;ul&gt;
  6035. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-atx/events/310457307/&quot;&gt;&lt;strong&gt;Rust Lunch - Fareground&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6036. &lt;/ul&gt;
  6037. &lt;/li&gt;
  6038. &lt;li&gt;2025-10-23 | Nashville, TN, US | &lt;a href=&quot;https://www.meetup.com/music-city-rust-developers&quot;&gt;Music City Rust Developers&lt;/a&gt;&lt;ul&gt;
  6039. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/music-city-rust-developers/events/304333267/&quot;&gt;&lt;strong&gt;Year In Review&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6040. &lt;/ul&gt;
  6041. &lt;/li&gt;
  6042. &lt;li&gt;2025-10-25 | Boston, MA, US | &lt;a href=&quot;https://www.meetup.com/bostonrust&quot;&gt;Boston Rust Meetup&lt;/a&gt;&lt;ul&gt;
  6043. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/bostonrust/events/310983712/&quot;&gt;&lt;strong&gt;Porter Square Rust Lunch, Oct 25&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6044. &lt;/ul&gt;
  6045. &lt;/li&gt;
  6046. &lt;/ul&gt;
  6047. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#oceania&quot;&gt;Oceania&lt;/a&gt;&lt;/h5&gt;
  6048. &lt;ul&gt;
  6049. &lt;li&gt;2025-10-22 | Perth, AU | &lt;a href=&quot;https://www.meetup.com/perth-rust-meetup-group&quot;&gt;Rust Perth Meetup Group&lt;/a&gt;&lt;ul&gt;
  6050. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/perth-rust-meetup-group/events/310847099/&quot;&gt;&lt;strong&gt;October Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6051. &lt;/ul&gt;
  6052. &lt;/li&gt;
  6053. &lt;li&gt;2025-10-28 | Barton, AU | &lt;a href=&quot;https://www.meetup.com/rust-canberra&quot;&gt;Canberra Rust User Group&lt;/a&gt;&lt;ul&gt;
  6054. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-canberra/events/311234237/&quot;&gt;&lt;strong&gt;October Meetup&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6055. &lt;/ul&gt;
  6056. &lt;/li&gt;
  6057. &lt;/ul&gt;
  6058. &lt;h5&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#south-america&quot;&gt;South America&lt;/a&gt;&lt;/h5&gt;
  6059. &lt;ul&gt;
  6060. &lt;li&gt;2025-10-08 | Buenos Aires, AR | &lt;a href=&quot;https://www.meetup.com/rust-argentina&quot;&gt;Rust en Español&lt;/a&gt;&lt;ul&gt;
  6061. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-argentina/events/311276950/&quot;&gt;&lt;strong&gt;Octubre Async - Escribimos un Runtime desde Cero!&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6062. &lt;/ul&gt;
  6063. &lt;/li&gt;
  6064. &lt;li&gt;2025-10-25 | São Paulo, BR | &lt;a href=&quot;https://www.meetup.com/rust-sao-paulo-meetup&quot;&gt;Rust São Paulo Meetup&lt;/a&gt;&lt;ul&gt;
  6065. &lt;li&gt;&lt;a href=&quot;https://www.meetup.com/rust-sao-paulo-meetup/events/311084440/&quot;&gt;&lt;strong&gt;Encontro do Rust-SP na Amazon Web Services&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
  6066. &lt;/ul&gt;
  6067. &lt;/li&gt;
  6068. &lt;/ul&gt;
  6069. &lt;p&gt;If you are running a Rust event please add it to the &lt;a href=&quot;https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com&quot;&gt;calendar&lt;/a&gt; to get
  6070. it mentioned here. Please remember to add a link to the event too.
  6071. Email the &lt;a href=&quot;mailto:community-team@rust-lang.org&quot;&gt;Rust Community Team&lt;/a&gt; for access.&lt;/p&gt;
  6072. &lt;h4&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#jobs&quot;&gt;Jobs&lt;/a&gt;&lt;/h4&gt;
  6073.  
  6074.  
  6075. &lt;p&gt;Please see the latest &lt;a href=&quot;https://www.reddit.com/r/rust/comments/1nknaii/official_rrust_whos_hiring_thread_for_jobseekers/&quot;&gt;Who's Hiring thread on r/rust&lt;/a&gt;&lt;/p&gt;
  6076. &lt;h3&gt;&lt;a class=&quot;toclink&quot; href=&quot;http://this-week-in-rust.org/atom.xml#quote-of-the-week&quot;&gt;Quote of the Week&lt;/a&gt;&lt;/h3&gt;
  6077. &lt;blockquote&gt;
  6078. &lt;p&gt;I must personally extend my condolences to those who forgot they chose in the past to annoy their future self.&lt;/p&gt;
  6079. &lt;/blockquote&gt;
  6080. &lt;p&gt;– &lt;a href=&quot;https://github.com/rust-lang/rust/issues/145936#issuecomment-3322104583&quot;&gt;@workingjubilee on github&lt;/a&gt;&lt;/p&gt;
  6081. &lt;p&gt;Thanks to &lt;a href=&quot;https://users.rust-lang.org/t/twir-quote-of-the-week/328/1719&quot;&gt;Riking&lt;/a&gt; for the suggestion!&lt;/p&gt;
  6082. &lt;p&gt;&lt;a href=&quot;https://users.rust-lang.org/t/twir-quote-of-the-week/328&quot;&gt;Please submit quotes and vote for next week!&lt;/a&gt;&lt;/p&gt;
  6083. &lt;p&gt;&lt;em&gt;This Week in Rust is edited by: &lt;a href=&quot;https://github.com/nellshamrell&quot;&gt;nellshamrell&lt;/a&gt;, &lt;a href=&quot;https://github.com/llogiq&quot;&gt;llogiq&lt;/a&gt;, &lt;a href=&quot;https://github.com/cdmistman&quot;&gt;cdmistman&lt;/a&gt;, &lt;a href=&quot;https://github.com/ericseppanen&quot;&gt;ericseppanen&lt;/a&gt;, &lt;a href=&quot;https://github.com/extrawurst&quot;&gt;extrawurst&lt;/a&gt;, &lt;a href=&quot;https://github.com/U007D&quot;&gt;U007D&lt;/a&gt;, &lt;a href=&quot;https://github.com/joelmarcey&quot;&gt;joelmarcey&lt;/a&gt;, &lt;a href=&quot;https://github.com/mariannegoldin&quot;&gt;mariannegoldin&lt;/a&gt;, &lt;a href=&quot;https://github.com/bennyvasquez&quot;&gt;bennyvasquez&lt;/a&gt;, &lt;a href=&quot;https://github.com/bdillo&quot;&gt;bdillo&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  6084. &lt;p&gt;&lt;em&gt;Email list hosting is sponsored by &lt;a href=&quot;https://foundation.rust-lang.org/&quot;&gt;The Rust Foundation&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
  6085. &lt;p&gt;&lt;small&gt;&lt;a href=&quot;https://www.reddit.com/r/rust/comments/1nvpd2x/this_week_in_rust_619/&quot;&gt;Discuss on r/rust&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;</description>
  6086. <pubDate>Wed, 01 Oct 2025 04:00:00 +0000</pubDate>
  6087. <dc:creator>TWiR Contributors</dc:creator>
  6088. </item>
  6089. <item>
  6090. <title>Mozilla Localization (L10N): Localizer Spotlight: Selim</title>
  6091. <guid isPermaLink="false">https://blog.mozilla.org/l10n/?p=1784</guid>
  6092. <link>https://blog.mozilla.org/l10n/2025/09/30/localizer-spotlight-selim/</link>
  6093. <description>&lt;p style=&quot;text-align: left;&quot;&gt;&lt;b&gt;About You&lt;/b&gt;&lt;/p&gt;
  6094. &lt;p&gt;My name is &lt;a href=&quot;https://pontoon.mozilla.org/contributors/Qkxrfae9uxCIC_PmnqAsJREVw8U/&quot;&gt;Selim&lt;/a&gt; and I’m the Turkish localization manager. I’m from İstanbul, Türkiye. I’ve been contributing to Mozilla since 2010.&lt;/p&gt;
  6095. &lt;p&gt;&lt;b&gt;Your Contributions&lt;/b&gt;&lt;/p&gt;
  6096. &lt;div class=&quot;wp-caption alignright&quot; id=&quot;attachment_1785&quot; style=&quot;width: 444px;&quot;&gt;&lt;a href=&quot;https://blog.mozilla.org/l10n/files/2025/09/selim-brussels.jpg&quot;&gt;&lt;img alt=&quot;Selim (first left) with fellow Turkish Mozillians Onur, Didem and Serkan (Mozilla Summit Brussels)&quot; class=&quot;wp-image-1785&quot; height=&quot;287&quot; src=&quot;https://blog.mozilla.org/l10n/files/2025/09/selim-brussels-e1759172589317-600x397.jpg&quot; width=&quot;434&quot; /&gt;&lt;/a&gt;&lt;p class=&quot;wp-caption-text&quot; id=&quot;caption-attachment-1785&quot;&gt;Selim (first left) with fellow Turkish Mozillians Onur, Didem and Serkan (Mozilla Summit Brussels)&lt;/p&gt;&lt;/div&gt;
  6097. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; Over the years, do you remember how many projects you’ve been involved in (including ones that may no longer exist)?&lt;/em&gt;&lt;/p&gt;
  6098. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; It’s been so many! I began with Firefox 15 years ago, but I think I’ve been involved in around 30 projects over the years. We currently have 23 projects active in Pontoon, and I’ve been involved in every single one of them to some degree.&lt;/p&gt;
  6099. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; Roughly how many Mozilla events have you joined — whether localization meetups, company-wide gatherings, MozFest, or others?&lt;/em&gt;&lt;/p&gt;
  6100. &lt;p&gt;&lt;strong&gt;A: &lt;/strong&gt;I’ve attended six of them. My first one was the Mozilla Balkans Meetup 2011 in Sofia. Then I had the chance to meet fellow Mozillians in Zagreb, Brussels, Berlin, Paris, and my hometown İstanbul. They were all great experiences, both enlightening and rewarding.&lt;/p&gt;
  6101. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; Looking back, are there any contributions or milestones you feel especially proud of?&lt;/em&gt;&lt;/p&gt;
  6102. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; When I first began contributing, my intention was to complete a few missing translations I had noticed in Firefox. However, I quickly realized that the project was huge and there was much more to it than met the eye. Its Turkish localization was around 85% complete at that time, but the community lacked the resources to push it forward. I took it as my duty to reach 100% first, and then spellcheck and fix all existing translations. It took me a few months to get there, but Firefox has clearly had the best Turkish localization among all browsers ever since.&lt;/p&gt;
  6103. &lt;p&gt;&lt;b&gt;Your Background&lt;/b&gt;&lt;/p&gt;
  6104. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; Does your professional background support or connect with your work in localization?&lt;/em&gt;&lt;/p&gt;
  6105. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; I currently work as a freelance editor and translator, translating and editing print magazines (mostly tech, popular science, and general knowledge titles), and localizing software and websites.&lt;/p&gt;
  6106. &lt;p&gt;And the event that kickstarted my career in publishing and professional translation was volunteering for localization. (No, not Firefox. It didn’t even exist yet!) Back in high school, I began localizing an open-source CMS called PHP-Nuke to be used on my school’s website. PHP-Nuke became very popular in a short amount of time, and a computer magazine editor approached me to build the magazine’s website using open-source tools, including PHP-Nuke. I’ve been an avid reader of those magazines since my childhood but never imagined that one day I’d be working for Türkiye’s best-selling computer magazine!&lt;/p&gt;
  6107. &lt;p&gt;In time, I began translating and writing articles for the magazine as a freelancer and joined the editorial staff after graduating from university.&lt;/p&gt;
  6108. &lt;p&gt;I’ve written hundreds of software and website reviews and kept noticing that some of them were high-quality products that needed better localization. Now, with a better understanding of how things work and with some technical background, I began contributing to more and more open-source projects in my free time, and Firefox was one of them.&lt;/p&gt;
  6109. &lt;p&gt;I was lucky that the previous Turkish contributors did a great job “localizing” Firefox, not just translating it. I learned a great deal from them, and it had a huge impact on my later professional work.&lt;/p&gt;
  6110. &lt;p&gt;I was also approached and/or approved by several clients who had seen my volunteer localization work.&lt;/p&gt;
  6111. &lt;p&gt;So, in a way, my professional background does support my work in localization — and vice versa.&lt;/p&gt;
  6112. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; In what ways has being part of Mozilla’s localization community influenced you — whether in problem-solving, leadership, or collaborating across cultures?&lt;/em&gt;&lt;/p&gt;
  6113. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; Once I started contributing, I quickly realized that Mozilla had something none of the other projects I had contributed to previously had: a community that I felt part of. These people &lt;i&gt;loved &lt;/i&gt;the internet, and they were having fun localizing stuff, just like me.&lt;/p&gt;
  6114. &lt;p&gt;The localization community helped me improve myself both professionally and personally in a lot of ways: I learned how to collaborate better with a team of volunteers from different backgrounds, how to use different translation tools, how to properly report bugs, how to deal with different time zones, and how to get out of my comfort zone and talk to people from abroad both in virtual and face-to-face events.&lt;/p&gt;
  6115. &lt;p&gt;&lt;b&gt;Your Community&lt;/b&gt;&lt;/p&gt;
  6116. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; As a long-time contributor, what motivates you to continue after all these years?&lt;/em&gt;&lt;/p&gt;
  6117. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; First and foremost, I believe in Mozilla’s mission wholeheartedly. But there’s a practical motivation too: Turkish is spoken by tens of millions of people, so the potential impact of localization is huge. Ensuring my fellow nationals have access to high-quality, localized open-source software is a driving force. And I’m still having fun doing it!&lt;/p&gt;
  6118. &lt;p&gt;&lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; Many communities struggle with onboarding or retaining contributors, especially after COVID limited in-person events. What are the challenges you face as a manager and how do you address them? And how do you engage with active contributors today? Do you have a process or approach for welcoming newcomers?&lt;/em&gt;&lt;/p&gt;
  6119. &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; The Turkish community had its fair share of struggles with onboarding and retaining contributors, but it never became a huge challenge because of an advantage we had: The first iteration of the community started very early. Firefox 1.0 was already available in Turkish, and they maintained a good localization percentage for most Mozilla products, even if not 100%. So when I joined, there were things to do but not a single project that needed to be started from scratch. They were maintainable by one or two enthusiastic localizers. And when I took on the manager role, I always tried to keep it that way. I did approve a number of new projects, but not before ensuring that we had the resources to always keep them at least 90% complete.&lt;/p&gt;
  6120. &lt;p&gt;But that creates a dilemma: New Turkish contributors usually face strings that are harder to grasp without context or are more difficult to translate, because the easier and more visible strings have already been translated. I guess that makes newcomers frustrated and they leave after translating a few strings. In fact, over the past 10 years, we’ve had only one contributor (&lt;a href=&quot;https://pontoon.mozilla.org/contributors/VB0eftwM_mnLHjP8UDNrurc_mzk/&quot;&gt;Grk&lt;/a&gt;) who has translated more than 10,000 strings (apart from myself), and two contributors (&lt;a href=&quot;https://pontoon.mozilla.org/contributors/tQetFmUNDeSWuQYsEjhTDVQdyNw/&quot;&gt;Ali&lt;/a&gt; and &lt;a href=&quot;https://pontoon.mozilla.org/contributors/rLfANGZKSoM1QVtAYg9lpSI6qro/&quot;&gt;Osman&lt;/a&gt;) with more than 1,000 strings. I’d like to thank them once again for their awesome contributions.&lt;/p&gt;
  6121. &lt;p&gt;The Turkish community has always been very small: just a few people contributing at a time, and that has worked for us. So I’m not anxiously trying to onboard or retain contributors, but if I see an enthusiastic newcomer, I try to guide them by commenting on their translations or sending a welcome email to let them know how things work.&lt;/p&gt;
  6122. &lt;p&gt;&lt;b&gt;Something Fun&lt;/b&gt;&lt;br /&gt;
  6123. &lt;em&gt;&lt;strong&gt;Q:&lt;/strong&gt; Could you share a few fun or unexpected facts about yourself that people might not know?&lt;/em&gt;&lt;/p&gt;
  6124. &lt;p&gt;&lt;strong&gt;A: &lt;/strong&gt;Certainly:&lt;/p&gt;
  6125. &lt;ul&gt;
  6126. &lt;li&gt;I’m a metalhead, and the first thing I ever translated as a hobby was the lyrics of a Sentenced song. I’ve been translating song lyrics ever since, and &lt;a href=&quot;https://www.sozbuyucusu.com/&quot;&gt;I have a blog&lt;/a&gt; where I publish them.&lt;/li&gt;
  6127. &lt;li&gt;My favorite documentary is &lt;a href=&quot;https://en.wikipedia.org/wiki/Helvetica_(film)&quot;&gt;&lt;i&gt;Helvetica&lt;/i&gt;&lt;/a&gt;.&lt;/li&gt;
  6128. &lt;li&gt;I built my first website when I was 13, by manually typing HTML in Windows Notepad. That’s when I discovered the internet’s endless possibilities and fell in love with it.&lt;/li&gt;
  6129. &lt;/ul&gt;</description>
  6130. <pubDate>Tue, 30 Sep 2025 00:03:10 +0000</pubDate>
  6131. <dc:creator>Peiying Mo</dc:creator>
  6132. </item>
  6133. <item>
  6134. <title>Matthew Gaudet: Summer of Sharpening</title>
  6135. <guid isPermaLink="false">52c2f0cde4b0537e2cba526e:57f70c5c440243051b0c3ce8:68dab97df724e53f95683011</guid>
  6136. <link>https://www.mgaudet.ca/technical/2025/9/29/summer-of-sharpening</link>
  6137. <description>&lt;p&gt;As we head into fall, I wanted to write up a bit of an experience report on a project I ran this summer with a few other people on the SpiderMonkey team. &lt;/p&gt;
  6138. &lt;p&gt;A few of us on the team chose to block off some time during the summer to do intentional professional development. Exploring topics that we hadn’t looked into, often due to a feeling of time starvation.&lt;/p&gt;
  6139. &lt;p&gt;Myself, I blocked off 2 hours every Friday through the summer. &lt;/p&gt;
  6140. &lt;p&gt;In order to turn this into a &lt;strong&gt;team&lt;/strong&gt; exercise, rather than just a personal development period, I create a shared document where I encouraged people to write up their experiments, so that we could read about their exploits. &lt;/p&gt;
  6141. &lt;h3&gt;How did it go?&lt;/h3&gt;
  6142. &lt;p&gt;Well, I don’t think -anyone- did 2 hours every week But I think most people did a little bit of exploration. &lt;/p&gt;
  6143. &lt;p&gt;I’ve blogged already a bit about some of the topics I worked on for sharpening time: &lt;a href=&quot;https://www.mgaudet.ca/technical/2025/5/28/exploring-a-language-runtime-with-bpftrace&quot;&gt;Both my&lt;/a&gt; blog posts &lt;a href=&quot;https://www.mgaudet.ca/technical/2025/5/28/finding-hot-allocation-sites-with-bpftrace&quot;&gt;about eBPF&lt;/a&gt; were a result of this practice. Other things I looked into that I didn’t get a chance to blog about include: &lt;/p&gt;
  6144. &lt;ul&gt;
  6145. &lt;li&gt;Learning about Instruments, and in particular Processor Trace (so painfully slow)&lt;/li&gt;
  6146. &lt;li&gt;Exploring &lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;Coz&lt;/a&gt;, the causal profiler  (really focused on multihreaded workloads in a way that didn’t produce value for me)&lt;/li&gt;
  6147. &lt;li&gt;Playing with Zed (clangd so slow for some reason)&lt;/li&gt;
  6148. &lt;li&gt;‘vibe coding’ (AI can do some things, but man, local minima are a pain).&lt;/li&gt;
  6149. &lt;li&gt;Exploring different options for Android emulation&lt;/li&gt;
  6150. &lt;li&gt;Watching WWDC videos on performance optimization (nice overview, mostly stuff I knew).&lt;/li&gt;
  6151. &lt;/ul&gt;
  6152. &lt;p&gt;I was very happy overall with the results, and have already created another document for next year to capture some ideas that we could look into next year. &lt;/p&gt;</description>
  6153. <pubDate>Mon, 29 Sep 2025 16:54:00 +0000</pubDate>
  6154. <dc:creator>Matthew Gaudet</dc:creator>
  6155. </item>
  6156. <item>
  6157. <title>The Servo Blog: This month in Servo: variable fonts, network tools, SVG, and more!</title>
  6158. <guid isPermaLink="true">https://servo.org/blog/2025/09/25/this-month-in-servo/</guid>
  6159. <link>https://servo.org/blog/2025/09/25/this-month-in-servo/</link>
  6160. <description>&lt;p&gt;Another month, another record number of pull requests merged!
  6161. August flew by, and with it came &lt;strong&gt;447 pull requests&lt;/strong&gt; from Servo contributors.
  6162. It was also the final month of our &lt;a href=&quot;https://www.outreachy.org/&quot;&gt;Outreachy&lt;/a&gt; cohort; you can read &lt;a href=&quot;https://www.jerensl.com/blog/en-final-project-progress-outreachy/&quot;&gt;Jerens’&lt;/a&gt; and &lt;a href=&quot;https://uthmaniv.github.io/&quot;&gt;Uthman’s&lt;/a&gt; blogs to learn about how it went!&lt;/p&gt;
  6163. &lt;h3&gt;Highlights &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/25/this-month-in-servo/#highlights&quot;&gt;
  6164.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  6165.      &lt;/a&gt;&lt;/h3&gt;
  6166. &lt;p&gt;Our big new feature this month is rendering &lt;strong&gt;inline SVG elements&lt;/strong&gt; (&lt;a href=&quot;https://github.com/mukilan&quot;&gt;@mukilan&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38188&quot;&gt;#38188&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38603&quot;&gt;#38603&lt;/a&gt;).
  6167. This improves the appearance of many popular websites.&lt;/p&gt;
  6168. &lt;figure&gt;
  6169.  &lt;a href=&quot;https://servo.org/img/blog/2025-09-svg.png&quot;&gt;&lt;img alt=&quot;Screenshot of servoshell with the Google homepage loaded&quot; src=&quot;https://servo.org/img/blog/2025-09-svg.png&quot; /&gt;&lt;/a&gt;
  6170.  &amp;lt;figcaption&amp;gt;Did you know that the Google logo is an SVG element?&amp;lt;/figcaption&amp;gt;
  6171. &lt;/figure&gt;
  6172. &lt;p&gt;We have implemented &lt;strong&gt;named grid line lines and areas&lt;/strong&gt; (&lt;a href=&quot;https://github.com/nicoburns&quot;&gt;@nicoburns&lt;/a&gt;, &lt;a href=&quot;https://github.com/loirooriol&quot;&gt;@loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38306&quot;&gt;#38306&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38574&quot;&gt;#38574&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38493&quot;&gt;#38493&lt;/a&gt;), still gated behind the &lt;code&gt;layout_grid_enabled&lt;/code&gt; preference (&lt;a href=&quot;https://github.com/servo/servo/pull/38306&quot;&gt;#38306&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38574&quot;&gt;#38574&lt;/a&gt;).&lt;/p&gt;
  6173. &lt;figure&gt;
  6174.  &lt;a href=&quot;https://servo.org/img/blog/2025-09-grid.jpg&quot;&gt;&lt;img alt=&quot;Screenshot of servoshell loading a page demoing a complex grid layout&quot; src=&quot;https://servo.org/img/blog/2025-09-grid.jpg&quot; /&gt;&lt;/a&gt;
  6175.  &amp;lt;figcaption&amp;gt;CSS grids are all around us.&amp;lt;/figcaption&amp;gt;
  6176. &lt;/figure&gt;
  6177. &lt;p&gt;Servo now supports CSS &lt;strong&gt;‘font-variation-settings’&lt;/strong&gt; on all main desktop platforms (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38642&quot;&gt;#38642&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38760&quot;&gt;#38760&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38831&quot;&gt;#38831&lt;/a&gt;).
  6178. This feature is currently gated behind the &lt;code&gt;layout_variable_fonts_enabled&lt;/code&gt; preference.
  6179. We also respect &lt;code&gt;format(*-variations)&lt;/code&gt; inside &lt;code&gt;@font-face&lt;/code&gt; rules (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38832&quot;&gt;#38832&lt;/a&gt;).
  6180. Additionally, Servo now reads data from &lt;strong&gt;OpenType Collection (.ttc)&lt;/strong&gt; system font files on macOS (&lt;a href=&quot;https://github.com/nicoburns&quot;&gt;@nicoburns&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38753&quot;&gt;#38753&lt;/a&gt;), and uses &lt;code&gt;Helvetica&lt;/code&gt; for the &lt;strong&gt;‘system-ui’&lt;/strong&gt; font (&lt;a href=&quot;https://github.com/dpogue&quot;&gt;@dpogue&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39001&quot;&gt;#39001&lt;/a&gt;).&lt;/p&gt;
  6181. &lt;figure&gt;
  6182.  &lt;details&gt;
  6183.    &lt;img alt=&quot;servoshell nightly showcasing variable fonts, with variable weight (`wght`) values smoothly increasing and decreasing (click to pause)&quot; src=&quot;https://servo.org/img/blog/2025-09-variations.webp&quot; style=&quot;margin: 0;&quot; /&gt;
  6184.    &lt;img src=&quot;https://servo.org/img/blog/2025-09-variations-preview.png&quot; style=&quot;margin: 0;&quot; /&gt;&lt;div alt=&quot;servoshell nightly showcasing variable fonts, with variable weight (`wght`) values smoothly increasing and decreasing (click to play)&quot;&gt;▶&lt;/div&gt;
  6185.  &lt;/details&gt;
  6186.  &amp;lt;figcaption&amp;gt;This font can be customized!&amp;lt;/figcaption&amp;gt;
  6187. &lt;/figure&gt;
  6188. &lt;p&gt;Our &lt;a href=&quot;https://book.servo.org/hacking/using-devtools.html&quot;&gt;developer tools&lt;/a&gt; continue to make progress!
  6189. We now have a functional &lt;strong&gt;network monitor&lt;/strong&gt; panel (&lt;a href=&quot;https://github.com/uthmaniv&quot;&gt;@uthmaniv&lt;/a&gt;, &lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38216&quot;&gt;#38216&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38601&quot;&gt;#38601&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38625&quot;&gt;#38625&lt;/a&gt;),
  6190. and our JS debugger can show potential breakpoints (&lt;a href=&quot;https://github.com/delan&quot;&gt;@delan&lt;/a&gt;, &lt;a href=&quot;https://github.com/atbrakhi&quot;&gt;@atbrakhi&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38331&quot;&gt;#38331&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38363&quot;&gt;#38363&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38333&quot;&gt;#38333&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38551&quot;&gt;#38551&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38550&quot;&gt;#38550&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38334&quot;&gt;#38334&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38624&quot;&gt;#38624&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38826&quot;&gt;#38826&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38797&quot;&gt;#38797&lt;/a&gt;).
  6191. Additionally, the layout inspector now &lt;strong&gt;dims nodes that are not displayed&lt;/strong&gt; (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38575&quot;&gt;#38575&lt;/a&gt;).&lt;/p&gt;
  6192. &lt;figure&gt;
  6193. &lt;a href=&quot;https://servo.org/img/blog/2025-09-mastodon.png&quot;&gt;&lt;img alt=&quot;servoshell showing the Servo Mastodon account homepage&quot; src=&quot;https://servo.org/img/blog/2025-09-mastodon.png&quot; /&gt;&lt;/a&gt;
  6194. &lt;a href=&quot;https://servo.org/img/blog/2025-09-netmonitor.png&quot;&gt;&lt;img alt=&quot;The Firefox network monitor, showing a list of network connections for the Servo Mastodon account homepage&quot; src=&quot;https://servo.org/img/blog/2025-09-netmonitor.png&quot; /&gt;&lt;/a&gt;
  6195.  &amp;lt;figcaption&amp;gt;That's a lot of network requests.&amp;lt;/figcaption&amp;gt;
  6196. &lt;/figure&gt;
  6197. &lt;p&gt;We’ve fixed a significant source of crashes in the engine: hit testing using outdated display lists (&lt;a href=&quot;https://github.com/servo/servo/issues/37932&quot;&gt;issue #37932&lt;/a&gt;).
  6198. &lt;strong&gt;Hit testing&lt;/strong&gt; in a web rendering engine is the process that determines which element(s) the user’s mouse is hovering over.&lt;/p&gt;
  6199. &lt;p&gt;Previously, this process ran inside of &lt;a href=&quot;https://github.com/servo/webrender&quot;&gt;WebRender&lt;/a&gt;, which receives a display list representing what should be rendered for a particular page.
  6200. WebRender runs on a separate thread or process from the actual page content, so display lists are updated asynchronously.
  6201. By the time we do a hit test, the elements reported may not exist anymore, so we could trigger crashes by (for example) moving the mouse quickly over parts of the page that were rapidly changing.&lt;/p&gt;
  6202. &lt;p&gt;This was fixed by making the hit test operation synchronous and moving it into the same thread as the actual content being tested against, eliminating the possibility of outdated results (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/kongbai1996&quot;&gt;@kongbai1996&lt;/a&gt;, &lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38480&quot;&gt;#38480,&lt;/a&gt; &lt;a href=&quot;https://github.com/servo/servo/pull/38464&quot;&gt;#38464,&lt;/a&gt; &lt;a href=&quot;https://github.com/servo/servo/pull/38463&quot;&gt;#38463,&lt;/a&gt; &lt;a href=&quot;https://github.com/servo/servo/pull/38884&quot;&gt;#38884,&lt;/a&gt; &lt;a href=&quot;https://github.com/servo/servo/pull/38518&quot;&gt;#38518)&lt;/a&gt;.&lt;/p&gt;
  6203. &lt;h3&gt;Web platform support &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/25/this-month-in-servo/#web-platform-support&quot;&gt;
  6204.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  6205.      &lt;/a&gt;&lt;/h3&gt;
  6206. &lt;h4&gt;DOM &amp;amp; JS &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/25/this-month-in-servo/#dom-%26-js&quot;&gt;
  6207.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  6208.      &lt;/a&gt;&lt;/h4&gt;
  6209. &lt;p&gt;We’ve upgraded to &lt;strong&gt;SpiderMonkey v140&lt;/strong&gt; (&lt;a href=&quot;https://gitlab.gnome.org/GNOME/gjs/-/blob/master/NEWS#L39-137&quot;&gt;changelog&lt;/a&gt;) (&lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37077&quot;&gt;#37077&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38563&quot;&gt;#38563&lt;/a&gt;).&lt;/p&gt;
  6210. &lt;p&gt;Numerous pieces of the &lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Web/API/Trusted_Types_API&quot;&gt;&lt;strong&gt;Trusted Types API&lt;/strong&gt;&lt;/a&gt; are now present in Servo
  6211. (&lt;a href=&quot;https://github.com/TimvdLippe&quot;&gt;@TimvdLippe&lt;/a&gt;, &lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38595&quot;&gt;#38595&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37834&quot;&gt;#37834&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38700&quot;&gt;#38700&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38736&quot;&gt;#38736&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38718&quot;&gt;#38718&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38784&quot;&gt;#38784&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38871&quot;&gt;#38871&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/8623&quot;&gt;#8623&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38874&quot;&gt;#38874&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38872&quot;&gt;#38872&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38886&quot;&gt;#38886&lt;/a&gt;), all gated behind the &lt;code&gt;dom_trusted_types_enabled&lt;/code&gt; preference.&lt;/p&gt;
  6212. &lt;p&gt;The &lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API&quot;&gt;&lt;strong&gt;IndexedDB&lt;/strong&gt;&lt;/a&gt; implementation (gated behind &lt;code&gt;dom_indexeddb_enabled&lt;/code&gt;) is progressing quickly (&lt;a href=&quot;https://github.com/arihant2math&quot;&gt;@arihant2math&lt;/a&gt;, &lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/rodion&quot;&gt;@rodion&lt;/a&gt;, &lt;a href=&quot;https://github.com/kkoyung&quot;&gt;@kkoyung&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/28744&quot;&gt;#28744&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38737&quot;&gt;#38737&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38836&quot;&gt;#38836&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38813&quot;&gt;#38813&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38819&quot;&gt;#38819&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38115&quot;&gt;#38115&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38944&quot;&gt;#38944&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38740&quot;&gt;#38740&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38891&quot;&gt;#38891&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38723&quot;&gt;#38723&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38850&quot;&gt;#38850&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38735&quot;&gt;#38735&lt;/a&gt;), now reporting errors via &lt;code&gt;IDBRequest&lt;/code&gt; interface and supporting autoincrement keys.&lt;/p&gt;
  6213. &lt;p&gt;A prototype implementation of the &lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Web/API/CookieStore&quot;&gt;&lt;strong&gt;CookieStore&lt;/strong&gt; API&lt;/a&gt; is now implemented and gated by the &lt;code&gt;dom_cookiestore_enabled&lt;/code&gt; preference (&lt;a href=&quot;https://github.com/sebsebmc&quot;&gt;@sebsebmc&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37968&quot;&gt;#37968&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38876&quot;&gt;#38876&lt;/a&gt;).&lt;/p&gt;
  6214. &lt;p&gt;Servo now passes over &lt;strong&gt;99.6% of the &lt;a href=&quot;https://drafts.fxtf.org/geometry/&quot;&gt;CSS geometry&lt;/a&gt; test suite&lt;/strong&gt;, thanks to an implementation of &lt;strong&gt;matrixTransform() on DOMPointReadOnly&lt;/strong&gt;, making all geometry interfaces serializable, and adding the &lt;strong&gt;SVGMatrix and SVGPoint aliases&lt;/strong&gt; (&lt;a href=&quot;https://github.com/lumiscosity&quot;&gt;@lumiscosity&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38801&quot;&gt;#38801&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38828&quot;&gt;#38828&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38810&quot;&gt;#38810&lt;/a&gt;).&lt;/p&gt;
  6215. &lt;p&gt;You can now use the &lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Web/API/TextEncoderStream&quot;&gt;&lt;strong&gt;TextEncoderStream&lt;/strong&gt; API&lt;/a&gt; (&lt;a href=&quot;https://github.com/minghuaw&quot;&gt;@minghuaw&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38466&quot;&gt;#38466&lt;/a&gt;).
  6216. Streams that are piped now correctly pass through &lt;code&gt;undefined&lt;/code&gt; values, too (&lt;a href=&quot;https://github.com/gterzian&quot;&gt;@gterzian&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38470&quot;&gt;#38470&lt;/a&gt;).
  6217. We also fixed a crash in the result of &lt;strong&gt;pipeTo() on ReadableStream&lt;/strong&gt; (&lt;a href=&quot;https://github.com/gterzian&quot;&gt;@gterzian&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38385&quot;&gt;#38385&lt;/a&gt;).&lt;/p&gt;
  6218. &lt;p&gt;We’ve implemented &lt;strong&gt;getModifierState() on MouseEvent&lt;/strong&gt; (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38535&quot;&gt;#38535&lt;/a&gt;), and made a number of changes involving DOM events: &lt;strong&gt;‘mouseleave’ events&lt;/strong&gt; are fired when the pointer leaves an &amp;lt;iframe&amp;gt; (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38539&quot;&gt;#38539&lt;/a&gt;), pasting from the clipboard into a text input triggers an &lt;strong&gt;‘input’ event&lt;/strong&gt; (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37100&quot;&gt;#37100&lt;/a&gt;), &lt;strong&gt;focus now occurs after ‘mousedown’&lt;/strong&gt; instead of ‘click’ (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38589&quot;&gt;#38589&lt;/a&gt;), we ignore ‘mousedown’ and ‘mouseup’ events for elements that are disabled (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38671&quot;&gt;#38671&lt;/a&gt;), and removing an event handler attribute like ‘onclick’ clears all relevant event listeners (&lt;a href=&quot;https://github.com/TimvdLippe&quot;&gt;@TimvdLippe&lt;/a&gt;, &lt;a href=&quot;https://github.com/kotx&quot;&gt;@kotx&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38734&quot;&gt;#38734&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39011&quot;&gt;#39011&lt;/a&gt;).&lt;/p&gt;
  6219. &lt;p&gt;Servo now supports &lt;strong&gt;scrollIntoView()&lt;/strong&gt; (&lt;a href=&quot;https://github.com/abdelrahman1234567&quot;&gt;@abdelrahman1234567&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38230&quot;&gt;#38230&lt;/a&gt;), and fires a &lt;strong&gt;‘scroll’ event&lt;/strong&gt; whenever a page is scrolled (&lt;a href=&quot;https://github.com/stevennovaryo&quot;&gt;@stevennovaryo&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38321&quot;&gt;#38321&lt;/a&gt;).
  6220. You can now focus an element without scrolling, by passing the &lt;code&gt;{preventScroll: true}&lt;/code&gt; option to focus() (&lt;a href=&quot;https://github.com/abdelrahman1234567&quot;&gt;@abdelrahman1234567&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38495&quot;&gt;#38495&lt;/a&gt;).&lt;/p&gt;
  6221. &lt;p&gt;&lt;strong&gt;navigator.sendBeacon()&lt;/strong&gt; is now implemented, gated behind the &lt;code&gt;dom_navigator_sendbeacon_enabled&lt;/code&gt; preference (&lt;a href=&quot;https://github.com/TimvdLippe&quot;&gt;@TimvdLippe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38301&quot;&gt;#38301&lt;/a&gt;).
  6222. Similarly, the &lt;strong&gt;AbortSignal.abort()&lt;/strong&gt; static method is hidden behind &lt;code&gt;dom_abort_controller_enabled&lt;/code&gt; (&lt;a href=&quot;https://github.com/Taym95&quot;&gt;@Taym95&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38746&quot;&gt;#38746&lt;/a&gt;).&lt;/p&gt;
  6223. &lt;p&gt;The &lt;strong&gt;HTMLDocument&lt;/strong&gt; interface now exists as a property on the &lt;code&gt;Window&lt;/code&gt; object (&lt;a href=&quot;https://github.com/leo030303&quot;&gt;@leo030303&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38433&quot;&gt;#38433&lt;/a&gt;).
  6224. Meanwhile, the &lt;strong&gt;CSS&lt;/strong&gt; window property is now a &lt;a href=&quot;https://webidl.spec.whatwg.org/#idl-namespaces&quot;&gt;WebIDL namespace&lt;/a&gt; (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38579&quot;&gt;#38579&lt;/a&gt;).
  6225. We also implemented the new &lt;strong&gt;QuotaExceededError&lt;/strong&gt; interface (&lt;a href=&quot;https://github.com/rmeno12&quot;&gt;@rmeno12&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38507&quot;&gt;#38507&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38720&quot;&gt;#38720&lt;/a&gt;), which replaces previous usages of DOMException with the &lt;code&gt;QUOTA_EXCEEDED_ERR&lt;/code&gt; name.&lt;/p&gt;
  6226. &lt;p&gt;Our 2D canvas implementation now supports &lt;strong&gt;addPath() on Path2D&lt;/strong&gt; (&lt;a href=&quot;https://github.com/arthmis&quot;&gt;@arthmis&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37838&quot;&gt;#37838&lt;/a&gt;) and the &lt;strong&gt;restore()&lt;/strong&gt; methods on &lt;strong&gt;CanvasRenderingContext2D&lt;/strong&gt; and &lt;strong&gt;OffscreenCanvas&lt;/strong&gt; now pop all applied clipping paths (&lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38496&quot;&gt;#38496&lt;/a&gt;).
  6227. Additionally, we now support &lt;strong&gt;using web fonts in the 2D canvas&lt;/strong&gt; (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38979&quot;&gt;#38979&lt;/a&gt;).
  6228. Meanwhile, the performance continues to improve in the new &lt;a href=&quot;https://github.com/linebender/vello?tab=readme-ov-file#vello&quot;&gt;Vello&lt;/a&gt;-based backends (&lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38406&quot;&gt;#38406&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38356&quot;&gt;#38356&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38440&quot;&gt;#38440&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38437&quot;&gt;#38437&lt;/a&gt;), with asynchronous uploading also showing improvements (&lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37776&quot;&gt;#37776&lt;/a&gt;).&lt;/p&gt;
  6229. &lt;p&gt;Muting media elements with the &lt;strong&gt;‘mute’&lt;/strong&gt; HTML attribute now works during the initial resource load (&lt;a href=&quot;https://github.com/rayguo17&quot;&gt;@rayguo17&lt;/a&gt;, &lt;a href=&quot;https://github.com/jschwe&quot;&gt;@jschwe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38462&quot;&gt;#38462&lt;/a&gt;).&lt;/p&gt;
  6230. &lt;p&gt;Modifying stylesheets now integrates better with incremental layout, in both light trees and shadow trees (&lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38530&quot;&gt;#38530&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38529&quot;&gt;#38529&lt;/a&gt;).
  6231. Note that calling setProperty() on a readonly CSSStyleDeclaration correctly throws an exception (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38677&quot;&gt;#38677&lt;/a&gt;).&lt;/p&gt;
  6232. &lt;h4&gt;CSS &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/25/this-month-in-servo/#css&quot;&gt;
  6233.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  6234.      &lt;/a&gt;&lt;/h4&gt;
  6235. &lt;p&gt;We’ve upgraded to the upstream &lt;strong&gt;Stylo&lt;/strong&gt; revision as of August 1, 2025.&lt;/p&gt;
  6236. &lt;p&gt;We now support custom CSS properties with the &lt;strong&gt;CSS.registerProperty()&lt;/strong&gt; method (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38682&quot;&gt;#38682&lt;/a&gt;), as well as custom element states with the &lt;strong&gt;‘states’ property on ElementInternals&lt;/strong&gt; (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38564&quot;&gt;#38564&lt;/a&gt;).&lt;/p&gt;
  6237. &lt;p&gt;Flexbox cross sizes can no longer end up negative through stretching (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38521&quot;&gt;#38521&lt;/a&gt;), while ‘stretch’ on flex items now stretches to the line if possible (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38526&quot;&gt;#38526&lt;/a&gt;).&lt;/p&gt;
  6238. &lt;p&gt;&lt;strong&gt;Overflow calculations are more accurate&lt;/strong&gt;, now that we ignore ‘position: fixed’ children of the root element (&lt;a href=&quot;https://github.com/stevennovaryo&quot;&gt;@stevennovaryo&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38618&quot;&gt;#38618&lt;/a&gt;), compute overflow for &amp;lt;body&amp;gt; separate from the viewport (&lt;a href=&quot;https://github.com/shubhamg13&quot;&gt;@shubhamg13&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38825&quot;&gt;#38825&lt;/a&gt;), check for ‘overflow: visible’ in parents and children (&lt;a href=&quot;https://github.com/shubhamg13&quot;&gt;@shubhamg13&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38443&quot;&gt;#38443&lt;/a&gt;), and propagate ‘overflow’ to the viewport correctly (&lt;a href=&quot;https://github.com/shubhamg13&quot;&gt;@shubhamg13&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38598&quot;&gt;#38598&lt;/a&gt;).&lt;/p&gt;
  6239. &lt;p&gt;‘color’ and ‘text-decoration’ properties no longer inherit into the contents of &amp;lt;select&amp;gt; elements (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38570&quot;&gt;#38570&lt;/a&gt;).&lt;/p&gt;
  6240. &lt;p&gt;Negative outline offsets work correctly (&lt;a href=&quot;https://github.com/lumiscosity&quot;&gt;@lumiscosity&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38418&quot;&gt;#38418&lt;/a&gt;).&lt;/p&gt;
  6241. &lt;p&gt;Video elements no longer fall back to a preferred aspect ratio of 2 (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38705&quot;&gt;#38705&lt;/a&gt;).&lt;/p&gt;
  6242. &lt;p&gt;‘position: sticky’ elements are handled correctly inside CSS transforms (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38391&quot;&gt;#38391&lt;/a&gt;).&lt;/p&gt;
  6243. &lt;h3&gt;Performance &amp;amp; Stability &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/25/this-month-in-servo/#performance-%26-stability&quot;&gt;
  6244.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  6245.      &lt;/a&gt;&lt;/h3&gt;
  6246. &lt;p&gt;We fixed several panics this month, involving IntersectionObserver and missing stacking contexts (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38473&quot;&gt;#38473&lt;/a&gt;), unpaintable canvases and text (&lt;a href=&quot;https://github.com/gterzian&quot;&gt;@gterzian&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38664&quot;&gt;#38664&lt;/a&gt;), serializing ‘location’ properties on Window objects (&lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38709&quot;&gt;#38709&lt;/a&gt;), and navigations canceled before HTTP headers are received (&lt;a href=&quot;https://github.com/gterzian&quot;&gt;@gterzian&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38739&quot;&gt;#38739&lt;/a&gt;).&lt;/p&gt;
  6247. &lt;p&gt;We also fixed a number of performance pitfalls.
  6248. The document rendering loop is now &lt;strong&gt;throttled to 60 FPS&lt;/strong&gt; (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38431&quot;&gt;#38431&lt;/a&gt;), while &lt;strong&gt;animated images do less work&lt;/strong&gt; when advancing the current frame (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38857&quot;&gt;#38857&lt;/a&gt;).
  6249. In addition, elements with &lt;strong&gt;CSS images will not trigger page reflow&lt;/strong&gt; until their image data is fully available (&lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38916&quot;&gt;#38916&lt;/a&gt;).&lt;/p&gt;
  6250. &lt;p&gt;Finally, we made improvements to memory usage and binary size.
  6251. Inline stylesheets are now deduplicated, which can have a significant impact on pages with &lt;strong&gt;lots of form inputs&lt;/strong&gt; or &lt;strong&gt;custom elements&lt;/strong&gt; with common styles (&lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38540&quot;&gt;#38540&lt;/a&gt;).
  6252. We also removed many unused pieces of the ICU library, &lt;strong&gt;saving 16MB&lt;/strong&gt; from the final binary.&lt;/p&gt;
  6253. &lt;h3&gt;Embedding &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/25/this-month-in-servo/#embedding&quot;&gt;
  6254.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  6255.      &lt;/a&gt;&lt;/h3&gt;
  6256. &lt;p&gt;Servo has declared a &lt;strong&gt;Minimum Supported Rust Version&lt;/strong&gt; (1.85.0), and this is verified with every new pull request (&lt;a href=&quot;https://github.com/jschwe&quot;&gt;@jschwe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37152&quot;&gt;#37152&lt;/a&gt;).&lt;/p&gt;
  6257. &lt;p&gt;Evaluating JS from the embedding layer now &lt;strong&gt;reports an error&lt;/strong&gt; if the evaluation failed for any reason (&lt;a href=&quot;https://github.com/rodio&quot;&gt;@rodio&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38602&quot;&gt;#38602&lt;/a&gt;).&lt;/p&gt;
  6258. &lt;p&gt;Our &lt;strong&gt;WebDriver&lt;/strong&gt; implementation now passes 80% of the implementation conformance tests.
  6259. This is the result of lots of work on handling user prompts (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38591&quot;&gt;#38591&lt;/a&gt;), computing obscured/disabled elements while clicking (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38497&quot;&gt;#38497&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38841&quot;&gt;#38841&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38436&quot;&gt;#38436&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38490&quot;&gt;#38490&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38383&quot;&gt;#38383&lt;/a&gt;), and improving window focus behaviours (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38889&quot;&gt;#38889&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38909&quot;&gt;#38909&lt;/a&gt;).
  6260. We also implemented the &lt;strong&gt;Get Window Handles&lt;/strong&gt; command (&lt;a href=&quot;https://github.com/longvatrong111&quot;&gt;@longvatrong111&lt;/a&gt;, &lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38622&quot;&gt;#38622&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38745&quot;&gt;#38745&lt;/a&gt;), added support for getting element boolean attributes (&lt;a href=&quot;https://github.com/kkoyung&quot;&gt;@kkoyung&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38401&quot;&gt;#38401&lt;/a&gt;), and added more accurate errors for a number of commands (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/longvatrong111&quot;&gt;@longvatrong111&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38620&quot;&gt;#38620&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38357&quot;&gt;#38357&lt;/a&gt;).
  6261. The &lt;strong&gt;Element Clear&lt;/strong&gt; command now clears &lt;code&gt;&amp;lt;input type=&quot;file&quot;&amp;gt;&lt;/code&gt; elements correctly (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38536&quot;&gt;#38536&lt;/a&gt;), and &lt;strong&gt;Element Send Keys&lt;/strong&gt; now appends to file inputs with the ‘multiple’ attribute.&lt;/p&gt;
  6262. &lt;h3&gt;servoshell &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/25/this-month-in-servo/#servoshell&quot;&gt;
  6263.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  6264.      &lt;/a&gt;&lt;/h3&gt;
  6265. &lt;p&gt;We now &lt;strong&gt;display favicons&lt;/strong&gt; of each top-level page in the tab bar (&lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/36680&quot;&gt;#36680&lt;/a&gt;).&lt;/p&gt;
  6266. &lt;figure&gt;
  6267. &lt;a href=&quot;https://servo.org/img/blog/2025-09-favicon.png&quot;&gt;&lt;img alt=&quot;servoshell showing a diffie favicon in the tab bar&quot; src=&quot;https://servo.org/img/blog/2025-09-favicon.png&quot; /&gt;&lt;/a&gt;
  6268. &lt;/figure&gt;
  6269. &lt;p&gt;Resizing the browser window to a very small dimension no longer crashes the browser (&lt;a href=&quot;https://github.com/leo030303&quot;&gt;@leo030303&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38461&quot;&gt;#38461&lt;/a&gt;).
  6270. Element hit testing in full screen mode now works as expected (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38328&quot;&gt;#38328&lt;/a&gt;).&lt;/p&gt;
  6271. &lt;p&gt;Various popup dialogs, such as the &amp;lt;select&amp;gt; option chooser dialog, can now be closed without choosing a value (&lt;a href=&quot;https://github.com/TimvdLippe&quot;&gt;@TimvdLippe&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38373&quot;&gt;#38373&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38949&quot;&gt;#38949&lt;/a&gt;).
  6272. Additionally, the browser now responds to a popup closing without any other inputs (&lt;a href=&quot;https://github.com/lumiscosity&quot;&gt;@lumiscosity&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/39038&quot;&gt;#39038&lt;/a&gt;).&lt;/p&gt;
  6273. &lt;h3&gt;Donations &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/25/this-month-in-servo/#donations&quot;&gt;
  6274.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  6275.      &lt;/a&gt;&lt;/h3&gt;
  6276. &lt;p&gt;Thanks again for your generous support!
  6277. We are now receiving &lt;strong&gt;5552 USD/month&lt;/strong&gt; (+18.3% over July) in recurring donations.&lt;/p&gt;
  6278. &lt;p&gt;Historically this has helped cover the cost of our &lt;a href=&quot;https://ci0.servo.org/&quot;&gt;speedy&lt;/a&gt; &lt;a href=&quot;https://ci1.servo.org/&quot;&gt;CI&lt;/a&gt; &lt;a href=&quot;https://ci2.servo.org/&quot;&gt;servers&lt;/a&gt; and &lt;a href=&quot;https://www.outreachy.org/alums/2025-06/#:~:text=Servo&quot;&gt;Outreachy interns&lt;/a&gt;.
  6279. Thanks to your support, we’re now setting up &lt;strong&gt;&lt;a href=&quot;https://ci3.servo.org/&quot;&gt;two&lt;/a&gt; &lt;a href=&quot;https://ci4.servo.org/&quot;&gt;new&lt;/a&gt; CI servers for benchmarking&lt;/strong&gt;, and &lt;strong&gt;&lt;a href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/&quot;&gt;funding the work of our long-time maintainer&lt;/a&gt; Josh Matthews&lt;/strong&gt; (@jdm), with a particular focus on helping more people contribute to Servo.&lt;/p&gt;
  6280. &lt;p&gt;Keep an eye out for &lt;a href=&quot;https://github.com/servo/servo/issues/38141&quot;&gt;further CI improvements&lt;/a&gt; in the coming months, including &lt;a href=&quot;https://github.com/servo/ci-runners/issues/21&quot;&gt;&lt;strong&gt;ten-minute WPT builds&lt;/strong&gt;&lt;/a&gt;, &lt;strong&gt;macOS arm64 builds&lt;/strong&gt;, and &lt;strong&gt;faster pull request checks&lt;/strong&gt;.&lt;/p&gt;
  6281. &lt;p&gt;Servo is also on &lt;a href=&quot;https://thanks.dev/&quot;&gt;thanks.dev&lt;/a&gt;, and already &lt;strong&gt;15 GitHub users&lt;/strong&gt; (−7 from July) that depend on Servo are sponsoring us there.
  6282. If you use Servo libraries like &lt;a href=&quot;https://crates.io/crates/url/reverse_dependencies&quot;&gt;url&lt;/a&gt;, &lt;a href=&quot;https://crates.io/crates/html5ever/reverse_dependencies&quot;&gt;html5ever&lt;/a&gt;, &lt;a href=&quot;https://crates.io/crates/selectors/reverse_dependencies&quot;&gt;selectors&lt;/a&gt;, or &lt;a href=&quot;https://crates.io/crates/cssparser/reverse_dependencies&quot;&gt;cssparser&lt;/a&gt;, signing up for &lt;a href=&quot;https://thanks.dev/&quot;&gt;thanks.dev&lt;/a&gt; could be a good way for you (or your employer) to give back to the community.&lt;/p&gt;
  6283. &lt;figure class=&quot;_fig&quot; style=&quot;width: 100%; margin: 1em 0;&quot;&gt;&lt;div class=&quot;_flex&quot;&gt;
  6284.    &lt;div style=&quot;text-align: right;&quot;&gt;
  6285.        &lt;div&gt;&lt;strong&gt;5552&lt;/strong&gt; USD/month&lt;/div&gt;
  6286.        &lt;div&gt;&lt;/div&gt;
  6287.        &lt;div&gt;&lt;/div&gt;
  6288.        &lt;div style=&quot;padding-right: 1em;&quot;&gt;&lt;strong&gt;10000&lt;/strong&gt;&lt;/div&gt;
  6289.    &lt;/div&gt;
  6290.    &lt;progress max=&quot;10000&quot; value=&quot;5552&quot;&gt;&lt;/progress&gt;
  6291. &lt;/div&gt;&lt;/figure&gt;
  6292. &lt;p&gt;As always, use of these funds will be decided transparently in the Technical Steering Committee.
  6293. For more details, head to our &lt;a href=&quot;https://servo.org/sponsorship/&quot;&gt;Sponsorship page&lt;/a&gt;.&lt;/p&gt;</description>
  6294. <pubDate>Thu, 25 Sep 2025 00:00:00 +0000</pubDate>
  6295. </item>
  6296. <item>
  6297. <title>Niko Matsakis: Symposium: exploring new AI workflows</title>
  6298. <guid isPermaLink="false">https://smallcultfollowing.com/babysteps/blog/2025/09/24/symposium/</guid>
  6299. <link>https://smallcultfollowing.com/babysteps/blog/2025/09/24/symposium/?utm_source=atom_feed</link>
  6300. <description>&lt;div style=&quot;overflow: auto;&quot;&gt;
  6301. &lt;img alt=&quot;Screenshot of the Symposium app&quot; src=&quot;https://smallcultfollowing.com/babysteps/ /assets/2025-09-24-symposium/logo-alcove.png&quot; style=&quot;float: left; margin-right: 15px; margin-bottom: 10px;&quot; width=&quot;25%&quot; /&gt;
  6302. &lt;p&gt;This blog post gives you a tour of &lt;a href=&quot;https://github.com/symposium-dev/symposium&quot;&gt;Symposium&lt;/a&gt;, a wild-and-crazy project that I’ve been obsessed with over the last month or so. Symposium combines an MCP server, a VSCode extension, an OS X Desktop App, and some &lt;a href=&quot;https://github.com/symposium-dev/symposium/blob/main/symposium/mcp-server/src/guidance/main.md&quot;&gt;mindful prompts&lt;/a&gt; to forge new ways of working with agentic CLI tools.&lt;/p&gt;
  6303. &lt;/div&gt;
  6304. &lt;p&gt;Symposium is currently focused on my setup, which means it works best with VSCode, Claude, Mac OS X, and Rust. But it’s meant to be unopinionated, which means it should be easy to extend to other environments (and in particular it already works great with other programming languages). The goal is not to compete with or replace those tools but to combine them together into something new and better.&lt;/p&gt;
  6305. &lt;p&gt;In addition to giving you a tour of Symposium, this blog post is an invitation: &lt;a href=&quot;https://github.com/symposium-dev/symposium&quot;&gt;Symposium is an open-source project&lt;/a&gt;, and I’m looking for people to explore with me! If you are excited about the idea of inventing new styles of AI collaboration, join the &lt;a href=&quot;https://symposium-dev.zulipchat.com&quot;&gt;symposium-dev Zulip&lt;/a&gt;. Let’s talk!&lt;/p&gt;
  6306. &lt;h3&gt;Demo video&lt;/h3&gt;
  6307. &lt;p&gt;I’m not normally one to watch videos online. But in this particular case, I do think a movie is going to be worth 1,000,000 words. Therefore, I’m embedding a short video (6min) demonstrating how Symposium works below. Check it out! But don’t worry, if videos aren’t your thing, you can just read the rest of the post instead.&lt;/p&gt;
  6308. &lt;div style=&quot;padding-bottom: 56.25%; height: 0; overflow: hidden;&quot;&gt;
  6309.      
  6310.    &lt;/div&gt;
  6311.  
  6312. &lt;p&gt;Alternatively, if you &lt;em&gt;really&lt;/em&gt; love videos, you can watch the &lt;a href=&quot;https://youtu.be/HQcIp-IBj0Q&quot;&gt;first version I made, which went into more depth&lt;/a&gt;. That version came in at 20 minutes, which I decided was…a bit much. 😁&lt;/p&gt;
  6313. &lt;h3&gt;Taskspaces let you juggle concurrent agents&lt;/h3&gt;
  6314. &lt;p&gt;The Symposium story begins with &lt;code&gt;Symposium.app&lt;/code&gt;, an OS X desktop application for managing &lt;em&gt;taskspaces&lt;/em&gt;. A taskspace is a clone of your project&lt;sup id=&quot;fnref:1&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:1&quot;&gt;1&lt;/a&gt;&lt;/sup&gt; paired with an agentic CLI tool that is assigned to complete some task.&lt;/p&gt;
  6315. &lt;p&gt;My observation has been that most people doing AI development spend a lot of time waiting while the agent does its thing. Taskspaces let you switch quickly back and forth.&lt;/p&gt;
  6316. &lt;p&gt;Before I was using taskspaces, I was doing this by jumping between different projects. I found that was really hurting my brain from context switching. But jumping between &lt;em&gt;tasks&lt;/em&gt; in a project is much easier. I find it works best to pair a complex topic with some simple refactorings.&lt;/p&gt;
  6317. &lt;p&gt;Here is what it looks like to use Symposium:&lt;/p&gt;
  6318. &lt;img alt=&quot;Screenshot of the Symposium app&quot; src=&quot;https://smallcultfollowing.com/babysteps/ /assets/2025-09-24-symposium/taskspaces.png&quot; width=&quot;100%&quot; /&gt;
  6319. &lt;p&gt;Each of those boxes is a taskspace. It has both its own isolated directory on the disk and an associated VSCode window. When you click on the taskspace, the app brings that window to the front. It can also hide other windows by positioning them exactly behind the first one in a stack&lt;sup id=&quot;fnref:2&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:2&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;. So it’s kind of like a mini window manager.&lt;/p&gt;
  6320. &lt;p&gt;Within each VSCode window, there is a terminal running an agentic CLI tool that has the Symposium &lt;a href=&quot;https://modelcontextprotocol.io/docs/getting-started/intro&quot;&gt;MCP server&lt;/a&gt;. If you’re not familiar with MCP, it’s a way for an LLM to invoke custom tools; it basically just gives the agent a list of available tools and a JSON scheme for what arguments they expect.&lt;/p&gt;
  6321. &lt;p&gt;The Symposium MCP server does a bunch of things–we’ll talk about more of them later–but one of them is that it lets the agent interact with taskspaces. The agent can use the MCP server to post logs and signal progress (you can see the logs in that screenshot); it can also spawn new taskspaces. I find that last part very handy.&lt;/p&gt;
  6322. &lt;p&gt;It often happens to me that while working on one idea, I find opportunities for cleanups or refactorings. Nowadays I just spawn out a taskspace with a quick description of the work to be done. Next time I’m bored, I can switch over and pick that up.&lt;/p&gt;
  6323. &lt;h3&gt;An aside: the Symposium app is written in Swift, a language I did not know 3 weeks ago&lt;/h3&gt;
  6324. &lt;p&gt;It’s probably worth mentioning that the Symposium app is written in Swift. I did not know Swift three weeks ago. But I’ve now written about 6K lines and counting. I feel like I’ve got a pretty good handle on how it works.&lt;sup id=&quot;fnref:3&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:3&quot;&gt;3&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
  6325. &lt;p&gt;Well, it’d be more accurate to say that I have &lt;em&gt;reviewed&lt;/em&gt; about 6K lines, since most of the time Claude generates the code. I mostly read it and offer suggestions for improvement&lt;sup id=&quot;fnref:4&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:4&quot;&gt;4&lt;/a&gt;&lt;/sup&gt;. When I do dive in and edit the code myself, it’s interesting because I find I don’t have the muscle memory for the syntax. I think this is pretty good evidence for the fact that agentic tools help you get started in a new programming language.&lt;/p&gt;
  6326. &lt;h3&gt;Walkthroughs let AIs explain code to you&lt;/h3&gt;
  6327. &lt;p&gt;So, while taskspaces let you jump between tasks, the rest of Symposium is dedicated to helping you complete an individual task. A big part of that is trying to go beyond the limits of the CLI interface by connecting the agent up to the IDE. For example, the Symposium MCP server has a tool called &lt;code&gt;present_walkthrough&lt;/code&gt; which lets the agent present you with a markdown document that explains how some code works. These walkthroughs show up in a side panel in VSCode:&lt;/p&gt;
  6328. &lt;img alt=&quot;Walkthrough screenshot&quot; src=&quot;https://smallcultfollowing.com/babysteps/ /assets/2025-09-24-symposium/walkthrough.png&quot; width=&quot;100%&quot; /&gt;
  6329. &lt;p&gt;As you can see, the walkthroughs can embed mermaid, which is pretty cool. It’s sometimes so clarifying to see a flowchart or a sequence diagram.&lt;/p&gt;
  6330. &lt;p&gt;Walkthroughs can also embed &lt;em&gt;comments&lt;/em&gt;, which are anchored to particular parts of the code. You can see one of those in the screenshot too, on the right.&lt;/p&gt;
  6331. &lt;p&gt;Each comment has a Reply button that lets you respond to the comment with further questions or suggest changes; you can also select random bits of text and use the “code action” called “Discuss in Symposium”. Both of these take you back to the terminal where your agent is running. They embed a little bit of XML (&lt;code&gt;&amp;lt;symposium-ref id=&quot;...&quot;/&amp;gt;&lt;/code&gt;) and then you can just type as normal. The agent can then use another MCP tool to expand that reference to figure out what you are referring to or what you are replying to.&lt;/p&gt;
  6332. &lt;p&gt;To some extent, this “reference the thing I’ve selected” functionality is “table stakes”, since Claude Code already does it. But Symposium’s version works anywhere (Q CLI doesn’t have that functionality, for example) and, more importantly, it lets you embed multiple refrences at once. I’ve found that to be really useful. Sometimes I’ll wind up with a message that is replying to one comment while referencing two or three other things, and the &lt;code&gt;&amp;lt;symposium-ref/&amp;gt;&lt;/code&gt; system lets me do that no problem.&lt;/p&gt;
  6333. &lt;h3&gt;Integrating with IDE knowledge&lt;/h3&gt;
  6334. &lt;p&gt;Symposium also includes an &lt;code&gt;ide-operations&lt;/code&gt; tool that lets the agent connect to the IDE to do things like “find definitions” or “find references”. To be honest I haven’t noticed this being that important (Claude is surprisingly handy with awk/sed) but I also haven’t done much tinkering with it. I know there are other MCP servers out there too, like &lt;a href=&quot;https://github.com/oraios/serena&quot;&gt;Serena&lt;/a&gt;, so maybe the right answer is just to import one of those, but I think there’s a lot of interesting stuff we &lt;em&gt;could&lt;/em&gt; do here by integrating deeper knowledge of the code, so I have been trying to keep it “in house” for now.&lt;/p&gt;
  6335. &lt;h3&gt;Leveraging Rust conventions&lt;/h3&gt;
  6336. &lt;p&gt;Continuing our journey down the stack, let’s look at one more bit of functionality, which are MCP tools aimed at making agents better at working with Rust code. By far the most effective of these so far is one I call &lt;a href=&quot;https://symposium-dev.github.io/symposium/design/mcp-tools/rust-development.html#get_rust_crate_source&quot;&gt;&lt;code&gt;get_rust_crate_source&lt;/code&gt;&lt;/a&gt;. It is very simple: given the name of a crate, it just checks out the code into a temporary directory for the agent to use. Well, actually, it does a &lt;em&gt;bit&lt;/em&gt; more than that. If the agent supplies a search string, it also searches for that string so as to give the agent a “head start” in finding the relevant code, and it makes a point to highlight code in the examples directory in particular.&lt;/p&gt;
  6337. &lt;h3&gt;We could do a lot more with Rust…&lt;/h3&gt;
  6338. &lt;p&gt;My experience has been that this tool makes all the difference. Without it, Claude just geneates plausible-looking APIs that don’t really exist. With it, Claude generally figures out exactly what to do. But really it’s just scratching the surface of what we can do. I am excited to go deeper here now that the basic structure of Symposium is in place – for example, I’d love to develop Rust-specific code reviewers that can critique the agent’s code or offer it architectural advice&lt;sup id=&quot;fnref:5&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:5&quot;&gt;5&lt;/a&gt;&lt;/sup&gt;, or a tool like &lt;a href=&quot;https://github.com/plasma-umass/CWhy&quot;&gt;CWhy&lt;/a&gt; to help people resolve Rust trait errors or macro problems.&lt;/p&gt;
  6339. &lt;h3&gt;…and can we decentralize it?&lt;/h3&gt;
  6340. &lt;p&gt;But honestly what I’m &lt;em&gt;most&lt;/em&gt; excited about is the idea of &lt;strong&gt;decentralizing&lt;/strong&gt;. I want Rust library authors to have a standard way to attach custom guidance and instructions that will help agents use their library. I want an AI-enhanced variant of &lt;code&gt;cargo upgrade&lt;/code&gt; that automatically bridges over major versions, making use of crate-supplied metadata about what changed and what rewrites are needed. Heck, I want libraries to be able to ship with MCP servers implemented in WASM (&lt;a href=&quot;https://opensource.microsoft.com/blog/2025/08/06/introducing-wassette-webassembly-based-tools-for-ai-agents/&quot;&gt;Wassette&lt;/a&gt;, anyone?) so that Rust developers using that library can get custom commands and tools for working with it. I don’t 100% know what this looks like but I’m keen to explore it. If there’s one thing I’ve learned from Rust, it’s always bet on the ecosystem.&lt;/p&gt;
  6341. &lt;h3&gt;Looking further afield, can we use agents to help humans collaborate better?&lt;/h3&gt;
  6342. &lt;p&gt;One of the things I am very curious to explore is how we can use agents to help humans collaborate better. It’s oft observed that coding with agents can be a bit lonely&lt;sup id=&quot;fnref:6&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:6&quot;&gt;6&lt;/a&gt;&lt;/sup&gt;. But I’ve also noticed that structuring a project for AI consumption requires relatively decent documentation. For example, one of the things I did recently for Symposium was to create a Request for Dialogue (RFD) process – a simplified version of Rust’s RFC process. My motivation was partly in anticipation of trying to grow a community of contributors, but it was also because most every major refactoring or feature work I do begins with iterating on docs. The doc becomes a central tracking record so that I can clear the context and rest assured that I can pick up where I left off. But a nice side-effect is that the project has more docs than you might expect, considering, and I hope that will make it easier to dive in and get acquainted.&lt;/p&gt;
  6343. &lt;p&gt;And what about other things? Like, I think that taskspaces should really be associated with github issues. If we did that, could we do a better job at helping new contributors pick up an issue? Or at providing mentoring instructions to get started?&lt;/p&gt;
  6344. &lt;p&gt;What about memory? I really want to add in some kind of automated memory system that accumulates knowledge about the system more automatically. But could we then share that knowledge (or a subset of it) across users, so that when I go to hack on a project, I am able to “bootstrap” with the accumulated observations of other people who’ve been working on it?&lt;/p&gt;
  6345. &lt;p&gt;Can agents help in guiding and shepherding design conversations? At work, when I’m circulating a document, I will typically download a copy of that document with people’s comments embedded in it. Then I’ll use pandoc to convert that into Markdown with HTML comments and then ask Claude to read it over and help me work through the comments systematically. Could we do similar things to manage unwieldy RFC threads?&lt;/p&gt;
  6346. &lt;p&gt;This is part of what gets me excited about AI. I mean, don’t get me wrong. I’m scared too. There’s no question that the spread of AI will change a lot of things in our society, and definitely not always for the better. But it’s also a huge opportunity. AI is empowering! Suddenly, learning new things is just &lt;em&gt;vastly&lt;/em&gt; easier. And when you think about the potential for integrating AI into community processes, I think that it could easily be used to bring us closer together and maybe even to make progress on previously intractable problems in open-source&lt;sup id=&quot;fnref:7&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:7&quot;&gt;7&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
  6347. &lt;h3&gt;Conclusion: Want to build something cool?&lt;/h3&gt;
  6348. &lt;p&gt;As I said in the beginning, this post is two things. Firstly, it’s an advertisement for Symposium. If you think the stuff I described sounds cool, give Symposium a try! You can find &lt;a href=&quot;https://symposium-dev.github.io/symposium/install.html&quot;&gt;installation instructions&lt;/a&gt; here. I gotta warn you, as of this writing, I think I’m the only user, so I would not at all be surprised to find out that there’s bugs in setup scripts etc. But hey, try it out, find bugs and tell me about them! Or better yet, fix them!&lt;/p&gt;
  6349. &lt;p&gt;But secondly, and more importantly, this blog post is an invitation to come out and play&lt;sup id=&quot;fnref:8&quot;&gt;&lt;a class=&quot;footnote-ref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fn:8&quot;&gt;8&lt;/a&gt;&lt;/sup&gt;. I’m keen to have more people come and hack on Symposium. There’s so much we could do! I’ve identified a number of &lt;a href=&quot;http://smallcultfollowing.com/babysteps/atom.xml&quot;&gt;“good first issue” bugs&lt;/a&gt;. Or, if you’re keen to take on a larger project, I’ve got a set of invited “Request for Dialogue” projects you could pick up and make your own. And if none of that suits your fancy, feel free to pitch you own project – just join the &lt;a href=&quot;https://symposium-dev.zulipchat.com&quot;&gt;Zulip&lt;/a&gt; and open a topic!&lt;/p&gt;
  6350. &lt;div class=&quot;footnotes&quot;&gt;
  6351. &lt;hr /&gt;
  6352. &lt;ol&gt;
  6353. &lt;li id=&quot;fn:1&quot;&gt;
  6354. &lt;p&gt;Technically, a git worktree. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:1&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  6355. &lt;/li&gt;
  6356. &lt;li id=&quot;fn:2&quot;&gt;
  6357. &lt;p&gt;That’s what the “Stacked” box does; if you uncheck it, the windows can be positioned however you like. I’m also working on a tiled layout mode. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:2&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  6358. &lt;/li&gt;
  6359. &lt;li id=&quot;fn:3&quot;&gt;
  6360. &lt;p&gt;Well, mostly. I still have some warnings about something or other not being threadsafe that I’ve been ignoring. Claude assures me they are not a big deal (Claude can be so lazy omg). &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:3&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  6361. &lt;/li&gt;
  6362. &lt;li id=&quot;fn:4&quot;&gt;
  6363. &lt;p&gt;Mostly: “Claude will you please for the love of God stop copying every function ten times.” &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:4&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  6364. &lt;/li&gt;
  6365. &lt;li id=&quot;fn:5&quot;&gt;
  6366. &lt;p&gt;E.g., don’t use a tokio mutex you fool, &lt;a href=&quot;https://ryhl.io/blog/actors-with-tokio/&quot;&gt;use an actor&lt;/a&gt;. That is one particular bit of advice I’ve given more than once. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:5&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  6367. &lt;/li&gt;
  6368. &lt;li id=&quot;fn:6&quot;&gt;
  6369. &lt;p&gt;I’m kind of embarassed to admit that Claude’s dad jokes have managed to get a laugh out of me on occassion, though. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:6&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  6370. &lt;/li&gt;
  6371. &lt;li id=&quot;fn:7&quot;&gt;
  6372. &lt;p&gt;Narrator voice: &lt;em&gt;burnout. he means maintainer burnout.&lt;/em&gt; &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:7&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  6373. &lt;/li&gt;
  6374. &lt;li id=&quot;fn:8&quot;&gt;
  6375. &lt;p&gt;Tell me you went to high school in the 90s without telling me you went to high school in the 90s. &lt;a class=&quot;footnote-backref&quot; href=&quot;http://smallcultfollowing.com/babysteps/atom.xml#fnref:8&quot;&gt;↩︎&lt;/a&gt;&lt;/p&gt;
  6376. &lt;/li&gt;
  6377. &lt;/ol&gt;
  6378. &lt;/div&gt;</description>
  6379. <pubDate>Wed, 24 Sep 2025 20:39:46 +0000</pubDate>
  6380. </item>
  6381. <item>
  6382. <title>Mozilla Thunderbird: Thunderbird Monthly Development Digest: August 2025</title>
  6383. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3822</guid>
  6384. <link>https://blog.thunderbird.net/2025/09/thunderbird-monthly-development-digest-august-2025/</link>
  6385. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/09/blog-banner-developer1-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  6386. &lt;p&gt;Hello again from the Thunderbird development team! As autumn settles in, we’re balancing the steady pace of ongoing projects with some forward-looking planning for 2026. Alongside coding and testing, some of our recent attention has gone into budgets, roadmaps, and setting priorities for the year ahead. It’s not the most glamorous work, but it’s essential for keeping our momentum strong and ensuring that the big features we’re building today continue to deliver value well into the future. In the meantime, plenty of exciting progress has landed across the application, and here are some of the highlights.&lt;/p&gt;
  6387.  
  6388.  
  6389.  
  6390. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Exchange support for email is here&lt;/strong&gt;&lt;/h3&gt;
  6391.  
  6392.  
  6393.  
  6394. &lt;p&gt;Exchange support has officially landed in Thunderbird 144, which will roll out as our October monthly release. A big final push from the team saw a number of important features make it in before the merge:&lt;/p&gt;
  6395.  
  6396.  
  6397.  
  6398. &lt;ul&gt;
  6399. &lt;li&gt;Undo/Redo operations for move/copy/delete&lt;/li&gt;
  6400.  
  6401.  
  6402.  
  6403. &lt;li&gt;Notifications&lt;/li&gt;
  6404.  
  6405.  
  6406.  
  6407. &lt;li&gt;Basic Search&lt;/li&gt;
  6408.  
  6409.  
  6410.  
  6411. &lt;li&gt;Folder Repair&lt;/li&gt;
  6412.  
  6413.  
  6414.  
  6415. &lt;li&gt;Remote message content display &amp;amp; blocking&lt;/li&gt;
  6416.  
  6417.  
  6418.  
  6419. &lt;li&gt;Status Bar feedback messaging&lt;/li&gt;
  6420.  
  6421.  
  6422.  
  6423. &lt;li&gt;Account Settings screen changes&lt;/li&gt;
  6424.  
  6425.  
  6426.  
  6427. &lt;li&gt;Autosync manager for message downloads&lt;/li&gt;
  6428.  
  6429.  
  6430.  
  6431. &lt;li&gt;Attachment delete &amp;amp; detach&lt;/li&gt;
  6432.  
  6433.  
  6434.  
  6435. &lt;li&gt;First set of advanced server settings&lt;/li&gt;
  6436.  
  6437.  
  6438.  
  6439. &lt;li&gt;Experimental tenant-specific configuration options (behind a preference) now being tested with early adopters&lt;/li&gt;
  6440. &lt;/ul&gt;
  6441.  
  6442.  
  6443.  
  6444. &lt;p&gt;The QA team is continuing to work through their test plans with support from a small beta test group, and their findings will guide the documentation and support we share more broadly with users on monthly release 144, as well as the priorities to tackle before we head into the next chapter.&lt;/p&gt;
  6445.  
  6446.  
  6447.  
  6448. &lt;p&gt;Looking ahead, the team is already focused on:&lt;/p&gt;
  6449.  
  6450.  
  6451.  
  6452. &lt;ul&gt;
  6453. &lt;li&gt;Expanding advanced server settings for more complex environments&lt;/li&gt;
  6454.  
  6455.  
  6456.  
  6457. &lt;li&gt;Improving search functionality&lt;/li&gt;
  6458.  
  6459.  
  6460.  
  6461. &lt;li&gt;Folder Quotas &amp;amp; Subscriptions&lt;/li&gt;
  6462.  
  6463.  
  6464.  
  6465. &lt;li&gt;Refining the user experience as more real-world feedback comes in&lt;/li&gt;
  6466.  
  6467.  
  6468.  
  6469. &lt;li&gt;A planning session to scope work to support calendar and address book via EWS&lt;/li&gt;
  6470. &lt;/ul&gt;
  6471.  
  6472.  
  6473.  
  6474. &lt;p&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1847846&quot;&gt;&lt;u&gt;Keep track of feature delivery here.&lt;/u&gt;&lt;/a&gt;&lt;/p&gt;
  6475.  
  6476.  
  6477.  
  6478. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Conversation View Work Week&lt;/strong&gt;&lt;/h3&gt;
  6479.  
  6480.  
  6481.  
  6482. &lt;p&gt;One of the biggest milestones this month was our dedicated Conversation View Work Week which recently wrapped up, where designers and engineers gathered in person to tackle one of Thunderbird’s most anticipated UX features. &lt;/p&gt;
  6483.  
  6484.  
  6485.  
  6486. &lt;p&gt;The team aligned early on goals and scope, rapidly iterated on wireframes and high-fidelity mockups, and built out initial front-end components powered by the new Panorama database. &lt;/p&gt;
  6487.  
  6488.  
  6489.  
  6490. &lt;p&gt;By the end of the week, we had working prototypes that collapsed threads into a Gmail-style conversation view, demonstrated the new LiveView architecture, and produced detailed design documentation. It was an intense but rewarding sprint that laid the foundation for a more modern and intuitive Thunderbird experience.&lt;/p&gt;
  6491.  
  6492.  
  6493.  
  6494. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Account Hub&lt;/strong&gt;&lt;/h3&gt;
  6495.  
  6496.  
  6497.  
  6498. &lt;p&gt;We’ve now added the ability to manually edit an EWS configuration, as well as allow for users to create an advanced EWS configuration through the manual configuration step&lt;/p&gt;
  6499.  
  6500.  
  6501.  
  6502. &lt;p&gt;The ability to cancel any loading operation in account hub for email has been completed and will be added to daily shortly&lt;/p&gt;
  6503.  
  6504.  
  6505.  
  6506. &lt;ul&gt;
  6507. &lt;li&gt;This also had the side effect of users who click “Stop” in the account old setup with an OAuth window open now closing the OAuth window automatically&lt;/li&gt;
  6508.  
  6509.  
  6510.  
  6511. &lt;li&gt;We will be uplifting this change to beta and then ESR&lt;/li&gt;
  6512. &lt;/ul&gt;
  6513.  
  6514.  
  6515.  
  6516. &lt;p&gt;Progress is being made with adding a step for 3rd party hosting credentials confirmation, with the UI complete and the logic being worked on&lt;/p&gt;
  6517.  
  6518.  
  6519.  
  6520. &lt;ul&gt;
  6521. &lt;li&gt;This progress will have to take into account changes from the cancel loading patch, as there are conflicting changes&lt;/li&gt;
  6522.  
  6523.  
  6524.  
  6525. &lt;li&gt;Once this feature is complete, it will be uplifted to beta, and then ESR&lt;/li&gt;
  6526. &lt;/ul&gt;
  6527.  
  6528.  
  6529.  
  6530. &lt;p&gt;Work will soon be starting to enable the creation of address books through account hub by default.&lt;/p&gt;
  6531.  
  6532.  
  6533.  
  6534. &lt;p&gt;Follow progress in the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1981786&quot;&gt;&lt;u&gt;Meta Bug&lt;/u&gt;&lt;/a&gt;&lt;/p&gt;
  6535.  
  6536.  
  6537.  
  6538. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Calendar UI Rebuild&lt;/strong&gt;&lt;/h3&gt;
  6539.  
  6540.  
  6541.  
  6542. &lt;p&gt;After a long pause, work on the Calendar re-write has resumed! We’ve picked things back up by continuing focus on the event read dialog. A number of improvements have already landed, including proper handling of description data and several small bug fixes.&lt;/p&gt;
  6543.  
  6544.  
  6545.  
  6546. &lt;p&gt;We have seven patches under review that cover key areas such as:&lt;/p&gt;
  6547.  
  6548.  
  6549.  
  6550. &lt;ul&gt;
  6551. &lt;li&gt;Accessibility improvements, including proper announcements of event and calendar titles.&lt;/li&gt;
  6552.  
  6553.  
  6554.  
  6555. &lt;li&gt;Adding the footer for acceptance.&lt;/li&gt;
  6556.  
  6557.  
  6558.  
  6559. &lt;li&gt;Updating displays and transitioning current work to use the mod-src protocol.&lt;/li&gt;
  6560.  
  6561.  
  6562.  
  6563. &lt;li&gt;Handling resizing&lt;/li&gt;
  6564. &lt;/ul&gt;
  6565.  
  6566.  
  6567.  
  6568. &lt;p&gt;Development is also underway to add attendee support, after which we’ll move on to polishing the remaining pieces of the read dialog UI.&lt;/p&gt;
  6569.  
  6570.  
  6571.  
  6572. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Maintenance, Recent Features and Fixes&lt;/strong&gt;&lt;/h3&gt;
  6573.  
  6574.  
  6575.  
  6576. &lt;p&gt;August was set aside as a focus for maintenance, with a good number of our team dedicated to handling upstream liabilities such as our continued l10n migration to Fluent and module loading changes. In addition to these items, we’ve had help from the development community to deliver a variety of improvements over the past month:&lt;/p&gt;
  6577.  
  6578.  
  6579.  
  6580. &lt;ul&gt;
  6581. &lt;li&gt;Tree restyling following upstream changes – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1978947&quot;&gt;&lt;u&gt;solved&lt;/u&gt;&lt;/a&gt;&lt;/li&gt;
  6582.  
  6583.  
  6584.  
  6585. &lt;li&gt;An 18 year old bug to enable event duplication via drag &amp;amp; drop – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=411069&quot;&gt;&lt;u&gt;solved&lt;/u&gt;&lt;/a&gt;&lt;/li&gt;
  6586.  
  6587.  
  6588.  
  6589. &lt;li&gt;A 15 year old bug to sort by unread in threads correctly – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=617855&quot;&gt;&lt;u&gt;solved&lt;/u&gt;&lt;/a&gt;&lt;/li&gt;
  6590.  
  6591.  
  6592.  
  6593. &lt;li&gt;Implementation of standard colours throughout the application. [&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979362&quot;&gt;&lt;u&gt;meta bug&lt;/u&gt;&lt;/a&gt;]&lt;/li&gt;
  6594.  
  6595.  
  6596.  
  6597. &lt;li&gt;Modernization of module inclusion. [&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979960&quot;&gt;&lt;u&gt;meta bug&lt;/u&gt;&lt;/a&gt;]&lt;/li&gt;
  6598.  
  6599.  
  6600.  
  6601. &lt;li&gt;and many more which are listed in &lt;a href=&quot;https://www.thunderbird.net/en-US/thunderbird/144.0beta/releasenotes/&quot;&gt;&lt;u&gt;release notes for beta&lt;/u&gt;&lt;/a&gt;.&lt;/li&gt;
  6602. &lt;/ul&gt;
  6603.  
  6604.  
  6605.  
  6606. &lt;p&gt;If you would like to see new features as they land, and help us squash some early bugs, you can try running &lt;a href=&quot;https://archive.mozilla.org/pub/thunderbird/nightly/latest-comm-central/&quot;&gt;&lt;u&gt;daily&lt;/u&gt;&lt;/a&gt; and check the pushlog to see what has recently landed. This assistance is immensely helpful for catching problems early.&lt;/p&gt;
  6607.  
  6608.  
  6609.  
  6610. &lt;p&gt;—&lt;/p&gt;
  6611.  
  6612.  
  6613.  
  6614. &lt;p&gt;&lt;strong&gt;Toby Pilling&lt;/strong&gt;&lt;/p&gt;
  6615.  
  6616.  
  6617.  
  6618. &lt;p&gt;Senior Manager, Desktop Engineering&lt;/p&gt;
  6619. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/09/thunderbird-monthly-development-digest-august-2025/&quot;&gt;Thunderbird Monthly Development Digest: August 2025&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  6620. <pubDate>Wed, 24 Sep 2025 14:22:05 +0000</pubDate>
  6621. <dc:creator>Toby Pilling</dc:creator>
  6622. </item>
  6623. <item>
  6624. <title>The Rust Programming Language Blog: crates.io: Malicious crates faster_log and async_println</title>
  6625. <guid isPermaLink="true">https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/</guid>
  6626. <link>https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/</link>
  6627. <description>&lt;p&gt;&lt;strong&gt;Updated September 24th, 2025 17:34:38 UTC&lt;/strong&gt; - Socket has also published their own &lt;a href=&quot;https://socket.dev/blog/two-malicious-rust-crates-impersonate-popular-logger-to-steal-wallet-keys&quot;&gt;accompanying blog post&lt;/a&gt; about the attack.&lt;/p&gt;
  6628. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#summary&quot;&gt;&lt;/a&gt;
  6629. Summary&lt;/h3&gt;
  6630. &lt;p&gt;On September 24th, the crates.io team was notified by Kirill Boychenko from the &lt;a href=&quot;https://www.socket.dev/&quot;&gt;Socket Threat Research Team&lt;/a&gt; of two malicious crates which were actively searching file contents for Etherum private keys, Solana private keys, and arbitrary byte arrays for exfiltration.&lt;/p&gt;
  6631. &lt;p&gt;These crates were:&lt;/p&gt;
  6632. &lt;ul&gt;
  6633. &lt;li&gt;&lt;code&gt;faster_log&lt;/code&gt; - Published on May 25th, 2025, downloaded 7181 times&lt;/li&gt;
  6634. &lt;li&gt;&lt;code&gt;async_println&lt;/code&gt; - Published on May 25th, 2025, downloaded 1243 times&lt;/li&gt;
  6635. &lt;/ul&gt;
  6636. &lt;p&gt;The malicious code was executed at runtime, when running or testing a project depending on them. Notably, they did not execute any malicious code at build time. Except for their malicious payload, these crates copied the source code, features, and documentation of legitimate crates, using a similar name to them (a case of typosquatting&lt;sup class=&quot;footnote-reference&quot; id=&quot;fr-typosquatting-1&quot;&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#fn-typosquatting&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;).&lt;/p&gt;
  6637. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#actions-taken&quot;&gt;&lt;/a&gt;
  6638. Actions taken&lt;/h3&gt;
  6639. &lt;p&gt;The users in question were immediately disabled, and the crates in question were deleted&lt;sup class=&quot;footnote-reference&quot; id=&quot;fr-deletion-1&quot;&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#fn-deletion&quot;&gt;2&lt;/a&gt;&lt;/sup&gt; from crates.io shortly after. We have retained copies of all logs associated with the users and the malicious crate files for further analysis.&lt;/p&gt;
  6640. &lt;p&gt;The deletion was performed at 15:34 UTC on September 24, 2025.&lt;/p&gt;
  6641. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#analysis&quot;&gt;&lt;/a&gt;
  6642. Analysis&lt;/h3&gt;
  6643. &lt;p&gt;Both crates were copies of a crate which provided logging functionality, and the logging implementation remained functional in the malicious crates. The original crate had a feature which performed log file packing, which iterated over an associated directories files.&lt;/p&gt;
  6644. &lt;p&gt;The attacker inserted code to perform the malicious action during a log packing operation, which searched the log files being processed from that directory for:&lt;/p&gt;
  6645. &lt;ul&gt;
  6646. &lt;li&gt;Quoted Ethereum private keys (0x + 64 hex)&lt;/li&gt;
  6647. &lt;li&gt;Solana-style Base58 secrets&lt;/li&gt;
  6648. &lt;li&gt;Bracketed byte arrays&lt;/li&gt;
  6649. &lt;/ul&gt;
  6650. &lt;p&gt;The crates then proceeded to exfiltrate the results of this search to &lt;code&gt;https://mainnet[.]solana-rpc-pool[.]workers[.]dev/&lt;/code&gt;.&lt;/p&gt;
  6651. &lt;p&gt;These crates had no dependent downstream crates on crates.io.&lt;/p&gt;
  6652. &lt;p&gt;The malicious users associated with these crates had no other crates or publishes, and the team is actively investigating associative actions in our retained&lt;sup class=&quot;footnote-reference&quot; id=&quot;fr-retention-1&quot;&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#fn-retention&quot;&gt;3&lt;/a&gt;&lt;/sup&gt; logs.&lt;/p&gt;
  6653. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#thanks&quot;&gt;&lt;/a&gt;
  6654. Thanks&lt;/h3&gt;
  6655. &lt;p&gt;Our thanks to Kirill Boychenko from the &lt;a href=&quot;https://www.socket.dev/&quot;&gt;Socket Threat Research Team&lt;/a&gt; for reporting the crates. We also want to thank Carol Nichols from the crates.io team, Pietro Albini from the Rust Security Response WG and Walter Pearce from the &lt;a href=&quot;https://foundation.rust-lang.org/&quot;&gt;Rust Foundation&lt;/a&gt; for aiding in the response.&lt;/p&gt;
  6656. &lt;section class=&quot;footnotes&quot;&gt;
  6657. &lt;ol class=&quot;footnotes-list&quot;&gt;
  6658. &lt;li id=&quot;fn-typosquatting&quot;&gt;
  6659. &lt;p&gt;typosquatting is a technique used by bad actors to initiate dependency confusion attacks where a legitimate user might be tricked into using a malicious dependency instead of their intended dependency — for example, a bad actor might try to publish a crate at &lt;code&gt;proc-macro3&lt;/code&gt; to catch users of the legitimate &lt;code&gt;proc-macro2&lt;/code&gt; crate. &lt;a href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#fr-typosquatting-1&quot;&gt;↩&lt;/a&gt;&lt;/p&gt;
  6660. &lt;/li&gt;
  6661. &lt;li id=&quot;fn-deletion&quot;&gt;
  6662. &lt;p&gt;The crates were preserved for future analysis should there be other attacks, and to inform scanning efforts in the future. &lt;a href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#fr-deletion-1&quot;&gt;↩&lt;/a&gt;&lt;/p&gt;
  6663. &lt;/li&gt;
  6664. &lt;li id=&quot;fn-retention&quot;&gt;
  6665. &lt;p&gt;One year of logs are retained on crates.io, but only 30 days are immediately available on our log platform. We chose not to go further back in our analysis, since IP address based analysis is limited by the use of dynamic IP addresses in the wild, and the relevant IP address being part of an allocation to a residential ISP. &lt;a href=&quot;https://blog.rust-lang.org/2025/09/24/crates.io-malicious-crates-fasterlog-and-asyncprintln/#fr-retention-1&quot;&gt;↩&lt;/a&gt;&lt;/p&gt;
  6666. &lt;/li&gt;
  6667. &lt;/ol&gt;
  6668. &lt;/section&gt;</description>
  6669. <pubDate>Wed, 24 Sep 2025 00:00:00 +0000</pubDate>
  6670. <dc:creator>Walter Pearce</dc:creator>
  6671. </item>
  6672. <item>
  6673. <title>Mozilla Thunderbird: State of the Thunder 12: Community, Android, and Mozilla Connect</title>
  6674. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3814</guid>
  6675. <link>https://blog.thunderbird.net/2025/09/state-of-the-thunder-12-community-android-and-mozilla-connect/</link>
  6676. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/09/Blog-banner-State-of-the-Thunder12-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  6677. &lt;p&gt;We’re back with our twelfth episode of the State of the Thunder! In this episode, we’re talking about community initiatives, filling you in on Android development, and finishing our updates on popular Mozilla Connect requests. &lt;/p&gt;
  6678.  
  6679.  
  6680.  
  6681. &lt;p&gt;Want to find out how to join future State of the Thunders? Be sure to join our &lt;a href=&quot;https://thunderbird.topicbox.com/groups/planning&quot;&gt;Thunderbird planning mailing list&lt;/a&gt; for all the details. &lt;/p&gt;
  6682.  
  6683.  
  6684.  
  6685. &lt;h3&gt;Austin RiverHacks and Ask-A Fox&lt;/h3&gt;
  6686.  
  6687.  
  6688.  
  6689. &lt;p&gt;Thunderbird is a Silver sponsor for &lt;a href=&quot;https://austin-ai.org/event/riverhacks-nasa-space-apps-challenge-2025/&quot;&gt;Austin RiverHacks NASA Space Apps Challenge 2025&lt;/a&gt;! If you’re in or around Austin, Texas from October 4th-5th, and want to join an in-person event where curious minds delve into NASA data to tackle real-life problems, we’d love to see you. &lt;/p&gt;
  6690.  
  6691.  
  6692.  
  6693. &lt;p&gt;This week (as in right now! Check it out and get involved!), we’re joining forces with Firefox for the &lt;a href=&quot;https://community.mozilla.org/en/campaigns/ask-a-fox/&quot;&gt;Ask-A-Fox event on Mozilla Support&lt;/a&gt;! Earn swag, join an incredible community, and help fellow Thunderbird users on desktop and Android! Want a great overview of how to contribute to SUMO? Watch our &lt;a href=&quot;https://blog.thunderbird.net/2024/08/video-how-to-answer-thunderbird-questions-on-mozilla-support/&quot;&gt;Community Office Hours&lt;/a&gt; with advice on getting started.&lt;/p&gt;
  6694.  
  6695.  
  6696.  
  6697. &lt;h3&gt;Android Plans for Q4 2025&lt;/h3&gt;
  6698.  
  6699.  
  6700.  
  6701. &lt;p&gt;It’s hard to believe we’re almost into the last three months of the year! We’ve just released our joint &lt;a href=&quot;https://blog.thunderbird.net/2025/09/mobile-progress-report-july-august-2025/&quot;&gt;July/August Mobile Progress&lt;/a&gt; report. We also want to give you all an update on our overall progress on the &lt;a href=&quot;https://github.com/orgs/thunderbird/projects/19&quot;&gt;roadmap&lt;/a&gt; we created at the beginning of the year. &lt;/p&gt;
  6702.  
  6703.  
  6704.  
  6705. &lt;p&gt;The new Account Drawer, currently in Beta, isn’t finished yet. We’re still working on real, proper unified folders! We’ll have mockups of the account drawer progress before the end of the month and more info in the next beta’s release notes. We’ll also have updates soon on message list status notifications (similar to the desktop). In the single message view, we have improvements coming! This includes making attachments quicker to see and open. &lt;/p&gt;
  6706.  
  6707.  
  6708.  
  6709. &lt;p&gt;The battle for proper IMAP fetch continues. Different server setups complicate this struggle, but we want to get this right, nonetheless. This will bring the Android app more on par with other emails apps.&lt;/p&gt;
  6710.  
  6711.  
  6712.  
  6713. &lt;p&gt;Unfortunately, work on things like message sync, notifications, and Android 15 might delay features like HTML signatures.&lt;/p&gt;
  6714.  
  6715.  
  6716.  
  6717. &lt;h3&gt;Mozilla Connect Updates, Continued&lt;/h3&gt;
  6718.  
  6719.  
  6720.  
  6721. &lt;p&gt;We’re tackling more of the most frequently requested changes and features on Mozilla Connect, and we’re answering questions about native operating system integration, conversation view, and Thunderbird Pro related features!&lt;/p&gt;
  6722.  
  6723.  
  6724.  
  6725. &lt;h4&gt;Native Operating System Integration&lt;/h4&gt;
  6726.  
  6727.  
  6728.  
  6729. &lt;p&gt;When your operating system is capable of something Thunderbird isn’t, we share your frustration. We want things like OS-native progress bars that show you how downloads are going. We’ve started work on OS-native notification actions, like &lt;a href=&quot;https://connect.mozilla.org/t5/ideas/delete-a-mail-directly-from-notification/idi-p/15884&quot;&gt;deleting messages&lt;/a&gt;. We love how helpful and time-saving this is, and want to expand it to things like calendar reminders.&lt;/p&gt;
  6730.  
  6731.  
  6732.  
  6733. &lt;p&gt;There’s possibility and limitation in this, thanks to both Firefox and the OS itself. Firefox enables us more than it restricts us. For example, our work on the progress bar comes straight from Firefox code. Though there are some limits, and Thunderbird’s different needs as a mail client sometimes mean we need to improve an aspect of Firefox to enable further development. But the beauty of open source means we can contribute our improvements upstream!  The OS often constrains us more. For example, we’d love snoozeable native OS calendar notifications, but they just aren’t possible yet.&lt;/p&gt;
  6734.  
  6735.  
  6736.  
  6737. &lt;h4&gt;Conversation View&lt;/h4&gt;
  6738.  
  6739.  
  6740.  
  6741. &lt;p&gt;We just finished an entire in-person work week focused on this in Vancouver! &lt;a href=&quot;https://connect.mozilla.org/t5/ideas/true-threaded-conversations-in-thunderbird/idi-p/29558&quot;&gt;Conversation view&lt;/a&gt;, if you’re not familiar with it, includes ALL messages in a conversation, including your replies and messages moved to different folders. This feature, along with others, depends on having a single database for all messages in Thunderbird. Our current database doesn’t do this; instead, each folder is its own database.&lt;/p&gt;
  6742.  
  6743.  
  6744.  
  6745. &lt;p&gt;The new SQLite database, which we’re calling Panorama, will enable a true Conversation View. During the work week, we thought about (and visualized) what the UI will look like. Having developers and designers in the same room was incredibly helpful for a complicated change. (Having a gassy Boston Terrier in said room, less so.) The existing code expects the current database, so we’ll have to rebuild a lot and carefully consider our decisions. The switch to the new database will probably occur next year after the Extended Support Release, behind a preference.&lt;/p&gt;
  6746.  
  6747.  
  6748.  
  6749. &lt;p&gt;This change will help Thunderbird behave like a modern email client! Moving to Panorama will not only move us into the future, but into the present.&lt;/p&gt;
  6750.  
  6751.  
  6752.  
  6753. &lt;h3&gt;Thunderbird Pro Related-Requests&lt;/h3&gt;
  6754.  
  6755.  
  6756.  
  6757. &lt;p&gt;Three Mozilla Connect requests (&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/expand-relay-to-create-full-mozmail-e-mail/idi-p/7985&quot;&gt;Expanding Firefox Relay&lt;/a&gt;, a &lt;a href=&quot;https://connect.mozilla.org/t5/ideas/proposal-for-mozilla-email-domain/idi-p/48656&quot;&gt;paid Mozilla email domain&lt;/a&gt;, and a &lt;a href=&quot;https://connect.mozilla.org/t5/ideas/thunderbird-web-i-d-pay-a-sub-fee-for-it/idi-p/17607&quot;&gt;Thunderbird webmail&lt;/a&gt;) were all out of our control once. But now, with the upcoming Thunderbird Pro offerings, these all will be possible! We’re even experimenting with a webmail experience for Thundermail, in addition to using Thunderbird (or even another email client if you want.) We’ll have an upcoming State of the Thunder dedicated to Thunderbird Pro with more info and updates!&lt;/p&gt;
  6758.  
  6759.  
  6760.  
  6761. &lt;h3&gt;Watch the Video (also on &lt;a href=&quot;https://tilvids.com/w/pmPUW6bjXecEyw6uoq7R1t&quot;&gt;PeerTube&lt;/a&gt;)&lt;/h3&gt;
  6762.  
  6763.  
  6764.  
  6765. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  6766.  
  6767. &lt;/div&gt;&lt;/figure&gt;
  6768.  
  6769.  
  6770.  
  6771. &lt;h3&gt;Listen to the Podcast&lt;/h3&gt;
  6772.  
  6773.  
  6774.  
  6775. &lt;p&gt;&lt;/p&gt;
  6776. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/09/state-of-the-thunder-12-community-android-and-mozilla-connect/&quot;&gt;State of the Thunder 12: Community, Android, and Mozilla Connect&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  6777. <pubDate>Tue, 23 Sep 2025 15:10:45 +0000</pubDate>
  6778. <dc:creator>Monica Ayhens-Madon</dc:creator>
  6779. </item>
  6780. <item>
  6781. <title>Firefox Nightly: Firefox 144 Highlights: Faster Add-ons, Smarter DevTools, and Tab Group Boosts – These Weeks in Firefox, Issue 189</title>
  6782. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1888</guid>
  6783. <link>https://blog.nightly.mozilla.org/2025/09/22/firefox-144-highlights-faster-add-ons-smarter-devtools-and-tab-group-boosts-these-weeks-in-firefox-issue-189/</link>
  6784. <description>&lt;h3&gt;Highlights&lt;/h3&gt;
  6785. &lt;ul&gt;
  6786. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=772178&quot;&gt;Leo Liu [:leoliu]&lt;/a&gt; added a panel for AntiTracking debugging (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1972771&quot;&gt;#1972771&lt;/a&gt;) behind devtools.anti-tracking.enabled&lt;/li&gt;
  6787. &lt;/ul&gt;
  6788. &lt;p&gt;&lt;img alt=&quot;A panel in DevTools for AntiTracking debugging&quot; class=&quot;alignnone size-large wp-image-1890&quot; height=&quot;152&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/09/headlines189_2-600x152.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  6789. &lt;ul&gt;
  6790. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot [:ochameau]&lt;/a&gt; added a “User-defined” badge in the markup view event tooltip to differentiate them from “native” events (and possibly spotting event not supported in Firefox) (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1977628&quot;&gt;#1977628&lt;/a&gt;)&lt;/li&gt;
  6791. &lt;/ul&gt;
  6792. &lt;p&gt;&lt;img alt=&quot;&amp;quot;User-defined&amp;quot; badge in the DevTools markup view event tooltip&quot; class=&quot;alignnone size-large wp-image-1891&quot; height=&quot;182&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/09/headlines189_3-600x182.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  6793. &lt;ul&gt;
  6794. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=557153&quot;&gt;Nicolas Chevobbe [:nchevobbe]&lt;/a&gt; added a “Jump to definition” icon for CSS variables in the Inspector Rules view (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1278517&quot;&gt;#1278517&lt;/a&gt;)&lt;/li&gt;
  6795. &lt;/ul&gt;
  6796. &lt;p&gt;&lt;img alt=&quot;A &amp;quot;Jump to definition&amp;quot; icon for CSS variables in the Inspector Rules view&quot; class=&quot;alignnone size-large wp-image-1889&quot; height=&quot;74&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/09/headlines189_1-600x74.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  6797. &lt;h3&gt;Friends of the Firefox team&lt;/h3&gt;
  6798. &lt;h4&gt;Introductions/Shout-Outs&lt;/h4&gt;
  6799. &lt;ul&gt;
  6800. &lt;li&gt;New contributor &lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=409790&quot;&gt;Merci chao&lt;/a&gt; has filed a whole bunch of valid and useful tab group bugs&lt;/li&gt;
  6801. &lt;/ul&gt;
  6802. &lt;h4&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20(excluding%20employees)&amp;amp;quicksearch=1892101%2C1969417%2C1979919%2C1689380%2C1982968%2C1984296%2C1982767%2C1981384%2C1984788%2C1813675%2C1583902%2C1956493%2C1984661%2C1679997%2C1787457%2C1984872&quot;&gt;Resolved bugs (excluding employees)&lt;/a&gt;&lt;/h4&gt;
  6803. &lt;h4&gt;Volunteers that fixed more than one bug&lt;/h4&gt;
  6804. &lt;ul&gt;
  6805. &lt;li&gt;Alexander Kuleshov&lt;/li&gt;
  6806. &lt;/ul&gt;
  6807. &lt;h4&gt;New contributors (🌟 = first patch)&lt;/h4&gt;
  6808. &lt;ul&gt;
  6809. &lt;li&gt;Josh Berry added &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984553&quot;&gt;groupId to browser.tabs.onUpdated event&lt;/a&gt;&lt;/li&gt;
  6810. &lt;li&gt;Jacqueline Amherst [:jqln] &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1981376&quot;&gt;moved gPrivateBrowsingUI to its own file&lt;/a&gt; and avoid loading it unless/until we encounter our first private window&lt;/li&gt;
  6811. &lt;/ul&gt;
  6812. &lt;h3&gt;Project Updates&lt;/h3&gt;
  6813. &lt;h4&gt;Add-ons / Web Extensions&lt;/h4&gt;
  6814. &lt;h5&gt;Addon Manager &amp;amp; about:addons&lt;/h5&gt;
  6815. &lt;ul&gt;
  6816. &lt;li&gt;InstallTrigger API implementation has been fully removed in Firefox 144 🥳 – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1776426&quot;&gt;Bug 1776426&lt;/a&gt; / &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979227&quot;&gt;Bug 1979227&lt;/a&gt;
  6817. &lt;ul&gt;
  6818. &lt;li&gt;Thanks to Gregory Pappas for the immense help on this one!&lt;/li&gt;
  6819. &lt;/ul&gt;
  6820. &lt;/li&gt;
  6821. &lt;li&gt;Fixed issue with add-on updates automatically cancelled due to new extension metadata property missing from previously installed add-ons – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984724&quot;&gt;Bug 1984724&lt;/a&gt;&lt;/li&gt;
  6822. &lt;li&gt;Improved spacing between about:addons add-on card message bars and add-ons card header – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984872&quot;&gt;Bug 1984872&lt;/a&gt;
  6823. &lt;ul&gt;
  6824. &lt;li&gt;Thanks to Sujal Singh for contributing this improvement to the about:addons cards!&lt;/li&gt;
  6825. &lt;/ul&gt;
  6826. &lt;/li&gt;
  6827. &lt;/ul&gt;
  6828. &lt;h5&gt;WebExtensions Framework&lt;/h5&gt;
  6829. &lt;ul&gt;
  6830. &lt;li&gt;Fixed Customize mode and keyboard shortcuts issue hit when a user may have clicked to the “extension settings” link from the add-on post-install dialog – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983869&quot;&gt;Bug 1983869&lt;/a&gt;&lt;/li&gt;
  6831. &lt;li&gt;Fixed regression preventing SVG icons associated with extension context menu items to be loaded successfully – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986618&quot;&gt;Bug 1986618&lt;/a&gt; (fixed in the Firefox 143, same Firefox version where the regression was initially introduced through &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979338&quot;&gt;Bug 1979338&lt;/a&gt;).&lt;/li&gt;
  6832. &lt;/ul&gt;
  6833. &lt;h5&gt;WebExtension APIs&lt;/h5&gt;
  6834. &lt;ul&gt;
  6835. &lt;li&gt;In Firefox 144 browser.storage.local and browser.storage.managed WebExtensions API are now also providing a getBytesInUse API method – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1385832&quot;&gt;Bug 1385832&lt;/a&gt;
  6836. &lt;ul&gt;
  6837. &lt;li&gt;Thanks to Nathan Gross for contributing this enhancement to the WebExtensions storage APIs!&lt;/li&gt;
  6838. &lt;/ul&gt;
  6839. &lt;/li&gt;
  6840. &lt;li&gt;Added missing groupId property to the browser.tabs.onUpdated API method – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984553&quot;&gt;Bug 1984553&lt;/a&gt;.
  6841. &lt;ul&gt;
  6842. &lt;li&gt;Thanks to Josh Berry for reporting and fixing this gap in our WebExtensions API JSONSchema definitions&lt;/li&gt;
  6843. &lt;li&gt;NOTE&lt;b&gt;:&lt;/b&gt; this change mainly matters for TypeScript type definitions being generated based on our JSONSchema definitions. The groupId property was set in the browser.tabs.onUpdated API event details even without this fix to the JSONSchema.&lt;/li&gt;
  6844. &lt;/ul&gt;
  6845. &lt;/li&gt;
  6846. &lt;/ul&gt;
  6847. &lt;h4&gt;DevTools&lt;/h4&gt;
  6848. &lt;ul&gt;
  6849. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=750915&quot;&gt;Artem Manushenkov&lt;/a&gt;
  6850. &lt;ul&gt;
  6851. &lt;li&gt;documented &lt;a href=&quot;https://firefox-source-docs.mozilla.org/devtools-user/web_console/split_console/index.html#:~:text=you%20also%20can%20disable%20the%20split%20console%20altogether&quot;&gt;“Enable Split Console” setting&lt;/a&gt; and added missing alt attributes for images and updated the screenshot (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984296&quot;&gt;#1984296&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1981384&quot;&gt;#1981384&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984788&quot;&gt;#1984788&lt;/a&gt;)&lt;/li&gt;
  6852. &lt;li&gt;removed unused npm scripts from the debugger folder (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984661&quot;&gt;#1984661&lt;/a&gt;)&lt;/li&gt;
  6853. &lt;li&gt;added keyboard shortcuts for clearing the console in the clear button title (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984993&quot;&gt;#1984993&lt;/a&gt;)&lt;/li&gt;
  6854. &lt;/ul&gt;
  6855. &lt;/li&gt;
  6856. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=446518&quot;&gt;Sebastian Zartner [:sebo]&lt;/a&gt; added a inactive CSS warning for usage of overflow on non-block containers (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1583902&quot;&gt;#1583902&lt;/a&gt;)&lt;/li&gt;
  6857. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=764501&quot;&gt;Riz&lt;/a&gt; removed Chrome frames from Netmonitor stack traces (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1280266&quot;&gt;#1280266&lt;/a&gt;)&lt;/li&gt;
  6858. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=218550&quot;&gt;Robert Longson [:longsonr]&lt;/a&gt; fixed an issue where we would show an invalid message to users when devtools.netmonitor.requestBodyLimit=0 (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986196&quot;&gt;#1986196&lt;/a&gt;)&lt;/li&gt;
  6859. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=703422&quot;&gt;David Shin[:dshin]&lt;/a&gt; fixed a Chrome-Only method to make the selector highlighter work for @scope rules (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980210&quot;&gt;#1980210&lt;/a&gt;)&lt;/li&gt;
  6860. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=34283&quot;&gt;Masayuki Nakano [:masayuki]&lt;/a&gt; fixed the “Break on node removal” feature when a node is removed because a parent node’s innerHTML is updated (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984312&quot;&gt;#1984312&lt;/a&gt;)&lt;/li&gt;
  6861. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=763731&quot;&gt;Holger Benl [:hbenl]&lt;/a&gt; fixed an issue with screenshots in Responsive Design Mode (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979518&quot;&gt;#1979518&lt;/a&gt;)&lt;/li&gt;
  6862. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot [:ochameau]&lt;/a&gt; made React avoid updates for devtools in inactive/background tab (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1897765&quot;&gt;#1897765&lt;/a&gt;)&lt;/li&gt;
  6863. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot [:ochameau]&lt;/a&gt; fixed fetching iframe source content in the Debugger (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1977100&quot;&gt;#1977100&lt;/a&gt;)&lt;/li&gt;
  6864. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot [:ochameau]&lt;/a&gt; fixed opening some webpack-internal:///./ source from console stack traces (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982271&quot;&gt;#1982271&lt;/a&gt;)&lt;/li&gt;
  6865. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=656417&quot;&gt;Hubert Boma Manilla (:bomsy)&lt;/a&gt; made it possible to see server sent events in the Netmonitor event if the connection is still open (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1830230&quot;&gt;#1830230&lt;/a&gt;)&lt;/li&gt;
  6866. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=559949&quot;&gt;Julian Descottes [:jdescottes]&lt;/a&gt; fixed an issue that would crash DevTools (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979448&quot;&gt;#1979448&lt;/a&gt;)&lt;/li&gt;
  6867. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=559949&quot;&gt;Julian Descottes [:jdescottes]&lt;/a&gt; improved performance of a regexp we use to check if a given network request is local (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983755&quot;&gt;#1983755&lt;/a&gt;)&lt;/li&gt;
  6868. &lt;/ul&gt;
  6869. &lt;h4&gt;WebDriver BiDi&lt;/h4&gt;
  6870. &lt;ul&gt;
  6871. &lt;li&gt;Sasha updated &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983807&quot;&gt;“emulation.setLocaleOverride” and “emulation.setTimezoneOverride” commands to also apply overrides to the existing sandboxes created with WebDriver BiDi&lt;/a&gt;.&lt;/li&gt;
  6872. &lt;li&gt;Sasha implemented the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1974167&quot;&gt;“emulation.setScreenOrientationOverride” command&lt;/a&gt;, which allows clients to override screen orientation per browsing or user contexts.&lt;/li&gt;
  6873. &lt;li&gt;Henrik &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986238&quot;&gt;reverted the scrollIntoView algorithm for elements in Marionette&lt;/a&gt; to always use the instant scroll behavior. This undoes the change introduced in Firefox 97, which had switched the behavior to auto. The reversion addresses potential race conditions when scrolling elements that use smooth behavior.&lt;/li&gt;
  6874. &lt;li&gt;Julian updated the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1914407&quot;&gt;”browsingContext.navigate” to succeed and stop throwing errors if the navigation was interrupted&lt;/a&gt; by another navigation. Typically this could happen with a script updating “window.location”.&lt;/li&gt;
  6875. &lt;/ul&gt;
  6876. &lt;h4&gt;Lint, Docs and Workflow&lt;/h4&gt;
  6877. &lt;ul&gt;
  6878. &lt;li&gt;mlucks &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982463&quot;&gt;turned on&lt;/a&gt; the ESLint Lit rule, &lt;a href=&quot;https://github.com/43081j/eslint-plugin-lit/blob/master/docs/rules/no-value-attribute.md&quot;&gt;no-value-attribute&lt;/a&gt;.&lt;/li&gt;
  6879. &lt;li&gt;Standard8 &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985946&quot;&gt;fixed&lt;/a&gt; verbose logging for mach lint.&lt;/li&gt;
  6880. &lt;/ul&gt;
  6881. &lt;h4&gt;Profile Management&lt;/h4&gt;
  6882. &lt;ul&gt;
  6883. &lt;li&gt;We have been &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1WONCxwmd17l3iF2ZCxkDSnaAaIZf-rl8CGoIHBYkDSo/edit?gid=600962034#gid=600962034&quot;&gt;incrementally rolling out&lt;/a&gt;, currently at 5.5%, and profiles &lt;a href=&quot;https://sql.telemetry.mozilla.org/dashboard/firefox-profiles-overview&quot;&gt;telemetry data&lt;/a&gt; looks good.&lt;/li&gt;
  6884. &lt;li&gt;OMC and Nimbus completed migration to the multi-profile datastore, their integration testing and telemetry data also looks healthy.&lt;/li&gt;
  6885. &lt;li&gt;We are planning for a full rollout in 144 (excluding win 10 users until we have backup support for multiple profiles)&lt;/li&gt;
  6886. &lt;li&gt;Closed bugs:
  6887. &lt;ul&gt;
  6888. &lt;li&gt;Contributor fix! 🎉 Alexander Kuleshov fixed bug 1987225, Remove unused gRestartMode variable.&lt;/li&gt;
  6889. &lt;/ul&gt;
  6890. &lt;/li&gt;
  6891. &lt;li&gt;Other bugs closed out:
  6892. &lt;ul&gt;
  6893. &lt;li&gt;1950741     When a non-system theme is selected in about:newprofile, overscrolling the page displays a different page background in the overscrolled area     &lt;a href=&quot;mailto:mlucks@mozilla.com&quot;&gt;mlucks@mozilla.com&lt;/a&gt;&lt;/li&gt;
  6894. &lt;li&gt;1950743     Tabbing to the “Explore more themes” link in about:newprofile makes the link’s focus ring span the entire container instead of just the link     &lt;a href=&quot;mailto:squiles@mozilla.com&quot;&gt;squiles@mozilla.com&lt;/a&gt;&lt;/li&gt;
  6895. &lt;li&gt;1966284     hide new profile manager pages (new, edit, delete) from about:about     &lt;a href=&quot;mailto:mlucks@mozilla.com&quot;&gt;mlucks@mozilla.com&lt;/a&gt;&lt;/li&gt;
  6896. &lt;li&gt;1979898     Remove some of the extraneous directories added when using MOZ_APP_DATA     &lt;a href=&quot;mailto:dtownsend@mozilla.com&quot;&gt;dtownsend@mozilla.com&lt;/a&gt;&lt;/li&gt;
  6897. &lt;li&gt;1984193     Add hover tooltips to avatar picker     &lt;a href=&quot;mailto:mlucks@mozilla.com&quot;&gt;mlucks@mozilla.com&lt;/a&gt;&lt;/li&gt;
  6898. &lt;li&gt;1985340     Update Profiles avatars’ alt text to match tooltip text     &lt;a href=&quot;mailto:mlucks@mozilla.com&quot;&gt;mlucks@mozilla.com&lt;/a&gt;&lt;/li&gt;
  6899. &lt;li&gt;1986080     Update Profiles avatars’ aria label text to match tooltip text     &lt;a href=&quot;mailto:mlucks@mozilla.com&quot;&gt;mlucks@mozilla.com&lt;/a&gt;&lt;/li&gt;
  6900. &lt;/ul&gt;
  6901. &lt;/li&gt;
  6902. &lt;/ul&gt;
  6903. &lt;h4&gt;Search and Navigation&lt;/h4&gt;
  6904. &lt;ul&gt;
  6905. &lt;li&gt;adw is continuing to work on Google Lens which is a feature that allows users to search images by using the context menu (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1987045&quot;&gt;1987045&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986301&quot;&gt;1986301&lt;/a&gt;)&lt;/li&gt;
  6906. &lt;li&gt;Standard8 has been working on an experiment to send Search Suggestions over Oblivious HTTP for privacy (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984624&quot;&gt;1984624&lt;/a&gt;)&lt;/li&gt;
  6907. &lt;li&gt;Standard8 converted the urlbar code to use &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1966464&quot;&gt;moz-src URIs&lt;/a&gt;.&lt;/li&gt;
  6908. &lt;li&gt;Mandy has been working on adding localized trending URL results for Perplexity which is still hidden behind an experiment. (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985515&quot;&gt;1985515&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984201&quot;&gt;1984201&lt;/a&gt;)&lt;/li&gt;
  6909. &lt;li&gt;Dao is working on making the address bar more modular for other features to use. For example, there’s been work done to prepare the search bar.  (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985734&quot;&gt;1985734&lt;/a&gt;,  &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985833&quot;&gt;1985833&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986128&quot;&gt;1986128&lt;/a&gt;,&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986129&quot;&gt;1986129&lt;/a&gt;)&lt;/li&gt;
  6910. &lt;li&gt;Mortiz and adw continue to work on displaying relevant dates for suggest (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986685&quot;&gt;1986685&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986786&quot;&gt;1986786&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1981490&quot;&gt;1981490&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986680&quot;&gt;1986680&lt;/a&gt;,&lt;/li&gt;
  6911. &lt;li&gt;Daisuke is working on yelp online suggestions (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986224&quot;&gt;1986224&lt;/a&gt;)&lt;/li&gt;
  6912. &lt;li&gt;Dale is working on the unified trust panel which will inform users if the site is secure. This is a new design that combines the privacy shield and page information icons and dialogs. (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1976108&quot;&gt;1976108&lt;/a&gt;)&lt;/li&gt;
  6913. &lt;/ul&gt;
  6914. &lt;h4&gt;Storybook/Reusable Components/Acorn Design System&lt;/h4&gt;
  6915. &lt;ul&gt;
  6916. &lt;li&gt;Some new docs related to Figma Code Connect on &lt;a href=&quot;https://firefoxux.github.io/firefox-desktop-components/?path=/docs/docs-figma-code-connect--docs#how-to-find-the-code-connect-snippet&quot;&gt;Storybook&lt;/a&gt;
  6917. &lt;ul&gt;
  6918. &lt;li&gt;Mostly about adding new Code Connects but that section goes over the usage in Figma Dev Mode&lt;/li&gt;
  6919. &lt;/ul&gt;
  6920. &lt;/li&gt;
  6921. &lt;li&gt;More border-radius tokens filled out and are in the tokens table on &lt;a href=&quot;https://firefoxux.github.io/firefox-desktop-components/?path=/story/docs-tokens-table--default&quot;&gt;Storybook&lt;/a&gt;&lt;/li&gt;
  6922. &lt;li&gt;Moz-promo now avoids wrapping actions until necessary (prefers being one line) &lt;a href=&quot;https://firefoxux.github.io/firefox-desktop-components/?path=/story/ui-widgets-promo--slotted-action&quot;&gt;Storybook&lt;/a&gt; (&lt;a href=&quot;https://firefoxux.github.io/firefox-desktop-components/?path=/story/ui-widgets-promo--slotted-action&amp;amp;args=width:300&quot;&gt;narrow example&lt;/a&gt;)&lt;/li&gt;
  6923. &lt;li&gt;MozLitElements that use the automatic fluent data-l10n-attrs population (setting fluent: true in the property definition) can now have additional per-instance data-l10n-attrs (this attribute is now added to, rather than being replaced) &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1987682&quot;&gt;Bug 1987682&lt;/a&gt;
  6924. &lt;ul&gt;
  6925. &lt;li&gt;This could be useful especially for moz-button accesskey which is not currently a fluent attribute due to &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1945032&quot;&gt;Bug 1945032&lt;/a&gt; (if you have a hidden HTML element with an accesskey it will still fire, gonna stop doing that in chrome documents since that’s how XUL worked)&lt;/li&gt;
  6926. &lt;/ul&gt;
  6927. &lt;/li&gt;
  6928. &lt;/ul&gt;
  6929. &lt;h4&gt;Tab Groups&lt;/h4&gt;
  6930. &lt;ul&gt;
  6931. &lt;li&gt;dwalker polished the “active tab in a collapsed group” feature (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979067&quot;&gt;1979067&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1971388&quot;&gt;1971388&lt;/a&gt;)&lt;/li&gt;
  6932. &lt;li&gt;jswinarton polishing the collapsed tab group hover preview panel (1981197, 1971235, 1981201, 1983054)
  6933. &lt;ul&gt;
  6934. &lt;li&gt;Now in Nightly, likely release in Firefox 145&lt;/li&gt;
  6935. &lt;/ul&gt;
  6936. &lt;/li&gt;
  6937. &lt;li&gt;Enormous shout-out to contributor Merci chao for 17 tab group bugs filed in the last month! All of them are written well, actionable, and sometimes even include fixes&lt;/li&gt;
  6938. &lt;/ul&gt;</description>
  6939. <pubDate>Mon, 22 Sep 2025 10:18:52 +0000</pubDate>
  6940. <dc:creator>Anna Kulyk</dc:creator>
  6941. </item>
  6942. <item>
  6943. <title>Mozilla Addons Blog: Now you can roll back to a previous version of your extension</title>
  6944. <guid isPermaLink="false">https://blog.mozilla.org/addons/?p=9260</guid>
  6945. <link>https://blog.mozilla.org/addons/2025/09/19/now-you-can-roll-back-to-a-previous-version-of-your-extension/</link>
  6946. <description>&lt;p&gt;&lt;img alt=&quot;Firefox logo&quot; class=&quot;alignleft size-medium wp-image-8750&quot; height=&quot;252&quot; src=&quot;https://blog.mozilla.org/addons/files/2019/10/Fx-Browser-icon-fullColor-252x252.png&quot; width=&quot;252&quot; /&gt;In response to feedback we’ve heard from the community, AMO (&lt;a href=&quot;http://addons.mozilla.org&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;addons.mozilla.org&lt;/a&gt;) just introduced a new feature allowing developers the ability to quickly roll back to a previously approved extension version. The most common need for roll-back ability are occasions when developers may release a new version they later discover has critical bugs. Now in such cases, instead of needing to make fast fixes and quickly submit an even newer version, which could be further delayed during a review process, developers are free to revert back to a previously approved version.&lt;/p&gt;
  6947. &lt;p&gt;For users who may have already installed the buggy version that’s later pulled, the extension will update to the roll-back version when Firefox checks for the next update (which occurs every 24 hours by default, save for users who’ve turned off automatic updates from the Add-ons Manager).&lt;/p&gt;
  6948. &lt;p&gt;To learn more about the new roll-back feature, please visit &lt;a href=&quot;https://extensionworkshop.allizom.org/documentation/publish/version-rollback/&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;Extension Workshop&lt;/a&gt;.&lt;/p&gt;
  6949. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/addons/2025/09/19/now-you-can-roll-back-to-a-previous-version-of-your-extension/&quot;&gt;Now you can roll back to a previous version of your extension&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/addons&quot;&gt;Mozilla Add-ons Community Blog&lt;/a&gt;.&lt;/p&gt;</description>
  6950. <pubDate>Fri, 19 Sep 2025 17:18:36 +0000</pubDate>
  6951. <dc:creator>Scott DeVaney</dc:creator>
  6952. </item>
  6953. <item>
  6954. <title>Firefox Nightly: Add-ons, Fixes, and DevTools Snacks – These Weeks in Firefox: Issue 188</title>
  6955. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1885</guid>
  6956. <link>https://blog.nightly.mozilla.org/2025/09/19/add-ons-fixes-and-devtools-snacks-these-weeks-in-firefox-issue-188/</link>
  6957. <description>&lt;h3&gt;Highlights&lt;/h3&gt;
  6958. &lt;ul&gt;
  6959. &lt;li&gt;The Timer and TODO List widget are now available to be enabled in Firefox Labs on Nightly and Beta:&lt;/li&gt;
  6960. &lt;/ul&gt;
  6961. &lt;p&gt;&lt;img alt=&quot;Lists and timer on Firefox Home checkbox in Settings&quot; class=&quot;alignnone size-large wp-image-1887&quot; height=&quot;129&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/09/headlines188_2-600x129.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  6962. &lt;ul&gt;
  6963. &lt;li&gt;Firefox Desktop about:addons add-on card view has been updated to list API, host and data collection permissions as separate permission lists – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1956493&quot;&gt;Bug 1956493&lt;/a&gt;&lt;/li&gt;
  6964. &lt;li&gt;Firefox Suggest:
  6965. &lt;ul&gt;
  6966. &lt;li&gt;Moritz has been working on the important dates feature, which highlights country-specific holidays. This is now enabled by default in Firefox 143beta (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985394&quot;&gt;1985394&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982011&quot;&gt;1982011&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983077&quot;&gt;1983077&lt;/a&gt;)&lt;/li&gt;
  6967. &lt;/ul&gt;
  6968. &lt;/li&gt;
  6969. &lt;/ul&gt;
  6970. &lt;h3&gt;Friends of the Firefox team&lt;/h3&gt;
  6971. &lt;h4&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20(excluding%20employees)&amp;amp;quicksearch=1892101%2C1969417%2C1979919%2C1689380%2C1982968%2C1984296%2C1982767%2C1981384%2C1984788%2C1813675%2C1583902%2C1956493%2C1984661%2C1679997%2C1787457%2C1984872&quot;&gt;Resolved bugs (excluding employees)&lt;/a&gt;&lt;/h4&gt;
  6972. &lt;h4&gt;Volunteers that fixed more than one bug&lt;/h4&gt;
  6973. &lt;ul&gt;
  6974. &lt;li&gt;Artem Manushenkov&lt;/li&gt;
  6975. &lt;li&gt;Christina&lt;/li&gt;
  6976. &lt;/ul&gt;
  6977. &lt;h4&gt;New contributors (🌟 = first patch)&lt;/h4&gt;
  6978. &lt;ul&gt;
  6979. &lt;li&gt;Christina &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1679997&quot;&gt;added support&lt;/a&gt; for specifying the cssOrigin (author, user) when injecting CSS via the WebExtension browser.contentScripts.register method&lt;/li&gt;
  6980. &lt;li&gt;Christina &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1956493&quot;&gt;also updated about:addons&lt;/a&gt; to include “permissions and data” for each addon&lt;/li&gt;
  6981. &lt;li&gt;🌟Sujal Singh[:sujaldev] &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984872&quot;&gt;fixed a visual glitch when showing the “unsigned extension” warning&lt;/a&gt; in about:addons&lt;/li&gt;
  6982. &lt;li&gt;chase.philpot &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1689380&quot;&gt;fixed a glitch where AddonManager logging&lt;/a&gt; would claim that a download had completed when it had actually failed&lt;/li&gt;
  6983. &lt;/ul&gt;
  6984. &lt;h3&gt;Project Updates&lt;/h3&gt;
  6985. &lt;h4&gt;Add-ons / Web Extensions&lt;/h4&gt;
  6986. &lt;h5&gt;Addon Manager &amp;amp; about:addons&lt;/h5&gt;
  6987. &lt;ul&gt;
  6988. &lt;li&gt;Fixed missing margin between add-on card warning messagebar and expanded add-on card header – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984872&quot;&gt;Bug 1984872&lt;/a&gt;
  6989. &lt;ul&gt;
  6990. &lt;li&gt;Thanks to sujaldev contributing this fix to the add-on card messagebars 🎉&lt;/li&gt;
  6991. &lt;/ul&gt;
  6992. &lt;/li&gt;
  6993. &lt;/ul&gt;
  6994. &lt;h5&gt;WebExtension APIs&lt;/h5&gt;
  6995. &lt;ul&gt;
  6996. &lt;li&gt;Added support for cssOrigin option to the scripting API and content_scripts manifest.json property – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1679997&quot;&gt;Bug 1679997&lt;/a&gt;&lt;/li&gt;
  6997. &lt;/ul&gt;
  6998. &lt;h4&gt;DevTools&lt;/h4&gt;
  6999. &lt;ul&gt;
  7000. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1278517&quot;&gt;Bug 1278517 – Jump to CSS variable definition in the CSS rule-view&lt;/a&gt;&lt;/li&gt;
  7001. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1972771&quot;&gt;Bug 1972771 – Adding a new panel for AntiTracking debugger behind a pref&lt;/a&gt;&lt;/li&gt;
  7002. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1897765&quot;&gt;Bug 1897765 – Network requests in background tabs where devtools is open jank the parent process main thread&lt;/a&gt;&lt;/li&gt;
  7003. &lt;/ul&gt;
  7004. &lt;h4&gt;WebDriver BiDi&lt;/h4&gt;
  7005. &lt;ul&gt;
  7006. &lt;li&gt;Henrik &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1965465&quot;&gt;cleaned up the test expectations for multiple-status outcomes in all existing WebDriver tests&lt;/a&gt; under web-platform-tests. These statuses, typically added by wpt-sync when tests fail in CI, led to inaccurate reporting. Over the past six months, 106 test files on macOS, 39 on Linux, and 51 on Android stopped producing meaningful results due to entries like [OK, TIMEOUT].&lt;/li&gt;
  7007. &lt;/ul&gt;
  7008. &lt;p&gt;Similar cleanups should be performed for other components to avoid losing test coverage. Alternatively, &lt;a href=&quot;https://github.com/mozilla/wpt-sync/blob/master/sync_prod.ini#L102-L103&quot;&gt;enable syncbot notifications&lt;/a&gt; for your component (opt-in) to automatically get bugs filed, which helps to keep accurate metadata under control.&lt;/p&gt;
  7009. &lt;ul&gt;
  7010. &lt;li&gt;Julian fixed a &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983414&quot;&gt;bug with the network.addDataCollector command which could lead to errors&lt;/a&gt; when receiving certain requests (for instance data: URIs or cached stylesheets)&lt;/li&gt;
  7011. &lt;li&gt;Julian &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1874365&quot;&gt;implemented a new event browsingContext.downloadWillBegin&lt;/a&gt;, which is emitted when a download starts. The event is currently only supported on Firefox desktop, support for Android will be added later.&lt;/li&gt;
  7012. &lt;li&gt;Sasha added &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1976493&quot;&gt;a platform API to set timezone override&lt;/a&gt; and &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1978027&quot;&gt;“emulation.setTimezoneOverride” WebDriver BiDi command&lt;/a&gt;, which utilizes this API.&lt;/li&gt;
  7013. &lt;li&gt;Sasha fixed the bug when &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980211&quot;&gt;locale override was sometimes shared between browsing contexts&lt;/a&gt;. That was happening because the override was shared inside the process. With this fix, the locale override is attached to the realm, so it stays isolated in a browsing context.&lt;/li&gt;
  7014. &lt;/ul&gt;
  7015. &lt;h4&gt;Lint, Docs and Workflow&lt;/h4&gt;
  7016. &lt;ul&gt;
  7017. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1944290&quot;&gt;Updated ESLint to the latest v9.x version&lt;/a&gt; (from 9.6.0).
  7018. &lt;ul&gt;
  7019. &lt;li&gt;You may need to run ./mach eslint –setup and restart your editor if you haven’t already triggered the updates (e.g. &lt;a href=&quot;https://firefox-source-docs.mozilla.org/code-quality/lint/usage.html#vcs-integrations&quot;&gt;via the hooks&lt;/a&gt;).&lt;/li&gt;
  7020. &lt;li&gt;Standard8 also &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1395426&quot;&gt;fixed a long standing issue&lt;/a&gt; which was blocking the upgrade, where using /* import-globals-from … */ in a cyclic dependency way could cause problems for correctly detecting the globals.&lt;/li&gt;
  7021. &lt;li&gt;Also &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985519&quot;&gt;updated&lt;/a&gt; the other ESLint related modules to their latest versions.&lt;/li&gt;
  7022. &lt;li&gt;Import attributes&lt;/li&gt;
  7023. &lt;/ul&gt;
  7024. &lt;/li&gt;
  7025. &lt;li&gt;Stylelint is now covered under the &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983638&quot;&gt;node-licenses checker&lt;/a&gt;.&lt;/li&gt;
  7026. &lt;li&gt;Jon has started rolling out a new Stylelint rule to &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979115&quot;&gt;enforce using border-radius tokens&lt;/a&gt;.&lt;/li&gt;
  7027. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1945456&quot;&gt;TypeScript&lt;/a&gt;
  7028. &lt;ul&gt;
  7029. &lt;li&gt;As part of the work for getting TypeScript ready for production, the TypeScript node_modules install has now been &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1975509&quot;&gt;moved to the top-level of firefox-main&lt;/a&gt;.&lt;/li&gt;
  7030. &lt;li&gt;We’re experimenting with adding a &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1986283&quot;&gt;tier-3 linter for TypeScript&lt;/a&gt;.
  7031. &lt;ul&gt;
  7032. &lt;li&gt;The main aim here is to start getting feedback on how regressions in TypeScript appear on the reviewbot, and to reduce the likelihood of new issues being introduced on some of the components that we’ve already enabled TypeScript on and which have no outstanding issues currently.&lt;/li&gt;
  7033. &lt;li&gt;This is intentionally scope limited to avoid impacting developers whilst we’re still in the set-up phase. Hence, this will report new issues against only a few components:
  7034. &lt;ul&gt;
  7035. &lt;li&gt;{browser,toolkit}/components/search&lt;/li&gt;
  7036. &lt;li&gt;browser/components/urlbar&lt;/li&gt;
  7037. &lt;/ul&gt;
  7038. &lt;/li&gt;
  7039. &lt;li&gt;As this is Tier 3, it won’t show on CI by default, however, failures will show on reviewbot.&lt;/li&gt;
  7040. &lt;/ul&gt;
  7041. &lt;/li&gt;
  7042. &lt;li&gt;There’s still a lot of work to do to get type generation set-up, documentation, and other issues fixed.&lt;/li&gt;
  7043. &lt;/ul&gt;
  7044. &lt;/li&gt;
  7045. &lt;/ul&gt;
  7046. &lt;h4&gt;New Tab Page&lt;/h4&gt;
  7047. &lt;ul&gt;
  7048. &lt;li&gt;The new Sections UI was enabled by default for users in the US last week! We’ll be rolling it out to more regions in the coming weeks and months.&lt;/li&gt;
  7049. &lt;/ul&gt;
  7050. &lt;p&gt;&lt;img alt=&quot;The new Sections UI of the New Tab&quot; class=&quot;alignnone size-large wp-image-1886&quot; height=&quot;291&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/09/headlines188_1-600x291.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  7051. &lt;ul&gt;
  7052. &lt;li&gt;Our release channel train-hop experiment has concluded, and we passed our checks! We’re now cleared to start doing these train-hops! (presuming a green light from Release Management and QA, of course)
  7053. &lt;ul&gt;
  7054. &lt;li&gt;Special thanks to everybody who helped with this! &lt;a href=&quot;mailto:pdahiya@mozilla.com&quot;&gt;&lt;span&gt;Punam Dahiya&lt;/span&gt;&lt;/a&gt;, &lt;a href=&quot;mailto:lgreco@mozilla.com&quot;&gt;&lt;span&gt;Luca Greco&lt;/span&gt;&lt;/a&gt;, &lt;a href=&quot;mailto:wdurand@mozilla.com&quot;&gt;&lt;span&gt;William Durand&lt;/span&gt;&lt;/a&gt;, &lt;a href=&quot;mailto:amarchesini@mozilla.com&quot;&gt;&lt;span&gt;Andrea Marchesini&lt;/span&gt;&lt;/a&gt;, &lt;a href=&quot;mailto:dmeehan@mozilla.com&quot;&gt;&lt;span&gt;Donal Meehan&lt;/span&gt;&lt;/a&gt;, &lt;a href=&quot;mailto:ahalberstadt@mozilla.com&quot;&gt;&lt;span&gt;Andrew Halberstadt&lt;/span&gt;&lt;/a&gt;, &lt;a href=&quot;mailto:joelm@mozilla.com&quot;&gt;&lt;span&gt;Joel Maher&lt;/span&gt;&lt;/a&gt;, &lt;a href=&quot;mailto:beth@mozilla.com&quot;&gt;&lt;span&gt;Beth Rennie&lt;/span&gt;&lt;/a&gt;, and anybody who reviewed any of our patches or helped us out in the past few months on this project.&lt;/li&gt;
  7055. &lt;/ul&gt;
  7056. &lt;/li&gt;
  7057. &lt;/ul&gt;
  7058. &lt;h4&gt;Search and Navigation&lt;/h4&gt;
  7059. &lt;ul&gt;
  7060. &lt;li&gt;Search
  7061. &lt;ul&gt;
  7062. &lt;li&gt;Drew fixed a bug where Google Lens searches were returning invalid results when searching from an already-searched image (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985563&quot;&gt;1985563&lt;/a&gt;)&lt;/li&gt;
  7063. &lt;/ul&gt;
  7064. &lt;/li&gt;
  7065. &lt;/ul&gt;
  7066. &lt;ul&gt;
  7067. &lt;li&gt;&lt;/li&gt;
  7068. &lt;/ul&gt;
  7069. &lt;ul&gt;
  7070. &lt;li&gt;Urlbar
  7071. &lt;ul&gt;
  7072. &lt;li&gt;Dao continued his work on the new searchbar implementation, including fixing some layout issues (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1975010&quot;&gt;1975010&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1975011&quot;&gt;1975011&lt;/a&gt;)&lt;/li&gt;
  7073. &lt;li&gt;Moritz landed a series of patches to improve provider concurrency in the urlbar (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1628016&quot;&gt;1628016&lt;/a&gt;)&lt;/li&gt;
  7074. &lt;/ul&gt;
  7075. &lt;/li&gt;
  7076. &lt;/ul&gt;
  7077. &lt;ul&gt;
  7078. &lt;li&gt;&lt;/li&gt;
  7079. &lt;/ul&gt;
  7080. &lt;ul&gt;
  7081. &lt;li&gt;&lt;/li&gt;
  7082. &lt;li&gt;Firefox Suggest
  7083. &lt;ul&gt;
  7084. &lt;li&gt;
  7085. &lt;ul&gt;
  7086. &lt;li&gt;Drew and Daisuke landed many improvements and bug fixes for the new market-related suggestions (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985916&quot;&gt;1985916&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985293&quot;&gt;1985293&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984501&quot;&gt;1984501&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982026&quot;&gt;1982026&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985260&quot;&gt;1985260&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1985287&quot;&gt;1985287&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982024&quot;&gt;1982024&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982034&quot;&gt;1982034&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982375&quot;&gt;1982375&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982535&quot;&gt;1982535&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1981770&quot;&gt;1981770&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982319&quot;&gt;1982319&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982030&quot;&gt;1982030&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982565&quot;&gt;1982565&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982836&quot;&gt;1982836&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983377&quot;&gt;1983377&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983027&quot;&gt;1983027&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982603&quot;&gt;1982603&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982031&quot;&gt;1982031&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984262&quot;&gt;1984262&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984214&quot;&gt;1984214&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1983984&quot;&gt;1983984&lt;/a&gt;)&lt;/li&gt;
  7087. &lt;/ul&gt;
  7088. &lt;/li&gt;
  7089. &lt;/ul&gt;
  7090. &lt;/li&gt;
  7091. &lt;/ul&gt;
  7092. &lt;ul&gt;
  7093. &lt;li&gt;Places Database
  7094. &lt;ul&gt;
  7095. &lt;li&gt;Marco landed a patch that replaces fixed frecency algorithm thresholds with a function that calculates those thresholds dynamically instead (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1982059&quot;&gt;1982059&lt;/a&gt;)&lt;/li&gt;
  7096. &lt;li&gt;Marco also fixed two bugs stemming from crashes related to the Favicons service (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980992&quot;&gt;1980992&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1984088&quot;&gt;1984088&lt;/a&gt;)&lt;/li&gt;
  7097. &lt;/ul&gt;
  7098. &lt;/li&gt;
  7099. &lt;/ul&gt;
  7100. &lt;ul&gt;
  7101. &lt;li&gt;&lt;/li&gt;
  7102. &lt;/ul&gt;
  7103. &lt;ul&gt;
  7104. &lt;li&gt;&lt;/li&gt;
  7105. &lt;/ul&gt;
  7106. &lt;ul&gt;
  7107. &lt;li&gt;
  7108. &lt;ul&gt;
  7109. &lt;li&gt;&lt;/li&gt;
  7110. &lt;/ul&gt;
  7111. &lt;/li&gt;
  7112. &lt;/ul&gt;</description>
  7113. <pubDate>Fri, 19 Sep 2025 16:56:58 +0000</pubDate>
  7114. <dc:creator>Anna Kulyk</dc:creator>
  7115. </item>
  7116. <item>
  7117. <title>The Rust Programming Language Blog: Announcing Rust 1.90.0</title>
  7118. <guid isPermaLink="true">https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/</guid>
  7119. <link>https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/</link>
  7120. <description>&lt;p&gt;The Rust team is happy to announce a new version of Rust, 1.90.0. Rust is a programming language empowering everyone to build reliable and efficient software.&lt;/p&gt;
  7121. &lt;p&gt;If you have a previous version of Rust installed via &lt;code&gt;rustup&lt;/code&gt;, you can get 1.90.0 with:&lt;/p&gt;
  7122. &lt;pre class=&quot;language-console z-code&quot;&gt;&lt;code class=&quot;language-console&quot;&gt;&lt;span class=&quot;z-text z-plain&quot;&gt;$ rustup update stable
  7123. &lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
  7124. &lt;p&gt;If you don't have it already, you can &lt;a href=&quot;https://www.rust-lang.org/install.html&quot;&gt;get &lt;code&gt;rustup&lt;/code&gt;&lt;/a&gt; from the appropriate page on our website, and check out the &lt;a href=&quot;https://doc.rust-lang.org/stable/releases.html#version-1900-2025-09-18&quot;&gt;detailed release notes for 1.90.0&lt;/a&gt;.&lt;/p&gt;
  7125. &lt;p&gt;If you'd like to help us out by testing future releases, you might consider updating locally to use the beta channel (&lt;code&gt;rustup default beta&lt;/code&gt;) or the nightly channel (&lt;code&gt;rustup default nightly&lt;/code&gt;). Please &lt;a href=&quot;https://github.com/rust-lang/rust/issues/new/choose&quot;&gt;report&lt;/a&gt; any bugs you might come across!&lt;/p&gt;
  7126. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/#what-s-in-1-90-0-stable&quot;&gt;&lt;/a&gt;
  7127. What's in 1.90.0 stable&lt;/h4&gt;
  7128. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/#lld-is-now-the-default-linker-on-x86-64-unknown-linux-gnu&quot;&gt;&lt;/a&gt;
  7129. LLD is now the default linker on &lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt;&lt;/h3&gt;
  7130. &lt;p&gt;The &lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt; target will now use the LLD linker for linking Rust crates by default. This should result in improved linking performance vs the default Linux linker (BFD), particularly for large binaries, binaries with a lot of debug information, and for incremental rebuilds.&lt;/p&gt;
  7131. &lt;p&gt;In the vast majority of cases, LLD should be backwards compatible with BFD, and you should not see any difference other than reduced compilation time. However, if you do run into any new linker issues, you can always opt out using the &lt;code&gt;-C linker-features=-lld&lt;/code&gt; compiler flag. Either by adding it to the usual &lt;code&gt;RUSTFLAGS&lt;/code&gt; environment variable, or to a project's &lt;a href=&quot;https://doc.rust-lang.org/cargo/reference/config.html&quot;&gt;&lt;code&gt;.cargo/config.toml&lt;/code&gt;&lt;/a&gt; configuration file,
  7132. like so:&lt;/p&gt;
  7133. &lt;pre class=&quot;language-toml z-code&quot;&gt;&lt;code class=&quot;language-toml&quot;&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-table z-begin z-toml&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;z-meta z-tag z-table z-toml&quot;&gt;&lt;span class=&quot;z-entity z-name z-table z-toml&quot;&gt;target&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-table z-toml&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;z-entity z-name z-table z-toml&quot;&gt;x86_64-unknown-linux-gnu&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-definition z-table z-end z-toml&quot;&gt;]&lt;/span&gt;
  7134. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;&lt;span class=&quot;z-meta z-tag z-key z-toml&quot;&gt;&lt;span class=&quot;z-entity z-name z-tag z-toml&quot;&gt;rustflags&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;z-punctuation z-definition z-key-value z-toml&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;z-punctuation z-definition z-array z-begin z-toml&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;z-string z-quoted z-double z-basic z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-string z-begin z-toml&quot;&gt;&quot;&lt;/span&gt;-Clinker-features=-lld&lt;span class=&quot;z-punctuation z-definition z-string z-end z-toml&quot;&gt;&quot;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-definition z-array z-end z-toml&quot;&gt;]&lt;/span&gt;
  7135. &lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
  7136. &lt;p&gt;If you encounter any issues with the LLD linker, please &lt;a href=&quot;https://github.com/rust-lang/rust/issues/new/choose&quot;&gt;let us know&lt;/a&gt;. You can read more about the switch to LLD, some benchmark numbers and the opt out mechanism &lt;a href=&quot;https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
  7137. &lt;h5&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/#cargo-adds-native-support-for-workspace-publishing&quot;&gt;&lt;/a&gt;
  7138. Cargo adds native support for workspace publishing&lt;/h5&gt;
  7139. &lt;p&gt;&lt;code&gt;cargo publish --workspace&lt;/code&gt; is now supported, automatically publishing all of
  7140. the crates in a workspace in the right order (following any dependencies
  7141. between them).&lt;/p&gt;
  7142. &lt;p&gt;This has long been possible with external tooling or manual ordering of
  7143. individual publishes, but this brings the functionality into Cargo itself.&lt;/p&gt;
  7144. &lt;p&gt;Native integration allows Cargo's publish verification to run a build across
  7145. the full set of to-be-published crates &lt;em&gt;as if&lt;/em&gt; they were published, including
  7146. during dry-runs. Note that publishes are still not atomic -- network errors or
  7147. server-side failures can still lead to a partially published workspace.&lt;/p&gt;
  7148. &lt;h5&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/#demoting-x86-64-apple-darwin-to-tier-2-with-host-tools&quot;&gt;&lt;/a&gt;
  7149. Demoting &lt;code&gt;x86_64-apple-darwin&lt;/code&gt; to Tier 2 with host tools&lt;/h5&gt;
  7150. &lt;p&gt;GitHub will soon &lt;a href=&quot;https://github.blog/changelog/2025-07-11-upcoming-changes-to-macos-hosted-runners-macos-latest-migration-and-xcode-support-policy-updates/#macos-13-is-closing-down&quot;&gt;discontinue&lt;/a&gt; providing free macOS x86_64 runners for public repositories. Apple has also announced their &lt;a href=&quot;https://en.wikipedia.org/wiki/Mac_transition_to_Apple_silicon#Timeline&quot;&gt;plans&lt;/a&gt; for discontinuing support for the x86_64 architecture.&lt;/p&gt;
  7151. &lt;p&gt;In accordance with these changes, as of Rust 1.90, we have &lt;a href=&quot;https://github.com/rust-lang/rfcs/pull/3841&quot;&gt;demoted the &lt;code&gt;x86_64-apple-darwin&lt;/code&gt; target&lt;/a&gt; from &lt;a href=&quot;https://doc.rust-lang.org/stable/rustc/platform-support.html#tier-1-with-host-tools&quot;&gt;Tier 1 with host tools&lt;/a&gt; to &lt;a href=&quot;https://doc.rust-lang.org/stable/rustc/platform-support.html#tier-2-with-host-tools&quot;&gt;Tier 2 with host tools&lt;/a&gt;. This means that the target, including tools like &lt;code&gt;rustc&lt;/code&gt; and &lt;code&gt;cargo&lt;/code&gt;, will be guaranteed to build but is not guaranteed to pass our automated test suite.&lt;/p&gt;
  7152. &lt;p&gt;For users, this change will not immediately cause impact. Builds of both the standard library and the compiler will still be distributed by the Rust Project for use via &lt;code&gt;rustup&lt;/code&gt; or alternative installation methods while the target remains at Tier 2. Over time, it's likely that reduced test coverage for this target will cause things to break or fall out of compatibility with no further announcements.&lt;/p&gt;
  7153. &lt;h5&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/#stabilized-apis&quot;&gt;&lt;/a&gt;
  7154. Stabilized APIs&lt;/h5&gt;
  7155. &lt;ul&gt;
  7156. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.usize.html#method.checked_sub_signed&quot;&gt;&lt;code&gt;u{n}::checked_sub_signed&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7157. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.usize.html#method.overflowing_sub_signed&quot;&gt;&lt;code&gt;u{n}::overflowing_sub_signed&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7158. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.usize.html#method.saturating_sub_signed&quot;&gt;&lt;code&gt;u{n}::saturating_sub_signed&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7159. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.usize.html#method.wrapping_sub_signed&quot;&gt;&lt;code&gt;u{n}::wrapping_sub_signed&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7160. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/num/enum.IntErrorKind.html#impl-Copy-for-IntErrorKind&quot;&gt;&lt;code&gt;impl Copy for IntErrorKind&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7161. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/num/enum.IntErrorKind.html#impl-Hash-for-IntErrorKind&quot;&gt;&lt;code&gt;impl Hash for IntErrorKind&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7162. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/ffi/struct.CStr.html#impl-PartialEq%3C%26CStr%3E-for-CStr&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;&amp;amp;CStr&amp;gt; for CStr&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7163. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/ffi/struct.CStr.html#impl-PartialEq%3CCString%3E-for-CStr&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;CString&amp;gt; for CStr&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7164. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/ffi/struct.CStr.html#impl-PartialEq%3CCow%3C'_,+CStr%3E%3E-for-CStr&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;Cow&amp;lt;CStr&amp;gt;&amp;gt; for CStr&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7165. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/ffi/struct.CString.html#impl-PartialEq%3C%26CStr%3E-for-CString&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;&amp;amp;CStr&amp;gt; for CString&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7166. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/ffi/struct.CString.html#impl-PartialEq%3CCStr%3E-for-CString&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;CStr&amp;gt; for CString&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7167. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/ffi/struct.CString.html#impl-PartialEq%3CCow%3C'_,+CStr%3E%3E-for-CString&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;Cow&amp;lt;CStr&amp;gt;&amp;gt; for CString&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7168. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/borrow/enum.Cow.html#impl-PartialEq%3C%26CStr%3E-for-Cow%3C'_,+CStr%3E&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;&amp;amp;CStr&amp;gt; for Cow&amp;lt;CStr&amp;gt;&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7169. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/borrow/enum.Cow.html#impl-PartialEq%3CCStr%3E-for-Cow%3C'_,+CStr%3E&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;CStr&amp;gt; for Cow&amp;lt;CStr&amp;gt;&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7170. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/borrow/enum.Cow.html#impl-PartialEq%3CCString%3E-for-Cow%3C'_,+CStr%3E&quot;&gt;&lt;code&gt;impl PartialEq&amp;lt;CString&amp;gt; for Cow&amp;lt;CStr&amp;gt;&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7171. &lt;/ul&gt;
  7172. &lt;p&gt;These previously stable APIs are now stable in const contexts:&lt;/p&gt;
  7173. &lt;ul&gt;
  7174. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.slice.html#method.reverse&quot;&gt;&lt;code&gt;&amp;lt;[T]&amp;gt;::reverse&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7175. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f32.html#method.floor&quot;&gt;&lt;code&gt;f32::floor&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7176. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f32.html#method.ceil&quot;&gt;&lt;code&gt;f32::ceil&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7177. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f32.html#method.trunc&quot;&gt;&lt;code&gt;f32::trunc&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7178. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f32.html#method.fract&quot;&gt;&lt;code&gt;f32::fract&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7179. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f32.html#method.round&quot;&gt;&lt;code&gt;f32::round&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7180. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f32.html#method.round_ties_even&quot;&gt;&lt;code&gt;f32::round_ties_even&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7181. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f64.html#method.floor&quot;&gt;&lt;code&gt;f64::floor&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7182. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f64.html#method.ceil&quot;&gt;&lt;code&gt;f64::ceil&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7183. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f64.html#method.trunc&quot;&gt;&lt;code&gt;f64::trunc&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7184. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f64.html#method.fract&quot;&gt;&lt;code&gt;f64::fract&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7185. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f64.html#method.round&quot;&gt;&lt;code&gt;f64::round&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7186. &lt;li&gt;&lt;a href=&quot;https://doc.rust-lang.org/stable/std/primitive.f64.html#method.round_ties_even&quot;&gt;&lt;code&gt;f64::round_ties_even&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
  7187. &lt;/ul&gt;
  7188. &lt;h5&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/#platform-support&quot;&gt;&lt;/a&gt;
  7189. Platform Support&lt;/h5&gt;
  7190. &lt;ul&gt;
  7191. &lt;li&gt;&lt;code&gt;x86_64-apple-darwin&lt;/code&gt; is now a tier 2 target&lt;/li&gt;
  7192. &lt;/ul&gt;
  7193. &lt;p&gt;Refer to Rust’s &lt;a href=&quot;https://doc.rust-lang.org/rustc/platform-support.html&quot;&gt;platform support page&lt;/a&gt; for more information on Rust’s tiered platform support.&lt;/p&gt;
  7194. &lt;h5&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/#other-changes&quot;&gt;&lt;/a&gt;
  7195. Other changes&lt;/h5&gt;
  7196. &lt;p&gt;Check out everything that changed in &lt;a href=&quot;https://github.com/rust-lang/rust/releases/tag/1.90.0&quot;&gt;Rust&lt;/a&gt;, &lt;a href=&quot;https://doc.rust-lang.org/nightly/cargo/CHANGELOG.html#cargo-190-2025-09-18&quot;&gt;Cargo&lt;/a&gt;, and &lt;a href=&quot;https://github.com/rust-lang/rust-clippy/blob/master/CHANGELOG.md#rust-190&quot;&gt;Clippy&lt;/a&gt;.&lt;/p&gt;
  7197. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/#contributors-to-1-90-0&quot;&gt;&lt;/a&gt;
  7198. Contributors to 1.90.0&lt;/h4&gt;
  7199. &lt;p&gt;Many people came together to create Rust 1.90.0. We couldn't have done it without all of you. &lt;a href=&quot;https://thanks.rust-lang.org/rust/1.90.0/&quot;&gt;Thanks!&lt;/a&gt;&lt;/p&gt;</description>
  7200. <pubDate>Thu, 18 Sep 2025 00:00:00 +0000</pubDate>
  7201. <dc:creator>The Rust Release Team</dc:creator>
  7202. </item>
  7203. <item>
  7204. <title>The Servo Blog: Your Donations at Work: Funding Josh Matthews' Contributions to Servo</title>
  7205. <guid isPermaLink="true">https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/</guid>
  7206. <link>https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/</link>
  7207. <description>&lt;p&gt;The Servo project is excited to share that long-time maintainer &lt;a href=&quot;https://github.com/jdm&quot;&gt;Josh Matthews (@jdm)&lt;/a&gt; is now working part-time on improving the Servo contributor experience.&lt;/p&gt;
  7208. &lt;p&gt;This is a direct result of the monthly donations to the project through &lt;a href=&quot;https://opencollective.com/servo&quot;&gt;OpenCollective&lt;/a&gt; and &lt;a href=&quot;https://github.com/sponsors/servo&quot;&gt;GitHub&lt;/a&gt;. The generosity of our supporters has allowed us to operate dedicated computing resources for CI purposes, as well as participate in the &lt;a href=&quot;https://www.outreachy.org/&quot;&gt;Outreachy program&lt;/a&gt; as a mentoring organization. We’re excited that we can now financially support developers and allow them to dedicate more time to the Servo project over longer periods.&lt;/p&gt;
  7209. &lt;p&gt;Josh will use this funded time to make it easier for others to contribute to the project. You will see him improving documentation, reviewing pull requests, breaking down large projects into smaller actionable tasks, and generally helping others get unstuck quicker.&lt;/p&gt;
  7210. &lt;p&gt;Here’s Josh in his own words:&lt;/p&gt;
  7211. &lt;h3&gt;Tell us about yourself! &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#tell-us-about-yourself!&quot;&gt;
  7212.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7213.      &lt;/a&gt;&lt;/h3&gt;
  7214. &lt;p&gt;I’ve been working on web browsers since 2009, with a brief diversion into distributed systems and finance for a few years. I’ve been a stay at home dad for several years, though, and Servo is a great way for me to keep that intellectual curiosity. I love helping people accomplish things they haven’t tried before; it’s a very satisfying experience to watch them flourish and grow.&lt;/p&gt;
  7215. &lt;h3&gt;Why did you start contributing to Servo? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#why-did-you-start-contributing-to-servo%3F&quot;&gt;
  7216.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7217.      &lt;/a&gt;&lt;/h3&gt;
  7218. &lt;p&gt;The team I had lined up at Mozilla in 2012 abruptly was cancelled shortly before I started full time. I knew of the existence of the very beginnings of the Servo project, and I was in the unique position of having several years of experience in both working on Firefox and the early Rust compiler. When I suggested that I should help get Servo off the ground, everyone thought that was a good idea.&lt;/p&gt;
  7219. &lt;h3&gt;What was challenging about your first contribution? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#what-was-challenging-about-your-first-contribution%3F&quot;&gt;
  7220.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7221.      &lt;/a&gt;&lt;/h3&gt;
  7222. &lt;p&gt;Brian Anderson (@brson) handed me a program that could parse simple HTML and a tiny bit of CSS and draw solid rectangles into a png. He said “Can you make it run JavaScript?” The amount of details I needed to learn about how a web page’s DOM gets hooked up to a JS engine were intimidating, and the relevant web standards were still quite underdeveloped in 2012. There was a lot of guessing and then going and talking to the experts from the Firefox side of the org.&lt;/p&gt;
  7223. &lt;h3&gt;What do you like about contributing to the project? What do you get out of it? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#what-do-you-like-about-contributing-to-the-project%3F-what-do-you-get-out-of-it%3F&quot;&gt;
  7224.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7225.      &lt;/a&gt;&lt;/h3&gt;
  7226. &lt;p&gt;I love seeing familiar websites becoming more usable. I am fascinated by all the different technologies that make up rendering engines today, and all the ways we discover that websites use them. And I love working in Rust in a large project, especially one that I’m so familiar with. There are a lot of kind, talented, and clever people that contribute to the project that make it a really enjoyable experience for me.&lt;/p&gt;
  7227. &lt;h3&gt;What is currently being worked on in Servo that you’re excited about? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#what-is-currently-being-worked-on-in-servo-that-you%E2%80%99re-excited-about%3F&quot;&gt;
  7228.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7229.      &lt;/a&gt;&lt;/h3&gt;
  7230. &lt;p&gt;The work to get the JavaScript debugger up and running will be a game changer for investigating site compatibility problems. I’m also really pleased to see work happening in the JS bindings layer—ways to reduce the number of string conversions required when going from JS-&amp;gt;Rust-&amp;gt;JS, or make interactions with typed arrays safer and more ergonomic. I love when we make it easier for non-experts to implement missing web APIs.&lt;/p&gt;
  7231. &lt;h3&gt;What would you like to see the Servo community do more of? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#what-would-you-like-to-see-the-servo-community-do-more-of%3F&quot;&gt;
  7232.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7233.      &lt;/a&gt;&lt;/h3&gt;
  7234. &lt;p&gt;I would love to see more experiments with embedding Servo in other projects. The ones I know about, like the verso browser and the cuervo text-mode browser, have been enormously helpful in pointing out use cases that we had missed, or areas of the engine that could be made more modular and configurable. I’d love to get to a place where almost any major component of Servo could be replaced without forking the engine.&lt;/p&gt;
  7235. &lt;h3&gt;Do you have any advice for new developers who are thinking of contributing to the project? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#do-you-have-any-advice-for-new-developers-who-are-thinking-of-contributing-to-the-project%3F&quot;&gt;
  7236.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7237.      &lt;/a&gt;&lt;/h3&gt;
  7238. &lt;p&gt;Choose your favourite web feature and look for it in the engine. Either it’s already implemented and you can use it to understand how some pieces fit together, or you could probably get a skeleton implementation going! Either way, we would love to help you find your way around the codebase. I take pride in the number of PRs we’ve received from people who have never written Rust code before, but their implementation is totally mergeable. I think Servo is the most approachable web rendering engine for new contributors, and I want to keep it that way.&lt;/p&gt;
  7239. &lt;h3&gt;What do you hope to see evolve in Servo over the next 1-2 years? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#what-do-you-hope-to-see-evolve-in-servo-over-the-next-1-2-years%3F&quot;&gt;
  7240.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7241.      &lt;/a&gt;&lt;/h3&gt;
  7242. &lt;p&gt;I would love to see a larger set of maintainers who review code changes, which will be good for maintainers and contributors alike. Similarly, I’d love to see more experienced contributors writing down the details for solving complex issues that only live in their heads right now. That’s how we grow a long-term project contributor base that skills up over time, by modelling that kind of behaviour.&lt;/p&gt;
  7243. &lt;h3&gt;Any final thoughts you’d like to share? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/09/17/your-donations-at-work-funding-jdm/#any-final-thoughts-you%E2%80%99d-like-to-share%3F&quot;&gt;
  7244.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  7245.      &lt;/a&gt;&lt;/h3&gt;
  7246. &lt;p&gt;I’m humbled by how many people contribute to Servo, whether financially, through code, or just Zulip discussions. I think Servo is in a really lucky position, and I hope to continue shepherding it towards a bright future.&lt;/p&gt;</description>
  7247. <pubDate>Wed, 17 Sep 2025 00:00:00 +0000</pubDate>
  7248. </item>
  7249. <item>
  7250. <title>Firefox Developer Experience: Firefox WebDriver Newsletter 143</title>
  7251. <guid isPermaLink="false">https://fxdx.dev/?p=510</guid>
  7252. <link>https://fxdx.dev/firefox-webdriver-newsletter-143/</link>
  7253. <description>&lt;p&gt;&lt;em&gt;WebDriver is a remote control interface that enables introspection and control of user agents.&lt;/em&gt; &lt;em&gt;As such it&lt;/em&gt; &lt;em&gt;can&lt;/em&gt; &lt;em&gt;help developers to verify that their websites are working and performing well with all major browsers. The protocol is standardized by the&lt;/em&gt;&lt;a href=&quot;https://www.w3.org/&quot;&gt;&lt;em&gt; &lt;/em&gt;&lt;em&gt;W3C&lt;/em&gt;&lt;/a&gt;&lt;em&gt; and consists of two separate specifications:&lt;/em&gt;&lt;a href=&quot;https://w3c.github.io/webdriver/&quot;&gt;&lt;em&gt; &lt;/em&gt;&lt;em&gt;WebDriver classic&lt;/em&gt;&lt;/a&gt;&lt;em&gt; (HTTP) and the new&lt;/em&gt;&lt;a href=&quot;https://w3c.github.io/webdriver-bidi/&quot;&gt;&lt;em&gt; &lt;/em&gt;&lt;em&gt;WebDriver BiDi&lt;/em&gt;&lt;/a&gt;&lt;em&gt; &lt;/em&gt;&lt;em&gt;(Bi-Directional).&lt;/em&gt;&lt;/p&gt;
  7254.  
  7255.  
  7256.  
  7257. &lt;p&gt;&lt;em&gt;This newsletter gives an overview of the work we’ve done as part of the Firefox 143 release cycle&lt;/em&gt;.&lt;/p&gt;
  7258.  
  7259.  
  7260.  
  7261. &lt;h3&gt;Contributions&lt;/h3&gt;
  7262.  
  7263.  
  7264.  
  7265. &lt;p&gt;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.&lt;/p&gt;
  7266.  
  7267.  
  7268.  
  7269. &lt;p&gt;In Firefox 143, two contributors managed to land fixes and improvements in our codebase:&lt;/p&gt;
  7270.  
  7271.  
  7272.  
  7273. &lt;ul&gt;
  7274. &lt;li&gt;Liam (ldebeasi) implemented the logic to &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1754273&quot;&gt;emit events for existing contexts&lt;/a&gt; when subscribing to the &lt;code&gt;browsingContext.contextCreated&lt;/code&gt; event.&lt;/li&gt;
  7275.  
  7276.  
  7277.  
  7278. &lt;li&gt;Sabina (sabina.zaripova) &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1972865&quot;&gt;added an internal helper&lt;/a&gt; to make it easier to check our session data.&lt;/li&gt;
  7279. &lt;/ul&gt;
  7280.  
  7281.  
  7282.  
  7283. &lt;p&gt;WebDriver code is written in JavaScript, Python, and Rust so any web developer can contribute! Read&lt;a href=&quot;https://firefox-source-docs.mozilla.org/devtools/getting-started/README.html&quot;&gt; how to setup the work environment&lt;/a&gt; and check&lt;a href=&quot;https://codetribute.mozilla.org/projects/automation&quot;&gt; the list of mentored issues&lt;/a&gt; for Marionette, or the&lt;a href=&quot;https://codetribute.mozilla.org/languages/javascript?project%3DWebDriver%2520BiDi&quot;&gt; list of mentored JavaScript bugs for WebDriver BiDi&lt;/a&gt;. Join&lt;a href=&quot;https://chat.mozilla.org/#/room/#webdriver:mozilla.org&quot;&gt; our chatroom&lt;/a&gt; if you need any help to get started!&lt;br /&gt;&lt;/p&gt;
  7284.  
  7285.  
  7286.  
  7287. &lt;h3&gt;WebDriver BiDi&lt;/h3&gt;
  7288.  
  7289.  
  7290.  
  7291. &lt;h4&gt;Updated: &lt;code&gt;browsingContext.contextCreated&lt;/code&gt; for existing contexts&lt;/h4&gt;
  7292.  
  7293.  
  7294.  
  7295. &lt;p&gt;Updated the &lt;code&gt;browsingContext.contextCreated&lt;/code&gt; event to be &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1754273&quot;&gt;emitted for all open contexts&lt;/a&gt; when subscribing to the event.&lt;/p&gt;
  7296.  
  7297.  
  7298.  
  7299. &lt;h4&gt;New: several commands to record network data&lt;/h4&gt;
  7300.  
  7301.  
  7302.  
  7303. &lt;p&gt;We implemented several new commands for the network module to enable recording network data.&lt;/p&gt;
  7304.  
  7305.  
  7306.  
  7307. &lt;p&gt;&lt;strong&gt;&lt;code&gt;network.addDataCollector&lt;/code&gt;&lt;/strong&gt; &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1971778&quot;&gt;adds a network data collector&lt;/a&gt; to &lt;code&gt;contexts&lt;/code&gt;, &lt;code&gt;userContexts&lt;/code&gt; or globally. The collector will record network data corresponding to the provided &lt;code&gt;dataTypes&lt;/code&gt;. At the moment, only the &lt;code&gt;&quot;response&quot;&lt;/code&gt; data type is supported. A &lt;code&gt;maxEncodedDataSize&lt;/code&gt; must also be provided, network data exceeding this size will not be recorded.&lt;/p&gt;
  7308.  
  7309.  
  7310.  
  7311. &lt;p&gt;&lt;strong&gt;&lt;code&gt;network.removeDataCollector&lt;/code&gt;&lt;/strong&gt; &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1971781&quot;&gt;removes a previously added network data collector&lt;/a&gt;.&lt;/p&gt;
  7312.  
  7313.  
  7314.  
  7315. &lt;p&gt;&lt;strong&gt;&lt;code&gt;network.getData&lt;/code&gt;&lt;/strong&gt; &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1971780&quot;&gt;retrieves the data collected&lt;/a&gt; for a provided &lt;code&gt;request&lt;/code&gt; id, &lt;code&gt;dataType&lt;/code&gt; and optionally &lt;code&gt;collector&lt;/code&gt; id. When providing a &lt;code&gt;collector&lt;/code&gt; id, clients may also pass the &lt;code&gt;disown&lt;/code&gt; flag to release the network data from the collector. Note that data is deleted when it is no longer owned by any collector.&lt;/p&gt;
  7316.  
  7317.  
  7318.  
  7319. &lt;p&gt;&lt;strong&gt;&lt;code&gt;network.disownData&lt;/code&gt;&lt;/strong&gt; &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1971779&quot;&gt;releases the data&lt;/a&gt; for a given &lt;code&gt;request&lt;/code&gt; id and &lt;code&gt;dataType&lt;/code&gt; from the provided &lt;code&gt;collector&lt;/code&gt; id.&lt;/p&gt;
  7320.  
  7321.  
  7322.  
  7323. &lt;h4&gt;Bug fixes:&lt;/h4&gt;
  7324.  
  7325.  
  7326.  
  7327. &lt;ul&gt;
  7328. &lt;li&gt;Fixed a bug where &lt;code&gt;emulation.setLocaleOverride&lt;/code&gt; &lt;a href=&quot;https://bugzil.la/1980137&quot;&gt;did not apply the override to newly created cross-origin iframes&lt;/a&gt;.&lt;/li&gt;
  7329.  
  7330.  
  7331.  
  7332. &lt;li&gt;Fixed a bug where several commands such as &lt;code&gt;session.subscribe&lt;/code&gt; would &lt;a href=&quot;https://bugzil.la/1949037&quot;&gt;fail if any tab was unloaded&lt;/a&gt;.&lt;/li&gt;
  7333.  
  7334.  
  7335.  
  7336. &lt;li&gt;Fixed the &lt;code&gt;browsingContext.navigationCommitted&lt;/code&gt; event so that the &lt;code&gt;url&lt;/code&gt; property &lt;a href=&quot;https://bugzil.la/1980137&quot;&gt;now includes basic auth credentials&lt;/a&gt;.&lt;/li&gt;
  7337. &lt;/ul&gt;</description>
  7338. <pubDate>Tue, 16 Sep 2025 19:00:00 +0000</pubDate>
  7339. <dc:creator>Julian Descottes</dc:creator>
  7340. </item>
  7341. <item>
  7342. <title>Mozilla Future Releases Blog: Raising the Minimum Android Version for Firefox</title>
  7343. <guid isPermaLink="false">https://blog.mozilla.org/futurereleases/?p=2729</guid>
  7344. <link>https://blog.mozilla.org/futurereleases/2025/09/15/raising-the-minimum-android-version-for-firefox/</link>
  7345. <description>&lt;p&gt;Mozilla has always aimed to make Firefox available to as many people as possible, including those on older Android devices. For years, we’ve supported versions of Android going all the way back to 5 (Lollipop), which first launched in 2014. That broad support has helped extend the life of many devices. However, the Android ecosystem is constantly evolving and it has become increasingly difficult for us to find ways to maintain and develop apps on these long-unsupported platforms while also allowing Firefox to take advantage of more modern devices and Android operating systems.&lt;/p&gt;
  7346. &lt;p&gt;Beginning with Firefox 144, &lt;strong&gt;the minimum supported Android version will increase to 8.0 (Oreo)&lt;/strong&gt;, which was released in 2017. At the same time, we will end support for 32-bit x86 Android devices. Usage of these older platforms has become increasingly rare, and continuing to support them has made it harder for us to deliver the best performance and reliability to the vast majority of our users.&lt;/p&gt;
  7347. &lt;p&gt;If your device runs Android 7 or earlier, or if you rely on Firefox for a 32-bit x86 device, Firefox 143 will be the final version available to you. You will still be able to use that version, but it will no longer receive updates once Firefox 144 is released. Please note that 32-bit ARM devices will continue to be supported.&lt;/p&gt;
  7348. &lt;p&gt;These changes apply not only to Firefox for Android but also to Firefox Focus &amp;amp; Klar, our privacy-first browsers. By narrowing our supported platforms, we can take better advantage of modern Android APIs, improve stability and security, and focus our engineering resources where they will have the greatest impact.&lt;/p&gt;
  7349. &lt;p&gt;We know some users will be affected by this transition, and we don’t take that lightly. Our goal remains to balance broad accessibility with the ability to deliver the best possible Firefox experience on modern hardware and operating systems.&lt;/p&gt;
  7350. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/futurereleases/2025/09/15/raising-the-minimum-android-version-for-firefox/&quot;&gt;Raising the Minimum Android Version for Firefox&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/futurereleases&quot;&gt;Future Releases&lt;/a&gt;.&lt;/p&gt;</description>
  7351. <pubDate>Mon, 15 Sep 2025 17:00:36 +0000</pubDate>
  7352. <dc:creator>Ryan VanderMeulen</dc:creator>
  7353. </item>
  7354. <item>
  7355. <title>Mozilla Thunderbird: Mobile Progress Report – July/August 2025</title>
  7356. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3793</guid>
  7357. <link>https://blog.thunderbird.net/2025/09/mobile-progress-report-july-august-2025/</link>
  7358. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/09/blog-banner-mobile-1-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  7359. &lt;p&gt;Hello wonderful community, it has been a while since the &lt;a href=&quot;https://blog.thunderbird.net/2025/07/mobile-progress-report-june-2025/&quot;&gt;last Mobile update&lt;/a&gt;.&lt;/p&gt;
  7360.  
  7361.  
  7362.  
  7363. &lt;p&gt;A lot has happened in the past 2 months, so let’s jump right into a quick overview of current work in progress and primary efforts.&lt;/p&gt;
  7364.  
  7365.  
  7366.  
  7367. &lt;h4&gt;Account Drawer in progress&lt;/h4&gt;
  7368.  
  7369.  
  7370.  
  7371. &lt;p&gt;If you’re rocking the Beta version of Thunderbird for Android, you might have noticed that all your unified folders have disappeared! Don’t panic, that’s just temporary.&lt;/p&gt;
  7372.  
  7373.  
  7374.  
  7375. &lt;p&gt;We’re still churning through the technical debt and the database inconsistencies in order to create through virtual unified folders for all your accounts.&lt;/p&gt;
  7376.  
  7377.  
  7378.  
  7379. &lt;p&gt;The final goal is the same as the one we shared in a previous update, which you can see the final mock-ups here:&lt;/p&gt;
  7380.  
  7381.  
  7382.  
  7383. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/09/Mobile-Update-July_August.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3794&quot; height=&quot;647&quot; src=&quot;https://blog.thunderbird.net/files/2025/09/Mobile-Update-July_August.png&quot; width=&quot;1600&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  7384.  
  7385.  
  7386.  
  7387. &lt;p&gt;Expect more updates in the coming releases.&lt;/p&gt;
  7388.  
  7389.  
  7390.  
  7391. &lt;h3&gt;iOS account setup&lt;/h3&gt;
  7392.  
  7393.  
  7394.  
  7395. &lt;p&gt;The work on the iOS version is moving at full speed!&lt;/p&gt;
  7396.  
  7397.  
  7398.  
  7399. &lt;p&gt;We found ourselves in a bit of a tight spot due to the recent announcements of Apple with their new iOS 26 version, and a somewhat complete redesign of all the SwiftUI and general Human Interface Guidelines.&lt;/p&gt;
  7400.  
  7401.  
  7402.  
  7403. &lt;p&gt;When will iOS 26 be widely available and adopted?&lt;/p&gt;
  7404.  
  7405.  
  7406.  
  7407. &lt;p&gt;Will we have our iOS version of Thunderbird ready before that?&lt;/p&gt;
  7408.  
  7409.  
  7410.  
  7411. &lt;p&gt;If we build it on current iOS 18 design guidelines, how would that look on the new version?&lt;/p&gt;
  7412.  
  7413.  
  7414.  
  7415. &lt;p&gt;Will we need to update everything right after releasing the first version?&lt;/p&gt;
  7416.  
  7417.  
  7418.  
  7419. &lt;p&gt;Due to these uncertainties, we decided to focus only on the new iOS 26 user interface and be compatible with the new version right off the bat.&lt;/p&gt;
  7420.  
  7421.  
  7422.  
  7423. &lt;p&gt;We will need to test and explore carefully how that behaves on iOS 18 and prior, hoping for some available translation layers in order to guarantee compatibility.&lt;/p&gt;
  7424.  
  7425.  
  7426.  
  7427. &lt;p&gt;For now, here’s a sneak peek of the Account Setup flow for iOS!&lt;/p&gt;
  7428.  
  7429.  
  7430.  
  7431. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/09/Mobile-Update-July_August1.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3800&quot; height=&quot;1600&quot; src=&quot;https://blog.thunderbird.net/files/2025/09/Mobile-Update-July_August1.png&quot; width=&quot;1312&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  7432.  
  7433.  
  7434.  
  7435. &lt;h3&gt;Read/Unread status improvements in Android&lt;/h3&gt;
  7436.  
  7437.  
  7438.  
  7439. &lt;p&gt;As we move through an old codebase and we work hard to modernize components and layouts, it is unfortunately inevitable that we accidentally break old features or setups that are familiar to users.&lt;/p&gt;
  7440.  
  7441.  
  7442.  
  7443. &lt;p&gt;We apologize for the inconvenience, especially in this latest highlighted issue which created some discomfort when it comes to the visual distinction between read and unread messages.&lt;/p&gt;
  7444.  
  7445.  
  7446.  
  7447. &lt;p&gt;The old UI offered an option to customize the background color of those states. Even if this solution sounds like a good approach, it created multiple problems related to following system themes, light/dark mode variations, and the overall outdated implementation that needed to be removed.&lt;/p&gt;
  7448.  
  7449.  
  7450.  
  7451. &lt;p&gt;Some users were dissatisfied, and rightly so, due to the less than optimal visual distinction between those states that solely relied on background colors.&lt;/p&gt;
  7452.  
  7453.  
  7454.  
  7455. &lt;p&gt;We already improved the overall visual consistency and distinction in that area, but we’re working towards implementing a much clearer visual representation for each state that doesn’t just rely on background colors.&lt;/p&gt;
  7456.  
  7457.  
  7458.  
  7459. &lt;p&gt;We’re implementing a combination of background and foreground colors, font weight variation, and a visual indicator that specifically represents unread and new messages.&lt;/p&gt;
  7460.  
  7461.  
  7462.  
  7463. &lt;p&gt;This approach will remove any confusion and hopefully completely fix this problem.&lt;/p&gt;
  7464.  
  7465.  
  7466.  
  7467. &lt;p&gt;Thank you all those involved for your feedback and concerns, and for using the Beta version to provide early feedback and test the new updates.&lt;/p&gt;
  7468.  
  7469.  
  7470.  
  7471. &lt;h3&gt;A new release cadence&lt;/h3&gt;
  7472.  
  7473.  
  7474.  
  7475. &lt;p&gt;Starting from September, we’re switching to a faster and more consistent release cadence.&lt;/p&gt;
  7476.  
  7477.  
  7478.  
  7479. &lt;p&gt;The first week of every month we will release a new beta version, for example v13b1, followed by a new incremental beta version with improvements and fixes directly from the main branch, being released every week during that month (eg: v13b2, v13b3, etc).&lt;/p&gt;
  7480.  
  7481.  
  7482.  
  7483. &lt;p&gt;At the end of that month, the current beta, after being deemed reliable and having passed our QA steps, will be promoted as a stable version and at the same time a new beta branch will be released.&lt;/p&gt;
  7484.  
  7485.  
  7486.  
  7487. &lt;p&gt;In summary, starting from September you can expect a new stable version and a new beta cycle every month.&lt;/p&gt;
  7488.  
  7489.  
  7490.  
  7491. &lt;p&gt;Changing our cadence will allow us to expose new and work in progress features more quickly to our beta audience, and shorten the waiting time for users on the stable branch, with smaller and consistent incremental improvements.&lt;/p&gt;
  7492.  
  7493.  
  7494.  
  7495. &lt;p&gt;Cheers,&lt;/p&gt;
  7496.  
  7497.  
  7498.  
  7499. &lt;p&gt;—&lt;/p&gt;
  7500.  
  7501.  
  7502.  
  7503. &lt;p&gt;&lt;strong&gt;Alessandro Castellani&lt;/strong&gt;(he, him)&lt;br /&gt;&lt;strong&gt;Director, Desktop and Mobile Apps&lt;/strong&gt; | Mozilla Thunderbird&lt;/p&gt;
  7504. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/09/mobile-progress-report-july-august-2025/&quot;&gt;Mobile Progress Report – July/August 2025&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  7505. <pubDate>Mon, 15 Sep 2025 15:09:31 +0000</pubDate>
  7506. <dc:creator>Alessandro Castellani</dc:creator>
  7507. </item>
  7508. <item>
  7509. <title>Firefox Nightly: Webcam previews and more! – These Weeks in Firefox: Issue 187</title>
  7510. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1893</guid>
  7511. <link>https://blog.nightly.mozilla.org/2025/09/12/webcam-previews-and-more-these-weeks-in-firefox-issue-187/</link>
  7512. <description>&lt;h3&gt;Highlights&lt;/h3&gt;
  7513. &lt;ul&gt;
  7514. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=557153&quot;&gt;Nicolas Chevobbe&lt;/a&gt; added presentational hints in the Inspector’s rule-view (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1212289&quot;&gt;#1212289&lt;/a&gt;)&lt;/li&gt;
  7515. &lt;/ul&gt;
  7516. &lt;p&gt;&lt;img alt=&quot;Presentational hints in the Inspector's rule-view&quot; class=&quot;alignnone size-large wp-image-1898&quot; height=&quot;183&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/09/headlines187_2-600x183.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  7517. &lt;ul&gt;
  7518. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=774869&quot;&gt;Nate Gross&lt;/a&gt; added a new getKeys API method available across all browser.storage APIs (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1910669&quot;&gt;Bug 1910669&lt;/a&gt;)&lt;/li&gt;
  7519. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=636491&quot;&gt;Emma Zühlcke (:emz)&lt;/a&gt; added a fix so that the users can preview their webcam(s) before giving sites access to it.  (To make sure users look their best, or just to figure out which of their many webcams is the correct one). (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=799415&quot;&gt;Bug 799415&lt;/a&gt;)&lt;/li&gt;
  7520. &lt;/ul&gt;
  7521. &lt;p&gt;&lt;img alt=&quot;Webcam preview&quot; class=&quot;alignnone size-full wp-image-1897&quot; height=&quot;530&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/09/headlines187_1.png&quot; width=&quot;562&quot; /&gt;&lt;/p&gt;
  7522. &lt;ul&gt;
  7523. &lt;li&gt;The New Tab team is testing out productivity widgets like a focus timer for healthy screen-time breaks and a list widget to manage your tasks.&lt;/li&gt;
  7524. &lt;/ul&gt;
  7525. &lt;p&gt;&lt;img alt=&quot;New Tab productivity widgets&quot; class=&quot;alignnone size-large wp-image-1899&quot; height=&quot;307&quot; src=&quot;https://blog.nightly.mozilla.org/files/2025/09/headlines187_3-600x307.png&quot; width=&quot;600&quot; /&gt;&lt;/p&gt;
  7526. &lt;h3&gt;Friends of the Firefox team&lt;/h3&gt;
  7527. &lt;h4&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20(excluding%20employees)&amp;amp;quicksearch=1975093%2C1976968%2C1977124%2C1910669%2C1977066%2C1943057%2C1884618%2C1936018%2C1975872%2C1979623%2C1979294%2C1957214%2C1974983%2C1980170%2C1959618%2C1980854%2C1754273%2C1497064%2C1981039&quot;&gt;Resolved bugs (excluding employees)&lt;/a&gt;&lt;/h4&gt;
  7528. &lt;h4&gt;Volunteers that fixed more than one bug&lt;/h4&gt;
  7529. &lt;ul&gt;
  7530. &lt;li&gt;Gregory Pappas [:gregp]&lt;/li&gt;
  7531. &lt;li&gt;Mauro V [:cheff]&lt;/li&gt;
  7532. &lt;/ul&gt;
  7533. &lt;h4&gt;New contributors (🌟 = first patch)&lt;/h4&gt;
  7534. &lt;ul&gt;
  7535. &lt;li&gt;Jacqueline Amherst &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1959618&quot;&gt;helped reorganize some of the code that we use for performing navigations from the front-end code&lt;/a&gt;&lt;/li&gt;
  7536. &lt;li&gt;Mason Abbruzzese &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1957214&quot;&gt;cleaned up an old and outdated comment in our code&lt;/a&gt;&lt;/li&gt;
  7537. &lt;li&gt;Nate Gross &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1910669&quot;&gt;added a new getKeys API method available across all browser.storage APIs&lt;/a&gt;&lt;/li&gt;
  7538. &lt;li&gt;chase.philpot &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1884618&quot;&gt;cleaned up some old extensions utility code written from the era before DOM Promises&lt;/a&gt;&lt;/li&gt;
  7539. &lt;li&gt;Richard LoRicco &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1975872&quot;&gt;got rid of some unnecessary awaits in some of our preferences tests&lt;/a&gt;&lt;/li&gt;
  7540. &lt;li&gt;Jim Gong made it so that &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1497064&quot;&gt;we fail more gracefully when WebExtensions attempt to set cookies with invalid URLs&lt;/a&gt;&lt;/li&gt;
  7541. &lt;/ul&gt;
  7542. &lt;h3&gt;Project Updates&lt;/h3&gt;
  7543. &lt;h4&gt;Add-ons / Web Extensions&lt;/h4&gt;
  7544. &lt;h5&gt;WebExtension APIs&lt;/h5&gt;
  7545. &lt;ul&gt;
  7546. &lt;li&gt;Thanks to Jim Gong contributing changes needed to improve the errors reported by browser.cookies.set API method on invalid domains (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1497064&quot;&gt;Bug 1497064&lt;/a&gt;)&lt;/li&gt;
  7547. &lt;/ul&gt;
  7548. &lt;h5&gt;WebExtensions Framework&lt;/h5&gt;
  7549. &lt;ul&gt;
  7550. &lt;li&gt;WebExtensions framework and AddonManager internals cleanups:
  7551. &lt;ul&gt;
  7552. &lt;li&gt;Thanks to Chase Philpot for contributing to WebExtensions internals cleanups by removing the now unnecessary filterStack helper function from the WebExtensions internals (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1884618&quot;&gt;Bug 1884618&lt;/a&gt;)&lt;/li&gt;
  7553. &lt;li&gt;Thanks to Mauro V. [:cheff] for removing old rollout prefs for the userScripts APIs (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1943057&quot;&gt;Bug 1943057&lt;/a&gt;)&lt;/li&gt;
  7554. &lt;li&gt;Migrating tests away from deprecated InstallTrigger API (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979294&quot;&gt;Bug 1979294&lt;/a&gt; / &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979648&quot;&gt;Bug 1979648&lt;/a&gt; / &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979657&quot;&gt;Bug 1979657&lt;/a&gt; / &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979690&quot;&gt;Bug 1979690&lt;/a&gt; / &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979712&quot;&gt;Bug 1979712&lt;/a&gt; / &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980604&quot;&gt;Bug 1980604&lt;/a&gt;), in preparation for fully removing the InstallTrigger API implementation (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1776426&quot;&gt;Bug 1776426&lt;/a&gt;)
  7555. &lt;ul&gt;
  7556. &lt;li&gt;Huge shout out goes to Gregory Pappas 🎉 for his contributions to the work for removing the deprecated InstallTrigger API, as well as for fixing an issue (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979281&quot;&gt;Bug 1979281&lt;/a&gt;) preventing use of Mochia test helpers in mochitest-browser tests and then refactoring browser_doorhanger_installs.js test cases to use the Mochia describe/it test helpers (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979294&quot;&gt;Bug 1979294&lt;/a&gt;) 😍&lt;/li&gt;
  7557. &lt;/ul&gt;
  7558. &lt;/li&gt;
  7559. &lt;/ul&gt;
  7560. &lt;/li&gt;
  7561. &lt;li&gt;Investigated issue introduced in recently released 1password WebExtension versions, which was triggering the extension process to hang, reported to 1password developers which have released a fixed version of their add-on (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980009&quot;&gt;Bug 1980009&lt;/a&gt;)
  7562. &lt;ul&gt;
  7563. &lt;li&gt;We have also investigated why ProcessHangMonitor isn’t currently detecting and showing to the user a notification box on slow scripts that are making the extension process hanging and filed &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980452&quot;&gt;Bug 1980452&lt;/a&gt; to capture the findings and tracking fixing that as a followup for the 1password incident.&lt;/li&gt;
  7564. &lt;/ul&gt;
  7565. &lt;/li&gt;
  7566. &lt;li&gt;Investigated and fixed AsyncShutdown failures hit due to a race between application shutdown and active add-ons background pages starting up (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1959339&quot;&gt;Bug 1959339&lt;/a&gt;)&lt;/li&gt;
  7567. &lt;li&gt;As part of introducing support for WPT WebExtensions API tests (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1949012&quot;&gt;Bug 1949012&lt;/a&gt;), new browser.test.onTestStarted and browser.test.onTestFinished API events are now supported from inside tests running WPT mode (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1971013&quot;&gt;Bug 1971013&lt;/a&gt;)&lt;/li&gt;
  7568. &lt;li&gt;Replaced mouseenter/mouseleave with mouseove/mouseout in browser-addons.js logic handled the extensions button auto-hiding mode (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1976773&quot;&gt;Bug 1976773&lt;/a&gt;)&lt;/li&gt;
  7569. &lt;li&gt;Fixed bug which was generating WebExtensions uuids for extensions not yet installed and increasing the size of extensions.webextensions.uuids pref value unnecessarily (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1974419&quot;&gt;Bug 1974419&lt;/a&gt;)&lt;/li&gt;
  7570. &lt;/ul&gt;
  7571. &lt;h5&gt;Addon Manager &amp;amp; about:addons&lt;/h5&gt;
  7572. &lt;ul&gt;
  7573. &lt;li&gt;Added new localized string to improve error message shown on add-on install flows failing due to errors hit on accessing the XPI file being installed (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1976490&quot;&gt;Bug 1976490&lt;/a&gt;)&lt;/li&gt;
  7574. &lt;/ul&gt;
  7575. &lt;h4&gt;DevTools&lt;/h4&gt;
  7576. &lt;ul&gt;
  7577. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=473060&quot;&gt;Kagami Rosylight&lt;/a&gt; migrated the DevTools color picker widget to Fluent for devtools color picker widget (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1978294&quot;&gt;#1978294&lt;/a&gt;)&lt;/li&gt;
  7578. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot&lt;/a&gt; improved performance of the Debugger sources tree on pages with a lot of sources (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1976570&quot;&gt;#1976570&lt;/a&gt;)
  7579. &lt;ul&gt;
  7580. &lt;li&gt;For example, on a page with 90K sources, on Alex’s machine, we went from 3800ms to 190ms&lt;/li&gt;
  7581. &lt;/ul&gt;
  7582. &lt;/li&gt;
  7583. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=283262&quot;&gt;Alexandre Poirot&lt;/a&gt; was able to make the Debugger reuse the same tab when pretty printing a source (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1971817&quot;&gt;#1971817&lt;/a&gt;)
  7584. &lt;ul&gt;
  7585. &lt;li&gt;It used to create a new Tab with the pretty content, which could be confusing&lt;/li&gt;
  7586. &lt;/ul&gt;
  7587. &lt;/li&gt;
  7588. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=557153&quot;&gt;Nicolas Chevobbe&lt;/a&gt; removed usage of the &lt;a href=&quot;https://www.npmjs.com/package/whatwg-url&quot;&gt;whatwg-url&lt;/a&gt; package in our source map code, which &lt;a href=&quot;https://treeherder.mozilla.org/perfherder/alerts?id=46058&quot;&gt;significantly improved performance&lt;/a&gt; (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1829610&quot;&gt;#1829610&lt;/a&gt;)&lt;/li&gt;
  7589. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=559949&quot;&gt;Julian Descottes&lt;/a&gt; made the “tab toolbox” (e.g. about:debugging) to be focused when the tab was in background and a breakpoint is hit (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1978100&quot;&gt;#1978100&lt;/a&gt;)&lt;/li&gt;
  7590. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=557153&quot;&gt;Nicolas Chevobbe&lt;/a&gt; fixed 2 regressions in the markup view:
  7591. &lt;ul&gt;
  7592. &lt;li&gt;First, the tree would no longer gets focused when opening the inspector via the “Inspect” context menu (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979591&quot;&gt;#1979591&lt;/a&gt;)&lt;/li&gt;
  7593. &lt;li&gt;Second, the search wouldn’t find css selector with tagname + class with hyphens (e.g. div.narrow-item) (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980892&quot;&gt;#1980892&lt;/a&gt;)&lt;/li&gt;
  7594. &lt;/ul&gt;
  7595. &lt;/li&gt;
  7596. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=559949&quot;&gt;Julian Descottes&lt;/a&gt; fixed the splitter in Memory panel for the Retaining Paths view (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1978538&quot;&gt;#1978538&lt;/a&gt;)&lt;/li&gt;
  7597. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/user_profile?user_id=557153&quot;&gt;Nicolas Chevobbe&lt;/a&gt; made “Group Similar Messages” setting also impact the “repeat bubble”: when the feature is disabled, successive similar messages will all be displayed in the console (&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1615206&quot;&gt;#1615206&lt;/a&gt;)&lt;/li&gt;
  7598. &lt;/ul&gt;
  7599. &lt;h4&gt;WebDriver BiDi&lt;/h4&gt;
  7600. &lt;ul&gt;
  7601. &lt;li&gt;Sabina added a &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1972865&quot;&gt;new helper to check if there is existing session data matching specific criteria&lt;/a&gt;, and at the same time cleaned up the SessionData class to use proper private fields and methods where possible.&lt;/li&gt;
  7602. &lt;li&gt;Mauro &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1938638&quot;&gt;removed the deprecated “–enable-crash-reporter” argument from geckodriver&lt;/a&gt;.&lt;/li&gt;
  7603. &lt;li&gt;Sasha fixed a bug when &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1978533&quot;&gt;locale override, set with “emulation.setLocaleOverride” command, was not inherited to newly created cross-origin iframes&lt;/a&gt;.&lt;/li&gt;
  7604. &lt;/ul&gt;
  7605. &lt;h4&gt;New Tab Page&lt;/h4&gt;
  7606. &lt;ul&gt;
  7607. &lt;li&gt;We are experimenting adding productivity widgets to new tab in 143
  7608. &lt;ul&gt;
  7609. &lt;li&gt;To enable:
  7610. &lt;ul&gt;
  7611. &lt;li&gt;Browser.newtabpage.activity-stream.widgets.system.enabled (allow all widgets)&lt;/li&gt;
  7612. &lt;li&gt;Timer
  7613. &lt;ul&gt;
  7614. &lt;li&gt;browser.newtabpage.activity-stream.widgets.system.focusTimer.enabled&lt;/li&gt;
  7615. &lt;li&gt;browser.newtabpage.activity-stream.widgets.focusTimer.enabled&lt;/li&gt;
  7616. &lt;li&gt;browser.newtabpage.activity-stream.widgets.focusTimer.showSystemNotifications&lt;/li&gt;
  7617. &lt;/ul&gt;
  7618. &lt;/li&gt;
  7619. &lt;li&gt;Lists
  7620. &lt;ul&gt;
  7621. &lt;li&gt;browser.newtabpage.activity-stream.widgets.system.lists.enabled&lt;/li&gt;
  7622. &lt;li&gt;browser.newtabpage.activity-stream.widgets.lists.enabled&lt;/li&gt;
  7623. &lt;/ul&gt;
  7624. &lt;/li&gt;
  7625. &lt;/ul&gt;
  7626. &lt;/li&gt;
  7627. &lt;/ul&gt;
  7628. &lt;/li&gt;
  7629. &lt;li&gt;We’re aiming to do our first train-hop pilot to Beta either later this week or early next!&lt;/li&gt;
  7630. &lt;/ul&gt;
  7631. &lt;h4&gt;Search and Navigation&lt;/h4&gt;
  7632. &lt;ul&gt;
  7633. &lt;li&gt;Drew has added a “Search Image” context menu for visual search – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1977965&quot;&gt;1977965&lt;/a&gt;&lt;/li&gt;
  7634. &lt;li&gt;Moritz has enabled urlbar deduplication by default – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979658&quot;&gt;1979658&lt;/a&gt;&lt;/li&gt;
  7635. &lt;li&gt;Dao is working on several refactors to enable reuse of the urlbar – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980372&quot;&gt;1980372&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1980913&quot;&gt;1980913&lt;/a&gt;&lt;/li&gt;
  7636. &lt;li&gt;Daisuke has started working on stock suggestions – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1969990&quot;&gt;1969990&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979232&quot;&gt;1979232&lt;/a&gt;&lt;/li&gt;
  7637. &lt;li&gt;Mark fixed several bug with Rakuten – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1979030&quot;&gt;1979030&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1924693&quot;&gt;1924693&lt;/a&gt;&lt;/li&gt;
  7638. &lt;li&gt;Marco fixed bug with results flashing – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1978283&quot;&gt;1978283&lt;/a&gt;&lt;/li&gt;
  7639. &lt;li&gt;Emilio polished the padding of the library toolbar – &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1978699&quot;&gt;1978699&lt;/a&gt;&lt;/li&gt;
  7640. &lt;/ul&gt;</description>
  7641. <pubDate>Fri, 12 Sep 2025 19:59:17 +0000</pubDate>
  7642. <dc:creator>Anna Kulyk</dc:creator>
  7643. </item>
  7644. <item>
  7645. <title>The Rust Programming Language Blog: crates.io phishing campaign</title>
  7646. <guid isPermaLink="true">https://blog.rust-lang.org/2025/09/12/crates-io-phishing-campaign/</guid>
  7647. <link>https://blog.rust-lang.org/2025/09/12/crates-io-phishing-campaign/</link>
  7648. <description>&lt;p&gt;We received multiple reports of a phishing campaign targeting crates.io users
  7649. (from the &lt;code&gt;rustfoundation.dev&lt;/code&gt; domain name), mentioning a compromise of our
  7650. infrastructure and asking users to authenticate to limit damage to their crates.&lt;/p&gt;
  7651. &lt;p&gt;These emails are malicious and come from a domain name not controlled by  the
  7652. Rust Foundation (nor the Rust Project), seemingly with the purpose of stealing
  7653. your GitHub credentials. We have no evidence of a compromise of the crates.io
  7654. infrastructure.&lt;/p&gt;
  7655. &lt;p&gt;We are taking steps to get the domain name taken down and to monitor for
  7656. suspicious activity on crates.io. Do not follow any links in these emails if you
  7657. receive them, and mark them as phishing with your email provider.&lt;/p&gt;
  7658. &lt;p&gt;If you have any further questions please reach out to &lt;a href=&quot;mailto:security@rust-lang.org&quot;&gt;security@rust-lang.org&lt;/a&gt;
  7659. and &lt;a href=&quot;mailto:help@crates.io&quot;&gt;help@crates.io&lt;/a&gt;.&lt;/p&gt;</description>
  7660. <pubDate>Fri, 12 Sep 2025 00:00:00 +0000</pubDate>
  7661. <dc:creator>Rust Security Response WG, crates.io team</dc:creator>
  7662. </item>
  7663. <item>
  7664. <title>Mozilla Thunderbird: State of the Thunder: Mozilla Connect Updates</title>
  7665. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3783</guid>
  7666. <link>https://blog.thunderbird.net/2025/09/state-of-the-thunder-mozilla-connect-updates/</link>
  7667. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/09/Blog-banner-State-of-the-Thunder6-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  7668. &lt;p&gt;Welcome back to the latest season of State of the Thunder! After a short break, we’re back and ready to go. Michael Ellis, our Manager of Community Programs, is helping Alessandro with hosting duties. Along with members of the Thunderbird team and community, they’re answering your questions and keeping everyone updated on our roadmap progress for our projects.&lt;/p&gt;
  7669.  
  7670.  
  7671.  
  7672. &lt;p&gt;In this episode, we’re talking about our initiatives for regular community feedback, tackling a variety of questions, and providing status updates on the top 20-ish Mozilla Connect Thunderbird suggestions. &lt;/p&gt;
  7673.  
  7674.  
  7675.  
  7676. &lt;h3&gt;Community Questions&lt;/h3&gt;
  7677.  
  7678.  
  7679.  
  7680. &lt;h4&gt;Accidental Message Order Sorting&lt;/h4&gt;
  7681.  
  7682.  
  7683.  
  7684. &lt;p&gt;&lt;strong&gt;Question:&lt;/strong&gt; Clearly the number one issue with Thunderbird that breaks for many of my clients is that if they accidentally click on a column header the sorting of the message is changed. “My messages are gone” is what I then hear all the time from my clients. It would be wonderful if the sorting of the message could be locked and not changed through such an easy operation, which often is invoked accidentally.&lt;/p&gt;
  7685.  
  7686.  
  7687.  
  7688. &lt;p&gt;Answer: This is a great usability question and a complicated one. Alessandro recommends switching to CardsView, as it’s harder to accidentally change. This one one of the reasons we implemented it! However, we can definitely explore options to lock the message order in through enterprise policies. We would want to be mindful of users who wanted to change the order. &lt;/p&gt;
  7689.  
  7690.  
  7691.  
  7692. &lt;p&gt;Michael discusses the option of a pop-up warning that could inform the user they’re about the change the message sorting order. Increased friction through a pop-up, though, as Alessandro and Jesse Miksic from the design team both point out, can cause its own issues. But this is certainly something we’ll look into more! &lt;/p&gt;
  7693.  
  7694.  
  7695.  
  7696. &lt;h4&gt;Move Focus Keyboard Shortcut&lt;/h4&gt;
  7697.  
  7698.  
  7699.  
  7700. &lt;p&gt;&lt;strong&gt;Question:&lt;/strong&gt; Could there be consideration to add a keystroke to immediately move the focus to the list of messages in the currently open mailbox? Even better if keystrokes that would automatically do this for the inbox folder or the default account.&lt;/p&gt;
  7701.  
  7702.  
  7703.  
  7704. &lt;p&gt;&lt;strong&gt;Answer:&lt;/strong&gt; Alessandro notes Thunderbird already has this ability, but it’s not super noticeable. The F6 key allows you to switch focuses between the main areas of the application. So we’re approaching this problem from two directions: implementing tabular keyboard navigation and customizable shortcuts. We don’t have an expected delivery date on the latter, but we plan to have a searchable keyboard shortcut hub. We know our interface can be a little daunting, and we’re tackling it from multiple angles.&lt;/p&gt;
  7705.  
  7706.  
  7707.  
  7708. &lt;h4&gt;Option for Simplified Thunderbird?&lt;/h4&gt;
  7709.  
  7710.  
  7711.  
  7712. &lt;p&gt;&lt;strong&gt;Question: &lt;/strong&gt;I work for a company which develops a Raspberry Pi-based computer made specific… specifically for blind consumers. Thunderbird is installed on this device by default. Many of our users are not tech-savvy. and just want a simple email client. I would love to have an easy method for removing some of the clutters with the goal of having a UI with fewer controls. Currently, users often have to press the tab key many times just to move to the list of messages in their inbox. For some users, all they really want is the message list and the list of folders, with the menu bar open, and that’s it. A bit like we once had with Outlook Express.&lt;/p&gt;
  7713.  
  7714.  
  7715.  
  7716. &lt;p&gt;&lt;strong&gt;Answer:&lt;/strong&gt; Alessandro and Ryan Sipes, our director, have talked about the need for a lighter version of Thunderbird a lot. This would help users who don’t need all the power of Thunderbird, and just want to focus on their messages (not even their folders). However, Ryan doesn’t want a separate version of Thunderbird we’d need to maintain, but to build a better usability curve into Thunderbird. Answering this question means having a Thunderbird that is simple by default, but more powerful and customizable if needed, without upsetting our current users.&lt;/p&gt;
  7717.  
  7718.  
  7719.  
  7720. &lt;p&gt;Heather Ellsworth from the community team also supports the idea of a user preference for a lighter Thunderbird. At conferences and co-working spaces, she constantly hears the requests for a slightly simpler version of Thunderbird.&lt;/p&gt;
  7721.  
  7722.  
  7723.  
  7724. &lt;h4&gt;Thunderbird PPA&lt;/h4&gt;
  7725.  
  7726.  
  7727.  
  7728. &lt;p&gt;&lt;strong&gt;Question: &lt;/strong&gt;I’m using Linux, one of the Ubuntu-derived flavors. And I have Thunderbird 128.14 ESR installed through the &lt;a href=&quot;https://launchpad.net/~mozillateam/+archive/ubuntu/ppa&quot;&gt;Mozilla Team PPA&lt;/a&gt;. I would love to know when the ESR version of 140 will be available in this PPA.&lt;/p&gt;
  7729.  
  7730.  
  7731.  
  7732. &lt;p&gt;&lt;strong&gt;Answer:&lt;/strong&gt; Heather, who works a lot with Linux packaging, takes this question. This PPA isn’t an official distribution channel for Thunderbird, which leads to some confusion. Our official Linux packages are the Snap and flatpak, and the tarball available on our website. A community member named Rico, whose handle is ricotz, maintains this PPA. In the PPA, you can click on his name to learn how to contact him for question like this.&lt;/p&gt;
  7733.  
  7734.  
  7735.  
  7736. &lt;h3&gt;Top 20-ish Mozilla Connect Posts&lt;/h3&gt;
  7737.  
  7738.  
  7739.  
  7740. &lt;p&gt;If you’ve ever posted an idea to make Thunderbird better in a blog comment, social media post, or a SUMO (&lt;a href=&quot;https://support.mozilla.org&quot;&gt;Mozilla Support&lt;/a&gt;) thread, you’ve probably been prompted to share your suggestion on &lt;a href=&quot;https://connect.mozilla.org/&quot;&gt;Mozilla Connect.&lt;/a&gt; This helps us keep our community feedback in one place, which helps our team prioritize features the community wants!&lt;/p&gt;
  7741.  
  7742.  
  7743.  
  7744. &lt;p&gt;Where we’re falling short, however, is keeping the community updated on the progress of their suggestions. With a dedicated community team, this is something we can do better! Right now, we’d like to provide a quick status update on the top 20-ish Mozilla Connect posts related to Thunderbird.&lt;/p&gt;
  7745.  
  7746.  
  7747.  
  7748. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/firefox-sync-for-thunderbird/idi-p/28971&quot;&gt;Sync&lt;/a&gt;&lt;/h4&gt;
  7749.  
  7750.  
  7751.  
  7752. &lt;p&gt;We implemented this in the Daily build of the desktop app last year, using a staging environment for Firefox Sync. But Firefox Sync is called Firefox Sync because it’s built for Firefox. Thunderbird profiles, in comparison, have a lot more data points. This meant we had to build something completely different. &lt;/p&gt;
  7753.  
  7754.  
  7755.  
  7756. &lt;p&gt;As we started to spin up Thunderbird Pro, we decided it made more sense to have a Thunderbird account that would manage everything, including Sync. Unfortunately, this meant a lot of delays. So Sync is still on our radar, and we hope to have it next year, barring further complications.&lt;/p&gt;
  7757.  
  7758.  
  7759.  
  7760. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/better-gnome-desktop-integration/idi-p/14612&quot;&gt;GNOME Desktop Integration&lt;/a&gt;&lt;/h4&gt;
  7761.  
  7762.  
  7763.  
  7764. &lt;p&gt;Yes, we’re working on this, starting with native desktop notifications. Ideally, we want to be integrated with more Linux desktop environments through expanded native APIs.&lt;/p&gt;
  7765.  
  7766.  
  7767.  
  7768. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/color-for-thunderbird-accounts/idi-p/14758&quot;&gt;Color for Thunderbird Accounts&lt;/a&gt;&lt;/h4&gt;
  7769.  
  7770.  
  7771.  
  7772. &lt;p&gt;We already have it! You can access your account settings and customize the colors of each account.&lt;/p&gt;
  7773.  
  7774.  
  7775.  
  7776. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/show-full-email-address-when-mouse-over-sender/idi-p/29010&quot;&gt;Show full email address on mouse-over&lt;/a&gt;&lt;/h4&gt;
  7777.  
  7778.  
  7779.  
  7780. &lt;p&gt;Already have this too. If this doesn’t happen, it’s a bug, and we’d definitely appreciate a report at &lt;a href=&quot;https://bugzilla.mozilla.org&quot;&gt;Bugzilla&lt;/a&gt;.&lt;/p&gt;
  7781.  
  7782.  
  7783.  
  7784. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/don-t-save-passwords-as-plain-text-but-rather-integrate-with-os/idi-p/29377&quot;&gt;Don’t save passwords as plain text, but rather integrate with the OS storage system&lt;/a&gt;&lt;/h4&gt;
  7785.  
  7786.  
  7787.  
  7788. &lt;p&gt;We’re exploring this as both part of our increased native OS integrations and strengthening and security integrations with Thunderbird.&lt;/p&gt;
  7789.  
  7790.  
  7791.  
  7792. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/thunderbird-should-by-default-have-all-telemetry-as-an-opt-in/idi-p/24953&quot;&gt;Thunderbird should, by default, have all telemetry as an opt-in option, or have zero telemetry&lt;/a&gt;&lt;/h4&gt;
  7793.  
  7794.  
  7795.  
  7796. &lt;p&gt;We’re already adopting opt-in telemetry for an upcoming release of Thunderbird for Android, and we want to make this the default for desktop in the future. While desktop is currently opt-out, Alessandro stresses we only have a few limited telemetry probes for desktop Thunderbird. And those probes can show how the majority of users are using the app and help us avoid bad UX choices. &lt;/p&gt;
  7797.  
  7798.  
  7799.  
  7800. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/thunderbird-for-iphone-and-ipad/idi-p/21628&quot;&gt;Thunderbird for iPhone and iPad&lt;/a&gt;&lt;/h4&gt;
  7801.  
  7802.  
  7803.  
  7804. &lt;p&gt;In progress! &lt;/p&gt;
  7805.  
  7806.  
  7807.  
  7808. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/jmap-support-or-similar-for-thunderbird/idi-p/28974&quot;&gt;JMAP Support&lt;/a&gt;&lt;/h4&gt;
  7809.  
  7810.  
  7811.  
  7812. &lt;p&gt;Currently in the works for the upcoming iOS release, with plans for support on desktop and Android. Thundermail will also come with JMAP.&lt;/p&gt;
  7813.  
  7814.  
  7815.  
  7816. &lt;h4&gt;&lt;a href=&quot;https://connect.mozilla.org/t5/ideas/firefox-translations-in-thunderbird/idi-p/24890&quot;&gt;Firefox Translate&lt;/a&gt;&lt;/h4&gt;
  7817.  
  7818.  
  7819.  
  7820. &lt;p&gt;Exploring this is low on our list right now. This is both because of performance concerns and we want to be very cautious with anything concerning machine learning, which includes translation. &lt;/p&gt;
  7821.  
  7822.  
  7823.  
  7824. &lt;h3&gt;Watch the Video (Also on &lt;a href=&quot;https://tilvids.com/w/8DL2nGZjfv3h62ormxB6cW&quot;&gt;Peertube&lt;/a&gt;)&lt;/h3&gt;
  7825.  
  7826.  
  7827.  
  7828. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-4-3 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  7829.  
  7830. &lt;/div&gt;&lt;/figure&gt;
  7831.  
  7832.  
  7833.  
  7834. &lt;h3&gt;Listen on the Thundercast!&lt;/h3&gt;
  7835.  
  7836.  
  7837. &lt;pre&gt;&lt;/pre&gt;
  7838.  
  7839.  
  7840. &lt;h3&gt;Our Next State of the Thunder&lt;/h3&gt;
  7841.  
  7842.  
  7843.  
  7844. &lt;p&gt;Anxious to know the rest of the top 20 Mozilla Connect posts? Join us on Tuesday, September 16 at 3 PM Pacific (22:00 UTC)! Find out how to join on the &lt;a href=&quot;https://thunderbird.topicbox.com/groups/planning/&quot;&gt;TB Planning mailing list&lt;/a&gt;. We think this will be a great season and who knows, by the end of it, we may even have a jingle. See you next time!&lt;/p&gt;
  7845. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/09/state-of-the-thunder-mozilla-connect-updates/&quot;&gt;State of the Thunder: Mozilla Connect Updates&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  7846. <pubDate>Thu, 11 Sep 2025 19:20:10 +0000</pubDate>
  7847. <dc:creator>Monica Ayhens-Madon</dc:creator>
  7848. </item>
  7849. <item>
  7850. <title>The Rust Programming Language Blog: Rust compiler performance survey 2025 results</title>
  7851. <guid isPermaLink="true">https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/</guid>
  7852. <link>https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/</link>
  7853. <description>&lt;p&gt;Two months ago, we launched the first &lt;a href=&quot;https://blog.rust-lang.org/2025/06/16/rust-compiler-performance-survey-2025&quot;&gt;Rust Compiler Performance Survey&lt;/a&gt;, with the goal of helping us understand the biggest pain points of Rust developers related to build performance. It is clear that this topic is very important for the Rust community, as the survey received over 3 700 responses! We would like to thank everyone who participated in the survey, and especially those who described their workflows and challenges with an open answer. We plan to run this survey annually, so that we can observe long-term trends in Rust build performance and its perception.&lt;/p&gt;
  7854. &lt;p&gt;In this post, we'll show some interesting results and insights that we got from the survey and promote work that we have already done recently or that we plan to do to improve the build performance of Rust code. If you would like to examine the complete results of the survey, you can find them &lt;a href=&quot;https://raw.githubusercontent.com/rust-lang/surveys/main/surveys/2025/compiler-performance-survey/report/compiler-performance-2025-report.pdf&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
  7855. &lt;p&gt;And now strap in, as there is a lot of data to explore! As this post is relatively long, here is an index of topics that it covers:&lt;/p&gt;
  7856. &lt;ul&gt;
  7857. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#overall-satisfaction&quot;&gt;Overall satisfaction&lt;/a&gt;&lt;/li&gt;
  7858. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#important-workflows&quot;&gt;Important workflows&lt;/a&gt;&lt;/li&gt;
  7859. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#incremental-rebuilds&quot;&gt;Incremental rebuilds&lt;/a&gt;&lt;/li&gt;
  7860. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#type-checking-and-ide-performance&quot;&gt;Type checking and IDE performance&lt;/a&gt;&lt;/li&gt;
  7861. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#clean-and-ci-builds&quot;&gt;Clean and CI builds&lt;/a&gt;&lt;/li&gt;
  7862. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#debug-information&quot;&gt;Debug information&lt;/a&gt;&lt;/li&gt;
  7863. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#workarounds-for-improving-build-performance&quot;&gt;Workarounds for improving build performance&lt;/a&gt;&lt;/li&gt;
  7864. &lt;li&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#understanding-why-builds-are-slow&quot;&gt;Understanding why builds are slow&lt;/a&gt;&lt;/li&gt;
  7865. &lt;/ul&gt;
  7866. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#overall-satisfaction&quot;&gt;&lt;/a&gt;
  7867. Overall satisfaction&lt;/h3&gt;
  7868. &lt;p&gt;To understand the overall sentiment, we asked our respondents to rate their satisfaction with their build performance, on a scale from 0 (worst) to 10 (best). The average rating was 6, with most people rating their experience with 7 out of 10:&lt;/p&gt;
  7869.  
  7870. &lt;div&gt;
  7871.    &lt;div class=&quot;bar-chart&quot; id=&quot;satisfaction&quot;&gt;&amp;lt;noscript&amp;gt;
  7872. &amp;lt;img alt=&quot;satisfaction&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/satisfaction.png&quot; /&amp;gt;
  7873. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  7874.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  7875.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/satisfaction.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/satisfaction.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  7876.    &lt;/div&gt;
  7877. &lt;/div&gt;
  7878.  
  7879. &lt;p&gt;To help us understand the overall build experience in more detail, we also analyzed all open answers (over a thousand of them) written by our respondents, to help us identify several recurring themes, which we will discuss in this post.&lt;/p&gt;
  7880. &lt;p&gt;One thing that is clear from both the satisfaction rating and the open answers is that the build experience differs wildly across users and workflows, and it is not as clear-cut as &quot;Rust builds are slow&quot;. We actually received many positive comments about users being happy with Rust build performance, and appreciation for it being improved vastly over the past several years to the point where it stopped being a problem.&lt;/p&gt;
  7881. &lt;p&gt;People also liked to compare their experience with other competing technologies. For example, many people wrote that the build performance of Rust is not worse, or is even better, than what they saw with C++. On the other hand, others noted that the build performance of languages such as Go or Zig is much better than that of Rust.&lt;/p&gt;
  7882. &lt;p&gt;While it is great to see some developers being happy with the state we have today, it is clear that many people are not so lucky, and Rust's build performance limits their productivity. Around 45% respondents who answered that they are no longer using Rust said that at least one of the reasons why they stopped were long compile times.&lt;/p&gt;
  7883. &lt;p&gt;In our survey we received a lot of feedback pointing out real issues and challenges in several areas of build performance, which is what we will focus on in this post.&lt;/p&gt;
  7884. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#important-workflows&quot;&gt;&lt;/a&gt;
  7885. Important workflows&lt;/h3&gt;
  7886. &lt;p&gt;The challenges that Rust developers experience with build performance are not always as simple as the compiler itself being slow. There are many diverse workflows with competing trade-offs, and optimizing build performance for them might require completely different solutions. Some approaches for improving build performance can also be quite unintuitive. For example, stabilizing certain language features could help remove the need for certain build scripts or proc macros, and thus speed up compilation across the Rust ecosystem. You can watch &lt;a href=&quot;https://www.youtube.com/watch?v=-jy4HaNEJCo&quot;&gt;this talk&lt;/a&gt; from RustWeek about build performance to learn more.&lt;/p&gt;
  7887. &lt;p&gt;It is difficult to enumerate all possible build workflows, but we at least tried to ask about workflows that we assumed are common and could limit the productivity of Rust developers the most:&lt;/p&gt;
  7888.  
  7889. &lt;div&gt;
  7890.    &lt;div class=&quot;matrix-chart&quot; id=&quot;limiting-workflows&quot;&gt;&amp;lt;noscript&amp;gt;
  7891. &amp;lt;img alt=&quot;limiting-workflows&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/limiting-workflows.png&quot; /&amp;gt;
  7892. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  7893.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  7894.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/limiting-workflows.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/limiting-workflows.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  7895.    &lt;/div&gt;
  7896. &lt;/div&gt;
  7897.  
  7898. &lt;p&gt;We can see that all the workflows that we asked about cause significant problems to at least a fraction of the respondents, but some of them more so than others. To gain more information about the specific problems that developers face, we also asked a more detailed, follow-up question:&lt;/p&gt;
  7899.  
  7900. &lt;div&gt;
  7901.    &lt;div class=&quot;matrix-chart&quot; id=&quot;problems&quot;&gt;&amp;lt;noscript&amp;gt;
  7902. &amp;lt;img alt=&quot;problems&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/problems.png&quot; /&amp;gt;
  7903. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  7904.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  7905.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/problems.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/problems.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  7906.    &lt;/div&gt;
  7907. &lt;/div&gt;
  7908.  
  7909. &lt;p&gt;Based on the answers to these two questions and other experiences shared in the open answers, we identified three groups of workflows that we will discuss next:&lt;/p&gt;
  7910. &lt;ul&gt;
  7911. &lt;li&gt;Incremental rebuilds after making a small change&lt;/li&gt;
  7912. &lt;li&gt;Type checking using &lt;code&gt;cargo check&lt;/code&gt; or with a code editor&lt;/li&gt;
  7913. &lt;li&gt;Clean, from-scratch builds, including CI builds&lt;/li&gt;
  7914. &lt;/ul&gt;
  7915. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#incremental-rebuilds&quot;&gt;&lt;/a&gt;
  7916. Incremental rebuilds&lt;/h4&gt;
  7917. &lt;p&gt;Waiting too long for an incremental rebuild after making a small source code change was by far the most common complaint in the open answers that we received, and it was also the most common problem that respondents said they struggle with. Based on our respondents' answers, this comes down to three main bottlenecks:&lt;/p&gt;
  7918. &lt;ul&gt;
  7919. &lt;li&gt;&lt;strong&gt;Changes in workspaces trigger unnecessary rebuilds.&lt;/strong&gt; If you modify a crate in a workspace that has several dependent crates and perform a rebuild, all those dependent crates will currently have to be recompiled. This can cause a lot of unnecessary work and dramatically increase the latency of rebuilds in large (or deep) workspaces. We have some ideas about how to improve this workflow, such as the &lt;a href=&quot;https://rust-lang.github.io/rust-project-goals/2025h2/relink-dont-rebuild.html&quot;&gt;&quot;Relink, don't rebuild&quot;&lt;/a&gt; proposal, but these are currently in a very experimental stage.&lt;/li&gt;
  7920. &lt;li&gt;&lt;strong&gt;The linking phase is too slow.&lt;/strong&gt; This was a very common complaint, and it is indeed a real issue, because unlike the rest of the compilation process, linking is always performed &quot;from scratch&quot;. The Rust compiler usually delegates linking to an external/system linker, so its performance is not completely within our hands. However, we are attempting to switch to faster linkers by default. For example, the most popular target (&lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt;) will very soon switch to the &lt;a href=&quot;https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable&quot;&gt;LLD linker&lt;/a&gt;, which provides significant performance wins. Long-term, it is possible that some linkers (e.g. &lt;a href=&quot;https://github.com/davidlattimore/wild&quot;&gt;wild&lt;/a&gt;) will allow us to perform even linking incrementally.&lt;/li&gt;
  7921. &lt;li&gt;&lt;strong&gt;Incremental rebuild of a single crate is too slow.&lt;/strong&gt; The performance of this workflow depends on the cleverness of the incremental engine of the Rust compiler. While it is already very sophisticated, there are some parts of the compilation process that are not incremental yet or that are not cached in an optimal way. For example, expansion of derive proc macros is not currently cached, although work is underway to &lt;a href=&quot;https://github.com/rust-lang/rust/pull/145354&quot;&gt;change that&lt;/a&gt;.&lt;/li&gt;
  7922. &lt;/ul&gt;
  7923. &lt;p&gt;Several users have mentioned that they would like to see Rust perform hot-patching (such as the &lt;code&gt;subsecond&lt;/code&gt; system used by the Dioxus UI framework or similar approaches used e.g. by the Bevy game engine). While these hot-patching systems are very exciting and can produce truly near-instant rebuild times for specialized use-cases, it should be noted that they also come with many limitations and edge-cases, and it does not seem that a solution that would allow hot-patching to work in a robust way has been found yet.&lt;/p&gt;
  7924. &lt;p&gt;To gauge how long is the typical rebuild latency, we asked our respondents to pick a single Rust project that they work on and which causes them to struggle with build times the most, and tell us how long they have to wait for it to be rebuilt after making a code change.&lt;/p&gt;
  7925.  
  7926. &lt;div&gt;
  7927.    &lt;div class=&quot;bar-chart&quot; id=&quot;rebuild-wait-time&quot;&gt;&amp;lt;noscript&amp;gt;
  7928. &amp;lt;img alt=&quot;rebuild-wait-time&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time.png&quot; /&amp;gt;
  7929. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  7930.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  7931.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  7932.    &lt;/div&gt;
  7933. &lt;/div&gt;
  7934.  
  7935. &lt;p&gt;Even though many developers do not actually experience this latency after each code change, as they consume results of type checking or inline annotations in their code editor, the fact that 55% of respondents have to wait more than ten seconds for a rebuild is far from ideal.&lt;/p&gt;
  7936. &lt;p&gt;If we partition these results based on answers to other questions, it is clear that the rebuild times depend a lot on the size of the project:&lt;/p&gt;
  7937.  
  7938. &lt;div&gt;
  7939.    &lt;div class=&quot;class&quot; id=&quot;rebuild-wait-time-code-size&quot;&gt;&amp;lt;noscript&amp;gt;
  7940. &amp;lt;img alt=&quot;rebuild-wait-time-code-size&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time-code-size.png&quot; /&amp;gt;
  7941. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  7942.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  7943.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time-code-size.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time-code-size.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  7944.    &lt;/div&gt;
  7945. &lt;/div&gt;
  7946.  
  7947. &lt;p&gt;And to a lesser factor also on the number of used dependencies:&lt;/p&gt;
  7948.  
  7949. &lt;div&gt;
  7950.    &lt;div class=&quot;class&quot; id=&quot;rebuild-wait-time-dep-count&quot;&gt;&amp;lt;noscript&amp;gt;
  7951. &amp;lt;img alt=&quot;rebuild-wait-time-dep-count&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time-dep-count.png&quot; /&amp;gt;
  7952. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  7953.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  7954.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time-dep-count.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/rebuild-wait-time-dep-count.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  7955.    &lt;/div&gt;
  7956. &lt;/div&gt;
  7957.  
  7958. &lt;p&gt;We would love to get to a point where the time needed to rebuild a Rust project is dependent primarily on the amount of performed code changes, rather than on the size of the codebase, but clearly we are not there yet.&lt;/p&gt;
  7959. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#type-checking-and-ide-performance&quot;&gt;&lt;/a&gt;
  7960. Type checking and IDE performance&lt;/h4&gt;
  7961. &lt;p&gt;Approximately 60% of respondents say that they use &lt;code&gt;cargo&lt;/code&gt; terminal commands to type check, build or test their code, with &lt;code&gt;cargo check&lt;/code&gt; being the most commonly used command performed after each code change:&lt;/p&gt;
  7962.  
  7963. &lt;div&gt;
  7964.    &lt;div class=&quot;matrix-chart&quot; id=&quot;cargo-commands&quot;&gt;&amp;lt;noscript&amp;gt;
  7965. &amp;lt;img alt=&quot;cargo-commands&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/cargo-commands.png&quot; /&amp;gt;
  7966. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  7967.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  7968.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/cargo-commands.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/cargo-commands.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  7969.    &lt;/div&gt;
  7970. &lt;/div&gt;
  7971.  
  7972. &lt;p&gt;While the performance of &lt;code&gt;cargo check&lt;/code&gt; does not seem to be as big of a blocker as e.g. incremental rebuilds, it also causes some pain points. One of the most common ones present in the survey responses is the fact that &lt;code&gt;cargo check&lt;/code&gt; does not share the build cache with &lt;code&gt;cargo build&lt;/code&gt;. This causes additional compilation to happen when you run e.g. &lt;code&gt;cargo check&lt;/code&gt; several times to find all type errors, and when it succeeds, you follow up with &lt;code&gt;cargo build&lt;/code&gt; to actually produce a built artifact. This workflow is an example of competing trade-offs, because sharing the build cache between these two commands by unifying them more would likely make &lt;code&gt;cargo check&lt;/code&gt; itself slightly slower, which might be undesirable to some users. It is possible that we might be able to find some middle ground to improve the status quo though. You can follow updates to this work in &lt;a href=&quot;https://github.com/rust-lang/cargo/issues/3501&quot;&gt;this issue&lt;/a&gt;.&lt;/p&gt;
  7973. &lt;p&gt;A related aspect is the latency of type checking in code editors and IDEs. Around 87% of respondents say that they use inline annotations in their editor as the primary mechanism of inspecting compiler errors, and around 33% of them consider waiting for these annotations to be a big blocker. In the open answers, we also received many reports of Rust Analyzer's performance and memory usage being a limiting factor.&lt;/p&gt;
  7974. &lt;p&gt;The maintainers of Rust Analyzer are working hard on improving its performance. Its caching system is &lt;a href=&quot;https://www.youtube.com/watch?v=tn6qwhMNBJo&quot;&gt;being improved&lt;/a&gt; to reduce analysis latency, the distributed builds of the editor are now &lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/19582&quot;&gt;optimized with PGO&lt;/a&gt;, which provided 15-20% performance wins, and work is underway to integrate the compiler's &lt;a href=&quot;https://github.com/rust-lang/rust-analyzer/pull/20329&quot;&gt;new trait solver&lt;/a&gt; into Rust Analyzer, which could eventually also result in increased performance.&lt;/p&gt;
  7975. &lt;p&gt;More than 35% users said that they consider the IDE and Cargo &lt;a href=&quot;https://github.com/rust-lang/cargo/issues/4282&quot;&gt;blocking one another&lt;/a&gt; to be a big problem. There is an existing workaround for this, where you can configure Rust Analyzer to use a different target directory than Cargo, at the cost of increased disk space usage. We realized that this workaround has not been documented in a very visible way, so we added it to the &lt;a href=&quot;https://rust-analyzer.github.io/book/faq.html#rust-analyzer-and-cargo-compete-over-the-build-lock&quot;&gt;FAQ section&lt;/a&gt; of the Rust Analyzer book.&lt;/p&gt;
  7976. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#clean-and-ci-builds&quot;&gt;&lt;/a&gt;
  7977. Clean and CI builds&lt;/h4&gt;
  7978. &lt;p&gt;Around 20% of participants responded that clean builds are a significant blocker for them. In order to improve their performance, you can try a recently introduced experimental Cargo and compiler option called &lt;a href=&quot;https://blog.rust-lang.org/inside-rust/2025/07/15/call-for-testing-hint-mostly-unused&quot;&gt;&lt;code&gt;hint-mostly-unused&lt;/code&gt;&lt;/a&gt;, which can in certain situations help improve the performance of clean builds, particularly if your dependencies contain a lot of code that might not actually be used by your crate(s).&lt;/p&gt;
  7979. &lt;p&gt;One area where clean builds might happen often is Continuous Integration (CI). 1495 respondents said that they use CI to build Rust code, and around 25% of them consider its performance to be a big blocker for them. However, almost 36% of respondents who consider CI build performance to be a big issue said that they do not use any caching in CI, which we found surprising. One explanation might be that the generated artifacts (the &lt;code&gt;target&lt;/code&gt; directory) is too large for effective caching, and runs into usage limits of CI providers, which is something that we saw mentioned repeatedly in the open answers section. We have recently introduced an experimental Cargo and compiler option called &lt;a href=&quot;https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#no-embed-metadata&quot;&gt;&lt;code&gt;-Zembed-metadata&lt;/code&gt;&lt;/a&gt; that is designed to reduce the size of the &lt;code&gt;target&lt;/code&gt; directories, and work is also underway to regularly &lt;a href=&quot;https://github.com/rust-lang/cargo/issues/13136&quot;&gt;garbage collect&lt;/a&gt; them. This might help with the disk space usage issue somewhat in the future.&lt;/p&gt;
  7980. &lt;p&gt;One additional way to significantly reduce disk usage is to reduce the amount of generated debug information, which brings us to the next section.&lt;/p&gt;
  7981. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#debug-information&quot;&gt;&lt;/a&gt;
  7982. Debug information&lt;/h3&gt;
  7983. &lt;p&gt;The default Cargo &lt;code&gt;dev&lt;/code&gt; profile generates full debug information (debuginfo) both for workspace crates and also all dependencies. This enables stepping through code with a debugger, but it also increases disk usage of the &lt;code&gt;target&lt;/code&gt; directory, and crucially it makes compilation and linking slower. This effect can be quite large, as our benchmarks show a possible improvement of &lt;a href=&quot;https://perf.rust-lang.org/compare.html?start=0d0f4eac8b98133e5da6d3604d86a8f3b5a67844&amp;amp;end=71ea9a0cacc3473c7b6852c17453259f74635c62&amp;amp;stat=cycles%3Au&amp;amp;doc=false&amp;amp;check=false&amp;amp;opt=false&quot;&gt;2-30% in cycle counts&lt;/a&gt; if we reduce the debuginfo level to &lt;code&gt;line-tables-only&lt;/code&gt; (which only generates enough debuginfo for backtraces to work), and the improvements are &lt;a href=&quot;https://perf.rust-lang.org/compare.html?start=bea625f3275e3c897dc965ed97a1d19ef7831f01&amp;amp;end=87c3e1ecd699573f7cb4c9074b8727956bd37a74&amp;amp;stat=cycles%3Au&amp;amp;check=false&amp;amp;opt=false&amp;amp;doc=false&quot;&gt;even larger&lt;/a&gt; if we disable debuginfo generation completely&lt;sup class=&quot;footnote-reference&quot; id=&quot;fr-lld-1&quot;&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#fn-lld&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
  7984. &lt;p&gt;However, if Rust developers debug their code after most builds, then this cost might be justified. We thus asked them how often they use a debugger to debug their Rust code:&lt;/p&gt;
  7985.  
  7986. &lt;div&gt;
  7987.    &lt;div class=&quot;bar-chart&quot; id=&quot;debugger&quot;&gt;&amp;lt;noscript&amp;gt;
  7988. &amp;lt;img alt=&quot;debugger&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/debugger.png&quot; /&amp;gt;
  7989. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  7990.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  7991.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/debugger.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/debugger.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  7992.    &lt;/div&gt;
  7993. &lt;/div&gt;
  7994.  
  7995. &lt;p&gt;Based on these results, it seems that the respondents of our survey do not actually use a debugger all that much&lt;sup class=&quot;footnote-reference&quot; id=&quot;fr-why-not-debug-1&quot;&gt;&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#fn-why-not-debug&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
  7996. &lt;p&gt;However, when we asked people if they require debuginfo to be generated by default, the responses were much less clear-cut:&lt;/p&gt;
  7997.  
  7998. &lt;div&gt;
  7999.    &lt;div class=&quot;bar-chart&quot; id=&quot;required-debuginfo&quot;&gt;&amp;lt;noscript&amp;gt;
  8000. &amp;lt;img alt=&quot;required-debuginfo&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/required-debuginfo.png&quot; /&amp;gt;
  8001. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  8002.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  8003.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/required-debuginfo.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/required-debuginfo.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  8004.    &lt;/div&gt;
  8005. &lt;/div&gt;
  8006.  
  8007. &lt;p&gt;This is the problem with changing defaults: it is challenging to improve the workflows of one user without regressing the workflow of another.  For completeness, here are the answers to the previous question partitioned on the answer to the &quot;How often do you use a debugger&quot; question:&lt;/p&gt;
  8008.  
  8009. &lt;div&gt;
  8010.    &lt;div class=&quot;class&quot; id=&quot;required-debuginfo-debugger&quot;&gt;&amp;lt;noscript&amp;gt;
  8011. &amp;lt;img alt=&quot;required-debuginfo-debugger&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/required-debuginfo-debugger.png&quot; /&amp;gt;
  8012. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  8013.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  8014.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/required-debuginfo-debugger.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/required-debuginfo-debugger.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  8015.    &lt;/div&gt;
  8016. &lt;/div&gt;
  8017.  
  8018. &lt;p&gt;It was surprising for us to see that around a quarter of respondents who (almost) never use a debugger still want to have full debuginfo generated by default.&lt;/p&gt;
  8019. &lt;p&gt;Of course, you can always disable debuginfo manually to improve your build performance, but not everyone knows about that option, and defaults matter a lot. The Cargo team is &lt;a href=&quot;https://github.com/rust-lang/cargo/issues/15931&quot;&gt;considering&lt;/a&gt; ways of changing the status quo, for example by reducing the level of generated debug information in the &lt;code&gt;dev&lt;/code&gt; profile, and introducing a new built-in profile designed for debugging.&lt;/p&gt;
  8020. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#workarounds-for-improving-build-performance&quot;&gt;&lt;/a&gt;
  8021. Workarounds for improving build performance&lt;/h3&gt;
  8022. &lt;p&gt;Build performance of Rust is affected by many different aspects, including the configuration of the build system (usually Cargo) and the Rust compiler, but also the organization of Rust crates and used source code patterns. There are thus several approaches that can be used to improve build performance by either using different configuration options or restructuring source code. We asked our respondents if they are even aware of such possibilities, whether they have tried them and how effective they were:&lt;/p&gt;
  8023.  
  8024. &lt;div&gt;
  8025.    &lt;div class=&quot;matrix-chart&quot; id=&quot;compile-time-improvement-mechanisms&quot;&gt;&amp;lt;noscript&amp;gt;
  8026. &amp;lt;img alt=&quot;compile-time-improvement-mechanisms&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/compile-time-improvement-mechanisms.png&quot; /&amp;gt;
  8027. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  8028.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  8029.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/compile-time-improvement-mechanisms.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/compile-time-improvement-mechanisms.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  8030.    &lt;/div&gt;
  8031. &lt;/div&gt;
  8032.  
  8033. &lt;p&gt;It seems that the most popular (and effective) mechanisms for improving build performance are reducing the number of dependencies and their activated features, and splitting larger crates into smaller crates. The most common way of improving build performance without making source code changes seems to be the usage of an alternative linker. It seems that especially the mold and LLD linkers are very popular:&lt;/p&gt;
  8034.  
  8035. &lt;div&gt;
  8036.    &lt;div class=&quot;bar-chart&quot; id=&quot;alternative-linker&quot;&gt;&amp;lt;noscript&amp;gt;
  8037. &amp;lt;img alt=&quot;alternative-linker&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/alternative-linker.png&quot; /&amp;gt;
  8038. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  8039.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  8040.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/alternative-linker.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/alternative-linker.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/alternative-linker-wordcloud.png&quot; target=&quot;_href_&quot; title=&quot;Download open answers as wordcloud PNG&quot;&gt;Wordcloud of open answers&lt;/a&gt;]&lt;/span&gt;
  8041.    &lt;/div&gt;
  8042. &lt;/div&gt;
  8043.  
  8044. &lt;p&gt;We have good news here! The most popular &lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt; Linux target will start using the LLD linker in the next Rust stable release, resulting in faster link times &lt;em&gt;by default&lt;/em&gt;. Over time, we will be able to evaluate how disruptive is this change to the overall Rust ecosystem, and whether we could e.g. switch to a different (even faster) linker.&lt;/p&gt;
  8045. &lt;h4&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#build-performance-guide&quot;&gt;&lt;/a&gt;
  8046. Build performance guide&lt;/h4&gt;
  8047. &lt;p&gt;We were surprised by the relatively large number of users who were unaware of some approaches for improving compilation times, in particular those that are very easy to try and typically do not require source code changes (such as reducing debuginfo or using a different linker or a codegen backend). Furthermore, almost 42% of respondents have not tried to use &lt;em&gt;any&lt;/em&gt; mechanism for improving build performance whatsoever. While this is not totally unexpected, as some of these mechanisms require using the nightly toolchain or making non-trivial changes to source code, we think that one the reasons is also simply that Rust developers might not know about these mechanisms being available. In the open answers, several people also noted that they would appreciate if there was some sort of official guidance from the Rust Project about such mechanisms for improving compile times.&lt;/p&gt;
  8048. &lt;p&gt;It should be noted that the mechanisms that we asked about are in fact workarounds that present various trade-offs, and these should always be carefully considered. Several people have expressed dissatisfaction with some of these workarounds in the open answers, as they find it unacceptable to modify their code (which could sometimes result e.g. in increased maintenance costs or worse runtime performance) just to achieve reasonable compile times. Nevertheless, these workarounds can still be incredibly useful in some cases.&lt;/p&gt;
  8049. &lt;p&gt;The feedback that we received shows that it might be beneficial to spread awareness of these mechanisms in the Rust community more, as some of them can make a really large difference in build performance, but also to candidly explain the trade-offs that they introduce. Even though several great resources that cover this topic already exist online, we decided to create an &lt;a href=&quot;https://github.com/rust-lang/cargo/pull/15924&quot;&gt;official guide&lt;/a&gt; for optimizing build performance (currently work-in-progress), which will likely be hosted in the &lt;a href=&quot;https://doc.rust-lang.org/cargo&quot;&gt;Cargo book&lt;/a&gt;. The aim of this guide is to increase the awareness of various mechanisms for improving build performance, and also provide a framework for evaluating their trade-offs.&lt;/p&gt;
  8050. &lt;p&gt;Our long-standing goal is to make compilation so fast that similar workarounds will not be necessary anymore for the vast majority of use-cases. However, there is no free lunch, and the combination of Rust's strong type system guarantees, its compilation model and also heavy focus on runtime performance often go against very fast (re)build performance, and might require usage of at least some workarounds. We hope that this guide will help Rust developers learn about them and evaluate them for their specific use-case.&lt;/p&gt;
  8051. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#understanding-why-builds-are-slow&quot;&gt;&lt;/a&gt;
  8052. Understanding why builds are slow&lt;/h3&gt;
  8053. &lt;p&gt;When Rust developers experience slow builds, it can be challenging to identify where exactly is the compilation process spending time, and what could be the bottleneck. It seems that only very few Rust developers leverage tools for profiling their builds:&lt;/p&gt;
  8054.  
  8055. &lt;div&gt;
  8056.    &lt;div class=&quot;matrix-chart&quot; id=&quot;profiling-tools&quot;&gt;&amp;lt;noscript&amp;gt;
  8057. &amp;lt;img alt=&quot;profiling-tools&quot; src=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/profiling-tools.png&quot; /&amp;gt;
  8058. &amp;lt;/noscript&amp;gt;&lt;/div&gt;
  8059.    &lt;div style=&quot;display: flex; margin-bottom: 10px;&quot;&gt;
  8060.        &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/profiling-tools.png&quot; target=&quot;_href_&quot; title=&quot;Download chart as PNG&quot;&gt;PNG&lt;/a&gt;]&lt;/span&gt; &lt;span&gt;[&lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/profiling-tools.svg&quot; target=&quot;_href_&quot; title=&quot;Download chart as SVG&quot;&gt;SVG&lt;/a&gt;]&lt;/span&gt;
  8061.    &lt;/div&gt;
  8062. &lt;/div&gt;
  8063.  
  8064. &lt;p&gt;This hardly comes as a surprise. There are currently not that many ways of intuitively understanding the performance characteristics of Cargo and &lt;code&gt;rustc&lt;/code&gt;. Some tools offer only a limited amount of information (e.g. &lt;code&gt;cargo build --timings&lt;/code&gt;), and the output of others (e.g. &lt;code&gt;-Zself-profile&lt;/code&gt;) is very hard to interpret without knowledge of the compiler internals.&lt;/p&gt;
  8065. &lt;p&gt;To slightly improve this situation, we have recently added support for displaying &lt;a href=&quot;https://github.com/rust-lang/cargo/pull/15923&quot;&gt;link times&lt;/a&gt; to the &lt;code&gt;cargo build --timings&lt;/code&gt; output, to provide more information about the possible bottleneck in crate compilation (note this feature has not been stabilized yet).&lt;/p&gt;
  8066. &lt;p&gt;Long-term, it would be great to have tooling that could help Rust developers diagnose compilation bottlenecks in their crates without them having to understand how the compiler works. For example, it could help answer questions such as &quot;Which code had to be recompiled after a given source change&quot; or &quot;Which (proc) macros take the longest time to expand or produce the largest output&quot;, and ideally even offer some actionable suggestions. We plan to work on such tooling, but it will take time to manifest.&lt;/p&gt;
  8067. &lt;p&gt;One approach that could help Rust compiler contributors understand why are Rust (re)builds slow &quot;in the wild&quot; is the opt-in &lt;a href=&quot;https://rust-lang.github.io/rust-project-goals/2025h1/metrics-initiative.html&quot;&gt;compilation metrics collection initiative&lt;/a&gt;.&lt;/p&gt;
  8068. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#what-s-next&quot;&gt;&lt;/a&gt;
  8069. What's next&lt;/h3&gt;
  8070. &lt;p&gt;There are more interesting things in the survey results, for example how do answers to selected questions differ based on the used operating system. You can examine the full results in the &lt;a href=&quot;https://raw.githubusercontent.com/rust-lang/surveys/main/surveys/2025/compiler-performance-survey/report/compiler-performance-2025-report.pdf&quot;&gt;full report PDF&lt;/a&gt;.&lt;/p&gt;
  8071. &lt;p&gt;We would like to thank once more everyone who has participated in our survey. It helped us understand which workflows are the most painful for Rust developers, and especially the open answers provided several great suggestions that we tried to act upon.&lt;/p&gt;
  8072. &lt;p&gt;Even though the Rust compiler is getting increasingly faster every year, we understand that many Rust developers require truly significant improvements to improve their productivity, rather than &quot;just&quot; incremental performance wins. Our goal for the future is to finally stabilize long-standing initiatives that could improve build performance a lot, such as the &lt;a href=&quot;https://rust-lang.github.io/rust-project-goals/2025h2/production-ready-cranelift.html&quot;&gt;Cranelift codegen backend&lt;/a&gt; or the &lt;a href=&quot;https://rust-lang.github.io/rust-project-goals/2025h2/parallel-front-end.html&quot;&gt;parallel compiler frontend&lt;/a&gt;. One such initiative (using a &lt;a href=&quot;https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable&quot;&gt;faster linker by default&lt;/a&gt;) will finally land soon, but the fact that it took many years shows how difficult it is to make such large cutting changes to the compilation process.&lt;/p&gt;
  8073. &lt;p&gt;There are other ambitious ideas for reducing (re)build times, such as &lt;a href=&quot;https://rust-lang.github.io/rust-project-goals/2025h2/relink-dont-rebuild.html&quot;&gt;avoiding unnecessary workspace rebuilds&lt;/a&gt; or e.g. using some form of &lt;a href=&quot;https://github.com/davidlattimore/wild&quot;&gt;incremental linking&lt;/a&gt;, but these will require a lot of work and design discussions.&lt;/p&gt;
  8074. &lt;p&gt;We know that some people are wondering why it takes so much time to achieve progress in improving the build performance of Rust. The answer is relatively simple. These changes require a lot of work, domain knowledge (that takes a relatively long time to acquire) and many discussions and code reviews, and the pool of people that have time and motivation to work on them or review these changes is very limited. Current compiler maintainers and contributors (many of whom work on the compiler as volunteers, without any funding) work very hard to keep up with maintaining the compiler and keeping it working with the high-quality bar that Rust developers expect, across many targets, platforms and operating systems. Introducing large structural changes, which are likely needed to reach massive performance improvements, would require a lot of concentrated effort and funding.&lt;/p&gt;
  8075.  
  8076.  
  8077.  
  8078. &lt;section class=&quot;footnotes&quot;&gt;
  8079. &lt;ol class=&quot;footnotes-list&quot;&gt;
  8080. &lt;li id=&quot;fn-lld&quot;&gt;
  8081. &lt;p&gt;This benchmark was already performed using the fast LLD linker. If a slower linker was used, the build time wins would likely be even larger. &lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#fr-lld-1&quot;&gt;↩&lt;/a&gt;&lt;/p&gt;
  8082. &lt;/li&gt;
  8083. &lt;li id=&quot;fn-why-not-debug&quot;&gt;
  8084. &lt;p&gt;Potentially because of the strong invariants upheld by the Rust type system, and partly also because the Rust debugging experience might not be optimal for many users, which is a feedback that we received in the &lt;a href=&quot;https://blog.rust-lang.org/2025/02/13/2024-State-Of-Rust-Survey-results/#challenges&quot;&gt;State of Rust 2024 survey&lt;/a&gt;. &lt;a href=&quot;https://blog.rust-lang.org/2025/09/10/rust-compiler-performance-survey-2025-results/#fr-why-not-debug-1&quot;&gt;↩&lt;/a&gt;&lt;/p&gt;
  8085. &lt;/li&gt;
  8086. &lt;/ol&gt;
  8087. &lt;/section&gt;</description>
  8088. <pubDate>Wed, 10 Sep 2025 00:00:00 +0000</pubDate>
  8089. <dc:creator>Jakub Beránek</dc:creator>
  8090. </item>
  8091. <item>
  8092. <title>Mozilla Open Policy &amp; Advocacy Blog: Mozilla Meetup: “The Future of Competition: How to Save the Open Web”</title>
  8093. <guid isPermaLink="false">https://blog.mozilla.org/netpolicy/?p=2501</guid>
  8094. <link>https://blog.mozilla.org/netpolicy/2025/09/09/mozilla-meetup-the-future-of-competition-how-to-save-the-open-web/</link>
  8095. <description>&lt;p&gt;The promise of an open and competitive internet hangs in the balance. From the future of AI agents to the underappreciated role of browsers and browser engines, the technological landscape continues to evolve. Getting the regulatory and enforcement backdrop right is critical: from competition bills in Congress to the EU’s DMA, the stakes for innovation, privacy and consumer choice have never been higher.&lt;/p&gt;
  8096. &lt;p&gt;&lt;br /&gt;
  8097. &lt;br /&gt;
  8098. &lt;br /&gt;
  8099. &lt;/p&gt;
  8100. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2025/09/09/mozilla-meetup-the-future-of-competition-how-to-save-the-open-web/&quot;&gt;Mozilla Meetup: “The Future of Competition: How to Save the Open Web”&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/netpolicy&quot;&gt;Open Policy &amp;amp; Advocacy&lt;/a&gt;.&lt;/p&gt;</description>
  8101. <pubDate>Tue, 09 Sep 2025 14:10:03 +0000</pubDate>
  8102. <dc:creator>Jenn Taylor Hodges</dc:creator>
  8103. </item>
  8104. <item>
  8105. <title>Wladimir Palant: A look at a P2P camera (LookCam app)</title>
  8106. <guid isPermaLink="true">https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/</guid>
  8107. <link>https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/</link>
  8108. <description>&lt;p&gt;I’ve got my hands on an internet-connected camera and decided to take a closer look, having already read about security issues with similar cameras. What I found far exceeded my expectations: fake access controls, bogus protocol encryption, completely unprotected cloud uploads and firmware riddled with security flaws. One could even say that these cameras are Murphy’s Law turned solid: everything that could be done wrong has been done wrong here. While there is considerable prior research on these and similar cameras that outlines some of the flaws, I felt that the combination of severe flaws is reason enough to publish an article of my own.&lt;/p&gt;
  8109. &lt;p&gt;My findings should apply to any camera that can be managed via the LookCam app. This includes cameras meant to be used with less popular apps of the same developer: tcam, CloudWayCam, VDP, AIBoxcam, IP System. Note that the LookCamPro app, while visually very similar, is technically quite different. It also uses the PPPP protocol for low-level communication but otherwise doesn’t seem to be related, and the corresponding devices are unlikely to suffer from the same flaws.&lt;/p&gt;
  8110. &lt;figure&gt;&lt;img alt=&quot;A graphic with the LookCam logo in the middle. Around it are arranged five devices with the respective camera locations marked: a radio clock, a power outlet, a light switch, a USB charger, a bulb socket.&quot; class=&quot;article-image&quot; height=&quot;423&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/devices.jpg&quot; width=&quot;600&quot; /&gt;&lt;/figure&gt;
  8111.  
  8112. &lt;p&gt;There seems to be little chance that things will improve with these cameras. I have no way of contacting either the hardware vendors or the developers behind the LookCam app. In fact, it looks like masking their identity was done on purpose here. But even if I could contact them, the cameras lack an update mechanism for their firmware. So fixing the devices already sold is impossible.&lt;/p&gt;
  8113. &lt;p&gt;I have no way of knowing how many of these cameras exist. The LookCam app is currently listed with almost 1.5 million downloads on Google Play however. An iPhone and a Windows version of the app are also available but no public statistics exist here.&lt;/p&gt;
  8114. &lt;div id=&quot;tocBox&quot;&gt;
  8115.  &lt;h5&gt;Contents&lt;/h5&gt;
  8116.  &lt;nav id=&quot;TableOfContents&quot;&gt;
  8117.  &lt;ul&gt;
  8118.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-highlights&quot;&gt;The highlights&lt;/a&gt;&lt;/li&gt;
  8119.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-hardware&quot;&gt;The hardware&lt;/a&gt;&lt;/li&gt;
  8120.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-lookcam-app&quot;&gt;The LookCam app&lt;/a&gt;&lt;/li&gt;
  8121.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-pppp-protocol&quot;&gt;The PPPP protocol&lt;/a&gt;
  8122.      &lt;ul&gt;
  8123.        &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-basics&quot;&gt;The basics&lt;/a&gt;&lt;/li&gt;
  8124.        &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-encryption&quot;&gt;The “encryption”&lt;/a&gt;&lt;/li&gt;
  8125.        &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-threat-model&quot;&gt;The threat model&lt;/a&gt;&lt;/li&gt;
  8126.      &lt;/ul&gt;
  8127.    &lt;/li&gt;
  8128.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-firmware&quot;&gt;The firmware&lt;/a&gt;&lt;/li&gt;
  8129.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#the-cloud&quot;&gt;The cloud&lt;/a&gt;&lt;/li&gt;
  8130.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#how-safe-are-device-ids&quot;&gt;How safe are device IDs?&lt;/a&gt;&lt;/li&gt;
  8131.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#recommendations&quot;&gt;Recommendations&lt;/a&gt;&lt;/li&gt;
  8132.    &lt;li&gt;&lt;a href=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/#further-reading&quot;&gt;Further reading&lt;/a&gt;&lt;/li&gt;
  8133.  &lt;/ul&gt;
  8134. &lt;/nav&gt;
  8135. &lt;/div&gt;
  8136.  
  8137. &lt;h3&gt;The highlights&lt;/h3&gt;
  8138. &lt;p&gt;The camera cannot be easily isolated from unauthorized access. It can either function as a WiFi access point, but setting a WiFi password isn’t possible. Or it can connect to an existing network, and then it will insist on being connected to the internet. If internet access is removed the camera will go into a reboot loop. So you have the choice of letting anybody in the vicinity access this camera or allowing it to be accessed from the internet.&lt;/p&gt;
  8139. &lt;p&gt;The communication of this camera is largely unencrypted. The underlying PPPP protocol supports “encryption” which is better described as obfuscation, but the LookCam app almost never makes use of it. Not that it would be of much help, the proprietary encryption algorithms being developed without any understanding of cryptography. These rely on static encryption keys which are trivially extracted from the app but should be easy enough to deduce even from merely observing some traffic.&lt;/p&gt;
  8140. &lt;p&gt;The camera firmware is riddled with buffer overflow issues which should be trivial to turn into arbitrary code execution. Protection mechanisms like DEP or ASLR might have been a hurdle but these are disabled. And while the app allows you to set an access password, the firmware doesn’t really enforce it. So access without knowing the password can be accomplished simply by modifying the app to skip the password checks.&lt;/p&gt;
  8141. &lt;p&gt;The only thing preventing complete compromise of any camera is the “secret” device ID which has to be known in order to establish a connection. And by “secret” I mean that device IDs can generally be enumerated but they are “secured” with a five letter verification code. Unlike with some similar cameras, the algorithm used to generate the verification code isn’t public knowledge yet. So somebody wishing to compromise as many cameras as possible would need to either guess the algorithm or guess the verification codes by trying out all possible combinations. I suspect that both approaches are viable.&lt;/p&gt;
  8142. &lt;p&gt;And while the devices themselves have access passwords which a future firmware version could in theory start verifying, the corresponding cloud service has no authentication beyond knowledge of the device ID. So any recordings uploaded to the cloud are accessible even if the device itself isn’t. Even if the camera owner hasn’t paid for the cloud service, anyone could book it for them if they know the device ID. The cloud configuration is managed by the server, so making the camera upload its recordings doesn’t require device access.&lt;/p&gt;
  8143. &lt;h3&gt;The hardware&lt;/h3&gt;
  8144. &lt;p&gt;Most cameras connecting to the LookCam app are being marketed as “spy cam” or “nanny cam.” These are made to look like radio clocks, USB chargers, bulb sockets, smoke detectors, even wall outlets. Most of the time their pretended functionality really works. In addition they have an almost invisible pinhole camera that can create remarkably good recordings. I’ve seen prices ranging from US$40 to hundreds of dollars.&lt;/p&gt;
  8145. &lt;p&gt;The marketing spin says that these cameras are meant to detect when your house is being robbed. Or maybe they allow you to observe your baby while it is in the next room. Of course, in reality people are far more inventive in their use of tiny cameras. Students &lt;a href=&quot;https://theconversation.com/students-are-using-smart-spy-technology-to-cheat-in-exams-59241&quot;&gt;discovered them for cheating in exams&lt;/a&gt;. Gamblers use them to &lt;a href=&quot;https://www.wired.com/story/miniature-camera-poker-cheating/&quot;&gt;get an advantage at card games&lt;/a&gt;. And then there is of course the matter of non-consentual video recordings. So next time you stay somewhere where you don’t quite trust the host you might want to search for “LookCam” on YouTube, just to get an idea of how to recognize such devices.&lt;/p&gt;
  8146. &lt;p&gt;The camera I had was based on the &lt;a href=&quot;http://anyka.net/en/productInfo.aspx?id=123&quot;&gt;Anyka AK39Ev330 hardware platform&lt;/a&gt;, essentially an ARM CPU with an attached pinhole camera. Presumably, other cameras connecting to the LookCam app are similar, even though there are some provisions for hardware differences in the firmware. The device looked very convincing, its main giveaway being unexpected heat development.&lt;/p&gt;
  8147. &lt;p&gt;All LookCam cameras I’ve seen were strictly noname devices, it is unclear who builds them. Given the variety of competing form factors I suspect that a number of hardware vendors are involved. Maybe there is one vendor producing the raw camera kit and several others who package it within the respective casings.&lt;/p&gt;
  8148. &lt;h3&gt;The LookCam app&lt;/h3&gt;
  8149. &lt;p&gt;The LookCam app can manage a number of cameras. Some people demonstrating the app on YouTube had around 50 of them, though I suspect that these are camera sellers and not regular users.&lt;/p&gt;
  8150. &lt;figure&gt;&lt;img alt=&quot;App screenshot, a screen titled “My Device.” It lists a number of cameras with stills on the left side. The cameras are titled something like G000001NRLXW. At the bottom of the screen are the options Video (selected), Photo, Files and More.&quot; class=&quot;article-image&quot; height=&quot;480&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/screenshot.png&quot; width=&quot;240&quot; /&gt;&amp;lt;figcaption&amp;gt;
  8151. LookCam app as seen in the example screenshot
  8152. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  8153.  
  8154. &lt;p&gt;While each camera can be given a custom name, its unique ID is always visible as well. For example, the first camera listed in the screenshot above has the ID GHBB-000001-NRLXW which the apps shortens into G000001NRLXW. Here GHBB is the device prefix: LookCam supports a number of these but only BHCC, FHBB and GHBB seem to exist in reality (abbreviated as B, F and G respectively). 000001 is the device number, each prefix can theoretically support a million devices. The final part is a five-letter verification code: NRLXW. This one has to be known for the device connection to succeed, it makes enumerating device IDs more difficult.&lt;/p&gt;
  8155. &lt;p&gt;Out of the box, the device is in access point mode: it provides a WiFi access point with the device ID used as wireless network name. You can connect to that access point, and LookCam will be able to find the camera via a network broadcast, allowing you to configure it. You might be inclined to leave the camera in access point mode but it is impossible to set a WiFi password. This means that anybody in the vicinity can connect to this WiFi network and access the camera through it. So there is no way around configuring the camera to connect to your network.&lt;/p&gt;
  8156. &lt;p&gt;Once the camera is connected to your network the P2P “magic” happens. LookCam app can still find the camera via a network broadcast. But it can also establish a connection when you are not on the same network. In other words: the camera can be accessed from the internet, assuming that someone knows its device ID.&lt;/p&gt;
  8157. &lt;p&gt;Exposing the camera to internet-based attacks might not be something that you want, with it being in principle perfectly capable of writing its recordings to an SD card. But if you deny it access to the internet (e.g. via a firewall rule) the camera will try to contact its server, fail, panic and reboot. It will keep rebooting until it receives a response from the server.&lt;/p&gt;
  8158. &lt;p&gt;One thing to note is also: the device ID is displayed in pretty much every screen of this app. So when users share screenshots or videos of the app (which they do often) they will inevitably expose the ID of their camera, allowing anyone in the world to connect to it. I’ve seen very few cases of people censoring the device ID, clearly most of them aren’t aware that it is sensitive information. The LookCam app definitely isn’t communicating that it is.&lt;/p&gt;
  8159. &lt;h3&gt;The PPPP protocol&lt;/h3&gt;
  8160. &lt;h4&gt;The basics&lt;/h4&gt;
  8161. &lt;p&gt;How can LookCam establish a connection to the camera having only its device ID? The app uses the PPPP protocol developed by the Chinese company CS2 Network. Supposedly, in 2019 CS2 Network had 300 customers with 20 million devices in total. This company supplies its customers with a code library and the corresponding server code which the customers can run as a black box. The idea of the protocol is providing an equivalent of the TCP protocol which implicitly locates a device by its ID and connects to it.&lt;/p&gt;
  8162. &lt;figure&gt;&lt;img alt=&quot;Screenshot of a presentation slide divided in two with TCP on the left and P2P on the right. Left side shows the calls to establish a TCP connection and write data, right side equivalent function calls with PPC_ prefix&quot; class=&quot;article-image&quot; height=&quot;267&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/slide_tcp_p2p.png&quot; width=&quot;475&quot; /&gt;&amp;lt;figcaption&amp;gt;
  8163. Slide from a CS2 Network sales pitch
  8164. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  8165.  
  8166. &lt;p&gt;&lt;em&gt;Side note&lt;/em&gt;: Whoever designed this protocol didn’t really understand TCP. For example, they tried to replicate the fault tolerance of TCP. But instead of making retransmissions an underlying protocol feature there are dozens of different (not duplicated but really different) retransmission loops throughout the library. Where TCP tries to detect network congestions and back off the PPPP protocol will send even more retransmitted messages, rendering suboptimal connections completely unusable.&lt;/p&gt;
  8167. &lt;p&gt;Despite being marketed as Peer-to-Peer (P2P) this protocol relies on centralized servers. Each device prefix is associated with a set of three servers, this being the protocol designers’ idea of high-availability infrastructure. Devices regularly send messages to all three servers, making sure that these are aware of the device’s IP address. When the LookCam app (client) wants to connect to a device, it also contacts all three servers to get the device’s IP address.&lt;/p&gt;
  8168. &lt;figure&gt;&lt;img alt=&quot;Screenshot of a presentation slide titled “High Availability Architecture.” The text says: Redundant P2P Servers, Flexible and Expandable Relay Servers&quot; class=&quot;article-image&quot; height=&quot;209&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/slide_high_availability.png&quot; width=&quot;362&quot; /&gt;&amp;lt;figcaption&amp;gt;
  8169. Slide from a CS2 Network sales pitch
  8170. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  8171.  
  8172. &lt;p&gt;The P2P part is the fact that device and client try to establish a direct connection instead of relaying all communication via a central server. The complicating factor here are firewalls which usually disallow direct connections. The developers didn’t like established approaches like &lt;a href=&quot;https://en.wikipedia.org/wiki/Universal_Plug_and_Play&quot;&gt;Universal Plug and Play (UPnP)&lt;/a&gt;, probably because these are often disabled for security reasons. So they used a trick called &lt;a href=&quot;https://en.wikipedia.org/wiki/UDP_hole_punching&quot;&gt;UDP hole punching&lt;/a&gt;. This involves guessing which port the firewall assigned to outgoing UDP traffic and then communicating with that port, so that the firewall considers incoming packets a response to previously sent UDP packets and allows them through.&lt;/p&gt;
  8173. &lt;p&gt;Does that always work? That’s doubtful. So the PPPP protocol allows for relay servers to be used as fallback, forwarding traffic from and to the device. But this direct communication presumably succeeds often enough to keep the traffic on PPPP servers low, saving costs.&lt;/p&gt;
  8174. &lt;p&gt;The FHBB and GHBB device prefixes are handled by the same set of servers, named the “mykj” network in the LookCam app internally. Same string appears in the name of the main class as well, indicating that it likely refers to the company developing the app. This seems to be a short form of “Meiyuan Keji,” a company name that translates as “Dollar Technology.” I couldn’t find any further information on this company however.&lt;/p&gt;
  8175. &lt;p&gt;The BHCC device prefix is handled by a different set of servers that the app calls the “hekai” network. The corresponding devices appear to be marketed in China only.&lt;/p&gt;
  8176. &lt;h4&gt;The “encryption”&lt;/h4&gt;
  8177. &lt;p&gt;With potentially very sensitive data being transmitted one would hope that the data is safely encrypted in transit. The TCP protocol outsources this task to additional layers like TLS. The PPPP protocol on the other hand has built-in “encryption,” in fact even two different encryption mechanisms.&lt;/p&gt;
  8178. &lt;p&gt;First there is the blanket encryption of all transmitted messages. The corresponding function is aptly named &lt;code&gt;P2P_Proprietary_Encrypt&lt;/code&gt; and it is in fact a very proprietary encryption algorithm. To my untrained eye there are a few issues with it:&lt;/p&gt;
  8179. &lt;ul&gt;
  8180. &lt;li&gt;It is optional, with many networks choosing not to use it (like all networks supported by LookCam).&lt;/li&gt;
  8181. &lt;li&gt;When present, the encryption key is part of the “init string” which is hardcoded in the app. It is trivial to extract from the application, even a file viewer will do if you know what to look for.&lt;/li&gt;
  8182. &lt;li&gt;Even if the encryption key weren’t easily extracted, it is mashed into four bytes which become the effective key. So there are merely four billion possible keys.&lt;/li&gt;
  8183. &lt;li&gt;Even if it weren’t possible to just go through all possible encryption keys, the algorithm can be trivially attacked via a &lt;a href=&quot;https://en.wikipedia.org/wiki/Known-plaintext_attack&quot;&gt;known-plaintext attack&lt;/a&gt;. It’s sometimes even possible to deduce the effective key by passively observing a single four bytes &lt;code&gt;MSG_HELLO&lt;/code&gt; message (it is known that the first four bytes message sent to port 32100 has the plaintext &lt;code&gt;F1 00 00 00&lt;/code&gt;).&lt;/li&gt;
  8184. &lt;/ul&gt;
  8185. &lt;p&gt;In addition to that, some messages get special treatment. For example, the &lt;code&gt;MSG_REPORT_SESSION_READY&lt;/code&gt; message is generally encrypted via &lt;code&gt;P2P_Proprietary_Encrypt&lt;/code&gt; function with a key that is hardcoded in the CS2 library and has the same value in every app I checked.&lt;/p&gt;
  8186. &lt;p&gt;Some messages employ a different encryption method. In case of the networks supported by LookCam it is only the &lt;code&gt;MSG_DEV_LGN_CRC&lt;/code&gt; message (device registering with the server) that is used instead of the plaintext &lt;code&gt;MSG_DEV_LGN&lt;/code&gt; message. As this message is sent by the device, the corresponding encryption key is only present in the device firmware, not in the application. I didn’t bother checking whether the server would still accept the unencrypted &lt;code&gt;MSG_DEV_LGN&lt;/code&gt; message.&lt;/p&gt;
  8187. &lt;p&gt;The encryption function responsible here is &lt;code&gt;PPPP_CRCEnc&lt;/code&gt;. No, this isn’t a cyclic redundancy check (CRC). It’s rather an encryption function that will extend the plaintext by a four bytes padding. The decryptor will validate the padding, presumably that’s the reason for the name.&lt;/p&gt;
  8188. &lt;p&gt;Of course, this still doesn’t make it an authenticated encryption scheme, yet the &lt;a href=&quot;https://en.wikipedia.org/wiki/Padding_oracle_attack&quot;&gt;padding oracle attack&lt;/a&gt; is really the least of its worries. While there is a complicated selection approach, it effectively results in a sequence of bytes that the plaintext is XOR’ed with. &lt;em&gt;Same&lt;/em&gt; sequence for every single message being encrypted in this way. Wikipedia has the following to say on the &lt;a href=&quot;https://en.wikipedia.org/wiki/XOR_cipher#Use_and_security&quot;&gt;security of XOR ciphers&lt;/a&gt;:&lt;/p&gt;
  8189. &lt;blockquote&gt;
  8190. &lt;p&gt;By itself, using a constant repeating key, a simple XOR cipher can trivially be broken using frequency analysis. If the content of any message can be guessed or otherwise known then the key can be revealed.&lt;/p&gt;&lt;/blockquote&gt;
  8191. &lt;p&gt;Well, yes. That’s what we have here.&lt;/p&gt;
  8192. &lt;p&gt;It’s doubtful that any of these encryption algorithms can deter even a barely determined attacker. But a blanket encryption with &lt;code&gt;P2P_Proprietary_Encrypt&lt;/code&gt; (which LookCam doesn’t enable) would have three effects:&lt;/p&gt;
  8193. &lt;ol&gt;
  8194. &lt;li&gt;Network traffic is obfuscated, making the contents of transmitted messages not immediately obvious.&lt;/li&gt;
  8195. &lt;li&gt;Vulnerable devices cannot be discovered on the local network using the &lt;a href=&quot;https://github.com/pmarrapese/iot/tree/master/p2p/lansearch&quot;&gt;script developed by Paul Marrapese&lt;/a&gt;. This script relies on devices responding to an unencrypted search request.&lt;/li&gt;
  8196. &lt;li&gt;P2P servers can no longer be discovered easily and won’t show up on Shodan for example. This discovery method relies on servers responding to an unencrypted &lt;code&gt;MSG_HELLO&lt;/code&gt; message.&lt;/li&gt;
  8197. &lt;/ol&gt;
  8198. &lt;h4&gt;The threat model&lt;/h4&gt;
  8199. &lt;p&gt;It is obvious that the designers of the PPPP protocol don’t understand cryptography, yet for some reason they don’t want to use established solutions either. It cannot even be about performance because AES is supported in hardware on these devices. But why for example this strange choice of encrypting a particular message while keeping the encryption of highly private data optional? Turns out, this is due to the threat model used by the PPPP protocol designers.&lt;/p&gt;
  8200. &lt;figure&gt;&lt;img alt=&quot;Screenshot of a presentation slide containing yellow text: Malicious hacker can make thousands of Fake Device by writing a software program (As you know, the cost may be less than 1 USD), however. It then continues with red text: It may cause thousands pcs of your product to malfunction, thus cost hundred thousands.&quot; class=&quot;article-image&quot; height=&quot;221&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/slide_fake_devices.png&quot; width=&quot;380&quot; /&gt;&amp;lt;figcaption&amp;gt;
  8201. Slide from a CS2 Network sales pitch
  8202. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  8203.  
  8204. &lt;p&gt;As a CS2 Network presentation deck shows, their threat model isn’t concerned about data leaks. The concern is rather denial-of-service attacks caused by registering fake devices. And that’s why this one message enjoys additional encryption. Not that I really understand the concern here, since the supposed hacker would still have to generate valid device IDs somehow. And if they can do that – well, them bringing the server down should really be the least concern.&lt;/p&gt;
  8205. &lt;p&gt;But wait, there is another security layer here!&lt;/p&gt;
  8206. &lt;figure&gt;&lt;img alt=&quot;Screenshot of a presentation slide titled “Encrypted P2P Server IP String.” The text says: The encrypted string is given to platform owner only. Without correct string, Fake Device can’t use P2P API to reach P2P Server. The API require encrypt P2P Server IP String, but not raw IP String.&quot; class=&quot;article-image&quot; height=&quot;281&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/slide_init_string.png&quot; width=&quot;383&quot; /&gt;&amp;lt;figcaption&amp;gt;
  8207. Slide from a CS2 Network sales pitch
  8208. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  8209.  
  8210. &lt;p&gt;This is about the “init string” already mentioned in the context of encryption keys above. It also contains the IP addresses of the servers, mildly obfuscated. While these were “given to platform owner only,” these are necessarily contained in the LookCam app:&lt;/p&gt;
  8211. &lt;figure&gt;&lt;img alt=&quot;Screenshot of a source code listing with four fields g_hekai_init_string, g_mykj_init_string, g_ppcs_init_string, g_rtos_init_string. All four values are strings consisting of upper-case letters.&quot; class=&quot;article-image&quot; height=&quot;132&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/initstrings.png&quot; width=&quot;607&quot; /&gt;&lt;/figure&gt;
  8212.  
  8213. &lt;p&gt;Some other apps contain dozens of such init strings, allowing them to deal with many different networks. So the threat model of the PPPP protocol cannot imagine someone extracting the “encrypted P2P server IP string” from the app. It cannot imagine someone reverse engineering the (trivial) obfuscation used here. And it definitely cannot imagine someone reverse engineering the protocol, so that they can communicate with the servers via “raw IP string” instead of their obfuscated one. &lt;em&gt;Note&lt;/em&gt;: The latter has happened on several documented occasions already, e.g. &lt;a href=&quot;https://www.elastic.co/security-labs/storm-on-the-horizon#building-a-p2p-client&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
  8214. &lt;p&gt;These underlying assumptions become even more obvious on this slide:&lt;/p&gt;
  8215. &lt;figure&gt;&lt;img alt=&quot;Screenshot of a presentation slide titled “Worry about security?” The text says: Super Device can not spy any data it Relayed (No API for this)&quot; class=&quot;article-image&quot; height=&quot;188&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/slide_spying.png&quot; width=&quot;412&quot; /&gt;&amp;lt;figcaption&amp;gt;
  8216. Slide from a CS2 Network sales pitch
  8217. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  8218.  
  8219. &lt;p&gt;Yes, the only imaginable way to read out network data is via the API of their library. With a threat model like this, it isn’t surprising that the protocol makes all the wrong choices security-wise.&lt;/p&gt;
  8220. &lt;h3&gt;The firmware&lt;/h3&gt;
  8221. &lt;p&gt;Once a connection is etablished the LookCam app and the camera will exchange JSON-encoded messages like the following:&lt;/p&gt;
  8222. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;
  8223. &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;  &lt;span class=&quot;nt&quot;&gt;&quot;cmd&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s2&quot;&gt;&quot;LoginDev&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;
  8224. &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;  &lt;span class=&quot;nt&quot;&gt;&quot;pwd&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s2&quot;&gt;&quot;123456&quot;&lt;/span&gt;
  8225. &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;
  8226. &lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;A &lt;a href=&quot;https://www.dcs.warwick.ac.uk/~fenghao/files/hidden_camera.pdf&quot;&gt;paper from the Warwick University&lt;/a&gt; already took a closer look at the firmware and discovered something surprising. The LookCam app will send a &lt;code&gt;LoginDev&lt;/code&gt; command like above to check whether the correct access password is being used for the device. But sending this command is entirely optional, and the firmware will happily accept other commands without a “login”!&lt;/p&gt;
  8227. &lt;p&gt;The LookCam app will also send the access password along with every other command yet this password isn’t checked by the firmware either. I tried adding a trivial modification to the LookCam app which made it ignore the result of the &lt;code&gt;LoginDev&lt;/code&gt; command. And this in fact bypassed the authentication completely, allowing me to access my camera despite a wrong password.&lt;/p&gt;
  8228. &lt;p&gt;I could also confirm their finding that the &lt;code&gt;DownloadFile&lt;/code&gt; command will read arbitrary files, allowing me to extract the firmware of my camera with the approach described in the paper. They even describe a trivial Remote Code Execution vulnerability which I also found in my firmware: that firmware often relies on running shell commands for tasks that could be easily done in its C language code.&lt;/p&gt;
  8229. &lt;p&gt;This clearly isn’t the only Remote Code Execution vulnerability however. Here is some fairly typical code for this firmware:&lt;/p&gt;
  8230. &lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;chroma&quot; tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-c&quot;&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kt&quot;&gt;char&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;256&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;]&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;buf&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;
  8231. &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;kt&quot;&gt;char&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;*&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;cmd&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;cJSON_GetObjectItem&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;request&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;&quot;cmd&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;-&amp;gt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;valuestring&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;;&lt;/span&gt;
  8232. &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;nf&quot;&gt;memset&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;buf&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;mi&quot;&gt;0&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;k&quot;&gt;sizeof&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;buf&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;));&lt;/span&gt;
  8233. &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;cl&quot;&gt;&lt;span class=&quot;nf&quot;&gt;memcpy&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;buf&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;cmd&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;nf&quot;&gt;strlen&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;cmd&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;));&lt;/span&gt;
  8234. &lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This code copies a string (pointlessly but this isn’t the issue here). It completely fails to consider the size of the target buffer, going by the size of the incoming data instead. So any command larger than 255 bytes will cause a &lt;a href=&quot;https://en.wikipedia.org/wiki/Buffer_overflow&quot;&gt;buffer overflow&lt;/a&gt;. And there is no stack canary here, Data Execution Prevention (DEP) and Address Space Layout Randomization (ASLR) are disabled, so nothing prevents this buffer overflow from being turned into Remote Code Execution.&lt;/p&gt;
  8235. &lt;p&gt;Finally, I’ve discovered that the &lt;code&gt;searchWiFiList&lt;/code&gt; command will produce the list of WiFi networks visible to the camera. These by itself often already allow a good guess as to where the camera is located. In combination with a &lt;a href=&quot;https://developers.google.com/maps/documentation/geolocation/overview&quot;&gt;geolocation service&lt;/a&gt; these will typically narrow down the camera’s position to a radius of only a few dozen meters.&lt;/p&gt;
  8236. &lt;p&gt;The only complication here: most geolocation services require not the network names but the MAC addresses of the access points. The MAC addresses aren’t part of the response data however. But: &lt;code&gt;searchWiFiList&lt;/code&gt; works by running &lt;code&gt;iwlist&lt;/code&gt; shell command and storing the complete output in &lt;code&gt;/tmp/wifi_scan.txt&lt;/code&gt; file. It reads this file but does not remove it. This means that the file can subsequently be downloaded via &lt;code&gt;DownloadFile&lt;/code&gt; command (allows reading arbitrary files as mentioned above) and that one contains full data including MAC addresses of all access points. So somebody who happened to learn the device ID can not only access the video stream but also find out where exactly this footage is being recorded.&lt;/p&gt;
  8237. &lt;p&gt;The camera I’ve been looking at is running firmware version 2023-11-22. Is there a newer version, maybe one that fixes the password checks or the already published Remote Code Execution vulnerability? I have no idea. If the firmware for these cameras is available somewhere online then I cannot find it. I’ve also been looking for some kind of update functionality in these devices. But there is only a generic script from the Anyka SDK which isn’t usable for anyone other than maybe the hardware vendor.&lt;/p&gt;
  8238. &lt;h3&gt;The cloud&lt;/h3&gt;
  8239. &lt;p&gt;When looking at the firmware I noticed some code uploading 5 MiB data chunks to &lt;code&gt;api.l040z.com&lt;/code&gt; (or &lt;code&gt;apicn.l040z.com&lt;/code&gt; if you happen to own a &lt;code&gt;BHCC&lt;/code&gt; device). Now uploading &lt;em&gt;exactly&lt;/em&gt; 5 MiB is weird (this size is hardcoded) but inspecting the LookCam app confirmed it: this is cloud functionality, and the firmware regularly uploads videos in this way. At least it does that when cloud functionality is enabled.&lt;/p&gt;
  8240. &lt;p&gt;First thing worth noting: while the cloud server uses regular HTTP rather than some exotic protocol, all connections to it are generally unencrypted. The firmware simply lacks a TLS library it could use, and so the server doesn’t bother with supporting TLS. Meaning for example: if you happen to use their cloud functionality your ISP better be very trustworthy because it can see all the data your camera sends to the LookCam cloud. In fact, your ISP could even run its own “cloud server” and the camera will happily send your recorded videos to it.&lt;/p&gt;
  8241. &lt;p&gt;Anyone dare a guess what the app developers mean by “financial-grade encryption scheme” here? Is it worse or better than military-grade encryption?&lt;/p&gt;
  8242. &lt;figure&gt;&lt;img alt=&quot;Screenshot containing two text sections. The section above it titled “Safe storage” and reads: The video data is stored in the cloud, even if the device is offline or lost. Can also view previous recordings. The section below is titled “Privacy double encryption” and reads: Using financial-grade encryption scheme, data is transmitted from data to Transfer data from transfer data from transfer.&quot; class=&quot;article-image&quot; height=&quot;452&quot; src=&quot;https://palant.info/2025/09/08/a-look-at-a-p2p-camera-lookcam-app/cloud.png&quot; width=&quot;385&quot; /&gt;&amp;lt;figcaption&amp;gt;
  8243. Screenshot from the LookCam app
  8244. &amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
  8245.  
  8246. &lt;p&gt;Second interesting finding: the cloud server has no authentication whatsoever. The camera only needs to know its device ID when uploading to the cloud. And the LookCam app – well, any cloud-related requests here also require device ID only. If somebody happens to learn your device ID they will gain full access to your cloud storage.&lt;/p&gt;
  8247. &lt;p&gt;Now you might think that you can simply skip paying for the cloud service which, depending on the package you book, can come for as much as $40 per month. But this doesn’t mean that you are on the safe side because you aren’t the one controlling the cloud functionality on your device, the cloud server is. Every time the device boots up it sends a request to &lt;code&gt;http://api.l040z.com/camera/signurl&lt;/code&gt; and the response tells it whether cloud functionality needs to be enabled.&lt;/p&gt;
  8248. &lt;p&gt;So if LookCam developers decide that they want to see what your camera is doing (or if Chinese authorities become interested in that), they can always adjust that server response and the camera will start uploading video snapshots. You won’t even notice anything because the LookCam app checks cloud configuration by requesting &lt;code&gt;http://api.l040z.com/app/cloudConfig&lt;/code&gt; which can remain unchanged.&lt;/p&gt;
  8249. &lt;p&gt;And they aren’t the only ones who can enable the cloud functionality of your device. Anybody who happens to know your device ID can buy a cloud package for it. This way they can get access to your video recordings without ever accessing your device directly. And you will only notice the cloud functionality being active if you happen to go to the corresponding tab in the LookCam app.&lt;/p&gt;
  8250. &lt;h3&gt;How safe are device IDs?&lt;/h3&gt;
  8251. &lt;p&gt;Now that you are aware of device IDs being highly sensitive data, you certainly won’t upload screenshots containing them to social media. Does that mean that your camera is safe because nobody other than you knows its ID?&lt;/p&gt;
  8252. &lt;p&gt;The short answer is: you don’t know that. First of all, you simply don’t know who already has your device ID. Did the shop that sold you the camera write the ID down? Did they maybe record a sales pitch featuring your camera before they sold it to you? Did somebody notice your camera’s device ID show up in the list of WiFi networks when it was running in access point mode? Did anybody coming to your home run a &lt;a href=&quot;https://github.com/pmarrapese/iot/tree/master/p2p/lansearch&quot;&gt;script to discover PPPP devices on the network&lt;/a&gt;? Yes, all of that might seem unlikely, yet it should be reason enough to wonder whether your camera’s recordings are really as private as they should be.&lt;/p&gt;
  8253. &lt;p&gt;Then there is the issue of unencrypted data transfers. Whenever you connect to your camera from outside your home network the LookCam app will send all data unencrypted – including the device ID. Do you do that when connected to public WiFi? At work? In a vacation home? You don’t know who else is listening.&lt;/p&gt;
  8254. &lt;p&gt;And finally there is the matter of verification codes which are the only mechanism preventing somebody from enumerating all device IDs. How difficult would it be to guess a verification code? Verification codes seem to use 22 letters (all Latin uppercase letters but A, I, O, Q). With five letters this means around 5 million possible combinations. According to Paul Marrapese &lt;a href=&quot;https://media.defcon.org/DEF%20CON%2028/DEF%20CON%20Safe%20Mode%20presentations/DEF%20CON%20Safe%20Mode%20-%20Paul%20Marrapese%20-%20Abusing%20P2P%20to%20Hack%203%20Million%20Cameras%20Ain%27t%20Nobody%20Got%20Time%20for%20NAT.pdf&quot;&gt;PPPP servers don’t implement rate limiting&lt;/a&gt; (page 33), making trying out all these combinations perfectly realistic – maybe not for all possible device IDs but definitely for some.&lt;/p&gt;
  8255. &lt;p&gt;But that resource-intensive approach is only necessary as long as the algorithm used to generate verification codes is a secret. Yet we have to assume that at least CS2 Network’s 300 customers have access to that algorithm, given that their server software somehow validates device IDs. Are they all trustworthy? How much would it cost to become a “customer” simply in order to learn that algorithm?&lt;/p&gt;
  8256. &lt;p&gt;And even if we are willing to assume that CS2 Network runs proper background checks to ensure that their algorithm remains a secret: how difficult would it be to guess that algorithm? I found a number of device IDs online, and my primitive analysis of their verification codes indicates that these aren’t distributed equally. There is a noticeable affinity for certain prime numbers, so the algorithm behind them is likely a similar hack job as the other CS2 Network algorithms, throwing in mathematical operations and table lookups semi-randomly to make things look complicated. How long would this approach hold if somebody with actual cryptanalysis knowledge decided to figure this out?&lt;/p&gt;
  8257. &lt;h3&gt;Recommendations&lt;/h3&gt;
  8258. &lt;p&gt;So if you happen to own one of these cameras, what does all this mean to you? Even if you never disclosed the camera’s device ID yourself, you cannot rely on it staying a secret. And this means that whatever your camera is recording is no longer private.&lt;/p&gt;
  8259. &lt;p&gt;Are you using it as a security camera? Your security camera might now inform potential thieves of the stuff that you have standing around and the times when you leave home. It will also let them know where exactly you live.&lt;/p&gt;
  8260. &lt;p&gt;Are you using it to keep an eye on your child? Just… don’t. Even if you think that you yourself have a right to violate your child’s privacy, you really don’t want anybody else to watch.&lt;/p&gt;
  8261. &lt;p&gt;And even if you “have nothing to hide”: somebody could compromise the camera in order to hack other devices on your network or to simply make it part of a botnet. Such things &lt;a href=&quot;https://www.bleepingcomputer.com/news/security/hackers-target-critical-zero-day-vulnerability-in-ptz-cameras/&quot;&gt;happened before&lt;/a&gt;, many times actually.&lt;/p&gt;
  8262. &lt;p&gt;So the best solution is to dispose of this camera ASAP. Don’t sell it please because this only moves the problem to the next person. The main question is: how do you know that the camera you get instead will do better? I can only think of one indicator: if you want to access the camera from outside your network it should involve explicit setup steps, likely changing router configuration. The camera shouldn’t just expose itself to the internet automatically.&lt;/p&gt;
  8263. &lt;p&gt;But if you actually paid hundreds of dollars for that camera and dumping it isn’t an option: running it in a safe manner is complicated. As I mentioned already, simply blocking internet access for the camera won’t work. This can be worked around but it’s complex enough to be not worth doing. You should be better off by installing a &lt;a href=&quot;https://github.com/Nemobi/Anyka/&quot;&gt;custom firmware&lt;/a&gt;. I haven’t tried it but at least this one looks like somebody actually thought about security.&lt;/p&gt;
  8264. &lt;h3&gt;Further reading&lt;/h3&gt;
  8265. &lt;p&gt;As far as I am aware, the first research on the PPPP protocol was &lt;a href=&quot;https://hacked.camera/&quot;&gt;published by Paul Marrapese in 2019&lt;/a&gt;. He found a number of vulnerabilities, including one brand of cameras shipping their algorithm to generate verification codes with their client application. Knowing this algorithm, device IDs could be enumerated easily. Paul used this flaw to display the locations of millions of affected devices. His DEF CON talk is linked from the website and well worth watching.&lt;/p&gt;
  8266. &lt;p&gt;&lt;strong&gt;Edit&lt;/strong&gt; (2025-09-15): I was wrong, there is at the very least &lt;a href=&quot;https://www.slideshare.net/slideshow/iot-security-is-a-nightmare-but-what-is-the-real-risk/65213457&quot;&gt;this early analysis of the protocol by Zoltán Balázs (2016)&lt;/a&gt; (starting at page 29) and &lt;a href=&quot;https://pierrekim.github.io/blog/2017-03-08-camera-goahead-0day.html&quot;&gt;some research into a particular brand of PPPP-based cameras by Pierre Kim (2017)&lt;/a&gt;.&lt;/p&gt;
  8267. &lt;p&gt;A &lt;a href=&quot;https://www.dcs.warwick.ac.uk/~fenghao/files/hidden_camera.pdf&quot;&gt;paper from the Warwick University (2023)&lt;/a&gt; researched LookCam app specifically. In additions to some vulnerabilities I mentioned here it contains a number of details on how these cameras operate.&lt;/p&gt;
  8268. &lt;p&gt;This &lt;a href=&quot;https://www.elastic.co/security-labs/storm-on-the-horizon&quot;&gt;Elastic Labs article (2024)&lt;/a&gt; took a close look at some other PPPP-based cameras, finding a number of issues.&lt;/p&gt;
  8269. &lt;p&gt;The &lt;a href=&quot;https://prezi.com/5cztk-98izyc/cs2-network-p2p/&quot;&gt;CS2 Network sales presentation (2016)&lt;/a&gt; offers a fascinating look into the thinking of PPPP protocol designers and into how their system was meant to work.&lt;/p&gt;</description>
  8270. <pubDate>Mon, 08 Sep 2025 13:00:50 +0000</pubDate>
  8271. </item>
  8272. <item>
  8273. <title>Mozilla Thunderbird: VIDEO: Thunderbird Accessibility Study</title>
  8274. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3769</guid>
  8275. <link>https://blog.thunderbird.net/2025/09/video-thunderbird-accessibility-study/</link>
  8276. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/09/blog-banner-community-hours1-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  8277. &lt;p&gt;Welcome back to another edition of the Community Office Hours! This month, we’re taking a closer look at accessibility in the Thunderbird desktop and mobile apps. We’re chatting with Rebecca Taylor and Solange Valverde, members of our designer, about a recent accessibility (often shortened as a11y) study. We wanted to find out where Thunderbird was doing well, and where we could improve. Rebecca and Solange walk us through the study and answer our questions!&lt;/p&gt;
  8278.  
  8279.  
  8280.  
  8281. &lt;p&gt;We’ll be back next month with the latest Community Office Hours! If you have a suggestion for a topic or team you’d love us to cover, please let us know in the comments!&lt;/p&gt;
  8282.  
  8283.  
  8284.  
  8285. &lt;h3&gt;August Office Hours: Thunderbird Accessibility Study&lt;/h3&gt;
  8286.  
  8287.  
  8288.  
  8289. &lt;p&gt;The Thunderbird Team wants to make desktop and mobile apps that maximizes everyone’s productivity and freedom. This means making Thunderbird accessible for all of our users, and the first step is finding where we can do better. Thanks to our relationship with Mozilla, our design team commissioned a study with &lt;a href=&quot;https://makeitfable.com/&quot;&gt;Fable&lt;/a&gt;, who connects companies building inclusive products to experienced testers with disabilities. We asked participants to evaluate the Thunderbird desktop app using assistive tech, including screen readers, alternative navigation, and magnification. And we also asked a user on the cognitive spectrum to evaluate how our language, layouts, and reminders helped or hindered their use of the app.&lt;/p&gt;
  8290.  
  8291.  
  8292.  
  8293. &lt;p&gt;Members of the design team then conducted 60 minute moderated interviews with study participants. In these talks, participants pointed out where they struggled with accessibility roadblocks, and what strategies they used to try and work through them. &lt;/p&gt;
  8294.  
  8295.  
  8296.  
  8297. &lt;h3&gt;Screen Reader Users&lt;/h3&gt;
  8298.  
  8299.  
  8300.  
  8301. &lt;p&gt;Screen readers convert on-screen text to either speech or Braille, and help blind or low-vision users navigate and access digital content. Our study participants, many of whom switch between multiple screen readers, let us know where Thunderbird falls short.&lt;/p&gt;
  8302.  
  8303.  
  8304.  
  8305. &lt;p&gt;Some issues were common to all screen readers. Keyboard shortcuts didn’t follow common norms, and workflows in search and filter results made for a confusing experience. Thunderbird could benefit from a table view with &lt;a href=&quot;https://www.a11yproject.com/posts/getting-started-aria/&quot;&gt;ARIA&lt;/a&gt;, a W3C specification created to improve accessibility. &lt;/p&gt;
  8306.  
  8307.  
  8308.  
  8309. &lt;p&gt;Other issues were specific to the individual screen reader programs. In Narrator, for example, expected confirmation for actions like moving messages was missing, and the screen reader didn’t recognize menu stage changes in submenus. In JAWS, meanwhile, message bodies were unreadable in email and compose windows with Braille display, and filter menus opened silently, not announcing the content or state to the user. Finally, with NVDA, users noted confusing structures and organization that lacked the structure and context they expected, as well as poor content prioritization.&lt;/p&gt;
  8310.  
  8311.  
  8312.  
  8313. &lt;h3&gt;Cognitive Usability&lt;/h3&gt;
  8314.  
  8315.  
  8316.  
  8317. &lt;p&gt;In a previous office hours, we talked about how we wanted to make Thunderbird more cognitively accessible with our work on the &lt;a href=&quot;https://blog.thunderbird.net/2024/01/january-2024-thunderbird-community-office-hours-how-to-join-us/&quot;&gt;Message Context Menu&lt;/a&gt;. Cognition relates to how we think, learn, understand, remember, and pay attention, and clear language, regular layouts, and meaningful reminders all improve cognitive accessibility. Our cognitive accessibility tester expressed concerns about a lack of a quick, non-technical setup, imbalances in our whitespace, and unpredictable layout controls, among other issues.&lt;/p&gt;
  8318.  
  8319.  
  8320.  
  8321. &lt;h3&gt;Alternative Navigation and Magnification&lt;/h3&gt;
  8322.  
  8323.  
  8324.  
  8325. &lt;p&gt;Our alternative navigation users tested how well they could use Thunderbird with voice controls and eye tracking software. Our voice control testers found room for improvement with menu action labels, better autofocus shift when scrolling through emails, and a larger font size for more comfortable voice-driven use. Likewise, our eye tracking software tester found issues with font sizes.  They also noted concerns with composition workflow and focus, too-small controls, and a drag-and-drop bug.&lt;/p&gt;
  8326.  
  8327.  
  8328.  
  8329. &lt;p&gt;Our magnification tester found where we could improve visual contrast and pane layouts. They also found off-screen elements could steal focus from new messages, and that folder paths and hierarchies could use more clarification. &lt;/p&gt;
  8330.  
  8331.  
  8332.  
  8333. &lt;h3&gt;Conclusions and Next Steps&lt;/h3&gt;
  8334.  
  8335.  
  8336.  
  8337. &lt;p&gt;We’re incredibly grateful for the insights we learned from this study on the many aspects of accessibility we want to improve in all of our apps. We want to thank Mozilla for their helping us take the next step in accessibility research, and Fable for providing a fantastic platform for accessibility testing. We’re also so grateful to our study participants for all their time and sharing their perspectives, concerns, and insights.&lt;/p&gt;
  8338.  
  8339.  
  8340.  
  8341. &lt;p&gt;This is far from the end of our accessibility journey. We’re looking forward to working what we learned in this study into deeper research and ultimately our desktop roadmap. We can’t wait to start accessibility research on our mobile apps. And we hope this study can help other open source projects start their own accessibility research to improve their projects.&lt;/p&gt;
  8342.  
  8343.  
  8344.  
  8345. &lt;p&gt;One way you can get involved is to report accessibility bugs on the desktop app. Go to the &lt;a href=&quot;https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird&quot;&gt;Thunderbird section on Bugzilla&lt;/a&gt;, and under ‘Component’ select ‘Disability Access.’ Additionally, click ‘Show Advanced Fields’ and enter ‘access’ into the ‘Details &amp;gt; Keywords’ section. Add screenshots when possible. Be sure to describe the bug so others can try and reproduce the it for better troubleshooting. &lt;/p&gt;
  8346.  
  8347.  
  8348.  
  8349. &lt;p&gt;If you want to learn more about our accessibility efforts, please join our User Experience mailing list! If you think you’re ready to get involved, please join our dedicated Matrix channel. We hope you help us make Thunderbird available, and accessible, everywhere!&lt;/p&gt;
  8350.  
  8351.  
  8352.  
  8353. &lt;h4&gt;VIDEO (Also &lt;a href=&quot;https://tilvids.com/w/3ymZQj1ikB9hdtpMmaP836&quot;&gt;on Peertube&lt;/a&gt;):&lt;/h4&gt;
  8354.  
  8355.  
  8356.  
  8357. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  8358.  
  8359. &lt;/div&gt;&lt;/figure&gt;
  8360.  
  8361.  
  8362.  
  8363. &lt;h3&gt;Slides:&lt;/h3&gt;
  8364.  
  8365.  
  8366.  
  8367. &lt;div class=&quot;wp-block-file&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/09/ThunderbirdCommunityHoursAccessibilityReport-compressed.pdf&quot; id=&quot;wp-block-file--media-2d726133-12fc-4117-a5e6-734962ae66d2&quot;&gt;ThunderbirdCommunityHoursAccessibilityReport-compressed&lt;/a&gt;&lt;a class=&quot;wp-block-file__button wp-element-button&quot; href=&quot;https://blog.thunderbird.net/files/2025/09/ThunderbirdCommunityHoursAccessibilityReport-compressed.pdf&quot;&gt;Download&lt;/a&gt;&lt;/div&gt;
  8368.  
  8369.  
  8370.  
  8371. &lt;h3&gt;Resources:&lt;/h3&gt;
  8372.  
  8373.  
  8374.  
  8375. &lt;ul&gt;
  8376. &lt;li&gt;Bugzilla Disability Access bugs and enhancement requests: https://mzl.la/41jrnuv&lt;/li&gt;
  8377.  
  8378.  
  8379.  
  8380. &lt;li&gt;Fable: https://makeitfable.com/&lt;/li&gt;
  8381.  
  8382.  
  8383.  
  8384. &lt;li&gt;Thunderbird A11y Matrix channel: https://matrix.to/#/%23tb-a11y:mozilla.org&lt;/li&gt;
  8385.  
  8386.  
  8387.  
  8388. &lt;li&gt;Thunderbird User Experience Mailing List: https://thunderbird.topicbox.com/groups/ux&lt;/li&gt;
  8389.  
  8390.  
  8391.  
  8392. &lt;li&gt;Thunderbird suggested tools and resources for Accessibility: https://bolt.thunderbird.net/8b179dbfd/p/33ddcb-accessibility&lt;/li&gt;
  8393.  
  8394.  
  8395.  
  8396. &lt;li&gt;Config 2024: Pitching accessible design like a pro: https://www.youtube.com/watch?v=NoHIDWF0d6I&lt;/li&gt;
  8397. &lt;/ul&gt;
  8398. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/09/video-thunderbird-accessibility-study/&quot;&gt;VIDEO: Thunderbird Accessibility Study&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  8399. <pubDate>Fri, 05 Sep 2025 15:14:54 +0000</pubDate>
  8400. <dc:creator>Monica Ayhens-Madon</dc:creator>
  8401. </item>
  8402. <item>
  8403. <title>Mozilla Future Releases Blog: Firefox 32-bit Linux Support to End in 2026</title>
  8404. <guid isPermaLink="false">https://blog.mozilla.org/futurereleases/?p=2722</guid>
  8405. <link>https://blog.mozilla.org/futurereleases/2025/09/05/firefox-32-bit-linux-support-to-end-in-2026/</link>
  8406. <description>&lt;p&gt;For many years, Mozilla has continued to provide Firefox for 32-bit Linux systems long after most other browsers and operating systems ended support. We made this choice because we care deeply about keeping Firefox available to as many people as possible, helping our users extend the life of their hardware and reduce unnecessary obsolescence.&lt;/p&gt;
  8407. &lt;p&gt;Today, however, 32-bit Linux (on x86) is no longer widely supported by the vast majority of Linux distributions, and maintaining Firefox on this platform has become increasingly difficult and unreliable. To focus our efforts on delivering the best and most modern Firefox, we are &lt;b&gt;ending support for 32-bit x86 Linux&lt;/b&gt; with the release of Firefox 144 (or to rephrase, Firefox 145 will not have 32-bit Linux support).&lt;/p&gt;
  8408. &lt;p&gt;If you are currently using Firefox on a 32-bit x86 Linux system, we strongly encourage you to move to a 64-bit operating system and install the 64-bit version of Firefox, which will continue to be supported and updated.&lt;/p&gt;
  8409. &lt;p&gt;For users who cannot transition immediately, Firefox ESR 140 will remain available — including 32-bit builds — and will continue to receive security updates until at least &lt;b&gt;September 2026&lt;/b&gt;.&lt;/p&gt;
  8410. &lt;p&gt;[Updated on 2025-09-09 to clarify the affected builds are 32-bit x86]&lt;/p&gt;
  8411. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/futurereleases/2025/09/05/firefox-32-bit-linux-support-to-end-in-2026/&quot;&gt;Firefox 32-bit Linux Support to End in 2026&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/futurereleases&quot;&gt;Future Releases&lt;/a&gt;.&lt;/p&gt;</description>
  8412. <pubDate>Fri, 05 Sep 2025 09:18:30 +0000</pubDate>
  8413. <dc:creator>Julien Cristau and Sylvestre Ledru</dc:creator>
  8414. </item>
  8415. <item>
  8416. <title>Karl Dubost: Did you open a bug?</title>
  8417. <guid isPermaLink="false">tag:www.otsukare.info,2025-09-05:/2025/09/05/open-bug-webdev</guid>
  8418. <link>https://www.otsukare.info/2025/09/05/open-bug-webdev</link>
  8419. <description>&lt;p&gt;&lt;img alt=&quot;Wall with broken tiles.&quot; src=&quot;https://www.otsukare.info/images/20250905-bugs-reports.jpg&quot; /&gt;&lt;/p&gt;
  8420. &lt;p&gt;If you are a webdev…&lt;/p&gt;
  8421. &lt;p&gt;and you had an issue on the website you were working on, because of a web browser…&lt;/p&gt;
  8422. &lt;p&gt;Why didn't you file a bug on a browser bug tracker? What are the frictions?&lt;/p&gt;
  8423. &lt;p&gt;(not asking those who did, because they already do the right thing ❤️)&lt;/p&gt;
  8424. &lt;ul&gt;
  8425. &lt;li&gt;&lt;a href=&quot;https://issues.chromium.org/issues?q=status:open&quot;&gt;Blink bug tracker&lt;/a&gt;&lt;/li&gt;
  8426. &lt;li&gt;&lt;a href=&quot;https://bugzilla.mozilla.org&quot;&gt;Gecko bug tracker&lt;/a&gt;&lt;/li&gt;
  8427. &lt;li&gt;&lt;a href=&quot;https://bugs.webkit.org/&quot;&gt;WebKit bug tracker&lt;/a&gt;&lt;/li&gt;
  8428. &lt;/ul&gt;
  8429. &lt;p&gt;Or &lt;a href=&quot;https://webcompat.com/&quot;&gt;Webcompat.com&lt;/a&gt;. A cross-browsers bug tracker.&lt;/p&gt;
  8430. &lt;p&gt;PS: do not hesitate to ask around you, your colleagues, mates, etc.&lt;/p&gt;
  8431. &lt;p&gt;This was &lt;a href=&quot;https://mastodon.cloud/@karlcow/115150006126574667&quot;&gt;initially posted on mastodon&lt;/a&gt;, you can contact me there. Also on &lt;a href=&quot;https://github.com/karlcow&quot;&gt;GitHub&lt;/a&gt;.&lt;/p&gt;
  8432. &lt;p&gt;Otsukare!&lt;/p&gt;</description>
  8433. <pubDate>Fri, 05 Sep 2025 08:50:00 +0000</pubDate>
  8434. <dc:creator>Karl Dubost</dc:creator>
  8435. </item>
  8436. <item>
  8437. <title>Mozilla Future Releases Blog: Extended Firefox ESR 115 Support for Windows 7, 8, and 8.1 and macOS 10.12-10.14</title>
  8438. <guid isPermaLink="false">https://blog.mozilla.org/futurereleases/?p=2723</guid>
  8439. <link>https://blog.mozilla.org/futurereleases/2025/09/04/firefox-esr-115-support-for-windows-7-8-and-8-1-and-old-mac-os-versions-extended-until-march-2026/</link>
  8440. <description>&lt;p&gt;Mozilla has continued to support Firefox on Windows 7, Windows 8, and Windows 8.1 long after these operating systems reached end of life, helping users extend the life of their devices and reduce unnecessary obsolescence. We originally announced that security updates for &lt;a href=&quot;https://www.firefox.com/download/all/desktop-esr/&quot;&gt;Firefox ESR&lt;/a&gt; 115 would end in September 2024, later extending that into 2025.&lt;/p&gt;
  8441. &lt;p&gt;Today, we are extending support once again: &lt;b&gt;Firefox ESR 115 will continue to receive security updates on Windows 7, 8, and 8.1 until March 2026&lt;/b&gt;. This extension gives users more time to transition while ensuring critical security protections remain available. We still strongly encourage upgrading to a supported operating system to access the latest Firefox features and maintain long-term stability.&lt;/p&gt;
  8442. &lt;p&gt;Note that this extension is also applicable for macOS 10.12-10.14 users running Firefox ESR 115.&lt;/p&gt;
  8443. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/futurereleases/2025/09/04/firefox-esr-115-support-for-windows-7-8-and-8-1-and-old-mac-os-versions-extended-until-march-2026/&quot;&gt;Extended Firefox ESR 115 Support for Windows 7, 8, and 8.1 and macOS 10.12-10.14&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.mozilla.org/futurereleases&quot;&gt;Future Releases&lt;/a&gt;.&lt;/p&gt;</description>
  8444. <pubDate>Thu, 04 Sep 2025 14:50:41 +0000</pubDate>
  8445. <dc:creator>Ryan VanderMeulen</dc:creator>
  8446. </item>
  8447. <item>
  8448. <title>The Rust Programming Language Blog: Welcoming the Rust Innovation Lab</title>
  8449. <guid isPermaLink="true">https://blog.rust-lang.org/2025/09/03/welcoming-the-rust-innovation-lab/</guid>
  8450. <link>https://blog.rust-lang.org/2025/09/03/welcoming-the-rust-innovation-lab/</link>
  8451. <description>&lt;p&gt;TL;DR: &lt;a href=&quot;https://github.com/rustls/rustls&quot;&gt;Rustls&lt;/a&gt; is the inaugural project of the &lt;a href=&quot;https://rustfoundation.org/rust-innovation-lab&quot;&gt;Rust Innovation Lab&lt;/a&gt;, which is a new home for Rust projects under the Rust Foundation.&lt;/p&gt;
  8452. &lt;p&gt;At the Rust Foundation's August meeting, the Project Directors and the rest of the Rust Foundation board voted to approve &lt;a href=&quot;https://github.com/rustls/rustls&quot;&gt;Rustls&lt;/a&gt; as the first project housed under the newly formed Rust Innovation Lab. Prior to the vote, the Project Directors consulted with the Leadership Council who confirmed the Project's support for this initiative.&lt;/p&gt;
  8453. &lt;p&gt;The Rust Innovation Lab (RIL) is designed to provide support for funded Rust-based open source projects from the Rust Foundation in the form of governance, legal, networking, marketing, and administration, while keeping the technical direction solely in the hands of the current maintainers. As with the other work of the Rust Foundation (e.g. its many existing &lt;a href=&quot;https://rustfoundation.org/initiatives/&quot;&gt;initiatives&lt;/a&gt;), the purpose of the RIL is to strengthen the Rust ecosystem generally.&lt;/p&gt;
  8454. &lt;p&gt;The Foundation has been working behind the scenes to establish the Rust Innovation Lab, which includes setting up infrastructure under the Foundation to ensure smooth transition for Rustls into RIL. More details are available in &lt;a href=&quot;https://rustfoundation.org/media/rust-foundation-launches-rust-innovation-lab-with-rustls-as-inaugural-project/&quot;&gt;the Foundation's announcement&lt;/a&gt; and on &lt;a href=&quot;https://rustfoundation.org/rust-innovation-lab&quot;&gt;the Rust Innovation Lab's page&lt;/a&gt;.&lt;/p&gt;
  8455. &lt;p&gt;We are all excited by the formation of the Rust Innovation Lab. The support this initiative will provide to Rustls (and, eventually, other important projects that are using Rust) will improve software security for the entire industry. The Rust Project is grateful for the support of the Rust Foundation corporate members who are making this initiative possible for the benefit of everyone.&lt;/p&gt;
  8456. &lt;p&gt;More information on the criteria for projects wishing to become part of the RIL and the process for applying will be coming soon. The Project Directors and Leadership Council have been and will continue working with the Foundation to communicate information, questions, and feedback with the Rust community about the RIL as the details are worked out.&lt;/p&gt;</description>
  8457. <pubDate>Wed, 03 Sep 2025 00:00:00 +0000</pubDate>
  8458. <dc:creator>Carol Nichols</dc:creator>
  8459. </item>
  8460. <item>
  8461. <title>The Rust Programming Language Blog: Faster linking times with 1.90.0 stable on Linux using the LLD linker</title>
  8462. <guid isPermaLink="true">https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/</guid>
  8463. <link>https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/</link>
  8464. <description>&lt;p&gt;TL;DR: rustc will start using the LLD linker by default on the &lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt; target starting with the next stable release (1.90.0, scheduled for 2025-09-18), which should significantly reduce linking times. Test it out on beta now, and please report any encountered issues.&lt;/p&gt;
  8465. &lt;h4 id=&quot;some-context&quot;&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/#some-context&quot;&gt;&lt;/a&gt;
  8466. Some context&lt;/h4&gt;
  8467. &lt;p&gt;Linking time is often a big part of compilation time. When rustc needs to build a binary or a shared library, it will usually call the default linker installed on the system to do that (this can be changed on the command-line or by the target for which the code is compiled).&lt;/p&gt;
  8468. &lt;p&gt;The linkers do an important job, with concerns about stability, backwards-compatibility and so on. For these and other reasons, on the most popular operating systems they usually are older programs, designed when computers only had a single core. So, they usually tend to be slow on a modern machine. For example, when building ripgrep 13 in debug mode on Linux, roughly half of the time is actually spent in the linker.&lt;/p&gt;
  8469. &lt;p&gt;There are different linkers, however, and the usual advice to improve linking times is to use one of these newer and faster linkers, like LLVM's &lt;a href=&quot;https://lld.llvm.org/&quot;&gt;&lt;code&gt;lld&lt;/code&gt;&lt;/a&gt; or Rui Ueyama's &lt;a href=&quot;https://github.com/rui314/mold&quot;&gt;&lt;code&gt;mold&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
  8470. &lt;p&gt;Some of Rust's wasm and aarch64 targets already use &lt;code&gt;lld&lt;/code&gt; by default. When using rustup, rustc ships with a version of &lt;code&gt;lld&lt;/code&gt; for this purpose. When CI builds LLVM to use in the compiler, it also builds the linker and packages it. It's referred to as &lt;code&gt;rust-lld&lt;/code&gt; to avoid colliding with any &lt;code&gt;lld&lt;/code&gt; already installed on the user's machine.&lt;/p&gt;
  8471. &lt;p&gt;Since improvements to linking times are substantial, it would be a good default to use in the most popular targets. This has been discussed for a long time, for example in issues &lt;a href=&quot;https://github.com/rust-lang/rust/issues/39915&quot;&gt;#39915&lt;/a&gt; and &lt;a href=&quot;https://github.com/rust-lang/rust/issues/71515&quot;&gt;#71515&lt;/a&gt;.&lt;/p&gt;
  8472. &lt;p&gt;To expand our testing, we have enabled rustc to use &lt;code&gt;rust-lld&lt;/code&gt; by default on nightly, &lt;a href=&quot;https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html&quot;&gt;in May 2024&lt;/a&gt;. No major issues have been reported since then.&lt;/p&gt;
  8473. &lt;p&gt;We believe we've done all the internal testing that we could, on CI, crater, on our benchmarking infrastructure and on nightly, and plan to enable &lt;code&gt;rust-lld&lt;/code&gt; to be the linker used by default on &lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt; for stable builds in 1.90.0.&lt;/p&gt;
  8474. &lt;h4 id=&quot;benefits&quot;&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/#benefits&quot;&gt;&lt;/a&gt;
  8475. Benefits&lt;/h4&gt;
  8476. &lt;p&gt;While this also enables the compiler to use more linker features in the future, the most immediate benefit is much improved linking times.&lt;/p&gt;
  8477. &lt;p&gt;Here are more details from the ripgrep example mentioned above: for an incremental rebuild, linking is reduced 7x, resulting in a 40% reduction in end-to-end compilation times. For a from-scratch debug build, it is a 20% improvement.&lt;/p&gt;
  8478. &lt;p&gt;&lt;img alt=&quot;Before/after comparison of a ripgrep incremental debug build&quot; src=&quot;https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/ripgrep-comparison.png&quot; /&gt;&lt;/p&gt;
  8479. &lt;p&gt;Most binaries should see some improvements here, but it's especially significant with e.g. bigger binaries, or for incremental rebuilds, or when involving debuginfo. These usually see bottlenecks in the linker.&lt;/p&gt;
  8480. &lt;p&gt;Here's &lt;a href=&quot;https://perf.rust-lang.org/compare.html?start=b3e117044c7f707293edc040edb93e7ec5f7040a&amp;amp;end=baed03c51a68376c1789cc373581eea0daf89967&amp;amp;stat=instructions%3Au&amp;amp;tab=compile&quot;&gt;a link&lt;/a&gt; to the complete results from our benchmarks.&lt;/p&gt;
  8481. &lt;h4 id=&quot;possible-drawbacks&quot;&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/#possible-drawbacks&quot;&gt;&lt;/a&gt;
  8482. Possible drawbacks&lt;/h4&gt;
  8483. &lt;p&gt;From our prior testing, we don't really expect issues to happen in practice. It is a drop-in replacement for the vast majority of cases, but &lt;code&gt;lld&lt;/code&gt; is not &lt;em&gt;bug-for-bug&lt;/em&gt; compatible with GNU ld.&lt;/p&gt;
  8484. &lt;p&gt;In any case, using &lt;code&gt;rust-lld&lt;/code&gt; can be disabled if any problem occurs: use the &lt;code&gt;-C linker-features=-lld&lt;/code&gt; flag to revert to using the system's default linker.&lt;/p&gt;
  8485. &lt;p&gt;Some crates somehow relying on these differences could need additional link args, though we also expect this to be quite rare. Let us know if you encounter problems, by &lt;a href=&quot;https://github.com/rust-lang/rust/issues/new/choose&quot;&gt;opening an issue&lt;/a&gt; on GitHub.&lt;/p&gt;
  8486. &lt;p&gt;Some of the big gains in performance come from parallelism, which could be undesirable in resource-constrained environments, or for heavy projects that are already reaching hardware limits.&lt;/p&gt;
  8487. &lt;h4 id=&quot;summary-and-call-for-testing&quot;&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/#summary-and-call-for-testing&quot;&gt;&lt;/a&gt;
  8488. Summary, and call for testing&lt;/h4&gt;
  8489. &lt;p&gt;rustc will use &lt;code&gt;rust-lld&lt;/code&gt; on &lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt;, starting with the 1.90.0 stable release, for much improved linking times. Rust 1.90.0 will be released next month, on the 18th of September 2025.&lt;/p&gt;
  8490. &lt;p&gt;This linker change is already available on the current beta (&lt;code&gt;1.90.0-beta.6&lt;/code&gt;). To help everyone prepare for this landing on stable, please test your projects on beta and let us know if you encounter problems, by &lt;a href=&quot;https://github.com/rust-lang/rust/issues/new/choose&quot;&gt;opening an issue&lt;/a&gt; on GitHub.&lt;/p&gt;
  8491. &lt;p&gt;If that happens, you can revert to the default linker with the &lt;code&gt;-C linker-features=-lld&lt;/code&gt; flag. Either by adding it to the usual &lt;code&gt;RUSTFLAGS&lt;/code&gt; environment variable, or to a project's &lt;a href=&quot;https://doc.rust-lang.org/cargo/reference/config.html&quot;&gt;&lt;code&gt;.cargo/config.toml&lt;/code&gt;&lt;/a&gt; configuration file,
  8492. like so:&lt;/p&gt;
  8493. &lt;pre class=&quot;language-toml z-code&quot;&gt;&lt;code class=&quot;language-toml&quot;&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-table z-begin z-toml&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;z-meta z-tag z-table z-toml&quot;&gt;&lt;span class=&quot;z-entity z-name z-table z-toml&quot;&gt;target&lt;/span&gt;&lt;span class=&quot;z-punctuation z-separator z-table z-toml&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;z-entity z-name z-table z-toml&quot;&gt;x86_64-unknown-linux-gnu&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-definition z-table z-end z-toml&quot;&gt;]&lt;/span&gt;
  8494. &lt;/span&gt;&lt;span class=&quot;z-source z-toml&quot;&gt;&lt;span class=&quot;z-meta z-tag z-key z-toml&quot;&gt;&lt;span class=&quot;z-entity z-name z-tag z-toml&quot;&gt;rustflags&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;z-punctuation z-definition z-key-value z-toml&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;z-punctuation z-definition z-array z-begin z-toml&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;z-string z-quoted z-double z-basic z-toml&quot;&gt;&lt;span class=&quot;z-punctuation z-definition z-string z-begin z-toml&quot;&gt;&quot;&lt;/span&gt;-Clinker-features=-lld&lt;span class=&quot;z-punctuation z-definition z-string z-end z-toml&quot;&gt;&quot;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;z-punctuation z-definition z-array z-end z-toml&quot;&gt;]&lt;/span&gt;
  8495. &lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;</description>
  8496. <pubDate>Mon, 01 Sep 2025 00:00:00 +0000</pubDate>
  8497. <dc:creator>Rémy Rakic</dc:creator>
  8498. </item>
  8499. <item>
  8500. <title>Mozilla Thunderbird: Thunderbird Monthly Release 142 Recap</title>
  8501. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3743</guid>
  8502. <link>https://blog.thunderbird.net/2025/08/thunderbird-monthly-release-142-recap/</link>
  8503. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2025/08/blog-banner-desktop-month-release-series-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  8504. &lt;p&gt;We’re back with another exciting Monthly Release recap! Thunderbird 142.0 brings a host of user-requested features and important bug fixes that make your email experience smoother and more reliable. From better folder management to smarter PDF handling, this release focuses on the details that matter most to your daily workflow.&lt;/p&gt;
  8505.  
  8506.  
  8507.  
  8508. &lt;p&gt;&lt;strong&gt;A quick reminder&lt;/strong&gt; – these updates are for users on our &lt;strong&gt;monthly Thunderbird Release channel&lt;/strong&gt;. For our users still on the ESR (Extended Standard Release) channel, these updates won’t land until next July 2026. For more information on the differences between the channels and how to make the switch:&lt;/p&gt;
  8509.  
  8510.  
  8511.  
  8512. &lt;ul&gt;
  8513. &lt;li&gt;Visit the Release download portal:&lt;a href=&quot;https://updates.thunderbird.net/thunderbird/128.0/monthly/&quot;&gt; Thunderbird Release Page&lt;/a&gt;.&lt;/li&gt;
  8514.  
  8515.  
  8516.  
  8517. &lt;li&gt;&lt;a href=&quot;https://support.mozilla.org/en-US/kb/thunderbird-release&quot;&gt;Explore detailed comparisons&lt;/a&gt; and migration guides.&lt;/li&gt;
  8518. &lt;/ul&gt;
  8519.  
  8520.  
  8521.  
  8522. &lt;p&gt;Now let’s dive into &lt;strong&gt;what’s new in 142.0!&lt;/strong&gt;&lt;/p&gt;
  8523.  
  8524.  
  8525.  
  8526. &lt;h3&gt;&lt;strong&gt;New Features:&lt;/strong&gt;&lt;/h3&gt;
  8527.  
  8528.  
  8529.  
  8530. &lt;h4&gt;&lt;strong&gt;Reset Manual Folder Sorting&lt;/strong&gt; &lt;/h4&gt;
  8531.  
  8532.  
  8533.  
  8534. &lt;p class=&quot;has-small-font-size&quot;&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1972710&quot;&gt;Bug 1972710&lt;/a&gt;&lt;/p&gt;
  8535.  
  8536.  
  8537.  
  8538. &lt;p&gt;Ever tweaked your folder order and wished you could start fresh? We hear you! Thunderbird 142 introduces a simple way to reset your folder sorting back to defaults. &lt;/p&gt;
  8539.  
  8540.  
  8541.  
  8542. &lt;p&gt;&lt;strong&gt;Benefits:&lt;/strong&gt;&lt;/p&gt;
  8543.  
  8544.  
  8545.  
  8546. &lt;ul&gt;
  8547. &lt;li&gt;The new Reset Folder Order option lets users right‑click an account in the Folder Pane to instantly clear any custom sorting. &lt;/li&gt;
  8548.  
  8549.  
  8550.  
  8551. &lt;li&gt;Provides a quick clean slate and avoids manually dragging folders back to default positions.&lt;/li&gt;
  8552. &lt;/ul&gt;
  8553.  
  8554.  
  8555.  
  8556. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/08/reset-folder-sort.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3751&quot; height=&quot;555&quot; src=&quot;https://blog.thunderbird.net/files/2025/08/reset-folder-sort.png&quot; width=&quot;416&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  8557.  
  8558.  
  8559.  
  8560. &lt;p&gt;&lt;em&gt;Note: This feature resets sorting order but doesn’t restore folders that were moved inside different parent folders.&lt;/em&gt;&lt;/p&gt;
  8561.  
  8562.  
  8563.  
  8564. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 25px;&quot;&gt;&lt;/div&gt;
  8565.  
  8566.  
  8567.  
  8568. &lt;h4&gt;&lt;strong&gt;PDF Signatures and Attachment Handling&lt;/strong&gt;&lt;/h4&gt;
  8569.  
  8570.  
  8571.  
  8572. &lt;p class=&quot;has-small-font-size&quot;&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1970796&quot;&gt;Bug 1970796&lt;/a&gt;&lt;/p&gt;
  8573.  
  8574.  
  8575.  
  8576. &lt;p&gt;Thunderbird now lets you &lt;strong&gt;add visual signatures to PDF attachments&lt;/strong&gt; opened inside the app. This update brings Thunderbird in line with modern PDF functionality, making it easier to handle contracts, forms, and other documents without leaving your inbox.&lt;/p&gt;
  8577.  
  8578.  
  8579.  
  8580. &lt;p&gt;&lt;strong&gt;Benefits:&lt;/strong&gt;&lt;/p&gt;
  8581.  
  8582.  
  8583.  
  8584. &lt;ul&gt;
  8585. &lt;li&gt;Add a handwritten-style visual signature directly in Thunderbird.&lt;/li&gt;
  8586.  
  8587.  
  8588.  
  8589. &lt;li&gt;No need for external tools to sign simple PDF documents.&lt;/li&gt;
  8590.  
  8591.  
  8592.  
  8593. &lt;li&gt;Keeps everyday document handling faster and more convenient.&lt;/li&gt;
  8594. &lt;/ul&gt;
  8595.  
  8596.  
  8597.  
  8598. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://blog.thunderbird.net/files/2025/08/PDF-Signature.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-3758&quot; height=&quot;345&quot; src=&quot;https://blog.thunderbird.net/files/2025/08/PDF-Signature.png&quot; width=&quot;1867&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  8599.  
  8600.  
  8601.  
  8602. &lt;ul&gt;
  8603. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 25px;&quot;&gt;&lt;/div&gt;
  8604. &lt;/ul&gt;
  8605.  
  8606.  
  8607.  
  8608. &lt;h4&gt;&lt;strong&gt;Custom OAuth Support for Add-on developers&lt;/strong&gt;&lt;/h4&gt;
  8609.  
  8610.  
  8611.  
  8612. &lt;p class=&quot;has-small-font-size&quot;&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1967370&quot;&gt;Bug 1967370&lt;/a&gt;&lt;/p&gt;
  8613.  
  8614.  
  8615.  
  8616. &lt;p&gt;New add-on API support for OAuth client registration now allows developers and organizations to add custom OAuth providers at runtime. Instead of requiring changes in Thunderbird’s core code, an add-on can handle the setup. &lt;/p&gt;
  8617.  
  8618.  
  8619.  
  8620. &lt;p&gt;&lt;strong&gt;Benefits:&lt;/strong&gt;&lt;/p&gt;
  8621.  
  8622.  
  8623.  
  8624. &lt;ul&gt;
  8625. &lt;li&gt;Supports custom OAuth providers through add-ons.&lt;/li&gt;
  8626.  
  8627.  
  8628.  
  8629. &lt;li&gt;Works with enterprise policies for organizational deployments.&lt;/li&gt;
  8630.  
  8631.  
  8632.  
  8633. &lt;li&gt;Simplifies integration with unique authentication systems.&lt;/li&gt;
  8634. &lt;/ul&gt;
  8635.  
  8636.  
  8637.  
  8638. &lt;ul&gt;
  8639. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 30px;&quot;&gt;&lt;/div&gt;
  8640. &lt;/ul&gt;
  8641.  
  8642.  
  8643.  
  8644. &lt;h3&gt;&lt;strong&gt;Bug Fixes&lt;/strong&gt;&lt;/h3&gt;
  8645.  
  8646.  
  8647.  
  8648. &lt;h4&gt;&lt;strong&gt;Respect for “Do Not Disturb”&lt;/strong&gt;&lt;/h4&gt;
  8649.  
  8650.  
  8651.  
  8652. &lt;p class=&quot;has-small-font-size&quot;&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1876310&quot;&gt;Bug 1876310&lt;/a&gt;&lt;/p&gt;
  8653.  
  8654.  
  8655.  
  8656. &lt;p&gt;Your focus time is sacred, and Thunderbird now honors that across all operating systems.&lt;/p&gt;
  8657.  
  8658.  
  8659.  
  8660. &lt;p&gt;&lt;strong&gt;Benefits:&lt;/strong&gt;&lt;/p&gt;
  8661.  
  8662.  
  8663.  
  8664. &lt;ul&gt;
  8665. &lt;li&gt;Native OS notifications now respect the “Do Not Disturb” setting of every operating system, including blocking calendar reminders and chat notification sounds.&lt;/li&gt;
  8666.  
  8667.  
  8668.  
  8669. &lt;li&gt;Delivers protected focus time and consistent behavior with other applications.&lt;/li&gt;
  8670. &lt;/ul&gt;
  8671.  
  8672.  
  8673.  
  8674. &lt;ul&gt;
  8675. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 25px;&quot;&gt;&lt;/div&gt;
  8676. &lt;/ul&gt;
  8677.  
  8678.  
  8679.  
  8680. &lt;h4&gt;&lt;strong&gt;Improved Dark Reader Mode Toggle&lt;/strong&gt;&lt;/h4&gt;
  8681.  
  8682.  
  8683.  
  8684. &lt;p class=&quot;has-small-font-size&quot;&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1962931&quot;&gt;Bug 1962931&lt;/a&gt;&lt;/p&gt;
  8685.  
  8686.  
  8687.  
  8688. &lt;p&gt;Reading flow is now smoother when switching between &lt;strong&gt;light and dark message modes&lt;/strong&gt;.  An issue was reported where toggling the setting in the message header would reset your scroll position and pull focus away from the message body. &lt;/p&gt;
  8689.  
  8690.  
  8691.  
  8692. &lt;p&gt;&lt;strong&gt;Benefits:&lt;/strong&gt;&lt;/p&gt;
  8693.  
  8694.  
  8695.  
  8696. &lt;ul&gt;
  8697. &lt;li&gt;Keep your scroll position in the message when switching between light and dark mode so you can continue reading without interruption.&lt;/li&gt;
  8698.  
  8699.  
  8700.  
  8701. &lt;li&gt;Retain focus on the message body for easier keyboard navigation.&lt;/li&gt;
  8702.  
  8703.  
  8704.  
  8705. &lt;li&gt;Reduce extra clicks and scrolling, making reading more seamless.&lt;/li&gt;
  8706. &lt;/ul&gt;
  8707.  
  8708.  
  8709.  
  8710. &lt;ul&gt;
  8711. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 25px;&quot;&gt;&lt;/div&gt;
  8712. &lt;/ul&gt;
  8713.  
  8714.  
  8715.  
  8716. &lt;h4&gt;&lt;strong&gt;Message List Scrolling Fix&lt;/strong&gt;&lt;/h4&gt;
  8717.  
  8718.  
  8719.  
  8720. &lt;p class=&quot;has-small-font-size&quot;&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1968967&quot;&gt;Bug 1968967&lt;/a&gt;&lt;/p&gt;
  8721.  
  8722.  
  8723.  
  8724. &lt;p&gt;&lt;strong&gt;Unwanted scrolling of the message list&lt;/strong&gt; that happened when returning to the Mail tab after opening a message is now a thing of the past. Instead of jumping to the top and slowly scrolling back down, the list now stays put.&lt;/p&gt;
  8725.  
  8726.  
  8727.  
  8728. &lt;p&gt;&lt;strong&gt;Benefits:&lt;/strong&gt;&lt;/p&gt;
  8729.  
  8730.  
  8731.  
  8732. &lt;ul&gt;
  8733. &lt;li&gt;Keep your place in the message list when switching tabs.&lt;/li&gt;
  8734. &lt;/ul&gt;
  8735.  
  8736.  
  8737.  
  8738. &lt;ul&gt;
  8739. &lt;div class=&quot;wp-block-spacer&quot; style=&quot;height: 25px;&quot;&gt;&lt;/div&gt;
  8740. &lt;/ul&gt;
  8741.  
  8742.  
  8743.  
  8744. &lt;h4&gt;&lt;strong&gt;PDF Attachments Reload Correctly on Startup&lt;/strong&gt;&lt;/h4&gt;
  8745.  
  8746.  
  8747.  
  8748. &lt;p class=&quot;has-small-font-size&quot;&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1970615&quot;&gt;Bug 1970615&lt;/a&gt;&lt;/p&gt;
  8749.  
  8750.  
  8751.  
  8752. &lt;p&gt;Thunderbird now correctly &lt;strong&gt;reloads PDF attachments&lt;/strong&gt; that were left open in tabs when you restart the app. Previously, these tabs would fail to open and display an error, forcing you to reload them manually.&lt;/p&gt;
  8753.  
  8754.  
  8755.  
  8756. &lt;p&gt;&lt;strong&gt;Benefits:&lt;/strong&gt;&lt;/p&gt;
  8757.  
  8758.  
  8759.  
  8760. &lt;ul&gt;
  8761. &lt;li&gt;Open PDF attachments are restored automatically on startup.&lt;/li&gt;
  8762.  
  8763.  
  8764.  
  8765. &lt;li&gt;No more error messages when resuming work.&lt;/li&gt;
  8766. &lt;/ul&gt;
  8767. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/08/thunderbird-monthly-release-142-recap/&quot;&gt;Thunderbird Monthly Release 142 Recap&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  8768. <pubDate>Thu, 28 Aug 2025 13:43:54 +0000</pubDate>
  8769. <dc:creator>David Hathaway</dc:creator>
  8770. </item>
  8771. <item>
  8772. <title>The Servo Blog: This month in Servo: new image formats, canvas backends, automation, and more!</title>
  8773. <guid isPermaLink="true">https://servo.org/blog/2025/08/22/this-month-in-servo/</guid>
  8774. <link>https://servo.org/blog/2025/08/22/this-month-in-servo/</link>
  8775. <description>&lt;p&gt;Servo has smashed its record again in July, with &lt;strong&gt;367 pull requests&lt;/strong&gt; landing in our nightly builds!
  8776. This includes several new web platform features:&lt;/p&gt;
  8777. &lt;ul&gt;
  8778. &lt;li&gt;&lt;strong&gt;APNG&lt;/strong&gt; and &lt;strong&gt;WebP animated images&lt;/strong&gt;, in addition to GIF (&lt;a href=&quot;https://github.com/rayguo17&quot;&gt;@rayguo17&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37637&quot;&gt;#37637&lt;/a&gt;)&lt;/li&gt;
  8779. &lt;li&gt;&lt;strong&gt;&amp;lt;source width&amp;gt;&lt;/strong&gt; and &lt;strong&gt;&amp;lt;source height&amp;gt;&lt;/strong&gt; (&lt;a href=&quot;https://github.com/leo030303&quot;&gt;@leo030303&lt;/a&gt;, &lt;a href=&quot;https://github.com/xiaochengh&quot;&gt;@xiaochengh&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38152&quot;&gt;#38152&lt;/a&gt;)&lt;/li&gt;
  8780. &lt;li&gt;&lt;strong&gt;TextDecoderStream&lt;/strong&gt; (&lt;a href=&quot;https://github.com/minghuaw&quot;&gt;@minghuaw&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38112&quot;&gt;#38112&lt;/a&gt;)&lt;/li&gt;
  8781. &lt;li&gt;&lt;strong&gt;replace() method&lt;/strong&gt; on &lt;strong&gt;CSSStyleSheet&lt;/strong&gt; (&lt;a href=&quot;https://github.com/stevennovaryo&quot;&gt;@stevennovaryo&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38244&quot;&gt;#38244&lt;/a&gt;)&lt;/li&gt;
  8782. &lt;li&gt;&lt;strong&gt;texImage3D() method&lt;/strong&gt; on &lt;strong&gt;WebGL2RenderingContext&lt;/strong&gt; (&lt;a href=&quot;https://github.com/wusyong&quot;&gt;@wusyong&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37718&quot;&gt;#37718&lt;/a&gt;)&lt;/li&gt;
  8783. &lt;li&gt;&lt;strong&gt;convertToBlob()&lt;/strong&gt; and &lt;strong&gt;transferToImageBitmap() methods&lt;/strong&gt; on &lt;strong&gt;OffscreenCanvas&lt;/strong&gt; (&lt;a href=&quot;https://github.com/tharkum&quot;&gt;@tharkum&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37786&quot;&gt;#37786&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37880&quot;&gt;#37880&lt;/a&gt;)&lt;/li&gt;
  8784. &lt;li&gt;&lt;strong&gt;adoptedStyleSheets property&lt;/strong&gt; on &lt;strong&gt;Document&lt;/strong&gt; and &lt;strong&gt;ShadowRoot&lt;/strong&gt;, with &lt;code&gt;--pref dom_adoptedstylesheet_enabled&lt;/code&gt; (&lt;a href=&quot;https://github.com/stevennovaryo&quot;&gt;@stevennovaryo&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38163&quot;&gt;#38163&lt;/a&gt;)&lt;/li&gt;
  8785. &lt;li&gt;&lt;strong&gt;ImageBitmap&lt;/strong&gt; no longer requires &lt;code&gt;--enable-experimental-web-platform-features&lt;/code&gt; (&lt;a href=&quot;https://github.com/tharkum&quot;&gt;@tharkum&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38050&quot;&gt;#38050&lt;/a&gt;)&lt;/li&gt;
  8786. &lt;/ul&gt;
  8787. &lt;p&gt;Notable changes for Servo library consumers:&lt;/p&gt;
  8788. &lt;ul&gt;
  8789. &lt;li&gt;
  8790. &lt;p&gt;&lt;strong&gt;Stylo 0.6.0&lt;/strong&gt; was released, &lt;strong&gt;fixing build errors&lt;/strong&gt; caused by an undeclared dependency on &lt;code&gt;markupsafe&lt;/code&gt; (&lt;a href=&quot;https://github.com/nicoburns&quot;&gt;@nicoburns&lt;/a&gt;, &lt;a href=&quot;https://github.com/delan&quot;&gt;@delan&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/stylo/pull/215&quot;&gt;stylo#215&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/stylo/issues/218&quot;&gt;stylo#218&lt;/a&gt;).
  8791. To work around this in Stylo 0.5.0, install the dependency: &lt;code&gt;pip install markupsafe&lt;/code&gt;&lt;/p&gt;
  8792. &lt;/li&gt;
  8793. &lt;li&gt;
  8794. &lt;p&gt;&lt;a href=&quot;https://doc.servo.org/servo/struct.WebView.html#method.notify_scroll_event&quot;&gt;&lt;strong&gt;notify_scroll_event()&lt;/strong&gt; on WebView&lt;/a&gt; now &lt;strong&gt;scrolls down as the &lt;code&gt;y&lt;/code&gt; value increases&lt;/strong&gt; (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37752&quot;&gt;#37752&lt;/a&gt;), consistent with the web platform.
  8795. This is a &lt;strong&gt;breaking change to the Servo API&lt;/strong&gt;.&lt;/p&gt;
  8796. &lt;/li&gt;
  8797. &lt;/ul&gt;
  8798. &lt;figure&gt;
  8799.  &lt;details&gt;
  8800.    &lt;img alt=&quot;servoshell nightly showing the same things, but animated&quot; src=&quot;https://servo.org/img/blog/2025-08-diffies.webp&quot; style=&quot;margin: 0;&quot; /&gt;
  8801.    &lt;img src=&quot;https://servo.org/img/blog/2025-08-diffies.jpg&quot; style=&quot;margin: 0;&quot; /&gt;&lt;div alt=&quot;servoshell nightly showing APNG and WebP animated images, ‘image-rendering’ applying to a ‘border-image’, a WebGL 2 example using texImage3D(), ‘text-decoration’ applying to a link with spaces, and an example of adoptedStyleSheets being controlled by a color input&quot;&gt;▶&lt;/div&gt;
  8802.  &lt;/details&gt;
  8803.  &amp;lt;figcaption&amp;gt;texImage3D() example reproduced from &lt;a href=&quot;https://webglsamples.org/WebGL2Samples/#texture_2d_array&quot;&gt;texture_2d_array&lt;/a&gt; in the &lt;a href=&quot;https://github.com/WebGLSamples/WebGL2Samples&quot;&gt;&lt;i&gt;WebGL 2.0 Samples&lt;/i&gt;&lt;/a&gt; by Trung Le, Shuai Shao (Shrek), et al (&lt;a href=&quot;https://github.com/WebGLSamples/WebGL2Samples/blob/7aef7dd1ef2615e657e0110df10a0fd6270cd50e/LICENSE.md&quot;&gt;license&lt;/a&gt;).&amp;lt;/figcaption&amp;gt;
  8804. &lt;/figure&gt;
  8805. &lt;h3&gt;Engine changes &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/08/22/this-month-in-servo/#engine-changes&quot;&gt;
  8806.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  8807.      &lt;/a&gt;&lt;/h3&gt;
  8808. &lt;p&gt;Like many browsers, Servo has two kinds of zoom: &lt;strong&gt;page zoom&lt;/strong&gt; affects the size of the viewport, while &lt;strong&gt;pinch zoom&lt;/strong&gt; does not (&lt;a href=&quot;https://github.com/shubhamg13&quot;&gt;@shubhamg13&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38194&quot;&gt;#38194&lt;/a&gt;).
  8809. &lt;strong&gt;Page zoom&lt;/strong&gt; now correctly triggers reflow (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38166&quot;&gt;#38166&lt;/a&gt;), and &lt;strong&gt;pinch zoom&lt;/strong&gt; is now reset to the viewport meta config when navigating (&lt;a href=&quot;https://github.com/shubhamg13&quot;&gt;@shubhamg13&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37315&quot;&gt;#37315&lt;/a&gt;).&lt;/p&gt;
  8810. &lt;p&gt;&lt;strong&gt;‘image-rendering’ property&lt;/strong&gt; now affects &lt;strong&gt;‘border-image’&lt;/strong&gt; (&lt;a href=&quot;https://github.com/lumiscosity&quot;&gt;@lumiscosity&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38346&quot;&gt;#38346&lt;/a&gt;), &lt;strong&gt;‘text-decoration[-line]’&lt;/strong&gt; is now &lt;strong&gt;drawn under whitespace&lt;/strong&gt; (&lt;a href=&quot;https://github.com/leo030303&quot;&gt;@leo030303&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38007&quot;&gt;#38007&lt;/a&gt;), and we’ve also fixed several layout bugs around &lt;strong&gt;grid item contents&lt;/strong&gt; (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37981&quot;&gt;#37981&lt;/a&gt;), &lt;strong&gt;table cell contents&lt;/strong&gt; (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38290&quot;&gt;#38290&lt;/a&gt;), &lt;strong&gt;quirks mode&lt;/strong&gt; (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37814&quot;&gt;#37814&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37831&quot;&gt;#37831&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37820&quot;&gt;#37820&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37837&quot;&gt;#37837&lt;/a&gt;), &lt;strong&gt;clientWidth&lt;/strong&gt; and &lt;strong&gt;clientHeight&lt;/strong&gt; queries of grid layouts (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37917&quot;&gt;#37917&lt;/a&gt;), and &lt;strong&gt;‘min-height’&lt;/strong&gt; and &lt;strong&gt;‘max-height’&lt;/strong&gt; of replaced elements (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37758&quot;&gt;#37758&lt;/a&gt;).&lt;/p&gt;
  8811. &lt;p&gt;As part of our &lt;strong&gt;incremental layout&lt;/strong&gt; project, we now &lt;strong&gt;cache the layout results&lt;/strong&gt; of replaced boxes (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37971&quot;&gt;#37971&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37897&quot;&gt;#37897&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37962&quot;&gt;#37962&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37943&quot;&gt;#37943&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37985&quot;&gt;#37985&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38349&quot;&gt;#38349&lt;/a&gt;), &lt;strong&gt;avoid unnecessary reflows&lt;/strong&gt; after animations (&lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37954&quot;&gt;#37954&lt;/a&gt;), &lt;strong&gt;invalidate layouts more precisely&lt;/strong&gt; (&lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38199&quot;&gt;#38199&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38057&quot;&gt;#38057&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38198&quot;&gt;#38198&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38059&quot;&gt;#38059&lt;/a&gt;), and we’ve added &lt;strong&gt;incremental box tree construction&lt;/strong&gt; (&lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37751&quot;&gt;#37751&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37957&quot;&gt;#37957&lt;/a&gt;) for flex and grid items (&lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37854&quot;&gt;#37854&lt;/a&gt;), table columns, cells, and captions (&lt;a href=&quot;https://github.com/Loirooriol&quot;&gt;@Loirooriol&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37851&quot;&gt;#37851&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37850&quot;&gt;#37850&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37849&quot;&gt;#37849&lt;/a&gt;), and a variety of inline elements (&lt;a href=&quot;https://github.com/coding-joedow&quot;&gt;@coding-joedow&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38084&quot;&gt;#38084&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37866&quot;&gt;#37866&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37868&quot;&gt;#37868&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37892&quot;&gt;#37892&lt;/a&gt;).&lt;/p&gt;
  8812. &lt;p&gt;Work on &lt;strong&gt;IndexedDB&lt;/strong&gt; continues, notably including support for &lt;strong&gt;key ranges&lt;/strong&gt; (&lt;a href=&quot;https://github.com/arihant2math&quot;&gt;@arihant2math&lt;/a&gt;, &lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38268&quot;&gt;#38268&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37684&quot;&gt;#37684&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38278&quot;&gt;#38278&lt;/a&gt;).&lt;/p&gt;
  8813. &lt;p&gt;&lt;strong&gt;sessionStorage&lt;/strong&gt; is now isolated between webviews, and copied to new webviews with the same &lt;code&gt;opener&lt;/code&gt; (&lt;a href=&quot;https://github.com/janvarga&quot;&gt;@janvarga&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37803&quot;&gt;#37803&lt;/a&gt;).&lt;/p&gt;
  8814. &lt;h3&gt;Browser changes &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/08/22/this-month-in-servo/#browser-changes&quot;&gt;
  8815.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  8816.      &lt;/a&gt;&lt;/h3&gt;
  8817. &lt;p&gt;&lt;strong&gt;servoshell&lt;/strong&gt; now has a &lt;strong&gt;.desktop file&lt;/strong&gt; and &lt;strong&gt;window name&lt;/strong&gt;, so you can now &lt;strong&gt;pin it to your taskbar&lt;/strong&gt; on Linux (&lt;a href=&quot;https://github.com/MichaelMcDonnell&quot;&gt;@MichaelMcDonnell&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38038&quot;&gt;#38038&lt;/a&gt;).
  8818. We’ve made it more ergonomic too, fixing both the sluggish &lt;strong&gt;mouse wheel&lt;/strong&gt; and &lt;strong&gt;pixel-perfect trackpad scrolling&lt;/strong&gt; and the too fast &lt;strong&gt;arrow key scrolling&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37982&quot;&gt;#37982&lt;/a&gt;).&lt;/p&gt;
  8819. &lt;p&gt;You can now &lt;strong&gt;focus the location bar with Alt+D&lt;/strong&gt; in addition to Ctrl+L on non-macOS platforms (&lt;a href=&quot;https://github.com/MichaelMcDonnell&quot;&gt;@MichaelMcDonnell&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37794&quot;&gt;#37794&lt;/a&gt;), and &lt;strong&gt;clicking the location bar&lt;/strong&gt; now selects the contents (&lt;a href=&quot;https://github.com/MichaelMcDonnell&quot;&gt;@MichaelMcDonnell&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37839&quot;&gt;#37839&lt;/a&gt;).&lt;/p&gt;
  8820. &lt;p&gt;When debugging Servo &lt;a href=&quot;https://book.servo.org/hacking/using-devtools.html&quot;&gt;with the &lt;strong&gt;Firefox devtools&lt;/strong&gt;&lt;/a&gt;, you can now view requests in the &lt;strong&gt;Network tab&lt;/strong&gt; both &lt;strong&gt;after navigating&lt;/strong&gt; (&lt;a href=&quot;https://github.com/uthmaniv&quot;&gt;@uthmaniv&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37778&quot;&gt;#37778&lt;/a&gt;) and when &lt;strong&gt;responses are served from cache&lt;/strong&gt; (&lt;a href=&quot;https://github.com/uthmaniv&quot;&gt;@uthmaniv&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37906&quot;&gt;#37906&lt;/a&gt;).
  8821. We’re also implementing the &lt;strong&gt;Debugger tab&lt;/strong&gt; (&lt;a href=&quot;https://github.com/delan&quot;&gt;@delan&lt;/a&gt;, &lt;a href=&quot;https://github.com/atbrakhi&quot;&gt;@atbrakhi&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/36027&quot;&gt;#36027&lt;/a&gt;), including several changes to our script system (&lt;a href=&quot;https://github.com/delan&quot;&gt;@delan&lt;/a&gt;, &lt;a href=&quot;https://github.com/atbrakhi&quot;&gt;@atbrakhi&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38236&quot;&gt;#38236&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38232&quot;&gt;#38232&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38265&quot;&gt;#38265&lt;/a&gt;) and fixing a whole class of bugs where devtools ends up broken (&lt;a href=&quot;https://github.com/atbrakhi&quot;&gt;@atbrakhi&lt;/a&gt;, &lt;a href=&quot;https://github.com/delan&quot;&gt;@delan&lt;/a&gt;, &lt;a href=&quot;https://github.com/simonwuelker&quot;&gt;@simonwuelker&lt;/a&gt;, &lt;a href=&quot;https://github.com/the6p4c&quot;&gt;@the6p4c&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37686&quot;&gt;#37686&lt;/a&gt;).&lt;/p&gt;
  8822. &lt;h3&gt;WebDriver changes &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/08/22/this-month-in-servo/#webdriver-changes&quot;&gt;
  8823.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  8824.      &lt;/a&gt;&lt;/h3&gt;
  8825. &lt;p&gt;&lt;strong&gt;WebDriver automation&lt;/strong&gt; support now &lt;strong&gt;goes through servoshell&lt;/strong&gt;, rather than through libservo internally, ensuring that WebDriver commands are consistently executed in the correct order (&lt;a href=&quot;https://github.com/longvatrong111&quot;&gt;@longvatrong111&lt;/a&gt;, &lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37669&quot;&gt;#37669&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37908&quot;&gt;#37908&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37663&quot;&gt;#37663&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37911&quot;&gt;#37911&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38212&quot;&gt;#38212&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38314&quot;&gt;#38314&lt;/a&gt;).
  8826. We’ve also fixed race conditions in the &lt;strong&gt;Back&lt;/strong&gt;, &lt;strong&gt;Forward&lt;/strong&gt; (&lt;a href=&quot;https://github.com/longvatrong111&quot;&gt;@longvatrong111&lt;/a&gt;, &lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37950&quot;&gt;#37950&lt;/a&gt;), &lt;strong&gt;Element Click&lt;/strong&gt; (&lt;a href=&quot;https://github.com/longvatrong111&quot;&gt;@longvatrong111&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37935&quot;&gt;#37935&lt;/a&gt;), &lt;strong&gt;Switch To Window&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38160&quot;&gt;#38160&lt;/a&gt;), and other commands (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/longvatrong111&quot;&gt;@longvatrong111&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38079&quot;&gt;#38079&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38234&quot;&gt;#38234&lt;/a&gt;).&lt;/p&gt;
  8827. &lt;p&gt;We’ve added support for the &lt;strong&gt;Dismiss Alert&lt;/strong&gt;, &lt;strong&gt;Accept Alert&lt;/strong&gt;, &lt;strong&gt;Get Alert Text&lt;/strong&gt; (&lt;a href=&quot;https://github.com/longvatrong111&quot;&gt;@longvatrong111&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37913&quot;&gt;#37913&lt;/a&gt;), and &lt;strong&gt;Send Alert Text&lt;/strong&gt; commands for &lt;a href=&quot;https://html.spec.whatwg.org/multipage/#simple-dialogs&quot;&gt;&lt;strong&gt;simple dialogs&lt;/strong&gt;&lt;/a&gt; (&lt;a href=&quot;https://github.com/longvatrong111&quot;&gt;@longvatrong111&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38140&quot;&gt;#38140&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38035&quot;&gt;#38035&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38142&quot;&gt;#38142&lt;/a&gt;), as well as the &lt;strong&gt;Maximize Window&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38271&quot;&gt;#38271&lt;/a&gt;) and &lt;strong&gt;Element Clear&lt;/strong&gt; commands (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/jdm&quot;&gt;@jdm&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38208&quot;&gt;#38208&lt;/a&gt;).
  8828. &lt;a href=&quot;https://w3c.github.io/webdriver/#element-retrieval&quot;&gt;&lt;strong&gt;Find Element&lt;/strong&gt; family of commands&lt;/a&gt; can now use the &lt;strong&gt;&lt;code&gt;&quot;xpath&quot;&lt;/code&gt; location strategy&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37783&quot;&gt;#37783&lt;/a&gt;).
  8829. &lt;strong&gt;Get Element Shadow Root&lt;/strong&gt; commands can now interact with &lt;strong&gt;closed shadow roots&lt;/strong&gt; (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37826&quot;&gt;#37826&lt;/a&gt;).&lt;/p&gt;
  8830. &lt;p&gt;You can now &lt;strong&gt;run the WebDriver test suite&lt;/strong&gt; in CI with &lt;code&gt;mach try wd&lt;/code&gt; or &lt;code&gt;mach try webdriver&lt;/code&gt; (&lt;a href=&quot;https://github.com/PotatoCP&quot;&gt;@PotatoCP&lt;/a&gt;, &lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37498&quot;&gt;#37498&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37873&quot;&gt;#37873&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37712&quot;&gt;#37712&lt;/a&gt;).&lt;/p&gt;
  8831. &lt;h3&gt;2D graphics &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/08/22/this-month-in-servo/#2d-graphics&quot;&gt;
  8832.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  8833.      &lt;/a&gt;&lt;/h3&gt;
  8834. &lt;p&gt;&lt;strong&gt;&amp;lt;canvas&amp;gt;&lt;/strong&gt; is key to programmable graphics on the web, with Servo supporting WebGPU, WebGL, and 2D canvas contexts.
  8835. But the &lt;strong&gt;general-purpose 2D graphics&lt;/strong&gt; routines that power Servo’s 2D canvases are potentially useful for a lot more than &amp;lt;canvas&amp;gt;: &lt;strong&gt;font rendering&lt;/strong&gt; is bread and butter for Servo, but &lt;strong&gt;SVG rendering&lt;/strong&gt; is only minimally supported right now, and &lt;strong&gt;PDF output&lt;/strong&gt; is not yet implemented at all.&lt;/p&gt;
  8836. &lt;p&gt;Those features have one thing in common: they require things that WebRender can’t yet do.
  8837. &lt;strong&gt;WebRender&lt;/strong&gt; does one thing and does it well: rasterise the layouts of the web, really fast, by &lt;a href=&quot;https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/&quot;&gt;using the GPU as much as possible&lt;/a&gt;.
  8838. Font rendering and SVG rendering both involve rasterising arbitrary paths, which currently has to be done outside WebRender, and PDF output is out of scope entirely.&lt;/p&gt;
  8839. &lt;p&gt;The more code we can share between these tasks, the better we can make that code, and the smaller we can make Servo’s binary sizes (&lt;a href=&quot;https://github.com/servo/servo/issues/38022&quot;&gt;#38022&lt;/a&gt;).
  8840. We’ve started by moving 2D-&amp;lt;canvas&amp;gt;-specific state out of the &lt;code&gt;canvas&lt;/code&gt; crate (&lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38098&quot;&gt;#38098&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38114&quot;&gt;#38114&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38164&quot;&gt;#38164&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38214&quot;&gt;#38214&lt;/a&gt;), which has in turn allowed us to modernise it with &lt;strong&gt;new backends based on &lt;a href=&quot;https://github.com/linebender/vello&quot;&gt;Vello&lt;/a&gt;&lt;/strong&gt; (&lt;a href=&quot;https://github.com/EnnuiL&quot;&gt;@EnnuiL&lt;/a&gt;, &lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/30636&quot;&gt;#30636&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/38345&quot;&gt;#38345&lt;/a&gt;):&lt;/p&gt;
  8841. &lt;ul&gt;
  8842. &lt;li&gt;
  8843. &lt;p&gt;a Vello GPU-based backend (&lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/36821&quot;&gt;#36821&lt;/a&gt;), currently slower than the default backend; to use it, build Servo with &lt;code&gt;--features vello&lt;/code&gt; and enable it with &lt;code&gt;--pref dom_canvas_vello_enabled&lt;/code&gt;&lt;/p&gt;
  8844. &lt;/li&gt;
  8845. &lt;li&gt;
  8846. &lt;p&gt;a Vello CPU-based backend (&lt;a href=&quot;https://github.com/sagudev&quot;&gt;@sagudev&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38282&quot;&gt;#38282&lt;/a&gt;), &lt;strong&gt;already faster than the default backend&lt;/strong&gt;; to use it, build Servo with &lt;code&gt;--features vello_cpu&lt;/code&gt; and enable it with &lt;code&gt;--pref dom_canvas_vello_cpu_enabled&lt;/code&gt;&lt;/p&gt;
  8847. &lt;/li&gt;
  8848. &lt;/ul&gt;
  8849. &lt;h3&gt;What is a pixel? &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/08/22/this-month-in-servo/#what-is-a-pixel%3F&quot;&gt;
  8850.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  8851.      &lt;/a&gt;&lt;/h3&gt;
  8852. &lt;p&gt;Many recent Servo bugs have been related to our handling of &lt;strong&gt;viewport&lt;/strong&gt;, &lt;strong&gt;window&lt;/strong&gt;, and &lt;strong&gt;screen coordinate spaces&lt;/strong&gt; (&lt;a href=&quot;https://github.com/servo/servo/issues/36817&quot;&gt;#36817&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/37804&quot;&gt;#37804&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/37824&quot;&gt;#37824&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/37878&quot;&gt;#37878&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/37978&quot;&gt;#37978&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/38089&quot;&gt;#38089&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/38090&quot;&gt;#38090&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/38093&quot;&gt;#38093&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/issues/38255&quot;&gt;#38255&lt;/a&gt;).
  8853. Symptoms of these bugs include &lt;strong&gt;bad hit testing&lt;/strong&gt; (e.g. links that can’t be clicked), &lt;strong&gt;inability to scroll&lt;/strong&gt; to the end of the page, or &lt;strong&gt;graphical glitches&lt;/strong&gt; like disappearing browser UI or black bars.&lt;/p&gt;
  8854. &lt;p&gt;Windows rarely take up the whole screen, viewports rarely take up the whole window due to window decorations, and when different units come into play, like CSS &lt;code&gt;px&lt;/code&gt; vs device pixels, a more systematic approach is needed.
  8855. We built &lt;a href=&quot;https://docs.rs/euclid/0.22.11/euclid/&quot;&gt;&lt;strong&gt;euclid&lt;/strong&gt;&lt;/a&gt; to solve these problems in a strongly typed way within Servo, but beyond the viewport, we need to convert between euclid types and the geometry types provided by the embedder, the toolkit, the platform, or WebDriver, which creates opportunities for errors.&lt;/p&gt;
  8856. &lt;p&gt;Embedders are now the single source of truth for &lt;strong&gt;window rects&lt;/strong&gt; and &lt;strong&gt;screen sizes&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37960&quot;&gt;#37960&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38020&quot;&gt;#38020&lt;/a&gt;), and we’ve fixed incorrect coordinate handling in &lt;a href=&quot;https://w3c.github.io/webdriver/#get-window-rect&quot;&gt;&lt;strong&gt;Get Window Rect&lt;/strong&gt;&lt;/a&gt;, &lt;a href=&quot;https://w3c.github.io/webdriver/#set-window-rect&quot;&gt;&lt;strong&gt;Set Window Rect&lt;/strong&gt;&lt;/a&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37812&quot;&gt;#37812&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37893&quot;&gt;#37893&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38209&quot;&gt;#38209&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38258&quot;&gt;#38258&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38249&quot;&gt;#38249&lt;/a&gt;), &lt;strong&gt;resizeTo()&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37848&quot;&gt;#37848&lt;/a&gt;), &lt;strong&gt;screenX&lt;/strong&gt;, &lt;strong&gt;screenY&lt;/strong&gt;, &lt;strong&gt;screenLeft&lt;/strong&gt;, &lt;strong&gt;screenTop&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37934&quot;&gt;#37934&lt;/a&gt;), and in &lt;strong&gt;servoshell&lt;/strong&gt; (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37961&quot;&gt;#37961&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38174&quot;&gt;#38174&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38307&quot;&gt;#38307&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38082&quot;&gt;#38082&lt;/a&gt;).
  8857. We’ve also improved the Web Platform Tests (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37856&quot;&gt;#37856&lt;/a&gt;) and clarified our docs (&lt;a href=&quot;https://github.com/yezhizhen&quot;&gt;@yezhizhen&lt;/a&gt;, &lt;a href=&quot;https://github.com/mrobinson&quot;&gt;@mrobinson&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/37879&quot;&gt;#37879&lt;/a&gt;, &lt;a href=&quot;https://github.com/servo/servo/pull/38110&quot;&gt;#38110&lt;/a&gt;) in these areas.&lt;/p&gt;
  8858. &lt;h3&gt;Donations &lt;a class=&quot;header-anchor&quot; href=&quot;https://servo.org/blog/2025/08/22/this-month-in-servo/#donations&quot;&gt;
  8859.        &lt;span class=&quot;icon hashlink&quot;&gt;&lt;i class=&quot;fas fa-link&quot;&gt;&lt;/i&gt;&lt;/span&gt;
  8860.      &lt;/a&gt;&lt;/h3&gt;
  8861. &lt;p&gt;Thanks again for your generous support!
  8862. We are now receiving &lt;strong&gt;4691 USD/month&lt;/strong&gt; (+5.0%  over June) in recurring donations.
  8863. This helps cover the cost of our &lt;a href=&quot;https://ci0.servo.org/&quot;&gt;self-hosted&lt;/a&gt; &lt;a href=&quot;https://ci1.servo.org/&quot;&gt;CI&lt;/a&gt; &lt;a href=&quot;https://ci2.servo.org/&quot;&gt;runners&lt;/a&gt; and one of our &lt;a href=&quot;https://www.outreachy.org/alums/2025-06/#:~:text=Servo&quot;&gt;latest Outreachy interns&lt;/a&gt;!&lt;/p&gt;
  8864. &lt;p&gt;Keep an eye out for &lt;a href=&quot;https://github.com/servo/servo/issues/38141&quot;&gt;further improvements to our CI system&lt;/a&gt; in the coming months, including &lt;a href=&quot;https://github.com/servo/ci-runners/issues/21&quot;&gt;&lt;strong&gt;ten-minute WPT builds&lt;/strong&gt;&lt;/a&gt; and our new proposal for &lt;a href=&quot;https://github.com/servo/project/issues/160&quot;&gt;&lt;strong&gt;dedicated benchmarking runners&lt;/strong&gt;&lt;/a&gt;, all thanks to your support.&lt;/p&gt;
  8865. &lt;p&gt;Servo is also on &lt;a href=&quot;https://thanks.dev/&quot;&gt;thanks.dev&lt;/a&gt;, and already &lt;strong&gt;22 GitHub users&lt;/strong&gt; (−3 from June) that depend on Servo are sponsoring us there.
  8866. If you use Servo libraries like &lt;a href=&quot;https://crates.io/crates/url/reverse_dependencies&quot;&gt;url&lt;/a&gt;, &lt;a href=&quot;https://crates.io/crates/html5ever/reverse_dependencies&quot;&gt;html5ever&lt;/a&gt;, &lt;a href=&quot;https://crates.io/crates/selectors/reverse_dependencies&quot;&gt;selectors&lt;/a&gt;, or &lt;a href=&quot;https://crates.io/crates/cssparser/reverse_dependencies&quot;&gt;cssparser&lt;/a&gt;, signing up for &lt;a href=&quot;https://thanks.dev/&quot;&gt;thanks.dev&lt;/a&gt; could be a good way for you (or your employer) to give back to the community.&lt;/p&gt;
  8867. &lt;figure class=&quot;_fig&quot; style=&quot;width: 100%; margin: 1em 0;&quot;&gt;&lt;div class=&quot;_flex&quot;&gt;
  8868.    &lt;div style=&quot;text-align: right;&quot;&gt;
  8869.        &lt;div&gt;&lt;strong&gt;4691&lt;/strong&gt; USD/month&lt;/div&gt;
  8870.        &lt;div&gt;&lt;/div&gt;
  8871.        &lt;div&gt;&lt;/div&gt;
  8872.        &lt;div style=&quot;padding-right: 1em;&quot;&gt;&lt;strong&gt;10000&lt;/strong&gt;&lt;/div&gt;
  8873.    &lt;/div&gt;
  8874.    &lt;progress max=&quot;10000&quot; value=&quot;4691&quot;&gt;&lt;/progress&gt;
  8875. &lt;/div&gt;&lt;/figure&gt;
  8876. &lt;p&gt;As always, use of these funds will be decided transparently in the Technical Steering Committee.
  8877. For more details, head to our &lt;a href=&quot;https://servo.org/sponsorship/&quot;&gt;Sponsorship page&lt;/a&gt;.&lt;/p&gt;</description>
  8878. <pubDate>Fri, 22 Aug 2025 00:00:00 +0000</pubDate>
  8879. </item>
  8880. <item>
  8881. <title>Mozilla Thunderbird: Thunderbird Pro August 2025 Update</title>
  8882. <guid isPermaLink="false">https://blog.thunderbird.net/?p=3734</guid>
  8883. <link>https://blog.thunderbird.net/2025/08/tbpro-august-2025-update/</link>
  8884. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;320&quot; src=&quot;https://blog.thunderbird.net/files/2025/08/tb-pro-blog.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
  8885. &lt;p&gt;In April of this year &lt;a href=&quot;https://blog.thunderbird.net/2025/04/thundermail-and-thunderbird-pro-services/&quot;&gt;we announced Thunderbird Pro&lt;/a&gt;, additional subscription services from Thunderbird meant to help you get more done with the app you already use and love. These services include a first ever email service from Thunderbird, called Thundermail. They also include Appointment, for scheduling meetings and appointments and Send, an end-to-end encrypted filesharing tool. &lt;strong&gt;Each of these services are open source, repositories are linked down below.&lt;/strong&gt;&lt;/p&gt;
  8886.  
  8887.  
  8888.  
  8889. &lt;p&gt;Thunderbird Pro services are being built as part of the broader Thunderbird product ecosystem. These services are enhancements to the current Thunderbird application experience. They are optional, designed to enhance productivity for users who need features like scheduling, file sharing and email hosting, without relying on the alternate platforms. For users who opt in, the goal is for these services to be smoothly integrated into the Thunderbird app, providing a natural extension of the familiar experience they already enjoy, enhanced with additional capabilities they may be looking for. For updates on Thunderbird Pro development and beta access availability, &lt;a href=&quot;https://thundermail.com/&quot;&gt;sign &lt;/a&gt;up for the mailing list at &lt;a href=&quot;http://thundermail.com&quot;&gt;thundermail.com&lt;/a&gt;. &lt;/p&gt;
  8890.  
  8891.  
  8892.  
  8893. &lt;h3&gt;&lt;strong&gt;Progress So Far&lt;/strong&gt;&lt;/h3&gt;
  8894.  
  8895.  
  8896.  
  8897. &lt;h4&gt;Thundermail&lt;/h4&gt;
  8898.  
  8899.  
  8900.  
  8901. &lt;p&gt;Development has been moving steadily forward and community interest in Thundermail has been strong. The upcoming email hosting service from Thunderbird will support IMAP, SMTP and JMAP out of the box, making it compatible with the Thunderbird app and many other email clients. If you have your own domain, you’ll be able to bring it in and host it with us. Alternatively, grab an email address provided by Thunderbird with your choice of @thundermail.com or @tb.pro as the domains.  The servers hosting Thundermail will initially be located in Germany with more countries to follow in the future. Thunderbird’s investment in offering an email service reflects our broader goal of strengthening support for open standards and giving users the option to keep their entire email experience within Thunderbird. &lt;/p&gt;
  8902.  
  8903.  
  8904.  
  8905. &lt;h4&gt;Thunderbird Appointment &lt;a href=&quot;https://github.com/thunderbird/appointment&quot;&gt;(Repo)&lt;/a&gt;&lt;/h4&gt;
  8906.  
  8907.  
  8908.  
  8909. &lt;p&gt;We originally developed the scheduling tool as a standalone web app. On the current roadmap, however, we’re tightly integrating Appointment into the Thunderbird app through the compose window, allowing users to insert scheduling links without leaving the email workflow. It will be easy for organizations and individuals to self-host, fork and adapt the tool to their own needs. The future is for Appointment to support multiple meeting types, like Zoom calls, phone meetings, or in-person coffee chats. Each of these will have its own settings and scheduling rules. &lt;/p&gt;
  8910.  
  8911.  
  8912.  
  8913. &lt;p&gt;One of the most requested future features is group scheduling, which would allow multiple team members to offer shared availability via a single link. The current calendar protocols don’t fully support this flow, however Thunderbird is participating in discussions around open standards like VPOLL to help move things forward. Usability studies are helping refine the MVP and community feedback is shaping the roadmap.&lt;/p&gt;
  8914.  
  8915.  
  8916.  
  8917. &lt;h4&gt;Thunderbird Send &lt;a href=&quot;https://github.com/thunderbird/tbpro-add-on&quot;&gt;(Repo)&lt;/a&gt;&lt;/h4&gt;
  8918.  
  8919.  
  8920.  
  8921. &lt;p&gt;A secure, end-to-end encrypted file sharing tool, built on Thunderbird app’s existing Filelink feature. It supports large file transfers directly from the email client. This allows users to bypass platforms like Google Drive or OneDrive. Pro users will receive 500 GB of storage to start, with no individual file size limit, only constrained by their total quota. We’re planning support for chunked uploads and encryption  to ensure reliability and data protection. We’ll deliver Send as a system add-on which lets the team push updates faster. This also avoids locking new capabilities behind major Thunderbird release cycles.&lt;/p&gt;
  8922.  
  8923.  
  8924.  
  8925. &lt;p&gt;All Thunderbird Pro tools are open source and self-hostable. For users who prefer to run their own infrastructure or work in regulated environments, both Send and Appointment can be deployed independently. Thunderbird will continue to support these users with documentation and open APIs.&lt;/p&gt;
  8926.  
  8927.  
  8928.  
  8929. &lt;h3&gt;&lt;strong&gt;A Look Ahead&lt;/strong&gt;&lt;/h3&gt;
  8930.  
  8931.  
  8932.  
  8933. &lt;p&gt;Thunderbird is exploring additional Pro features beyond the current lineup. While we’ve made no commitments yet, there is strong interest in adding markdown based Notes functionality, especially as lightweight personal knowledge management becomes more popular. Heavier lifts like collaborative docs or spreadsheets may follow, depending on adoption and sustainability.&lt;/p&gt;
  8934.  
  8935.  
  8936.  
  8937. &lt;p&gt;Another worthy mention: a fourth, previously announced service called Assist, which will eventually enable users to take advantage of AI features in their day-to-day email tasks, is still in the research and development phase. It will not be part of the initial lineup of services. This initiative is a bigger undertaking as we ensure we get it right for user privacy and make sure the features included are actually things our users want. More to come on this as the project progresses.&lt;/p&gt;
  8938.  
  8939.  
  8940.  
  8941. &lt;p&gt;To improve transparency and invite community collaboration, Thunderbird is also preparing a public roadmap covering desktop, mobile and Pro services. We’re developing the roadmap in collaboration with the Thunderbird Council. Our goal is to encourage participation from contributors and users alike.&lt;/p&gt;
  8942.  
  8943.  
  8944.  
  8945. &lt;h4&gt;Free vs Paid&lt;/h4&gt;
  8946.  
  8947.  
  8948.  
  8949. &lt;p&gt;Adding these additional subscription services will never compromise the features, stability or functionality our users are accustomed to in the free Thunderbird desktop and mobile applications. These services come with real costs, especially storage and bandwidth. Charging for them helps ensure that users who benefit from these tools help cover their cost, instead of donors footing the bill. &lt;/p&gt;
  8950.  
  8951.  
  8952.  
  8953. &lt;p&gt;Thunderbird Pro is a completely optional suite of (open source) services designed to provide additional productivity capabilities to the Thunderbird app and never to replace them. The current Thunderbird desktop and mobile applications are, and always will be, free. They will still heavily rely on ongoing donations for both development and independence.&lt;/p&gt;
  8954.  
  8955.  
  8956.  
  8957. &lt;p&gt;If you haven’t already, j&lt;a href=&quot;https://thundermail.com/&quot;&gt;oin our waiting list&lt;/a&gt; to be one of the early beta testers for Thunderbird Pro. While we don’t have a specific timeline just yet, we will be sharing ongoing updates as development progresses.&lt;/p&gt;
  8958.  
  8959.  
  8960.  
  8961. &lt;p&gt;—&lt;/p&gt;
  8962.  
  8963.  
  8964.  
  8965. &lt;p&gt;Ryan Sipes&lt;br /&gt;Managing Director, Product&lt;br /&gt;Mozilla Thunderbird&lt;/p&gt;
  8966. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2025/08/tbpro-august-2025-update/&quot;&gt;Thunderbird Pro August 2025 Update&lt;/a&gt; appeared first on &lt;a href=&quot;https://blog.thunderbird.net&quot;&gt;The Thunderbird Blog&lt;/a&gt;.&lt;/p&gt;</description>
  8967. <pubDate>Tue, 19 Aug 2025 18:54:37 +0000</pubDate>
  8968. <dc:creator>Ryan Sipes</dc:creator>
  8969. </item>
  8970. <item>
  8971. <title>Hacks.Mozilla.Org: CRLite: Fast, private, and comprehensive certificate revocation checking in Firefox</title>
  8972. <guid isPermaLink="false">https://hacks.mozilla.org/?p=48231</guid>
  8973. <link>https://hacks.mozilla.org/2025/08/crlite-fast-private-and-comprehensive-certificate-revocation-checking-in-firefox/</link>
  8974. <description>&lt;p&gt;Firefox is now the first and the only browser to deploy fast and comprehensive certificate revocation checking that does not reveal your browsing activity to anyone (not even to Mozilla).&lt;/p&gt;
  8975. &lt;p&gt;Tens of millions of TLS server certificates are issued each day to secure communications between browsers and websites. These certificates are the cornerstones of &lt;a href=&quot;https://www.mozilla.org/en-US/about/webvision/full/#ubiquitousencryption&quot;&gt;ubiquitous encryption&lt;/a&gt; and a key part of our vision for the web. While a certificate can be valid for up to 398 days, it can also be revoked at any point in its lifetime. A revoked certificate poses a serious security risk and should not be trusted to authenticate a server.&lt;/p&gt;
  8976. &lt;p&gt;Identifying a revoked certificate is difficult because information needs to flow from the &lt;a href=&quot;https://en.wikipedia.org/wiki/Certificate_authority&quot;&gt;certificate’s issuer&lt;/a&gt; out to each browser. There are basically two ways to handle this. The browser either needs to ask an authority in real time about each certificate that it encounters, or it needs to maintain a frequently-updated list of revoked certificates. Firefox’s new mechanism, CRLite, has made the latter strategy feasible for the first time.&lt;/p&gt;
  8977. &lt;p&gt;With CRLite, Firefox periodically downloads a compact encoding of the set of all revoked certificates that appear in &lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Web/Security/Certificate_Transparency&quot;&gt;Certificate Transparency logs&lt;/a&gt;. Firefox stores this encoding locally, updates it every 12 hours, and queries it privately every time a new TLS connection is created.&lt;/p&gt;
  8978. &lt;p&gt;You may have heard that &lt;a href=&quot;https://scotthelme.co.uk/revocation-is-broken/&quot;&gt;revocation is broken&lt;/a&gt; or that &lt;a href=&quot;https://www.imperialviolet.org/2011/03/18/revocation.html&quot;&gt;revocation doesn’t work&lt;/a&gt;. For a long time, the web was stuck with bad tradeoffs between security, privacy, and reliability in this space. That’s no longer the case. We enabled CRLite for all Firefox desktop (Windows, Linux, MacOS) users starting in Firefox 137, and we have seen that it makes revocation checking functional, reliable, and performant. We are hopeful that we can replicate our success in other, more constrained, environments as well.&lt;/p&gt;
  8979. &lt;h3&gt;Better privacy and performance&lt;/h3&gt;
  8980. &lt;p&gt;Prior to version 137, Firefox used the &lt;a href=&quot;https://en.wikipedia.org/wiki/Online_Certificate_Status_Protocol&quot;&gt;Online Certificate Status Protocol (OCSP)&lt;/a&gt; to ask authorities about revocation statuses in real time. Certificate authorities are &lt;a href=&quot;https://cabforum.org/2023/07/14/ballot-sc063v4-make-ocsp-optional-require-crls-and-incentivize-automation/&quot;&gt;no longer required&lt;/a&gt; to support OCSP, and some major certificate authorities have already &lt;a href=&quot;https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls/&quot;&gt;announced&lt;/a&gt; their intention to wind down their OCSP services. There are several reasons for this, but the foremost is that OCSP is a privacy leak. When a user asks an OCSP server about a certificate, they reveal to the server that they intend to visit a certain domain. Since OCSP requests are typically made over unencrypted HTTP, this information is also leaked to all on-path observers.&lt;/p&gt;
  8981. &lt;p&gt;Having gained confidence in the robustness, accuracy and performance of our CRLite implementation, we will be disabling OCSP for &lt;a href=&quot;https://en.wikipedia.org/wiki/Domain-validated_certificate&quot;&gt;domain validated certificates&lt;/a&gt; in Firefox 142. Sealing the OCSP privacy leak complements our ongoing efforts to encrypt everything on the internet by rolling out &lt;a href=&quot;https://support.mozilla.org/en-US/kb/https-first&quot;&gt;HTTPS-First&lt;/a&gt;, &lt;a href=&quot;https://support.mozilla.org/en-US/kb/firefox-dns-over-https&quot;&gt;DNS over HTTPS&lt;/a&gt;, and &lt;a href=&quot;https://blog.mozilla.org/en/firefox/encrypted-hello/&quot;&gt;Encrypted Client Hello&lt;/a&gt;.&lt;/p&gt;
  8982. &lt;p&gt;Disabling OCSP also has performance benefits: we have found that OCSP requests block the TLS handshake for 100 ms at the median. As we rolled out CRLite, we saw notable improvements in TLS handshake times.&lt;/p&gt;
  8983. &lt;p&gt;&lt;a href=&quot;https://hacks.mozilla.org/wp-content/uploads/2025/07/chart.svg&quot;&gt;&lt;img alt=&quot;A graph showing &amp;quot;Median TLS Handshake Time (ms)&amp;quot; and &amp;quot;Revocation mechanism usage&amp;quot; over time. As the percentage of revocation checks performed with CRLite increases from 0% to 80%, the median TLS handshake time decreases from 56.4 ms to 39.9 ms.&quot; class=&quot; wp-image-48232 aligncenter&quot; height=&quot;294&quot; src=&quot;https://hacks.mozilla.org/wp-content/uploads/2025/07/chart.svg&quot; width=&quot;475&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
  8984. &lt;h3&gt;Bandwidth requirements of CRLite&lt;/h3&gt;
  8985. &lt;p&gt;Users with CRLite download an average of 300 kB of revocation data per day: a 4 MB snapshot every 45 days and a sequence of “delta updates” in-between. (The exact sizes of snapshots and delta updates fluctuate day by day. You can explore the real data on our &lt;a href=&quot;https://yardstick.mozilla.org/dashboard/snapshot/c1WZrxGkNxdm9oZp7xVvGUEFJCELfApN&quot;&gt;dashboard&lt;/a&gt;.)&lt;/p&gt;
  8986. &lt;p&gt;To get a sense for how compact CRLite artifacts are, let’s compare them with &lt;a href=&quot;https://en.wikipedia.org/wiki/Certificate_revocation_list&quot;&gt;Certificate Revocation Lists (CRLs)&lt;/a&gt;. A CRL is a list of serial numbers that each identify a revoked certificate from a single issuer. Certificate authorities in Mozilla’s root store have disclosed approximately three thousand active CRLs to the &lt;a href=&quot;https://www.ccadb.org/&quot;&gt;Common CA Database&lt;/a&gt;. In total, these three thousand CRLs are 300 MB in size, and the only way to keep a copy of them up-to-date is to redownload them regularly. CRLite encodes the same dynamic set of revoked certificates in 300 kB per day. In other words, CRLite is &lt;b&gt;one&lt;/b&gt; &lt;b&gt;thousand times more bandwidth-efficient&lt;/b&gt; than daily CRL downloads.&lt;/p&gt;
  8987. &lt;p&gt;Of course, no browser is performing daily downloads of all CRLs. For a more meaningful comparison, we can consider Chrome’s CRLSets. These are hand-picked sets of revocations that are delivered to Chrome users daily. Recent CRLSets weigh in at 600 kB and include about 1% of all revocations (thirty-five thousand of the four million total). Firefox’s CRLite implementation uses half the bandwidth, updates twice as frequently, and includes &lt;b&gt;all&lt;/b&gt; revocations.&lt;/p&gt;
  8988. &lt;p&gt;Including all revocations is essential for security as there is no reliable way today to distinguish security-critical revocations from administrative revocations. Roughly half of all revocations are made without a specified reason code, and some of these revocations are likely due to security concerns that the certificate’s owner did not wish to highlight. When reason codes &lt;i&gt;are&lt;/i&gt; used, they are often used in an ambiguous way that does not clearly map to security risk. In this environment, the only secure approach is to check all revocations, which is now possible with CRLite.&lt;/p&gt;
  8989. &lt;h3&gt;State-of-the-art blocklist technology&lt;/h3&gt;
  8990. &lt;p&gt;You may recall a &lt;a href=&quot;https://blog.mozilla.org/security/2020/01/09/crlite-part-1-all-web-pki-revocations-compressed/&quot;&gt;series&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/security/2020/01/09/crlite-part-2-end-to-end-design/&quot;&gt;of&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/security/2020/01/21/crlite-part-3-speeding-up-secure-browsing/&quot;&gt;blog&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/security/2020/12/01/crlite-part-4-infrastructure-design/&quot;&gt;posts&lt;/a&gt; on our experiments with CRLite back in 2020. We followed these experiments with successful deployments to Nightly, Beta, and 1% of Release users. But the bandwidth requirements for this early CRLite design turned out to be prohibitive.&lt;/p&gt;
  8991. &lt;p&gt;We solved our bandwidth issue by developing a novel data structure—the “Clubcard” set membership test. Where the &lt;a href=&quot;https://ieeexplore.ieee.org/document/7958597&quot;&gt;original&lt;/a&gt; CRLite design used a “multi-level cascades of Bloom filters”, Clubcard-based CRLite uses a “partitioned two-level cascade of &lt;a href=&quot;https://engineering.fb.com/2021/07/09/core-infra/ribbon-filter/&quot;&gt;Ribbon filters&lt;/a&gt;”. The “two-level cascade” idea was presented by Mike Hamburg at &lt;a href=&quot;https://youtu.be/Htms5rNy7B8?list=PLeeS-3Ml-rpovBDh6do693We_CP3KTnHU&amp;amp;t=2359&quot;&gt;RWC 2022&lt;/a&gt;, and “partitioning” is an innovation of our own that we presented in a paper at &lt;a href=&quot;https://research.mozilla.org/files/2025/04/clubcards_for_the_webpki.pdf&quot;&gt;IEEE S&amp;amp;P 2025&lt;/a&gt; and a talk at &lt;a href=&quot;https://www.youtube.com/watch?v=gnB76DQI1GE&amp;amp;t=19510s&quot;&gt;RWC 2025&lt;/a&gt;.&lt;/p&gt;
  8992. &lt;h3&gt;Future improvements&lt;/h3&gt;
  8993. &lt;p&gt;We are working on making CRLite even more bandwidth efficient. We are developing new Clubcard partitioning strategies that will compress mass revocation events more efficiently. We are also integrating support for the HTTP &lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Compression_dictionary_transport&quot;&gt;compression dictionary transport&lt;/a&gt;, which will further compress delta updates. And we have successfully advocated for shorter &lt;a href=&quot;https://github.com/cabforum/servercert/pull/553&quot;&gt;certificate validity periods&lt;/a&gt;, which will reduce the number of CRLite artifacts that need to encode any given revocation. With these enhancements, we expect the bandwidth requirements of CRLite to trend down over the coming years, even as the TLS ecosystem itself continues to grow.&lt;/p&gt;
  8994. &lt;p&gt;Our &lt;a href=&quot;https://github.com/mozilla/clubcard&quot;&gt;Clubcard&lt;/a&gt; blocklist library, our instantiation of &lt;a href=&quot;https://github.com/mozilla/clubcard-crlite&quot;&gt;Clubcards for CRLite&lt;/a&gt;, and our &lt;a href=&quot;http://github.com/mozilla/crlite&quot;&gt;CRLite&lt;/a&gt; backend are freely available for anyone to use. We hope that our success in building fast, private, and comprehensive revocation checking for Firefox will encourage other software vendors to adopt this technology.&lt;/p&gt;
  8995. &lt;p&gt;The post &lt;a href=&quot;https://hacks.mozilla.org/2025/08/crlite-fast-private-and-comprehensive-certificate-revocation-checking-in-firefox/&quot;&gt;CRLite: Fast, private, and comprehensive certificate revocation checking in Firefox&lt;/a&gt; appeared first on &lt;a href=&quot;https://hacks.mozilla.org&quot;&gt;Mozilla Hacks - the Web developer blog&lt;/a&gt;.&lt;/p&gt;</description>
  8996. <pubDate>Tue, 19 Aug 2025 16:03:19 +0000</pubDate>
  8997. <dc:creator>John Schanck</dc:creator>
  8998. </item>
  8999. <item>
  9000. <title>Firefox Developer Experience: Firefox WebDriver Newsletter 142</title>
  9001. <guid isPermaLink="false">https://fxdx.dev/?p=507</guid>
  9002. <link>https://fxdx.dev/firefox-webdriver-newsletter-142/</link>
  9003. <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;WebDriver is a remote control interface that enables introspection and control of user agents.&lt;/em&gt; &lt;em&gt;As such it&lt;/em&gt; &lt;em&gt;can&lt;/em&gt; &lt;em&gt;help developers to verify that their websites are working and performing well with all major browsers. The protocol is standardized by the&lt;/em&gt;&lt;a href=&quot;https://www.w3.org/&quot;&gt;&lt;em&gt; W3C&lt;/em&gt;&lt;/a&gt;&lt;em&gt; and consists of two separate specifications:&lt;/em&gt;&lt;a href=&quot;https://w3c.github.io/webdriver/&quot;&gt;&lt;em&gt; WebDriver classic&lt;/em&gt;&lt;/a&gt;&lt;em&gt; (HTTP) and the new&lt;/em&gt;&lt;a href=&quot;https://w3c.github.io/webdriver-bidi/&quot;&gt;&lt;em&gt; WebDriver BiDi&lt;/em&gt;&lt;/a&gt;&lt;em&gt; (Bi-Directional).This newsletter gives an overview of the work we’ve done as part of the Firefox 142 release cycle&lt;/em&gt;.&lt;/p&gt;&lt;h3&gt;Contributions&lt;/h3&gt;&lt;p&gt;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.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;
  9004.  
  9005.  
  9006.  
  9007. &lt;p&gt;In Firefox 142, Sabina (sabina.zaripova) &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1969898&quot;&gt;renamed &lt;code&gt;Proxy&lt;/code&gt; capability class to &lt;code&gt;ProxyConfiguration&lt;/code&gt;&lt;/a&gt; to avoid confusion with JavaScript Proxy.&lt;/p&gt;
  9008.  
  9009.  
  9010.  
  9011. &lt;p&gt;Also, biyul.dev &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1931528&quot;&gt;reverted a workaround for &lt;code&gt;asyncOpenTime=0&lt;/code&gt;&lt;/a&gt; in WebDriver BiDi and &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1976504&quot;&gt;removed support for &lt;code&gt;localize_entity&lt;/code&gt; from the localization module&lt;/a&gt;.&lt;/p&gt;
  9012.  
  9013.  
  9014.  
  9015. &lt;p&gt;&lt;/p&gt;&lt;p&gt;WebDriver code is written in JavaScript, Python, and Rust so any web developer can contribute! Read&lt;a href=&quot;https://firefox-source-docs.mozilla.org/devtools/getting-started/README.html&quot;&gt; how to setup the work environment&lt;/a&gt; and check&lt;a href=&quot;https://codetribute.mozilla.org/projects/automation&quot;&gt; the list of mentored issues&lt;/a&gt; for Marionette, or the&lt;a href=&quot;https://codetribute.mozilla.org/languages/javascript?project%3DWebDriver%2520BiDi&quot;&gt; list of mentored JavaScript bugs for WebDriver BiDi&lt;/a&gt;. Join&lt;a href=&quot;https://chat.mozilla.org/#/room/#webdriver:mozilla.org&quot;&gt; our chatroom&lt;/a&gt; if you need any help to get started!&lt;/p&gt;&lt;p&gt;&lt;/p&gt;
  9016.  
  9017.  
  9018.  
  9019. &lt;h3&gt;General&lt;/h3&gt;
  9020.  
  9021.  
  9022.  
  9023. &lt;h4&gt;Removed: FTP proxy support from WebDriver capabilities&lt;/h4&gt;
  9024.  
  9025.  
  9026.  
  9027. &lt;p&gt;Support for &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1972670&quot;&gt;setting FTP proxy with WebDriver capabilities&lt;/a&gt; was completely removed. &lt;/p&gt;
  9028.  
  9029.  
  9030.  
  9031. &lt;h4&gt;Updated: the expiry value of the cookies set via WebDriver BiDi and WebDriver classic (Marionette)&lt;/h4&gt;
  9032.  
  9033.  
  9034.  
  9035. &lt;p&gt;The expiry value of all the cookies set via WebDriver BiDi and WebDriver classic (Marionette) is &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1974394&quot;&gt;limited now to 400 days&lt;/a&gt;.&lt;/p&gt;
  9036.  
  9037.  
  9038.  
  9039. &lt;h3&gt;WebDriver BiDi&lt;/h3&gt;
  9040.  
  9041.  
  9042.  
  9043. &lt;h4&gt;New: &lt;code&gt;emulation.setLocaleOverride&lt;/code&gt; command&lt;/h4&gt;
  9044.  
  9045.  
  9046.  
  9047. &lt;p&gt;Implemented &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1968952&quot;&gt;the new &lt;code&gt;emulation.setLocaleOverride&lt;/code&gt; command&lt;/a&gt; which allows clients to override a locale in JavaScript APIs. As all the other emulation commands, the locale override can be applied to the list of browsing contexts or user contexts IDs.&lt;/p&gt;
  9048.  
  9049.  
  9050.  
  9051. &lt;h4&gt;Updated: the &lt;code&gt;session.end&lt;/code&gt; command to resume the blocked requests&lt;/h4&gt;
  9052.  
  9053.  
  9054.  
  9055. &lt;p&gt;The &lt;code&gt;session.end&lt;/code&gt; command was updated to &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1974426&quot;&gt;resume all requests which were blocked by network interceptions&lt;/a&gt;.&lt;/p&gt;
  9056.  
  9057.  
  9058.  
  9059. &lt;h4&gt;Improved: support for setting proxy with &lt;code&gt;browser.createUserContext&lt;/code&gt; command&lt;/h4&gt;
  9060.  
  9061.  
  9062.  
  9063. &lt;p&gt;Added support for &lt;a href=&quot;http://bugzil.la/1977180&quot;&gt;host patterns like &lt;code&gt;.mozilla.org&lt;/code&gt; in &lt;code&gt;noProxy&lt;/code&gt; property&lt;/a&gt; and fixed a bug when setting &lt;a href=&quot;https://bugzil.la/1977168&quot;&gt;a HTTP proxy wouldn’t allow navigating to HTTPS URLs&lt;/a&gt;.&lt;/p&gt;
  9064.  
  9065.  
  9066.  
  9067. &lt;h4&gt;Bug fixes&lt;/h4&gt;
  9068.  
  9069.  
  9070.  
  9071. &lt;ul&gt;
  9072. &lt;li&gt;&lt;code&gt;browsingContext.create&lt;/code&gt; command will not &lt;a href=&quot;https://bugzil.la/1841125&quot;&gt;fail anymore after a &lt;code&gt;browsingContext.print&lt;/code&gt; command was interrupted by closing a tab with the &lt;code&gt;browsingContext.close&lt;/code&gt; command&lt;/a&gt;.&lt;/li&gt;
  9073. &lt;/ul&gt;
  9074.  
  9075.  
  9076.  
  9077. &lt;h3&gt;Marionette&lt;/h3&gt;
  9078.  
  9079.  
  9080.  
  9081. &lt;h4&gt;Updated: the &lt;code&gt;WebDriver:AddCookie&lt;/code&gt; command to throw an error for &lt;code&gt;sameSite=none&lt;/code&gt; and &lt;code&gt;secure=false&lt;/code&gt; attributes&lt;/h4&gt;
  9082.  
  9083.  
  9084.  
  9085. &lt;p&gt;From now on, &lt;a href=&quot;https://bugzil.la/1977205&quot;&gt;the &lt;code&gt;WebDriver:AddCookie&lt;/code&gt; command will throw an error when a target cookie has &lt;code&gt;sameSite=none&lt;/code&gt; and &lt;code&gt;secure=false&lt;/code&gt; attributes&lt;/a&gt;.&lt;/p&gt;
  9086.  
  9087.  
  9088.  
  9089. &lt;h4&gt;Removed: the dialog text value from the &lt;code&gt;unexpected alert open&lt;/code&gt; error message&lt;/h4&gt;
  9090.  
  9091.  
  9092.  
  9093. &lt;p&gt;&lt;a href=&quot;http://bugzil.la/1948236&quot;&gt;The &lt;code&gt;unexpected alert open&lt;/code&gt; error message will not contain anymore the dialog text value&lt;/a&gt;, since it is available via the &lt;code&gt;data&lt;/code&gt; field.&lt;/p&gt;</description>
  9094. <pubDate>Tue, 19 Aug 2025 14:58:36 +0000</pubDate>
  9095. <dc:creator>Alexandra Borovova</dc:creator>
  9096. </item>
  9097. <item>
  9098. <title>The Rust Programming Language Blog: Demoting x86_64-apple-darwin to Tier 2 with host tools</title>
  9099. <guid isPermaLink="true">https://blog.rust-lang.org/2025/08/19/demoting-x86-64-apple-darwin-to-tier-2-with-host-tools/</guid>
  9100. <link>https://blog.rust-lang.org/2025/08/19/demoting-x86-64-apple-darwin-to-tier-2-with-host-tools/</link>
  9101. <description>&lt;p&gt;In Rust 1.90.0, the target &lt;code&gt;x86_64-apple-darwin&lt;/code&gt; will be demoted to Tier 2 with host tools.
  9102. The standard library and the compiler will continue to be built and distributed,
  9103. but automated tests of these components are no longer guaranteed to be run.&lt;/p&gt;
  9104. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/08/19/demoting-x86-64-apple-darwin-to-tier-2-with-host-tools/#background&quot;&gt;&lt;/a&gt;
  9105. Background&lt;/h3&gt;
  9106. &lt;p&gt;Rust has supported macOS for a long time,
  9107. with some amount of support dating back to Rust 0.1 and likely before that.
  9108. During that time period,
  9109. Apple has changed CPU architectures from x86 to x86_64 and now to Apple silicon,
  9110. ultimately announcing the &lt;a href=&quot;https://en.wikipedia.org/wiki/Mac_transition_to_Apple_silicon#Timeline&quot;&gt;end of support&lt;/a&gt; for the x86_64 architecture.&lt;/p&gt;
  9111. &lt;p&gt;Similarly,
  9112. &lt;a href=&quot;https://github.blog/changelog/2025-07-11-upcoming-changes-to-macos-hosted-runners-macos-latest-migration-and-xcode-support-policy-updates/#macos-13-is-closing-down&quot;&gt;GitHub has announced&lt;/a&gt; that they will no longer provide free macOS x86_64 runners for public repositories.
  9113. The Rust Project uses these runners to execute automated tests for the &lt;code&gt;x86_64-apple-darwin&lt;/code&gt; target.
  9114. Since the &lt;a href=&quot;https://doc.rust-lang.org/stable/rustc/target-tier-policy.html&quot;&gt;target tier policy&lt;/a&gt; requires that Tier 1 platforms must run tests in CI,
  9115. the &lt;code&gt;x86_64-apple-darwin&lt;/code&gt; target must be demoted to Tier 2.&lt;/p&gt;
  9116. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/08/19/demoting-x86-64-apple-darwin-to-tier-2-with-host-tools/#what-changes&quot;&gt;&lt;/a&gt;
  9117. What changes?&lt;/h3&gt;
  9118. &lt;p&gt;Starting with Rust 1.90.0, &lt;code&gt;x86_64-apple-darwin&lt;/code&gt; will be Tier 2 with host tools.
  9119. For users,
  9120. nothing will change immediately;
  9121. builds of both the standard library and the compiler will still be distributed by the Rust Project for use via &lt;code&gt;rustup&lt;/code&gt; or alternative installation methods.&lt;/p&gt;
  9122. &lt;p&gt;Over time,
  9123. this target will likely accumulate bugs faster due to reduced testing.&lt;/p&gt;
  9124. &lt;h3&gt;&lt;a class=&quot;anchor&quot; href=&quot;https://blog.rust-lang.org/2025/08/19/demoting-x86-64-apple-darwin-to-tier-2-with-host-tools/#future&quot;&gt;&lt;/a&gt;
  9125. Future&lt;/h3&gt;
  9126. &lt;p&gt;If the &lt;code&gt;x86_64-apple-darwin&lt;/code&gt; target causes concrete problems,
  9127. it may be demoted further.
  9128. No plans for further demotion have been made yet.&lt;/p&gt;
  9129. &lt;p&gt;For more details on the motivation of the demotion, see &lt;a href=&quot;https://rust-lang.github.io/rfcs/3841-demote-x86_64-apple-darwin.html&quot;&gt;RFC 3841&lt;/a&gt;.&lt;/p&gt;</description>
  9130. <pubDate>Tue, 19 Aug 2025 00:00:00 +0000</pubDate>
  9131. <dc:creator>Jake Goulding</dc:creator>
  9132. </item>
  9133.  
  9134. </channel>
  9135. </rss>
  9136.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//planet.mozilla.org/rss20.xml

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda