Yonhap reported yesterday that a planned visit to South Korea by Madison Huang, a senior director at Nvidia and the daughter of Jensen Huang, had been canceled. The trip was called off due to “family issues,” per the report.
Show more
*matt levine voice* everything is securities fraud
I think it’s underrated that even if the spy/natsec stuff isn’t a factor, Jensen appears to have had an affair with a major customer for months — which violated Nvidia’s own conflict of interest policy.
Did he disclose it to the board? If not, that seems like a resignable offense in and of itself
Show more
tbh it’s possible he was telling the truth and he sleeps with all his customers.
@sama please confirm
remember when OpenAI said it was going to ditch side projects and focus?
(Also a bit gross for OpenAI to be partnering with Palmer Luckey on merch)
It sounds like US officials have known about Jensen’s affair with a top customer since May, but the public (and Nvidia’s board!!!) only learned about it because of the excellent NYT reporting. Hugely impactful journalism.
Show more
Jensen was conducting an AI safety master plan all along.
1. Make the entire AI economy dependent on Nvidia’s stock price
2. Have an affair with a Chinese spy
3. Resign, tanking Nvidia’s stock price because you have no successor
4. The AI investment bubble implodes, slowing down the datacenter buildouts and lengthening timelines to AGI by a decade
thank you jensen I never should have doubted you
Show more
Ugh, yeah, sorry about this. METR makes a bunch of valid critiques but this is the one I feel worst about; I think not putting enough time into making sure the public version of the AI R&D section was as clear and transparent as possible was one of my biggest failures in the drafting process for this report.
The badness of this language is particularly rough due to a second issue, which is that the paragraph right below this one in the public report makes it sound like the question of whether leading indicator acceleration is above or below 2 is the primary factor determining RSP threshold determination - which it's not, RSP talks about 2x in aggregate capabilities. The private report doesn't make an RSP threshold claim solely on the basis of this number, and says it thinks that overall progress had *not* accelerated by that much (bc AECI analysis at the time didn't look faster), but the public wording makes it sound (incorrectly) like these leading indicators were the primary basis on which to make a threshold determination, which is particularly unfortunate given that the phrasing downplays the value of this number and doesn't caveat its uncertainty enough. METR's suggested language of "We are uncertain how these leading indicators relate to downstream capabilities" would have made this clearer.
To give some behind-the-scenes context on how the risk report sausage is made, here's my current best reconstruction of how it came to be that this paragraph ended up in the public report:
(1) Around July 1, a very early draft of some of the material for this section had a lower central estimate for this rate of progress, and it included the text "At our central estimate (~[redacted]×/yr), [redacted] progress falls short of a doubling", with some later caveats about ways that more aggressive estimates would imply a doubling in the rate of progress on this metric. I think it was still close enough to 2 that it should have explicitly given a number, but it was more reasonable wording imo.
(2) After updates to our data and methodology around the mid-July coverage date, we had a higher estimate that was quoted in the final report. The progress rate number was edited in place but the surrounding text wasn't; probably someone checked the number was less than 2x and didn't think hard about whether the surrounding language was tonally off.
(3) Our main focus was on drafting the private section to be as accurate and clear as we could; producing a redacted public version was a much later process. We had a few different drafts of possible public versions floating around depending on where we landed on decisions about what to redact. On August 6, someone sketched a doc with a possible public version that included the text "Our leading indicators point to a picture of meaningful acceleration starting in early 2025, but falling short of the “double the pace of progress” threshold", basically just removing the numbers from an earlier sentence in the private report. (That drafting was by a different person than the author of the earlier text, and they hadn't run the numbers to see this would imply a ratio very close to 2. If they had, probably this would have said "have nearly doubled" or something.)
(4) Very close to risk report publication, we decided on the version of the public draft which had the above language; I had previously left a comment on that draft noting that doubling the pace of progress was "not technically the v3.4 threshold, which is impossible to crisply refer to in a sentence of reasonable length", so I edited the final version to say "though by less than a factor of 2" so as not to misstate the RSP threshold. (And as mentioned above, RSP is about overall downstream capabilities anyway.) Anyway this language was accurate enough that Claude-powered factchecking didn't complain and it survived through publication from there. IIRC when making these edits I didn't go back to perform this calculation and wasn't tracking that the corresponding "less than 2" number was so close, although I had computed it at earlier points when working on the private report.
Anyway, apologies that the public risk report underemphasized the uncertainty around these leading indicator acceleration rates and wasn't sufficiently clear about their connection to the RSP; this was not anyone's intention, and I'm glad METR was able to catch this for the public. I will try to make sure the next one does better.
Show more
NEW: Nat Sec Adviser Marco Rubio oversaw drafting of a highly classified memo this spring that the intel community assessed a woman who had established a close relationship w Jensen Huang was working for China's Ministry of State Security
Show more
New contender for most useful thing Claude's done: Couldn't use Infuse video player inflight, because airplane wifi blocked the App Store, so Infuse couldn’t restore my Pro subscription.
Claude worked out exactly which Apple servers were blocked + tunneled just those through my Mac mini at home. Problem solved!
Show more
This has also been happening in London recently. Bleak! (Also isn’t the whole point of Blank St that it’s fast, there shouldn’t be lines!)
Situation is dire in DC… lines around the block for Blank Street coffee
METR are very measured here -- frankly, i think it's wilfully misleading to describe a 1.97x (!) acceleration rate, estimated with substantial uncertainty (METR think a reasonable estimate is between 1.3-2.8x (!!)) as "less than a factor of 2"
Show more
NEW on Transformer:
@Kirsten3531 set up the UK Government’s AI and Energy Directorate.
Now she warns that AI is going to run out of power, and the industry is not on track to fix that problem.
"If the AI industry doesn’t act now, energy infrastructure will slow down how quickly new technologies can be developed and the economy can grow."
Show more
Emil Michael RTing an article claiming OpenAI’s relationship with the government is damaged because the admin doesn’t like Dean Ball???
This neatly captures my own biggest criticism of AI 2040 (and 2027 before it)