Urgent.News

What's breaking now, across thousands of outlets.

AI

“Don’t use ‘open weight’ and ‘open source’ interchangeably”: Percona CEO on why AI terminology matters

The AI industry has enthusiastically embraced the language of open source, even as some of its most prominent “open” models The post “Don’t use ‘open weight’ and ‘open source’ interchangeably”: Percona CEO on why AI terminology matters appeared first on The New Stack .

“Don’t use ‘open weight’ and ‘open source’ interchangeably”: Percona CEO on why AI terminology matters

The AI industry has embraced the language of open source, but some "open" models offer developers only limited access to what that term traditionally promised. At Open Source Summit Europe in Prague, Percona CEO Peter Farkas asked, "Don’t use ‘open weight’ and ‘open source’ interchangeably." Farkas explained that "open source" preserves the freedoms and openness behind it, while "open weights" only provide numerical parameters produced during training.

These weights allow developers to run models on their own infrastructure but do not offer the ability to trust, improve, or build upon the model. As open-weight models become more common in production AI, the distinction between open source and open weights is becoming increasingly important. "Open weights answer ‘can I run this?’

Open source answers ‘can I trust this, improve it, and build the next thing on top of it?’" Farkas argues that if companies start calling open weights as good as open source, they are "open washing" and weakening the definition of open source, which could have broader implications for software as well. The Open Source Initiative is currently re-evaluating its definition of open source AI to address these concerns.

Written by urgent.news from The New Stack's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at thenewstack.io →

More in AI

OpenAI API Rate Limit Errors (429): Which Ones to Retry and Which Ones to Stop

Originally published on the Djangix blog: OpenAI API Rate Limit Errors (429): Which Ones to Retry and Which Ones to Stop A 429 from the OpenAI API is not one problem — it is at least two very…

  • 429 status code indicates two issues: temporary overload or quota/billing limitations
  • Prevention strategies like caching, batching, and model selection reduce long-term rate limit errors

More from Friday 9 October →