FEED Validator

Congratulations!

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.

• line 1324, column 0: style attribute contains potentially dangerous content: border-radius (13 occurrences) [help]

  <blockquote class="instagram-media"><div style="padd ...
  

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>Firefox Nightly: Today’s Forecast: Browser Improvements – These Weeks in Firefox: Issue 161</title>
16. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1641</guid>
17. <link>https://blog.nightly.mozilla.org/2024/05/17/todays-forecast-browser-improvements-these-weeks-in-firefox-issue-161/</link>
18. <description>&lt;h3&gt;Highlights&lt;/h3&gt;
19. <ul>
20. <li>Volunteer contributor tamas.beno12 <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=28354">has fixed a 5 digit (25 year old) bug</a>! The patch for the bug makes it easier to create transparent windows</li>
21. <li>The newtab team is experimenting with a weather widget! It’s still early days, but you can turn it on in Nightly with a set of 2 prefs found in about:config:
22. <ul>
23. <li>Set the following to true:
24. <ul>
25. <li>browser.newtabpage.activity-stream.showWeather</li>
26. <li>browser.newtabpage.activity-stream.system.showWeather</li>
27. </ul>
28. </li>
29. <li><img src="https://blog.nightly.mozilla.org/files/2024/05/headlines161_0.png" /></li>
30. <li>If you notice any bugs with it, you can <a href="https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&bug_ignored=0&bug_severity=--&bug_status=NEW&cf_a11y_review_project_flag=---&cf_accessibility_severity=---&cf_fx_iteration=---&cf_fx_points=---&cf_has_str=---&cf_install_update_workflow=---&cf_performance_impact=---&cf_status_firefox126=---&cf_status_firefox127=---&cf_status_firefox128=---&cf_status_firefox_esr115=---&cf_tracking_firefox126=---&cf_tracking_firefox127=---&cf_tracking_firefox128=---&cf_tracking_firefox_esr115=---&cf_tracking_firefox_relnote=---&cf_webcompat_priority=---&component=New%20Tab%20Page&contenttypemethod=list&contenttypeselection=text%2Fplain&defined_groups=1&filed_via=standard_form&flag_type-203=X&flag_type-37=X&flag_type-41=X&flag_type-607=X&flag_type-708=X&flag_type-721=X&flag_type-737=X&flag_type-748=X&flag_type-787=X&flag_type-799=X&flag_type-803=X&flag_type-846=X&flag_type-855=X&flag_type-864=X&flag_type-930=X&flag_type-936=X&flag_type-937=X&flag_type-963=X&needinfo_role=other&needinfo_type=needinfo_from&op_sys=Unspecified&priority=--&product=Firefox&rep_platform=Unspecified&target_milestone=---&version=unspecified">file them under Firefox :: New Tab Page</a></li>
31. </ul>
32. </li>
33. <li>Some nice updates to Picture-in-Picture:
34. <ul>
35. <li>Volunteer contributor Joseph Webster <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1818054">added captions support</a> for Vimeo players!</li>
36. <li>kpatenio <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888691">added captions support and fixed some live video playback issues for Canal+ and Timvision</a> when opened in the Picture-in-Picture player window
37. <ul>
38. <li>Thanks to leojellimann for helping identify how video captions are loaded. Without his help, this patch would not have been possible!</li>
39. </ul>
40. </li>
41. </ul>
42. </li>
43. <li>Bounce Tracking Protection has been enabled in Nightly (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1846492">Bug 1846492</a>)
44. <ul>
45. <li><a href="https://blog.mozilla.org/security/2020/08/04/firefox-79-includes-protections-against-redirect-tracking/">What is bounce tracking / redirect tracking?</a></li>
46. <li>The feature detects bounce trackers based on redirect behaviour and periodically purges their cookies & site data to prevent tracking.</li>
47. <li>If you notice that you lose site data or get logged out of sites more than usual please file a bug under <a href="https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&bug_ignored=0&bug_severity=--&bug_status=NEW&cf_a11y_review_project_flag=---&cf_accessibility_severity=---&cf_fx_iteration=---&cf_fx_points=---&cf_has_str=---&cf_performance_impact=---&cf_status_firefox126=---&cf_status_firefox127=---&cf_status_firefox128=---&cf_status_firefox_esr115=---&cf_status_thunderbird_esr115=---&cf_tracking_firefox126=---&cf_tracking_firefox127=---&cf_tracking_firefox128=---&cf_tracking_firefox_esr115=---&cf_tracking_firefox_relnote=---&cf_tracking_thunderbird_esr115=---&cf_webcompat_priority=---&component=Privacy%3A%20Anti-Tracking&contenttypemethod=list&contenttypeselection=text%2Fplain&defined_groups=1&filed_via=standard_form&flag_type-203=X&flag_type-37=X&flag_type-41=X&flag_type-607=X&flag_type-721=X&flag_type-737=X&flag_type-787=X&flag_type-799=X&flag_type-803=X&flag_type-846=X&flag_type-855=X&flag_type-863=X&flag_type-864=X&flag_type-930=X&flag_type-936=X&flag_type-937=X&flag_type-963=X&needinfo_role=other&needinfo_type=needinfo_from&op_sys=Unspecified&priority=--&product=Core&rep_platform=Unspecified&target_milestone=---&version=unspecified">Core :: Privacy: Anti-Tracking</a> so we can investigate</li>
48. <li>The feature is still in development so detected trackers are not yet counted as part of our regular ETP stats or on about:protections.</li>
49. <li>Advanced: If you want to see which bounce trackers get detected and purged you can enable the logging by going to about:logging and adding the following logger: BounceTrackingProtection:3</li>
50. </ul>
51. </li>
52. <li>Niklas <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1801957">made the screenshots initial state (crosshairs) keyboard accessible</a>
53. <ul>
54. <li>The arrow keys can be used to move the cursor around the content area. Enter will select the current hovered region and space will start the dragging state to draw a region.</li>
55. </ul>
56. </li>
57. </ul>
58. <h3>Friends of the Firefox team</h3>
59. <h3><a href="https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20%28excluding%20employees%29&quicksearch=1893985%2C1893607%2C1893935%2C1894063%2C1798464%2C1880909%2C1845151%2C1895154%2C1868943%2C1895564%2C1742889%2C1895398%2C1896034%2C1892052%2C1896360&list_id=17031415">Resolved bugs (excluding employees)</a></h3>
60. <h4>Volunteers that fixed more than one bug</h4>
61. <ul>
62. <li>Itiel</li>
63. </ul>
64. <h4>New contributors (🌟 = first patch)</h4>
65. <ul>
66. <li>endington543 <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893985">removed incorrect and unnecessary strict statement</a> from FxAccountsProfileClient.sys.mjs</li>
67. <li>Joseph Webster <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1894063">added PiP captions support</a> for additional sites that use JWPlayer</li>
68. <li>Leeya <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1742889">rewrote consumers of whereToOpenLink</a> to use BrowserUtils.whereToOpenLink</li>
69. <li>Steve P <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1880909">moved gBrowserInit to its own file</a></li>
70. </ul>
71. <h3>Project Updates</h3>
72. <h4>Add-ons / Web Extensions</h4>
73. <h5>Addon Manager & about:addons</h5>
74. <ul>
75. <li>As already anticipated in this meeting, starting from Firefox 127, installing new single-signed add-ons is disallowed. The QA verification has been completed and this restriction is now enabled on all channels and riding the Firefox 127 release train (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886160">Bug 1886160</a>).</li>
76. </ul>
77. <h5>WebExtension APIs</h5>
78. <ul>
79. <li>Starting from Firefox 127, the installType property returned by the management API (e.g. management.getSelf) will be set to ”admin” for extensions that are installed through Enterprise Policy Settings (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1895341">Bug 1895341</a>)
80. <ul>
81. <li>Thanks to mkaply for working on this API improvement for Enterprise Firefox add-ons!</li>
82. </ul>
83. </li>
84. <li>As part of the ongoing work related to improving cross-browser compatibility for Manifest Version 3 extensions, starting from Firefox 127:
85. <ul>
86. <li>Host permissions requested by Manifest V3 extensions will be listed in the install dialog and granted as part of the add-on installation flow (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889402">Bug 1889402</a>).</li>
87. <li>Extensions using the ”incognito”: “split” mode will be allowed to install successfully in Firefox (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1876924">Bug 1876924</a>)
88. <ul>
89. <li>Incognito split mode is still not supported in Firefox, and so the extensions using this mode will not be allowed access to private browsing tabs.</li>
90. </ul>
91. </li>
92. <li>The new runtime.getContexts API method is now supported (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1875480">Bug 1875480</a>).
93. <ul>
94. <li>This new API method allows extensions to discover their existing Extensions contexts (but unlike runtime.getViews it returns a json representation of the metadata for the related extension contexts).</li>
95. </ul>
96. </li>
97. </ul>
98. </li>
99. </ul>
100. <h4>Developer Tools</h4>
101. <h5>DevTools</h5>
102. <ul>
103. <li><a href="https://bugzilla.mozilla.org/user_profile?user_id=697330">Pier Angelo Vendrame</a> prevented new request data to be persisted in Private Browsing (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1892052">#1892052</a>)</li>
104. <li>Arai fixed exceptions that could happen when evaluating Services.prompt and Services.droppedLinkHandler in the Browser Console (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893611">#1893611</a>)</li>
105. <li>Nicolas fixed an issue that was preventing users to see stacktrace from WASM-issued error messages (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888645">#1888645</a>)</li>
106. <li>Alexandre managed to tackle an issue that would prevent DevTools to be initialized when a page was using Atomics.wait , e.g. <a href="http://stackblitz.com">stackblitz.com</a> (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1821250">#1821250</a>)</li>
107. <li>Nicolas added the new textInput event to the Event Listener Breakpoints in the Debugger (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1892459">#1892459</a>)</li>
108. <li>Hubert is making good progress migrating the Debugger to CodeMirror 6 (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1887649">#1887649</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889277">#1889277</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889283">#1889283</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1894379">#1894379</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1894659">#1894659</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889276">#1889276</a>)</li>
109. <li>Nicolas made sure that ::backdrop pseudo-element rules are visible in the Rules view for popover elements (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893644">#1893644</a>), as well as @keyframes rules nested in other at-rules (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1894603">#1894603</a>)</li>
110. <li>Nicolas fixed performance issue in the Inspector when displaying deeply nested rule (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1844446">#1844446</a>)
111. <ul>
112. <li>for example, a 15-level deep rule was taking almost <b>9 seconds</b> to be displayed, now it’s only <b>a few milliseconds </b></li>
113. </ul>
114. </li>
115. <li>Julian removed code that was forcing the Performance tab to be always enabled in the Browser Toolbox, even if the user disabled it in a previous session (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1895434">#1895434</a>)</li>
116. </ul>
117. <h5>WebDriver BiDi</h5>
118. <ul>
119. <li>Thanks to Victoria Ajala for replacing the usage of the “isElementEnabled” selenium atom with a custom implementation which is more lightweight and maintainable (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1798464">#1798464</a>)</li>
120. <li>Sasha implemented the permissions.setPermission command which allows clients to set permissions such as geolocation, notifications, … (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1875065">#1875065</a>)</li>
121. <li>Sasha fixed a bug where wheel scroll actions would not use the provided modifiers (eg shift, ctrl, …) (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885542">#1885542</a>)</li>
122. <li>Sasha improved the implementation of the browsingContext.locateNodes command to also accept Document objects as the root to locate nodes. Previously this was restricted to Elements only, but Puppeteer relies heavily on using Document for this command. (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893922">#1893922</a>)</li>
123. <li>Henrik fixed a bug where the WebDriver classic GetElementText command would fail to capitalise text containing a underscore (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888004">#1888004</a>)</li>
124. </ul>
125. <h4>Migration Improvements</h4>
126. <ul>
127. <li>Device Migration
128. <ul>
129. <li>We’ve completed the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885369">staging</a> and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885955">recovery</a> metabugs, and have started into the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890579">management UI metabug</a>. We’re also branching a bit, and some of us are working on the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890322">single-file archive metabug</a>.</li>
130. </ul>
131. </li>
132. </ul>
133. <h4>New Tab Page</h4>
134. <ul>
135. <li>Newtab wallpaper experiment going out either this release (next week) or next release, depending on some telemetry bug fix uplifts.
136. <ul>
137. <li>To enable wallpapers on HNT, set the following to TRUE:
138. <ul>
139. <li>browser.newtabpage.activity-stream.newtabWallpapers.enabled</li>
140. </ul>
141. </li>
142. </ul>
143. </li>
144. <li>Newtab wallpapers are getting some updates soon. A bunch more wallpapers as options, and some tweaks to the customize menu, a nested menu, to better organize the wallpapers so it’s easier to explore as we add more options.</li>
145. </ul>
146. <h4>Picture-in-Picture</h4>
147. <ul>
148. <li>Thanks to Joseph Webster for adding PiP captions support for more sites with our JWPlayer wrapper (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1894063">bug</a>)</li>
149. </ul>
150. <h4>Performance</h4>
151. <ul>
152. <li>mconley <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1503809">has patches up that move the favicon-fetching part of the Windows Jump List off of the main thread</a>.</li>
153. </ul>
154. <h4>Screenshots</h4>
155. <ul>
156. <li>Thanks to Kelly for joining the screenshots team!</li>
157. <li>Kelly <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1730169">added the “take screenshot”</a> item to image and video elements</li>
158. <li>Niklas fixed a bug where <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1894740">clicking the preview copy or download buttons</a> before the image loaded would not actually save the image</li>
159. <li>Niklas <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1892125">refactored the screenshots preview</a> to use LitElement and moz-button</li>
160. <li>Niklas fixed an issue with <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893680">RTL pages with negative scrollMinX</a></li>
161. </ul>
162. <h4>Search and Navigation</h4>
163. <ul>
164. <li>Clipboard suggestions have been temporarily disabled in nightly as it was possible to freeze Firefox on Windows – we’re moving the feature to asynchronous clipboard API – <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1894614">1894614</a></li>
165. <li>Features for an update to the urlbar UX codenamed scotchBonnet have started landing, secondary Actions have landed and dedicated search button + others are in progress. These will be enabled in nightly at some point so keep an eye out. Meta bug tracking @ <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891857">1891857</a></li>
166. <li>Mandy fixed an issue with stripping a leading question mark when the urlbar is already in search mode @ <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1837624">1837624</a></li>
167. <li>Marco fixed protocols being trimmed when copying urls @ ​​<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893871">1893871</a>
168. <ul>
169. <li>In Nightly, when https stripping is enabled, the loaded URL will gain back the trimmed protocol when the user interacts with the urlbar input field text</li>
170. </ul>
171. </li>
172. <li>Marco changed domain inline completion, so that when permanent private browsing is active domain will be picked based on the number of bookmarks to that domain. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893840">Bug 1893840</a></li>
173. <li>The new search configuration (aka search consolidation) is now rolling out in FF 126 release.
174. <ul>
175. <li>Ebay support in Poland has been added to application provided engines in the new search configuration and so will become available during FF 126 @ <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885391">1885391</a></li>
176. </ul>
177. </li>
178. <li>For Places, Daisuke removed the ReplaceFaviconData() and ReplaceFaviconDataFromDataURL() APIs, replacing their use with a new SetFaviconForPage() API accepting a data URL for the favicon. Long term this is the API we want to use, Places should never fetch from the Network, only store data.</li>
179. </ul>
180. <h4>Storybook/Reusable Components</h4>
181. <ul>
182. <li>Work has started on form components with an eye for the Sidebar Settings feature (and potentially the Experiments section of preferences). Initial components: moz-checkbox, moz-radio-group and moz-fieldset</li>
183. </ul>
184. &lt;p&gt;The message-bar component has been fully removed from the codebase (replaced by moz-message-bar) &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=1845151&quot;&gt;Bug 1845151 – Remove all code associated with the message-bar component&lt;/a&gt; – Thanks Anna!&lt;/p&gt;</description>
185. <pubDate>Fri, 17 May 2024 20:24:08 +0000</pubDate>
186. <dc:creator>Niklas Baumgardner</dc:creator>
187. </item>
188. <item>
189. <title>Firefox Developer Experience: Firefox DevTools Newsletter — 126</title>
190. <guid isPermaLink="false">https://fxdx.dev/?p=273</guid>
191. <link>https://fxdx.dev/firefox-devtools-newsletter-126/</link>
192. <description>&lt;p id=&quot;block-42a3529c-86fa-43e3-a037-427905914805&quot;&gt;&lt;em&gt;Developer Tools help developers write and debug websites on Firefox. This newsletter gives an overview of the work we’ve done as part of the Firefox 126 Nightly release cycle.&lt;/em&gt;&lt;/p&gt;
193.  
194.  
195.  
196. <hr class="wp-block-separator has-alpha-channel-opacity" />
197.  
198.  
199.  
200. <p id="block-af771a18-b7d9-4c63-9879-0a4a0dd015b4">Firefox being an open source project, we are grateful to get contributions from people outside of Mozilla, like <a href="https://bugzilla.mozilla.org/user_profile?user_id=750915">Artem Manushenkov</a> who added a setting that can be used to disable <a href="https://firefox-source-docs.mozilla.org/devtools-user/web_console/split_console/index.html">the split console</a> (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1731635">#1731635</a>).</p>
201.  
202.  
203.  
204. <p></p>
205.  
206.  
207.  
208. <figure class="wp-block-image aligncenter size-large"><img alt="Firefox DevTools settings panel. Along side many items, there a new "Enable Split Console" checkbox in the Web Console section" class="wp-image-286" height="205" src="https://fxdx.dev/files/2024/05/CleanShot-2024-05-17-at-14.36.31-600x205.png" width="600" /></figure>
209.  
210.  
211.  
212. <p class="has-background-secondary-background-color has-background" id="block-9944af63-0ae5-4c30-a32d-8ebfda4b5527">Want to help? DevTools are written in HTML, CSS and JS so any web developer can contribute! Read <a href="https://firefox-source-docs.mozilla.org/devtools/getting-started/README.html">how to setup the work environment</a> and check <a href="https://codetribute.mozilla.org/projects/devtools">the list of mentored issues</a></p>
213.  
214.  
215.  
216. <h3>Performance</h3>
217.  
218.  
219.  
220. <p>As announced in <a href="https://fxdx.dev/firefox-devtools-newsletter-124/">previous</a> <a href="https://fxdx.dev/firefox-devtools-newsletter-125/">newsletters</a>, we’re focusing on performance for a few months to make our tools as fast as they can be.</p>
221.  
222.  
223.  
224. <p>A few years back, we got a report from a user telling us that modifying a property in a rule from the Inspector was very slow (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1644138">#1644138</a>). The stylesheet they were using was massive, with 185K lines of code and a total size of approximately 4 MB, and our machinery to replace the rule content was not handling this well. After rewriting some old Javascript code in Rust (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1882964">#1882964</a>), the function call that was taking more than <strong>500ms</strong> on my machine now only takes about <strong>10ms</strong>. Yes, that’s <strong>50 times faster</strong>! This also shows in less extreme cases: our performance tests are reporting an almost 10% improvement to display Rules in the Inspector <img alt="🎉" class="wp-smiley" src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f389.png" style="height: 1em;" /></p>
225.  
226.  
227.  
228. <p></p>
229.  
230.  
231.  
232. <figure class="wp-block-image aligncenter size-large"><img alt="Chart where x is the time and y is duration, where we can see the values going from 750ms to 700ms around April 8th" class="wp-image-287" height="176" src="https://fxdx.dev/files/2024/05/CleanShot-2024-05-17-at-15.23.00-600x176.png" width="600" /><figcaption class="wp-element-caption">Performance test duration going from ~750ms to ~700ms</figcaption></figure>
233.  
234.  
235.  
236. <p>We also came across an issue that showed a pretty bad mistake when handling rules using pseudo-elements (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886947">#1886947</a>), and fixing it, alongside some minor tweak <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886818">(#1886818</a>), got us another ~10% improvement when displaying Rules in the Inspector. </p>
237.  
238.  
239.  
240. <p>Finally, we realized we could have some unnecessary computation when editing a rule (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888079">#1888079</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888081">#1888081</a>), so we fixed that for an even smoother experience.</p>
241.  
242.  
243.  
244. <h3>Custom State</h3>
245.  
246.  
247.  
248. <p>Firefox 126 adds support for <a href="https://developer.mozilla.org/en-US/docs/Web/API/CustomStateSet"><code>CustomStateSet</code></a> (mostly done by an external contributor, <a href="https://www.keithcirkel.co.uk/">Keith Cirkel</a>):</p>
249.  
250.  
251.  
252. <blockquote class="wp-block-quote">
253. <p style="margin-top: 0; margin-bottom: 0;">The <strong><code>CustomStateSet</code></strong> interface of the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model">Document Object Model</a> stores a list of states for an <a href="https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements#types_of_custom_element">autonomous custom element</a>, and allows states to be added and removed from the set.</p>
254.  
255.  
256.  
257. <p>The interface can be used to expose the internal states of a custom element, allowing them to be used in CSS selectors by code that uses the element.</p>
258. <cite>MDN</cite></blockquote>
259.  
260.  
261.  
262. <p>The <a href="https://developer.mozilla.org/en-US/docs/Web/API/CustomStateSet">MDN page</a> has some nice examples on how this can be used to style custom elements based on a specific state. Rules using the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/:state"><code>:state()</code></a> pseudo-class are displayed in the Inspector and its properties can be modified like any other rules.</p>
263.  
264.  
265.  
266. <p></p>
267.  
268.  
269.  
270. <figure class="wp-block-image aligncenter size-large"><img alt="Firefox DevTools Inspector panel. The markup view has a `<label-checkbox>` custom element selected. In the rules view, we can see a few rules using `:state(checked)`, which are using to style the element" class="wp-image-285" height="242" src="https://fxdx.dev/files/2024/05/CleanShot-2024-05-17-at-14.24.16-600x242.png" width="600" /></figure>
271.  
272.  
273.  
274. <p>You can quickly see which states are in the set when logging a CustomStateSet instance in the console (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1862896">#1862896</a>).</p>
275.  
276.  
277.  
278. <p></p>
279.  
280.  
281.  
282. <figure class="wp-block-image aligncenter size-large"><img alt="Firefox DevTools Console with the following code being executed: `document.querySelector("labeled-checkbox")._internals.states`  The results shows an object whose header is`CustomStateSet [ "checked" ]`. The object is expanded, and we can see that it has a `<entries>` node, which contains one item, which is `"checked"`" class="wp-image-284" height="123" src="https://fxdx.dev/files/2024/05/CleanShot-2024-05-17-at-14.24.40-600x123.png" width="600" /></figure>
283.  
284.  
285.  
286. <p><br /></p>
287.  
288.  
289.  
290. <h3>And more…</h3>
291.  
292.  
293.  
294. <ul>
295. <li>We’re currently working on migrating our CodeMirror usage to <a href="https://codemirror.net/">CodeMirror 6</a> (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1773246">#1773246</a>), which we hope will allow for performance improvement in the Debugger. This is a pretty big task and we’ll report progress in the next newsletters!</li>
296.  
297.  
298.  
299. <li>We added support for <a href="https://github.com/WebAssembly/exception-handling/">Wasm exception handling proposal</a> in the Debugger (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885589">#1885589</a>)</li>
300.  
301.  
302.  
303. <li>We’re now showing the color swatch when a CSS custom property is used in color definition (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1718894">#1718894</a>)</li>
304.  
305.  
306.  
307. <li>In order to enable debugging Firefox on Android devices, we maintain an ADB extension,  we finally released a new version of the DevTools ADB extension that is used by <a href="https://firefox-source-docs.mozilla.org/devtools-user/about_colon_debugging/index.html">about:debugging</a>. The extension is now shipping with notarized binaries and can be used on recent macOS versions (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890843">#1890843</a>)</li>
308. </ul>
309.  
310.  
311.  
312. &lt;p class=&quot;has-text-align-center has-background-secondary-background-color has-background&quot;&gt;&lt;strong&gt;That’s all folks, see you in June for the 127 newsletter!&lt;/strong&gt;&lt;/p&gt;</description>
313. <pubDate>Fri, 17 May 2024 14:31:51 +0000</pubDate>
314. <dc:creator>Nicolas Chevobbe</dc:creator>
315. </item>
316. <item>
317. <title>Mozilla Thunderbird: The New Thunderbird Website Has Hatched</title>
318. <guid isPermaLink="false">https://blog.thunderbird.net/?p=1756</guid>
319. <link>https://blog.thunderbird.net/2024/05/the-new-thunderbird-website-has-hatched/</link>
320. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;321&quot; src=&quot;https://blog.thunderbird.net/files/2024/05/The-New-Thunderbird.net_.png&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
321. <p><a href="http://Thunderbird.net">Thunderbird.net</a> has a new look, but the improvements go beyond that. We wanted a website where you could quickly find the information you need, from support to contribution, in clear and easy to understand text. While staying grateful to the many amazing contributors who have helped build and maintain our website over the past 20 years, we wanted to refresh our information along with our look. Finally, we wanted to partner with Freehive’s Ryan Gorley for their sleek, cohesive design vision and commitment to open source.</p>
322.  
323.  
324.  
325. <p>We wanted a website that’s ready for the next 20 years of Thunderbird, including the upcoming arrival of Thunderbird on mobile devices. But you don’t have to wait for that future to experience the new website now.</p>
326.  
327.  
328.  
329. <h3>The New Thunderbird.net</h3>
330.  
331.  
332.  
333. <p>The new, more organized framework starts with the refreshed Home page. All the great content you’ve relied on is still here, just easier to find! The expanded navigation menu makes it almost effortless to find the information and resources you need.</p>
334.  
335.  
336.  
337. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/05/TBWebsiteResources.png"><img alt="" class="wp-image-1757" height="337" src="https://blog.thunderbird.net/files/2024/05/TBWebsiteResources-600x337.png" width="600" /></a></figure>
338.  
339.  
340.  
341. <p></p>
342.  
343.  
344.  
345. <p>Resources provide a quick link to all the news and updates in the Thunderbird Blog and the unmatched community assistance in Mozilla Support, aka SUMO. Release notes are linked from the <a href="https://www.thunderbird.net/thunderbird/all/" rel="noreferrer noopener" target="_blank">download and other options page</a>. That page has also been simplified while still maintaining all the usual options. It’s now the main way to get links to download Beta and Daily, and in the future any other apps or versions we produce.</p>
346.  
347.  
348.  
349. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/05/TBWebsiteDownloads.png"><img alt="" class="wp-image-1758" height="414" src="https://blog.thunderbird.net/files/2024/05/TBWebsiteDownloads-600x414.png" width="600" /></a></figure>
350.  
351.  
352.  
353. <p></p>
354.  
355.  
356.  
357. <p>The About section introduces the values and the people behind the Thunderbird project, which includes our growing MZLA team. Our contact page connects you with the right community resources or team member, no matter your question or concern. And if you’d like to join us, or just see what positions are open, you’ll find a link to our career page here.</p>
358.  
359.  
360.  
361. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/05/TBCommunity.png"><img alt="" class="wp-image-1759" height="200" src="https://blog.thunderbird.net/files/2024/05/TBCommunity-600x200.png" width="600" /></a></figure>
362.  
363.  
364.  
365. <p></p>
366.  
367.  
368.  
369. <p>Whether it’s giving your time and skill or making a financial donation, it’s easy to discover all the ways to contribute to the project. Our new and improved Participate page shows how to get involved, from coding and testing to everyday advocacy. No matter your talents and experience, everyone can contribute!</p>
370.  
371.  
372.  
373. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/05/TBWebsiteCareer.gif"><img alt="" class="wp-image-1760" height="410" src="https://blog.thunderbird.net/files/2024/05/TBWebsiteCareer-600x410.gif" width="600" /></a></figure>
374.  
375.  
376.  
377. <p></p>
378.  
379.  
380.  
381. <p>If you want to download the latest stable release, or to donate and help bring Thunderbird everywhere, those options are still an easy click from the navigation menu.</p>
382.  
383.  
384.  
385. <h3>Your Feedback</h3>
386.  
387.  
388.  
389. <p>We’d love to have your thoughts and feedback on the new website. Is there a new and improved section you love? Is there something we missed? Let us know in the comments below. Want to see all the changes we made? Check <a href="https://github.com/thunderbird/thunderbird-website/commits/master/" rel="noreferrer noopener" target="_blank">the repository</a> for the detailed commit log.</p>
390. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2024/05/the-new-thunderbird-website-has-hatched/&quot;&gt;The New Thunderbird Website Has Hatched&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>
391. <pubDate>Fri, 17 May 2024 11:00:00 +0000</pubDate>
392. <dc:creator>Monica Ayhens-Madon</dc:creator>
393. </item>
394. <item>
395. <title>The Rust Programming Language Blog: Faster linking times on nightly on Linux using `rust-lld`</title>
396. <guid isPermaLink="true">https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html</guid>
397. <link>https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html</link>
398. <description>&lt;p&gt;TL;DR: rustc will use &lt;code&gt;rust-lld&lt;/code&gt; by default on &lt;code&gt;x86_64-unknown-linux-gnu&lt;/code&gt; on nightly to
399. significantly reduce linking times.</p>
400. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html#some-context" id="some-context"></a>Some context</h4>
401. <p>Linking time is often a big part of compilation time. When rustc needs to build a binary or a shared
402. library, it will usually call the default linker installed on the system to do that (this can be
403. changed on the command-line or by the target for which the code is compiled).</p>
404. <p>The linkers do an important job, with concerns about stability, backwards-compatibility and so on.
405. For these and other reasons, on the most popular operating systems they usually are older programs,
406. designed when computers only had a single core. So, they usually tend to be slow on a modern
407. machine. For example, when building ripgrep 13 in debug mode on Linux, roughly half of the time is
408. actually spent in the linker.</p>
409. <p>There are different linkers, however, and the usual advice to improve linking times is to use one of
410. these newer and faster linkers, like LLVM's <a href="https://lld.llvm.org/"><code>lld</code></a> or Rui Ueyama's
411. <a href="https://github.com/rui314/mold"><code>mold</code></a>.</p>
412. <p>Some of Rust's wasm and aarch64 targets already use <code>lld</code> by default. When using rustup, rustc ships
413. with a version of <code>lld</code> for this purpose. When CI builds LLVM to use in the compiler, it also builds
414. the linker and packages it. It's referred to as <code>rust-lld</code> to avoid colliding with any <code>lld</code> already
415. installed on the user's machine.</p>
416. <p>Since improvements to linking times are substantial, it would be a good default to use in the most
417. popular targets. This has been discussed for a long time, for example in issues
418. <a href="https://github.com/rust-lang/rust/issues/39915">#39915</a> and
419. <a href="https://github.com/rust-lang/rust/issues/71515">#71515</a>, and rustc already offers nightly flags to
420. use <code>rust-lld</code>.</p>
421. <p>By now, we believe we've done all the internal testing that we could, on CI, crater, and our
422. benchmarking infrastructure. We would now like to expand testing and gather real-world feedback and
423. use-cases. Therefore, we will enable <code>rust-lld</code> to be the linker used by default on
424. <code>x86_64-unknown-linux-gnu</code> for nightly builds.</p>
425. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html#benefits" id="benefits"></a>Benefits</h4>
426. <p>While this also enables the compiler to use more linker features in the future, the most immediate
427. benefit is much improved linking times.</p>
428. <p>Here are more details from the ripgrep example mentioned above: linking is reduced 7x, resulting in
429. a 40% reduction in end-to-end compilation times.</p>
430. <p><img alt="Before/after comparison of a ripgrep debug build" src="https://blog.rust-lang.org/../images/2024-05-17-enabling-rust-lld-on-linux/ripgrep-comparison.png" /></p>
431. <p>Most binaries should see some improvements here, but it's especially significant with e.g. bigger
432. binaries, or when involving debuginfo. These usually see bottlenecks in the linker.</p>
433. <p>Here's <a href="https://perf.rust-lang.org/compare.html?start=b3e117044c7f707293edc040edb93e7ec5f7040a&end=baed03c51a68376c1789cc373581eea0daf89967&stat=instructions%3Au&tab=compile">a
434. link</a>
435. to the complete results from our benchmarks.</p>
436. <p>If testing goes well, we can then stabilize using this faster linker by default for
437. <code>x86_64-unknown-linux-gnu</code> users, before maybe looking at other targets.</p>
438. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html#possible-drawbacks" id="possible-drawbacks"></a>Possible drawbacks</h4>
439. <p>From our prior testing, we don't really expect issues to happen in practice. It is a drop-in
440. replacement for the vast majority of cases, but <code>lld</code> is not <em>bug-for-bug</em> compatible with GNU ld.</p>
441. <p>In any case, using <code>rust-lld</code> can be disabled if any problem occurs: use the <code>-Z linker-features=-lld</code> flag to revert to using the system's default linker.</p>
442. <p>Some crates somehow relying on these differences could need additional link args. For example, we
443. saw <20 crates in the crater run failing to link because of a different default about <a href="https://lld.llvm.org/ELF/start-stop-gc">encapsulation
444. symbols</a>: these could require
445. <code>-Clink-arg=-Wl,-z,nostart-stop-gc</code> to match the legacy GNU ld behavior.</p>
446. <p>Some of the big gains in performance come from parallelism, which could be undesirable in
447. resource-constrained environments.</p>
448. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html#summary" id="summary"></a>Summary</h4>
449. <p>rustc will use <code>rust-lld</code> on <code>x86_64-unknown-linux-gnu</code> nightlies, for much improved linking times,
450. starting in tomorrow's rustup nightly (<code>nightly-2024-05-18</code>).
451. Let us know if you encounter problems, by <a href="https://github.com/rust-lang/rust/issues/new/choose">opening an
452. issue</a> on GitHub.</p>
453. <p>If that happens, you can revert to the default linker with the <code>-Z linker-features=-lld</code> flag.
454. Either by adding it to the usual <code>RUSTFLAGS</code> environment variable, or to a project's
455. <a href="https://doc.rust-lang.org/cargo/reference/config.html"><code>.cargo/config.toml</code></a> configuration file,
456. like so:</p>
457. <pre><code class="language-toml">[target.x86_64-unknown-linux-gnu]
458. rustflags = ["-Zlinker-features=-lld"]
459. &lt;/code&gt;&lt;/pre&gt;</description>
460. <pubDate>Fri, 17 May 2024 00:00:00 +0000</pubDate>
461. <dc:creator>Rémy Rakic</dc:creator>
462. </item>
463. <item>
464. <title>Support.Mozilla.Org: Kitsune Release Notes – May 15, 2024</title>
465. <guid isPermaLink="false">https://blog.mozilla.org/sumo/?p=4123</guid>
466. <link>https://blog.mozilla.org/sumo/2024/05/16/kitsune-release-notes-may-15-2024/</link>
467. <description>&lt;p&gt;&lt;i&gt;See full platform release notes on &lt;/i&gt;&lt;a href=&quot;https://github.com/mozilla/kitsune/releases&quot;&gt;&lt;i&gt;GitHub&lt;/i&gt;&lt;/a&gt;&lt;i&gt;. &lt;/i&gt;&lt;/p&gt;
468. <h3><b>New</b><b><br />
469. </b><i></i></h3>
470. <p><i>Description of new features, how it benefits the user, and any relevant details.</i></p>
471. <ul>
472. <li><b>Group messaging</b>: <i>Staff</i> group members can send messages to groups as well as individual users.</li>
473. <li><b><i>Staff</i></b><b> group permissions</b>: We are now using a user’s membership in the <i>Staff </i>group rather than the user’s <i>is_staff </i>attribute to determine elevated privileges like being able to send messages to groups or seeing restricted KB articles</li>
474. <li><b>In-product link on article page</b>: You’ll now see an indicator on the KB article page for articles that are the target of in-product links. This is visible to users in the <i>Staff</i> group.</li>
475. </ul>
476. <p><b><a href="http://blog.mozilla.org/sumo/files/2024/05/Screenshot-2024-05-16-at-15-43-56-Tab-context-menu-in-Firefox-close-multiple-tabs-Firefox-Help.png"><img alt="Screenshot of the in-product indicator in a KB article" class="size-full wp-image-4124 aligncenter" height="135" src="http://blog.mozilla.org/sumo/files/2024/05/Screenshot-2024-05-16-at-15-43-56-Tab-context-menu-in-Firefox-close-multiple-tabs-Firefox-Help.png" width="215" /></a></b></p>
477. <h3><b>Changed</b><b></b><br />
478. <i></i></h3>
479. <p><i>Explanation of the enhancements or changes to existing features, including performance improvements, user interface changes, etc.</i></p>
480. <ul>
481. <li><b>Conversion from GA3 to GA4 data API for gathering Google Analytics data</b>: We recently migrated SUMO’s Google Analytics (GA) from GA3 to GA4. This has temporarily impacted our access to historical data on the <a href="https://support.mozilla.org/en-US/contributors">SUMO KB Dashboard</a>. Data will now be pulled from GA4, which only has data since April 10, 2024. The number of “Visits” for the “Last 90 days” and “Last year” will only reflect the data gathered since this date. Stay tuned for additional dashboard updates, including the inclusion of GA3 data.</li>
482. </ul>
483. <p><a href="http://blog.mozilla.org/sumo/files/2024/05/Screenshot-2024-05-16-at-15-45-39-Knowledge-Base-Dashboard-Mozilla-Support.png"><img alt="Screenshot of the Knowledge Base Dashboard in SUMO" class="alignnone size-full wp-image-4125" height="660" src="http://blog.mozilla.org/sumo/files/2024/05/Screenshot-2024-05-16-at-15-45-39-Knowledge-Base-Dashboard-Mozilla-Support.png" width="1090" /></a></p>
484. <ul>
485. <li><b>Improved tabbed portion of the localization dashboard</b>: Example <a href="https://support.allizom.org/de/localization">https://support.allizom.org/de/localization</a></li>
486. <li><b>Improved inbox and outbox message pages</b></li>
487. </ul>
488. <p><a href="http://blog.mozilla.org/sumo/files/2024/05/Screenshot-2024-05-16-at-15-48-40-Inbox-Mozilla-Support.png"><img alt="Screenshot of how the new SUMO inbox looks like" class="alignnone size-full wp-image-4126" height="290" src="http://blog.mozilla.org/sumo/files/2024/05/Screenshot-2024-05-16-at-15-48-40-Inbox-Mozilla-Support.png" width="747" /></a></p>
489. <ul>
490. <li><b>Removed New Contributors link from the Contributor Tools</b>: Discussions section of the top main menu (<a href="https://github.com/mozilla/sumo/issues/1746">#1746</a>)</li>
491. </ul>
492. <h3><b>Fixed </b><b><br />
493. </b><i></i></h3>
494. <p><i>Brief description of the bug and how it was fixed, possibly including affected components.</i></p>
495. <p>–</p>
496. &lt;p&gt; &lt;/p&gt;</description>
497. <pubDate>Thu, 16 May 2024 09:01:56 +0000</pubDate>
498. <dc:creator>Rizki Kelimutu</dc:creator>
499. </item>
500. <item>
501. <title>Spidermonkey Development Blog: SpiderMonkey Newsletter (Firefox 126-127)</title>
502. <guid isPermaLink="false">https://spidermonkey.dev/blog/2024/05/15/newsletter-firefox-126-127</guid>
503. <link>https://spidermonkey.dev/blog/2024/05/15/newsletter-firefox-126-127.html</link>
504. <description>&lt;p&gt;Hello and welcome to our newest newsletter. As the northern hemisphere warms and the southern hemisphere cools, we write to talk about what’s happened in the world of SpiderMonkey in the Firefox 126-127 timeline.&lt;/p&gt;
505.  
506. <h3 id="-performance">🚀 Performance</h3>
507.  
508. <p>Though Speedometer 3 has shipped, we cannot allow ourselves get lax with our performance. It’s important that SpiderMonkey be fast so Firefox can be fast!</p>
509.  
510. <ul>
511.  <li>Arai added <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1862273">special bytecode for checking <code class="language-plaintext highlighter-rouge">typeof val == "type"</code></a></li>
512.  <li>Justin analyzed our caches for atoms, which turn out to be a reasonably hot path, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1879143">and discovered that he could improve them</a>. Our <a href="https://treeherder.mozilla.org/perfherder/alerts?id=41941">perf-alerts noticed some interesting speedups up to 8% on some tests</a>!</li>
513.  <li>Jan has been playing with <a href="https://en.wikipedia.org/wiki/Trampoline_(computing)">trampolines</a>. Changing <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884360">how we handle the comparator function to Array.prototype.sort</a> improved performance, particularly at lower tiers, up to 4x!</li>
514.  <li>Alex <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1881995">added a new string type</a> which holds a pointer to a corresponding atom, allowing cheap atom lookup.</li>
515.  <li>André has <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889091">worked on</a> <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890513">improving calls</a> to native functions with variadic parameters.</li>
516. </ul>
517.  
518. <h3 id="-contributor-spotlight">🔦 Contributor Spotlight</h3>
519.  
520. <p>This newsletter, we’d like to Spotlight Jonatan Klemets. In his own words,</p>
521.  
522. <blockquote>
523.  <p>A full-stack web developer by day and a low-level enthusiast by night who likes tinkering with compilers, emulators, and other low-level projects</p>
524. </blockquote>
525.  
526. <p>Jonatan has been helping us for a few years now and has been the main force of late driving forwards our work on the <a href="https://github.com/tc39/proposal-import-attributes">Import Attributes proposal</a>. Pushing this proposal forward has required jumping into many different parts of Firefox, and Jonatan has done really well, and we are very thankful for the effort he has put into working on the project.</p>
527.  
528. <h3 id="-wasm">⚡ Wasm</h3>
529.  
530. <ul>
531.  <li>Yury has been working on the <a href="https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md">JavaScript-Promise Integration Proposal</a>, which when it’s all finished, will allow easier interop between Wasm and JS Promises.</li>
532.  <li>Ben has done some work on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1863609">optimizing out superfluous casts</a></li>
533.  <li>Julien has shipped the<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1837683"> Wasm branch hinting proposal</a>.</li>
534. </ul>
535.  
536. <h3 id="️-web-features-work">🕸️ Web Features Work</h3>
537.  
538. <ul>
539.  <li>Dan <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1805038">has shipped</a> the <a href="https://github.com/tc39/proposal-set-methods">new Set methods proposal</a></li>
540. </ul>
541.  
542. <h3 id="️--other-work">👷🏽‍♀️  Other Work</h3>
543.  
544. <ul>
545.  <li><a href="https://www.mozilla.org/en-US/security/advisories/mfsa2024-15/">We were Pwned</a> by Manfred Paul at Pwn2Own 2024, but <a href="https://blog.mozilla.org/security/2024/04/04/rapidly-leveling-up-firefox-security/">fixed builds shipped in 21 hours</a>, <a href="https://twitter.com/thezdi/status/1771296997787443370">first of the vendors at the competition</a>.</li>
546. &lt;/ul&gt;</description>
547. <pubDate>Wed, 15 May 2024 17:00:00 +0000</pubDate>
548. </item>
549. <item>
550. <title>The Mozilla Blog: Why I’m Joining Mozilla as Executive Director</title>
551. <guid isPermaLink="false">https://blog.mozilla.org/?p=74773</guid>
552. <link>https://blog.mozilla.org/en/mozilla/why-im-joining-mozilla-as-executive-director/</link>
553. <description>&lt;p&gt;&lt;/p&gt;
554.  
555.  
556.  
557. <p><strong>Delight</strong> — absolute <strong><em>delight</em></strong> — is what I felt when my parents brought home a <a href="https://en.wikipedia.org/wiki/Compaq_Deskpro_386">Compaq Deskpro 386</a> for us to play with. It was love at first sight, thanks to games like Reader Rabbit, but I fell especially hard once we had a machine connected to the Internet. The unparalleled joy that comes from making things with and for other people was intoxicating. I can’t tell you how many hours were spent building Geocities websites for friends, poring over message boards, writing X-Files fan fiction, exchanging inside jokes and song lyrics on AIM and ICQ chats with friends and far-flung cousins across the world. </p>
558.  
559.  
560.  
561. <p>Actually, I could tell you. In detail. But it would be embarrassing. </p>
562.  
563.  
564.  
565. <p>Years later I would learn that the ability to share, connect, and create is rooted in how the Internet works differently than the media preceding it. The Internet speaks standards and protocols. It links instead of copying. Its nature is open. You don’t need permission to make something on the Internet. That freedom holds enormous potential: At its best, it helps us explore history we didn’t know, build movements to better the future, or make a meme to brighten someone’s day. At its best, the Internet lets us <em>see</em> each other. </p>
566.  
567.  
568.  
569. <p>That magic — this power — is revolutionary. Protecting it, celebrating it, and expanding it is why I’m so excited to <a href="https://blog.mozilla.org/en/mozilla/mozilla-foundation-welcomes-nabiha-syed-as-executive-director/">join the Mozilla Foundation as its executive director</a>. </p>
570.  
571.  
572.  
573. <p>I started my career as a media lawyer to protect those who made things that helped us see one another, and the truth about our shared world. Almost fifteen years ago, I co-founded and built a <a href="https://law.yale.edu/studying-law-yale/clinical-and-experiential-learning/our-clinics/media-freedom-and-information-access-clinic">media law clinic</a> to train others to do the same. After a stint at a law firm, I joined BuzzFeed as its <a href="https://www.rcfp.org/5-things-you-should-know-about-rising-star-award-winner-nabiha-syed/">first newsroom lawyer</a>, which felt sort of like being a lawyer for the silliest and most serious parts of the internet all at the same time. In other words, I was a lawyer for the Internet at its best.</p>
574.  
575.  
576.  
577. <p>I am not naive about the Internet at its worst. From the <a href="https://www.degruyter.com/document/doi/10.7312/bell17612-012/html?lang=en">Edward Snowden disclosures</a> to a quick trip to Guantanamo Bay, Cuba, much of my career has confronted issues of surveillance — including of my own religious community. I watched as consumers became more concerned about surveillance and other harms online, and so we built an accountability journalism outlet, The Markup, to serve those needs. The Markup’s mission is to help people challenge technology to serve the public good, which intentionally centers human agency. So we didn’t just write articles: Our team imagined and made things people used to make informed choices. Blacklight, for example, empowers people to use the Web how they want, by helping them see the otherwise invisible set of tracking tools, watching them as they browse. </p>
578.  
579.  
580.  
581. <p>The through-line of my career has been grappling with how technology can uplift or stifle human agency. I choose the former. I bet you do too. </p>
582.  
583.  
584.  
585. <p>This, of course, brings me back to the Mozilla Foundation. In our particular moment – as we’re <a href="https://www.theverge.com/ai-artificial-intelligence">deploying large-scale AI systems</a> for the first time, as we’re <a href="https://www.newyorker.com/culture/infinite-scroll/the-revenge-of-the-home-page">waking up home pages from their long rests</a>, and trying to <a href="https://www.noemamag.com/we-need-to-rewild-the-internet/">“rewild” the Internet beyond walled gardens</a> – I can think of no other place that has the ability, to help people shape technology to achieve their goals on their own terms. And there is no more important time. </p>
586.  
587.  
588.  
589. <p>After all, <strong>the world we live in now was once someone’s imagination</strong>. Someone dreamt, and then many someones built, the Internet, and democracy, and other wild-eyed ideas too. We can imagine a future that centers human agency, and then we can build it, bit-by-byte. In this wildly unpredictable moment in 2024, it certainly feels like it’s up for grabs as to whether technology will be used to liberate us or shackle us. But that also means it’s up to us – if we act now. </p>
590.  
591.  
592.  
593. <p>With your help, together <a href="https://www.mozilla.org/en-US/about/manifesto/">we can imagine and create the Internet we want.</a> Not what Zuckerberg, Pichai, Musk, or any other tech titan wants – we can imagine and make what <em>you</em> want, on your own terms. Making things on your own terms is a team sport, and that’s why I’m especially thrilled to be joining <a href="https://blog.mozilla.org/en/mozilla/a-new-chapter-for-mozilla-laura-chambers-expanded-role/">Laura Chambers</a> (CEO, Mozilla Corporation), <a href="https://blog.mozilla.org/en/mozilla/introducing-mozilla-ai-investing-in-trustworthy-ai/">Moez Draief</a> (Managing Director, Mozilla.ai), <a href="https://blog.mozilla.org/en/mozilla/mozilla-launches-first-of-its-kind-venture-fund-to-fuel-responsible-tech-companies-products/">Mohamed Nanabhay </a>(Managing Partner, Mozilla Ventures), <a href="https://www.mozilla.org/en-US/about/leadership/#mitchell-baker">Mitchell Baker</a> (Executive Chair of the Board), and Mark Surman (President, Mozilla) as part of Mozilla’s senior leadership team.</p>
594.  
595.  
596.  
597. <p>Technology’s come a long way since that Compaq, and it’s moving faster than ever before. My young boys won’t experience the Internet through Geocities or X-Files fan fiction or dial-up modems (probably?).* But it’s my mission to make sure they – and all of us – do have the sense of delight I felt at the dawn of our connected age: The unparalleled joy that comes from making things with and for other people.</p>
598.  
599.  
600.  
601. <p>Always yours,</p>
602.  
603.  
604.  
605. <p>Nabiha</p>
606.  
607.  
608.  
609. <p>*They will, however, have Pikachu. There’s always Pikachu. <a href="https://images.app.goo.gl/MgVJXismZaT7RtC86">https://images.app.goo.gl/MgVJXismZaT7RtC86</a> </p>
610.  
611.  
612.  
613. <p>**There’s an important corollary to all this. I (and we at Mozilla) don’t have all the good ideas. We never will. So, consider my inbox to be yours. Got an idea? Let’s talk: hi-nabiha@mozillafoundation.org</p>
614. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/why-im-joining-mozilla-as-executive-director/&quot;&gt;Why I’m Joining Mozilla as Executive Director &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>
615. <pubDate>Wed, 15 May 2024 16:44:40 +0000</pubDate>
616. <dc:creator>Nabiha Syed</dc:creator>
617. </item>
618. <item>
619. <title>The Mozilla Blog: Mozilla Foundation Welcomes Nabiha Syed as Executive Director</title>
620. <guid isPermaLink="false">https://blog.mozilla.org/?p=74784</guid>
621. <link>https://blog.mozilla.org/en/mozilla/mozilla-foundation-welcomes-nabiha-syed-as-executive-director/</link>
622. <description>&lt;p&gt;&lt;/p&gt;
623.  
624.  
625.  
626. <p class="has-medium-font-size"><em><strong><em>Public interest tech advocate will harness collective power to deepen Mozilla’s focus on trustworthy AI</em></strong></em></p>
627.  
628.  
629.  
630. <p>Today, Mozilla Foundation is proud to announce Nabiha Syed — media executive, lawyer, and champion of public interest technology — as its Executive Director. Syed joins Mozilla from The Markup, where she was chief executive officer. </p>
631.  
632.  
633.  
634. <p>As technology companies, civil society, and governments race to keep up with the rapid pace of AI innovation, Syed will lead <a href="https://foundation.mozilla.org/en/blog/mozilla-seeks-new-leader-for-its-movement-building-arm/">Mozilla’s advocacy and philanthropy programs</a> to serve the public interest. Mozilla, with Syed’s leadership, will carry forward the Foundation’s <a href="https://blog.mozilla.org/en/mozilla/a-third-way-on-ai/">nuanced, practical perspective</a> to help steer society away from the real risks and toward the benefits of AI. </p>
635.  
636.  
637.  
638. <p>“Nabiha has an exceptional understanding of how technology, humanity and broader society intersect — and how to engage with the complicated challenges and opportunities at that intersection,” said Mark Surman, Mozilla Foundation President. “Nabiha will make Mozilla a stronger, bigger, and more impactful organization, at a time when the internet needs it most.”</p>
639.  
640.  
641.  
642. <p>Syed is known for her mission-driven leadership, focused on increasing transparency into the most powerful institutions in society. She comes to Mozilla after leading The Markup, an award-winning publication that challenges technology to serve the public good, from its launch through its successful acquisition in 2024. The Markup drove Congressional debates, inspired watershed litigation, and won multiple prestigious awards including Fast Company’s “Most Innovative,” along with the Edward R. Murrow, National Press Club, and Scripps Howard prizes. </p>
643.  
644.  
645.  
646. <p>“The through-line of my career has been grappling with how technology can uplift or stifle human agency,” said Nabiha Syed, incoming Mozilla Foundation Executive Director. “After all, the technology we have now was once just someone’s imagination. We can dream, build, and demand technology that serves all of us, not just the powerful few. Mozilla is the perfect place to make that happen.” </p>
647.  
648.  
649.  
650. <p>As Executive Director, Syed will oversee a staff of more than 100 full-time employees and an annual budget of $30 million. She joins Mozilla at a time of growth <a href="http://foundation.mozilla.org/blog/growing-our-movement-and-growing-mozilla-to-shape-the-ai-era">and ambitious leadership</a>: Mozilla is rapidly expanding its investment in building a movement for trustworthy AI through grantmaking, campaigning, and research. The Mozilla portfolio has also grown to include a <a href="https://mozilla.vc/">venture capital arm</a> and a<a href="https://blog.mozilla.org/en/mozilla/introducing-mozilla-ai-investing-in-trustworthy-ai/"> commercial AI R+D lab</a>. </p>
651.  
652.  
653.  
654. <p>Prior to The Markup, Syed was a highly acclaimed media lawyer. Syed’s legal career spanned private practice, the New York Times First Amendment Fellowship, and leading BuzzFeed’s libel and newsgathering matters, including the successful defense of the Steele Dossier litigations. She sits on the board of the <a href="https://www.theguardian.com/the-scott-trust">Scott Trust</a>, the $1B+ British company that owns The Guardian newspaper, the New York Civil Liberties Union, the Reporters Committee for the Freedom of the Press, Upturn, the New Press, and serves as an advisor to ex/ante, the first venture fund dedicated to agentic tech.  </p>
655.  
656.  
657.  
658. <p>Syed is widely sought after for her views on technology and media law, and has briefed two sitting presidents on free speech matters as well as diverse audiences including the World Economic Forum, annual investor meetings, Stanford, Wharton, and Columbia, where she is a lecturer.</p>
659.  
660.  
661.  
662. <p>She has been recognized with numerous awards, including as a 40 Under 40 Rising Star by the New York Law Journal, Crain’s New York Business 40 under 40 award, a Rising Star award from the Reporter’s Committee for Freedom of the Press. Syed was selected to be on the National Commission for US-China Relations, and was recognized by Forbes as one of the best emerging free speech lawyers. </p>
663.  
664.  
665.  
666. <p>Syed holds a J.D. from Yale Law School, an M.St from the University of Oxford where she was a Marshall Scholar, and a B.A from Johns Hopkins University. She lives in Brooklyn with her husband and her two young boys.</p>
667.  
668.  
669.  
670. <p><strong>Also read:</strong></p>
671.  
672.  
673.  
674. <p><a href="https://blog.mozilla.org/en/mozilla/why-im-joining-mozilla-as-executive-director/">Why I’m Joining Mozilla as Executive Director</a>, by Nabiha Syed </p>
675.  
676.  
677.  
678. <p><a href="https://blog.mozilla.org/en/mozilla/growing-our-movement-and-growing-mozilla-to-shape-the-ai-era/">Growing Our Movement — and Growing Mozilla — to Shape the AI Era</a>, by Mark Surman</p>
679. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/mozilla-foundation-welcomes-nabiha-syed-as-executive-director/&quot;&gt;Mozilla Foundation Welcomes Nabiha Syed as Executive Director&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>
680. <pubDate>Wed, 15 May 2024 16:44:31 +0000</pubDate>
681. <dc:creator>Mozilla</dc:creator>
682. </item>
683. <item>
684. <title>The Mozilla Blog: Growing Our Movement — and Growing Mozilla — to Shape the AI Era</title>
685. <guid isPermaLink="false">https://blog.mozilla.org/?p=74795</guid>
686. <link>https://blog.mozilla.org/en/mozilla/growing-our-movement-and-growing-mozilla-to-shape-the-ai-era/</link>
687. <description>&lt;p&gt;&lt;/p&gt;
688.  
689.  
690.  
691. <p>Last August, we announced that Mozilla was seeking a <a href="https://blog.mozilla.org/en/mozilla/mozilla-seeks-new-leader-for-its-movement-building-arm/">new executive director to lead its movement building arm</a>. I’m excited to <a href="https://blog.mozilla.org/en/mozilla/mozilla-foundation-welcomes-nabiha-syed-as-executive-director/">announce</a> that Nabiha Syed — media executive, lawyer, and champion of public interest technology — is joining us to take on this role. </p>
692.  
693.  
694.  
695. <p>I’ve gotten to know — and admire — Nabiha over the last few years in her role as the chief executive officer of <a href="https://themarkup.org/">The Markup</a>. I’ve been impressed by her thinking on how technology, humanity and society intersect — and the way she has used journalism and research to uncover the challenges and opportunities we face in the AI era. </p>
696.  
697.  
698.  
699. <p>As we talked about the executive director role, I also found a thought partner who sees the potential to combine the ‘market’ and ‘movement’ sides of Mozilla’s personality to shape how the tech universe works. I am convinced that Nabiha will make us a stronger, bigger and more impactful organization, at a time when the internet needs it most.</p>
700.  
701.  
702.  
703. <p>Nabiha will take over leadership of Mozilla Foundation’s $30M/year portfolio of movement building programs starting on July 1. Her first task will be to supercharge the Foundation’s <a href="https://foundation.mozilla.org/en/research/library/accelerating-progress-toward-trustworthy-ai/whitepaper/">trustworthy AI</a> efforts, with an initial focus on:</p>
704.  
705.  
706.  
707. <ul>
708. <li>Partnering with other public interest organizations to shift the narrative on AI.</li>
709.  
710.  
711.  
712. <li>Creating — and funding — open source and community-driven data sets, tools, and research.</li>
713.  
714.  
715.  
716. <li>Growing a global community of talent committed to building responsible and trustworthy tech. </li>
717. </ul>
718.  
719.  
720.  
721. <p>She will take on the responsibility for all of Mozilla’s philanthropic and advocacy programs, and will lead fundraising for our charitable initiatives.</p>
722.  
723.  
724.  
725. <p>It’s important to note: Nabiha’s appointment is part of a broader effort to build new <a href="https://stateof.mozilla.org/">leadership that can take Mozilla into its next chapter</a>. She joins <a href="https://blog.mozilla.org/en/mozilla/a-new-chapter-for-mozilla-laura-chambers-expanded-role/">Laura Chambers</a> (CEO, Mozilla Corporation), <a href="https://blog.mozilla.org/en/mozilla/introducing-mozilla-ai-investing-in-trustworthy-ai/">Moez Draief</a> (Managing Director, Mozilla.ai), <a href="https://blog.mozilla.org/en/mozilla/mozilla-launches-first-of-its-kind-venture-fund-to-fuel-responsible-tech-companies-products/">Mohamed Nanabhay </a>(Managing Partner, Mozilla Ventures) as well as Mitchell Baker (Executive Chair of Mozilla Corporation) and I, as part of the senior leadership team charged with advancing the <a href="https://www.mozilla.org/en-CA/about/manifesto/">Mozilla Manifesto</a> in the AI era. </p>
726.  
727.  
728.  
729. <p>As Nabiha joins, I will be moving full-time to the role of Mozilla Foundation President, focusing even more deeply on the growth, cohesion and sustainability of the overall Mozilla portfolio of organizations. This includes further work with Mitchell and our Boards to develop a clear roadmap for Mozilla’s next chapter — with a particular focus on the role Mozilla can play in AI. It also includes support for senior leaders at <a href="https://www.mozilla.ai/">Mozilla.ai</a> and <a href="https://mozilla.vc/">Mozilla Ventures</a> — our two newest entities — as well as Mozilla’s new Global Head of Public Policy, <a href="https://www.mozilla.org/en-US/about/leadership/#linda-griffin">Linda Griffin</a>. </p>
730.  
731.  
732.  
733. <p>This is an exciting and pivotal moment — for Mozilla, the internet and the world. More and more people are realizing the need for tech products that are designed to be trustworthy, empowering and delightful — and for a movement that mobilizes people to reclaim the internet and ownership over their digital lives. We have a chance to build these things right now, and to reshape the relationship between technology and humanity for the better. I’m so glad Nabiha has joined us to make this happen. Welcome!</p>
734. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/growing-our-movement-and-growing-mozilla-to-shape-the-ai-era/&quot;&gt;Growing Our Movement — and Growing Mozilla — to Shape the AI Era&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>
735. <pubDate>Wed, 15 May 2024 16:44:22 +0000</pubDate>
736. <dc:creator>Mark Surman</dc:creator>
737. </item>
738. <item>
739. <title>This Week In Rust: This Week in Rust 547</title>
740. <guid isPermaLink="false">tag:this-week-in-rust.org,2024-05-15:/blog/2024/05/15/this-week-in-rust-547/</guid>
741. <link>https://this-week-in-rust.org/blog/2024/05/15/this-week-in-rust-547/</link>
742. <description>&lt;p&gt;Hello and welcome to another issue of &lt;em&gt;This Week in Rust&lt;/em&gt;!
743. <a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
744. This is a weekly summary of its progress and community.
745. Want something mentioned? Tag us at <a href="https://twitter.com/ThisWeekInRust">@ThisWeekInRust</a> on Twitter or <a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social, or <a href="https://github.com/rust-lang/this-week-in-rust">send us a pull request</a>.
746. Want to get involved? <a href="https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md">We love contributions</a>.</p>
747. <p><em>This Week in Rust</em> is openly developed <a href="https://github.com/rust-lang/this-week-in-rust">on GitHub</a> and archives can be viewed at <a href="https://this-week-in-rust.org/">this-week-in-rust.org</a>.
748. If you find any errors in this week's issue, <a href="https://github.com/rust-lang/this-week-in-rust/pulls">please submit a PR</a>.</p>
749. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#updates-from-rust-community">Updates from Rust Community</a></h4>
750.  
751.  
752. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#official">Official</a></h5>
753. <ul>
754. <li><a href="https://blog.rust-lang.org/inside-rust/2024/05/14/leadership-council-update.html">May 2024 Leadership Council Update</a></li>
755. </ul>
756. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#newsletters">Newsletters</a></h5>
757. <ul>
758. <li><a href="https://thisweekinbevy.com/issue/2024-05-13-clearcoat-new-examples-and-game-updates">ClearCoat, new examples, and game updates</a></li>
759. </ul>
760. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#projecttooling-updates">Project/Tooling Updates</a></h5>
761. <ul>
762. <li><a href="https://lwn.net/Articles/970216/">Rust for embedded Linux kernels</a></li>
763. <li><a href="https://github.com/tesselode/kira/releases/tag/v0.9.0">kira - release v0.9.0</a></li>
764. <li><a href="https://ecton.dev/cushy-v0-3/">Cushy v0.3: New widgets, offscreen capture, Plotters and Tokio integrations, and more</a></li>
765. <li><a href="https://github.com/ambaxter/bbolt-rs/blob/v1.3.8/docs/announcement.md">bbolt-rs v1.3.8</a></li>
766. <li><a href="https://www.reddit.com/r/rust/comments/1chrshl/maelstrom_a_hermetic_clustered_test_runner_for/">Maelstrom: A Hermetic, Clustered Test Runner for Rust (and It’s Fast)</a></li>
767. <li><a href="https://github.com/r3bl-org/r3bl-open-core/blob/main/CHANGELOG.md#v0012-2024-05-12">r3bl_cmdr version v0.0.12 released</a></li>
768. <li><a href="https://iroh.computer/blog/iroh-0-16-a-better-client">Iroh 0.16 - A Better <code>Client</code></a></li>
769. </ul>
770. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#observationsthoughts">Observations/Thoughts</a></h5>
771. <ul>
772. <li><a href="https://corrode.dev/blog/long-term-rust-maintenance/">Long-term Rust Project Maintenance</a></li>
773. <li><a href="https://nora.codes/post/methods-should-be-object-safe/">Methods Should Be Object Safe</a></li>
774. <li><a href="https://without.boats/blog/references-are-like-jumps/">References are like jumps</a></li>
775. <li><a href="https://codspeed.io/blog/rust-1-78-performance-impact-of-the-128-bit-memory-alignment-fix">Rust 1.78: Performance Impact of the 128-bit Memory Alignment Fix</a></li>
776. <li><a href="https://voelklmichael.github.io/Blog/2024/05/12/egui-wasm-threads.html">HowTo: Egui with webworkers</a></li>
777. <li><a href="https://neosmart.net/blog/using-build-rs-to-integrate-rust-applications-with-system-libraries-like-a-pro/">Using build.rs to integrate rust applications with system libraries like a pro</a></li>
778. <li><a href="https://dgroshev.com/blog/rust-actors-mutex/">Rust actors + ArcMutex: handle with care</a></li>
779. <li><a href="https://www.ncameron.org/blog/rust-through-the-ages/">Rust through the ages</a></li>
780. <li><a href="https://blog.dureuill.net/articles/dont-mix-rayon-tokio/">Mixing rayon and tokio for fun and (hair) loss</a></li>
781. <li><a href="https://sneakycrow.dev/blog/2024-05-12-running-async-tasks-in-tauri-v2">Long-running backend async tasks in tauri v2</a></li>
782. <li><a href="https://dygalo.dev/blog/blazingly-fast-linked-lists/">Blazingly Fast Linked Lists</a></li>
783. <li><a href="https://lwn.net/Articles/970186/">Existential types in Rust</a></li>
784. <li><a href="https://greptime.com/blogs/2024-05-07-error-rust">Error Handling for Large Rust Projects - A Deep Dive into GreptimeDB's Practices</a></li>
785. </ul>
786. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust-walkthroughs">Rust Walkthroughs</a></h5>
787. <ul>
788. <li><a href="https://marcobacis.com/blog/load-balancer-rust-1/">Let's build a Load Balancer in Rust - Part 1</a></li>
789. <li>[video] <a href="https://www.youtube.com/watch?v=Wf8JrLgBuKI">Build with Naz : tokio tracing & OTel and how to use it in Rust</a></li>
790. </ul>
791. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#miscellaneous">Miscellaneous</a></h5>
792. <ul>
793. <li><a href="https://filtra.io/rust-apr-24">April 2024 Rust Jobs Report</a></li>
794. <li><a href="https://code.visualstudio.com/blogs/2024/05/08/wasm">VS Code Extensions and WebAssembly</a></li>
795. </ul>
796. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#crate-of-the-week">Crate of the Week</a></h4>
797. <p>This week's crate is <a href="https://crates.io/crates/stated-scope-guard">stated-scope-guard</a>, a library supporting a more flexible RAII pattern for stated resouce management.</p>
798. <p>Thanks to <a href="https://users.rust-lang.org/t/crate-of-the-week/2704/1309">Evian Zhang</a> for the self-suggestion!</p>
799. <p><a href="https://users.rust-lang.org/t/crate-of-the-week/2704">Please submit your suggestions and votes for next week</a>!</p>
800. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#call-for-testing">Call for Testing</a></h4>
801. <p>An important step for RFC implementation is for people to experiment with the
802. implementation and give feedback, especially before stabilization.  The following
803. RFCs would benefit from user testing before moving forward:</p>
804. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rfcs"></a><a href="https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing">RFCs</a></h5>
805. <ul>
806. <li><em>No calls for testing were issued this week.</em></li>
807. </ul>
808. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust"></a><a href="https://github.com/rust-lang/rust/labels/call-for-testing">Rust</a></h5>
809. <ul>
810. <li><em>No calls for testing were issued this week.</em></li>
811. </ul>
812. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rustup"></a><a href="https://github.com/rust-lang/rustup/labels/call-for-testing">Rustup</a></h5>
813. <ul>
814. <li><em>No calls for testing were issued this week.</em></li>
815. </ul>
816. <p>If you are a feature implementer and would like your RFC to appear on the above list, add the new <code>call-for-testing</code>
817. label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
818. need testing.</p>
819. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers">Call for Participation; projects and speakers</a></h4>
820. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#cfp-projects">CFP - Projects</a></h5>
821. <p>Always wanted to contribute to open-source projects but did not know where to start?
822. Every week we highlight some tasks from the Rust community for you to pick and get started!</p>
823. <p>Some of these tasks may also have mentors available, visit the task page for more information.</p>
824. <ul>
825. <li><a href="https://github.com/GreptimeTeam/greptimedb/issues/3265">greptimedb - Add more tests for Copy From</a></li>
826. <li><a href="https://github.com/GreptimeTeam/greptimedb/issues/3004">greptimedb - Checksum for manifests</a></li>
827. <li><a href="https://github.com/GreptimeTeam/greptimedb/issues/3686">greptimedb - Adding JSON Type to GreptimeDB</a>*</li>
828. <li><a href="https://github.com/GreptimeTeam/greptimedb/issues/3685">greptimedb - Resource Constrained Framework for Embedded Environments</a>*</li>
829. <li><a href="https://github.com/GreptimeTeam/greptime-bench">GreptimeTeam - Design and implement an evaluation program similar to TPC-DS/TPC-H for time-series scenarios</a>*</li>
830. </ul>
831. <blockquote>
832. <p>"*" = Issues open for student applications via OSPP. Selected students will be assigned a mentor(s), and may receive bonuses. Please register through the <a href="https://summer-ospp.ac.cn/org/orgdetail/32cda81d-a705-4ab7-8b13-7c27a86ac19a?lang=en">OSPP link</a>.</p>
833. </blockquote>
834. <p>If you are a Rust project owner and are looking for contributors, please submit tasks <a href="https://users.rust-lang.org/t/twir-call-for-participation/4821">here</a>.</p>
835. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#cfp-speakers">CFP - Speakers</a></h5>
836. <p>Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.</p>
837. <ul>
838. <li><a href="https://sessionize.com/rust-argentina-june/">Rust Argentina June 2024</a> | Closes 2024-05-31 | Buenos Aires, AR | Event date: 2024-06-04</li>
839. <li><a href="https://www.papercall.io/eurorust-2024">EuroRust 2024</a> | Closes 2024-06-03 | Vienna, Austria & online | Event date: 2024-10-10</li>
840. <li><a href="https://scientificcomputing.rs/">Scientific Computing in Rust 2024</a> | Closes 2024-06-14 | online | Event date: 2024-07-17 - 2024-07-19</li>
841. <li><a href="https://www.papercall.io/conf42-rustlang-2024">Conf42 Rustlang 2024</a> | Closes 2024-07-22 | online | Event date: 2024-08-22</li>
842. </ul>
843. <p>If you are an event organizer hoping to expand the reach of your event, please submit a link to the submission website through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a>.</p>
844. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#updates-from-the-rust-project">Updates from the Rust Project</a></h4>
845. <p>329 pull requests were <a href="https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2024-05-07..2024-05-14">merged in the last week</a></p>
846. <ul>
847. <li><a href="https://github.com/rust-lang/rust/pull/124936">analyse visitor: build proof tree in probe</a></li>
848. <li><a href="https://github.com/rust-lang/rust/pull/124988">consolidate obligation cause codes for where clauses</a></li>
849. <li><a href="https://github.com/rust-lang/rust/pull/124836">correct the const stabilization of <code>last_chunk</code> for slices</a></li>
850. <li><a href="https://github.com/rust-lang/rust/pull/124223">coverage: branch coverage support for let-else and if-let</a></li>
851. <li><a href="https://github.com/rust-lang/rust/pull/124615">coverage: further simplify extraction of mapping info from MIR</a></li>
852. <li><a href="https://github.com/rust-lang/rust/pull/124774">display walltime benchmarks with subnanosecond precision</a></li>
853. <li><a href="https://github.com/rust-lang/rust/pull/124219">do not ICE on <code>AnonConst</code>s in <code>diagnostic_hir_wf_check</code></a></li>
854. <li><a href="https://github.com/rust-lang/rust/pull/124683">do not ICE on foreign malformed <code>diagnostic::on_unimplemented</code></a></li>
855. <li><a href="https://github.com/rust-lang/rust/pull/124157">do not add leading asterisk in the <code>PartialEq</code></a></li>
856. <li><a href="https://github.com/rust-lang/rust/pull/124846">don't ICE when we cannot eval a const to a valtree in the new solver</a></li>
857. <li><a href="https://github.com/rust-lang/rust/pull/125063">don't call <code>env::set_var</code> in <code>rustc_driver::install_ice_hook</code></a></li>
858. <li><a href="https://github.com/rust-lang/rust/pull/124777">fix error messages for <code>break</code> inside coroutines</a></li>
859. <li><a href="https://github.com/rust-lang/rust/pull/124997">fix ICE while casting a type with error</a></li>
860. <li><a href="https://github.com/rust-lang/rust/pull/124902">fix <code>MemCategorization</code> and <code>ExprUse</code> visitors for new solver (this time it's better)</a></li>
861. <li><a href="https://github.com/rust-lang/rust/pull/124761">fix insufficient logic when searching for the underlying allocation</a></li>
862. <li><a href="https://github.com/rust-lang/rust/pull/124875">fix more ICEs in <code>diagnostic::on_unimplemented</code></a></li>
863. <li><a href="https://github.com/rust-lang/rust/pull/124778">fix parse error message for meta items</a></li>
864. <li><a href="https://github.com/rust-lang/rust/pull/124978">handle Deref expressions in <code>invalid_reference_casting</code></a></li>
865. <li><a href="https://github.com/rust-lang/rust/pull/124908">handle field projections like slice indexing in <code>invalid_reference_casting</code></a></li>
866. <li><a href="https://github.com/rust-lang/rust/pull/124903">ignore empty <code>RUSTC_WRAPPER</code> in bootstrap</a></li>
867. <li><a href="https://github.com/rust-lang/rust/pull/124318">ignore generics args in attribute paths</a></li>
868. <li><a href="https://github.com/rust-lang/rust/pull/124793">implement <code>as_chunks</code> with <code>split_at_unchecked</code></a></li>
869. <li><a href="https://github.com/rust-lang/rust/pull/124781">implement lldb formatter for "clang encoded" enums (LLDB 18.1+) (V3)</a></li>
870. <li><a href="https://github.com/rust-lang/rust/pull/124779">improve <code>rustc_parse::Parser</code>'s debuggability</a></li>
871. <li><a href="https://github.com/rust-lang/rust/pull/124926">make <code>#![feature]</code> suggestion <code>MaybeIncorrect</code></a></li>
872. <li><a href="https://github.com/rust-lang/rust/pull/124957">make <code>Ty::builtin_deref</code> just return a <code>Ty</code></a></li>
873. <li><a href="https://github.com/rust-lang/rust/pull/124930">make sure we consume a generic arg when checking mistyped turbofish</a></li>
874. <li><a href="https://github.com/rust-lang/rust/pull/124869">make sure we don't deny macro vars w keyword names</a></li>
875. <li><a href="https://github.com/rust-lang/rust/pull/124567">match ergonomics 2024: let <code>&</code> patterns eat <code>&mut</code></a></li>
876. <li><a href="https://github.com/rust-lang/rust/pull/124639">match ergonomics 2024: migration lint</a></li>
877. <li><a href="https://github.com/rust-lang/rust/pull/125051">pretty-print let-else with added parenthesization when needed</a></li>
878. <li><a href="https://github.com/rust-lang/rust/pull/123344">remove braces when fixing a nested use tree into a single item</a></li>
879. <li><a href="https://github.com/rust-lang/rust/pull/124953">rename <code>Generics::params</code> to <code>Generics::own_params</code></a></li>
880. <li><a href="https://github.com/rust-lang/rust/pull/124876">simplify <code>use crate::rustc_foo::bar</code> occurrences</a></li>
881. <li><a href="https://github.com/rust-lang/rust/pull/125076">split out <code>ty::AliasTerm</code> from <code>ty::AliasTy</code></a></li>
882. <li><a href="https://github.com/rust-lang/rust/pull/124982">uplift <code>TraitRef</code> into <code>rustc_type_ir</code></a></li>
883. <li><a href="https://github.com/rust-lang/rust/pull/125001">uplift various <code>*Predicate</code> types into <code>rustc_type_ir</code></a></li>
884. <li><a href="https://github.com/rust-lang/rust/pull/124955">use fewer origins when creating type variables</a></li>
885. <li><a href="https://github.com/rust-lang/rust/pull/123332">never patterns: lower never patterns to <code>Unreachable</code> in MIR</a></li>
886. <li><a href="https://github.com/rust-lang/rust/pull/123886">avoid <code>alloca</code>s in codegen for simple <code>mir::Aggregate</code> statements</a></li>
887. <li><a href="https://github.com/rust-lang/rust/pull/124923">interpret/miri: better errors on failing <code>offset_from</code></a></li>
888. <li><a href="https://github.com/rust-lang/miri/pull/3589">miri: <code>io::Error</code> handling: keep around the full <code>io::Error</code> for longer so we can give better errors</a></li>
889. <li><a href="https://github.com/rust-lang/miri/pull/3601">miri: a bit of intrinsics organization</a></li>
890. <li><a href="https://github.com/rust-lang/miri/pull/3588">miri: allow test targets to be set via CLI args</a></li>
891. <li><a href="https://github.com/rust-lang/miri/pull/3604">miri: intrinsics: just panic when they get used incorrectly</a></li>
892. <li><a href="https://github.com/rust-lang/miri/pull/3590">miri: make <code>MIRI_TEST_TARGET</code> and <code>RUSTC_BLESS</code> entirely an internal thing</a></li>
893. <li><a href="https://github.com/rust-lang/miri/pull/3580">miri: return non-null pointer from <code>malloc(0)</code></a></li>
894. <li><a href="https://github.com/rust-lang/miri/pull/3596">miri: support <code>f*_algebraic</code></a></li>
895. <li><a href="https://github.com/rust-lang/miri/pull/3600">miri: use non-null pointer for size 0 posix memalign</a></li>
896. <li><a href="https://github.com/rust-lang/rust/pull/124932">codegen: memmove/memset cannot be non-temporal</a></li>
897. <li><a href="https://github.com/rust-lang/rustc_codegen_cranelift/pull/1489">codegen-cranelift: translate MIR to clif ir in parallel with parallel rustc</a></li>
898. <li><a href="https://github.com/rust-lang/rust/pull/124928">stabilize <code>byte_slice_trim_ascii</code> for <code>&[u8]</code>/<code>&str</code></a></li>
899. <li><a href="https://github.com/rust-lang/rust/pull/123817">stabilize <code>seek_seek_relative</code></a></li>
900. <li><a href="https://github.com/rust-lang/rust/pull/124981">relax allocator requirements on some Rc/Arc APIs</a></li>
901. <li><a href="https://github.com/rust-lang/rust/pull/124828"><code>f16::is_sign_{positive,negative}</code> were feature-gated on f128</a></li>
902. <li><a href="https://github.com/rust-lang/rust/pull/125012"><code>io::Write::write_fmt</code>: panic if the formatter fails when the stream does not fail</a></li>
903. <li><a href="https://github.com/rust-lang/rust/pull/124470"><code>std::net: Socket::new_raw</code> now set to <code>SO_NOSIGPIPE</code> on freebsd</a></li>
904. <li><a href="https://github.com/rust-lang/rust/pull/124766"><code>std::rand</code>: adding solaris/illumos for getrandom support</a></li>
905. <li><a href="https://github.com/rust-lang/cargo/pull/13884">cargo: add local-only build scripts example in check-cfg docs</a></li>
906. <li><a href="https://github.com/rust-lang/cargo/pull/13842">cargo: fix: build only the specified artifact library when multiple types are available</a></li>
907. <li><a href="https://github.com/rust-lang/rust/pull/124738">rustdoc: dedup search form HTML</a></li>
908. <li><a href="https://github.com/rust-lang/rust/pull/124864">rustdoc: use stability, instead of features, to decide what to show</a></li>
909. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12764">clippy: <code>significant_drop_in_scrutinee</code>: Fix false positives due to false drops of place expressions</a></li>
910. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12770">clippy: add new lint <code>doc_lazy_continuation</code></a></li>
911. <li><a href="https://github.com/rust-lang/rust-clippy/pull/11540">clippy: add new lint that disallow renaming parameters in trait functions</a></li>
912. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12650">clippy: fix false positive because lack of consideration of mutable caller</a></li>
913. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12777">clippy: fix: merge multiple suggestions into a single multi-span suggestion in <code>needless_late_init</code></a></li>
914. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12783">clippy: fix: use <code>hir_with_context</code> to produce correct snippets for <code>assigning_clones</code></a></li>
915. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12620">clippy: handle <code>rustc_on_unimplemented</code> in <code>duplicated_attributes</code></a></li>
916. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12780">clippy: ignore <code>_to_string</code> lints in code <code>from_expansion</code></a></li>
917. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12730">clippy: lint direct priority conflicts in <code>[workspace.lints]</code></a></li>
918. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12787">clippy: make <code>from_str_radix_10</code> skip constant context</a></li>
919. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12107">clippy: new lint: <code>macro_metavars_in_unsafe</code></a></li>
920. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17203">rust-analyzer: fix OOM caused by term search</a></li>
921. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17192">rust-analyzer: fix <code>source_range</code> for <code>INT_NUMBER</code> in completion</a></li>
922. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17220">rust-analyzer: fix: improve confusing literal hovers</a></li>
923. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17187">rust-analyzer: fix: keep parentheses when the precedence of inner expr is lower than the outer one</a></li>
924. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17207">rust-analyzer: fix: report all LSP protocol errors with <code>invalid_data</code></a></li>
925. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17208">rust-analyzer: fix: report both IO errors and <code>main_loop</code> errors</a></li>
926. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17195">rust-analyzer: implement unsafe attribute parsing</a></li>
927. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17188">rust-analyzer: use the repository field to link to the repository</a></li>
928. </ul>
929. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage">Rust Compiler Performance Triage</a></h5>
930. <p>A pretty quiet week with only a few PRs being flagged for analysis.
931. More improvements than regressions this week, and also several nice
932. binary size reductions caused by generating less LLVM IR.</p>
933. <p>Triage done by <strong>@kobzol</strong>.
934. Revision range: <a href="https://perf.rust-lang.org/?start=69f53f5e5583381267298ac182eb02c7f1b5c1cd&end=9105c57b7f6623310e33f3ee7e48a3114e5190a7&absolute=false&stat=instructions%3Au">69f53f5e..9105c57b</a></p>
935. <p><strong>Summary</strong>:</p>
936. <table>
937. <thead>
938. <tr>
939. <th align="center">(instructions:u)</th>
940. <th align="center">mean</th>
941. <th align="center">range</th>
942. <th align="center">count</th>
943. </tr>
944. </thead>
945. <tbody>
946. <tr>
947. <td align="center">Regressions ❌ <br /> (primary)</td>
948. <td align="center">0.4%</td>
949. <td align="center">[0.2%, 0.9%]</td>
950. <td align="center">8</td>
951. </tr>
952. <tr>
953. <td align="center">Regressions ❌ <br /> (secondary)</td>
954. <td align="center">0.9%</td>
955. <td align="center">[0.2%, 2.4%]</td>
956. <td align="center">18</td>
957. </tr>
958. <tr>
959. <td align="center">Improvements ✅ <br /> (primary)</td>
960. <td align="center">-1.1%</td>
961. <td align="center">[-2.3%, -0.2%]</td>
962. <td align="center">51</td>
963. </tr>
964. <tr>
965. <td align="center">Improvements ✅ <br /> (secondary)</td>
966. <td align="center">-0.6%</td>
967. <td align="center">[-1.4%, -0.3%]</td>
968. <td align="center">19</td>
969. </tr>
970. <tr>
971. <td align="center">All ❌✅ (primary)</td>
972. <td align="center">-0.9%</td>
973. <td align="center">[-2.3%, 0.9%]</td>
974. <td align="center">59</td>
975. </tr>
976. </tbody>
977. </table>
978. <p>1 Regression, 0 Improvements, 3 Mixed; 0 of them in rollups
979. 75 artifact comparisons made in total</p>
980. <p><a href="https://github.com/Kobzol/rustc-perf/blob/0ab8cfe4bdc3044f8e610349d90c1708675b1ccf/triage/2024-05-14.md">Full report here</a></p>
981. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#approved-rfcs"></a><a href="https://github.com/rust-lang/rfcs/commits/master">Approved RFCs</a></h5>
982. <p>Changes to Rust follow the Rust <a href="https://github.com/rust-lang/rfcs#rust-rfcs">RFC (request for comments) process</a>. These
983. are the RFCs that were approved for implementation this week:</p>
984. <ul>
985. <li><em>No RFCs were approved this week.</em></li>
986. </ul>
987. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#final-comment-period">Final Comment Period</a></h5>
988. <p>Every week, <a href="https://www.rust-lang.org/team.html">the team</a> announces the 'final comment period' for RFCs and key PRs
989. which are reaching a decision. Express your opinions now.</p>
990. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rfcs_1"></a><a href="https://github.com/rust-lang/rfcs/labels/final-comment-period">RFCs</a></h6>
991. <ul>
992. <li><em>No RFCs entered Final Comment Period this week.</em></li>
993. </ul>
994. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#tracking-issues-prs">Tracking Issues & PRs</a></h6>
995. <a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust_1"></a><a href="https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc">Rust</a>
996. <ul>
997. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/issues/113744">Tracking Issue for <code>IpvNAddr::{BITS, to_bits, from_bits}</code> (<code>ip_bits</code>)</a></li>
998. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/123168">Add <code>size_of</code> and <code>size_of_val</code> and <code>align_of</code> and <code>align_of_val</code> to the prelude</a></li>
999. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/117329">offset: allow zero-byte offset on arbitrary pointers</a></li>
1000. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124611">Add <code>-</code> (stdin) support in rustdoc</a></li>
1001. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124187">Warn (or error) when <code>Self</code> ctor from outer item is referenced in inner nested item</a></li>
1002. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124211">Bump <code>elided_lifetimes</code>_in_associated_constant to deny</a></li>
1003. </ul>
1004. <a class="toclink" href="http://this-week-in-rust.org/atom.xml#unsafe-code-guidelines"></a><a href="https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc">Unsafe Code Guidelines</a>
1005. <ul>
1006. <li>[disposition: merge] <a href="https://github.com/rust-lang/unsafe-code-guidelines/issues/510">Decide on validity for metadata of wide pointer/reference with slice tail</a></li>
1007. </ul>
1008. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#new-and-updated-rfcs"></a><a href="https://github.com/rust-lang/rfcs/pulls">New and Updated RFCs</a></h6>
1009. <ul>
1010. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3635">[RFC] externally definable statics</a></li>
1011. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3634">Scoped <code>impl Trait for Type</code></a></li>
1012. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3633">[RFC] <code>core::marker::Freeze</code> in bounds</a></li>
1013. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3632">[RFC] externally implementable functions</a></li>
1014. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3631">RFC for doc_cfg, doc_cfg_auto, doc_cfg_hide and doc_cfg_show features</a></li>
1015. </ul>
1016. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#upcoming-events">Upcoming Events</a></h4>
1017. <p>Rusty Events between 2024-05-15 - 2024-06-12 🦀</p>
1018. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#virtual">Virtual</a></h5>
1019. <ul>
1020. <li>2024-05-15 | Virtual (Ankara, TR) | <a href="https://kommunity.com/turkiye-rust-community/events/">Türkiye Rust Community</a><ul>
1021. <li><a href="https://kommunity.com/turkiye-rust-community/events/rustsemineri-7-0a97e784"><strong>#RustSemineri - 7</strong></a></li>
1022. </ul>
1023. </li>
1024. <li>2024-05-15 | Virtual (Cardiff, UK) | <a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/">Rust and C++ Cardiff</a><ul>
1025. <li><a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/events/300819214/"><strong>Rust for Rustaceans Book Club: Chapter 6 - Testing</strong></a></li>
1026. </ul>
1027. </li>
1028. <li>2024-05-15 | Virtual (Vancouver, BC, CA) | <a href="https://www.meetup.com/vancouver-rust/">Vancouver Rust</a><ul>
1029. <li><a href="https://www.meetup.com/vancouver-rust/events/298542331/"><strong>NativeLink</strong></a></li>
1030. </ul>
1031. </li>
1032. <li>2024-05-16 | Virtual (Ankara, TR) | <a href="https://kommunity.com/turkiye-rust-community/events">Türkiye Rust Community</a><ul>
1033. <li><a href="https://kommunity.com/turkiye-rust-community/events/rustsemineri-8-ddfe6b15"><strong>#RustSemineri - 8</strong></a></li>
1034. </ul>
1035. </li>
1036. <li>2024-05-16 | Virtual (Charlottesville, VA, US) | <a href="https://www.meetup.com/charlottesville-rust-meetup/">Charlottesville Rust Meetup</a><ul>
1037. <li><a href="https://www.meetup.com/charlottesville-rust-meetup/events/298312423/"><strong>Crafting Interpreters in Rust Collaboratively</strong></a></li>
1038. </ul>
1039. </li>
1040. <li>2024-05-17 | Virtual | <a href="https://www.eventbrite.com/o/training-4-programmers-llc-80387368983">Training 4 Programmers LLC</a><ul>
1041. <li><a href="https://www.eventbrite.com/e/rust-at-full-speed-harnessing-concurrency-with-confidence-tickets-884842296127"><strong>Rust at Full Speed: Harnessing Concurrency with Confidence</strong></a></li>
1042. </ul>
1043. </li>
1044. <li>2024-05-21 | Virtual (Washington, DC, US) | <a href="https://www.meetup.com/rustdc/">Rust DC</a><ul>
1045. <li><a href="https://www.meetup.com/rustdc/events/299346490/"><strong>Mid-month Rustful—forensic parsing via Artemis</strong></a></li>
1046. </ul>
1047. </li>
1048. <li>2024-05-23 | Virtual (Berlin, DE) | <a href="https://berline.rs/">OpenTechSchool Berlin</a> + <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
1049. <li><a href="https://meet.jit.si/RustHackAndLearnBerlin"><strong>Rust Hack and Learn</strong></a> | <a href="https://www.meetup.com/rust-berlin/events/298477699/"><strong>Mirror: Rust Hack n Learn Meetup</strong></a></li>
1050. </ul>
1051. </li>
1052. <li>2024-05-23 | Virtual (Israel) | <a href="https://rust.org.il/">Rust in Israel</a><ul>
1053. <li><a href="https://www.meetup.com/code-mavens/events/300974367/"><strong>Web development in Rust using Rocket (Hebrew)</strong></a></li>
1054. </ul>
1055. </li>
1056. <li>2024-05-28 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/">Dallas Rust</a><ul>
1057. <li><a href="https://www.meetup.com/dallasrust/events/300533392/"><strong>Last Tuesday</strong></a></li>
1058. </ul>
1059. </li>
1060. <li>2024-05-28 & 2024-05-28 | Virtual | <a href="https://mainmatter.com/">Mainmatter</a><ul>
1061. <li><a href="https://ti.to/mainmatter/rust-telemetry-may-2024"><strong>Remote Workshop: Telemetry for Rust APIs – you can't fix what you can't see (fee)</strong></a></li>
1062. </ul>
1063. </li>
1064. <li>2024-05-30 | Virtual + In Person (Barcelona, ES) | <a href="https://mainmatter.com/">Mainmatter</a> & <a href="https://www.meetup.com/es-ES/bcnrust/">BcnRust</a><ul>
1065. <li><a href="https://www.meetup.com/es-ES/bcnrust/events/300765894/"><strong>Rust for the web, Barcelona 2024</strong></a> </li>
1066. </ul>
1067. </li>
1068. <li>2024-05-30 | Virtual (Charlottesville, NC, US) | <a href="https://www.meetup.com/charlottesville-rust-meetup/">Charlottesville Rust Meetup</a><ul>
1069. <li><a href="https://www.meetup.com/charlottesville-rust-meetup/events/298542326/"><strong>Crafting Interpreters in Rust Collaboratively</strong></a></li>
1070. </ul>
1071. </li>
1072. <li>2024-06-04 | Virtual (Buffalo, NY) | <a href="https://www.meetup.com/buffalo-rust-meetup/">Buffalo Rust Meetup</a><ul>
1073. <li><a href="https://www.meetup.com/buffalo-rust-meetup/events/300191681/"><strong>Buffalo Rust User Group</strong></a></li>
1074. </ul>
1075. </li>
1076. <li>2024-06-05 | Virtual (Indianapolis, IN, US) | <a href="https://www.meetup.com/indyrs/">Indy Rust</a><ul>
1077. <li><a href="https://www.meetup.com/indyrs/events/299047896/"><strong>Indy.rs - with Social Distancing</strong></a></li>
1078. </ul>
1079. </li>
1080. <li>2024-06-06 | Virtual (Berlin, DE) | <a href="https://berline.rs/">OpenTechSchool Berlin</a> + <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
1081. <li><a href="https://meet.jit.si/RustHackAndLearnBerlin"><strong>Rust Hack and Learn</strong></a> | <a href="https://www.meetup.com/rust-berlin/events/298477702/"><strong>Mirror: Rust Hack n Learn Meetup</strong></a></li>
1082. </ul>
1083. </li>
1084. <li>2024-06-11 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/">Dallas Rust</a><ul>
1085. <li><a href="https://www.meetup.com/dallasrust/events/298341709/"><strong>Second Tuesday</strong></a></li>
1086. </ul>
1087. </li>
1088. </ul>
1089. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#africa">Africa</a></h5>
1090. <ul>
1091. <li>2024-06-01 | Kampala, UG | <a href="https://www.eventbrite.com/o/rust-circle-kampala-65249289033">Rust Circle Kampala</a><ul>
1092. <li><a href="https://www.eventbrite.com/e/rust-circle-meetup-tickets-628763176587"><strong>Rust Circle Meetup</strong></a></li>
1093. </ul>
1094. </li>
1095. </ul>
1096. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#asia">Asia</a></h5>
1097. <ul>
1098. <li>2024-05-22 | Singapore, SG | <a href="https://www.meetup.com/rust-singapore/">SG Rust Meetup</a><ul>
1099. <li><a href="https://www.meetup.com/rust-singapore/events/300988123/"><strong>SG Rustaceans! Updated - SG Rust Meetup at CraftsforGreen Whole Studio</strong></a></li>
1100. </ul>
1101. </li>
1102. </ul>
1103. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#europe">Europe</a></h5>
1104. <ul>
1105. <li>2024-05-16 | Augsburg, DE | <a href="https://www.meetup.com/rust-meetup-augsburg/">Rust Meetup Augsburg</a><ul>
1106. <li><a href="https://www.meetup.com/rust-meetup-augsburg/events/300174327/"><strong>Augsburg Rust Meetup #7</strong></a></li>
1107. </ul>
1108. </li>
1109. <li>2024-05-16 | Paris, FR | <a href="https://mobilizon.fr/@rust_paris">Rust Paris</a><ul>
1110. <li><a href="https://mobilizon.fr/events/14b51ccc-211f-400f-9615-707d9d871e78"><strong>Paris Rust Meetup #68</strong></a></li>
1111. </ul>
1112. </li>
1113. <li>2024-05-21 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus/">Rust Aarhus</a><ul>
1114. <li><a href="https://www.meetup.com/rust-aarhus/events/300307155/"><strong>Hack Night</strong></a></li>
1115. </ul>
1116. </li>
1117. <li>2024-05-21 | Zurich, CH | <a href="https://www.meetup.com/rust-zurich/">Rust Zurich</a><ul>
1118. <li><a href="https://www.meetup.com/rust-zurich/events/300513957/"><strong>Save the date - Mai Meetup</strong></a></li>
1119. </ul>
1120. </li>
1121. <li>2024-05-22 | Leiden, NL | <a href="https://www.meetup.com/freshminds-future-proof-software-development/">Future-proof Software Development by FreshMinds</a><ul>
1122. <li><a href="https://www.meetup.com/freshminds-future-proof-software-development/events/300566391/"><strong>Coding Dojo Session</strong></a></li>
1123. </ul>
1124. </li>
1125. <li>2024-05-23 | Bern, CH | <a href="https://www.meetup.com/de-DE/rust-bern/">Rust Bern</a><ul>
1126. <li><a href="https://www.meetup.com/rust-bern/events/300286917/"><strong>2024 Rust Talks Bern #2</strong></a></li>
1127. </ul>
1128. </li>
1129. <li>2024-05-23 | Łodz, PL | <a href="https://www.linkedin.com/posts/mobica_rust-programming-embeddedsoftware-activity-7193232853717946369-CK68/">Mobica</a><ul>
1130. <li><a href="https://www.interankiety.pl/f/b4D7G7xO"><strong>Zapisz się na warsztat Rust / Embedded w Łodzi! / What's all the fuss about Rust?</strong></a></li>
1131. </ul>
1132. </li>
1133. <li>2024-05-23 | Manchester, UK | <a href="https://www.meetup.com/rust-manchester/">Rust Manchester</a><ul>
1134. <li><a href="https://www.meetup.com/rust-manchester/events/300923207/"><strong>Rust Manchester May Code Night</strong></a></li>
1135. </ul>
1136. </li>
1137. <li>2024-05-24 | Bordeaux, FR | <a href="https://www.meetup.com/bordeaux-rust/">Rust Bordeaux</a><ul>
1138. <li><a href="https://www.meetup.com/bordeaux-rust/events/300723854/"><strong>Rust Bordeaux #3: Discussions</strong></a></li>
1139. </ul>
1140. </li>
1141. <li>2024-05-25 | Stockholm, SE | <a href="https://www.meetup.com/stockholm-rust/">Stockholm Rust</a><ul>
1142. <li><a href="https://www.meetup.com/stockholm-rust/events/301014982/"><strong>Ferris' Fika Forum #3 [Embedded lab edition]</strong></a></li>
1143. </ul>
1144. </li>
1145. <li>2024-05-28 - 2024-05-30 | Berlin, DE | <a href="https://oxidizeconf.com/">Oxidize</a><ul>
1146. <li><a href="https://oxidizeconf.com/"><strong>Oxidize Conf 2024</strong></a></li>
1147. </ul>
1148. </li>
1149. <li>2024-05-30 | Barcelona, ES | <a href="https://mainmatter.com/">Mainmatter</a> & <a href="https://www.meetup.com/es-ES/bcnrust/">BcnRust</a><ul>
1150. <li><a href="https://www.meetup.com/es-ES/bcnrust/events/300765894/"><strong>Rust for the web, Barcelona 2024</strong></a> </li>
1151. </ul>
1152. </li>
1153. <li>2024-05-30 | Berlin, DE | <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
1154. <li><a href="https://www.meetup.com/rust-berlin/events/299288963/"><strong>Rust and Tell - Title</strong></a></li>
1155. </ul>
1156. </li>
1157. <li>2024-05-30 | Copenhagen, DK | <a href="https://www.meetup.com/copenhagen-rust-community">Copenhagen Rust Community</a><ul>
1158. <li><a href="https://www.meetup.com/copenhagen-rust-community/events/300458222/"><strong>Rust meetup #47 sponsored by Microsoft!</strong></a></li>
1159. </ul>
1160. </li>
1161. <li>2024-05-30 | Oslo, NO | <a href="https://www.meetup.com/rust-oslo/events/">Rust Oslo</a><ul>
1162. <li><a href="https://www.meetup.com/rust-oslo/events/300453310/"><strong>Rust Hack'n'Learn at Kampen Bistro</strong></a></li>
1163. </ul>
1164. </li>
1165. <li>2024-06-05 | Hamburg, DE | <a href="https://www.meetup.com/rust-meetup-hamburg/">Rust Meetup Hamburg</a><ul>
1166. <li><a href="https://www.meetup.com/rust-meetup-hamburg/events/299235215/"><strong>Rust Hack & Learn June 2024</strong></a></li>
1167. </ul>
1168. </li>
1169. <li>2025-06-06 | Vilnius, LT | <a href="https://www.meetup.com/rust-in-vilnius/">Rust Vilnius</a><ul>
1170. <li><a href="https://www.meetup.com/rust-in-vilnius/events/301012097/"><strong>Enjoy our second Rust and ZIG event</strong></a></li>
1171. </ul>
1172. </li>
1173. </ul>
1174. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#north-america">North America</a></h5>
1175. <ul>
1176. <li>2024-05-16 | Mountain View, CA, US | <a href="https://www.meetup.com/mv-rust-meetup/">Mountain View Rust Meetup</a><ul>
1177. <li><a href="https://www.meetup.com/mv-rust-meetup/events/300775539/"><strong>Rust Meetup at Hacker Dojo</strong></a></li>
1178. </ul>
1179. </li>
1180. <li>2024-05-16 | Seattle, WA, US | <a href="https://www.meetup.com/seattle-rust-user-group/">Seattle Rust User Group</a><ul>
1181. <li><a href="https://www.meetup.com/seattle-rust-user-group/events/299509369/"><strong>Seattle Rust User Group Meetup</strong></a></li>
1182. </ul>
1183. </li>
1184. <li>2024-05-20 | Somerville, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
1185. <li><a href="https://www.meetup.com/bostonrust/events/300116765/"><strong>Ball Square Rust Lunch, May 20</strong></a></li>
1186. </ul>
1187. </li>
1188. <li>2024-05-21 | San Francisco, CA, US | <a href="https://www.meetup.com/san-francisco-rust-study-group/">San Francisco Rust Study Group</a><ul>
1189. <li><a href="https://www.meetup.com/san-francisco-rust-study-group/events/299186931/"><strong>Rust Hacking in Person</strong></a></li>
1190. </ul>
1191. </li>
1192. <li>2024-05-22 | Austin, TX, US | <a href="https://www.meetup.com/rust-atx/">Rust ATX</a><ul>
1193. <li><a href="https://www.meetup.com/rust-atx/events/xvkdgtygchbdc/"><strong>Rust Lunch - Fareground</strong></a></li>
1194. </ul>
1195. </li>
1196. <li>2024-05-25 | Chicago, IL, US | <a href="https://www.meetup.com/deep-dish-rust/">Deep Dish Rust</a><ul>
1197. <li><a href="https://www.meetup.com/deep-dish-rust/events/300665520/"><strong>Rust Talk Double Feature</strong></a></li>
1198. </ul>
1199. </li>
1200. <li>2024-05-30 | Mountain View, CA, US | <a href="https://www.meetup.com/mv-rust-meetup/">Mountain View Rust Meetup</a><ul>
1201. <li><a href="https://www.meetup.com/mv-rust-meetup/events/300775547/"><strong>Rust Meetup at Hacker Dojo</strong></a></li>
1202. </ul>
1203. </li>
1204. <li>2024-05-31 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
1205. <li><a href="https://www.meetup.com/bostonrust/events/300116786/"><strong>Boston Common Rust Lunch, May 31</strong></a></li>
1206. </ul>
1207. </li>
1208. <li>2024-06-08 | Somerville, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
1209. <li><a href="https://www.meetup.com/bostonrust/events/300116799/"><strong>Porter Square Rust Lunch, Jun 8</strong></a></li>
1210. </ul>
1211. </li>
1212. </ul>
1213. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#oceania">Oceania</a></h5>
1214. <ul>
1215. <li>2024-05-28 | Sydney, NSW, AU | <a href="https://www.meetup.com/rust-sydney/">Rust Sydney</a><ul>
1216. <li><a href="https://www.meetup.com/rust-sydney/events/300854266/"><strong>a demo 🤯 & a lightning ⚡show ✨</strong></a></li>
1217. </ul>
1218. </li>
1219. </ul>
1220. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#south-america">South America</a></h5>
1221. <ul>
1222. <li>2024-06-06 | Buenos Aires, AR | <a href="https://www.meetup.com/rust-argentina/">Rust en Español | Rust Argentina</a><ul>
1223. <li><a href="https://www.meetup.com/rust-argentina/events/299740249"><strong>Juntada de Junio</strong></a></li>
1224. </ul>
1225. </li>
1226. </ul>
1227. <p>If you are running a Rust event please add it to the <a href="https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com">calendar</a> to get
1228. it mentioned here. Please remember to add a link to the event too.
1229. Email the <a href="mailto:community-team@rust-lang.org">Rust Community Team</a> for access.</p>
1230. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#jobs">Jobs</a></h4>
1231.  
1232.  
1233. <p>Please see the latest <a href="https://www.reddit.com/r/rust/comments/1cixuzr/official_rrust_whos_hiring_thread_for_jobseekers/">Who's Hiring thread on r/rust</a></p>
1234. <h3><a class="toclink" href="http://this-week-in-rust.org/atom.xml#quote-of-the-week">Quote of the Week</a></h3>
1235. <blockquote>
1236. <p>Unfortunately, most people seem to have taken the wrong lesson from Rust. They see all of this business with lifetimes and ownership as a dirty mess that Rust has had to adopt because it wanted to avoid garbage collection. But this is completely backwards! Rust adopted rules around shared mutable state and this enabled it to avoid garbage collection. These rules are a good idea regardless.</p>
1237. </blockquote>
1238. <p>– <a href="https://without.boats/blog/references-are-like-jumps/">without boats</a></p>
1239. <p>Thanks to <a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328/1567">Jules Bertholet</a> for the last-minute suggestion!</p>
1240. <p><a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328">Please submit quotes and vote for next week!</a></p>
1241. <p><em>This Week in Rust is edited by: <a href="https://github.com/nellshamrell">nellshamrell</a>, <a href="https://github.com/llogiq">llogiq</a>, <a href="https://github.com/cdmistman">cdmistman</a>, <a href="https://github.com/ericseppanen">ericseppanen</a>, <a href="https://github.com/extrawurst">extrawurst</a>, <a href="https://github.com/andrewpollack">andrewpollack</a>, <a href="https://github.com/U007D">U007D</a>, <a href="https://github.com/kolharsam">kolharsam</a>, <a href="https://github.com/joelmarcey">joelmarcey</a>, <a href="https://github.com/mariannegoldin">mariannegoldin</a>, <a href="https://github.com/bennyvasquez">bennyvasquez</a>.</em></p>
1242. <p><em>Email list hosting is sponsored by <a href="https://foundation.rust-lang.org/">The Rust Foundation</a></em></p>
1243. &lt;p&gt;&lt;small&gt;&lt;a href=&quot;https://www.reddit.com/r/rust/comments/1ct92nz/this_week_in_rust_547/&quot;&gt;Discuss on r/rust&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;</description>
1244. <pubDate>Wed, 15 May 2024 04:00:00 +0000</pubDate>
1245. <dc:creator>TWiR Contributors</dc:creator>
1246. </item>
1247. <item>
1248. <title>Mozilla Addons Blog: Manifest V3 Updates</title>
1249. <guid isPermaLink="false">https://blog.mozilla.org/addons/?p=9173</guid>
1250. <link>https://blog.mozilla.org/addons/2024/05/14/manifest-v3-updates/</link>
1251. <description>&lt;p&gt;Greetings add-on developers! We wanted to provide an update on some exciting engineering work planned for the next few Firefox releases in support of Manifest V3. The team continues to implement API changes that were previously defined in agreement with other browser vendors that participate in the WECG, ahead of Chrome’s MV2 deprecation. Another top area of focus has been around addressing some developer and end user friction related to MV3 host permissions.&lt;/p&gt;
1252. <p>The table below details some MV3 changes that are going to be available in the Firefox release channel soon.</p>
1253. <table class="data-table" style="height: 335px;" width="679">
1254. <thead>
1255. <tr>
1256. <th>Version</th>
1257. <th>Manifest V3 engineering updates</th>
1258. <th>Nightly</th>
1259. <th>Beta</th>
1260. <th>Release</th>
1261. </tr>
1262. </thead>
1263. <tbody>
1264. <tr>
1265. <td><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/126#changes_for_add-on_developers">126</a></td>
1266. <td>Chrome extension porting API enhancements:<p></p>
1267. <ul>
1268. <li>The “webRequestAuthProvider” permission is now supported to provide compatibility with Chrome for requesting permission for<a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/onAuthRequired"> webRequest.onAuthRequired</a> in Manifest V3</li>
1269. <li>The<a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/options_page"> options_page manifest key</a> is provided as an alias of the<a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/options_ui"> options_ui</a> key to offer better extension compatibility with Chrome</li>
1270. </ul>
1271. </td>
1272. <td style="text-align: center;">3/18</td>
1273. <td style="text-align: left;">4/15</td>
1274. <td style="text-align: center;">5/14</td>
1275. </tr>
1276. <tr>
1277. <td><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/127#changes_for_add-on_developers">127</a></td>
1278. <td>Updating MV3 host permissions on both desktop and mobile.</td>
1279. <td style="text-align: center;">4/15</td>
1280. <td style="text-align: center;">5/13</td>
1281. <td style="text-align: center;">6/11</td>
1282. </tr>
1283. <tr>
1284. <td>128</td>
1285. <td>Implementing the UI necessary to control optional permissions and supporting host permissions on Android that landed in 127.</td>
1286. <td style="text-align: center;">5/13</td>
1287. <td style="text-align: center;">6/10</td>
1288. <td style="text-align: center;">7/9</td>
1289. </tr>
1290. </tbody>
1291. </table>
1292. <p>The Chrome extension porting API work that will land beginning in 126 will help ensure a higher level of compatibility and reduce friction for add-on developers supporting multiple browsers.</p>
1293. <p>Beginning with Firefox 127, users will be prompted to grant MV3 host permissions as part of the install flow (similar to MV2 extensions). We’re excited to deliver this work as based on feedback from Firefox users and extension developers, this has been a major hurdle for MV3 extensions in Firefox.</p>
1294. <p>However, unlike the host permission granted at install time for MV2 extensions, MV3 host permissions can still be revoked by the user at any time from the about:addons page on Firefox Desktop. Given that, MV3 extensions should still leverage the permissions API to ensure that the permissions required are already granted.</p>
1295. <p>Lastly, in Firefox for Android 128, the Add-ons Manager will include a new permissions UI as shown below — this new UI will allow users to do the same as above on Firefox for Android with regards to host permissions, while also granting or revoking other optional permissions on MV2 and MV3 extensions.</p>
1296. <p><span style="color: #ffffff;">                 </span> <img alt="" class="alignnone wp-image-9177" height="422" src="https://blog.mozilla.org/addons/files/2024/05/Screenshot-from-2024-05-15-12-35-36-580x930.png" width="279" />             <img alt="" class="alignnone wp-image-9176" height="449" src="https://blog.mozilla.org/addons/files/2024/05/Screenshot-from-2024-05-15-11-50-56-580x930.png" width="280" /></p>
1297. <p>We also wanted to take this opportunity to address a couple common questions we’ve been seeing in the community, specifically around the webRequest API and MV2:</p>
1298. <ol>
1299. <li>The webRequest API is not on a deprecation path in Firefox</li>
1300. <li>Mozilla has no current plans to deprecate MV2 as mentioned in our <a href="https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/">previous MV3 update</a></li>
1301. </ol>
1302. <p>For more information on adopting MV3, please see our <a href="https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/">migration guide</a>. Another great resource is the FOSDEM presentation a couple Mozilla engineers delivered recently, <a href="https://fosdem.org/2024/schedule/event/fosdem-2024-2412-firefox-android-and-cross-browser-webextensions-in-2024/">Firefox, Android, and Cross-browser WebExtensions in 2024</a>.</p>
1303. <p>If you have questions or feedback on our Manifest V3 plans we would love to hear from you in the comments section below or if you prefer, drop us an <a href="mailto:mozilla-add-ons-community@mozilla.com">email</a>.</p>
1304. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/addons/2024/05/14/manifest-v3-updates/&quot;&gt;Manifest V3 Updates&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>
1305. <pubDate>Tue, 14 May 2024 22:41:23 +0000</pubDate>
1306. <dc:creator>Edward Sullivan</dc:creator>
1307. </item>
1308. <item>
1309. <title>The Mozilla Blog: Firefox at the Webbys: Winners talk internet red flags and what they’d rather keep private online</title>
1310. <guid isPermaLink="false">https://blog.mozilla.org/?p=74797</guid>
1311. <link>https://blog.mozilla.org/en/internet-culture/webbys-red-carpet-event-2024/</link>
1312. <description>&lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;A big screen reads: 28th Annual Webby Awards&quot; class=&quot;wp-image-74862&quot; height=&quot;682&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/2152826293-1024x682.jpg&quot; width=&quot;1024&quot; /&gt;&amp;lt;figcaption class=&quot;wp-element-caption&quot;&amp;gt;Credit: Getty Images for the Webby Awards&amp;lt;/figcaption&amp;gt;&lt;/figure&gt;
1313.  
1314.  
1315.  
1316. <p>The Firefox team hit the red carpet Monday at this year’s 28th annual Webby Awards with some of the internet’s most influential figures and their groundbreaking projects. But we weren’t just there to watch the honorees accept their trophies. We wanted the inside scoop on how they win the web game every day. </p>
1317.  
1318.  
1319.  
1320. <p>So, we asked them about internet red flags and even threw down a challenge called “Unload or <a href="https://blog.mozilla.org/en/mozilla/firefoxs-private-browsing-mode-upleveled-for-you/">Private Mode</a>,” where they had a choice: spill the beans or take a “Firefox shot” to <a href="https://blog.mozilla.org/en/mozilla/mozilla-vpn-update-new-privacy-features-plus-independent-security-audit-results/">keep it private</a>. Check out the video below to see how Webby winners like Madison Tevlin, Abi Marquez, James and Oliver Phelps, Michelle Buteau and more responded:</p>
1321.  
1322.  
1323.  
1324. <blockquote class="instagram-media"><div style="padding: 16px;"> <a href="https://www.instagram.com/reel/C69TUqFgTxk/?utm_source=ig_embed&utm_campaign=loading" rel="noopener" style="line-height: 0; padding: 0 0; text-align: center; text-decoration: none; width: 100%;" target="_blank"> <div style="display: flex;"> <div style="background-color: #F4F4F4; border-radius: 50%; height: 40px; margin-right: 14px; width: 40px;"></div> <div style="display: flex;"> <div style="background-color: #F4F4F4; border-radius: 4px; height: 14px; margin-bottom: 6px; width: 100px;"></div> <div style="background-color: #F4F4F4; border-radius: 4px; height: 14px; width: 60px;"></div></div></div><div style="padding: 19% 0;"></div> <div style="display: block; height: 50px; margin: 0 auto 12px; width: 50px;"></div><div style="padding-top: 8px;"> <div style="color: #3897f0; font-family: Arial,sans-serif; font-size: 14px; font-style: normal; font-weight: 550; line-height: 18px;">View this post on Instagram</div></div><div style="padding: 12.5% 0;"></div> <div style="display: flex; margin-bottom: 14px;"><div> <div></div> <div></div> <div></div></div><div style="margin-left: 8px;"> <div style="background-color: #F4F4F4; border-radius: 50%; height: 20px; width: 20px;"></div> <div></div></div><div style="margin-left: auto;"> <div></div> <div></div> <div></div></div></div> <div style="display: flex; margin-bottom: 24px;"> <div style="background-color: #F4F4F4; border-radius: 4px; height: 14px; margin-bottom: 6px; width: 224px;"></div> <div style="background-color: #F4F4F4; border-radius: 4px; height: 14px; width: 144px;"></div></div></a><p style="color: #c9c8cd; font-family: Arial,sans-serif; font-size: 14px; line-height: 17px; margin-bottom: 0; margin-top: 8px; overflow: hidden; padding: 8px 0 7px; text-align: center; white-space: nowrap;"><a href="https://www.instagram.com/reel/C69TUqFgTxk/?utm_source=ig_embed&utm_campaign=loading" rel="noopener" style="color: #c9c8cd; font-family: Arial,sans-serif; font-size: 14px; font-style: normal; font-weight: normal; line-height: 17px; text-decoration: none;" target="_blank">A post shared by Firefox (@firefox)</a></p></div></blockquote>
1325.  
1326.  
1327.  
1328. <p>The Webbys are hosted each year by the International Academy of Digital Arts and Sciences — a group of over 3,000 tech experts, industry leaders, and creative minds. Each category honors two achievements: The Webby Award, chosen by the Academy, and The Webby People’s Voice Award, which is voted on by the global internet community. It’s possible for nominees to win one or both. </p>
1329.  
1330.  
1331.  
1332. <p>Monday’s ceremony featured notable guests like Keke Palmer, Coco Rocha, Ina Garten, Julia Louis-Dreyfus and Laverne Cox, as well as tech journalist Kara Swisher, who was honored with the Webby Lifetime Achievement Award. </p>
1333.  
1334.  
1335.  
1336. <figure class="wp-block-image size-large"><img alt="Kara Swisher accepts an award on stage." class="wp-image-74852" height="682" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/2152825501-1024x682.jpg" width="1024" /><figcaption class="wp-element-caption">Kara Swisher accepts her Webby Lifetime Achievement Award. Credit: Getty Images for the Webby Awards</figcaption></figure>
1337.  
1338.  
1339.  
1340. <p>The Webbys have evolved with the internet since the award’s inception in 1996, adding to its roster of acknowledgments like Podcasts; Games and AI, Metaverse & Virtual; and more. And just as the web is a critical tool for every area of life today, the Webby Awards remains an important and relevant award honoring achievement in interactive media.</p>
1341.  
1342.  
1343.  
1344. <p>A hallmark feature is the ceremony’s <a href="https://www.youtube.com/watch?v=JLyvGn9T4Us&list=PLWeKJ75kFs5S1X-NzWXhx6z9fU7HzArLf" rel="noreferrer noopener" target="_blank">five-word acceptance speech limit</a>, which has produced some memorable moments from the likes of David Bowie and Prince over the years. Monday night’s speeches didn’t disappoint. Here are some of our favorite speeches: </p>
1345.  
1346.  
1347.  
1348. <ul>
1349. <li>“Cooking Show Pretend, Gratitude Real.” –<strong> Jennifer Garner</strong></li>
1350.  
1351.  
1352.  
1353. <li>“Don’t put twinkies on pizza.” – <strong>Josh Scherer</strong></li>
1354.  
1355.  
1356.  
1357. <li>“Actually, we are all one degree.” – <strong>Kevin Bacon</strong></li>
1358.  
1359.  
1360.  
1361. <li>“I ain’t done, tech bros.”<strong> </strong>–<strong> Kara Swisher  </strong></li>
1362.  
1363.  
1364.  
1365. <li>“I’m blessed to do this.” – <strong>Keke Palmer</strong></li>
1366.  
1367.  
1368.  
1369. <li>“Risk everything every time.” – <strong>Jerrod Carmichael</strong></li>
1370.  
1371.  
1372.  
1373. <li> “It’s fun proving people wrong.” –<strong> Madison Tevlin</strong></li>
1374.  
1375.  
1376.  
1377. <li>“Healing, collective trauma, necessary, possible.” –<strong> Laverne Cox</strong></li>
1378. </ul>
1379.  
1380.  
1381.  
1382. <p>Check out some other highlights:</p>
1383.  
1384.  
1385.  
1386. <figure class="wp-block-image size-large"><img alt="Keke Palmer accepts an award on stage." class="wp-image-74842" height="682" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/2152817821-1024x682.jpg" width="1024" /><figcaption class="wp-element-caption">Keke Palmer accepts the Webby Award for Special Achievement. Credit: Getty Images for the Webby Awards</figcaption></figure>
1387.  
1388.  
1389.  
1390. <figure class="wp-block-image size-large"><img alt="Julia Louis-Dreyfus accepts an award on stage." class="wp-image-74832" height="682" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/2152819238-1024x682.jpg" width="1024" /><figcaption class="wp-element-caption">Julia Louis-Dreyfus accepts the Webby Podcast of the Year Award. Credit: Getty Images for the Webby Awards</figcaption></figure>
1391.  
1392.  
1393.  
1394. <figure class="wp-block-image size-large"><img alt="Shannon Sharpe accepts an award on stage." class="wp-image-74812" height="683" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/2152816708-1024x683.jpg" width="1024" /><figcaption class="wp-element-caption">Shannon Sharpe accepts his Webby Advocate of the Year Award. Credit: Getty Images for the Webby Awards</figcaption></figure>
1395.  
1396.  
1397.  
1398. <figure class="wp-block-image size-large"><img alt="" class="wp-image-74822" height="683" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/2152817644-1024x683.jpg" width="1024" /><figcaption class="wp-element-caption">Creator Abi Marquez accepts her Webby Award. Credit: Getty Images for the Webby Awards</figcaption></figure>
1399.  
1400.  
1401.  
1402. <p>See all the best moments from last night’s show on social media by searching #Webbys and at<a href="http://webbyawards.com" rel="noreferrer noopener" target="_blank"> webbyawards.com</a>. For the full list of Webby Award winners, visit <a href="https://winners.webbyawards.com/winners" rel="noreferrer noopener" target="_blank">winners.webbyawards.com/winners</a>. </p>
1403.  
1404.  
1405.  
1406. <p>That’s a wrap on our Webby Awards coverage! Keep hanging with us and we’ll help you navigate the web safely and freely, having a little fun along the way. </p>
1407.  
1408.  
1409.  
1410. <a class="ft-c-inline-cta" href="https://www.mozilla.org/en-US/firefox/new?utm_medium=mozilla-websites&utm_source=blog.mozilla.org&utm_content=inline-cta">
1411.  <div class="ft-c-inline-cta__media">
1412.  <img alt="" class="attachment-1x1 size-1x1" height="512" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2020/12/Fx-Browser-icon-fullColor-512-512x512.png" width="512" />  </div>
1413.  <div class="ft-c-inline-cta__content">
1414.     <h3>Get Firefox</h3>      <span>Get the browser that protects what’s important</span>   </div>
1415. </a>
1416. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/internet-culture/webbys-red-carpet-event-2024/&quot;&gt;Firefox at the Webbys: Winners talk internet red flags and what they’d rather keep private online&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>
1417. <pubDate>Tue, 14 May 2024 18:53:34 +0000</pubDate>
1418. <dc:creator>Damiano</dc:creator>
1419. </item>
1420. <item>
1421. <title>Firefox Developer Experience: Firefox WebDriver Newsletter — 126</title>
1422. <guid isPermaLink="false">https://fxdx.dev/?p=283</guid>
1423. <link>https://fxdx.dev/firefox-webdriver-newsletter-126/</link>
1424. <description>&lt;p&gt;&lt;em&gt;WebDriver is a remote control interface that enables introspection and control of user agents. 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;a href=&quot;https://www.w3.org/&quot;&gt;W3C&lt;/a&gt; and consists of two separate specifications: &lt;a href=&quot;https://w3c.github.io/webdriver/&quot;&gt;WebDriver classic&lt;/a&gt; (HTTP) and the new &lt;a href=&quot;https://w3c.github.io/webdriver-bidi/&quot;&gt;WebDriver BiDi &lt;/a&gt;(Bi-Directional).&lt;/em&gt;&lt;/p&gt;
1425.  
1426.  
1427.  
1428. <p id="block-657c8643-6b93-4546-8626-3d7c3976c217"><em>This newsletter gives an overview of the work we’ve done as part of the Firefox 125 release cycle</em>.</p>
1429.  
1430.  
1431.  
1432. <h3>Contributions</h3>
1433.  
1434.  
1435.  
1436. <p id="block-9278fa20-63dc-4975-a72b-e3ba73b202a4">With Firefox being an open source project, we are grateful to get contributions from people outside of Mozilla:</p>
1437.  
1438.  
1439.  
1440. <ul>
1441. <li>Gravyant <a href="https://bugzil.la/1838152">improved the error message for the <code>session.new</code> command</a> when no capabilities are specified.</li>
1442. </ul>
1443.  
1444.  
1445.  
1446. <p id="block-f6e2b9b0-63b6-4a4b-aeea-cffbde1019dd">WebDriver code is written in JavaScript, Python, and Rust so any web developer can contribute! Read <a href="https://firefox-source-docs.mozilla.org/devtools/getting-started/README.html">how to setup the work environment</a> and check <a href="https://codetribute.mozilla.org/projects/automation">the list of mentored issues</a> for Marionette.</p>
1447.  
1448.  
1449.  
1450. <h3>WebDriver BiDi</h3>
1451.  
1452.  
1453.  
1454. <h4><a href="https://fxdx.dev/feed/">New: Support for the “contexts” argument for the “network.addIntercept” command</a></h4>
1455.  
1456.  
1457.  
1458. <p>Since the introduction of the <code>network.addIntercept</code> command in Firefox 124, users could only apply network interceptions globally, affecting all open web pages across various tabs and windows. This necessitated the setup of specific filters to limit the impact to tabs requiring interception. However, this approach adversely affected performance, particularly when client code didn’t run locally, leading to increased data transmission over the network.</p>
1459.  
1460.  
1461.  
1462. <p>To address these issues and simplify the use of network interception for specific tabs, we’ve <a href="https://bugzil.la/1882260">added the <code>context</code>s argument in the <code>network.addIntercept</code> command</a>. This enhancement facilitates the targeting of specific top-level browsing contexts, enabling the restriction of network request interception to individual tabs even with the same web page open in multiple tabs.</p>
1463.  
1464.  
1465.  
1466. <h4>Bug fixes</h4>
1467.  
1468.  
1469.  
1470. <ul>
1471. <li>Both the commands <a href="https://bugzil.la/1887871"><code>session.subscribe</code> and <code>session.unsubscribe</code> now raise an <code>invalid argument</code></a> error when the value of the arguments <code>events</code> or <code>contexts</code> are empty arrays.</li>
1472.  
1473.  
1474.  
1475. <li>Updated the implementation of <a href="https://bugzil.la/1879503">the <code>storage.getCookies</code> command to align with the Gecko default cookie behavior</a>. This allows the removal of the user value for the preference <code>network.cookie.cookieBehavior</code>, which was only expected to be set for our experimental CDP implementation. </li>
1476.  
1477.  
1478.  
1479. <li><a href="https://bugzil.la/1838152">Removed the <code>ownership</code> and <code>sandbox</code> arguments for the <code>browsingContext.locateNodes</code></a> command because they are no longer necessary. </li>
1480. &lt;/ul&gt;</description>
1481. <pubDate>Tue, 14 May 2024 14:46:05 +0000</pubDate>
1482. <dc:creator>Henrik Skupin</dc:creator>
1483. </item>
1484. <item>
1485. <title>The Mozilla Blog: See what’s changing in Firefox: Better insights, same privacy</title>
1486. <guid isPermaLink="false">https://blog.mozilla.org/?p=74713</guid>
1487. <link>https://blog.mozilla.org/en/products/firefox/firefox-search-update/</link>
1488. <description>&lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;An illustration shows the Firefox logo, a fox curled up in a circle.&quot; class=&quot;wp-image-53149&quot; height=&quot;538&quot; src=&quot;https://blog.mozilla.org/wp-content/blogs.dir/278/files/2020/01/firefox-browser-logo-1024x538.png&quot; width=&quot;1024&quot; /&gt;&lt;/figure&gt;
1489.  
1490.  
1491.  
1492. <p>Innovation and privacy go hand in hand here at Mozilla. To continue developing features and products that resonate with our users, we’re adopting a new approach to better understand how you engage with Firefox. Rest assured, the way we gather these insights will always put user <a href="https://www.mozilla.org/en-US/privacy/firefox/" rel="noreferrer noopener" target="_blank">privacy first</a>.</p>
1493.  
1494.  
1495.  
1496. <h3><strong>What’s new in Firefox’s approach to search data </strong></h3>
1497.  
1498.  
1499.  
1500. <p>To improve Firefox based on your needs, understanding how users interact with essential functions like search is key. We’re ramping up our efforts to enhance search experience by developing new features like <a href="https://blog.mozilla.org/products/firefox/firefox-news/firefox-suggest/">Firefox Suggest</a>, which provides recommended online content that corresponds to queries. To make sure that features like this work well, we need better insights on overall search activity – all without trading off on our commitment to user privacy. Our goal is to understand what types of searches are happening so that we can prioritize the correct features by use case.</p>
1501.  
1502.  
1503.  
1504. <p>With the <a href="https://www.mozilla.org/en-US/firefox/126.0/releasenotes/" rel="noreferrer noopener" target="_blank">latest version of Firefox</a> for U.S. desktop users, we’re introducing a new way to measure search activity broken down into high level categories. This measure is not linked with specific individuals and is further anonymized using a technology called <a href="https://blog.mozilla.org/products/firefox/partnership-ohttp-prio/">OHTTP</a> to ensure it can’t be connected with user <a href="https://blog.mozilla.org/internet-culture/what-is-an-ip-address/">IP addresses</a>.    <br /><br />Let’s say you’re using Firefox to <a href="https://blog.mozilla.org/products/firefox/firefox-tips/internet-safety-for-families-total-cookie-protection/">plan a trip</a> to Spain and search for “Barcelona hotels.” Firefox infers that the search results fall under the category of “travel,” and it increments a counter to calculate the total number of searches happening at the country level.<br /><br />Here’s the current list of categories we’re using: animals, arts, autos, business, career, education, fashion, finance, food, government, health, hobbies, home, inconclusive, news, real estate, society, sports, tech and travel.</p>
1505.  
1506.  
1507.  
1508. <p>Having an understanding of what types of searches happen most frequently will give us a better understanding of what’s important to our users, without giving us additional insight into individual browsing preferences. This helps us take a step forward in providing a browsing experience that is more tailored to your needs, without us stepping away from the principles that make us who we are. </p>
1509.  
1510.  
1511.  
1512. <h3><strong>What Firefox’s search data collection means for you</strong></h3>
1513.  
1514.  
1515.  
1516. <p>We understand that any new data collection might spark some questions. Simply put, this new method only categorizes the websites that show up in your searches — not the specifics of what you’re personally looking up. </p>
1517.  
1518.  
1519.  
1520. <p>Sensitive topics, like searching for particular health care services, are categorized only under broad terms like health or society. Your search activities are handled with the same level of confidentiality as all other data regardless of any local laws surrounding certain health services. </p>
1521.  
1522.  
1523.  
1524. <p>Remember, you can always opt out of sending any technical or usage data to Firefox. <a href="https://support.mozilla.org/en-US/kb/share-data-mozilla-help-improve-firefox" rel="noreferrer noopener" target="_blank">Here’s a step-by-step guide</a> on how to adjust your settings. We also don’t collect category data when you use <a href="https://blog.mozilla.org/mozilla/firefoxs-private-browsing-mode-upleveled-for-you/">Private Browsing mode</a> on Firefox.  </p>
1525.  
1526.  
1527.  
1528. <p>As far as user experience goes, you won’t see any visible changes in your browsing. Our new approach to data will just enable us to better refine our product features and offerings in ways that matter to you. </p>
1529.  
1530.  
1531.  
1532. <p>We’re here to make the internet safer, faster and more in tune with what you need – just as we have since open-sourcing our browser code more than <a href="https://blog.mozilla.org/mozilla/mitchell-baker-mozilla-25-anniversary/">25 years ago</a>. Thanks for being part of our journey!</p>
1533.  
1534.  
1535.  
1536. <a class="ft-c-inline-cta" href="https://www.mozilla.org/en-US/firefox/new?utm_medium=mozilla-websites&utm_source=blog.mozilla.org&utm_content=inline-cta">
1537.  <div class="ft-c-inline-cta__media">
1538.  <img alt="" class="attachment-1x1 size-1x1" height="512" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2020/12/Fx-Browser-icon-fullColor-512-512x512.png" width="512" />  </div>
1539.  <div class="ft-c-inline-cta__content">
1540.     <h4>Get Firefox</h4>      <span>Get the browser that protects what’s important</span>   </div>
1541. </a>
1542. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/products/firefox/firefox-search-update/&quot;&gt;See what’s changing in Firefox: Better insights, same privacy&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>
1543. <pubDate>Tue, 14 May 2024 13:00:00 +0000</pubDate>
1544. <dc:creator>Mozilla</dc:creator>
1545. </item>
1546. <item>
1547. <title>The Mozilla Blog: Raphael Mimoun on creating tech for human rights and justice, combatting misinformation and building a privacy-centric culture</title>
1548. <guid isPermaLink="false">https://blog.mozilla.org/?p=74738</guid>
1549. <link>https://blog.mozilla.org/en/internet-culture/raphael-mimoun-mozilla-rise-25-human-rights-justice-journalists/</link>
1550. <description>&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;
1551.  
1552. </div></figure>
1553.  
1554.  
1555.  
1556. <p><em>At Mozilla, we know we can’t create a better future alone, that is why each year we will be highlighting the work of 25 digital leaders using technology to amplify voices, effect change, and build new technologies globally through our <a href="https://rise25.mozilla.org/?_gl=1*585km0*_ga*MTY1MDQ4MTg2NC4xNjk5NDc0NTE5*_ga_X4N05QV93S*MTcwNzE4MDk3Ny40NC4wLjE3MDcxODA5NzcuMC4wLjA." rel="noreferrer noopener" target="_blank">Rise 25 Awards.</a> These storytellers, innovators, activists, advocates. builders and artists are helping make the internet more diverse, ethical, responsible and inclusive.</em></p>
1557.  
1558.  
1559.  
1560. <p><em>This week, we chatted with Raphael Mimoun, a builder dedicated to making tools that empower journalists and human rights defenders. We talk with Raphael about the launch of his app, Tella, combatting misinformation online, the future of social media platforms and more.</em></p>
1561.  
1562.  
1563.  
1564. <p><strong>How did the work you did early on in human rights after you completed university help you understand the power of technology and ultimately inspire you to do a lot of the work that you do right now?</strong></p>
1565.  
1566.  
1567.  
1568. <p>Raphael Mimoun: So I never worked in tech per se and only developed a passion for technology as I was working in human rights. It was really a time when, basically, the power of technology to support movements and to head movements around the world was kind of getting fully understood. You had the Arab Spring, you had Occupy Wall Street, you had all of these movements for social justice, for democracy, for human rights, that were very much kind of spread through technology, right? Technology played a very, very important role. But just after that, it was kind of like a hangover where we all realized, “OK, it’s not just all good and fine.” You also have the flip side, which is government spying on the citizens, identifying citizens through social media, through hacking, and so on and so forth — harassing them, repressing them online, but translating into offline violence, repression, and so on. And so I think that was the moment where I was like, “OK, there is something that needs to be done around technology,” specifically for those people who are on the front lines because if we just treat it as a tool — one of those neutral tools — we end up getting very vulnerable to violence, and it can be from the state, it can also be from online mobs, armed groups, all sort of things. So that was really the point when I was like, “OK, let’s try and tackle technology as its own thing.” Not just thinking of it as a neutral tool that can help or not.</p>
1569.  
1570.  
1571.  
1572. <p><strong>There’s so much misinformation out there now that it’s so much harder to tell the difference between what’s real and fake news. Twitter was such a reliable tool of information before, but that’s changed. Do you think that any of these other platforms can be able to help make up for so much of the misinformation that is out there?</strong></p>
1573.  
1574.  
1575.  
1576. <p>I think we all feel the weight of that loss of losing Twitter. Twitter was always a large corporation, partially owned by a billionaire. It was never kind of a community tool, but there was still an ethos, right? Like a philosophy, or the values of the platform were still very much like community-oriented, right? It was that place for activists and human rights defenders and journalists and communities in general to voice their opinions. So I think that loss was very hard on all of us.</p>
1577.  
1578.  
1579.  
1580. <p>I see a lot of misinformation on Instagram as well. There is very little moderation there. It’s also all visual, so if you want traction, you’re going to try to put something that is very spectacular that is very eye catchy, and so I think that leads to even more misinformation.</p>
1581.  
1582.  
1583.  
1584. <p>I am pretty optimistic about some of the alternatives that have popped up since Twitter’s downfall. Mastodon actually blew up after Twitter, but it’s much older — I think it’s 10 years old by now. And there’s Bluesky. So I think those two are building up, and they offer spaces that are much more decentralized with much more autonomy and agency to users. You are more likely to be able to customize your feeds. You are more likely to have tools for your own safety online, right? All of those different things that I feel like you could never get on Threads, on Instagram or on Twitter, or anything like that. I’m hoping it’s actually going to be able to recreate the community that is very much what Twitter was. It’s never going to be exactly the same thing, but I’m hoping we will get there. And I think the fact that it is decentralized, open source and with very much a philosophy of agency and autonomy is going to lead us to a place where these social networks can’t actually be taken over by a power hungry billionaire.</p>
1585.  
1586.  
1587.  
1588. <p><strong>What do you think is the biggest challenge that we face in the world this year on and offline, and then how do you think we can combat it?</strong></p>
1589.  
1590.  
1591.  
1592. <p>I don’t know if that’s the biggest challenge, but one of the really big challenges that we’re seeing is how the digital is meeting real life and how people who are active online or on the phone on the computer are getting repressed for that work in real life. So we developed an app called Tella, which encrypts and hides files on your phone, right? So you take a photo or a video of a demonstration or police violence, or whatever it is, and then if the police tries to catch you and grab your phone to delete it, they won’t be able to find it, or at least it will be much more difficult to find it. Or it would be uploaded already. And things like that, I think is one of the big things that we’re seeing again. I don’t know if that the biggest challenge online at the moment, but one of the big things we’re seeing is just that it’s becoming completely normalized to grab someone’s phone or check someone’s computer at the airport, or at the border, in the street and go through it without any form of accountability. People have no idea what the regulations are, what the rules are, what’s allowed, what’s not allowed. And when they abuse those powers, is there any recourse? Most places in the world, at least, where we are working, there is definitely no recourse. And so I think that connection between thinking you’re just taking a photo for social media but actually the repercussion is so real because you’re going to have someone take your phone, and maybe they’re going to delete the photo, or maybe they’re going to detain you. Or maybe they’re going to beat you up — like all of those different things. I think this is one of the big challenges that we’re seeing at the moment, and something that isn’t traditionally thought of as an internet issue or an online digital rights issue because it’s someone taking a physical device and looking through it. It often gets overlooked, and then we don’t have much kind of advocacy around it, or anything like that.</p>
1593.  
1594.  
1595. <div class="wp-block-image">
1596. <figure class="aligncenter size-large"><img alt="" class="wp-image-74749" height="1024" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/Mozilla_rise25_Raphael-Mimoun_1-683x1024.jpg" width="683" /><figcaption class="wp-element-caption">Raphael Mimoun at Mozilla’s Rise25 award ceremony in October 2023.</figcaption></figure></div>
1597.  
1598.  
1599. <p><strong>How is this issue overseas compared to America?</strong></p>
1600.  
1601.  
1602.  
1603. <p>It really depends on where in each country, but many places where we work, we work with human rights defenders who on the front lines, and journalists who are on the front lines in places that are very repressive. So there is no form of accountability whatsoever. They can take your phone again. It depends on where, but they can take your phone, put it into the trash, and you’ll never see it again. And you have no recourse whatsoever. It’s not like you can go to the police because they laugh at you and say, “What the hell are you doing here?” </p>
1604.  
1605.  
1606.  
1607. <p><strong>What do you think is one action everybody can take to make the world and our lives online a little bit better?</strong><br /><br />I think social media has a lot of negative consequences for everyone’s mental health and many other things, but for people who are active and who want to be active, consider social networks that are open source, privacy-friendly and decentralized. Bluesky, the Fediverse —including Mastodon — are examples because I think it’s our responsibility to kind of build up a community there, so we can move away from those social media platforms that are owned by either billionaires or massive corporations, who only want to extract value from us and who spy on us and who censor us. And I feel like if everyone committed to being active on those social media platforms — one way of doing that is just having an account, and whatever you post on one, you just post on the other — I feel like that’s one thing that can make a big difference in the long run.</p>
1608.  
1609.  
1610.  
1611. <p><strong>We started Rise25 to celebrate Mozilla’s 25th anniversary. What do you hope that people are celebrating in the next 25 years?</strong></p>
1612.  
1613.  
1614.  
1615. <p>I was talking a little bit earlier about how we are building a culture that is more privacy-centric, like people are becoming aware, becoming wary about all these things happening to the data, the identity, and so on. And I do think we are at a turning point in terms of the technology that’s available to us, the practices and what we need as users to maintain our privacy and our security.  I feel like in honestly not even 25, I think in 10 years, if things go well — which it’s hard to know in this field — and if we keep on building what we already are building, I can see how we will have an internet that is a lot more privacy-centric where communications are by default are private. Where end-to-end encryption is ubiquitous in our communication, in our emailing. Where social media isn’t extractive and people have actual ownership and agency in the social network networks they use. Where data mining is no longer a thing. I feel like overall, I can see how the infrastructure is now getting built, and that in 10,15 or 25 years, we will be in a place where we can use the internet without having to constantly watch over our shoulder to see if someone is spying on us or seeing who has access and all of those things.</p>
1616.  
1617.  
1618.  
1619. <p><strong>Lastly, what gives you hope about the future of our world?</strong></p>
1620.  
1621.  
1622.  
1623. <p>That people are not getting complacent and that it is always people who are standing up to fight back. We’re seeing it at. We saw it at Google with people standing up as part of <a href="https://www.notechforapartheid.com/">No Tech for Apartheid coalition</a> and people losing the jobs. We’re seeing it on university campuses around the country. We’re seeing it on the streets. People fight back. That’s where any change has ever come from: the bottom up. I think now, more than ever, people are willing to put something on the line to make sure that they defend their rights. So I think that really gives me hope.</p>
1624.  
1625.  
1626.  
1627. <a class="ft-c-inline-cta" href="https://www.mozilla.org/en-US/firefox/new?utm_medium=mozilla-websites&utm_source=blog.mozilla.org&utm_content=inline-cta">
1628.  <div class="ft-c-inline-cta__media">
1629.  <img alt="" class="attachment-1x1 size-1x1" height="512" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2020/12/Fx-Browser-icon-fullColor-512-512x512.png" width="512" />  </div>
1630.  <div class="ft-c-inline-cta__content">
1631.     <h3>Get Firefox</h3>      <span>Get the browser that protects what’s important</span>   </div>
1632. </a>
1633. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/internet-culture/raphael-mimoun-mozilla-rise-25-human-rights-justice-journalists/&quot;&gt;Raphael Mimoun on creating tech for human rights and justice, combatting misinformation and building a privacy-centric culture&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>
1634. <pubDate>Mon, 13 May 2024 15:00:00 +0000</pubDate>
1635. <dc:creator>Aron Yohannes</dc:creator>
1636. </item>
1637. <item>
1638. <title>The Mozilla Blog: Keoni Mahelona on promoting Indigenous communities, the evolution of the Fediverse and data protection</title>
1639. <guid isPermaLink="false">https://blog.mozilla.org/?p=74716</guid>
1640. <link>https://blog.mozilla.org/en/internet-culture/keoni-mahelona-mozilla-rise-25-data-protection/</link>
1641. <description>&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;
1642.  
1643. </div></figure>
1644.  
1645.  
1646.  
1647. <p><em>At Mozilla, we know we can’t create a better future alone, that is why each year we will be highlighting the work of 25 digital leaders using technology to amplify voices, effect change, and build new technologies globally through our <a href="https://rise25.mozilla.org/?_gl=1*585km0*_ga*MTY1MDQ4MTg2NC4xNjk5NDc0NTE5*_ga_X4N05QV93S*MTcwNzE4MDk3Ny40NC4wLjE3MDcxODA5NzcuMC4wLjA." rel="noreferrer noopener" target="_blank">Rise 25 Awards.</a> These storytellers, innovators, activists, advocates, builders and artists are helping make the internet more diverse, ethical, responsible and inclusive.</em></p>
1648.  
1649.  
1650.  
1651. <p><em>This week, we chatted with Keoni Mahelona, a builder behind technologies that aim to protect and promote Indigenous languages and knowledge. We talked with Keoni about his current work at Te Hiku Media, the challenges of preserving Indigenous cultures, </em>big tech and more.</p>
1652.  
1653.  
1654.  
1655. <p><strong>So first off, what inspired you to do the work you’re doing now with Te Hiku Media?</strong></p>
1656.  
1657.  
1658.  
1659. <p>Mahelona: I sort of started at the organization cause my partner, who’s the CEO, needed help with doing a website. But then the website turned into an entire digital platform, which then turned into building AI to help us do the work that we have to do, but I guess the most important thing is the alignment of values with like me as a person and as a native Hawaiian with the values of the community up here — Māori community and the organization. Having the strong desire for sovereignty for our land, which has been the struggle we’ve been having now for hundreds of years. We’re still trying to get that back, both in Aotearoa and in Hawaii, but also sovereignty for our languages and our data, and pretty much everything that encompasses us in our communities. And it was really clear that the work that we do at Te Hiku is very important for the community, but also that we needed to maintain sovereignty over that work. And if we made the wrong choices with how we store our data, where we put our data, what platforms we use, then we would cede some of that sovereignty over and take us further back rather than forward.</p>
1660.  
1661.  
1662.  
1663. <p><strong>What were (and are) some of those challenges that you guys had to overcome to be able to create those tools? I feel like a lot of people might not know those challenges and how you have to persevere through those things to create, to preserve.</strong></p>
1664.  
1665.  
1666.  
1667. <p>Sure, the lack of data is a challenge that big tech seem to overcome quite easily with their billions of dollars, whether they’re stealing it at scale or paying people for it at scale. They have the resources to do that and litigate if they need to, because of theft, and they’re just doing what America did right? Stole our land at scale. So for us, actually, we knew that the data would be the hardest part, but not so much like getting the data, or whether the data existed — there’s a vibrant community of language speakers here — the hard part was going to be, how do we protect the data that we collect? And even now, I worry because there’s just so many bots online scraping stuff, and we see bots trying to sort of log into our online forms. And I’m thinking hopefully these are just bots trying to log into a form because it sees the form, versus someone who knows that we’ve got some valuable data here, and if they can get in, they could use that data to add Māori to their models and profit off of that. When you have organizations like Microsoft and Google making hundreds of millions off of selling services to education and government in this country, you know that would be a valuable corpus for them — I’m not saying that they would sort of steal, I don’t know, I’d hope not, but I feel like OpenAI would probably do something like that.</p>
1668.  
1669.  
1670.  
1671. <p>And how do we overcome that? We just tried. We did the best we could do, given the resources we had to ensure that things are safe, and we think they’re relatively safe, although I still get anxiety about it. Some of the other challenges we face are being a bunch of brown people from a community, so there’s the stereotype associated with the area with anyone who might maybe sort of associates to this place. So there were people like, “Ha, you guys can’t do this.” And we proved them wrong. They were even funders who were Māori, who actually thought, “These guys are crazy, but you know what, this is exactly what we need to find. We need to find like people who are crazy and who might actually pull this off because it would be quite beneficial.” </p>
1672.  
1673.  
1674.  
1675. <p>We’ve had other people inquire as to why our organization got science funding to do science research. I actually have a master’s in science — I actually have two masters in science, although one’s a business science degree, whatever that means — but there was this quite racist media organization on the south island of this country who did an official Information Act request on our organization, saying, “Why is this Māori media company getting science-based funding? They don’t know anything about science.” We actually had a scientist at our organization, and they didn’t, so this is some of the more interesting challenges that we’ve come across in this journey of going from radio broadcasting and television broadcasting to actually being a tech company and doing science and research. So it’s the racism and the discrimination that we’ve had to overcome as well. In some cases, we think we’ve been denied funding because our organization is Māori, and we’ve had to often do the hard work first off the smell of an oily rag, as they say here, to prove that we are capable of doing the work for people to recognize that, yeah, they can actually fund us. And that we can deliver results based on the stipulations of the fund or whatever when you’re getting science-based funding grants and stuff like that. I think we’ve shown the government that you don’t need to be a large university to actually do good research and have an impact in the science community. But it certainly hasn’t been easy.</p>
1676.  
1677.  
1678. <div class="wp-block-image">
1679. <figure class="aligncenter size-large"><img alt="" class="wp-image-74728" height="1024" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/Mozilla_rise25_Keoni-Mahelona_2-683x1024.jpg" width="683" /><figcaption class="wp-element-caption">Keoni Mahelona at Mozilla’s Rise25 award ceremony in October 2023.</figcaption></figure></div>
1680.  
1681.  
1682. <p><strong>I imagine even with how long you’ve been there and how long you guys have been doing this, that there’s still an ongoing feeling of anxiety that’s extremely frustrating.</strong></p>
1683.  
1684.  
1685.  
1686. <p>We’re a nonprofit, so a lot of our money comes from government funding, and we’re also a broadcaster, so we have public broadcasting funding that fades some of the work we do and then you science-based funding. </p>
1687.  
1688.  
1689.  
1690. <p>The New Zealand political environment right now is absolutely terrible. There have been hundreds, probably thousands, of job cuts in the government. The current coalition government needs to raise something like three billion dollars for tax cuts for landlords, and in order to do that, they’re just slashing a lot of funding and projects and people’s jobs in government. There’s this rhetoric that’s been peddled that the government is quite inefficient, and we’re just hemorrhaging money and all these stupid positions and things like that. So that also gives us an anxiety, because a changing government might affect funding that is available to our organization. So we also have to deal with that as being a charity and not sort of being a capitalist organization.</p>
1691.  
1692.  
1693.  
1694. <p>The other thing that gives us anxiety is the inevitable, right? I actually think it’s inevitable, unfortunately, that these big tech companies will eventually be able to sort of replicate our languages. They won’t be good. They’ll never be good and good to the point where it will truly benefit and move our people forward. But they will be good enough that they will be able to profit from it. It profits by giving it that reputation of providing that service, ensuring you continue to go to Google, where you’re then served ads, and so they’re not selling the translation, but they are selling ads alongside it for profit, right? We see this essentially happening with a lot of Indigenous languages, where there is enough data being put online that these mostly American big tech corporations will profit from. And the sad thing is that it was the Americans in the first place and these other colonial nations that fought to make our languages extinct. And now their corporations stand to profit from the languages that they tried to make extinct. So it’s really terrible.</p>
1695.  
1696.  
1697.  
1698. <p><strong>How do you think some of these bigger corporations can be more respectful, inclusive, and supportive of Indigenous communities?</strong></p>
1699.  
1700.  
1701.  
1702. <p>That’s an interesting question. I guess the first question is, should they be inclusive? Because sometimes the best thing to do is just stay away and let us get on with it. We don’t need your help. The unfortunate reality is that so many of our people are on Facebook and are on Google, or whatever — the platforms are so dominating or imperialist that we have to use them in some cases, and because English is the dominant language on these platforms, especially for many Indigenous communities where they are colonized by English-speaking nations, it means that you’re just going to continue to be bombarded with English and not have a space if you don’t go out of your way to make a space and to sort of speak your language. It’s a bit of a catch-22, but I think it’s up to the communities to figure that one out because we could collectively come together as community and be like, “We’re not. We never expect Facebook or whatever to support our language and all these other tech companies and platforms.” And that’s fine, let’s go out into our own environment in our own communities and speak in languages rather than trying to rely on these tech companies to sort of do it for us, right?</p>
1703.  
1704.  
1705.  
1706. <p>There are ways that they can actually just kind of help, but like, stay out of our business.</p>
1707.  
1708.  
1709.  
1710. <p>And that’s the better way to do it, because this sort of outsider coming in trying to save us, it just doesn’t work. I’ve been advocating that you have to support these communities to lead the solutions and what they see is best for their people, because Google doesn’t know what’s best for these communities. So they need to support the communities, and I don’t mean by like building the language technologies themselves and selling it back to them, that is not the support I’m talking about. The support is staying away or giving them discounts on resources or giving them resources so that they can build, and they can lead, because then you’re also upskilling them. </p>
1711.  
1712.  
1713.  
1714. <p><strong>What do you think is the biggest challenge that we face in the world this year on and offline? And how do we combat it? </strong></p>
1715.  
1716.  
1717.  
1718. <p>I see stuff happening to the Fediverse, which is interesting. Something that happened recently was some guy who very much knows and in his blog post identified as a tech bro from Silicon Valley, made the universal decision that the best thing to do for everybody is to hook up Threads and the Fediverse, so that people in Threads can access stuff in Mastodon etc., and then likewise the other way around. And this is like a single dude who apparently had talked to people and decided it was his duty or mission to connect Threads to the Fediverse, and it was just like, are you joking? And then there’s this other thing going on now, where there are these similar types of dudes getting angry at some instances for blocking other instances because they have people who are like racist or misogynist, and they’re getting angry at these moderators who are doing what the point of the Fediverse is, right? Where you can create a safe space and decide who gets to come in and who doesn’t. What I’m getting at is, I think that as the Fediverse kind of grows, it’s going to be interesting to see what sort of problems comes and how the things that we wanted to escape by leaving Twitter and jumping on Mastodon are kind of coming in. And I think that’s going to be interesting to see how we deal with that.</p>
1719.  
1720.  
1721.  
1722. <p>This is again where the incompatibility of capitalism and general communities sort of comes to play because if we have for-profit companies trying to do Fediverse stuff, then essentially, we’re going to get what we already have, because ultimately, at the end of the day you’re trying to maximize for profit. So long as the internet is a place where we have dominating companies trying to maximize for profit, we’re just always going to have more problems, and it’s absolutely terrible and frightening.</p>
1723.  
1724.  
1725.  
1726. <p>But yeah, politics and I think the evolution of the Fediverse are probably the thing that I would be most concerned about. Then there’s also the normal stuff, which is just the theft of data and privacy. </p>
1727.  
1728.  
1729.  
1730. <p><strong>What is one action that you think everybody should take to make the world and our online lives a little bit better?</strong></p>
1731.  
1732.  
1733.  
1734. <p>I think they should just be more cognizant of the data they decide to put online and don’t just think about how that data affects you as an individual, but how does it affect those who are close to you? How does it affect the communities to which you belong? And how does it affect other people who might be similar to you in that way? </p>
1735.  
1736.  
1737.  
1738. <p>People need to be respectful of the data and others data and think about their actions online in respect to being good stewards of all data — their own data from their communities, data of others. And whether you should download this thing or steal that thing or whatever. And that’s essentially what I think is my message, for everyone, is to be respectful, but think about data as you would think about your environment and taking care of it and respecting.</p>
1739.  
1740.  
1741.  
1742. <p><strong>We started Rise25 to celebrate Mozilla’s 25th anniversary. What do you hope that people are celebrating in the next 25 years?</strong></p>
1743.  
1744.  
1745.  
1746. <p>The fall of capitalism, I guess. The restoration of the Hawaiian nation — I can continue. Ultimately, I think a lot of problems come back to some very fundamental ways in which society has structured itself.</p>
1747.  
1748.  
1749.  
1750. <p><strong>What gives you hope about the future of our world?</strong></p>
1751.  
1752.  
1753.  
1754. <p>I think actually this younger generation. I had this impression coming out of high school going to university and then kind of seeing the new generation coming through and being confused having perceptions through your generations. When we live stream high school speeches … just the stuff that these kids talk about is amazing. And even sometimes you’re like having a bit of a cry, because it’s so good in terms of the topics they talk about. But to me, that gives me hope there are actually like some really amazing people and young people who will someday fill our shoes and be politicians. That gives me hope that these people still exist despite all the negative stuff that we see today. That’s what I’m hopeful for.</p>
1755.  
1756.  
1757.  
1758. <a class="ft-c-inline-cta" href="https://www.mozilla.org/en-US/firefox/new?utm_medium=mozilla-websites&utm_source=blog.mozilla.org&utm_content=inline-cta">
1759.  <div class="ft-c-inline-cta__media">
1760.  <img alt="" class="attachment-1x1 size-1x1" height="512" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2020/12/Fx-Browser-icon-fullColor-512-512x512.png" width="512" />  </div>
1761.  <div class="ft-c-inline-cta__content">
1762.     <h3>Get Firefox</h3>      <span>Get the browser that protects what’s important</span>   </div>
1763. </a>
1764. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/internet-culture/keoni-mahelona-mozilla-rise-25-data-protection/&quot;&gt;Keoni Mahelona on promoting Indigenous communities, the evolution of the Fediverse and data protection&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>
1765. <pubDate>Fri, 10 May 2024 20:05:16 +0000</pubDate>
1766. <dc:creator>Aron Yohannes</dc:creator>
1767. </item>
1768. <item>
1769. <title>The Mozilla Blog: How AI is redefining your sports experience right now</title>
1770. <guid isPermaLink="false">https://blog.mozilla.org/?p=74644</guid>
1771. <link>https://blog.mozilla.org/en/mozilla/ai/ai-sports-nfl-draft-nba-mlb-mozilla-innovation/</link>
1772. <description>&lt;p&gt;Artificial intelligence has the potential to transform many sectors across the economy. The sports realm isn’t excluded from that. &lt;/p&gt;
1773.  
1774.  
1775.  
1776. <p>New technologies are already changing the way sports are played, viewed and consumed. From enhancing athlete recovery, to live performance tracking and influencing rule changes, AI’s plunge into sports is providing leagues more data and analysis than they’ve ever had. </p>
1777.  
1778.  
1779.  
1780. <p>Let’s start with football. The NFL has arguably led the way in integrating AI into sports. The league has partnered with Amazon Web Services (AWS) since 2017, and at the beginning of 2024 created the <a href="https://www.nfl.com/playerhealthandsafety/equipment-and-innovation/aws-partnership/building-a-digital-athlete-using-ai-to-rewrite-the-playbook-on-nfl-player-safety">Digital Athlete,</a> a tool using AI and machine learning to “build a complete view of players’ experience, which enables NFL teams to understand precisely what individual players need to stay healthy, recover quickly, and perform at their best.” The technology collects data from multiple sources, including game day data using AWS, and essentially takes video and data from training, practice and in-game action. It then uses AWS technology to “run millions of simulations of NFL games and specific in-game scenarios” to identify which players are at the highest risk of injury. Teams use that information to develop injury prevention, training and recovery regimens. The technology was used by all 32 teams this past NFL season.</p>
1781.  
1782.  
1783.  
1784. <p>AI and the NFL’s relationship goes beyond the Digital Athlete initiative. In March, the league implemented a new<a href="https://operations.nfl.com/updates/football-ops/new-nfl-kickoff-rule/"> kickoff rule</a> after predictive analysis identified plays and body positions that most likely lead to injuries. The process included capturing data through chips in players’ shoulder pads, Brian Rolapp, chief media and business officer for the NFL, recently explained at <a href="https://blog.mozilla.org/en/mozilla/ai/ai-mozilla-the-washington-post-tech-policy/">The Washington Post Futurist Tech Summit</a>, which was sponsored by Mozilla.</p>
1785.  
1786.  
1787.  
1788. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
1789.  
1790. </div></figure>
1791.  
1792.  
1793.  
1794. <p>Consumers get a chance to experience the league’s AI investment, too. During the NFL and Amazon’s “Thursday Night Football” TV broadcasts, viewers have the option to watch games with “Prime Vision,” an alternate broadcast powered by <a href="https://nextgenstats.nfl.com/">Next Gen </a>stats, a real-time player and ball tracking data system. Prime Vision <a href="https://www.aboutamazon.com/news/aws/prime-video-thursday-night-football-next-gen-stats-ai-features">can do fun things</a> like <a href="https://www.youtube.com/watch?v=vYYXKe1tWok">highlight</a> a potential blitzing defender on a play based on what happens before the ball is snapped. </p>
1795.  
1796.  
1797.  
1798. <p>At other levels of football, AI is prevalent for the next generation of players with dreams of making it to the NFL. <a href="https://www.teamexos.com/athlete/">Exos</a>, a sports science-driven performance company based in Arizona, has been employing AI technology for NFL draft hopefuls in the pre-draft training process for years. Several of the top picks in recent years have traveled to Exos’ facility in Phoenix to complete training, shed time off their 40-yard dashes and improve their vertical leaps, among other things. </p>
1799.  
1800.  
1801.  
1802. <p>“When an athlete arrives, we take them through a robust sports science evaluation process,”  said Anthony Hobgood, Exos’ senior director of performance. “This evaluation gives us critical information about the athletes’ force profile, muscle-to-bone ratio and fundamental movement qualities. For example, some athletes will run faster by putting on more muscle, while others’ performance could be negatively impacted by putting on more muscle. The data we collect allows our team to make informed decisions about the game plans we build for our athletes. Our speed coaches have a combined total of over 40 years of experience training over 1,500 NFL draft prospects. When an athlete decides to train at Exos, they can be confident they are getting the best system ever created for NFL draft preparation.”</p>
1803.  
1804.  
1805.  
1806. <p>This training has paid off: From 2015-2023, Exos has produced <a href="https://www.teamexos.com/media/article/31-nfl-teams-draft-exos-athletes/">743 draft picks,</a> an average of 83 per year, including 127 first-rounders. Last spring, almost every NFL team except one (Atlanta) drafted an Exos-trained athlete. </p>
1807.  
1808.  
1809.  
1810. <p>“Our system has been tried and tested for over 25 years and uses data and the latest science in order to ensure our athletes have the very best,” Exos VP of Sport Adam Farrand said.</p>
1811.  
1812.  
1813.  
1814. <p>The NBA has used AI for some time as well. This February, it debuted a generative AI feature at its All-Star tech summit called NB-AI, which aims to enhance and personalize the live game experience for fans. The technology can make game highlights look like an animated superhero movie — think a film based on a certain bug that resides in New York. Here’s how it sketches people: </p>
1815.  
1816.  
1817.  
1818. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
1819.  
1820. </div></figure>
1821.  
1822.  
1823.  
1824. <p>“Today, AI is creating a similar excitement to what we saw around the early days of the internet,” NBA Commissioner Adam Silver <a href="https://apnews.com/article/nba-all-star-2024-weekend-455b62fe0a94db152bb159dd909f21b7">said at the presentation.</a> “Intuitively, most of us have a sense that artificial intelligence is going to change our lives. The question is, ‘How?’” </p>
1825.  
1826.  
1827.  
1828. <p>The WNBA also utilizes similar tech as the NFL’s Digital Athlete, obtaining three-dimensional player and ball-tracking data through its partnership with Genius Sports’ Second Spectrum. WNBA coaches and front office leaders have access to analytical tools, including shot quality, maximum speed and defensive matchup data. </p>
1829.  
1830.  
1831.  
1832. <p>While the world of baseball has long stood behind its history and tradition, it has also stepped into the revolution of AI — in fun and strategic ways. </p>
1833.  
1834.  
1835.  
1836. <p>Baseball has been using data and AI to aid in scouting players, player development, injury risk assessment, video analysis and game strategy. There are even <a href="https://digital.kenyon.edu/cgi/viewcontent.cgi?article=1042&context=dh_iphs_ai">AI chatbots</a> that can create scouting reports for MLB players and evaluate them on metrics AI believes are the best representatives of their abilities. Minor league baseball clubs are embracing <a href="https://www.uplift.ai/">Uplift Labs,</a> which uses mobile movement tracking and 3D analysis tech for scouting players. The system uses mobile devices to “accurately capture athletic movements in any environment, gaining insights into performance optimization.” </p>
1837.  
1838.  
1839.  
1840. <p>In February, the Houston Astros were among the first MLB clubs to introduce facial recognition technology to allow fans into their ballpark. (The New York Mets <a href="https://finance.yahoo.com/news/9-stadiums-already-using-facial-110000157.html">were the first to do this,</a> in 2021.) The San Francisco Giants even <a href="https://blog.purestorage.com/perspectives/how-the-sf-giants-create-a-winning-fan-experience-with-data/?print=pdf">used AI and machine learning</a> to understand what giveaway products they should offer fans for game promos.</p>
1841.  
1842.  
1843.  
1844. <p>AI’s capabilities in the sports world are only expanding as the technology evolves at an extraordinary pace. This shift provides major sports leagues opportunities to continue to improve their product on and off the field, while giving fans an exciting way to experience the games they love.</p>
1845.  
1846.  
1847.  
1848. <p>But there’s still a human element in sports we can’t ignore as these advancements continue. The human aspect is what makes sports so great, after all. While AI can provide teams data about why a basketball player is struggling to shoot the ball well, for example, it has limitations and can’t replace a coach evaluating that player’s performance on video, talking and empathizing with them and coaching them through their struggles. The human interaction — not AI — builds trust between athletes and coaches to navigate those situations.  Or, while a team like the Giants can certainly utilize AI to determine fan giveaways, going to a tailgate and talking directly to fans about what they’d like to see incorporated at games is a better route. AI can never bench the human side of the sports experience, it should be utilized as a resource for leagues, players and coaches while still prioritizing the human element.</p>
1849.  
1850.  
1851.  
1852. <p>Protecting these sports, while following laws and regulations, is important to remember as the excitement around these tools grows. The work teams and leagues need to do to preserve the history and human side of these sports while progressing them forward and ensuring ethical AI is powered is critical.</p>
1853.  
1854.  
1855.  
1856. <a class="ft-c-inline-cta" href="https://vpn.mozilla.org/">
1857.  <div class="ft-c-inline-cta__media">
1858.  <img alt="" class="attachment-1x1 size-1x1" height="800" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2020/08/moz_web_vpn_hero_05_2x-800x800.png" width="800" />  </div>
1859.  <div class="ft-c-inline-cta__content">
1860.     <h3>Device-level encryption from a name you can trust</h3>      <span>Try Mozilla VPN</span>   </div>
1861. </a>
1862. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/ai/ai-sports-nfl-draft-nba-mlb-mozilla-innovation/&quot;&gt;How AI is redefining your sports experience right now&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>
1863. <pubDate>Fri, 10 May 2024 17:25:23 +0000</pubDate>
1864. <dc:creator>Aron Yohannes</dc:creator>
1865. </item>
1866. <item>
1867. <title>Firefox Nightly: Screenshots++ – These Weeks in Firefox: Issue 160</title>
1868. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1635</guid>
1869. <link>https://blog.nightly.mozilla.org/2024/05/09/screenshots-these-weeks-in-firefox-issue-160/</link>
1870. <description>&lt;h3&gt;Highlights&lt;/h3&gt;
1871. <ul>
1872. <li>The <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1870127">screenshots component pref just got enabled</a> and is riding the trains in 127! This is a new implementation of the screenshots feature with a number of usability, accessibility and performance improvements over the original.</li>
1873. <li>Thanks to Joseph Webster for creating a brand new JWPlayer video wrapper (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891599">bug</a>) and for adding more sites under this wrapper to expand Picture-in-Picture captions support (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893061">bug</a>).
1874. <ul>
1875. <li>New supported sites include AOL, C-SPAN, CPAC, CNBC, Reuters, The Independent, Yahoo and more!</li>
1876. </ul>
1877. </li>
1878. <li>Irene landed the first part of refreshed text formatting controls for Reader Mode. Check them out by toggling reader.improved_text_menu.enabled (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1880658">bug 1880658</a>)
1879. <ul>
1880. <li><a href="https://blog.nightly.mozilla.org/files/2024/05/image2.png"><img alt="A panel in Firefox's Reader Mode is shown for controlling layout and text on the page. The panel lets users control the content width, line spacing, character spacing, word spacing, and text alignment of the text in reader mode." class="aligncenter size-full wp-image-1630" height="688" src="https://blog.nightly.mozilla.org/files/2024/05/image2.png" width="430" /></a></li>
1881. </ul>
1882. </li>
1883. <li>New tab wallpapers have landed in Nightly and will be released as an experiment in en-US. If you’d like to enable wallpapers, set browser.newtabpage.activity-stream.newtabWallpapers.enabled to true.
1884. <ul>
1885. <li>
1886. <p></p><div class="wp-caption aligncenter" id="attachment_1616" style="width: 1006px;"><a href="https://blog.nightly.mozilla.org/files/2024/04/image2.png"><img alt="Firefox's New Tab page with a beautiful image of the aurora borealis set as the background wallpaper" class="size-full wp-image-1616" height="740" src="https://blog.nightly.mozilla.org/files/2024/04/image2.png" width="996" /></a><p class="wp-caption-text" id="caption-attachment-1616">Set a new look for new tabs!</p></div></li>
1887. </ul>
1888. </li>
1889. </ul>
1890. <h3>Friends of the Firefox team</h3>
1891. <h3><a href="https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20%28excluding%20employees%29&quicksearch=1856717%2C1888221%2C1887529%2C1887821%2C1889710%2C1887543%2C1886858%2C1838152%2C1883058%2C1876286%2C1880914%2C1825105%2C1891247%2C1891604%2C1870880%2C1844935%2C1891599%2C1869065%2C1836440%2C1891816%2C1893433%2C1893564%2C1893935%2C1893061&list_id=17012220">Resolved bugs (excluding employees)</a></h3>
1892. <p><a href="https://github.com/niklasbaumgardner/NewContributorScraper">Script to find new contributors from bug list</a></p>
1893. <h4>Volunteers that fixed more than one bug</h4>
1894. <ul>
1895. <li>Camille</li>
1896. <li>gravyant</li>
1897. <li>Itiel Joseph</li>
1898. <li>Webster</li>
1899. <li>Magnus Melin [:mkmelin]</li>
1900. <li>Meera Murthy</li>
1901. <li>Steve P</li>
1902. </ul>
1903. <h4>New contributors (🌟 = first patch)</h4>
1904. <ul>
1905. <li>🌟 endington543 <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891816">refactored gOnceInitializedDeferred</a> to use Promise.withResolvers</li>
1906. <li>gravyant <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1869065">updated some of the element property names</a> used in moz-message-bar and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1870880">added isInstance assertion</a> method to Assert.sys.mjs</li>
1907. <li>🌟 Joseph Webster <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891599">created PiP JWPlayer wrapper</a> and added <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893061">PiP captions support for additional</a> sites that use JWPlayer</li>
1908. <li>🌟 Steve P <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1836440">updated some Firefox favicons</a> to look better black/dark backgrounds and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1844935">replaced restart prompt</a> when changing history settings with an in-content dialogue box</li>
1909. </ul>
1910. <h3>Project Updates</h3>
1911. <h4>Add-ons / Web Extensions</h4>
1912. <h5>Addon Manager & about:addons</h5>
1913. <ul>
1914. <li>Starting from Firefox 127, installing new single-signed add-ons is disallowed (while already installed single-signed add-ons are still allowed to run). This behavior is currently only enabled in Nightly (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886157">Bug 1886157</a>) but it is expected to be extended to all channels later in the 127 cycle (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886160">Bug 1886160</a>)</li>
1915. <li>Fixed a styling issue hit by extensions options pages embedded in about:addons when the Dark mode is enabled (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888866">Bug 1888866</a>)</li>
1916. </ul>
1917. <h5>WebExtensions APIs</h5>
1918. <ul>
1919. <li>As part of the ongoing work related to improving cross-browser compatibility for Manifest Version 3 extensions:
1920. <ul>
1921. <li>Customized keyboard shortcuts associated to _execute_browser_action command for Manifest Version 2 extensions will be automatically associated to the _execute_action command when the same extension migrates to Manifest Version 3 (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1797811">Bug 1797811</a>). This way, the custom keyboard shortcut will keep working as expected from a user perspective.</li>
1922. <li>DNR rule limits have been raised to match the limits enforced by other browsers (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1803370">Bug 1803370</a>)</li>
1923. <li>DNR getDynamicRules and getSessionRules API methods will be accepting the additional ruleIds filter as a parameter and improve compatibility with DNR API in more recent Chrome versions (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1820870">Bug 1820870</a>)</li>
1924. </ul>
1925. </li>
1926. <li>Improved errors logged when a content script file does not exist (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891502">Bug 1891502</a>)
1927. <ul>
1928. <li>the error is now expected to look like Unable to load script: moz-extension://UUID/path/to/script.js</li>
1929. </ul>
1930. </li>
1931. </ul>
1932. <h4>Developer Tools</h4>
1933. <h5>DevTools</h5>
1934. <ul>
1935. <li>Julian reverted a change a few months ago so DevTools screenshots are saved in the same location as Firefox screenshots (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1845037">#1845037</a>)</li>
1936. <li>Alex fixed a Debugger crash (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891699">#1891699</a>)</li>
1937. <li>Nicolas fixed a visual glitch in the Debugger (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891681">#1891681</a>)</li>
1938. <li>Alex fixed an issue where Network request from iframe sent just before document destruction were not displayed in the Netmonitor (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1887852">#1887852</a>)</li>
1939. <li>Nicolas replaced DevTools JS-based CSS lexer with a Rust-based version, using the same cssparser crate than Stylo (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1887638">#1887638</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1892895">#1892895</a>)
1940. <ul>
1941. <li>This brought a ~10% performance improvement when displaying rules in the inspector (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888607">#1888607</a> + <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890552">#1890552</a>)</li>
1942. </ul>
1943. </li>
1944. <li>Thanks to :willdurand, we finally released a new version of the DevTools ADB extension used by about:debugging. The extension is now shipping with notarized binaries and can be used on recent macOS versions. (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1821449">#1821449</a>)</li>
1945. </ul>
1946. <h5>WebDriver BiDi</h5>
1947. <ul>
1948. <li>Thanks to gravyant who implemented a new helper Assert.isInstance to check whether objects are instances of specific classes (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1870880">#1870880</a>)</li>
1949. <li>Henrik updated mozrunner/mozprocess to use “psutil” and support the new application restart mechanism on macos (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884401">#1884401</a>)</li>
1950. <li>Sasha added support for the a11y attributes locator for the browsingContext.locateNodes command (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885577">#1885577</a>)</li>
1951. <li>Sasha added support for the devicePixelRatio parameter for the browsingContext.setViewport command (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1857961">#1857961</a>)</li>
1952. <li>Henrik improved the way we check if an element is disabled when using the WebDriver ElementClear command (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1863266">#1863266</a>)</li>
1953. <li>Julian updated the vendored puppeteer version to v22.6.5, which enables new network interception features in Puppeteer using WebDriver BiDi (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891762">#1891762</a>)</li>
1954. </ul>
1955. <h4>Migration Improvements</h4>
1956. <ul>
1957. <li>Profile backup / recovery
1958. <ul>
1959. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885369">We’re 95% done the staging metabug</a> – fchasen is just <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886235">trying to fix an absolute path problem</a> we discovered in our WebExtensions code.</li>
1960. <li>We’re about half-way done with <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885955">the recovery metabug</a>. We’re at the point where most critical data can be recovered from a decompressed backup archive. If you’re feeling adventurous, you can tinker with this at chrome://browser/content/backup/debug.html on Nightly, but no warranty implied.</li>
1961. <li>We’re working with the Glean team to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893650">come up with a mechanism of transferring the Glean client identifier</a> from the profile that initiates recovery.</li>
1962. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890579">We’ve also prepared the backup management UI metabug</a>. That’ll be next once we complete the recovery metabug.</li>
1963. </ul>
1964. </li>
1965. </ul>
1966. <h4>New Tab Page</h4>
1967. <ul>
1968. <li>Work continues on a weather widget for new tab (borrowing logic from URL bar). Stay tuned!</li>
1969. </ul>
1970. <h4>Privacy & Security</h4>
1971. <ul>
1972. <li>We’re working on a new anti-tracking feature: Bounce Tracking Protection. It works similar to the existing <a href="https://blog.mozilla.org/security/2020/08/04/firefox-79-includes-protections-against-redirect-tracking/">Cookie Purging</a> feature in Firefox, but instead of a tracker list it relies on heuristics to detect bounce trackers.
1973. <ul>
1974. <li>It’s based on the <a href="https://privacycg.github.io/nav-tracking-mitigations/#bounce-tracking-mitigations">navigational-tracking-protections spec draft</a> in the PrivacyCG</li>
1975. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1877432">Bug 1877432</a> first enabled the feature in Nightly in “dry run mode” where we don’t purge tracker storage but only collect telemetry. We’re looking to fully enable it in Nightly soon once we think it’s stable enough.</li>
1976. </ul>
1977. </li>
1978. </ul>
1979. <h4>Profile Management (new this week!)</h4>
1980. <ul>
1981. <li>We’re getting underway with improvements to multiple profiles support in Firefox!</li>
1982. <li>Eng discussion on Matrix: <a href="https://matrix.to/#/#fx-profile-eng:mozilla.org">#fx-profile-eng</a></li>
1983. <li>Backend work in toolkit/profile behind a build flag (MOZ_SELECTABLE_PROFILES)</li>
1984. <li>Frontend work in browser/components/profiles behind a pref (browser.profiles.enabled)</li>
1985. <li>Metabug is here: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1882882">1882882</a></li>
1986. <li>Bugs landed so far:
1987. <ul>
1988. <li>Mossop added telemetry to record the version of the profiles database on startup and the number of profiles in it (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1878339">bug 1878339</a>)</li>
1989. <li>Niklas added the profiles browser component (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883143">bug 1883143</a>)</li>
1990. <li>Niklas added profiles menu items to the app menu (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883155">bug 1883155</a>)</li>
1991. </ul>
1992. </li>
1993. <li>Coming soon: Docs, final UX, and good-first-bugs</li>
1994. </ul>
1995. <h4>Screenshots</h4>
1996. <ul>
1997. <li>Niklas added a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1873862">border to the region pixel size card</a> in the selected region
1998. <ul>
1999. <li>Before
2000. <ul>
2001. <li>
2002. <p></p><div class="wp-caption aligncenter" id="attachment_1633" style="width: 478px;"><a href="https://blog.nightly.mozilla.org/files/2024/05/image5.png"><img alt="The screenshot region picker in Firefox is displayed over top of an article from Wikipedia. A display in the centre of the picker shows that the region is "948 x 205". The display does not have a border around it, making it more difficult to distinguish it from the background." class="size-full wp-image-1633" height="254" src="https://blog.nightly.mozilla.org/files/2024/05/image5.png" width="468" /></a><p class="wp-caption-text" id="caption-attachment-1633">Can you see the screenshot dimensions hidden in that text?</p></div></li>
2003. </ul>
2004. </li>
2005. <li>After
2006. <ul>
2007. <li>
2008. <p></p><div class="wp-caption aligncenter" id="attachment_1632" style="width: 480px;"><a href="https://blog.nightly.mozilla.org/files/2024/05/image4.png"><img alt="The screenshot region picker in Firefox is displayed over top of an article from Wikipedia. A display in the centre of the picker shows that the region is "948 x 205". The display does has a border around it, making it easier to distinguish it from the background." class="size-full wp-image-1632" height="236" src="https://blog.nightly.mozilla.org/files/2024/05/image4.png" width="470" /></a><p class="wp-caption-text" id="caption-attachment-1632">That’s easier!</p></div></li>
2009. </ul>
2010. </li>
2011. </ul>
2012. </li>
2013. <li>Niklas fixed a bug where the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1887093">selected text would get cleared</a> when screenshotting a region
2014. <ul>
2015. <li><a href="https://blog.nightly.mozilla.org/files/2024/05/image3.png"><img alt=""Take screenshots in Firefox" is shown in text, with the word "screenshots" selected." class="aligncenter size-full wp-image-1631" height="138" src="https://blog.nightly.mozilla.org/files/2024/05/image3.png" width="660" /></a></li>
2016. </ul>
2017. </li>
2018. </ul>
2019. <h4>Search and Navigation</h4>
2020. <ul>
2021. <li>Marco <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1848715">fixed editing and copying URLs when the protocol is hidden in the address bar</a>
2022. <ul>
2023. <li>This was our main outstanding blocker for shipping hiding https:// instead of http://, so hopefully that should happen soon!</li>
2024. </ul>
2025. </li>
2026. <li>Dale <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1871206">landed a prototype of secondary actions buttons in address bar results</a>
2027. <ul>
2028. <li>As part of that secondary actions buttons effort, he also fixed some bugs with the (currently disabled by default) site-specific search feature:
2029. <ul>
2030. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893310">Bug 1893310 – Contextual Search only searches first letter</a></li>
2031. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893823">Bug 1893823 – Contextual search breaks urlbar when no engine</a></li>
2032. </ul>
2033. </li>
2034. </ul>
2035. </li>
2036. <li>Stephanie and James have been working on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1846381">phase 2 of implementing Search Engine Result Page Search Term Categorization</a>, specifically:
2037. <ul>
2038. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1882844">Updated search-telemetry-v2 collection on Remote Settings to include selectors for Bing search result pages</a></li>
2039. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1892267">Added the number of loaded and hidden ads to the categorization event</a></li>
2040. </ul>
2041. </li>
2042. <li>Standard8 and Mandy continued their work on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1833829">search-config-v2</a>:
2043. <ul>
2044. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889037">Updated documentation for search-config-v2</a></li>
2045. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890378">Changed some of the concept for search-config-v2 to avoid duplication and to simplify how variants are applied within the configuration</a></li>
2046. <li>We’re now rolling it out to 50% of beta users.</li>
2047. </ul>
2048. </li>
2049. <li>Daisuke <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891145">implemented history flooding protection</a> (currently disabled behind pref)</li>
2050. <li>Daisuke <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891602">added the “Manage Firefox Suggest” menu item for Navigational and Dynamic Wikipedia suggestions in the address bar</a></li>
2051. </ul>
2052. <h4>Storybook/Reusable Components</h4>
2053. <ul>
2054. <li>hjones fixed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1803678">Bug 1803678 – Enable on-demand/lazy loading for ESModule based reusable components</a>
2055. <ul>
2056. <li>if you’ve ever had to use ensureCustomElements before this is relevant to you</li>
2057. </ul>
2058. </li>
2059. <li>hjones is working on re-landing <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1858812">Bug 1858812 – Create a icon and text variant of moz-button</a></li>
2060. <li>jsudiaman fixed Firefox View stories in Storybook with the landing of <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1867614">Bug 1867614 – fxview-tab-list story is broken, shows a “ChromeUtils is not defined” error</a></li>
2061. <li>gravyant cleaned up propertie names in moz-message-bar in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1869065">Bug 1869065 – Re-visit some of the element property names used in moz-message-bar</a></li>
2062. <li>kcochrane landed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1877826">Bug 1877826 – Add MozPageNavLink custom component to MozPageNav</a>
2063. <ul>
2064. <li>this will enable us to start replacing nav menus in about:addons and about:preferences to better align with the nav in Firefox View</li>
2065. </ul>
2066. </li>
2067. <li>mstriemer made it so that you can use moz-buttons as children of moz-button-group in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893218">Bug 1893218 – moz-button-group should support moz-button children</a></li>
2068. <li>tgiles added a link to our new reusable components dashboard to Storybook <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893685">Bug 1893685 – Add link to the “Reusable Component Adoption” chart in our docs</a></li>
2069. <li>The dashboard to track adoption in Firefox can be visited here: <a href="https://firefoxux.github.io/recomp-metrics/">https://firefoxux.github.io/recomp-metrics/</a></li>
2070. &lt;/ul&gt;</description>
2071. <pubDate>Thu, 09 May 2024 16:20:17 +0000</pubDate>
2072. <dc:creator>Mike Conley</dc:creator>
2073. </item>
2074. <item>
2075. <title>Anne van Kesteren: Undue base URL influence</title>
2076. <guid isPermaLink="false">tag:annevankesteren.nl,2024-05-08:/091232/undue-base-url-influence</guid>
2077. <link>https://annevankesteren.nl/2024/05/undue-base-url-influence</link>
2078. <description>&lt;p&gt;The URL parser has many quirks due to its origins in a time where conformance test suites were atypical and implementation requirements were hidden in the examples section. Some consider these quirks deeply problematic, but personally I don’t really mind that one can write a hundred slashes after a scheme instead of two and get identical results. Sure, it would be better if that were not the case, but in the end it is something that is normalized away and therefore does not impact the fundamental aspects of the URL ecosystem.&lt;/p&gt;
2079.  
2080. <p>I was reminded the other day that there is one quirk however that does yield rather undesirable results. In particular for certain (non-conforming) inputs, the result will not be failure, but the exact URL returned will depend on the presence and type of base URL. This might be best explained with examples:</p>
2081.  
2082. <table>
2083. <thead>
2084.  <tr><th>Input</th><th>Base URL (serialized)</th><th>Output (serialized)</th></tr>
2085. </thead>
2086. <tbody>
2087.  <tr><td><code>https:test</code></td><td>—</td><td><code>https://test/</code></td></tr>
2088.  <tr><td><code>https:test</code></td><td><code>http://example/</code></td><td><code>https://test/</code></td></tr>
2089.  <tr><td><code>https:test</code></td><td><code>https://example/</code></td><td><code>https://example/test</code></td></tr>
2090.  <tr><td><code>hello:test</code></td><td>—</td><td><code>hello:test</code></td></tr>
2091.  <tr><td><code>hello:test</code></td><td><code>bye://example/</code></td><td><code>hello:test</code></td></tr>
2092.  <tr><td><code>hello:test</code></td><td><code>hello://example/</code></td><td><code>hello:test</code></td></tr>
2093. </tbody>
2094. </table>
2095.  
2096. <p>This quirk only impacts so-called <a href="https://url.spec.whatwg.org/#special-scheme">special schemes</a>, which include <code>http</code> and <code>https</code>. And only when they match between the input and base URL. As a user of URLs you could work around this quirk by first parsing without a base URL and only if that returns failure, parse a second time with a base URL. That does have the unfortunate side effect of being inconsistent with the web platform (for non-conforming input), but depending on your use case that might be okay.</p>
2097.  
2098. &lt;p&gt;I remember looking into whether this could be removed completely many years ago, but websites relied on it and &lt;a href=&quot;https://www.w3.org/TR/html-design-principles/#priority-of-constituencies&quot;&gt;end users trump theory&lt;/a&gt;.&lt;/p&gt;</description>
2099. <pubDate>Wed, 08 May 2024 12:30:23 +0000</pubDate>
2100. </item>
2101. <item>
2102. <title>Mozilla Thunderbird: Thunderbird for Android / K-9 Mail: April 2024 Progress Report</title>
2103. <guid isPermaLink="false">https://blog.thunderbird.net/?p=1744</guid>
2104. <link>https://blog.thunderbird.net/2024/05/thunderbird-for-android-k-9-mail-april-2024-progress-report/</link>
2105. <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/2024/05/blog-banner-logo-logo-FINAL-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
2106. <p>Welcome to our monthly report on turning K-9 Mail into Thunderbird for Android! <a href="https://blog.thunderbird.net/2024/04/thunderbird-for-android-k-9-mail-march-2024-progress-report/">Last month</a> you could read about how we found and fixed bugs after publishing a new stable release. This month we start with… telling you that we fixed even more bugs.</p>
2107.  
2108.  
2109.  
2110. <h3>Fixing bugs</h3>
2111.  
2112.  
2113.  
2114. <p>After the release of K-9 Mail 6.800 we dedicated some time to fixing bugs. We published the first bugfix release in March and continued that work in April.</p>
2115.  
2116.  
2117.  
2118. <h4>K-9 Mail 6.802</h4>
2119.  
2120.  
2121.  
2122. <p>The second bugfix release contained these changes:</p>
2123.  
2124.  
2125.  
2126. <ul>
2127. <li>Push: Notify user if permission to schedule exact alarms is missing</li>
2128.  
2129.  
2130.  
2131. <li>Renamed “Send client ID” setting to “Send client information”</li>
2132.  
2133.  
2134.  
2135. <li>IMAP: Added support for the \NonExistent LIST response attribute</li>
2136.  
2137.  
2138.  
2139. <li>IMAP: Issue EXPUNGE command after moving without MOVE extension</li>
2140.  
2141.  
2142.  
2143. <li>Updated translations; added Hebrew translation</li>
2144. </ul>
2145.  
2146.  
2147.  
2148. <p>I’m especially happy that we were able to add back the Hebrew translation. We removed it prior to the K-9 Mail 6.800 release due to the translation being less than 70% complete (it was at 49%). Since then volunteers translated the missing bits of the app and in April the translation was almost complete.</p>
2149.  
2150.  
2151.  
2152. <p>Unfortunately, the same isn’t true for the Korean translation that was also removed. It was 69% complete, right below the threshold. Since then there has been no significant change. If you are a K-9 Mail user and a native Korean speaker, please consider <a href="https://hosted.weblate.org/projects/tb-android/-/ko/">helping out</a>.</p>
2153.  
2154.  
2155.  
2156. <h4>F-Droid metadata (again?)</h4>
2157.  
2158.  
2159.  
2160. <p>In the previous progress report we described what change had led to the app description disappearing on F-Droid and how we intended to fix it. Unfortunately we found out that our approach to fixing the issue didn’t work due to the way F-Droid builds their app index. So we changed our approach once again and hope that the app description will be restored with the next app release.</p>
2161.  
2162.  
2163.  
2164. <h4>Push & the permission to schedule alarms</h4>
2165.  
2166.  
2167.  
2168. <p>K-9 Mail 6.802 notifies the user when Push is enabled in settings, but the permission to schedule exact alarms is missing. However, what we really want to do is ask the user for this permission before we allow them to enable Push.</p>
2169.  
2170.  
2171.  
2172. <figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex">
2173. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/05/k9mail__push_folders__permission-1.png"><img alt="" class="wp-image-1747" height="1270" src="https://blog.thunderbird.net/files/2024/05/k9mail__push_folders__permission-1-600x1270.png" width="600" /></a></figure>
2174.  
2175.  
2176.  
2177. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/05/k9mail__push_folders__enabled-1.png"><img alt="" class="wp-image-1748" height="1270" src="https://blog.thunderbird.net/files/2024/05/k9mail__push_folders__enabled-1-600x1270.png" width="600" /></a></figure>
2178. </figure>
2179.  
2180.  
2181.  
2182. <p>This change was completed in April and will be included in the next bugfix release, K-9 Mail 6.803.</p>
2183.  
2184.  
2185.  
2186. <h3>Material 3</h3>
2187.  
2188.  
2189.  
2190. <p>As briefly mentioned in March’s progress report, we’ve started work on switching the app to Google’s latest version of Material Design – <a href="https://m3.material.io/">Material 3</a>. In April we completed the technical conversion. The app is now using Material 3 components instead of the Material Design 2 ones.</p>
2191.  
2192.  
2193.  
2194. <p>The next step is to clean up the different screens in the app. This means adjusting spacings, text sizes, colors, and sometimes more extensive changes. </p>
2195.  
2196.  
2197.  
2198. <p>We didn’t release any beta versions while the development version was still a mix of Material Design 2 and Material 3. Now that the first step is complete, we’ll resume publishing beta versions.</p>
2199.  
2200.  
2201.  
2202. <p>If you are a beta tester, please be aware that the app still looks quite rough in a couple of places. While the app should be fully functional, you might want to <a href="https://support.google.com/googleplay/answer/7003180">leave the beta program</a> for a while if the look of the app is important to you.</p>
2203.  
2204.  
2205.  
2206. <h3>Targeting Android 14</h3>
2207.  
2208.  
2209.  
2210. <p>Part of the necessary app maintenance is to update the app to target the latest Android version. This is required for the app to use the latest security features and to cope with added restrictions the system puts in place. It’s also required by Google in order to be able to publish updates on Google Play.</p>
2211.  
2212.  
2213.  
2214. <p>The work to <a href="https://developer.android.com/about/versions/14/behavior-changes-14">target Android 14</a> is now mostly complete. This involved some behind the scenes changes that users hopefully won’t notice at all. We’ll be testing these changes in a future beta version before including them in a K-9 Mail 6.8xx release.</p>
2215.  
2216.  
2217.  
2218. <h3>Building two apps</h3>
2219.  
2220.  
2221.  
2222. <p>If you’re reading this, it’s probably because you’re excited for Thunderbird for Android to be finally released. However, we’ve also heard numerous times that people love K-9 Mail and wished the app would stay around. That’s why we’ve <a href="https://blog.thunderbird.net/2023/12/when-will-thunderbird-for-android-be-released/">announced</a> in December to do just that.</p>
2223.  
2224.  
2225.  
2226. <p>We’ve started work on this and are now able to build two apps from the same source code. Thunderbird for Android already includes the fancy new Thunderbird logo and a first version of a blue theme.</p>
2227.  
2228.  
2229.  
2230. <figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-3 is-layout-flex wp-block-gallery-is-layout-flex">
2231. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/05/k9mail__welcome.png"><img alt="" class="wp-image-1750" height="1270" src="https://blog.thunderbird.net/files/2024/05/k9mail__welcome-600x1270.png" width="600" /></a></figure>
2232.  
2233.  
2234.  
2235. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/05/thunderbird__welcome__incomplete.png"><img alt="" class="wp-image-1749" height="1270" src="https://blog.thunderbird.net/files/2024/05/thunderbird__welcome__incomplete-600x1270.png" width="600" /></a></figure>
2236. </figure>
2237.  
2238.  
2239.  
2240. <p>But as you can see in the screenshots above, we’re not quite done yet. We still have to change parts of the app where the app name is displayed to use a placeholder instead of a hard-coded string. Then there’s the About screen and a couple of other places that require app-specific behavior.</p>
2241.  
2242.  
2243.  
2244. <p>We’ll keep you posted.</p>
2245.  
2246.  
2247.  
2248. <h3>Releases</h3>
2249.  
2250.  
2251.  
2252. <p>In April 2024 we published the following stable release:</p>
2253.  
2254.  
2255.  
2256. <ul>
2257. <li><a href="https://github.com/thunderbird/thunderbird-android/releases/tag/6.802">K-9 Mail v6.802</a> (2024-04-05)</li>
2258. </ul>
2259. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2024/05/thunderbird-for-android-k-9-mail-april-2024-progress-report/&quot;&gt;Thunderbird for Android / K-9 Mail: April 2024 Progress Report&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>
2260. <pubDate>Wed, 08 May 2024 11:00:00 +0000</pubDate>
2261. <dc:creator>cketti</dc:creator>
2262. </item>
2263. <item>
2264. <title>This Week In Rust: This Week in Rust 546</title>
2265. <guid isPermaLink="false">tag:this-week-in-rust.org,2024-05-08:/blog/2024/05/08/this-week-in-rust-546/</guid>
2266. <link>https://this-week-in-rust.org/blog/2024/05/08/this-week-in-rust-546/</link>
2267. <description>&lt;p&gt;Hello and welcome to another issue of &lt;em&gt;This Week in Rust&lt;/em&gt;!
2268. <a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
2269. This is a weekly summary of its progress and community.
2270. Want something mentioned? Tag us at <a href="https://twitter.com/ThisWeekInRust">@ThisWeekInRust</a> on Twitter or <a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social, or <a href="https://github.com/rust-lang/this-week-in-rust">send us a pull request</a>.
2271. Want to get involved? <a href="https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md">We love contributions</a>.</p>
2272. <p><em>This Week in Rust</em> is openly developed <a href="https://github.com/rust-lang/this-week-in-rust">on GitHub</a> and archives can be viewed at <a href="https://this-week-in-rust.org/">this-week-in-rust.org</a>.
2273. If you find any errors in this week's issue, <a href="https://github.com/rust-lang/this-week-in-rust/pulls">please submit a PR</a>.</p>
2274. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#updates-from-rust-community">Updates from Rust Community</a></h4>
2275.  
2276.  
2277. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#official">Official</a></h5>
2278. <ul>
2279. <li><a href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html">Announcing Rust 1.78.0</a></li>
2280. <li><a href="https://blog.rust-lang.org/2024/05/06/Rustup-1.27.1.html">Announcing Rustup 1.27.1</a></li>
2281. <li><a href="https://blog.rust-lang.org/2024/05/06/check-cfg.html">Automatic checking of cfgs at compile-time</a></li>
2282. <li><a href="https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html">Announcing Google Summer of Code 2024 selected projects</a></li>
2283. <li><a href="https://blog.rust-lang.org/2024/05/07/OSPP-2024.html">Rust participates in OSPP 2024</a></li>
2284. <li><a href="https://blog.rust-lang.org/inside-rust/2024/05/07/this-development-cycle-in-cargo-1.79.html">This Development-cycle in Cargo: 1.79</a></li>
2285. <li><a href="https://blog.rust-lang.org/inside-rust/2024/05/07/announcing-project-goals.html">Rust Project Goals Submission Period</a></li>
2286. </ul>
2287. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#foundation">Foundation</a></h5>
2288. <ul>
2289. <li><a href="https://foundation.rust-lang.org/news/1m-microsoft-donation-to-fund-key-rust-foundation-project-priorities/">$1M Microsoft Donation to Fund Key Rust Foundation & Project Priorities</a></li>
2290. </ul>
2291. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#newsletters">Newsletters</a></h5>
2292. <ul>
2293. <li><a href="https://rust-osdev.com/this-month/2024-04/">This Month in Rust OSDev: April 2024</a></li>
2294. <li><a href="https://gamedev.rs/news/050/">This Month in Rust GameDev #50 - April 2024</a></li>
2295. <li><a href="https://rustfest.ch/posts/2024-05-07/all-talks-announced/">RustFest.ch - All talks announced</a></li>
2296. </ul>
2297. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#projecttooling-updates">Project/Tooling Updates</a></h5>
2298. <ul>
2299. <li><a href="https://www.reddit.com/r/rust/comments/1cj94va/image_v025_performance_improvements/">image v0.25: performance improvements, production-ready WebP</a></li>
2300. <li><a href="https://rust-analyzer.github.io/thisweek/2024/05/06/changelog-232.html">rust-analyzer changelog #232</a></li>
2301. <li><a href="https://blog.antoyo.xyz/rustc_codegen_gcc-progress-report-32">rustc_codegen_gcc: Progress Report #32</a></li>
2302. <li><a href="https://grafbase.com/changelog/graphql-lint">Introducing graphql-lint and gqlint</a></li>
2303. <li><a href="https://blog.meilisearch.com/meilisearch-1-8/">Meilisearch releases v1.8</a></li>
2304. <li><a href="https://github.com/r3bl-org/r3bl-open-core/blob/main/CHANGELOG.md#v052-2020-05-06">r3bl_terminal_async v0.5.2 released</a></li>
2305. <li><a href="https://zed.dev/blog/zed-decoded-linux-when">Zed Decoded: Linux when?</a></li>
2306. </ul>
2307. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#observationsthoughts">Observations/Thoughts</a></h5>
2308. <ul>
2309. <li><a href="https://faultlore.com/blah/abi-puns/">Pair Your Compilers At The ABI Café - Faultlore</a></li>
2310. <li><a href="https://smallcultfollowing.com/babysteps/blog/2024/05/02/unwind-considered-harmful/">Unwind considered harmful?</a></li>
2311. <li><a href="https://v5.chriskrycho.com/journal/async-rust-complexity/">Async Rust Complexity</a></li>
2312. <li><a href="https://ochagavia.nl/blog/download-accelerator-async-rust-edition/">Download Accelerator - Async Rust Edition</a></li>
2313. <li>[video] <a href="https://www.youtube.com/watch?v=WSHt3-gwVxc">David Lattimore - A Linker in the Wild</a></li>
2314. <li>[audio] <a href="https://corrode.dev/podcast/s02e01-curl/">curl - Daniel Stenberg, Open Source Maintainer and Public Speaker</a></li>
2315. </ul>
2316. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust-walkthroughs">Rust Walkthroughs</a></h5>
2317. <ul>
2318. <li><a href="https://gaultier.github.io/blog/how_to_rewrite_a_cpp_codebase_successfully.html">How to rewrite a C++ codebase successfully</a></li>
2319. <li><a href="https://www.sea-ql.org/blog/2024-05-05-redis-kafka-data-sink/">Building a Redis / Kafka Data Sink in Rust</a></li>
2320. <li>[ZH | EN] <a href="https://ideas.reify.ing/en/blog/gpt-plugin-rust-and-lost-gems/">Writing a GPT Plugin in Rust, and Lost Gems</a></li>
2321. <li><a href="https://blog.sulami.xyz/posts/what-is-in-a-rust-allocator/">What is in a Rust Allocator?</a></li>
2322. <li><a href="https://glitchcomet.com/articles/1024-bit-primes/">How hard can generating 1024-bit primes really be?</a></li>
2323. <li><a href="https://blog.theembeddedrustacean.com/stm32f4-embedded-rust-at-the-pac-system-clock-configuration">STM32F4 Embedded Rust at the PAC: System Clock Configuration</a></li>
2324. <li>[video] <a href="https://www.youtube.com/watch?v=J3C6sNK2wnk">Make a port scanner in #rustlang with Tokio and learn async Rust</a></li>
2325. </ul>
2326. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#research">Research</a></h5>
2327. <ul>
2328. <li><a href="https://rust-digger.code-maven.com/news/cargo-lock-and-main-rs">Rust Digger: 47,764 (32.92%) of the crates include a Cargo.lock file</a></li>
2329. <li><a href="https://arxiv.org/abs/2404.18852">VERT: Verified Equivalent Rust Transpilation with Few-Shot Learning</a></li>
2330. </ul>
2331. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#miscellaneous">Miscellaneous</a></h5>
2332. <ul>
2333. <li><a href="https://rust.code-maven.com/elapsed-time-logger">Elapsed time logger</a></li>
2334. </ul>
2335. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#crate-of-the-week">Crate of the Week</a></h4>
2336. <p>This week's crate is <a href="https://docs.rs/derive_more">derive_more</a>, a crate for deriving a whole lot of traits</p>
2337. <p>Thanks to <a href="https://users.rust-lang.org/t/crate-of-the-week/2704/1306">teor</a> for the suggestion!</p>
2338. <p><a href="https://users.rust-lang.org/t/crate-of-the-week/2704">Please submit your suggestions and votes for next week</a>!</p>
2339. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#call-for-testing">Call for Testing</a></h4>
2340. <p>An important step for RFC implementation is for people to experiment with the
2341. implementation and give feedback, especially before stabilization.  The following
2342. RFCs would benefit from user testing before moving forward:</p>
2343. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rfcs"></a><a href="https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing">RFCs</a></h5>
2344. <ul>
2345. <li><a href="https://github.com/rust-lang/rfcs/pull/3537">RFC: Make Cargo respect minimum supported Rust version (MSRV) when selecting dependencies</a></li>
2346. <li><a href="https://github.com/rust-lang/cargo/issues/13873">Testing steps</a></li>
2347. </ul>
2348. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rustup"></a><a href="https://github.com/rust-lang/rustup/labels/call-for-testing">Rustup</a></h5>
2349. <ul>
2350. <li><a href="https://github.com/rust-lang/rustup/issues/3806">CfT: Test out Rustup's <code>reqwest</code> backend with <code>rustls</code></a></li>
2351. <li><a href="https://github.com/rust-lang/rustup/issues/3806#issue-2278962476">Testing steps</a></li>
2352. </ul>
2353. <p>If you are a feature implementer and would like your RFC to appear on the above list, add the new <code>call-for-testing</code>
2354. label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
2355. need testing.</p>
2356. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers">Call for Participation; projects and speakers</a></h4>
2357. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#cfp-projects">CFP - Projects</a></h5>
2358. <p>Always wanted to contribute to open-source projects but did not know where to start?
2359. Every week we highlight some tasks from the Rust community for you to pick and get started!</p>
2360. <p>Some of these tasks may also have mentors available, visit the task page for more information.</p>
2361. <ul>
2362. <li><a href="https://github.com/GreptimeTeam/greptimedb/issues/3336">greptimedb - Add TLS support for GreptimeDB's gRPC service</a></li>
2363. </ul>
2364. <p>If you are a Rust project owner and are looking for contributors, please submit tasks <a href="https://users.rust-lang.org/t/twir-call-for-participation/4821">here</a>.</p>
2365. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#cfp-speakers">CFP - Speakers</a></h5>
2366. <p>Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.</p>
2367. <ul>
2368. <li><a href="https://www.papercall.io/eurorust-2024">EuroRust 2024</a>| Closes 2024-06-03 | Vienna, Austria & online | Event date: 2024-10-10</li>
2369. <li><a href="https://scientificcomputing.rs/">Scientific Computing in Rust 2024</a>| Closes 2024-06-14 | online | Event date: 2024-07-17 - 2024-07-19</li>
2370. <li><a href="https://www.papercall.io/conf42-rustlang-2024">Conf42 Rustlang 2024</a> | Closes 2024-07-22 | online | Event date: 2024-08-22</li>
2371. </ul>
2372. <p>If you are an event organizer hoping to expand the reach of your event, please submit a link to the submission website through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a>.</p>
2373. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#updates-from-the-rust-project">Updates from the Rust Project</a></h4>
2374. <p>426 pull requests were <a href="https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2024-04-30..2024-05-07">merged in the last week</a></p>
2375. <ul>
2376. <li><a href="https://github.com/rust-lang/rust/pull/124637">AST pretty: Use <code>builtin_syntax</code> for type ascription</a></li>
2377. <li><a href="https://github.com/rust-lang/rust/pull/124626"><code>const_eval_select</code>: add tracking issue</a></li>
2378. <li><a href="https://github.com/rust-lang/rust/pull/124059"><code>default_alloc_error_hook</code>: explain difference to default <code>__rdl_oom</code> in alloc</a></li>
2379. <li><a href="https://github.com/rust-lang/rust/pull/123602">account for immutably borrowed locals in MIR copy-prop and GVN</a></li>
2380. <li><a href="https://github.com/rust-lang/rust/pull/124561">add <code>normalize()</code> in run-make <code>Diff</code> type</a></li>
2381. <li><a href="https://github.com/rust-lang/rust/pull/124742">add <code>rustfmt</code> cfg to well known cfgs list</a></li>
2382. <li><a href="https://github.com/rust-lang/rust/pull/123939">add a lint against never type fallback affecting unsafe code</a></li>
2383. <li><a href="https://github.com/rust-lang/rust/pull/124612">add support for inputing via stdin with run-make-support</a></li>
2384. <li><a href="https://github.com/rust-lang/rust/pull/124568">adjust <code>#[macro_export]</code>/doctest help suggestion for <code>non_local_defs</code> lint</a></li>
2385. <li><a href="https://github.com/rust-lang/rust/pull/124582">always print nice 'std not found' error when std is not found</a></li>
2386. <li><a href="https://github.com/rust-lang/rust/pull/124809">borrowck: prepopulate opaque storage more eagerly</a></li>
2387. <li><a href="https://github.com/rust-lang/rust/pull/124539">consider inner modules to be local in the <code>non_local_definitions</code> lint</a></li>
2388. <li><a href="https://github.com/rust-lang/rust/pull/123480">deref patterns: impl <code>DerefPure</code> for more std types</a></li>
2389. <li><a href="https://github.com/rust-lang/rust/pull/124771">don't consider candidates with no failing where clauses when refining obligation causes in new solver</a></li>
2390. <li><a href="https://github.com/rust-lang/rust/pull/124345">enable <code>--check-cfg</code> by default in UI tests</a></li>
2391. <li><a href="https://github.com/rust-lang/rust/pull/124663">enable reusing CI Docker cache when running CI images locally</a></li>
2392. <li><a href="https://github.com/rust-lang/rust/pull/124566">fix <code>NormalizesTo</code> proof tree issue</a></li>
2393. <li><a href="https://github.com/rust-lang/rust/pull/124494">fix unwinding on 32-bit watchOS ARM</a></li>
2394. <li><a href="https://github.com/rust-lang/rust/pull/124748">fix unwinding on 32-bit watchOS ARM (v2)</a></li>
2395. <li><a href="https://github.com/rust-lang/rust/pull/124492">generalize <code>adjust_from_tcx</code> for <code>Allocation</code></a></li>
2396. <li><a href="https://github.com/rust-lang/rust/pull/124717">implement <code>do_not_recommend</code> in the new solver</a></li>
2397. <li><a href="https://github.com/rust-lang/rust/pull/122492">implement <code>ptr_as_ref_unchecked</code></a></li>
2398. <li><a href="https://github.com/rust-lang/rust/pull/124679">improve check-cfg CLI errors with more structured diagnostics</a></li>
2399. <li><a href="https://github.com/rust-lang/rust/pull/124715">interpret, miri: uniform treatments of intrinsics/functions with and without return block</a></li>
2400. <li><a href="https://github.com/rust-lang/rust/pull/124720">interpret: drop: always evaluate place</a></li>
2401. <li><a href="https://github.com/rust-lang/rust/pull/124627">interpret: hide some reexports in rustdoc</a></li>
2402. <li><a href="https://github.com/rust-lang/rust/pull/117164">lazily normalize inside trait ref during orphan check & consider ty params in rigid alias types to be uncovered</a></li>
2403. <li><a href="https://github.com/rust-lang/rust/pull/124293">let miri and const eval execute intrinsics' fallback bodies</a></li>
2404. <li><a href="https://github.com/rust-lang/rust/pull/124690">only consider ambiguous goals when finding best obligation for ambiguities</a></li>
2405. <li><a href="https://github.com/rust-lang/rust/pull/124724">prefer lower vtable candidates in select in new solver</a></li>
2406. <li><a href="https://github.com/rust-lang/rust/pull/124718">record impl args in the proof tree</a></li>
2407. <li><a href="https://github.com/rust-lang/rust/pull/124759">record impl args in the proof tree in new solver</a></li>
2408. <li><a href="https://github.com/rust-lang/rust/pull/124550">remove redundant union check in <code>KnownPanicsLint</code> const prop</a></li>
2409. <li><a href="https://github.com/rust-lang/rust/pull/124529">rewrite select (in the new solver) to use a <code>ProofTreeVisitor</code></a></li>
2410. <li><a href="https://github.com/rust-lang/rust/pull/124623">shallow resolve in orphan check</a></li>
2411. <li><a href="https://github.com/rust-lang/rust/pull/124399">split mcdc code to a sub module of coverageinfo</a></li>
2412. <li><a href="https://github.com/rust-lang/rust/pull/124606">stop <code>llvm.expect</code>ing assert terminators</a></li>
2413. <li><a href="https://github.com/rust-lang/rust/pull/122253">support <code>Result<T, E></code> across FFI when niche optimization can be used</a></li>
2414. <li><a href="https://github.com/rust-lang/rust/pull/124610">tweak <code>consts_may_unify</code></a></li>
2415. <li><a href="https://github.com/rust-lang/rust/pull/124588">use <code>ObligationCtxt</code> in favor of <code>TraitEngine</code> in many more places</a></li>
2416. <li><a href="https://github.com/rust-lang/rust/pull/124808">use <code>super_fold</code> in <code>RegionsToStatic</code> visitor</a></li>
2417. <li><a href="https://github.com/rust-lang/rust/pull/124624">use <code>tcx.types.unit</code> instead of <code>Ty::new_unit(tcx)</code></a></li>
2418. <li><a href="https://github.com/rust-lang/rust/pull/124418">use a proof tree visitor to refine the <code>Obligation</code> for error reporting in new solver</a></li>
2419. <li><a href="https://github.com/rust-lang/miri/pull/3545">miri: /miri run: support -v flag to print what it is doing</a></li>
2420. <li><a href="https://github.com/rust-lang/miri/pull/3531">miri: don’t print <code>Preparing a sysroot</code> when <code>-q</code>/<code>--quiet</code> is passed</a></li>
2421. <li><a href="https://github.com/rust-lang/miri/pull/3551">miri: macos: use getentropy from libc</a></li>
2422. <li><a href="https://github.com/rust-lang/miri/pull/3533">miri: make file descriptors into refcount references</a></li>
2423. <li><a href="https://github.com/rust-lang/miri/pull/3548">miri: make many-seeds a mode of ./miri run rather than a separate command</a></li>
2424. <li><a href="https://github.com/rust-lang/miri/pull/3562">miri: only show the 'basic API common for this target' message when this is a missing foreign function</a></li>
2425. <li><a href="https://github.com/rust-lang/miri/pull/3564">miri: pthread shims: reorganize field offset handling, and add sanity checks</a></li>
2426. <li><a href="https://github.com/rust-lang/miri/pull/3570">miri: solaris: make pre-main code work</a></li>
2427. <li><a href="https://github.com/rust-lang/miri/pull/3560">miri: sync: better error in invalid synchronization primitive ID</a></li>
2428. <li><a href="https://github.com/rust-lang/miri/pull/3550">miri: tls dtors: treat all unixes uniformly</a></li>
2429. <li><a href="https://github.com/rust-lang/miri/pull/3532">miri: tree Borrows: first apply transition, then check protector with new 'initialized'</a></li>
2430. <li><a href="https://github.com/rust-lang/miri/pull/3568">miri: unix/thread: properly use <code>pthread_t</code> for thread IDs</a></li>
2431. <li><a href="https://github.com/rust-lang/rust/pull/124401">some hir cleanups</a></li>
2432. <li><a href="https://github.com/rust-lang/rust/pull/124459">stabilize <code>exclusive_range_pattern</code></a></li>
2433. <li><a href="https://github.com/rust-lang/rust/pull/124749">stabilize <code>exclusive_range_pattern</code> (v2)</a></li>
2434. <li><a href="https://github.com/rust-lang/rust/pull/124678">stabilize <code>split_at_checked</code></a></li>
2435. <li><a href="https://github.com/rust-lang/rust/pull/122441">improve several <code>Read</code> implementations</a></li>
2436. <li><a href="https://github.com/rust-lang/rust/pull/123850">add constants for f16 and f128</a></li>
2437. <li><a href="https://github.com/rust-lang/compiler-builtins/pull/593">compiler builtins for <code>f16</code>/<code>f128</code> float conversions</a></li>
2438. <li><a href="https://github.com/rust-lang/cargo/pull/13833">cargo lint: Warn not Error on unsupported lint tool</a></li>
2439. <li><a href="https://github.com/rust-lang/cargo/pull/13852">cargo lints: Prevent inheritance from bring exposed for published packages</a></li>
2440. <li><a href="https://github.com/rust-lang/cargo/pull/13837">cargo lints: Remove ability to specify <code>-</code> in lint name</a></li>
2441. <li><a href="https://github.com/rust-lang/cargo/pull/13791">cargo resolver: Treat unset MSRV as compatible</a></li>
2442. <li><a href="https://github.com/rust-lang/cargo/pull/13836">cargo toml: Don't lose 'public' when inheriting a dep</a></li>
2443. <li><a href="https://github.com/rust-lang/cargo/pull/13839">cargo toml: On 2024 Edition, disallow ignored <code>default-features</code> when inheriting</a></li>
2444. <li><a href="https://github.com/rust-lang/cargo/pull/13861">cargo toml: Remove unstable rejrected frontmatter syntax for cargo script</a></li>
2445. <li><a href="https://github.com/rust-lang/cargo/pull/13841">cargo toml: Validate <code>crates_types/proc-macro</code> for bin like others</a></li>
2446. <li><a href="https://github.com/rust-lang/cargo/pull/13849">cargo toml: Avoid inferring when targets are known</a></li>
2447. <li><a href="https://github.com/rust-lang/cargo/pull/13818">cargo clean package perf improvements</a></li>
2448. <li><a href="https://github.com/rust-lang/cargo/pull/13805">cargo: error when unstable lints are specified but not enabled</a></li>
2449. <li><a href="https://github.com/rust-lang/cargo/pull/13832">cargo: populate git information when building Cargo from Rust's source tarball</a></li>
2450. <li><a href="https://github.com/rust-lang/cargo/pull/13571">cargo: stabilize <code>-Zcheck-cfg</code> as always enabled</a></li>
2451. <li><a href="https://github.com/rust-lang/cargo/pull/13845">cargo: workaround copying file returning EAGAIN on ZFS on mac OS</a></li>
2452. <li><a href="https://github.com/rust-lang/rust/pull/124148">rustdoc-search: search for references</a></li>
2453. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12755">clippy: allow more attributes in <code>clippy::useless_attribute</code></a></li>
2454. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12742">clippy: don't lint <code>assigning_clones</code> on nested late init locals</a></li>
2455. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12687">clippy: don't suggest <code>Box::default()</code> in functions with differing generics</a></li>
2456. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12567">clippy: fix <code>FormatArgs</code> storage when <code>-Zthreads</code> > 1</a></li>
2457. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12515">clippy: fix <code>for x in y unsafe { }</code></a></li>
2458. <li><a href="https://github.com/rust-lang/rust-clippy/pull/11988">clippy: fix suggestion error for <code>manual_is_ascii_check</code> with missing type</a></li>
2459. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12745">clippy: suggest collapsing nested or patterns if the MSRV allows it</a></li>
2460. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12747">clippy: type safe CLI implementation for clippy-dev</a></li>
2461. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17138">rust-analyzer: make generate function assist generate a function as a constructor if the generated function has the name "new" and is an asscociated function</a></li>
2462. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17177">rust-analyzer: fix Run lens showing when lenses are disabled</a></li>
2463. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17176">rust-analyzer: fix impl trait params not being counted properly</a></li>
2464. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17172">rust-analyzer: correctly handle <code>no_core</code>/<code>no_std</code> for preludes</a></li>
2465. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17161">rust-analyzer: discard path when the path is invalid</a></li>
2466. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17175">rust-analyzer: fix implicit ty args being lowered where they shouldn't</a></li>
2467. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17160">rust-analyzer: implement creating generics for impl traits in associated types</a></li>
2468. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17190">rust-analyzer: lifetime's Bound Var Debrujin Index in Dyn Traits</a></li>
2469. </ul>
2470. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage">Rust Compiler Performance Triage</a></h5>
2471. <p>Largely uneventful week; the most notable shifts were considered false-alarms
2472. that arose from changes related to cfg-checking (either cargo enabling it, or
2473. adding cfg's like <code>rustfmt</code> to the "well-known cfgs list").</p>
2474. <p>Triage done by <strong>@pnkfelix</strong>.
2475. Revision range: <a href="https://perf.rust-lang.org/?start=c65b2dc935c27c0c8c3997c6e8d8894718a2cb1a&end=69f53f5e5583381267298ac182eb02c7f1b5c1cd&absolute=false&stat=instructions%3Au">c65b2dc9..69f53f5e</a></p>
2476. <p>3 Regressions, 2 Improvements, 3 Mixed; 5 of them in rollups
2477. 54 artifact comparisons made in total</p>
2478. <p><a href="https://github.com/rust-lang/rustc-perf/blob/6774c877ace0a2d9138b2b06ef0aabf6c2317a43/triage/2024-05-06.md">Full report here</a></p>
2479. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#approved-rfcs"></a><a href="https://github.com/rust-lang/rfcs/commits/master">Approved RFCs</a></h5>
2480. <p>Changes to Rust follow the Rust <a href="https://github.com/rust-lang/rfcs#rust-rfcs">RFC (request for comments) process</a>. These
2481. are the RFCs that were approved for implementation this week:</p>
2482. <ul>
2483. <li><a href="https://github.com/rust-lang/rfcs/pull/3325">Merge RFC 3325: Unsafe attributes</a></li>
2484. <li><a href="https://github.com/rust-lang/rfcs/pull/3593">Merge RFC 3593: Reserve unprefixed guarded strings</a></li>
2485. <li><a href="https://github.com/rust-lang/rfcs/pull/3606">Merge RFC 3606: Shorter temp lifetimes in tail exprs</a></li>
2486. <li><a href="https://github.com/rust-lang/rfcs/pull/3519">Merge RFC 3519: Arbitrary self types v2</a></li>
2487. </ul>
2488. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#final-comment-period">Final Comment Period</a></h5>
2489. <p>Every week, <a href="https://www.rust-lang.org/team.html">the team</a> announces the 'final comment period' for RFCs and key PRs
2490. which are reaching a decision. Express your opinions now.</p>
2491. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rfcs_1"></a><a href="https://github.com/rust-lang/rfcs/labels/final-comment-period">RFCs</a></h6>
2492. <ul>
2493. <li>[disposition: merge] <a href="https://github.com/rust-lang/rfcs/pull/3550">RFC: New range types for Edition 2024</a></li>
2494. <li>[disposition: merge] <a href="https://github.com/rust-lang/rfcs/pull/3502">RFC: cargo-script</a></li>
2495. </ul>
2496. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#tracking-issues-prs">Tracking Issues & PRs</a></h6>
2497. <a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust"></a><a href="https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc">Rust</a>
2498. <ul>
2499. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/116675">[ptr] Document maximum allocation size</a></li>
2500. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/122792">Stabilize <code>min_exhaustive_patterns</code></a></li>
2501. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124367">Fix #124275: Implemented Default for Arc<\str></a></li>
2502. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124532">elaborate obligations in coherence</a></li>
2503. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/issues/98485">Tracking Issue for <code>AtomicBool::fetch_not</code></a></li>
2504. </ul>
2505. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#new-and-updated-rfcs"></a><a href="https://github.com/rust-lang/rfcs/pulls">New and Updated RFCs</a></h6>
2506. <ul>
2507. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3629">Function body blocks</a></li>
2508. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3628"><code>async T</code> and <code>gen T</code> types</a></li>
2509. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3627">Match ergonomics 2024</a></li>
2510. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3626">Extend format_args implicit arguments to allow field access</a></li>
2511. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3624">Supertrait item shadowing v2</a></li>
2512. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3621">RFC: #[derive(SmartPointer)]</a></li>
2513. </ul>
2514. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#upcoming-events">Upcoming Events</a></h4>
2515. <p>Rusty Events between 2024-05-08 - 2024-06-05 🦀</p>
2516. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#virtual">Virtual</a></h5>
2517. <ul>
2518. <li>2024-05-09 | Virtual (Berlin, DE) | <a href="https://berline.rs/">OpenTechSchool Berlin</a> + <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
2519. <li><a href="https://meet.jit.si/RustHackAndLearnBerlin"><strong>Rust Hack and Learn</strong></a> | <a href="https://www.meetup.com/rust-berlin/events/298477697/"><strong>Mirror: Rust Hack n Learn Meetup</strong></a></li>
2520. </ul>
2521. </li>
2522. <li>2024-05-09 | Virtual (Israel) | <a href="https://rust.org.il/">Rust in Israel</a><ul>
2523. <li><a href="https://www.meetup.com/code-mavens/events/300144781/"><strong>Rust at Microsoft, Tel Aviv - Are we embedded yet?</strong></a></li>
2524. </ul>
2525. </li>
2526. <li>2024-05-09 | Virtual (Nuremberg/Nürnberg, DE) | <a href="https://www.meetup.com/rust-noris/">Rust Nuremberg</a><ul>
2527. <li><a href="https://www.meetup.com/rust-noris/events/297945257/"><strong>Rust Nürnberg online</strong></a></li>
2528. </ul>
2529. </li>
2530. <li>2024-05-10 | Virtual | <a href="https://www.eventbrite.com/o/training-4-programmers-llc-80387368983">Training 4 Programmers LLC</a><ul>
2531. <li><a href="https://www.eventbrite.com/e/rusts-safety-net-crafting-memory-safe-applications-tickets-881820838867"><strong>Rust's Safety Net: Crafting Memory-Safe Applications</strong></a></li>
2532. </ul>
2533. </li>
2534. <li>2024-05-10 | Virtual (Ankara, TR) | <a href="https://kommunity.com/turkiye-rust-community/events/">Türkiye Rust Community</a><ul>
2535. <li><a href="https://kommunity.com/turkiye-rust-community/events/rustsemineri-4-4c6c7276"><strong>#RustSemineri - 4</strong></a></li>
2536. </ul>
2537. </li>
2538. <li>2024-05-12 | Virtual (Bangalore, IN) | <a href="https://www.meetup.com/coderrange-endless-programming-languages/">CoderRange</a><ul>
2539. <li><a href="https://www.meetup.com/coderrange-endless-programming-languages/events/300692075/"><strong>Rust Lang : Live Experts Discussion & Case Studies</strong></a></li>
2540. </ul>
2541. </li>
2542. <li>2024-05-13 | Virtual (Ankara, TR) | <a href="https://kommunity.com/turkiye-rust-community/events/">Türkiye Rust Community</a><ul>
2543. <li><a href="https://kommunity.com/turkiye-rust-community/events/rustsemineri-5-119bbf68"><strong>#RustSemineri - 5</strong></a></li>
2544. </ul>
2545. </li>
2546. <li>2024-05-14 | Virtual | <a href="https://lecture.senfcall.de/hay-gmh-wox-mru">Rust for Lunch</a><ul>
2547. <li><a href="https://lecture.senfcall.de/hay-gmh-wox-mru"><strong>Rust for Lunch (May)</strong></a></li>
2548. </ul>
2549. </li>
2550. <li>2024-05-14 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/">Dallas Rust</a><ul>
2551. <li><a href="https://www.meetup.com/dallasrust/events/298341699/"><strong>Second Tuesday</strong></a></li>
2552. </ul>
2553. </li>
2554. <li>2024-05-14 | Virtual (Halifax, NS, CA) | <a href="https://www.meetup.com/rust-tell-halifax/">Rust Halifax</a><ul>
2555. <li><a href="https://www.meetup.com/rust-tell-halifax/events/300437775/"><strong>Rust&Tell - Halifax</strong></a></li>
2556. </ul>
2557. </li>
2558. <li>2024-05-14 | Virtual + In-Person (München/Munich, DE) | <a href="https://www.meetup.com/rust-munich/">Rust Munich</a><ul>
2559. <li><a href="https://www.meetup.com/rust-munich/events/298507657/"><strong>Rust Munich 2024 / 1 - hybrid (Rescheduled)</strong></a></li>
2560. </ul>
2561. </li>
2562. <li>2024-05-15 | Virtual (Ankara, TR) | <a href="https://kommunity.com/turkiye-rust-community/events/">Türkiye Rust Community</a><ul>
2563. <li><a href="https://kommunity.com/turkiye-rust-community/events/rustsemineri-7-0a97e784"><strong>#RustSemineri - 7</strong></a></li>
2564. </ul>
2565. </li>
2566. <li>2024-05-15 | Virtual (Cardiff, UK) | <a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/">Rust and C++ Cardiff</a><ul>
2567. <li><a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/events/300819214/"><strong>Rust for Rustaceans Book Club: Chapter 6 - Testing</strong></a></li>
2568. </ul>
2569. </li>
2570. <li>2024-05-15 | Virtual (Vancouver, BC, CA) | <a href="https://www.meetup.com/vancouver-rust/">Vancouver Rust</a><ul>
2571. <li><a href="https://www.meetup.com/vancouver-rust/events/298542331/"><strong>NativeLink</strong></a></li>
2572. </ul>
2573. </li>
2574. <li>2024-05-16 | Virtual (Ankara, TR) | <a href="https://kommunity.com/turkiye-rust-community/events">Türkiye Rust Community</a><ul>
2575. <li><a href="https://kommunity.com/turkiye-rust-community/events/rustsemineri-8-ddfe6b15"><strong>#RustSemineri - 8</strong></a></li>
2576. </ul>
2577. </li>
2578. <li>2024-05-16 | Virtual (Charlottesville, VA, US) | <a href="https://www.meetup.com/charlottesville-rust-meetup/">Charlottesville Rust Meetup</a><ul>
2579. <li><a href="https://www.meetup.com/charlottesville-rust-meetup/events/298312423/"><strong>Crafting Interpreters in Rust Collaboratively</strong></a></li>
2580. </ul>
2581. </li>
2582. <li>2024-05-17 | Virtual | <a href="https://www.eventbrite.com/o/training-4-programmers-llc-80387368983">Training 4 Programmers LLC</a><ul>
2583. <li><a href="https://www.eventbrite.com/e/rust-at-full-speed-harnessing-concurrency-with-confidence-tickets-884842296127"><strong>Rust at Full Speed: Harnessing Concurrency with Confidence</strong></a></li>
2584. </ul>
2585. </li>
2586. <li>2024-05-21 | Virtual (Washington, DC, US) | <a href="https://www.meetup.com/rustdc/">Rust DC</a><ul>
2587. <li><a href="https://www.meetup.com/rustdc/events/299346490/"><strong>Mid-month Rustful—forensic parsing via Artemis</strong></a></li>
2588. </ul>
2589. </li>
2590. <li>2024-05-23 | Virtual (Berlin, DE) | <a href="https://berline.rs/">OpenTechSchool Berlin</a> + <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
2591. <li><a href="https://meet.jit.si/RustHackAndLearnBerlin"><strong>Rust Hack and Learn</strong></a> | <a href="https://www.meetup.com/rust-berlin/events/298477699/"><strong>Mirror: Rust Hack n Learn Meetup</strong></a></li>
2592. </ul>
2593. </li>
2594. <li>2024-05-28 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/">Dallas Rust</a><ul>
2595. <li><a href="https://www.meetup.com/dallasrust/events/300533392/"><strong>Last Tuesday</strong></a></li>
2596. </ul>
2597. </li>
2598. <li>2024-05-30 | Virtual (Charlottesville, NC, US) | <a href="https://www.meetup.com/charlottesville-rust-meetup/">Charlottesville Rust Meetup</a><ul>
2599. <li><a href="https://www.meetup.com/charlottesville-rust-meetup/events/298542326/"><strong>Crafting Interpreters in Rust Collaboratively</strong></a></li>
2600. </ul>
2601. </li>
2602. <li>2024-06-04 | Virtual (Buffalo, NY) | <a href="https://www.meetup.com/buffalo-rust-meetup/">Buffalo Rust Meetup</a><ul>
2603. <li><a href="https://www.meetup.com/buffalo-rust-meetup/events/300191681/"><strong>Buffalo Rust User Group</strong></a></li>
2604. </ul>
2605. </li>
2606. </ul>
2607. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#africa">Africa</a></h5>
2608. <ul>
2609. <li>2024-06-01 | Kampala, UG | <a href="https://www.eventbrite.com/o/rust-circle-kampala-65249289033">Rust Circle Kampala</a><ul>
2610. <li><a href="https://www.eventbrite.com/e/rust-circle-meetup-tickets-628763176587"><strong>Rust Circle Meetup</strong></a></li>
2611. </ul>
2612. </li>
2613. </ul>
2614. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#asia">Asia</a></h5>
2615. <ul>
2616. <li>2024-05-11 | Bangalore, IN | <a href="https://hasgeek.com/rustbangalore">Rust Bangalore</a><ul>
2617. <li><a href="https://hasgeek.com/rustbangalore/may-2024-rustacean-meetup/"><strong>May 2024 Rustacean meetup</strong></a></li>
2618. </ul>
2619. </li>
2620. <li>2024-05-14 | Tokyo, JP | <a href="https://www.meetup.com/tokyo-rust-meetup/">Tokyo Rust Meetup</a><ul>
2621. <li><a href="https://www.meetup.com/tokyo-rust-meetup/events/300879432/"><strong>Wrapping C++ in Rust</strong></a></li>
2622. </ul>
2623. </li>
2624. </ul>
2625. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#europe">Europe</a></h5>
2626. <ul>
2627. <li>2024-05-08 | Cambridge, UK | <a href="https://www.meetup.com/cambridge-rust-meetup/">Cambridge Rust Meetup</a><ul>
2628. <li><a href="https://www.meetup.com/cambridge-rust-meetup/events/300573716/"><strong>Monthly Rust Meetup</strong></a></li>
2629. </ul>
2630. </li>
2631. <li>2024-05-09 | Gdańsk, PL | <a href="https://www.meetup.com/rust-gdansk/">Rust Gdansk</a><ul>
2632. <li><a href="https://www.meetup.com/rust-gdansk/events/299766774/"><strong>Rust Gdansk Meetup #2</strong></a></li>
2633. </ul>
2634. </li>
2635. <li>2024-05-14 | Copenhagen, DK | <a href="https://www.meetup.com/copenhagen-rust-community/">Copenhagen Rust Community</a><ul>
2636. <li><a href="https://www.meetup.com/copenhagen-rust-community/events/300898453/"><strong>Rust Hack Night #5: Beginner-friendly</strong></a></li>
2637. </ul>
2638. </li>
2639. <li>2024-05-14 | Lille, FR | <a href="https://www.meetup.com/meetup-group-zgphbyet/">Rust Lille</a><ul>
2640. <li><a href="https://www.meetup.com/meetup-group-zgphbyet/events/300776874/"><strong>Rust Lille #7: Creative Coding & Data Visualization !</strong></a></li>
2641. </ul>
2642. </li>
2643. <li>2024-05-14 | London, UK | <a href="https://www.meetup.com/rust-london-user-group/">Rust London User Group</a><ul>
2644. <li><a href="https://www.meetup.com/rust-london-user-group/events/300715979/"><strong>Rust Hack & Learn May 2024</strong></a></li>
2645. </ul>
2646. </li>
2647. <li>2024-05-14 | Virtual + In-Person (München/Munich, DE) | <a href="https://www.meetup.com/rust-munich/">Rust Munich</a><ul>
2648. <li><a href="https://www.meetup.com/rust-munich/events/298507657/"><strong>Rust Munich 2024 / 1 - hybrid (Rescheduled)</strong></a></li>
2649. </ul>
2650. </li>
2651. <li>2024-05-14 | Prague, CZ | <a href="https://www.meetup.com/rust-prague/">Rust Prague</a><ul>
2652. <li><a href="https://www.meetup.com/rust-prague/events/300566374/"><strong>Rust Meetup Prague (May 2024)</strong></a></li>
2653. </ul>
2654. </li>
2655. <li>2024-05-14 | Reading, UK | <a href="https://www.meetup.com/reading-rust-workshop/">Reading Rust Workshop</a><ul>
2656. <li><a href="https://www.meetup.com/reading-rust-workshop/events/299694474/"><strong>Reading Rust Meetup</strong></a></li>
2657. </ul>
2658. </li>
2659. <li>2024-05-16 | Augsburg, DE | <a href="https://www.meetup.com/rust-meetup-augsburg/">Rust Meetup Augsburg</a><ul>
2660. <li><a href="https://www.meetup.com/rust-meetup-augsburg/events/300174327/"><strong>Augsburg Rust Meetup #7</strong></a></li>
2661. </ul>
2662. </li>
2663. <li>2024-05-16 | Paris, FR | <a href="https://mobilizon.fr/@rust_paris">Rust Paris</a><ul>
2664. <li><a href="https://mobilizon.fr/events/14b51ccc-211f-400f-9615-707d9d871e78"><strong>Paris Rust Meetup #68</strong></a></li>
2665. </ul>
2666. </li>
2667. <li>2024-05-21 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus/">Rust Aarhus</a><ul>
2668. <li><a href="https://www.meetup.com/rust-aarhus/events/300307155/"><strong>Hack Night</strong></a></li>
2669. </ul>
2670. </li>
2671. <li>2024-05-21 | Zurich, CH | <a href="https://www.meetup.com/rust-zurich/">Rust Zurich</a><ul>
2672. <li><a href="https://www.meetup.com/rust-zurich/events/300513957/"><strong>Save the date - Mai Meetup</strong></a></li>
2673. </ul>
2674. </li>
2675. <li>2024-05-22 | Leiden, NL | <a href="https://www.meetup.com/freshminds-future-proof-software-development/">Future-proof Software Development by FreshMinds</a><ul>
2676. <li><a href="https://www.meetup.com/freshminds-future-proof-software-development/events/300566391/"><strong>Coding Dojo Session</strong></a></li>
2677. </ul>
2678. </li>
2679. <li>2024-05-23 | Bern, CH | <a href="https://www.meetup.com/de-DE/rust-bern/">Rust Bern</a><ul>
2680. <li><a href="https://www.meetup.com/rust-bern/events/300286917/"><strong>2024 Rust Talks Bern #2</strong></a></li>
2681. </ul>
2682. </li>
2683. <li>2024-05-23 | Łodz, PL | <a href="https://www.linkedin.com/posts/mobica_rust-programming-embeddedsoftware-activity-7193232853717946369-CK68/">Mobica</a><ul>
2684. <li><a href="https://www.interankiety.pl/f/b4D7G7xO"><strong>Zapisz się na warsztat Rust / Embedded w Łodzi! / What's all the fuss about Rust?</strong></a></li>
2685. </ul>
2686. </li>
2687. <li>2024-05-24 | Bordeaux, FR | <a href="https://www.meetup.com/bordeaux-rust/">Rust Bordeaux</a><ul>
2688. <li><a href="https://www.meetup.com/bordeaux-rust/events/300723854/"><strong>Rust Bordeaux #3: Discussions</strong></a></li>
2689. </ul>
2690. </li>
2691. <li>2024-05-28 - 2024-05-30 | Berlin, DE | <a href="https://oxidizeconf.com/">Oxidize</a><ul>
2692. <li><a href="https://oxidizeconf.com/"><strong>Oxidize Conf 2024</strong></a></li>
2693. </ul>
2694. </li>
2695. <li>2024-05-30 | Barcelona, ES | <a href="https://www.meetup.com/bcnrust/">BcnRust</a><ul>
2696. <li><a href="https://www.meetup.com/bcnrust/events/300765894/"><strong>Rust for the web</strong></a></li>
2697. </ul>
2698. </li>
2699. <li>2024-05-30 | Berlin, DE | <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
2700. <li><a href="https://www.meetup.com/rust-berlin/events/299288963/"><strong>Rust and Tell - Title</strong></a></li>
2701. </ul>
2702. </li>
2703. <li>2024-05-30 | Copenhagen, DK | <a href="https://www.meetup.com/copenhagen-rust-community">Copenhagen Rust Community</a><ul>
2704. <li><a href="https://www.meetup.com/copenhagen-rust-community/events/300458222/"><strong>Rust meetup #47 sponsored by Microsoft!</strong></a></li>
2705. </ul>
2706. </li>
2707. <li>2024-05-30 | Oslo, NO | <a href="https://www.meetup.com/rust-oslo/events/">Rust Oslo</a><ul>
2708. <li><a href="https://www.meetup.com/rust-oslo/events/300453310/"><strong>Rust Hack'n'Learn at Kampen Bistro</strong></a></li>
2709. </ul>
2710. </li>
2711. </ul>
2712. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#north-america">North America</a></h5>
2713. <ul>
2714. <li>2024-05-08 | Detroit, MI, US | <a href="https://www.meetup.com/detroitrust/">Detroit Rust</a><ul>
2715. <li><a href="https://www.meetup.com/detroitrust/events/300763859/"><strong>Rust Social - Ann Arbor</strong></a></li>
2716. </ul>
2717. </li>
2718. <li>2024-05-09 - 2024-05-10 | Estes Park, CO, US | <a href="https://www.meetup.com/hackathons-denver/">Hackathons Denver</a><ul>
2719. <li><a href="https://www.meetup.com/hackathons-denver/events/300370255/"><strong>Lambda Conf 2024: Rust Workshop by John A. De Goes</strong></a></li>
2720. </ul>
2721. </li>
2722. <li>2024-05-09 | Lehi, UT, US | <a href="https://www.meetup.com/utah-rust/">Utah Rust</a><ul>
2723. <li><a href="https://www.meetup.com/utah-rust/events/300782766/"><strong>Writing and deploying a simple multi-threaded web backend</strong></a></li>
2724. </ul>
2725. </li>
2726. <li>2024-05-09 | Spokane, WA, US | <a href="https://www.meetup.com/spokane-rust/">Spokane Rust</a><ul>
2727. <li><a href="https://www.meetup.com/spokane-rust/events/300020003/"><strong>Monthly Meetup: Topic TBD!</strong></a></li>
2728. </ul>
2729. </li>
2730. <li>2024-05-12 | Brookline, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
2731. <li><a href="https://www.meetup.com/bostonrust/events/300116747/"><strong>Coolidge Corner Brookline Rust Lunch, May 12</strong></a></li>
2732. </ul>
2733. </li>
2734. <li>2024-05-14 | Minneapolis, MN, US | <a href="https://www.meetup.com/minneapolis-rust-meetup/">Minneapolis Rust Meetup</a><ul>
2735. <li><a href="https://www.meetup.com/minneapolis-rust-meetup/events/300744140/"><strong>Minneapolis Rust Meetup Happy Hour</strong></a></li>
2736. </ul>
2737. </li>
2738. <li>2024-05-14 | New York, NY, US | <a href="https://www.meetup.com/rust-nyc/">Rust NYC</a><ul>
2739. <li><a href="https://www.meetup.com/rust-nyc/events/300818688/"><strong>Rust NYC Monthly Meetup</strong></a></li>
2740. </ul>
2741. </li>
2742. <li>2024-05-16 | Mountain View, CA, US | <a href="https://www.meetup.com/mv-rust-meetup/">Mountain View Rust Meetup</a><ul>
2743. <li><a href="https://www.meetup.com/mv-rust-meetup/events/300775539/"><strong>Rust Meetup at Hacker Dojo</strong></a></li>
2744. </ul>
2745. </li>
2746. <li>2024-05-16 | Seattle, WA, US | <a href="https://www.meetup.com/seattle-rust-user-group/">Seattle Rust User Group</a><ul>
2747. <li><a href="https://www.meetup.com/seattle-rust-user-group/events/299509369/"><strong>Seattle Rust User Group Meetup</strong></a></li>
2748. </ul>
2749. </li>
2750. <li>2024-05-20 | Somerville, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
2751. <li><a href="https://www.meetup.com/bostonrust/events/300116765/"><strong>Ball Square Rust Lunch, May 20</strong></a></li>
2752. </ul>
2753. </li>
2754. <li>2024-05-21 | San Francisco, CA, US | <a href="https://www.meetup.com/san-francisco-rust-study-group/">San Francisco Rust Study Group</a><ul>
2755. <li><a href="https://www.meetup.com/san-francisco-rust-study-group/events/299186931/"><strong>Rust Hacking in Person</strong></a></li>
2756. </ul>
2757. </li>
2758. <li>2024-05-22 | Austin, TX, US | <a href="https://www.meetup.com/rust-atx/">Rust ATX</a><ul>
2759. <li><a href="https://www.meetup.com/rust-atx/events/xvkdgtygchbdc/"><strong>Rust Lunch - Fareground</strong></a></li>
2760. </ul>
2761. </li>
2762. <li>2024-05-25 | Chicago, IL, US | <a href="https://www.meetup.com/deep-dish-rust/">Deep Dish Rust</a><ul>
2763. <li><a href="https://www.meetup.com/deep-dish-rust/events/300665520/"><strong>Rust Talk Double Feature</strong></a></li>
2764. </ul>
2765. </li>
2766. <li>2024-05-30 | Mountain View, CA, US | <a href="https://www.meetup.com/mv-rust-meetup/">Mountain View Rust Meetup</a><ul>
2767. <li><a href="https://www.meetup.com/mv-rust-meetup/events/300775547/"><strong>Rust Meetup at Hacker Dojo</strong></a></li>
2768. </ul>
2769. </li>
2770. <li>2024-05-31 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
2771. <li><a href="https://www.meetup.com/bostonrust/events/300116786/"><strong>Boston Common Rust Lunch, May 31</strong></a></li>
2772. </ul>
2773. </li>
2774. <li>2024-06-05 | Hamburg, DE | <a href="https://www.meetup.com/rust-meetup-hamburg/">Rust Meetup Hamburg</a><ul>
2775. <li><a href="https://www.meetup.com/rust-meetup-hamburg/events/299235215/"><strong>Rust Hack & Learn June 2024</strong></a></li>
2776. </ul>
2777. </li>
2778. </ul>
2779. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#oceania">Oceania</a></h5>
2780. <ul>
2781. <li>2024-05-28 | Sydney, NSW, AU | <a href="https://www.meetup.com/rust-sydney/">Rust Sydney</a><ul>
2782. <li><a href="https://www.meetup.com/rust-sydney/events/300854266/"><strong>a demo 🤯 & a lightning ⚡show ✨</strong></a></li>
2783. </ul>
2784. </li>
2785. </ul>
2786. <p>If you are running a Rust event please add it to the <a href="https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com">calendar</a> to get
2787. it mentioned here. Please remember to add a link to the event too.
2788. Email the <a href="mailto:community-team@rust-lang.org">Rust Community Team</a> for access.</p>
2789. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#jobs">Jobs</a></h4>
2790.  
2791.  
2792. <p>Please see the latest <a href="https://www.reddit.com/r/rust/comments/1cixuzr/official_rrust_whos_hiring_thread_for_jobseekers/">Who's Hiring thread on r/rust</a></p>
2793. <h3><a class="toclink" href="http://this-week-in-rust.org/atom.xml#quote-of-the-week">Quote of the Week</a></h3>
2794. <blockquote>
2795. <p>Rust and its borrow checker are like proper form when lifting boxes. While you might have been lifting boxes "the natural way" for decades without a problem, and its an initial embuggerance to think and perform proper lifting form, it is learnable, efficient, and prevents some important problems.</p>
2796. <p>Or more succinctly:<br />
2797. C/C++: It'll screw your back(end).</p>
2798. </blockquote>
2799. <p>And the reply:</p>
2800. <blockquote>
2801. <ol>
2802. <li>there’s a largish group of men who would feel their masculinity attacked if you implied they should learn it</li>
2803. <li>while it's learnable finding usefully targeted educational resources are hard to come by</li>
2804. <li>proper form while lifting boxes are a really terrible way to model graphs</li>
2805. </ol>
2806. </blockquote>
2807. <p>– <a href="https://mstdn.social/@brettwitty/111734369720814683">Brett Witty and Leon on Mastodon</a></p>
2808. <p>Thanks to <a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328/1566">Brett Witty</a> for the self-suggestion!</p>
2809. <p><a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328">Please submit quotes and vote for next week!</a></p>
2810. <p><em>This Week in Rust is edited by: <a href="https://github.com/nellshamrell">nellshamrell</a>, <a href="https://github.com/llogiq">llogiq</a>, <a href="https://github.com/cdmistman">cdmistman</a>, <a href="https://github.com/ericseppanen">ericseppanen</a>, <a href="https://github.com/extrawurst">extrawurst</a>, <a href="https://github.com/andrewpollack">andrewpollack</a>, <a href="https://github.com/U007D">U007D</a>, <a href="https://github.com/kolharsam">kolharsam</a>, <a href="https://github.com/joelmarcey">joelmarcey</a>, <a href="https://github.com/mariannegoldin">mariannegoldin</a>, <a href="https://github.com/bennyvasquez">bennyvasquez</a>.</em></p>
2811. <p><em>Email list hosting is sponsored by <a href="https://foundation.rust-lang.org/">The Rust Foundation</a></em></p>
2812. &lt;p&gt;&lt;small&gt;&lt;a href=&quot;https://www.reddit.com/r/rust/comments/1cnn8dh/this_week_in_rust_546/&quot;&gt;Discuss on r/rust&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;</description>
2813. <pubDate>Wed, 08 May 2024 04:00:00 +0000</pubDate>
2814. <dc:creator>TWiR Contributors</dc:creator>
2815. </item>
2816. <item>
2817. <title>Mozilla Addons Blog: Developer Spotlight: Port Authority</title>
2818. <guid isPermaLink="false">https://blog.mozilla.org/addons/?p=9169</guid>
2819. <link>https://blog.mozilla.org/addons/2024/05/07/developer-spotlight-port-authority/</link>
2820. <description>&lt;div class=&quot;wp-caption alignleft&quot; id=&quot;attachment_9170&quot; style=&quot;width: 334px;&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-9170&quot; height=&quot;590&quot; src=&quot;https://blog.mozilla.org/addons/files/2024/05/blog_PA.png&quot; width=&quot;324&quot; /&gt;&lt;p class=&quot;wp-caption-text&quot; id=&quot;caption-attachment-9170&quot;&gt;Port Authority gives you intuitive control over global block settings, notifications, and allow-list customization.&lt;/p&gt;&lt;/div&gt;
2821. <p>A few years ago a developer known as <a href="https://github.com/ACK-J" rel="noopener" target="_blank">ACK-J</a> stumbled onto a tech article that revealed eBay was secretly port scanning their customers (i.e. scanning their users’ internet-facing devices to learn what apps and services are listening on the network). The article further claimed there was nothing anyone could do to prevent this privacy compromise. ACK-J took that as a challenge. “After going down many rabbit holes,” he says, “I found that this script, which was port scanning everyone, is in my opinion, malware.”</p>
2822. <p>We spoke with ACK-J to better understand the obscure privacy risks of port scanning and how his extension <a href="https://addons.mozilla.org/en-US/firefox/addon/port-authority/" rel="noopener" target="_blank">Port Authority</a> offers unique protections.</p>
2823. <p><b>Why does port scanning present a privacy risk?</b></p>
2824. <p>ACK-J: <i>There is a common misconception/ignorance around how far websites are able to peer into your private home network. While modern browsers limit this to an extent, it is still overly permissive in my opinion. The privacy implications arise when websites, such as</i> <i>g</i><i>o</i><i>ogle.com</i><i>, have the ability to secretly interact with your router’s administrative interface, local services running on your computer and discover devices on your home network. This behavior should be blocked by the same-origin policy (SOP), a fundamental security mechanism built into every web browser since the mid 1990’s, however due to convenience it appears to be disabled for these requests. This caught a lot of people by surprise, including myself, and is why I wanted to make this type of traffic “opt-in” on my devices.</i></p>
2825. <p><b>Do you consider port scanning “malware”? </b></p>
2826. <p>ACK-J: <i>I don’t necessarily consider port scanning malware, port scanning is commonplace and should be expected for any computer connected to the internet with a public IP address. On the other hand, devices on our home networks do not have public IP addresses and instead are protected from this scanning due to a technology called network address translation (NAT). Due to the nature of how browsers and websites work, the website code needs to be rendered on the user’s device (behind the protections put in place by NAT). This means websites are in a privileged position to communicate with devices on your home network (e.g. IOT devices, routers, TVs, etc.). There are certainly legitimate use cases for port scanning even on internal networks, the most common being communicating with a program running on your PC such as Discord. I prefer to be able to explicitly allow this type of behavior instead of leaving it wide open by default.</i></p>
2827. <p><b>Is there a way to summarize how your extension addresses the privacy leak of port scanning?</b></p>
2828. <p>ACK-J: <i>Port Authority acts in a similar manner to a bouncer at a bar, whenever your computer tries to make a request, Port Authority will verify that the request is not trying to port scan your private network. If the request passes the check it is allowed in and everything functions as normal. If it fails the request is dropped. This all happens in a matter of milliseconds, but if a request is blocked you will get a notification.</i></p>
2829. <p><b>Should Port Authority users expect occasional disruptions using websites that port scan, like eBay?</b></p>
2830. <p>ACK-J: <i>Nope, I’ve been using it for years along with many friends, family, and 1,000 other daily users. I’ve never received a single report that a website would not allow you to login, check-out, or other expected functionality due to the extension blocking port scans. There are instances where you’d like your browser to communicate with an app on your PC such as Discord, in this case you’ll receive an alert and could add Discord to an allow-list or simply click the “Blocking” toggle to disable blocking temporarily.</i></p>
2831. <p><b>Do you see Port Authority growing in terms of a feature set, or do you feel it’s relatively feature complete and your focus is on maintenance/refinement?</b></p>
2832. <p>ACK-J: <i>I like extensions that serve a specific purpose so I don’t see it growing in features but I’d never say never. I’ve added an allow-list to explicitly permit certain domains to interact with services on your private network. I haven’t enabled this feature on the public extension yet but will soon.</i></p>
2833. <p><b>Apart from Port Authority, do you have any plans to develop other extensions?</b></p>
2834. <p>ACK-J: <i>I actually do! I just finished writing up an extension called MailFail that checks the website you are on for misconfigurations in their email server that would allow someone to spoof emails using their domain. This will be posted soon!</i></p>
2835. <hr />
2836. <p><i>Do you have an intriguing extension development story? Do tell! Maybe your story should appear on this blog. Contact us at </i><b><i>amo-featured [at] mozilla [dot] org</i></b><i> and let us know a bit about your extension development journey. </i></p>
2837. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/addons/2024/05/07/developer-spotlight-port-authority/&quot;&gt;Developer Spotlight: Port Authority&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>
2838. <pubDate>Tue, 07 May 2024 16:44:38 +0000</pubDate>
2839. <dc:creator>Scott DeVaney</dc:creator>
2840. </item>
2841. <item>
2842. <title>Firefox Developer Experience: Firefox DevTools Newsletter — 125</title>
2843. <guid isPermaLink="false">https://fxdx.dev/?p=249</guid>
2844. <link>https://fxdx.dev/firefox-devtools-newsletter-125/</link>
2845. <description>&lt;p id=&quot;block-42a3529c-86fa-43e3-a037-427905914805&quot;&gt;&lt;em&gt;Developer Tools help developers write and debug websites on Firefox. This newsletter gives an overview of the work we’ve done as part of the Firefox 125 Nightly release cycle.&lt;/em&gt;&lt;/p&gt;
2846.  
2847.  
2848.  
2849. <p id="block-af771a18-b7d9-4c63-9879-0a4a0dd015b4">Firefox being an open source project, we are grateful to get contributions from people outside of Mozilla, like <a href="https://bugzilla.mozilla.org/user_profile?user_id=750915">Artem Manushenkov</a> who updated the Debugger Watch Expressions panel input field placeholder (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1619201">#1619201</a>)</p>
2850.  
2851.  
2852.  
2853. <p class="has-text-align-center has-background-secondary-background-color has-background" id="block-9944af63-0ae5-4c30-a32d-8ebfda4b5527">Want to help? DevTools are written in HTML, CSS and JS so any web developer can contribute! Read <a href="https://firefox-source-docs.mozilla.org/devtools/getting-started/README.html">how to setup the work environment</a> and check <a href="https://codetribute.mozilla.org/projects/devtools">the list of mentored issues</a></p>
2854.  
2855.  
2856.  
2857. <h3>Pop it up!</h3>
2858.  
2859.  
2860.  
2861. <p>Firefox 125 adds support for the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Popover_API">Popover API</a>, which is now supported across all major browsers <img alt="🎉" class="wp-smiley" src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f389.png" style="height: 1em;" />. As said on the related MDN page:</p>
2862.  
2863.  
2864.  
2865. <blockquote class="wp-block-quote">
2866. <p>The <strong>Popover API</strong> provides developers with a standard, consistent, flexible mechanism for displaying popover content on top of other page content. Popover content can be controlled either declaratively using HTML attributes, or via JavaScript.</p>
2867. </blockquote>
2868.  
2869.  
2870.  
2871. <p>In HTML, popover elements can be declared with a <code>popover</code> attribute. The popover can then be toggled from a button element which specifies a <code>popovertarget</code> attribute referencing the id of the popover element.</p>
2872.  
2873.  
2874.  
2875. <p><br /></p>
2876.  
2877.  
2878.  
2879. <figure class="wp-block-image aligncenter size-large"><img alt="Firefox DevTools Inspector markup view. We can see a button with a popovertarget attribute and next to it a "select element" button. A div element with a popover attribute is displayed as well" class="wp-image-277" height="160" src="https://fxdx.dev/files/2024/05/CleanShot-2024-05-07-at-16.18.24-600x160.png" width="600" /><figcaption class="wp-element-caption">Inspector displayed on <a href="https://mdn.github.io/dom-examples/popover-api/blur-background/">https://mdn.github.io/dom-examples/popover-api/blur-background/</a></figcaption></figure>
2880.  
2881.  
2882.  
2883. <p>In the Inspector markup view, an icon is displayed next to the <code>popovertarget</code> attribute so you can quickly jump to the popover element.<br />Popover element can be toggled in Javascript <code>HTMLElement.showPopover</code>, <code>HTMLElement.hidePopover</code> and <code>HTMLElement.</code><br /><code>togglePopover</code>. <code>beforetoggle</code> and <code>toggle</code> elements are fired when a popover element is toggled, and the Debugger provides those events in <a href="https://firefox-source-docs.mozilla.org/devtools-user/debugger/set_event_listener_breakpoints/index.html">the Event Listeners Breakpoints panel</a>.</p>
2884.  
2885.  
2886.  
2887. <p class="has-background-secondary-background-color has-background">Note that we don’t display <code>::backdrop</code> pseudo-element rules yet, but will be soon (target is Firefox 127, see <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1893644">#1893644</a>)<br /></p>
2888.  
2889.  
2890.  
2891. <h3>Performance</h3>
2892.  
2893.  
2894.  
2895. <p>As announced in <a href="https://fxdx.dev/firefox-devtools-newsletter-124/">the last newsletter</a>, we’re focusing on performance for a few months to provide a fast and snappy experience to our beloved users. We’re happy to report that the Style Editor panel is now up to <strong>20% faster</strong> to open (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884072">#1884072</a>).</p>
2896.  
2897.  
2898.  
2899. <p></p>
2900.  
2901.  
2902.  
2903. <figure class="wp-block-image aligncenter size-large"><img alt="Chart where x is the time and y is duration, where we can see the values going from 750ms to 600ms around March 14th" class="wp-image-274" height="176" src="https://fxdx.dev/files/2024/05/CleanShot-2024-05-07-at-14.58.50-600x176.png" width="600" /><figcaption class="wp-element-caption">Performance test duration going from ~750ms  to ~600ms</figcaption></figure>
2904.  
2905.  
2906.  
2907. <p>We also improved the Debugger opening when a page contains a lot of Javascript sources (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1880809">#1880809</a>). In a specific case, we could spend around <strong>9 whole seconds</strong> to process the different sources and populate the sources tree (<a href="https://share.firefox.dev/3y1eIAr">see the 124 Firefox profile</a>). In 125, it now only take a bit more than <strong>600 milliseconds</strong>, meaning <strong>it’s now 14 times faster</strong> (<a href="https://share.firefox.dev/3UyPwZS">see the 125 Firefox profile</a>).<br /></p>
2908.  
2909.  
2910.  
2911. <figure class="wp-block-image aligncenter size-large"><img alt="Firefox Profiler Flame chart screenshot for the same function, on Firefox 124 and 125." class="wp-image-275" height="212" src="https://fxdx.dev/files/2024/05/CleanShot-2024-05-07-at-15.26.29-600x212.png" width="600" /></figure>
2912.  
2913.  
2914.  
2915. <p>This also shows up on less extreme cases: our performance tests reported an average of 3% improvement on Debugger opening.</p>
2916.  
2917.  
2918.  
2919. <h3>Debugger</h3>
2920.  
2921.  
2922.  
2923. <p>There is now a button indicating if the opened file is an original file or a bundle, or if there was an issue when trying to retrieve the Source Map file  (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1853899">#1853899</a>).</p>
2924.  
2925.  
2926.  
2927. <figure class="wp-block-image aligncenter size-large"><img alt="Firefox debugger with a tsx file opened. At the bottom of the file text, there a button saying "original file". A popup menu is opened and has the following items: - Enable Source Maps - Show and open original location by default - Jump to the related original source - Open the Source Map file in a new tab" class="wp-image-276" height="409" src="https://fxdx.dev/files/2024/05/CleanShot-2024-05-07-at-15.42.30-600x409.png" width="600" /></figure>
2928.  
2929.  
2930.  
2931. <p>Clicking on the button opens a menu dedicated to Source Map, where you can:</p>
2932.  
2933.  
2934.  
2935. <ul>
2936. <li>enable or disable Source Map</li>
2937.  
2938.  
2939.  
2940. <li>indicate if the Debugger should open original files by default</li>
2941.  
2942.  
2943.  
2944. <li>select the related original/bundle source</li>
2945.  
2946.  
2947.  
2948. <li>open the <code>.map</code> file in a new Firefox tab</li>
2949. </ul>
2950.  
2951.  
2952.  
2953. <p>We also fixed a glitch around text selection and line highlighting (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1878698">#1878698</a>), as well as an issue which was preventing the Outline panel to work properly (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1879322">#1879322</a>). Finally we added back the preference that allows to disable the paused debugger overlay (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1865439">#1865439</a>). If you want to do so, go to <code>about:config</code> , search for <code>devtools.debugger.features.overlay</code> and toggle it to <code>false</code>.</p>
2954.  
2955.  
2956.  
2957. <h3>Miscellaneous</h3>
2958.  
2959.  
2960.  
2961. <ul>
2962. <li>CSP error messages in the Console now provide the effective directive (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1848315">#1848315</a>)</li>
2963.  
2964.  
2965.  
2966. <li><code>Infinity</code> wasn’t visible in the Console auto-completion menu (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1698260">#1698260</a>)</li>
2967.  
2968.  
2969.  
2970. <li>Clicking on a relative URL of an image in the Inspector now honor the document’s base URL (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1871391">#1871391</a>)</li>
2971.  
2972.  
2973.  
2974. <li>An issue that could provoke crashes of the Network Monitor is now fixed  (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884571">#1884571</a>)</li>
2975. </ul>
2976.  
2977.  
2978.  
2979. &lt;p class=&quot;has-text-align-center&quot;&gt;&lt;strong&gt;Thank you for reading this and using our tools, see you in a few weeks for a new round of updates &lt;img alt=&quot;🙂&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/14.0.0/72x72/1f642.png&quot; style=&quot;height: 1em;&quot; /&gt;&lt;/strong&gt;&lt;/p&gt;</description>
2980. <pubDate>Tue, 07 May 2024 14:56:57 +0000</pubDate>
2981. <dc:creator>Nicolas Chevobbe</dc:creator>
2982. </item>
2983. <item>
2984. <title>The Rust Programming Language Blog: Rust participates in OSPP 2024</title>
2985. <guid isPermaLink="true">https://blog.rust-lang.org/2024/05/07/OSPP-2024.html</guid>
2986. <link>https://blog.rust-lang.org/2024/05/07/OSPP-2024.html</link>
2987. <description>&lt;p&gt;Similar to our &lt;a href=&quot;https://blog.rust-lang.org/2024/02/21/Rust-participates-in-GSoC-2024.html&quot;&gt;previous&lt;/a&gt; &lt;a href=&quot;https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html&quot;&gt;announcements&lt;/a&gt; of the Rust Project's participation in Google Summer of Code (GSoC), we are now announcing our participation in &lt;a href=&quot;https://summer-ospp.ac.cn/&quot;&gt;Open Source Promotion Plan (OSPP) 2024&lt;/a&gt;.&lt;/p&gt;
2988. <p>OSPP is a program organized in large part by The Institute of Software Chinese Academy of Sciences. Its goal is to encourage college students to participate in developing and maintaining open source software. The Rust Project is <a href="https://summer-ospp.ac.cn/org/orgdetail/11769be7-d00a-4931-be95-13595ac181e4?lang=en">already registered</a> and has a number of projects available for mentorship:</p>
2989. <ul>
2990. <li><a href="https://summer-ospp.ac.cn/org/prodetail/241170274">C codegen backend for rustc</a></li>
2991. <li><a href="https://summer-ospp.ac.cn/org/prodetail/241170275">Extend annotate-snippets with features required by rustc</a></li>
2992. <li><a href="https://summer-ospp.ac.cn/org/prodetail/241170277">Improve bootstrap</a></li>
2993. <li><a href="https://summer-ospp.ac.cn/org/prodetail/241170528">Modernize the libc crate</a></li>
2994. <li><a href="https://summer-ospp.ac.cn/org/prodetail/241170529">Improve infrastructure automation tools</a></li>
2995. </ul>
2996. <p>Eligibility is limited to students and there is a <a href="https://summer-ospp.ac.cn/help/en/student/">guide</a> for potential participants. Student registration ends on the 3rd of June with the project application deadline a day later.</p>
2997. <p>Unlike GSoC which allows students to propose their own projects, OSPP requires that students only apply for one of the registered projects. We do have an <a href="https://rust-lang.zulipchat.com/#narrow/stream/436418-ospp">#ospp</a> Zulip stream and potential contributors are encouraged to join and discuss details about the projects and connect with mentors.</p>
2998. <p>After the project application window closes on June 4th, we will review and select participants, which will be announced on June 26th. From there, students will participate through to the end of September.</p>
2999. &lt;p&gt;As with GSoC, this is our first year participating in this program. We are incredibly excited for this opportunity to further expand into new open source communities and we're hopeful for a productive and educational summer.&lt;/p&gt;</description>
3000. <pubDate>Tue, 07 May 2024 00:00:00 +0000</pubDate>
3001. <dc:creator>Amanieu d'Antras, Jack Huey, and Jakub Beránek</dc:creator>
3002. </item>
3003. <item>
3004. <title>Support.Mozilla.Org: Make your support articles pop: Use the new Firefox Desktop Icon Gallery</title>
3005. <guid isPermaLink="false">https://blog.mozilla.org/sumo/?p=4118</guid>
3006. <link>https://blog.mozilla.org/sumo/2024/05/06/make-your-support-articles-pop-use-the-new-firefox-desktop-icon-gallery/</link>
3007. <description>&lt;p&gt;Hello, SUMO community!&lt;/p&gt;
3008. <p>We’re thrilled to roll out a new tool designed specifically for our contributors: the<a href="https://support.mozilla.org/en-US/kb/icon-gallery-firefox-desktop"> <b>Firefox Desktop Icon Gallery</b></a>. This gallery is crafted for quick access and is a key part of our strategy to<a href="https://blog.mozilla.org/sumo/2024/04/09/keeping-you-in-the-loop-whats-new-in-our-knowledge-base/?_gl=1*jjsqcb*_ga*NjcyOTQ2NzYxLjE2ODc5NTkxOTc.*_ga_2VC139B3XV*MTcxNDc1MTE0Mi4yNjkuMS4xNzE0NzUxMTQzLjAuMC4w"> reduce cognitive load</a> in our Knowledge Base content. By providing a range of inline icons that accurately depict interface elements of Firefox Desktop, this resource makes it easier for readers to follow along without overwhelming visual information.</p>
3009. <p><b>We want your feedback!</b> Join the conversation in our<a href="https://support.mozilla.org/en-US/forums/contributors/716947?last=87495"> SUMO forum thread</a> to ask questions or suggest new icons. Your feedback is crucial for improving this tool.</p>
3010. <p>Thanks for helping us support the Firefox community. We can’t wait to see how you use these new icons to enrich our Knowledge Base!</p>
3011. <p>Stay engaged and keep rocking the helpful web!</p>
3012. &lt;p&gt; &lt;/p&gt;</description>
3013. <pubDate>Mon, 06 May 2024 15:14:56 +0000</pubDate>
3014. <dc:creator>Lucas Siebert</dc:creator>
3015. </item>
3016. <item>
3017. <title>The Mozilla Blog: Julia Janssen creates art to be an ambassador for data protection</title>
3018. <guid isPermaLink="false">https://blog.mozilla.org/?p=74678</guid>
3019. <link>https://blog.mozilla.org/en/internet-culture/julia-janssen-data-protection-privacy-rise-25-mozilla-ai/</link>
3020. <description>&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;
3021.  
3022. </div></figure>
3023.  
3024.  
3025.  
3026. <p><em>At Mozilla, we know we can’t create a better future alone, that is why each year we will be highlighting the work of 25 digital leaders using technology to amplify voices, effect change, and build new technologies globally through our <a href="https://rise25.mozilla.org/?_gl=1*585km0*_ga*MTY1MDQ4MTg2NC4xNjk5NDc0NTE5*_ga_X4N05QV93S*MTcwNzE4MDk3Ny40NC4wLjE3MDcxODA5NzcuMC4wLjA." rel="noreferrer noopener" target="_blank">Rise 25 Awards.</a> These storytellers, innovators, activists, advocates, builders and artists are helping make the internet more diverse, ethical, responsible and inclusive.</em></p>
3027.  
3028.  
3029.  
3030. <p><em>This week, we chatted with <a href="https://studiojuliajanssen.com/">Julia Janssen</a>, an artist making our digital society’s challenges of data and AI tangible through the form of art. We talked with Julia about what sparked her passion for art, her experience in art school, traveling the world, generative AI and more.</em></p>
3031.  
3032.  
3033.  
3034. <p><strong>I’m always curious to ask artists what initially sparked their interest early in their lives, or just in general, what sparked their interest in the art that they do. How was that for you?</strong></p>
3035.  
3036.  
3037.  
3038. <p>Janssen: Well, it’s actually quite an odd story, because when I was 15 years old, and I was in high school — at the age of 15, you have to choose the kind of the courses or the direction of your classes, — and I chose higher mathematics and art history, both as substitute classes. And I remember my counselor asked me to his office and said, “why?” Like, “why would you do that like? Difficult mathematics and art and art history has nothing to do with each other.” I just remember saying, like, “Well, I think both are fun,” but also, for me, art is a way to understand mathematics and mathematics is for me a way to make art. I think at an early age, I kind of noticed that it was both of my interests. </p>
3039.  
3040.  
3041.  
3042. <p>So I started graphic design at an art academy. I also did a lot of different projects around kind of our relationship with technology, using a lot of mathematics to create patterns or art or always calculating things. And I never could kind of grasp a team or the fact that technology was something I was so interested in, but at graduation in 2016, it kind of all clicked together. It all kind of fell into place. When I started reading a lot of books about data ownership rights and early media theories, I was like, “what the hell is happening? Why aren’t we all constantly so concerned about our data? These big corporations are monetizing our attention. We’re basically kind of enslaved by this whole data industry.” It’s insane what’s happening, why is everybody not worried about this?” So, I made my first artwork during my graduation about this. And looking back at the time, I noticed that’s a lot of work during art school was already kind of understanding this — for example, things like terms and conditions. I did a Facebook journal where it was kind of a news anchor of a newsroom, reading out loud timelines and all these things. So I think it was already present in my work, but in 2016, it all kind of clicked together. And from there, things happened.</p>
3043.  
3044.  
3045.  
3046. <p><strong>I found that I learned so much more by actually being in the field and actually doing internships, etc. during college instead of just sitting in the classroom all day. Did you kind of have a similar experience in art school? What’s that like?</strong></p>
3047.  
3048.  
3049.  
3050. <p>Yeah, for sure. I do have some criticisms of how artists teach in schools, I’m not sure if it’s a worldwide thing, but from what I experienced, for example, is that the outside world is a place of freedom — you can express yourself, you can do anything you want. But I also noticed that, for example, privacy data protection was not a typical topic of interest at the time, so most of my teachers didn’t encourage me to kind of stand up for this. To research this, or at least in the way that I was doing it. Or they’d say, “you can be critical to worse tech technology, but saying that privacy is a commodity, that’s not done.” So I felt like, yes, It is a great space, and I learned a lot, but it’s also sometimes a little bit limited, I felt, on trending topics. For example, when I was graduating, everybody was working with gender identities and sustainability, those kinds of these things. And everybody’s focused on it and this was kind of the main thing to do. So I feel like, yeah, there should be more freedom in opening up the field for kind of other interests. </p>
3051.  
3052.  
3053.  
3054. <p>It’s kind of made me notice that all these kids are worrying so much about failing a grade, for example. But later on in the real world, it’s about surviving and getting your money and all these other things that can go wrong in the process. Go experiment and go crazy, the only thing that you can do is fail a class. It’s not so bad.</p>
3055.  
3056.  
3057.  
3058. <p><strong>There’s a system in place that has been there forever, and so I imagine there’s got to feel draining sometimes and really difficult to break through for a lot of young artists. </strong></p>
3059.  
3060.  
3061.  
3062. <p>Yeah, for sure. And I think that my teachers weren’t outdated — most of them were semi-young artists in the field as well and then teaching for one day — but I think there is also this culture of “this is how we do it. And this is what we think is awesome.” What I try to teach — so I teach there for, like 6 months as a substitute teacher — I try to encourage people and let them know that I can give you advice and I can be your guide into kind of helping you out with whatever you want, and if I’m not interested in what particularly what you want to, for example, say in a project, then I can help you find a way to make it awesome. How to exhibit it, how to make it bigger or smaller, or how to place it in a room. </p>
3063.  
3064.  
3065. <div class="wp-block-image">
3066. <figure class="aligncenter size-large"><img alt="" class="wp-image-74690" height="1024" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/Mozilla_rise25_Julia-Janssen_1-683x1024.jpg" width="683" /><figcaption class="wp-element-caption">Julia Janssen at Mozilla’s Rise25 award ceremony in October 2023.</figcaption></figure></div>
3067.  
3068.  
3069. <p><strong>I’m curious to know for you as an artist, when you see a piece of art, or you see something, what is the first thing that you look for or what’s something that catches your attention that inspires you when you see a piece of art?</strong></p>
3070.  
3071.  
3072.  
3073. <p>Honestly, it’s the way that is exhibited. I’m always very curious and interested in ways that people display research or kind of use media to express their work. When I’m walking to a museum, I get more enthusiastic from all the kind of things like the mechanics behind kind of hanging situations, and sometimes the work that is there to see, also to find inspirations to do things myself and what I find most thrilling. But also, I’m not just an artist who just kind of creates beautiful things, so to say, like I need information, data, mathematics to start even creating something. And I can highly appreciate people who can just make very beautiful emotional things that just exist. I think that’s a completely different type of art. </p>
3074.  
3075.  
3076.  
3077. <p><strong>You’ve also have traveled a lot, which is one of the best ways for people to learn and gain new perspectives. How much has traveling the world inspire you in the work that you create? </strong></p>
3078.  
3079.  
3080.  
3081. <p>I think a good example was last year when I went to Bali, which was actually kind of the weirdest experience in my life, because I hated the place. But it actually inspired a lot of things for my new project, mapping the oblivion, which I also talk about in my Rise25 video. Because what I felt in Bali was that this is just like such a beautiful island, such beautiful culture and nature, and it’s completely occupied by tourists and tourist traps and shiny things to make people feel well. It’s kind of hard to explain what I felt like there, but for example, I was there and what I like to do on a holiday or on a trip is just a lot of hiking, just going into nature, and just walk and explore and make up my mind or not think about anything. In Bali, everything is designed to feel at comfort or at your service, and that just felt completely out of place for me. But I felt maybe this is something that I need to embrace. So looking on Google Maps, I got this recommendation to go to a three-floor swimming pool. It was awesome, but it was also kind of weird, because I was looking like out on the jungle, and I felt like this place really completely ruined this whole beautiful area. It clicked with what I was researching about platformification and frictionlessness, where these platforms or technology or social media timelines try to make you at ease and comfortable, and making decisions be effortless. So on music apps, you click on “Jazzy Vibes” and it will kind of keep you satisfied with some Jazz vibes. But you will not be able to really explore kind of new things. It just kind of goes, as the algorithm goes. But it gives you a way of feeling of being in control. But it’s actually a highly curated playlist based on their data. But what I felt was happening in Bali was that I wanted to do something else, but to make myself more at comfort to kind of find the more safe option, I chose that swimming pool instead of exploring. And I did it based on a recommendation of an app. And then I felt constantly in-between. I actually want to go to more local places, but I had questions — What do I find out, is it safe there to eat there? I should’ve gone to easier places where I’ll probably meet peers and people who I can have a conversation or beer with. But then you go for the easier option, and then I felt I was drifting away from doing unexpected things and exploring what is there. I think that’s just a result of the technology being built around us and kind of conforming us with news that we probably might be interested in seeing, playing some music, etc. but what makes us human in the end is to feel discomfort, to be in awkward positions, to kind of explore something that is out there and unexpected and weird. I think that’s what makes the world we live in great.</p>
3082.  
3083.  
3084.  
3085. <p><strong>Yeah, that’s such a great point. There’s so many people that just don’t naturally and organically explore a city that they’re in. They are always going there and looking at recommendations and things like that. But a lot of times, if you just go and get lost in it, you can see a place for what it is, and it’s fun to do that. </strong></p>
3086.  
3087.  
3088.  
3089. <p>It’s also kind of the whole fear of missing out on that one special place. But I feel like you’re missing out on so much by constantly looking at the screen and finding recommendations of what you should like or what you should feel happy about. And I think this just kind of makes you blind to everything out there, and it also makes us very disconnected with our responsibility of making choices. </p>
3090.  
3091.  
3092.  
3093. <p><strong>What do you think is the biggest challenge that we face this year online, or as a society in the world, and how do we combat that?</strong></p>
3094.  
3095.  
3096.  
3097. <p>I mean, for me, I think most of the debate about generative AI is about taking our jobs or taking the job of creatives or writers, lawyers. I think the more fundamental question that we have to ask ourselves with generative AI is about how we will live with it, and still be human. Do we just allow what it can do or do we also take some measurements in what is desirable that it will replace? Because I feel like if we’re just kind of outsourcing all of our choices into this machine, then what the hell are we doing here? We need to find a proper relationship. I’m not saying I’m really not against technology not at all, I also see all the benefits and I love everything that it is creating — although not everything. But I think it’s really about creating this healthy relationship with the applications and the technology around us, which means that sometimes you have to chose friction and do it yourself and be a person. For example, if you are now graduating from university, I think it will be a challenge for students to actively choose to write their own thesis and not just generated by Chat GPT and setting some clever parameters. I think small challenges are something that we are currently all facing, and fixing them is something we have to want. </p>
3098.  
3099.  
3100.  
3101. <p><strong>What do you think is a simple action everyone can take to make the world online and offline a little better? </strong></p>
3102.  
3103.  
3104.  
3105. <p>Here in Europe, we have the <a href="https://gdpr-info.eu/">GDPR</a>. And it says that we have the right to data access and that means that you can ask a company to show the data that they collected about you, and they have to show you within 30 days. I do also a lot of teaching in workshops, at schools or at universities with this, showing how to request your own data. You get to know yourself a different way, which is funny. I did a lot of projects around this by making this in art installations. But I think this a very simple act to perform, but it’s kind of interesting to see, because this is only the raw data — so you still don’t know how they use it in profiling algorithms, but it gives you clarity on some advertisements that you see that you don’t understand, or just kind of understanding the skill of what they are collecting about in every moment. So that is something that I highly encourage, or also another thing that’s in line with that is <a href="https://gdpr.eu/right-to-be-forgotten/">“The right to be forgotten,”</a> which is also a European right. </p>
3106.  
3107.  
3108.  
3109. <p><strong>We started to Rise25 to celebrate Mozilla’s 25th anniversary. What do you hope people are celebrating in the next 25 years?</strong></p>
3110.  
3111.  
3112.  
3113. <p>That’s a nice question. I hope that we will be celebrating an internet that is not governed by big tech corporations, but based on public values and ethics. I think some of the smaller steps in that can be, for example, currently in Europe, one of the foundations of processing your data is having informed consent. Informed consent is such a beautiful term originating from the medical field where a doctor kind of gives you information about the procedure and the possibility, risks and everything. But on the internet, that is just kind of applied in this small button like, “Hey, click here” and give up all your rights and continue browsing without questioning. And I think one step is to kind of get a real, proper, fair way of getting consent, or maybe even switching it around, where the infrastructure of data collection is not the default, but instead it’s “do not collect anything without your consent.”  </p>
3114.  
3115.  
3116.  
3117. <p>We’re currently in a transition phase where there are a lot of very important alternatives to avoid big tech applications. Think about how Firefox already doing so much better than all these alternatives. But I think, at the core, like all our basic default apps should not be encouraged by commercial driven, very toxic incentives to just modify your data, and that has to do with how we design this infrastructure, the policies and the legislations, but also the technology itself and the kind of protocol layers of how it’s working. This is not something that we can change overnight. I hope that we’re not only thinking in alternatives to avoid kind of these toxic applications, big corporations, but that not harming your data, your equality, your fairness, your rights are the default.</p>
3118.  
3119.  
3120.  
3121. <p>In our physical world, we value things like democracy and equality and autonomy and freedom of choice. But on the internet, that is just not present yet, and I think that that should be at the core at the foundation of building a digital world as it should be in our current world. </p>
3122.  
3123.  
3124.  
3125. <p><strong>What gives you hope about the future of our world?</strong></p>
3126.  
3127.  
3128.  
3129. <p>Things like Rise25, to be honest. I think it was so special. I spoke about this with other winners as well, like, we’re all just so passionate about what we’re doing. Of course, we have inspiration from people around us, or also other people doing work on this, but we’re still not with so many and to be united in this way just gives a lot of hope. </p>
3130.  
3131.  
3132.  
3133. <a class="ft-c-inline-cta" href="https://www.mozilla.org/en-US/firefox/new?utm_medium=mozilla-websites&utm_source=blog.mozilla.org&utm_content=inline-cta">
3134.  <div class="ft-c-inline-cta__media">
3135.  <img alt="" class="attachment-1x1 size-1x1" height="512" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2020/12/Fx-Browser-icon-fullColor-512-512x512.png" width="512" />  </div>
3136.  <div class="ft-c-inline-cta__content">
3137.     <h3>Get Firefox</h3>      <span>Get the browser that protects what’s important</span>   </div>
3138. </a>
3139. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/internet-culture/julia-janssen-data-protection-privacy-rise-25-mozilla-ai/&quot;&gt;Julia Janssen creates art to be an ambassador for data protection&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>
3140. <pubDate>Mon, 06 May 2024 15:00:00 +0000</pubDate>
3141. <dc:creator>Aron Yohannes</dc:creator>
3142. </item>
3143. <item>
3144. <title>The Rust Programming Language Blog: Announcing Rustup 1.27.1</title>
3145. <guid isPermaLink="true">https://blog.rust-lang.org/2024/05/06/Rustup-1.27.1.html</guid>
3146. <link>https://blog.rust-lang.org/2024/05/06/Rustup-1.27.1.html</link>
3147. <description>&lt;p&gt;The Rustup team is happy to announce the release of Rustup version 1.27.1.
3148. <a href="https://rustup.rs">Rustup</a> is the recommended tool to install <a href="https://www.rust-lang.org">Rust</a>, a programming language that is empowering everyone to build reliable and efficient software.</p>
3149. <p>If you have a previous version of Rustup installed, getting Rustup 1.27.1 is as easy as stopping any programs which may be using Rustup (e.g. closing your IDE) and running:</p>
3150. <pre><code class="language-console">$ rustup self update
3151. </code></pre>
3152. <p>Rustup will also automatically update itself at the end of a normal toolchain update:</p>
3153. <pre><code class="language-console">$ rustup update
3154. </code></pre>
3155. <p>If you don't have it already, you can <a href="https://rustup.rs">get Rustup</a> from the appropriate page on our website.</p>
3156. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/Rustup-1.27.1.html#whats-new-in-rustup-1271" id="whats-new-in-rustup-1271"></a>What's new in Rustup 1.27.1</h3>
3157. <p>This new Rustup release involves some minor bug fixes.</p>
3158. <p>The headlines for this release are:</p>
3159. <ol>
3160. <li>Prebuilt Rustup binaries should be working on older macOS versions again.</li>
3161. <li><code>rustup-init</code> will no longer fail when <code>fish</code> is installed but <code>~/.config/fish/conf.d</code> hasn't been created.</li>
3162. <li>Regressions regarding symlinked <code>RUSTUP_HOME/(toolchains|downloads|tmp)</code> have been addressed.</li>
3163. </ol>
3164. <p>Full details are available in the <a href="https://github.com/rust-lang/rustup/blob/stable/CHANGELOG.md">changelog</a>!</p>
3165. <p>Rustup's documentation is also available in <a href="https://rust-lang.github.io/rustup/">the Rustup Book</a>.</p>
3166. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/Rustup-1.27.1.html#thanks" id="thanks"></a>Thanks</h3>
3167. <p>Thanks again to all the contributors who made Rustup 1.27.1 possible!</p>
3168. <ul>
3169. <li>Anas (0x61nas)</li>
3170. <li>cuiyourong (cuiyourong)</li>
3171. <li>Dirkjan Ochtman (djc)</li>
3172. <li>Eric Huss (ehuss)</li>
3173. <li>eth3lbert (eth3lbert)</li>
3174. <li>hev (heiher)</li>
3175. <li>klensy (klensy)</li>
3176. <li>Chih Wang (ongchi)</li>
3177. <li>Adam (pie-flavor)</li>
3178. <li>rami3l (rami3l)</li>
3179. <li>Robert (rben01)</li>
3180. <li>Robert Collins (rbtcollins)</li>
3181. <li>Sun Bin (shandongbinzhou)</li>
3182. <li>Samuel Moelius (smoelius)</li>
3183. <li>vpochapuis (vpochapuis)</li>
3184. <li>Renovate Bot (renovate)</li>
3185. &lt;/ul&gt;</description>
3186. <pubDate>Mon, 06 May 2024 00:00:01 +0000</pubDate>
3187. <dc:creator>The Rustup Team</dc:creator>
3188. </item>
3189. <item>
3190. <title>The Rust Programming Language Blog: Automatic checking of cfgs at compile-time</title>
3191. <guid isPermaLink="true">https://blog.rust-lang.org/2024/05/06/check-cfg.html</guid>
3192. <link>https://blog.rust-lang.org/2024/05/06/check-cfg.html</link>
3193. <description>&lt;p&gt;The Cargo and Compiler team are delighted to announce that starting with Rust 1.80 (or nightly-2024-05-05) every &lt;em&gt;reachable&lt;/em&gt; &lt;code&gt;#[cfg]&lt;/code&gt; will be &lt;strong&gt;automatically checked&lt;/strong&gt; that they match the &lt;strong&gt;expected config names and values&lt;/strong&gt;.&lt;/p&gt;
3194. <p>This can help with verifying that the crate is correctly handling conditional compilation for different target platforms or features. It ensures that the cfg settings are consistent between what is intended and what is used, helping to catch potential bugs or errors early in the development process.</p>
3195. <p>This addresses a common pitfall for new and advanced users.</p>
3196. <p>This is another step to our commitment to provide user-focused tooling and we are eager and excited to finally see it fixed, after more than two years since the original <a href="https://github.com/rust-lang/rfcs/pull/3013">RFC 3013</a><sup class="footnote-ref"><a href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#fn-1" id="fnref-1">1</a></sup>.</p>
3197. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#a-look-at-the-feature" id="a-look-at-the-feature"></a>A look at the feature</h3>
3198. <p>Every time a Cargo feature is declared that feature is transformed into a config that is passed to <code>rustc</code> (the Rust compiler) so it can verify with it along with <a href="https://doc.rust-lang.org/nightly/rustc/check-cfg.html#well-known-names-and-values">well known cfgs</a> if any of the <code>#[cfg]</code>, <code>#![cfg_attr]</code> and <code>cfg!</code> have unexpected configs and report a warning with the <code>unexpected_cfgs</code> lint.</p>
3199. <p><em><code>Cargo.toml</code></em>:</p>
3200. <pre><code class="language-toml">[package]
3201. name = "foo"
3202.  
3203. [features]
3204. lasers = []
3205. zapping = []
3206. </code></pre>
3207. <p><em><code>src/lib.rs</code>:</em></p>
3208. <pre><code class="language-rust">#[cfg(feature = "lasers")]  // This condition is expected
3209.                            // as "lasers" is an expected value
3210.                            // of the `feature` cfg
3211. fn shoot_lasers() {}
3212.  
3213. #[cfg(feature = "monkeys")] // This condition is UNEXPECTED
3214.                            // as "monkeys" is NOT an expected
3215.                            // value of the `feature` cfg
3216. fn write_shakespeare() {}
3217.  
3218. #[cfg(windosw)]             // This condition is UNEXPECTED
3219.                            // it's supposed to be `windows`
3220. fn win() {}
3221. </code></pre>
3222. <p><em><code>cargo check</code></em>:</p>
3223. <p><img alt="cargo-check" src="https://blog.rust-lang.org/../images/2024-05-06-check-cfg/cargo-check.svg" /></p>
3224. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#custom-cfgs-and-build-scripts" id="custom-cfgs-and-build-scripts"></a>Custom cfgs and build scripts</h3>
3225. <blockquote>
3226. <p>In Cargo point-of-view: a custom cfg is one that is neither defined by <code>rustc</code> nor by a Cargo feature. Think of <code>tokio_unstable</code>, <code>has_foo</code>, ... but not <code>feature = "lasers"</code>, <code>unix</code> or <code>debug_assertions</code></p>
3227. </blockquote>
3228. <p>Some crates use custom cfgs that they either expected from the environment (<code>RUSTFLAGS</code>or other means) or is enabled by some logic in the crate <code>build.rs</code>. For those crates Cargo provides a new instruction: <a href="https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg"><code>cargo::rustc-check-cfg</code></a><sup class="footnote-ref"><a href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#fn-2" id="fnref-2">2</a></sup> (or <code>cargo:rustc-check-cfg</code> for older Cargo version).</p>
3229. <p>The syntax to use is described in the <a href="https://doc.rust-lang.org/nightly/rustc/">rustc book</a> section <a href="https://doc.rust-lang.org/nightly/rustc/check-cfg.html">checking configuration</a>, but in a nutshell the basic syntax of <code>--check-cfg</code> is:</p>
3230. <pre><code>cfg(name, values("value1", "value2", ..., "valueN"))
3231. </code></pre>
3232. <p>Note that every custom cfgs must always be expected, regardless if the cfg is active or not!</p>
3233. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#buildrs-example" id="buildrs-example"></a><code>build.rs</code> example</h4>
3234. <p><code>build.rs</code>:</p>
3235. <pre><code class="language-rust">fn main() {
3236.    println!("cargo::rustc-check-cfg=cfg(has_foo)");
3237.    //        ^^^^^^^^^^^^^^^^^^^^^^ new with Cargo 1.80
3238.    if has_foo() {
3239.        println!("cargo::rustc-cfg=has_foo");
3240.    }
3241. }
3242. </code></pre>
3243. <blockquote>
3244. <p>Each <code>cargo::rustc-cfg</code> should have an accompanying <strong>unconditional</strong> <code>cargo::rustc-check-cfg</code> directive to avoid warnings like this: <code>unexpected cfg condition name: has_foo</code>.</p>
3245. </blockquote>
3246. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#equivalence-table" id="equivalence-table"></a>Equivalence table</h4>
3247. <table>
3248. <thead>
3249. <tr>
3250. <th><code>cargo::rustc-cfg</code></th>
3251. <th><code>cargo::rustc-check-cfg</code></th>
3252. </tr>
3253. </thead>
3254. <tbody>
3255. <tr>
3256. <td><code>foo</code></td>
3257. <td><code>cfg(foo)</code> or <code>cfg(foo, values(none()))</code></td>
3258. </tr>
3259. <tr>
3260. <td><code>foo=""</code></td>
3261. <td><code>cfg(foo, values(""))</code></td>
3262. </tr>
3263. <tr>
3264. <td><code>foo="bar"</code></td>
3265. <td><code>cfg(foo, values("bar"))</code></td>
3266. </tr>
3267. <tr>
3268. <td><code>foo="1"</code> and <code>foo="2"</code></td>
3269. <td><code>cfg(foo, values("1", "2"))</code></td>
3270. </tr>
3271. <tr>
3272. <td><code>foo="1"</code> and <code>bar="2"</code></td>
3273. <td><code>cfg(foo, values("1"))</code> and <code>cfg(bar, values("2"))</code></td>
3274. </tr>
3275. <tr>
3276. <td><code>foo</code> and <code>foo="bar"</code></td>
3277. <td><code>cfg(foo, values(none(), "bar"))</code></td>
3278. </tr>
3279. </tbody>
3280. </table>
3281. <p>More details can be found in the <a href="https://doc.rust-lang.org/nightly/rustc/check-cfg.html"><code>rustc</code> book</a>.</p>
3282. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#frequently-asked-questions" id="frequently-asked-questions"></a>Frequently asked questions</h3>
3283. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#can-it-be-disabled" id="can-it-be-disabled"></a>Can it be disabled?</h4>
3284. <p>For Cargo users, the feature is <strong>always on</strong> and <em>cannot</em> be disabled, but like any other lints it can be controlled: <code>#![warn(unexpected_cfgs)]</code>.</p>
3285. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#does-the-lint-affect-dependencies" id="does-the-lint-affect-dependencies"></a>Does the lint affect dependencies?</h4>
3286. <p>No, like most lints, <code>unexpected_cfgs</code> will only be reported for local packages thanks to <a href="https://doc.rust-lang.org/rustc/lints/levels.html#capping-lints">cap-lints</a>.</p>
3287. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#how-does-it-interact-with-the-rustflags-env" id="how-does-it-interact-with-the-rustflags-env"></a>How does it interact with the <code>RUSTFLAGS</code> env?</h4>
3288. <p>You should be able to use the <code>RUSTFLAGS</code> environment variable like it was before.
3289. <em>Currently <code>--cfg</code> arguments are not checked, only usage in code are.</em></p>
3290. <p>This means that doing <code>RUSTFLAGS="--cfg tokio_unstable" cargo check</code> will not report any warnings, unless <code>tokio_unstable</code> is used within your local crates, in which case crate author will need to make sure that that custom cfg is expected with <code>cargo::rustc-check-cfg</code> in the <code>build.rs</code> of that crate.</p>
3291. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#how-to-expect-custom-cfgs-without-a-buildrs" id="how-to-expect-custom-cfgs-without-a-buildrs"></a>How to expect custom cfgs without a <code>build.rs</code>?</h4>
3292. <p>There is <strong>currently no way</strong> to expect a custom cfg other than with <code>cargo::rustc-check-cfg</code> in a <code>build.rs</code>.</p>
3293. <p>Crate authors that don't want to use a <code>build.rs</code> are encouraged to use Cargo features instead.</p>
3294. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#how-does-it-interact-with-other-build-systems" id="how-does-it-interact-with-other-build-systems"></a>How does it interact with other build systems?</h4>
3295. <p>Non-Cargo based build systems are not affected by the lint by default. Build system authors that wish to have the same functionality should look at the <code>rustc</code> documentation for the <a href="https://doc.rust-lang.org/nightly/rustc/check-cfg.html"><code>--check-cfg</code></a> flag for a detailed explanation of how to achieve the same functionality.</p>
3296. <section class="footnotes">
3297. <ol>
3298. <li id="fn-1">
3299. <p>The stabilized implementation and RFC 3013 diverge significantly, in particular there is only one form for <code>--check-cfg</code>: <code>cfg()</code> (instead of <code>values()</code> and <code>names()</code> being incomplete and subtlety incompatible with each other). <a class="footnote-backref" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#fnref-1">↩</a></p>
3300. </li>
3301. <li id="fn-2">
3302. <p><code>cargo::rustc-check-cfg</code> will start working in Rust 1.80 (or nightly-2024-05-05). From Rust 1.77 to Rust 1.79 <em>(inclusive)</em> it is silently ignored. In Rust 1.76 and below a warning is emitted when used without the unstable Cargo flag <code>-Zcheck-cfg</code>. <a class="footnote-backref" href="https://blog.rust-lang.org/2024/05/06/check-cfg.html#fnref-2">↩</a></p>
3303. </li>
3304. </ol>
3305. &lt;/section&gt;</description>
3306. <pubDate>Mon, 06 May 2024 00:00:00 +0000</pubDate>
3307. <dc:creator>Urgau</dc:creator>
3308. </item>
3309. <item>
3310. <title>Don Marti: an easy experiment to support behavioral advertising</title>
3311. <guid isPermaLink="true">https://blog.zgp.org/easy-experiment-behavioral-advertising/</guid>
3312. <link>https://blog.zgp.org/easy-experiment-behavioral-advertising/</link>
3313. <description>&lt;p&gt;&lt;em&gt;This is a follow-up to a previous post on &lt;a href=&quot;https://blog.zgp.org/b-l-o-c-k-in-the-u-s-a/&quot;&gt;how a majority of US residents surveyed are now using an ad blocker&lt;/a&gt;, and how the survey found that privacy concerns are now the number one reason to block ads.&lt;/em&gt;&lt;/p&gt; &lt;p&gt;Almost as long as Internet privacy tools have been a thing, so have articles from personalized ad proponents telling us not to use them, because personalized ads are good actually. The policy debate over personalized (or surveillance, or cross-context behavioral, or tracking-based, or whatever you want to call it) advertising seems to keep repeating an endless argument that on the one hand, personalized advertising causes some risk or cost, &lt;span class=&quot;aside&quot;&gt;I’m not going to summarize the risks or costs here, go read &lt;a href=&quot;https://www.bobhoffmanswebsite.com/copy-of-audio-mall&quot;&gt;Bob Hoffman’s books&lt;/a&gt; or &lt;a href=&quot;https://cyberdefensereview.army.mil/CDR-Content/Articles/Article-View/Article/2537110/microtargeting-as-information-warfare/&quot;&gt;Microtargeting as Information Warfare&lt;/a&gt; for more info&lt;/span&gt; but on the other hand we have to somehow balance that against the &lt;em&gt;benefits&lt;/em&gt; of personalized advertising.&lt;/p&gt; &lt;p&gt;Benefits? Let’s see them. &lt;q&gt;Cross-context behavioral advertising is good for consumers&lt;/q&gt; should be straightforward to test. If ad personalization really helps &lt;a href=&quot;https://www.ft.com/partnercontent/facebook/how-products-are-finding-people.html&quot;&gt;match buyers and sellers in a market&lt;/a&gt;, then &lt;strong&gt;users of privacy tools and privacy settings must be buying worse products and services.&lt;/strong&gt; Research should show that the more privacy options you pick, the less happy you are with your stuff. And the more personalized your ad experience is, the more satisfied of a customer you are. This is different from asking whether or not people prefer to have ad personalization turned on. That has been pretty extensively covered, and the answer is that &lt;a href=&quot;https://blog.zgp.org/30-40-30/&quot;&gt;some people do, and some people don’t.&lt;/a&gt; This question isn’t about whether people &lt;em&gt;like&lt;/em&gt; personalized ads or not, it’s about whether people who get more personalized ads are happier with how they spend their money.&lt;/p&gt; &lt;p&gt;This should be a fairly low-cost project because in general, the companies that do the most personalized advertising are in the best position to do the research to support it. Are users of privacy tools and settings more or less satisfied with the products and services they buy than people who leave the personalized ad options on?&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;p&gt;Do privacy-protected users give lower ratings to the products they buy?&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;Do privacy-protected users return or stop using more of their purchases?&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;Are privacy-protected users more likely to buy a replacement, competing product after an unsuccessful first purchase in a category?&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;Are privacy-protected users more likely to agree with general statements about a decline in quality and trustworthiness in business in general?&lt;/p&gt;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;The correlation between &lt;strong&gt;more privacy&lt;/strong&gt; and &lt;strong&gt;less satisfied consumer&lt;/strong&gt; would be detectable from a variety of angles. Vendors of browsers with &lt;a href=&quot;https://blog.zgp.org/google-chrome-checklist/&quot;&gt;preferences that affect ad targeting&lt;/a&gt; should be able to show that people who turn on the privacy settings are somehow worse off than people who don’t. Anti-adblock companies do research on ad blocker users—so how are shopping experiences different for those users? Any product that connects to a server for updates or telemetry is providing data on how long the buyer chooses to keep using it. And—the biggest opportunity here—any company that has an Apple iOS app (and that’s a lot of companies) should be able to compare satisfaction metrics between customers with App Tracking Transparency (ATT) on or off.&lt;/p&gt; &lt;p&gt;Ad platforms, search engines, social network companies, and online retailers all have access to the needed info on ads, privacy settings, locations, and purchases. Best of all, they’re constantly running customer surveys and experiments of all kinds. It would be straightforward for any of these companies to run yet another user satisfaction survey, to prove what should be an obvious, measurable effect. I’m really looking for any kind of research here, whether it’s a credit card company running a SQL query on existing data to point out that customers with iOS app tracking turned off have more chargebacks, or a longer-term customer satisfaction study, anything.&lt;/p&gt; &lt;h3&gt;looking at the data we do have&lt;/h3&gt; &lt;p&gt;&lt;strong&gt;Update 16 May 2024:&lt;/strong&gt; &lt;a href=&quot;https://marketing.wharton.upenn.edu/wp-content/uploads/2023/10/11.09.2023-Korganbekova-Malika-PAPER-JMP.pdf&quot;&gt;Balancing User Privacy and Personalization by Malika Korganbekova and Cole Zuber&lt;/a&gt;. This study simulated the effects of a privacy feature by truncating browsing history for some Wayfair shoppers, and found that people who were assigned to the personalized group and chose a product personalized to them were 10% less likely to return it than people in the non-personalized group.&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4635884&quot;&gt;The Welfare Effects of Ad Blocking&lt;/a&gt; by Lin et al. was different—members of the treatment group got an ad blocker affecting all sites, not just one retail site.&lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;[P]articipants that were asked to install an ad-blocker become less likely to regret recent purchases, while participants that were asked to uninstall their ad-blocker report lower levels of satisfaction with their recent purchases.&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;The ad blockers used in that study, however, were multi-purpose ones such as &lt;a href=&quot;https://github.com/gorhill/uBlock/wiki/Scientific-papers&quot;&gt;uBlock Origin&lt;/a&gt; that block ads in general, not just personalization.&lt;/p&gt; &lt;p&gt;The effect of privacy settings on scams goes two ways: you can avoid being specifically targeted for a scam, but more likely you can also &lt;a href=&quot;https://blog.zgp.org/deception-design/&quot;&gt;just get more scam ads by default if you feed in too little info to be targeted for the good ads&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;The Internet as a whole is much more various in seller honesty level than the Wayfair platform is, which might help explain the difference in customer satisfaction seen between the Korganbekova and Zuber paper and the Lin et al. paper. Lin et al. showed that people were more satisfied as customers when receiving fewer ads in total, but they might have been even less satisified if they received more of the lower-quality ads that you’re more likely to get if adtech firms don’t have enough data to target you for a bigger-budget campaign.&lt;/p&gt; &lt;p&gt;Another related paper is &lt;a href=&quot;https://www.ftc.gov/system/files/ftc_gov/pdf/PrivacyCon-2022-Acquisiti-Mustri-Behavioral-Advertising-Consumer-Welfare.pdf&quot;&gt;Behavioral advertising and consumer welfare: An empirical investigation&lt;/a&gt;.&lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;The presence of low quality vendors, along with the recent increase in the use of ad blockers, makes it increasingly difficult for new, high quality vendors, to reach new clients. Consumers benefit from having access to new sellers that are able to meet their needs through behavioral ads, as long as they are good sellers.&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;but&lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;targeted ads are more likely to be associated with lower quality vendors, and higher prices for identical products, compared to competing alternatives found in organic search results&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;If you look back on the history of advertising, there has never been an ad medium that required so much legal and technical complexity to try to get people to accept it. Why is &lt;a href=&quot;https://techcrunch.com/2024/04/17/edpb-consent-or-pay-opinion/&quot;&gt;Meta going to so much trouble&lt;/a&gt; to try to come up with a legal way to require people in the EU to accept personalized ads? If ad personalization is so good for consumers, won’t they pick it on their own? Anyway, I’m looking for research on how personalization and privacy choices affect customer satisfaction.&lt;/p&gt; &lt;h3&gt;Related&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/free-riders/&quot;&gt;free riding on future web ads?&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/reputation-signal/&quot;&gt;Reputation, signaling, and targeted ads&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/b-l-o-c-k-in-the-u-s-a/&quot;&gt;B L O C K in the U S A&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/banning-surveillance-advertising/&quot;&gt;banning surveillance advertising&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/privacy-econ-sources/&quot;&gt;privacy economics sources&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/when-can-deceptive-sellers-outbid-honest-sellers-for-ad-impressions/&quot;&gt;When can deceptive sellers outbid honest sellers for ad impressions?&lt;/a&gt;&lt;/p&gt;</description>
3314. <pubDate>Sat, 04 May 2024 00:00:00 +0000</pubDate>
3315. </item>
3316. <item>
3317. <title>Adrian Gaudebert: The challenges of teaching a complex game</title>
3318. <guid isPermaLink="false">urn:md5:010cbc81f2b8194755897ca97bca68b0</guid>
3319. <link>http://adrian.gaudebert.fr/blog/post/The-challenges-of-teaching-a-complex-game</link>
3320. <description>&lt;p&gt;When I was 13, my mom bought me Civilization III from a retail shop, then went on to do some more shopping. I stayed in the car, with this elegant box in my hands, craving to play the game it contained. I opened the box, and there discovered something magical: the Civilization III Manual. Having nothing better to do, I started reading it…&lt;/p&gt;
3321.  
3322. <figure><a href="http://adrian.gaudebert.fr/blog/public/icones-billets/civilization-III-manual.jpg" target="_blank"><img alt="The Civilization III manual" class="media" src="http://adrian.gaudebert.fr/blog/public/icones-billets/.civilization-III-manual_m.jpg" style="width: 448px; height: 314px;" /></a>
3323.  
3324. <figcaption><em>That game manual was THICK<strong>.</strong></em></figcaption>
3325. </figure>        <p>More than 20 years later, I still remember how great reading that book felt. I was propelled into the game, learning about its systems and strategies, discovering screens of foggy maps and world wonders. It made me love the game before I had even played it! Since then I've played all Civilization games that came out — including Humankind, the unofficial 7th episode — and loved all of them. Would I have had the same connection to these games had I not read the manual? Impossible to tell. Would I have read that book had I not been trapped in a car with the game box on my laps? Definitely not! Even the developers of the game knew that nobody was reading those texts:</p>
3326.  
3327. <figure><a href="http://adrian.gaudebert.fr/blog/public/icones-billets/civilization-III-quote.jpg" target="_blank"><img alt="A quote from the Civilization III manual" class="media" src="http://adrian.gaudebert.fr/blog/public/icones-billets/civilization-III-quote.jpg" /></a>
3328.  
3329. <figcaption><em>“The authors and developers of computer games know too well that most players never read the manual.”</em></figcaption>
3330. </figure>
3331.  
3332. <p>Here's me now, 20-something years later, having made a game of my own and needing to teach it to potential players… Should I write a full-blown game manual, hoping that a little 13-years old will read it on a parking lot?</p>
3333.  
3334. <p>Heck no! Ain't nobody got time for that!</p>
3335.  
3336. <h3>Let's make a tutorial instead</h3>
3337.  
3338. <p>Dawnmaker has been built almost like a board game, in the sense that it has complex rules that you have to learn before you can play. Physical board game players are used to that: someone has to go through the rules before they can explain them to the rest of their players group. But video games are a different beast, and we've long moved away from reading… well, almost anything at all, really, and certainly not rules. You can't put each player into a car on a parking lot with nothing else to do other than reading the rules of your game. If you were to present the video game player with a rules book, in today's world of abundance, they would just move on to the next game in their unending backlog.</p>
3339.  
3340. <p>Teaching a game is thus incredibly difficult: it has to have as little text as possible, it has to be fun and rewarding, and it has to hook the player so that, by the end of the teaching phase, they still want to play the actual game.</p>
3341.  
3342. <p>It's with all those things in mind that I started building Dawnmaker's tutorial. I set two main rules in place: first, use as little words as possible, and second, make the player learn while doing. The first iteration of the tutorial was very terse: you only had a small goal written at the top of the screen, and almost no explanations whatsoever about what you were to do, or why. It turns out, that didn't work too well. Players were lost, especially when it came to the most complex actions or features of the game. Past a certain point in the tutorial, almost all of the players stopped reading the objectives at the top of the screen. And finally, they were also lacking a sense of purpose.</p>
3343.  
3344. <p><img alt="" class="media" src="http://adrian.gaudebert.fr/blog/public/icones-billets/tutorial-tooltips.png" style="float: right; margin: 0 0 1em 1em;" /></p>
3345.  
3346. <p>So for all my good intents, I had to revise my approach and write more words. The second iteration, which is now live in the game and demo, has a lot of small tooltips that pop up around the screen as the interface shows itself. I've tried to load information as slowly as possible, giving the player only what they need at a given moment. I think I approximately quadrupled the number of words in the tutorial, but such is the reality of teaching a complex game.</p>
3347.  
3348. <p>The other big change I made was to give the player a better sense of progression in the tutorial. The objectives now stay visible in a box on the left-hand side of the screen. They have little animations and sounds that reward the player when they complete a task. Seeing that list grow shows how the player has progressed and is also rewarding by itself.</p>
3349.  
3350. <p>Teaching the game doesn't only happen in the tutorial though, but also on the various signs and feedback we put around the game. Here's an example: during the tutorial, new players did not understand what was happening with the new building choice that was presented. The solution to this was not to explain with words what those buildings where, but to show a feedback. Now, whenever you gain a new building, you see that same building popping up in the center of the board, then moving towards the buildings roster. It's a double win: they understand that the building goes somewhere, they see where, and they are inclined to check that place and see what it is. I guess one feedback is worth a thousand words?</p>
3351.  
3352. <p>This version of the tutorial is still far from perfect. But it is the first thing players interact with, and thus it is a piece of the game that really has to shine. We'll keep collecting feedback from new players, and use that to polish the tutorial until, like Eclairium, it shines bright.</p>
3353.  
3354. <p><em>BTW: unlike Eclairium, diamonds do not shine, they simply reflect light. <a href="https://www.youtube.com/watch?v=lWA2pjMjpBs">Rihanna has been lying to us all</a>.</em></p>
3355.  
3356. <h3>Next event: Geektouch in Lyon</h3>
3357.  
3358. <p>If you're in Lyon or close to it, come and meet us at the <a href="https://www.geektouch-festival.com/" rel="noopener noreferrer" target="_blank" title="Geektouch 4 & 5 mai 2024 à Lyon Eurexpo - GEEKTOUCH">Geektouch / Japan Touch festival</a> in Eurexpo on May 4th and 5th! We'll have a stand on the Indie Game Lab space (lot A87). You will of course get to play with the latest version of Dawnmaker. We hope to see you there!</p>
3359.  
3360. <hr />
3361. <p>This piece was initially sent out to the readers of our newsletter. Wanna join in on the fun? Head out to <a href="https://arpentor.studio/games/dawnmaker/" hreflang="en">Dawnmaker's presentation page</a> and fill the form. You'll receive regular stories about how we're making this game, the latest news of its development, as well as an exclusive access to Dawnmaker's alpha version!</p>
3362.  
3363. &lt;p style=&quot;text-align: center;&quot;&gt;&lt;a href=&quot;https://arpentor.studio/games/dawnmaker/&quot; hreflang=&quot;en&quot; style=&quot;display: inline-block; border-radius: 1em; background-color: #C8D6AF; padding: 1em 2em; font-weight: bold; font-size: 1.1em;&quot;&gt;Join our community!&lt;/a&gt;&lt;/p&gt;</description>
3364. <pubDate>Fri, 03 May 2024 14:29:14 +0000</pubDate>
3365. <dc:creator>Adrian</dc:creator>
3366. </item>
3367. <item>
3368. <title>The Mozilla Blog: Abbie Richards on the wild world of conspiracy theories and battling misinformation on the internet</title>
3369. <guid isPermaLink="false">https://blog.mozilla.org/?p=74657</guid>
3370. <link>https://blog.mozilla.org/en/internet-culture/abbie-richards-misinformation-conspiracy-theories-mozilla-rise-25-election/</link>
3371. <description>&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;
3372.  
3373. </div></figure>
3374.  
3375.  
3376.  
3377. <p><em>At Mozilla, we know we can’t create a better future alone, that is why each year we will be highlighting the work of 25 digital leaders using technology to amplify voices, effect change, and build new technologies globally through our <a href="https://rise25.mozilla.org/?_gl=1*585km0*_ga*MTY1MDQ4MTg2NC4xNjk5NDc0NTE5*_ga_X4N05QV93S*MTcwNzE4MDk3Ny40NC4wLjE3MDcxODA5NzcuMC4wLjA." rel="noreferrer noopener" target="_blank">Rise 25 Awards.</a> These storytellers, innovators, activists, advocates, builders and artists are helping make the internet more diverse, ethical, responsible and inclusive.</em></p>
3378.  
3379.  
3380.  
3381. <p><em>This week, we chatted with Abbie Richards, a former stand-up comedian turned content creator dominating TikTok as a researcher, focusing on understanding how misinformation, conspiracy theories and extremism spread on the platform. She also is a co-founder of EcoTok, an environmental TikTok collective specializing in social media climate solutions. We talked with Abbie about finding emotional connections with audiences, the responsibility of social media platforms and more.</em></p>
3382.  
3383.  
3384.  
3385. <p><strong>First off, what’s the wildest conspiracy theory that you have seen online?</strong></p>
3386.  
3387.  
3388.  
3389. <p>It’s hard to pick the wildest because I don’t know how to even begin to measure that. One that I think about a lot, though, is that I tend to really find the spirituality ones very interesting. There’s the new Earth one with people who think that the earth is going to be ascending into a higher dimension. And the way that that links to climate change — like when heat waves happen, and when the temperature is hotter than normal, and they’re like “it’s because the sun’s frequency is increasing because we’re going to ascend into a higher dimension.” And I am kind of obsessed with that line of thought. Also because they think that if you, your soul, vibrate at a high enough frequency — essentially, if your vibes are good enough — you will ascend, and if not, you will stay trapped here in dystopian earth post ascension which is wild because then you’re assigning some random, universal, numerical system for how good you are based on your vibrational frequency. Where is the cut off? At what point of vibrating am I officially good enough to ascend, or am I going to always vibrate too low? Are my vibes not good? And do I not bring good vibes to go to your paradise? I think about that one a lot.</p>
3390.  
3391.  
3392.  
3393. <p><strong>As someone who has driven through tons of misinformation and conspiracy theories all the time, what do you think are the most common things that people should be able to notice when they need to be able to identify if something’s fake? </strong></p>
3394.  
3395.  
3396.  
3397. <p>So I have two answers to this. The first is that the biggest thing that people should know when they’re encountering this information and conspiracy theories online is that they need to check in with how a certain piece of information makes them feel. And if it’s a certain piece of information that they really, really want to believe, they should be especially skeptical, because that’s the number one thing. Not whether they can recognize something like that or if AI-generated human ears are janky. It’s the fact that they want to believe what the AI generated deepfake is saying and no matter how many tricks we can tell them about symmetry and about looking for clues that it is a deepfake, fundamentally, if they want to believe it, the thing will still stick in their brain. And they need to learn more about the emotional side of encountering this misinformation and conspiracy theories online. I would prioritize that over the tiny little tricks and tips for how to spot it, because really, it’s an emotional problem. When people lean into and dive into conspiracy theories, and they fall down a rabbit hole, it’s not because they’re not media literate enough. Fundamentally, it’s because it’s emotionally serving something for them. It’s meeting some sort of emotional psychological epistemic need to feel like they have control, to feel like they have certainty to feel like they understand things that other people don’t, and they’re in on knowledge to feel like they have a sense of community, right? Conspiracy theories create senses of community and make people feel like they’re part of a group. There are so many things that it’s providing that no amount of tips and tricks for spotting deepfakes will ever address. And we need to be addressing those. How can we help them feel in control? How can we help them feel empowered so that they don’t fall into this?</p>
3398.  
3399.  
3400.  
3401. <p>The second to me is wanting to make sure that we’re putting the onus on the platforms rather than the people to decipher what is real and not real because people are going to consistently be bad at that, myself included. We all are quite bad at determining what’s real. I mean, we’re encountering more information in a day than our brains can even remotely keep up with. It’s really hard for us to decipher which things are true and not true. Our brains aren’t built for that. And while media literacy is great, there’s a much deeper emotional literacy that needs to come along with it, and also a shifting of that onus from the consumer onto the platforms.</p>
3402.  
3403.  
3404. <div class="wp-block-image">
3405. <figure class="aligncenter size-large"><img alt="" class="wp-image-74658" height="1024" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2024/05/Mozilla_rise25_Abbie-Spector-Richards_1-683x1024.jpg" width="683" /><figcaption class="wp-element-caption">Abbie Richards at Mozilla’s Rise25 award ceremony in October 2023.</figcaption></figure></div>
3406.  
3407.  
3408. <p><strong>What are some of the ways these platforms could take more responsibility and combat misinformation on their platforms?</strong></p>
3409.  
3410.  
3411.  
3412. <p>It’s hard. I’m not working within the platforms, so it’s hard to know what sort of infrastructure they have versus what they could have. It’s easy to look at what they’re doing and say that it’s not enough because I don’t know about their systems. It’s hard to make specific recommendations like “here’s what you should be doing to set up a more effective …”. What I can say is that, without a doubt, these mega corporations that are worth billions of dollars certainly have the resources to be investing in better moderation and figuring out ways to experiment with different ways. Try different things to see what works and encourage healthier content on your platform. Fundamentally, that’s the big shift. I can yell about content moderation all day, and I will, but the incentives on the platforms are not to create high quality, accurate information. The incentives on all of these platforms are entirely driven by profit, and how long they can keep you watching, and how many ads they can push to you, which means that the content that will thrive is the stuff that is the most engaging, which tends to be less accurate. It tends to be catering to your negative emotions, catering to things like outrage and that sort of content that is low quality, easy to produce, inaccurate, highly emotive content is what is set up to thrive on the platform. This is not a system that is functional with a couple of flaws, this misinformation crisis that we’re in is very much the results of the system functioning exactly as it’s intended.</p>
3413.  
3414.  
3415.  
3416. <p><strong>What do you think is the biggest challenge we face in the world this year on and offline? </strong></p>
3417.  
3418.  
3419.  
3420. <p>It is going to be the biggest election year in history. We just have so many elections all around the world, and platforms that we know don’t serve healthy, functional democracy super well, and I am concerned about that combination of things this year.</p>
3421.  
3422.  
3423.  
3424. <p><strong>What do you think is one action that everybody can take to make the world, and our online lives, a little bit better?</strong></p>
3425.  
3426.  
3427.  
3428. <p>I mean, log off (laughs). Sometimes log off. Go sit in silence just for a bit. Don’t say anything, don’t hear anything. Just go sit in silence. I swear to God it’ll change your life. I think we are in a state right now where we are chronically consuming so much information, like we are addicted to information, and just drinking it up, and I am begging people to at least just like an hour a week to not consume anything, and just see how that feels. If we could all just step back for a little bit and log off and rebel a little bit against having our minds commodified for these platforms to just sell ads, I really feel like that is one of the easiest things that people can do to take care of themselves.</p>
3429.  
3430.  
3431.  
3432. <p>The other thing would be check in with your emotions. I can’t stress this enough. Like when you encounter information, how does that information make you feel? How much do you want to believe that information and those things. So very much, my advice is to slow down and feel your feelings.</p>
3433.  
3434.  
3435.  
3436. <p><strong>We started Rise25 to celebrate Mozilla’s 25th anniversary, what do you hope people are celebrating in the next 25 years?</strong></p>
3437.  
3438.  
3439.  
3440. <p>I hope that we’ve created a nice socialist internet utopia where we have platforms that people can go interact and build community and create culture and share information and share stories in a way that isn’t driven entirely by what’s the most profitable. I’d like to be celebrating something where we’ve created the opposite of a clickbait economy where everybody takes breaks. I hope that that’s where we are at in 25 years.</p>
3441.  
3442.  
3443.  
3444. <p><strong>What gives you hope about the future of our world?</strong></p>
3445.  
3446.  
3447.  
3448. <p>I interact with so many brilliant people who care so much and are doing such cool work because they care, and they want to make the world better, and that gives me a lot of hope. In general. I think that approaching all of these issues from an emotional lens and understanding that, people in general just want to feel safe and secure, and they just want to feel like they know what’s coming around the corner for them, and they can have their peaceful lives, is a much more hopeful way to think about pretty scary kind of political divides. I think that there is genuinely a lot more that we have in common than there are things that we have differences. It’s just that right now, those differences feel very loud. There are so many great people doing such good work with so many different perspectives, and combined, we are so smart together. On top of that, people just want to feel safe and secure. And if we can figure out a way to help people feel safe and secure and help them feel like their needs are being met, we could create a much healthier society collectively.</p>
3449.  
3450.  
3451.  
3452. <a class="ft-c-inline-cta" href="https://www.mozilla.org/en-US/firefox/new?utm_medium=mozilla-websites&utm_source=blog.mozilla.org&utm_content=inline-cta">
3453.  <div class="ft-c-inline-cta__media">
3454.  <img alt="" class="attachment-1x1 size-1x1" height="512" src="https://blog.mozilla.org/wp-content/blogs.dir/278/files/2020/12/Fx-Browser-icon-fullColor-512-512x512.png" width="512" />  </div>
3455.  <div class="ft-c-inline-cta__content">
3456.     <h3>Get Firefox</h3>      <span>Get the browser that protects what’s important</span>   </div>
3457. </a>
3458. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/en/internet-culture/abbie-richards-misinformation-conspiracy-theories-mozilla-rise-25-election/&quot;&gt;Abbie Richards on the wild world of conspiracy theories and battling misinformation on the internet&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>
3459. <pubDate>Fri, 03 May 2024 13:00:00 +0000</pubDate>
3460. <dc:creator>Aron Yohannes</dc:creator>
3461. </item>
3462. <item>
3463. <title>Wil Clouser: I made a new hack poster</title>
3464. <guid isPermaLink="false">https://micropipes.com/2024/05/03/I-made-a-new-hack-poster</guid>
3465. <link>https://micropipes.com/2024/05/03/I-made-a-new-hack-poster/</link>
3466. <description>&lt;p&gt;I was feeling nostalgic a couple months ago and built a hack poster out of
3467. plywood.  It’s mostly modeled after the original but I added the radio tower
3468. and changed the words.  “This technology could fall into the right hands” still
3469. makes me smile when I see it out in the world.</p>
3470.  
3471. <p><img alt="Poster hanging on the wall" src="https://micropipes.com/assets/img/2024-art-hack-poster-1.jpg" />
3472. <img alt="Close-up of radio tower" src="https://micropipes.com/assets/img/2024-art-hack-poster-2.jpg" />
3473. &lt;img alt=&quot;Close-up of lettering&quot; src=&quot;https://micropipes.com/assets/img/2024-art-hack-poster-3.jpg&quot; /&gt;&lt;/p&gt;</description>
3474. <pubDate>Fri, 03 May 2024 07:00:00 +0000</pubDate>
3475. <dc:creator>Wil Clouser</dc:creator>
3476. </item>
3477. <item>
3478. <title>Mozilla Addons Blog: 1000+ Firefox for Android extensions now available</title>
3479. <guid isPermaLink="false">https://blog.mozilla.org/addons/?p=9166</guid>
3480. <link>https://blog.mozilla.org/addons/2024/05/02/1000-firefox-for-android-extensions-now-available/</link>
3481. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;alignleft size-medium wp-image-9167&quot; height=&quot;326&quot; src=&quot;https://blog.mozilla.org/addons/files/2024/05/android_pic-580x326.png&quot; width=&quot;580&quot; /&gt;The new open ecosystem of extensions on Firefox for Android &lt;a href=&quot;https://blog.mozilla.org/addons/2023/12/14/a-new-world-of-open-extensions-on-firefox-for-android-has-arrived/&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;launched in December with just over 400 extensions&lt;/a&gt;. Less than five months later we’ve &lt;a href=&quot;https://addons.mozilla.org/android/search/?sort=users&amp;amp;type=extension&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;surpassed 1,000 Firefox for Android extensions&lt;/a&gt;. That’s an impressive achievement by this developer community! It’s exciting to see so many developers embrace the opportunity to explore new creative possibilities for mobile browser customization.&lt;/p&gt;
3482. <p>If you’re a developer intrigued to learn more about building extensions on Firefox for Android, here’s a great place to <a href="https://extensionworkshop.com/documentation/develop/developing-extensions-for-firefox-for-android/" rel="noopener" target="_blank">get started</a>. Or maybe you already have some <a href="https://discourse.mozilla.org/t/top-apis-mising-on-firefox-for-android/124506" rel="noopener" target="_blank">feedback about missing API’s on Firefox for Android?</a></p>
3483. <p>What are some of your favorite new Firefox for Android extensions? Drop some props in the comments below.</p>
3484. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/addons/2024/05/02/1000-firefox-for-android-extensions-now-available/&quot;&gt;1000+ Firefox for Android extensions now available&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>
3485. <pubDate>Thu, 02 May 2024 19:54:59 +0000</pubDate>
3486. <dc:creator>Scott DeVaney</dc:creator>
3487. </item>
3488. <item>
3489. <title>Mozilla Localization (L10N): L10n report: May 2024 Edition</title>
3490. <guid isPermaLink="false">https://blog.mozilla.org/l10n/?p=1675</guid>
3491. <link>https://blog.mozilla.org/l10n/2024/05/02/l10n-report-may-2024-edition/</link>
3492. <description>&lt;p&gt;&lt;i&gt;Please note some of the information provided in this report may be subject to change as we are sometimes sharing information about projects that are still in early stages and are not final yet. &lt;/i&gt;&lt;/p&gt;
3493. <h3>New content and projects</h3>
3494. <h4>What’s new or coming up in Firefox desktop</h4>
3495. <p>To start, a “logistic” announcement: on April 29 we changed the configuration of the Firefox project in Pontoon to use a different repository for source (English) strings. This is part of a larger change that will <a href="https://groups.google.com/a/mozilla.org/g/firefox-dev/c/QnfydsDj48o/m/8WadV0_dBQAJ">move Firefox development from Mercurial to Git</a>.</p>
3496. <p>While the change was mostly transparent for localizers, there is an added benefit: as part of the Firefox project, you will now be able to localize about 40 strings that are used by <a href="https://mozilla.github.io/geckoview/">GeckoView</a>, the core of our Android browsers (Firefox, Focus). For your convenience, these are grouped in a specific tag called GeckoView. Since these are mostly old strings dating back to Fennec (Firefox for Android up to version 68), you will also find that existing translations have been imported — in fact, we imported over 4 thousand translations.</p>
3497. <p>Going back to Firefox desktop, version 127 is currently in Nightly, and will move to Beta on May 13. Over the past few weeks there have been a few new features and updates that’s it’s worth testing to ensure the best experience for users.</p>
3498. <p>You are probably aware of the <a href="https://support.mozilla.org/kb/website-translation">Firefox Translations</a> feature available for a growing number of languages. While this feature was originally available for full-page translation, now it’s also possible to select text in the page and translate it through the context menu.</p>
3499. <div class="wp-caption aligncenter" id="attachment_1682" style="width: 610px;"><a href="https://blog.mozilla.org/l10n/files/2024/05/select_translate.png"><img alt="Screenshot of the translation selection feature in Firefox." class="wp-image-1682 size-large" height="388" src="https://blog.mozilla.org/l10n/files/2024/05/select_translate-600x388.png" width="600" /></a><p class="wp-caption-text" id="caption-attachment-1682">Screenshot of the Translation selection feature in Firefox.</p></div>
3500. <p><a href="https://support.mozilla.org/kb/firefox-reader-view-clutter-free-web-pages">Reader Mode</a> is also in the process of getting a redesign, with more controls to customize the user experience.</p>
3501. <div class="wp-caption aligncenter" id="attachment_1681" style="width: 610px;"><a href="https://blog.mozilla.org/l10n/files/2024/05/reader_mode.png"><img alt="Screenshot of the Reader Mode settings in Firefox Nightly." class="wp-image-1681 size-large" height="374" src="https://blog.mozilla.org/l10n/files/2024/05/reader_mode-600x374.png" width="600" /></a><p class="wp-caption-text" id="caption-attachment-1681">Screenshot of the Reader Mode settings in Firefox Nightly.</p></div>
3502. <p>The New Tab page has a new wallpaper function: in order to test it, go to <code>about:config</code> (see <a href="https://support.mozilla.org/kb/about-config-editor-firefox">this page</a> if you’re unfamiliar), search for <code>browser.newtabpage.activity-stream.newtabWallpapers.enabled</code> and flip its value to <code>true</code> (double-click will work). At this point, open a new tab and click the gear icon in the top-right corner. Note that the available wallpapers change depending on the current theme (dark vs light).</p>
3503. <div class="wp-caption aligncenter" id="attachment_1678" style="width: 610px;"><a href="https://blog.mozilla.org/l10n/files/2024/05/newtab_wallpaper.png"><img alt="Screenshot of New Tab wallpaper selection in Nightly." class="size-large wp-image-1678" height="504" src="https://blog.mozilla.org/l10n/files/2024/05/newtab_wallpaper-600x504.png" width="600" /></a><p class="wp-caption-text" id="caption-attachment-1678">Screenshot of New Tab wallpaper selection in Nightly.</p></div>
3504. <p>Last but not least, make sure to test the new features available in the integrated PDF Reader, in particular the dialog to <a href="https://support.mozilla.org/kb/view-pdf-files-firefox-or-choose-another-viewer#w_add-an-image-to-pdf-files">add images</a> and <a href="https://support.mozilla.org/kb/view-pdf-files-firefox-or-choose-another-viewer#w_highlight-in-pdf-files">highlight</a> elements in the page.</p>
3505. <div class="wp-caption aligncenter" id="attachment_1679" style="width: 610px;"><a href="https://blog.mozilla.org/l10n/files/2024/05/pdf_viewer.png"><img alt="Screenshot of the PDF Viewer in Firefox, with the "Add image" UI." class="size-large wp-image-1679" height="501" src="https://blog.mozilla.org/l10n/files/2024/05/pdf_viewer-600x501.png" width="600" /></a><p class="wp-caption-text" id="caption-attachment-1679">Screenshot of the PDF Viewer in Firefox, with the “Add image” UI.</p></div>
3506. <h4>What’s new or coming up in mobile</h4>
3507. <p>The mobile team is currently redesigning the app menus in Firefox Android and iOS. There will be many new menu strings landing in the upcoming versions (you may have already noticed some prelanding), including some dynamic menu text that may get truncated for some locales – especially on smaller screens.</p>
3508. <p>Testing for this type of localization issues will be a focus: we’ll set expectations for it soon and send testing instructions (v130 or v131 releases are currently the target). Strings will be making their way incrementally in the new menus available through Firefox Nightly, allowing enough time for localizers to translate and test continuously.</p>
3509. <h4>What’s new or coming up in web projects</h4>
3510. <h5>Mozilla.org</h5>
3511. <p>The mozilla.org team is creating a regular cleanup routine by labeling the soon-to-be replaced strings with an expiration date, usually two months after the string has become obsolete. This approach will minimize communities’ time localizing strings no longer used. In other words, if you see a string labeled with a date, please skip it. Below is an example, and in this case, you want to localize the v2 string:</p>
3512. <blockquote style="font-family: Monospace;"><p>example-v2 = Security, reliability and speed — on every device, anywhere you go.</p>
3513. <p># Obsolete string (expires: 2024-03-18)<br />
3514. example = Security, reliability and speed — from a name you can trust.</p></blockquote>
3515. <h5>Relay Website</h5>
3516. <p>This product is in maintenance mode and it will not be open for new locales until we remove obsolete strings and revert the content migration to mozilla.org (see also <a href="https://blog.mozilla.org/l10n/2023/11/03/l10n-report-november-2023-edition/">l10n report from November 2023</a>).</p>
3517. <h4>What’s new or coming up in SUMO</h4>
3518. <ul>
3519. <li><a href="https://blog.mozilla.org/sumo/2024/03/25/introducing-konstantina/">Konstantina</a> is joining the SUMO force! She moved from the Marketing team to the Customer Experience team in late Q1. If you haven’t get to know her, please don’t hesitate to say hi!</li>
3520. <li>AI spam has been a big issue in our forum lately, so we decided to spin up a new contributor policy around the use of AI-generated tools. Please check<a href="https://support.mozilla.org/forums/contributors/716669?last=86840"> this thread</a> if you haven’t!</li>
3521. <li>We opened an<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885070"> AAQ for NL</a> in our support forum. Thanks to Tim Maks and the rest of the NL community, who’ve been very supportive of this work.</li>
3522. <li>Are you contributing to our Knowledge Base? You may want to read the recent blog posts from the content team to get to know more about<a href="https://blog.mozilla.org/sumo/2024/04/09/keeping-you-in-the-loop-whats-new-in-our-knowledge-base/"> what they’re up to</a>. In short, they’re doing a lot around<a href="https://blog.mozilla.org/sumo/2024/04/18/freshening-up-the-knowledge-base-for-spring-2024/"> freshening up our knowledge base articles</a>.</li>
3523. <li>Wanna know more about what we’ve done in Q1 2024, read the recap <a href="https://blog.mozilla.org/sumo/2024/04/30/whats-up-with-sumo-q1-2024/">here</a>.</li>
3524. </ul>
3525. <h4>What’s new or coming up in Pontoon</h4>
3526. <h5>Large Language Model (LLM) Integration</h5>
3527. <p>We’re thrilled to announce the integration of LLM-assisted translations into Pontoon! For all locales utilizing Google Translate as a translation source, a new AI-powered option is now available within the ‘Machinery’ tab. This feature enhances Google Translate outputs by leveraging a Large Language Model (LLM). Users can now tailor translations to be more formal or informal and rephrase text for clarity and tone.</p>
3528. <p>Since January, our team has conducted extensive research to explore how other localization services are utilizing AI. We specifically focused on comparing the capabilities of Large Language Models (LLMs) against traditional machine translation methods and identifying industry best practices.</p>
3529. <p>Our findings revealed that while tools like Google Translate provide a solid foundation, they sometimes fall short, often translating text too literally. Recognizing the potential for improvement, we introduced functionality within Pontoon to adjust the tone and refine phrases directly.</p>
3530. <p>For example, consider the phrase “Firefox has your back” translated in the Italian locale. The suggestion provided by Google’s machine translation is literal and incorrect (“Firefox covers your shoulders”). The images below demonstrate the use of the “Rephrase” option:</p>
3531. <div class="wp-caption aligncenter" id="attachment_1677" style="width: 472px;"><a href="https://blog.mozilla.org/l10n/files/2024/05/llm2.png"><img alt="Screenshot of the LLM feature in Pontoon (before selecting a command)." class="size-full wp-image-1677" height="374" src="https://blog.mozilla.org/l10n/files/2024/05/llm2.png" width="462" /></a><p class="wp-caption-text" id="caption-attachment-1677">Dropdown to use the LLM feature</p></div>
3532. <div class="wp-caption aligncenter" id="attachment_1676" style="width: 459px;"><a href="https://blog.mozilla.org/l10n/files/2024/05/llm1.png"><img alt="Screenshot of the LLM feature in Pontoon (after selecting the rephrase command)." class="size-full wp-image-1676" height="351" src="https://blog.mozilla.org/l10n/files/2024/05/llm1.png" width="449" /></a><p class="wp-caption-text" id="caption-attachment-1676">Enhanced translation output from the LLM rephrasing the initial Google Translate result.</p></div>
3533. <p>Furthering our community engagement, on April 29th, we hosted a Localization Fireside Chat. During this session, we discussed the new feature in depth and provided a live demonstration. Catch the highlights of our discussion at the following recordings (the LLM feature is discussed at the 7:22 mark):</p>
3534. <ul>
3535. <li><b>AirMozilla:</b><a href="https://mzl.la/localization-fireside-chat-2024-04-29"> View Recording</a></li>
3536. <li><b>YouTube: </b><a href="https://youtube.com/live/eUcHRDaaFe0?feature=share">View Recording</a></li>
3537. </ul>
3538. <h5>Performance improvements</h5>
3539. <p>At the end of the last year we’ve <a href="https://blog.mozilla.org/l10n/2023/12/20/2024-pontoon-survey-results/">asked</a> Mozilla localizers what areas of <a href="https://pontoon.mozilla.org/">Pontoon</a> would they like to see improved. Performance optimizations were one of the top-voted requests and we’re happy to report we’ve landed several speedups since the beginning of the year.</p>
3540. <p>Most notable improvements were made to the dashboards, with Contributors, Insights and Tags pages now loading in a fraction of the time they took to load earlier in the year. We’ve also improved the loading times of Permissions tab, Notifications page and some filters.</p>
3541. <p>As shown in the chart below, almost all the pages and actions will now take less time to load.</p>
3542. <div class="wp-caption aligncenter" id="attachment_1680" style="width: 610px;"><a href="https://blog.mozilla.org/l10n/files/2024/05/pontoon_perfs.png"><img alt="Chart showing the apdex score of several views in Pontoon." class="wp-image-1680 size-large" height="283" src="https://blog.mozilla.org/l10n/files/2024/05/pontoon_perfs-600x283.png" width="600" /></a><p class="wp-caption-text" id="caption-attachment-1680">Chart showing the improved apdex score of several views in Pontoon.</p></div>
3543. <h3>Events</h3>
3544. <p>Watch our latest localization virtual events <a href="https://mozilla.hosted.panopto.com/Panopto/Pages/Sessions/List.aspx#folderID=%220e65cd7b-1564-4b1c-9537-aff1000a5aa5%22">here</a>.</p>
3545. <p>Want to showcase an event coming up that your community is participating in? <a href="mailto:l10n-drivers@mozilla.org">Contact us</a> and we’ll include it.</p>
3546. <h3>Useful Links</h3>
3547. <ul>
3548. <li><a href="https://chat.mozilla.org/#/room/#l10n-community:mozilla.org">#l10n-community channel on Element (chat.mozilla.org)</a></li>
3549. <li><a href="https://discourse.mozilla.org/c/l10n/547">Localization category on Discourse</a></li>
3550. <li><a href="https://twitter.com/mozilla_l10n">Twitter</a></li>
3551. <li><a href="https://blog.mozilla.org/l10n/">L10n blog</a></li>
3552. </ul>
3553. <h3>Questions? Want to get involved?</h3>
3554. <p>If you want to get involved, or have any question about l10n, reach out to:</p>
3555. <ul>
3556. <li><a href="https://pontoon.mozilla.org/contributors/mZuzEFP7EcmgBBTbvtgJP2LFFTY/">Francesco Lodolo (flod)</a> – Engineering Manager</li>
3557. <li><a href="https://pontoon.mozilla.org/contributors/CMLZ_n1lNNSfQScLGE2yBmlS55w/">Bryan</a> – l10n Project Manager</li>
3558. <li><a href="https://pontoon.mozilla.org/contributors/3LPn77ppB_IQ9F6ruL5lw2IVrvQ/">Delphine</a> – l10n Project Manager for mobile</li>
3559. <li><a href="https://pontoon.mozilla.org/contributors/jIdunhnZ8Edgi9npILuSoFvf5ZY/">Peiying (CocoMo)</a> – l10n Project Manager for mozilla.org, marketing, and legal</li>
3560. <li><a href="https://pontoon.mozilla.org/contributors/m6r3HOfoijMdyeJNKKFHchjjRbw/">Francis</a> – l10n Project Manager for Common Voice, Mozilla Foundation</li>
3561. <li><a href="https://pontoon.mozilla.org/contributors/lY_FTvtnYcVoDP7JYZjMsm6tRno/">Théo Chevalier</a> – l10n Project Manager for Mozilla Foundation</li>
3562. <li><a href="https://pontoon.mozilla.org/contributors/dvgiVCmoeidF2xcqSnBHtpzLTFU/">Matjaž (mathjazz)</a> – Pontoon dev</li>
3563. <li><a href="https://pontoon.mozilla.org/contributors/pmz0uSCe_Mk9Td1cksHLI1y471k/">Eemeli</a> – Pontoon, Fluent dev</li>
3564. </ul>
3565. &lt;p&gt;Did you enjoy reading this report? &lt;a href=&quot;mailto:l10n-drivers@mozilla.org&quot;&gt;Let us know&lt;/a&gt; how we can improve it.&lt;/p&gt;</description>
3566. <pubDate>Thu, 02 May 2024 16:01:16 +0000</pubDate>
3567. <dc:creator>Francesco Lodolo [:flod]</dc:creator>
3568. </item>
3569. <item>
3570. <title>The Rust Programming Language Blog: Announcing Rust 1.78.0</title>
3571. <guid isPermaLink="true">https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html</guid>
3572. <link>https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html</link>
3573. <description>&lt;p&gt;The Rust team is happy to announce a new version of Rust, 1.78.0. Rust is a programming language empowering everyone to build reliable and efficient software.&lt;/p&gt;
3574. <p>If you have a previous version of Rust installed via <code>rustup</code>, you can get 1.78.0 with:</p>
3575. <pre><code class="language-console">$ rustup update stable
3576. </code></pre>
3577. <p>If you don't have it already, you can <a href="https://www.rust-lang.org/install.html">get <code>rustup</code></a> from the appropriate page on our website, and check out the <a href="https://doc.rust-lang.org/nightly/releases.html#version-1780-2024-05-02">detailed release notes for 1.78.0</a>.</p>
3578. <p>If you'd like to help us out by testing future releases, you might consider updating locally to use the beta channel (<code>rustup default beta</code>) or the nightly channel (<code>rustup default nightly</code>). Please <a href="https://github.com/rust-lang/rust/issues/new/choose">report</a> any bugs you might come across!</p>
3579. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html#whats-in-1780-stable" id="whats-in-1780-stable"></a>What's in 1.78.0 stable</h3>
3580. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html#diagnostic-attributes" id="diagnostic-attributes"></a>Diagnostic attributes</h4>
3581. <p>Rust now supports a <code>#[diagnostic]</code> attribute namespace to influence compiler error messages. These are treated as hints which the compiler is not <em>required</em> to use, and it is also not an error to provide a diagnostic that the compiler doesn't recognize. This flexibility allows source code to provide diagnostics even when they're not supported by all compilers, whether those are different versions or entirely different implementations.</p>
3582. <p>With this namespace comes the first supported attribute, <code>#[diagnostic::on_unimplemented]</code>, which can be placed on a trait to customize the message when that trait is required but hasn't been implemented on a type. Consider the example given in the <a href="https://github.com/rust-lang/rust/pull/119888/">stabilization pull request</a>:</p>
3583. <pre><code class="language-rust">#[diagnostic::on_unimplemented(
3584.    message = "My Message for `ImportantTrait<{A}>` is not implemented for `{Self}`",
3585.    label = "My Label",
3586.    note = "Note 1",
3587.    note = "Note 2"
3588. )]
3589. trait ImportantTrait<A> {}
3590.  
3591. fn use_my_trait(_: impl ImportantTrait<i32>) {}
3592.  
3593. fn main() {
3594.    use_my_trait(String::new());
3595. }
3596. </code></pre>
3597. <p>Previously, the compiler would give a builtin error like this:</p>
3598. <pre><code>error[E0277]: the trait bound `String: ImportantTrait<i32>` is not satisfied
3599.  --> src/main.rs:12:18
3600.   |
3601. 12 |     use_my_trait(String::new());
3602.   |     ------------ ^^^^^^^^^^^^^ the trait `ImportantTrait<i32>` is not implemented for `String`
3603.   |     |
3604.   |     required by a bound introduced by this call
3605.   |
3606. </code></pre>
3607. <p>With <code>#[diagnostic::on_unimplemented]</code>, its custom message fills the primary error line, and its custom label is placed on the source output. The original label is still written as help output, and any custom notes are written as well. (These exact details are subject to change.)</p>
3608. <pre><code>error[E0277]: My Message for `ImportantTrait<i32>` is not implemented for `String`
3609.  --> src/main.rs:12:18
3610.   |
3611. 12 |     use_my_trait(String::new());
3612.   |     ------------ ^^^^^^^^^^^^^ My Label
3613.   |     |
3614.   |     required by a bound introduced by this call
3615.   |
3616.   = help: the trait `ImportantTrait<i32>` is not implemented for `String`
3617.   = note: Note 1
3618.   = note: Note 2
3619. </code></pre>
3620. <p>For trait authors, this kind of diagnostic is more useful if you can provide a better hint than just talking about the missing implementation itself. For example, this is an abridged sample from the standard library:</p>
3621. <pre><code class="language-rust">#[diagnostic::on_unimplemented(
3622.    message = "the size for values of type `{Self}` cannot be known at compilation time",
3623.    label = "doesn't have a size known at compile-time"
3624. )]
3625. pub trait Sized {}
3626. </code></pre>
3627. <p>For more information, see the reference section on <a href="https://doc.rust-lang.org/nightly/reference/attributes/diagnostics.html#the-diagnostic-tool-attribute-namespace">the <code>diagnostic</code> tool attribute namespace</a>.</p>
3628. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html#asserting-unsafe-preconditions" id="asserting-unsafe-preconditions"></a>Asserting <code>unsafe</code> preconditions</h4>
3629. <p>The Rust standard library has a number of assertions for the preconditions of <code>unsafe</code> functions, but historically they have only been enabled in <code>#[cfg(debug_assertions)]</code> builds of the standard library to avoid affecting release performance. However, since the standard library is usually compiled and distributed in release mode, most Rust developers weren't ever executing these checks at all.</p>
3630. <p>Now, the condition for these assertions is delayed until code generation, so they will be checked depending on the user's own setting for debug assertions -- enabled by default in debug and test builds. This change helps users catch undefined behavior in their code, though the details of how much is checked are generally not stable.</p>
3631. <p>For example, <a href="https://doc.rust-lang.org/std/slice/fn.from_raw_parts.html"><code>slice::from_raw_parts</code></a> requires an aligned non-null pointer. The following use of a purposely-misaligned pointer has undefined behavior, and while if you were unlucky it may have <em>appeared</em> to "work" in the past, the debug assertion can now catch it:</p>
3632. <pre><code class="language-rust">fn main() {
3633.    let slice: &[u8] = &[1, 2, 3, 4, 5];
3634.    let ptr = slice.as_ptr();
3635.  
3636.    // Create an offset from `ptr` that will always be one off from `u16`'s correct alignment
3637.    let i = usize::from(ptr as usize & 1 == 0);
3638.    
3639.    let slice16: &[u16] = unsafe { std::slice::from_raw_parts(ptr.add(i).cast::<u16>(), 2) };
3640.    dbg!(slice16);
3641. }
3642. </code></pre>
3643. <pre><code>thread 'main' panicked at library/core/src/panicking.rs:220:5:
3644. unsafe precondition(s) violated: slice::from_raw_parts requires the pointer to be aligned and non-null, and the total size of the slice not to exceed `isize::MAX`
3645. note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
3646. thread caused non-unwinding panic. aborting.
3647. </code></pre>
3648. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html#deterministic-realignment" id="deterministic-realignment"></a>Deterministic realignment</h4>
3649. <p>The standard library has a few functions that change the alignment of pointers and slices, but they previously had caveats that made them difficult to rely on in practice, if you followed their documentation precisely. Those caveats primarily existed as a hedge against <code>const</code> evaluation, but they're only stable for non-<code>const</code> use anyway. They are now promised to have consistent runtime behavior according to their actual inputs.</p>
3650. <ul>
3651. <li>
3652. <p><a href="https://doc.rust-lang.org/std/primitive.pointer.html#method.align_offset"><code>pointer::align_offset</code></a> computes the offset needed to change a pointer to the given alignment. It returns <code>usize::MAX</code> if that is not possible, but it was previously permitted to <em>always</em> return <code>usize::MAX</code>, and now that behavior is removed.</p>
3653. </li>
3654. <li>
3655. <p><a href="https://doc.rust-lang.org/std/primitive.slice.html#method.align_to"><code>slice::align_to</code></a> and <a href="https://doc.rust-lang.org/std/primitive.slice.html#method.align_to_mut"><code>slice::align_to_mut</code></a> both transmute slices to an aligned middle slice and the remaining unaligned head and tail slices. These methods now promise to return the largest possible middle part, rather than allowing the implementation to return something less optimal like returning everything as the head slice.</p>
3656. </li>
3657. </ul>
3658. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html#stabilized-apis" id="stabilized-apis"></a>Stabilized APIs</h4>
3659. <ul>
3660. <li><a href="https://doc.rust-lang.org/stable/std/io/struct.Stdin.html#impl-Read-for-%26Stdin"><code>impl Read for &Stdin</code></a></li>
3661. <li><a href="https://github.com/rust-lang/rust/pull/113833/">Accept non <code>'static</code> lifetimes for several <code>std::error::Error</code> related implementations</a></li>
3662. <li><a href="https://github.com/rust-lang/rust/pull/114655/">Make <code>impl<Fd: AsFd></code> impl take <code>?Sized</code></a></li>
3663. <li><a href="https://doc.rust-lang.org/stable/std/io/struct.Error.html#impl-From%3CTryReserveError%3E-for-Error"><code>impl From<TryReserveError> for io::Error</code></a></li>
3664. </ul>
3665. <p>These APIs are now stable in const contexts:</p>
3666. <ul>
3667. <li><a href="https://doc.rust-lang.org/stable/std/sync/struct.Barrier.html#method.new"><code>Barrier::new()</code></a></li>
3668. </ul>
3669. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html#compatibility-notes" id="compatibility-notes"></a>Compatibility notes</h4>
3670. <ul>
3671. <li>As <a href="https://blog.rust-lang.org/2024/02/26/Windows-7.html">previously announced</a>, Rust 1.78 has increased its minimum requirement to Windows 10 for the following targets:
3672. <ul>
3673. <li><code>x86_64-pc-windows-msvc</code></li>
3674. <li><code>i686-pc-windows-msvc</code></li>
3675. <li><code>x86_64-pc-windows-gnu</code></li>
3676. <li><code>i686-pc-windows-gnu</code></li>
3677. <li><code>x86_64-pc-windows-gnullvm</code></li>
3678. <li><code>i686-pc-windows-gnullvm</code></li>
3679. </ul>
3680. </li>
3681. <li>Rust 1.78 has upgraded its bundled LLVM to version 18, completing the announced <a href="https://blog.rust-lang.org/2024/03/30/i128-layout-update.html"><code>u128</code>/<code>i128</code> ABI change</a> for x86-32 and x86-64 targets. Distributors that use their own LLVM older than 18 may still face the calling convention bugs mentioned in that post.</li>
3682. </ul>
3683. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html#other-changes" id="other-changes"></a>Other changes</h4>
3684. <p>Check out everything that changed in <a href="https://github.com/rust-lang/rust/releases/tag/1.78.0">Rust</a>, <a href="https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#cargo-178-2024-05-02">Cargo</a>, and <a href="https://github.com/rust-lang/rust-clippy/blob/master/CHANGELOG.md#rust-178">Clippy</a>.</p>
3685. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/05/02/Rust-1.78.0.html#contributors-to-1780" id="contributors-to-1780"></a>Contributors to 1.78.0</h3>
3686. &lt;p&gt;Many people came together to create Rust 1.78.0. We couldn't have done it without all of you. &lt;a href=&quot;https://thanks.rust-lang.org/rust/1.78.0/&quot;&gt;Thanks!&lt;/a&gt;&lt;/p&gt;</description>
3687. <pubDate>Thu, 02 May 2024 00:00:00 +0000</pubDate>
3688. <dc:creator>The Rust Release Team</dc:creator>
3689. </item>
3690. <item>
3691. <title>Dave Townsend: Tests don't replace Code Review</title>
3692. <guid isPermaLink="true">https://www.oxymoronical.com/blog/2024/05/tests-dont-replace-code-review/</guid>
3693. <link>https://www.oxymoronical.com/blog/2024/05/tests-dont-replace-code-review/</link>
3694. <description>&lt;img alt=&quot;Featured image of post Tests don't replace Code Review&quot; src=&quot;https://www.oxymoronical.com/blog/2024/05/tests-dont-replace-code-review/240401-105514.jpg&quot; /&gt;&lt;p&gt;I frequently see a bold claim come up in tech circles. That as a team you’re wasting time by doing code reviews. You should instead rely on automated tests to catch bugs. This surprises me because I can’t imagine anyone thinking that such a blanket statement is true. But then most of the time this is brought up in places like Twitter where nuance is impossible and engagement farming is rife. Still it got me thinking about why I think code review is important even if you have amazing tests.&lt;/p&gt;
3695. <p>Before I elaborate I’ll point out what should be obvious. Different projects have different needs. You shouldn’t listen to me tell you that you must do code review any more than you should listen to anyone else tell you that you must not do code review. Be pragmatic in all things. Beware one-size-fits-all statements (in almost any context).</p>
3696. <p>We’ve been religiously performing code review on every (well almost every) patch at Mozilla since well before I joined the project which was quite some time ago. And in that time I’ve seen Firefox go from having practically no automated tests to a set of automated test suites that if run end to end on a single machine (which is impossible but let’s ignore that) would take nearly <strong>two months</strong> (😱) to complete. And in that time I don’t think I’ve ever heard anyone suggest we should stop doing code review for anything that actually ships to users (we do allow documentation changes with no review). Why?</p>
3697. <h4 id="a-good-set-of-automated-tests-doesnt-just-magically-appear">
3698.    <a class="header-anchor" href="http://www.oxymoronical.com/blog/category/technical/mozilla/feed#a-good-set-of-automated-tests-doesnt-just-magically-appear">#</a>
3699.    A good set of automated tests doesn’t just magically appear
3700. </h4><p>Let’s start with the obvious.</p>
3701. <p>Someone has to have written all of those tests. And others have to have verified all that. And even if your test suite is already perfect, how do you know that the developer building a new feature has also included the tests necessary to verify that feature going forwards?</p>
3702. <p>There are some helpful tools that exist, like code coverage. But these are more informative than indicative. Useful to track but should rarely be used by themselves.</p>
3703. <h4 id="garbage-unmaintainable-code-passes-tests">
3704.    <a class="header-anchor" href="http://www.oxymoronical.com/blog/category/technical/mozilla/feed#garbage-unmaintainable-code-passes-tests">#</a>
3705.    Garbage unmaintainable code passes tests
3706. </h4><p>There are usually many ways to fix a bug or implement a feature. Some of those will be clear readable code with appropriate comments that a random developer in three years time can look at and understand quickly. Others will be spaghetti code that is to all intents and purposes obfuscated. Got a bug in there? It may take ten times longer to fix it. Lint rules can help with this to some extent, but a human code reviewer is going to spot unreadable code a mile away.</p>
3707. <h4 id="you-cannot-test-everything">
3708.    <a class="header-anchor" href="http://www.oxymoronical.com/blog/category/technical/mozilla/feed#you-cannot-test-everything">#</a>
3709.    You cannot test everything
3710. </h4><p>It’s often not feasible to test for every possible case. Anywhere your code interacts with anything outside of itself, like a filesystem or a network, is going to have cases that are really hard to simulate. What if memory runs out at a critical moment? What if the OS suddenly decides that the disk is not writable? These are cases we have to handle all the time in Firefox. You could say we should build abstractions around everything so that tests can simulate all those cases. But abstractions are not cheap and performance is pretty critical for us.</p>
3711. <h4 id="but-im-a-100x-developer-none-of-this-applies-to-me">
3712.    <a class="header-anchor" href="http://www.oxymoronical.com/blog/category/technical/mozilla/feed#but-im-a-100x-developer-none-of-this-applies-to-me">#</a>
3713.    But I’m a 100x developer, none of this applies to me
3714. </h4><p>I don’t care how senior a developer you are, you’ll make mistakes. I sure do. Now it’s true that there is something to be said for adjusting your review approach based on the developer who wrote the code. If I’m reviewing a patch by a junior developer I’m going to go over the patch with a fine tooth-comb and then when they re-submit I’m going to take care to make sure they addressed all my changes. Less so with a senior developer who I know knows the code at hand.</p>
3715. <h4 id="so-do-tests-help-with-code-review-at-all">
3716.    <a class="header-anchor" href="http://www.oxymoronical.com/blog/category/technical/mozilla/feed#so-do-tests-help-with-code-review-at-all">#</a>
3717.    So do tests help with code review at all?
3718. </h4><p>Absolutely!</p>
3719. <p>Tests are there to automatically spot problems, ideally before a change even reaches the review stage. Code review is there to fill in the gaps. You can mostly skip over worrying about whether this breaks well tested functionality (just don’t assume all functionality is well tested!). Instead you can focus on what the change is doing that cannot be tested:</p>
3720. <ul>
3721. <li>Is it actually fixing the problem at hand?</li>
3722. <li>Does it include appropriate changes to the automated tests?</li>
3723. <li>Is the code maintainable?</li>
3724. <li>Is the approach going to cause problems for other changes down the road?</li>
3725. <li>Could there be performance issues?</li>
3726. </ul>
3727. &lt;p&gt;Code review and automated tests are complimentary. I believe you’ll get the best result when you employ both sensibly. Assuming you have the resources to do so of course. I don’t think large projects can do without both.&lt;/p&gt;</description>
3728. <pubDate>Wed, 01 May 2024 22:02:00 +0000</pubDate>
3729. </item>
3730. <item>
3731. <title>Mozilla Thunderbird: Thunderbird Monthly Development Digest: April 2024</title>
3732. <guid isPermaLink="false">https://blog.thunderbird.net/?p=1717</guid>
3733. <link>https://blog.thunderbird.net/2024/05/thunderbird-monthly-development-digest-april-2024/</link>
3734. <description>&lt;p&gt;&lt;img alt=&quot;Graphic with text &amp;quot;Thunderbird Development Digest April 2024,&amp;quot; featuring abstract ASCII art on a dark Thunderbird logo background.&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2024/04/dev-digest-april-2024-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
3735. <div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
3736. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=de&u=https://blog.thunderbird.net/2024/05/thunderbird-monthly-development-digest-april-2024/" rel="noreferrer noopener" target="_blank">Auf Deutsch übersetzen</a></div>
3737.  
3738.  
3739.  
3740. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=fr&u=https://blog.thunderbird.net/2024/05/thunderbird-monthly-development-digest-april-2024/" rel="noreferrer noopener" target="_blank">Traduire en français</a></div>
3741.  
3742.  
3743.  
3744. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=ja&u=https://blog.thunderbird.net/2024/05/thunderbird-monthly-development-digest-april-2024/" rel="noreferrer noopener" target="_blank">日本語に翻訳</a></div>
3745. </div>
3746.  
3747.  
3748.  
3749. <p>Hello Thunderbird Community, and welcome back to the monthly Thunderbird development digest. April just ended and we’re running at full speed into May. We’re only a couple of months away from the next ESR, so things are landing faster and we’re seeing the finalization of a lot of parallel efforts.</p>
3750.  
3751.  
3752.  
3753. <h3 class="wp-block-heading"><strong>20-Year-Old bugs</strong></h3>
3754.  
3755.  
3756.  
3757. <p>Something that has been requested for almost 20 years finally landed on Daily. The ability to control the display of recipients in the message list and better distinguish unknown addresses from those saved in the Address Book was finally implemented in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=243258">Bug 243258 – Show email address in message list</a>.</p>
3758.  
3759.  
3760.  
3761. <p>This is one of the many examples of features that in the past were very complicated and tricky to implement, but that we were finally able to address thanks to the improvements of our architecture and being able to work with a more flexible and modular code.</p>
3762.  
3763.  
3764.  
3765. <p>We’re aiming at going through those very very old requests and slowly addressing them when possible.</p>
3766.  
3767.  
3768.  
3769. <h3 class="wp-block-heading"><strong>Exchange alpha</strong></h3>
3770.  
3771.  
3772.  
3773. <p>More <a href="https://blog.thunderbird.net/2024/04/adventures-in-rust-bringing-exchange-support-to-thunderbird/">Exchange support</a> improvements and features are landing on Daily almost…daily (pun intended). If you want to test things with a local build, you can follow <a href="https://thunderbird.topicbox.com/groups/planning/T05e94ced3641f616/exchange-testing-our-patience">this overview from Ikey.</a></p>
3774.  
3775.  
3776.  
3777. <p>We will soon look at the possibility of enabling Rust builds by default, making sure that all users will be able to consume our Rust code from next beta, and only needing to switch a pref in order to test Exchange.</p>
3778.  
3779.  
3780.  
3781. <h3 class="wp-block-heading"><strong>Folder compaction</strong></h3>
3782.  
3783.  
3784.  
3785. <p>If you’ve been tracking our most recent struggles, you’re probably aware of one of the lingering annoying issues which sees the bubbling up of the size of the user profile caused by local folder corruption.</p>
3786.  
3787.  
3788.  
3789. <p>Ben dive bombed into the code and found a spaghetti mess that was hard to untangle. You can read more about his exploration and discoveries in his <a href="https://thunderbird.topicbox.com/groups/developers/T181eda13fce07dd9/folder-compaction-rewrite">recent post on TB-Planning</a>.</p>
3790.  
3791.  
3792.  
3793. <p>We’re aiming to land this code hopefully before the end of the week and start calling for some testing and feedback from the community to ensure that all the various issues have been addressed correctly.</p>
3794.  
3795.  
3796.  
3797. <p>You can follow the progress in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890448">Bug 1890448 – Rewrite folder compaction</a>.</p>
3798.  
3799.  
3800.  
3801. <h3 class="wp-block-heading"><strong>Cards View</strong></h3>
3802.  
3803.  
3804.  
3805. <p>If you’re running Beta or Daily, you might have noticed some very fancy new UI for the Cards View. This has been a culmination of many weeks of UX analysis to ensure a flexible and consistent hover, selection, and focus state.</p>
3806.  
3807.  
3808.  
3809. <p>Micah and Sol identified a total of 27 different interaction states on that list, and implementing visual consistency while guaranteeing optimal accessibility levels for all operating systems and potential custom themes was not easy.</p>
3810.  
3811.  
3812.  
3813. <p>We’re very curious to hear your feedback.</p>
3814.  
3815.  
3816.  
3817. <h3 class="wp-block-heading"><strong>Context menu</strong></h3>
3818.  
3819.  
3820.  
3821. <p>A more refined and updated context menu for the message list also landed on Daily.</p>
3822.  
3823.  
3824.  
3825. <p>A very detailed UX exploration and overview of the implementation was <a href="https://thunderbird.topicbox.com/groups/ux/T3d84faa372bf41a8/message-context-menu-updates">shared on the UX Mailing list</a> a while ago.</p>
3826.  
3827.  
3828.  
3829. <p>This update is only the first step of many more to come, so we apologize in advance if some things are not super polished or things seem temporarily off.</p>
3830.  
3831.  
3832.  
3833. <h3 class="wp-block-heading"><strong>ESR Preview</strong></h3>
3834.  
3835.  
3836.  
3837. <p>If you’re curious about what the next ESR will look like or checking new features, please consider downloading and installing Beta (preferably in another directory to not override your current profile.) Help us test this new upcoming release and find bugs early.</p>
3838.  
3839.  
3840.  
3841. <p><em>As usual, if you want to see things as they land you can always check the <a href="https://hg.mozilla.org/comm-central/pushloghtml">pushlog </a>and <a href="https://ftp.mozilla.org/pub/thunderbird/nightly/2024/">try running daily</a>, which would be immensely helpful for catching bugs early.</em></p>
3842.  
3843.  
3844.  
3845. <p>See ya next month.</p>
3846.  
3847.  
3848.  
3849. <p><strong>Alessandro Castellani</strong> <em>(he, him)<br /></em><strong>Director, Desktop and Mobile Apps</strong></p>
3850.  
3851.  
3852.  
3853. <figure class="wp-block-pullquote" style="border-width: 2px; border-radius: 10px; font-style: normal; font-weight: 400;"><blockquote><p>If you’re interested in joining the technical discussion around Thunderbird development, consider joining one or several of our <a href="https://thunderbird.topicbox.com">mailing list groups here</a>. </p></blockquote></figure>
3854. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2024/05/thunderbird-monthly-development-digest-april-2024/&quot;&gt;Thunderbird Monthly Development Digest: April 2024&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>
3855. <pubDate>Wed, 01 May 2024 16:30:14 +0000</pubDate>
3856. <dc:creator>Alessandro Castellani</dc:creator>
3857. </item>
3858. <item>
3859. <title>This Week In Rust: This Week in Rust 545</title>
3860. <guid isPermaLink="false">tag:this-week-in-rust.org,2024-05-01:/blog/2024/05/01/this-week-in-rust-545/</guid>
3861. <link>https://this-week-in-rust.org/blog/2024/05/01/this-week-in-rust-545/</link>
3862. <description>&lt;p&gt;Hello and welcome to another issue of &lt;em&gt;This Week in Rust&lt;/em&gt;!
3863. <a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
3864. This is a weekly summary of its progress and community.
3865. Want something mentioned? Tag us at <a href="https://twitter.com/ThisWeekInRust">@ThisWeekInRust</a> on Twitter or <a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social, or <a href="https://github.com/rust-lang/this-week-in-rust">send us a pull request</a>.
3866. Want to get involved? <a href="https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md">We love contributions</a>.</p>
3867. <p><em>This Week in Rust</em> is openly developed <a href="https://github.com/rust-lang/this-week-in-rust">on GitHub</a> and archives can be viewed at <a href="https://this-week-in-rust.org/">this-week-in-rust.org</a>.
3868. If you find any errors in this week's issue, <a href="https://github.com/rust-lang/this-week-in-rust/pulls">please submit a PR</a>.</p>
3869. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#updates-from-rust-community">Updates from Rust Community</a></h4>
3870.  
3871.  
3872. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#newsletters">Newsletters</a></h5>
3873. <ul>
3874. <li><a href="https://thisweekinbevy.com/issue/2024-04-29-motion-blur-visualizations-and-beautiful-renders">Motion Blur, Visualizations, and beautiful renders</a></li>
3875. </ul>
3876. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#projecttooling-updates">Project/Tooling Updates</a></h5>
3877. <ul>
3878. <li><a href="https://github.com/r3bl-org/r3bl-open-core/blob/main/CHANGELOG.md#v051-2024-04-28">r3bl_trerminal_async v0.5.1 released</a></li>
3879. <li><a href="https://github.com/gnp/minbpe-rs">minbpe-rs v0.1.0: Port of Andrej Karpathy's <code>minbpe</code> to Rust</a></li>
3880. <li><a href="https://selium.com/news/introducing-selium-log">Message retention and replay with Selium</a></li>
3881. </ul>
3882. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#observationsthoughts">Observations/Thoughts</a></h5>
3883. <ul>
3884. <li><a href="https://loglog.games/blog/leaving-rust-gamedev/">Leaving Rust gamedev after 3 years</a></li>
3885. <li><a href="https://blog.yoshuawuyts.com/tasks-are-the-wrong-abstraction/">Tasks are the wrong abstraction</a></li>
3886. <li><a href="https://cybernetist.com/2024/04/25/go-or-rust-just-listen-to-the-bots/">Go or Rust? Just Listen to the Bots</a></li>
3887. <li><a href="https://hugopeters.me/posts/21/">Cracking the Cryptic (with Z3 and Rust)</a></li>
3888. <li><a href="https://blog.dureuill.net/articles/nolife-0-4/">So, you want to write an unsafe crate</a></li>
3889. <li><a href="https://alonely0.github.io/blog/unions/">Designing an efficient memory layout in Rust with unsafe & unions, or, an overlong guide in avoiding dynamic dispatch</a></li>
3890. <li><a href="https://www.shuttle.rs/blog/2024/04/25/event-driven-services-using-kafka-rust">Event driven Microservices using Kafka and Rust</a></li>
3891. <li><a href="https://www.niklaslong.ch/deadline/">Writing ergonomic async assertions in Rust</a></li>
3892. <li><a href="https://medium.com/@sam.van.overmeire/making-an-html-parsing-script-a-hundred-times-faster-with-rayon-5ed952c9011c">Making an HTML parsing script a hundred times faster with Rayon</a></li>
3893. <li><a href="https://mirekdlugosz.com/blog/2024/rust-binaries-stability/">Rust binaries stability</a></li>
3894. <li>[audio] <a href="https://rustacean-station.org/episode/orhun-parmaksiz/">Ratatui with Orhun Parmaksiz :: Rustacean Station</a></li>
3895. <li><a href="https://www.hezmatt.org/~mpalmer/blog/2024/05/01/the-mediocre-programmers-guide-to-rust.html">The Mediocre Programmer's Guide to Rust</a></li>
3896. </ul>
3897. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust-walkthroughs">Rust Walkthroughs</a></h5>
3898. <ul>
3899. <li><a href="https://blog.jetbrains.com/rust/2024/04/26/boosting-dev-experience-with-serverless-rust-in-rustrover/">Boosting Dev Experience with Serverless Rust in RustRover</a></li>
3900. <li><a href="https://developerlife.com/2024/04/28/rust-polymorphism-dyn-impl-trait-objects-for-testing-and-extensibiity/">developerlife.com - Rust Polymorphism, dyn, impl, using existing traits, trait objects for testing and extensibility</a></li>
3901. <li><a href="https://hegdenu.net/posts/performance-optimization-flamegraph-divan/">Performance optimization with flamegraph and Divan</a></li>
3902. </ul>
3903. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#research">Research</a></h5>
3904. <ul>
3905. <li><a href="https://rust-digger.code-maven.com/news/interesting-homepages">Rust Digger: There are 4,907 interesting Crate homepages</a></li>
3906. </ul>
3907. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#miscellaneous">Miscellaneous</a></h5>
3908. <ul>
3909. <li><a href="https://skanehira.github.io/writing-a-wasm-runtime-in-rust/">Writing A Wasm Runtime In Rust</a></li>
3910. <li><a href="https://dev.to/szabgab/github-sponsor-rust-developer-andrew-gallant-burntsushi-31lh">GitHub Sponsor Rust developer Andrew Gallant (BurntSushi)</a></li>
3911. <li><a href="https://lwn.net/SubscriberLink/970565/ac5ffc2e9ad20f1e/">Giving Rust a chance for in-kernel codecs</a></li>
3912. <li><a href="https://zed.dev/blog/zed-decoded-rope-sumtree">Zed Decoded: Rope & SumTree</a></li>
3913. <li><a href="https://rust.code-maven.com/fibonacci-iterator">An almost infinite Fibonacci Iterator</a></li>
3914. <li>[video] <a href="https://www.youtube.com/watch?v=hmQr4fq6sH0">From C to Rust: Bringing Rust Abstractions to Embedded Linux</a></li>
3915. </ul>
3916. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#crate-of-the-week">Crate of the Week</a></h4>
3917. <p>This week's crate is <a href="https://codeberg.org/RatCornu/efs">efs</a>, a no-std ext2 filesystem implementation with plans to add other file systems in the future.</p>
3918. <p>Another week completely devoid of suggestions, but llogiq stays hopeful he won't have to dig for next week's crate all by himself.</p>
3919. <p><a href="https://users.rust-lang.org/t/crate-of-the-week/2704">Please submit your suggestions and votes for next week</a>!</p>
3920. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#call-for-testing">Call for Testing</a></h4>
3921. <p>An important step for RFC implementation is for people to experiment with the
3922. implementation and give feedback, especially before stabilization.  The following
3923. RFCs would benefit from user testing before moving forward:</p>
3924. <ul>
3925. <li><em>No calls for testing were issued this week.</em></li>
3926. </ul>
3927. <p>If you are a feature implementer and would like your RFC to appear on the above list, add the new <code>call-for-testing</code>
3928. label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
3929. need testing.</p>
3930. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers">Call for Participation; projects and speakers</a></h4>
3931. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#cfp-projects">CFP - Projects</a></h5>
3932. <p>Always wanted to contribute to open-source projects but did not know where to start?
3933. Every week we highlight some tasks from the Rust community for you to pick and get started!</p>
3934. <p>Some of these tasks may also have mentors available, visit the task page for more information.</p>
3935. <ul>
3936. <li><em>No Calls for papers or presentations were submitted this week.</em></li>
3937. </ul>
3938. <p>If you are a Rust project owner and are looking for contributors, please submit tasks <a href="https://users.rust-lang.org/t/twir-call-for-participation/4821">here</a>.</p>
3939. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#cfp-speakers">CFP - Speakers</a></h5>
3940. <p>Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.</p>
3941. <ul>
3942. <li><a href="https://www.papercall.io/eurorust-2024">EuroRust 2024</a>| Closes 2024-06-03 | Vienna, Austria & online | Event date: 2024-10-10</li>
3943. <li><a href="https://scientificcomputing.rs/">Scientific Computing in Rust 2024</a>| Closes 2024-06-14 | online | Event date: 2024-07-17 - 2024-07-19</li>
3944. <li><a href="https://www.papercall.io/conf42-rustlang-2024">Conf42 Rustlang 2024</a> | Closes 2024-07-22 | online | Event date: 2024-08-22</li>
3945. </ul>
3946. <p>If you are an event organizer hoping to expand the reach of your event, please submit a link to the submission website through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a>.</p>
3947. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#updates-from-the-rust-project">Updates from the Rust Project</a></h4>
3948. <p>409 pull requests were <a href="https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2024-04-23..2024-04-30">merged in the last week</a></p>
3949. <ul>
3950. <li><a href="https://github.com/rust-lang/rust/pull/124210">abort a process when FD ownership is violated</a></li>
3951. <li><a href="https://github.com/rust-lang/rust/pull/124321">add support for run-make-support unit tests to be run with bootstrap</a></li>
3952. <li><a href="https://github.com/rust-lang/rust/pull/124382">ast: generalize item kind visiting</a></li>
3953. <li><a href="https://github.com/rust-lang/rust/pull/124508">coverage: avoid hard-coded values when visiting logical ops</a></li>
3954. <li><a href="https://github.com/rust-lang/rust/pull/124507">coverage: replace boolean options with a <code>CoverageLevel enum</code></a></li>
3955. <li><a href="https://github.com/rust-lang/rust/pull/120845">debuginfo: stabilize <code>-Z debug-macros</code>, <code>-Z collapse-macro-debuginfo</code> and <code>#[collapse_debuginfo]</code></a></li>
3956. <li><a href="https://github.com/rust-lang/rust/pull/122500">delegation: support renaming, and async, const, extern "ABI" and C-variadic functions</a></li>
3957. <li><a href="https://github.com/rust-lang/rust/pull/123680">deny gen keyword in <code>edition_2024_compat</code> lints</a></li>
3958. <li><a href="https://github.com/rust-lang/rust/pull/122598">deref patterns: lower deref patterns to MIR</a></li>
3959. <li><a href="https://github.com/rust-lang/rust/pull/124313">detect borrow error involving sub-slices and suggest <code>split_at_mut</code></a></li>
3960. <li><a href="https://github.com/rust-lang/rust/pull/124099">disallow ambiguous attributes on expressions</a></li>
3961. <li><a href="https://github.com/rust-lang/rust/pull/124425">do not ICE on invalid consts when walking mono-reachable blocks</a></li>
3962. <li><a href="https://github.com/rust-lang/rust/pull/124374">don't ICE when <code>codegen_select_candidate</code> returns ambiguity in new solver</a></li>
3963. <li><a href="https://github.com/rust-lang/rust/pull/124169">don't fatal when calling <code>expect_one_of</code> when recovering arg in <code>parse_seq</code></a></li>
3964. <li><a href="https://github.com/rust-lang/rust/pull/123531">enforce closure args + return type are WF</a></li>
3965. <li><a href="https://github.com/rust-lang/rust/pull/124394">fix ICE on invalid const param types</a></li>
3966. <li><a href="https://github.com/rust-lang/rust/pull/124057">fix ICE when ADT tail has type error</a></li>
3967. <li><a href="https://github.com/rust-lang/rust/pull/124281">fix weak memory bug in TLS on Windows</a></li>
3968. <li><a href="https://github.com/rust-lang/rust/pull/124333">improve diagnostic for unknown <code>--print</code> request</a></li>
3969. <li><a href="https://github.com/rust-lang/rust/pull/124200">improve handling of expr→field errors</a></li>
3970. <li><a href="https://github.com/rust-lang/rust/pull/124504">mark unions non-const-propagatable in <code>KnownPanicsLint</code> without calling layout</a></li>
3971. <li><a href="https://github.com/rust-lang/rust/pull/124269">pretty-print parenthesis around binary in postfix match</a></li>
3972. <li><a href="https://github.com/rust-lang/rust/pull/124136">provide more context and suggestions in borrowck errors involving closures</a></li>
3973. <li><a href="https://github.com/rust-lang/rust/pull/124444">record certainty of <code>evaluate_added_goals_and_make_canonical_response</code> call in candidate</a></li>
3974. <li><a href="https://github.com/rust-lang/rust/pull/124379">remove special-casing for <code>SimplifiedType</code> for next solver</a></li>
3975. <li><a href="https://github.com/rust-lang/rust/pull/124463">rename <code>inhibit_union_abi_opt()</code> to <code>inhibits_union_abi_opt()</code></a></li>
3976. <li><a href="https://github.com/rust-lang/rust/pull/124381">renamed <code>DerivedObligation</code> to <code>WellFormedDeriveObligation</code></a></li>
3977. <li><a href="https://github.com/rust-lang/rust/pull/123792">require explicitly marking closures as coroutines</a></li>
3978. <li><a href="https://github.com/rust-lang/rust/pull/121557">restrict promotion of <code>const fn</code> calls</a></li>
3979. <li><a href="https://github.com/rust-lang/rust/pull/121298">set writable and <code>dead_on_unwind</code> attributes for sret arguments</a></li>
3980. <li><a href="https://github.com/rust-lang/rust/pull/124334">strengthen tracking issue policy with consequences</a></li>
3981. <li><a href="https://github.com/rust-lang/rust/pull/119650">suggest ref mut for pattern matching assignment</a></li>
3982. <li><a href="https://github.com/rust-lang/rust/pull/122591">suggest using type args directly instead of equality constraint</a></li>
3983. <li><a href="https://github.com/rust-lang/rust/pull/122317">use fulfillment in method probe, not evaluation</a></li>
3984. <li><a href="https://github.com/rust-lang/rust/pull/124415">use probes more aggressively in new solver</a></li>
3985. <li><a href="https://github.com/rust-lang/rust/pull/124067">weak lang items are not allowed to be <code>#[track_caller]</code></a></li>
3986. <li><a href="https://github.com/rust-lang/rust/pull/124220">miri: detect wrong vtables in wide pointers</a></li>
3987. <li><a href="https://github.com/rust-lang/miri/pull/3510">miri: <code>unix_sigpipe</code>: don't inline DEFAULT, just use it from rustc</a></li>
3988. <li><a href="https://github.com/rust-lang/miri/pull/3493">miri: add <code>-Zmiri-env-set</code> to set environment variables without modifying the host environment</a></li>
3989. <li><a href="https://github.com/rust-lang/miri/pull/3517">miri env: split up Windows and Unix environment variable handling</a></li>
3990. <li><a href="https://github.com/rust-lang/miri/pull/3524">miri: file descriptors: make write take &mut self</a></li>
3991. <li><a href="https://github.com/rust-lang/miri/pull/3492">miri: implement LLVM x86 AVX2 intrinsics</a></li>
3992. <li><a href="https://github.com/rust-lang/miri/pull/3512">miri: make miri-script a workspace root</a></li>
3993. <li><a href="https://github.com/rust-lang/miri/pull/3523">miri: use the interpreted program's TZ variable in <code>localtime_r</code></a></li>
3994. <li><a href="https://github.com/rust-lang/miri/pull/3502">miri: windows: basic support for GetUserProfileDirectoryW</a></li>
3995. <li><a href="https://github.com/rust-lang/rust/pull/104087">stabilise <code>inline_const</code></a></li>
3996. <li><a href="https://github.com/rust-lang/rust/pull/123909">stabilize <code>Utf8Chunks</code></a></li>
3997. <li><a href="https://github.com/rust-lang/rust/pull/124498">stabilize <code>non_null_convenience</code></a></li>
3998. <li><a href="https://github.com/rust-lang/rust/pull/124335">stabilize <code>std::path::absolute</code></a></li>
3999. <li><a href="https://github.com/rust-lang/rust/pull/124076">stabilize <code>io_error_downcast</code></a></li>
4000. <li><a href="https://github.com/rust-lang/rust/pull/124003">deLLVMize some intrinsics (use <code>u32</code> instead of <code>Self</code> in some integer intrinsics)</a></li>
4001. <li><a href="https://github.com/rust-lang/rust/pull/122053">stop using LLVM <code>struct</code> types for alloca</a></li>
4002. <li><a href="https://github.com/rust-lang/rust/pull/124387"><code>thread_local</code>: be excruciatingly explicit in dtor code</a></li>
4003. <li><a href="https://github.com/rust-lang/rust/pull/124484">fix <code>offset_of!</code> returning a temporary</a></li>
4004. <li><a href="https://github.com/rust-lang/rust/pull/124432">relax <code>A: Clone</code> bound for <code>rc::Weak::into_raw_and_alloc</code></a></li>
4005. <li><a href="https://github.com/rust-lang/rust/pull/124410"><code>PathBuf</code>: replace transmuting by accessor functions</a></li>
4006. <li><a href="https://github.com/rust-lang/rustc_codegen_gcc/pull/504">codegen_gcc: some fixes for aarch64</a></li>
4007. <li><a href="https://github.com/rust-lang/rustc_codegen_gcc/pull/508">codegen_gcc: some more fixes and workarounds for Aarch64</a></li>
4008. <li><a href="https://github.com/rust-lang/cargo/pull/13819">cargo: alias: Aliases without subcommands should not panic</a></li>
4009. <li><a href="https://github.com/rust-lang/cargo/pull/13812">cargo: lints: Don't always inherit workspace lints</a></li>
4010. <li><a href="https://github.com/rust-lang/cargo/pull/13790">cargo install: Don't respect MSRV for non-local installs</a></li>
4011. <li><a href="https://github.com/rust-lang/cargo/pull/13798">cargo toml: Be more forceful with underscore/dash redundancy</a></li>
4012. <li><a href="https://github.com/rust-lang/cargo/pull/13800">cargo toml: Don't double-warn when underscore is used in workspace dep</a></li>
4013. <li><a href="https://github.com/rust-lang/cargo/pull/13804">cargo toml: Remove underscore field support in 2024</a></li>
4014. <li><a href="https://github.com/rust-lang/cargo/pull/13713">cargo toml: Warn, rather than fail publish, if a target is excluded</a></li>
4015. <li><a href="https://github.com/rust-lang/cargo/pull/13788">cargo toml: remove support for inheriting badges</a></li>
4016. <li><a href="https://github.com/rust-lang/cargo/pull/13801">cargo: note where lint was set</a></li>
4017. <li><a href="https://github.com/rust-lang/cargo/pull/13797">cargo: cleanup linting system</a></li>
4018. <li><a href="https://github.com/rust-lang/cargo/pull/13817">cargo: fix target entry in .gitignore</a></li>
4019. <li><a href="https://github.com/rust-lang/cargo/pull/13793">cargo: fix warning suppression for config.toml vs config compat symlinks</a></li>
4020. <li><a href="https://github.com/rust-lang/rust-bindgen/pull/2812">bindgen: add dynamic loading of variable</a></li>
4021. <li><a href="https://github.com/rust-lang/rust-bindgen/pull/2809">bindgen: remove which dependency</a></li>
4022. <li><a href="https://github.com/rust-lang/rust-bindgen/pull/2808">bindgen: simplify Rust to Clang target conversion</a></li>
4023. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12726">clippy: <code>single_match</code>(<code>_else</code>) may be machine applicable</a></li>
4024. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12702">clippy: <code>non_canonical_partial_ord_impl</code>: Fix emitting warnings which conflict with <code>needless_return</code></a></li>
4025. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12736">clippy: <code>type_complexity</code>: Fix duplicate errors</a></li>
4026. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12694">clippy: check if closure as method arg has read access in <code>collection_is_never_read</code></a></li>
4027. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12725">clippy: configurably allow <code>useless_vec</code> in tests</a></li>
4028. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12624">clippy: fix <code>large_stack_arrays</code> linting in <code>vec</code> macro</a></li>
4029. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12722">clippy: fix false positive in <code>cast_possible_truncation</code></a></li>
4030. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12734">clippy: suppress <code>readonly_write_lock</code> for underscore-prefixed bindings</a></li>
4031. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17131">rust-analyzer: different error code of "no such field" error based on variant type</a></li>
4032. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17157">rust-analyzer: don't retry position relient requests and version resolve data</a></li>
4033. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17151">rust-analyzer: fix attributes on generic parameters colliding in item tree</a></li>
4034. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17153">rust-analyzer: fix doc comment desugaring for proc-macros</a></li>
4035. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17135">rust-analyzer: fix expression scopes not being calculated for inline consts</a></li>
4036. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17145">rust-analyzer: fix source roots not always being created when necessary</a></li>
4037. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/16972">rust-analyzer: make <code>cargo run</code> always available for binaries</a></li>
4038. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17144">rust-analyzer: manual: remove suggestion of rust-project.json example</a></li>
4039. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17021">rust-analyzer: support hovering limits for adts</a></li>
4040. <li><a href="https://github.com/rust-lang/rustfmt/pull/6148">rustfmt: fix wrong indentation on inner attribute</a></li>
4041. </ul>
4042. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage">Rust Compiler Performance Triage</a></h5>
4043. <p>Several non-noise changes this week, with both improvements and regresions
4044. coming as a result. Overall compiler performance is roughly neutral across the
4045. week.</p>
4046. <p>Triage done by <strong>@simulacrum</strong>.
4047. Revision range: <a href="https://perf.rust-lang.org/?start=a77f76e26302e9a084fb321817675b1dfc1dcd63&end=c65b2dc935c27c0c8c3997c6e8d8894718a2cb1a&absolute=false&stat=instructions%3Au">a77f76e2..c65b2dc9</a></p>
4048. <p>2 Regressions, 2 Improvements, 3 Mixed; 1 of them in rollups
4049. 51 artifact comparisons made in total</p>
4050. <p><a href="https://github.com/rust-lang/rustc-perf/blob/master/triage/2024-04-29.md">Full report here</a></p>
4051. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#approved-rfcs"></a><a href="https://github.com/rust-lang/rfcs/commits/master">Approved RFCs</a></h5>
4052. <p>Changes to Rust follow the Rust <a href="https://github.com/rust-lang/rfcs#rust-rfcs">RFC (request for comments) process</a>. These
4053. are the RFCs that were approved for implementation this week:</p>
4054. <ul>
4055. <li><a href="https://github.com/rust-lang/rfcs/pull/3614">experimental project goal program for 2024 H2</a></li>
4056. </ul>
4057. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#final-comment-period">Final Comment Period</a></h5>
4058. <p>Every week, <a href="https://www.rust-lang.org/team.html">the team</a> announces the 'final comment period' for RFCs and key PRs
4059. which are reaching a decision. Express your opinions now.</p>
4060. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rfcs"></a><a href="https://github.com/rust-lang/rfcs/labels/final-comment-period">RFCs</a></h6>
4061. <ul>
4062. <li>[disposition: merge] <a href="https://github.com/rust-lang/rfcs/pull/3617">Precise capturing</a></li>
4063. <li>[disposition: merge] <a href="https://github.com/rust-lang/rfcs/pull/3484">Unsafe Extern Blocks</a></li>
4064. <li>[disposition: merge] <a href="https://github.com/rust-lang/rfcs/pull/3336">MaybeDangling</a></li>
4065. </ul>
4066. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#tracking-issues-prs">Tracking Issues & PRs</a></h6>
4067. <a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust"></a><a href="https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc">Rust</a>
4068. <ul>
4069. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/issues/98934">Add <code>Option::take_if</code></a></li>
4070. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124532">elaborate obligations in coherence</a></li>
4071. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124297">Allow coercing functions whose signature differs in opaque types in their defining scope into a shared function pointer type</a></li>
4072. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/120924">Let's <code>#[expect]</code> some lints: <code>Stabilize lint_reasons</code> (RFC 2383)</a></li>
4073. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/issues/94035">Tracking Issue for ASCII trim functions on byte slices</a></li>
4074. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124097">Add <code>IntoIterator</code> for <code>Box<[T]></code> + edition 2024-specific lints</a></li>
4075. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124108">Add <code>Box<[T; N]>: IntoIterator</code> without any method dispatch hacks</a></li>
4076. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/124148">rustdoc-search: search for references</a></li>
4077. <li>[disposition: close] <a href="https://github.com/rust-lang/rust/issues/82219">Extra trait bound makes function body fail to typecheck</a></li>
4078. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/120248">Make casts of pointers to trait objects stricter</a></li>
4079. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/issues/119128">Tracking Issue for split_at_checked</a></li>
4080. </ul>
4081. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#new-and-updated-rfcs"></a><a href="https://github.com/rust-lang/rfcs/pulls">New and Updated RFCs</a></h6>
4082. <ul>
4083. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3617">Precise capturing</a></li>
4084. </ul>
4085. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#upcoming-events">Upcoming Events</a></h4>
4086. <p>Rusty Events between 2024-05-01 - 2024-05-29 🦀</p>
4087. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#virtual">Virtual</a></h5>
4088. <ul>
4089. <li>2024-05-01 | Virtual (Cardiff, UK) | <a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/">Rust and C++ Cardiff</a><ul>
4090. <li><a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/events/300325526/"><strong>Rust for Rustaceans Book Club: Chapter 5 - Project Structure</strong></a></li>
4091. </ul>
4092. </li>
4093. <li>2024-05-01 | Virtual (Indianapolis, IN, US) | <a href="https://www.meetup.com/indyrs/">Indy Rust</a><ul>
4094. <li><a href="https://www.meetup.com/indyrs/events/299047895/"><strong>Indy.rs - with Social Distancing</strong></a></li>
4095. </ul>
4096. </li>
4097. <li>2024-05-02 | Virtual (Aarhus, DK) | <a href="https://www.meetup.com/rust-aarhus-organizers/">Rust Aarhus Organizers</a><ul>
4098. <li><a href="https://www.meetup.com/rust-aarhus-organizers/events/300416935/"><strong>Rust Aarhus Organizers: Status</strong></a></li>
4099. </ul>
4100. </li>
4101. <li>2024-05-02 | Virtual (Charlottesville, NC, US) | <a href="https://www.meetup.com/charlottesville-rust-meetup/">Charlottesville Rust Meetup</a><ul>
4102. <li><a href="https://www.meetup.com/charlottesville-rust-meetup/events/298368804/"><strong>Crafting Interpreters in Rust Collaboratively</strong></a></li>
4103. </ul>
4104. </li>
4105. <li>2024-05-02 | Virtual (London, UK) | <a href="https://www.meetup.com/women-in-rust/">Women in Rust</a><ul>
4106. <li><a href="https://www.meetup.com/women-in-rust/events/300208946/"><strong>Women in Rust: Lunch & Learn! (Virtual)</strong></a></li>
4107. </ul>
4108. </li>
4109. <li>2024-05-07 | Virtual (Buffalo, NY) | <a href="https://www.meetup.com/buffalo-rust-meetup/">Buffalo Rust Meetup</a><ul>
4110. <li><a href="https://www.meetup.com/buffalo-rust-meetup/events/300100279/"><strong>Buffalo Rust User Group</strong></a></li>
4111. </ul>
4112. </li>
4113. <li>2024-05-09 | Virtual (Berlin, DE) | <a href="https://berline.rs/">OpenTechSchool Berlin</a> + <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
4114. <li><a href="https://meet.jit.si/RustHackAndLearnBerlin"><strong>Rust Hack and Learn</strong></a> | <a href="https://www.meetup.com/rust-berlin/events/298477697/"><strong>Mirror: Rust Hack n Learn Meetup</strong></a></li>
4115. </ul>
4116. </li>
4117. <li>2024-05-09 | Virtual (Israel) | <a href="https://rust.org.il/">Rust in Israel</a><ul>
4118. <li><a href="https://www.meetup.com/code-mavens/events/300144781/"><strong>Rust at Microsoft, Tel Aviv - Are we embedded yet?</strong></a></li>
4119. </ul>
4120. </li>
4121. <li>2024-05-09 | Virtual (Nuremberg/Nürnberg, DE) | <a href="https://www.meetup.com/rust-noris/">Rust Nuremberg</a><ul>
4122. <li><a href="https://www.meetup.com/rust-noris/events/297945257/"><strong>Rust Nürnberg online</strong></a></li>
4123. </ul>
4124. </li>
4125. <li>2024-05-14 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/">Dallas Rust</a><ul>
4126. <li><a href="https://www.meetup.com/dallasrust/events/298341699/"><strong>Second Tuesday</strong></a></li>
4127. </ul>
4128. </li>
4129. <li>2024-05-14 | Virtual (Halifax, NS, CA) | <a href="https://www.meetup.com/rust-tell-halifax/">Rust Halifax</a><ul>
4130. <li><a href="https://www.meetup.com/rust-tell-halifax/events/300437775/"><strong>Rust&Tell - Halifax</strong></a></li>
4131. </ul>
4132. </li>
4133. <li>2024-05-14 | Virtual + In-Person (München/Munich, DE) | <a href="https://www.meetup.com/rust-munich/">Rust Munich</a><ul>
4134. <li><a href="https://www.meetup.com/rust-munich/events/298507657/"><strong>Rust Munich 2024 / 1 - hybrid (Rescheduled)</strong></a></li>
4135. </ul>
4136. </li>
4137. <li>2024-05-15 | Virtual (Vancouver, BC, CA) | <a href="https://www.meetup.com/vancouver-rust/">Vancouver Rust</a><ul>
4138. <li><a href="https://www.meetup.com/vancouver-rust/events/298542323/"><strong>Rust Study/Hack/Hang-out</strong></a></li>
4139. </ul>
4140. </li>
4141. <li>2024-05-16 | Virtual (Charlottesville, VA, US) | <a href="https://www.meetup.com/charlottesville-rust-meetup/">Charlottesville Rust Meetup</a><ul>
4142. <li><a href="https://www.meetup.com/charlottesville-rust-meetup/events/298312423/"><strong>Crafting Interpreters in Rust Collaboratively</strong></a></li>
4143. </ul>
4144. </li>
4145. <li>2024-05-21 | Virtual (Washington, DC, US) | <a href="https://www.meetup.com/rustdc/">Rust DC</a><ul>
4146. <li><a href="https://www.meetup.com/rustdc/events/299346490/"><strong>Mid-month Rustful—forensic parsing via Artemis</strong></a></li>
4147. </ul>
4148. </li>
4149. <li>2024-05-23 | Virtual (Berlin, DE) | <a href="https://berline.rs/">OpenTechSchool Berlin</a> + <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
4150. <li><a href="https://meet.jit.si/RustHackAndLearnBerlin"><strong>Rust Hack and Learn</strong></a> | <a href="https://www.meetup.com/rust-berlin/events/298477699/"><strong>Mirror: Rust Hack n Learn Meetup</strong></a></li>
4151. </ul>
4152. </li>
4153. <li>2024-05-28 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/">Dallas Rust</a><ul>
4154. <li><a href="https://www.meetup.com/dallasrust/events/300533392/"><strong>Second Tuesday</strong></a></li>
4155. </ul>
4156. </li>
4157. </ul>
4158. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#africa">Africa</a></h5>
4159. <ul>
4160. <li>2024-05-04 | Kampala, UG | <a href="https://www.eventbrite.com/o/rust-circle-kampala-65249289033">Rust Circle Kampala</a><ul>
4161. <li><a href="https://www.eventbrite.com/e/rust-circle-meetup-tickets-628763176587?aff=ebdsoporgprofile"><strong>Rust Circle Meetup</strong></a></li>
4162. </ul>
4163. </li>
4164. </ul>
4165. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#asia">Asia</a></h5>
4166. <ul>
4167. <li>2024-05-11 | Bangalore, IN | <a href="https://hasgeek.com/rustbangalore">Rust Bangalore</a><ul>
4168. <li><a href="https://hasgeek.com/rustbangalore/may-2024-rustacean-meetup/"><strong>May 2024 Rustacean meetup</strong></a></li>
4169. </ul>
4170. </li>
4171. </ul>
4172. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#europe">Europe</a></h5>
4173. <ul>
4174. <li>2024-05-01 | Köln/Cologne, DE | <a href="https://www.meetup.com/rustcologne/">Rust Cologne</a><ul>
4175. <li><a href="https://www.meetup.com/rustcologne/events/300610856/"><strong>This Month in Rust, May</strong></a></li>
4176. </ul>
4177. </li>
4178. <li>2024-05-01 | Utrecht, NL | <a href="https://nl-rse.org/events/2024-05-01-meetup">NL-RSE Community</a><ul>
4179. <li><a href="https://www.eventbrite.nl/e/nl-rse-rust-meetup-tickets-871056271757"><strong>NL-RSE RUST meetup</strong></a></li>
4180. </ul>
4181. </li>
4182. <li>2024-05-06 | Delft, NL | <a href="https://www.gosim.org/">GOSIM</a><ul>
4183. <li><a href="https://europe2024.gosim.org/"><strong>GOSIM Europe 2024</strong></a></li>
4184. </ul>
4185. </li>
4186. <li>2024-05-07 & 2024-05-08 | Delft, NL | <a href="https://rustnl.org/">RustNL</a><ul>
4187. <li><a href="https://2024.rustnl.org/"><strong>RustNL 2024</strong></a></li>
4188. </ul>
4189. </li>
4190. <li>2024-05-07 | Oxford, UK | <a href="https://www.meetup.com/oxford-rust-meetup-group/">Oxfrod Rust Meetup Group</a><ul>
4191. <li><a href="https://www.meetup.com/oxford-rust-meetup-group/events/300567559/"><strong>More Rust - Generics, constraints, safety.</strong></a></li>
4192. </ul>
4193. </li>
4194. <li>2024-05-08 | Cambridge, UK | <a href="https://www.meetup.com/cambridge-rust-meetup/">Cambridge Rust Meetup</a><ul>
4195. <li><a href="https://www.meetup.com/cambridge-rust-meetup/events/300573716/"><strong>Monthly Rust Meetup</strong></a></li>
4196. </ul>
4197. </li>
4198. <li>2024-05-09 | Gdańsk, PL | <a href="https://www.meetup.com/rust-gdansk/">Rust Gdansk</a><ul>
4199. <li><a href="https://www.meetup.com/rust-gdansk/events/299766774/"><strong>Rust Gdansk Meetup #2</strong></a></li>
4200. </ul>
4201. </li>
4202. <li>2024-05-14 | London, UK | <a href="https://www.meetup.com/rust-london-user-group/">Rust London User Group</a><ul>
4203. <li><a href="https://www.meetup.com/rust-london-user-group/events/300715979/"><strong>Rust Hack & Learn May 2024</strong></a></li>
4204. </ul>
4205. </li>
4206. <li>2024-05-14 | Virtual + In-Person (München/Munich, DE) | <a href="https://www.meetup.com/rust-munich/">Rust Munich</a><ul>
4207. <li><a href="https://www.meetup.com/rust-munich/events/298507657/"><strong>Rust Munich 2024 / 1 - hybrid (Rescheduled)</strong></a></li>
4208. </ul>
4209. </li>
4210. <li>2024-05-14 | Prague, CZ | <a href="https://www.meetup.com/rust-prague/">Rust Prague</a><ul>
4211. <li><a href="https://www.meetup.com/rust-prague/events/300566374/"><strong>Rust Meetup Prague (May 2024)</strong></a></li>
4212. </ul>
4213. </li>
4214. <li>2024-05-14 | Reading, UK | <a href="https://www.meetup.com/reading-rust-workshop/">Reading Rust Workshop</a><ul>
4215. <li><a href="https://www.meetup.com/reading-rust-workshop/events/299694474/"><strong>Reading Rust Meetup</strong></a></li>
4216. </ul>
4217. </li>
4218. <li>2024-05-16 | Augsburg, DE | <a href="https://www.meetup.com/rust-meetup-augsburg/">Rust Meetup Augsburg</a><ul>
4219. <li><a href="https://www.meetup.com/rust-meetup-augsburg/events/300174327/"><strong>Augsburg Rust Meetup #7</strong></a></li>
4220. </ul>
4221. </li>
4222. <li>2024-05-16 | Paris, FR | <a href="https://mobilizon.fr/@rust_paris">Rust Paris</a><ul>
4223. <li><a href="https://mobilizon.fr/events/14b51ccc-211f-400f-9615-707d9d871e78"><strong>Paris Rust Meetup #68</strong></a></li>
4224. </ul>
4225. </li>
4226. <li>2024-05-21 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus/">Rust Aarhus</a><ul>
4227. <li><a href="https://www.meetup.com/rust-aarhus/events/300307155/"><strong>Hack Night</strong></a></li>
4228. </ul>
4229. </li>
4230. <li>2024-05-21 | Zurich, CH | <a href="https://www.meetup.com/rust-zurich/">Rust Zurich</a><ul>
4231. <li><a href="https://www.meetup.com/rust-zurich/events/300513957/"><strong>Save the date - Mai Meetup</strong></a></li>
4232. </ul>
4233. </li>
4234. <li>2024-05-22 | Leiden, NL | <a href="https://www.meetup.com/freshminds-future-proof-software-development/">Future-proof Software Development by FreshMinds</a><ul>
4235. <li><a href="https://www.meetup.com/freshminds-future-proof-software-development/events/300566391/"><strong>Coding Dojo Session</strong></a></li>
4236. </ul>
4237. </li>
4238. <li>2024-05-23 | Bern, CH | <a href="https://www.meetup.com/de-DE/rust-bern/">Rust Bern</a><ul>
4239. <li><a href="https://www.meetup.com/rust-bern/events/300286917/"><strong>2024 Rust Talks Bern #2</strong></a></li>
4240. </ul>
4241. </li>
4242. <li>2024-05-24 | Bordeaux, FR | <a href="https://www.meetup.com/bordeaux-rust/">Rust Bordeaux</a><ul>
4243. <li><a href="https://www.meetup.com/bordeaux-rust/events/300723854/"><strong>Rust Bordeaux #3: Discussions</strong></a></li>
4244. </ul>
4245. </li>
4246. <li>2024-05-28 - 2024-05-30 | Berlin, DE | <a href="https://oxidizeconf.com/">Oxidize</a><ul>
4247. <li><a href="https://oxidizeconf.com/"><strong>Oxidize Conf 2024</strong></a></li>
4248. </ul>
4249. </li>
4250. </ul>
4251. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#north-america">North America</a></h5>
4252. <ul>
4253. <li>2024-05-04 | Cambridge, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
4254. <li><a href="https://www.meetup.com/bostonrust/events/300116701/"><strong>Kendall Rust Lunch, May 4</strong></a></li>
4255. </ul>
4256. </li>
4257. <li>2024-05-08 | Detroit, MI, US | <a href="https://www.meetup.com/detroitrust/">Detroit Rust</a><ul>
4258. <li><a href="https://www.meetup.com/detroitrust/events/300763859/"><strong>Rust Social - Ann Arbor</strong></a></li>
4259. </ul>
4260. </li>
4261. <li>2024-05-09 | Spokane, WA, US | <a href="https://www.meetup.com/spokane-rust/">Spokane Rust</a><ul>
4262. <li><a href="https://www.meetup.com/spokane-rust/events/300020003/"><strong>Monthly Meetup: Topic TBD!</strong></a></li>
4263. </ul>
4264. </li>
4265. <li>2024-05-12 | Brookline, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
4266. <li><a href="https://www.meetup.com/bostonrust/events/300116747/"><strong>Coolidge Corner Brookline Rust Lunch, May 12</strong></a></li>
4267. </ul>
4268. </li>
4269. <li>2024-05-14 | Minneapolis, MN, US | <a href="https://www.meetup.com/minneapolis-rust-meetup/">Minneapolis Rust Meetup</a><ul>
4270. <li><a href="https://www.meetup.com/minneapolis-rust-meetup/events/300744140/"><strong>Minneapolis Rust Meetup Happy Hour</strong></a></li>
4271. </ul>
4272. </li>
4273. <li>2024-05-16 | Seattle, WA, US | <a href="https://www.meetup.com/seattle-rust-user-group/">Seattle Rust User Group</a><ul>
4274. <li><a href="https://www.meetup.com/seattle-rust-user-group/events/299509369/"><strong>Seattle Rust User Group Meetup</strong></a></li>
4275. </ul>
4276. </li>
4277. <li>2024-05-20 | Somerville, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
4278. <li><a href="https://www.meetup.com/bostonrust/events/300116765/"><strong>Ball Square Rust Lunch, May 20</strong></a></li>
4279. </ul>
4280. </li>
4281. <li>2024-05-21 | San Francisco, CA, US | <a href="https://www.meetup.com/san-francisco-rust-study-group/">San Francisco Rust Study Group</a><ul>
4282. <li><a href="https://www.meetup.com/san-francisco-rust-study-group/events/299186931/"><strong>Rust Hacking in Person</strong></a></li>
4283. </ul>
4284. </li>
4285. <li>2024-05-22 | Austin, TX, US | <a href="https://www.meetup.com/rust-atx/">Rust ATX</a><ul>
4286. <li><a href="https://www.meetup.com/rust-atx/events/xvkdgtygchbdc/"><strong>Rust Lunch - Fareground</strong></a></li>
4287. </ul>
4288. </li>
4289. <li>2024-05-25 | Chicago, IL, US | <a href="https://www.meetup.com/deep-dish-rust/">Deep Dish Rust</a><ul>
4290. <li><a href="https://www.meetup.com/deep-dish-rust/events/300665520/"><strong>Rust Talk Double Feature</strong></a></li>
4291. </ul>
4292. </li>
4293. </ul>
4294. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#oceania">Oceania</a></h5>
4295. <ul>
4296. <li>2024-05-02 | Brisbane City, QL, AU | <a href="https://www.meetup.com/rust-brisbane/">Rust Brisbane</a><ul>
4297. <li><a href="https://www.meetup.com/rust-brisbane/events/300647409/"><strong>May Meetup</strong></a></li>
4298. </ul>
4299. </li>
4300. </ul>
4301. <p>If you are running a Rust event please add it to the <a href="https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com">calendar</a> to get
4302. it mentioned here. Please remember to add a link to the event too.
4303. Email the <a href="mailto:community-team@rust-lang.org">Rust Community Team</a> for access.</p>
4304. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#jobs">Jobs</a></h4>
4305.  
4306.  
4307. <p>Please see the latest <a href="https://www.reddit.com/r/rust/comments/1bpg8b8/official_rrust_whos_hiring_thread_for_jobseekers/">Who's Hiring thread on r/rust</a></p>
4308. <h3><a class="toclink" href="http://this-week-in-rust.org/atom.xml#quote-of-the-week">Quote of the Week</a></h3>
4309. <blockquote>
4310. <p>"I'll never!"
4311. "No, never is in the 2024 Edition."
4312. "But never can't be this year, it's never!"
4313. "Well we're trying to make it happen now!"
4314. "But never isn't now?" "I mean technically, now never is the unit."
4315. "But how do you have an entire unit if it never happens?"</p>
4316. </blockquote>
4317. <p>– <a href="https://rust-lang.zulipchat.com/#narrow/stream/268952-edition/topic/should.20have.20been.202025.20edition/near/435845944">Jubilee on Zulip</a></p>
4318. <p>Thanks to <a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328/1565">Jacob Pratt</a> for the suggestion! </p>
4319. <p><a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328">Please submit quotes and vote for next week!</a></p>
4320. <p><em>This Week in Rust is edited by: <a href="https://github.com/nellshamrell">nellshamrell</a>, <a href="https://github.com/llogiq">llogiq</a>, <a href="https://github.com/cdmistman">cdmistman</a>, <a href="https://github.com/ericseppanen">ericseppanen</a>, <a href="https://github.com/extrawurst">extrawurst</a>, <a href="https://github.com/andrewpollack">andrewpollack</a>, <a href="https://github.com/U007D">U007D</a>, <a href="https://github.com/kolharsam">kolharsam</a>, <a href="https://github.com/joelmarcey">joelmarcey</a>, <a href="https://github.com/mariannegoldin">mariannegoldin</a>, <a href="https://github.com/bennyvasquez">bennyvasquez</a>.</em></p>
4321. <p><em>Email list hosting is sponsored by <a href="https://foundation.rust-lang.org/">The Rust Foundation</a></em></p>
4322. &lt;p&gt;&lt;small&gt;&lt;a href=&quot;https://www.reddit.com/r/rust/comments/1ci5khm/this_week_in_rust_545/&quot;&gt;Discuss on r/rust&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;</description>
4323. <pubDate>Wed, 01 May 2024 04:00:00 +0000</pubDate>
4324. <dc:creator>TWiR Contributors</dc:creator>
4325. </item>
4326. <item>
4327. <title>William Durand: Moziversary #6</title>
4328. <guid isPermaLink="false">https://williamdurand.fr/2024/05/01/moziversary-6</guid>
4329. <link>https://williamdurand.fr/2024/05/01/moziversary-6/</link>
4330. <description>&lt;p&gt;&lt;em&gt;Today is my sixth Moziversary 🎂 I joined Mozilla as a full-time employee on
4331. May 1st, 2018. I previously blogged in <del>2019</del>, <a href="https://williamdurand.fr/2020/05/01/moziversary-2/">2020</a>, <a href="https://williamdurand.fr/2021/05/01/moziversary-3/">2021</a>, <a href="https://williamdurand.fr/2022/05/01/moziversary-4/">2022</a>,
4332. and <a href="https://williamdurand.fr/2023/05/01/moziversary-5/">2023</a>.</em></p>
4333.  
4334. <p>Last year, I mainly contributed to Firefox for Android as the lead engineer on a
4335. project called “Add-ons General Availability (GA)”. The goal was to allow for
4336. more add-ons on this platform. Success! <a href="https://addons.mozilla.org/android/">More than a thousand extensions are now
4337. available on Android</a> 🎉</p>
4338.  
4339. <p>In addition, I worked on a Firefox feature called <a href="https://support.mozilla.org/kb/quarantined-domains">Quarantined Domains</a> and
4340. implemented a new abuse report form on <a href="https://addons.mozilla.org/">addons.mozilla.org</a> (AMO) to comply
4341. with the Digital Services Act (DSA). I was also involved in two other cross-team
4342. efforts related to the Firefox installation funnel. I investigated various
4343. issues (<em>e.g.</em> this <a href="https://bugzilla.opensuse.org/show_bug.cgi?id=1221531#c22">openSUSE bug</a>), and I coordinated the deprecation of
4344. <a href="https://discourse.mozilla.org/t/upgraded-add-on-signatures/129599">weak add-on signatures</a> and some more changes around certificates
4345. lately, which is why I wrote <a href="https://williamdurand.fr/xpidump/">xpidump</a>.</p>
4346.  
4347. <p>Phew! There is no shortage of work.</p>
4348.  
4349. <p>When I moved to the WebExtensions team in 2022, <a href="https://williamdurand.fr/2022/01/25/new-team-mozilla/">I wrote about this incredible
4350. challenge</a>. I echoed this sentiment several months later in my <a href="https://williamdurand.fr/2022/05/01/moziversary-4/">2022
4351. Moziversary update</a>. I couldn’t imagine how much I would achieve in two
4352. years…</p>
4353.  
4354. <p>Back then, I didn’t know what the next step in my career would be. I have been
4355. aiming to bridge the gap between the AMO and WebExtensions engineering teams
4356. since at least <a href="https://williamdurand.fr/2021/05/01/moziversary-3/">2021</a> and that <em>is</em> my “next step”.</p>
4357.  
4358. <p>I recently took a new role as Add-ons Tech Lead. This is the continuation of
4359. what I’ve been doing for some time but that comes with new challenges and
4360. opportunities as well. We’ll see how it goes but I am excited!</p>
4361.  
4362. &lt;p&gt;I’ll be forever grateful to my manager and coworkers. Thank you ❤️&lt;/p&gt;</description>
4363. <pubDate>Wed, 01 May 2024 00:00:00 +0000</pubDate>
4364. </item>
4365. <item>
4366. <title>Don Marti: blog fix: remove stray files</title>
4367. <guid isPermaLink="true">https://blog.zgp.org/blog-remove-stray-files/</guid>
4368. <link>https://blog.zgp.org/blog-remove-stray-files/</link>
4369. <description>&lt;p&gt;Another update from the blog. Quick recap: I’m re-doing this blog with mostly Pandoc and make, with a few helper scripts.&lt;/p&gt; &lt;p&gt;This is a personal web site and can be broken sometimes, and one of the breakage problems was: oops, I removed a draft post from the directory of source files (in &lt;a href=&quot;https://commonmark.org/&quot;&gt;CommonMark&lt;/a&gt;) but the HTML version got built and put in &lt;code&gt;public&lt;/code&gt; and copied to the server, possibly also affecting the &lt;code&gt;index.html&lt;/code&gt; and the RSS feed.&lt;/p&gt; &lt;p&gt;If you’re reading the RSS and got some half-baked drafts, that’s why.&lt;/p&gt; &lt;p&gt;So, to fix it, I need to ask &lt;code&gt;make&lt;/code&gt; if there’s anything in the &lt;code&gt;public&lt;/code&gt; directory that doesn’t have a corresponding source file or files and remove it. Quick helper script:&lt;/p&gt;   &lt;p&gt;That should mean a better RSS reading experience since you shouldn’t get it cluttered up with drafts if I make a mistake.&lt;/p&gt; &lt;p&gt;But I’m sure I have plenty of other mistakes I can make.&lt;/p&gt; &lt;h3&gt;Related&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/scale-2025/&quot;&gt;planning for SCALE 2025&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/automatically-run-make/&quot;&gt;Automatically run make when a file changes&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/favicon/&quot;&gt;Hey kids, favicon!&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/responsive-ascii/&quot;&gt;responsive ascii art&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;Bonus links&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;https://www.citationneeded.news/we-can-have-a-different-web/&quot;&gt;We can have a different web&lt;/a&gt; &lt;q&gt;Nothing about the web has changed that prevents us from going back. If anything, it’s become a lot easier.&lt;/q&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.wired.com/story/meta-section-230-users-algorithm/&quot;&gt;A Lawsuit Argues Meta Is Required by Law to Let You Control Your Own Feed&lt;/a&gt; (Section 230 protection for a research extension? Makes sense to me.)&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://platformpapers.substack.com/p/effects-of-banning-targeted-advertising&quot;&gt;Effects of Banning Targeted Advertising&lt;/a&gt; (The top 10 percent of Android apps for kids did better after an ad personalization policy change, while the bottom 90 percent lost revenue. If Sturgeon’s Law applies to Android apps, the average under-13 user might be better off?)&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.wheresyoured.at/in-response-to-google/&quot;&gt;In Response To Google&lt;/a&gt; (Does anyone else notice more and more people working on ways to fix their personal information environment because of the search quality crisis? This blog series from Ed Zitron has some good background.)&lt;/p&gt;</description>
4370. <pubDate>Wed, 01 May 2024 00:00:00 +0000</pubDate>
4371. </item>
4372. <item>
4373. <title>The Rust Programming Language Blog: Announcing Google Summer of Code 2024 selected projects</title>
4374. <guid isPermaLink="true">https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html</guid>
4375. <link>https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html</link>
4376. <description>&lt;p&gt;The Rust Project is &lt;a href=&quot;https://blog.rust-lang.org/2024/02/21/Rust-participates-in-GSoC-2024.html&quot;&gt;participating&lt;/a&gt; in &lt;a href=&quot;https://summerofcode.withgoogle.com&quot;&gt;Google Summer of Code (GSoC) 2024&lt;/a&gt;, a global program organized by Google which is designed to bring new contributors to the world of open-source.&lt;/p&gt;
4377. <p>In February, we published a list of <a href="https://github.com/rust-lang/google-summer-of-code">GSoC project ideas</a>, and started discussing these projects with potential GSoC applicants on our <a href="https://rust-lang.zulipchat.com/#narrow/stream/421156-gsoc">Zulip</a>. We were pleasantly surprised by the amount of people that wanted to participate in these projects and that led to many fruitful discussions with members of various Rust teams. Some of them even immediately began contributing to various repositories of the Rust Project, even before GSoC officially started!</p>
4378. <p>After the initial discussions, GSoC applicants prepared and submitted their project proposals. We received 65 (!) proposals in total. We are happy to see that there was so much interest, given that this is the first time the Rust Project is participating in GSoC.</p>
4379. <p>A team of mentors primarily composed of Rust Project contributors then thoroughly examined the submitted proposals. GSoC required us to produce a ranked list of the best proposals, which was a challenging task in itself since Rust is a big project with many priorities! We went through many rounds of discussions and had to consider many factors, such as prior conversations with the given applicant, the quality and scope of their proposal, the importance of the proposed project for the Rust Project and its wider community, but also the availability of mentors, who are often volunteers and thus have limited time available for mentoring.</p>
4380. <p>In many cases, we had multiple proposals that aimed to accomplish the same goal. Therefore, we had to pick only one per project topic despite receiving several high-quality proposals from people we'd love to work with. We also often had to choose between great proposals targeting different work within the same Rust component to avoid overloading a single mentor with multiple projects.</p>
4381. <p>In the end, we narrowed the list down to twelve best proposals, which we felt was the maximum amount that we could realistically support with our available mentor pool. We submitted this list and eagerly awaited how many of these twelve proposals would be accepted into GSoC.</p>
4382. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html#selected-projects" id="selected-projects"></a>Selected projects</h3>
4383. <p>On the 1st of May, Google has announced the accepted projects. We are happy to announce that <code>9</code> proposals out of the twelve that we have submitted were accepted by Google, and will thus participate in Google Summer of Code 2024! Below you can find the list of accepted proposals (in alphabetical order), along with the names of their authors and the assigned mentor(s):</p>
4384. <ul>
4385. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/hADSyIDV">Adding lint-level configuration to cargo-semver-checks</a></strong> by Max Carr, mentored by Predrag Gruevski</li>
4386. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/zxxeGZMt">Implementation of a Faster Register Allocator For Cranelift</a></strong> by d-sonuga, mentored by Chris Fallin and Amanieu d'Antras</li>
4387. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/MeyNanKI">Improve Rust benchmark suite</a></strong> by s7tya, mentored by Jakub Beránek</li>
4388. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/jjnidpgn">Move cargo shell completions to Rust</a></strong> by shanmu, mentored by Ed Page</li>
4389. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/P5BC91Hr">Rewriting Esoteric, Error-Prone Makefile Tests Using Robust Rust Features</a></strong> by Julien Robert, mentored by Jieyou Xu</li>
4390. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/gHEu3vxc">Rewriting the Rewrite trait</a></strong> by SeoYoung Lee, mentored by Yacin Tmimi</li>
4391. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/IIHP5ozV">Rust to .NET compiler - add support for compiling & running cargo tests</a></strong> by Fractal Fir, mentored by Jack Huey</li>
4392. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/kXG0mZoj">Sandboxed and Deterministic Proc Macro using Wasm</a></strong> by Apurva Mishra, mentored by David Lattimore</li>
4393. <li><strong><a href="https://summerofcode.withgoogle.com/programs/2024/projects/rk1Ey4hN">Tokio async support in Miri</a></strong> by Tiffany Pek Yuan, mentored by Oli Scherer</li>
4394. </ul>
4395. <p><strong>Congratulations to all applicants whose project was selected!</strong> The mentors are looking forward to working with you on these exciting projects to improve the Rust ecosystem. You can expect to hear from us soon, so that we can start coordinating the work on your GSoC projects.</p>
4396. <p>We would also like to thank all the applicants whose proposal was sadly not accepted, for their interactions with the Rust community and contributions to various Rust projects. There were some great proposals that did not make the cut, in large part because of limited review capacity. However, even if your proposal was not accepted, we would be happy if you would consider contributing to the projects that got you interested, even outside GSoC! Our <a href="https://github.com/rust-lang/google-summer-of-code">project idea list</a> is still actual, and could serve as a general entry point for contributors that would like to work on projects that would help the Rust Project maintainers and the Rust ecosystem.</p>
4397. <p>Assuming our involvement in GSoC 2024 is successful, there's a good chance we'll participate next year as well (though we can't promise anything yet) and we hope to receive your proposals again in the future! We also are planning to participate in similar programs in the very near future. Those announcements will come in separate blog posts, so make sure to subscribe to this blog so that you don't miss anything.</p>
4398. &lt;p&gt;The accepted GSoC projects will run for several months. After GSoC 2024 finishes (in autumn of 2024), we plan to publish a blog post in which we will summarize the outcome of the accepted projects.&lt;/p&gt;</description>
4399. <pubDate>Wed, 01 May 2024 00:00:00 +0000</pubDate>
4400. <dc:creator>Jakub Beránek, Jack Huey and Paul Lenz</dc:creator>
4401. </item>
4402. <item>
4403. <title>Support.Mozilla.Org: What’s up with SUMO — Q1 2024</title>
4404. <guid isPermaLink="false">https://blog.mozilla.org/sumo/?p=4112</guid>
4405. <link>https://blog.mozilla.org/sumo/2024/04/30/whats-up-with-sumo-q1-2024/</link>
4406. <description>&lt;p&gt;Hi everybody,&lt;/p&gt;
4407. <p>It’s always exciting to start a new year as it provides renewed spirit. Even more exciting because the CX team welcomed a few additional members this quarter, including Konstantina, who will be with us crafting better community experiences in SUMO. This is huge, since the SUMO community team has been under resourced for the past few years. I’m personally super excited about this. There are a few things that we’re working on internally, and I can’t wait to share them with you all. But first thing first, let’s read the recap of what happened and what we did in Q1 2024!</p>
4408. <h3>Welcome note and shout-outs</h3>
4409. <ul>
4410. <li>Thanks for joining the Social and Mobile Store Support program!</li>
4411. <li>Welcome back to Erik L and Noah. It’s good to see you more often these days.</li>
4412. <li>Shout-outs to Noah and Sören for their observations during the 125 release so we can take prompt actions on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1892521">bug1892521</a> and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1892612">bug1892612</a>. Also, special thanks to Paul W for his direct involvement in the war room for the NordVPN incident.</li>
4413. <li>Thanks to Philipp for his consistency in creating desktop thread in the contributor forum for every release. Your help is greatly appreciated!</li>
4414. <li>Also huge thanks to everybody who is involved in the Night Mode removal issue on Firefox for iOS 124. In the end, we decided to end the experiment early, since many people raised concern about accessibility issues. This really shows the power of community and users’ feedback.</li>
4415. </ul>
4416. <p>If you know someone who you’d like to feature here, please contact <a href="https://support.mozilla.org/user/kelimutu">Kiki</a>, and we’ll make sure to add them in our next edition.</p>
4417. <h3>Community news</h3>
4418. <ul>
4419. <li>As I mentioned, we started the year by onboarding <a href="https://blog.mozilla.org/sumo/2024/01/04/introducing-mandy-and-donna/">Mandy, Donna</a>, and Britney. If that’s not enough, we also welcomed <a href="https://blog.mozilla.org/sumo/2024/03/25/introducing-konstantina/">Konstantina</a>, who moved from Marketing to the CX team in March. If you haven’t got to know them, please don’t hesitate to say hi when you can.</li>
4420. <li>AI spam has been a big issue in our forum lately, so we decided to spin up a new contributor policy around the use of AI-generated tools. Please check <a href="https://support.mozilla.org/forums/contributors/716669?last=86840">this thread</a> if you haven’t!</li>
4421. <li>We participated in FOSDEM 2024 in Brussels and it was a blast! It’s great to be able to meet face to face with many community members after a long hiatus since the pandemic. Kiki and the platform team also presented <a href="https://fosdem.org/2024/schedule/event/fosdem-2024-2419-17-year-journey-of-the-mozilla-support-platform-its-community/">a talk</a> in the Mozilla devroom. We also shared free cookies (not a tracking one) and talked with many Firefox fans from around the globe. All in all, it was a productive weekend, indeed.</li>
4422. <li>We added a new capability in our KB to set restricted visibility on specific articles. This is a staff-only feature, but we believe it’s important for everybody to be aware of this. If you haven’t, please check out <a href="https://support.mozilla.org/forums/contributors/716808?last=87367">this thread</a> to get to know more!</li>
4423. <li>Please be aware of Hubs sunset plan from <a href="https://support.mozilla.org/forums/contributors/716909?last=87356">this thread</a>.</li>
4424. <li>We opened an <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885070">AAQ for NL</a> in our support forum. Thanks to Tim Maks and the rest of the NL community, who’ve been very supportive of this work.</li>
4425. <li>We’ve done our usual <a href="https://support.mozilla.org/forums/contributors/716855?last=87308">annual contributor survey in March</a>. Thank you to every one of you who filled out the survey and shared great feedback!</li>
4426. <li>We change something around how we communicate product release updates through bi-weekly scrum meetings. Please be aware of it by checking out <a href="https://support.mozilla.org/forums/contributors/716856?last=87188">this contributor thread</a>.</li>
4427. <li>Are you contributing to our Knowledge Base? You may want to read the recent blog posts from the content team to get to know more about <a href="https://blog.mozilla.org/sumo/2024/04/09/keeping-you-in-the-loop-whats-new-in-our-knowledge-base/">what they’re up to</a>. In short, they’re doing a lot around <a href="https://blog.mozilla.org/sumo/2024/04/18/freshening-up-the-knowledge-base-for-spring-2024/">freshening up our knowledge base articles</a>.</li>
4428. </ul>
4429. <h3>Stay updated</h3>
4430. <ul>
4431. <li>Join our discussions in the <a href="https://support.mozilla.org/en-US/forums/contributors/">contributor forum</a> to see what’s happening in the latest release on Desktop and mobile.</li>
4432. <li>Watch the monthly community call if you haven’t. Learn more about what’s new in <a href="https://wiki.mozilla.org/Support/Weekly_Meetings/Agenda_2024-01-17">January</a>, and <a href="https://wiki.mozilla.org/Support/Weekly_Meetings/Agenda_2024-03-13">March</a> (we canceled February)! <b><i>Reminder</i></b><b>:</b> <i>Don’t hesitate to join the call in person if you can. We try our best to provide a safe space for everyone to contribute. You’re more than welcome to lurk in the call if you don’t feel comfortable turning on your video or speaking up. If you feel shy to ask questions during the meeting, feel free to add your questions on the contributor forum in advance, or put them in our Matrix channel, so we can answer them during the meeting.</i></li>
4433. <li>If you’re an NDA’ed contributor, you can watch the recording of our Firefox Pod Meeting from <a href="https://mzl.la/SUMO-release-scrum">AirMozilla</a> to catch up with the latest train release. You can also subscribe to the AirMozilla folder by clickling on the Subscribe button at the top right corner of the page to get notifications each time we add a new recording.</li>
4434. <li>Consider subscribing to <a href="https://mzl.la/3NZO8tI">Firefox Daily Digest</a> to get daily updates (Mon-Fri) about Firefox from across the internet.</li>
4435. <li>Check out <a href="https://github.com/mozilla/sumo-project/projects/1">SUMO Engineering Board</a> to see what the platform team is cooking in the engine room. Also, check out <a href="https://github.com/mozilla/kitsune/releases">this page</a> to see our latest release notes</li>
4436. </ul>
4437. <h3>Community stats</h3>
4438. <h4>KB</h4>
4439. <p><b>KB pageviews</b></p>
4440. <table style="height: 114px;" width="638">
4441. <tbody>
4442. <tr>
4443. <td><b>Month</b></td>
4444. <td><b>Page views</b></td>
4445. <td><b>Vs previous month</b></td>
4446. </tr>
4447. <tr>
4448. <td>Jan 2024</td>
4449. <td>6,743,722</td>
4450. <td>3.20%</td>
4451. </tr>
4452. <tr>
4453. <td>Feb 2024</td>
4454. <td>7,052,665</td>
4455. <td>4.58%</td>
4456. </tr>
4457. <tr>
4458. <td>Mar 2024</td>
4459. <td>6,532,175</td>
4460. <td>-7.38%</td>
4461. </tr>
4462. </tbody>
4463. </table>
4464. <pre>KB pageviews number is a total of English (en-US) KB pageviews</pre>
4465. <p><b>Top 5 KB contributors in the last 90 days: </b></p>
4466. <ul>
4467. <li><a href="https://support.mozilla.org/en-US/user/AliceWyman">AliceWyman</a></li>
4468. <li><a href="https://support.mozilla.org/en-US/user/Mozinet">Pierre Mozinet</a></li>
4469. <li><a href="https://support.mozilla.org/user/markh2/">Mark Heijl</a></li>
4470. <li><a href="https://support.mozilla.org/user/michro/">Michele Rodaro</a></li>
4471. <li><a href="https://support.mozilla.org/user/erling.rosag/">Erling R</a></li>
4472. </ul>
4473. <h4>KB Localization</h4>
4474. <p><b>Top 10 locales based on total page views</b></p>
4475. <table style="height: 547px;" width="1098">
4476. <tbody>
4477. <tr>
4478. <td><b>Locale/pageviews</b></td>
4479. <td>
4480. <p style="text-align: left;"><b>Jan 2024</b><b></b></p>
4481. </td>
4482. <td style="text-align: left;"><b>Feb 2024<br />
4483. </b></td>
4484. <td>
4485. <p style="text-align: left;"><b>Mar 2024 </b></p>
4486. </td>
4487. <td><b>Localization progress (per Apr, 23)</b></td>
4488. </tr>
4489. <tr>
4490. <td><a href="https://support.mozilla.org/de/localization">de</a></td>
4491. <td>2,425,154</td>
4492. <td>2,601,865</td>
4493. <td>2,315,952</td>
4494. <td>92%</td>
4495. </tr>
4496. <tr>
4497. <td><a href="https://support.mozilla.org/fr/localization">fr</a></td>
4498. <td>1,559,222</td>
4499. <td>1,704,271</td>
4500. <td>1,529,981</td>
4501. <td>81%</td>
4502. </tr>
4503. <tr>
4504. <td><a href="https://support.mozilla.org/zh-CN/localization">zh-CN</a></td>
4505. <td>1,351,729</td>
4506. <td>1,224,284</td>
4507. <td>1,306,699</td>
4508. <td>100%</td>
4509. </tr>
4510. <tr>
4511. <td><a href="https://support.mozilla.org/es/localization">es</a></td>
4512. <td>1,171,981</td>
4513. <td>1,353,200</td>
4514. <td>1,212,666</td>
4515. <td>25%</td>
4516. </tr>
4517. <tr>
4518. <td><a href="https://support.mozilla.org/ja/localization">ja</a></td>
4519. <td>1,019,806</td>
4520. <td>1,068,034</td>
4521. <td>1,051,625</td>
4522. <td>34%</td>
4523. </tr>
4524. <tr>
4525. <td><a href="https://support.mozilla.org/ru/localization">ru</a></td>
4526. <td>801,370</td>
4527. <td>886,163</td>
4528. <td>812,882</td>
4529. <td>100%</td>
4530. </tr>
4531. <tr>
4532. <td><a href="https://support.mozilla.org/pt-BR/localization">pt-BR</a></td>
4533. <td>661,612</td>
4534. <td>748,185</td>
4535. <td>714,554</td>
4536. <td>42%</td>
4537. </tr>
4538. <tr>
4539. <td><a href="https://support.mozilla.org/zh-TW/localization">zh-TW</a></td>
4540. <td>598,085</td>
4541. <td>623,218</td>
4542. <td>366,320</td>
4543. <td>3%</td>
4544. </tr>
4545. <tr>
4546. <td><a href="https://support.mozilla.org/it/localization">It</a></td>
4547. <td>533,071</td>
4548. <td>575,245</td>
4549. <td>529,887</td>
4550. <td>96%</td>
4551. </tr>
4552. <tr>
4553. <td><a href="https://support.mozilla.org/pl/localization">pl</a></td>
4554. <td>489,532</td>
4555. <td>532,506</td>
4556. <td>454,347</td>
4557. <td>84%</td>
4558. </tr>
4559. </tbody>
4560. </table>
4561. <pre>Locale pageviews is an overall pageview from the given locale (KB and other pages)
4562.  
4563. Localization progress is the percentage of localized articles from all KB articles per locale</pre>
4564. <p><b>Top 5 localization contributors in the last 90 days: </b></p>
4565. <ul>
4566. <li><a href="https://support.mozilla.org/user/michro/">Michele Rodaro</a></li>
4567. <li><a href="https://support.mozilla.org/user/wxie2016/">Wxie</a></li>
4568. <li><a href="https://support.mozilla.org/user/Goudron/">Valery Ledovskoy</a></li>
4569. <li><a href="https://support.mozilla.org/user/d.spentzos/">Jim Spentzos</a></li>
4570. <li><a href="https://support.mozilla.org/user/markh2/">Mark Heijl</a></li>
4571. </ul>
4572. <h4>Forum Support</h4>
4573. <p><b>Forum stats</b></p>
4574. <table style="height: 133px;" width="902">
4575. <tbody>
4576. <tr>
4577. <td><b>Month</b></td>
4578. <td><b>Total questions</b></td>
4579. <td><b>Answer rate within 72 hrs</b></td>
4580. <td><b>Solved rate within 72 hrs</b></td>
4581. <td><b>Forum helpfulness</b></td>
4582. </tr>
4583. <tr>
4584. <td>Jan 2024</td>
4585. <td>2999</td>
4586. <td>72.6%</td>
4587. <td>10.8%</td>
4588. <td>61.3%</td>
4589. </tr>
4590. <tr>
4591. <td>Feb 2024</td>
4592. <td>2766</td>
4593. <td>72.4%</td>
4594. <td>9.5%</td>
4595. <td>65.6%</td>
4596. </tr>
4597. <tr>
4598. <td>Mar 2024</td>
4599. <td>2516</td>
4600. <td>71.5%</td>
4601. <td>10.4%</td>
4602. <td>71.6%</td>
4603. </tr>
4604. </tbody>
4605. </table>
4606. <p><b>Top 5 forum contributors in the last 90 days: </b></p>
4607. <ul>
4608. <li><a href="https://support.mozilla.org/en-US/user/287">Cor-el</a></li>
4609. <li><a href="https://support.mozilla.org/en-US/user/davidsk">Davidsk</a></li>
4610. <li><a href="https://support.mozilla.org/en-US/user/jonzn4SUSE/">Jonzn4SUSE</a></li>
4611. <li><a href="https://support.mozilla.org/user/MattAuSupport/">Matt</a></li>
4612. <li><a href="https://support.mozilla.org/user/jscher2000/">Jscher2000</a></li>
4613. </ul>
4614. <h4>Social Support</h4>
4615. <table style="height: 99px;" width="867">
4616. <tbody>
4617. <tr>
4618. <td><b>Month</b></td>
4619. <td><b>Total replies</b></td>
4620. <td><b>Total interactions</b></td>
4621. <td><b>Respond conversion rate</b></td>
4622. </tr>
4623. <tr>
4624. <td>Jan 2024</td>
4625. <td>33</td>
4626. <td>46</td>
4627. <td>71.74%</td>
4628. </tr>
4629. <tr>
4630. <td>Feb 2024</td>
4631. <td>25</td>
4632. <td>65</td>
4633. <td>38.46%</td>
4634. </tr>
4635. <tr>
4636. <td>Mar 2024</td>
4637. <td>14</td>
4638. <td>87</td>
4639. <td>16.09%</td>
4640. </tr>
4641. </tbody>
4642. </table>
4643. <p><b>Top 5 Social Support contributors in the past 3 months: </b></p>
4644. <ul>
4645. <li><a href="https://support.mozilla.org/user/Mad_Maks/">Tim Maks </a></li>
4646. <li><a href="https://support.mozilla.org/user/Fjoerfoks">Wim Benes</a></li>
4647. <li><a href="https://support.mozilla.org/user/petergallwas/">Peter Gallwas</a></li>
4648. <li><a href="https://support.mozilla.org/user/eyad02122/">Eyad Ahmed</a></li>
4649. <li><a href="https://support.mozilla.org/user/sebastianbeck2209/">Sebastian Becker</a></li>
4650. </ul>
4651. <p> </p>
4652. <h4>Play Store Support</h4>
4653. <table style="height: 5px;" width="886">
4654. <tbody>
4655. <tr>
4656. <td><b>Month</b></td>
4657. <td><b>Total replies</b></td>
4658. <td><b>Total interactions</b></td>
4659. <td><b>Respond conversion rate</b></td>
4660. </tr>
4661. <tr>
4662. <td>Jan 2024</td>
4663. <td>76</td>
4664. <td>276</td>
4665. <td>27.54%</td>
4666. </tr>
4667. <tr>
4668. <td>Feb 2024</td>
4669. <td>49</td>
4670. <td>86</td>
4671. <td>56.98%</td>
4672. </tr>
4673. <tr>
4674. <td>Mar 2024</td>
4675. <td>47</td>
4676. <td>80</td>
4677. <td>58.75%</td>
4678. </tr>
4679. </tbody>
4680. </table>
4681. <p><b>Top 5 Play Store contributors in the past 3 months:</b></p>
4682. <ul>
4683. <li><a href="https://support.mozilla.org/user/eyad02122/">Eyad Ahmed</a></li>
4684. <li><a href="https://support.mozilla.org/user/Fjoerfoks">Wim Benes</a></li>
4685. <li><a href="https://support.mozilla.org/user/gelopl/">Damian Szabat</a></li>
4686. <li><a href="https://support.mozilla.org/user/hellosct1/">Christophe Villeneuve</a></li>
4687. <li><a href="https://support.mozilla.org/user/Mad_Maks/">Tim Maks </a></li>
4688. </ul>
4689. <h3>Stay connected</h3>
4690. <ul>
4691. <li><a href="https://chat.mozilla.org/#/room/#SUMO:mozilla.org">#SUMO Matrix group</a></li>
4692. <li><a href="https://support.mozilla.org/en-US/forums">Contributor forums</a></li>
4693. <li>Twitter <a href="https://twitter.com/SUMO_Mozilla">@SUMO_mozilla</a> and <a href="https://twitter.com/FirefoxSupport">@FirefoxSupport</a></li>
4694. <li><a href="https://blog.mozilla.org/sumo/">SUMO Blog</a></li>
4695. &lt;/ul&gt;</description>
4696. <pubDate>Tue, 30 Apr 2024 16:15:01 +0000</pubDate>
4697. <dc:creator>Rizki Kelimutu</dc:creator>
4698. </item>
4699. <item>
4700. <title>Mozilla Privacy Blog: The UK’s Digital Markets, Competition, and Consumers Bill will spark the UK’s digital economy, not stifle it</title>
4701. <guid isPermaLink="false">https://blog.mozilla.org/netpolicy/?p=2374</guid>
4702. <link>https://blog.mozilla.org/netpolicy/2024/04/26/dmcc-uk-support/</link>
4703. <description>&lt;p&gt;In today’s digital age, an open and competitive ecosystem with a diverse range of players is essential for building a resilient economy. New products and ideas must have the opportunity to grow to give people meaningful choices. Yet, this reality often falls short due to the dominance of a handful of large companies that create walled gardens by self-preferencing their services over independent competitors  –  limiting choice and hampering innovation.&lt;/p&gt;
4704. <p>The UK’s Digital Markets, Competition, and Consumers Bill (DMCCB) offers a unique opportunity to break down these barriers, paving the way for a more competitive and consumer-centric digital market. On the competition side, the DMCCB offers <a href="https://www.timetoplayfair.com/dmcc/">flexibility</a> in allowing for targeted <a href="https://www.timetoplayfair.com/dmcc/">codes of conduct </a>to regulate the behaviour of dominant players. This agile and future-proof approach makes it unique in the ex-ante interventions being considered around the world to rein in abuse in digital markets. An <a href="https://blog.mozilla.org/netpolicy/files/2021/07/Mozillas-Response-to-the-CMA-Consultation-on-Googles-Chrome-Privacy-Sandbox-Commitments-Case-50972.pdf">example</a> of what such a code of conduct might look like in practice is the voluntary commitments given by Google to the CMA in the Privacy Sandbox case.</p>
4705. <p>Mozilla, in line with our <a href="https://blog.mozilla.org/en/mozilla/calling-for-antitrust-reform/">long</a> <a href="https://blog.mozilla.org/netpolicy/2022/07/05/mozilla-statement-as-eu-parliament-adopts-new-pro-competition-rulebook-for-big-tech/">history</a> of supporting pro-competition regulatory interventions, supports the DMCCB and its underlying goal of fostering competition by empowering consumers. However, to truly deliver on this promise, the law must be robust, effective, and free from loopholes that could undermine its intent.</p>
4706. <p>Last month, the House of Lords made some much needed <a href="https://www.parliament.uk/business/news/2024/march/digital-markets-competition-and-consumers-bill-set-for-further-lords-scrutiny/">improvements</a> to the DMCCB – which are now slated to be debated in the House of Commons in late April/early May 2024. A high-level overview of the key positive changes and why they should remain a part of the law are:</p>
4707. <ul>
4708. <li><b>Time Limits: </b>To ensure the CMA can act swiftly and decisively, its work should be free from undue political influence. This reduces opportunities for undue lobbying and provides clarity for both consumers and companies. While it would be ideal for the CMA to be able to enforce its code of conduct, Mozilla supports the House of Lords’ amendment to introduce a 40-day time limit for the Secretary of State’s approval of CMA guidance. This is a crucial step in avoiding delays and ensuring effective enforcement. The government’s acceptance of this approach and the alternative proposal of 30 working days for debate in the House of Commons is a positive sign, which we hope is reflected in the final law.</li>
4709. <li><b>Proportionality: </b>The Bill’s approach to proportionality is vital. Introducing prohibitive proportionality requirements on remedies could weaken the CMA’s ability to make meaningful interventions, undermining the Bill’s effectiveness. Mozilla endorses the current draft of the Bill from the House of Lords, which strikes a balance by allowing for effective remedies without excessive constraints.</li>
4710. <li><b>Countervailing Benefits: </b>Similarly, the countervailing benefits exemption to CMA’s remedies, while powerful, should not be used as a loophole to justify anti-competitive practices. Mozilla urges that this exemption be reserved for cases of genuine consumer benefit by restoring the government’s original requirement that such exemptions are “indispensable”, ensuring that it does not become a ‘get out of jail free’ card for dominant players.</li>
4711. </ul>
4712. <p><b></b>Mozilla remains committed to supporting the DMCCB’s swift passage through Parliament and ensuring that it delivers on its promise to empower consumers and promote innovation. We launched a <a href="https://foundation.mozilla.org/en/campaigns/dmccb-bill/">petition</a> earlier today to help push the law over the finish line. By addressing the key concerns we’ve highlighted above and maintaining a robust framework, the UK can set a global standard for digital markets and create an environment where consumers are truly in charge.</p>
4713. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2024/04/26/dmcc-uk-support/&quot;&gt;The UK’s Digital Markets, Competition, and Consumers Bill will spark the UK’s digital economy, not stifle it&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>
4714. <pubDate>Sat, 27 Apr 2024 05:17:47 +0000</pubDate>
4715. <dc:creator>Udbhav Tiwari</dc:creator>
4716. </item>
4717. <item>
4718. <title>Don Marti: realistically get rid of third-party cookies</title>
4719. <guid isPermaLink="true">https://blog.zgp.org/realistically-get-rid-of-third-party-cookies/</guid>
4720. <link>https://blog.zgp.org/realistically-get-rid-of-third-party-cookies/</link>
4721. <description>&lt;p&gt;How would a browser realistically get rid of third-party cookies, if the plan was to just replace third-party cookies, and the project requirements did not include a bunch of anticompetitive tricks too?&lt;/p&gt; &lt;ol type=&quot;1&quot;&gt; &lt;li&gt;&lt;p&gt;Start offering a very scary dialog to a fraction of new users. Something like &lt;q&gt;Do you want to test a new experimental feature? It might—maybe—have some privacy benefits but many sites will break.&lt;/q&gt; Don’t expect a lot of people to agree at first.&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;Turn off third-party cookies for the users who did say yes in step 1, and watch the telemetry. There will be positive and negative effects, but they won’t be overwhelmingly bad because most sites have to work with other browsers.&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;When the breakage detected in step 2 gets to be insignificant as a cause of new browser users quitting or reinstalling, start making the dialog less scary and show it to more people.&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;Keep repeating until most new installs are third-party cookie-free, then start offering the dialog on browser upgrades.&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;Continue, for more and more users, until you get to 95-99%. Leave the third-party cookies on for 1-5% of users for a couple of releases just to spot any lingering problems, then make third-party cookies default off, with no dialog (users would have to find the preference to re-enable them, or their sysadmin would have to push out a centralized change if some legacy corporate site still needs them).&lt;/p&gt;&lt;/li&gt; &lt;/ol&gt; &lt;p&gt;But what about the personalized ads? &lt;a href=&quot;https://blog.zgp.org/30-40-30/&quot;&gt;Some people actually want those!&lt;/a&gt; Not a problem. The good news is that &lt;strong&gt;ad personalization can be done in an extension.&lt;/strong&gt; Ask extension developers who have extensions that support ad personalization to sign up for a registry of ad personalization extensions, then keep track of how many users are installing each one. Adtech firms don’t (usually?) have personalization extensions today, but every company can develop one on its own schedule, with less uncertainty and fewer dependencies and delays than the current &lt;q&gt;end of cookies&lt;/q&gt; mess. The extension development tools are really good now.&lt;/p&gt; &lt;p&gt;As soon as an ad personalization extension can pass an independent security audit (done by a company agreed on by the extension developer and the browser vendor) and get, say, 10,000 users, then the browser can put it on a choice screen that gets shown for new installs and, if added since last upgrade, upgrades. (The browser could give the dogmatic anti-personalization users a preference to opt out of these choice screens if they really wanted to dig in and find it.) This makes the work of competition regulators much easier—they just have to check that the browser vendor’s own ad personalization extension gets fair treatment with competing ones.&lt;/p&gt; &lt;p&gt;And we’re done. The privacy people and the personalized ad people get what they want with much less drama and delay, the whole web ad business isn’t stuck queued up waiting for one development team, and all that’s missing is the anticompetitive stuff that has been making &lt;q&gt;end of cookies&lt;/q&gt; work such a pain since 2019.&lt;/p&gt; &lt;h3&gt;Related&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/30-40-30/&quot;&gt;the 30-40-30 rule&lt;/a&gt; An updated list of citations to user research on how many people want personalized ads&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/please-delete/&quot;&gt;Can database marketing sell itself to the people in the database?&lt;/a&gt; Some issues that an ad personalization extension might have to address in order to get installs&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/user-tracking-as-chesterton-s-fence/&quot;&gt;User tracking as Chesterton’s Fence&lt;/a&gt; What tracking-based advertising still offers (that alternatives don’t)&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/tp-strategy/&quot;&gt;Catching up to Safari?&lt;/a&gt; Some features that Apple has done right, with opportunities for other browsers to think different(ly)&lt;/p&gt; &lt;h3&gt;Bonus links&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;https://bokonads.com/p/an-open-letter-to-the-advertising&quot;&gt;An open letter to the advertising punditry&lt;/a&gt; &lt;q&gt; I personally got involved in the Inventory Quality reviews to make sure that the data scientists weren’t pressured by the business and could find the patterns–like ww3 [dot] forbes [dot] com–and go after them.&lt;/q&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.schneier.com/blog/archives/2024/04/the-rise-of-large.html&quot;&gt;The Rise of Large-Language-Model Optimization&lt;/a&gt; &lt;q&gt;The advent of AI threatens to destroy the complex online ecosystem that allows writers, artists, and other creators to reach human audiences.&lt;/q&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.wheresyoured.at/the-men-who-killed-google/&quot;&gt;The Man Who Killed Google Search&lt;/a&gt; &lt;q&gt;[M]any found that the update mostly rolled back changes, and traffic was increasing to sites that had previously been suppressed by Google Search’s “Penguin” update from 2012 that specifically targeted spammy search results, as well as those hit by an update from an August 1, 2018…&lt;/q&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.theguardian.com/technology/2024/apr/22/lawsuit-in-london-to-allege-grindr-shared-users-hiv-status-with-ad-firms&quot;&gt;Lawsuit in London to allege Grindr shared users’ HIV status with ad firms&lt;/a&gt; (This is why you can safely mute anybody who uses the expression &lt;q&gt;k-anonymity,&lt;/q&gt; the info about yourself that you most want to keep private is true for more than &lt;em&gt;k&lt;/em&gt; other people.)&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.theguardian.com/society/2024/apr/21/uk-children-bombarded-by-gambling-ads-and-images-online-charity-warns&quot;&gt;UK children bombarded by gambling ads and images online, charity warns&lt;/a&gt; (attention parents: copy the device rules that Big Tech big shots maintain for their own children, not what they want for yours)&lt;/p&gt;</description>
4722. <pubDate>Sat, 27 Apr 2024 00:00:00 +0000</pubDate>
4723. </item>
4724. <item>
4725. <title>Mozilla Privacy Blog: Work Gets Underway on a New Federal Privacy Proposal</title>
4726. <guid isPermaLink="false">https://blog.mozilla.org/netpolicy/?p=2371</guid>
4727. <link>https://blog.mozilla.org/netpolicy/2024/04/26/work-gets-underway-on-a-new-federal-privacy-proposal/</link>
4728. <description>&lt;p&gt;At Mozilla, safeguarding privacy has been core to our mission for decades — we believe that individuals’ security and privacy on the Internet are fundamental and must not be treated as optional. We have &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2022/08/29/save-the-date-the-long-road-to-federal-privacy-protections-are-we-there-yet/&quot;&gt;long&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2022/08/24/its-time-to-pass-u-s-federal-privacy-legislation/&quot;&gt;advocated&lt;/a&gt; for a federal privacy law to ensure consumers have control over their data and that companies are accountable for their privacy practices.&lt;/p&gt;
4729. <p>Earlier this month, House Committee on Energy and Commerce Chair Cathy McMorris Rodgers (R-WA) and Senate Committee on Commerce, Science and Transportation Chair Maria Cantwell (D-WA) unveiled a discussion draft of the <a href="https://www.commerce.senate.gov/services/files/3F5EEA76-5B18-4B40-ABD9-F2F681AA965F">American Privacy Rights Act of 2024 (APRA)</a>. The Act is a welcome bipartisan effort to create a unified privacy standard across the United States, with the promise of finally protecting the privacy of all Americans.</p>
4730. <p>At Mozilla, we are committed to the principle of data minimization – a concept that’s fundamental in effective privacy legislation – and we are pleased to see it at the core of APRA. Data minimization means we conscientiously collect only the necessary data, ensure its protection, and provide clear and concise explanations about what data we collect and why. We are also happy to see additional strong language from the American Data Privacy and Protect Act (ADPPA) reflected in this new draft, including non-discrimination provisions and a universal opt-out mechanism (though we support clarification that ensures allowance of multiple mechanisms).</p>
4731. <p>However, the APRA discussion draft has open questions that must be refined. These include how APRA handles protections for children, options for strengthening data brokers provisions even further (such as a centralized mechanism for opt-out rights), and key definitions that require clarity around advertising. We look forward to engaging with policymakers as the process advances.</p>
4732. <p>Achieving meaningful <a href="https://foundation.mozilla.org/en/privacy-for-all/">reform in the U.S. is long overdue</a>. In an era where digital privacy concerns are on the rise, it’s essential to establish clear and enforceable privacy rights for all Americans. Mozilla stands ready to contribute to the dialogue on APRA and collaborate toward achieving comprehensive privacy reform. Together, we can prioritize the interests of individuals and cultivate trust in the digital ecosystem.</p>
4733. <p> </p>
4734. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2024/04/26/work-gets-underway-on-a-new-federal-privacy-proposal/&quot;&gt;Work Gets Underway on a New Federal Privacy Proposal&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>
4735. <pubDate>Fri, 26 Apr 2024 19:48:55 +0000</pubDate>
4736. <dc:creator>Jenn Taylor Hodges</dc:creator>
4737. </item>
4738. <item>
4739. <title>Mozilla Privacy Blog: Net Neutrality is Back!</title>
4740. <guid isPermaLink="false">https://blog.mozilla.org/netpolicy/?p=2370</guid>
4741. <link>https://blog.mozilla.org/netpolicy/2024/04/26/net-neutrality-is-back/</link>
4742. <description>&lt;p&gt;Yesterday, the Federal Communications Commission (FCC) voted 3-2 to reinstate net neutrality rules and protect consumers online. We applaud this decision to keep the internet open and accessible to all, and reverse the 2018 roll-back of net neutrality protections. Alongside our many partners and allies, Mozilla has been a &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/mozilla-files-suit-fcc-protect-net-neutrality/&quot;&gt;long time&lt;/a&gt; proponent of net neutrality &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2015/10/24/net-neutrality-amendments-and-final-vote-in-the-eu/&quot;&gt;across&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/netpolicy/files/2015/12/Comentarios-generales-a-OSIPTEL.pdf&quot;&gt;the&lt;/a&gt; &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2020/09/14/mozilla-applauds-trai-for-maintaining-the-status-quo-on-ott-regulation-upholding-a-key-aspect-of-net-neutrality-in-india/&quot;&gt;world&lt;/a&gt; and in U.S. &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/in-california-an-important-victory-for-net-neutrality/&quot;&gt;states&lt;/a&gt;, and &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/internet-policy/stand-net-neutrality-help-paperstorm-fcc/&quot;&gt;mobilized&lt;/a&gt; hundreds of thousands of people over the years.&lt;/p&gt;
4743. <p>The new FCC order reclassifies broadband internet as a “telecommunications service” and prevents ISPs from blocking, throttling, or paid prioritization of traffic. This action restores meaningful and enforceable FCC oversight and protection on the internet, and unlocks innovation, <a href="https://ilsr.org/report-most-americans-have-no-real-choice-in-internet-providers/">competition</a>, and free expression online.</p>
4744. <p style="text-align: left;"><i>You can read Mozilla’s submission to the FCC on the proposed Safeguarding and Securing the Open Internet rules </i><a href="https://www.fcc.gov/ecfs/document/121497799035/1"><i>in December 2023 here</i></a><i> and additional reply comments </i><a href="https://www.fcc.gov/ecfs/document/1011790221057/1"><i>in January 2024 here</i></a><i>.</i></p>
4745. <p>Net neutrality and openness are essential parts of how we experience the internet, and <a href="https://www.wired.com/story/covid-19-pandemic-shows-virtues-net-neutrality/">as illustrated</a> during the COVID pandemic, can offer important protections – so it shouldn’t come as a surprise that such a <a href="https://foundation.mozilla.org/en/blog/with-net-neutrality-back-on-national-agenda-mozilla-survey-finds-americans-do-not-trust-isps-to-look-out-for-their-best-interests/">majority of Americans</a> support it. Yesterday’s decision reaffirms the internet is and should remain a public resource, where companies cannot abuse their market power to the detriment of consumers, and where actors large and small operate on a level playing field.</p>
4746. <p>Earlier this month, Mozilla participated in a <a href="https://docs.fcc.gov/public/attachments/DOC-401773A1.pdf">roundtable discussion</a> with experts and allies hosted by Chairwoman Rosenworcel at the Santa Clara County Fire Department. The event location highlighted the importance of net neutrality, as the site where <a href="https://www.nytimes.com/2018/08/22/us/verizon-throttling-california-fire-net-neutrality.html">Verizon throttled</a> firefighters’ internet speeds in the midst of fighting a raging wildfire. You can watch the full press conference below, and read coverage of the event <a href="https://www.nbcbayarea.com/news/local/fcc-chair-roundtable-net-neutrality-campbell/3504159/">here</a>.</p>
4747. <p>We thank the FCC for protecting these vital net neutrality safeguards, and we look forward to seeing the details of the final order when released.</p>
4748. &lt;p&gt;The post &lt;a href=&quot;https://blog.mozilla.org/netpolicy/2024/04/26/net-neutrality-is-back/&quot;&gt;Net Neutrality is Back!&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>
4749. <pubDate>Fri, 26 Apr 2024 19:28:00 +0000</pubDate>
4750. <dc:creator>Jenn Taylor Hodges</dc:creator>
4751. </item>
4752. <item>
4753. <title>The Servo Blog: This month in Servo: Acid2 redux, Servo book, Qt demo, and more!</title>
4754. <guid isPermaLink="true">https://servo.org/blog/2024/04/26/acid2-servo-book-qt/</guid>
4755. <link>https://servo.org/blog/2024/04/26/acid2-servo-book-qt/</link>
4756. <description>&lt;figure class=&quot;_figr&quot;&gt;&lt;a href=&quot;https://servo.org/img/servo-acid2-202404.png&quot;&gt;&lt;img alt=&quot;Servo nightly, now rendering Acid2 perfectly&quot; src=&quot;https://servo.org/img/servo-acid2-202404.png&quot; style=&quot;width: auto;&quot; /&gt;&lt;/a&gt;
4757. <figcaption>Servo now renders Acid2 perfectly, but like all browsers, only at 1x dpi.</figcaption></figure>
4758. <p><span class="_floatmin"></span><a href="https://servo.org/blog/2023/11/30/embedding-floats-color-mix/">Back in November</a>, Servo’s new layout engine passed <a href="http://acid1.acidtests.org/">Acid1</a>, and this month, thanks to a bug-squashing sprint by <a href="http://github.com/mrobinson">@mrobinson</a> and <a href="https://github.com/Loirooriol">@Loirooriol</a>, we now pass <a href="https://acid2.acidtests.org/">Acid2</a>!</p>
4759. <aside class="_note">
4760. <p>Note that Acid2 is only designed to work at 1x dpi, so if you have a HiDPI monitor, be sure to run servoshell with <code>--device-pixel-ratio 1</code> to avoid a red pattern over the eyes.</p>
4761. </aside>
4762. <p>We would also like to thank you all for your generous support!
4763. Since we moved to <a href="https://opencollective.com/servo">Open Collective</a> and <a href="https://github.com/sponsors/servo">GitHub Sponsors</a> in March, we have received <strong>1578 USD</strong> (after fees), including <strong>1348 USD/month</strong> (before fees) in recurring donations.
4764. This smashed our first two goals, and is a respectable part of the way towards our next goal of 10000 USD/month.
4765. For more details, see our <a href="https://servo.org/sponsorship/">Sponsorship</a> page and <a href="https://servo.org/blog/2024/03/12/sponsoring-servo/">announcement post</a>.</p>
4766. <figure class="_fig" style="width: 100%; margin: 1em 0;"><div class="_flex">
4767.    <div style="text-align: right;">
4768.        <div><strong>1348</strong> USD/month</div>
4769.        <div></div>
4770.        <div></div>
4771.        <div style="padding-right: 1em;"><strong>10000</strong></div>
4772.    </div>
4773.    <progress max="10000" value="1348"></progress>
4774. </div></figure>
4775. <p>We are still receiving donations from <strong>19 people</strong> on LFX, and we’re working on transferring the balance to our new fund, but we will stop accepting donations there soon — <strong>please move your recurring donations to <a href="https://github.com/sponsors/servo">GitHub</a> or <a href="https://opencollective.com/servo">Open Collective</a></strong>.
4776. As always, use of these funds will be decided transparently in the Technical Steering Committee, starting with the TSC meeting <a href="https://github.com/servo/project/issues/85">on 29 April</a>.</p>
4777. <figure class="_figl"><a href="https://servo.org/img/blog/servo-book.png"><img alt="The Servo book, a book much like the Rust book" src="https://servo.org/img/blog/servo-book.png" /></a>
4778. </figure>
4779. <p><span class="_floatmin"></span>Servo’s docs are moving to <a href="https://book.servo.org/"><strong>the Servo book</strong></a>, and a very early version of this is now online (<a href="https://github.com/delan">@delan</a>, <a href="https://github.com/servo/book">servo/book</a>)!
4780. The goal is to unify our many sources of documentation, including the <a href="https://github.com/servo/servo/blob/81c4f2ae7a0b605befae652c0feeea03caba6292/docs/HACKING_QUICKSTART.md">hacking quickstart guide</a>, <a href="https://github.com/servo/servo/wiki/Building/e04d7a194b59fad65fbd3eefb7aab12ae3a60eba">building Servo page</a>, <a href="https://github.com/servo/servo/wiki/Design/0941531122361aac8c88d582aa640ec689cdcdd1">Servo design page</a>, and <a href="https://book.servo.org/hacking/older-versions.html">other in-tree docs and wiki pages</a>, into a book that’s richer and easier to search and navigate.</p>
4781. <p>Servo now supports several new features in its nightly builds:</p>
4782. <ul>
4783. <li>as of 2024-04-02, <code>files</code> setter on HTMLInputElement (<a href="https://github.com/shanehandley">@shanehandley</a>, <a href="https://github.com/servo/servo/pull/31934">#31934</a>)</li>
4784. <li>as of 2024-04-05, <strong>‘ex’ units</strong> in CSS (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/31966">#31966</a>)</li>
4785. <li>as of 2024-04-05, <code>onSubmittedWorkDone</code> method on GPUQueue (<a href="https://github.com/sagudev">@sagudev</a>, <a href="https://github.com/servo/servo/pull/31772">#31772</a>)</li>
4786. <li>as of 2024-04-08, <code>deleteRow(-1)</code> on empty HTMLTableElement (<a href="https://github.com/shanehandley">@shanehandley</a>, <a href="https://github.com/servo/servo/pull/32009">#32009</a>)</li>
4787. <li>as of 2024-04-12, <strong>ElementInternals</strong> and <strong>attachInternals</strong> (<a href="https://github.com/pshaughn">@pshaughn</a>, <a href="https://github.com/cathiechen">@cathiechen</a>, <a href="https://github.com/servo/servo/pull/25705">#25705</a>, <a href="https://github.com/servo/servo/pull/31980">#31980</a>)</li>
4788. <li>as of 2024-04-16, <strong>‘background-attachment: fixed’</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/32068">#32068</a>)</li>
4789. <li>as of 2024-04-16, <strong><object></strong> with <strong>image data URLs</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/32069">#32069</a>)</li>
4790. <li>as of 2024-04-18, <strong>‘clear’</strong> property on <strong><br></strong> elements (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/32094">#32094</a>)</li>
4791. <li>as of 2024-04-23, basic support for <strong>‘list-style-position: outside’</strong> (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/32114">#32114</a>)</li>
4792. </ul>
4793. <p>As of 2024-04-05, we now support <strong>non-autoplay <video></strong> (<a href="https://github.com/eerii">@eerii</a>, <a href="https://github.com/servo/media/pull/419">media#419</a>, <a href="https://github.com/servo/servo/pull/32001">#32001</a>), as long as the page provides its own controls, as well as the <strong>‘baseline-source’</strong> property (<a href="https://github.com/MunishMummadi">@MunishMummadi</a>, <a href="https://github.com/servo/servo/pull/31904">#31904</a>, <a href="https://github.com/servo/servo/pull/31913">#31913</a>).
4794. Both of these contributors started out as Outreachy participants, and we’re thrilled to see their continued work on improving Servo.</p>
4795. <p>We’ve also landed several other rendering improvements:</p>
4796. <ul>
4797. <li><strong>Stylo</strong> is now fully caught up with upstream (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/31932">#31932</a>, <a href="https://github.com/servo/servo/pull/31991">#31991</a>, <a href="https://github.com/servo/servo/pull/32032">#32032</a>, <a href="https://github.com/servo/servo/pull/32066">#32066</a>, <a href="https://github.com/servo/servo/pull/32089">#32089</a>, <a href="https://github.com/servo/servo/pull/32128">#32128</a>)</li>
4798. <li>elements or frames <strong>no longer scroll to top</strong> when transforms change (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/31892">#31892</a>)</li>
4799. <li>fixed <strong>intrinsic sizing</strong> of inline content containing <strong>‘pre-wrap’</strong> (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/31930">#31930</a>)</li>
4800. <li>fixed <strong>margin collapsing</strong> with indefinite percentages or non-zero height (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/32059">#32059</a>, <a href="https://github.com/servo/servo/pull/32060">#32060</a>)</li>
4801. <li>fixed some (but not all) <strong>HTTP 400</strong> errors when sending requests to nginx (<a href="https://github.com/philip-lamb">@philip-lamb</a>, <a href="https://github.com/servo/servo/pull/32024">#32024</a>, <a href="https://github.com/servo/servo/pull/32093">#32093</a>)</li>
4802. <li>fixed <strong>‘min-height’</strong> and <strong>‘max-height’</strong> on elements with <strong>‘float’</strong> (<a href="https://github.com/Loirooriol">@Loirooriol</a>, <a href="https://github.com/servo/servo/pull/32057">#32057</a>)</li>
4803. </ul>
4804. <p>Our font rendering has improved, with support for selecting the correct weight and style in <strong>indexed fonts (.ttc)</strong> on Linux (<a href="https://github.com/mukilan">@mukilan</a>, <a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/32127">#32127</a>), as well as support for <strong>emoji font fallback</strong> on macOS (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/32122">#32122</a>).
4805. Note that color emoji are not yet supported.</p>
4806. <p>Other big changes are coming to Servo’s font loading and rendering, thanks to <a href="https://github.com/mrobinson">@mrobinson</a>’s <strong>font system redesign</strong> RFC (<a href="https://github.com/servo/servo/issues/32033">#32033</a>).
4807. Work has already started on this (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/mukilan">@mukilan</a>, <a href="https://github.com/servo/servo/pull/32034">#32034</a>, <a href="https://github.com/servo/servo/pull/32038">#32038</a>, <a href="https://github.com/servo/servo/pull/32100">#32100</a>, <a href="https://github.com/servo/servo/pull/32101">#32101</a>, <a href="https://github.com/servo/servo/pull/32115">#32115</a>), with the eventual goal of making font data <strong>zero-copy readable from multiple threads</strong>.
4808. This in turn will fix several major issues with font caching, including cached font data leaking over time and between pages, unnecessary loading from disk, and unnecessary copying to layout.</p>
4809. <p>We’ve also started simplifying the script–layout interface (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/31937">#31937</a>, <a href="https://github.com/servo/servo/pull/32081">#32081</a>), since <a href="https://servo.org/blog/2024/02/28/gamepads-font-fallback-space-jam/">layout was merged into the script thread</a>, and script can now call into layout without IPC.</p>
4810. <h3>Embedding and dev changes <a class="header-anchor" href="https://servo.org/blog/2024/04/26/acid2-servo-book-qt/#embedding-and-dev-changes">
4811.        <span class="icon hashlink"><i class="fas fa-link"></i></span>
4812.      </a></h3>
4813. <figure class="_figr"><a href="https://servo.org/img/blog/cxx-qt-servo-webview.png"><img alt="Servo running in a Qt app via CXX-Qt" src="https://servo.org/img/blog/cxx-qt-servo-webview.png" /></a>
4814. <figcaption>The prototype shows that Servo can be integrated with a Qt app via <a href="https://github.com/KDAB/cxx-qt">CXX-Qt</a>.</figcaption></figure>
4815. <p><span class="_floatmin"></span>A prototype for <strong>integrating Servo with Qt</strong> was built by <a href="https://github.com/ahayzen-kdab">@ahayzen-kdab</a> and <a href="https://github.com/vimpostor">@vimpostor</a> and <a href="https://www.kdab.com/kdab-at-embedded-world-2024/">shown at Embedded World 2024</a>.
4816. We’re looking forward to incorporating their feedback from this to improve Servo’s embedding API.
4817. For more details, check out <a href="https://github.com/KDABLabs/cxx-qt-servo-webview">their GitHub repo</a> and <a href="https://www.kdab.com/embedding-servo-in-qt/"><em>Embedding the Servo Web Engine in Qt</em></a>.</p>
4818. <p>Servo now supports <strong>multiple concurrent webviews</strong> (<a href="https://github.com/wusyong">@wusyong</a>, <a href="https://github.com/delan">@delan</a>, <a href="https://github.com/atbrakhi">@atbrakhi</a>, <a href="https://github.com/servo/servo/pull/31417">#31417</a>, <a href="https://github.com/servo/servo/pull/32067">#32067</a>)!
4819. This is a big step towards making Servo a viable embedded webview, and we will soon use it to implement tabbed browsing in servoshell (<a href="https://github.com/delan">@delan</a>, <a href="https://github.com/servo/servo/pull/31545">#31545</a>).</p>
4820. <p>Three of the slowest crates in the Servo build process are <strong>mozjs_sys</strong>, <strong>mozangle</strong>, and <strong>script</strong>.
4821. The first two compile some very large C++ libraries in their build scripts — SpiderMonkey and ANGLE respectively — and the third blocks on the first two.
4822. They can account for over two minutes of build time, even on a very fast machine (AMD 7950X), and a breaking change in newer versions of GNU Make (<a href="https://github.com/servo/mozjs/issues/375">mozjs#375</a>) can make mozjs_sys take <strong>over eight minutes</strong> to build!</p>
4823. <p>mozjs_sys now uses a <strong>prebuilt version of SpiderMonkey</strong> by default (<a href="https://github.com/wusyong">@wusyong</a>, <a href="https://github.com/sagudev">@sagudev</a>, <a href="https://github.com/servo/mozjs/pull/450">mozjs#450</a>, <a href="https://github.com/servo/servo/pull/31824">#31824</a>), <strong>cutting clean build times by over seven minutes</strong> on a very fast machine (see above).
4824. On Linux with Nix (the package manager), where we run an unaffected version of GNU Make, it can still save over 100 seconds on a quad-core CPU with SMT.
4825. Further savings will be possible once we <a href="https://github.com/servo/mozangle/pull/71#issuecomment-1878567207">do the same for mozangle</a>.</p>
4826. <p>If you use NixOS, or any Linux distro with Nix, you can now get a shell with all of the tools and dependencies needed to build and run Servo by typing <code>nix-shell</code> (<a href="https://github.com/delan">@delan</a>, <a href="https://github.com/servo/servo/pull/32035">#32035</a>), without also needing to type <code>etc/shell.nix</code>.</p>
4827. <p>As for CI, our experimental Android build now supports aarch64 (<a href="https://github.com/mukilan">@mukilan</a>, <a href="https://github.com/servo/servo/pull/32137">#32137</a>), in addition to Android on armv7, x86_64, and i686, and we’ve improved flakiness in the WebGPU tests (<a href="https://github.com/sagudev">@sagudev</a>, <a href="https://github.com/servo/servo/pull/31952">#31952</a>) and macOS builds (<a href="https://github.com/mrobinson">@mrobinson</a>, <a href="https://github.com/servo/servo/pull/32005">#32005</a>).</p>
4828. <h3>Conferences and events <a class="header-anchor" href="https://servo.org/blog/2024/04/26/acid2-servo-book-qt/#conferences-and-events">
4829.        <span class="icon hashlink"><i class="fas fa-link"></i></span>
4830.      </a></h3>
4831. <p>Earlier this month, Rakhi Sharma gave her talk <a href="https://servo.org/slides/2024-04-16-open-source-summit-NA/"><strong>A year of Servo reboot: where are we now?</strong></a> at <a href="https://events.linuxfoundation.org/open-source-summit-north-america/">Open Source Summit North America</a> (<a href="https://servo.org/slides/2024-04-16-open-source-summit-NA/">slides</a>; recording available soon) and at the <a href="https://www.meetup.com/Seattle-Rust-Meetup/">Seattle Rust User Group</a> (<a href="https://servo.org/slides/2024-04-16-seattle-rust-user-group/">slides</a>).</p>
4832. <p>In the Netherlands, Gregory Terzian will be presenting <strong>Modular Servo: Three Paths Forward</strong> at the <a href="https://europe2024.gosim.org/schedule#mobile-and-web-app">GOSIM Conference 2024</a>, on <strong>6 May</strong> at <strong>15:10 local time</strong> (13:10 UTC).
4833. That’s the <strong>same venue as <a href="https://2024.rustnl.org/">RustNL 2024</a></strong>, just one day earlier, and you can also find Gregory, Rakhi, and Nico at RustNL afterwards.
4834. See you there!&lt;/p&gt;</description>
4835. <pubDate>Fri, 26 Apr 2024 00:00:00 +0000</pubDate>
4836. </item>
4837. <item>
4838. <title>Will Kahn-Greene: crashstats-tools v2.0.0 released!</title>
4839. <guid isPermaLink="true">https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html</guid>
4840. <link>https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html</link>
4841. <description>&lt;section id=&quot;what-is-it&quot;&gt;
4842. <h3>What is it?</h3>
4843. <p><a class="reference external" href="https://github.com/willkg/crashstats-tools/">crashstats-tools</a> is a set of
4844. command-line tools for working with Crash Stats
4845. (<a class="reference external" href="https://crash-stats.mozilla.org/">https://crash-stats.mozilla.org/</a>).</p>
4846. <p>crashstats-tools comes with four commands:</p>
4847. <ul class="simple">
4848. <li><p>supersearch: for performing Crash Stats Super Search queries</p></li>
4849. <li><p>supersearchfacet: for performing aggregations, histograms, and cardinality
4850. Crash Stats Super Search queries</p></li>
4851. <li><p>fetch-data: for fetching raw crash, dumps, and processed crash data for
4852. specified crash ids</p></li>
4853. <li><p>reprocess: for sending crash report reprocess requests</p></li>
4854. </ul>
4855. </section>
4856. <section id="v2-0-0-released">
4857. <h3>v2.0.0 released!</h3>
4858. <p>There have been a lot of improvements since the last blog post for the v1.0.1
4859. release. New commands, new features, improved cli ui, etc.</p>
4860. <p>v2.0.0 focused on two major things:</p>
4861. <ol class="arabic simple">
4862. <li><p>improving <code class="docutils literal">supersearchfacet</code> to support nested aggregation, histogram, and
4863. cardinality queries</p></li>
4864. <li><p>moving some of the code into a <code class="docutils literal">crashstats_tools.libcrashstats</code> module
4865. improving its use as a library</p></li>
4866. </ol>
4867. </section>
4868. <section id="improved-supersearchfacet">
4869. <h3>Improved supersearchfacet</h3>
4870. <p>The other day, <a class="reference external" href="https://hacks.mozilla.org/2024/04/porting-a-cross-platform-gui-application-to-rust/">Alex and team finished up the crash reporter Rust rewrite</a>.
4871. The crash reporter rewrite landed and is available in Firefox, nightly channel,
4872. where <code class="docutils literal">build_id >= 20240321093532</code>.</p>
4873. <p>The crash reporter is one of the clients that submits crash reports to Socorro
4874. which is now maintained by the Observability Team. Firefox has multiple crash
4875. reporter clients and there are many ways that crash reports can get submitted
4876. to Socorro.</p>
4877. <p>One of the changes we can see in the crash report data now is the change in
4878. <code class="docutils literal"><span class="pre">User-Agent</span></code> header. The new rewritten crash reporter sends a header of
4879. <code class="docutils literal"><span class="pre">crash-reporter/1.0.0</span></code>. That gets captured by the collector and put in the
4880. raw crash <code class="docutils literal">metadata.user_agent</code> field. It doesn't get indexed, so we can't
4881. search on it directly.</p>
4882. <p>We can get a sampling of the last 100 crash reports, download the raw crash
4883. data, and look at the user agents.</p>
4884. <div class="code"><pre class="code bash"><a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-1" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-1" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-1"></a>$ supersearch --num<span class="o">=</span><span class="m">100</span> --product<span class="o">=</span>Firefox --build_id<span class="o">=</span><span class="s1">'>=20240321093532'</span> <span class="se">\</span>
4885. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-2" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-2" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-2"></a>    --release_channel<span class="o">=</span>nightly > crashids.txt
4886. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-3" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-3" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-3"></a>$ fetch-data --raw --no-dumps --no-processed crashdata < crashids.txt
4887. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-4" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-4" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-4"></a>$ jq .metadata.user_agent crashdata/raw_crash/*/* <span class="p">|</span> sort <span class="p">|</span> uniq -c
4888. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-5" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-5" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-5"></a>     <span class="m">16</span> <span class="s2">"crashreporter/1.0.0"</span>
4889. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-6" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-6" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-6"></a>      <span class="m">2</span> <span class="s2">"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:127.0) Gecko/20100101 Firefox/127.0"</span>
4890. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-7" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-7" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-7"></a>      <span class="m">1</span> <span class="s2">"Mozilla/5.0 (Windows NT 10.0; rv:127.0) Gecko/20100101 Firefox/127.0"</span>
4891. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-8" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-8" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-8"></a>      <span class="m">2</span> <span class="s2">"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0"</span>
4892. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-9" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-9" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-9"></a>     <span class="m">63</span> <span class="s2">"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:127.0) Gecko/20100101 Firefox/127.0"</span>
4893. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-10" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-10" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-10"></a>      <span class="m">1</span> <span class="s2">"Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0"</span>
4894. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-11" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-11" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-11"></a>     <span class="m">12</span> <span class="s2">"Mozilla/5.0 (X11; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0"</span>
4895. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-12" id="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-12" name="rest_code_ec3ca2839a4f4f5d8897dd9381a9661a-12"></a>      <span class="m">3</span> <span class="s2">"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0"</span>
4896. </pre></div>
4897. <p>16 out of 100 crash reports were submitted by the new crash reporter. We were
4898. surprised there are so many Firefox user agents. We discussed this on Slack. I
4899. loosely repeat it here because it's a great way to show off some of the changes
4900. of <code class="docutils literal">supersearchfacet</code> in v2.0.0.</p>
4901. <p>First, the rewritten crash reporter only affects the parent (aka main) process.
4902. The other processes have different crash reporters that weren't rewritten.</p>
4903. <p>How many process types are there for Firefox crash reports in the last week? We
4904. can see that in the <code class="docutils literal">ProcessType</code> annotation
4905. (<a class="reference external" href="https://crash-stats.mozilla.org/documentation/datadictionary/dataset/annotation/field/ProcessType">docs</a>)
4906. which is processed and saved in the <code class="docutils literal">process_type</code> field
4907. (<a class="reference external" href="https://crash-stats.mozilla.org/documentation/datadictionary/dataset/processed/field/process_type">docs</a>).</p>
4908. <div class="code"><pre class="code bash"><a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-1" id="rest_code_20d71c94db314fc89188d9d6521668d1-1" name="rest_code_20d71c94db314fc89188d9d6521668d1-1"></a>$ supersearchfacet --product<span class="o">=</span>Firefox --build_id<span class="o">=</span><span class="s1">'>=20240321093532'</span> --release_channel<span class="o">=</span>nightly
4909. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-2" id="rest_code_20d71c94db314fc89188d9d6521668d1-2" name="rest_code_20d71c94db314fc89188d9d6521668d1-2"></a>    --_facets<span class="o">=</span>process_type
4910. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-3" id="rest_code_20d71c94db314fc89188d9d6521668d1-3" name="rest_code_20d71c94db314fc89188d9d6521668d1-3"></a>process_type
4911. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-4" id="rest_code_20d71c94db314fc89188d9d6521668d1-4" name="rest_code_20d71c94db314fc89188d9d6521668d1-4"></a> process_type <span class="p">|</span> count
4912. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-5" id="rest_code_20d71c94db314fc89188d9d6521668d1-5" name="rest_code_20d71c94db314fc89188d9d6521668d1-5"></a>--------------<span class="p">|</span>-------
4913. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-6" id="rest_code_20d71c94db314fc89188d9d6521668d1-6" name="rest_code_20d71c94db314fc89188d9d6521668d1-6"></a> content      <span class="p">|</span> <span class="m">3664</span>
4914. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-7" id="rest_code_20d71c94db314fc89188d9d6521668d1-7" name="rest_code_20d71c94db314fc89188d9d6521668d1-7"></a> parent       <span class="p">|</span> <span class="m">2323</span>
4915. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-8" id="rest_code_20d71c94db314fc89188d9d6521668d1-8" name="rest_code_20d71c94db314fc89188d9d6521668d1-8"></a> gpu          <span class="p">|</span> <span class="m">855</span>
4916. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-9" id="rest_code_20d71c94db314fc89188d9d6521668d1-9" name="rest_code_20d71c94db314fc89188d9d6521668d1-9"></a> utility      <span class="p">|</span> <span class="m">225</span>
4917. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-10" id="rest_code_20d71c94db314fc89188d9d6521668d1-10" name="rest_code_20d71c94db314fc89188d9d6521668d1-10"></a> rdd          <span class="p">|</span> <span class="m">60</span>
4918. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-11" id="rest_code_20d71c94db314fc89188d9d6521668d1-11" name="rest_code_20d71c94db314fc89188d9d6521668d1-11"></a> plugin       <span class="p">|</span> <span class="m">18</span>
4919. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-12" id="rest_code_20d71c94db314fc89188d9d6521668d1-12" name="rest_code_20d71c94db314fc89188d9d6521668d1-12"></a> socket       <span class="p">|</span> <span class="m">2</span>
4920. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_20d71c94db314fc89188d9d6521668d1-13" id="rest_code_20d71c94db314fc89188d9d6521668d1-13" name="rest_code_20d71c94db314fc89188d9d6521668d1-13"></a> total        <span class="p">|</span> <span class="m">7147</span>
4921. </pre></div>
4922. <p>Judging by that output, I would expect to see a higher percentage of
4923. <code class="docutils literal">crashreporter/1.0.0</code> in our sampling of 100 crash reports.</p>
4924. <p>Turns out that Firefox uses different code to submit crash reports not just by
4925. process type, but also by user action. That's in the <code class="docutils literal">SubmittedFrom</code> annotation
4926. (<a class="reference external" href="https://crash-stats.mozilla.org/documentation/datadictionary/dataset/annotation/field/SubmittedFrom">docs</a>)
4927. which is processed and saved in the <code class="docutils literal">submitted_from</code> field
4928. (<a class="reference external" href="https://crash-stats.mozilla.org/documentation/datadictionary/dataset/processed/field/submitted_from">docs</a>).</p>
4929. <div class="code"><pre class="code bash"><a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-1" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-1" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-1"></a>$ supersearchfacet --product<span class="o">=</span>Firefox --build_id<span class="o">=</span><span class="s1">'>=20240321093532'</span> --release_channel<span class="o">=</span>nightly <span class="se">\</span>
4930. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-2" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-2" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-2"></a>    --_facets<span class="o">=</span>submitted_from
4931. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-3" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-3" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-3"></a>submitted_from
4932. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-4" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-4" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-4"></a> submitted_from <span class="p">|</span> count
4933. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-5" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-5" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-5"></a>----------------<span class="p">|</span>-------
4934. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-6" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-6" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-6"></a> Auto           <span class="p">|</span> <span class="m">3477</span>
4935. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-7" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-7" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-7"></a> Client         <span class="p">|</span> <span class="m">1741</span>
4936. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-8" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-8" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-8"></a> CrashedTab     <span class="p">|</span> <span class="m">928</span>
4937. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-9" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-9" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-9"></a> Infobar        <span class="p">|</span> <span class="m">792</span>
4938. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-10" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-10" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-10"></a> AboutCrashes   <span class="p">|</span> <span class="m">209</span>
4939. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_fab4c0a65a1e4ebe967c24600aa38907-11" id="rest_code_fab4c0a65a1e4ebe967c24600aa38907-11" name="rest_code_fab4c0a65a1e4ebe967c24600aa38907-11"></a> total          <span class="p">|</span> <span class="m">7147</span>
4940. </pre></div>
4941. <p>What is "Auto"? The user can opt-in to auto-send crash reports. When Firefox
4942. upgrades and this setting is set, then Firefox will auto-send any unsubmitted
4943. crash reports. The nightly channel has two updates a day, so there's lots of
4944. opportunity for this event to trigger.</p>
4945. <p>What're the counts for <code class="docutils literal">submitted_from</code>/<code class="docutils literal">process_type</code> pairs?</p>
4946. <div class="code"><pre class="code bash"><a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-1" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-1" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-1"></a>$ supersearchfacet --product<span class="o">=</span>Firefox --build_id<span class="o">=</span><span class="s1">'>=20240321093532'</span> --release_channel<span class="o">=</span>nightly <span class="se">\</span>
4947. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-2" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-2" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-2"></a>    --_aggs.process_type<span class="o">=</span>submitted_from
4948. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-3" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-3" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-3"></a>process_type / submitted_from
4949. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-4" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-4" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-4"></a> process_type / submitted_from <span class="p">|</span> count
4950. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-5" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-5" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-5"></a>-------------------------------<span class="p">|</span>-------
4951. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-6" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-6" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-6"></a> content / Auto                <span class="p">|</span> <span class="m">2214</span>
4952. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-7" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-7" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-7"></a> content / CrashedTab          <span class="p">|</span> <span class="m">926</span>
4953. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-8" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-8" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-8"></a> content / Infobar             <span class="p">|</span> <span class="m">399</span>
4954. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-9" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-9" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-9"></a> content / AboutCrashes        <span class="p">|</span> <span class="m">125</span>
4955. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-10" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-10" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-10"></a> parent / Client               <span class="p">|</span> <span class="m">1741</span>
4956. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-11" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-11" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-11"></a> parent / Auto                 <span class="p">|</span> <span class="m">450</span>
4957. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-12" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-12" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-12"></a> parent / Infobar              <span class="p">|</span> <span class="m">107</span>
4958. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-13" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-13" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-13"></a> parent / AboutCrashes         <span class="p">|</span> <span class="m">25</span>
4959. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-14" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-14" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-14"></a> gpu / Auto                    <span class="p">|</span> <span class="m">565</span>
4960. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-15" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-15" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-15"></a> gpu / Infobar                 <span class="p">|</span> <span class="m">236</span>
4961. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-16" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-16" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-16"></a> gpu / AboutCrashes            <span class="p">|</span> <span class="m">54</span>
4962. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-17" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-17" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-17"></a> utility / Auto                <span class="p">|</span> <span class="m">198</span>
4963. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-18" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-18" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-18"></a> utility / Infobar             <span class="p">|</span> <span class="m">25</span>
4964. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-19" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-19" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-19"></a> utility / AboutCrashes        <span class="p">|</span> <span class="m">2</span>
4965. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-20" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-20" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-20"></a> rdd / Auto                    <span class="p">|</span> <span class="m">34</span>
4966. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-21" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-21" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-21"></a> rdd / Infobar                 <span class="p">|</span> <span class="m">23</span>
4967. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-22" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-22" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-22"></a> rdd / AboutCrashes            <span class="p">|</span> <span class="m">3</span>
4968. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-23" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-23" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-23"></a> plugin / Auto                 <span class="p">|</span> <span class="m">14</span>
4969. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-24" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-24" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-24"></a> plugin / CrashedTab           <span class="p">|</span> <span class="m">2</span>
4970. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-25" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-25" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-25"></a> plugin / Infobar              <span class="p">|</span> <span class="m">2</span>
4971. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-26" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-26" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-26"></a> socket / Auto                 <span class="p">|</span> <span class="m">2</span>
4972. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_db3692710cd6465ba1c7d3b13f8f5099-27" id="rest_code_db3692710cd6465ba1c7d3b13f8f5099-27" name="rest_code_db3692710cd6465ba1c7d3b13f8f5099-27"></a> total                         <span class="p">|</span> <span class="m">7147</span>
4973. </pre></div>
4974. <p>We can spot check these different combinations to see what the user-agent looks
4975. like.</p>
4976. <p>For brevity, we'll just look at <code class="docutils literal">parent / Client</code> in this blog post.</p>
4977. <div class="code"><pre class="code bash"><a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_96abcc445423445e969536857cd50448-1" id="rest_code_96abcc445423445e969536857cd50448-1" name="rest_code_96abcc445423445e969536857cd50448-1"></a>$ supersearch --num<span class="o">=</span><span class="m">100</span> --product<span class="o">=</span>Firefox --build_id<span class="o">=</span><span class="s1">'>=20240321093532'</span> --release_channel<span class="o">=</span>nightly <span class="se">\</span>
4978. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_96abcc445423445e969536857cd50448-2" id="rest_code_96abcc445423445e969536857cd50448-2" name="rest_code_96abcc445423445e969536857cd50448-2"></a>    --process_type<span class="o">=</span>parent --submitted_from<span class="o">=</span><span class="s1">'~Client'</span> > crashids_clarified.txt
4979. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_96abcc445423445e969536857cd50448-3" id="rest_code_96abcc445423445e969536857cd50448-3" name="rest_code_96abcc445423445e969536857cd50448-3"></a>$ fetch-data --raw --no-dumps --no-processed crashdata_clarified < crashids_clarified.txt
4980. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_96abcc445423445e969536857cd50448-4" id="rest_code_96abcc445423445e969536857cd50448-4" name="rest_code_96abcc445423445e969536857cd50448-4"></a>$ jq .metadata.user_agent crashdata_clarified/raw_crash/*/* <span class="p">|</span> sort <span class="p">|</span> uniq -c
4981. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_96abcc445423445e969536857cd50448-5" id="rest_code_96abcc445423445e969536857cd50448-5" name="rest_code_96abcc445423445e969536857cd50448-5"></a>    <span class="m">100</span> <span class="s2">"crashreporter/1.0.0"</span>
4982. </pre></div>
4983. <p>Seems like the crash reporter rewrite only affects crash reports where
4984. <code class="docutils literal">ProcessType=parent</code> and <code class="docutils literal">SubmittedFrom=Client</code>. All the other
4985. <code class="docutils literal">process_type</code>/<code class="docutils literal">submitted_from</code> combinations get submitted a different way
4986. where the user agent is the browser itself.</p>
4987. <p>How many crash reports has the new crash reporter submitted over time?</p>
4988. <div class="code"><pre class="code bash"><a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-1" id="rest_code_a69437e062104bdebf3db51e94d1b704-1" name="rest_code_a69437e062104bdebf3db51e94d1b704-1"></a>$ supersearchfacet --_histogram.date<span class="o">=</span>product --_histogram.interval<span class="o">=</span>1d --denote-weekends <span class="se">\</span>
4989. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-2" id="rest_code_a69437e062104bdebf3db51e94d1b704-2" name="rest_code_a69437e062104bdebf3db51e94d1b704-2"></a>    --date<span class="o">=</span><span class="s1">'>=2024-03-20'</span> --date<span class="o">=</span><span class="s1">'<=2024-04-25'</span> <span class="se">\</span>
4990. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-3" id="rest_code_a69437e062104bdebf3db51e94d1b704-3" name="rest_code_a69437e062104bdebf3db51e94d1b704-3"></a>    --release_channel<span class="o">=</span>nightly --product<span class="o">=</span>Firefox --build_id<span class="o">=</span><span class="s1">'>=20240321093532'</span> <span class="se">\</span>
4991. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-4" id="rest_code_a69437e062104bdebf3db51e94d1b704-4" name="rest_code_a69437e062104bdebf3db51e94d1b704-4"></a>    --submitted_from<span class="o">=</span><span class="s1">'~Client'</span> --process_type<span class="o">=</span>parent
4992. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-5" id="rest_code_a69437e062104bdebf3db51e94d1b704-5" name="rest_code_a69437e062104bdebf3db51e94d1b704-5"></a>histogram_date.product
4993. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-6" id="rest_code_a69437e062104bdebf3db51e94d1b704-6" name="rest_code_a69437e062104bdebf3db51e94d1b704-6"></a> histogram_date <span class="p">|</span> Firefox <span class="p">|</span> total
4994. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-7" id="rest_code_a69437e062104bdebf3db51e94d1b704-7" name="rest_code_a69437e062104bdebf3db51e94d1b704-7"></a>----------------<span class="p">|</span>---------<span class="p">|</span>-------
4995. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-8" id="rest_code_a69437e062104bdebf3db51e94d1b704-8" name="rest_code_a69437e062104bdebf3db51e94d1b704-8"></a> <span class="m">2024</span>-03-21     <span class="p">|</span> <span class="m">58</span>      <span class="p">|</span> <span class="m">58</span>
4996. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-9" id="rest_code_a69437e062104bdebf3db51e94d1b704-9" name="rest_code_a69437e062104bdebf3db51e94d1b704-9"></a> <span class="m">2024</span>-03-22     <span class="p">|</span> <span class="m">124</span>     <span class="p">|</span> <span class="m">124</span>
4997. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-10" id="rest_code_a69437e062104bdebf3db51e94d1b704-10" name="rest_code_a69437e062104bdebf3db51e94d1b704-10"></a> <span class="m">2024</span>-03-23 **  <span class="p">|</span> <span class="m">189</span>     <span class="p">|</span> <span class="m">189</span>
4998. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-11" id="rest_code_a69437e062104bdebf3db51e94d1b704-11" name="rest_code_a69437e062104bdebf3db51e94d1b704-11"></a> <span class="m">2024</span>-03-24 **  <span class="p">|</span> <span class="m">289</span>     <span class="p">|</span> <span class="m">289</span>
4999. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-12" id="rest_code_a69437e062104bdebf3db51e94d1b704-12" name="rest_code_a69437e062104bdebf3db51e94d1b704-12"></a> <span class="m">2024</span>-03-25     <span class="p">|</span> <span class="m">202</span>     <span class="p">|</span> <span class="m">202</span>
5000. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-13" id="rest_code_a69437e062104bdebf3db51e94d1b704-13" name="rest_code_a69437e062104bdebf3db51e94d1b704-13"></a> <span class="m">2024</span>-03-26     <span class="p">|</span> <span class="m">164</span>     <span class="p">|</span> <span class="m">164</span>
5001. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-14" id="rest_code_a69437e062104bdebf3db51e94d1b704-14" name="rest_code_a69437e062104bdebf3db51e94d1b704-14"></a> <span class="m">2024</span>-03-27     <span class="p">|</span> <span class="m">199</span>     <span class="p">|</span> <span class="m">199</span>
5002. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-15" id="rest_code_a69437e062104bdebf3db51e94d1b704-15" name="rest_code_a69437e062104bdebf3db51e94d1b704-15"></a> <span class="m">2024</span>-03-28     <span class="p">|</span> <span class="m">187</span>     <span class="p">|</span> <span class="m">187</span>
5003. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-16" id="rest_code_a69437e062104bdebf3db51e94d1b704-16" name="rest_code_a69437e062104bdebf3db51e94d1b704-16"></a> <span class="m">2024</span>-03-29     <span class="p">|</span> <span class="m">188</span>     <span class="p">|</span> <span class="m">188</span>
5004. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-17" id="rest_code_a69437e062104bdebf3db51e94d1b704-17" name="rest_code_a69437e062104bdebf3db51e94d1b704-17"></a> <span class="m">2024</span>-03-30 **  <span class="p">|</span> <span class="m">155</span>     <span class="p">|</span> <span class="m">155</span>
5005. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-18" id="rest_code_a69437e062104bdebf3db51e94d1b704-18" name="rest_code_a69437e062104bdebf3db51e94d1b704-18"></a> <span class="m">2024</span>-03-31 **  <span class="p">|</span> <span class="m">146</span>     <span class="p">|</span> <span class="m">146</span>
5006. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-19" id="rest_code_a69437e062104bdebf3db51e94d1b704-19" name="rest_code_a69437e062104bdebf3db51e94d1b704-19"></a> <span class="m">2024</span>-04-01     <span class="p">|</span> <span class="m">201</span>     <span class="p">|</span> <span class="m">201</span>
5007. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-20" id="rest_code_a69437e062104bdebf3db51e94d1b704-20" name="rest_code_a69437e062104bdebf3db51e94d1b704-20"></a> <span class="m">2024</span>-04-02     <span class="p">|</span> <span class="m">226</span>     <span class="p">|</span> <span class="m">226</span>
5008. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-21" id="rest_code_a69437e062104bdebf3db51e94d1b704-21" name="rest_code_a69437e062104bdebf3db51e94d1b704-21"></a> <span class="m">2024</span>-04-03     <span class="p">|</span> <span class="m">236</span>     <span class="p">|</span> <span class="m">236</span>
5009. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-22" id="rest_code_a69437e062104bdebf3db51e94d1b704-22" name="rest_code_a69437e062104bdebf3db51e94d1b704-22"></a> <span class="m">2024</span>-04-04     <span class="p">|</span> <span class="m">266</span>     <span class="p">|</span> <span class="m">266</span>
5010. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-23" id="rest_code_a69437e062104bdebf3db51e94d1b704-23" name="rest_code_a69437e062104bdebf3db51e94d1b704-23"></a> <span class="m">2024</span>-04-05     <span class="p">|</span> <span class="m">259</span>     <span class="p">|</span> <span class="m">259</span>
5011. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-24" id="rest_code_a69437e062104bdebf3db51e94d1b704-24" name="rest_code_a69437e062104bdebf3db51e94d1b704-24"></a> <span class="m">2024</span>-04-06 **  <span class="p">|</span> <span class="m">227</span>     <span class="p">|</span> <span class="m">227</span>
5012. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-25" id="rest_code_a69437e062104bdebf3db51e94d1b704-25" name="rest_code_a69437e062104bdebf3db51e94d1b704-25"></a> <span class="m">2024</span>-04-07 **  <span class="p">|</span> <span class="m">214</span>     <span class="p">|</span> <span class="m">214</span>
5013. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-26" id="rest_code_a69437e062104bdebf3db51e94d1b704-26" name="rest_code_a69437e062104bdebf3db51e94d1b704-26"></a> <span class="m">2024</span>-04-08     <span class="p">|</span> <span class="m">259</span>     <span class="p">|</span> <span class="m">259</span>
5014. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-27" id="rest_code_a69437e062104bdebf3db51e94d1b704-27" name="rest_code_a69437e062104bdebf3db51e94d1b704-27"></a> <span class="m">2024</span>-04-09     <span class="p">|</span> <span class="m">257</span>     <span class="p">|</span> <span class="m">257</span>
5015. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-28" id="rest_code_a69437e062104bdebf3db51e94d1b704-28" name="rest_code_a69437e062104bdebf3db51e94d1b704-28"></a> <span class="m">2024</span>-04-10     <span class="p">|</span> <span class="m">223</span>     <span class="p">|</span> <span class="m">223</span>
5016. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-29" id="rest_code_a69437e062104bdebf3db51e94d1b704-29" name="rest_code_a69437e062104bdebf3db51e94d1b704-29"></a> <span class="m">2024</span>-04-11     <span class="p">|</span> <span class="m">250</span>     <span class="p">|</span> <span class="m">250</span>
5017. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-30" id="rest_code_a69437e062104bdebf3db51e94d1b704-30" name="rest_code_a69437e062104bdebf3db51e94d1b704-30"></a> <span class="m">2024</span>-04-12     <span class="p">|</span> <span class="m">235</span>     <span class="p">|</span> <span class="m">235</span>
5018. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-31" id="rest_code_a69437e062104bdebf3db51e94d1b704-31" name="rest_code_a69437e062104bdebf3db51e94d1b704-31"></a> <span class="m">2024</span>-04-13 **  <span class="p">|</span> <span class="m">154</span>     <span class="p">|</span> <span class="m">154</span>
5019. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-32" id="rest_code_a69437e062104bdebf3db51e94d1b704-32" name="rest_code_a69437e062104bdebf3db51e94d1b704-32"></a> <span class="m">2024</span>-04-14 **  <span class="p">|</span> <span class="m">162</span>     <span class="p">|</span> <span class="m">162</span>
5020. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-33" id="rest_code_a69437e062104bdebf3db51e94d1b704-33" name="rest_code_a69437e062104bdebf3db51e94d1b704-33"></a> <span class="m">2024</span>-04-15     <span class="p">|</span> <span class="m">207</span>     <span class="p">|</span> <span class="m">207</span>
5021. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-34" id="rest_code_a69437e062104bdebf3db51e94d1b704-34" name="rest_code_a69437e062104bdebf3db51e94d1b704-34"></a> <span class="m">2024</span>-04-16     <span class="p">|</span> <span class="m">201</span>     <span class="p">|</span> <span class="m">201</span>
5022. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-35" id="rest_code_a69437e062104bdebf3db51e94d1b704-35" name="rest_code_a69437e062104bdebf3db51e94d1b704-35"></a> <span class="m">2024</span>-04-17     <span class="p">|</span> <span class="m">346</span>     <span class="p">|</span> <span class="m">346</span>
5023. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-36" id="rest_code_a69437e062104bdebf3db51e94d1b704-36" name="rest_code_a69437e062104bdebf3db51e94d1b704-36"></a> <span class="m">2024</span>-04-18     <span class="p">|</span> <span class="m">270</span>     <span class="p">|</span> <span class="m">270</span>
5024. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-37" id="rest_code_a69437e062104bdebf3db51e94d1b704-37" name="rest_code_a69437e062104bdebf3db51e94d1b704-37"></a> <span class="m">2024</span>-04-19     <span class="p">|</span> <span class="m">221</span>     <span class="p">|</span> <span class="m">221</span>
5025. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-38" id="rest_code_a69437e062104bdebf3db51e94d1b704-38" name="rest_code_a69437e062104bdebf3db51e94d1b704-38"></a> <span class="m">2024</span>-04-20 **  <span class="p">|</span> <span class="m">190</span>     <span class="p">|</span> <span class="m">190</span>
5026. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-39" id="rest_code_a69437e062104bdebf3db51e94d1b704-39" name="rest_code_a69437e062104bdebf3db51e94d1b704-39"></a> <span class="m">2024</span>-04-21 **  <span class="p">|</span> <span class="m">183</span>     <span class="p">|</span> <span class="m">183</span>
5027. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-40" id="rest_code_a69437e062104bdebf3db51e94d1b704-40" name="rest_code_a69437e062104bdebf3db51e94d1b704-40"></a> <span class="m">2024</span>-04-22     <span class="p">|</span> <span class="m">266</span>     <span class="p">|</span> <span class="m">266</span>
5028. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-41" id="rest_code_a69437e062104bdebf3db51e94d1b704-41" name="rest_code_a69437e062104bdebf3db51e94d1b704-41"></a> <span class="m">2024</span>-04-23     <span class="p">|</span> <span class="m">303</span>     <span class="p">|</span> <span class="m">303</span>
5029. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_a69437e062104bdebf3db51e94d1b704-42" id="rest_code_a69437e062104bdebf3db51e94d1b704-42" name="rest_code_a69437e062104bdebf3db51e94d1b704-42"></a> <span class="m">2024</span>-04-24     <span class="p">|</span> <span class="m">308</span>     <span class="p">|</span> <span class="m">308</span>
5030. </pre></div>
5031. <p>There are more examples in the <a class="reference external" href="https://github.com/willkg/crashstats-tools">crashstats-tools README</a>.</p>
5032. </section>
5033. <section id="crashstats-tools-libcrashstats-library">
5034. <h3>crashstats_tools.libcrashstats library</h3>
5035. <p>Starting with v2.0.0, you can use <code class="docutils literal">crashstats_tools.libcrashstats</code> as a
5036. library for Python scripts.</p>
5037. <p>For example:</p>
5038. <div class="code"><pre class="code python"><a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_4b9e67fff7ad4f25929e70065aa75ccf-1" id="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-1" name="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-1"></a><span class="kn">from</span> <span class="nn">crashstats_tools.libcrashstats</span> <span class="kn">import</span> <span class="n">supersearch</span>
5039. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_4b9e67fff7ad4f25929e70065aa75ccf-2" id="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-2" name="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-2"></a>
5040. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_4b9e67fff7ad4f25929e70065aa75ccf-3" id="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-3" name="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-3"></a><span class="n">results</span> <span class="o">=</span> <span class="n">supersearch</span><span class="p">(</span><span class="n">params</span><span class="o">=</span><span class="p">{</span><span class="s2">"_columns"</span><span class="p">:</span> <span class="s2">"uuid"</span><span class="p">},</span> <span class="n">num_results</span><span class="o">=</span><span class="mi">100</span><span class="p">)</span>
5041. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_4b9e67fff7ad4f25929e70065aa75ccf-4" id="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-4" name="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-4"></a>
5042. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_4b9e67fff7ad4f25929e70065aa75ccf-5" id="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-5" name="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-5"></a><span class="k">for</span> <span class="n">result</span> <span class="ow">in</span> <span class="n">results</span><span class="p">:</span>
5043. <a href="https://bluesock.org/~willkg/blog/mozilla/crashstats_tools_v2_0_0.html#rest_code_4b9e67fff7ad4f25929e70065aa75ccf-6" id="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-6" name="rest_code_4b9e67fff7ad4f25929e70065aa75ccf-6"></a>    <span class="nb">print</span><span class="p">(</span><span class="sa">f</span><span class="s2">"</span><span class="si">{</span><span class="n">result</span><span class="si">}</span><span class="s2">"</span><span class="p">)</span>
5044. </pre></div>
5045. <p><code class="docutils literal">libcrashstats</code> makes using the Crash Stats API a little more ergonomic.</p>
5046. <p>See the <code class="docutils literal">crashstats_tools.libcrashstats</code>
5047. <a class="reference external" href="https://github.com/willkg/crashstats-tools?tab=readme-ov-file#library">library documentation</a>.</p>
5048. </section>
5049. <section id="be-thoughtful-about-using-data">
5050. <h3>Be thoughtful about using data</h3>
5051. <p>Make sure to use these tools in compliance with our data policy:</p>
5052. <p><a class="reference external" href="https://crash-stats.mozilla.org/documentation/protected_data_access/">https://crash-stats.mozilla.org/documentation/protected_data_access/</a></p>
5053. </section>
5054. <section id="where-to-go-for-more">
5055. <h3>Where to go for more</h3>
5056. <p>See the project on GitHub which includes a README which contains everything
5057. about the project including examples of usage, the issue tracker, and the
5058. source code:</p>
5059. <p><a class="reference external" href="https://github.com/willkg/crashstats-tools">https://github.com/willkg/crashstats-tools</a></p>
5060. <p>Let me know whether this helps you!</p>
5061. &lt;/section&gt;</description>
5062. <pubDate>Thu, 25 Apr 2024 16:00:00 +0000</pubDate>
5063. <dc:creator>Will Kahn-Greene</dc:creator>
5064. </item>
5065. <item>
5066. <title>Hacks.Mozilla.Org: Llamafile’s progress, four months in</title>
5067. <guid isPermaLink="false">https://hacks.mozilla.org/?p=48149</guid>
5068. <link>https://hacks.mozilla.org/2024/04/llamafiles-progress-four-months-in/</link>
5069. <description>&lt;p&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;When Mozilla’s Innovation group &lt;/span&gt;&lt;a href=&quot;https://hacks.mozilla.org/2023/11/introducing-llamafile/&quot;&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;first launched&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt; the &lt;/span&gt;&lt;a href=&quot;https://github.com/Mozilla-Ocho/llamafile&quot;&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;llamafile project&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt; late last year, we were thrilled by the immediate positive response from open source AI developers. It’s become one of Mozilla’s top three most-favorited repositories on GitHub, attracting a number of contributors, some excellent PRs, and a growing community on our &lt;/span&gt;&lt;a href=&quot;https://discord.gg/YTgM42NZEr&quot;&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;Discord server&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;.&lt;/span&gt;&lt;/p&gt;
5070. <p>Through it all, lead developer and project visionary <a href="https://github.com/jart">Justine Tunney</a> has remained hard at work on a wide variety of fundamental improvements to the project. Just last night, Justine <a href="https://github.com/Mozilla-Ocho/llamafile/releases/tag/0.8">shipped the v0.8 release of llamafile</a>, which includes not only support for the very latest open models, but also a number of big performance improvements for CPU inference.</p>
5071. <p>As a result of Justine’s work, today llamafile is both the easiest <i>and fastest</i> way to run a wide range of open large language models on your own hardware. See for yourself: with llamafile, you can run Meta’s just-released <a href="https://huggingface.co/jartine/Meta-Llama-3-8B-Instruct-llamafile">LLaMA 3 model</a>–which rivals the very best models available in its size class–on an everyday Macbook.</p>
5072. <p><span style="font-weight: 400;">How did we do it? To explain that, let’s take a step back and tell you about everything that’s changed since v0.1.</span></p>
5073. <p><b>tinyBLAS: democratizing GPU support for NVIDIA </b><b><i>and</i></b><b> AMD</b></p>
5074. <p><span style="font-weight: 400;">llamafile is built atop the now-legendary </span><a href="https://github.com/ggerganov/llama.cpp"><span style="font-weight: 400;">llama.cpp</span></a><span style="font-weight: 400;"> project. llama.cpp supports GPU-accelerated inference for NVIDIA processors via the cuBLAS linear algebra library, but that requires users to install NVIDIA’s CUDA SDK. We felt uncomfortable with that fact, because it conflicts with our project goal of building a fully open-source and transparent AI stack that anyone can run on commodity hardware. And besides, getting CUDA set up correctly can be a bear on some systems. There had to be a better way.</span></p>
5075. <p><span style="font-weight: 400;">With the community’s help (here’s looking at you, </span><a href="https://ahgamut.github.io/"><span style="font-weight: 400;">@ahgamut</span></a><span style="font-weight: 400;"> and </span><a href="https://github.com/mrdomino"><span style="font-weight: 400;">@mrdomino</span></a><span style="font-weight: 400;">!), we created our own solution: it’s called tinyBLAS, and it’s llamafile’s brand-new and highly efficient linear algebra library. tinyBLAS makes NVIDIA acceleration simple and seamless for llamafile users. On Windows, you don’t even need to install CUDA at all; all you need is the display driver you’ve probably already installed.</span></p>
5076. <p><span style="font-weight: 400;">But tinyBLAS is about more than just NVIDIA: it supports AMD GPUs, as well. This is no small feat. While AMD commands a respectable 20% of today’s GPU market, poor software and driver support have historically made them a secondary player in the machine learning space. That’s a shame, given that AMD’s GPUs offer high performance, are price competitive, and are widely available. </span></p>
5077. <p><span style="font-weight: 400;">One of llamafile’s goals is to democratize access to open source AI technology, and that means getting AMD a seat at the table. That’s exactly what we’ve done: with llamafile’s tinyBLAS, you can now easily make full use of your AMD GPU to accelerate local inference. And, as with CUDA, if you’re a Windows user you don’t even have to install AMD’s ROCm SDK.</span></p>
5078. <p><span style="font-weight: 400;">All of this means that, for many users, llamafile will automatically use your GPU right out of the box, with little to no effort on your part.</span></p>
5079. <p><b>CPU performance gains for faster local AI</b></p>
5080. <p><span style="font-weight: 400;">Here at Mozilla, we are keenly interested in the promise of “local AI,” in which AI models and applications run directly on end-user hardware instead of in the cloud. Local AI is exciting because it opens up the possibility of more user control over these systems and greater privacy and security for users.</span></p>
5081. <p><span style="font-weight: 400;">But many consumer devices lack the high-end GPUs that are often required for inference tasks. llama.cpp has been a game-changer in this regard because it makes local inference both possible and usably performant on CPUs instead of just GPUs. </span></p>
5082. <p><span style="font-weight: 400;">Justine’s recent work on llamafile has now pushed the state of the art even further. As documented in </span><a href="http://justine.lol/matmul/"><span style="font-weight: 400;">her detailed blog post</span></a><span style="font-weight: 400;"> on the subject, by writing 84 new matrix multiplication kernels she was able to increase llamafile’s prompt evaluation performance by an astonishing 10x compared to our previous release. This is a substantial and impactful step forward in the quest to make local AI viable on consumer hardware.</span></p>
5083. <p><span style="font-weight: 400;">This work is also a great example of our commitment to the open source AI community. After completing this work we immediately </span><a href="https://github.com/ggerganov/llama.cpp/pull/6414"><span style="font-weight: 400;">submitted a PR</span></a><span style="font-weight: 400;"> to upstream these performance improvements to llama.cpp. This was just the latest of a number of enhancements we’ve contributed back to llama.cpp, a practice we plan to continue.</span></p>
5084. <p><b>Raspberry Pi performance gains</b></p>
5085. <p><span style="font-weight: 400;">Speaking of consumer hardware, there are few examples that are both more interesting and more humble than the beloved Raspberry Pi. For a bargain basement price, you get a full-featured computer running Linux with plenty of computing power for typical desktop uses. It’s an impressive package, but historically it hasn’t been considered a viable platform for AI applications.</span></p>
5086. <p><span style="font-weight: 400;">Not any more. llamafile has now been optimized for the latest model (the Raspberry Pi 5), and the result is that a number of small LLMs–such as Rocket-3B (</span><a href="https://huggingface.co/jartine/rocket-3B-llamafile/resolve/main/rocket-3b.Q5_K_M.llamafile?download=true"><span style="font-weight: 400;">download</span></a><span style="font-weight: 400;">), TinyLLaMA-1.5B (</span><a href="https://huggingface.co/jartine/TinyLlama-1.1B-Chat-v1.0-GGUF/resolve/main/TinyLlama-1.1B-Chat-v1.0.Q5_K_M.llamafile?download=true"><span style="font-weight: 400;">download</span></a><span style="font-weight: 400;">), and Phi-2 (</span><a href="https://huggingface.co/jartine/phi-2-llamafile/resolve/main/phi-2.Q5_K_M.llamafile?download=true"><span style="font-weight: 400;">download</span></a><span style="font-weight: 400;">)–run at usable speeds on one of the least expensive computers available today. We’ve seen prompt evaluation speeds of </span><a href="https://twitter.com/JustineTunney/status/1776440470152867930"><span style="font-weight: 400;">up to 80 tokens/sec</span></a><span style="font-weight: 400;"> in some cases!</span></p>
5087. <p><b>Keeping up with the latest models</b></p>
5088. <p><span style="font-weight: 400;">The pace of progress in the open model space has been </span><a href="https://twitter.com/maximelabonne/status/1779123021480865807"><span style="font-weight: 400;">stunningly fast</span></a><span style="font-weight: 400;">. Over the past few months, hundreds of models have been released or updated via fine-tuning. Along the way, there has been a clear trend of ever-increasing model performance and ever-smaller model sizes. </span></p>
5089. <p><span style="font-weight: 400;">The llama.cpp project has been doing an excellent job of keeping up with all of these new models, frequently rolling-out support for new architectures and model features within days of their release.</span></p>
5090. <p><span style="font-weight: 400;">For our part we’ve been keeping llamafile closely synced with llama.cpp so that we can support all the same models. Given the complexity of both projects, this has been no small feat, so we’re lucky to have Justine on the case. </span></p>
5091. <p><span style="font-weight: 400;">Today, you can today use the very latest and most capable open models with llamafile thanks to her hard work. For example, we were able to roll-out llamafiles for Meta’s newest LLaMA 3 models–</span><a href="https://huggingface.co/jartine/Meta-Llama-3-8B-Instruct-llamafile"><span style="font-weight: 400;">8B-Instruct</span></a><span style="font-weight: 400;"> and </span><a href="https://huggingface.co/jartine/Meta-Llama-3-70B-Instruct-llamafile"><span style="font-weight: 400;">70B-Instruct</span></a><span style="font-weight: 400;">–within a day of their release. With yesterday’s 0.8 release, llamafile can also run Grok, Mixtral 8x22B, and Command-R.</span></p>
5092. <p><b>Creating your own llamafiles</b></p>
5093. <p><span style="font-weight: 400;">Since the day that llamafile shipped people have wanted to create their own llamafiles. Previously, this required a number of steps, but today you can do it with a single command, e.g.:</span></p>
5094. <p><span style="font-weight: 400;"><code>llamafile-convert [model.gguf]</code></span></p>
5095. <p><span style="font-weight: 400;">In just moments, this will produce a “model.llamafile” file that is ready for immediate use. Our thanks to community member </span><a href="https://github.com/chand1012"><span style="font-weight: 400;">@chan1012</span></a><span style="font-weight: 400;"> for contributing this helpful improvement.</span></p>
5096. <p><span style="font-weight: 400;">In a related development, Hugging Face recently added official support for llamafile within their model hub. This means you can now </span><a href="https://huggingface.co/models?library=llamafile&sort=trending"><span style="font-weight: 400;">search and filter</span></a><span style="font-weight: 400;"> Hugging Face specifically for llamafiles created and distributed by other people in the open source community.</span></p>
5097. <p><b>OpenAI-compatible API server</b></p>
5098. <p><span style="font-weight: 400;">Since it’s built on top of llama.cpp, llamafile inherits that project’s server component, which provides OpenAI-compatible API endpoints. This enables developers who are building on top of OpenAI to switch to using open models instead. At Mozilla we very much want to support this kind of future: one where open-source AI is a viable alternative to centralized, closed, commercial offerings. </span></p>
5099. <p><span style="font-weight: 400;">While open models do not yet fully rival the capabilities of closed models, they’re making rapid progress. We believe that making it easier to pivot existing code over to executing against open models will increase demand and further fuel this progress.</span></p>
5100. <p><span style="font-weight: 400;">Over the past few months, we’ve invested effort in extending these endpoints, both to increase functionality and improve compatibility. Today, llamafile can serve as a drop-in replacement for OpenAI in a wide variety of use cases. </span></p>
5101. <p><span style="font-weight: 400;">We want to further extend our API server’s capabilities, and we’re eager to hear what developers want and need. What’s holding you back from using open models? What features, capabilities, or tools do you need? </span><a href="https://discord.gg/YTgM42NZEr"><span style="font-weight: 400;">Let us know</span></a><span style="font-weight: 400;">!</span></p>
5102. <p><b>Integrations with other open source AI projects</b></p>
5103. <p><span style="font-weight: 400;">Finally, it’s been a delight to see llamafile adopted by independent developers and integrated into leading open source AI projects (like </span><a href="https://github.com/OpenInterpreter/open-interpreter"><span style="font-weight: 400;">Open Interpreter</span></a><span style="font-weight: 400;">). Kudos in particular to our own </span><a href="https://github.com/k8si"><span style="font-weight: 400;">Kate Silverstein</span></a><span style="font-weight: 400;"> who landed PRs that add llamafile support to </span><a href="https://github.com/langchain-ai/langchain"><span style="font-weight: 400;">LangChain</span></a><span style="font-weight: 400;"> and </span><a href="https://github.com/run-llama/llama_index"><span style="font-weight: 400;">LlamaIndex</span></a><span style="font-weight: 400;"> (with </span><a href="https://github.com/Significant-Gravitas/AutoGPT"><span style="font-weight: 400;">AutoGPT</span></a><span style="font-weight: 400;"> coming soon).</span></p>
5104. <p><span style="font-weight: 400;">If you’re a maintainer or contributor to an open source AI project that you feel would benefit from llamafile integration, </span><a href="https://discord.gg/YTgM42NZEr"><span style="font-weight: 400;">let us know how we can help</span></a><span style="font-weight: 400;">.</span></p>
5105. <p><b>Join us!</b></p>
5106. <p><span style="font-weight: 400;">The llamafile project is just getting started, and it’s also only the first step in a major new initiative on Mozilla’s part to contribute to and participate in the open source AI community. We’ll have more to share about that soon, but for now: I invite you to join us on the llamafile project!</span></p>
5107. <p><span style="font-weight: 400;">The best place to connect with both the llamafile team at Mozilla and the overall llamafile community is over at our Discord server, which has </span><a href="https://discord.gg/YTgM42NZEr"><span style="font-weight: 400;">a dedicated channel just for llamafile</span></a><span style="font-weight: 400;">. And of course, your enhancement requests, issues, and PRs are always welcome over at our </span><a href="https://github.com/Mozilla-Ocho/llamafile"><span style="font-weight: 400;">GitHub repo</span></a><span style="font-weight: 400;">.</span></p>
5108. <p><span style="font-weight: 400;">I hope you’ll join us. The next few months are going to be even more interesting and unexpected than the last, both for llamafile and for open source AI itself.</span></p>
5109. <p> </p>
5110. &lt;p&gt;The post &lt;a href=&quot;https://hacks.mozilla.org/2024/04/llamafiles-progress-four-months-in/&quot;&gt;Llamafile’s progress, four months in&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>
5111. <pubDate>Thu, 25 Apr 2024 15:34:08 +0000</pubDate>
5112. <dc:creator>Stephen Hood</dc:creator>
5113. </item>
5114. <item>
5115. <title>This Week In Rust: This Week in Rust 544</title>
5116. <guid isPermaLink="false">tag:this-week-in-rust.org,2024-04-24:/blog/2024/04/24/this-week-in-rust-544/</guid>
5117. <link>https://this-week-in-rust.org/blog/2024/04/24/this-week-in-rust-544/</link>
5118. <description>&lt;p&gt;Hello and welcome to another issue of &lt;em&gt;This Week in Rust&lt;/em&gt;!
5119. <a href="https://www.rust-lang.org/">Rust</a> is a programming language empowering everyone to build reliable and efficient software.
5120. This is a weekly summary of its progress and community.
5121. Want something mentioned? Tag us at <a href="https://twitter.com/ThisWeekInRust">@ThisWeekInRust</a> on Twitter or <a href="https://mastodon.social/@thisweekinrust">@ThisWeekinRust</a> on mastodon.social, or <a href="https://github.com/rust-lang/this-week-in-rust">send us a pull request</a>.
5122. Want to get involved? <a href="https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md">We love contributions</a>.</p>
5123. <p><em>This Week in Rust</em> is openly developed <a href="https://github.com/rust-lang/this-week-in-rust">on GitHub</a> and archives can be viewed at <a href="https://this-week-in-rust.org/">this-week-in-rust.org</a>.
5124. If you find any errors in this week's issue, <a href="https://github.com/rust-lang/this-week-in-rust/pulls">please submit a PR</a>.</p>
5125. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#updates-from-rust-community">Updates from Rust Community</a></h4>
5126.  
5127.  
5128. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#foundation">Foundation</a></h5>
5129. <ul>
5130. <li><a href="https://foundation.rust-lang.org/news/attending-cisas-open-source-software-security-summit/">Guest Blog: Attending CISA’s Open Source Software Security Summit</a></li>
5131. </ul>
5132. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#newsletters">Newsletters</a></h5>
5133. <ul>
5134. <li><a href="https://rust-osdev.com/this-month/2024-03/">This Month in Rust OSDev: March 2024</a></li>
5135. </ul>
5136. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#projecttooling-updates">Project/Tooling Updates</a></h5>
5137. <ul>
5138. <li><a href="https://cliffle.com/blog/lilos-1-0/">lilos v1.0 released</a></li>
5139. <li><a href="https://medium.com/@harshiljani2002/a-parser-in-rust-to-convert-your-medium-blogs-to-markdown-84173a6c1300">medium-to-markdown v0.1.1 : Convert your medium blogs easily into markdown files</a></li>
5140. <li><a href="https://www.fluvio.io/news/this-week-in-fluvio-0060/">Fluvio v0.11.6 release and project updates</a></li>
5141. <li><a href="https://github.com/plabayo/venndb/releases/tag/0.4.0">venndb 0.4.0 - custom validators</a></li>
5142. <li><a href="https://quickwit.io/blog/tantivy-0.22">Tantivy 0.22: Performance improvements, new aggregations and stability fixes</a></li>
5143. <li><a href="https://developerlife.com/2024/04/21/build-async-interactive-cli-apps-in-rust/">Announcing r3bl_terminal_async - build async interactive CLIs in Rust</a></li>
5144. <li>[video] <a href="https://www.youtube.com/watch?v=8PuWu_Pi2sk">Demo + architecture overview of Ferrostar, a cross-platform turn-by-turn navigation SDK with a Rust core</a></li>
5145. </ul>
5146. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#observationsthoughts">Observations/Thoughts</a></h5>
5147. <ul>
5148. <li><a href="https://mcyoung.xyz/2024/04/17/calling-convention/">The Rust Calling Convention We Deserve</a></li>
5149. <li><a href="https://smallcultfollowing.com/babysteps/blog/2024/04/23/dynsized-unsized/">Sized, DynSized, and Unsized</a></li>
5150. <li><a href="https://without.boats/blog/coroutines-and-effects/">Coroutines and effects</a></li>
5151. <li><a href="https://hacks.mozilla.org/2024/04/porting-a-cross-platform-gui-application-to-rust/">Porting a cross-platform GUI application to Rust</a></li>
5152. <li><a href="https://blog.thunderbird.net/2024/04/adventures-in-rust-bringing-exchange-support-to-thunderbird/">Adventures In Rust: Bringing Exchange Support To Thunderbird</a></li>
5153. </ul>
5154. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust-walkthroughs">Rust Walkthroughs</a></h5>
5155. <ul>
5156. <li><a href="https://bencher.dev/learn/engineering/sqlite-performance-tuning/">Why SQLite Performance Tuning made Bencher 1200x Faster</a></li>
5157. <li><a href="https://rust.code-maven.com/drop-the-destructor-of-rust-structs">drop, the destructor of Rust structs</a></li>
5158. <li><a href="https://www.shuttle.rs/blog/2024/04/17/using-aws-s3-rust">Building with AWS S3 using Rust</a></li>
5159. <li><a href="https://cybernetist.com/2024/04/19/rust-tokio-task-cancellation-patterns/">Rust tokio task cancellation patterns</a></li>
5160. <li>[video] <a href="https://www.youtube.com/watch?v=X5wDVaZENOo">Build with Naz - Published crate r3bl_terminal_async for building async interactive CLIs in Rust</a></li>
5161. <li>[video] <a href="https://www.youtube.com/watch?v=ocacUsyJXpg">Trent Billington - Bevy ECS - Power tool for data oriented applications</a></li>
5162. <li>[video] <a href="https://www.youtube.com/watch?v=BxxUPdiBjkc">Building a procedural art generator</a></li>
5163. <li>[audio] <a href="https://rustacean-station.org/episode/robert-balicki/">Isograph with Robert Balicki</a></li>
5164. </ul>
5165. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#research">Research</a></h5>
5166. <ul>
5167. <li><a href="https://arxiv.org/abs/2404.11671">A Study of Undefined Behavior Across Foreign Function Boundaries in Rust Libraries</a></li>
5168. <li><a href="https://rust-digger.code-maven.com/news/biggest-crates-is-450-megabyte">Rust Digger: Does size matter? The biggest crate is 450MB; More than 100 crates are over 50MB</a></li>
5169. </ul>
5170. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#miscellaneous">Miscellaneous</a></h5>
5171. <ul>
5172. <li><a href="https://dev.to/szabgab/github-sponsor-rust-developer-david-tolnay-53kc">GitHub Sponsor Rust developer David Tolnay</a></li>
5173. <li><a href="https://app.codecrafters.io/concepts/rust-tcp-server">Learn how to write TCP servers using Rust's std::net module</a></li>
5174. <li><a href="https://rustfest.ch/posts/2024-04-23/the-cfp-has-concluded/">RustFest Zürich 🇨 Talks announced</a></li>
5175. </ul>
5176. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#crate-of-the-week">Crate of the Week</a></h4>
5177. <p>This week's crate is <a href="https://crates.io/crates/scandir">scandir</a>, a high-performance file tree scanner.</p>
5178. <p>Thanks to <a href="https://users.rust-lang.org/t/crate-of-the-week/2704/1305">Marty B.</a> for the self-suggestion!</p>
5179. <p><a href="https://users.rust-lang.org/t/crate-of-the-week/2704">Please submit your suggestions and votes for next week</a>!</p>
5180. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#call-for-testing">Call for Testing</a></h4>
5181. <p>An important step for RFC implementation is for people to experiment with the
5182. implementation and give feedback, especially before stabilization.  The following
5183. RFCs would benefit from user testing before moving forward:</p>
5184. <ul>
5185. <li><em>No calls for testing were issued this week.</em></li>
5186. </ul>
5187. <p>If you are a feature implementer and would like your RFC to appear on the above list, add the new <code>call-for-testing</code>
5188. label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
5189. need testing.</p>
5190. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#call-for-participation-projects-and-speakers">Call for Participation; projects and speakers</a></h4>
5191. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#cfp-projects">CFP - Projects</a></h5>
5192. <p>Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!</p>
5193. <p>Some of these tasks may also have mentors available, visit the task page for more information.</p>
5194. <ul>
5195. <li><a href="https://github.com/TaKO8Ki/awesome-alternatives-in-rust/pull/124">awesome-alternatives-in-rust - Add <code>dqy</code> alternative to <code>dig</code></a></li>
5196. <li><a href="https://github.com/infinyon/fluvio/issues/3836">fluvio - When a topic is deleted, connected clients should have their connection closed</a></li>
5197. <li><a href="https://github.com/infinyon/fluvio/issues/3825">fluvio - MQTT Connector: Prefix auto generated Client ID to prevent connection drops</a></li>
5198. <li><a href="https://github.com/infinyon/fluvio/issues/3866">fluvio - Remove localhost from fluvio in favor of 127.0.0.1</a></li>
5199. </ul>
5200. <p>If you are a Rust project owner and are looking for contributors, please submit tasks <a href="https://users.rust-lang.org/t/twir-call-for-participation/4821">here</a>.</p>
5201. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#cfp-speakers">CFP - Speakers</a></h5>
5202. <p>Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.</p>
5203. <ul>
5204. <li><a href="https://foundation.rust-lang.org/news/the-rustconf-2024-call-for-talk-proposals-is-open/">RustConf 2024</a> | Closes 2024-04-25 | Montreal, Canada | Event date: 2024-09-10</li>
5205. <li><a href="https://sessionize.com/rustlab-2024">RustLab 2024</a> | Closes 2024-05-01 | Florence, Italy | Event date: 2024-11-09 - 2024-11-11</li>
5206. <li><a href="https://www.papercall.io/eurorust-2024">EuroRust 2024</a>| Closes 2024-06-03 | Vienna, Austria & online | Event date: 2024-10-10</li>
5207. <li><a href="https://scientificcomputing.rs/">Scientific Computing in Rust 2024</a>| Closes 2024-06-14 | online | Event date: 2024-07-17 - 2024-07-19</li>
5208. <li><a href="https://www.papercall.io/conf42-rustlang-2024">Conf42 Rustlang 2024</a> | Closes 2024-07-22 | online | Event date: 2024-08-22</li>
5209. </ul>
5210. <p>If you are an event organizer hoping to expand the reach of your event, please submit a link to the submission website through a <a href="https://github.com/rust-lang/this-week-in-rust">PR to TWiR</a>.</p>
5211. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#updates-from-the-rust-project">Updates from the Rust Project</a></h4>
5212. <p>432 pull requests were <a href="https://github.com/search?q=is%3Apr+org%3Arust-lang+is%3Amerged+merged%3A2024-04-16..2024-04-23">merged in the last week</a></p>
5213. <ul>
5214. <li><a href="https://github.com/rust-lang/rust/pull/121801">add simple async drop glue generation</a></li>
5215. <li><a href="https://github.com/rust-lang/rust/pull/124178">llvm backend: Prevent creating the same <code>Instance::mono</code> multiple times</a></li>
5216. <li><a href="https://github.com/rust-lang/rust/pull/123967"><code>static_mut_refs</code>: use raw pointers to remove the remaining FIXME</a></li>
5217. <li><a href="https://github.com/rust-lang/rust/pull/122013">add a lower bound check to <code>unicode-table-generator</code> output</a></li>
5218. <li><a href="https://github.com/rust-lang/rust/pull/123980">add an opt-in to store incoming edges in <code>VecGraph</code> + misc</a></li>
5219. <li><a href="https://github.com/rust-lang/rust/pull/124071">add llvm-bitcode-linker to build manifest</a></li>
5220. <li><a href="https://github.com/rust-lang/rust/pull/124023">allow workproducts without object files</a></li>
5221. <li><a href="https://github.com/rust-lang/rust/pull/123949">at debuginfo=0, don't inline debuginfo when inlining</a></li>
5222. <li><a href="https://github.com/rust-lang/rust/pull/123571">correctly change type when adding adjustments on top of <code>NeverToAny</code></a></li>
5223. <li><a href="https://github.com/rust-lang/rust/pull/124053">coverage: branch coverage tests for lazy boolean operators</a></li>
5224. <li><a href="https://github.com/rust-lang/rust/pull/124217">coverage: prepare for improved branch coverage</a></li>
5225. <li><a href="https://github.com/rust-lang/rust/pull/122684">delay interning errors to after validation</a></li>
5226. <li><a href="https://github.com/rust-lang/rust/pull/123997">delay span bug when <code>Self</code> kw resolves to <code>DefKind::{Mod,Trait}</code></a></li>
5227. <li><a href="https://github.com/rust-lang/rust/pull/123673">don't ICE for kind mismatches during error rendering</a></li>
5228. <li><a href="https://github.com/rust-lang/rust/pull/124037">don't ascend into parent bodies when collecting stmts for possible return suggestion</a></li>
5229. <li><a href="https://github.com/rust-lang/rust/pull/124066">don't error on subtyping of equal types</a></li>
5230. <li><a href="https://github.com/rust-lang/rust/pull/123935">don't inline integer literals when they overflow - new attempt</a></li>
5231. <li><a href="https://github.com/rust-lang/rust/pull/124106">don't repeatedly duplicate TAIT lifetimes for each subsequently nested TAIT</a></li>
5232. <li><a href="https://github.com/rust-lang/rust/pull/123491">fix ICE in <code>eval_body_using_ecx</code></a></li>
5233. <li><a href="https://github.com/rust-lang/rust/pull/124112">fix ICE when there is a non-Unicode entry in the incremental crate directory</a></li>
5234. <li><a href="https://github.com/rust-lang/rust/pull/124104">fix capturing duplicated lifetimes via parent in <code>precise_captures</code> (<code>impl use<'...></code>)</a></li>
5235. <li><a href="https://github.com/rust-lang/rust/pull/124203">fix normalizing in different <code>ParamEnv</code>s with the same InferCtxt</a></li>
5236. <li><a href="https://github.com/rust-lang/rust/pull/123594">fix trait solver overflow with <code>non_local_definitions</code> lint</a></li>
5237. <li><a href="https://github.com/rust-lang/rust/pull/124198">flip spans for precise capturing syntax not capturing a ty/const param, and for implicit captures of lifetime params</a></li>
5238. <li><a href="https://github.com/rust-lang/rust/pull/124191">give a name to each distinct manipulation of pretty-printer FixupContext</a></li>
5239. <li><a href="https://github.com/rust-lang/rust/pull/115120">ignore <code>-C strip</code> on MSVC</a></li>
5240. <li><a href="https://github.com/rust-lang/rust/pull/123409">implement Modified Condition/Decision Coverage</a></li>
5241. <li><a href="https://github.com/rust-lang/rust/pull/115253">implement <code>PROBLEMATIC_CONSTS</code> generalization</a></li>
5242. <li><a href="https://github.com/rust-lang/rust/pull/123468">implement syntax for <code>impl Trait</code> to specify its captures explicitly (<code>feature(precise_capturing)</code>)</a></li>
5243. <li><a href="https://github.com/rust-lang/rust/pull/124252">improve ICE message for forbidden dep-graph reads</a></li>
5244. <li><a href="https://github.com/rust-lang/rust/pull/124030">interpret: pass MemoryKind to <code>adjust_alloc_base_pointer</code></a></li>
5245. <li><a href="https://github.com/rust-lang/rust/pull/124018">interpret: pass MemoryKind to <code>before_memory_deallocation</code></a></li>
5246. <li><a href="https://github.com/rust-lang/rust/pull/124113">interpret: use ScalarInt for bin-ops; avoid PartialOrd for ScalarInt</a></li>
5247. <li><a href="https://github.com/rust-lang/rust/pull/117919">introduce perma-unstable <code>wasm-c-abi</code> flag</a></li>
5248. <li><a href="https://github.com/rust-lang/rust/pull/124166">let inherent associated types constrain opaque types during projection</a></li>
5249. <li><a href="https://github.com/rust-lang/rust/pull/123990">make <code>suggest_deref_closure_return</code> more idiomatic/easier to understand</a></li>
5250. <li><a href="https://github.com/rust-lang/rust/pull/123995">make <code>thir_tree</code> and <code>thir_flat</code> into hooks</a></li>
5251. <li><a href="https://github.com/rust-lang/rust/pull/124052">make the comments for <code>ReturnDest</code> variants doc comments</a></li>
5252. <li><a href="https://github.com/rust-lang/rust/pull/123512">match ergonomics 2024: Implement eat-one-layer</a></li>
5253. <li><a href="https://github.com/rust-lang/rust/pull/123535">match ergonomics 2024: <code>mut</code> doesn't reset binding mode</a></li>
5254. <li><a href="https://github.com/rust-lang/rust/pull/124137">match hyphen in multi-revision comment matchers</a></li>
5255. <li><a href="https://github.com/rust-lang/rust/pull/123998">opaque types have no namespace</a></li>
5256. <li><a href="https://github.com/rust-lang/rust/pull/124016">outline default query and hook provider function implementations</a></li>
5257. <li><a href="https://github.com/rust-lang/rust/pull/124027">prefer identity equality over equating types during coercion</a></li>
5258. <li><a href="https://github.com/rust-lang/rust/pull/123379">print note with closure signature on type mismatch</a></li>
5259. <li><a href="https://github.com/rust-lang/rust/pull/123752">properly handle emojis as literal prefix in macros</a></li>
5260. <li><a href="https://github.com/rust-lang/rust/pull/124036">remove <code>default_hidden_visibility: false</code> from wasm targets</a></li>
5261. <li><a href="https://github.com/rust-lang/rust/pull/123859">remove uneeded clones now that TrustedStep implies Copy</a></li>
5262. <li><a href="https://github.com/rust-lang/rust/pull/123674">silence some follow-up errors on trait impls in case the trait has conflicting or otherwise incoherent impls</a></li>
5263. <li><a href="https://github.com/rust-lang/rust/pull/123537">simplify shallow resolver to just fold ty/consts</a></li>
5264. <li><a href="https://github.com/rust-lang/rust/pull/124183">stop taking <code>ParamTy</code>/<code>ParamConst</code>/<code>EarlyParamRegion</code>/<code>AliasTy</code> by ref</a></li>
5265. <li><a href="https://github.com/rust-lang/rust/pull/123979">subtype predicates only exist on inference types, so we can allow them to register opaque types within them</a></li>
5266. <li><a href="https://github.com/rust-lang/rust/pull/123930">tell LLVM <code>Vec::len</code> is invariant across growth</a></li>
5267. <li><a href="https://github.com/rust-lang/rust/pull/124019">use raw-dylib for Windows synchronization functions</a></li>
5268. <li><a href="https://github.com/rust-lang/rust/pull/122883">refactor clippy in bootstrap</a></li>
5269. <li><a href="https://github.com/rust-lang/rust/pull/124116">when suggesting <code>RUST_BACKTRACE=1,</code> add a special note for Miri's env var isolation</a></li>
5270. <li><a href="https://github.com/rust-lang/miri/pull/3495">miri: <code>data_race</code>: make the release/acquire API more clear</a></li>
5271. <li><a href="https://github.com/rust-lang/miri/pull/3477">miri: <code>no_std</code> works on Windows now</a></li>
5272. <li><a href="https://github.com/rust-lang/miri/pull/3461">miri: add <code>localtime_r</code> shim</a></li>
5273. <li><a href="https://github.com/rust-lang/miri/pull/3475">miri: address reuse improvements and fixes</a></li>
5274. <li><a href="https://github.com/rust-lang/miri/pull/3472">miri: deadlock: show backtrace for all threads</a></li>
5275. <li><a href="https://github.com/rust-lang/miri/pull/3480">miri: directly call <code>handle_alloc_error</code></a></li>
5276. <li><a href="https://github.com/rust-lang/miri/pull/3478">miri: implement support for <code>__rust_alloc_error_handler</code></a></li>
5277. <li><a href="https://github.com/rust-lang/miri/pull/3484">miri: make realloc with a size of zero fail</a></li>
5278. <li><a href="https://github.com/rust-lang/miri/pull/3485">miri: move <code>read_byte_slice</code> to general helpers file, next to <code>read_c_str</code></a></li>
5279. <li><a href="https://github.com/rust-lang/miri/pull/3471">miri: threads: keep track of why we are blocked, and sanity-check that when waking up</a></li>
5280. <li><a href="https://github.com/rust-lang/rust/pull/124013"><code>Box::into_raw</code>: make Miri understand that this is a box-to-raw cast</a></li>
5281. <li><a href="https://github.com/rust-lang/rust/pull/124190"><code>PatRangeBoundary::compare_with</code>: also add a fast-path for signed integers</a></li>
5282. <li><a href="https://github.com/rust-lang/rust/pull/123936">codegen ZSTs without an allocation</a></li>
5283. <li><a href="https://github.com/rust-lang/rust/pull/117457">stabilize Wasm target features that are in phase 4 and 5</a></li>
5284. <li><a href="https://github.com/rust-lang/rust/pull/124049">stabilize <code>const_io_structs</code></a></li>
5285. <li><a href="https://github.com/rust-lang/rust/pull/123501">stabilize checking of cfgs at compile-time: <code>--check-cfg</code> option</a></li>
5286. <li><a href="https://github.com/rust-lang/rust/pull/124230">stabilize generic <code>NonZero</code></a></li>
5287. <li><a href="https://github.com/rust-lang/rust/pull/124114">make <code>checked</code> ops emit <em>unchecked</em> LLVM operations where feasible</a></li>
5288. <li><a href="https://github.com/rust-lang/rust/pull/124103">improve <code>std::fs::Metadata</code> Debug representation</a></li>
5289. <li><a href="https://github.com/rust-lang/rust/pull/124110">fix negating <code>f16</code> and <code>f128</code> constants</a></li>
5290. <li><a href="https://github.com/rust-lang/rust/pull/123406">force exhaustion in <code>iter::ArrayChunks::into_remainder</code></a></li>
5291. <li><a href="https://github.com/rust-lang/rust/pull/115913"><code>checked_ilog</code>: improve performance</a></li>
5292. <li><a href="https://github.com/rust-lang/rust/pull/123840">add an intrinsic for <code>ptr::from_raw_parts(_mut)</code></a></li>
5293. <li><a href="https://github.com/rust-lang/rust/pull/124100">fix: make <code>str::from_raw_parts_mut mut</code></a></li>
5294. <li><a href="https://github.com/rust-lang/rust/pull/123811">use queue-based <code>RwLock</code> on more platforms</a></li>
5295. <li><a href="https://github.com/rust-lang/rust/pull/123144">add support for Arm64EC to the standard library</a></li>
5296. <li><a href="https://github.com/rust-lang/rustc_codegen_gcc/pull/498">codegen_gcc: fix <code>PassMode::Indirect</code> with params</a></li>
5297. <li><a href="https://github.com/rust-lang/rustc_codegen_gcc/pull/497">codegen_gcc: fix check for main function already declared</a></li>
5298. <li><a href="https://github.com/rust-lang/rustc_codegen_gcc/pull/499">codegen_gcc: fix panic when calling <code>get_fn</code> for a variable</a></li>
5299. <li><a href="https://github.com/rust-lang/rustc_codegen_gcc/pull/493">codegen_gcc: fix passing custom <code>CG_RUSTFLAGS</code> when building sysroot</a></li>
5300. <li><a href="https://github.com/rust-lang/rustc_codegen_gcc/pull/500">codegen_gcc: implement more type kinds</a></li>
5301. <li><a href="https://github.com/rust-lang/cargo/pull/13764">cargo install: including Locking message</a></li>
5302. <li><a href="https://github.com/rust-lang/cargo/pull/13785">cargo resolver: add default Edition2024 to resolver v3</a></li>
5303. <li><a href="https://github.com/rust-lang/cargo/pull/13776">cargo resolver: add v3 resolver for MSRV-aware resolving</a></li>
5304. <li><a href="https://github.com/rust-lang/cargo/pull/13770">cargo credential: trim newlines in tokens from stdin</a></li>
5305. <li><a href="https://github.com/rust-lang/cargo/pull/13771">cargo msrv: error, rather than panic, on rust-version 'x'</a></li>
5306. <li><a href="https://github.com/rust-lang/cargo/pull/13769">cargo msrv: put MSRV-aware resolver behind a config</a></li>
5307. <li><a href="https://github.com/rust-lang/cargo/pull/13780">cargo toml: don't crash on parse errors that point to multi-byte character</a></li>
5308. <li><a href="https://github.com/rust-lang/cargo/pull/13775">cargo toml: disallow source-less dependencies</a></li>
5309. <li><a href="https://github.com/rust-lang/cargo/pull/13747">cargo toml: error on <code>[project]</code> in Edition 2024</a></li>
5310. <li><a href="https://github.com/rust-lang/cargo/pull/13783">cargo toml: report <code>_</code>fied variants (e.g. <code>dev_dependencies</code>) as deprecated</a></li>
5311. <li><a href="https://github.com/rust-lang/cargo/pull/13777">cargo: fix 'cargo build' fails when <code>list_files()</code> with gix is triggered</a></li>
5312. <li><a href="https://github.com/rust-lang/rust/pull/118441">rustdoc: always display stability version even if it's the same as the containing item</a></li>
5313. <li><a href="https://github.com/rust-lang/rust/pull/124041">rustdoc: fix copy path button</a></li>
5314. <li><a href="https://github.com/rust-lang/rust/pull/123355">rustdoc: support type '/' to search</a></li>
5315. <li><a href="https://github.com/rust-lang/rust/pull/124149">rustdoc-search: fix description on aliases in results</a></li>
5316. <li><a href="https://github.com/rust-lang/rust/pull/119912">rustdoc-search: single result for items with multiple paths</a></li>
5317. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12685">clippy: <code>threadlocal_initializer_can_be_made_const</code> will not trigger for unreachable initializers</a></li>
5318. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12692">clippy: <code>arithmetic_side_effects</code> fix false negative on <code>+=</code></a></li>
5319. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12673">clippy: <code>ptr_as_ptr</code>: fix duplicate diagnostics</a></li>
5320. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12693">clippy: emit the <code>needless_pass_by_ref_mut</code> lint on <code>self</code> arguments as well</a></li>
5321. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12696">clippy: fix <code>is_test_module_or_function</code></a></li>
5322. <li><a href="https://github.com/rust-lang/rust-clippy/pull/11852">clippy: reduce <code>single_char_pattern</code> to only lint on ascii chars</a></li>
5323. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12691">clippy: rework interior mutability detection</a></li>
5324. <li><a href="https://github.com/rust-lang/rust-clippy/pull/12682">clippy: the <code>multiple_unsafe_ops_per_block</code> test needs <code>asm!</code></a></li>
5325. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17110">rust-analyzer: cargo script mvp</a></li>
5326. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17094">rust-analyzer: add convert From to TryFrom assist</a></li>
5327. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17118">rust-analyzer: allow rust files to be used linkedProjects</a></li>
5328. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17093">rust-analyzer: VFS should not walk circular symlinks</a></li>
5329. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17024">rust-analyzer: handle escaped chars in doc comments</a></li>
5330. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17055">rust-analyzer: replace Just the variable name in Unused Variable Diagnostic Fix</a></li>
5331. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/16938">rust-analyzer: implement <code>BeginPanic</code> handling in const eval</a></li>
5332. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17105">rust-analyzer: make test harness arguments configurable and not <code>--nocapture</code></a></li>
5333. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/16057">rust-analyzer: render matched macro arm on hover of macro calls</a></li>
5334. <li><a href="https://github.com/rust-lang/rust-analyzer/pull/17115">rust-analyzer: try to generate more meaningful names in json converter</a></li>
5335. </ul>
5336. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust-compiler-performance-triage">Rust Compiler Performance Triage</a></h5>
5337. <p>A week dominated by small mixed changes to perf with improvements slightly outweighing regressions. There were no pure regressions, and many of the mixed perf results were deemed worth it for their potential improvements to runtime performance through further optimization from LLVM.</p>
5338. <p>Triage done by <strong>@rylev</strong>.
5339. Revision range: <a href="https://perf.rust-lang.org/?start=ccfcd950b333fed046275dd8d54fe736ca498aa7&end=a77f76e26302e9a084fb321817675b1dfc1dcd63&absolute=false&stat=instructions%3Au">ccfcd950..a77f76e2</a></p>
5340. <p><strong>Summary</strong>:</p>
5341. <table>
5342. <thead>
5343. <tr>
5344. <th align="center">(instructions:u)</th>
5345. <th align="center">mean</th>
5346. <th align="center">range</th>
5347. <th align="center">count</th>
5348. </tr>
5349. </thead>
5350. <tbody>
5351. <tr>
5352. <td align="center">Regressions ❌ <br /> (primary)</td>
5353. <td align="center">0.4%</td>
5354. <td align="center">[0.2%, 1.8%]</td>
5355. <td align="center">57</td>
5356. </tr>
5357. <tr>
5358. <td align="center">Regressions ❌ <br /> (secondary)</td>
5359. <td align="center">0.4%</td>
5360. <td align="center">[0.2%, 1.9%]</td>
5361. <td align="center">26</td>
5362. </tr>
5363. <tr>
5364. <td align="center">Improvements ✅ <br /> (primary)</td>
5365. <td align="center">-0.8%</td>
5366. <td align="center">[-3.4%, -0.2%]</td>
5367. <td align="center">50</td>
5368. </tr>
5369. <tr>
5370. <td align="center">Improvements ✅ <br /> (secondary)</td>
5371. <td align="center">-0.6%</td>
5372. <td align="center">[-1.9%, -0.1%]</td>
5373. <td align="center">32</td>
5374. </tr>
5375. <tr>
5376. <td align="center">All ❌✅ (primary)</td>
5377. <td align="center">-0.2%</td>
5378. <td align="center">[-3.4%, 1.8%]</td>
5379. <td align="center">107</td>
5380. </tr>
5381. </tbody>
5382. </table>
5383. <p>0 Regressions, 5 Improvements, 6 Mixed; 2 of them in rollups
5384. 62 artifact comparisons made in total</p>
5385. <p><a href="https://github.com/rust-lang/rustc-perf/blob/e29814aa8d206406ae2711773bd882b39598a9d8/triage/2024-04-23.md">Full report here</a></p>
5386. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#approved-rfcs"></a><a href="https://github.com/rust-lang/rfcs/commits/master">Approved RFCs</a></h5>
5387. <p>Changes to Rust follow the Rust <a href="https://github.com/rust-lang/rfcs#rust-rfcs">RFC (request for comments) process</a>. These
5388. are the RFCs that were approved for implementation this week:</p>
5389. <ul>
5390. <li><em>No RFCs were approved this week.</em></li>
5391. </ul>
5392. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#final-comment-period">Final Comment Period</a></h5>
5393. <p>Every week, <a href="https://www.rust-lang.org/team.html">the team</a> announces the 'final comment period' for RFCs and key PRs
5394. which are reaching a decision. Express your opinions now.</p>
5395. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#rfcs"></a><a href="https://github.com/rust-lang/rfcs/labels/final-comment-period">RFCs</a></h6>
5396. <ul>
5397. <li>[disposition: merge] <a href="https://github.com/rust-lang/rfcs/pull/3614">experimental project goal program for 2024 H2</a></li>
5398. </ul>
5399. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#tracking-issues-prs">Tracking Issues & PRs</a></h6>
5400. <a class="toclink" href="http://this-week-in-rust.org/atom.xml#rust"></a><a href="https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc">Rust</a>
5401. <ul>
5402. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/issues/92750">Tracking Issue for <code>std::path::absolute</code></a></li>
5403. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/issues/117691">Tracking Issue for convenience methods on <code>NonNull</code></a></li>
5404. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/123734">Inline more svg images into CSS</a></li>
5405. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/pull/123508">Edition 2024: Make <code>!</code> fall back to <code>!</code></a></li>
5406. <li>[disposition: merge] <a href="https://github.com/rust-lang/rust/issues/123060">static_mut_refs: Should the lint cover hidden references?</a></li>
5407. </ul>
5408. <a class="toclink" href="http://this-week-in-rust.org/atom.xml#cargo"></a><a href="https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc">Cargo</a>
5409. <ul>
5410. <li>[disposition: merge] <a href="https://github.com/rust-lang/cargo/pull/13713">fix(toml): Warn, rather than fail publish, if a target is excluded</a></li>
5411. </ul>
5412. <h6><a class="toclink" href="http://this-week-in-rust.org/atom.xml#new-and-updated-rfcs"></a><a href="https://github.com/rust-lang/rfcs/pulls">New and Updated RFCs</a></h6>
5413. <ul>
5414. <li>[new] <a href="https://github.com/rust-lang/rfcs/pull/3614">experimental project goal program for 2024 H2</a></li>
5415. </ul>
5416. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#upcoming-events">Upcoming Events</a></h4>
5417. <p>Rusty Events between 2024-04-24 - 2024-05-22 🦀</p>
5418. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#virtual">Virtual</a></h5>
5419. <ul>
5420. <li>2024-04-24 | Virtual + In Person (Prague, CZ) | <a href="https://www.meetup.com/rust-czech-republic/">Rust Czech Republic</a><ul>
5421. <li><a href="https://www.meetup.com/rust-czech-republic/events/300388563"><strong>#2: Making Safe Rust Safer (Pavel Šimerda)</strong></a></li>
5422. </ul>
5423. </li>
5424. <li>2024-04-25 | Virtual (Berlin, DE) | <a href="https://berline.rs/">OpenTechSchool Berlin</a> + <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
5425. <li><a href="https://meet.jit.si/RustHackAndLearnBerlin"><strong>Rust Hack and Learn</strong></a> | <a href="https://www.meetup.com/rust-berlin/events/298477692/"><strong>Mirror: Rust Hack n Learn Meetup</strong></a></li>
5426. </ul>
5427. </li>
5428. <li>2024-04-30 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/">Dallas Rust</a><ul>
5429. <li><a href="https://www.meetup.com/dallasrust/events/mvdtgtygcgbnc/"><strong>Last Tuesday</strong></a></li>
5430. </ul>
5431. </li>
5432. <li>2024-05-01 | Virtual (Cardiff, UK) | <a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/">Rust and C++ Cardiff</a><ul>
5433. <li><a href="https://www.meetup.com/rust-and-c-plus-plus-in-cardiff/events/300325526/"><strong>Rust for Rustaceans Book Club: Chapter 5 - Project Structure</strong></a></li>
5434. </ul>
5435. </li>
5436. <li>2024-05-01 | Virtual (Indianapolis, IN, US) | <a href="https://www.meetup.com/indyrs/">Indy Rust</a><ul>
5437. <li><a href="https://www.meetup.com/indyrs/events/299047895/"><strong>Indy.rs - with Social Distancing</strong></a></li>
5438. </ul>
5439. </li>
5440. <li>2024-05-02 | Virtual (Charlottesville, NC, US) | <a href="https://www.meetup.com/charlottesville-rust-meetup/">Charlottesville Rust Meetup</a><ul>
5441. <li><a href="https://www.meetup.com/charlottesville-rust-meetup/events/298368804/"><strong>Crafting Interpreters in Rust Collaboratively</strong></a></li>
5442. </ul>
5443. </li>
5444. <li>2024-05-07 | Virtual (Buffalo, NY) | <a href="https://www.meetup.com/buffalo-rust-meetup/">Buffalo Rust Meetup</a><ul>
5445. <li><a href="https://www.meetup.com/buffalo-rust-meetup/events/300100279/"><strong>Buffalo Rust User Group</strong></a></li>
5446. </ul>
5447. </li>
5448. <li>2024-05-09 | Virtual (Berlin, DE) | <a href="https://berline.rs/">OpenTechSchool Berlin</a> + <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
5449. <li><a href="https://meet.jit.si/RustHackAndLearnBerlin"><strong>Rust Hack and Learn</strong></a> | <a href="https://www.meetup.com/rust-berlin/events/298477697/"><strong>Mirror: Rust Hack n Learn Meetup</strong></a></li>
5450. </ul>
5451. </li>
5452. <li>2024-05-09 | Virtual (Israel) | <a href="https://rust.org.il/">Rust in Israel</a><ul>
5453. <li><a href="https://www.meetup.com/code-mavens/events/300144781/"><strong>Rust at Microsoft, Tel Aviv - Are we embedded yet?</strong></a></li>
5454. </ul>
5455. </li>
5456. <li>2024-05-09 | Virtual (Nuremberg/Nürnberg, DE) | <a href="https://www.meetup.com/rust-noris/">Rust Nuremberg</a><ul>
5457. <li><a href="https://www.meetup.com/rust-noris/events/297945257/"><strong>Rust Nürnberg online</strong></a></li>
5458. </ul>
5459. </li>
5460. <li>2024-05-14 | Virtual (Dallas, TX, US) | <a href="https://www.meetup.com/dallasrust/">Dallas Rust</a><ul>
5461. <li><a href="https://www.meetup.com/dallasrust/events/298341699/"><strong>Second Tuesday</strong></a></li>
5462. </ul>
5463. </li>
5464. <li>2024-05-14 | Virtual (Halifax, NS, CA) | <a href="https://www.meetup.com/rust-tell-halifax/">Rust Halifax</a><ul>
5465. <li><a href="https://www.meetup.com/rust-tell-halifax/events/300437775/"><strong>Rust&Tell - Halifax</strong></a></li>
5466. </ul>
5467. </li>
5468. <li>2024-05-14 | Virtual + In-Person (München/Munich, DE) | <a href="https://www.meetup.com/rust-munich/">Rust Munich</a><ul>
5469. <li><a href="https://www.meetup.com/rust-munich/events/298507657/"><strong>Rust Munich 2024 / 1 - hybrid (Rescheduled)</strong></a></li>
5470. </ul>
5471. </li>
5472. <li>2024-05-15 | Virtual (Vancouver, BC, CA) | <a href="https://www.meetup.com/vancouver-rust/">Vancouver Rust</a><ul>
5473. <li><a href="https://www.meetup.com/vancouver-rust/events/298542323/"><strong>Rust Study/Hack/Hang-out</strong></a></li>
5474. </ul>
5475. </li>
5476. <li>2024-05-16 | Virtual (Charlottesville, VA, US) | <a href="https://www.meetup.com/charlottesville-rust-meetup/">Charlottesville Rust Meetup</a><ul>
5477. <li><a href="https://www.meetup.com/charlottesville-rust-meetup/events/298312423/"><strong>Crafting Interpreters in Rust Collaboratively</strong></a></li>
5478. </ul>
5479. </li>
5480. <li>2024-05-21 | Virtual (Washington, DC, US) | <a href="https://www.meetup.com/rustdc/">Rust DC</a><ul>
5481. <li><a href="https://www.meetup.com/rustdc/events/299346490/"><strong>Mid-month Rustful—forensic parsing via Artemis</strong></a></li>
5482. </ul>
5483. </li>
5484. </ul>
5485. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#africa">Africa</a></h5>
5486. <ul>
5487. <li>2024-05-04 | Kampala, UG | <a href="https://www.eventbrite.com/o/rust-circle-kampala-65249289033">Rust Circle Kampala</a><ul>
5488. <li><a href="https://www.eventbrite.com/e/rust-circle-meetup-tickets-628763176587?aff=ebdsoporgprofile"><strong>Rust Circle Meetup</strong></a></li>
5489. </ul>
5490. </li>
5491. </ul>
5492. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#asia">Asia</a></h5>
5493. <ul>
5494. <li>2024-05-11 | Bangalore, IN | <a href="https://hasgeek.com/rustbangalore">Rust Bangalore</a><ul>
5495. <li><a href="https://hasgeek.com/rustbangalore/may-2024-rustacean-meetup/"><strong>May 2024 Rustacean meetup</strong></a></li>
5496. </ul>
5497. </li>
5498. </ul>
5499. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#europe">Europe</a></h5>
5500. <ul>
5501. <li>2024-04-24 | Virtual + In Person (Prague, CZ) | <a href="https://www.meetup.com/rust-czech-republic/">Rust Czech Republic</a><ul>
5502. <li><a href="https://www.meetup.com/rust-czech-republic/events/300388563"><strong>#2: Making Safe Rust Safer (Pavel Šimerda)</strong></a></li>
5503. </ul>
5504. </li>
5505. <li>2024-04-25 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus/">Rust Aarhus</a><ul>
5506. <li><a href="https://www.meetup.com/rust-aarhus/events/299564517/"><strong>Talk Night at MFT Energy</strong></a></li>
5507. </ul>
5508. </li>
5509. <li>2024-04-25 | Berlin, DE | <a href="https://www.meetup.com/rust-berlin/">Rust Berlin</a><ul>
5510. <li><a href="https://www.meetup.com/rust-berlin/events/299288960/"><strong>Rust and Tell - TBD</strong></a></li>
5511. </ul>
5512. </li>
5513. <li>2024-04-25 | København/Copenhagen, DK | <a href="https://www.meetup.com/copenhagen-rust-community/">Copenhagen Rust Community</a><ul>
5514. <li><a href="https://www.meetup.com/copenhagen-rust-community/events/300458178/"><strong>Rust meetup #46 sponsored by Nine A/S</strong></a></li>
5515. </ul>
5516. </li>
5517. <li>2024-04-25 | Vienna, AT | <a href="https://www.meetup.com/rust-vienna/">Rust Vienna</a><ul>
5518. <li><a href="https://www.meetup.com/rust-vienna/events/300389154/"><strong>Rust Vienna x Python User Group - April</strong></a></li>
5519. </ul>
5520. </li>
5521. <li>2024-04-27 | Basel, CH | <a href="https://www.meetup.com/rust-basel/">Rust Basel</a><ul>
5522. <li><a href="https://www.meetup.com/rust-basel/events/299933581/"><strong>Fullstack Rust - Workshop #2 (Register by 23 April)</strong></a></li>
5523. </ul>
5524. </li>
5525. <li>2024-04-27 | Stockholm, SE | <a href="https://www.meetup.com/stockholm-rust/">Stockholm Rust</a><ul>
5526. <li><a href="https://www.meetup.com/stockholm-rust/events/300369409"><strong>Ferris' Fika Forum #2</strong></a></li>
5527. </ul>
5528. </li>
5529. <li>2024-04-30 | Budapest, HU | <a href="https://www.meetup.com/budapest-rust-meetup-group/">Budapest Rust Meetup Group</a><ul>
5530. <li><a href="https://www.meetup.com/budapest-rust-meetup-group/events/300269044/"><strong>Rust Meetup Budapest 2</strong></a></li>
5531. </ul>
5532. </li>
5533. <li>2024-04-30 | Salzburg, AT | Rust Salzburg<ul>
5534. <li>[<strong>Rust Salzburg meetup</strong>]: 6:30pm - CCC Salzburg, 1. OG, ArgeKultur, Ulrike-Gschwandtner-Straße 5, 5020 Salzburg</li>
5535. </ul>
5536. </li>
5537. <li>2024-05-01 | Köln/Cologne, DE | <a href="https://www.meetup.com/rustcologne/">Rust Cologne</a><ul>
5538. <li><a href="https://www.meetup.com/rustcologne/events/300610856/"><strong>This Month in Rust, May</strong></a></li>
5539. </ul>
5540. </li>
5541. <li>2024-05-01 | Utrecht, NL | <a href="https://nl-rse.org/events/2024-05-01-meetup">NL-RSE Community</a><ul>
5542. <li><a href="https://www.eventbrite.nl/e/nl-rse-rust-meetup-tickets-871056271757"><strong>NL-RSE RUST meetup</strong></a></li>
5543. </ul>
5544. </li>
5545. <li>2024-05-06 | Delft, NL | <a href="https://www.gosim.org/">GOSIM</a><ul>
5546. <li><a href="https://europe2024.gosim.org/"><strong>GOSIM Europe 2024</strong></a></li>
5547. </ul>
5548. </li>
5549. <li>2024-05-07 & 2024-05-08 | Delft, NL | <a href="https://rustnl.org/">RustNL</a><ul>
5550. <li><a href="https://2024.rustnl.org/"><strong>RustNL 2024</strong></a></li>
5551. </ul>
5552. </li>
5553. <li>2024-05-08 | Cambridge, UK | <a href="https://www.meetup.com/cambridge-rust-meetup/">Cambridge Rust Meetup</a><ul>
5554. <li><a href="https://www.meetup.com/cambridge-rust-meetup/events/300573716/"><strong>Monthly Rust Meetup</strong></a></li>
5555. </ul>
5556. </li>
5557. <li>2024-05-09 | Gdańsk, PL | <a href="https://www.meetup.com/rust-gdansk/">Rust Gdansk</a><ul>
5558. <li><a href="https://www.meetup.com/rust-gdansk/events/299766774/"><strong>Rust Gdansk Meetup #2</strong></a></li>
5559. </ul>
5560. </li>
5561. <li>2024-05-14 | Virtual + In-Person (München/Munich, DE) | <a href="https://www.meetup.com/rust-munich/">Rust Munich</a><ul>
5562. <li><a href="https://www.meetup.com/rust-munich/events/298507657/"><strong>Rust Munich 2024 / 1 - hybrid (Rescheduled)</strong></a></li>
5563. </ul>
5564. </li>
5565. <li>2024-05-14 | Prague, CZ | <a href="https://www.meetup.com/rust-prague/">Rust Prague</a><ul>
5566. <li><a href="https://www.meetup.com/rust-prague/events/300566374/"><strong>Rust Meetup Prague (May 2024)</strong></a></li>
5567. </ul>
5568. </li>
5569. <li>2024-05-21 | Aarhus, DK | <a href="https://www.meetup.com/rust-aarhus/">Rust Aarhus</a><ul>
5570. <li><a href="https://www.meetup.com/rust-aarhus/events/300307155/"><strong>Hack Night</strong></a></li>
5571. </ul>
5572. </li>
5573. <li>2024-05-21 | Zurich, CH | <a href="https://www.meetup.com/rust-zurich/">Rust Zurich</a><ul>
5574. <li><a href="https://www.meetup.com/rust-zurich/events/300513957/"><strong>Save the date - Mai Meetup</strong></a></li>
5575. </ul>
5576. </li>
5577. </ul>
5578. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#north-america">North America</a></h5>
5579. <ul>
5580. <li>2024-04-24 | Austin, TX, US | <a href="https://www.meetup.com/rust-atx/">Rust ATX</a><ul>
5581. <li><a href="https://www.meetup.com/rust-atx/events/299960315/"><strong>Rust Lunch - Fareground</strong></a></li>
5582. </ul>
5583. </li>
5584. <li>2024-04-25 | Nashville, TN, US | <a href="https://www.meetup.com/music-city-rust-developers/">Music City Rust Developers</a><ul>
5585. <li><a href="https://www.meetup.com/music-city-rust-developers/events/299976876/"><strong>Music City Rust Developers - Async Rust on Embedded</strong></a></li>
5586. </ul>
5587. </li>
5588. <li>2024-04-26 | Boston, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
5589. <li><a href="https://www.meetup.com/bostonrust/events/300116689/"><strong>North End Rust Lunch, Apr 26</strong></a></li>
5590. </ul>
5591. </li>
5592. <li>2024-05-04 | Cambridge, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
5593. <li><a href="https://www.meetup.com/bostonrust/events/300116701/"><strong>Kendall Rust Lunch, May 4</strong></a></li>
5594. </ul>
5595. </li>
5596. <li>2024-05-09 | Spokane, WA, US | <a href="https://www.meetup.com/spokane-rust/">Spokane Rust</a><ul>
5597. <li><a href="https://www.meetup.com/spokane-rust/events/300020003/"><strong>Monthly Meetup: Topic TBD!</strong></a></li>
5598. </ul>
5599. </li>
5600. <li>2024-05-12 | Brookline, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
5601. <li><a href="https://www.meetup.com/bostonrust/events/300116747/"><strong>Coolidge Corner Brookline Rust Lunch, May 12</strong></a></li>
5602. </ul>
5603. </li>
5604. <li>2024-05-16 | Seattle, WA, US | <a href="https://www.meetup.com/seattle-rust-user-group/">Seattle Rust User Group</a><ul>
5605. <li><a href="https://www.meetup.com/seattle-rust-user-group/events/299509369/"><strong>Seattle Rust User Group Meetup</strong></a></li>
5606. </ul>
5607. </li>
5608. <li>2024-05-20 | Somerville, MA, US | <a href="https://www.meetup.com/bostonrust/">Boston Rust Meetup</a><ul>
5609. <li><a href="https://www.meetup.com/bostonrust/events/300116765/"><strong>Ball Square Rust Lunch, May 20</strong></a></li>
5610. </ul>
5611. </li>
5612. <li>2024-05-21 | San Francisco, CA, US | <a href="https://www.meetup.com/san-francisco-rust-study-group/">San Francisco Rust Study Group</a><ul>
5613. <li><a href="https://www.meetup.com/san-francisco-rust-study-group/events/299186931/"><strong>Rust Hacking in Person</strong></a></li>
5614. </ul>
5615. </li>
5616. <li>2024-05-22 | Austin, TX, US | <a href="https://www.meetup.com/rust-atx/">Rust ATX</a><ul>
5617. <li><a href="https://www.meetup.com/rust-atx/events/xvkdgtygchbdc/"><strong>Rust Lunch - Fareground</strong></a></li>
5618. </ul>
5619. </li>
5620. </ul>
5621. <h5><a class="toclink" href="http://this-week-in-rust.org/atom.xml#oceania">Oceania</a></h5>
5622. <ul>
5623. <li>2024-04-30 | Auckland, NZ | <a href="https://www.meetup.com/rust-akl/">Rust AKL</a><ul>
5624. <li><a href="https://www.meetup.com/rust-akl/events/300304958/"><strong>Rust AKL: Why Rust? Convince Me!</strong></a></li>
5625. </ul>
5626. </li>
5627. <li>2024-04-30 | Canberra, ACT, AU | <a href="https://www.meetup.com/rust-canberra/">Canberra Rust User Group</a><ul>
5628. <li><a href="https://www.meetup.com/rust-canberra/events/300023000/"><strong>CRUG April Meetup: Generics and Traits</strong></a></li>
5629. </ul>
5630. </li>
5631. </ul>
5632. <p>If you are running a Rust event please add it to the <a href="https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com">calendar</a> to get
5633. it mentioned here. Please remember to add a link to the event too.
5634. Email the <a href="mailto:community-team@rust-lang.org">Rust Community Team</a> for access.</p>
5635. <h4><a class="toclink" href="http://this-week-in-rust.org/atom.xml#jobs">Jobs</a></h4>
5636.  
5637.  
5638. <p>Please see the latest <a href="https://www.reddit.com/r/rust/comments/1bpg8b8/official_rrust_whos_hiring_thread_for_jobseekers/">Who's Hiring thread on r/rust</a></p>
5639. <h3><a class="toclink" href="http://this-week-in-rust.org/atom.xml#quote-of-the-week">Quote of the Week</a></h3>
5640. <blockquote>
5641. <p>The learning curve for Rust is relatively steep compared to other languages, but once you climb it you'll never look down.</p>
5642. </blockquote>
5643. <p>– <a href="https://hachyderm.io/@bd103/112318610927827520">BD103 on Mastodon</a></p>
5644. <p>Thanks to <a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328/1563">BD103</a> for the self-suggestion!</p>
5645. <p><a href="https://users.rust-lang.org/t/twir-quote-of-the-week/328">Please submit quotes and vote for next week!</a></p>
5646. <p><em>This Week in Rust is edited by: <a href="https://github.com/nellshamrell">nellshamrell</a>, <a href="https://github.com/llogiq">llogiq</a>, <a href="https://github.com/cdmistman">cdmistman</a>, <a href="https://github.com/ericseppanen">ericseppanen</a>, <a href="https://github.com/extrawurst">extrawurst</a>, <a href="https://github.com/andrewpollack">andrewpollack</a>, <a href="https://github.com/U007D">U007D</a>, <a href="https://github.com/kolharsam">kolharsam</a>, <a href="https://github.com/joelmarcey">joelmarcey</a>, <a href="https://github.com/mariannegoldin">mariannegoldin</a>, <a href="https://github.com/bennyvasquez">bennyvasquez</a>.</em></p>
5647. <p><em>Email list hosting is sponsored by <a href="https://foundation.rust-lang.org/">The Rust Foundation</a></em></p>
5648. &lt;p&gt;&lt;small&gt;&lt;a href=&quot;https://www.reddit.com/r/rust/comments/1ccwpku/this_week_in_rust_544/&quot;&gt;Discuss on r/rust&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;</description>
5649. <pubDate>Wed, 24 Apr 2024 04:00:00 +0000</pubDate>
5650. <dc:creator>TWiR Contributors</dc:creator>
5651. </item>
5652. <item>
5653. <title>Niko Matsakis: Sized, DynSized, and Unsized</title>
5654. <guid isPermaLink="false">https://smallcultfollowing.com/babysteps/blog/2024/04/23/dynsized-unsized/</guid>
5655. <link>https://smallcultfollowing.com/babysteps/blog/2024/04/23/dynsized-unsized/?utm_source=atom_feed</link>
5656. <description>&lt;p&gt;&lt;a href=&quot;https://rust-lang.github.io/rfcs/1861-extern-types.html&quot;&gt;Extern types&lt;/a&gt; have been blocked for an unreasonably long time on a fairly narrow, specialized question: Rust today divides all types into two categories — &lt;em&gt;sized&lt;/em&gt;, whose size can be statically computed, and &lt;em&gt;unsized&lt;/em&gt;, whose size can only be computed at runtime. But for external types what we really want is a &lt;em&gt;third category&lt;/em&gt;, types whose size can never be known, even at runtime (in C, you can model this by defining structs with an unknown set of fields). The problem is that Rust’s &lt;code&gt;?Sized&lt;/code&gt; notation does not naturally scale to this third case. I think it’s time we fixed this. At some point I read a proposal — I no longer remember where — that seems like the obvious way forward and which I think is a win on several levels. So I thought I would take a bit of time to float the idea again, explain the tradeoffs I see with it, and explain why I think the idea is a good change.&lt;/p&gt;
5657. <h3>TL;DR: write <code>T: Unsized</code> in place of <code>T: ?Sized</code> (and sometimes <code>T: DynSized</code>)</h3>
5658. <p>The basic idea is to deprecate the <code>?Sized</code> notation and instead have a family of <code>Sized</code> supertraits. As today, the default is that every type parameter <code>T</code> gets a <code>T: Sized</code> bound unless the user explicitly chooses one of the other supertraits:</p>
5659. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="sd">/// Types whose size is known at compilation time (statically).
5660. </span></span></span><span class="line"><span class="cl"><span class="sd">/// Implemented by (e.g.) `u32`. References to `Sized` types
5661. </span></span></span><span class="line"><span class="cl"><span class="sd">/// are "thin pointers" -- just a pointer.
5662. </span></span></span><span class="line"><span class="cl"><span class="sd"></span><span class="k">trait</span><span class="w"> </span><span class="nb">Sized</span>: <span class="nc">DynSized</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="p">}</span><span class="w">
5663. </span></span></span><span class="line"><span class="cl"><span class="w">
5664. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="sd">/// Types whose size can be computed at runtime (dynamically).
5665. </span></span></span><span class="line"><span class="cl"><span class="sd">/// Implemented by (e.g.) `[u32]` or `dyn Trait`.
5666. </span></span></span><span class="line"><span class="cl"><span class="sd">/// References to these types are "wide pointers",
5667. </span></span></span><span class="line"><span class="cl"><span class="sd">/// with the extra metadata making it possible to compute the size
5668. </span></span></span><span class="line"><span class="cl"><span class="sd">/// at runtime.
5669. </span></span></span><span class="line"><span class="cl"><span class="sd"></span><span class="k">trait</span><span class="w"> </span><span class="n">DynSized</span>: <span class="nc">Unsized</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="p">}</span><span class="w">
5670. </span></span></span><span class="line"><span class="cl"><span class="w">
5671. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="sd">/// Types that may not have a knowable size at all (either statically or dynamically).
5672. </span></span></span><span class="line"><span class="cl"><span class="sd">/// All types implement this, but extern types **only** implement this.
5673. </span></span></span><span class="line"><span class="cl"><span class="sd"></span><span class="k">trait</span><span class="w"> </span><span class="n">Unsized</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="p">}</span><span class="w">
5674. </span></span></span></code></pre></div><p>Under this proposal, <code>T: ?Sized</code> notation could be converted to <code>T: DynSized</code> or <code>T: Unsized</code>. <code>T: DynSized</code> matches the current semantics precisely, but <code>T: Unsized</code> is probably what most uses actually want. This is because most users of <code>T: ?Sized</code> never compute the size of <code>T</code> but rather just refer to existing values of <code>T</code> by pointer.</p>
5675. <h4>Credit where credit is due?</h4>
5676. <p>For the record, this design is not my idea, but I’m not sure where I saw it. I would appreciate a link so I can properly give credit.</p>
5677. <h3>Why do we have a default <code>T: Sized</code> bound in the first place?</h3>
5678. <p>It’s natural to wonder why we have this <code>T: Sized</code> default in the first place. The short version is that Rust would be very annoying to use without it. If the compiler doesn’t know the size of a value at compilation time, it cannot (at least, cannot easily) generate code to do a number of common things, such as store a value of type <code>T</code> on the stack or have structs with fields of type <code>T</code>. This means that a very large fraction of generic type parameters would wind up with <code>T: Sized</code>.</p>
5679. <h3>So why the <code>?Sized</code> notation?</h3>
5680. <p>The <code>?Sized</code> notation was the result of a lot of discussion. It satisfied a number of criteria.</p>
5681. <h4><code>?</code> signals that the bound operates in reverse</h4>
5682. <p>The <code>?</code> is meant to signal that a bound like <code>?Sized</code> actually works in <strong>reverse</strong> from a normal bound. When you have <code>T: Clone</code>, you are saying “type <code>T</code> <strong>must</strong> implement <code>Clone</code>”. So you are <strong>narrowing</strong> the set of types that <code>T</code> could be: before, it could have been both types that implement <code>Clone</code> and those that do not. After, it can <em>only</em> be types that implement <code>Clone</code>. <code>T: ?Sized</code> does the reverse: before, it can <strong>only</strong> be types that implement <code>Sized</code> (like <code>u32</code>), but after, it can <strong>also</strong> be types that do not (like <code>[u32]</code> or <code>dyn Debug</code>). Hence the <code>?</code>, which can be read as “maybe” — i.e., <code>T</code> is “maybe” Sized.</p>
5683. <h4><code>?</code> can be extended to other default bounds</h4>
5684. <p>The <code>?</code> notation also scales to other default traits. Although we’ve been reluctant to exercise this ability, we wanted to leave room to add a new default bound. This power will be needed if we ever adopt <a href="https://smallcultfollowing.com/babysteps/blog/2023/03/16/must-move-types/">“must move” types</a><sup id="fnref:1"><a class="footnote-ref" href="http://smallcultfollowing.com/babysteps/atom.xml#fn:1">1</a></sup> or add a bound like <code>?Leak</code> to signal a value that cannot be leaked.</p>
5685. <h3>But <code>?</code> doesn’t scale well to “differences in degree”</h3>
5686. <p>When we debated the <code>?</code> notation, we thought a lot about extensibility to other <em>orthogonal</em> defaults (like <code>?Leak</code>), but we didn’t consider extending a single dimension (like <code>Sized</code>) to multiple levels. There is no theoretical challenge. In principle we could say…</p>
5687. <ul>
5688. <li><code>T</code> means <code>T: Sized + DynSized</code></li>
5689. <li><code>T: ?Sized</code> drops the <code>Sized</code> default, leaving <code>T: DynSized</code></li>
5690. <li><code>T: ?DynSized</code> drops both, leaving any type <code>T</code></li>
5691. </ul>
5692. <p>…but I personally find that very confusing. To me, saying something “might be statically sized” does not signify that it <em>is</em> dynamically sized.</p>
5693. <h3>And <code>?</code> looks “more magical” than it needs to</h3>
5694. <p>Despite knowing that <code>T: ?Sized</code> operates in reverse, I find that in practice it still <em>feels</em> very much like other bounds. Just like <code>T: Debug</code> gives the function the extra capability of generating debug info, <code>T: ?Sized</code> feels to me like it gives the function an extra capability: the ability to be used on unsized types. This logic is specious, these are different kinds of capabilities, but, as I said, it’s how I find myself thinking about it.</p>
5695. <p>Moreover, even though I know that <code>T: ?Sized</code> “most properly” means “a type that may or may not be Sized”, I find it wind up <em>thinking</em> about it as “a type that is unsized”, just as I think about <code>T: Debug</code> as a “type that is <code>Debug</code>”. Why is that? Well, beacuse <code>?Sized</code> types <em>may</em> be unsized, I have to treat them as if they <em>are</em> unsized – i.e., refer to them only by pointer. So the fact that they <em>might</em> also be sized isn’t very relevant.</p>
5696. <h3>How would we use these new traits?</h3>
5697. <p>So if we adopted the “family of sized traits” proposal, how would we use it? Well, for starters, the <code>size_of</code> methods would no longer be defined as <code>T</code> and <code>T: ?Sized</code>…</p>
5698. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">size_of</span><span class="o"><</span><span class="n">T</span><span class="o">></span><span class="p">()</span><span class="w"> </span>-> <span class="kt">usize</span> <span class="p">{}</span><span class="w">
5699. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="k">fn</span> <span class="nf">size_of_val</span><span class="o"><</span><span class="n">T</span>: <span class="o">?</span><span class="nb">Sized</span><span class="o">></span><span class="p">(</span><span class="n">t</span>: <span class="kp">&</span><span class="nc">T</span><span class="p">)</span><span class="w"> </span>-> <span class="kt">usize</span> <span class="p">{}</span><span class="w">
5700. </span></span></span></code></pre></div><p>… but instead as <code>T</code> and <code>T: DynSized</code> …</p>
5701. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">size_of</span><span class="o"><</span><span class="n">T</span><span class="o">></span><span class="p">()</span><span class="w"> </span>-> <span class="kt">usize</span> <span class="p">{}</span><span class="w">
5702. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="k">fn</span> <span class="nf">size_of_val</span><span class="o"><</span><span class="n">T</span>: <span class="nc">DynSized</span><span class="o">></span><span class="p">(</span><span class="n">t</span>: <span class="kp">&</span><span class="nc">T</span><span class="p">)</span><span class="w"> </span>-> <span class="kt">usize</span> <span class="p">{}</span><span class="w">
5703. </span></span></span></code></pre></div><p>That said, most uses of <code>?Sized</code> today do not need to compute the size of the value, and would be better translated to <code>Unsized</code>…</p>
5704. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">impl</span><span class="o"><</span><span class="n">T</span>: <span class="nc">Unsized</span><span class="o">></span><span class="w"> </span><span class="n">Debug</span><span class="w"> </span><span class="k">for</span><span class="w"> </span><span class="o">&</span><span class="n">T</span><span class="w"> </span><span class="p">{</span><span class="w">
5705. </span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="k">fn</span> <span class="nf">fmt</span><span class="p">(</span><span class="o">&</span><span class="bp">self</span><span class="p">,</span><span class="w"> </span><span class="n">f</span>: <span class="kp">&</span><span class="nc">mut</span><span class="w"> </span><span class="n">std</span>::<span class="n">fmt</span>::<span class="n">Formatter</span><span class="o"><</span><span class="nb">'_</span><span class="o">></span><span class="p">)</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="o">..</span><span class="w"> </span><span class="p">}</span><span class="w">
5706. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="p">}</span><span class="w">
5707. </span></span></span></code></pre></div><h3>Option: Defaults could also be disabled by supertraits?</h3>
5708. <p>As an interesting extension to today’s system, we could say that every type parameter <code>T</code> gets an implicit <code>Sized</code> bound unless either…</p>
5709. <ol>
5710. <li>There is an explicit weaker alternative(like <code>T: DynSized</code> or <code>T: Unsized</code>);</li>
5711. <li>Or some other bound <code>T: Trait</code> has an explicit supertrait <code>DynSized</code> or <code>Unsized</code>.</li>
5712. </ol>
5713. <p>This would clarify that trait aliases can be used to disable the <code>Sized</code> default. For example, today, one might create a <code>Value</code> trait is equivalent to <code>Debug + Hash + Org</code>, roughly like this:</p>
5714. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">trait</span><span class="w"> </span><span class="n">Value</span>: <span class="nc">Debug</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Hash</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="nb">Ord</span><span class="w"> </span><span class="p">{</span><span class="w">
5715. </span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// Note that `Self` is the *only* type parameter that does NOT get `Sized` by default
5716. </span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="p">}</span><span class="w">
5717. </span></span></span><span class="line"><span class="cl"><span class="w">
5718. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="k">impl</span><span class="o"><</span><span class="n">T</span>: <span class="o">?</span><span class="nb">Sized</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Debug</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Hash</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="nb">Ord</span><span class="o">></span><span class="w"> </span><span class="n">Value</span><span class="w"> </span><span class="k">for</span><span class="w"> </span><span class="n">T</span><span class="w"> </span><span class="p">{}</span><span class="w">
5719. </span></span></span></code></pre></div><p>But what if, in your particular data structure, all values are boxed and hence can be unsized. Today, you have to repeat <code>?Sized</code> everywhere:</p>
5720. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">struct</span> <span class="nc">Tree</span><span class="o"><</span><span class="n">V</span>: <span class="o">?</span><span class="nb">Sized</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Value</span><span class="o">></span><span class="w"> </span><span class="p">{</span><span class="w">
5721. </span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="n">value</span>: <span class="nb">Box</span><span class="o"><</span><span class="n">V</span><span class="o">></span><span class="p">,</span><span class="w">
5722. </span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="n">children</span>: <span class="nb">Vec</span><span class="o"><</span><span class="n">Tree</span><span class="o"><</span><span class="n">V</span><span class="o">>></span><span class="p">,</span><span class="w">
5723. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="p">}</span><span class="w">
5724. </span></span></span><span class="line"><span class="cl"><span class="w">
5725. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="k">impl</span><span class="o"><</span><span class="n">V</span>: <span class="o">?</span><span class="nb">Sized</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Value</span><span class="o">></span><span class="w"> </span><span class="n">Tree</span><span class="o"><</span><span class="n">V</span><span class="o">></span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="err">…</span><span class="w"> </span><span class="p">}</span><span class="w">
5726. </span></span></span></code></pre></div><p>With this proposal, the <em>explicit</em> <code>Unsized</code> bound could be signaled on the trait:</p>
5727. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">trait</span><span class="w"> </span><span class="n">Value</span>: <span class="nc">Debug</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Hash</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="nb">Ord</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Unsized</span><span class="w"> </span><span class="p">{</span><span class="w">
5728. </span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// Note that `Self` is the *only* type parameter that does NOT get `Sized` by default
5729. </span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="p">}</span><span class="w">
5730. </span></span></span><span class="line"><span class="cl"><span class="w">
5731. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="k">impl</span><span class="o"><</span><span class="n">T</span>: <span class="nc">Unsized</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Debug</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="n">Hash</span><span class="w"> </span><span class="o">+</span><span class="w"> </span><span class="nb">Ord</span><span class="o">></span><span class="w"> </span><span class="n">Value</span><span class="w"> </span><span class="k">for</span><span class="w"> </span><span class="n">T</span><span class="w"> </span><span class="p">{}</span><span class="w">
5732. </span></span></span></code></pre></div><p>which would mean that</p>
5733. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">struct</span> <span class="nc">Tree</span><span class="o"><</span><span class="n">V</span>: <span class="nc">Value</span><span class="o">></span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="err">…</span><span class="w"> </span><span class="p">}</span><span class="w">
5734. </span></span></span></code></pre></div><p>would imply <code>V: Unsized</code>.</p>
5735. <h3>Alternatives</h3>
5736. <h4>Different names</h4>
5737. <p>The name of the <code>Unsized</code> trait in particular is a bit odd. It means “you can treat this type as unsized”, which is true of all types, but it <em>sounds</em> like the type is <em>definitely</em> unsized. I’m open to alternative names, but I haven’t come up with one I like yet. Here are some alternatives and the problems with them I see:</p>
5738. <ul>
5739. <li><code>Unsizeable</code> — doesn’t meet our typical name conventions, has overlap with the <code>Unsize</code> trait</li>
5740. <li><code>NoSize</code>, <code>UnknownSize</code> — same general problem as <code>Unsize</code></li>
5741. <li><code>ByPointer</code> — in some ways, I kind of like this, because it says “you can work with this type by pointer”, which is clearly true of all types. But it doesn’t align well with the existing <code>Sized</code> trait — what would we call that, <code>ByValue</code>? And it seems too tied to today’s limitations: there are, after all, ways that we can make <code>DynSized</code> types work by value, at least in some places.</li>
5742. <li><code>MaybeSized</code> — just seems awkward, and should it be <code>MaybeDynSized</code>?</li>
5743. </ul>
5744. <p>All told, I think <code>Unsized</code> is the best name. It’s a <em>bit</em> wrong, but I think you can understand it, and to me it fits the intuition I have, which is that I mark type parameters as <code>Unsized</code> and then I tend to just think of them as being unsized (since I have to).</p>
5745. <h4>Some sigil</h4>
5746. <p>Under this proposal, the <code>DynSized</code> and <code>Unsized</code> traits are “magic” in that explicitly declaring them as a bound has the impact of disabling a default <code>T: Sized</code> bound. We could signify that in their names by having their name be prefixed with some sort of sigil. I’m not really sure what that sigil would be — <code>T: %Unsized</code>? <code>T: ?Unsized</code>? It all seems unnecessary.</p>
5747. <h4>Drop the implicit bound altogether</h4>
5748. <p>The purist in me is tempted to question whether we need the default bound. Maybe in Rust 2027 we should try to drop it altogether. Then people could write</p>
5749. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">fn</span> <span class="nf">size_of</span><span class="o"><</span><span class="n">T</span>: <span class="nb">Sized</span><span class="o">></span><span class="p">()</span><span class="w"> </span>-> <span class="kt">usize</span> <span class="p">{}</span><span class="w">
5750. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="k">fn</span> <span class="nf">size_of_val</span><span class="o"><</span><span class="n">T</span>: <span class="nc">DynSized</span><span class="o">></span><span class="p">(</span><span class="n">t</span>: <span class="kp">&</span><span class="nc">T</span><span class="p">)</span><span class="w"> </span>-> <span class="kt">usize</span> <span class="p">{}</span><span class="w">
5751. </span></span></span></code></pre></div><p>and</p>
5752. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">impl</span><span class="o"><</span><span class="n">T</span><span class="o">></span><span class="w"> </span><span class="n">Debug</span><span class="w"> </span><span class="k">for</span><span class="w"> </span><span class="o">&</span><span class="n">T</span><span class="w"> </span><span class="p">{</span><span class="w">
5753. </span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="k">fn</span> <span class="nf">fmt</span><span class="p">(</span><span class="o">&</span><span class="bp">self</span><span class="p">,</span><span class="w"> </span><span class="n">f</span>: <span class="kp">&</span><span class="nc">mut</span><span class="w"> </span><span class="n">std</span>::<span class="n">fmt</span>::<span class="n">Formatter</span><span class="o"><</span><span class="nb">'_</span><span class="o">></span><span class="p">)</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="o">..</span><span class="w"> </span><span class="p">}</span><span class="w">
5754. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="p">}</span><span class="w">
5755. </span></span></span></code></pre></div><p>Of course, it would also mean a lot of <code>Sized</code> bounds cropping up in surprising places. Beyond random functions, consider that every associated type today has a default <code>Sized</code> bound, so you would need</p>
5756. <div class="highlight"><pre class="chroma" tabindex="0"><code class="language-rust"><span class="line"><span class="cl"><span class="k">trait</span><span class="w"> </span><span class="nb">Iterator</span><span class="w"> </span><span class="p">{</span><span class="w">
5757. </span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="k">type</span> <span class="nc">Item</span>: <span class="nb">Sized</span><span class="p">;</span><span class="w">
5758. </span></span></span><span class="line"><span class="cl"><span class="w"></span><span class="p">}</span><span class="w">
5759. </span></span></span></code></pre></div><p>Overall, I doubt this idea is worth it. Not surprising: it was deemed too annoying before, and now it has the added problem of being hugely disruptive.</p>
5760. <h3>Conclusion</h3>
5761. <p>I’ve covered a design to move away from <code>?Sized</code> bounds and towards specialized traits. There are avrious “pros and cons” to this proposal but one aspect in particular feels common to this question and many others: when do you make two “similar but different” concepts feel very different — e.g., via special syntax like <code>T: ?Sized</code> — and when do you make them feel very similar — e.g., via the idea of “special traits” where a bound like <code>T: Unsized</code> has extra meaning (disabling defaults).</p>
5762. <p>There is a definite trade-off here. Distinct syntax help avoid potential confusion, but it forces people to recognize that something special is going on even when that may not be relevant or important to them. This can deter folks early on, when they are most “deter-able”. I think it can also contribute to a general sense of “big-ness” that makes it feel like understanding the entire language is harder.</p>
5763. <p>Over time, I’ve started to believe that it’s generally better to make things feel similar, letting people push off the time at which they have to learn a new concept. In this case, this lessens my fears around the idea that <code>Unsized</code> and <code>DynSized</code> traits would be confusing because they behave differently than other traits. In this particular case, I also feel that <code>?Sized</code> doesn’t “scale well” to default bounds where you want to pick from one of many options, so it’s kind of the worst of both worlds – distinct syntax that shouts at you but which <em>also</em> fails to add clarity.</p>
5764. <p>Ultimately, though, I’m not wedded to this idea, but I am interested in kicking off a discussion of how we can unblock <a href="https://rust-lang.github.io/rfcs/1861-extern-types.html">extern types</a>. I think by now we’ve no doubt covered the space pretty well and we should pick a direction and go for it (or else just give up on <a href="https://rust-lang.github.io/rfcs/1861-extern-types.html">extern types</a>).</p>
5765. <div class="footnotes">
5766. <hr />
5767. <ol>
5768. <li id="fn:1">
5769. <p>I still think <a href="https://smallcultfollowing.com/babysteps/blog/2023/03/16/must-move-types/">“must move” types</a> are a good idea — but that’s a topic for another post. <a class="footnote-backref" href="http://smallcultfollowing.com/babysteps/atom.xml#fnref:1">↩︎</a></p>
5770. </li>
5771. </ol>
5772. &lt;/div&gt;</description>
5773. <pubDate>Tue, 23 Apr 2024 20:51:54 +0000</pubDate>
5774. </item>
5775. <item>
5776. <title>Hacks.Mozilla.Org: Porting a cross-platform GUI application to Rust</title>
5777. <guid isPermaLink="false">https://hacks.mozilla.org/?p=48127</guid>
5778. <link>https://hacks.mozilla.org/2024/04/porting-a-cross-platform-gui-application-to-rust/</link>
5779. <description>&lt;p&gt;Firefox’s crash reporter is hopefully not something that most users experience often. However, it is still a very important component of Firefox, as it is integral in providing insight into the most visible bugs: those which crash the main process. These bugs offer the worst user experience (since the entire application must close), so fixing them is a very high priority. Other types of crashes, such as content (tab) crashes, can be handled by the browser and reported gracefully, sometimes without the user being aware that an issue occurred at all. But when the main browser process comes to a halt, we need another separate application to gather information about the crash and interact with the user.&lt;/p&gt;
5780. <p>This post details the approach we have taken to rewrite the crash reporter in Rust. We discuss the reasoning behind this rewrite, what makes the crash reporter a unique application, the architecture we used, and some details of the implementation.</p>
5781. <h3>Why Rewrite?</h3>
5782. <p>Even though it is important to properly handle main process crashes, the crash reporter hasn’t received significant development in a while (aside from development to ensure that crash reports and telemetry continue to reliably be delivered)! It has long been stuck in a local maximum of “good enough” and “scary to maintain”: it features 3 individual GUI implementations (for Windows, GTK+ for Linux, and macOS), glue code abstracting a few things (mostly in C++, and Objective-C for macOS), a binary blob produced by obsoleted Apple development tools, and no test suite. Because of this, there is a backlog of features and improvements which haven’t been acted on.</p>
5783. <p>We’ve recently had a number of successful pushes to decrease crash rates (including both <a href="https://hacks.mozilla.org/2022/11/improving-firefox-stability-with-this-one-weird-trick/">big leaps</a> and many small bug fixes), and the crash reporter has functioned well enough for our needs during this time. However, we’ve reached an inflection point where improving the crash reporter would provide valuable insight to enable us to decrease the crash rate even further. For the reasons previously mentioned, improving the current codebase is difficult and error-prone, so we deemed it appropriate to rewrite the application so we can more easily act on the feature backlog and improve crash reports.</p>
5784. <p>Like many components of Firefox, we decided to use Rust for this rewrite to produce a more reliable and maintainable program. Besides the often-touted memory safety built into Rust, its type system and standard library make reasoning about code, handling errors, and developing cross-platform applications far more robust and comprehensive.</p>
5785. <h3>Crash Reporting is an Edge Case</h3>
5786. <p>There are a number of features of the crash reporter which make it quite unique, especially compared to other components which have been ported to Rust. For one thing, it is a standalone, individual program; basically no other components of Firefox are used in this way. Firefox itself launches many processes as a means of sandboxing and insulating against crashes, however these processes all talk to one another and have access to the same code base.</p>
5787. <p>The crash reporter has a very unique requirement: it must use as <i>little as possible </i>of the Firefox code base, ideally none! We don’t want it to rely on code which may be buggy and cause the reporter itself to crash. Using a completely independent implementation ensures that when a main process crash does occur, the cause of that crash won’t affect the reporter’s functionality as well.</p>
5788. <p>The crash reporter also necessarily has a GUI. This alone may not separate it from other Firefox components, but we can’t leverage any of the cross-platform rendering goodness that Firefox provides! So we need to implement a cross-platform GUI independent of Firefox as well. You might think we could reach for an existing cross-platform GUI crate, however we have a few reasons not to do so.</p>
5789. <ul>
5790. <li>We want to minimize the use of external code: to improve crash reporter reliability (which is paramount), we want it to be as simple and auditable as possible.</li>
5791. <li>Firefox vendors all dependencies in-tree, so we are hesitant to bring in large dependencies (GUI libraries are likely pretty sizable).</li>
5792. <li>There are only a few third-party crates that provide a native OS look and feel (or actually <i>use</i> native GUI APIs): it’s desirable for the crash reporter to have a native feel to be familiar to users and take advantage of accessibility features.</li>
5793. </ul>
5794. <p>So all of this is to say that third-party cross-platform GUI libraries aren’t a favorable option.</p>
5795. <p>These requirements significantly narrow the approach that can be used.</p>
5796. <h3>Building a GUI View Abstraction</h3>
5797. <p>In order to make the crash reporter more maintainable (and make it easier to add new features in the future), we want to have as minimal and generic platform-specific code as possible. We can achieve this by using a simple UI model that can be converted into native GUI code for each platform. Each UI implementation will need to provide two methods (over arbitrary platform-specific <tt>&self</tt> data):</p>
5798. <pre><code class="language-rust">/// Run a UI loop, displaying all windows of the application until it terminates.
5799. fn run_loop(&self, app: model::Application)
5800.  
5801. /// Invoke a function asynchronously on the UI loop thread.
5802. fn invoke(&self, f: model::InvokeFn)
5803. </code></pre>
5804. <p>The <tt>run_loop</tt> function is pretty self-explanatory: the UI implementation takes an <tt>Application</tt> model (which we’ll discuss shortly) and runs the application, <i>blocking</i> until the application is complete. Conveniently, our target platforms generally have similar assumptions around threading: the UI runs in a single thread and typically runs an event loop which blocks on new events until an event signaling the end of the application is received.</p>
5805. <p>There are some cases where we’ll need to run a function on the UI thread asynchronously (like displaying a window, updating a text field, etc). Since <tt>run_loop</tt> blocks, we need the <tt>invoke</tt> method to define how to do this. This threading model will make it easy to use the platform GUI frameworks: everything calling native functions will occur on a single thread (the main thread in fact) for the duration of the program.</p>
5806. <p>This is a good time to be a bit more specific about exactly what each UI implementation will look like. We’ll discuss pain points for each later on. There are 4 UI implementations:</p>
5807. <ul>
5808. <li>A Windows implementation using the Win32 API.</li>
5809. <li>A macOS implementation using Cocoa (AppKit and Foundation frameworks).</li>
5810. <li>A Linux implementation using GTK+ 3 (the “+” has since been dropped in GTK 4, so henceforth I’ll refer to it as “GTK”). Linux doesn’t provide its own GUI primitives, and we already ship GTK with Firefox on Linux to make a modern-feeling GUI, so we can use it for the crash reporter, too. Note that some platforms that aren’t directly supported by Mozilla (like BSDs) use the GTK implementation as well.</li>
5811. <li>A testing implementation which will allow tests to hook into a virtual UI and poke things (to simulate interactions and read state).</li>
5812. </ul>
5813. <p>One last detail before we dive in: the crash reporter (at least right now) has a pretty simple GUI. Because of this, an explicit <b>non-goal</b> of the development was to create a separate Rust GUI crate. We wanted to create just enough of an abstraction to cover the cases we needed in the crash reporter. If we need more controls in the future, we can add them to the abstraction, but we avoided spending extra cycles to fill out every GUI use case.</p>
5814. <p>Likewise, we tried to avoid unnecessary development by allowing some tolerance for hacks and built-in edge cases. For example, our model defines a <tt>Button</tt> as an element which contains an arbitrary element, but actually supporting that with Win32 or AppKit would have required a lot of custom code, so we special case on a <tt>Button</tt> containing a <tt>Label</tt> (which is all we need right now, and an easy primitive available to us). I’m happy to say there aren’t really <i>many</i> special cases like that at all, but we are comfortable with the few that were needed.</p>
5815. <h4>The UI Model</h4>
5816. <p>Our model is a declarative structuring of concepts mostly present in GTK. Since GTK is a mature library with proven high-level UI concepts, this made it appropriate for our abstraction and made the GTK implementation pretty simple. For instance, the simplest way that GTK does layout (using container GUI elements and per-element margins/alignments) is good enough for our GUI, so we use similar definitions in the model. Notably, this “simple” layout definition is actually somewhat high-level and complicates the macOS and Windows implementations a bit (but this tradeoff is worth the ease of creating UI models).</p>
5817. <p>The top-level type of our UI model is <tt>Application</tt>. This is pretty simple: we define an <tt>Application</tt> as a set of top-level <tt>Window</tt>s (though our application only has one) and whether the current locale is <a href="https://en.wikipedia.org/wiki/Right-to-left_script">right-to-left</a>. We inspect Firefox resources to use the same locale that Firefox would, so we don’t rely on the native GUI’s locale settings.</p>
5818. <p>As you might expect, each <tt>Window</tt> contains a single root element. The rest of the model is made up of a handful of typical container and primitive GUI elements:</p>
5819. <p><img alt="A class diagram showing the inheritance structure. An Application contains one or more Windows. A Window contains one Element. An Element is subclassed to Checkbox, Label, Progress, TextBox, Button, Scroll, HBox, and VBox types." class="aligncenter wp-image-48128 size-full" height="421" src="https://hacks.mozilla.org/wp-content/uploads/2024/03/class_diagram.png" width="389" /></p>
5820. <p>The crash reporter only needs 8 types of GUI elements! And really, <tt>Progress</tt> is used as a spinner rather than indicating any real progress as of right now, so it’s not strictly necessary (but nice to show).</p>
5821. <p>Rust does not explicitly support the object-oriented concept of inheritance, so you might be wondering how each GUI element “extends” <tt>Element</tt>. The relationship represented in the picture is somewhat abstract; the implemented <tt>Element</tt> looks like:</p>
5822. <pre><code class="language-rust">pub struct Element {
5823.    pub style: ElementStyle,
5824.    pub element_type: ElementType
5825. }
5826. </code></pre>
5827. <p>where <tt>ElementStyle</tt> contains all the common properties of elements (alignment, size, margin, visibility, and enabled state), and <tt>ElementType</tt> is an <tt>enum</tt> containing each of the specific GUI elements as variants.</p>
5828. <h5>Building the Model</h5>
5829. <p>The model elements are all intended to be consumed by the UI implementations; as such, almost all of the fields have public visibility. However, as a means of having a separate interface for <i>building</i> elements, we define an <tt>ElementBuilder<T></tt> type. This type has methods that maintain assertions and provide convenience setters. For instance, many methods accept parameters that are <tt>impl Into<MemberType></tt>, some methods like <tt>margin()</tt> set multiple values (but you can be more specific with <tt>margin_top()</tt>), etc.</p>
5830. <p>There is a general <tt>impl<T> ElementBuilder<T></tt> which provides setters for the various <tt>ElementStyle</tt> properties, and then each specific element type can also provide their own <tt>impl ElementBuilder<SpecificElement></tt> with additional properties unique to the element type.</p>
5831. <p>We combine <tt>ElementBuilder<T></tt> with the final piece of the puzzle: a <tt>ui!</tt> macro. This macro allows us to write our UI in a declarative manner. For example, it allows us to write:</p>
5832. <pre><code class="language-rust">let details_window = ui! {
5833.    Window title("Crash Details") visible(show_details) modal(true) hsize(600) vsize(400)
5834.         halign(Alignment::Fill) valign(Alignment::Fill)
5835.    {
5836.         VBox margin(10) spacing(10) halign(Alignment::Fill) valign(Alignment::Fill) {
5837.             Scroll halign(Alignment::Fill) valign(Alignment::Fill) {
5838.                 TextBox content(details) halign(Alignment::Fill) valign(Alignment::Fill)
5839.             },
5840.             Button halign(Alignment::End) on_click(move || *show_details.borrow_mut() = false)
5841.             {
5842.                 Label text("Ok")
5843.             }
5844.         }
5845.     }
5846. };
5847. </code></pre>
5848. <p>The implementation of <tt>ui!</tt> is fairly simple. The first identifier provides the element type and an <tt>ElementBuilder<T></tt> is created. After that, the remaining method-call-like syntax forms are called on the builder (which is mutable).</p>
5849. <p>Optionally, a final set of curly braces indicate that the element has children. In that case, the macro is recursively called to create them, and <tt>add_child</tt> is called on the builder with the result (so we just need to make sure a builder has an <tt>add_child</tt> method). Ultimately the syntax transformation is pretty simple, but I believe that this macro is a little bit more than <i>just</i> syntax sugar: it makes reading and editing the UI a fair bit clearer, since the hierarchy of elements is represented in the syntax. Unfortunately a downside is that there’s no way to support automatic formatting of such macro DSLs, so developers will need to maintain a sane formatting.</p>
5850. <p>So now we have a model defined and a declarative way of building it. But we haven’t discussed any dynamic runtime behaviors here. In the above example, we see an <tt>on_click</tt> handler being set on a <tt>Button</tt>. We also see things like the <tt>Window</tt>’s <tt>visible</tt> property being set to a <tt>show_details</tt> value which is changed when <tt>on_click</tt> is pressed. We hook into this declarative UI to change or react to events at runtime using a set of simple data binding primitives with which UI implementations can interact.</p>
5851. <div style="background-color: lightgrey;">
5852. <p><i>Many</i> GUI frameworks nowadays (both for Rust and other languages) have been built with the “diffing element trees” architecture (think <a href="https://react.dev/">React</a>), where your code is (at least mostly) functional and side-effect-free and produces the GUI view as a function of the current state. This approach has its tradeoffs: for instance, it makes complicated, stateful alterations of the layout very simple to write, understand, and maintain, and encourages a clean separation of model and view! However since we <i>aren’t</i> writing a framework, and our application is and will remain fairly simple, the benefits of such an architecture were not worth the additional development burden. Our implementation is more similar to the <a href="https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93viewmodel">MVVM architecture</a>:</p>
5853. <ul>
5854. <li>the model is, well, the model discussed here;</li>
5855. <li>the views are the various UI implementations; and</li>
5856. <li>the viewmodel is (loosely, if you squint) the collection of data bindings.</li>
5857. </ul>
5858. </div>
5859. <h4>Data Binding</h4>
5860. <p>There are a few types which we use to declare dynamic (runtime-changeable) values. In our UI, we needed to support a few different behaviors:</p>
5861. <ul>
5862. <li>triggering <b>events</b>, i.e., what happens when a button is clicked,</li>
5863. <li><b>synchronized</b> values which will mirror and notify of changes to all clones, and</li>
5864. <li><b>on-demand</b> values which can be queried for the current value.</li>
5865. </ul>
5866. <div style="background-color: lightgrey;">
5867. <p>On-demand values are used to get textbox contents rather than using a synchronized value, in an effort to avoid implementing debouncing in each UI. It may not be terribly difficult to do so, but it also wasn’t difficult to support the on-demand implementation.</p>
5868. </div>
5869. <p>As a means of convenience, we created a <tt>Property</tt> type which encompasses the value-oriented fields as well. A <tt>Property<T></tt> can be set to either a static value (<tt>T</tt>), a synchronized value (<tt>Synchronized<T></tt>), or an on-demand value (<tt>OnDemand<T></tt>). It supports an <tt>impl From</tt> for each of these, so that builder methods can look like <tt>fn my_method(&mut self, value: impl Into<Property<T>>)</tt> allowing any supported value to be passed in a UI declaration.</p>
5870. <p>We won’t discuss the implementation in depth (<a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/data.rs">it’s what you’d expect</a>), but it’s worth noting that these are all <tt>Clone</tt> to easily share the data bindings: they use <tt>Rc</tt> (we don’t need thread safety) and <tt>RefCell</tt> as necessary to access callbacks.</p>
5871. <p>In the example from the last section, <tt>show_details</tt> is a <tt>Synchronized<bool></tt> value. When it changes, the UI implementations change the associated window visibility. The <tt>Button</tt> <tt>on_click</tt> callback sets the synchronized value to false, hiding the window (note that the details window used in this example is never closed, it is just shown and hidden).</p>
5872. <div style="background-color: lightgrey;">
5873. <p>In a former iteration, data binding types had a lifetime parameter which specified the lifetime for which event callbacks were valid. While we were able to make this work, it greatly complicated the code, especially because there’s no way to communicate the correct covariance of the lifetime to the compiler, so there was additional <tt>unsafe</tt> code transmuting lifetimes (though it was contained as an implementation detail). These lifetimes were also infectious, requiring some of the complicated semantics regarding their safety to be propagated into the model types which stored <tt>Property</tt> fields.</p>
5874. <p>Much of this was to avoid cloning values into the callbacks, but changing these types to all be <tt>Clone</tt> and store static-lifetime callbacks was worth making the code far more maintainable.</p>
5875. </div>
5876. <h5>Threading and Thread Safety</h5>
5877. <p>The careful reader might remember that we discussed how our threading model involves interacting with the UI implementations <em>only</em> on the main thread. This includes updating the data bindings, since the UI implementations might have registered callbacks on them! While we <i>could</i> run everything in the main thread, it’s generally a much better experience to do as much off of the UI thread as possible, even if we don’t do much that’s blocking (though we will be blocking when we send crash reports). We want our business logic to default to being off of the main thread so that the UI doesn’t ever freeze. We can guarantee this with some careful design.</p>
5878. <p>The simplest way to guarantee this behavior is to put all of the business logic in one (non-<tt>Clone</tt>, non-<tt>Sync</tt>) type (let’s call it <tt>Logic</tt>) and construct the UI and UI state (like <tt>Property</tt> values) in another type (let’s call it <tt>UI</tt>). We can then <i>move</i> the <tt>Logic</tt> value into a separate thread to guarantee that <tt>UI</tt> can’t interact with <tt>Logic</tt> directly, and vice versa. Of course we do need to communicate sometimes! But we want to ensure that this communication will always be delegated to the thread which owns the values (rather than the values directly interacting with each other).</p>
5879. <p>We can accomplish this by creating an enqueuing function for each type and storing that in the opposite type. Such a function will be passed boxed functions to run on the owning thread that get a reference to the owned type (e.g., <tt>Box<dyn FnOnce(&T) + Send + 'static></tt>). This is simple to create: for the <tt>UI</tt> thread, it is just the <tt>UI</tt> implementation’s <tt>invoke</tt> method which we briefly discussed previously. The <tt>Logic</tt> thread does nothing <i>but</i> run a loop which will get these functions and run them on the owned value (we just enqueue and pass them using an <a href="https://doc.rust-lang.org/stable/std/sync/mpsc/fn.channel.html"><tt>mpsc::channel</tt></a>). Now each type can asynchronously call methods on the other with the guarantee that they’ll be run on the correct thread.</p>
5880. <div style="background-color: lightgrey;">
5881. <p>In a former iteration, a more complicated scheme was used with thread-local storage and a central type which was responsible for both creating threads and delegating the functions. But with such a basic use case as two threads delegating between each other, we were able to distill this to the essential aspects needed, greatly simplifying the code.</p>
5882. </div>
5883. <h4>Localization</h4>
5884. <p>One nice benefit of this rewrite is that we could bring the localization of the crash reporter up to speed with our modern tooling. In almost every other part of Firefox, we use <a href="https://projectfluent.org/"><tt>fluent</tt></a> to handle localization. Using <tt>fluent</tt> in the crash reporter makes the experience of localizers more uniform and predictable; they do not need to understand more than one localization system (the crash reporter was one of the last holdouts of the old system). It was very easy to use in the new code, with just a bit of extra code to extract the localization files from the Firefox installation when the crash reporter is run. In the worst case scenario where we can’t find or access these files, we have the <tt>en-US</tt> definitions directly bundled in the crash reporter binary.</p>
5885. <h3>The UI Implementations</h3>
5886. <p>We won’t go into much detail about the implementations, but it’s worth talking about each a bit.</p>
5887. <h4>Linux (GTK)</h4>
5888. <p>The GTK implementation is probably the most straightforward and succinct. We use <a href="https://github.com/rust-lang/rust-bindgen"><tt>bindgen</tt></a> to generate Rust bindings to the GTK functions we need (avoiding vendoring any external crates). Then we simply call all of the corresponding GTK functions to set up the GTK widgets as described in the model (remember, the model was made to mirror some of the GTK concepts).</p>
5889. <p>Since GTK is somewhat modern and meant to be written by humans (not automated tools like some of the other platforms), there weren’t really any pain points or unusual behaviors that needed to be addressed.</p>
5890. <p>We have a handful of nice features to improve memory safety and correctness. <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/gtk.rs#96,105">A set of traits</a> makes it easy to attach owned data to GObjects (ensuring data remains valid and is properly dropped when the GObject is destroyed), and <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/gtk.rs#177,205,228">a few macros</a> set up the glue code between GTK signals and our data binding types.</p>
5891. <h4>Windows (Win32)</h4>
5892. <p>The Windows implementation may have been the most difficult to write, since Win32 GUIs are very rarely written nowadays and the API shows its age. We use the <a href="https://crates.io/crates/windows-sys"><tt>windows-sys</tt></a> crate to access bindings to the API (which was already vendored in the codebase for many other Windows API uses). This crate is generated directly from Windows function metadata (by Microsoft), but otherwise its bindings aren’t terribly different from what <tt>bindgen</tt> might have produced (though they are likely a bit more accurate).</p>
5893. <p>There were a number of hurdles to overcome. For one thing, the Win32 API doesn’t provide any layout primitives, so the high-level layout concepts we use (which allow graceful resize/repositioning) had to be <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/windows/layout.rs">implemented manually</a>. There’s also quite a few extra API calls just to get to a GUI that looks somewhat decent (correct window colors, font smoothing, high DPI handling, etc). Even the default font ends up being a terrible looking bitmapped font rather than the more modern system default; we needed to manually retrieve the system default and set it as the font to use, which was a bit surprising!</p>
5894. <p>We have <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/windows/window.rs#16,40,120">a set of traits</a> to facilitate creating custom window classes and managing associated window data of class instances. We also <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/windows/gdi.rs">have</a> <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/windows/font.rs">wrapper</a> <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/windows/widestring.rs">types</a> to properly manage the lifetimes of handles and perform type conversions (mainly <tt>String</tt> to null-terminated wide strings and back) as an extra layer of safety around the API.</p>
5895. <h4>macOS (Cocoa/AppKit)</h4>
5896. <p>The macOS implementation had its tricky parts, as overwhelmingly macOS GUIs are written with XCode and there’s a lot of automated and generated portions (such as nibs). We again use <a href="https://github.com/rust-lang/rust-bindgen"><tt>bindgen</tt></a> to generate Rust bindings, this time for the Objective-C APIs in macOS framework headers.</p>
5897. <p>Unlike Windows and GTK, you don’t get keyboard shortcuts like Cmd-C, Cmd-Q, etc, for free if creating a GUI without e.g. XCode (which generates it for you as part of a new project template). To have these typical shortcuts that users expect, we needed to manually implement the application main menu (which is what governs keyboard shortcuts). We also had to handle runtime setup like creating Objective-C autorelease pools, bringing the window <i>and application</i> (which are separate concepts) to the foreground, etc. Even implementing <tt>invoke</tt> to call a function on the main thread had its nuances, since modal windows use a nested event loop which would not call queued functions under the default <tt>NSRunLoop</tt> mode.</p>
5898. <p>We wrote some <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/macos/objc.rs">simple helper types and a macro</a> to make it easy to implement, register, and create Objective-C classes from Rust code. We used this for creating delegate classes as well as subclassing some controls for the implementation (like <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/ui/macos/mod.rs#365-386"><tt>NSButton</tt></a>); it made it easy to safely manage the memory of Rust values underlying the classes and correctly register class method selectors.</p>
5899. <h4>The Test UI</h4>
5900. <p>We’ll discuss testing in the next section. Our testing UI is very simple. It <i>doesn’t</i> create a GUI, but allows us to interact directly with the model. The <tt>ui!</tt> macro supports an extra piece of syntax when tests are enabled to optionally set a string identifier for each element. We use these strings in unit tests to access and interact with the UI. The data binding types also support a few additional methods in tests to easily manipulate values. This UI allows us to simulate button presses, field entry, etc, to ensure that other UI state changes as expected as well as simulating the system side effects.</p>
5901. <h3>Mocking and Testing</h3>
5902. <p>An important goal of our rewrite was to add tests to the crash reporter; our old code was sorely lacking them (in part because unit testing GUIs is notoriously difficult).</p>
5903. <h4>Mocking Everything</h4>
5904. <p>In the new code, we can mock the crash reporter regardless of whether we are running tests or not (though it is always mocked for tests). This is important because mocking allows us to (manually) run the GUI in various states to check that the GUI implementations are correct and render well. Our mocking not only mocks the inputs to the crash reporter (environment variables, command line parameters, etc), it also mocks <i>all</i> side-effectful std functions.</p>
5905. <p>We accomplish this by having a <tt>std</tt> module in the crate, and using <tt>crate::std</tt> throughout the rest of the code. When mocking is disabled, <tt>crate::std</tt> is simply the same as <tt>::std</tt>. But when it is enabled, a bunch of functions that we have written are used instead. These mock the filesystem, environment, launching external commands, and other side effects. Importantly, only the minimal amount to mock the existing functions is implemented, so that if e.g. some new functions from <tt>std::fs</tt>, <tt>std::net</tt>, etc. are used, the crate will fail to compile with mocking enabled (so that we don’t <i>miss</i> any side effects). This might sound like a lot of effort, but you might be surprised at how little of <tt>std</tt> really needed to be mocked, and most implementations were pretty straightforward.</p>
5906. <p>Now that we have our code using different mocked functions, we need to have a way of injecting the desired mock data (both in tests and in our normal mocked operation). For example, we have the ability to return some data when a <tt>File</tt> is read, but we need to be able to set that data differently for tests. Without going into too much detail, we accomplish this using a thread-local store of mock data. This way, we don’t need to change any code to accommodate the mock data; we only need to make changes where we set and retrieve it. The programming language enthusiasts out there may recognize this as a form of <a href="https://en.wikipedia.org/wiki/Scope_(computer_science)#Dynamic_scope">dynamic scoping</a>. The <a href="https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/toolkit/crashreporter/client/app/src/std/mock.rs">implementation</a> allows our mock data to be set with code like</p>
5907. <pre><code class="language-rust">mock::builder()
5908.    .set(
5909.        crate::std::env::MockCurrentExe,
5910.        "work_dir/crashreporter".into(),
5911.    )
5912.    .run(|| crash_reporter_main())
5913. </code></pre>
5914. <p>in tests, and</p>
5915. <pre><code class="language-rust">pub fn current_exe() -> std::io::Result {
5916.    Ok(MockCurrentExe.get(|r| r.clone()))
5917. }
5918. </code></pre>
5919. <p>in our <tt>crate::std::env</tt> implementation.</p>
5920. <h4>Testing</h4>
5921. <p>With our mocking setup and test UI, we are able to extensively test the behavior of the crash reporter. The “last mile” of this testing which we can’t automate easily is whether each UI implementation faithfully represents the UI model. We manually test this with a mocked GUI for each platform.</p>
5922. <p>Besides that, we are able to automatically test how arbitrary UI interactions cause the crash reporter to affect its own UI state and the environment (checking which programs are invoked and network connections are made, what happens if they fail, succeed, or timeout, etc). We also set up a mock filesystem and add assertions in various scenarios over the precise resulting filesystem state once the crash reporter completes. This greatly increases our confidence in the current behaviors and ensures that future changes will not alter them, which is of the utmost importance for such an essential component of our crash reporting pipeline.</p>
5923. <h3>The End Product</h3>
5924. <p>Of course we can’t get away with writing all of this without a picture of the crash reporter! This is what it looks like on Linux using GTK. The other GUI implementations look the same but styled with a native look and feel.</p>
5925. <p><img alt="The crash reporter dialog on Linux." class="alignnone wp-image-48136 size-large" height="356" src="https://hacks.mozilla.org/wp-content/uploads/2024/04/crashreporter-500x356.png" width="500" /></p>
5926. <p>Note that, for now, we wanted to keep it looking exactly the same as it previously did. So if you are unfortunate enough to see it, it shouldn’t appear as if anything has changed!</p>
5927. <p>With a new, cleaned up crash reporter, we can finally unblock a number of feature requests and bug reports, such as:</p>
5928. <ul>
5929. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1821414">detecting whether an installation is corrupt and telling the user to re-install Firefox</a>,</li>
5930. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1565033">checking whether there is faulty memory hardware on the crashing system</a>, and</li>
5931. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1866863">using the Firefox network stack for the first attempt at submitting crashes (which respects user network settings like proxies)</a>.</li>
5932. </ul>
5933. <p>We are excited to iterate and improve further on crash reporter functionality. But ultimately it’d be wonderful if you never see or use it, and we are constantly working toward that goal!</p>
5934. &lt;p&gt;The post &lt;a href=&quot;https://hacks.mozilla.org/2024/04/porting-a-cross-platform-gui-application-to-rust/&quot;&gt;Porting a cross-platform GUI application to Rust&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>
5935. <pubDate>Tue, 23 Apr 2024 19:08:08 +0000</pubDate>
5936. <dc:creator>Alex Franchuk</dc:creator>
5937. </item>
5938. <item>
5939. <title>Firefox Nightly: Wall to Wall Improvements – These Weeks in Firefox: Issue 159</title>
5940. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1620</guid>
5941. <link>https://blog.nightly.mozilla.org/2024/04/23/wall-to-wall-improvements-these-weeks-in-firefox-issue-159/</link>
5942. <description>&lt;h3&gt;Highlights&lt;/h3&gt;
5943. <ul>
5944. <li>The team is in the early stages of adding wallpaper support! This is still very preliminary, but you can test what they’ve currently landed on Nightly:
5945. <ul>
5946. <li>Set <code>browser.newtabpage.activity-stream.newtabWallpapers.enabled</code> to true in about:config</li>
5947. <li>Click on the “gear” icon in the top-right of the new tab page</li>
5948. <li>Choose a wallpaper! Note that you get different options depending on whether or not you’re using a light or dark theme.</li>
5949. </ul>
5950. </li>
5951. </ul>
5952. <div class="wp-caption aligncenter" id="attachment_1616" style="width: 1006px;"><img alt="Firefox's New Tab page with a beautiful image of the aurora borealis set as the background wallpaper" class="size-full wp-image-1616" height="740" src="https://blog.nightly.mozilla.org/files/2024/04/image2.png" width="996" /><p class="wp-caption-text" id="caption-attachment-1616">Set a new look for new tabs!</p></div>
5953. <ul>
5954. <li>Among other things, Firefox 125 is going to ship with support for the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Popover_API">Popover Web API</a>
5955. <ul>
5956. <li>This should make it easier to create dropdown / popup menus without doing so much management with JavaScript. <a href="https://mdn.github.io/dom-examples/popover-api/">Here are some demos</a>.</li>
5957. </ul>
5958. </li>
5959. <li>Niklas <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1864038">added keyboard shortcuts</a> for copying and downloading a screenshot in the Screenshots tool
5960. <ul>
5961. <li>The keyboard shortcuts work in the overlay and in the preview window
5962. <ul>
5963. <li><code>ctrl/cmd + c</code> to copy the screenshot</li>
5964. <li><code>ctrl/cmd + s</code> to download/save the screenshot</li>
5965. </ul>
5966. </li>
5967. </ul>
5968. </li>
5969. <li>Nicolas fixed some <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886818">performance</a> <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886947">issues</a> in the Rules view in the Firefox DevTools Inspector tab when there are <b>a lot</b> of rules with pseudo elements. For example, with 1500 pseudo elements, what was taking <b>3 seconds</b> on a developer machine now only takes <b>~30ms! </b>These fixes are slated to go out in Firefox 126.</li>
5970. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1356686">jesup moved brotli decompression fully off of the main thread.</a> This has shown major wins in the wild – <a href="https://glam.telemetry.mozilla.org/firefox/probe/perf_first_contentful_paint_from_responsestart_ms/explore?currentPage=1&os=Windows&ref=20240318110542&visiblePercentiles=%5B99.9%2C99%2C95%2C75%2C50%2C25%2C5%5D">we’re seeing a 10% improvement for FirstContentfulPaint</a> pretty much across the board, and a <a href="https://glam.telemetry.mozilla.org/firefox/probe/perf_largest_contentful_paint_from_response_start_ms/explore?currentPage=1&os=Windows&ref=20240319215652">10% improvement on LargestContentfulPaint</a> at the 50% percentile, 20% at the 75% percentile and 95%(!) at the 95% percentile. Nice! This improvement is rolling out in Firefox 126.</li>
5971. </ul>
5972. <h3>Friends of the Firefox team</h3>
5973. <div>
5974. <div>
5975. <h4 dir="ltr" id="m_2704358428833711463gmail-docs-internal-guid-ef3a8f36-7fff-eb59-ec7a-5ab8df1d7e62">Introductions/Shout-Outs</h4>
5976. <ul>
5977. <li>Shoutout to Yi Xiong Wong for submitting <strong>16 patches</strong> to refactor a bunch of <code>browser.js</code> code into a separate file (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1880914" rel="noopener" target="_blank">bug</a>)</li>
5978. </ul>
5979. </div>
5980. </div>
5981. <h4><a href="https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20(excluding%20employees)&quicksearch=1856717%2C1888221%2C1887529%2C1887821%2C1889710%2C1887543%2C1886858%2C1838152%2C1883058%2C1876286%2C1880914">Resolved bugs (excluding employees)</a></h4>
5982. <h4>Volunteers that fixed more than one bug</h4>
5983. <ul>
5984. <li>Camille</li>
5985. <li>Magnus Melin [:mkmelin]</li>
5986. <li>Meera Murthy</li>
5987. </ul>
5988. <h4>New contributors (🌟 = first patch)</h4>
5989. <ul>
5990. <li>🌟 Camille added <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1856717">`text-align: start` to moz-message-bar</a> so it doesn’t inherit alignment from parent and updated <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883058">moz-toggle to only show active state</a> when hovering</li>
5991. <li>gravyant <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1838152">improved error message</a> when sending session.new without capabilities</li>
5992. <li>🌟 Harshit <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888221">replaced `validateURL`</a> with `URL.parse()`</li>
5993. </ul>
5994. <h3>Project Updates</h3>
5995. <h4>Add-ons / Web Extensions</h4>
5996. <h5>WebExtension APIs</h5>
5997. <ul>
5998. <li>As part of the ongoing work related to improving cross-browser compatibility for Manifest Version 3 extensions:
5999. <ul>
6000. <li>The <code>options_page</code> manifest property is supported as an alias of <code>options_page.ui</code> – <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1816960">Bug 1816960</a></li>
6001. <li>A new <code>webRequestAuthProvider</code> permission allows extensions to register  webRequest.onAuthRequired blocking listeners (in addition to the <code>webRequestBlocking</code> permission, which is deprecated on Chrome but still supported by Firefox) – <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1820569">Bug 1820569</a></li>
6002. <li><code>commands.onCommand</code> listeners now receive details of the currently active tab – <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1843866">Bug 1843866</a></li>
6003. <li>WebExtensions with a granted active tab permission can now call <code>tabs.captureVisibleTab</code> API method without any additional host permissions – <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1784920">Bug 1784920</a></li>
6004. <li>MessageSender details received by <code>runtime.onMessage/runtime.onConnect</code> listeners include a new <code>origin</code> property – <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1787379">Bug 1787379</a></li>
6005. </ul>
6006. </li>
6007. </ul>
6008. <h4>Developer Tools</h4>
6009. <h5>DevTools</h5>
6010. <ul>
6011. <li>Artem Manushenkov added a setting to disable the split console (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1731635">#1731635</a>)</li>
6012. <li>Yury added support for <a href="https://github.com/WebAssembly/exception-handling/">Wasm exception handling proposal</a> in the Debugger (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885589">#1885589</a>)</li>
6013. <li>Emilio fixed a rendering issue that could happen after exiting Responsive Design Mode (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888242">#1888242</a>)</li>
6014. <li>Alex migrated the last DevTools JSMs to ESMs (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1789981">#1789981</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1827382">#1827382</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888171">#1888171</a>)</li>
6015. <li>Nicolas improved performance of the Inspector when modifying a single rule, in a stylesheet with a lot of rules (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888079">#1888079</a>, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888081">#1888081</a>)</li>
6016. <li>Nicolas improved the Rules view by showing the color picker button on color functions using CSS variables in their definition (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1718894">#1718894</a>)</li>
6017. <li>Bomsy fixed a crash in the netmonitor (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884571">#1884571</a>)</li>
6018. <li>Julian reverted the location of DevTools screenshots on OSX to match where Firefox screenshots are saved (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1845037">#1845037</a>)</li>
6019. <li>Nicolas added <code>@property</code> rules (enabled on Nightly by default) in the Style Editor sidebar (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886392">#1886392</a>)</li>
6020. </ul>
6021. <h5>WebDriver BiDi</h5>
6022. <ul>
6023. <li>New contributor: <a href="https://bugzilla.mozilla.org/user_profile?user_id=752453">:gravyant</a> improved the error message when the session.new command is used without a proper capabilities parameter (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1838152">#1838152</a>)</li>
6024. <li><a href="https://bugzilla.mozilla.org/user_profile?user_id=559949">Julian Descottes</a> added support for the <code>contexts</code> argument of the network.addIntercept command which allows to restrict a network intercept to a set of top-level browsing contexts (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1882260">#1882260</a>)</li>
6025. <li><a href="https://bugzilla.mozilla.org/user_profile?user_id=704132">Sasha Borovova</a> updated the <code>storage.getCookies</code> command to return third party cookies selectively, based on the value of the network.cookie.cookieBehavior and <code>network.cookie.cookieBehavior.optInPartitioning</code> preferences (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1879503">#1879503</a>)</li>
6026. <li><a href="https://bugzilla.mozilla.org/user_profile?user_id=704132">Sasha Borovova</a> removed the <code>ownership</code> and <code>sandbox</code> parameters for the <code>browsingContext.locateNodes</code> command to align with a recent specification update (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884935">#1884935</a>)</li>
6027. <li><a href="https://bugzilla.mozilla.org/user_profile?user_id=704132">Sasha Borovova</a> updated the <code>session.subscribe</code> and <code>session.unsubscribe</code> commands to throw an error when the events or contexts parameters are empty arrays (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1887871">#1887871</a>)</li>
6028. <li>The team completed the Milestone 10 of the project (<a href="https://bugzilla.mozilla.org/buglist.cgi?f5=status_whiteboard&f4=short_desc&f1=classification&query_format=advanced&list_id=16990273&v1=Graveyard&f6=CP&o5=substring&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&j3=OR&f7=CP&o4=substring&v5=webdriver%3Am10%5D&f3=OP&v4=webdriver%3Am10%5D&o1=notequals&f2=OP">bug list</a>), where we implemented 50% of the commands needed to completely support Puppeteer, with 75% of the Puppeteer unit-tests passing with WebDriver BiDi. For Milestone 11 (<a href="https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%5Bwebdriver%3Am11&list_id=16990274">bug list</a>), our focus remains to implement the remaining commands and features required to fully support Puppeteer (<a href="https://docs.google.com/document/d/1dDl1038bCehxUEot-21_bn_zn8uRCidjpXZ0SxwU-Ng/edit">doc</a>).</li>
6029. </ul>
6030. <h4>Lint, Docs and Workflow</h4>
6031. <ul>
6032. <li>Enabling ESLint rules for requiring JSDocs just got easier.
6033. <ul>
6034. <li>The rules are <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1799465">now enabled by default</a>.</li>
6035. <li>Places where there are currently failures are <a href="https://searchfox.org/mozilla-central/rev/77f8c66362e5f18f8e7cbaf1ba3ed6286f203d33/.eslintrc.js#631-797">explicitly disabled</a> in the top-level .eslintrc.js file.</li>
6036. <li>Please consider enabling these (and the valid-jsdoc ones) on your area, especially if you are using (or will be using) <a href="https://firefox-source-docs.mozilla.org/tools/moztreedocs/jsdoc-support.html">JSDoc document generation</a> for source docs.</li>
6037. </ul>
6038. </li>
6039. <li>eslint-plugin-mozilla <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890330">now supports ESLint v9 APIs</a>.
6040. <ul>
6041. <li>We still have some work to complete to fully support the new flat configuration.</li>
6042. </ul>
6043. </li>
6044. <li>We’re now rejecting the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889087">JSM based ChromeUtils.import across the tree</a> via ESLint.</li>
6045. </ul>
6046. <h4>Migration Improvements</h4>
6047. <ul>
6048. <li>Negin <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889703">fixed an issue</a> where the migration wizard title wasn’t appearing when embedded in about:welcome</li>
6049. <li>Negin is working on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886362">fixing an issue on about:welcome</a> where clicking on the browser/profile selector when the panel is already open doesn’t close the panel.</li>
6050. <li>For the backup project, we’ve made some pretty big strides!
6051. <ul>
6052. <li>We closed out <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883503">the measurement metabug</a>, and have the measurements <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886174">being collected by default</a> starting in Firefox 126.</li>
6053. <li>We’re now staging backups for various resources
6054. <ul>
6055. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885939">User preferences</a></li>
6056. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885609">The Places databases (history, bookmarks, favicons)</a></li>
6057. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885929">Credentials (passwords, certificates, payment methods, addresses)</a></li>
6058. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885944">A bunch of miscellaneous data stores</a></li>
6059. </ul>
6060. </li>
6061. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888491">We added a very simple debug tool</a> in Nightly at <code>chrome://browser/content/backup/debug.html</code>. You can test staging a backup at runtime with what we have so far using this tool. It may take several minutes depending on how big your databases are, and how intensely you’re using the browser while the backup is underway.</li>
6062. </ul>
6063. </li>
6064. </ul>
6065. <h4>Picture-in-Picture</h4>
6066. <ul>
6067. <li>Thanks to :joe.scott.webster for submitting a patch that fixes PiP captions issues with several Yahoo sites (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1825105">bug</a>) and filing a follow-up ticket for AOL (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1891599">bug</a>).
6068. <ul>
6069. <li>Also thanks to Niklas Baumgardner (:niklas) for lending a hand!</li>
6070. </ul>
6071. </li>
6072. </ul>
6073. <h4>Performance</h4>
6074. <ul>
6075. <li>mconley <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1879136">got rid of some nsTerminator telemetry that was causing us to block shutting down the browser if a quit was requested very soon after a startup.</a></li>
6076. </ul>
6077. <h4>Screenshots (enabled by default in Nightly)</h4>
6078. <ul>
6079. <li>Niklas made the save full page the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886843">primary action button</a>
6080. <ul>
6081. <li>Thanks reusable components for moz-button-group!</li>
6082. </ul>
6083. </li>
6084. <li>Niklas fixed an issue where <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889438">dragging the scrollbar could drag a region</a></li>
6085. <li>Niklas fixed an issue where <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889473">the window would sometimes scroll</a> when focusing the download or copy button</li>
6086. </ul>
6087. <h4>Search and Navigation</h4>
6088. <ul>
6089. <li>Firefox Suggest experience
6090. <ul>
6091. <li>Daisuke renamed the “Learn More about Firefox Suggest” menuitem to a more direct “Manage Firefox Suggest”. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889820">Bug 1889820</a></li>
6092. <li>Drew added new telemetry to measure in experiments the potential exposure of simulated results, depending on the typed search string. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1881875">Bug 1881875</a></li>
6093. </ul>
6094. </li>
6095. <li>SERP categorization telemetry
6096. <ul>
6097. <li>James, Stephanie and Karandeep have landed many fixes to the storage, logging and measurements.</li>
6098. </ul>
6099. </li>
6100. <li>Search Config v2
6101. <ul>
6102. <li>Enabling new config in Nightly lowered the number of initialization errors for the Search Service</li>
6103. <li>Mark fixed character-set handling. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890698">Bug 1890698</a></li>
6104. <li>Mark added a new property covering the device type. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889910">Bug 1889910</a></li>
6105. <li>Mandy sorted collections by engine identifier and property names, to make the config more easily navigable and diffs nicer and easier to maintain. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889247">Bug 1889247</a></li>
6106. <li>Mandy updated the <a href="https://firefox-source-docs.mozilla.org/toolkit/search/index.html">documentation</a>. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889037">Bug 1889037</a></li>
6107. </ul>
6108. </li>
6109. <li>Other fixes
6110. <ul>
6111. <li>Marco fixed a bug causing engagement on certain results to be registered both as engagement and abandonment. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1888627">Bug 1888627</a></li>
6112. <li>Dao has fixed alignment of “switch to tab” and “visit” chiclets. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886761">Bug 1886761</a></li>
6113. </ul>
6114. </li>
6115. </ul>
6116. <h4>Storybook/Reusable Components</h4>
6117. <ul>
6118. <li>Thanks to Camille Davis for fixing these two bugs!
6119. <ul>
6120. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1856717">Bug 1856717 – Set ‘text-align: start’ on ‘:host’ in moz-message-bar.css</a></li>
6121. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883058">Bug 1883058 – moz-toggle should only show active state on hover</a></li>
6122. </ul>
6123. </li>
6124. <li>Thanks to :nordzilla for <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886276">fixing a race condition in menulist</a></li>
6125. <li>Thanks to :kcochrane for <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883091">adding documentation to moz-page-nav</a> and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1877826">adding support for external and support links in moz-page-nav</a></li>
6126. <li>:hjones <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1890433">fixed the interactive storybook component examples on Windows</a></li>
6127. <li>:tgiles <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1889469">fixed the ./mach addstory command</a></li>
6128. <li>Work is underway to remove the <code>window.ensureCustomElements</code> function now that we can lazy load ES modules. See <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1803678">Bug 1803678 – Enable on-demand/lazy loading for ESModule based reusable components</a> for more details
6129. <ul>
6130. <li>Big thanks to :arai for the work to make this possible! <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1803810">Bug 1803810 – Support synchronously loading ESMs into given global, in the same way as Services.scriptloader.loadSubScript</a></li>
6131. </ul>
6132. </li>
6133. &lt;/ul&gt;</description>
6134. <pubDate>Tue, 23 Apr 2024 17:32:41 +0000</pubDate>
6135. <dc:creator>Katherine Patenio</dc:creator>
6136. </item>
6137. <item>
6138. <title>Firefox Nightly: Firefox Nightly Now Available for Linux on ARM64</title>
6139. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1595</guid>
6140. <link>https://blog.nightly.mozilla.org/2024/04/19/firefox-nightly-now-available-for-linux-on-arm64/</link>
6141. <description>&lt;p&gt;We’re excited to share an update with people running Linux on ARM64 (also known as AArch64) architectures.&lt;/p&gt;
6142. <h3>ARM64 Binaries Are Here</h3>
6143. <p>After <a href="https://blog.nightly.mozilla.org/2023/10/30/introducing-mozillas-firefox-nightly-deb-packages-for-debian-based-linux-distributions/">launching the Firefox Nightly .deb package</a>, feedback highlighted a demand for ARM64 builds. In response, we’re excited to now offer Firefox Nightly for ARM64 as both <code>.tar</code> archives and <code>.deb</code> packages. Keep the suggestions coming – feedback is always welcome!</p>
6144. <ul>
6145. <li><strong>.tar Archives: </strong>Prefer our traditional <code>.tar.bz2</code> binaries? You can get them from <a href="https://www.mozilla.org/firefox/all/#product-desktop-nightly">our downloads page</a> by selecting <code>Firefox Nightly</code> for <code>Linux ARM64/AArch64</code>.</li>
6146. <li><strong>.deb Packages: </strong>For updates and installation via our APT repository, you can <a href="https://support.mozilla.org/kb/install-firefox-linux#w_install-firefox-deb-package-for-debian-based-distributions">follow these instructions</a> and install the <code>firefox-nightly</code> package.</li>
6147. </ul>
6148. <h3>On ARM64 Build Stability</h3>
6149. <p>We want to be upfront about the current state of our ARM64 builds. Although we are confident in the quality of Firefox on this architecture, we are still incorporating comprehensive ARM64 testing into Firefox’s continuous integration and release pipeline. Our goal is to integrate ARM64 builds into Firefox’s extensive automated test suite, which will enable us to offer this architecture across the beta, release, and ESR channels.</p>
6150. <h3>Your Feedback Is Crucial</h3>
6151. &lt;p&gt;We encourage you to download the new ARM64 Firefox Nightly binaries, test them, and share your findings with us. By using these builds and reporting any issues, you’re empowering our developers to better support and test on this architecture, ultimately leading to a stable and reliable Firefox for ARM64. Please share your findings through &lt;a href=&quot;https://bugzilla.mozilla.org/enter_bug.cgi?format=__default__&amp;amp;blocked=1867368&amp;amp;product=Release%20Engineering&amp;amp;component=General&amp;amp;rep_platform=ARM64&amp;amp;op_sys=Linux&quot;&gt;Bugzilla&lt;/a&gt; and stay tuned for more updates. Thank you for your ongoing participation in the Firefox Nightly community!&lt;/p&gt;</description>
6152. <pubDate>Fri, 19 Apr 2024 17:35:32 +0000</pubDate>
6153. <dc:creator>Gabriel Bustamante</dc:creator>
6154. </item>
6155. <item>
6156. <title>IRL (podcast): Mozilla’s IRL podcast is a Shorty Awards finalist - we need your help to win!</title>
6157. <guid isPermaLink="false">63cfa320-a1c6-47d7-9b08-0bda89510d45</guid>
6158. <link>https://irlpodcast.org/</link>
6159. <description>&lt;p&gt;We’re excited to share that Mozilla's IRL podcast is a &lt;a href=&quot;https://shortyawards.com/16th/irl-online-life-is-real-life-season-7&quot;&gt;Shorty Awards finalist&lt;/a&gt; in the Science and Technology Podcast category! If you enjoy IRL you can show your support by voting for us.&lt;/p&gt;&lt;p&gt;The Shorty Awards recognizes great content by brands, agencies and nonprofits. It’s really an honor to be able to feature the voices and stories of the folks who are putting people over profit in AI. A Shorty Award will help bring these stories to even more listeners. &lt;/p&gt;&lt;p&gt;&lt;strong&gt;How to vote&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;1. Go to &lt;a href=&quot;http://mzl.la/shorty&quot;&gt;mzl.la/shorty&lt;/a&gt;&lt;/p&gt;&lt;p&gt;2. Click 'Vote in Science and Technology Podcast'&lt;/p&gt;&lt;p&gt;3. create a username and password (it's easy, we promise!)&lt;/p&gt;&lt;p&gt;4. Come back and &lt;strong&gt;vote every day until April 30th&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;We believe putting people over profit is award-worthy. Don’t you?  Thanks for your support!&lt;/p&gt;</description>
6160. <pubDate>Fri, 19 Apr 2024 16:51:37 +0000</pubDate>
6161. <author>info@pacific-content.com (Mozilla)</author>
6162.        <enclosure url="https://cdn.simplecast.com/audio/9b52b824-909f-4be5-aaf0-10f9e93c7818/episodes/c6f576bb-c082-4e2f-903d-3e95735862fc/audio/4e2e64e8-2066-42bf-9243-3bda4505bfb9/default_tc.mp3?aid=rss_feed&amp;feed=lP7owBq8" length="6037192" type="audio/mpeg"/>
6163. </item>
6164. <item>
6165. <title>Mozilla Thunderbird: Adventures In Rust: Bringing Exchange Support To Thunderbird</title>
6166. <guid isPermaLink="false">https://blog.thunderbird.net/?p=1702</guid>
6167. <link>https://blog.thunderbird.net/2024/04/adventures-in-rust-bringing-exchange-support-to-thunderbird/</link>
6168. <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/2024/04/Tb-rust1.png&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
6169. <p>Microsoft Exchange is a popular choice of email service for corporations and educational institutions, and so it’s no surprise that there’s demand among Thunderbird users to support Exchange. Until recently, this functionality was only available through an add-on. But, in the next ESR (Extended Support) release of Thunderbird in July 2024, we expect to provide this support natively within Thunderbird. Because of the size of this undertaking, the first roll-out of the Exchange support will <a href="https://youtu.be/7jNV1J2pdPc">initially cover only email</a>, with calendar and address book support coming at a later date.</p>
6170.  
6171.  
6172.  
6173. <p>This article will go into technical detail on how we are implementing support for the Microsoft Exchange Web Services mail protocol, and some idea of where we’re going next with the knowledge gained from this adventure.</p>
6174.  
6175.  
6176.  
6177. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
6178.  
6179. </div></figure>
6180.  
6181.  
6182.  
6183. <h3>Historical context</h3>
6184.  
6185.  
6186.  
6187. <p>Thunderbird is a long-lived project, which means there’s lots of old code. The current architecture for supporting mail protocols predates Thunderbird itself, having been developed more than 20 years ago as part of Netscape Communicator. There was also no paid maintainership from about 2012 — when Mozilla divested and  transferred ownership of Thunderbird to its community — until 2017, when Thunderbird rejoined the Mozilla Foundation. That means years of ad hoc changes without a larger architectural vision and a lot of decaying C++ code that was not using modern standards.</p>
6188.  
6189.  
6190.  
6191. <p>Furthermore, in the entire 20 year lifetime of the Thunderbird project, no one has added support for a new mail protocol before. As such, no one has updated the architecture as mail protocols change and adapt to modern usage patterns, and a great deal of institutional knowledge has been lost. Implementing this much-needed feature is the first organization-led effort to actually understand and address limitations of Thunderbird’s architecture in an incremental fashion.</p>
6192.  
6193.  
6194.  
6195. <h3>Why we chose Rust</h3>
6196.  
6197.  
6198.  
6199. <p>Thunderbird is a large project maintained by a small team, so choosing a language for new work cannot be taken lightly. We need powerful tools to develop complex features relatively quickly, but we absolutely must balance this with long-term maintainability. Selecting Rust as the language for our new protocol support brings some important benefits:</p>
6200.  
6201.  
6202.  
6203. <ol>
6204. <li><strong>Memory safety.</strong> Thunderbird takes input from anyone who sends an email, so we need to be diligent about keeping security bugs out.</li>
6205.  
6206.  
6207.  
6208. <li><strong>Performance.</strong> Rust runs as native code with all of the associated performance benefits.</li>
6209.  
6210.  
6211.  
6212. <li><strong>Modularity and Ecosystem.</strong> The built-in modularity of Rust gives us access to a large ecosystem where there are already a lot of people doing things related to email which we can benefit from.</li>
6213. </ol>
6214.  
6215.  
6216.  
6217. <p>The above are all on the standard list of benefits when discussing Rust. However, there are some additional considerations for Thunderbird:</p>
6218.  
6219.  
6220.  
6221. <ol>
6222. <li><strong>Firefox.</strong> Thunderbird is built on top of Firefox code and we use a shared CI infrastructure with Firefox which already enables Rust. Additionally, Firefox provides a language interop layer called XPCOM (Cross-Platform Component Object Model), which has Rust support and allows us to call between Rust, C++, and JavaScript.</li>
6223.  
6224.  
6225.  
6226. <li><strong>Powerful tools.</strong> Rust gives us a large toolbox for building APIs which are difficult to misuse by pushing logical errors into the domain of the compiler. We can easily avoid circular references or provide functions which simply cannot be called with values which don’t make sense, letting us have a high degree of confidence in features with a large scope. Rust also provides first-class tooling for documentation, which is critically important on a small team.</li>
6227.  
6228.  
6229.  
6230. <li><strong>Addressing architectural technical debt.</strong> Introducing a new language gives us a chance to reconsider some aging architectures while benefiting from a growing language community.</li>
6231.  
6232.  
6233.  
6234. <li><strong>Platform support and portability.</strong> Rust supports a broad set of host platforms. By building modular crates, we can reuse our work in other projects, such as Thunderbird for Android/K-9 Mail.</li>
6235. </ol>
6236.  
6237.  
6238.  
6239. <h4>Some mishaps along the way</h4>
6240.  
6241.  
6242.  
6243. <p>Of course, the endeavor to introduce our first Rust component in Thunderbird is not without its challenges, mostly related to the size of the Thunderbird codebase. For example, there is a lot of existing code with idiosyncratic asynchronous patterns that don’t integrate nicely with idiomatic Rust. There are also lots of features and capabilities in the Firefox and Thunderbird codebase that don’t have any existing Rust bindings.</p>
6244.  
6245.  
6246.  
6247. <h5>The first roadblock: the build system</h5>
6248.  
6249.  
6250.  
6251. <p>Our first hurdle came with getting any Rust code to run in Thunderbird at all. There are two things you need to know to understand why:</p>
6252.  
6253.  
6254.  
6255. <p>First, since the Firefox code is a dependency of Thunderbird, you might expect that we pull in their code as a subtree of our own, or some similar mechanism. However, for historical reasons, it’s the other way around: building Thunderbird requires fetching Firefox’s code, fetching Thunderbird’s code as a subtree of Firefox’s, and using a build configuration file to point into that subtree.</p>
6256.  
6257.  
6258.  
6259. <p>Second, because Firefox’s entrypoint is written in C++ and Rust calls happen via an interoperability layer, there is no single point of entry for Rust. In order to create a tree-wide dependency graph for Cargo and avoid duplicate builds or version/feature conflicts, Firefox introduced a hack to generate a single Cargo workspace which aggregates all the individual crates in the tree.</p>
6260.  
6261.  
6262.  
6263. <p>In isolation, neither of these is a problem in itself. However, in order to build Rust into Thunderbird, we needed to define our own Cargo workspace which lives in our tree, and Cargo does not allow nesting workspaces. To solve this issue, we had to define our own workspace and add configuration to the upstream build tool, <code>mach</code>, to build from this workspace instead of Firefox’s. We then use a newly-added <code>mach</code> subcommand to sync our dependencies and lockfile with upstream and to vendor the resulting superset.</p>
6264.  
6265.  
6266.  
6267. <h5>XPCOM</h5>
6268.  
6269.  
6270.  
6271. <p>While the availability of language interop through XPCOM is important for integrating our frontend and backend, the developer experience has presented some challenges. Because XPCOM was originally designed with C++ in mind, implementing or consuming an XPCOM interface requires a lot of boilerplate and prevents us from taking full advantage of tools like rust-analyzer. Over time, Firefox has significantly reduced its reliance on XPCOM, making a clunky Rust+XPCOM experience a relatively minor consideration. However, as part of the previously-discussed maintenance gap, Thunderbird never undertook a similar project, and supporting a new mail protocol requires implementing hundreds of functions defined in XPCOM.</p>
6272.  
6273.  
6274.  
6275. <p>Existing protocol implementations ease this burden by inheriting C++ classes which provide the basis for most of the shared behavior. Since we can’t do this directly, we are instead implementing our protocol-specific logic in Rust and communicating with a bridge class in C++ which combines our Rust implementations (an internal crate called <code>ews_xpcom</code>) with the existing code for shared behavior, with as small an interface between the two as we can manage.</p>
6276.  
6277.  
6278.  
6279. <p>Please visit our <a href="https://source-docs.thunderbird.net/en/latest/rust/index.html" rel="noreferrer noopener" target="_blank">documentation</a> to learn more about how to create Rust components in Thunderbird.</p>
6280.  
6281.  
6282.  
6283. <h3>Implementing Exchange support with Rust</h3>
6284.  
6285.  
6286.  
6287. <p>Despite the technical hiccups experienced along the way, we were able to clear the hurdles, use, and build Rust within Thunderbird. Now we can talk about how we’re using it and the tools we’re building. Remember all the way back to the beginning of this blog post, where we stated that our goal is to support Microsoft’s Exchange Web Services (EWS) API. EWS communicates over HTTP with request and response bodies in XML.</p>
6288.  
6289.  
6290.  
6291. <h4>Sending HTTP requests</h4>
6292.  
6293.  
6294.  
6295. <p>Firefox already includes a full-featured HTTP stack via its <code>necko</code> networking component. However, <code>necko</code> is written in C++ and exposed over XPCOM, which as previously stated does not make for nice, idiomatic Rust. Simply sending a GET request requires a great deal of boilerplate, including nasty-looking unsafe blocks where we call into XPCOM. (XPCOM manages the lifetime of pointers and their referents, ensuring memory safety, but the Rust compiler doesn’t know this.) Additionally, the interfaces we need are callback-based. For making HTTP requests to be simple for developers, we need to do two things:</p>
6296.  
6297.  
6298.  
6299. <ol>
6300. <li><strong>Support native Rust async/await syntax.</strong> For this, we added a new Thunderbird-internal crate, <code>xpcom_async</code>. This is a low-level crate which translates asynchronous operations in XPCOM into Rust’s native async syntax by defining callbacks to buffer incoming data and expose it by implementing Rust’s <code>Future</code> trait so that it can be awaited by consumers. (If you’re not familiar with the <code>Future</code> concept in Rust, it is similar to a JS <code>Promise</code> or a Python coroutine.)</li>
6301.  
6302.  
6303.  
6304. <li><strong>Provide an idiomatic HTTP API.</strong> Now that we had native <code>async</code>/<code>await</code> support, we created another internal crate (<code>moz_http</code>) which provides an HTTP client inspired by <code>reqwest</code>. This crate handles creating all of the necessary XPCOM objects and providing Rustic error handling (much nicer than the standard XPCOM error handling).</li>
6305. </ol>
6306.  
6307.  
6308.  
6309. <h4>Handling XML requests and responses</h4>
6310.  
6311.  
6312.  
6313. <p>The hardest task in working with EWS is translating between our code’s own data structures and the XML expected/provided by EWS. Existing crates for serializing/deserializing XML didn’t meet our needs. <code>serde</code>’s data model doesn’t align well with XML, making distinguishing XML attributes and elements difficult. EWS is also sensitive to XML namespaces, which are completely foreign to <code>serde</code>. Various <code>serde</code>-inspired crates designed for XML exist, but these require explicit annotation of how to serialize every field. EWS defines hundreds of types which can have dozens of fields, making that amount of boilerplate untenable.</p>
6314.  
6315.  
6316.  
6317. <p>Ultimately, we found that existing <code>serde</code>-based implementations worked fine for deserializing XML into Rust, but we were unable to find a satisfactory tool for serialization. To that end, we introduced another new crate, <code>xml_struct</code>. This crate defines traits governing serialization behavior and uses Rust’s procedural derive macros to automatically generate implementations of these traits for Rust data structures. It is built on top of the existing <code>quick_xml</code> crate and designed to create a low-boilerplate, intuitive mapping between XML and Rust.  While it is in the early stages of development, it does not make use of any Thunderbird/Firefox internals and is <a href="https://github.com/thunderbird/xml-struct-rs">available on GitHub</a>.</p>
6318.  
6319.  
6320.  
6321. <p>We have also introduced one more new crate, <code>ews</code>, which defines types for working with EWS and an API for XML serialization/deserialization, based on <code>xml_struct</code> and <code>serde</code>. Like <code>xml_struct</code>, it is in the early stages of development, but is <a href="https://github.com/thunderbird/ews-rs">available on GitHub</a>.</p>
6322.  
6323.  
6324.  
6325. <h4>Overall flow chart</h4>
6326.  
6327.  
6328.  
6329. <p>Below, you can find a handy flow chart to help understand the logical flow for making an Exchange request and handling the response. </p>
6330.  
6331.  
6332.  
6333. <figure class="wp-block-image size-full"><a href="https://blog.thunderbird.net/files/2024/04/pasted-image-.png"><img alt="A bird's eye view of the flow" class="wp-image-1708" height="716" src="https://blog.thunderbird.net/files/2024/04/pasted-image-.png" title="A bird’s eye view of the flow" width="1600" /></a></figure>
6334.  
6335.  
6336.  
6337. <p>Fig 1. A bird’s eye view of the flow</p>
6338.  
6339.  
6340.  
6341. <h3>What’s next?</h3>
6342.  
6343.  
6344.  
6345. <h4>Testing all the things</h4>
6346.  
6347.  
6348.  
6349. <p>Before landing our next major features, we are taking some time to build out our automated tests. In addition to unit tests, we just landed a mock EWS server for integration testing. The current focus on testing is already paying dividends, having exposed a couple of crashes and some double-sync issues which have since been rectified. Going forward, new features can now be easily tested and verified.</p>
6350.  
6351.  
6352.  
6353. <h4>Improving error handling</h4>
6354.  
6355.  
6356.  
6357. <p>While we are working on testing, we are also busy improving the story around error handling. EWS’s error behavior is often poorly documented, and errors can occur at multiple levels (e.g., a request may fail as a whole due to throttling or incorrect structure, or parts of a request may succeed while other parts fail due to incorrect IDs). Some errors we can handle at the protocol level, while others may require user intervention or may be intractable. In taking the time now to improve error handling, we can provide a more polished implementation and set ourselves up for easier long-term maintenance.</p>
6358.  
6359.  
6360.  
6361. <h4>Expanding support</h4>
6362.  
6363.  
6364.  
6365. <p>We are working on expanding protocol support for EWS (via <code>ews</code> and the internal <code>ews_xpcom</code> crate) and hooking it into the Thunderbird UI. Earlier this month, we landed a series of patches which allow adding an EWS account to Thunderbird, syncing the account’s folder hierarchy from the remote server, and displaying those folders in the UI. (At present, this alpha-state functionality is gated behind a build flag and a preference.) Next up, we’ll work on fetching message lists from the remote server as well as generalizing outgoing mail support in Thunderbird.</p>
6366.  
6367.  
6368.  
6369. <h4>Documentation</h4>
6370.  
6371.  
6372.  
6373. <p>Of course, all of our work on maintainability is for naught if no one understands what the code does. To that end, we’re producing documentation on how all of the bits we have talked about here come together, as well as describing the existing architecture of mail protocols in Thunderbird and thoughts on future improvements, so that once the work of supporting EWS is done, we can continue building and improving on the Thunderbird you know and love.</p>
6374.  
6375.  
6376.  
6377. <h5>QUESTIONS FROM YOU</h5>
6378.  
6379.  
6380.  
6381. <h5>EWS is deprecated for removal in 2026. Are there plans to add support for Microsoft Graph into Thunderbird?</h5>
6382.  
6383.  
6384.  
6385. <blockquote class="wp-block-quote">
6386. <p>This is a common enough question that we probably should have addressed it in the post! EWS will no longer be available for Exchange Online in October 2026, but our research in the lead-up to this project showed that there’s a significant number of users who are still using on-premise installs of Exchange Server. That is, many companies and educational institutions are running Exchange Server on their own hardware.</p>
6387. </blockquote>
6388.  
6389.  
6390.  
6391. <blockquote class="wp-block-quote">
6392. <p>These on-premise installs largely support EWS, but they cannot support the Azure-based Graph API. We expect that this will continue to be the case for some time to come, and EWS provides a means of supporting those users for the foreseeable future. Additionally, we found a few outstanding issues with the Graph API (which is built with web-based services in mind, not desktop applications), and adding EWS support allows us to take some extra time to find solutions to those problems before building Graph API support.</p>
6393.  
6394.  
6395.  
6396. <p>Diving into the past has enabled a sound engineering-led strategy for dealing with the future: Thanks to the deep dive into the existing Thunderbird architecture we can begin to leverage more efficient and productive patterns and technologies when implementing protocols.</p>
6397.  
6398.  
6399.  
6400. <p>In time this will have far reaching consequences for the Thunderbird code base which will not only run faster and more reliably, but significantly reduce maintenance burden when landing bug fixes and new features.</p>
6401.  
6402.  
6403.  
6404. <p>Rust and EWS are elements of a larger effort in Thunderbird to reduce turnarounds and build resilience into the very core of the software.</p>
6405. </blockquote>
6406. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2024/04/adventures-in-rust-bringing-exchange-support-to-thunderbird/&quot;&gt;Adventures In Rust: Bringing Exchange Support To Thunderbird&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>
6407. <pubDate>Fri, 19 Apr 2024 16:50:17 +0000</pubDate>
6408. <dc:creator>Sean Burke</dc:creator>
6409. </item>
6410. <item>
6411. <title>Firefox UX: On Purpose: Collectively Defining Our Team’s Mission Statement</title>
6412. <guid isPermaLink="false">https://blog.mozilla.org/ux/?p=4477</guid>
6413. <link>https://blog.mozilla.org/ux/2024/04/on-purpose-collectively-defining-our-teams-mission-statement/</link>
6414. <description>&lt;p class=&quot;pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj&quot; id=&quot;7f2c&quot;&gt;&lt;em class=&quot;aep&quot;&gt;How the Firefox User Research team crafted our mission statement&lt;/em&gt;&lt;/p&gt;
6415. <div class="wp-caption aligncenter" id="attachment_4478" style="width: 788px;"><img alt="Image of person hugging Firefox logo" class=" wp-image-4478" height="589" src="https://blog.mozilla.org/ux/files/2024/04/firefox-hug-300x227.jpg" width="778" /><p class="wp-caption-text" id="caption-attachment-4478">Firefox illustration by UX designer <a href="https://www.gbrielle.design/">Gabrielle Lussier</a></p></div>
6416. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="6b08">Like many people who work at Mozilla, I’m inspired by the <a class="af jo" href="https://www.mozilla.org/en-US/mission/" rel="noopener ugc nofollow" target="_blank">organization’s mission</a>: <em class="aep">to ensure the Internet is a global public resource, open and accessible to all</em>. In thinking about the team I belong to, though, what’s our piece of this bigger puzzle?</p>
6417. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="8035">The Firefox User Research team tackled this question early last year. We gathered in person for a week of team-focused activities; defining a team mission statement was on the agenda. As someone who enjoys workshop creation and strategic planning, I was on point to develop the workshop. The end goal? A team-backed statement that communicated our unique purpose and value.</p>
6418. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="85c6">Mission statement development was new territory for me. I read up on approaches for creating them and landed on a workshop design (adapted from <a class="af jo" href="https://itk.mitre.org/toolkit-tools/mission-and-vision-canvas/" rel="noopener ugc nofollow" target="_blank">MITRE’s Innovation Toolkit</a>) that would enable the team to participate in a process of collectively reflecting on our work and defining our shared purpose.</p>
6419. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="2627">To my delight, the workshop was fruitful and engaging. Not only did it lead us to a statement that resonates, it sparked meaningful discussion along the way.</p>
6420. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="b135">Here, I outline the <strong class="adw jx">five workshop activities </strong>that guided us there.</p>
6421. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="252e"><strong class="adw jx">1) Discuss the value of a good mission statement</strong></p>
6422. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="861a">We kicked off the workshop by discussing the value of a well-crafted statement. Why were we aiming to define one in the first place? Benefits include: fostering alignment between the team’s activities and objectives, communicating the team’s purpose, and helping the team to cohere around a shared direction. In contrast to a vision statement, which describes future conditions in aspirational language, a mission statement describes present conditions in concrete terms.</p>
6423. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="9804">In our case, the team had recently grown in size to thirteen people. We had a fairly new leadership team, along with a few new members of the team. With a mix of longer tenure and newer members, and quantitative and mixed methods researchers (which at one point in the past had been on separate teams), we wanted to inspire team alignment around our shared goals and build bridges between team members.</p>
6424. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="9378"><strong class="adw jx">2) Individually answer a set of questions about our team’s work</strong></p>
6425. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="d613">Large sheets of paper were set up around the room with the following questions:</p>
6426. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="7dd2">A. What do we, as a user research team, do?</p>
6427. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="cc8c">B. How do we do what we do?</p>
6428. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="c133">C. What value do we bring?</p>
6429. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="ea1c">D. Who benefits from our work?</p>
6430. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="abfd">E. Why does our team exist?</p>
6431. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="1f72">Markers in hand, team members dispersed around the room, spending a few minutes writing answers to each question until we had cycled through them all.</p>
6432. <div class="wp-caption aligncenter" id="attachment_4479" style="width: 775px;"><img alt="People in a workshop" class=" wp-image-4479" height="574" src="https://blog.mozilla.org/ux/files/2024/04/IMG_25821-300x225.jpg" width="765" /><p class="wp-caption-text" id="caption-attachment-4479">Team members during the workshop</p></div>
6433. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="d0f0"><strong class="adw jx">3) Highlight keywords and work in groups to create draft statements</strong></p>
6434. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="8431">Small groups were formed and were tasked with highlighting keywords from the answers provided in the previous step. These keywords served as the foundation for drafting statements, with the following format provided as a helpful guide:</p>
6435. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="9344">Our mission is to (A — <em class="aep">what we do</em>) by (B — <em class="aep">how we do it</em>).</p>
6436. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="d66a">We (C <em class="aep">— the value we bring</em>) so that (D — <em class="aep">who benefits from our work</em> ) can (E — <em class="aep">why we exist</em>).</p>
6437. <div class="wp-caption aligncenter" id="attachment_4480" style="width: 591px;"><img alt="" class=" wp-image-4480" height="775" src="https://blog.mozilla.org/ux/files/2024/04/IMG_2585-2-300x400.jpg" width="581" /><p class="wp-caption-text" id="caption-attachment-4480">One group’s draft statement from Step 3</p></div>
6438. <article>
6439. <div class="l">
6440. <div class="l">
6441. <section>
6442. <div>
6443. <div class="kd lo mf zn zo">
6444. <div class="ab cl">
6445. <div class="cm bg cn co cp cq">
6446. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="99bc"><strong class="adw jx">4) Review and discuss resulting statements</strong></p>
6447. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="7ee9">Draft statements emerged remarkably fluidly from the activities in Steps 2 and 3. Common elements were easy to identify (we develop insights and shape product decisions), while the differences sparked worthwhile discussions. For example: How well does the term ‘human-centered’ capture the work of our quantitative researchers? Is creating empathy for our users a core part of our purpose? How does our value extend beyond impacting product decisions?</p>
6448. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="53dc">As a group, we reviewed and discussed the statements, crossing out any jargony terms and underlining favoured actions and words. After this step, we knew we were close to a final statement. We concluded the workshop, with a plan to revisit the statements when we were back to work the following week.</p>
6449. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="2588"><strong class="adw jx">5) Refine and share for feedback</strong></p>
6450. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="3866">The following week, we refined our work and shared the outcome with the lead of our Content Design practice for review. Her sharp feedback included encouraging us to change the phrase ‘<em class="aep">informing </em>strategic decisions’ to ‘<em class="aep">influencing</em> strategic decisions’ to articulate our role as less passive — a change we were glad to make. After another round of editing, we arrived at our final mission statement:</p>
6451. <blockquote class="afh afi afj">
6452. <p class="adu adv aep adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="40b1"><strong class="adw jx">Our mission is to influence strategic decisions through systematic, qualitative, and quantitative research. We develop insights that uncover opportunities for Mozilla to build an open and healthy internet for all.</strong></p>
6453. </blockquote>
6454. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="e4b4"><strong class="adw jx">Closing thoughts</strong></p>
6455. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="1bab">If you’re considering involving your team in defining a team mission statement, it makes for a rewarding workshop activity. The five steps presented in this article give team members the opportunity to reflect on important foundational questions (what value do we bring?), while deepening mutual understanding.</p>
6456. <p class="pw-post-body-paragraph adu adv zq adw b adx ady adz aea aeb aec aed aee wn aef aeg aeh wq aei aej aek wt ael aem aen aeo kd bj" id="ea14">Crafting a team mission statement was much less of an exercise in wordsmithing than I might have assumed. Instead, it was an exercise in aligning on the bigger questions of why we exist and who benefits from our work. I walked away with a better understanding of the value our team brings to Mozilla, a clearer way to articulate how our work ladders up to the organization’s mission, and a deeper appreciation for the individual perspectives of our team members.</p>
6457. </div>
6458. </div>
6459. </div>
6460. </div>
6461. </section>
6462. </div>
6463. </div>
6464. &lt;/article&gt;</description>
6465. <pubDate>Thu, 18 Apr 2024 20:17:26 +0000</pubDate>
6466. <dc:creator>Brooke Sykes</dc:creator>
6467. </item>
6468. <item>
6469. <title>Support.Mozilla.Org: Freshening up the Knowledge Base for spring 2024</title>
6470. <guid isPermaLink="false">https://blog.mozilla.org/sumo/?p=4107</guid>
6471. <link>https://blog.mozilla.org/sumo/2024/04/18/freshening-up-the-knowledge-base-for-spring-2024/</link>
6472. <description>&lt;p&gt;Hello, SUMO community!&lt;/p&gt;
6473. <p>This spring we’re happy to announce that we’re refreshing the Mozilla Firefox Desktop and Mobile knowledge bases. This is a project that we’ve been working on for the past several months and now, we’re ready to finally share it with you all! We’ve put together a video to walk you through what these changes mean for SUMO and how they’ll impact you.</p>
6474. <p></p>
6475. <p><b>Introduction of Article Categories</b></p>
6476. <p>When exploring our knowledge base, we realized there’s so many articles and it’s important to set expectations for users. We’ll be introducing three article types:</p>
6477. <ul>
6478. <li><a href="https://support.mozilla.org/en-US/kb/about-article-type-best-practices">About</a> – Article that aims to be educational and informs the reader about a certain feature.</li>
6479. <li><a href="https://support.mozilla.org/en-US/kb/how-to-article-type-best-practices">How To</a> – Article that aims to teach a user how to interact with a feature or complete a task.</li>
6480. <li><a href="https://support.mozilla.org/en-US/kb/troubleshooting-article-type-best-practices">Troubleshooting</a> – Article that aims to provide solutions to an issue a user might encounter.</li>
6481. <li><a href="https://support.mozilla.org/en-US/kb/faq-article-type-best-practices">FAQ</a> – Article that focuses on answering frequently asked questions that a user might have.</li>
6482. </ul>
6483. <p>We will standardize titles and how articles are formatted per category, so users know what to expect when interacting with an article.</p>
6484. <p><b>Downsizing and concentration of articles</b></p>
6485. <p>There’s hundreds upon hundreds of articles in our knowledge base. However, many of them are repetitive and contain similar information. We want to reduce the number of articles and improve the quality of our content. We will be archiving articles and revising active articles throughout this refresh.</p>
6486. <p><b>Style guideline update focus on reducing cognitive load</b></p>
6487. <p>As mentioned in a previous post, we will be updating the style guideline and aiming to reduce the cognitive load on users by introducing new style guidelines like in-line images. There’s not huge changes, but we’ll go over them more when we release the updated style guidelines.</p>
6488. <p>With all this coming up, we hope you join us for the community call today and learn more about the knowledge base refresh today. We hope to collaborate with our community to make this update successful.</p>
6489. &lt;p&gt;Have questions or feedback? Drop us a message in this &lt;a href=&quot;https://support.mozilla.org/en-US/forums/contributors/716916?last=87365&quot;&gt;SUMO forum thread&lt;/a&gt;.&lt;/p&gt;</description>
6490. <pubDate>Thu, 18 Apr 2024 13:47:39 +0000</pubDate>
6491. <dc:creator>Lucas Siebert</dc:creator>
6492. </item>
6493. <item>
6494. <title>Mozilla Thunderbird: April 2024 Community Office Hours: Rust and Exchange Support</title>
6495. <guid isPermaLink="false">https://blog.thunderbird.net/?p=1692</guid>
6496. <link>https://blog.thunderbird.net/2024/04/april-2024-community-office-hours-rust-and-exchange-support/</link>
6497. <description>&lt;p&gt;&lt;img alt=&quot;Text &amp;quot;COMMUNITY OFFICE HOURS APRIL 2024: RUST AND EXCHANGE&amp;quot; with a stylized Thunderbird bird icon in shades of blue and a custom community icon Iin the center on a lavender background with abstract circular design elements.&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2024/04/COH-APRIL-2024-768x432.png&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
6498. <p>We admit it. Thunderbird is getting a bit Rusty, but in a good way!  In our monthly Development Digests, we’ve been updating the community about <a href="https://blog.thunderbird.net/2024/01/thunderbird-monthly-development-digest-january-2024/">enabling Rust in Thunderbird</a> <a href="https://blog.thunderbird.net/2024/02/thunderbird-monthly-development-digest-february-2024/">to implement</a> <a href="https://blog.thunderbird.net/2024/04/thunderbird-monthly-development-digest-march-24/">native support for Exchange</a>. Now, we’d like to invite you for a chat with Team Thunderbird and the developers making this change possible.  As always, send your questions in advance to <a href="mailto:officehours@thunderbird.net">officehours@thunderbird.net</a>! This is a great way to get answers even if you can’t join live.</p>
6499.  
6500.  
6501.  
6502. <p>Be sure to note the change in day of the week and the UTC time. (At least the time changes are done for now!) We had to shift our calendar a bit to fit everyone’s schedules and time zones!</p>
6503.  
6504.  
6505.  
6506. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
6507.  
6508. </div><figcaption class="wp-element-caption">UPDATE: Watch the entire conversation here. </figcaption></figure>
6509.  
6510.  
6511.  
6512. <h3>April Office Hours: Rust and Exchange</h3>
6513.  
6514.  
6515.  
6516. <p>This month’s topic is a new and exciting change to the core functionality: using Rust to natively support Microsoft Exchange. Join us and talk with the three key Thunderbird developers responsible for this shiny (<em>rusty</em>) new addition: Sean Burke, Ikey Doherty, and Brendan Abolivier! You’ll find out why we chose Rust,  challenges we encountered, how we used Rust  to interface with XPCOM and Necko to provide Exchange support. We’ll also give you a peek into some future plans around Rust.</p>
6517.  
6518.  
6519.  
6520. <h3>Catch Up On Last Month’s Thunderbird Community Office Hours</h3>
6521.  
6522.  
6523.  
6524. <p>While you’re thinking of questions to ask, watch last month’s office hours where we answered some of your frequently asked recent questions. You can watch clips of specific questions and answers <a href="https://tilvids.com/c/thunderbird_channel/videos?s=1">on our TILvids channel</a>. If you’d prefer a written summary, <a href="https://blog.thunderbird.net/2024/04/team-thunderbird-answers-your-most-frequently-asked-questions/">this blog post</a> has you covered. </p>
6525.  
6526.  
6527.  
6528. <h3>Join The Video Chat</h3>
6529.  
6530.  
6531.  
6532. <p>We’ve also got a shiny new Big Blue Button room, thanks to KDE! We encourage everyone to check out their <a href="https://community.kde.org/Get_Involved">Get Involved page</a>. We’re grateful for their support and to have an open source web conferencing solution for our community office hours.</p>
6533.  
6534.  
6535.  
6536. <p><strong>Date and Time: </strong>Tuesday, April 23 at 16:00 UTC</p>
6537.  
6538.  
6539.  
6540. <p><strong>Direct URL to Join:</strong> <a href="https://meet.thunderbird.net/b/hea-uex-usn-rb1">https://meet.thunderbird.net/b/hea-uex-usn-rb1</a></p>
6541.  
6542.  
6543.  
6544. <p><strong>Access Code: </strong>964573</p>
6545. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2024/04/april-2024-community-office-hours-rust-and-exchange-support/&quot;&gt;April 2024 Community Office Hours: Rust and Exchange Support&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>
6546. <pubDate>Wed, 17 Apr 2024 17:22:44 +0000</pubDate>
6547. <dc:creator>Monica Ayhens-Madon</dc:creator>
6548. </item>
6549. <item>
6550. <title>Firefox Developer Experience: Firefox WebDriver Newsletter — 125</title>
6551. <guid isPermaLink="false">https://fxdx.dev/?p=268</guid>
6552. <link>https://fxdx.dev/firefox-webdriver-newsletter-125/</link>
6553. <description>&lt;p&gt;&lt;em&gt;WebDriver is a remote control interface that enables introspection and control of user agents. As such it 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;a href=&quot;https://www.w3.org/&quot;&gt;W3C&lt;/a&gt; and consists of two separate specifications: &lt;a href=&quot;https://w3c.github.io/webdriver/&quot;&gt;WebDriver classic&lt;/a&gt; (HTTP) and the new &lt;a href=&quot;https://w3c.github.io/webdriver-bidi/&quot;&gt;WebDriver BiDi &lt;/a&gt;(Bi-Directional).&lt;/em&gt;&lt;/p&gt;
6554.  
6555.  
6556.  
6557. <p id="block-657c8643-6b93-4546-8626-3d7c3976c217"><em>This newsletter gives an overview of the work we’ve done as part of the Firefox 125 release cycle</em>.</p>
6558.  
6559.  
6560.  
6561. <h3>Contributions</h3>
6562.  
6563.  
6564.  
6565. <p id="block-9278fa20-63dc-4975-a72b-e3ba73b202a4">With Firefox being an open source project, we are grateful to get contributions from people outside of Mozilla.</p>
6566.  
6567.  
6568.  
6569. <p id="block-f6e2b9b0-63b6-4a4b-aeea-cffbde1019dd">WebDriver code is written in JavaScript, Python, and Rust so any web developer can contribute! Read <a href="https://firefox-source-docs.mozilla.org/devtools/getting-started/README.html">how to setup the work environment</a> and check <a href="https://codetribute.mozilla.org/projects/automation">the list of mentored issues</a> for Marionette.</p>
6570.  
6571.  
6572.  
6573. <h3>General</h3>
6574.  
6575.  
6576.  
6577. <h4>New: Support for the “userAgent” capability</h4>
6578.  
6579.  
6580.  
6581. <p>We added <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885495">support for the User Agent capability</a> which is returned with all the other capabilities by the new session commands. It is listed under the <code>userAgent</code> key and contains the default user-agent string of the browser. For instance when connecting to Firefox 125 (here on macos), the capabilities will contain a <code>userAgent</code> property such as: </p>
6582.  
6583.  
6584.  
6585. <pre class="wp-block-code"><code>"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:125.0) Gecko/20100101 Firefox/125.0"</code></pre>
6586.  
6587.  
6588.  
6589. <h3>WebDriver BiDi</h3>
6590.  
6591.  
6592.  
6593. <h4>New: Support for the “input.setFiles” command</h4>
6594.  
6595.  
6596.  
6597. <p>The <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1855040">“input.setFiles” command</a> is a new feature which allows clients to interact with <code><input></code> elements with <code>type="file"</code>. As the name suggests, it can be used to set the list of files of such an input. The command expects three mandatory parameters. First the <code>context</code> parameter identifies the <a href="https://w3c.github.io/webdriver-bidi/#type-browsingContext-Browsingcontext">BrowsingContext</a> (tab or window) where we expect to find an <code><input type="file"></code>. Then <code>element</code> should be a <a href="https://w3c.github.io/webdriver-bidi/#deserialize-shared-reference">sharedReference</a> to this specific <code><input></code> element. Finally the <code>files</code> parameter should be a list (potentially empty) of strings which are the paths of the files to set for the <code><input></code>. This command has a <code>null</code> return value.</p>
6598.  
6599.  
6600.  
6601. <pre class="wp-block-prismatic-blocks"><code class="language-json">-> {
6602.  "method": "input.setFiles",
6603.  "params": {
6604.    "context": "096fca46-5860-412b-8107-dae7a80ee412",
6605.    "element": {
6606.      "sharedId": "520c3e2b-6210-41da-8ae3-2c499ad66049"
6607.    },
6608.    "files": [
6609.      "/Users/test/somefile.txt"
6610.    ]
6611.  },
6612.  "id": 7
6613. }
6614. <- { "type": "success", "id": 7, "result": {} }</code></pre>
6615.  
6616.  
6617.  
6618. <p>Note that providing more than one path in the <code>files</code> parameter is only supported for <code><input></code> elements with the <code>multiple</code> attribute set. Trying to send several paths to a regular <code><input></code> element will result in an error.</p>
6619.  
6620.  
6621.  
6622. <p>It’s also worth highlighting that the command will override the files which were previously set on the input. For instance providing an empty list as the <code>files</code> parameter will reset the input to have no file selected.</p>
6623.  
6624.  
6625.  
6626. <h4>New: Support for the “storage.deleteCookies” command</h4>
6627.  
6628.  
6629.  
6630. <p>In Firefox 124, we added two methods to interact with cookies: “storage.getCookies” and “storage.setCookie”. <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=1854581">In Firefox 125 we are adding “storage.deleteCookies”</a> so that you can remove previously created cookies. The parameters for the “deleteCookies” command are identical to the ones for the “getCookies” command: the <code>filter</code> argument allows to match cookies based on specific criteria and the <code>partition</code> argument allows to match cookies owned by a certain storage partition. All the cookies matching the provided parameters will be deleted. Similarly to “getCookies” and “setCookie”, “deleteCookies” will return the <code>partitionKey</code> which was built to retrieve the cookies.</p>
6631.  
6632.  
6633.  
6634. <pre class="wp-block-prismatic-blocks"><code class="language-json"># Assuming we have two cookies on fxfdx.dev, foo=value1 and bar=value2
6635.  
6636. -> {
6637.  "method": "storage.deleteCookies",
6638.  "params": {
6639.    "filter": {
6640.      "name": "foo",
6641.      "domain": "fxdx.dev"
6642.    }
6643.  },
6644.  "id": 8
6645. }
6646.  
6647. <- { "type": "success", "id": 8, "result": { "partitionKey": {} } }
6648.  
6649. -> {
6650.  "method": "storage.getCookies",
6651.  "params": {
6652.    "filter": {
6653.      "domain": "fxdx.dev"
6654.    }
6655.  },
6656.  "id": 9
6657. }
6658.  
6659. <- {
6660.  "type": "success",
6661.  "id": 9,
6662.  "result": {
6663.    "cookies": [
6664.      {
6665.        "domain": "fxdx.dev",
6666.        "httpOnly": false,
6667.        "name": "bar",
6668.        "path": "/",
6669.        "sameSite": "none",
6670.        "secure": false,
6671.        "size": 9,
6672.        "value": {
6673.          "type": "string",
6674.          "value": "value2"
6675.        }
6676.      }
6677.    ],
6678.    "partitionKey": {}
6679.  }
6680. }</code></pre>
6681.  
6682.  
6683.  
6684. <h4>New: Support for the “userContext” property in the “partition” argument</h4>
6685.  
6686.  
6687.  
6688. <p>All storage commands accept a <code>partition</code> parameter to specify which storage partition it should use, whether it is to retrieve, create or delete cookie(s). Clients can now provide a <code>userContext</code> property in the <code>partition</code> parameter to build a partition key tied to a specific user context. As a reminder, user contexts are collections of browsing contexts sharing the same storage partition, and are implemented as Containers in Firefox.</p>
6689.  
6690.  
6691.  
6692. <pre class="wp-block-prismatic-blocks"><code class="language-json">-> { "method": "browser.createUserContext", "params": {}, "id": 8 }
6693. <- { "type": "success", "id": 8, "result": { "userContext": "6ade5b81-ef5b-4669-83d6-8119c238a3f7" } }
6694. -> {
6695.  "method": "storage.setCookie",
6696.  "params": {
6697.    "cookie": {
6698.      "name": "test",
6699.      "value": {
6700.        "type": "string",
6701.        "value": "cookie in user context partition"
6702.      },
6703.      "domain": "fxdx.dev"
6704.    },
6705.    "partition": {
6706.      "type": "storageKey",
6707.      "userContext": "6ade5b81-ef5b-4669-83d6-8119c238a3f7"
6708.    }
6709.  },
6710.  "id": 9
6711. }
6712.  
6713. <- { "type": "success", "id": 9, "result": { "partitionKey": { "userContext": "6ade5b81-ef5b-4669-83d6-8119c238a3f7" } } }</code></pre>
6714.  
6715.  
6716.  
6717. <h4>Bug fixes</h4>
6718.  
6719.  
6720.  
6721. <ul>
6722. <li>Fixed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884647">a bug where “storage.getCookies” would not retrieve all expected cookies</a> for a <code>partition</code> with a given “sourceOrigin”.</li>
6723.  
6724.  
6725.  
6726. <li>Fixed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1882748">an issue where recommended preferences would not be applied</a> if WebDriver BiDi is the only remote protocol enabled, which means CDP is disabled.</li>
6727.  
6728.  
6729.  
6730. <li>Fixed an issue where <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1877469">creating and switching to a new tab would not wait for the <code>visibilityState</code> to be updated</a>.</li>
6731. &lt;/ul&gt;</description>
6732. <pubDate>Wed, 17 Apr 2024 15:59:43 +0000</pubDate>
6733. <dc:creator>Julian Descottes</dc:creator>
6734. </item>
6735. <item>
6736. <title>Mozilla Thunderbird: Team Thunderbird Answers Your Most Frequently Asked Questions</title>
6737. <guid isPermaLink="false">https://blog.thunderbird.net/?p=1675</guid>
6738. <link>https://blog.thunderbird.net/2024/04/team-thunderbird-answers-your-most-frequently-asked-questions/</link>
6739. <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/2024/04/QA.png&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
6740. <div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
6741. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=de&u=https://blog.thunderbird.net/2024/04/team-thunderbird-answers-your-most-frequently-asked-questions" rel="noreferrer noopener" target="_blank">Auf Deutsch übersetzen</a></div>
6742.  
6743.  
6744.  
6745. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=fr&u=https://blog.thunderbird.net/2024/04/team-thunderbird-answers-your-most-frequently-asked-questions" rel="noreferrer noopener" target="_blank">Traduire en français</a></div>
6746.  
6747.  
6748.  
6749. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=ja&u=https://blog.thunderbird.net/2024/04/team-thunderbird-answers-your-most-frequently-asked-questions" rel="noreferrer noopener" target="_blank">日本語に翻訳</a></div>
6750. </div>
6751.  
6752.  
6753.  
6754. <p>We know the Thunderbird community has LOTS of questions! We get them on <a href="https://support.mozilla.org/products/thunderbird">Mozilla Support</a>, <a href="https://mastodon.online/@thunderbird">Mastodon</a>, and <a href="https://x.com/mozthunderbird">X.com</a> (formerly Twitter). They pop up everywhere, from the <a href="https://www.reddit.com/r/Thunderbird/">Thunderbird subreddit</a> to the teeming halls of conferences like FOSDEM and SCaLE. During our March Community Office Hours, we took your most frequently asked questions to Team Thunderbird and got some answers. If you couldn’t watch the full session, or would rather have the answers in abbreviated text clips, this post is for you!</p>
6755.  
6756.  
6757.  
6758. <h3><strong>Thunderbird for Android / K-9 Mail</strong></h3>
6759.  
6760.  
6761.  
6762. <p>The upcoming release on Android is definitely on everyone’s mind! We received lots of questions about this at our conference booths, so let’s answer them!</p>
6763.  
6764.  
6765.  
6766. <p><em><strong>Will there be Exchange support for Thunderbird for Android?</strong></em></p>
6767.  
6768.  
6769.  
6770. <p>Yes! Implementing Exchange in Rust in the Thunderbird Desktop client will enable us to reuse those Rust crates as shared libraries with the Mobile client. Stay up to date on Exchange support progress via our monthly <a href="https://blog.thunderbird.net/tag/dev-digest/">Developer Digests</a>.</p>
6771.  
6772.  
6773.  
6774. <p><em><strong>Will Thunderbird Add-ons be available on Android?</strong></em></p>
6775.  
6776.  
6777.  
6778. <p>Right now, no, they will not be available. K-9 Mail uses a different code base than Thunderbird Desktop. Thunderbird add-ons are designed for a desktop experience, not a mobile one. We <em>want</em> to have add-ons in the future, but this will likely not happen within the next two years.</p>
6779.  
6780.  
6781.  
6782. <p><em><strong>When Thunderbird for Android </strong></em><strong><em>launches, will it be available on <a href="https://f-droid.org">F-Droid</a>?</em></strong></p>
6783.  
6784.  
6785.  
6786. <p>It absolutely will. </p>
6787.  
6788.  
6789.  
6790. <p><em><strong>When Thunderbird for Android is ready to be released, what will the upgrade path look like?</strong></em></p>
6791.  
6792.  
6793.  
6794. <p>We know some in the K-9 Mail community love their adorable robot dog and don’t want to give him up yet. So we will support K-9 Mail (same code, different brand) in parallel for a year or two, until the product is more mature, and we see that more K-9 Mail users are organically switching.</p>
6795.  
6796.  
6797.  
6798. <p>Because of Android security, users will need to manually migrate from K-9 Mail to Thunderbird for Android, versus an automatic migration. We want to make that effortless and unobtrusive, and the Sync feature using Mozilla accounts will be a large part of that. We are exploring one-tap migration tools that will prompt you to switch easily and keep all your data and settings – and your peace of mind.</p>
6799.  
6800.  
6801.  
6802. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
6803.  
6804. </div></figure>
6805.  
6806.  
6807.  
6808. <p><em><strong>Will CalDAV and CardDAV be available on Thunderbird for Android?</strong></em></p>
6809.  
6810.  
6811.  
6812. <p>Probably! We’re still determining this, but we know our users like having their contacts and calendars inside one app for convenience, as well as out of privacy concerns. While it would be a lot of engineering effort, we understand the reasoning behind these requests. As we consider how to go forward, we’ll release all these explorations and ideas in our monthly updates, where people can give us feedback.</p>
6813.  
6814.  
6815.  
6816. <p><em><strong>Will the K-9 Mail API provide the ability to download the save preferences that Sync stores locally to plug into automation like Ansible?</strong></em></p>
6817.  
6818.  
6819.  
6820. <p>Yes! Sync is open source, so users can self-host their own instead of using Mozilla services. This question touches on the differences between data structure for desktop and mobile, and how they handle settings. So this will take a while, but once we have something stable in a beta release, we’ll have articles on how to hook up your own sync server and do your own automation.</p>
6821.  
6822.  
6823.  
6824. <hr class="wp-block-separator has-alpha-channel-opacity" />
6825.  
6826.  
6827.  
6828. <h3><strong>Thunderbird for Desktop</strong></h3>
6829.  
6830.  
6831.  
6832. <p><em><strong>When will we have native Exchange support for desktop Thunderbird?</strong></em></p>
6833.  
6834.  
6835.  
6836. <p>We hope to land this in the next ESR (Extended Support Release), version 128, in limited capacity. Users will still need to use the OWL Add-on for all situations where the standard exchange web service is not available. We don’t yet know if native calendar and address book support will be included in the ESR. We want to support every aspect of Exchange, but there is a lot of code complexity and a history of changes from Microsoft. So our primary goal is good, stable support for email by default, and calendar and address book if possible, for the next ESR.</p>
6837.  
6838.  
6839.  
6840. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
6841.  
6842. </div></figure>
6843.  
6844.  
6845.  
6846. <p><em><strong>When will conversations and a true threaded view be added to Thunderbird?</strong></em></p>
6847.  
6848.  
6849.  
6850. <p>Viewing your own sent emails is an important component of a true conversation view. This is a top priority and we’re actively working towards it. Unfortunately, this requires overhauling the backend database that underlies Thunderbird, which is 20 years old. Our legacy database is not built to handle conversation views with received and sent messages listed in the same thread. Restructuring a two decades old database is not easy. Our goal is to have a new global message database in place by May 31. If nothing has exploded, it should be much easier to enable conversation view in the front end.</p>
6851.  
6852.  
6853.  
6854. <p><em><strong>When will we get a full sender name column</strong></em> <em><strong>with the raw email address of the sender</strong></em>?<em><strong> </strong></em><strong><em>This will</em></strong><em><strong> help further avoid phishing and spam</strong></em>.</p>
6855.  
6856.  
6857.  
6858. <p>We plan to make this available in the next ESR — Thunderbird 128 — which is due July 2024.</p>
6859.  
6860.  
6861.  
6862. <p><em><strong>Will there ever be a browser-based view of Thunderbird?</strong></em></p>
6863.  
6864.  
6865.  
6866. <p>Despite our foundations in Firefox, this is a huge effort that would have to be built from scratch. This isn’t on our roadmap and not in our plans for now. If there was a high demand, we might examine how feasible this could be. Alex explains this in more detail during the short video below:</p>
6867.  
6868.  
6869.  
6870. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
6871.  
6872. </div></figure>
6873. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2024/04/team-thunderbird-answers-your-most-frequently-asked-questions/&quot;&gt;Team Thunderbird Answers Your Most Frequently Asked Questions&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>
6874. <pubDate>Tue, 16 Apr 2024 13:59:00 +0000</pubDate>
6875. <dc:creator>Monica Ayhens-Madon</dc:creator>
6876. </item>
6877. <item>
6878. <title>Mozilla Performance Blog: Performance Testing Newsletter, Q1 Edition</title>
6879. <guid isPermaLink="false">https://blog.mozilla.org/performance/?p=502</guid>
6880. <link>https://blog.mozilla.org/performance/2024/04/16/performance-testing-newsletter-q1-edition/</link>
6881. <description>&lt;div class=&quot;Ar Au Ao&quot; id=&quot;:1mc&quot;&gt;
6882. <div class="Am aiL Al editable LW-avf tS-tW tS-tY" contenteditable="true" id=":1m8" tabindex="1">
6883. <p dir="ltr" id="gmail-docs-internal-guid-6605a564-7fff-78e7-5da5-47ac73c643d0">Welcome to the latest edition of the Performance Testing Newsletter! The PerfTools team empowers engineers with tools to continuously improve the performance of Mozilla products. See below for highlights from the changes made in the last quarter.</p>
6884. <h3>Highlights <img height="31" src="https://lh7-us.googleusercontent.com/emyZXyy_8A-kowHeY1AoiLXtM3WBGpLDfxtL5Oj0tzFoH7eA5_siRJiM-zJbe5uIWPyRBYVDUG4cFOuARt072bpSZH0kqlZQZ83ManvR-AYnuGqjIRNYqNE1YxOgJOlAaHPAuv8M7TTRCytwE9TXrPA" width="29" /></h3>
6885. <ul>
6886. <li dir="ltr">
6887. <p dir="ltr">[gijs] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1762951">Made a fix to remove the statuspanel in our raptor performance tests.</a></p>
6888. </li>
6889. <li dir="ltr">
6890. <p dir="ltr">[jmaher] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1859911">Manifest test files in Raptor now follow the toml format.</a></p>
6891. </li>
6892. <li dir="ltr">
6893. <p dir="ltr">[myeongjun] <a href="https://github.com/mozilla/treeherder/commit/b4a2a528dce7b72a74225ee56cd4dbcb42b32f7a">Fixed an issue with manual ingestion in Treeherder.</a></p>
6894. </li>
6895. <li dir="ltr">
6896. <p dir="ltr">[myeongjun] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1830984">Added the –non-pgo flag to mach-try-perf to allow users to easily make use of opt builds instead of pgo builds. This will result in faster try run times.</a></p>
6897. </li>
6898. <li dir="ltr">
6899. <p dir="ltr">[andrej] <a href="https://docs.google.com/document/d/1VsomiBS_LiF0xbC8TL0mV3AqBM7gVApeih5XIZmLuaU/edit?usp=sharing">Produced some documentation to help firefox-android engineers with mobile performance testing in mozilla-central.</a></p>
6900. <p>[kshampur] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1689537">Added Motionmark 1.3 tests to Raptor.</a></p></li>
6901. <li dir="ltr">
6902. <p dir="ltr">[kshampur] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1861731">Failing Raptor tasks now provide a screenshot of the failure.</a></p>
6903. </li>
6904. <li dir="ltr">
6905. <p dir="ltr">[fbilt] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1615258">Added searchfox links from tests to test manifests in our Raptor performance documentations.</a> <a href="https://firefox-source-docs.mozilla.org/testing/perfdocs/raptor.html#wasm-godot-baseline-b">Example here.</a></p>
6906. </li>
6907. <li dir="ltr">
6908. <p dir="ltr">[sparky] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1855674">Talos pdfpaint test has been updated to use a larger, and newer set of PDFs.</a></p>
6909. </li>
6910. </ul>
6911. <h3>Contributors <img height="31" src="https://lh7-us.googleusercontent.com/gyN-8bl66lKh7I-Op-GihM7KjlKRGt3y8c9A57Br034ic1a8OGWHyITHCGv9gNgh2TSddD2yxQNjCwbPwj-4f9NMQPoJm1dMWnHAMy2u44vOPFdZJHWbls4k8DHj7DBRsv9BrfHtiS2HnYUU65NXA7Y" width="31" /></h3>
6912. <ul>
6913. <li dir="ltr">
6914. <p dir="ltr">Myeongjun Go [:myeongjun]</p>
6915. </li>
6916. </ul>
6917. <p dir="ltr">If you have any questions, or are looking to add performance testing for your code component, you can find us in <a href="https://matrix.to/#/#perftest:mozilla.org">#perftest on Element</a>, or <a href="https://mozilla.slack.com/archives/C03U19JCSFQ">#perf-help on Slack</a>.</p>
6918. <p dir="ltr">P.S. If you’re interested in including updates from your teams in a quarterly newsletter like this, and you are not currently covered by another newsletter, please reach out to me (:sparky). I’m interested in making a more general newsletter for these.</p>
6919. </div>
6920. &lt;/div&gt;</description>
6921. <pubDate>Tue, 16 Apr 2024 13:34:38 +0000</pubDate>
6922. <dc:creator>Gregory Mierzwinski</dc:creator>
6923. </item>
6924. <item>
6925. <title>Will Kahn-Greene: Observability Team Newsletter (2024q1)</title>
6926. <guid isPermaLink="true">https://bluesock.org/~willkg/blog/mozilla/obs_2024q1.html</guid>
6927. <link>https://bluesock.org/~willkg/blog/mozilla/obs_2024q1.html</link>
6928. <description>&lt;p&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/428965889/Observability+Team&quot;&gt;Observability Team&lt;/a&gt;
6929. is a team dedicated to the problem domain and discipline of Observability at
6930. Mozilla.</p>
6931. <p>We own, manage, and support monitoring infrastructure and tools supporting
6932. Mozilla products and services. Currently this includes
6933. <a class="reference external" href="https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/609845437/Sentry">Sentry</a>
6934. and crash ingestion related services
6935. (<a class="reference external" href="https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/6849069/Crash+Stats+Crash+Reports+Crash+ingestion+Socorro+Antenna">Crash Stats (Socorro)</a>,
6936. <a class="reference external" href="https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/178061663/Symbols+aka+Tecken">Mozilla Symbols Server (Tecken)</a>,
6937. and <a class="reference external" href="https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/178192647/Symbolication+Eliot">Mozilla Symbolication Service (Eliot)</a>).</p>
6938. <p>In 2024, we'll be working with SRE to take over other monitoring services they
6939. are currently supporting like New Relic, InfluxDB/Grafana, and others.</p>
6940. <p>This newsletter covers an overview of 2024q1. Please forward it to interested
6941. readers.</p>
6942. <section id="highlights">
6943. <h3>Highlights</h3>
6944. <ul class="simple">
6945. <li><p>🤹 Observability Services: Change in user support</p></li>
6946. <li><p>🏆 Sentry: Change in ownership</p></li>
6947. <li><p>‼️ Sentry: Please don't start new trials</p></li>
6948. <li><p>⏲️ Sentry: Cron monitoring trial ending April 30th</p></li>
6949. <li><p>⏱️ Sentry: Performance monitoring pilot</p></li>
6950. <li><p>🤖 Socorro: Improvements to Fenix support</p></li>
6951. <li><p>🐛 Socorro: Support guard page access information</p></li>
6952. </ul>
6953. <p>See details below.</p>
6954. </section>
6955. <section id="blog-posts">
6956. <h3>Blog posts</h3>
6957. <p>None this quarter.</p>
6958. </section>
6959. <section id="detailed-project-updates">
6960. <h3>Detailed project updates</h3>
6961. <section id="observability-services-change-in-user-support">
6962. <h4>Observability Services: Change in user support</h4>
6963. <p>We overhauled our pages in Confluence, started an #obs-help Slack channel,
6964. created a new Jira OBSHELP project, built out a support rotation, and leveled
6965. up our ability to do support for Observability-owned services.</p>
6966. <p>See our <a class="reference external" href="https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/605978960/Observability+Service+User+Support">User Support Confluence page</a>
6967. for:</p>
6968. <ul class="simple">
6969. <li><p>where to get user support</p></li>
6970. <li><p>documentation for common tasks (get protected data access, create a Sentry
6971. team, etc)</p></li>
6972. <li><p>self-serve instructions</p></li>
6973. </ul>
6974. <p>Hop in <a class="reference external" href="https://app.slack.com/client/T027LFU12/C06N3QR11E0">#obs-help in Slack</a> to ask for service
6975. support, help with monitoring problems, and advice.</p>
6976. </section>
6977. <section id="sentry-change-in-ownership">
6978. <h4>Sentry: Change in ownership</h4>
6979. <p>The Observability team now owns Sentry service at Mozilla!</p>
6980. <p>We successfully completed <a class="reference external" href="https://mozilla-hub.atlassian.net/browse/OBS-21">Phase 1 of the transition</a> in Q1. If you're a member
6981. of the Mozilla Sentry organization, you should have received a separate email
6982. about this to the <a class="reference external" href="https://groups.google.com/a/mozilla.com/g/sentry-users">sentry-users</a> Google group.</p>
6983. <p>We've overhauled Sentry user support documentation to improve it in a few ways:</p>
6984. <ul class="simple">
6985. <li><p>easier to find "how to" articles for common tasks</p></li>
6986. <li><p>best practices to help you set up and configure Sentry for your project needs</p></li>
6987. </ul>
6988. <p>Check out our
6989. <a class="reference external" href="https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/609452284/Sentry+User+Guide">Sentry user guide</a>.</p>
6990. <p>There's still a lot that we're figuring out, so we appreciate your patience and
6991. cooperation.</p>
6992. </section>
6993. <section id="sentry-please-don-t-start-new-trials">
6994. <h4>Sentry: Please don't start new trials</h4>
6995. <p>Sentry sends marketing and promotional emails to Sentry users which often
6996. include links to start a new trial. Please contact us before starting any new
6997. feature trials in Sentry.</p>
6998. <p>Starting new trials may prevent us from trialing those features in the future
6999. when we’re in a better position to evaluate the feature. There's no way for
7000. admins to prevent users from starting a trial.</p>
7001. </section>
7002. <section id="sentry-cron-monitoring-trial-ending-april-30th">
7003. <h4>Sentry: Cron monitoring trial ending April 30th</h4>
7004. <p>The <a class="reference external" href="https://docs.sentry.io/product/crons/">Cron Monitoring</a> trial that was
7005. started a couple of months ago will end April 30th.</p>
7006. <p>Based on feedback so far and other factors, we will not be enabling this
7007. feature once the trial ends.</p>
7008. <p>This is a good reminder to build in redundancy in your monitoring systems.
7009. Don't rely solely on trial or pilot features for mission critical information!</p>
7010. <p>Once the trial is over, we'll put together an evaluation summary.</p>
7011. </section>
7012. <section id="sentry-performance-monitoring-pilot">
7013. <h4>Sentry: Performance monitoring pilot</h4>
7014. <p><a class="reference external" href="https://docs.sentry.io/product/performance/">Performance Monitoring</a> is
7015. being piloted by a couple of teams; it is not currently available for general
7016. use.</p>
7017. <p>In the meantime, if you are not one of these pilot teams, please do not use
7018. Performance Monitoring. There is a shared transaction event quota for the
7019. entire Mozilla Sentry organization. Once we hit that quota, events are dumped.</p>
7020. <p>If you have questions about any of this, please reach out.</p>
7021. <p>Once the trial is over, we'll put together an evaluation summary.</p>
7022. </section>
7023. <section id="socorro-improvements-to-fenix-support">
7024. <h4>Socorro: Improvements to Fenix support</h4>
7025. <p>We worked on improvements to crash ingestion and the Crash Stats site for the
7026. Fenix project:</p>
7027. <p><a class="reference external" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1812771">1812771: Fenix crash reporter's Socorro crash reports for Java exceptions have "Platform" = "Unknown" instead of "Android"</a></p>
7028. <p>Previously, the platform would be "Unknown". Now the platform for Fenix crash
7029. reports is "Android". Further, the <code class="docutils literal">platform_pretty_version</code> includes the
7030. Android ABI version.</p>
7031. <figure>
7032. <a class="reference external image-reference" href="https://bluesock.org/~willkg/blog/images/obs_2024q1_android_version.png"><img alt="/images/obs_2024q1_android_version.thumbnail.png" src="https://bluesock.org/~willkg/blog/images/obs_2024q1_android_version.thumbnail.png" /></a>
7033. <figcaption>
7034. <p>Figure 1: Screenshot of Crash Stats Super Search results showing Android
7035. versions for crash reports.</p>
7036. </figcaption>
7037. </figure>
7038. <p><a class="reference external" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1819628">1819628: reject crash reports for unsupported Fenix forks</a></p>
7039. <p>Forks of Fenix outside of our control periodically send large swaths of crash
7040. reports to Socorro. When these sudden spikes happened, Mozillians would spend
7041. time looking into them only to discover they're not related to our code or our
7042. users. This is a waste of our time and resources.</p>
7043. <p>We implemented support for the <code class="docutils literal">Android_PackageName</code> crash annotation and
7044. added a throttle rule to the collector to drop crash reports from any
7045. non-Mozilla releases of Fenix.</p>
7046. <p>From 2024-01-18 to 2024-03-31, Socorro accepted 2,072,785 Fenix crash reports
7047. for processing and rejected 37,483 unhelpful crash reports with this new rule.
7048. That's roughly 1.7%. That's not a huge amount, but because they sometimes come
7049. in bursts with the same signature, they show up in Top Crashers wasting
7050. investigation time.</p>
7051. <p><a class="reference external" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884041">1884041: fix create-a-bug links to work with java_exception</a></p>
7052. <p>A long time ago, in an age partially forgotten, Fenix crash reports from a
7053. crash in Java code would send a crash report with a <code class="docutils literal">JavaStackTrace</code> crash
7054. annotation. This crash annotation was a string representation of the Java
7055. exception. As such, it was difficult-to-impossible to parse reliably.</p>
7056. <p>In 2020, Roger Yang and Will Kahn-Greene spec'd out a new <code class="docutils literal">JavaException</code> crash
7057. annotation. The value is a JSON-encoded structure mirroring what Sentry uses
7058. for exception information. This structure provides more information than the
7059. <code class="docutils literal">JavaStackTrace</code> crash annotation did and is much easier to work with because we
7060. don't have to parse it first.</p>
7061. <p>Between 2020 and now, we have been transitioning from crash reports that only
7062. contained a <code class="docutils literal">JavaStackTrace</code> to crash reports that contained both a
7063. <code class="docutils literal">JavaStackTrace</code> and a <code class="docutils literal">JavaException</code>. Once all Fenix crash reports from
7064. crashes in Java code contained a <code class="docutils literal">JavaException</code>, we could transition Socorro
7065. code to use the <code class="docutils literal">JavaException</code> value for Crash Stats views, signature
7066. generation, generate-create-bug-url, and other things.</p>
7067. <p>Recently, Fenix dropped the <code class="docutils literal">JavaStackTrace</code> crash annotation. However, we
7068. hadn't yet gotten to updating Socorro code to use--and prefer--the
7069. <code class="docutils literal">JavaException</code> values. This broke the ability to generate a bug for a Fenix
7070. crash with the needed data added to the bug description.  Work on bug 1884041
7071. fixed that.</p>
7072. <p>Comments for Fenix Java crash reports went from:</p>
7073. <pre class="literal-block">Crash report: https://crash-stats.mozilla.org/report/index/eb6f852b-4656-4cf5-8350-fd91a0240408</pre>
7074. <p>to:</p>
7075. <pre class="literal-block">Crash report: https://crash-stats.mozilla.org/report/index/eb6f852b-4656-4cf5-8350-fd91a0240408
7076.  
7077. Top 10 frames:
7078.  
7079. 0  android.database.sqlite.SQLiteConnection  nativePrepareStatement  SQLiteConnection.java:-2
7080. 1  android.database.sqlite.SQLiteConnection  acquirePreparedStatement  SQLiteConnection.java:939
7081. 2  android.database.sqlite.SQLiteConnection  executeForString  SQLiteConnection.java:684
7082. 3  android.database.sqlite.SQLiteConnection  setJournalMode  SQLiteConnection.java:369
7083. 4  android.database.sqlite.SQLiteConnection  setWalModeFromConfiguration  SQLiteConnection.java:299
7084. 5  android.database.sqlite.SQLiteConnection  open  SQLiteConnection.java:218
7085. 6  android.database.sqlite.SQLiteConnection  open  SQLiteConnection.java:196
7086. 7  android.database.sqlite.SQLiteConnectionPool  openConnectionLocked  SQLiteConnectionPool.java:503
7087. 8  android.database.sqlite.SQLiteConnectionPool  open  SQLiteConnectionPool.java:204
7088. 9  android.database.sqlite.SQLiteConnectionPool  open  SQLiteConnectionPool.java:196</pre>
7089. <p>This both fixes the bug and also vastly improves the bug comments from what we
7090. were previously doing with <code class="docutils literal">JavaStackTrace</code>.</p>
7091. <p>Between 2024-03-31 and 2024-04-06, there were 158,729 Fenix crash reports
7092. processed. Of those, 15,556 have the circumstances affected by this bug: a
7093. <code class="docutils literal">JavaException</code> but don't have a <code class="docutils literal">JavaStackTrace</code>. That's roughly 10% of
7094. incoming Fenix crash reports.</p>
7095. <p>While working on this, we refactored the code that generates these crash report
7096. bugs, so it's in a separate module that's easier to copy and use in external
7097. systems in case others want to generate bug comments from processed crash data.</p>
7098. <p>Further, we changed the code so that instead of dropping arguments in function
7099. signatures, it now truncates them at 80 characters.</p>
7100. <p>We're hoping to improve signature generation for Java crashes using
7101. <code class="docutils literal">JavaException</code> values in 2024q2. That work is tracked in
7102. <a class="reference external" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1541120">bug #1541120</a>.</p>
7103. </section>
7104. <section id="socorro-support-guard-page-access-information">
7105. <h4>Socorro: Support guard page access information</h4>
7106. <p><a class="reference external" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1830954">1830954: Expose crashes which were likely accessing a guard page</a></p>
7107. <p>We updated the stackwalker to pick up the changes for determining
7108. <code class="docutils literal">is_likely_guard_page</code>. Then we exposed that in crash reports in the
7109. <code class="docutils literal">has_guard_page_access</code> field. We added this field to the Details tab in
7110. crash reports and made it searchable. We also added this to the signature
7111. report.</p>
7112. <p>This helps us know if a crash is possibly due to a bug with memory access that
7113. could be a possible security vulnerability vector--something we want to
7114. prioritize fixing.</p>
7115. <p>Since this field is security sensitive, it requires protected data access to
7116. view and search with.</p>
7117. </section>
7118. <section id="socorro-misc">
7119. <h4>Socorro misc</h4>
7120. <ul class="simple">
7121. <li><p><a class="reference external" href="https://pypi.org/project/crashstats-tools/2.0.0/">crashstats-tools 2.0.0 release</a></p></li>
7122. <li><p><a class="reference external" href="https://pypi.org/project/siggen/2.1.20240412/">socorro-siggen 2.1.20240412 release</a></p></li>
7123. <li><p>4 signature generation changes. Thank you Andrew McCreight and Jim Blandy!</p></li>
7124. <li><p>Maintenance and documentation improvements.</p></li>
7125. <li><p>6 production deploys. Created 71 issues. Resolved 61 issues.</p></li>
7126. </ul>
7127. </section>
7128. <section id="tecken-eliot-misc">
7129. <h4>Tecken/Eliot misc</h4>
7130. <ul class="simple">
7131. <li><p>Maintenance and documentation improvements.</p></li>
7132. <li><p>5 production deploys. Created 21 issues. Resolved 28 issues.</p></li>
7133. </ul>
7134. </section>
7135. </section>
7136. <section id="more-information">
7137. <h3>More information</h3>
7138. <p>Find us:</p>
7139. <ul class="simple">
7140. <li><p>Confluence page: <a class="reference external" href="https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/428965889/Observability+Team">Observability Team</a></p></li>
7141. <li><p>User support hub: <a class="reference external" href="https://mozilla-hub.atlassian.net/wiki/spaces/CS1/pages/605978960/Observability+Service+User+Support">User Support</a></p></li>
7142. <li><p>Support: <a class="reference external" href="https://app.slack.com/client/T027LFU12/C06N3QR11E0">#obs-help</a> (Slack)</p></li>
7143. <li><p>Crash ingestion: <a class="reference external" href="https://matrix.to/#/%23crashreporting:mozilla.org">#crashreporting</a> (Matrix)</p></li>
7144. </ul>
7145. <p>Thank you for reading!</p>
7146. &lt;/section&gt;</description>
7147. <pubDate>Tue, 16 Apr 2024 13:00:00 +0000</pubDate>
7148. <dc:creator>Will Kahn-Greene</dc:creator>
7149. </item>
7150. <item>
7151. <title>Firefox Nightly: Exploring improvements to the Firefox sidebar</title>
7152. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1612</guid>
7153. <link>https://blog.nightly.mozilla.org/2024/04/15/exploring-improvements-to-the-firefox-sidebar/</link>
7154. <description>&lt;p&gt;&lt;b&gt;What are we working on? &lt;/b&gt;&lt;/p&gt;
7155. <p>We have long been excited to improve the existing Firefox sidebar and strengthen productivity use cases in the browser. We are laying the groundwork for these improvements, and you may have seen early work-in-progress in our test builds and in Nightly behind preferences (<a href="https://www.reddit.com/r/firefox/comments/1bpywre/firefox_nightly_w_vertical_tabs_build/">Firefox Nightly with vertical tabs</a> and <a href="https://www.reddit.com/r/firefox/comments/1bqlb84/looks_like_firefox_is_experimenting_a_sidebar_in/">Firefox is experimenting with a sidebar in Nightly</a>).</p>
7156. <p><b>What to expect next?</b></p>
7157. <p>In the near future, we will be landing foundational sidebar features in Nightly to ensure parity with the existing sidebar and make the new experience more useful and easy to use. Many of the ideas we are exploring are based on your suggestions in Mozilla Connect. You’ve shared how you imagine productivity, switching between contexts, and juggling multiple tasks could improve in Firefox, and we’ve listened.</p>
7158. <p>We are encouraged by your positive feedback on our early concepts, and we look forward to engaging with the community and hearing more about what you think once sidebar features are ready for testing. We will announce feature readiness for feedback in the follow-up blog posts and on Connect.</p>
7159. &lt;p&gt;In the meantime, if you have questions or general feedback, please engage with us on &lt;a href=&quot;https://connect.mozilla.org/t5/moderation-archive/improvements-to-the-firefox-sidebar-are-on-the-way/td-p/55247&quot;&gt;Mozilla Connect.&lt;/a&gt;&lt;/p&gt;</description>
7160. <pubDate>Mon, 15 Apr 2024 19:30:02 +0000</pubDate>
7161. <dc:creator>Ania Safko</dc:creator>
7162. </item>
7163. <item>
7164. <title>Firefox Nightly: Customizing Reader Mode – These Weeks in Firefox: Issue 158</title>
7165. <guid isPermaLink="false">https://blog.nightly.mozilla.org/?p=1609</guid>
7166. <link>https://blog.nightly.mozilla.org/2024/04/15/customizing-reader-mode-these-weeks-in-firefox-issue-158/</link>
7167. <description>&lt;h3&gt;Highlights&lt;/h3&gt;
7168. <ul>
7169. <li>Irene has just landed a patch supporting custom color themes! You can flip the pref ​​reader.colors_menu.enabled to preview this feature in Nightly. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1876432">Bug 1876432 – Add support for custom themes as its own menu in Reader View</a>
7170. <ul>
7171. <li><img src="https://blog.nightly.mozilla.org/files/2024/04/headlines158_0.png" /></li>
7172. <li><img src="https://blog.nightly.mozilla.org/files/2024/04/headlines158_1.png" /></li>
7173. </ul>
7174. </li>
7175. <li>Niklas added <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883765">RTL support</a> for the new screenshots UI component (currently enabled by default in Nightly)</li>
7176. <li>Shout-out to Paul Bone who landed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1857841">some changes to mozjemalloc</a>, reducing the number of calls to VirtualAlloc. This change caused various improvements (3.5% – 5%) to both <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1857841#c21">Speedometer 2</a> and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1857841#c22">Speedometer 3</a> subtests, with no measurable regression in memory usage!</li>
7177. <li>The Search team enabled Search Config V2 in Nightly, and this has shown multiple improvements in startup time,<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885002#c4"> by at least 3%</a>!</li>
7178. </ul>
7179. <h3>Friends of the Firefox team</h3>
7180. <h3><a href="https://bugzilla.mozilla.org/buglist.cgi?title=Resolved%20bugs%20%28excluding%20employees%29&quicksearch=1865558%2C1861325%2C1887467%2C1887331%2C1731635&list_id=16968858">Resolved bugs (excluding employees)</a></h3>
7181. <p><a href="https://github.com/niklasbaumgardner/NewContributorScraper">Script to find new contributors from bug list</a></p>
7182. <h4>New contributors (🌟 = first patch)</h4>
7183. <ul>
7184. <li>Golubets added an <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1731635">option to disable split console</a></li>
7185. </ul>
7186. <h3>Project Updates</h3>
7187. <h4>Add-ons / Web Extensions</h4>
7188. <h5>WebExtensions Framework</h5>
7189. <ul>
7190. <li>Fixed a regression introduced in Firefox 116 for extensions including a sidebar command shortcut (fixed in Nightly 126 and Beta 125) – <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1881820">Bug 1881820</a>
7191. <ul>
7192. <li>Thanks to Dao for investigating the regression and then following up with a fix</li>
7193. </ul>
7194. </li>
7195. <li>Fixed a long standing uninterruptible reflow triggered by browser-addons.js on handling “addon-install-confirmation” notifications – <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1360028">Bug 1360028</a>
7196. <ul>
7197. <li>Thanks to Dao for fixing it too!</li>
7198. </ul>
7199. </li>
7200. </ul>
7201. <h4>ESMification status</h4>
7202. <ul>
7203. <li><a href="https://spidermonkey.dev/areweesmifiedyet/#/">100%</a>
7204. <ul>
7205. <li><a href="http://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAPMxTNomzkw8ZrOKwaDG6tXf8e_C9sKTPoyxHpqM4pBsDHR5eA%40mail.gmail.com">Thank you to everyone</a> that has worked on and supported this effort.</li>
7206. <li>Plan for out-of-tree changes & removing old loaders is coming soon.</li>
7207. </ul>
7208. </li>
7209. </ul>
7210. <h4>Lint, Docs and Workflow</h4>
7211. <ul>
7212. <li>Dave has now <a href="https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAPMxTNqotW_KwDZ1TL%3DNZ1iSgsHCbG_WzrUvs09Lmm_1KPwXxg%40mail.gmail.com">finished landing and turning on</a> the argument linting for no-unused-vars</li>
7213. </ul>
7214. <h4>Migration Improvements</h4>
7215. <ul>
7216. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883503">The measurements bugs</a> are basically done, just a few outstanding ones that should hopefully close out this week. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885369">We’re now focusing more on copying the various data stores to the “staging” directory</a>.</li>
7217. <li>We’re in talks with the DOM team to get their support for <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1887978">cloning privileged and WebExtension IndexedDB databases safely</a> at runtime.</li>
7218. <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1885993">We hope to turn on measurements this week on Nightly.</a></li>
7219. </ul>
7220. <h4>Screenshots (enabled by default in Nightly)</h4>
7221. <ul>
7222. <li>Niklas fixed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1883717">selection pixel size issues</a> with high device pixel ratios</li>
7223. <li>Niklas fixed issues with <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1881506">right clicking while dragging</a> in the overlay</li>
7224. </ul>
7225. <h4>Search and Navigation</h4>
7226. <ul>
7227. <li>Firefox Suggest experience</li>
7228. </ul>
7229. <ul>
7230. <li>Work continues integrating the new Rust backend and improving exposure metrics.</li>
7231. <li>Daisuke has exposed icons mime-types along with blobs, from the offline Suggest backend.<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1882967"> Bug 1882967</a></li>
7232. <li>Drew has fixed a problem with the recording of exposure metrics in experiments.<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886175"> Bug 1886175</a></li>
7233. </ul>
7234. <ul>
7235. <li>Clipboard result</li>
7236. </ul>
7237. <ul>
7238. <li>Karandeep has fixed a problem with empty searches returning no results in Tab, History and Bookmarks Search Mode, and a problem with the clipboard result persisting when switching through multiple empty tabs.<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1884094"> Bug 1884094</a>,<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1865336"> Bug 1865336</a></li>
7239. </ul>
7240. <ul>
7241. <li>SERP categorization metrics</li>
7242. </ul>
7243. <ul>
7244. <li>Stephanie and James have fixed multiple issues in this area.</li>
7245. <li>Categorization metric has been enabled in Nightly.</li>
7246. </ul>
7247. <ul>
7248. <li>Search Config v2
7249. <ul>
7250. <li>Standard8 and Mandy have fixed multiple issues in this area.</li>
7251. <li>Work continues as Config v2 has been enabled in Nightly.</li>
7252. </ul>
7253. </li>
7254. <li>Frecency ranking
7255. <ul>
7256. <li>Marco has changed frecency recalculation to accelerate when many changes have been made from the last recalculation. This should help with large imports.<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1873629"> Bug 1873629</a></li>
7257. <li>Marco has corrected a schema migration mistake, preventing recalculation of frecency for not recently accessed domains. That caused autofill of domains to not work as expected in the Address Bar for Firefox 125 Nightly (and first week of Beta).<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886975"> Bug 1886975</a></li>
7258. </ul>
7259. </li>
7260. <li>Other fixes
7261. <ul>
7262. <li>Drew has corrected visual alignment of weather results.<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1886694"> Bug 1886694</a></li>
7263. <li>Dale has corrected visual alignment of rich search suggestions.<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1871022"> Bug 1871022</a></li>
7264. </ul>
7265. </li>
7266. </ul>
7267. <h4>Storybook/Reusable Components</h4>
7268. <ul>
7269. <li>Design Tokens
7270. <ul>
7271. <li>We’ve recently landed some changes to how our design tokens are handed in mozilla-central, we now have a <a href="https://searchfox.org/mozilla-central/source/toolkit/themes/shared/design-system/design-tokens.json">JSON source of truth for these tokens</a></li>
7272. <li>To update the tokens files (tokens-shared, tokens-platform, tokens-brand), you’ll need to modify the design-tokens.json file and then run ./mach npm run build –prefix=toolkit/themes/shared/design-system</li>
7273. <li>Our current docs can be found on Storybook: <a href="https://firefoxux.github.io/firefox-desktop-components/?path=/docs/docs-json-design-tokens--docs">JSON design tokens</a>, and the more general <a href="https://firefoxux.github.io/firefox-desktop-components/?path=/docs/docs-design-tokens--docs">design tokens</a> docs
7274. <ul>
7275. <li>Porting these docs over to Firefox Source Docs will happen in the next couple of days</li>
7276. </ul>
7277. </li>
7278. <li>This info will also be sent out to the firefox-dev mailing list with more details and links to Firefox Source Docs</li>
7279. </ul>
7280. </li>
7281. &lt;/ul&gt;</description>
7282. <pubDate>Mon, 15 Apr 2024 18:34:51 +0000</pubDate>
7283. <dc:creator>Niklas Baumgardner</dc:creator>
7284. </item>
7285. <item>
7286. <title>The Servo Blog: Servo and SpiderMonkey</title>
7287. <guid isPermaLink="true">https://servo.org/blog/2024/04/15/spidermonkey/</guid>
7288. <link>https://servo.org/blog/2024/04/15/spidermonkey/</link>
7289. <description>&lt;p&gt;As a web engine, Servo embeds another engine for its script execution capabilities, including both JavaScript and Wasm: &lt;a href=&quot;https://spidermonkey.dev/&quot;&gt;SpiderMonkey&lt;/a&gt;.
7290. One of the goals of Servo is modularity, and the question of how modular it really was with regards to those capabilities came up.
7291. For example, how easy would it be for Servo to use Chrome’s V8 engine, or the next big script engine?
7292. To answer that question, we’ve written a <a href="https://github.com/servo/servo/wiki/Servo-and-SpiderMonkey-Report">short report</a> analysing the relationship between Servo and SpiderMonkey.</p>
7293. <h3>The problem <a class="header-anchor" href="https://servo.org/blog/2024/04/15/spidermonkey/#the-problem">
7294.        <span class="icon hashlink"><i class="fas fa-link"></i></span>
7295.      </a></h3>
7296. <p>Running a webpage happens inside the <a href="https://github.com/servo/servo/tree/main/components/script"><code>script</code></a> component of Servo; the loading process <a href="https://github.com/servo/servo/blob/d9f067e998671d16a0274c2a7c8227fec96a4607/components/script/script_thread.rs#L3192">starts there</a>, and the page continues to run its <a href="https://html.spec.whatwg.org/multipage/#event-loop-processing-model">HTML event loop</a> there.
7297. By its very nature, executing a script from within a webpage requires an integration between the script engine and the web engine that surrounds it.
7298. Anything shared between the two, including the DOM itself and any other construct calling from one into the other, needs to be integrated somehow, and much but not all of that is done via <a href="https://webidl.spec.whatwg.org/#introduction">WebIDL</a>.
7299. For example, an integration area that is left for web and script engines to implement as they see fit is that with a garbage collector (see example <a href="https://github.com/servo/mozjs/blob/8603cbf35781ea8f2d57e4822a2b874f56a53914/mozjs-sys/src/jsgc.rs#L87">in Rust for SpiderMonkey</a>).</p>
7300. <p>The need to integrate can result in tight coupling, but the classic ways of increasing <a href="https://en.wikipedia.org/wiki/Modularity">modularity</a> — abstractions and interfaces — can be applied here as well, and that is where we found Servo lacking in some ways, but also on the right path.
7301. Servo already comes with abstractions and interfaces for <a href="https://github.com/servo/servo/tree/d9f067e998671d16a0274c2a7c8227fec96a4607/components/script/dom/bindings">a large surface area</a> of its <a href="https://github.com/servo/mozjs">integration with SpiderMonkey</a>, providing ease of use and clarity while preserving boundaries between the two.
7302. Other parts of that integration rely on direct, and unsafe, calls into the <a href="https://github.com/servo/mozjs/tree/8603cbf35781ea8f2d57e4822a2b874f56a53914/mozjs-sys/src">low-level SpiderMonkey APIs</a>.</p>
7303. <h3>The solution <a class="header-anchor" href="https://servo.org/blog/2024/04/15/spidermonkey/#the-solution">
7304.        <span class="icon hashlink"><i class="fas fa-link"></i></span>
7305.      </a></h3>
7306. <p>The low-hanging fruit consists of removing these direct calls into low-level SpiderMonkey APIs, replacing them with safe and higher-level constructs.
7307. Work on this has started, through a combination of efforts from maintainers and the enthusiasm of community members: <a href="https://github.com/eerii">eri</a>, <a href="https://github.com/tannal">tannal</a>, and <a href="https://github.com/Taym95">Taym Haddadi</a>.
7308. These efforts have already resulted in the closing of several issues:</p>
7309. <ul>
7310. <li><a href="https://github.com/servo/servo/issues/31319">WedIDL: bring dom/bindings/typedarray further in line with spec</a></li>
7311. <li><a href="https://github.com/servo/servo/issues/31064">WebIDL: use TypedArray</a></li>
7312. <li><a href="https://github.com/servo/servo/issues/31050">Remove create_typed_array from dom/bindings</a></li>
7313. <li><a href="https://github.com/servo/servo/issues/31049">WebIDL: use Float32Array in GamePad</a></li>
7314. <li><a href="https://github.com/servo/servo/issues/31048">WebIDL: use Float32Array in XRRay</a></li>
7315. <li><a href="https://github.com/servo/servo/issues/31047">WebIDL: use Float32Array in XRRigidTransform</a></li>
7316. <li><a href="https://github.com/servo/servo/issues/31046">WebIDL: use Float32Array in XRView</a></li>
7317. <li><a href="https://github.com/servo/servo/issues/30890">WebIDL impl: remove unsafe JSObject from return value of Document::NamedGetter</a></li>
7318. </ul>
7319. <p>Note that the safer higher-level constructs that replace low-level SpiderMonkey API calls are still <a href="https://github.com/servo/servo/blob/d9f067e998671d16a0274c2a7c8227fec96a4607/components/script/dom/bindings/buffer_source.rs">internally tightly coupled</a> to SpiderMonkey.
7320. By centralizing these calls, and hiding them from the rest of the codebase, it becomes possible to enumerate what exactly Servo is doing with SpiderMonkey, and to start thinking about a second layer of abstraction: one that would hide the underlying script engine.
7321. An existing, and encouraging, example of such a layer comes from React Native in the form of its <a href="https://reactnative.dev/docs/the-new-architecture/landing-page#fast-javascriptnative-interfacing">JavaScript Interface (JSI)</a>.</p>
7322. <h3>Call to action <a class="header-anchor" href="https://servo.org/blog/2024/04/15/spidermonkey/#call-to-action">
7323.        <span class="icon hashlink"><i class="fas fa-link"></i></span>
7324.      </a></h3>
7325. <p>If you are interested in contributing to these efforts, the issues below are good places to start:</p>
7326. <ul>
7327. <li><a href="https://github.com/servo/servo/issues/30863">Modular JS/execution engine</a></li>
7328. <li><a href="https://github.com/servo/servo/issues/30891">WebIDL impl: remove unsafe JSObject when returning a ReadableStream</a></li>
7329. <li><a href="https://github.com/servo/servo/issues/30892">WebIDL impl: remove unsafe JSObject from WebGLExtensionWrapper</a></li>
7330. <li><a href="https://github.com/servo/servo/issues/31072">Support FinalizationRegistry</a></li>
7331. <li><a href="https://github.com/servo/servo/issues/30889">WebIDL impl: Replace use of NonNull</a></li>
7332. </ul>
7333. &lt;p&gt;For more details, read &lt;a href=&quot;https://github.com/servo/servo/wiki/Servo-and-SpiderMonkey-Report&quot;&gt;the full report&lt;/a&gt; on our wiki.&lt;/p&gt;</description>
7334. <pubDate>Mon, 15 Apr 2024 00:00:00 +0000</pubDate>
7335. </item>
7336. <item>
7337. <title>Don Marti: planning for SCALE 2025</title>
7338. <guid isPermaLink="true">https://blog.zgp.org/scale-2025/</guid>
7339. <link>https://blog.zgp.org/scale-2025/</link>
7340. <description>&lt;p&gt;I missed &lt;a href=&quot;https://www.socallinuxexpo.org/scale/21x&quot;&gt;Southern California Linux Expo&lt;/a&gt; this year. Normally I can think of a talk to do, but between work and [virus redacted] I didn’t have a lot of conference abstract writing time last fall. I need some new material anyway. The talks that tend to do well for me there are kind of a mix of tips for doing weird stuff.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/scale-20/&quot;&gt;privacy tools&lt;/a&gt;&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;&lt;a href=&quot;https://lwn.net/Articles/589196/&quot;&gt;Using git and make for tasks beyond coding&lt;/a&gt;&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;&lt;a href=&quot;https://www.socallinuxexpo.org/scale6x/conference-info/speakers/Don-Marti/index.html&quot;&gt;tools for working offline&lt;/a&gt;&lt;/p&gt;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;I didn’t really have anything good to submit last fall, but this year I am building up a bunch of miscellaneous Linux stuff similar to what has worked for me at SCALE before. Because of the big Fediverse trend, the search quality crisis, the ends of third-party cookies and Twitter, and enshittification in general, it seems like there’s a lot more interest in redoing your blog—I know I have been doing it, so that’s what I’m going to see if I can come up with something on for next SCALE. But I’m not going to use a blog software package. I’m more comfortable with a mix of different stuff. This blog is now mainly done in Pandoc, &lt;a href=&quot;https://blog.zgp.org/automatically-run-make/&quot;&gt;auto-rebuilt by Make&lt;/a&gt;, and has a bunch of scripts in various languages, including shell, Perl, Python, and even &lt;a href=&quot;https://blog.zgp.org/code/lazy.lua&quot;&gt;a little bit of Lua&lt;/a&gt; now.&lt;/p&gt; &lt;figure&gt; &lt;img alt=&quot;protip: use cowsay(1) to alert the user to errors in Makefile before restarting&quot; src=&quot;https://blog.zgp.org/i/cowsay.png&quot; /&gt; &amp;lt;figcaption&amp;gt;protip: use cowsay(1) to alert the user to errors in Makefile before restarting&amp;lt;/figcaption&amp;gt; &lt;/figure&gt; &lt;p&gt;I don’t really expect anybody to copy this blog, more outdo it by getting the audience to realize how much you can now do with the available tools. I’m not going to win any design prizes but with modern CSS I can make a reasonable responsive layout and dark/light modes. And yes you can make a &lt;a href=&quot;https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fblog.zgp.org%2Ffeed.xml&quot;&gt;valid RSS feed&lt;/a&gt; in GNU Make.&lt;/p&gt; &lt;p&gt;The feature I just did today is the &lt;q&gt;similar posts&lt;/q&gt; in the left column. Remember that paper about how you can measure the similarity between two pieces of text by seeing how well they compress together? &lt;a href=&quot;https://aclanthology.org/2023.findings-acl.426/&quot;&gt;“Low-Resource” Text Classification: A Parameter-Free Classification Method with Compressors - ACL Anthology&lt;/a&gt; This is Python code for rating similarity of chunks of text. Check it out in the left column, you can now follow the links to similar blog posts.&lt;/p&gt; &lt;pre&gt;&lt;code&gt;import gzip def z(s): return len(gzip.compress(bytes(s, 'utf-8'))) def simscore(t1, t2): &quot;lower is better&quot; if len(t1) == 0 or len(t2) == 0: return 1 base = z(t1) + z(t2) minsize = min(z(' '.join([t1, t2])), z(' '.join([t2, t1])), base) return int(10000 * minsize/base)&lt;/code&gt;&lt;/pre&gt; &lt;p&gt;Next I will probably try stuff like Fediverse-powered comments, some kind of search feature, LLM training set poisoning, some privacy and p2p features, and maybe something else. A lot of what I’m doing here will be possible to translate into other environments, and should be portable to people’s favorite blog software.&lt;/p&gt; &lt;h3&gt;Related&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;http://blog.zgp.org/am-i-metal-yet/&quot;&gt;Am I metal yet?&lt;/a&gt; The old blog software&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;http://blog.zgp.org/automatically-run-make/&quot;&gt;Automatically run make when a file changes&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/favicon/&quot;&gt;Hey kids, favicon!&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;Bonus links&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;https://jvns.ca/blog/2024/04/10/notes-on-git-error-messages/&quot;&gt;Notes on git’s error messages&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://daniel.haxx.se/blog/2024/04/10/verified-curl/&quot;&gt;Verified curl&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://a.wholelottanothing.org/a-blueprint-of-my-dream-blogging-cms/&quot;&gt;Ideas for my dream blogging CMS&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.documentfoundation.org/blog/2024/04/04/german-state-moving-30000-pcs-to-libreoffice/&quot;&gt;German state moving 30,000 PCs to LibreOffice&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.tidelift.com/xz-tidelift-and-paying-the-maintainers&quot;&gt;xz, Tidelift, and paying the maintainers&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://lwn.net/Articles/966869/&quot;&gt;[$] Radicle: peer-to-peer collaboration with Git&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://webkit.org/blog/15054/an-html-switch-control/&quot;&gt;An HTML Switch Control&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://shkspr.mobi/blog/2024/02/a-tiny-incomplete-single-user-write-only-activitypub-server-in-php/&quot;&gt;A (tiny, incomplete, single user, write-only) ActivityPub server in PHP&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://jvns.ca/blog/2024/02/16/popular-git-config-options/&quot;&gt;Popular git config options&lt;/a&gt;&lt;/p&gt;</description>
7341. <pubDate>Sun, 14 Apr 2024 00:00:00 +0000</pubDate>
7342. </item>
7343. <item>
7344. <title>Don Marti: B L O C K in the U S A</title>
7345. <guid isPermaLink="true">https://blog.zgp.org/b-l-o-c-k-in-the-u-s-a/</guid>
7346. <link>https://blog.zgp.org/b-l-o-c-k-in-the-u-s-a/</link>
7347. <description>&lt;p&gt;According to a survey done by Censuswide for Ghostery, a &lt;a href=&quot;https://www.theregister.com/2024/03/27/america_ad_blocker/&quot;&gt;majority of Americans now use ad blockers&lt;/a&gt;. Yes, it looks like a &lt;a href=&quot;https://www.ghostery.com/blog/privacy-report-advertisers-and-adblockers&quot;&gt;well-designed survey of 2,000 people&lt;/a&gt;. But it’s hard to go from what people &lt;em&gt;say&lt;/em&gt; they’re using to figuring out how much protection they really have.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;p&gt;&lt;strong&gt;Are they answering accurately?&lt;/strong&gt; People might be under- or over-reporting their use of ad blockers. Under-reporting because they don’t want to admit to free-riding on ad-supported sites, or over-reporting because &lt;q&gt;install an ad blocker&lt;/q&gt; is now one of the typical Internet tips you’re supposed to do, like not re-using passwords and installing software updates when they come out. People might be trying to look more responsible. When &lt;a href=&quot;https://techcrunch.com/2022/12/22/fbi-ad-blocker/&quot;&gt;the FBI says you should be running an ad blocker to deal with fake search ads&lt;/a&gt;, that puts a certain amount of pressure on people.&lt;span class=&quot;aside&quot;&gt;icymi: &lt;a href=&quot;https://www.fortressofdoors.com/ad-blockers-and-the-four-currencies/&quot;&gt;Ad Blockers and the Four Currencies&lt;/a&gt; by Lars Doucet.&lt;/span&gt;&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;&lt;strong&gt;Are they using an honest blocker with real protection?&lt;/strong&gt; The ad blocking category has a lot of scams, including adware and paid allow-listing, so most of the people saying yes are not getting the blocking they think they are. (The company that owns the number one ad blocker makes a business out of selling exceptions from blocking. &lt;a href=&quot;https://www.theverge.com/2020/1/14/21065154/ron-wyden-ftc-joe-simons-adblock-plus-ad-blocking-software-investigation&quot;&gt;Senator Ron Wyden wrote a letter to the FTC asking them to investigate the ad-blocking industry&lt;/a&gt; back in 2020, but no action as far as I know. In the meantime you can check your ad blocker using &lt;a href=&quot;https://coveryourtracks.eff.org/&quot;&gt;a tool from the EFF&lt;/a&gt;.)&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;&lt;strong&gt;How much of their browsing is on a protected browser or device?&lt;/strong&gt; It’s a lot easier to install an ad blocker on desktop than on mobile, and people have different habits.&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;&lt;strong&gt;Is protection being circumvented by server-to-server tracking?&lt;/strong&gt; Ad blocking has been a thing for a long time, so the surveillance industry has gotten pretty good at working around it. &lt;a href=&quot;https://themarkup.org/privacy/2024/01/17/each-facebook-user-is-monitored-by-thousands-of-companies-study-indicates&quot;&gt;Facebook has responded to Apple ATT and to blockage of their tracking pixels by rolling out server-to-server tracking&lt;/a&gt;, which avoids any protection on the client. Google and other companies also have server-to-server tracking.&lt;/p&gt;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;The second most newsworthy part of the new Censuswide survey is &lt;em&gt;why&lt;/em&gt; people say they’re using an ad blocker. &lt;q&gt;Protect online privacy&lt;/q&gt; is now the number one reason, with &lt;q&gt;block ads&lt;/q&gt; and &lt;q&gt;speed up page loads&lt;/q&gt; coming in after that. &lt;span class=&quot;aside&quot;&gt;I’ll leave the most newsworthy part to the end.&lt;/span&gt; I know, I know, the surveillance advertising people are going to reply with something like, yeah, right, these ad blocker users are just rationalizing free-riding on ad-supported sites, like Napster users making bogus fair use arguments instead of paying for CDs back when that was a thing. In order to understand this survey we have to put it in context with other research. Compare to &lt;a href=&quot;http://repository.upenn.edu/asc_papers/137/&quot;&gt;Turow et al.&lt;/a&gt; on attitudes to cross-context tracking, and to an &lt;a href=&quot;https://web.archive.org/web/20180129155334/https://www.iabeurope.eu/wp-content/uploads/2017/09/EuropeOnline_FINAL.pdf&quot;&gt;IAB Europe study&lt;/a&gt; that found only 20% of users &lt;q&gt;would be happy for their data to be shared with third parties for advertising purposes.&lt;/q&gt;&lt;/p&gt; &lt;p&gt;It looks like the privacy concerns are real for a significant subset of people, and part of the same trend as popular &lt;a href=&quot;https://iapp.org/resources/article/us-state-privacy-legislation-tracker/&quot;&gt;US State Privacy Legislation&lt;/a&gt;. &lt;a href=&quot;https://blog.zgp.org/30-40-30/&quot;&gt;Different people have different norms around ad personalization&lt;/a&gt;, and if people can’t get companies to comply with those norms they will get the government to do something about it. For companies, adjusting to privacy norms doesn’t just mean throwing &lt;q&gt;privacy-enhancing technologies&lt;/q&gt; (PETs) at the problem. &lt;a href=&quot;https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4736957&quot;&gt;Jerath et al.&lt;/a&gt; found similar levels of &lt;q&gt;perceived privacy violations&lt;/q&gt; for on-device ad personalization as for old-fashioned cookie-based tracking. PETs have different mathematical properties from cookies, but either don’t address other problems or make them worse.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/personalization-risks/&quot;&gt;personalization risks&lt;/a&gt; such as discrimination&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;complexity and information asymmetry&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;trust&lt;/p&gt;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;Companies deploying PETs are asking users to trust that they will do complicated math honestly—but they’re &lt;a href=&quot;https://www.brookings.edu/articles/how-americans-confidence-in-technology-firms-has-dropped-evidence-from-the-second-wave-of-the-american-institutional-confidence-poll/&quot;&gt;not starting from a position of trust&lt;/a&gt;. When users have the opportunity to evaluate the companies’ honesty in a way they do understand, the companies don’t measure up. Most people can look at an online map of their neighborhood and spot &lt;a href=&quot;https://doctorow.medium.com/https-pluralistic-net-2024-03-05-the-map-is-not-the-territory-vapor-locksmith-57251144ea94&quot;&gt;places where a locksmith isn’t&lt;/a&gt;. And it’s easy to look up a person on a social site and see where there are enough profiles that not all of them can be real.&lt;/p&gt; &lt;figure&gt; &lt;img alt=&quot;screenshot of several fake Facebook profiles, all using the same two photos of retired US Army General Mark Hertling&quot; src=&quot;https://blog.zgp.org/i/hertling-facebook.png&quot; /&gt; &amp;lt;figcaption&amp;gt;screenshot of several fake Facebook profiles, all using the same two photos of retired US Army General Mark Hertling&amp;lt;/figcaption&amp;gt; &lt;/figure&gt; &lt;p&gt;The biggest problem with PETs will be that the Big Tech companies do both easy-to-understand activities—like scams, fake profiles, and &lt;a href=&quot;https://www.washingtonpost.com/technology/2024/03/01/youtube-union-contractor-layoffs/&quot;&gt;union busting&lt;/a&gt;—&lt;em&gt;and&lt;/em&gt; hard-to-understand activities, like PET math. &lt;span class=&quot;aside&quot;&gt;&lt;q&gt;I see you served me scam ads and a map with fake companies in my neighborhood, but I totally trust your math to protect my privacy&lt;/q&gt; — no one ever&lt;/span&gt; If you don’t know if the PET math is honest, but you can see the same company acting dishonestly in other ways, then it’s hard to trust the PET math. (Personally I think the actual PETs are probably legit, but they’re being rolled out as part of a &lt;a href=&quot;https://blog.zgp.org/device-drivers-privacy-publishing/&quot;&gt;larger program to squeeze out legit publishers and other smaller companies&lt;/a&gt;.)&lt;/p&gt; &lt;figure&gt; &lt;img alt=&quot;In AIC polls, confidence in Amazon, Meta, and Google has fallen since 2018.&quot; src=&quot;https://blog.zgp.org/i/confidence-in-tech.webp&quot; /&gt; &amp;lt;figcaption&amp;gt;In AIC polls, confidence in Amazon, Meta, and Google has fallen since 2018.&amp;lt;/figcaption&amp;gt; &lt;/figure&gt; &lt;p&gt;(source: &lt;a href=&quot;https://www.brookings.edu/articles/how-americans-confidence-in-technology-firms-has-dropped-evidence-from-the-second-wave-of-the-american-institutional-confidence-poll/&quot;&gt;How Americans’ confidence in technology firms has dropped: evidence from the second wave of the American Institutional Confidence poll&lt;/a&gt;)&lt;/p&gt; &lt;p&gt;Maybe trust issues are behind Censuswide’s most newsworthy data point: &lt;strong&gt;&lt;q&gt;experienced advertisers&lt;/q&gt; (with 5 or more years of experience in advertising) are more likely to run an ad blocker than average. (66% &amp;gt; 52%)&lt;/strong&gt; Reminds me of &lt;a href=&quot;https://blog.zgp.org/apple-s-kangaroo-cookie-robot/&quot;&gt;how experienced email users were early adopters of spam filters&lt;/a&gt;—the more you know, the more you block. Between &lt;a href=&quot;https://checkmyads.org/google-gsp-pmax-transparency/&quot;&gt;sketchy&lt;/a&gt; &lt;a href=&quot;https://checkmyads.org/confirmed-google-shark-tank-keto-scam/&quot;&gt;placements&lt;/a&gt;, &lt;a href=&quot;https://www.vanityfair.com/news/2018/10/was-the-medias-big-pivot-to-video-all-based-on-a-lie&quot;&gt;bogus&lt;/a&gt; &lt;a href=&quot;https://www.msn.com/en-us/money/companies/mark-zuckerberg-led-meta-faces-class-action-lawsuit-over-alleged-misrepresentation-of-facebook-instagram-ad-audience-size/ar-BB1kkhCG&quot;&gt;reports&lt;/a&gt; and &lt;a href=&quot;https://searchengineland.com/google-ads-reps-customer-service-advertisers-low-436434&quot;&gt;a &lt;q&gt;your call is important to us&lt;/q&gt; approach to advertiser support&lt;/a&gt;, the advertisers are having a much worse surveillance advertising experience than the rest of us. The Censuswide survey &lt;a href=&quot;https://ghostery.cdn.prismic.io/ghostery/ZgP8q7LRO5ile652_Ghostery_ThePrivacyPulseReport_2024.pdf&quot;&gt;(full report PDF)&lt;/a&gt; also shows that more &lt;q&gt;experienced advertisers&lt;/q&gt; than ordinary users believe that the Big Tech companies are &lt;q&gt;likely to abuse data.&lt;/q&gt;&lt;span class=&quot;aside&quot;&gt;but realistically, &lt;a href=&quot;https://www.vice.com/en/article/akvmke/facebook-doesnt-know-what-it-does-with-your-data-or-where-it-goes&quot;&gt;who knows if they are or not?&lt;/a&gt;&lt;/span&gt;&lt;/p&gt; &lt;p&gt;The &lt;q&gt;Tragedy of the Commons&lt;/q&gt; is &lt;a href=&quot;https://archive.org/details/governingthecommons/page/n21/mode/2up&quot;&gt;bogus when it comes to actual traditional practices for managing common resources&lt;/a&gt;, but it is a thing within large companies. Individual product managers are incentivized to achieve &lt;a href=&quot;https://www.atlassian.com/agile/agile-at-scale/okr&quot;&gt;short-term goals&lt;/a&gt; either at the expense of other product managers, by dishonest practices that spend down the (common across the whole company) reputation level, or both. For example, within the same large company &lt;a href=&quot;https://blog.zgp.org/ad-supported-piracy/&quot;&gt;one business unit can achieve its goals by licensing e-books, while another business unit can achieve its goals by running ads on infringing copies of the same titles&lt;/a&gt;. Big Tech fans often ask, if these companies are so distrusted, why do people keep using their products? But another question is, if these companies are so trusted, why do voters keep asking the government to take over managing their products? &lt;a href=&quot;https://www.tomscott.com/usvsth3m/realistic-facebook-privacy-simulator/&quot;&gt;Privacy settings are hard for users to figure out&lt;/a&gt; and easy for companies to override, but a vote for privacy is easier and sticks better. (and &lt;a href=&quot;https://vermontbiz.com/news/2024/march/23/vermont-sets-national-precedent-unanimous-house-passage-comprehensive-data&quot;&gt;possibly the one thing that a bitterly divided nation can agree on&lt;/a&gt;)&lt;/p&gt; &lt;p&gt;Doc Searls called ad blocking &lt;q&gt;&lt;a href=&quot;https://doc.searls.com/2015/09/28/beyond-ad-blocking-the-biggest-boycott-in-human-history/&quot;&gt;the biggest boycott in world history&lt;/a&gt;&lt;/q&gt; back in 2015. Ad blocking looks like a response to creepy practices (or &lt;q&gt;perceived privacy violations&lt;/q&gt; if that works better for you) and those practices are part of a more general scam culture crisis. &lt;a href=&quot;https://www.nytimes.com/2021/12/10/opinion/scams-trust-institutions.html&quot;&gt;Tressie McMillan Cottom writes&lt;/a&gt;,&lt;span class=&quot;aside&quot;&gt;read the whole thing&lt;/span&gt;&lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;Scams weaken our trust in social institutions, but their going mainstream—divorced from empathy for the victims or stigma for the perpetrators—means that we have accepted scams as institutions themselves.&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;I can’t see any one big policy solution for surveillance advertising, tech oligopolies, or the broader scam culture problem. All of that stuff would have to change in order to move the ad blocking numbers. It’s going to take a variety of approaches, maybe including a &lt;a href=&quot;https://blog.zgp.org/banning-surveillance-advertising/&quot;&gt;surveillance advertising ban&lt;/a&gt;, maybe &lt;a href=&quot;https://blog.zgp.org/surveillance-marketing-taxes/&quot;&gt;a Pigovian tax on databases containing PII&lt;/a&gt;, maybe &lt;a href=&quot;https://www.schizochronotopia.com/p/a-brief-list-of-business-units-google&quot;&gt;breaking up Big Tech firms&lt;/a&gt;. So far the most promising approach seems to be state laws with private right of action, which is one of the reasons I’m so optimistic about &lt;a href=&quot;https://hintzelaw.com/blog/2023/4/9/wa-my-health-my-data-act-pt1-overview&quot;&gt;Washington State’s My Health My Data Act&lt;/a&gt;. My experience on a jury (not an ad-related case) was the most productive meeting I have been in since I came to California. If surveillance advertising issues can grind their way through a few jury trials, where lawyers have an incentive to explain what’s going on in an accurate, comprehensible way, then both surveillance marketers and privacy nerds will be able to reset how we approach this stuff based on more common sense.&lt;/p&gt; &lt;h3&gt;Related&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/reputation-signal/&quot;&gt;Reputation, signaling, and targeted ads&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/banning-surveillance-advertising/&quot;&gt;banning surveillance advertising&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://blog.zgp.org/improving-web-advertising/&quot;&gt;improving web advertising&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;Bonus links&lt;/h3&gt; &lt;p&gt;&lt;a href=&quot;https://www.adexchanger.com/publishers/why-does-ad-tech-still-fail-to-spot-and-stop-mfa-fueled-schemes/&quot;&gt;Why Does Ad Tech Still Fail To Spot – And Stop – MFA-Fueled Schemes?&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.adexchanger.com/data-privacy-roundup/flying-under-the-radar-is-not-a-realistic-compliance-strategy/&quot;&gt;Flying Under The Radar Is Not A Realistic Compliance Strategy&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.adexchanger.com/privacy/7-things-you-should-know-about-californias-privacy-watchdog/&quot;&gt;7 Things You Should Know About California’s Privacy Watchdog&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.schneier.com/blog/archives/2024/04/class-action-lawsuit-against-googles-incognito-mode.html&quot;&gt;Class-Action Lawsuit against Google’s Incognito Mode&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://checkmyads.org/elon-musk-twitter-tag-not-certified/&quot;&gt;CONFIRMED: Elon Musk’s X lost a HUGE brand safety certification after our complaint&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.adexchanger.com/publishers/nubai-ventures-sues-outbrain-claiming-its-traffic-is-riddled-with-bots/&quot;&gt;Nubai Ventures Sues Outbrain, Claiming Its Traffic Is Riddled With Bots&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.theatlantic.com/ideas/archive/2024/03/tiktok-bill-foreign-influence/677806/&quot;&gt;Critics of the TikTok Bill Are Missing the Point&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://techcrunch.com/2024/03/20/meta-privacy-fee-eu-assessment/&quot;&gt;EU signals doubts over legality of Meta’s privacy fee&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.honest-broker.com/p/they-praised-ai-at-sxswand-the-audience&quot;&gt;They Praised AI at SXSW—and the Audience Started Booing&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.mcsweeneys.net/articles/ai-is-threatening-my-tech-and-lifestyle-content-mill&quot;&gt;AI Is Threatening My Tech and Lifestyle Content Mill&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.bitecode.dev/p/there-is-no-eu-cookie-banner-law&quot;&gt;There is no EU cookie banner law&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://krebsonsecurity.com/2024/03/a-close-up-look-at-the-consumer-data-broker-radaris/&quot;&gt;A Close Up Look at the Consumer Data Broker Radaris&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.adexchanger.com/data-privacy-roundup/the-ftcs-privacycon-was-chock-full-of-warning-signs-for-ad-tech/&quot;&gt;The FTC’s PrivacyCon Was Chock-Full Of Warning Signs For Online Advertising&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.bigtechnology.com/p/how-google-blew-up-its-open-culture&quot;&gt;How Google Blew Up Its Open Culture and Compromised Its Product&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://soatok.blog/2024/02/27/the-tech-industry-doesnt-understand-consent/&quot;&gt;The Tech Industry Doesn’t Understand Consent&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://techcrunch.com/2024/03/07/iab-tcf-cjeu/&quot;&gt;Tracking ads industry faces another body blow in the EU&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://www.adexchanger.com/the-sell-sider/privacy-sandboxs-latency-issues-will-cost-publishers/&quot;&gt;Privacy Sandbox’s Latency Issues Will Cost Publishers&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;https://searchengineland.com/google-enforcing-stricter-rules-consumer-finance-ad-targeting-437939&quot;&gt;Reminder – Google is enforcing stricter rules for consumer finance ad targeting&lt;/a&gt;&lt;/p&gt;</description>
7348. <pubDate>Fri, 12 Apr 2024 00:00:00 +0000</pubDate>
7349. </item>
7350. <item>
7351. <title>Hacks.Mozilla.Org: Prototype even faster with the Gradio UI for Figma component library</title>
7352. <guid isPermaLink="false">https://hacks.mozilla.org/?p=48138</guid>
7353. <link>https://hacks.mozilla.org/2024/04/prototype-even-faster-with-the-gradio-ui-for-figma-component-library/</link>
7354. <description>&lt;p&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;As an industry, generative AI is moving quickly, and so requires teams exploring new ideas and technologies to move quickly as well. To do so, we have been using Gradio, a low-code prototyping toolkit from Hugging Face, to spin up experiments and experiences. Gradio has allowed us to validate concepts through prototyping without large investments of time, effort, or infrastructure.&lt;/span&gt;&lt;/p&gt;
7355. <p><span style="font-weight: 400;">Although Gradio has made the development phase of prototyping easier, the design phase has been largely the same. Even with Gradio, designers have had to create components in Figma, outline expected user flows and behaviors, and hand off designs for developers in the same way they have always done. While working on a recent exploration, we realized something was needed: a set of Figma components based on Gradio that enabled designers to create wireframes quickly.</span></p>
7356. <p><span style="font-weight: 400;">Today, we are releasing our library of design components for Gradio for others to use. The components are based on version 4.23.0 of Gradio and will be available through our Figma profile: Mozilla Innovation Projects, </span><a href="https://www.figma.com/@futureatmozilla"><span style="font-weight: 400;">https://www.figma.com/@futureatmozilla</span></a><span style="font-weight: 400;">. We hope these components help teams accelerate their discovery and experimentation with ML and generative AI.</span></p>
7357. <p><span style="font-weight: 400;">You can find out more about Gradio at </span><a href="https://www.gradio.app/"><span style="font-weight: 400;">https://www.gradio.app/</span></a><span style="font-weight: 400;"> and more about innovation at Mozilla at </span><a href="https://future.mozilla.org"><span style="font-weight: 400;">https://future.mozilla.org</span></a></p>
7358. <p><span style="font-weight: 400;">Thanks to Amy Chiu and Anais Ron who created the components and to the Gradio team for their work. Happy designing!</span></p>
7359. <h3><b>What’s Inside </b><b><i>Gradio UI for Figma</i></b><b>?</b></h3>
7360. <p><img alt="" class="alignnone wp-image-48140 size-full" height="900" src="https://hacks.mozilla.org/wp-content/uploads/2024/04/figma2.png" width="1600" /></p>
7361. <p><span style="font-weight: 400;">Because Gradio is an ever-changing prototyping kit, current components are based on version 4.23.0 of Gradio. We selected components based on their wide array of potential uses. Here is a list of the components inside the kit:</span></p>
7362. <ul>
7363. <li style="font-weight: 400;"><span style="font-weight: 400;">Typography (e.g. headers, body fonts)</span></li>
7364. <li style="font-weight: 400;"><span style="font-weight: 400;">Iconography (e.g. chevrons, arrows, corner expanders) </span></li>
7365. </ul>
7366. <p><span style="font-weight: 400;">Small Components:</span></p>
7367. <ul>
7368. <li style="font-weight: 400;"><span style="font-weight: 400;">Buttons</span></li>
7369. <li style="font-weight: 400;"><span style="font-weight: 400;">Checkbox</span></li>
7370. <li style="font-weight: 400;"><span style="font-weight: 400;">Radio</span></li>
7371. <li style="font-weight: 400;"><span style="font-weight: 400;">Sliders</span></li>
7372. <li style="font-weight: 400;"><span style="font-weight: 400;">Tabs</span></li>
7373. <li style="font-weight: 400;"><span style="font-weight: 400;">Accordion</span></li>
7374. <li style="font-weight: 400;"><span style="font-weight: 400;">Delete Button</span></li>
7375. <li style="font-weight: 400;"><span style="font-weight: 400;">Error Message</span></li>
7376. <li style="font-weight: 400;"><span style="font-weight: 400;">Media Type Labels</span></li>
7377. <li style="font-weight: 400;"><span style="font-weight: 400;">Media Player Controller</span></li>
7378. </ul>
7379. <p><span style="font-weight: 400;">Big Components:</span></p>
7380. <ul>
7381. <li style="font-weight: 400;"><span style="font-weight: 400;">Label + Textbox</span></li>
7382. <li style="font-weight: 400;"><span style="font-weight: 400;">Accordion with Label + Input</span></li>
7383. <li style="font-weight: 400;"><span style="font-weight: 400;">Video Player</span></li>
7384. <li style="font-weight: 400;"><span style="font-weight: 400;">Label + Counter</span></li>
7385. <li style="font-weight: 400;"><span style="font-weight: 400;">Label + Slider</span></li>
7386. <li style="font-weight: 400;"><span style="font-weight: 400;">Accordion + Label</span></li>
7387. <li style="font-weight: 400;"><span style="font-weight: 400;">Checkbox with Label</span></li>
7388. <li style="font-weight: 400;"><span style="font-weight: 400;">Radio with Label</span></li>
7389. <li style="font-weight: 400;"><span style="font-weight: 400;">Accordion with Content</span></li>
7390. <li style="font-weight: 400;"><span style="font-weight: 400;">Accordion with Label + Input</span></li>
7391. <li style="font-weight: 400;"><span style="font-weight: 400;">Top navigation</span></li>
7392. </ul>
7393. <h3><b>How to Access and Use </b><b><i>Gradio UI for Figma</i></b></h3>
7394. <p><span style="font-weight: 400;">To start using the library, follow these simple steps:</span></p>
7395. <ol>
7396. <li style="font-weight: 400;"><b>Access the Library</b><span style="font-weight: 400;">: Access the component library directly by visiting our public Figma profile (https://www.figma.com/@futureatmozilla) or by searching for “Gradio UI for Figma” within the Figma Community section of your web or desktop Figma application.</span></li>
7397. <li style="font-weight: 400;"><b>Explore the Documentation</b><span style="font-weight: 400;">: Familiarize yourself with the components and guidelines to make the most out of your design process.</span></li>
7398. <li style="font-weight: 400;"><b>Connect with Us</b><span style="font-weight: 400;">: Connect with us by following our Figma profile or emailing us at </span><a href="mailto:innovations@mozilla.com"><span style="font-weight: 400;">innovations@mozilla.com</span></a></li>
7399. </ol>
7400. &lt;p&gt;The post &lt;a href=&quot;https://hacks.mozilla.org/2024/04/prototype-even-faster-with-the-gradio-ui-for-figma-component-library/&quot;&gt;Prototype even faster with the Gradio UI for Figma component library&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>
7401. <pubDate>Thu, 11 Apr 2024 15:13:48 +0000</pubDate>
7402. <dc:creator>Melissa Thermidor</dc:creator>
7403. </item>
7404. <item>
7405. <title>Mozilla Thunderbird: Thunderbird for Android / K-9 Mail: March 2024 Progress Report</title>
7406. <guid isPermaLink="false">https://blog.thunderbird.net/?p=1662</guid>
7407. <link>https://blog.thunderbird.net/2024/04/thunderbird-for-android-k-9-mail-march-2024-progress-report/</link>
7408. <description>&lt;p&gt;&lt;img alt=&quot;Featured graphic for &amp;quot;Thunderbird for Android March 2024 Progress Report&amp;quot; with stylized Thunderbird logo and K-9 Mail Android icon, resembling an envelope with dog ears.&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;360&quot; src=&quot;https://blog.thunderbird.net/files/2024/04/Progress-Report-March-2024-768x432.jpg&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
7409. <p>If you’ve been wondering how the work to turn K-9 Mail into Thunderbird for Android is coming along, you’ve found the right place. This blog post contains a report of our development activities in March 2024. </p>
7410.  
7411.  
7412.  
7413. <p>We’ve published monthly progress reports for a while now. If you’re interested in what happened previously, check out <a href="https://blog.thunderbird.net/2024/03/thunderbird-for-android-k-9-mail-february-2024-progress-report/">February’s progress report</a>. The report for the preceding month is usually linked in the first section of a post. But you can also browse the <a href="https://blog.thunderbird.net/category/thunderbird-mobile/">Android section of our blog</a> to find progress reports and release announcements.</p>
7414.  
7415.  
7416.  
7417. <h3>Fixing bugs</h3>
7418.  
7419.  
7420.  
7421. <p>For K-9 Mail, new stable releases typically include a lot of changes. K-9 Mail 6.800 was <a href="https://github.com/thunderbird/thunderbird-android/compare/6.603...6.800">no exception</a>. That means a lot of opportunities to accidentally introduce new bugs. And while we test the app in several ways – manual tests, automated tests, and via beta releases – there’s always some bugs that aren’t caught and make it into a stable version. So we typically spend a couple of weeks after a new major release fixing the bugs reported by our users.</p>
7422.  
7423.  
7424.  
7425. <h4>K-9 Mail 6.801</h4>
7426.  
7427.  
7428.  
7429. <h5>Stop capitalizing email addresses</h5>
7430.  
7431.  
7432.  
7433. <p>One of the known bugs was that some software keyboards automatically capitalized words when entering the email address in the first account setup screen. A user opened a <a href="https://github.com/thunderbird/thunderbird-android/issues/7665">bug</a> and provided enough information (<img alt="❤" class="wp-smiley" src="https://s.w.org/images/core/emoji/14.0.0/72x72/2764.png" style="height: 1em;" />) for us to reproduce the issue and come up with a <a href="https://github.com/thunderbird/thunderbird-android/pull/7694">fix</a>.</p>
7434.  
7435.  
7436.  
7437. <h5>Line breaks in single line text inputs</h5>
7438.  
7439.  
7440.  
7441. <p>At the end of the beta phase a user <a href="https://github.com/thunderbird/thunderbird-android/issues/7670">noticed</a> that K-9 Mail wasn’t able to connect to their email account even though they copy-pasted the correct password to the app. It turned out that the text in the clipboard ended with a line break. The single line text input we use for the password field didn’t automatically strip that line break and didn’t give any visual indication that there was one.</p>
7442.  
7443.  
7444.  
7445. <p>While we knew about this issue, we decided it wasn’t important enough to delay the release of K-9 Mail 6.800. After the release we took some time to <a href="https://github.com/thunderbird/thunderbird-android/pull/7699">fix</a> the problem.</p>
7446.  
7447.  
7448.  
7449. <h5>DNSSEC? Is anyone using that?</h5>
7450.  
7451.  
7452.  
7453. <p>When setting up an account, the app attempts to automatically find the server settings for the given email address. One part of this mechanism is looking up the email domain’s <a href="https://en.wikipedia.org/wiki/MX_record">MX record</a>. We intended for this lookup to support DNSSEC and specifically looked for a library supporting this.</p>
7454.  
7455.  
7456.  
7457. <p>Thanks to a beta tester we learned that DNSSEC signatures were never checked. The solution turned out to be embarrassingly simple: <a href="https://github.com/thunderbird/thunderbird-android/pull/7654/files">use the library in a way that it actually validates signatures</a>.</p>
7458.  
7459.  
7460.  
7461. <h5>Strange error message on OAuth 2.0 failure</h5>
7462.  
7463.  
7464.  
7465. <p>A user in our support forum <a href="https://forum.k9mail.app/t/error-when-using-oauth2-cannot-serialize-abstract-class/8188">reported</a> a strange error message (“Cannot serialize abstract class com.fsck.k9.mail.oauth.XOAuth2Response”) when using OAuth 2.0 while adding their email account. Our intention was to display the error message returned by the OAuth server. Instead an internal error occurred. </p>
7466.  
7467.  
7468.  
7469. <p>We tracked this down to the tool optimizing the app by stripping unused code and resources when building the final APK. The optimizer was removing a bit too much. But once the issue was identified, the <a href="https://github.com/thunderbird/thunderbird-android/pull/7698">fix</a> was simple enough.</p>
7470.  
7471.  
7472.  
7473. <h5>Crash when downloading an attachment</h5>
7474.  
7475.  
7476.  
7477. <p>Shortly after K-9 Mail 6.800 was made available on Google Play, I checked the list of reported app crashes in the developer console. Not a lot of users had gotten the update yet. So there were only very few reports. One was about a crash that occurred when the progress dialog was displayed while downloading an attachment. </p>
7478.  
7479.  
7480.  
7481. <p>The crash had been reported before. But the number of crashes never crossed the threshold where we consider a crash important enough to actually look at. </p>
7482.  
7483.  
7484.  
7485. <p>It turned out that the code contained the bug since it was first added in 2017. It was a race condition that was very timing sensitive. And so it worked fine much more often than it did not. </p>
7486.  
7487.  
7488.  
7489. <p><a href="https://github.com/thunderbird/thunderbird-android/pull/7689">The fix</a> was simple enough. So now this bug is history.</p>
7490.  
7491.  
7492.  
7493. <h5>Don’t write novels in the subject line</h5>
7494.  
7495.  
7496.  
7497. <p>The app was crashing when trying to send a message with a very long subject line (around 1000 characters). This, too, wasn’t a new bug. But the crash occurred rarely enough that we didn’t notice it before.</p>
7498.  
7499.  
7500.  
7501. <p>The bug is <a href="https://github.com/thunderbird/thunderbird-android/pull/7687">fixed</a> now. But it’s still best practice to keep the subject short!</p>
7502.  
7503.  
7504.  
7505. <h4>Work on K-9 Mail 6.802</h4>
7506.  
7507.  
7508.  
7509. <p>Even though we fixed quite a few bugs in K-9 Mail 6.801, there’s still more work to do. Besides fixing a couple of minor issues, K-9 Mail 6.802 will include the following changes.</p>
7510.  
7511.  
7512.  
7513. <h5>F-Droid metadata</h5>
7514.  
7515.  
7516.  
7517. <p>In preparation of building two apps (Thunderbird for Android and K-9 Mail), we moved the app description and screenshots that are used for F-Droid’s app listing to a new location inside our source code repository. We later found out that this new location is not supported by F-Droid, leading to an empty app description on the F-Droid website and inside their app.</p>
7518.  
7519.  
7520.  
7521. <p>We switched to a different approach and hope this will fix the app description once K-9 Mail 6.802 is released.</p>
7522.  
7523.  
7524.  
7525. <h5>Push not working due to missing permission</h5>
7526.  
7527.  
7528.  
7529. <p>Fresh installs of the app on Android 14 no longer automatically get the permission to schedule exact alarms. But this permission is necessary for Push to work. This was a known issue. But since it only affects new installs and users can manually grant this permission via Android settings, we decided not to delay the stable release until we added a user interface to guide the user through the permission flow.</p>
7530.  
7531.  
7532.  
7533. <p>K-9 Mail 6.802 will include a first step to improve the user experience. If Push is enabled but the permission to schedule exact alarms hasn’t been granted, the app will change the ongoing Push notification to ask the user to grant this permission.</p>
7534.  
7535.  
7536.  
7537. <figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-7 is-layout-flex wp-block-gallery-is-layout-flex">
7538. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/04/image.png"><img alt="" class="wp-image-1663" height="1270" src="https://blog.thunderbird.net/files/2024/04/image-600x1270.png" width="600" /></a></figure>
7539.  
7540.  
7541.  
7542. <figure class="wp-block-image size-large"><a href="https://blog.thunderbird.net/files/2024/04/image-1.png"><img alt="" class="wp-image-1664" height="1270" src="https://blog.thunderbird.net/files/2024/04/image-1-600x1270.png" width="600" /></a></figure>
7543. </figure>
7544.  
7545.  
7546.  
7547. <p>In a future update we’ll expand on that and ask the user to grant the permission before allowing them to enable Push.</p>
7548.  
7549.  
7550.  
7551. <h3>What about new features?</h3>
7552.  
7553.  
7554.  
7555. <p>Of course we haven’t forgotten about our <a href="https://developer.thunderbird.net/planning/android-roadmap">roadmap</a>. As mentioned in <a href="https://blog.thunderbird.net/2024/03/thunderbird-for-android-k-9-mail-february-2024-progress-report/">February’s progress report</a> we’ve started work on switching the user interface to use Material 3 and adding/improving Android 14 compatibility.</p>
7556.  
7557.  
7558.  
7559. <p>There’s not much to show yet. Some Material 3 changes have been merged already. But the user interface in our development version is currently very much in a transitional phase.</p>
7560.  
7561.  
7562.  
7563. <p>The Android 14 compatibility changes will be tested in beta versions first, and then back-ported to K-9 Mail 6.8xx.</p>
7564.  
7565.  
7566.  
7567. <h3>Releases</h3>
7568.  
7569.  
7570.  
7571. <p>In March 2024 we published the following stable release:</p>
7572.  
7573.  
7574.  
7575. <ul>
7576. <li><a href="https://github.com/thunderbird/thunderbird-android/releases/tag/6.801">K-9 Mail v6.801</a> (2024-03-11)</li>
7577. </ul>
7578.  
7579.  
7580.  
7581. <p>There hasn’t been a release of a new beta version in March.</p>
7582. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2024/04/thunderbird-for-android-k-9-mail-march-2024-progress-report/&quot;&gt;Thunderbird for Android / K-9 Mail: March 2024 Progress Report&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>
7583. <pubDate>Thu, 11 Apr 2024 13:00:00 +0000</pubDate>
7584. <dc:creator>cketti</dc:creator>
7585. </item>
7586. <item>
7587. <title>Chris H-C: How to go from “Looks like something changed in a Firefox Desktop version” to “Here is a list of potential culprit bugs”</title>
7588. <guid isPermaLink="false">http://chuttenblog.wordpress.com/?p=6362</guid>
7589. <link>https://chuttenblog.wordpress.com/2024/04/10/how-to-go-from-looks-like-something-changed-in-a-firefox-desktop-version-to-here-is-a-list-of-potential-culprit-bugs/</link>
7590. <description>&lt;p&gt;This will mostly be helpful to Firefox Desktop folks, so if you’re not one of those, please instead enjoy a different blogpost. I recommend &lt;a href=&quot;https://chuttenblog.wordpress.com/2021/10/22/this-week-in-glean-the-three-roles-of-data-engagements/&quot;&gt;this one about the three roles of data engagements&lt;/a&gt;.&lt;/p&gt;
7591.  
7592.  
7593.  
7594. <p>So you’ve found yourself a plot that looks like this:</p>
7595.  
7596.  
7597. <div class="wp-block-image">
7598. <figure class="aligncenter size-large"><img alt="A timeseries bar plot that begins as an uptake curve then has a sudden drop around February 22. There is no legend and no y-axis as they are unimportant, and sometimes I like to be cagey about absolute figures." class="wp-image-6365" height="432" src="https://chuttenblog.wordpress.com/wp-content/uploads/2024/04/image.png?w=524" width="524" /></figure></div>
7599.  
7600.  
7601. <p>You suspect this has something to do with a code change because, wouldn’t you know it, the sharp decline starts around Feb 22 and we released Firefox 123 on Feb 20. But where do you go from here? Here’s a step-by-step of how I went from this plot arriving in Slack#data-help to finding the bugfix that most likely caused the change:</p>
7602.  
7603.  
7604.  
7605. <h3>1. Ensure this is actually a version-specific change</h3>
7606.  
7607.  
7608.  
7609. <p>It’s interesting that the cliff in the plot happened near a release day, and it’s an excellent intuition to consider code releases for these sorts of sea-changes in data volume or character. But we should verify that this is the case by grouping by <code>mozfun.norm.truncate_version(app_version, 'major') AS major_version</code> which in our case gives us:</p>
7610.  
7611.  
7612. <div class="wp-block-image">
7613. <figure class="aligncenter size-large"><img alt="The same timeseries bar plot as before, but coloured to show groups by major Firefox Desktop version. The cliff happens solely in the colours for Firefox 123 and above." class="wp-image-6369" height="426" src="https://chuttenblog.wordpress.com/wp-content/uploads/2024/04/image-1.png?w=567" width="567" /></figure></div>
7614.  
7615.  
7616. <p>Sure enough, in this case the volume cliff happens entirely within the Firefox 123+ colours. If this isn’t what you get, then it’s somewhat less likely that this is caused by a client code change and this guide might not help you. But for us this is near-certain confirmation that the change in the data is caused by a code change that landed in Firefox 123… but which one?</p>
7617.  
7618.  
7619.  
7620. <p>( This is where I spent a little time checking some frequent “gotcha” changes that could’ve happened. I checked: was it because data went from all-channel to pre-release-only? (No, the probe definitions didn’t change and the fall isn’t severe enough for that (would look more like an order of magnitude)) Was it because specific instrumentation within the group happened to expire in Fx123? (No, the first plot is grouped by specific probe, and all of the groups shared the same shape as their sum) Was it an incredibly-successful engagement-boosting experiment that ended? (No, there haven’t been any relevant experiments since last July) )</p>
7621.  
7622.  
7623.  
7624. <h3>2. Figure out which Nightly builds are affected</h3>
7625.  
7626.  
7627.  
7628. <p>Firefox Desktop releases new software versions twice a day on the Nightly channel. We can look at the numbers reported by these builds to narrow down what specific 12h period the code landed that caused this drastic shift. Or, well, you’d think we could, but when you group by <code>build_id</code> you get:</p>
7629.  
7630.  
7631. <div class="wp-block-image">
7632. <figure class="aligncenter size-large"><img alt="Another bar plot, but instead of the x-axis being time it is now "build id" which is a timestamp of a sort. The data is all over the place and patchy with no or little clear pattern." class="wp-image-6373" height="406" src="https://chuttenblog.wordpress.com/wp-content/uploads/2024/04/image-2.png?w=623" width="623" /></figure></div>
7633.  
7634.  
7635. <p>Because our Nightly population isn’t randomly distributed across timezones, there are usage patterns that affect the population who use which build on which day. And sometimes there are “respins” where specific days will have more than 2 nightlies. And since our Nightly population is so small (You Can Help! <a href="https://www.mozilla.org/firefox/channel/desktop/">Download Nightly Today</a>!), and this data is a little sparse to begin with, little changes have big effects.</p>
7636.  
7637.  
7638.  
7639. <p>No, far more commonly the correct thing to do is to look at what I call a “build day”. This is how <a href="https://glam.telemetry.mozilla.org/">GLAM</a> makes things useful, and this is how I make patterns visible. So group by <code>SUBSTR(build_id, 1, 8) AS build_day,</code> and you get:</p>
7640.  
7641.  
7642. <div class="wp-block-image">
7643. <figure class="aligncenter size-large"><img alt="It looks like a timeseries bar plot, but the x-axis is "build day" so it isn't quite. Notably, there's a sudden cliff starting with the nightlies for January 18." class="wp-image-6377" height="406" src="https://chuttenblog.wordpress.com/wp-content/uploads/2024/04/image-3.png?w=618" width="618" /></figure></div>
7644.  
7645.  
7646. <p>Much better. We can see that the change likely landed in Jan 18’s nightlies. That Jan 18-20 are all of a level suggests to me that it probably ended up in all of Jan 18’s nightly builds (if it only landed in one of the (normally) two nightly builds we’d expect to see a short fall-off where Jan 18 would be more like an average between Jan 17 and 19.). </p>
7647.  
7648.  
7649.  
7650. <p>Regardless of when during the day, we’re pretty sure we have this nailed down to only one day’s worth of patches! That’s good… but it could be better.</p>
7651.  
7652.  
7653.  
7654. <h3>3. Going from build days to pushlog</h3>
7655.  
7656.  
7657.  
7658. <p>Ever since I was the human glue keeping the (now-decommissioned) automated regression detection system “alerts.tmo” working, I’ve had a document on my disk reminding me how to transform build days or build_ids into a “pushlog” of changes that landed in the suspect builds. This is how it works:</p>
7659.  
7660.  
7661.  
7662. <ol>
7663. <li>Get the hg revisions of the suspect builds by looking through <a href="https://hg.mozilla.org/mozilla-central/firefoxreleases">this list of all firefox releases</a> for the suspect builds’ ids. You want the final build of the day <em>before</em> the first suspect build day and the final build of the final suspect build day, which in this case are Jan 17 and Jan 18, so we get f593f07c9772 and 9c0c2aab123:</li>
7664. </ol>
7665.  
7666.  
7667. <div class="wp-block-image">
7668. <figure class="aligncenter size-large"><img alt="A visual excerpt of the firefox releases list https://hg.mozilla.org/mozilla-central/firefoxreleases. For illustration only." class="wp-image-6380" height="241" src="https://chuttenblog.wordpress.com/wp-content/uploads/2024/04/image-4.png?w=433" width="433" /></figure></div>
7669.  
7670.  
7671. <ol start="2">
7672. <li>Put them into this template: <code>https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange={}&tochange={}</code> — which gives us <a href="https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f593f07c9772&tochange=9c0c2aaab123">https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f593f07c9772&tochange=9c0c2aaab123</a></li>
7673. </ol>
7674.  
7675.  
7676.  
7677. <p>This gives you a list of all changes that are in the suspect builds, plus links to the specific code changes and the relevant bugs, with the topic sentence from each commit right there for you. Handy!</p>
7678.  
7679.  
7680.  
7681. <h3>4. Going from a pushlog to a culprit</h3>
7682.  
7683.  
7684.  
7685. <p>This is where human pattern matching, domain expertise, organizational memory, culture and practices, and institutional conventions all combine… or, to put it another way, I don’t know how to help you get from the list of all code that <em>could</em> have caused your data change to the one (or more) likely suspects. My brain has handily built me a heuristic and not handed me the source code, alas. But I’ve noticed some patterns:</p>
7686.  
7687.  
7688.  
7689. <ul>
7690. <li>Any change that is backed out can be disregarded. Often for reasons of test failures changes will be backed out and relanded later. Sometimes that’s later the same day. Sometimes that’s outside our pushlog. Skip any changes that have been backed out by disregarding any commits from a bug that is mentioned before a commit that says “Backed out N changesets (bug ###)…”.</li>
7691.  
7692.  
7693.  
7694. <li>You can often luck out by just text searching for keywords. It is custom at Mozilla to try to be descriptive about the “what” of a change in the commit’s topic, so you could try looking for “telemetry” or “ping” or “glean” to see if there’s anything from the data collection system itself in there. Or, since this particular example had to do with Firefox Relay’s integration with Firefox Desktop, I looked for “relay” (no hits) and then “form” (which hit a few times, like on the word “information”, … but also on the culprit which was in the form detector code.)</li>
7695.  
7696.  
7697.  
7698. <li>This is a web view on the source code, so you’re not limited to what it gives you. If you have a mozilla-central checkout yourself, you can pull up the commits (if you’re using <a href="https://github.com/glandium/git-cinnabar">git-cinnabar</a> you can use its <code>hg2git</code> functionality to change the revs from hg to git) and dump their sum-total changes to a viewer, or pipe it through grep, or turn it into a spreadsheet you can go through row-by-row, or anything you want. I’m lazy so I always try keywording on the pushlog first, but these are always there for when I strike out.</li>
7699. </ul>
7700.  
7701.  
7702.  
7703. <h3>5. Getting it wrong</h3>
7704.  
7705.  
7706.  
7707. <p>Just because you found the one and only commit that landed in a suspect build that is at all related, even if that commit’s bug specifically mentions that it fixed a double-counting issue, even if there’s commentary in the code review that explains that they expect to see this exact change you just saw… you might be wrong.</p>
7708.  
7709.  
7710.  
7711. <p>Do not be brusque in your reporting. Do not cast blame. And for goodness’ sake be kind. Even if you are correct, being the person who caused a change that resulted in this investigation can be a not-fun experience. <em>Ask Me How I Know</em>.</p>
7712.  
7713.  
7714.  
7715. <p>Firefox Desktop is a complex system, and <a href="https://how.complexsystems.fail/">complex systems fail</a>. It’s in their nature.</p>
7716.  
7717.  
7718.  
7719. <hr class="wp-block-separator has-alpha-channel-opacity" />
7720.  
7721.  
7722.  
7723. <p>And that’s it! If you have any comments, question, or (better yet) improvements, please find me on <a href="https://chat.mozilla.org/#/room/#glean:mozilla.org">the #glean:mozilla.org channel on Matrix</a> and I’d love to chat.</p>
7724.  
7725.  
7726.  
7727. &lt;p&gt;:chutten&lt;/p&gt;</description>
7728. <pubDate>Wed, 10 Apr 2024 20:24:31 +0000</pubDate>
7729. <dc:creator>chuttenc</dc:creator>
7730. </item>
7731. <item>
7732. <title>Mozilla Thunderbird: Automated Testing: How We Catch Thunderbird Bugs Before You Do</title>
7733. <guid isPermaLink="false">https://blog.thunderbird.net/?p=1620</guid>
7734. <link>https://blog.thunderbird.net/2024/04/automated-testing-how-we-catch-thunderbird-bugs-before-you-do/</link>
7735. <description>&lt;p&gt;&lt;img alt=&quot;&quot; class=&quot;attachment-640x360 size-640x360 wp-post-image&quot; height=&quot;321&quot; src=&quot;https://blog.thunderbird.net/files/2024/04/Automated-testing-blog5.png&quot; width=&quot;640&quot; /&gt;&lt;/p&gt;
7736. <div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
7737. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=de&u=https://blog.thunderbird.net/2024/04/automated-testing-how-we-catch-thunderbird-bugs-before-you-do/" rel="noreferrer noopener" target="_blank">Auf Deutsch übersetzen</a></div>
7738.  
7739.  
7740.  
7741. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=fr&u=https://blog.thunderbird.net/2024/04/automated-testing-how-we-catch-thunderbird-bugs-before-you-do/" rel="noreferrer noopener" target="_blank">Traduire en français</a></div>
7742.  
7743.  
7744.  
7745. <div class="wp-block-button has-custom-font-size has-small-font-size"><a class="wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button" href="https://translate.google.com/translate?js=n&sl=auto&tl=ja&u=https://blog.thunderbird.net/2024/04/automated-testing-how-we-catch-thunderbird-bugs-before-you-do/" rel="noreferrer noopener" target="_blank">日本語に翻訳</a></div>
7746. </div>
7747.  
7748.  
7749.  
7750. <p>Since the release of <a href="https://blog.thunderbird.net/2023/07/our-fastest-most-beautiful-release-ever-thunderbird-115-supernova-is-here/">Thunderbird 115</a>, a big focus has been on improving the state of our automated testing. Automated testing increases the software quality by minimizing the number of bugs accidentally introduced by changes to the code. For each change made to Thunderbird, our testing machines run a set of tests across Windows, macOS, and Linux to detect mistakes and unintended consequences. For a single change (or a group of changes that land at the same time), 60 to 80 hours of machine time is used running tests.</p>
7751.  
7752.  
7753.  
7754. <p>Our code is going to be under more pressure than ever before – with a bigger team making more changes, and monthly releases reducing the time code spends on testing channels before being released. </p>
7755.  
7756.  
7757.  
7758. <p><em>We want to find the bugs before our users do.</em></p>
7759.  
7760.  
7761.  
7762. <h3>Why We’re Testing</h3>
7763.  
7764.  
7765.  
7766. <p>We’re not writing tests merely to make ourselves feel better. Tests improve Thunderbird by:</p>
7767.  
7768.  
7769.  
7770. <ul>
7771. <li><strong>Preventing mistakes</strong><br />If we test that some code behaves in an expected way, we’ll find out immediately if it no longer behaves that way. This means a shorter feedback loop, and we can fix the problem before it annoys the users.</li>
7772.  
7773.  
7774.  
7775. <li><strong>Finding out when somebody upstream breaks us</strong><br />Thunderbird is built from the Firefox code. The Firefox code, which we are not responsible for, is 30 to 40 times the size of the code we <em>are</em> responsible for. When something inevitably changes in Firefox that affects us, we want to know about it immediately so that we can respond.</li>
7776.  
7777.  
7778.  
7779. <li><strong>Freeing up human testers</strong><br />If we use computers to prove that the program does what it’s supposed to do, particularly if we avoid tedious repetition and difficult-to-set-up tasks, then the limited human resources we have can do more things that humans are better at.<br />For example, I’ve recently added tests that check 22 ways to trigger fetching mail, and 10 circumstances fetching mail might not work. There’s no way our human testers (great though they are) are testing all of them, but our automated tests can and do, several times a day.</li>
7780.  
7781.  
7782.  
7783. <li><strong>Thinking through what the code should be doing</strong><br />Testing forces an engineer to look at the code from a different point-of-view, and this is helpful to think about what the code is <em>supposed</em> to do in more circumstances. It also makes it easier to prove that the code does work in obscure circumstances.</li>
7784.  
7785.  
7786.  
7787. <li><strong>Finding existing bugs</strong><br />In software terms we’re working with some very old code, and much of it is untested. Testing it puts a fresh set of eyes on the code and reveals some of the mistakes of the past, and where the ravages of time have broken things. It also helps the person writing the tests to understand what the code does, a lot better than just reading the code does.</li>
7788. </ul>
7789.  
7790.  
7791.  
7792. <p>We’re not trying to completely cover a feature or every edge case in tests. We are trying to create a testing framework around the feature so that when we find a bug, as well as fixing it, we can easily write a test preventing the bug from happening again without being noticed. For too much of the code, this has been impossible without a weeks-long detour into tests.</p>
7793.  
7794.  
7795.  
7796. <h3>Breaking New Ground</h3>
7797.  
7798.  
7799.  
7800. <p>In the past few months we’ve figured out how to make automated tests for things that were previously impossible:</p>
7801.  
7802.  
7803.  
7804. <ul>
7805. <li>Communication with mail servers using encrypted channels.</li>
7806.  
7807.  
7808.  
7809. <li>OAuth2 authentication with mail servers.</li>
7810.  
7811.  
7812.  
7813. <li>Communication with web servers where a specific address must be used and an unencrypted channel must not be used.</li>
7814.  
7815.  
7816.  
7817. <li>Servers at any given host name or port. Previously, if we wanted to start a server for automated testing, it had to be on the local machine at a non-standard location. Now we can pretend that the server is anywhere, and using standard ports, which is needed for proper testing of account configuration features. (Actually, this <em>was </em>possible before, but now it’s much easier.)</li>
7818. </ul>
7819.  
7820.  
7821.  
7822. <p>These new abilities are being used to wrap better testing around account set-up features, ahead of the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1789966">new Account Hub development</a>, so that we can be sure nothing breaks without being noticed. They’re also helping test that collecting mail works when it should, or gives the error prompts we expect when it doesn’t.</p>
7823.  
7824.  
7825.  
7826. <h3>Code coverage</h3>
7827.  
7828.  
7829.  
7830. <p>We record every line of code that runs during our tests. Collecting all that data tells what code doesn’t run during our tests. If a block of code doesn’t run during any of our tests, nothing will tell us when it breaks until somebody uses the code and complains.</p>
7831.  
7832.  
7833.  
7834. <p>Our code coverage data can be viewed at<a href="https://coverage.thunderbird.net/"> coverage.thunderbird.net</a>. You can also look at Firefox’s data at<a href="https://coverage.moz.tools"> coverage.moz.tools</a>.</p>
7835.  
7836.  
7837.  
7838. <p>Looking at the data, you might notice that our overall number is now <em>lower</em> than it was when we started measuring. This doesn’t mean that our testing got worse, it actually shows where we added <em>a lot</em> of code (that isn’t maintained by us) in the third_party directory. For a better reflection of the progress we’ve made, check out the individual directories, especially mail/base which contains the most important user interface code.</p>
7839.  
7840.  
7841.  
7842. <ul>
7843. <li>Just setting up the code coverage tools and looking at the results uncovered several memory leaks. (A memory leak is where memory is allocated for a task and not released when it is no longer needed.) We fixed these leaks and some more that existed in our test code. We now have very low levels of memory leaking in our test runs, so if we make a mistake it is easy to spot.</li>
7844.  
7845.  
7846.  
7847. <li>Code coverage data can also point to code that is no longer used. We’ve removed some big chunks of this dead code, which means we’re not wasting time maintaining it.</li>
7848. </ul>
7849.  
7850.  
7851.  
7852. <h3>Mozmill no more</h3>
7853.  
7854.  
7855.  
7856. <p>Towards the end of last year we finally retired an old test suite known as Mozmill. Those tests were partially migrated to a different test suite (Mochitest) about four years ago, and things were mostly working fine so it wasn’t a priority to finish. These tests now do things in a more conventional way instead of relying on a bunch of clever but weird tricks.</p>
7857.  
7858.  
7859.  
7860. <h3>How much of the code is test code?</h3>
7861.  
7862.  
7863.  
7864. <p>About 27%. This is a very rough estimate based on the files in our code repository (minus some third-party directories) and whether they are inside a directory with “test” in the name or not. That’s risen from about 19% in the last five years.</p>
7865.  
7866.  
7867.  
7868. <p>There is no particular goal in mind, but I can imagine a future where there is as much test code as non-test code. If we achieve that, Thunderbird will be in a very healthy place.</p>
7869.  
7870.  
7871.  
7872. <figure class="wp-block-image size-full"><a href="https://blog.thunderbird.net/files/2024/03/Screenshot-2024-03-25-at-9.14.08 AM.png"><img alt="A stacked area chart showing the estimated lines of test code (in red) and non-test code (in blue) over time, from January 2019 to January 2024. The chart indicates both types of code increase over this period." class="wp-image-1621" height="974" src="https://blog.thunderbird.net/files/2024/03/Screenshot-2024-03-25-at-9.14.08 AM.png" width="1660" /></a></figure>
7873.  
7874.  
7875.  
7876. <p>Looking ahead, we’ll be asking contributors to add tests to their patches more often. This obviously depends on the circumstance. But if you’re adding or fixing something, that is the best time to ensure it continues to work in the future. As always, feel free to reach out if you need help writing or running tests, either via Matrix or Topicbox mailing lists:</p>
7877.  
7878.  
7879.  
7880. <ul>
7881. <li>Matrix: You can join our development chat channel at <a href="https://matrix.to/#/#maildev:mozilla.org?via=mozilla.org&via=matrix.org&via=trancart.eu&web-instance%5Belement.io%5D=chat.mozilla.org">#maildev:mozilla.org</a></li>
7882.  
7883.  
7884.  
7885. <li>Topicbox mailing list: The <a href="https://thunderbird.topicbox.com/groups/developers">Thunderbird Developers list</a> a good place to raise questions about Thunderbird development.</li>
7886. </ul>
7887.  
7888.  
7889.  
7890. <p><strong><span style="text-decoration: underline;">Geoff Lankow, Staff Engineer</span></strong></p>
7891. &lt;p&gt;The post &lt;a href=&quot;https://blog.thunderbird.net/2024/04/automated-testing-how-we-catch-thunderbird-bugs-before-you-do/&quot;&gt;Automated Testing: How We Catch Thunderbird Bugs Before You Do&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>
7892. <pubDate>Tue, 09 Apr 2024 17:03:36 +0000</pubDate>
7893. <dc:creator>Geoff Lankow</dc:creator>
7894. </item>
7895. <item>
7896. <title>Support.Mozilla.Org: Keeping you in the loop: What’s new in our Knowledge Base?</title>
7897. <guid isPermaLink="false">https://blog.mozilla.org/sumo/?p=4105</guid>
7898. <link>https://blog.mozilla.org/sumo/2024/04/09/keeping-you-in-the-loop-whats-new-in-our-knowledge-base/</link>
7899. <description>&lt;p&gt;Hello, SUMO community!&lt;/p&gt;
7900. <p>We’re setting the stage for something big: a revamp of our style guide designed to make our support content not just user-friendly, but user-delightful. To get a clearer picture of the SUMO user experience, we enlisted the help of an external agency, embarking on a research project designed to peel back the layers of how users interact with our platform. The results were quite revealing. Many users, it turns out, find themselves overwhelmed by the vast amount of information available, often feeling confused and struggling to pinpoint the exact answers they’re searching for. To address this, we’re rolling out targeted improvements focused enhancements to our style guides and contributor resources, aiming to refine how we organize, categorize, and present our support content in SUMO for a smoother, more intuitive user journey.</p>
7901. <p>Have questions or feedback? Drop us a message in this <a href="https://support.mozilla.org/en-US/forums/contributors/716916?last=87365">SUMO forum thread</a>.</p>
7902. <p><b>Refreshing the content taxonomy</b></p>
7903. <p>A key takeaway from the research was the users’ difficulty in navigating our content categories. This prompted us to rethink our approach to organizing support content, aiming for a better alignment with user needs and industry best practices. This project is in full swing, and we’ll be ready to share more details with you shortly.</p>
7904. <p><b>Auditing the Firefox content</b></p>
7905. <p>In our effort to align our content with user needs, we’ve initiated a comprehensive audit of all Firefox support articles. This exhaustive review aims to identify areas where we can reclassify content, eliminate outdated information, and consolidate similar topics. Our goal is to ensure that every piece of information in the KB is relevant, easy to understand, and directly beneficial to our users.</p>
7906. <p>We’re gearing up to share how you can contribute to this exciting initiative. Mark your calendars for the <a href="https://wiki.mozilla.org/Support:Community_Calls">SUMO Community Meeting</a> on Wednesday, April 10, 2024, where we’ll unveil more about this project.</p>
7907. <p><b>Updating the article types</b></p>
7908. <p>Using consistent content types for our knowledge base articles has many benefits including ease of navigation and improved clarity and organization, in addition to helping us create content more effectively. We are transitioning to categorizing external knowledge base articles into four types, each serving a specific purpose:</p>
7909. <ul>
7910. <li><b>About</b>: These articles address “What is…” questions, providing essential information to help readers understand a topic.</li>
7911. <li><b>How-to</b>: These articles focus on answering “How to…?” questions, guiding readers through the steps required to achieve a specific goal or procedure.</li>
7912. <li><b>Troubleshooting</b>: These articles assist users in identifying, diagnosing, and resolving common issues they may encounter with a product, service, or feature by addressing “How to…?” questions related to problem-solving.</li>
7913. <li><b>FAQ</b>: These articles contain concise answers to frequently asked questions on a single topic, which may not fit within other individual KB articles, providing a quick reference for common inquiries.</li>
7914. </ul>
7915. <p>Stay tuned for additional training and documentation on these article types!</p>
7916. <p><b>Reducing cognitive load </b><b><br />
7917. </b>We believe finding information should not be akin to a mental obstacle course. Focused on minimizing cognitive load, we’ve outlined a series of strategies aimed at guiding users directly to the information they need, no fuss involved. Below are the key strategies we’re implementing:</p>
7918. <ul>
7919. <li><b>Straight to the point with inline images and icons</b>: We’re transitioning from textual guidance to visual demonstrations. By embedding inline targeted UI captures and icons directly into the article flow, we aim to provide a more visual path for users, minimizing the need for mental translation of text into actions. But, hang on – we haven’t forgotten about making these changes work for everyone. For those using screen readers, we’re counting on you to help us ensure every image and icon comes with comprehensive alt text, making every visual accessible through sound. And on the localization front, your skills are more important than ever. We’re calling on you to assist in capturing and adding alt text to localized images, ensuring it’s accessible and resonant for every member of our global community. For details see <a href="https://support.mozilla.org/en-US/kb/how-place-images-article#w_effective-use-of-inline-images">Effective use of inline images</a>.</li>
7920. <li><b>Cleaner, more focused images with SUI (simplified user interfaces)</b>: To make things even clearer, we’re simplifying our product’s UI in screenshots to just the essentials. This not only makes the images easier to follow but also means they’ll stay accurate longer, even if small UI changes happen. For more info, see <a href="https://support.mozilla.org/en-US/kb/how-to-make-screenshots#w_simplifications">Simplifications</a>.</li>
7921. <li><b>Streamlined steps with annotated screenshots</b>: For tasks that necessitate two or more clicks or actions on a single screen, we’re shifting to a more intuitive approach: using screenshots marked with numbered annotations. This strategy will clear away the need for multiple, similar screenshots, making instructions easier to follow while minimizing scrolling.</li>
7922. </ul>
7923. <p>Keep an eye out for the updated style guides – they’re coming soon!</p>
7924. <p><b>What this means for you</b></p>
7925. <p>Our updates will be rolling out from Q2 to Q4 2024, and we’re thrilled to have you on board as we bring these changes to life. The kickoff is just around the corner, so stay tuned for updates! Have thoughts to share or looking to contribute? We’re all ears. Engage with us directly on this <a href="https://support.mozilla.org/en-US/forums/contributors/716916?last=87365">SUMO forum thread</a>. Your feedback and involvement are crucial as we progress together.</p>
7926. &lt;p&gt;&lt;b&gt;Thank you for making a difference!&lt;/b&gt;&lt;/p&gt;</description>
7927. <pubDate>Tue, 09 Apr 2024 16:20:28 +0000</pubDate>
7928. <dc:creator>Lucas Siebert</dc:creator>
7929. </item>
7930. <item>
7931. <title>The Rust Programming Language Blog: Announcing Rust 1.77.2</title>
7932. <guid isPermaLink="true">https://blog.rust-lang.org/2024/04/09/Rust-1.77.2.html</guid>
7933. <link>https://blog.rust-lang.org/2024/04/09/Rust-1.77.2.html</link>
7934. <description>&lt;p&gt;The Rust team has published a new point release of Rust, 1.77.2. Rust is a
7935. programming language that is empowering everyone to build reliable and
7936. efficient software.</p>
7937. <p>If you have a previous version of Rust installed via rustup, getting Rust
7938. 1.77.2 is as easy as:</p>
7939. <pre><code>rustup update stable
7940. </code></pre>
7941. <p>If you don't have it already, you can <a href="https://www.rust-lang.org/install.html">get <code>rustup</code></a> from the
7942. appropriate page on our website.</p>
7943. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/04/09/Rust-1.77.2.html#whats-in-1772" id="whats-in-1772"></a>What's in 1.77.2</h3>
7944. <p>This release includes a fix for <a href="https://www.cve.org/CVERecord?id=CVE-2024-24576">CVE-2024-24576</a>.</p>
7945. <p>Before this release, the Rust standard library did not properly escape
7946. arguments when invoking batch files (with the <code>bat</code> and <code>cmd</code> extensions) on
7947. Windows using the <a href="https://doc.rust-lang.org/std/process/struct.Command.html"><code>Command</code></a> API. An attacker able to control the arguments
7948. passed to the spawned process could execute arbitrary shell commands by
7949. bypassing the escaping.</p>
7950. <p>This vulnerability is <strong>CRITICAL</strong> if you are invoking batch files on Windows
7951. with untrusted arguments. No other platform or use is affected.</p>
7952. <p><a href="https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html">You can learn more about the vulnerability in the dedicated
7953. advisory.</a></p>
7954. <h4><a class="anchor" href="https://blog.rust-lang.org/2024/04/09/Rust-1.77.2.html#contributors-to-1772" id="contributors-to-1772"></a>Contributors to 1.77.2</h4>
7955. <p>Many people came together to create Rust 1.77.2. We couldn't have done it
7956. without all of you. &lt;a href=&quot;https://thanks.rust-lang.org/rust/1.77.2/&quot;&gt;Thanks!&lt;/a&gt;&lt;/p&gt;</description>
7957. <pubDate>Tue, 09 Apr 2024 00:00:02 +0000</pubDate>
7958. <dc:creator>The Rust Security Response WG</dc:creator>
7959. </item>
7960. <item>
7961. <title>The Rust Programming Language Blog: Changes to Rust's WASI targets</title>
7962. <guid isPermaLink="true">https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html</guid>
7963. <link>https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html</link>
7964. <description>&lt;p&gt;&lt;a href=&quot;https://bytecodealliance.org/articles/WASI-0.2&quot;&gt;WASI 0.2 was recently
7965. stabilized</a>, and Rust has begun
7966. implementing first-class support for it in the form of a dedicated new target.
7967. Rust 1.78 will introduce new <code>wasm32-wasip1</code> (tier 2) and <code>wasm32-wasip2</code> (tier
7968. 3) targets. <code>wasm32-wasip1</code> is an effective rename of the existing <code>wasm32-wasi</code>
7969. target, freeing the target name up for an eventual WASI 1.0 release. <strong>Starting
7970. Rust 1.78 (May 2nd, 2024), users of WASI 0.1 are encouraged to begin migrating
7971. to the new <code>wasm32-wasip1</code> target before the existing <code>wasm32-wasi</code> target is
7972. removed in Rust 1.84 (January 5th, 2025).</strong></p>
7973. <p>In this post we'll discuss the introduction of the new targets, the motivation
7974. behind it, what that means for the existing WASI targets, and a detailed
7975. schedule for these changes. This post is about the WASI targets only; the
7976. existing <code>wasm32-unknown-unknown</code> and <code>wasm32-unknown-emscripten</code> targets are
7977. unaffected by any changes in this post.</p>
7978. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html#introducing-wasm32-wasip2" id="introducing-wasm32-wasip2"></a>Introducing <code>wasm32-wasip2</code></h3>
7979. <p>After nearly five years of work the <a href="https://wasi.dev">WASI 0.2 specification</a>
7980. was recently stabilized. This work builds on <a href="https://component-model.bytecodealliance.org">WebAssembly
7981. Components</a> (think: strongly-typed
7982. ABI for Wasm), providing standard interfaces for things like asynchronous IO,
7983. networking, and HTTP. This will finally make it possible to write asynchronous
7984. networked services on top of WASI, something which wasn't possible using WASI
7985. 0.1.</p>
7986. <p>People interested in compiling Rust code to WASI 0.2 today are able to do so
7987. using the <a href="https://github.com/bytecodealliance/cargo-component">cargo-component</a>
7988. tool. This tool is able to take WASI 0.1 binaries, and transform them to WASI 0.2
7989. Components using a shim. It also provides native support for common cargo
7990. commands such as <code>cargo build</code>, <code>cargo test</code>, and <code>cargo run</code>. While it
7991. introduces some inefficiencies because of the additional translation layer, in
7992. practice this already works really well and people should be able to get
7993. started with WASI 0.2 development.</p>
7994. <p>We're however keen to begin making that translation layer obsolete. And for
7995. that reason we're happy to share that Rust has made its first steps towards
7996. that with the introduction of the <a href="https://doc.rust-lang.org/rustc/platform-support.html#tier-3">tier
7997. 3</a> <code>wasm32-wasip2</code>
7998. target landing in Rust 1.78. <strong>This will initially miss a lot of expected</strong>
7999. <strong>features such as stdlib support, and we don't recommend people use this target</strong>
8000. <strong>quite yet.</strong> But as we fill in those missing features over the coming months, we
8001. aim to eventually meet the criteria to become a tier 2 target, at which
8002. point the <code>wasm32-wasip2</code> target would be considered ready for general use. This
8003. work will happen through 2024, and we expect for this to land before the end of
8004. the calendar year.</p>
8005. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html#renaming-wasm32-wasi-to-wasm32-wasip1" id="renaming-wasm32-wasi-to-wasm32-wasip1"></a>Renaming <code>wasm32-wasi</code> to <code>wasm32-wasip1</code></h3>
8006. <p>The original name for what we now call WASI 0.1 was "WebAssembly System
8007. Interface, snapshot 1". Rust shipped support for this in 2019, and we did so
8008. knowing the target would likely undergo significant changes in the future. With
8009. the knowledge we have today though, we would not have chosen to introduce the
8010. "WASI, snapshot 1" target as <code>wasm32-wasi</code>. We should have instead chosen to add
8011. some suffix to the initial target triple so that the eventual stable WASI 1.0
8012. target can just be called <code>wasm32-wasi</code>.</p>
8013. <p>In anticipation of both an eventual WASI 1.0 target, and to preserve consistency
8014. between target names, we'll begin rolling out a name change to the existing WASI
8015. 0.1 target. Starting in Rust 1.78 (May 2nd, 2024) a new <code>wasm32-wasip1</code> target
8016. will become available. Starting Rust 1.81 (September 5th, 2024) we will begin
8017. warning existing users of <code>wasm32-wasi</code> to migrate to <code>wasm32-wasip1</code>. And
8018. finally in Rust 1.84 (January 9th, 2025) the <code>wasm32-wasi</code> target will no longer
8019. be shipped on the stable release channel. This will provide an 8 month
8020. transition period for projects to switch to the new target name when they update
8021. their Rust toolchains.</p>
8022. <p>The name <code>wasip1</code> can be read as either "WASI (zero) point one" or "WASI preview
8023. one". The official specification uses the "preview" moniker, however in most
8024. communication the form "WASI 0.1" is now preferred. This target triple was
8025. chosen because it not only maps to both terms, but also more closely resembles
8026. the target terminology used in <a href="https://go.dev/blog/wasi">other programming
8027. languages</a>. This is something the WASI Preview 2
8028. specification <a href="https://github.com/WebAssembly/WASI/tree/f45e72e5294e990c23d548eea32fd35c80525fd6/preview2#introduction">also makes note
8029. of</a>.</p>
8030. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html#timeline" id="timeline"></a>Timeline</h3>
8031. <p>This table provides the dates and cut-offs for the target rename from
8032. <code>wasm32-wasi</code> to <code>wasm32-wasip1</code>. The dates in this table do not apply to the
8033. newly-introduced <code>wasm32-wasi-preview1-threads</code> target; this will be renamed to
8034. <code>wasm32-wasip1-threads</code> in Rust 1.78 without going through a transition period.
8035. The tier 3 <code>wasm32-wasip2</code> target will also be made available in Rust 1.78.</p>
8036. <table>
8037. <thead>
8038. <tr>
8039. <th>date</th>
8040. <th>Rust Stable</th>
8041. <th>Rust Beta</th>
8042. <th>Rust Nightly</th>
8043. <th>Notes</th>
8044. </tr>
8045. </thead>
8046. <tbody>
8047. <tr>
8048. <td>2024-02-08</td>
8049. <td>1.76</td>
8050. <td>1.77</td>
8051. <td>1.78</td>
8052. <td><code>wasm32-wasip1</code> available on nightly</td>
8053. </tr>
8054. <tr>
8055. <td>2024-03-21</td>
8056. <td>1.77</td>
8057. <td>1.78</td>
8058. <td>1.79</td>
8059. <td><code>wasm32-wasip1</code> available on beta</td>
8060. </tr>
8061. <tr>
8062. <td>2024-05-02</td>
8063. <td>1.78</td>
8064. <td>1.79</td>
8065. <td>1.80</td>
8066. <td><code>wasm32-wasip1</code> available on stable</td>
8067. </tr>
8068. <tr>
8069. <td>2024-06-13</td>
8070. <td>1.79</td>
8071. <td>1.80</td>
8072. <td>1.81</td>
8073. <td>warn if <code>wasm32-wasi</code> is used on nightly</td>
8074. </tr>
8075. <tr>
8076. <td>2024-07-25</td>
8077. <td>1.80</td>
8078. <td>1.81</td>
8079. <td>1.82</td>
8080. <td>warn if <code>wasm32-wasi</code> is used on beta</td>
8081. </tr>
8082. <tr>
8083. <td>2024-09-05</td>
8084. <td>1.81</td>
8085. <td>1.82</td>
8086. <td>1.83</td>
8087. <td>warn if <code>wasm32-wasi</code> is used on stable</td>
8088. </tr>
8089. <tr>
8090. <td>2024-10-17</td>
8091. <td>1.82</td>
8092. <td>1.83</td>
8093. <td>1.84</td>
8094. <td><code>wasm32-wasi</code> unavailable on nightly</td>
8095. </tr>
8096. <tr>
8097. <td>2024-11-28</td>
8098. <td>1.83</td>
8099. <td>1.84</td>
8100. <td>1.85</td>
8101. <td><code>wasm32-wasi</code> unavailable on beta</td>
8102. </tr>
8103. <tr>
8104. <td>2025-01-09</td>
8105. <td>1.84</td>
8106. <td>1.85</td>
8107. <td>1.86</td>
8108. <td><code>wasm32-wasi</code> unavailable on stable</td>
8109. </tr>
8110. </tbody>
8111. </table>
8112. <h3><a class="anchor" href="https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html#conclusion" id="conclusion"></a>Conclusion</h3>
8113. <p>In this post we've discussed the upcoming updates to Rust's WASI targets. Come
8114. Rust 1.78 the <code>wasm32-wasip1</code> (tier 2) and <code>wasm32-wasip2</code> (tier 3) targets will
8115. be added. In Rust 1.81 we will begin warning if <code>wasm32-wasi</code> is being used. And
8116. in Rust 1.84, the existing <code>wasm32-wasi</code> target will be removed. This will free
8117. up <code>wasm32-wasi</code> to eventually be used for a WASI 1.0 target. Users will have 8
8118. months to switch to the new target name when they update their Rust toolchains.</p>
8119. <p>The <code>wasm32-wasip2</code> target marks the start of native support for WASI 0.2. In
8120. order to target it today from Rust, people are encouraged to use
8121. <a href="https://github.com/bytecodealliance/cargo-component">cargo-component</a> tool
8122. instead. The plan is to eventually graduate <code>wasm32-wasip2</code> to a tier-2 target,
8123. at which point <code>cargo-component</code> will be upgraded to support it natively instead.</p>
8124. <p>With WASI 0.2 finally stable, it's an exciting time for WebAssembly development.
8125. We're happy for Rust to begin implementing native support for WASI 0.2, and
8126. we're excited about what this will enable people to build.&lt;/p&gt;</description>
8127. <pubDate>Tue, 09 Apr 2024 00:00:01 +0000</pubDate>
8128. <dc:creator>Yosh Wuyts</dc:creator>
8129. </item>
8130.  
8131. </channel>
8132. </rss>
8133.