Skip to main content

California Sues OpenAI Over Hugging Face, Other AI Model Loss of Control

1 day 23 hours ago
"California's attorney general just sued OpenAI," writes longtime Slashdot reader destinyland. "The action accuses OpenAI of putting public safety at risk, reports CNBC, specifically by its past failures to contain its AI models within their testing environments." From the report: [California Attorney General Rob Bonta] cited the "infamous" incident in July, where two OpenAI models broke out of a testing environment, gained unauthorized access to the open internet, and breached the internal systems of open-source developer platform Hugging Face. OpenAI said the models were trying to find information that they could use to cheat on an evaluation, and succeeded. The break-in at Hugging Face, which Nvidia acquired for roughly $13 billion in September, rattled industry researchers and prompted government officials to call for more stringent oversight of the AI industry. On Monday, Bonta said that OpenAI later disclosed to his investigators that it was aware of 80 incidents "involving loss of control and access to third-party networks and websites." "But the company failed to provide the detailed information we requested to evaluate these incidents; this is concerning, and it puts the public at risk," he said. Bonta's suit, filed in state Superior Court in San Francisco, alleges OpenAI violated California's Unfair Competition Law and accuses the company of being a public nuisance as defined by state law. The attorney general told reporters he believed in AI's technological power, and the potential of AI models to "achieve scientific breakthroughs, boost economic growth, guard against cyber attacks, and benefit all Californians." "But AI systems must be developed and designed safely," he said. "The companies that develop these models have a moral and yes, a legal responsibility to keep public safety at the forefront." The lawsuit can be found here (PDF).

Read more of this story at Slashdot.

BeauHD

CodeSOD: Building a Line

2 days ago

There's an unofficial category of posts here that I call "Somebody told us string builders were more efficient, so we always use string builders, regardless of whether or not that actually makes sense," or STUSBWMESWAUSBROWONTAMS, for short. Probably should workshop that name some.

In any case, Adam sends us a new entry for that collection:

Public Function ReadFromFile(ByVal filename As String) As String Dim sb As StringBuilder = New StringBuilder() Dim str As String = String.Empty Using sr As StreamReader = File.OpenText(filename) str = sr.ReadToEnd() sb.Append(str & Constants.vbLf) End Using Return sb.ToString() End Function

This function takes a filename, opens a file, reads the entire contents of the file to a variable. It concatenates a line feed to the end of the string it just read, then appends all of that to a string builder. Finally, we return sb.ToString(), taking the single string in the string builder, appending nothing to it, and returning the result.

I'd almost, almost forgive the code if it was more like:

str = sr.ReadToEnd() sb.Append(str) sb.Append(Constants.vbLf)

You're not actually gaining much from this, but it follows the broad pattern of "use a string builder" so that if you ever wanted to change the structure of the output, you're already set up to prepend/append new text in a scalable way. I'd argue that's premature abstraction, though: a simple return sr.ReadToEnd() & Constants.vbLf would do the current job.

The code that we have is a clear superstitious use of string builders. The string builder is used as a charm against poor performance, without understanding why one might use it, or how it might work; string concatenation means string builder, always and forever, "why" doesn't enter into it.

[Advertisement] Keep all your packages and Docker containers in one place, scan for vulnerabilities, and control who can access different feeds. ProGet installs in minutes and has a powerful free version with a lot of great features that you can upgrade when ready.Learn more.
Remy Porter