Elon Musk’s only expert witness at the OpenAI trial fears an AGI arms race
Elon Musk's lawsuit against OpenAI centers on claims that the organization abandoned its original nonprofit mission focused on AI safety. His sole expert witness, Stuart Russell, testified about the dangers of AI and the risks of an AGI arms race, though his broader concerns were limited in court. The case highlights tensions between AI innovation, corporate interests, and safety, as both sides selectively use AI risk arguments for legal advantage.
- ▪Elon Musk is suing OpenAI, arguing it strayed from its nonprofit, safety-focused origins.
- ▪Stuart Russell, a UC Berkeley AI expert, was Musk's only expert witness and warned of AI risks including misalignment and an AGI arms race.
- ▪Russell's testimony was restricted by the judge after objections from OpenAI's legal team.
- ▪OpenAI's attorneys emphasized that Russell did not assess the company's specific safety policies or corporate structure.
- ▪Senator Bernie Sanders has cited AI safety concerns from figures like Musk and Sam Altman to support a proposed moratorium on data center construction.
Opening excerpt (first ~120 words) tap to expand
When do we take AI doomers seriously? That’s a key subtext of Elon Musk’s attempt to shut down OpenAI’s for-profit AI business. His attorneys argue that the organization was set up as a charity focused on AI safety, and lost its way in pursuit of lucre. To prove that, they cite old emails and statements from the organization’s founders about the need for a public-spirited counterweight to Google DeepMind. Today, they called their only expert witness: Stuart Russell, a University of California, Berkeley computer science professor who has studied AI for decades. His job was to offer background on AI, and establish that this technology is dangerous enough to worry about. Russell co-signed an open letter in March 2023 calling for a six-month pause in AI research.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at TechCrunch.
Discussion
0 commentsMore from TechCrunch
