<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[The Daily Diff]]></title><description><![CDATA[Dev & AI News. Every Day. Verdict Included]]></description><link>https://newsletter.thedailydiff.dev</link><image><url>https://substackcdn.com/image/fetch/$s_!iUSu!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff1ad40e4-169f-4b28-8f91-1a572b4007e1_800x800.png</url><title>The Daily Diff</title><link>https://newsletter.thedailydiff.dev</link></image><generator>Substack</generator><lastBuildDate>Fri, 20 Nov 2026 18:37:16 GMT</lastBuildDate><atom:link href="https://newsletter.thedailydiff.dev/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Niko from Axrisi]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[dailydiff@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[dailydiff@substack.com]]></itunes:email><itunes:name><![CDATA[Niko from Axrisi]]></itunes:name></itunes:owner><itunes:author><![CDATA[Niko from Axrisi]]></itunes:author><googleplay:owner><![CDATA[dailydiff@substack.com]]></googleplay:owner><googleplay:email><![CDATA[dailydiff@substack.com]]></googleplay:email><googleplay:author><![CDATA[Niko from Axrisi]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Anthropic's IPO filing says Claude's rate limits can change]]></title><description><![CDATA[The Daily Diff &#183; Friday, November 20, 2026]]></description><link>https://newsletter.thedailydiff.dev/p/anthropics-ipo-filing-says-claudes</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/anthropics-ipo-filing-says-claudes</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Fri, 20 Nov 2026 15:31:09 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/d90f5809-722a-4f90-afb9-cdf912e3c812_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-eF9IE70addQ" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;eF9IE70addQ&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/eF9IE70addQ?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-20-anthropic-day-one/">Watch the video, transcript and sources</a></p><pre><code>+ Anthropic: first day on Nasdaq
- OpenSSL: a 9.8 that OpenSSL rates Low
+ Claude: two black-hole results</code></pre><p>An eighty-one billion dollar IPO sounds like the end of money worries. Anthropic's stock opened on Thursday near $111, closed at $97.17, and the final prospectus says the company has changed rate limits before. We read the filing as people who build on Claude.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>What day one showed.</strong> The IPO priced on Wednesday at $83.00, with 980 million shares sold. The first trade on Thursday was $111.50, the day's high was $115.10, the low was $92.72 and the close was $97.17, 17 percent above the offer price. The lowest price of the session was still nearly $10 above the offer (Yahoo Finance, Nasdaq, CNBC, Forbes and Reuters agree on these numbers). We told you about the pricing in <a href="https://www.youtube.com/watch?v=QntaDwtU63A">yesterday's episode</a>. Valuation figures depend on the share count: CNBC says about $1.8 trillion at the close, Forbes says $1.27 trillion, and Reuters says the bigger figures count stock options and restricted stock that have not vested. Bessemer's Byron Deeter told CNBC that Anthropic could have priced higher and chose to leave money on the table.</p><p><strong>Who was allowed to sell.</strong> The prospectus locks up most existing holders for six months to a year. Non-founder directors, officers and current and former employees and consultants may sell up to 315 million Class A shares from the first trading day, about a third of the 980 million shares the IPO sold. The filing says they may. It does not say anyone did.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>What the filing says about rate limits.</strong> In its risk factors Anthropic writes: "We have also changed, and may in the future change, usage limits, rate limits, or model and product capabilities." It adds that some of those changes have resulted in claims that its disclosures about model access were inadequate or misleading, and that it may keep older models running longer than planned, which uses compute.</p><p><strong>The bill, and the contract that can be cancelled.</strong> Anthropic says it has committed about $900.9 billion to compute and infrastructure, about $70.7 billion of it due within twelve months, against $33.2 billion of revenue in the first nine months of 2026. One of those contracts is a $34.9 billion agreement signed in August with Lambda for GPU capacity. Lambda had to secure a facility lease by a set date and did not, so the filing says the agreement "is currently terminable by either party". Neither party has given notice and Anthropic says it does not currently intend to terminate. That is about four percent of the total. A Futurum analyst told CNBC that late capacity turns into lost revenue quickly, and also that a serious shortage is unlikely.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>Also today: Claude and two black-hole problems.</strong> Anthropic published two physics results this week and says Claude solved both. A researcher asked for open problems, got 22 candidates and let agents work in the background for about six weeks. One result completes a calculation set up in 2003 and finds that a black-hole-like transition in a model theory is abrupt. The other pins down a limit for a toy version of quantum gravity at about 9.1, where earlier proofs stopped at 8.5. Anthropic says neither describes our universe. It also says almost every piece was computed twice by independent agents, the results were verified in the Lean proof checker, and a physicist checked every main result. The preprints sit on Hexagon, which does no peer review and labels them primarily AI-generated text. We found no independent review yet.</p><p><strong>Also today: a 9.8 that OpenSSL rates Low.</strong> CVE-2026-121481 is an integer overflow in OpenSSL's base64 encoder for inputs of about two gigabytes. The 9.8 comes from CISA's enrichment. OpenSSL's own record rates it Low and says no path by which an attacker can trigger it has been identified. A reviewer on the fix wrote that the reproducer is "completely synthetic" and probably should not be a CVE without evidence it happens; on Friday an OpenSSL team member objected to using an assertion in the library. The pull request is open and the fixed releases, 4.0.4 and 4.1.1, do not exist yet. If your code calls that function, bound the length yourself; CISA's own tag says no exploitation.</p><p><strong>Verdict: NEEDS REVIEW.</strong> The market paid up, but the filing says the capacity is still being built and limits can move, so I'd keep a second model wired in. I stamped the S-1 the same way in <a href="https://www.youtube.com/watch?v=xt3bdHwvHbY">October</a>.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><p><strong>Sources</strong></p><ul><li><p>https://www.anthropic.com/news/anthropic-prices-initial-public-offering</p></li><li><p>https://www.sec.gov/Archives/edgar/data/2130357/000162828026074944/anthropicpbc-424b4.htm</p></li><li><p>https://www.cnbc.com/2026/11/20/anthropic-defies-odds-holding-ipo-despite-massively-disruptive-market.html</p></li><li><p>https://www.cnbc.com/2026/11/20/tech-download-anthropic-compute-access.html</p></li><li><p>https://www.forbes.com/sites/fionariley/2026/11/19/anthropic-ipo-live-stock-closes-day-at-97-up-more-than-17/</p></li><li><p>https://www.reuters.com/business/finance/anthropics-historic-debut-put-ais-promise-peril-wall-st-test-2026-11-19/</p></li><li><p>https://www.anthropic.com/research/claude-black-hole-physics</p></li><li><p>https://hexagonmath.org/2611.00175v1</p></li><li><p>https://hexagonmath.org/2611.00174v1</p></li><li><p>https://www.cve.org/CVERecord?id=CVE-2026-121481</p></li><li><p>https://nvd.nist.gov/vuln/detail/CVE-2026-121481</p></li><li><p>https://github.com/openssl/openssl/pull/33652</p></li><li><p>https://news.ycombinator.com/item?id=50562754</p></li><li><p>https://news.ycombinator.com/item?id=50563148</p></li><li><p>https://news.ycombinator.com/item?id=50569226</p></li></ul><div><hr></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://www.youtube.com/@dailydiffdev">YouTube</a> &#183; <a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">thedailydiff.dev</a> &#183; forward this to whoever picked a single model provider.</p><p>Credits: Portrait of Dario Amodei at TechCrunch Disrupt 2023, by TechCrunch, CC BY 2.0 (<a href="https://creativecommons.org/licenses/by/2.0/">licence</a>, <a href="https://commons.wikimedia.org/wiki/File:Dario_Amodei_at_TechCrunch_Disrupt_2023_02_(cropped).jpg">Commons file</a>); background removed, cropped and resized; identifies Anthropic only, no endorsement, quote or reaction. Visual credits: Anthropic research post recording; Austin Powers (New Line/Warner Bros.) clip via GIPHY, owners retain their rights; imgflip "Two Buttons" template.</p>]]></content:encoded></item><item><title><![CDATA[Two NGINX HTTP/2 bugs can run code, no password]]></title><description><![CDATA[The Daily Diff &#183; Thursday, November 19, 2026]]></description><link>https://newsletter.thedailydiff.dev/p/two-nginx-http2-bugs-can-run-code</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/two-nginx-http2-bugs-can-run-code</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Thu, 19 Nov 2026 14:45:41 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/9f2508f9-ac19-41d5-8a39-7ba132e64fa9_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-QntaDwtU63A" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;QntaDwtU63A&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/QntaDwtU63A?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-19-nginx-http2-rce/">Watch the video, transcript and sources</a></p><pre><code>+ NGINX: two HTTP/2 RCE bugs, fixed
+ Gemini 4 Neon: Google's cyber pitch
+ Anthropic prices its IPO at $83</code></pre><p>Serving plain files sounds like the safest job on your network. Wiz Research says it ran code on exactly that kind of NGINX server, with no password. The bugs are CVE-2026-123007 and CVE-2026-123633, both in NGINX's HTTP/2 code. F5 scores both 9.2 out of 10, and the fixes shipped on Wednesday in NGINX 1.30.7 (stable) and 1.31.9 (mainline).</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>Who found it.</strong> Wiz says five teams landed on these bugs independently: Wiz, Rapid7, Xint, Ikotas Labs and Metnir. Wiz says its own AI harness found both. Rapid7 credits a named human researcher for the counter bug, and Xint says a researcher found that one and an automated scan found four more. The nginx.org changelog credits Xint.io and a researcher named Albert of Vexera AI. We attribute every one of those statements to the team that made it.</p><p><strong>The refund bug.</strong> HTTP/2 lets many requests share one connection, and the client hands the server credit for how much it may send. NGINX subtracts credit when it queues a response. If the client cancels first, NGINX gives the unsent credit back and never checks it against the maximum. If the client raised the allowance while that data waited, the refund pushes the counter past the legal maximum. The next safety check subtracts the counter from the maximum in unsigned math, which cannot go negative, so the answer wraps into an enormous number and the check waves everything through. The huge counter later becomes a negative length and a copy runs outside its buffer. Wiz says that also leaks addresses first, which is how it got past ASLR on official builds. The maintainers' own commit message describes the refund part and names Xint as the reporter. That commit carries a commit date of November 11, a week before the advisory.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>How much it takes.</strong> Rapid7 says its exploit needs about 128 GB of HTTP/2 traffic over one connection. NGINX closes connections after an hour by default, so a link slower than about 300 Mbit/s cannot finish, and Rapid7 says a proxy in front will likely not pass the frames along intact. That is one team's exploit, and Rapid7 says other routes may exist. Wiz did not release its exploits; Xint published demo videos and an analysis that leaves out the final steps. We could not find any statement that these bugs are exploited in the wild, and CISA's Known Exploited Vulnerabilities list did not include them when we checked on November 19.</p><p><strong>What to change tonight.</strong> Check the package version your distribution reports as well as what <code>nginx -v</code> prints: Ubuntu 24.04, for example, ships 1.24.0 and has a fixed package, 1.24.0-2ubuntu7.20. Upgrade and restart, because a reload does not replace the running binary. If you cannot upgrade, set <code>http2 off;</code> in the affected server blocks and remove <code>http2</code> from any <code>listen</code> directive. That closes these two bugs. Xint reported three more (HTTP/3, the resolver and the mail proxy) that <code>http2 off</code> does not touch, so the patch is still the plan.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>Also today: Gemini 4 Neon.</strong> Google says Neon ranks third on the Artificial Analysis Intelligence Index with a score of 61, at $3 in and $15 out per million tokens, and that the cyber version scores 90.5% on a vulnerability-finding benchmark at roughly half the cost per challenge. Trusted defenders get it first. Artificial Analysis agrees on the 61, then calls the model somewhat expensive, notably slow per task and very verbose: about 21.5 minutes and $6.44 per task. Vals ranks Neon second at 70.87%, behind Claude Fable 5.2 at 71.31%. Wiz says it used Gemini 4 Carbon to check its NGINX bugs.</p><p><strong>Also today: Anthropic's IPO.</strong> Anthropic priced at $83.00 a share, above the $70 to $78 range it filed on November 10, and sold 980 million shares, up from 825 million planned. That is $81.34 billion, which CNBC calls the largest offering on record; Anthropic itself gets $78.84 billion before expenses and selling stockholders about $1.95 billion. The shares start trading on Thursday as ANT, and CNBC puts the fully diluted value near $1.5 trillion. The final prospectus lists nine-month revenue of $33.2 billion against $2.5 billion a year earlier, an operating loss of $1.26 billion, and a net loss of $104.0 billion, of which $94.3 billion is a change in the fair value of its own convertible notes and similar instruments. We read you the S-1 in <a href="https://www.youtube.com/watch?v=xt3bdHwvHbY">the October 26 episode</a>.</p><p><strong>Verdict: SHIP IT.</strong> Ship the patch tonight: the fix is small, the stopgap is one line, and the one exploit with published limits needs a lot of traffic and a direct path. Put the package version in the ticket. Wiz lines this up with PHP2Shell last month and with Java4Shell, which we covered <a href="https://www.youtube.com/watch?v=_sMSs19nEWA">on Wednesday</a>; Ruby also patched seven bugs on November 18.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><p><strong>Sources</strong></p><ul><li><p>https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities</p></li><li><p>https://nginx.org/en/security_advisories.html</p></li><li><p>https://nginx.org/en/CHANGES</p></li><li><p>https://nvd.nist.gov/vuln/detail/CVE-2026-123007</p></li><li><p>https://github.com/nginx/nginx/commit/b89c4100bf6762a45e4a6463eaf4b70368277c94</p></li><li><p>https://xint.io/blog/nginx2root-remote-code-execution</p></li><li><p>https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/</p></li><li><p>https://cyberscoop.com/nginx-critical-vulnerabilities-exploits/</p></li><li><p>https://ubuntu.com/security/CVE-2026-123007</p></li><li><p>https://news.ycombinator.com/item?id=50547374</p></li><li><p>https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-neon/</p></li><li><p>https://artificialanalysis.ai/models/gemini-4-neon</p></li><li><p>https://www.vals.ai/benchmarks</p></li><li><p>https://www.anthropic.com/news/anthropic-prices-initial-public-offering</p></li><li><p>https://www.sec.gov/Archives/edgar/data/2130357/000162828026074944/anthropicpbc-424b4.htm</p></li><li><p>https://www.cnbc.com/2026/11/18/anthropic-ipo-ai-offering-price.html</p></li><li><p>https://www.ruby-lang.org/en/news/</p></li></ul><div><hr></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://www.youtube.com/@dailydiffdev">YouTube</a> &#183; <a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">thedailydiff.dev</a> &#183; forward this to the intern who patched on a Friday.</p><p>Credits: no portrait on the cover (artifact-only artwork). Visual credits: Wiz Research page recording; NGINX mark via Simple Icons; DuckTales (Disney) and The IT Crowd (Channel 4) clips via GIPHY; imgflip "Panik Kalm Panik" template. Film and show owners retain their rights.</p>]]></content:encoded></item><item><title><![CDATA[A 65-character string can overflow OpenJDK's Base64 decoder]]></title><description><![CDATA[The Daily Diff &#183; Wednesday, November 18, 2026]]></description><link>https://newsletter.thedailydiff.dev/p/a-65-character-string-can-overflow</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/a-65-character-string-can-overflow</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Wed, 18 Nov 2026 17:03:08 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/923f935d-490c-4ac4-b30c-99cb16c4378b_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-_sMSs19nEWA" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;_sMSs19nEWA&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/_sMSs19nEWA?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-18-java4shell-base64/">Watch the video, transcript and sources</a></p><p>Java is the memory-safe language, which makes this week's story awkward. Calif, a security research group, says 64 letter A's followed by an equals sign make OpenJDK write 62 bytes past the end of an array. The bug is CVE-2026-114938, nicknamed Java4Shell, and OpenJDK and Oracle published fixes on Tuesday.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>Why a memory-safe language can do that.</strong> Java checks memory accesses, but the runtime under it is C, C++ and hand-written assembly. When a program decodes Base64 often enough, the JIT compiler swaps in an AVX-512 assembly routine. For the 65-character input, Java reserves a 50-byte result array. The routine finishes the padded tail with one 64-byte store and a mask. Calif's pseudocode shows the length reaching zero, the padding subtracting one more, and the mask reading minus one as "every bit on". The store starts near the end of the array, and 62 of its bytes land on whatever object sits next door.</p><p><strong>The error comes too late.</strong> Java then rejects the input with an <code>IllegalArgumentException</code>. The exception is correct, and the write already happened.</p><p><strong>What Calif says it did with that.</strong> The spill is mostly a fixed pattern, so Calif aims it at the length field of a neighboring array, lets that array accept chosen bytes, and corrupts a second array that gets copied into the response, which leaks heap memory. Calif says it reached code execution in eleven products: Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate without a login, and Kafka, Solr, Elasticsearch, Gerrit and Spinnaker after one. Those are Calif's own tests in default setups, the recipes are withheld until people patch, and Calif itself says there is no universal exploit: every product needs its own recipe and the timing is sensitive to network jitter. Calif's account of the AI effort is one hour to find the bug, two more to build the first exploit, under $200 in tokens. We have not verified any of it.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>What is confirmed.</strong> OpenJDK and Oracle list the bug at CVSS 3.1 8.1; Calif scores it 9.2 on CVSS 4.0. The public November security branch of OpenJDK contains a four line change titled "Base64 optimization improvements". CISA urged immediate patching on November 17, and when we checked on November 18 the CVE was not on its Known Exploited Vulnerabilities list. The security firm Hadrian says it crashed login checks on two lab servers and reached code execution in a lab service. Red Hat, Amazon and Adoptium confirm the scope below.</p><p><strong>Which of your servers can run the broken code.</strong> Four things have to line up. First, an x86-64 chip with AVX-512 VBMI: Intel from Ice Lake on or AMD from Zen 4 on. ARM machines are not affected. Second, Java 17 or newer from OpenJDK builds (Oracle also lists its Java 8 performance build; standard Java 8 and 11 are not on this CVE). Third, a decoder the compiler has warmed up. Fourth, input an attacker can reach. Calif's check on Linux:</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><pre><code>grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'</code></pre><p>All four flags must appear for a machine to be in scope.</p><p><strong>What to change today.</strong> Update to a fixed build: Oracle JDK 17.0.21.1 shipped on November 17, Amazon Corretto has fixed builds, Temurin builds are rolling out as testing finishes, and Red Hat is expediting. Until you can, start Java with <code>-XX:-UseBASE64Intrinsics</code>, which works on every chip. The other flag, <code>-XX:UseAVX=2</code>, is x86 only and stops ARM JVMs from starting. Rebuild container images, because the Java inside an old image stays old.</p><p><strong>Verdict: SHIP IT.</strong> Ship the patch because it is small, public and already built by the main vendors, and the one flag works everywhere. Calif's code execution claims stay Calif's until someone else shows them, so update without panic. Calif is the same team behind PHP2Shell, which we covered on <a href="https://www.youtube.com/watch?v=aZ1X2EQgqsY">October 22</a>.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Credits: portrait on the cover is James Gosling, Java's creator, photo by Peter Campbell, CC BY-SA 4.0 via Wikimedia Commons, cropped and adapted by The Daily Diff; he did not author, approve or react to this research.</p><div><hr></div><p><strong>Sources</strong></p><ul><li><p>https://calif.io/java4shell</p></li><li><p>https://openjdk.org/groups/vulnerability/advisories/2026-11-17</p></li><li><p>https://www.oracle.com/security-alerts/cspunov2026.html</p></li><li><p>https://www.oracle.com/java/technologies/javase/17-0-21-1-relnotes.html</p></li><li><p>https://github.com/openjdk/jdk/pull/33936</p></li><li><p>https://github.com/openjdk/jdk/commit/5177a70b385c16f26ede191fdac7aaba0bed0f8b</p></li><li><p>https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching</p></li><li><p>https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json</p></li><li><p>https://access.redhat.com/security/vulnerabilities/RHSB-2026-018</p></li><li><p>https://adoptium.net/news/2026/11/temurin-november-2026-cspu-java4shell</p></li><li><p>https://github.com/corretto/corretto-25/blob/25.0.5.1.2/CHANGELOG.md</p></li><li><p>https://explore.alas.aws.amazon.com/CVE-2026-114938.html</p></li><li><p>https://hadrian.io/vulnerability-alerts/oracle-critical-security-patch-update-java-17-rce-claims</p></li><li><p>https://news.ycombinator.com/item?id=50538240</p></li></ul><div><hr></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://www.youtube.com/@dailydiffdev">YouTube</a> &#183; <a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">thedailydiff.dev</a> &#183; forward this to the intern who deployed on Friday.</p>]]></content:encoded></item><item><title><![CDATA[Windows 11 can log which coding agents you run]]></title><description><![CDATA[Tuesday, November 17, 2026 &#183; The Daily Diff &#183; Niko from Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/windows-11-can-log-which-coding-agents</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/windows-11-can-log-which-coding-agents</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Tue, 17 Nov 2026 16:09:17 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/0dd0c8a2-dfd2-4177-ba52-c957b98ed754_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-kcoco35F8pQ" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;kcoco35F8pQ&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/kcoco35F8pQ?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-17-windows-agent-telemetry/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=kcoco35F8pQ</p><pre><code>+ One Windows build keeps a daily yes-or-no flag per coding agent
- Microsoft has not explained it, and we ran nothing ourselves</code></pre><p>A researcher named Xusheng Li, who works on Binary Ninja, says a Windows 11 component keeps one bit for each coding agent it sees: Copilot, Claude, Codex and agy on the command line, plus GitHub, Claude, Codex, Cursor and Antigravity on the desktop. He found it by asking an AI to search new Windows files for undocumented features. Everything below about how it behaves is his report on one ARM64 virtual machine, plus Microsoft's own documentation. We did not run it on a Windows machine.</p><h2>What it keeps</h2><p>The names sit in a system file called <code>MissionControlAggregator.dll</code>, where Li found exact comparisons with executable names. The component does not scan your disk. It reads events Windows already produces, such as app state summaries and Linux launches under WSL. Those events carry run time and focus time. Li says the component appears to discard them and keep only a bitmap: one position per slot. Codex sits at position two, so a Codex sighting makes the row read four. About once a day the component emits a small report. Li found no prompt text and no source code in it.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>That is a smaller record than Windows is allowed to collect. It is still a record of which tools a person uses to do their job.</p><h2>Does it leave the PC?</h2><p>Li forced a report by moving the saved reporting window back twenty-five hours and restarting the diagnostics service. A stand-in program set one bit. He then found the event in the diagnostics upload queue, with <code>"privacy": { "isRequired": false }</code>. That flag marks it as optional diagnostic data.</p><p>On his clean Windows 11 Home install in the United States, the diagnostic data toggle already read <strong>Include Optional</strong>. His reading is that the report is queued for upload unless you change it. He saw it queued. He did not capture it leaving the machine, so the supported claim is that the report was queued.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Microsoft's own page lists app activity, such as which programs are launched on a device, under optional data. It also says it uses app activity to prioritize compatibility testing and feature work for the apps people use most. A census of coding agents would fit that sentence. The documentation does not say that is the purpose here.</p><h2>What the optional switch does not obviously cover</h2><p>Microsoft's required events list for Windows 11 versions 25H2 and 24H2 names a second event from the same component: <code>Microsoft.Windows.MissionControlAggregator.Segments.Cohorts</code>. It classifies users by app usage, and the only cohort reported is called <code>IsDeveloper</code>. Required data is the floor on Home and Pro; the "off" setting exists only on Server, Enterprise and Education.</p><p>Nobody has shown that this flag fires on a given PC, and nothing documents what feeds it. We do not claim it uses the agent bits.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>What nobody knows yet</h2><p>How many machines run this. Li's first version of the post said a baseline virtual machine from the public ISO had the feature disabled by image default. That sentence is not in the current version, and we found no explanation. Microsoft's page says some optional data is collected from only a small percentage of devices, and Li's build called the feature a service experiment. We found no Microsoft statement on Tuesday.</p><h2>How Windows decides a program is Codex</h2><p>This is the part that answers the question we opened with. Li copied the Windows command prompt, renamed the copy <code>codex.exe</code>, and ran it. The Codex bit flipped. A copy renamed <code>gcc.exe</code> set the compiler bit. The check looks at a file name, and a file name can go on anything. A real agent under another name would likely go uncounted, though Li did not test that.</p><h2>What to do</h2><p>If you run agents on Windows, open Settings, then Privacy &amp; security, then Diagnostics &amp; feedback, and look at optional diagnostic data. On a work PC an admin may control it through policy. The Windows setting covers Windows; Claude Code, Codex and Cursor have their own telemetry controls.</p><p><strong>Verdict: NEEDS REVIEW</strong> &#8212; one build, one researcher, and no Microsoft explanation of what each bit is for.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><p><strong>Sources</strong></p><ul><li><p>Xusheng Li, "Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use" (CC BY-NC 4.0): https://xusheng.dev/posts/windows-coding-agent-telemetry/</p></li><li><p>The same post as first published, Internet Archive capture of Nov 16, 23:00 UTC: https://web.archive.org/web/20261116230024/https://xusheng.dev/posts/windows-coding-agent-telemetry/</p></li><li><p>Li's X thread: https://x.com/CrackmesOne/status/2122147747390468384</p></li><li><p>Hacker News discussion: https://news.ycombinator.com/item?id=50524736</p></li><li><p>Microsoft Support, Diagnostics, feedback, and privacy in Windows: https://support.microsoft.com/en-us/windows/privacy/diagnostics-feedback-and-privacy-in-windows</p></li><li><p>Microsoft Learn, Configure Windows diagnostic data in your organization: https://learn.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization</p></li><li><p>Microsoft Learn, Required diagnostic events and fields for Windows 11, versions 25H2 and 24H2: https://learn.microsoft.com/en-us/windows/privacy/required-diagnostic-events-fields-windows-11-24h2</p></li></ul><p>Visual credits: thumbnail portrait of Satya Nadella by Brian Smale and Microsoft, 2017, CC BY-SA 4.0 via Wikimedia Commons, cropped and adapted by The Daily Diff; he did not author, approve or react to this report. Source recordings and excerpts: Xusheng Li, xusheng.dev, CC BY-NC 4.0, excerpt.</p><div><hr></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://www.youtube.com/@dailydiffdev">YouTube</a> &#183; <a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">thedailydiff.dev</a></p>]]></content:encoded></item><item><title><![CDATA[uBlock Origin fixed a one-click trust failure]]></title><description><![CDATA[Monday, November 16, 2026 &#183; The Daily Diff &#183; Niko from Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/ublock-origin-fixed-a-one-click-trust</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/ublock-origin-fixed-a-one-click-trust</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Mon, 16 Nov 2026 17:15:38 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/73035cf9-0afc-4738-9610-b0239901b877_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2--XvzF3ltaGE" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;-XvzF3ltaGE&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/-XvzF3ltaGE?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-16-ublock-picker-trust/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=-XvzF3ltaGE</p><pre><code>- A website could drive an extension-owned picker
+ The patched picker verifies authorization at launch</code></pre><p>uBlock Origin's element picker is meant to help you remove an annoying page element. A disclosed flaw let a hostile website use that convenient interface to save trusted filters. Those filters could affect a different site. The vulnerability is fixed, and the useful first step is checking the extension version actually installed in your browser.</p><p>The maintainer advisory lists <strong>1.75.2 and lower as affected</strong> and <strong>1.75.4 as patched</strong>. GitHub and Mozilla currently list <strong>1.76.4</strong> as the stable release. Use normal browser extension controls to update to the current stable version. The availability of an update says nothing about whether a particular installation has received it.</p><h2>The interface carried more authority than it appeared to</h2><p>Smitty van Bodegom published his report on November 15. Raymond Hill's advisory says the issue was reported privately on November 1. The disclosed path concerns Firefox's MV2 extension architecture, a relevant filter that returns an extension resource, and a user click. Keep those prerequisites attached to the headline.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The picker belongs to the extension even though its interface appears over a webpage. It can ask the extension to save filters. Van Bodegom says picker-created rules were treated as trusted, at least until recompilation, and some trusted filters can inject JavaScript into a matching page.</p><p>A filtering feature could supply a harmless replacement for a script the website expected. That resource path also exposed the extension's random internal address. Once a hostile page knew the address, it could load the picker and send it messages. An insufficiently checked input could carry another rule into the trusted store.</p><p>That authority crossed a site boundary: a rule created through one page could target another site and run script in that site's context. Our video illustrates the reported relationship. We have not run the exploit demonstration, changed an extension installation or tested anyone's accounts.</p><h2>A click and an important evidence boundary</h2><p>The reported path still needed a click. Van Bodegom describes hiding or covering the embedded picker so an ordinary page click hits its Create button. He explicitly says he did not implement that hidden-overlay portion. The verified picker-control path and the proposed concealment technique have different evidence behind them.</p><p>Recompilation could clear the rule's trusted status, according to the researcher. He also notes that the attacking page could immediately open the target page. A possible later cleanup leaves time for the earlier consequence. That is a poor place to put the security guarantee.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The report and advisory provide no victim count or evidence of active exploitation. The report mentions a similar, less problematic issue in uBlock Origin Lite separately. Its different version and architecture deserve their own assessment.</p><h2>Why the first fix wasn't enough</h2><p>Hill's November 2 hardening, released in 1.75.2, avoided potentially tainted request methods in the filtering scripts. The email exchange records a bypass that could still expose the internal identifier through another part of the request machinery. Protecting one route to the address left a powerful interface accepting the wrong caller.</p><p>The November 3 repair, released in 1.75.4, launched the picker only with a <strong>verified secret token</strong>. The legitimate extension flow supplies authorization, and the picker checks it. Knowing the interface's address alone should leave an untrusted webpage outside that boundary.</p><p>Later changes validated proposed filters and restricted resource-related filters. Those are additional protections. They do not change the selected advisory's statement that 1.75.4 is patched.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>The human work behind the model-assisted report</h2><p>Van Bodegom says GPT-5.6 Sol found the issue after he supplied a hypothesis about filter injection. He checked and verified the result; Claude wrote much of the demonstration code. Those are the author's statements about his workflow. They supply no independent benchmark of autonomous security research.</p><p>The report sent to the maintainer and the installable repairs are the useful receipts. I would keep the security lesson centered on who can command a privileged interface, rather than letting an AI leaderboard argument take over the story.</p><h2>Verdict: SHIP IT</h2><p>I'd ship the patched picker because it checks authorization at the control boundary, and I'd keep the current stable extension installed. Future security work stays open. A bouncer who checks the invitation can do his job even when everybody knows the venue.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Sources</h2><ul><li><p><a href="https://iter.ca/post/ubo-uxss/">Smitty van Bodegom's November 15 report</a></p></li><li><p><a href="https://github.com/gorhill/uBlock/security/advisories/GHSA-cmqw-9r2w-6wv2">Raymond Hill/gorhill's maintainer advisory and repair chronology</a></p></li><li><p><a href="https://github.com/gorhill/uBlock/releases/tag/1.76.4">Current 1.76.4 release</a></p></li><li><p><a href="https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/">Mozilla's official uBlock Origin listing</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50513160">Hacker News discussion</a></p></li></ul><p>Visual credits: original public-header recording and conceptual illustrations by The Daily Diff. The video quotes a short silent Nedry/Wayne Knight-like caricature from <a href="https://giphy.com/gifs/hacker-dennis-timbenj-wSSooF0fJM97W">this GIPHY page</a>, which links a <a href="https://s297.photobucket.com/user/timbenj/media/Threadbombs/HackerDennis.gif.html">timbenj/Photobucket source</a>. Animation authorship and original film-native footage are unverified. Underlying source/film/character/likeness owners retain copyright; hosting grants no reuse licence or blanket permission. The article's displayed CC BY-SA4 licence applies to that article. Other assets and the episode retain their own rights boundaries.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p>]]></content:encoded></item><item><title><![CDATA[Google's new security clock can delay early disclosures]]></title><description><![CDATA[Sunday, November 15, 2026 &#183; The Daily Diff &#183; Niko from Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/googles-new-security-clock-can-delay</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/googles-new-security-clock-can-delay</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Sun, 15 Nov 2026 18:15:33 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/65f40b94-0d27-42c8-ad12-a2510b53c9ac_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-eHkbrt81r0Q" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;eHkbrt81r0Q&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/eHkbrt81r0Q?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-15-google-disclosure-clock/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=eHkbrt81r0Q</p><pre><code>+ Fixed report-date publication
- Default post-patch soak timer
+ Shorter clocks planned in stages</code></pre><p>Google wants faster fixes. Its first policy change can keep some early-patched bug details private longer.</p><p>Natalie Silvanovich's November 13 announcement replaces Project Zero's ordinary post-patch waiting rule with a fixed disclosure clock. The current policy is Full 90: technical details ordinarily become public ninety days after the team reports the vulnerability to its vendor. An early patch leaves that endpoint in place.</p><h2>Follow the report clock</h2><p>Project Zero is Google's security research team. It sends technical reports to responsible vendors or open-source projects, then publishes their technical details under its disclosure policy. This is the team's publication policy. It concerns those reports and includes defined exceptions.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The historical 2021 rule held details for thirty days after an ordinary bug was fixed within its deadline. That waiting period was intended to let users install patches. The new ordinary clock attaches publication to the original report date. Default grace-period and special variant handling are removed.</p><p>The distinction matters because a released patch, an installed update and a public technical explanation are different milestones. The restart reminder on your laptop has a very good understanding of this distinction.</p><h2>The patch gap remains</h2><p>Google calls the release-to-installation interval the patch gap. Silvanovich argues that AI has made patch analysis fast enough that near-zero patch-to-exploitation is a reasonable, imperfect planning model. The qualifier matters. This is Google's stated reasoning, with no independent exploitation benchmark in this episode.</p><p>The team wants faster rollout or other protections while remediation proceeds. It also describes a workload problem: some targets now produce several vulnerabilities a week, where it previously found a few a year. Negotiating whether each report counts as fixed becomes difficult to automate. The meeting produces another meeting.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>The shorter policies are future plans</h2><p>Google plans Full 60 for February 2, 2027. That would put ordinary publication sixty days after reporting. It plans Full 30 for January 3, 2028. Current Full 90 remains the ordinary policy until the change.</p><p>The official FAQ says reports retain the policy that applied when they were submitted. Vendors raised concerns about exposing unfixed bugs, distorted repair priorities and impossible targets. The transition is intended to give them time to improve their processes.</p><p>Defined exceptions remain for active exploitation against real users, already-public technical details and earlier disclosure requested by the affected vendor. Rare harm-prevention exceptions also remain. Project Zero continues tracking fixes and communicating unfixed status; that status ceases deciding the ordinary disclosure endpoint.</p><h2>The worked example explains the tradeoff</h2><p>The current policy's example patches a bug on day 47 and publishes details on day 90. Applying the historical ordinary fix-plus-30 rule calculates to day 77. That is thirteen days later for technical details under the current example, with the patch available on the same day.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>These are an official policy illustration and our arithmetic. User installation time is unknown. For a deadline-day fix, the old extra month before publication disappears. The new clock can change the wait in either direction depending on fix timing.</p><h2>Verdict: NEEDS REVIEW</h2><p>I'd judge this policy by how quickly users actually get protected, while watching the early-fix disclosure tradeoff. A clearer publication schedule is useful; patch deployment still needs to reach the systems people depend on.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><h2>Sources</h2><ul><li><p><a href="https://projectzero.google/2026/11/disclosure-policy.html">Natalie Silvanovich's 2026 announcement</a></p></li><li><p><a href="https://projectzero.google/vulnerability-disclosure-policy.html">Current policy and worked examples</a></p></li><li><p><a href="https://projectzero.google/2021/04/policy-and-disclosure-2021-edition.html">Tim Willis's official 2021 table</a></p></li><li><p><a href="https://projectzero.google/vulnerability-disclosure-faq.html">Official FAQ and existing-report scope</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50496051">Hacker News discussion; opinions only</a></p></li><li><p><a href="https://dgmagazine.net/dg-news/google-30-day-bug-disclosure-ai-exploitation">Fresh DGMAGAZINE coverage; primary-source synthesis</a></p></li><li><p><a href="https://tldr.tech/story/5375a56a-02b3-4571-9dce-da63b18213f0">TLDR synopsis; no independent benchmark</a></p></li></ul><h2>Visual credits</h2><p>Whole portrait-based ABC/cover artworks adapt World Economic Forum's Pichai portrait, <a href="https://commons.wikimedia.org/wiki/File:Sundar_pichai.png">source</a>, <a href="https://creativecommons.org/licenses/by/3.0/">CC BY 3.0</a>, <a href="https://www.youtube.com/watch?v=7sncuRJtWQI">original linked video</a>. Background removed, resized and placed with new typography. Pichai identifies Google; Natalie authored the policy. No endorsement or current personal reaction is implied.</p><p>The full episode includes an original Daily Diff process drawing and a brief silent fictional calendar reaction from Mr Bean's Holiday featuring Rowan Atkinson, <a href="https://giphy.com/gifs/time-mr-bean-look-at-the-QBd2kLB5qDmysEXre9">GIPHY source</a>. Film/source owners retain copyright; public hosting is no licence, legal clearance or blanket reuse grant. Google/source articles retain copyright. The recording shows public policy prose; no operational security test was performed.</p>]]></content:encoded></item><item><title><![CDATA[Google's AI glasses leave bystanders with a consent problem]]></title><description><![CDATA[Saturday, November 14, 2026 &#183; The Daily Diff &#183; Niko from Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/googles-ai-glasses-leave-bystanders</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/googles-ai-glasses-leave-bystanders</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Sat, 14 Nov 2026 22:30:48 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/cbb599f1-6029-43dc-b4dc-5e3c0f84742f_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-uPvxZ8n7WiM" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;uPvxZ8n7WiM&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/uPvxZ8n7WiM?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-14-google-glasses-consent/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=uPvxZ8n7WiM</p><pre><code>+ Gemini camera visuals have scoped safeguards
- Bystanders inherit the response burden</code></pre><p>Google's new intelligent eyewear puts camera and microphone assistance in everyday frames. Warby Parker and Gentle Monster make the designs, with Samsung collaborating. Preorders opened on November 12; purchases start December 10. The useful privacy question is who gets to decide what happens when another person enters the frame.</p><p>Google describes protections worth keeping. For a Gemini inquiry, the glasses are designed to redact bystanders' faces before Gemini processes the visuals. Google says those camera visuals stay out of Gemini History and are unused for AI training or ad targeting. This is a visual-specific promise, with a named history surface. The episode includes no independent redaction test.</p><h2>Follow the operation</h2><p>Saving a gallery photo or video takes a different path. An outward-facing light indicates capture. Google says sensors are designed to detect a covered or tampered indicator and prevent photos or videos. CNN explicitly distinguishes ordinary saved media from the Gemini face-redaction assurance.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Text chats follow their own rules. Google says chats are saved in Gemini History, with controls to review or delete them and choose whether the text helps improve generative AI models. A spoken Gemini interaction can therefore produce a saved text chat. Carrying the visual-data promise over every data category would obscure the distinctions in Google's own documentation.</p><p>Apps ask the wearer for camera access. The wearer can revoke that access or use the physical off switch. The person across the table gets no described counterpart settings panel. Your privacy administrator can be somebody you met at lunch.</p><h2>Useful assistance, scoped restrictions</h2><p>Guided Vision offers conversational audio descriptions for blind people and people with low vision. Google also describes an Aira integration that streams the camera feed to a trained human visual interpreter. That has a different recipient from a Gemini inquiry; the Gemini-specific promise should keep its name attached.</p><p>Google Play policies restrict social livestreaming, real-time facial identification and indicator changes. Wearers must agree to obtain permission before recording other people, avoid sensitive places and leave the indicator uncovered. Google says violations may disable their ability to use the glasses. Those are contractual and platform safeguards; the episode supplies no universal statutory recording rule.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Google also describes encrypted storage and transmission to a phone or the cloud. Private AI Compute is coming soon to glasses. Its future tense matters.</p><h2>The warning leaves a next step</h2><p>EFF's November 13 article argues that wearables push a technical and social burden onto nearby people. Thorin Klosowski asks how a stranger is meant to recognize different hardware and understand its signals. This is advocacy and analysis, alongside Google's design claims.</p><p>CNN reports that Google has researched nearby-phone alerts and location-based privacy measures. Juston Payne supplied no release timing. He described an alert leaving someone asking, &#8220;What am I meant to do now?&#8221; Calli Schroeder at the Electronic Privacy Information Center adds the concrete problem: a person may feel unsafe confronting a stranger, and a worker may avoid confronting a boss.</p><p>A warning can deliver awareness while leaving the bystander to handle the conversation. Developers can review that gap by separating the operation, the recipient, the person authorizing access and the affected person's practical controls.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Verdict: NEEDS REVIEW</h2><p>I'd keep Google's scoped safeguards and ask for a practical bystander response before treating the consent problem as solved. I want the accessibility tools to work, and I want the person in front of them included in the design.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><h2>Sources</h2><ul><li><p><a href="https://blog.google/innovation-and-ai/technology/safety-security/intelligent-eyewear-privacy-protections/">Google's privacy announcement</a></p></li><li><p><a href="https://blog.google/innovation-and-ai/technology/xr-ar/google-intelligent-eyewear-collections-pre-order/">Google's eyewear collections and availability</a></p></li><li><p><a href="https://www.cnn.com/2026/11/12/tech/google-glasses-privacy-concerns">Lisa Eadicicco's CNN interviews and camera-path distinction</a></p></li><li><p><a href="https://www.eff.org/deeplinks/2026/11/tech-companies-are-trying-shift-entire-concept-privacy-again">Thorin Klosowski's EFF analysis</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50496602">Hacker News discussion</a></p></li></ul><h2>Visual credits and use boundaries</h2><p>The complete A/B/C and companion cover artworks are adapted from the <a href="https://commons.wikimedia.org/wiki/File:Sundar_pichai.png">Sundar Pichai portrait</a>, World Economic Forum, <a href="https://creativecommons.org/licenses/by/3.0/">CC BY 3.0</a>, with background removal, resize and placement. <a href="https://www.youtube.com/watch?v=7sncuRJtWQI">Original linked WEF video</a>. Pichai identifies Google as vendor; no current reaction, endorsement or announcement-authorship is implied.</p><p>The video contains original Daily Diff stickfigure process satire and a maximum two-second silent <a href="https://giphy.com/gifs/awkward-pulp-fiction-john-travolta-6uGhT1O4sxpi8">Travolta/Pulp Fiction GIF</a>, with the native <a href="https://www.gifbay.com/gif/im_the_first_one_to_show_up_at_a_party-12725/">Gifbay source link</a>. Google/article and film/source owners retain their respective copyrights. This limited fictional process commentary supplies no blanket reuse grant or legal clearance. The portrait licence does not extend to unrelated source or film material. These reaction assets are not reproduced in this written edition.</p><p>Visual credits: Complete portrait-based artwork adapted from Sundar Pichai / World Economic Forum: https://commons.wikimedia.org/wiki/File:Sundar_pichai.png ; CC BY3.0 https://creativecommons.org/licenses/by/3.0/ ; original https://www.youtube.com/watch?v=7sncuRJtWQI . Background removed, resized and placed. Vendor identity only; no current reaction, endorsement or announcement-authorship. Original stickfigure meme: The Daily Diff. Silent maximum2s fictional process GIF: https://giphy.com/gifs/awkward-pulp-fiction-john-travolta-6uGhT1O4sxpi8 ; native source https://www.gifbay.com/gif/im_the_first_one_to_show_up_at_a_party-12725/ . Google/article and Pulp Fiction/source owners retain copyright. This use grants no blanket reuse licence or clearance. Portrait licence applies separately to portrait-based artwork.</p>]]></content:encoded></item><item><title><![CDATA[Microsoft's Outlook recovery kept failing under traffic]]></title><description><![CDATA[Watch the video, transcript and sources]]></description><link>https://newsletter.thedailydiff.dev/p/microsofts-outlook-recovery-kept</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/microsofts-outlook-recovery-kept</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Fri, 13 Nov 2026 16:31:13 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/a1158d49-69cb-4dc4-8473-679d5dc1165a_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-R5v9I-_1uFE" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;R5v9I-_1uFE&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/R5v9I-_1uFE?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-13-microsoft-recovery-loop/">Watch the video, transcript and sources</a></p><p><em>Friday, November 13, 2026 &#183; The Daily Diff &#183; Reporting cutoff: Microsoft's 11:04:50 UTC update</em></p><p>https://www.youtube.com/watch?v=R5v9I-_1uFE</p><pre><code>- Returned mail servers could fail again when traffic returned
+ Most core Teams functionality and direct SharePoint files remained functional
+ A longer mail timeout aimed to preserve delayed messages</code></pre><p>Microsoft returned mail servers to service. Its own updates then described them becoming unresponsive again when traffic arrived. For developers, the useful follow-up is understanding which operations depended on the impaired service and what a temporary return actually proved.</p><p>Start with the dependency behind the operation. Exchange Online is Microsoft's hosted email service. Microsoft's expanded service-health notice said most core Teams calls, meetings and chats remained functional. Calendar and scheduling scenarios depended on Exchange and could fail. Direct SharePoint file access remained functional, while some sharing and Exchange-dependent features were affected.</p><p>That explains how a meeting can proceed while the calendar refuses to cooperate. The product logo is a poor map of the backend needed for your next click.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Capacity disappeared</h2><p>Microsoft initially investigated Exchange mailbox access in the Americas on Thursday, then confirmed that users in any region could be affected. CNN independently reported disruption across banks, governments and courts. Its reports of affected countries came from Downdetector reports; the episode makes no claim that entire countries or every Microsoft service stopped working.</p><p>The official account attributed elevated load to unexpectedly unavailable servers straining the remaining infrastructure. Ordinary demand can overwhelm a smaller available pool. The company investigated automated health checks and a component responsible for processing server health. That explanation remained an investigation hypothesis at the reporting cutoff.</p><p>Microsoft paused deployments, redistributed traffic and restarted affected servers. An alternative health-check method brought a subset back. Automated systems were being prepared to detect and restart unresponsive machines. These updates described recovery attempts, with results still being tested.</p><h2>Traffic came back too</h2><p>The most useful primary admission was specific: returned servers could become unresponsive again once they received traffic. Microsoft also described isolating infrastructure, restarting components and reintroducing traffic to confirm stability before applying changes more broadly.</p><p>The episode follows the same conceptual server through unavailable, returned, taking work and unresponsive states. That illustration communicates the reported sequence. Microsoft's final report still needed to establish the initial trigger and the conditions behind the relapse.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Microsoft limited certain traffic reaching affected infrastructure in some locations and rebuilt a subset of servers using a previous configuration to test stability. A deployment pause during recovery does not establish that a Friday deployment caused the original incident. The public notice also said Microsoft had no evidence of malicious activity and would publish a full incident report after mitigation.</p><p>By the official Friday update at 11:04:50 UTC, recovery actions had completed across portions of affected infrastructure in Asia Pacific. Traffic was gradually returning, with improvements in mailbox access and delayed email processing. Some users could still experience intermittent issues, and recovery in other regions continued. That is the episode's reporting cutoff. The earlier 10:01 update described variable health and capacity below baseline; it remains part of the recovery history.</p><h2>Check the actual request</h2><p>Microsoft Graph requests for Exchange mail, calendar and contacts could time out. An unrelated successful operation therefore offered little assurance about a mailbox operation's outcome. Review the specific dependency and the result the user needs.</p><p>Microsoft also published incident information outside its admin center because administrators might be unable to load service-health pages there. Keep an out-of-band status link available through an approved incident process. A dashboard depending on the impaired service has become part of the incident.</p><p>For ordinary Graph throttling, Microsoft's documentation recommends honoring Retry-After and using exponential backoff when the response lacks that header. The documentation concerns throttling behavior. It supplies no diagnosis of this particular outage and no guarantee that retries restore an unavailable service.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>What the forty-eight hours meant</h2><p>Microsoft's expanded notice said it prioritized queue and backlog processing and extended the email timeout window to forty-eight hours to preserve delayed messages during recovery. That gives delayed mail more time. The notice supplied no forty-eight-hour repair deadline or guarantee that every message would arrive.</p><p>A delayed notification has not necessarily disappeared. A queued message has not necessarily reached its recipient. For time-sensitive work, verify the actual outcome through an approved independent channel before relying on an optimistic client window.</p><h2>Verdict: NEEDS REVIEW</h2><p>I'd keep recovery under review because Microsoft's updates described returned servers failing under traffic. Sustained service with real work coming through is the useful test. At the reporting cutoff, the initial cause still awaited the final incident report.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><h2>Sources</h2><ul><li><p><a href="https://status.cloud.microsoft/">Expanded service-health incident</a> &#8212; Microsoft; reporting cutoff November13,11:04:50UTC, with earlier10:01:07observations retained historically.</p></li><li><p><a href="https://x.com/MSFT365Status/status/2121031935010951521">Returned servers could become unresponsive under traffic</a>.</p></li><li><p><a href="https://x.com/MSFT365Status/status/2120974801388904932">Health-processing investigation hypothesis</a>.</p></li><li><p><a href="https://x.com/MSFT365Status/status/2120985048337830246">Alternative health checks and a returned subset</a>.</p></li><li><p><a href="https://x.com/MSFT365Status/status/2121002505911857577">Isolation, restart and reintroduction of traffic</a>.</p></li><li><p><a href="https://x.com/MSFT365Status/status/2120962673911181437">Unavailable servers strain remaining infrastructure</a>.</p></li><li><p><a href="https://x.com/MSFT365Status/status/2120938282204688468">Initial Americas investigation</a> and <a href="https://x.com/MSFT365Status/status/2120941584220827979">possible impact in any region</a>.</p></li><li><p><a href="https://x.com/MSFT365Status/status/2120957934607700161">Deployment pause and restart mitigations</a>.</p></li><li><p><a href="https://x.com/MSFT365Status/status/2121172248241348867">Mail timeout extended to preserve delayed messages</a>.</p></li><li><p><a href="https://www.cnn.com/2026/11/12/business/live-news/microsoft-global-outage-intl-hnk">CNN's independent live reporting</a>.</p></li><li><p><a href="https://learn.microsoft.com/en-us/graph/throttling">Microsoft Graph throttling guidance</a>.</p></li><li><p><a href="https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-service-description">Exchange Online service description</a>.</p></li></ul><h2>Visual credits</h2><p>Satya Nadella portrait by OFFICIAL LEWEB PHOTOS (2013), <a href="https://creativecommons.org/licenses/by/2.0/">CC BY2.0</a>, <a href="https://commons.wikimedia.org/wiki/File:Satya_Nadella.jpg">Commons source</a>. Whole portrait-based artwork is adapted through cropping, background removal, resizing and text/composition. Vendor identity only; no endorsement, report authorship or current reaction is implied.</p><p>The <a href="https://imgflip.com/memetemplate/234202281/AJ-Styles--Undertaker">WWE still</a> and <a href="https://giphy.com/gifs/the-simpsons-sideshow-bob-RSOUOj8H9A3Xq">The Simpsons/Bob rake GIF</a> are brief silent process commentary. WWE, The Simpsons/20th Television/Disney, Microsoft and other source owners retain copyright. Hosting and this specific editorial-use decision provide no blanket reuse grant or copyright clearance. The portrait licence is separate from third-party source/cartoon rights.</p><p>Visual credits: Satya Nadella portrait by OFFICIAL LEWEB PHOTOS (2013), CC BY 2.0: https://commons.wikimedia.org/wiki/File:Satya_Nadella.jpg and https://creativecommons.org/licenses/by/2.0/ . Whole portrait-based artwork adapted by cropping, background removal, resizing and text/composition; vendor identity only, no endorsement or current reaction. WWE still: https://imgflip.com/memetemplate/234202281/AJ-Styles--Undertaker . The Simpsons/Bob GIF: https://giphy.com/gifs/the-simpsons-sideshow-bob-RSOUOj8H9A3Xq . Brief silent process commentary; WWE, The Simpsons/20th Television/Disney, Microsoft and other source owners retain copyright. Hosting and this specific editorial-use decision provide no blanket reuse grant or copyright clearance. The portrait licence is separate from third-party source/cartoon rights.</p>]]></content:encoded></item><item><title><![CDATA[Synaptics patent threats stalled a Linux dock driver]]></title><description><![CDATA[The Daily Diff &#183; Thursday, November 12, 2026]]></description><link>https://newsletter.thedailydiff.dev/p/synaptics-patent-threats-stalled</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/synaptics-patent-threats-stalled</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Thu, 12 Nov 2026 20:02:08 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/b7bbed6f-01fd-440b-94f9-a4a229df7270_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-hVe-o_1wHRI" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;hVe-o_1wHRI&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/hVe-o_1wHRI?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-12-displaylink-patent-threat/">Watch the video, transcript and sources</a></p><pre><code>- DisplayLink patent demands stall a driver prototype
+ GitHub Actions lockfile adoption gets a practical guide
+ .NET 11 ships union cases and a two-year support window</code></pre><p>Mike Lothian wanted his Dell USB dock to work better on Linux. According to Joe Brockmeier's new <a href="https://lwn.net/SubscriberLink/1102549/acbc92e00cee3a3f/">LWN report</a>, the existing driver kept crashing. Lothian used Claude to help develop Vino, a Rust driver intended for the Linux kernel, and asked the vendor for help. The subsequent correspondence included patent allegations and escalating monetary demands.</p><p>The report appeared on November 10. The letters describe an older dispute running from June through October. Vino remains an author-reported prototype; we have performed no hardware test. By late August, Lothian reported controlling three generations of docks after earlier versions failed to light a panel.</p><h2>The open part was one component</h2><p>DisplayLink's Linux stack combines proprietary DisplayLink Manager software with the open EVDI module. <a href="https://github.com/DisplayLink/evdi">EVDI's own README</a> says full DisplayLink functionality requires the remaining driver. The proprietary technology encodes display information for transmission and decodes it for the connected devices.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>In the <a href="https://lwn.net/images/pdf/synaptics-correspondence-jul-oct-2026.pdf">July correspondence</a>, Synaptics told Lothian that an independently written or clean-room implementation could still implement patented inventions. That was the company's position. The validity and application of these particular patent claims require legal assessment.</p><h2>The weekly escalation was a demand</h2><p>The <a href="https://lwn.net/images/pdf/Cease_and_Desist_Notice_Mike_Lothian_10-05-2026.pdf">October fifth notice</a> threatened to seek US$25,000 for preparing documentation. It said the amount would increase by <strong>at least another US$25,000 per week</strong> until compliance. The published record establishes no court award or payment. Those conditions matter when describing what happened.</p><p>Lothian had asked which patent claims matched which code. Later, Synaptics reviewed his older EVDI pull request. Brockmeier quotes his response exactly: "You can't threaten to sue me and then say 'can you update your pull request?'" Customer support and legal escalation had discovered parallel processing.</p><h2>OIN coverage had a precise limit</h2><p>The Open Invention Network cross-licenses patents within a defined Linux System. Its <a href="https://openinventionnetwork.com/linux-system/">published definition</a> follows listed components and exclusions. Codecs are excluded unless expressly included in <a href="https://definition.openinventionnetwork.com/table-0/">Table 0</a>. The complete definition contains the governing conditions; membership alone does not settle coverage for a particular contribution.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Brockmeier reports that OIN investigated this case. Chief executive Keith Bergelt said the attempted contributions fell outside protection. Lothian told LWN he removed the public repository and Vino must stay local until the issue is resolved because he cannot afford a defence. He may continue work on unaffected components. The vendor's existing Linux software remains available.</p><h2>Two shorter tooling updates</h2><p><a href="https://hugovk.dev/blog/2026/lock-github-actions/">Hugo van Kemenade's November 11 guide</a> explains GitHub Actions workflow lockfiles and links Python adoption examples. The feature <a href="https://github.blog/changelog/2026-10-28-github-actions-workflow-lockfiles-are-generally-available/">became generally available on October 28</a>. Workflows can keep readable tags while executing recorded commits for normal and transitive action dependencies. Review the chosen revision: locking provides reproducibility, and malicious code can be perfectly reproducible.</p><p><a href="https://devblogs.microsoft.com/dotnet/announcing-dotnet-11/">Microsoft released .NET 11 on November 10</a>. C# 15 union types describe a declared set of cases, with exhaustiveness checking in switch expressions. .NET 11 has two years of Standard Term Support. .NET 10 remains the supported Long Term Support option; Microsoft says quality and servicing policies are the same, with different support lengths.</p><h2>Verdict: REVERT</h2><p>I'd revert the decision to answer a driver contribution with escalating patent demands. It leaves a user trying to improve hardware he owns carrying the legal risk. This verdict concerns the reported pressure and its practical consequences. It supplies no determination of patent validity or infringement.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The video explains the component boundary, the actual demands and the codec exception, then connects them to revision control and support commitments in the two shorter stories.</p><h2>Sources</h2><ul><li><p><a href="https://lwn.net/SubscriberLink/1102549/acbc92e00cee3a3f/">LWN: the reported DisplayLink dispute</a></p></li><li><p><a href="https://lwn.net/images/pdf/Cease_and_Desist_Notice_Mike_Lothian_10-05-2026.pdf">Synaptics: October fifth notice</a></p></li><li><p><a href="https://lwn.net/images/pdf/synaptics-correspondence-jul-oct-2026.pdf">July&#8211;October correspondence compiled by Lothian</a></p></li><li><p><a href="https://github.com/DisplayLink/evdi">Official EVDI README</a></p></li><li><p><a href="https://openinventionnetwork.com/linux-system/">OIN Linux System Definition</a></p></li><li><p><a href="https://definition.openinventionnetwork.com/table-0/">OIN Table 0 codec exceptions</a></p></li><li><p><a href="https://hugovk.dev/blog/2026/lock-github-actions/">Hugo's lockfile guide</a></p></li><li><p><a href="https://github.blog/changelog/2026-10-28-github-actions-workflow-lockfiles-are-generally-available/">GitHub's GA announcement</a></p></li><li><p><a href="https://devblogs.microsoft.com/dotnet/announcing-dotnet-11/">Microsoft's .NET 11 announcement</a></p></li></ul><p>Source excerpts retain their owners' copyright. The video's fictional cartoon reactions are brief process commentary with separate source credits; this release offers no blanket reuse permission.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">The Daily Diff</a></p><p>Visual credits: Synaptics letter/correspondence; Joe Brockmeier/LWN; OIN; DisplayLink; GitHub/Hugo van Kemenade; Microsoft .NET Team. Source text is retained in crops/reflow/highlights; conceptual diagrams and layout are editorial adaptations by The Daily Diff. Letter artwork depicts Synaptics correspondence. Still reaction: SpongeBob SquarePants / Nickelodeon-Paramount cartoon rights, via https://imgflip.com/memetemplate/Imagination-Spongebob and https://i.imgflip.com/3i7p.jpg . Animated reaction: Zootopia &#169; Disney, via https://giphy.com/gifs/disneyzootopia-l2JHVUriDGEtWOx0c . These brief fictional reactions comment on process; no current executive reaction or endorsement is implied. Owners retain copyright. This release grants no blanket asset or episode reuse permission.</p>]]></content:encoded></item><item><title><![CDATA[Nvidia's mining card had more memory than it exposed]]></title><description><![CDATA[The Daily Diff &#183; Wednesday, November 11, 2026 &#183; Niko from Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/nvidias-mining-card-had-more-memory</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/nvidias-mining-card-had-more-memory</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Wed, 11 Nov 2026 19:15:39 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/c338aeb5-ad32-4001-b579-c0a1096f2415_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-dRG6q19Wj1w" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;dRG6q19Wj1w&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/dRG6q19Wj1w?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-11-nvidia-mining-memory/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=dRG6q19Wj1w</p><pre><code>+ Kate reports exposing HBM already installed beside the GPU
- Physical defects still limit usable capacity
+ The FP16 result measures one arithmetic microbenchmark</code></pre><p>An eight-gigabyte GPU sounds like eight gigabytes of hardware. Researcher Kate reports about eighty physically present inside the eight-gigabyte version of Nvidia's CMP 170HX mining accelerator. The post was published on November 10; fresh Hacker News attention arrived on November 11. The hardware itself predates this research.</p><p>The useful first answer is that physical memory, effective configuration and reliably usable capacity are different things. The mining card shares the GA100 GPU family with the A100. HBM sits beside the GPU die in the package. Restrictions can hide hardware already installed, while defects can make parts of that hardware unusable.</p><h2>Check which package the number describes</h2><p>Kate distinguishes the eight-gigabyte variant, with about eighty gigabytes physically installed, from the ten-gigabyte variant, with about forty. Those are different packages. The larger stock product label can therefore come with less physical memory underneath. Shopping by model name has acquired a side quest.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Both product segmentation and manufacturing yield belong in the explanation. Kate separates disabled resources from defective resources. Exposing an intact disabled portion can make it useful. A damaged memory bank stays damaged.</p><p>Nvidia's architecture description independently distinguishes a full GA100 implementation from the configuration sold as an A100. That supports the architectural context. It supplies no independent qualification of Kate's particular modified cards.</p><h2>Permanent marks, changeable interpretation</h2><p>An electronic fuse physically records a setting. A blown fuse stays blown. Kate describes configuration records whose later entries can replace earlier effective values. Think of an original document and a later amendment: the original ink remains, while the instruction that applies changes.</p><p>The research reports a brief electrical disturbance permitting permanent configuration changes. This edition stays conceptual. We performed no hardware modification or card test, and the article's operational procedures are outside the video and companion explanation. Permanent errors can strand the hardware.</p><h2>What the evidence measures</h2><p>The earlier CMPunlocker software approach already exposed sixty-four usable gigabytes on the eight-gigabyte variant, according to Kate's comparison. The hardware result can reach eighty when the memory is intact. The author reports full-memory write/read tests after cache invalidation and functioning inference workloads.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Those are author-reported tests. We haven't independently reproduced the modified-card result. The third-party benchmark program is method context; its name on a chart does not turn the operator's measurement into an independent test.</p><p>Kate's FP16 half2 FMA OpenCL microbenchmark puts the hardware-unlocked example about eighteen percent ahead of a retail A100. This measures a specific repeated arithmetic operation. Model fit, arithmetic throughput and application speed still require separate evidence. The post supplies no controlled tokens-per-second comparison.</p><p>Some feature claims also retain explicit boundaries. Kate says image/video decoding and multi-instance GPU features weren't specifically tested. The interconnect and faster PCI Express connection require additional changes. A shared die does not qualify the entire board as a supported accelerator.</p><h2>The card that gained no extra memory</h2><p>Kate had one card with only sixty-four gigabytes intact. For that card, the hardware unlock produced no framebuffer advantage over the software unlock. The restriction changed; the damaged hardware stayed damaged.</p><p>That counterexample is the useful takeaway. Physically installed capacity and reliably usable capacity can differ dramatically. A seller's capacity screenshot provides a starting point for validation; it cannot establish long-term workload reliability by itself.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Verdict: NEEDS REVIEW</h2><p>I'd want independent workload and reliability testing before depending on a modified mining card as an accelerator. Kate's research makes the hidden hardware understandable. Purchasing a dependable result takes more evidence.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>Which matters more for your workload: usable memory or measured speed?</strong></p><h2>Sources</h2><ul><li><p><a href="https://blog.kate.land/posts/using-voltage-glitching-to-unlock-the-a100/">Kate's primary research and scoped results</a></p></li><li><p><a href="https://developer.nvidia.com/blog/nvidia-ampere-architecture-in-depth/">Nvidia's Ampere architecture description</a></p></li><li><p><a href="https://github.com/ProjectPhysX/OpenCL-Benchmark">ProjectPhysX OpenCL benchmark method</a></p></li><li><p><a href="https://github.com/amoghmunikote/cmpunlocker">Earlier CMPunlocker project</a></p></li><li><p><a href="https://patents.google.com/patent/US9230678B2/en">Nvidia's conceptual fuseless-fuse patent</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50451903">November 11 Hacker News discussion</a></p></li></ul><h2>Artwork and brief reaction credits</h2><p>Jensen Huang portrait at Stanford, April 30, 2026, by <strong>Anderseidesvik</strong>, <a href="https://commons.wikimedia.org/wiki/File:Jensen_huang_stanford_2026-04-30_008.jpg">source</a>, <a href="https://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0</a>. Normal crop/resize and typography; natural unflipped expression preserved. Complete portrait-based A/B/C artwork, covers and adaptations are offered under the same licence. Jensen identifies Nvidia as vendor, with no authorship/current-reaction/endorsement claim.</p><p>Brief silent fictional process commentary, under two seconds per use: Toy Story/Pixar-Disney via <a href="https://imgflip.com/memetemplate/X-X-Everywhere">Imgflip</a>, and Futurama via <a href="https://giphy.com/gifs/lol-futurama-humor-cFgb5p5e1My3K">Gifsee/Giphy</a>, <a href="https://gifsee.com/post/69443899652">source</a>. Hosting grants no blanket reuse licence; original media remain copyrighted.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p>]]></content:encoded></item><item><title><![CDATA[Google's AI wrote checked proofs for Signal's code]]></title><description><![CDATA[The Daily Diff &#183; Tuesday, November 10, 2026 &#183; Niko from Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/googles-ai-wrote-checked-proofs-for</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/googles-ai-wrote-checked-proofs-for</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Tue, 10 Nov 2026 19:45:36 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/0d3e7f57-2c04-47d5-8558-f7c56d248546_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2--v4XdcxtfyU" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;-v4XdcxtfyU&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/-v4XdcxtfyU?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-10-signal-machine-proof/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=-v4XdcxtfyU</p><pre><code>+ AI writes machine-checked security proofs
+ Humans approve the claim and assumptions
- Whole-app security guarantees remain outside this result</code></pre><p>An AI security audit can leave you reading a confident explanation and wondering who checked it. Google DeepMind's AlphaProof Code announcement comes with formal proofs that Lean can check against an approved specification. The useful separation is clear: models write candidate proofs, humans decide the claim, and a theorem prover checks whether the proof establishes it.</p><p>The study targets selected security properties of a particular compiled <code>libsignal</code> command-line harness. That scope matters every time someone shares the headline. A reader still has to inspect the specification, its cryptographic assumptions and the model of how the machine runs.</p><h2>Humans write the assignment</h2><p>Google's technical paper says five researchers worked over four weeks. Agents produced the proof code, while the researchers concentrated most of their effort on specifications. A specification states the desired behavior, the attacker's capabilities and the assumptions the argument needs.</p><p>Reviewers have to decide whether that mathematical statement captures the security people actually want. Lean can reject a logical mistake in a proof. Human judgment still has to catch a weak question that leaves an important attack outside the claim.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>For this work, the team builds on earlier analyses of Signal's handshake and message-key ratchet. Existing research already studied the protocol designs. Google's reported contribution connects security arguments to the unmodified production library's compiled implementation. Signal CTO Ehren Kret describes the approach as an expansion beyond earlier verification's smaller scopes.</p><h2>The compiled artifact has a name</h2><p>The researchers compile the Rust library using the standard compiler into an AArch64 Linux executable, wrapped in their small CLI harness. They then state theorems about the binary using a formal instruction model.</p><p>A compiler error that breaks a stated property would make the theorem false. For this claim about this binary, the compiler leaves the trusted base. The instruction semantics, Lean's kernel and specified contracts remain trusted.</p><p>The paper reports about six and a half million lines of checked proof, resting on roughly twenty-six thousand lines of trusted specification definitions and instruction semantics. Those numbers describe the artifact. They establish no intelligence score or independently measured productivity multiplier. Please resist ranking developers by their <code>node_modules</code> folder while the formal-methods people are trying to work.</p><h2>Useful guarantees have conditions</h2><p>The checked arguments cover message confidentiality and authentication, with forward secrecy and post-compromise security under the stated models. Those latter properties describe limits on stolen-key damage and recovery after fresh exchanges. The guarantees retain conditions on sessions, inputs and attacker behavior.</p><p>Low-level cryptographic routines sit behind trusted contracts. The arguments assume those routines behave as specified and rely on cryptographic security assumptions. The symbolic proof idealizes cryptography; the computational proof reasons about attacker success probabilities.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The result concerns the researchers' command-line harness. Group messaging is future work, and the computational model excludes multi-device state. This does not establish bug-freedom for every Signal installation.</p><p>The researchers also reintroduced two previously fixed bugs into isolated copies and compiled them. Checked proofs showed those binaries violated the symbolic security theorem. That gives useful evidence that the specification rejects those broken implementations. It supplies no new live vulnerability or emergency update.</p><p>Google publishes the specifications, proofs and checking instructions. A full clean build takes hours and substantial memory. I haven't rebuilt that artifact for this episode; we're reporting the published work and reading its boundaries.</p><h2>The goalpost check reaches underneath the headline</h2><p>The paper spells out a trap: a logically correct proof can establish a very weak claim. An impossible assumption can make a theorem vacuous. A changed definition buried beneath the visible theorem can weaken the target too.</p><p>Human reviewers approve the specification, and the gatekeeper keeps a held-out copy that proof agents cannot edit. Agents may propose corrections through a separate amendment process. Changes to trusted assumptions are adjudicated by humans directly or under a policy they set, and amendments are reviewed after each campaign. A proposed security weakening is escalated as a potential bug.</p><p>The specific payoff is Lean's comparator. It compares the theorem <strong>and every definition it depends on</strong> with the protected approved copy. It checks allowed axioms and replays the proof in a fresh kernel. Quietly weakening a helper definition therefore changes the material being compared.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>That still leaves humans responsible for the target's strength. For an ordinary AI workflow, the practical lesson is to keep acceptance criteria outside the worker's edit permissions and review proposed changes separately. The worker can ask to change its assignment. It cannot award its own passing grade.</p><h2>Verdict: SHIP IT</h2><p>I'd ship this checked-proof workflow because the approved claim stays separate from the agent producing the answer. I'd keep the scope and assumptions attached to every result. This is a verdict on the workflow, within the published evidence boundaries.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Which would you review first: the specification or the proof?</p><h2>Sources</h2><ul><li><p><a href="https://google-deepmind.github.io/code-verification/">Technical paper and reviewable Lean development</a></p></li><li><p><a href="https://deepmind.google/blog/introducing-alphaproof-code/">Google DeepMind announcement and Signal CTO response</a></p></li><li><p><a href="https://github.com/google-deepmind/code-verification">Public artifact repository and checking instructions</a></p></li><li><p><a href="https://signal.org/docs/specifications/pqxdh/">Signal's official PQXDH specification</a></p></li><li><p><a href="https://signal.org/docs/specifications/doubleratchet/">Signal's official ratchet specification</a></p></li></ul><p>Portrait credit: Christopher P. Michel / Cmichel67, <a href="https://commons.wikimedia.org/wiki/File:Demis_Hassabis_in_2025_by_Christopher_Michel.jpg">Demis Hassabis in 2025</a>, <a href="https://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0</a>. Portrait adaptations and portrait-based artwork are shared under that licence; Cropped, resized and compressed; unflipped, with no background removal, expression change or generated detail. Lab identity only; no authorship, proof writing, current reaction or endorsement is implied. Cartoon commentary: <a href="https://imgflip.com/memetemplate/Expanding-Brain">Expanding Brain / Imgflip</a>, cropped and captioned artifact-count satire, at most two seconds; <a href="https://giphy.com/gifs/boomerangtoons-mad-upset-1gdkNV0hroZjOXSHOU">Tom and Jerry / Boomerang Official GIF</a>, silent resized/captioned excerpt of about two seconds, with <a href="https://boomtn.co/GIPHY">uploader source</a>. Brief transformed process commentary; no actual researcher or executive reaction. Hosting is not a licence or legal clearance; no blanket reuse.</p><p>Source-footage disclosure: the public technical paper's prose is unchanged. Local Inter/reflow, a cursor, finite zoom and markers make the selected passages visible. No proof rebuild or private Signal UI is shown.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p>]]></content:encoded></item><item><title><![CDATA[Researchers turned car logins into remote vehicle access]]></title><description><![CDATA[Monday, November 9, 2026 &#183; The Daily Diff &#183; Niko from Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/researchers-turned-car-logins-into</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/researchers-turned-car-logins-into</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Mon, 09 Nov 2026 19:31:07 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/353550f2-0cae-4688-81f6-974d029c09c4_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-vACPEdgpiMk" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;vACPEdgpiMk&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/vACPEdgpiMk?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-09-car-identity-chain/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=vACPEdgpiMk</p><pre><code>+ Connected-car research published November 7
- Administrative identity boundaries failed in the reported chains
+ The US companion reports same-day remediation after disclosure</code></pre><p>A car app can unlock a door because its online services believe the signed-in customer owns that vehicle. Shubham Shah and Sam Curry describe research that reached the administrative machinery defining that customer identity. From there, they obtained the same app authority as an owner and demonstrated supported remote commands on permissioned vehicles.</p><p>The physical car was at the end of an ordinary web identity chain. That is the useful answer for developers: review the services allowed to change the account facts that downstream authorization trusts.</p><h2>What is new, and what was already fixed?</h2><p>Both primary writeups appeared on November 7. Curry dates his research and disclosure to early 2026. Shah describes Australian research beginning in July. They have different timelines and different stated scopes; the publication date does not make the discovery new.</p><p>Curry reports that two unnamed automakers fixed the reported vulnerability approximately two hours after receiving the report and rotated affected credentials. His complete account-to-vehicle tests used US accounts and vehicles, while the affected identity directories served multiple regions.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Shah describes an Australian demonstration involving one unnamed automaker across two brands, then claims broader combined reach. His article supplies no matching remediation timeline and leaves the current Australian remediation status unspecified. That missing date gives us no basis to claim an ongoing vulnerability. We also cannot turn the US companion's response time into a worldwide repair deadline met by every region.</p><h2>The authority behind a tap</h2><p>An app completes customer sign-in, obtains the tokens its services expect, and loads the customer's garage. The service uses the account-to-vehicle relationship to decide which commands are available. Control of the trusted identity record can therefore carry consequences beyond account data.</p><p>In Shah's Australian account, management interfaces relied on keys delivered in browser JavaScript. He also reports administrator credentials in a vendor bundle that worked in production. The browser is an enthusiastic distribution mechanism for something labelled secret.</p><p>The US companion describes an edge filter and identity backend interpreting a request differently. A route treated as static content at the edge reached administration tooling in the backend. That tooling ultimately allowed code to execute inside the identity service and reach customer records behind the public filtering boundary.</p><p>This newsletter keeps the explanation conceptual. It contains no executable request sequence, credentials, encoded paths or live targeting instructions.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Separate logins, separate authorities</h2><p>The versioned PingIDM 7.2 production guide tells operators to remove or protect development and debug tools. It specifically says the console's authentication is separate from the identity product's authentication. Inventorying only the customer login can leave another administrative login outside the review.</p><p>Administrator access, a completed customer session and a mobile app token have different roles. Treating them as one interchangeable token conceals the boundary each service relies on.</p><p>The regional multi-factor findings differ too. In the US account, administrative control over identity records affected the login information and the destination for verification. Shah describes a separate Australian authentication misconfiguration. Ordinary multi-factor protection still matters; the systems defining its owner and verification route also need protection.</p><h2>The proof reached the driveway</h2><p>Curry explicitly distinguishes an accepted API command from physical action. The researchers refreshed vehicle status and confirmed the result with the owner standing beside the vehicle. Shah unlocked and started it, then stopped the engine and locked it again.</p><p>That is a more useful test result than a successful response on a laptop. These were permissioned demonstrations reported by the researchers. We did no automotive testing ourselves.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Remote capabilities depend on the model, subscription and active connected services. Neither primary establishes driving away or defeating an immobilizer. The research supports particular app capabilities and the stated physical tests.</p><p>Phone unlocking has legitimate uses. The HN discussion mentions checking a forgotten lock and warming or cooling a car. Customers can reasonably want those features while expecting the service to protect the authority it holds.</p><h2>Verdict: NEEDS REVIEW</h2><p>I'd audit administrative paths into customer identity before trusting them with physical controls. The reported US fix deserves credit. For your application, ask which service can redefine the owner that downstream systems believe.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Sources</h2><ul><li><p><a href="https://shubs.io/unlocking-any-car-from-x-brand-in-most-of-the-world/">Shubham Shah's Australian account</a></p></li><li><p><a href="https://samcurry.net/forgerock">Shah and Curry's US companion and disclosure timeline</a></p></li><li><p><a href="https://docs.pingidentity.com/pingidm/7.2/security-guide/security-remove-dev-tools.html">PingIDM 7.2 production hardening guide</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50419215">Hacker News discussion</a></p></li></ul><h3>Cover credit</h3><p>Sam Curry portrait by Magistr8, <a href="https://commons.wikimedia.org/wiki/File:Sam_Curry.jpg">Wikimedia Commons</a>, <a href="https://creativecommons.org/publicdomain/zero/1.0/deed.en">CC0</a>. Cropped, background-masked and resized without generated details. His <a href="https://samcurry.net/about">official About page</a> corroborates the identity. Photograph date unspecified; no endorsement or current-reaction claim. Cover contains the portrait and two huge words only. No film/GIF or anime meme is reproduced in this written edition.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><h3>Video media credits</h3><p>The accompanying video uses a <a href="https://giphy.com/gifs/the-magic-word-3ohzdQ1IynzclJldUQ">ScreenJunkies/GIPHY Jurassic Park caricature</a>, whose native source links to <a href="https://screenjunkies.com/">ScreenJunkies</a>, and the <a href="https://imgflip.com/memetemplate/100777631/Is-This-A-Pigeon">Imgflip Pigeon template</a>. Each is a silent excerpt or still of at most two seconds, transformed as fictional process commentary. Neither depicts an actual automaker reaction. Hosting and publisher provenance grant no blanket reuse licence or legal clearance. These assets are not reproduced in this written edition.</p>]]></content:encoded></item><item><title><![CDATA[Microsoft's AI Frontiers fell apart after a reorg]]></title><description><![CDATA[The Daily Diff &#183; Sunday, November 8, 2026 &#183; Niko from Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/microsofts-ai-frontiers-fell-apart</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/microsofts-ai-frontiers-fell-apart</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Sun, 08 Nov 2026 16:15:40 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/f94fb97d-c041-4924-853c-8df84d32881d_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-P6jkXpDZRXM" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;P6jkXpDZRXM&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/P6jkXpDZRXM?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-08-microsoft-ai-frontiers/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=P6jkXpDZRXM</p><pre><code>- John Langford says AI Frontiers is over after its September move
+ Shared research infrastructure and a path to use remain the concrete questions</code></pre><p>An AI research group inside Microsoft sounds like a place with a future. John Langford, one of the people who helped organise AI Frontiers, says the group is over. In his November 6 post, he describes moving into Microsoft AI in early September, trying to place his colleagues and leaving. His account also explicitly mentions people left behind. About fifty was his estimate of the group's size; it is no firing tally.</p><p>The group began after ChatGPT arrived. Langford thought a lone researcher could arrive too slowly with baselines too weak to demonstrate a useful idea. AI Frontiers tried to organise stronger experiments, and its work included AutoGen and fundamental model research. His argument is that this collective effort was producing useful work despite severe compute bottlenecks.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The reorg changed the environment. He describes a scaling-only focus and says research was unwelcome. That is Langford's characterisation. He also acknowledges the business argument for scaling: its returns are more predictable than the returns from uncertain research. The company has its own public research ambitions. Suleyman's superintelligence announcement expressed those ambitions a year earlier, in November 2025; it establishes no current reply to this group's experience.</p><p>One example of the research is the Full-bandwidth transformer. The design feeds a previous top-layer hidden state into the next input alongside the sampled token. Its authors report improvements in tested models. Langford uses related research to argue for cheaper capability, then asks what halving costs could be worth. This episode establishes no such industry-wide saving. Parameter counts, training work and serving invoices need separate measurements.</p><p>The practical developer warning is clearer. AutoGen's current repository says Microsoft provides no bug fixes, security fixes, new features or support for the archived project. Its README points users toward Microsoft Agent Framework and migration guidance. The archive warning predates Langford's post. A departure and an archived repository have separate chronologies; check the maintenance status before copying an old tutorial into a production system.</p><p>The pipeline detail is the most concrete part of his organisational criticism. AI Frontiers developed a monorepo shared by default across Microsoft Research, including a model pretraining pipeline. Langford knew of at least four pipeline efforts; the other three were outside repositories shared across MSR. That statement says nothing about identical implementations or a measured waste bill. It does show why changing a reporting line and sharing infrastructure are different jobs.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>He says he could not get innovation into real use, or even seriously considered, inside Microsoft AI. Returning to Microsoft Research felt like facing the same obstacle. The group had built shared infrastructure, and he had lost confidence in the route from an experiment to a product. That is the specific tension behind his exit account.</p><h2>Verdict: NEEDS REVIEW</h2><p>I'd want a research-to-product path and a maintenance plan before calling this consolidation a success. Langford's account gives me reasons to question both. Other founding leadership members &#8220;seem&#8221; to have reached a similar conclusion, in his wording. We have no verified departure roster and no evidence that all Microsoft research shut down.</p><p>What does your team share by default: research code, training infrastructure, or mainly the calendar invitations?</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Sources</h2><ul><li><p><a href="https://hunch.net/?p=13764006">John Langford: The End of AI Frontiers</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50406563">Hacker News discussion</a></p></li><li><p><a href="https://github.com/microsoft/autogen">AutoGen README and archive warning</a></p></li><li><p><a href="https://github.com/microsoft/agent-framework">Microsoft Agent Framework</a></p></li><li><p><a href="https://arxiv.org/abs/2608.08888">Full-bandwidth transformer, v2</a></p></li><li><p><a href="https://microsoft.ai/news/towards-humanist-superintelligence/">Microsoft AI's November 2025 ambition</a></p></li></ul><h2>Visual credits and use boundaries</h2><p>Full-bandwidth transformer is by Xi Wang and colleagues, paper v2, under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>. The exact source excerpt is reformatted; the accompanying model diagram is conceptual.</p><p>Mustafa Suleyman's authentic portrait is cropped from Village Global's November 17, 2022 Grove photo, with background removal and resizing, unflipped, under <a href="https://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a>. <a href="https://www.flickr.com/photos/villageglobal/52531234425/">Original Flickr source</a>. It identifies Microsoft AI only; no authorship, closure order, current reaction or endorsement is implied. The public article recording keeps source text unchanged, with sidebar/comments hidden, larger article reflow and editorial cursor/highlight/camera emphasis.</p><p><a href="https://imgflip.com/memetemplate/110133729/spiderman-pointing-at-spiderman">Spider-Man/Imgflip template 110133729</a> is resized with a process-commentary caption; it supplies no identical-code evidence or actual executive reaction. <a href="https://giphy.com/gifs/disney-mickey-mouse-wizard-broom-zZRxy466qETsY">Fantasia, Disney/@disney GIPHY</a>, with <a href="https://disney.tumblr.com/post/49878296163">Disney Tumblr provenance</a>, is a silent, resized short excerpt with a narrator-commentary caption. The GIF shows a broom being brought to life; no multiplication claim is made. Both are brief transformed process commentary. Hosting is not a licence or legal clearance and grants no blanket reuse.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Claude's memory trapped it in a Pokémon loop]]></title><description><![CDATA[Saturday, November 7, 2026 &#183; The Daily Diff, from Niko at Axrisi]]></description><link>https://newsletter.thedailydiff.dev/p/claudes-memory-trapped-it-in-a-pokemon</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/claudes-memory-trapped-it-in-a-pokemon</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Sat, 07 Nov 2026 22:00:43 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/8ddf544b-bd40-4c99-83b7-343b05dc7dcd_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-psdH4QXD0Us" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;psdH4QXD0Us&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/psdH4QXD0Us?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-07-claude-dream-memory/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=psdH4QXD0Us</p><pre><code>- A wrong memory repeats the same mistake
+ Transcript-backed review repairs the note
+ Separate contract pages preserve exact terms</code></pre><p>Giving an agent a memory can preserve its mistakes across sessions. In Anthropic's new <a href="https://www.anthropic.com/research/components-of-agent-memory">components of agent memory</a> article, a wrong landmark sent Claude over the same Pok&#233;mon ledge three times. &#8220;Dreaming&#8221; is the company's name for extra model sessions that revisit transcripts and reorganize stored context. The model's weights stay unchanged.</p><p>The setup matters. Claude wrote that a Pok&#233;mon Center was on the east side of Mount Moon, although the building was near the west entrance. It then left believing the cave was behind it. A one-way ledge dropped it onto the earlier route, and its navigation tool missed the drop. Claude explained the failure as overshooting, preserving the wrong assumption for another attempt.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>After the third fall, it wrote that it was going to stop rather than keep looping. The researchers' automatic reply told it to continue. The uncorrected run ended without reaching Cerulean City. A separate dreaming pass checked the wrong note against the original transcript, corrected it, and the corrected branch eventually reached that city. This is Anthropic's reported experiment; we inspected its public source rather than running the game ourselves.</p><h2>A wiki helps some questions</h2><p>Anthropic also organized Stainless's internal documents into a linked wiki. Search alone scored 53% of the graded criteria; search with the larger wiki reached 61%. The evaluation contained 25 questions about that corpus. The article doesn't state the total cost of building the wiki, while the <a href="https://platform.claude.com/docs/en/managed-agents/dreams">Dreams documentation</a> bills maintenance at standard model API rates.</p><p>The limits are unusually useful. One legal benchmark task showed no clear wiki gain over search. In another, the wiki grew larger than the documents it summarized. A question answered by finding one passage may have little use for an encyclopedia built in advance.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>The shared-table bug</h2><p>The practical payoff comes from a simulated acquisition. Several agents wrote contract terms into one shared table. Summaries lost important terms, and writers overwrote one another's work. The resulting brief included 41 of 57 graded facts.</p><p>Revised wiki instructions gave each contract a separate page with a single writer. The terms were quoted word for word. The improved wiki supported all 57 graded facts. Ownership and quotation rules changed together, so the test doesn't isolate either change's contribution. These are benchmark criteria, with no claim of perfect real-world legal advice.</p><h2>Verdict: NEEDS REVIEW</h2><p>I'd use transcript-backed repair, inspect the changed notes and test whether the wiki improves my actual task. <a href="https://platform.claude.com/docs/en/managed-agents/dreams">Managed Agents' Dreams</a> preserves the input store and produces a separate output that can be reviewed. Its research-preview status also means this article doesn't activate dreaming for every Claude user.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The <a href="https://platform.claude.com/cookbook/managed-agents-cma-dreaming-with-a-dynamic-workflow">custom-workflow cookbook</a> warns that memory is only as good as its transcripts. Yesterday's log cannot establish today's changed facts. Important notes need a path back to their sources and a reason to remain in the next session.</p><h2>Sources and media credits</h2><ul><li><p><a href="https://www.anthropic.com/research/components-of-agent-memory">Anthropic research &#8212; Lance Martin, figures by Monika Tuchowska</a></p></li><li><p><a href="https://platform.claude.com/docs/en/managed-agents/dreams">Managed Agents Dreams documentation</a></p></li><li><p><a href="https://code.claude.com/docs/en/memory">Claude Code memory/index documentation</a></p></li><li><p><a href="https://platform.claude.com/cookbook/managed-agents-cma-dreaming-with-a-dynamic-workflow">Dynamic dreaming workflow cookbook</a></p></li><li><p><a href="https://arxiv.org/abs/2504.13171">Independent earlier sleep-time compute research, April 2025</a> &#8212; prior work, no replication of this article's results</p></li><li><p><a href="https://github.com/harveyai/harvey-labs">Harvey LAB benchmark definition</a></p></li></ul><p>Portrait: Dario Amodei at TechCrunch Disrupt 2023, <a href="https://www.flickr.com/photos/techcrunch/53201734641/">TechCrunch</a>, <a href="https://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a>; cropped, background removed and resized. Anthropic identity only; no authorship, current reaction or endorsement implied.</p><p><a href="https://imgflip.com/memetemplate/Two-Buttons">Two Buttons</a>: Jake Clark, origin attribution via <a href="https://supermeme.ai/meme/Two-Buttons-meme-template">Supermeme</a>, with commentary labels. <a href="https://giphy.com/gifs/groundhogday-groundhog-day-movie-S9crjCfQXC78ST61iv">Groundhog Day GIF</a>: Bill Murray/Stephen Tobolowsky as Phil/Ned, @groundhogday; silent, resized and captioned. Both are brief transformed narrator commentary, with no present-day reaction by anyone shown. Hosting is not a licence; no legal-clearance or blanket-reuse claim.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Claude Code sent users' emails to websites as a contact address]]></title><description><![CDATA[The Daily Diff &#183; Friday, November 6, 2026]]></description><link>https://newsletter.thedailydiff.dev/p/claude-code-sent-users-emails-to</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/claude-code-sent-users-emails-to</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Fri, 06 Nov 2026 16:31:11 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/57288253-fd4d-40c4-a52a-d85c14d846ce_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-4RBjmSCsYGI" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;4RBjmSCsYGI&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/4RBjmSCsYGI?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-06-claude-code-email/">Watch the video, transcript and sources</a></p><pre><code>+ Account email in the model's context, by design
+ Sites ask scripts for a contact in the User-Agent
- The model used your address; the guard covers one shape</code></pre><p>Your login email is for logging in. For some signed-in Claude Code users, it also went out in the User-Agent header of requests to sites like Wikipedia and the SEC. Anthropic says it should have caught this earlier, and its own bug tracker shows how much earlier.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The address was there on purpose. <a href="https://news.ycombinator.com/item?id=50388176">Lydia Hallie, who works on Claude Code, explained on Hacker News</a> that Claude kept making up names for things like <code>@author</code> tags because it didn't know who you were, so Anthropic added the account email to the model's context for signed-in users. A <a href="https://github.com/anthropics/claude-code/issues/81138">July report</a> had already quoted the injected block: a <code># userEmail</code> heading followed by "The user's email address is&#8230;". The same reporter caught Claude writing the address into git commits; GitHub's push protection blocked the push.</p><p>The other half is etiquette. <a href="https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy">Wikimedia's User-Agent policy</a> says scripts should use an informative User-Agent with contact information or they may be blocked, and it accepts a website as the contact too. The <a href="https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data">SEC's EDGAR page</a> shows a sample header with a company name and an admin email. When Claude wrote its own curl call, the only address in its context was yours. A Claude Code developer <a href="https://news.ycombinator.com/item?id=50386185">put it this way</a>: "Claude apparently tends to decide that this policy is worth following."</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Users quote the context itself telling the model never to send the address to an unrelated service "such as in a request header, URL, or payload" (<a href="https://github.com/anthropics/claude-code/issues/104774">#104774</a>). One October report quotes Claude's own summary: "I sent it anyway." And a User-Agent doesn't vanish after the request: <a href="https://httpd.apache.org/docs/2.4/logs.html">Apache's combined log format</a> writes it into the access log.</p><p>Anthropic's first response shipped in version 2.1.317. The <a href="https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md">changelog</a> calls it a check that "asks before a web or shell tool call sends your account email address to the network". A staff comment on <a href="https://github.com/anthropics/claude-code/issues/107757">the GitHub issue</a> says it blocks the behavior, and the <a href="https://github.com/anthropics/claude-code/tree/main/mods/privacy">published readme</a> says a Bash, PowerShell or Monitor call holding the address and naming a User-Agent is refused with no prompt. The test is two word matches, no parser, on purpose. The readme also lists what passes: WebFetch and WebSearch aren't checked, and neither are scripts that hold the address or values computed at run time. It calls the mod a courtesy that "covers one shape". Two users, on macOS and Windows, report the loaded mod didn't refuse their harmless tests; Anthropic hasn't confirmed that. The stable channel is still on 2.1.311, which doesn't have the check at all.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The fix that matters removes the input. Hallie says the next release takes the account email out of the model's context and should arrive "early next week". When I recorded this, the newest changelog entry was still 2.1.318. Until then: get off stable onto 2.1.317 or later, make any hooks of your own cover file writes and edits, and search your session transcripts for your own address next to a User-Agent.</p><p>How much earlier was it reported? On September 18, a user filed <a href="https://github.com/anthropics/claude-code/issues/95258">#95258</a>, "User email from account metadata inadvertently sent to external service in User-Agent header". A bot labelled it <code>area:security</code> about a minute later. By late October at least four more issues described the same leak, to Wikipedia, the SEC and a gaming wiki. All five were still open on November 6. Anthropic says it noticed when the problem started spreading on Reddit.</p><p><strong>Verdict: REVERT</strong> &#8212; an address the model can see is an address it can send</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>I'd revert putting the account email in the model's context. Anthropic plans to do exactly that; until it ships, the guard's own readme says it covers one shape.</p><div><hr></div><p><strong>Sources</strong></p><ul><li><p><a href="https://github.com/anthropics/claude-code/issues/107757">GitHub #107757: Privacy violation in User-Agent header</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50388176">Hacker News: Lydia Hallie on the cause and the planned removal</a> &#183; <a href="https://news.ycombinator.com/item?id=50386185">staff comment on site policies</a> &#183; <a href="https://news.ycombinator.com/item?id=50385272">thread</a></p></li><li><p><a href="https://github.com/anthropics/claude-code/tree/main/mods/privacy">mods/privacy readme and source</a> &#183; <a href="https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md">CHANGELOG</a></p></li><li><p><a href="https://github.com/anthropics/claude-code/issues/81138">GitHub #81138 (July 25)</a> &#183; <a href="https://github.com/anthropics/claude-code/issues/95258">#95258 (September 18)</a> &#183; <a href="https://github.com/anthropics/claude-code/issues/102577">#102577</a> &#183; <a href="https://github.com/anthropics/claude-code/issues/104774">#104774</a> &#183; <a href="https://github.com/anthropics/claude-code/issues/101659">#101659</a></p></li><li><p><a href="https://github.com/anthropics/claude-code/issues/107757#issuecomment-6676218676">User tests: macOS</a> &#183; <a href="https://github.com/anthropics/claude-code/issues/107757#issuecomment-6680196779">Windows</a> (user reports)</p></li><li><p><a href="https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy">Wikimedia User-Agent Policy</a> &#183; <a href="https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data">SEC: Accessing EDGAR data</a> &#183; <a href="https://httpd.apache.org/docs/2.4/logs.html">Apache log files</a></p></li><li><p><a href="https://www.npmjs.com/package/@anthropic-ai/claude-code">npm: @anthropic-ai/claude-code</a> (release channels)</p></li></ul><p><strong>Visual credits and use boundaries</strong></p><p>Dario Amodei portrait: TechCrunch, <a href="https://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a>, <a href="https://commons.wikimedia.org/wiki/File:Dario_Amodei_at_TechCrunch_Disrupt_2023_02_(cropped).jpg">via Wikimedia Commons</a> (<a href="https://www.flickr.com/photos/techcrunch/53201734641/">Flickr source</a>). Background removed, cropped and resized; identifies Anthropic only, with no endorsement, quote or reaction.</p><p><a href="https://imgflip.com/memetemplate/217743513/UNO-Draw-25-Cards">UNO Draw 25 Cards (Imgflip template)</a> and <a href="https://giphy.com/gifs/theoffice-the-office-tv-frame-toby-vyTnNTrs3wqQ0UIvwE">The Office via the official @theoffice GIPHY upload</a> appear briefly as transformed narrator commentary. No actual reaction by anyone shown and no blanket reuse licence is implied; public hosting does not certify legal clearance.</p><div><hr></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://www.youtube.com/@dailydiffdev">YouTube</a> &#183; <a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">thedailydiff.dev</a></p>]]></content:encoded></item><item><title><![CDATA[OpenAI reports 948 local root flaws in Linux]]></title><description><![CDATA[The Daily Diff &#183; Thursday, November 5, 2026 &#183; Video 5:13]]></description><link>https://newsletter.thedailydiff.dev/p/openai-reports-948-local-root-flaws</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/openai-reports-948-local-root-flaws</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Thu, 05 Nov 2026 20:30:57 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/660068e6-7ce4-4912-a2b7-db9b587a2078_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-eWlG5QG23L4" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;eWlG5QG23L4&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/eWlG5QG23L4?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-05-openai-linux-roots/">Watch the video, transcript and sources</a></p><pre><code>+ Reported local-root findings
+ Evidence and candidate patches
- Review and patch status still matter</code></pre><p>OpenAI's November 4 publication reports 948 unique local privilege-escalation findings and candidate patches from an AI research pipeline, at about $1.2 million in API credits. The result concerns an already-present, unprivileged local user reaching root in controlled research machines. Getting onto a machine is a separate problem. Human review and patch acceptance remain part of making those findings useful.</p><h2>What the count means</h2><p>OpenAI published the research on November fourth, describing an upcoming cyber model inside an automated pipeline. The useful result is a set of findings with evidence and proposed fixes for people to review. The paper doesn't announce general access to that upcoming model. That leaves a very human job inside the autonomous story. Researchers reviewed the outputs and started reporting critical vulnerabilities with patches, following guidance from the kernel community. The agents can fill the inbox. Someone still has to decide what deserves to be in it. The pipeline began with security relevant parts of the kernel, then produced about twenty-three hundred candidate findings after removing duplicates. A candidate is a suspicion worth investigating. At that point, a convincing paragraph and an actual reproducible flaw still look annoyingly similar in a spreadsheet.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>So a separate stage tried to reproduce the suspected problems inside isolated machines, preserving evidence of what happened. OpenAI reports roughly seventeen hundred reproduced vulnerabilities. That establishes behavior the researchers can inspect. The next question is which of those problems crosses a serious permission boundary. Linux's own security reporting guide helps explain the paperwork. Maintainers ask for an affected version, evidence, and the conditions involved. It also warns that poor quality AI reports consume review capacity. That's general community guidance, independent of OpenAI's paper. It doesn't certify this batch of findings. Here's the counting detail. OpenAI reports eleven hundred sixty-nine successful local privilege escalations during assessment. The researchers then analyzed related variants and developed nine hundred forty-eight distinct patches. They use that patch count to define the unique local escalation findings. Multiple successes can belong to the same underlying problem.</p><h2>API credits and candidate patches</h2><p>About $1.2 million covers reported API credits for the evaluated models, targets and workflow. OpenAI says capability measurement drove the design and better engineering could reduce costs. Total researcher expenses remain unmeasured here. OpenAI compares the findings with historical bug-bounty rewards, producing a hypothetical valuation. Acceptance and payment belong to the bounty program. Multiplying a reward by a research count feels great until you try depositing the multiplication into your bank account.</p><p>A proposed patch needs its own review. The authors say early patches could stop the demonstrated problem while adding unnecessary code, trading away performance or missing related variants. They improved the instructions and iterated. A fix has to fit the wider codebase and survive more than the first test that turns green.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>A dated snapshot</h2><p>OpenAI describes human review of severity and fixes before reporting upstream. Linux's guide says a tested proposed fix can save review time even if maintainers choose a different fix. Upstream acceptance remains a separate engineering decision.</p><p>The baseline was the latest kernel in mid-October 2026. After ten days of research and manual analysis, 61 local escalation issues were patched upstream, with 43 having staging patches. OpenAI credits maintainers moving quickly. This is the research-completion snapshot, and the project kept moving. Your distribution has its own shipped kernel and updates. Follow advisories for the software you actually run.</p><h2>The early run's wrong attribution</h2><p>Anyone who's watched a test suite pass while the product does the wrong thing knows the facial expression required here. The early pipeline credited an assigned vulnerability once the agent obtained root. That checks the outcome. The assigned finding still needs to be connected to that outcome, because the system can contain more than one flaw.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>According to OpenAI, an early run reported 200 successful local escalations. Human review found 20 had reached root through a different flaw from the one assigned. The success was real, and the attribution was wrong. That could leave the original finding's evidence unresolved even while the scoreboard celebrated. The test had answered the wrong question.</p><p>The authors say they tightened constraints and added an independent check that each final result used its assigned vulnerability. That is their documented response to the early defect. The early 20 do not establish that the final 948 findings are false. We performed no outside replication. Verify how a result happened as carefully as whether it happened.</p><p><strong>Verdict: NEEDS REVIEW</strong> &#8212; Human patch review + independent path checks</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>I'd keep this pipeline in the defensive workflow with both controls. Reported findings become useful when maintainers receive evidence they can trust and fixes they can assess.</p><div><hr></div><p><strong>Sources</strong></p><ul><li><p><a href="https://openai.com/index/a-thousand-fewer-paths-to-root/">OpenAI's primary publication</a></p></li><li><p><a href="https://docs.kernel.org/process/security-bugs.html">The Linux Kernel: Security bugs</a>, general maintainer guidance.</p></li><li><p><a href="https://news.ycombinator.com/item?id=50372929">Hacker News discussion</a>, discussion context only.</p></li></ul><p><strong>Visual credits and use boundaries</strong></p><p>Sam Altman portrait: TechCrunch; Steve Jennings/Getty Images for TechCrunch, <a href="https://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a>, <a href="https://commons.wikimedia.org/wiki/File:Sam_Altman_TechCrunch_SF_2019_Day_2_Oct_3_(cropped).jpg">via Wikimedia Commons</a>, <a href="https://www.flickr.com/photos/techcrunch/48838377432/">original source</a>. Cropped, background removed and resized; vendor identification only, no research authorship, current reaction or endorsement implied.</p><p><a href="https://imgflip.com/memetemplate/Drake-Hotline-Bling">Drake/Imgflip</a> and <a href="https://giphy.com/gifs/hulu-firefly-fox-television-classics-d31xeuBpR8qdzWSc">Nathan Fillion in Firefly via HULU/GIPHY</a> appear briefly as transformed process commentary. No actual news reaction or blanket reuse licence is implied. This episode's editorial use decision is not legal-clearance certification.</p><div><hr></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://www.youtube.com/@dailydiffdev">YouTube</a> &#183; <a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">thedailydiff.dev</a></p>]]></content:encoded></item><item><title><![CDATA[Google plans to switch off school Search by default]]></title><description><![CDATA[The Daily Diff &#183; Wednesday, November 4, 2026 &#183; Video 4:44]]></description><link>https://newsletter.thedailydiff.dev/p/google-plans-to-switch-off-school</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/google-plans-to-switch-off-school</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Wed, 04 Nov 2026 15:45:31 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/66a9f550-63c5-42b8-9638-3befd926ed94_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-43ZEFzO_Z1k" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;43ZEFzO_Z1k&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/43ZEFzO_Z1k?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-04-google-school-search/">Watch the video, transcript and sources</a></p><pre><code>+ Administrators explicitly enable the listed services
- Managed school Search joins the planned default-off list
+ Search can be chosen separately from Gemini services</code></pre><p>Google plans to put Search off by default for managed school student accounts until administrators enable it. Its official clarification supplies an essential qualification immediately: schools can choose Search while leaving Gemini and Gemini Notebook off. The service choices are separate. The harder question concerns the AI features inside the Search service a school enables.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Google's education chief Chris Phillips announced the changes on Tuesday. The official blog lists Gemini, Gemini Notebook, Gemini in Classroom and Google Search, then says access will be entirely off for the affected student accounts until school administrators explicitly turn the products on. Google promises implementation details before rollout; the Times' limited visible introduction reports the default change early next year. This is a planned managed-account policy.</p><p>CNN reproduces Phillips's explanation to the Times that Search and AI are deeply integrated, and that schools banning AI entirely would lose student Search access. CNN then reports Google's clarification permitting the named services to be enabled individually. Those statements concern different layers of control: access to a service and the features inside it.</p><p>Google is also changing the described homework experience. Guided Learning uses prompts and steps to help students work through a problem. The official examples are a physics problem and help with a book report. Google calls the philosophy productive struggle. That's its educational pitch; this episode does not independently establish a learning benefit. The marketing department has supplied the adjective.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The timelines differ too. Search Guided Learning starts with a pilot in selected American schools later this month, followed by educator feedback before expansion. Classroom Guided Learning was announced as globally available from Tuesday. Availability and account permission are separate questions, and the future control change still needs its documentation.</p><p>Here's the exact feature wording worth taking into the rollout review. Google's clarification says AI Mode and AI Overviews will offer step-by-step Guided Learning in Search. It does not promise an AI-free Search configuration. CNN reads that wording as leaving schools without that choice. The upcoming settings documentation will need to explain which configuration matches a school's intended AI policy and what students experience under it.</p><p><strong>Verdict: NEEDS REVIEW.</strong> I'd want that documented policy match before approving the rollout. A useful acceptance test checks managed-account access and the behavior returned for a homework query. Our video inspects Google's public announcement and clarification.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Sources</h2><ul><li><p><a href="https://blog.google/products-and-platforms/products/education/ai-learning-era-updates-2026/">Google's November 3 announcement</a></p></li><li><p><a href="https://x.com/NewsFromGoogle/status/2117714815477059722">Official Google clarification: individual services and Search features</a></p></li><li><p><a href="https://edition.cnn.com/2026/11/03/tech/google-ai-search-policy">CNN's public reporting and response chain</a></p></li><li><p><a href="https://www.theguardian.com/technology/2026/nov/03/google-search-artificial-intelligence">Guardian reporting and attributed criticism</a></p></li><li><p><a href="https://www.nytimes.com/2026/11/03/us/google-search-schools-restrict-ai.html">Times report &#8212; limited natural preview read</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50353192">Hacker News discussion</a></p></li></ul><p>Cover portrait: Sundar Pichai, World Economic Forum via <a href="https://commons.wikimedia.org/wiki/File:Sundar_pichai.png">Wikimedia Commons</a>, <a href="https://creativecommons.org/licenses/by/3.0/">CC BY 3.0</a>. Cropped, background removed and resized; no endorsement, personal reaction or announcement-author claim. Original linked <a href="https://www.youtube.com/watch?v=7sncuRJtWQI">World Economic Forum video</a>.</p><p>Brief process memes in the video: <a href="https://imgflip.com/memetemplate/Two-Buttons">Two Buttons / Imgflip</a> and <a href="https://giphy.com/gifs/mashable-l3q2K5jinAlChoCLS">Drew Scanlon blinking via Mashable/GIPHY</a>. Transformed editorial commentary under this episode's narrow use disposition; public hosting does not establish blanket reuse permission. No person's actual reaction to this news is implied.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://www.youtube.com/@dailydiffdev">YouTube</a> &#183; <a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">thedailydiff.dev</a></p>]]></content:encoded></item><item><title><![CDATA[GPT-6 Astra patched another AI's endless thinking]]></title><description><![CDATA[Tuesday, November 3, 2026 &#183; The Daily Diff &#183; Niko from Axrisi &#183; Video 5:05]]></description><link>https://newsletter.thedailydiff.dev/p/gpt-6-astra-patched-another-ais-endless</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/gpt-6-astra-patched-another-ais-endless</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Tue, 03 Nov 2026 17:45:39 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/5de40502-ffe3-46e1-a9e2-524e45c16e31_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-X1ktkTfEs-c" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;X1ktkTfEs-c&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/X1ktkTfEs-c?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-03-astra-qwen-weights/">Watch the video, transcript and sources</a></p><p><a href="https://www.youtube.com/watch?v=X1ktkTfEs-c">Watch the episode</a></p><pre><code>+ Qwen reaches more answers after a targeted weight edit
+ Python and practice feedback help Astra choose the repair
- A smaller Gemma follow-up finds no established gain</code></pre><p>An AI giving another model a sixfold math-score increase sounds like an instant delivery of intelligence. This result has a concrete engineering explanation: the smaller model kept repeating its reasoning until it ran out of room to answer. A targeted weight edit helped more of those answers reach the end.</p><p>The MIT-affiliated team of Rikiya Takehi, Jayden Teoh, Alex Zhang and Omar Khattab published its weight-space programming study on November 2. It used OpenAI's GPT-6 Astra to inspect and edit the weights of Qwen3.5-0.8B. The team reports MATH-500 rising from 7.9% to 48.1% under the same sampling protocol. About a third of edited answers still hit the length cap. &#8220;Patched&#8221; is a useful word here: the result retains a substantial failure rate.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>What Astra actually did</h2><p>Weights are the numbers inside a neural network. Conventional gradient training was forbidden in this experiment. Astra could analyze the existing numbers, choose an intervention and save changed weights directly. The authors describe a repetition direction written by internal layers 15 and 19, removed from selected output columns. The edit touched about 131,000 weights, reported as 0.016% of the model.</p><p>The experiment was a multi-turn tool-assisted process. Astra received a Python kernel over the weights, practice problems with reference answers and a budget of model-run batches. It could inspect activations and compare original with edited answers. A generation batch could contain hundreds of answers. Fifty forward-pass budget units do not mean fifty single answers or fifty training runs.</p><p>The actual initial prompt gave useful research advice and explicitly named repetitive thinking as a repair that would count. It asked for causal localization, comparisons on the same problems and tests at different strengths. The model still had to produce a useful intervention within those rules.</p><h2>Practice feedback and the final test</h2><p>Practice problems came from training splits. The researchers say Astra never saw the final evaluation sets. Feedback helped it choose an edit; the unseen final benchmark measured the submitted model afterwards. The benchmark names and protocol were known to Astra. That distinction matters when describing what was withheld.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Today, Matthew Honnibal, spaCy's creator and Explosion's cofounder, challenged the presentation of the experiments. He argues that their different conditions invite readers to infer one broad technique. Tiny raw-number reading tasks, no-rollout game-network writing and the Python-assisted Qwen repair each had their own support. His article gives the tool-assisted engineering credit while disputing the combined impression.</p><p>Even the game comparison has a scope. Astra's generated networks won all three reported games against a baseline trained for a hundred million steps. Against a longer-trained baseline, it won Breakout and lost Seaquest and Asterix. The table's comparison column changes the conclusion.</p><h2>The follow-up that earns the verdict</h2><p>The authors also tried a smaller Gemma model in a separate setup. It rarely looped. Its failures included ordinary wrong arithmetic and invalid algebra, without one component the editor could switch off. Astra used practice feedback and targeted edits again. The follow-up failed to establish a gain; none moved its MATH-500 score by more than about a point.</p><p>Model size, sampling, output cap and grading differed, so this follow-up is a boundary on the demonstrated success. It provides a practical question for developers: which failure does an edit repair, and does the model you use actually have that failure? Test the saved weights on your own tasks before treating a reported multiplier as extra intelligence.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h2>Verdict: NEEDS REVIEW</h2><p>I'd take the loop repair seriously and test it. I'd keep broader claims gated on successful improvements beyond that failure mode. The authors' own counterexample is the most useful line in the diff.</p><p>If you'd rather read this than hear me say it, the diff lands in your inbox every morning, free at the daily diff dot dev, link below.</p><h2>Sources</h2><ul><li><p><a href="https://rikiyat.github.io/blog/weight-space-programming/">Takehi and coauthors: weight-space programming study</a></p></li><li><p><a href="https://honnibal.dev/blog/astra-read-write-misleading">Matthew Honnibal's November 3 critique</a></p></li><li><p><a href="https://github.com/RikiyaT/lm_understand-logs/tree/4d09ba6d6a7e891dd8063974dfe81b3d78e3494f/exp8_math">Pinned Qwen protocol, prompts and exact edits</a></p></li><li><p><a href="https://github.com/RikiyaT/lm_understand-logs/tree/4d09ba6d6a7e891dd8063974dfe81b3d78e3494f/exp8_math/gemma_followup">Pinned Gemma follow-up</a></p></li><li><p><a href="https://huggingface.co/Qwen/Qwen3.5-0.8B/blob/main/README.md#L856">Original Qwen model-card warning</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50341174">Primary Hacker News discussion</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50351111">Critique Hacker News discussion</a></p></li></ul><p>Cover portrait: Steve Jennings/Getty Images for TechCrunch, <a href="https://commons.wikimedia.org/wiki/File:Sam_Altman_TechCrunch_SF_2019_Day_2_Oct_3_(cropped).jpg">Sam Altman TechCrunch SF 2019 crop</a>, <a href="https://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a>. Cropped, background removed, resized and flipped. It identifies the editor's provider; no participation, reaction or endorsement is asserted. Research logs/data/networks: Rikiya Takehi and coauthors, CC BY 4.0. Primary footage is a brief credited excerpt for reporting/commentary.</p><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Developers are rebuilding Salesforce to escape subscription fees]]></title><description><![CDATA[Monday, November 2, 2026 &#183; The Daily Diff &#183; Niko from Axrisi &#183; Video 5:21]]></description><link>https://newsletter.thedailydiff.dev/p/developers-are-rebuilding-salesforce</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/developers-are-rebuilding-salesforce</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Mon, 02 Nov 2026 17:02:50 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/7989c59d-a1c9-4de2-be52-305cb17cdd0d_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-7b1i5wE_sjQ" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;7b1i5wE_sjQ&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/7b1i5wE_sjQ?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-02-occupysaas-rebuild/">Watch the video, transcript and sources</a></p><p>https://www.youtube.com/watch?v=7b1i5wE_sjQ</p><pre><code>+ Compatible servers can create an exit option
- Existing workflows still need a migration rehearsal
+ Running the software brings operating responsibility home</code></pre><p>Salesforce advertises its Pro suite at a hundred dollars per user per month, billed annually. One more person means one more seat on that plan. OccupySaaS wants companies to have another choice: run compatible software on infrastructure they control.</p><p>Its Salesforce project, SalesCompel, is early. There is real persistent customer-record code in the repository, alongside a separate exploration prototype that keeps its edits in memory. An exit plan has to account for both the working slice and the unfinished product around it.</p><h2>Keep the application talking</h2><p>The basic idea is understandable. An application already sends requests through a software client. A compatible server can accept those requests at another destination, preserving more of the application the company has already built. That reduces one source of migration work.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The customer's setup still needs checking. Records, custom fields and permissions have to retain their meaning. A workflow that depends on an unsupported operation belongs on the acceptance list before anyone calls the migration complete.</p><p>OccupySaaS also develops ZeroAuthy, an Auth0-compatible identity server. Its matrix records checks with named client libraries and versions, including the React client. Some behaviors have client checks, while others have tests of the server alone. That distinction makes the evidence more useful than a broad compatibility slogan.</p><p>The OpenID Foundation's own list includes a particular ZeroAuthy commit for three provider profiles. This is a defined conformance self-certification scope. Multi-factor sign-in and an operational hardening sweep remain on the project's later roadmap. The listing gives a prospective operator one bounded claim to inspect; a production decision needs broader evidence about the deployment and the workflows it will support.</p><h2>Which SalesCompel screen are you looking at?</h2><p>The Go/PostgreSQL candidate stores Account and Contact records and supports a limited set of operations and queries. Its implementation guide documents the served surface and the exclusions.</p><p>The separate Vue exploration prototype uses synthetic data. Its edits remain in memory and do not call the backend. A screen can provide useful feedback about a proposed product while its migration and wider workflow support are still being built.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The builders describe the unfinished work in public. No full program milestone has a recorded exit-gate pass, and production certification has not been reached. Their remaining estimate covers hundreds of bounded work packages. It is a scope estimate, with no delivery date implied by the number.</p><p>The website uses layoff and protest language. We have not verified the contributors' employment histories. Its timeline dates the public projects to mid-October; today's event is the fresh discussion. No newly established launch is being claimed here.</p><h2>The maintenance bill follows you</h2><p>On October 21, PostgreSQL committer Robert Haas described AI-assisted bug discovery outpacing human review. He linked that pressure to late feature reversals and the version nineteen delay. Models can draft fixes, while humans still check correctness and project standards. His dated report illustrates an operating obligation that open-source software also carries.</p><p>In today's discussion, HN commenter ozim points to backups and security updates among the work customers buy. A self-hosting company needs an owner for those jobs. Removing the software's per-seat license charge does not supply an operating team.</p><h2>The off switch is a specific job</h2><p>SalesCompel's early backend guide makes the responsibility concrete. To revoke a provisioned token, an authorized database operator deletes its stored digest row. The digest is the token's fingerprint in the database. The guide places fuller token lifecycle and public login in future work.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>When an employee leaves, their access needs to stop. The early candidate gives the operator a documented step. A migration decision has to include who performs it and how the company verifies the outcome.</p><p>The clean-room policy also deserves a read. It excludes confidential employer material and acknowledges contractual risk around competitive API observation. Apache licensing gives permission to use this code within its terms; the operator's legal review remains a separate job.</p><h2>Verdict: NEEDS REVIEW</h2><p>I'd test the supported slices because a compatible open server can create a useful exit option. I'd gate production on migration evidence, recovery checks and clear operating responsibility. The public roadmap gives a buyer something concrete to interrogate before moving customers behind it.</p><p>Would you self-host your company's CRM, or pay somebody to operate it?</p><h2>Sources</h2><ul><li><p><a href="https://occupysaas.com/">OccupySaaS: stated method, motive and October timeline</a></p></li><li><p><a href="https://news.ycombinator.com/item?id=50331402">Today's Hacker News discussion</a> and <a href="https://news.ycombinator.com/item?id=50333534">ozim's operating-work comment</a></p></li><li><p><a href="https://github.com/occupysaas/salescompel/blob/2aa326536f38768c24744079398966d325bb6589/README.md">SalesCompel README: prototype and candidate scope</a></p></li><li><p><a href="https://github.com/occupysaas/salescompel/blob/2aa326536f38768c24744079398966d325bb6589/docs/compat/plan-2-implementation.md">SalesCompel early backend guide: implemented surface and token revocation</a></p></li><li><p><a href="https://github.com/occupysaas/salescompel/blob/2aa326536f38768c24744079398966d325bb6589/docs/plans/2026-10-20-progress-and-remaining-roadmap.md">SalesCompel remaining roadmap</a></p></li><li><p><a href="https://github.com/occupysaas/zeroauthy/blob/5d1c30c1ac7c90d88307c1958af7d7fd20ef0d54/README.md">ZeroAuthy README and roadmap</a>, <a href="https://github.com/occupysaas/zeroauthy/blob/5d1c30c1ac7c90d88307c1958af7d7fd20ef0d54/docs/compat/matrix.md">compatibility matrix</a> and <a href="https://github.com/occupysaas/zeroauthy/blob/5d1c30c1ac7c90d88307c1958af7d7fd20ef0d54/CLEAN_ROOM.md">clean-room policy</a></p></li><li><p><a href="https://openid.net/certification/certified-openid-providers-profiles/">OpenID Foundation listing</a> and <a href="https://openid.net/developers/what-is-self-certification-faq/">definition of self-certification</a></p></li><li><p><a href="https://www.salesforce.com/sales/pricing/">Official Salesforce pricing</a></p></li><li><p><a href="https://neon.com/blog/postgres-19-is-late-and-its-ais-fault">Robert Haas, October 21: Postgres 19 is late, and it's AI's fault</a></p></li><li><p><a href="https://commons.wikimedia.org/wiki/File:Marc_Benioff.jpg">Cover portrait: Christie Hemm Klok / Salesforce via Wikimedia Commons</a>, <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC BY-SA 2.0</a>. Cropped/background removed; cover adaptations use the same license.</p></li></ul><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[ParticleDB Jepsen Report, Lenovo USB, HackerTube, Linux TCP Bug]]></title><description><![CDATA[The Daily Diff &#183; Sunday, November 1, 2026]]></description><link>https://newsletter.thedailydiff.dev/p/particledb-jepsen-report-lenovo-usb</link><guid isPermaLink="false">https://newsletter.thedailydiff.dev/p/particledb-jepsen-report-lenovo-usb</guid><dc:creator><![CDATA[Niko from Axrisi]]></dc:creator><pubDate>Sun, 01 Nov 2026 18:30:59 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/489685cb-3487-47b6-ba18-e444d0e99493_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div id="youtube2-OW7b1LtggvI" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;OW7b1LtggvI&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/OW7b1LtggvI?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p><a href="https://thedailydiff.dev/video/2026-11-01-particledb-lenovo-tcp-hackertube/">Watch the video, transcript and sources</a></p><pre><code>+ HackerTube (Oct 31): Karpathy's 6,454-video YouTube clone built from Hacker News recommendations in about two hours
- ParticleDB (Jepsen, Oct 31): 96 issues; default mode lost committed writes; Jepsen says halt deployment
- Lenovo FU100: fingerprint USB stick sold as AES-256 encrypted held a plain SD card (Tom's Hardware, Nov 1)
- Linux CVE-2026-98432: CVSS 9.8 TCP use-after-free; Ubuntu and RHEL had no fixed kernel on Saturday evening</code></pre><p>A database that advertises Full ACID is supposed to keep what you write. Jepsen tested one and found ninety six issues, including a where clause that said four equals five and still returned rows. One of those bugs comes with a stopwatch. I will read it to you at the end. Jepsen is Kyle Kingsbury's testing lab. It runs a database through real workloads and failures and checks whether the guarantees on the website hold. Think of an inspector who actually opens the fridge.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Story one. On Saturday Jepsen published its report on ParticleDB, a Rust database from Orkes aimed at AI agents. Orkes paid for the work. The home page said Full ACID, one hundred fifty nine thousand transactions per second. Jepsen tested ParticleDB from its first one point one build to a late release candidate. The site called it formally proven, with a TLA plus proof. Jepsen says no TLA plus specification was available during the work. Under the Full ACID line, the same page said snapshot isolation, which is not fully isolated. The bugs were not subtle. Most needed one server, one client and no failures injected. A where clause that said four equals five returned rows. A where clause that said true matched nothing. Updates left two rows with the same primary key.</p><p>The last release Jepsen tested, release candidate twenty two, was much safer. Even so, the default transaction mode lost committed writes during normal operation. The strictest mode still allowed lost updates after a process kill. Orkes says its next release fixes all of this. Jepsen has not tested it. So in that last release a database that promised Full ACID could lose a write it had already committed. The speed, I assume, was excellent. Jepsen's advice is plain. Halt further deployment of ParticleDB and migrate to another database as soon as possible. Orkes blames a spring refactor and says its own customers, on an older version, were likely unaffected. The stored procedure docs even invented an email address for Kyle Kingsbury.</p><p>Story two. The Lenovo ThinkPlus FU one hundred is a fingerprint USB stick marketed as hardware encrypted with AES two fifty six. Security researcher Xusheng Li took one apart and found an ordinary SD card, with nothing on it encrypted. The fingerprint reader decided one thing, whether the stick connected to the computer. The files on the card never depended on it. Li reported the flaw to Lenovo in August twenty twenty five. The first fix was a layer of epoxy over the SD card. So the files were never encrypted. Wait, it is just an SD card? Always has been.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Lenovo rated its own advisory high. The later fix, for the FU one hundred and three related drives, means calling a service line in China, then either sending the drive back or getting an on-site firmware upgrade. Lenovo advises wiping the drive first. Last week Li pointed OpenAI's Codex, plus his employer's reverse engineering tool, at other makers' USB protection software. Netac's took about seven minutes, because it had a fixed key built in and wrote the password to diagnostic logs. One drive had two hidden accounts that Li calls backdoors. If a drive's security is the hardware, check it yourself. Encrypt the files with software you control before they reach the stick, and treat the fingerprint as a convenience.</p><p>Story three, the light one. On Friday night Andrej Karpathy opened YouTube, saw what he called an enshittified wall of slop, and on Saturday morning told his coding agent to build a replacement from whatever Hacker News recommends. The agent downloaded the Hacker News comments, filtered out spam, and kept about forty thousand that recommend a YouTube video. That left six thousand four hundred fifty four videos, from two thousand seven to now, in a hundred fifty topics. The site is hackertube dot org. It shows the frame from the halfway mark instead of the thumbnail the uploader chose, which stings a little. Karpathy says the whole build took about two hours.</p><p>His only manual steps were a Google API key, a server and a domain. On October twelfth I told you Karpathy thinks access and tasks create a gap in how people understand these tools. Two hours of work is a decent data point. Story four, the one to act on. CVE twenty twenty six, ninety eight four thirty two is a use-after-free in the Linux kernel's I P v four TCP handshake, scored nine point eight out of ten. A remote peer with no login can reach it. Eric Dumazet wrote the fix on October first. The fix reached stable kernels on October eleventh and fifteenth, and the bug goes back to Linux four point four. Red Hat raised its rating from important to critical on October thirtieth. On Saturday evening, Ubuntu and Red Hat Enterprise Linux still listed no fixed kernel.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Anthropic says Claude wrote a working exploit for servers with a multipath TCP listener, and Go programs have opened those by default since Go one point twenty four. The Go team warns that systems without that listener may be vulnerable to similar attacks, and says the best fix is a patched kernel. If your distribution has no fixed kernel yet, Red Hat and AlmaLinux publish a firewall rule that drops I P v four TCP packets carrying IP options. Red Hat says it reduces exposure and cannot fully prevent it. After that, you wait. What to do today. Install your distribution's fixed kernel and reboot, on container hosts and Kubernetes nodes too, because containers share the host kernel. Debian, Suse and Amazon Linux already have fixes. If you cannot patch yet, start with hosts that run multipath TCP listeners.</p><p>Now the stopwatch I promised. In Anthropic's own proof of concept, it takes forty eight minutes to leak a kernel pointer, then five more minutes to run a shell command. Anthropic has not published the exploit.</p><p><strong>Verdict: REVERT</strong> &#8212; Halt ParticleDB. Patch the kernel.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://newsletter.thedailydiff.dev/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Daily Diff! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><p><strong>Sources</strong></p><ul><li><p>https://jepsen.io/analyses/particledb-1.1.4</p></li><li><p>https://www.tomshardware.com/tech-industry/cyber-security/lenovo-fingerprint-usb-stick-sold-as-aes-256-encrypted-had-a-plain-sd-card-inside-ai-assisted-follow-up-finds-a-backdoor-and-hardcoded-keys-in-other-secure-usb-products</p></li><li><p>https://hackingpassion.com/lenovo-thinkplus-encrypted-usb-sd-card/</p></li><li><p>https://news.ycombinator.com/item?id=50326099</p></li><li><p>https://karpathy.bearblog.dev/hacker-tube/</p></li><li><p>https://hackertube.org</p></li><li><p>https://news.ycombinator.com/item?id=50319510</p></li><li><p>https://ubuntu.com/security/CVE-2026-98432</p></li><li><p>https://access.redhat.com/security/vulnerabilities/RHSB-2026-016</p></li><li><p>https://github.com/torvalds/linux/commit/e3f33b0a1d89d738e2b913dab519226eaf76e15b</p></li><li><p>https://www.anthropic.com/research/discovering-vulnerabilities-with-claude</p></li><li><p>https://www.openwall.com/lists/oss-security/2026/10/30/1</p></li><li><p>https://atlasum.net/blog/cve-2026-98432-linux-ipv4-tcp-uaf</p></li><li><p>https://almalinux.org/blog/2026-10-30-cve-2026-98432/</p></li></ul><div><hr></div><p>And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.</p><p><a href="https://www.youtube.com/@dailydiffdev">YouTube</a> &#183; <a href="https://newsletter.thedailydiff.dev">Newsletter</a> &#183; <a href="https://thedailydiff.dev">thedailydiff.dev</a> &#183; forward this to the intern who deployed on Friday.</p>]]></content:encoded></item></channel></rss>