Rachel retweeted
The Y2K bug and the hole in the ozone layer were both serious problems that we chose to fix. It took a lot of work!
Rachel retweeted
Lots of people are asking me where to give their money - if you can only do one race, I’d give what you can to @MaryPeltola
Several reasons:
1) It’s a small state, so your money goes further per expected senate vote
2) Direct donations buy 19x ads per dollar than committees due to the unit rule - this also frees up the DSCC and SMP to put their money on states with smaller IE/coord ad price spreads and frees them up to spend more on digital
3) it’s likely going to be close!
It’s not too late! Any money you send today will get spent immediately and will provide real relief to an overworked campaign workers across a bunch of orgs!
secure.actblue.com/donate/mp…
Rachel retweeted
Steven Pinker is correct that these extreme warnings coming from the lab leaders while they race ahead is discordant and confusing.
But I am literally chuckling at the recent line i've seen from a few folks (not just Pinker) that "RSI leading to permanent irrevocable loss of control is a smokescreen to avoid scrutiny on real issues like AI enabled bioterrorism and rogue AI swarms shutting down the internet."
Fun to imagine showing this clip to myself in 2022, when a frequent argument was that talking about catastrophic cyber or bio risk was speculative sci fi and a distraction from real issues.
One night at Progress Conference while sitting around a fire I said Nvidia making the H20 to skirt export controls was traitorous. This kinda killed the convo and someone turned to the person next to them and was like, ‘Soo, what do you do?’ And they were like ‘I work at Nvidia’
I noticed when I have too many tasks, I find it hard to get started. I realized this may be because I like to start with the hardest task first. I’ve inverted it and tried doing the easiest tasks first and now get way less stuck. This uh seems incredibly obvious in retrospect.
Rachel retweeted
Based on this article, OpenAI has made false accusations about me. The three researchers fired from OpenAI were told I facilitated architecture leaks to The Information. This is false.
A journalist from The Information did reach out to me shortly before that article came out. I did not comment at all beyond asking the journalist to make it clear that a blog post I wrote which was referenced in the article was preexisting and public.
The article also mentions an internal OpenAI monitorability proposal. I have heard that this memo contained highly sensitive architecture information, and that OpenAI accused me of accessing and reading it. This accusation is also false.
As reported in the article, I viewed a version of the proposal that did not have sensitive IP and was approved for sharing with me. I believe OpenAI now knows this accusation was based on a conflation of these two documents, though I do not know if they have clearly retracted that accusation.
I do not and have never solicited proprietary information, and the three employees who were recently fired from OpenAI never leaked IP to me. As the article mentions, I did have Signal chats with them that had disappearing messages on; they’re professional contacts that I’ve had on Signal for a while, and use of Signal is common in the tech industry. During the Hugging Face investigation, I was careful to avoid sending Signal messages with confidential information, though I did sometimes discuss high level things on Signal calls. As far as I understood, this was normal.
New: The three researchers OpenAI fired last month spent the summer fighting to keep AI's chain-of-thought process visible.
Then, OpenAI asked to see their Signal chats. A week later, they were let go.
More below from @keachhagey, @berber_jin1, and me.
wsj.com/tech/ai/the-signal-c…
Rachel retweeted
Quest Diagnostics has been hacked. Patient data was exposed. They serve roughly half of U.S. hospitals and physicians. Investigation ongoing.
Rachel retweeted
Yes. note that there's also a third option, which is "if it's too dangerous for everyone to have it, it's too dangerous to train in the first place."
Everyone should be looking for data points to advance the longstanding debate in AI policy between “diffuse dual-use capabilities rapidly so the good guys can defend themselves” and “restrict capabilities proliferation to only carefully vetted good guys.” We are putting the former position to the test as we speak.
No motivated reasoning to reach your preferred conclusion; just pay attention and update as appropriate in whatever direction seems true. This is much too important for low-fidelity tribal polarization.
Rachel retweeted
quite the statement from Anthropic's head of security
Rachel retweeted
I think we should stop AI progress now, first unilaterally by key AI companies and then scaling up to more US companies and then China via international agreements. The reason for now is not that current AI models are the ones that could kill everyone, but because the coordinate steps take time. Immediate action means we have more time for the second steps.
When I tell this story to AI company folk, the typical response is "Yes pausing is good, but we should wait until the last minute when the very next model will be dangerous, and stop then."
What I realized recently is that this is being implicitly way more optimistic about government speed than I am (and I joined the UK government and was happy there for 2.5 years). They are imagining a world where, the moment the danger is imminent, a bunch of international coordination can happen on a dime.
Which is entirely inconsistent with their actual views about government! I'm the one that is more optimistic about government; why am I the one advocating for more time cushion to let the government story play out?
Rachel retweeted
Things are moving so fast that everyone seems to have completely missed how insane it is that AI companies have been allowed to unleash agentic AI products with no regulatory guidelines.
SCOOP: Major U.S. banks are detecting unauthorized third-party AI agents inside customer accounts, including some attempting to take actions that appear to be independent of user instructions, sources told Axios.
The findings have alarmed banking executives, who are racing to restrict access to their systems as AI moves at a velocity faster than financial institutions can respond, multiple industry and bank executives told Axios.
Several banks are now preparing for worst-case and even “day after” scenarios, including how to rapidly secure or restore customer accounts if things go wrong, the people said.
Several bank executives told Axios they're struggling to distinguish between human users and AI agents. One executive said banks also struggle to determine whether agents are authorized by customers or potentially operating without their permission, more akin to rogue agent behavior.
Read my latest for Axios here: axios.com/2026/10/22/ai-agen…
6-word horror story I experienced at the office today:
"Ajeya Cotra seminar cancelled, work emergency"
Rachel retweeted
These are some powerful parrots we're working with
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.


























