最新资讯
dev.to Google 将 AI 搜索与传统搜索定位为统一产品 dev.to 三周 agentic 会话的教训:长时运行 agent 的流程设计 dev.to 用 Switch AI 在 Slack 中构建自主 Sev-1 SRE 集群 www.youtube.com Modal CTO:不要用 vibe coding 搭建 Agent 基础设施 dev.to 用自有 Claude 订阅将 Claude Code 作为 osFoundry Worker 运行 dev.to osFoundry 如何检测 Claude Code 停在权限确认提示等待响应 marktechpost.com 用 llama.cpp 运行 NVIDIA Dory 4B:逐循环实操指南 www.youtube.com OpenAI 团队实操:在 ChatGPT 内构建金融 Agent dev.to 2026年11月哪些厂商提供可租用的机密 GPU:基于各家官方页面的核对 dev.to 从答案到订单:AI 推荐经济的执行层图谱 bloomberg.com 欧洲反 AI 情绪蔓延,多地爆发数据中心抗议 pub.towardsai.net OpenSpec 教程(2026):在 Claude Code 中逐步实践规格驱动开发
多元动态
登录 注册
行业动态 x.com · @Sam Altman (@sama)

Sam Altman 回应 Navier-Stokes 事件争议

原文 我的收藏

Sam Altman 在 X 上详细回应 Navier-Stokes 问题解决争议,称团队曾希望合作发布,但对方团队拒绝沟通,并指责 OpenAI 抄袭。Altman 表示双方方法不同,并强调最新模型能解决许多其他数学问题。

AI推荐理由 Sam Altman 详细回应 Navier-Stokes 事件争议,澄清合作与发布过程,涉及与 Anthropic 的竞争关系,但缺乏技术细节,对 AI 研究价值有限。

65 浏览 3,674,301 点赞 10,745 评论 960 转发 602

正文

我花了周末大部分时间与做这项工作的团队交谈。塞巴——以及所有其他人——在整个过程中都表现出正直和慷慨。 最初我们相信另一个团队也解决了这个问题。我们想合作并联合发布。 当我们得知他们解决了欧拉方程但没有解决纳维-斯托克斯方程时,我们提出让他们先发布,建议他们应该获得奖项,并且可选地让特里斯坦成为重写OpenAI证明的牵头作者。我们觉得向莱文特(Anthropic员工)提出同样的建议很困难,他反正也不愿意与我们交谈或协调。我们对其他解决方案持开放态度。 我们非常希望协调。即使另一个团队不与我们沟通,我们也没有急于发布。那个团队用毫无根据的抄袭指控威胁我们。 现在我们可以看到他们的工作,方法似乎不同。还值得注意的是,我们最新的模型可以解决许多其他数学问题。 确实,我们尝试这个是因为上周互联网上有传言说Anthropic的模型解决了一个千禧年问题,我们好奇我们的模型是否也能做到。 塞巴斯蒂安·布贝克 @SebastienBubeck 我想澄清几点: 1) 截图是我联系莱文特协调我们的发布。希望从消息中能清楚看出我们带着最好的意图而来。 2) 我从未要求将莱文特从他自己工作的作者名单中移除(正如我的文字所示)。在与特里斯坦通话时,我惊讶地得知他们只解决了欧拉方程而没有解决纳维-斯托克斯方程;得知此事后,我们头脑风暴了可能的推进路径。我们讨论的一个选项是特里斯坦可以成为重写OpenAI纳维-斯托克斯证明的牵头作者。正是在那个背景下,我说“如果莱文特不是Anthropic员工会更简单”,因为我觉得让Anthropic员工撰写OpenAI的工作是不合适的。重要的是,他们承认内部Anthropic模型被用于他们的欧拉爆破解证明;因此我觉得不能将莱文特视为独立学者。我想提出的另一个选项(但被打断了)是提供我们内部模型的访问权限,以便他们能尝试完成证明并弥合欧拉和NS之间的差距。同样,我不知道如何向Anthropic员工提供OpenAI内部IP的访问权限。 3) 直白地重申:正如我的文字清楚表明的,也正如我在通话中所说,OpenAI的意图是尽一切可能庆祝他们的数学成就以及他们在欧拉方程上所做的英勇努力。在通话中,我立刻遭到一连串诽谤,包括直接威胁说如果我们宣布纳维-斯托克斯,他会立即带着一连串毫无根据的指控去找媒体。我反驳了所有这些指控,但他回答说“你无能为力,我就是不信任你”。我很困惑为什么有人会把一个令人难以置信的庆祝来源(庆祝他们的成就!)变成这样的争吵,这时我说我不明白为什么有人会冒着职业生涯的风险[去进行毫无根据的指控]。真诚地说,在那一刻,我试图关心他,并做最后一次尝试,以获得机会给予他们应得的所有荣誉。我为我这个极其糟糕的措辞深表歉意,这与我想传达的相反。(顺便说一句,我应该说我当场收回了这些话。) 4) 总的来说,在个人层面上,进行这些对话极其困难。莱文特拒绝参加任何会议,尽管我一再要求。正如肖尔托·道格拉斯所说,未来Anthropic和OpenAI之间需要协调;我觉得我在与Anthropic进行代理谈判,而Anthropic员工拒绝直接参与。 🔗 查看引用的推文
查看原文(中文正文为 AI 翻译)
I spent much of the weekend talking with the team who did this work. Seb--and everyone else--acted with integrity and generosity throughout. Initially we believed the other team had also solved the problem. We wanted to collaborate and do a joint release. When we learned that they had Euler but not Navier-Stokes, we offered to let them go first, to suggest that they should be the ones to get the prize, and optionally for Tristan to be the lead author on a rewrite of the OpenAI proof. We felt it was challenging to offer the same to Levent (an Anthropic employee), who was not willing to talk or coordinate with us anyway. We were open to other solutions. We would have greatly preferred coordination. We did not rush to publish even though the other team wasn't communicating with us. The team threatened us with unfounded accusations of plagarism. Now that we can see their work, the approaches appear to be different. It is also worth noting that our latest model can solve many, many other math problems. It is true that we tried this because there were rumors on the internet last week that Anthropic's models had solved a millennium problem and we were curious if ours could do it too. Sebastien Bubeck @SebastienBubeck I would like to clarify a few things: 1) The screenshot is my reaching out to Levent to coordinate our releases. I hope it’s clear from the message that we came in with the best possible intentions. 2) I never ever asked for Levent to be removed from authorship of his own work (as indicated by my text). I was surprised to learn during the call with Tristan that they had only solved Euler and not Navier-Stokes; after learning this we brainstormed possible paths forward. One option we discussed was that Tristan could be the lead author on a rewrite of OpenAI’s Navier-Stokes proof. It is in that context that I said “it would be simpler if Levent was not an Anthropic employee” because I felt it would be inappropriate for an Anthropic employee to author OpenAI’s work. Importantly it was admitted that internal Anthropic models had been used in their proof of Euler blowup; I therefore felt I could not consider Levent to be an independent academic. Another option I wanted to propose (but got cut short) is to offer access to our internal model so that they could try to finish their proof and bridge the gap between Euler and NS. Again I did not know how to navigate giving access to internal OpenAI IP to an Anthropic employee. 3) To reiterate it plainly: as my text clearly indicates, and as I said during our call, OpenAI's intention was to do everything possible to celebrate their mathematical achievements and the heroic efforts that they made on Euler. In the call I was immediately met with a litany of slander, including direct threats that if we were to announce Navier-Stokes he would immediately go to the press with a barrage of unfounded accusations. I refuted all these accusations but he replied “there is nothing you can do, I simply do not trust you”. I was confused why one would turn an incredible source for celebration (of their achievements!) into such bickering, which is when I said that I did not understand why one would risk their career [over unfounded accusations]. Genuinely, at that moment, I was trying to care for him and do a last ditch attempt to get a chance to give them all the credits that they deserve. I deeply apologize for this extremely poor choice of words, it is the opposite of what I was trying to convey. (I should say that I retracted them on the spot by the way.) 4) Overall, on a personal level, it was incredibly difficult to have these conversations. Levent refused to attend any of the meetings despite my repeated asking. As Sholto Douglas said, there will need to be coordination between Anthropic and OpenAI in the future; I felt I was doing a proxy negotiation with Anthropic while the Anthropic employee refused to directly participate. 🔗 View Quoted Tweet

来源报道 · 3 篇 · 以下链接均前往原始媒体

Sam Altman (@sama) Sam Altman 回应 Navier-Stokes 事件争议 09-09 · 原文发布
← 返回精选动态 原文

更多内容