Digest: Hacker News: Nov 12 - Nov 13, 2026
Published: 13 hours ago | Author: System
NVIDIA Announces CEO Transition
NVIDIA Announces CEO Transition
https://www.reuters.com/live/nvidia-live-board-meets-fate-ce...1590 points | 1660 comments
I hope people understand that the affairs are not the reason he is being fired - NVIDIA has supposedly been skirting the export ban put in place by the previous administration. This was put in place for national security reasons. Whether you agree or disagree with the ban, it exists and Jensen&NVIDIA are in a world of trouble if this comes to light.From all the reporting I've read, it is hard for me to avoid the conclusion that NVIDIA sold to China despite the export ban. I'd love to be wrong — duplessitous
Anthropic IPO
617 points | 625 comments
It strikes me that if their models were good enough for recursive self improvement, then the VCs would have pushed to delay IPO until such time that they had clear market dominance.For some reason they need the $100B today at the cost of dilution, rather than additional private rounds and/or using cashflow+profits to continue the advancement. — maerF0x0
Service degradation on Microsoft 365
Service degradation on Microsoft 365
https://www.abc.net.au/news/2026-11-13/microsoft-outage-affe...https://www.reddit.com/r/sysadmin/comments/1xuje83/microsoft...
https://downdetector.com/status/microsoft-365/
468 points | 438 comments
Copied this from my post in the other thread:The Status page is not working well, but I managed to subscribe to their RSS feed and it has been sending out updates periodically. I'll post some of them here.
9:02 PM UTC: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue.
Previous status: While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.
8:52 PM UTC: While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.
Previous Status: While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.
7:52 PM UTC: We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service.
7:30 PM UTC: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.
7:16 PM UTC: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've also moved traffic for some services off the affected infrastructure to further reduce load, with additional traffic moves in progress.
6:59 PM UTC: We've completed redistributing connection traffic across our worldwide infrastructure, and we're moving additional traffic off the affected infrastructure to further reduce load. We're also restarting affected servers to return them to service. In parallel, we're investigating whether the elevated traffic reflects a genuine increase in requests or a shift in how traffic is being routed across our infrastructure. — beowulfey
Rust 1.100
390 points | 163 comments
Woohoo, that's a release! My personal favorites:- Stabilize never type
- Stabilize custom allocators
- Introduced minimum publish age configurations, also known as dependency cooldowns. When the relevant config is set, the resolver ignores versions published more recently than that, unless they are already in Cargo.lock. (RFC 3923) docs #17335
- cargo-install: now uses the existing lockfile in the .crate tarball by default. --locked in cargo install becomes a no-op. #17388 — nirinor
Nvidia employees petition to bring back Jensen Huang
Nvidia employees petition to bring back Jensen Huang
493 points | 351 comments
> "We are all humans and can make mistakes. Jensen did so many good things and he needs a second chance,” wrote another.I think if it was one affair, this would hold. It is allegedly 3 and counting, and includes a likely spy from a rival nation, and likely knowledge of selling to the rival nation despite the current laws.
You can think he is amazing at many parts of this job, but at this point it is less of a mistake, and more a pattern of behavior that he knew was hugely risky and decided to cover up.
This is a terrible time for Nvidia employees. But the solution is not to invite the cause of the terrible time back in. — soundworlds
Show HN: My $300 embroidery machine needed a subscription, so I built my own app
Show HN: My $300 embroidery machine needed a subscription, so I built my own app
309 points | 129 comments
I'm going to assume Claude did the heavy lifting here (because it's Q4 2026 and the odds are in my favor), so if I'm right: this is one of the best examples of the way LLMs can empower users to not only scratch all the itches, but demonstrate to anyone who stumbles by just how satisfying it can be to do so themselves.Your app represents a future that I, an old, actually love. When I see projects like this, I don't think about ongoing support or if the project will be abandoned. I think, "Woah, I hadn't thought of that. Now I'm going to try it. Because why wouldn't I try to get all the value I can out of my $20/month Claude subscription?"
Even though I've been a developer for 30+ years (and a nerd for longer), I've never felt so motivated by the potential of a technology to make an individual's life richer. Thanks for sharing it.
And if you wrote it by hand, my hat's off to you for sharing that, too. — spdustin
Gemini 4 Hydrogen
452 points | 292 comments
This was rolled out RIGHT away, as when I just went to use Gemini, seeing 3.8 Flash be replaced with "4 Hydrogen" was less hype and more a thought along the line of "What [on Earth] is Gemini Hydrogen???", then me going here to figure it out.This model naming scheme works for separate products, but using elements, molecules, etc. for products you're supposed to compare with each other... Not very helpful.
If anything, my intuition would say that Hydrogen is more powerful than Argon... I don't know. Not liking this naming scheme trend. — wds
Gemini 4 Hydrogen and Orchestrator
Gemini 4 Hydrogen and Orchestrator
286 points | 64 comments
This is essentially what Anthropic does with the advisor mode and what GitHub does with their multi-model pipeline using the HydraFusion model, which is just a large set of different models with different qualities used in a pipeline to produce an answer.What I don't understand is how they all make it work with caching in general. Looking at how the advisor mode in claude work you seem to only be billed the output tokens and cache hit on the whole session when it calls out to the advisor, making it super cheap compared to running the more expensive model for the entire session. — vegardx
Ask HN: Microsoft/Azure Outage?
401 points | 1 comments
Comments moved to https://news.ycombinator.com/item?id=50471731. — tomhow
I'm making LLMs work on small and old devices
I'm making LLMs work on small and old devices
344 points | 127 comments
For the last five months or so, opus and fable have both been able to do this task as a soneshot prompt. An inference engine is almost pure compute and to a first approximation the only operation your hardware needs to support to do llm inference is multiplication [the rest of an inference engine is "some trig"].So to get any model working on $OLD_HARDWARE, the hardest part of the task is now sourcing the hardware itself and giving the agent ssh access -- a modern agent will be able to source a compiler, write the implementation, optimize it, test in qemu (or any other simulator) and push it onto the device.
Example prompt: "write an inference engine for qwen3 0.6b in pure assembly that runs on this device. Write a script to attach the weights to the resulting binary. Prefix is supplied as a stream of u32 token IDs on stdin. The engine streams u32 token IDs on stdout." — Farmadupe2