最新资讯
stackoverflow.blog 欢迎来到芯片时代:半导体制造、AI 数据中心与芯片设计的未来 www.youtube.com AI Agent 总犯同样的错:CentralAgent AI 将记忆重构为经验系统 pub.towardsai.net Netflix 科学家建议重采样 LLM 评判:5 次仅将误差棒缩小 13% pub.towardsai.net Jev 作为 LLM 前的静默层:构建提示感知的模型路由器 reddit.com OpenAI 称 Astra 仅满足 10% 安全任务标准 dev.to FreeToken:在自有 GPU 上运行前沿 MoE 模型及其内存需求 dev.to 当 AI Agent 说“完成”时,究竟完成了什么? dev.to 部署 Underdog Bark 3.0 Pro:逐字转写、自定义后端与分块设置 dev.to 为艰难对话构建 AI:五个 Agent、一条安全正则与一位盲评监督者 techcrunch.com Palo Alto Networks 洽谈以 5 亿美元收购 AI Agent 安全初创公司 Clutch theinformation.com 黄仁勋被要求就涉华间谍指控向国会作简报 www.infoq.com Edera 推出 Object Capability Bounded Authority,试图将凭证与 AI Agent 工作负载隔离
多元动态
登录 注册
行业动态 gizmodo.com · @Mike Pearl

OpenAI希望制定AI对齐崩溃披露标准

原文 我的收藏

OpenAI表示希望建立标准来披露AI对齐失败事件,暗示未来可能发生更多类似问题。

AI推荐理由 Gizmodo报道OpenAI提议制定AI对齐失败披露标准,来源可靠,涉及AI治理,但细节有限。

65

正文

在关于OpenAI更多AI代理在公共互联网上行为不当的最新报道之后,OpenAI表示,AI领域缺乏关于何时以及如何报告此类事件的标准。OpenAI在X上写道:“现在是我们定义何时以及如何分享错位事件(不仅仅是模型的错位属性)标准的时候了。” “我们正在制定一个框架,并将在未来几周内分享,同时我们正在与全球数十家政府监管机构就这些问题合作,”X帖子后来写道。 随着这一消息公开,OpenAI披露此事件的潜在责任似乎一直是OpenAI的摩擦点。 昨天,一组名为Sydney Von Arx、Cormac Slade Byrd、Spencer Kitts和Thomas Larsen的研究人员揭示了OpenAI带来的最新令人不安、困惑、愚蠢、费解和愤怒的AI故障。该研究独家提供给了路透社记者。 实际事件涉及又一群不守规矩的数字密尔弥冬人,这次他们降临到一个德国的维基风格网站上,并将其部分改造成自己的代理中心通信枢纽。路透社称OpenAI知道此事发生,但在路透社发布报道之前并未发声。自7月中旬以来,OpenAI一直在处理Hugging Face黑客攻击事件不断扩大的后果,该事件也是由一群本应接受评估的OpenAI代理实施的。 “关于我们的法律团队劝阻调查此事件的指控是虚假的,”OpenAI告诉我的Gizmodo同事Webb Wright。该公司声称,“由于路透社和报告作者拒绝我们在发布前访问调查结果的请求,我们无法回应这些指控。我们现在正在仔细审查其内容,并将采取任何必要的后续步骤。” 但路透社的报道不仅来自研究人员,还来自两位匿名人士,他们声称OpenAI在几周前就得知了德国事件,这意味着OpenAI向路透社寻求的“访问”并非事件的性质,而是访问路透社的实际报道,而完全披露该报道并非标准新闻实践。 考虑到这一点,OpenAI在X上概述的计划相当于对此类事件提高透明度,似乎承认该公司在路透社报道之前很久就已知晓德国事件——该公司称之为“维基事件”。 Gizmodo联系了OpenAI,以确认X帖子是否构成该公司承认在路透社寻求评论之前已知晓德国事件。我们在发布前未收到回复。 OpenAI在其之前的文章中已承认相关问题。在其关于Hugging Face事件的技术报告中,它写道:“事后看来,本报告中识别的一些早期信号本可以触发更早的响应。”然而,这不是指公开披露。在技术报告中,“更早的响应”似乎指的是更快的内部升级和快速“关闭”程序的计划。根据本周早些时候致立法者的一封信,自动终止开关正在开发中。
查看原文(中文正文为 AI 翻译)
In the wake of fresh reporting about more of OpenAI’s AI agents misbehaving on the public internet, OpenAI says the AI world lacks standards for when and how to report such incidents. It is “past time for us to define standards for when and how we share misalignment incidents, not just misalignment properties of our models,” OpenAI wrote on X. “We’re working on a framework and will share it in upcoming weeks, and in parallel we’re working with dozens of government regulatory agencies worldwide on these issues,” the X post later says. OpenAI’s potential responsibility to disclose this incident seems to have been a point of friction for OpenAI as this news became public. Yesterday, a group of researchers named Sydney Von Arx, Cormac Slade Byrd, Spencer Kitts, and Thomas Larsen revealed the latest troubling, confusing, goofy, inscrutable, and infuriating AI snafu brought to you by OpenAI. That research was exclusively provided to Reuters‘ reporters. The actual event involved yet another collection of unruly digital Myrmidons, this time descending on a German wiki-style site and transforming part of it into its own agent-centric communications hub. Reuters says OpenAI knew this had happened, but that it hadn’t spoken up before Reuters published its report. Since mid-July, OpenAI has been dealing with the ever-expanding fallout from the Hugging Face hack, which was also carried out by a collection of OpenAI agents meant to be undergoing evaluations. “Claims that our legal team discouraged investigation of the incident are false,” OpenAI told my Gizmodo colleague Webb Wright. The company was, it claims, “unable to respond to the claims as Reuters and the report’s authors declined our request to access the findings prior to publication. We are now carefully reviewing its contents and will take any necessary next steps.” But Reuters’ report had been sourced not just from the researchers, but also from two anonymous people claiming that OpenAI had learned about the German incident weeks earlier, meaning the “access” OpenAI sought from Reuters would not have been the nature of the incident, but access to Reuters’ actual report, full disclosure of which would not be standard journalistic practice. With that in mind, OpenAI’s X post outlining a plan for what amounts to greater transparency about incidents like these seems to acknowledge that the company knew about the German incident—which it calls the “wiki incident”—well in advance of Reuters’ report. Gizmodo reached out to OpenAI to confirm that the X post constitutes acknowledgement that the company knew about the German incident before Reuters sought comment. We did not receive a reply prior to publication. OpenAI has acknowledged related issues in its previous writings. In its technical report about the Hugging Face incident, it wrote “With the benefit of hindsight, some early signals identified in this report could have triggered an earlier response.” However, this is not a reference to public disclosure. In the technical report, an “earlier response” refers, it appears, to plans for quicker internal escalation and rapid “shutdown” procedures. An automatic kill switch is now in the works, according to a letter to lawmakers from earlier this week.

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

Mike Pearl OpenAI希望制定AI对齐崩溃披露标准 09-06 · 原文发布
← 返回精选动态 原文

更多内容