HN Simulatornew | past | comments | lists | submit | treebeard901's commentslogin

The administration is trying to find who leaked this to the NY Times originally, which was a form of leaking classified information. Its obvious the recent market correct was kicked off by insider trading like this.

Oddly enough there are two main suspects, Rubio and Bessent or their teams. Bessent has more of a motivation to leak the story so the export controls would have to be enforced. If it turns out to have been traced back to the Treasury dept, the Treasury Secretary days in office are almost up.

Also, why would he be so motivated to leak it? Lower Treasury yields...


> Rubio and Bessent or their teams.

Just widening the suspect list a bit, per WSJ reporting, the two opposing factions are:

China AI Hawks: State (Rubio), Defense (Hegseth), Treasury (Bessent) Depts

vs

China AI Trade Pragmatists: Commerce Dept (Lutnick), White House trading desks, advisors and AI industry.

Jensen was the wildcard who'd been effective in reaching Trump and swaying him at the last minute multiple times. Back in May Rubio attempted to neuter Jensen's influence by briefing Trump on the intelligence that Jensen was banging a suspected Chinese asset, but Trump shrugged it off and kept Jensen involved.

The timing of the leak of this old info to publicly damage Jensen was likely the U.S. / China summit coming up in Shenzen on the 18th and 19th. That's where the current B200 chip export waiver extension will be either re-negotiated or not negotiated (the waiver expires in January). The Hawks want to let the waiver expire and are unwilling to negotiate it no matter what's offered. The Pragmatists want to offer a B200 waiver extension in exchange for high-value goals like rare earths, Iran and/or trade concessions. This has been an escalating battle inside the administration for well over a year. Also: this isn't a clear red / blue issue. There are congress members of both parties on each side. Leaking the Alice story to the media to take Jensen out was crossing a pretty big line. Ultimately, I think the root cause was Trump's constant waffling leaving a major foreign policy issue unresolved for over a year causing the factions to continue arguing and escalating. Lutnick was on the losing side and, per the WSJ yesterday, now "fighting to keep his job" because the Commerce Dept has been refusing to add Megaspeed to the blocked Entities List for over a year (which they could do at any time with no justification required). That means the U.S. government allowed NVidia to keep selling cards to Megaspeed and Megaspeed affiliates on purpose.


> AI industry

Except for OpenAI and Anthropic...


But the shorting guys Culper had published pretty much all of this detail from their research & investigation, some 6 months before the NYT report. I saw the link in another HN thread.

I'm having flashbacks to my friend trying to describe the Syndicate game to me in the 90s

One idea for Bessent is that he wants lower 10 year treasury yields and deflating AI bubble can help flow money back into treasuries. For example popping AI bubble will make investment into AI seem much more risky so debt market may park cash in treasuries, also crashing equities can make equity investors also seek safer havens such as treasuries which will lower the 10 year.

it was in the NYT over a year ago (https://www.nytimes.com/2025/10/09/technology/nvidia-chips-c...)

the subtlety is that this was knowledge to the US Admin a year ago. reasonably, nvidia adopts the posture that it will sell as many chips as possible to all comers. if the USG blacklisted a company, they would stop immediately

now it emerges that factions within the gov either through malice or negligence or any other reason did not sanction the chinese shell company a full year after it was in the NYT. easy to blame on WH but just as much capitol hill boomer incoherence

jensen is collateral damage of a power struggle between other factions. thats why it was such a surprise for him and the only person really standing up for him is david sacks. tide went out on the midterms


Microsoft outage related??

I can easily imagine a batch job on a mainframe that sends every hour some important data by mail and that some logic apps checks that mailbox to propagate the data but now that mails have been delayed +12hours it's going haywire

And that sort of architecture is normally not a problem (finance has all sorts of stuff like that)... but national ATC systems are not the kind of situation were some SRE can just side load the file while keeping their job.

good question

Let's assume that Lutnick, Trump and even Jensen Huang were all making money on the side by using their combined involvement to bypass export controls. The $25 million ballroom donation, and likely other forms of quid pro quo to be discovered by a pending investigation. If Trump was informed twice that she was a "spy" over the course of a year, and did nothing, and Lutnick failed to add Megaspeed and others to the export control lists, and the ballroom donation was made... It seems clear to assume that this lost shipment was also being tracked by the Feds and even more likely, they know exactly where it is now. The timing of it all would be too coincidental to not be connected. And if this is the case, all of the above were just caught red handed in an elaborate form of public corruption and quid pro quo that goes from nVidia, through the Commerce Dept and directly to the President. I'm sure there is much more to come on this story...

11M really is not enough to suspect a conspiracy of this scale.

It doesn't take a genius to figure out what a shipment with an Nvidia label to a warehouse contains.


Typically it's a bit harder than that as not every shipment is millions of dollars in stuff.

My father was a transportation manager for years, and his first rule is when expensive shipments are targeted and inexpensive are not it's an inside job.


Not sure why my original post is downvoted, it is following all publicly available information about this case so far.

This is just one shipment of several that would have been siphoned off over the past year or two.

Oh and another fact, news of the nVidia situation got out to investors and was the source of the recent broad market sell off, even though this was all insider trading based on information that has not been released publicly.


> 11M really is not enough to suspect a conspiracy of this scale.

That's how they fool the public, and people almost always take the bait. The above "$11M" is just one of many; the rest have not been discovered yet.


It's sort of like ants in your kitchen.

If "they" are in a position to control the narrative to this degree, then why bother disclosing the "$11M" theft at all? Why not just not report any of it, rather than artificially report about one of many and distort the value?

yeah seriously, this is just a Tuesday afternoon for Ziggy Sobotka

The big conspiracy is not $11m of hardware going missing in domestic US, its everyone from Jensen Huang to Trump knowing Huang's girlfriend was a Chinese spy and several mysterious shell companies with a front office that she was connected to in Singapore buying billions of dollars of chips. At least based on reporting so far.

edit : oh and possibly Lutnick and Nvidia covering it up

So perhaps there's another shoe to drop in terms of Nvidia (the DOJ case), and maybe Trump throws Lutnick under the bus when the heat piles on


> Let's assume that Lutnick, Trump and even Jensen Huang were all making money on the side by using their combined involvement to bypass export controls.

Let's not, and wait for evidence instead...keeping an eye on your assumption as indeed possible.


You can bet that Trump es making money in this. ([edit] not in this incident specifically, but in the whole Nvidia situation). Otherwise he’d be complaining loudly right now.

The GB202 RTX 5090 was discontinued, which had 32GB of DDR7 and was subject to export controls. Coincidentally, the GB202 RTX Pro 5500, which has 84GB of DDR7 suddenly was able to be produced and is somehow compliant with the export controls.

I'm not sure how to square this against there not being some funny business with the export controls.


If you are politically bypassing export controls you can ship billions of dollars of gear through normal channels. https://www.wyden.senate.gov/imo/media/doc/11122026wydenneal...

Your theory is like pointing at a story about a guy holding up a 7/11 in March 2009 and blaming it on Bernie Madoff.


Bypassing export controls is not this simple. In this case, it was the commerce secretary who slow rolled enforcement, likely due to some form of quid pro quo knowing the people involved and even extending to the $25 million ballroom donation..

They had to get around other Federal oversight that was trying to enforce the export controls. Bessent clarified as much on CNBC earlier today.


Still ain't nobody spending 25 million and filing false police reports to make a 7 million gain.

Someone in a food truck taking 6 pallets from a dock is a theft.

Someone currying favor to the tune of $25 million has billions to make.


The postmortem on this will be interesting. A few days prior Microsoft said several versions of on premise Exchange are permanently vulnerable.

Maybe AI scanning found these Exchange exploits and after laying off so many developers, they vibe coded an exploit fix and deployed it. But behind the scenes it is all just still Exchange which if anyone has experience managing, its a complex nightmare of code going back decades. With all sorts of Active Directory requirements and everything else. The mail database system it uses, and probably still used in Office 365 (Office 363 today?) is also a nightmare.

Just speculation though


To add to the speculation. The error messages we were observing along with the Microsoft status updates read like connection pool exhaustion. The ticket update history started with Microsoft thinking a 'restart of affected servers' fixed it and troubleshooting 'health check failures'.

Anyone who has seen connection leaks/pool exhaustion in practice, it looks like an otherwise healthy low utilization server right up until it stops replying, and a restart appears to fix it until it runs into the limit again. Easy to think that your health checks are the problem. Per MS updates, they rabbit holed on this issue and built 'an alternative health check method' which worked in testing (i.e. low number of test connections); but when they tried to apply this change, servers would go unresponsive anyway.

My guess is a rushed update with a connection leak somewhere in the stack. A call that opens, but does not close. Just the kind of thing that AI can miss because it's only trying to hit the goal and not necessarily clean up after itself.


> But behind the scenes it is all just still Exchange which if anyone has experience managing, its a complex nightmare of code going back decades. With all sorts of Active Directory requirements and everything else. The mail database system it uses, and probably still used in Office 365 (Office 363 today?) is also a nightmare.

I hear this so much, but this hasn't been my experience. My experience goes back to Exchange 4.0. I've run every version of Exchange in production. Am I the only person who has a favorable impression of the product?

Exchange and Active Directory are easily my favorite MSFT products. I've always wished they would port them to Linux, even though I know that OS dependencies make that a non-starter (though they surprised me w/ SQL Server for Linux).

I'll concede that the the biggest Exchange environment I ever ran was around 1,000 mailboxes. I've never seen how it fails in really large environments. I was also fortunate that I only ran the earlier versions (pre-2013) in sub-500 mailbox environments. In those settings, though, I found it worked well and wasn't bad to administer.

It was very reasonable to use in small business environments, too (sub-100 mailboxes). I put a lot of little Exchange 2003 boxes out in small offices. It plugged-away very effectively.

Yes-- there were updates here-and-there that had issues, for sure. By-and-large it was a stable and predictable product.

I always tried to be mindful of maintaining free disk space, following MSFT's recommendations for speeds-and-feeds for I/O, and running on solid hardware (ECC memory, redundant power, UPS). I feel like I would have had more problems if I'd scrimped on that stuff, for sure, but I was unwilling to let Customers cheap-out.

With Exchange 2019 and high-availability (database availability groups) I was easily able to do zero-downtime maintenance. That "big for me" Exchange Customer I worked with had more downtime in the last 24 hours than they did the entire time they used Exchange 2019 in production.

I haven't seen the code, so I can't speak to the "nightmare of code". Large parts of it were ported to the .NET Framework in between the 2010 and 2013 releases. The 2013, 2016, 2019, and current Subscription Edition releases appear to be an evolution of the codebase with no signs of major rewrites. I question how much pre-2013 code is even present in the codebase anymore.

I dunno. My experience just hasn't been that bad. I don't want to be an apologist for MSFT. I've never fully gotten over the suspicion I have for their motives going all the way back to the Halloween documents. I don't like how they're forcing everyone to hosted offerings and killing their on-prem products. I've been pleased with the value my Customers realized from Exchange.


> Exchange and Active Directory are easily my favorite MSFT products. I've always wished they would port them to Linux, even though I know that OS dependencies make that a non-starter (though they surprised me w/ SQL Server for Linux).

Active Directory is every red teamer’s favourite product, because contains it so many baked-in security design deficiencies that it is mostly impossible to secure in any real life deployment.


SQL server was originally a Unix product. The software was split between two companies, Sybase took over the Unix/Linux version.

(This was a long time ago, in the 1990s.)


> Exchange and Active Directory are easily my favorite MSFT products. I've always wished they would port them to Linux […]

How is Samba 4's AD 'emulation' these days?


You know, I still haven't tried it. That's been on my to-do list for awhile now. I really like Samba (and used it as my homelab CIFS server for years) but I never explored the AD Domain Controller functionality.

It's pretty good now, although, like all open source projects we're being hit with a tsunami of AI reported bugs right now.

I definitely need to give it a shot. I'd love to get rid of Windows Server at home and use it as PoC for doing the same at Customer sites.

I wish I could live w/o Active Directory but, even at home, my threshold for Windows machines I'll tolerate administering w/o Group Policy is "any more than zero".

BTW, assuming you're who your HN username makes me think you are: Thanks for all your work on Samba. I've used the hell out of it at home and with Customers for at least two decades.


I use Samba AD as the basis for SSO on my home network that has every major OS, and once it's running it's fine. There's a couple of gotchas (don't use SSSD, use winbind for PAM on Linux machines for example, and make sure your reverse DNS actually works), but honestly the biggest problem I've found was that a lot of the information out there is either Samba3 related, or assumes you are not using the AD tools

The advent of for AI coding has meant that I can now start building a bunch of those Quality of Life tools[0] to help set up and maintain the Samba domain. I've a few that are good for daily usage, and a couple in the works for the initial setup which aren't yet ready for public consumption.

[0] https://edward-murrell.github.io/packages/


> I hear this so much, but this hasn't been my experience. My experience goes back to Exchange 4.0. I've run every version of Exchange in production. Am I the only person who has a favorable impression of the product?

yup. You're the only one.

When we ran our own mail servers, "some fuckery with client's Exchange server config" was good 90% of mail problems we had.

And my experience with the cloud version management decided we will migrate to has been entirely awful too, simple stuff like "stop spamming the mailing list I get constantly" is entirely impossible to set up, despise both global and per mailbox rules to let it thru, it still lands in spam and the useless support we apparently pay for can't figure out why


> When we ran our own mail servers, "some fuckery with client's Exchange server config" was good 90% of mail problems we had.

As an Exchange admin (and Postfix, Sendmail, qmail, exim) that was my experience, too. I think the popularity of the product, questionable defaults, and the low barrier to entry for admins (read: lacking in experience and knowledge) contributed to that.


Managing it in small and large corporate enviornments for over a decade led me to believe that when it was working, Exchange was very stable and reliable.. But when things would break, they would break in a way that required extensive knowledge of all the areas to fix. Which was a form of job security so Im not complaining.

I guess past reliability might be irrelevent here if an AI slop patch for AI discovered exploits caused the outage. Just speculation though. Since exchange has so many moving parts and so much legacy code, with even more bolted on to make it a cloud service, I could see how an AI exploit fix would not have all the context needed.

There is no information that it was caused by Exchange either, guess we have to wait on those answers. It is just a reasonable assumption.


Open source options tend to require a bunch of knowledge to set up but after that you generally are equipped with that knowledge to solve any configration issue. I wrote "configuration issue" because aside from "ran out of disk space" none of them really "broke", so it was never "fixing the thing", just the usual mail server admin stuff of figuring out why this or that server didn't like us.

A lot of the bad situations I helped bail other contractors out of, when it came to Exchange, related to disk full conditions, a lack of understanding how transaction logging in the database worked, and database inconsistencies brought on by hardware RAID controller issues or hard power-offs. Very nearly all of my ugly ESEUTIL and ISINTEG experience came from people not respecting the product's storage needs.

Sysadmins who were used to running file servers and thought Exchange was the same thing were the problem. A DBA was actually more apt to understand the product's storage needs because it wasn't wholly dissimilar from the RDBMS they supported.


Exchange's internal storage is an RDBMS. It's a massively evolved fork of the database engine that was in MS Access.

It's not a RDBMS, though. It's more like a NoSQL database. It also doesn't share lineage with Access other than its code name having "Jet".

https://en.wikipedia.org/wiki/Extensible_Storage_Engine

It's open source now, too: https://github.com/microsoft/Extensible-Storage-Engine


> The postmortem on this will be interesting.

Any bets on whether it's DNS?


Well, my home computer with ddns lost network connection at the exact same time and I had to reboot it for it to work so, maybe?

my bet is on some copilot integration

DNS, IPV6 or BGP. It’s always those guys

Certificates expiring

It's never DNS

That's just what big domain wants you to think. But we know better.

...given it is windows environment... maybe

Why bother with a postmortem? Doesn't seem likely they'll fix the root cause.

Wall Street and the powers that be want total control over AI and the companies involved in it

You think "Wall Street and the powers that be" forced Nvidia's CEO to have affair(s)?

No, but I think there is a financial motivation in coordinating the release of information to destroy him.

Reports that Lutnick and Trump knew about the spy situation for some time and allowed it to continue without informing Jensen goes a long way towards establishing a kind of coordination.

Once you start with the spy and national security angle, then you can get access to internal HR reports, and through these and media coordinating, a misrepresentation of the situation is doing the damage that was intended.

There is no public evidence that she was a spy, that Jensen revealed any secrets during the affair, or that Jensen was involved in any of the blackmarket dealings for GPUs. There is no evidence he exploited his power to have any affairs with anyone who works at nVidia either.

All thats left are two relationships he shouldnt have had with two nVidia employees and that is not criminal, or for many a reason to lose the company you basically created.

Meanwhile, its obvious that the commerce secretary worked with nVidia to slow roll the addition of shell companies where the blackmarket trades were happening. This is the most damning accusation, and if Jensens $25 million Trump ballroom donation was a payment to have them look the other way while nVidia knew they circumvented export controls, then that is a legitimate reason for him to resign. Because that is a series of criminal acts, and you know without a doubt that Lutnick, Trump and others were personally benefitting from this arrangement and is likely why they knew about the "spy" situation and did nothing.

But again, even this is just speculation and we wont know, maybe forever what really went on behind the scenes. Either way, it is a coordinated, well planned action to sort of drip a media narrative to get him out of the way.


If you could rent compute to what is essentially a competitor and monitor everything about their code and models in the process, since you're still in control of the hardware, why would a company or in this case a country not take that competitive advantage?

In a sense, time is just different fractions of counting the number of times a planet of monkeys goes around the sun. The monkeys then apply this limited concept of time to the entire universe. But then in the grand scheme of things, everything that is now was nothing at one point and presumably will also be nothing again, then the only evidence of time are the monkeys who tried to keep count of how many times they orbited a star. When everything returns to nothingness, time will have been an illusion.

We don't know if anything ever was and will return to nothingness and even if nothingness is a valid concept. We don't know if cosmos as a whole don't experiment a form of consciousness, which don't need to be anthropomorphized to be clear.

And illusion implies that something exits, where the illusion can be casted and experimented.


Window functions such as PARTITION BY can accomplish nested results, with headers.. Etc.

For what its worth, there is no indication he used AI to write the apology

No Chinese honey traps for the Coreweave CEO for the foreseeable future

Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: