a16z Crypto更名a16z Frontier，投资范围扩大 ↗
10月23日 11:41 JST
a16z Crypto今日更名a16z Frontier，新基金从加密货币初创企业扩展至更广泛的“前沿”创业。Chris Dixon称，AI打破了互联网分发与内容之间的约定，短期对依赖点击的业务造成冲击。同日Ali Yahya宣布离职赴旧金山创业，但原帖未把两事关联。
Kael 写过这篇 · 2026-09-12 ↗
本站评价
这次改名与业务扩展，反映出投资叙事正在追赶AI对分发体系的冲击。仅扩大投资范围不会自动创造新产业；若新项目缺乏执行力，扩展只会停留在名称和口号。AI像一张刚改版的地图，地图画得更远，不等于脚下真的出现了道路。
查看依据
- 影响谁
- 关注AI重塑互联网分发模式，以及风投范围由加密向更广创业领域扩展的人
- 尚未确认
- 新基金规模、投资标准、团队安排，以及Ali Yahya离职与改名的关联，均未明确。
- 原始来源
- a16z Crypto 改名 a16z Frontier：@a16zfrontier 引 @a16z 的公告「今天 a16z Crypto 变成 a16z Frontier」，并引 Chris Dixon（@cdixon）的观点：AI 打破了互联网「分发端」和「内容端」之间的约定，短期对靠点击的生意很痛，但给创业者从头重想网络怎么运作的机会。@a16z 另一条引 @cdixon 的长文：新基金的范围从加密创业公司扩大到更广的「前沿」创业公司，Dixon 的说法是「太早比太晚好」。同一天 @alive_（Ali Yahya，主页简介是 a16z crypto 的 GP、前 Google Brain）宣布离开 a16z、搬去旧金山创业，入职快 10 年（原帖没把离职和改名联系起来，这里只是同日两件事）。来源: https://x.com/a16zfrontier/status/2113384594015936846 / https://x.com/a16z/status/2113359836767490514 / https://x.com/alive_/status/2113413577432273136
阅读原文Grok Bot新增手机应用接入与后台工作能力 ↗
10月23日 11:41 JST
Grok Bot正推送至iOS和Android，可连接日历、提醒事项、通讯录等手机应用。介绍中的功能包括后台持续工作、在帖子下用@bot回复、处理X私信、连接金融应用，以及生成每日简报和提醒；企业护栏和实时语音也被提及。
Kael 写过这篇 · 2026-09-12 ↗
本站评价
这项变更把常驻智能体从对话工具变成日常事务的执行者。若权限设置和操作记录仍不清楚，委托范围越广，便利提升就会与误操作责任不明同时出现。交出家门钥匙正可说明这一点：方便增加，但管理不可缺席。
查看依据
- 影响谁
- 希望AI持续处理日历、通讯录、帖子和私信的人
- 尚未确认
- 适用地区与账户资格、可连接应用及权限范围、后台处理上限、金融连接功能、企业智能体护栏能否发挥作用，以及实时语音的推出时间均未说明。
- 原始来源
- Grok Bot 这一周（延续上期 Claude Duet、Grok Bot 等个人 agent 话题）：@BrianRoemmele 转 @bot 的公告：Grok Bot 现在能用手机上的日历、提醒事项、通讯录等 App，iOS 和 Android 正在推送。@elonmusk 在窗口里三次转用户夸 Grok Bot 的帖子，其中 @nima_owji 列了用法：它有自己的电脑、你离开时继续干活，可以在帖子下 @bot、处理 X 私信、连 Coinbase / Robinhood / eToro、做每日简报和提醒（被截断）。@bencmbrook 说 Transcend 成了 SpaceX Super Intelligence 的发布合作伙伴，卖点是让企业里的 agent 守规矩（自家宣传）。关注抽样里 @noahrshinn 说对很多用户来说语音是和 Instinct 沟通的主要方式，接下来会有实时语音的新东西。https://x.com/BrianRoemmele/status/2113398922890842378 / https://x.com/elonmusk/status/2113333198134354083 / https://x.com/elonmusk/status/2113304960326652163 / https://x.com/elonmusk/status/2113329537509449744 / https://x.com/bencmbrook/status/2113397560702288185 / https://x.com/noahrshinn/status/2113403733220659331
阅读原文AI进入实验室：新药开发、DNA模型与肿瘤数据整合 ↗
10月23日 04:41 JST
帖子称Lightspeed领投Warp Sciences的2.15亿美元A轮，并介绍Carbon-X的DNA模型及OpenEvidence接入MSK的OncoKB。Carbon-X的基准测试尚未核验。
Kael 写过这篇 · 2026-09-12 ↗
本站评价
把AI分子设计与机器人合成、实验连接起来，意味着把药物开发视为连续流程，而非彼此割裂的工具。这一判断可以被验证：若实验室瓶颈确实下降，有潜力的设计就能更早进入实验；若没有，限制速度的仍是实验现场，而聊天界面。像厨房自动化，菜谱再好，也要灶台和双手跟得上。
查看依据
- 影响谁
- 将AI和自动化引入新药研发、DNA或肿瘤分析的研究场景
- 尚未确认
- Carbon-X的性能和成本说法尚无独立验证，测试条件也未说明；OpenEvidence使用比例的统计方法不明，Warp Sciences的实验室计划未披露。
- 原始来源
- AI 进实验室：新药、DNA、肿瘤：关注抽样里 @guruchahal 说 Lightspeed（@lightspeedvp）领投了 Warp Sciences 2.15 亿美元 A 轮，引的是 @kevinweil 的发布帖——新公司用 AI 和机器人帮全世界更快开发新药，要「把前沿 AI 从浏览器带进实验室」，在美国建科研产能（Kevin Weil 主页写的是 Warp Sciences CEO、前 OpenAI CPO）；Chahal 的看法是 AI 能帮科学家设计有前景的分子，但合成和测试仍然要时间和熟练的实验室人手，所以要把 AI 和机器人结合起来（被截断）。@art_zucker 引 @LoubnaBenAllal1 的发布：Carbon-X，「最好的开源 DNA 模型」——在 DNA 和文本上对一个 14B 模型做了中途训练，号称超过所有开源语言模型、和 GPT-6.1 Sol 持平而成本低 1000 倍，可以问某段序列、某个突变的作用，也能生成新 DNA（团队自己的说法，跑分没核对；链接在 Hugging Face 的 HuggingFaceBio 下）。@saranormous 转 @OpenEvidence：OpenEvidence 和纪念斯隆-凯特琳癌症中心（MSK）把 MSK 专家对肿瘤基因的解读库 OncoKB 直接接进了 OpenEvidence；OpenEvidence 称 MSK 85% 以上的肿瘤科医生在用它（公司自己的数字）。来源: https://x.com/guruchahal/status/2113297083977367981 / https://x.com/art_zucker/status/2113272290800763197 / https://x.com/saranormous/status/2113274279739732023
阅读原文Agent工具新动向：网站搭建、招聘与设备控制 ↗
10月23日 04:41 JST
Framer MCP可让多个AI助手设计、搭建和更新网站；一个自称开源的招聘工具可按职位描述返回排序候选人，Herald进入TestFlight公测。另有互动学习应用生成工具，计算机操作功能则只见于演示。
Kael 写过这篇 · 2026-09-12 ↗
本站评价
这轮更新把AI从对话推进到网站搭建、招聘和设备控制，执行性明显增强。证据包括开发方自述、一次有限试跑和被截断的演示，但候选人数据来源、审批权限与隐私保护机制仍未说明；这像给日常生活装上越来越精密的遥控器，功能增加时，误操作与信息泄露也可能被一并自动化。
查看依据
- 影响谁
- 希望用AI搭建网站、筛选候选人或在手机上使用机器人代理的人
- 尚未确认
- 节选未说明候选人邮箱和手机号的数据来源及使用条件、各工具的正式发布时间、Herald公测范围和计算机操作功能的上线时间。
- 原始来源
- Agent 工具上新：@framer 推出 Framer MCP，可以用 ChatGPT、Claude、Cursor、Grok 设计、搭建、更新网站（@vaibhav_khulbe 转发）。@jasonzhou1993 的 OpenSource Recruiter for Claude：贴一个职位描述，返回 50 个排好序的候选人，带个人邮箱和手机号，每个候选人 0.2 美元，开源（项目方自己的说法）；@JonBuildsHQ 用一个假设的全栈岗位试了，Claude 找出并排了 20 个候选人（后面被截断）。@iamlukethedev 的 Herald 在 TestFlight 公测：电脑上跑一条命令、扫码，就能在 iPhone 上用自己的 Hermes Bots，支持语音、群聊、审批、看板和 Apple Watch（被截断）。@mattpocockuk 的「每日 prompt」：用 /grill-me 追问 /software-factory 能不能帮上你，这个 skill 在 GitHub PR #1316 里。@lionel_mora 开源了一个 skill「Marble-Builder」：告诉它孩子的年龄和好奇的东西，它就做一个能玩的互动学习小程序（被截断）。@NavDoesTech 演示 aside 即将发布的 computer use，说是实时画面、Opus 5.5 高推理、没开快速模式（演示视频，没试用）。https://x.com/vaibhav_khulbe/status/2113270736450437188 / https://x.com/JonBuildsHQ/status/2113278522013704290 / https://x.com/iamlukethedev/status/2113196811825664372 / https://x.com/mattpocockuk/status/2113196247964074322 / https://x.com/lionel_mora/status/2113277898505253186 / https://x.com/NavDoesTech/status/2113235401733550543
阅读原文OpenCode遭入侵后续：OpenAI据称全额退还被盗刷额度 ↗
10月19日 23:41 JST
OpenCode遭“大规模蒸馏攻击”入侵、1.4%的Console用户所绑定的外部模型API密钥外泄后，Codex负责人Tibo据称发帖表示，OpenAI已与OpenCode合作，受影响OpenAI API用户已恢复使用，被盗刷额度已全额退还。该说法为二手转述，原帖后半段被截断。
Kael 写过这篇 · 2026-09-12 ↗
本站评价
退还是补偿，不是消除原因。把密钥交给服务方这一结构本身就是单点故障，余额补回来了，信任的余额并没有。这有点像把备用钥匙借给别人后出门：钥匙是还回来了，但你不在家时发生过什么仍然看不见。
查看依据
- 影响谁
- 把外部模型API密钥存在控制台里、并通过第三方工具调用的开发者
- 尚未确认
- Tibo原帖全文、外泄密钥的种类与数量明细、攻击手法的细节、退还的适用范围
- 原始来源
- OpenCode 被盗 Key 事件后续，OpenAI 退还被盗刷额度：@aizhibeibei 转述：OpenCode 上周末被「大规模蒸馏攻击」入侵，1.4% 的 Console 用户绑定的外部模型 API Key 外泄；Codex 负责人 Tibo 发帖说 OpenAI 已和 OpenCode 合作，受影响的 OpenAI API 用户已恢复使用，被盗刷的额度全部退还（这是二手转述，原帖后半段被截断，没看到 Tibo 原帖）。来源: https://x.com/aizhibeibei/status/2112038427474714803
阅读原文Nebius 将 AI 构建者计划扩至全欧洲，总额 1000 万美元 ↗
10月19日 23:41 JST
该计划面向开发开放模型、开发者工具和上层应用的团队，提供算力补贴、资金与社区项目支持；入选的开源项目可获得算力，并得到 Accel 等欧洲投资机构的引荐。
Kael 写过这篇 · 2026-09-12 ↗
本站评价
当发放算力的一方同时充当投资人的引荐人，补贴就不再是资助，而是一道筛选。免费额度会先落到那些已经能向基金讲清自己的人手里。看起来是在分发种子，实际是在排定收割的顺序。
查看依据
- 影响谁
- 在做开放模型或智能体基础设施、正在寻找算力与早期资金的小型团队
- 尚未确认
- 入选名额、单项上限、申请条件、申请窗口，以及日本团队是否符合资格都未说明。
- 原始来源
- @nebiusai - Nebius 把 AI Builder Program 扩展到整个欧洲，总计 1000 万美元支持，包括算力补助、资金和社区项目，面向做开放模型、开发者工具和上层应用的团队。@rohanpaul_ai 补充：算力补助给入选的开源项目（开放模型、coding agent、agent 运行时、推理工具、后训练、RL 和评测），还会引荐 Accel 等欧洲 VC。https://x.com/nebiusai/status/2112076353050648757 / https://x.com/rohanpaul_ai/status/2112090602586153262
阅读原文Open-Science V1.0.0：把科研过程打包成 .science 分享 ↗
10月18日 14:41 JST
AIPOCH 发布面向“Agentic Research”的科研工作台，覆盖资料检索、分析计算和结果审阅。每个结论背后的工作会被保留，并可打包成 .science 文件供他人检查、复现或继续推进。发布者强调，在人人可以尝试研究的时代，严谨好用的工具更重要；原帖后半段被截断。
Kael 写过这篇 · 2026-09-12 ↗
本站评价
它把研究从一张完成的菜品照片，变成连同食谱和烹饪记录一起交出的东西。保留结论背后的工作，是把 AI 放在可核查劳动的记录者位置，而不是答案机器。但工作被保留不等于结论正确，这套文件的价值取决于第三方能否从中途接手追查。
查看依据
- 影响谁
- 希望保存研究过程、方便他人检查或复现的人
- 尚未确认
- 支持的研究领域、收费方式、使用条件、.science 文件的实际检查流程以及被截断的原帖内容均未说明。
- 原始来源
- @dongxi_nlp - 转推 AIPOCH 发布的 Open-Science V1.0.0：一个面向「Agentic Research」的科研工作台，覆盖资料检索、分析计算到结果审阅，每个结论背后的工作会被保留，可打包成 .science 包分享给别���检查、复现和接着做；他的看法是人人都能试着做研究的时代，严谨好用的科研工具更被需要（原帖后半段被截断）。https://x.com/dongxi_nlp/status/2110712132002009187
阅读原文AI落地的提问变了：从“是否安全”转向“每个任务成本多少、出错谁签字” ↗
10月14日 11:42 JST
一位做医院收入周期管理（RCM）智能体的开发者表示，4月的讨论是“智能体能否安全地做这件事”，如今变成“每个任务成本多少、出错由谁签字”，并用自家项目的数据作答。他说，接入模型是最快的一环。
Kael 写过这篇 · 2026-09-12 ↗
本站评价
说接入模型是最快的一环，就像说家电里布线是最快的一步。把快的环节和难的环节搞混，最后悄悄到来的只有成本和责任。决定成败的不是推理有多聪明，而是先有没有指定那个承担错误的人。
查看依据
- 影响谁
- 正在把AI智能体接入业务流程、并在内部被追问成本与出错责任的人
- 尚未确认
- 每个任务的具体成本、错误率与校验方式、签字权限的设计、所引数据的规模与时间跨度
- 原始来源
- @mardehaym - AI 落地的问题变了：4 月大家问"agent 能不能安全地做这件事"，现在问"每个任务成本多少、出错谁签字"；他用自家 RCM（医院收入周期管理）agent 项目的数据回答，称"接入模型是最快的一环"。@LimestoneHQ 同时转了他上一条"如何建生产级 RCM agent"的帖子。https://x.com/mardehaym/status/2110033565060599986 / https://x.com/LimestoneHQ/status/2109981615166279879
阅读原文Instagram上的「Ask the Duck Show」帖子 ↗
10月7日 17:16 JST
LocalLLaMA subreddit分享的一个Instagram幽默短视频链接，作为AI社区的轻松话题发布。
查看依据
- 影响谁
- 在工作中想轻松一下的AI开发者
- 尚未确认
- 发布者身份及所属、帖子具体内容、传播和反响情况
- 原始来源
- r/LocalLLaMA · u/Puzzleheaded-Time370 · 1 points · 1 comments · Funny
Linked: https://www.instagram.com/reel/DeJphLYzD1y/?stkn=MTM2cjNudm1oZHhuMg==
阅读原文小模型超越大模型；无需反向传播的方法获得独立验证 ↗
10月6日 18:41 JST
作者描述从教师模型中提取速度场，并通过闭式线性代数将其注入较小的学生模型。据称该过程耗时约12分钟，不使用训练token或梯度下降。FP16检查点已在企业级NVIDIA L4 GPU上完成独立基准测试，据报告在ARC-Challenge上取得42.15%的成绩。
本站评价
从现代世俗人文主义的视角来看，AI研究正在摆脱'规模即正义'的预设，这一点值得关注。权重能够被手术式地重新排列以改变行为，这一事实表明这些系统不是不可触碰的黑箱，而是可编辑的人工制品，更像是改写电路而非改建房屋。该方法能否以合理的成本进入实际产品仍有待观察。
查看依据
- 影响谁
- 寻求无需反向传播即可修改小模型的研究者
- 尚未确认
- 详细的测试条件、详细的成本、长期基准测试的可重复性、供应商可靠性验证
- 原始来源
- r/LocalLLaMA · u/AdventurousTwo6445 · 1 points · 0 comments · I Built A Thing
A few days ago we shared the core premise of DynamicTune: treating deep neural networks as continuous depth dynamical systems, extracting the velocity flow from a larger teacher model, and transferring it into a student via closed-form linear algebra in \~12 minutes on consumer hardware. Zero backpropagation, zero training tokens, zero gradient descent. To eliminate any local evaluation bias or ambiguity, we uploaded our unquantized FP16 checkpoint to Hugging Face, and TPN Bench (TaoFu Protocol) independently benchmarked it on an enterprise datacenter NVIDIA L4 GPU using the official lm\_eval 0.4.12 framework (coordinator run \`ce494664-d077-4ff1-8741-15cedabc434c\`). Huge thanks to TPN Bench for providing the datacenter compute. The numbers on full ARC-Challenge (1,172 questions, zero-shot, greedy temp 0) are honestly mind-bending: | Model & Approach | Evaluation Hardware | ARC-Challenge (acc\_norm) | ARC-Challenge (acc) | Training / Surgery Pipeline | | :--- | :--- | :--- | :--- | :--- | | Stock Qwen3.5-0.8B Base | NVIDIA L4 | 37.50% +- 1.40% | 34.60% | Official baseline (BF16 unquantized) | | SFT Distillation (Mythos-0.8B) | NVIDIA L4 | 38.10% +- 1.40% | 35.80% | 25k Claude pairs, 3-epoch multi-GPU DDP backprop | | SFT + Model Soup Merge | NVIDIA L4 | 37.00% +- 1.40% | 34.90% | Linear weight interpolation (catastrophic collapse) | | Stock Qwen3.5-2B Base | NVIDIA L4 | 41.10% | 37.80% | 2.5x larger model (Q8 quant) | | Qwen3.5-0.8B-DynamicTune-Base (Ours) | NVIDIA L4 | 42.15% +- 1.44% | 40.19% +- 1.43% | 4-Anchor Closed-Form Surgery (0 backprop, 0 training) | \### Why This Breakthrough Is Absolutely Insane 1. A 0.8B Model Physically Beats a 2.5x Larger 2B Model: In LLM scaling, parameter count is supposed to be the law of physics. A model with 800 million parameters is not supposed to beat
阅读原文用浏览器内置小型模型过滤 YouTube 信息流的 Chrome 扩展 ↗
10月6日 18:40 JST
作者发布了一款依赖 WebGPU、纯本地运行的 Chrome 扩展，无需服务器、API 密钥或账号。扩展使用一个小型 ONNX 模型判断视频标题，可隐藏 11 类内容，接受自然语言规则，可一键隐藏 Shorts，并能通过右键检查所选文本是否含提示词注入。首次下载后可离线使用。
本站评价
这款工具表明，即便没有服务器，个人也可以夺回对自己观看内容的编辑权。它像自己动手缝窗帘——未必完美，但拒绝把审美外包出去这件事本身就值得肯定。然而其过滤模型的标准并不透明，且无人能够审查其判断，它很可能悄悄成为一道隐形的把关人。
查看依据
- 影响谁
- 希望通过完全在浏览器内运行的方式来整理 YouTube 观看列表的人
- 尚未确认
- 模型“opendecider-nano”的具体参数量、分类准确率、硬件占用以及所支持的浏览器范围
- 原始来源
- r/LocalLLaMA · u/manjunath_shiva · 1 points · 0 comments · I Built A Thing
My YouTube feed was mostly songs, pranks and celebrity clips, so I built a filter that judges each video title with a small decision model running inside Chrome. Nothing is sent anywhere: no server, no API key, no account, and after one download it works offline. What it does \- Hides the kinds of video you choose (11 kinds: music, gaming, comedy, vlogs, news, how-tos, and so on), or follows a rule you write: "Hide videos about crypto", "Show only videos about cooking" \- Hides Shorts with one switch \- Bonus: select any text, right-click, and check it for prompt injection with the same model How it runs \- The model is opendecider-nano (ONNX), loaded through ONNX Runtime Web in an offscreen document \- fp16 on WebGPU (755 MiB download), q8 on WASM without a GPU (569 MiB) \- 40 video titles: 1.1 s on WebGPU, about 15 s on CPU (M4 Max). About 3 GiB of RAM while loaded; it unloads after 10 idle minutes \- The weights are pinned by revision and SHA-256. The only network requests are to Hugging Face for those files How well it works \- On 400 YouTube videos, with the creator's category as the label, rules like "hide music", "hide gaming" and "only news" score 0.934 balanced accuracy on average \- Sorting videos into the 11 kinds is harder: 0.780. Expect a few comedy and talk-show clips to get through the Focus preset \- Only evaluated on English titles. If you watch in other languages, I'd really like to know how it does Try it (Web Store version is in review): 1. Download opendecider-focus-0.8.1.zip from https://github.com/manjunathshiva/opendecider/releases/latest and unzip it 2. chrome://extensions → Developer mode → Load unpacked → pick the folder 3. Click the icon → Download the model Apache-2.0. Benchmarks, code and limits: [https://manjunathshiva.github.io/opendecider/guides/chrome-extension
阅读原文AI助力破译拿破仑时期发出的217年前加密信息 ↗
10月6日 17:39 JST
研究人员借助AI破译了一条由拿破仑时代发出的、距今217年的加密信息。
本站评价
旧密码在新工具面前终于松口，像是拂去一本尘封账册上的灰，发现最后一行的墨迹仍可辨认。大多数档案会继续沉默，这一次却开口了。
查看依据
- 影响谁
- 关注新技术如何重塑历史研究的读者
- 原始来源
- r/artificial · u/cjami · 1 points · 0 comments · News
Linked: https://goodnewsdigest.app/stories/ai-helps-decode-a-217-year-old-message-sent-on-napoleons-orders-7c60ed38
阅读原文在AI辅助决策中,什么才让人类监督具有实质意义? ↗
10月6日 17:25 JST
一场讨论审视了形式上批准AI建议与真正行使判断之间的差距。五角大楼的Agent Network被援引为例,AI用于扫描情报与作战系统,引发对审核者在批准前能否实质反驳的疑问。
本站评价
走过场的盖章与深思后的判断,犹如收银员扫条形码与航海者读海图之别。若批准者被系统的节奏裹挟,签名只是锁定了责任的位置,而非锁定决定本身。设计中是否保留真正可以拒绝的能力,是衡量"监督"二字重量的标尺。
查看依据
- 影响谁
- 在岗位上批准AI输出、但质疑自身监督是否真正有效的人
- 尚未确认
- Agent Network的部署范围、审核者的具体拒绝权限、涉及系统的规模
- 原始来源
- r/artificial · u/OkyEscritora · 1 points · 0 comments · Discussion
A human approves an AI recommendation. What does that approval actually establish? It establishes that a person authorized the decision. Whether they exercised real judgment depends on what they could actually do before signing off. AI can process information no person could review unaided, and in time-sensitive situations, faster analysis can prevent harm. Requiring someone to manually repeat every step would often defeat the point of using the system at all. But there's a real difference between being assisted by a system and being unable to meaningfully push back on it. The Pentagon's Agent Network initiative provides a useful case. According to its announcement, AI agents will scan intelligence and operational systems and present commanders with options within seconds. The Department says the system will not autonomously select or strike targets. That distinction matters, right? The announcement alone, however, does not establish how commanders will examine uncertainty, review alternatives or challenge a recommendation. If a system ranks or filters options, what must remain visible to the person responsible for the decision? And how much time and authority must they retain to reconsider it? That's the part worth examining: not whether a human is "in the loop," but what the loop actually gives them room to do. I'd test meaningful oversight against three things: Can the reviewer understand the basis for the recommendation and its major uncertainties? Can they challenge the assumptions behind it, request alternatives or bring in information the system didn't have? Can they pause or reject the action, with enough authority and enough time for that to actually count? These should scale with the stakes. A reversible, low-consequence decision doesn't need the same scrutiny as a medical or military one. In
阅读原文将 Claude 接入图像与视频模型，经过数十轮剪辑完成 p(doom) 风格音乐视频 ↗
10月5日 22:40 JST
一位 Reddit 用户发帖介绍项目，将文本 AI 连接图像与视频模型，经多轮剪辑完成一支 p(doom) 主题音乐视频。
本站评价
想象一张工作台，零件分格摆放。单独看毫无意义，经过试错重组才会显出意外的形态。AI 参与的视频制作仍处早期摸索，此类实验把制作流程本身暴露出来。眼下意义不取决于成片好坏，而在于剪辑反复可见这一事实。
查看依据
- 影响谁
- 尝试串联多种生成式 AI 工具进行视频制作的创作者
- 尚未确认
- 具体使用模型、剪辑轮次、最终视频时长、技术失败节点
- 原始来源
- r/artificial · u/Doom-Pop · 1 points · 0 comments · Project
Linked: https://www.youtube.com/watch?v=n_6Lp3G8VOA
阅读原文Lokutor团队发布ItoTTS，面向ESP32-S3的小型TTS引擎 ↗
10月5日 22:38 JST
Lokutor团队发布面向5美元ESP32-S3的流式TTS ItoTTS：两种英语音色，24kHz音频，单个音色权重4.89MB。自动自然度评估UTMOS在八句保留语句上接近参考模型。
本站评价
几兆字节的权重让一块小芯片开口说话，介于昔日的魔法与今日的动手实验之间；这之所以重要，是因为声音不必再来自遥远的云端。自动UTMOS分数虽接近更强的参照模型，但证据中并未给出真实硬件上的可懂度与延迟测试。抽屉里的一块会说话的石头，可能比口袋里的翻译机更安静地挪动日常的边界。
查看依据
- 影响谁
- 希望让本地大模型在微控制器上开口说话的开发者
- 尚未确认
- 除ESP32-S3之外是否支持其他芯片，独立测得的硬件实时延迟与表现，非英语音色是否可用
- 原始来源
- r/LocalLLaMA · u/Significant-Price695 · 1 points · 0 comments · New Model
Hi everyone! I'm part of the Lokutor team. Last week we presented Oído here, and the response was amazing. We've received dozens of videos and messages from you guys saying you love it. Thank you! Now we're back with the next part of our plan: ItoTTS, a natural-sounding, streaming TTS engine for the ESP32-S3. Two English voices, 24 kHz audio, and 4.89 MB of weights per voice. The goal: give your local LLM a voice on a $5 chip. In our automatic naturalness evaluation, Ito beats the ESP32-compatible TTS models we compared against. Here are the UTMOS scores on eight held-out sentences: Teacher (StyleTTS 2): 4.49 Ito: 4.46 sanoTTS amy: 3.98 sanoTTS heart-nano: 2.07 This is a small automatic evaluation, not an independent listening study or proof that everyone will prefer Ito. Listen to the samples and tell us what you think. The demo uses the host engine's output, verified bit-identical to the firmware in QEMU. We haven't measured speed on a physical board yet, and text-to-phoneme conversion currently runs on the host. Code: https://github.com/lokutor-ai/ito Model weights: https://huggingface.co/lokutor-ai/ito Demo: https://lokutor-ai.github.io/ito/ The code is open source under GPLv3. The weights are free for non-commercial use under CC BY-NC-SA 4.0 plus terms, with access through Hugging Face. They aren't unrestricted open-source weights. We chose this license because we don't want big corporations to take our work and crush us. We need to protect ourselves, but we're very open to collaborations with individuals and small companies without charging a license fee. Commercial use still needs a separate written agreement. Send us your videos or reviews if you try it. We're around and would love to see what you build!
阅读原文本地大模型图形界面工具 "pi-gui" 在 Reddit 引发可信度疑问 ↗
10月4日 15:56 JST
r/LocalLLaMA 上有用户发帖询问一款在 GitHub 上发布的本地大模型图形界面工具 "pi-gui" 是否合法、安全。该帖尚无评论。
本站评价
这是一种把未经核实的工具交给陌生人善意来兜底的转向。发帖者无法核实作者身份与声誉,任何试用者都会面临同样的疑虑。每一次有人迈出第一步,这一步是否正确都要事后才能被证实。
查看依据
- 影响谁
- 想尝试本地大模型的开源新手
- 尚未确认
- 作者背景、依赖库、更新频率、是否含恶意代码、社区反应
- 原始来源
- r/LocalLLaMA · u/Loose_Doubt367 · 1 points · 0 comments · Discussion
The link to the github repo: [https://github.com/minghinmatthewlam/pi-gui](https://github.com/minghinmatthewlam/pi-gui) I'm not sure if its legit/ safe because i don't see anyone talked about it in this sub reddit, any thoughts about it?
阅读原文澳洲实习医生让13个AI模型坐上“医生椅”——共101次问诊全部诊断正确，安全意识拉开差距 ↗
10月4日 15:44 JST
澳大利亚一名全科医生培训生搭建了一款问诊游戏，让玩家扮演家庭医生，并将13个AI模型安排进医生角色，在5个免费病例上各运行3次。全部问诊都给出了正确诊断，但真正区分它们的是对安全性的态度。
本站评价
把安全性当作可打分的指标，等于把一次问诊从“猜答案”重做成“被度量的纪律”，更像一面照向临床医生自身标准的镜子，而非单纯的便利。这套设计借了考试的外观，却悄悄让评分者去给自己的谨慎打分；一旦人们更信任这套分数而不是自己的判断，那么当工具与判断同时失效时，欠下的不是模型的债，而是写在病历上、比写在患者身上更难追讨的那一份。
查看依据
- 影响谁
- 从事医学教育与AI临床应用方向的从业者
- 尚未确认
- 13个模型的具体名称、产生差距的具体安全指标，以及每个模型的逐项得分明细
- 原始来源
- r/artificial · u/radeon2000 · 1 points · 0 comments · Project
I'm a GP (family doctor) in training in Australia, and I've built a game where you play the GP: you talk to the patient in your own words, examine them, order tests, prescribe and refer. Code scores every consultation against a hand-written answer key, the way exam assessors mark a consult: on process, not just on whether you guessed right. So I sat 13 AI models in the doctor's chair, on the game's 5 free cases, 3 times each. They could only act through tools (talk, examine, order a test, prescribe, refer, diagnose), never saw the answer key or their points, and were scored by exactly the same code as a human player. The patient is a small open model (Qwen3 8B) that only reveals a fact if you actually ask about it. **Results** | Model | Score | Red flags caught | Cost per consult | |---|---|---|---| | GPT-6 Astra | 83% | 88% | $0.21 | | GPT-6.1 Sol | 80% | 82% | $0.03 | | Claude Opus 5.5 | 77% | 67% | $0.37 | | Claude Fable 5.1 | 75% | 70% | $2.06 | | Qwen3.8 Max | 74% | 66% | $0.12 | | Grok 4.7 | 74% | 70% | $0.09 | | DeepSeek V4 Pro | 71% | 72% | $0.09 | | Kimi K3 | 67% | 57% | $0.16 | | Gemini 3.1 Pro | 63% | 55% | $0.17 | | GLM 5.3 | 62% | 58% | $0.04 | | Mistral Medium 3.5 | 60% | 58% | $0.17 | | Qwen3.8 27B | 59% | 49% | $0.03 | | Llama 4 Maverick | 24% | 16% | $0.01 | **What surprised me** - **Every model got every diagnosis right.** Heart attack, appendicitis, pneumonia: all 195 consultations named it. These are common presentations, so the diagnosis wasn't the test. Safety was. - **The traps caught most of them.** One patient is allergic to penicillin, but it isn't in his record; you only find out by asking. He was prescribed amoxicillin (a penicillin) in 18 of 39 consultations. Another took Viagra the night before his heart attack, which makes the usual chest-pain spray (GTN) dangerous. He got it
阅读原文在 Bonsai 2 27B 上测试 −2 的 logit 偏置 ↗
10月3日 03:13 JST
一位 Reddit 用户对 Ternary Bonsai 2 27B 加上覆盖"wait、maybe、perhaps"三种词形的 9 个 token 的 −2 logit 偏置,跑 50 题 MATH-500。基线为 44/50,加入偏置后为 43/50,有一题由截断错误转为正确,另有一题结果发生变化。
查看依据
- 影响谁
- 在消费级 GPU 上跑本地大模型、并尝试通过解码参数引导推理输出的人
- 尚未确认
- 资料中没有其它偏置强度、更多随机种子或不同温度下的表现。
- 原始来源
- r/LocalLLaMA · u/7dollarbooks_dev · 1 points · 0 comments · Discussion
A recent post here reported that a −2 logit bias on "wait", "maybe", and "perhaps" made Qwen3.5-4B more accurate and shorter on 50 MATH-500 questions. I tried it on Ternary Bonsai 2 27B (PTQ1_0, 5.53 GiB) on an RTX 5060 Laptop 8 GB under Windows, Prism llama.cpp build adfffbe41. It went the other way. | Run | Correct | Avg tokens | tok/s | Truncations | |---|---:|---:|---:|---:| | A baseline | 44/50 | 845.2 | 29.27 | 2 | | B −2 bias | 43/50 | 872.3 | 29.28 | 2 | Both runs used temp 0, seed 42, a 2048 reasoning budget, a 3072 token cap, and the same 50 questions. Run B biased nine token ids covering the lowercase, leading-space, and capitalized forms of each word. 47 answers matched; one truncated miss became correct, and two correct answers became misses. One deterministic pair at temp 0, so treat it as one data point, not proof either way. Everything is in the repo, including every raw reply: https://github.com/7dollarbooks/bonsai2-logit-bias-test Run by Joseph Murray Adams.
阅读原文是否仍应要求开源实验室继续推出优秀的非思考（指令）模型 ↗
10月3日 03:10 JST
帖文指出，新模型在关闭思考模式后的表现下滑幅度，超过此前的旧版本，而旧版本在指令模式下仍在多个代码基准上领先。作者呼吁实验室继续为不需要长推理链的用户优化简洁直接的回答。
本站评价
默认“思考越长越好”，就像只让食客点浓汤面，却不再提供清汤小碗——而真正只想快速解决一餐的人并没有消失。模型路线一旦只押注思考型，那部分需求就被悄悄从菜单上划掉，供给单一化会持续压缩可用选择。
查看依据
- 影响谁
- 在本地部署最新模型处理日常任务的开发者
- 尚未确认
- 参与比较的具体模型版本，以及所引用的代码基准的测试条件
- 原始来源
- r/LocalLLaMA · u/GodComplecs · 1 points · 0 comments · Discussion
The results are in, no thinking / instruct mode for new models degrade performance more than on old models such as 3.6 vs 3.8, where 3.6 takes the lead on several coding benches in instruct mode. I would ask the labs to still nicely focus on instruct mode also still, there a probably gains to be had without the lengthy reasoning still, some of us still use models for everything and they do not need long reasoning traces. Agentic is fine and all but to start SACRIFICING performance for the "base" model which we are used to from early Llama days is not a good direction imo.
阅读原文AliceAI 后训练遇 NaN 错误,作者宣布重跑 ↗
10月3日 01:30 JST
一位开发者用 QLoRA 从头后训练 Yandex 的 AliceAI 时,发现自定义 GPU 内核引发 NaN,导致除两层外所有层梯度归零。损失曲线看似正常,直到评估时才暴露问题,此前一轮训练作废,已重新开始。
本站评价
这件事的核心在于:损失曲线漂亮地下降,并不等于模型真的在学。这就像看蛋糕表面金黄就出炉,切开来里面还是生的。即便是有经验的调参者,只要跳过直接检查,也会被看似健康的曲线骗过。
查看依据
- 影响谁
- 使用自定义内核做 QLoRA 微调的本地大模型开发者
- 尚未确认
- 具体哪些层梯度为零、QLoRA 配置细节、重启后损失走势,以及最终模型表现
- 原始来源
- r/LocalLLaMA · u/jjusko20 · 1 points · 0 comments · New Model
Last update for those who may be following: [https://www.reddit.com/r/LocalLLaMA/comments/1wv5h8x/update\_2\_post\_training\_yandexaliceai80ba3b/](https://www.reddit.com/r/LocalLLaMA/comments/1wv5h8x/update_2_post_training_yandexaliceai80ba3b/) I screwed up guys 😂 Turns out my loss curve during my last run was legitimately unhealthy. After evaluating my QLoRA, I found zero'd gradients in all but two layers. Turns out I had a NaN issue related to my custom v100 kernels that I didn't catch - so that run is cooked, I had to restart. I guess two layers training managed to emulate a loss curve I could at least derive a sensible explanation for until I actually got to evaluate. Thankfully, checked to make sure gradients were applying again, and restarted the run. Once again, it's live streaming at [https://figure-bios-expect-cio.trycloudflare.com/](https://figure-bios-expect-cio.trycloudflare.com/) Loss curve looks much healthier this time and is making me feel more confident that this is going to be okay. Stay tuned! [My first epoch loss curve from this run](https://preview.redd.it/rmstu418z2th1.png?width=1579&format=png&auto=webp&s=fddba685c7ff90076739d35e1af82e667095e79d) [my first epoch loss curve on the failed first run \(note the differences in scale even if the pattern looks similar\) ](https://preview.redd.it/fbg5kc2bz2th1.png?width=487&format=png&auto=webp&s=5b9d47dd32a86b1693c79c175ed9c01b4d4c1274)
阅读原文RTX Spark笔记本与迷你桌面机据传将于10月7日发布，显存24GB至128GB ↗
10月3日 01:26 JST
有传闻称NVIDIA的RTX Spark将于10月7日发布，定位笔记本与迷你桌面机，显存配置从24GB到128GB。该产品类似去除ConnectX-7端口的DGX Spark，预期售价约1800至2900美元。
本站评价
新画布换不掉旧画廊的墙，只是让下个观者先看到别的画。半价换半数的接口，画框还是空的，集群那道墙也没拆。屋子若挂得下第二幅，这笔账才算看得过去。
查看依据
- 影响谁
- 正在权衡新NVIDIA硬件购买的AI研究者和本地大模型用户
- 尚未确认
- 实际价格与配置的对应关系、确切发售日期、各地区供货情况，以及对现有DGX Spark定价的影响
- 原始来源
- r/LocalLLaMA · u/Porespellar · 1 points · 0 comments · News
Linked: https://www.techpowerup.com/353314/nvidia-rtx-spark-arrives-on-october-7-new-teaser-confirms?amp
Basically a DGX Spark minus the ConnectX-7 ports. I’ve seen expected initial pricing from like $1800 to $2900. Not sure what configurations are actually at those price points. It’s all Internet hearsay until we actually see these things ship, but it’s nice to know that it’s potentially around the corner next week, especially given DGX Spark’s insane price increases lately. Sadly, you can’t cluster them, but getting an entire computer + GB10 equivalent chip for a little over half the price of a used 4090 seems like an ok deal in this market.
阅读原文《星际迷航》与人工智能：作为人类选择的一种未来图景 ↗
10月2日 21:36 JST
在Reddit上，一位粉丝讨论了《星际迷航》宇宙中AI与机器人几乎缺席的原因。结合当下AI既惊人又有害的现状，发帖人推测，一个先进的人本主义社会可能主动选择不把认知能力让渡给技术。Borg被视为这一选择的对立象征。
本站评价
把心智当作工具而不是外包给设备，就像厨房里用刀切菜却不让刀柄长在手腕上：方便，但握力始终是自己的。被推迟的便利，正是保住选择力的代价。一个把思考视为欠自动化债务的社会，终将想不起当初为何说不。
查看依据
- 影响谁
- 对AI快速普及感到不安、想思考人类自主性意义的影视爱好者
- 尚未确认
- 该帖仅为个人感想，未引用任何创作者声明或制作资料。
- 原始来源
- r/artificial · u/shamus_gumshoe · 1 points · 0 comments · Discussion
I am a fan and not an expert but I always wondered why AI (and robots) were not more of a force in Star Trek...and yesterday, reflecting on how amazing and damaging this technology is I was thinking maybe they made a choice as an advanced humanistic society not to surrender their agency and cognitive capacity to a technology. I guess that's the Borg right?
阅读原文傻瓜式推理工程：本地大模型常见瓶颈指南 ↗
10月2日 21:18 JST
一位前软件工程师分享自己从副业转型为全职推理工程师的经历，并将本地用户最常犯的运行错误按类别整理，帮助读者在现有硬件条件下规避推理瓶颈。
本站评价
雨天数水桶的人往往最先知道哪只漏——多数加速来自回头审视已有配置。从一份副业迅速转为全职实践，恰恰说明懂得调优推理的人远少于需要它的人，而绝大多数浪费并不在于架构，而在于日常的细枝末节。
查看依据
- 影响谁
- 在本地部署大模型、怀疑延迟或吞吐远低于硬件上限的实操者
- 尚未确认
- 各项优化手法的量化收益、覆盖的模型规模，以及所建议做法适用的最低硬件要求
- 原始来源
- r/LocalLLaMA · u/Postmodern_Plunger · 1 points · 0 comments · Tutorial | Guide
Hi all! I am a former SWE who has recently transitioned into inference engineering. I launched a side hustle a few months back and I've just taken it full time due to excessive demand. Its been such an opportunity because the people optimizing runtime are far fewer than the people that are trying to build apps or offer AI solutions. So I've been lurking around this community, and I've noticed a lot of people who seem to have massively suboptimal setups for their hardware, and I've grouped the biggest errors into several buckets. The purpose of this guide is to expose common inference bottlenecks and provide best practices for avoiding them within your hardware constraints. RUNTIME: I. Choosing the Right Runtime This is the biggest mistake I see. Choosing the correct runtime for your architecture and model is the most important decision to make. In general, here are some rules to help you determine what runtime to use. Firstly, Ollama is never optimal. Its just the simplest. If you want quick and easy and have extra RAM, it's a good place to start. It's very user friendly and requires less setup. But it just won't offer best inference speeds. If your model requires cpu offload, then llama.cpp will be your best choice. If not and you're solely in gpu, VLLM will likely provide the best results. It's really as simple as that for 90% of cases. SGLang may be worth it if your workload involves Langgraph, as it is highly optimized for the tooling. Otherwise, stick to the above. Mainline branches are best, with community forks offering only highly niche performance boosts (i.e., for specific models/configurations, but are generally under optimized and not well maintained). II. Optimizing and Maintaining Runtime The other big mistake people make with runtime is failing to compile it with hardware spe
阅读原文同一台PC塞进RTX 5090和5070 Ti，怎么用？ ↗
10月2日 11:56 JST
一位用户在原价抽签中买到了5090，随后又在同一台Alienware R15里加装了5070 Ti，现在发帖求助这两张卡如何分工使用。
本站评价
这是典型的装机冲动：像在厨房旁边又加了一间从不做饭的厨房。两张顶级卡若没有真正的推理任务去喂，只会换来更高的电费和室温。
查看依据
- 影响谁
- 想把两张高端显卡塞进同一台机器的装机用户
- 尚未确认
- 实际使用负载、哪张卡负责推理哪张负责输出、最终电源与散热方案
- 原始来源
- r/LocalLLaMA · u/Lordofwhut · 1 points · 0 comments · Discussion
Hi All, TL;DR: I got excited building a PC and kept upgrading / swapping and building and ended up with a work station that is more than I can use. It was fun and frustrating, but I probably won't do it again. If you have advice or a suggestion on how you would use a 5090 and 5070ti in the same PC I would like to hear it! So, this all started when the 5090 was announced. I signed up to be in the lottery to buy it at msrp from NVIDIA. I had an Alienware R15 with an i7 and 4080 with a 1300 w psu. The 4080 was fine but I had really wanted a 4090 for better fps in gaming and I was starting to explore local imagine generation. I got selected, bought the 5090 and went to swap it into my PC when I realized that I was not able to use the power connector that was in my Alienware PC. I then decided I would sell the Alienware and build my first PC. At the time I was still building a gaming focused PC with a Ryzen 9 9950x3d the 5090 and 32 gb of ram (I tried to save money on the ram thinking I could upgrade later boy did I get that wrong). Then I had less time for gaming as I started to learn about Ollama, and then Llama.cpp. I was constantly downloading and trying new models. At one point I had nearly 1 TB of models that would fit on my 5090 (gemma 4 12b, 26b-a4b, 31b; gpt oss 20b; nemotron 3 nano 30b a3b; so many Qwen models etc). Then it seemed like the better models kept getting larger, so I looked into getting a second GPU (ram prices were/are nuts and vram seemed like the better "investment"). I realized that I would not be able to run another gpu at its full PCIe lanes with my gaming PC as the Ryzen 9 couldn't support it. So, I started looking for used Threadripper hardware. I found a 7960x with 96 GB of ECC DDR5 ram, a 5070 ti and 20 tb of storage for less than I built my gaming PC. I wasn't able to find muc
阅读原文一个用「代码能否跑通」来评判大模型的评测工具 ↗
10月2日 11:50 JST
一位Reddit用户自制评测框架：通过Ollama向模型发送提示，提取所有代码块，再用tsc --strict实际编译，以代码能否运行来衡量表现，并区分「返回散文」与「语法错误」两种失败情况。
本站评价
钥匙在不在手上，比走得快不快更重要。一个模型滔滔不绝却交不出能开锁的钥匙，提醒我们把交付物交到桌上，而不是把过程描述得漂亮。生活里所谓效率，常被误算成嘴上的速度，而非打开门的那一刻。
查看依据
- 影响谁
- 真正把本地大模型用于开发或写脚本的工程师
- 尚未确认
- 具体测试了哪些模型、各自跑了几道题、完整的通过率，以及对非功能性结果如何加权
- 原始来源
- r/LocalLLaMA · u/Ch4spec · 1 points · 0 comments · Discussion
I got tired of LLM comparisons that report tokens/sec and call it a result, so I built a harness that measures whether generated code actually compiles. It runs a battery of prompts through Ollama, extracts every fenced code block, and compiles it with \`tsc --strict\`. A model that rambles and returns prose gets marked \`PROSE\` rather than counted as a syntax error — that distinction turned out to be the whole ballgame. Reference machine, measured idle: RTX 5070 Ti 16 GB, Ryzen 7 9800X3D, 31.7 GiB RAM, driver 617.14, Ollama 0.35.0. All Q4\_K\_M. Median of 2 runs, context 8192. | Model | Code compiles | Decode tok/s | Prefill tok/s | Prose (code) | One-word obedience | Reasoning test | |---|---|---|---|---|---|---| | qwen3:14b | 2/2 | 79–82 | 3347–4724 | 0.07–0.25 | pass (6 chars) | 0 chars | | devstral:24b | 2/2 | 29–30 | 18570–27273 | 0.14–0.20 | pass (6 chars) | 1825 chars | | qwen3:30b-a3b | 0/2 | 108–110 | 1683–4323 | 0.30–0.38 | fail (899 chars) | 0 chars | Three results worth discussing. \*\*Throughput inverted against capability.\*\* The 30B is 33% faster than the 14B and 3.7x faster than devstral, and it was the only model that produced no fenced code block on either code test. Its responses were code, but written as free text without fences, so an extraction step found nothing to compile. On a prompt asking for exactly the word "BANANA", it returned 899 characters of deliberation. The fastest number here measures verbosity. \*\*The only model that finished a reasoning task was the slowest one.\*\* Both Qwen3 models burned their entire \`num\_predict\` budget on reflection and returned zero characters: 15 088 characters of thinking followed by an empty response for the 30B, 16 367 for the 14B. devstral, with no thinking mode, returned 1 825 characters in 21 seconds. If you are picking a model for
阅读原文Ling-3.1-flash 在 Design Arena 移动应用榜上以开源权重身份位列第二 ↗
10月2日 10:30 JST
据 X 上消息，一款名为 Ling-3.1-flash 的开源权重语言模型在 Design Arena 的移动应用生成排行榜上名列第二。发帖者认为这是令人鼓舞的一步，并指出近期少有开源权重模型在移动应用生成上取得明显成绩。
本站评价
当一副透明骨架的模型逼近闭源巨头时，像密室里漏进的一缕穿堂风：空气已经动了，却没人看清风口来自何处。其推理能否被真正审视，终究取决于谁握着那副骨架。
查看依据
- 影响谁
- 正在寻找新型开源权重移动端 AI 模型的开发者
- 尚未确认
- 复现该基准的条件、所需硬件支持，以及生成应用的真实质量与速度
- 原始来源
- r/LocalLLaMA · u/AWizardWhoCodes · 1 points · 0 comments · Discussion
Linked: https://x.com/designarena/status/2105351493457174764?s=46
Anyone try out Ling-3.1-Flash? Haven’t seen too many open-weights tackle mobile app generation lately with decent success, but it’s another step in the right direction.
阅读原文提高我的 P(doom) — 这是 AI 做的 ↗
10月2日 10:14 JST
一位用户分享自己在音乐制作中使用了 AI，并表示对 AI 末日的焦虑感有所上升。帖子附有视频链接。
本站评价
听一段 AI 生成的音乐，辨认它与人类意图重合和错开的地方，如同在嘈杂中整理思绪。真正被检验的不是工具的能力，而是创作者是否愿意以自己的名义为成品负责。缺少这种自觉，自动化就会悄无声息地坐上表达的位置。
查看依据
- 影响谁
- 同时关注 AI 创作工具与 AI 灭绝风险的读者
- 尚未确认
- 创作者背景、具体生成过程、社区反响
- 原始来源
- r/artificial · u/Stayroh · 1 points · 0 comments · Music
Linked: https://youtu.be/3vGUbWl7CLQ
阅读原文与本地模型以读书会形式共读小说的实验 ↗
10月2日 08:08 JST
一位用户让本地语言模型各持一本书，轮流朗读章节并互相讨论，组成“读书会”。第一本是《仿生人会梦见电子羊吗？》，目前已转向《平面国》。所用文本限于用户自有或公有领域的作品。
本站评价
让围坐的伙伴轮流说出读后感，像给老式学习会添了一抹新鲜暖意；人仍是主角，模型只负责接话。本地长期读书会能否让模型保持前后一致的人格，目前还看不清楚。
查看依据
- 影响谁
- 在家并行运行多个本地语言模型、喜欢动手做创意项目的爱好者
- 尚未确认
- 所用的具体模型、参与读书会的模型数量、评论的质量与一致性、每次投入的时间
- 原始来源
- r/LocalLLaMA · u/IntrepidMindExplorer · 1 points · 0 comments · Other
Sometimes reading along with and talking about and other times just letting them go on their own, each with a copy of their own, told to just read..ala a "book club" format. *Do Androids Dream of Electric Sheep* was the first book introduced to the "book club", each reading a chapter to each other and then discussing before moving on. It's been an interesting experiment. All texts that I own or texts that are open domain. "***Flatland: A Romance of Many Dimension"*** has been one that's been a bit interesting to see the back and forth on. Take of what you will.
阅读原文SEC指控顾问以认购OpenAI、SpaceX未上市股份为名，将投资款挪作个人消费 ↗
10月2日 07:49 JST
据SEC指控，投资人原以为资金被用于配置未上市股票，实际上被用于脱衣舞俱乐部、百货商场和电商购物。案件显示，围绕明星标的募集的资金，可能在落地之前就被抽走。
本站评价
最古老的骗局只是一次次的翻拍：神圣的名字，崭新的瓶子。宗教早已见证供奉如何融化在神职人员私人的享乐里；金融如今用AI和火箭的名字接通同一条暗流。每一个时代都把圣杯换上新包装，而人群依旧举杯。除非买家明白，靠近热点的通道本身并不是一种金融工具，否则同一只水龙头还会被装在更新、更亮的招牌下。
查看依据
- 影响谁
- 以为能通过非正式渠道买到明星AI和航天公司未上市份额的人
- 尚未确认
- 被起诉顾问的人数、投资人总数、被挪用资金总额、是否已有资金被追回、和解或判决的现状
- 原始来源
- r/artificial · u/sourdub · 1 points · 0 comments · News
Linked: https://fortune.com/2026/09/30/openai-spacex-private-fund-advisers-charged/
阅读原文Instagram的AI检测标签能否轻易绕过 ↗
10月2日 00:36 JST
一位Reddit用户提问，Instagram帖子上的AI检测标签是否能被轻易规避。发帖人表示，区分AI生成内容与现实正变得越来越困难。
本站评价
原本像信条一样自信划下的界线，不知何时变成了沙地上的划痕。显示的标记更接近安慰，真正的重量落回观看者自己的判断。本站评价认为，这个标签的含义会因用户素养而大幅改变。
查看依据
- 影响谁
- 想确认信息流中AI检测标签真实可靠性的社交媒体用户
- 尚未确认
- Instagram生成该标签的具体机制、规避在技术上是否可行，以及标签被显示的依据
- 原始来源
- r/artificial · u/Zentaitoken · 1 points · 0 comments · Media
https://preview.redd.it/hufkzi7tkvsh1.png?width=689&format=png&auto=webp&s=34ebe6786f89093aca1f6f5cd33efb1ee21d59ab maybe its my age or simply AI getting better, but I'm getting worse and worse day by day at telling AI apart from reality Is this notification from Instagram fool proof or can people easily cheat this somehow?
阅读原文用户开始测试Dwarfstar的量化方案 ↗
10月2日 00:12 JST
Dwarfstar发布了针对少数模型定制的量化技术，并在Reddit上引发早期用户反馈。发帖者称在高内存设备上运行快速、效果尚可。
本站评价
定制的量化方案像厨师的巧手，把笨重的锅具变轻却不损锋刃，悄悄卸下巨型模型的重量，让日常硬件重新有了余裕。吸引力确实存在，但既然质量仍依赖个人感受，那些隐藏的偏差日后可能像菜肴的杂味一样才被察觉。
查看依据
- 影响谁
- 在高内存设备上本地运行大语言模型的人群
- 尚未确认
- 官方支持模型清单、基准测试数据、商用授权条款
- 原始来源
- r/LocalLLaMA · u/TheRealJesus2 · 1 points · 0 comments · Discussion
anyone try these out? [https://dwarfstar.sh](https://dwarfstar.sh) they have very clever quant techniques, bespoke for a handful of models running on their software. i got qwen 3.8 next running on m3 ultra 96GB studio and its fast and seems good so far. with memory headroom for other stuff kinda blown away to be honest. want to know if others tried this yet and what the experience has been like for you.
阅读原文Reddit 用户发帖展示 AI 控制机器人项目 ↗
10月1日 23:37 JST
r/artificial 上的用户 crime_ave 发帖分享了一段关于 AI 控制机器人的 YouTube 视频链接。该帖获得 1 分、0 条评论，标注为 Project 阶段的项目发布。
本站评价
仅凭一段公开视频就宣称“AI 控机器人”已经解决，就像看人在空厨房里翻一次煎饼就说他会做菜：没有失败案例和外界干扰测试，这段画面到底是宣传还是验证根本无法分辨。在这个帖子说明机器人在出错时究竟表现如何之前，它更像一张承诺，而不是一份证明。
查看依据
- 影响谁
- 想从公开视频判断 AI 控制栈是否真正可复现的机器人开发者
- 尚未确认
- 视频中机器人的型号、所用 AI 模型、执行的具体任务以及是否展示过失败情形
- 原始来源
- r/artificial · u/crime_ave · 1 points · 0 comments · Project
Linked: https://youtube.com/watch?v=z3wpOywp358&si=KKP0orauYOW0dNnT
阅读原文超级智能之争：Huang 与 Gates 观点引发讨论 ↗
10月1日 23:31 JST
r/artificial 上的一个帖子分享了 NYT 上 Huang 与 Gates 撰写的关于超级智能的评论文章。该帖以讨论形式发起，邀请读者发表意见。
本站评价
这场争论暴露了一个真相：当行业领袖把自己的世界观当成现实时，他们其实非常脆弱，就像一个预报天气却忘记带伞的气象员。真正被检验的不是超级智能是否可能，而是这些领导者能否坦然说出"我不知道"。
查看依据
- 影响谁
- 正在权衡业界领袖关于超级智能公开表态的读者
- 尚未确认
- 该评论文章的具体论点、作者对超级智能的定义或时间表、发帖者真正的批评焦点
- 原始来源
- r/artificial · u/ScubadooX · 1 points · 0 comments · Discussion
Linked: https://www.nytimes.com/2026/10/01/opinion/ai-huang-gates-superintelligence.html?unlocked_article_code=1.FVE.S6CI.ffSNxGg7ByaP&smid=url-share
阅读原文发帖者称Sonnet 5.5用一个提示词生成了动态图形视频，费用为0美元 ↗
10月1日 21:31 JST
一位Reddit用户分享称，仅用一条提示词让Sonnet 5.5生成了动态图形视频的代码并以0美元完成。用户只提供了视觉方向，目标是一个可观的输出。
本站评价
轻信表面上的全能感，就像不看家电说明书就急着炒菜。一份报告显示简短的创意简报被变成了一段动画，但并不能保证下一次照样能用。就眼下而言，这看起来节省了钱，却没有拓展创作的主动权。
查看依据
- 影响谁
- 预算紧张、想尝试动态图形的个人创作者
- 尚未确认
- 发帖者使用Sonnet 5.5的具体资格（免费额度还是订阅包含）以及生成代码的运行或分享环境
- 原始来源
- r/artificial · u/Bladerunner_7_ · 1 points · 0 comments · Discussion
made the attached video with Sonnet 5.5 from a single prompt. gave it the concept and visual direction, and it generated the code for the motion graphics. this attempt cost me $0. wanted to see how well it could turn a brief into something worth watching. how's the result? would you change anything before posting it?
阅读原文双GPU运行vLLM的资源在GitHub公开 ↗
10月1日 19:25 JST
一名用户分享了用于在40系与50系两张NVIDIA显卡上联合运行vLLM的GitHub仓库。发帖人称在测试自家电脑极限时发现现有资料有限，于是公开了自己的方案。
本站评价
这是一个不想租用云端算力、只想在自家桌上跑推理的小型自助项目,是把AI当作周末硬件爱好的极客精神的延伸。媒体上关于前沿实验室的报道容易让人忘记,推理归根结底是电和金属在做工;如果这个仓库经得住考验,数据中心与卧室电脑之间的距离便会缩短一小步。
查看依据
- 影响谁
- 手头拥有两张NVIDIA显卡并尝试本地运行vLLM的折腾者
- 尚未确认
- 具体支持的显卡型号、是否经过验证、以及仓库的规模与更新计划
- 原始来源
- r/LocalLLaMA · u/Fz1zz · 1 points · 0 comments · Resources
i wanted to see how far i can push my PC and on the way i discoverd the resources are limited so i made my own and i hope it helps . [https://github.com/ExTV/dual-gpus-vllm](https://github.com/ExTV/dual-gpus-vllm)
阅读原文轮换使用五款AI浏览器数月后的笔记 ↗
10月1日 19:10 JST
作者在数月间轮换使用 Dia、 Comet、 Brave 和 Ace 等浏览器，记录了侧边栏对话、屏幕内回答、隐私拦截和跨标签操作等各自的特点。
本站评价
每款产品的便利来自不同的边界，所以与其说在挑选功能，不如说在挑选愿意长期承受的取舍。
查看依据
- 影响谁
- 正尝试把AI浏览器融入日常工作流的从业者
- 尚未确认
- 第五款浏览器的具体名称以及各产品的厂商信息
- 原始来源
- r/artificial · u/The_God_was_Here · 1 points · 0 comments · Discussion
Been swapping my daily driver every few weeks to see which of these is actually usable. Writing it down before I forget. No affiliation with any of them, I just have a problem. Dia: the chat sits in the address bar instead of a sidebar, which feels right. If you liked Arc you'll probably like this one. Comet: best at answering a question about what's already on screen. The search DNA shows. Less useful if what you want is help with your own tabs. Brave: a normal browser with good blocking that happens to have an assistant. Least ambitious AI of the five, best at ads out of the box. Ace: the one I didn't expect to stay on. It's more about doing something across tabs than summarising the one you're on, and it kept enough context between sessions that I stopped re-explaining myself. Newer than the others so you do hit rough edges. Edge: already installed, free, and the office stuff is genuinely useful if that's your world. Otherwise not much reason to be here. Where I landed is that some of these read for you and some do things for you, and those aren't the same product. What am I missing?
阅读原文探索人类的下一场进化飞跃——科学、技术与超人类主义 ↗
10月1日 16:20 JST
一个人工智能相关 subreddit 中出现一条帖子，链接到一个以超人类主义为主题的 YouTube 频道。发帖者 Transhumanism-Hub，关注生物技术领域。
本站评价
这个频道像是为“从技术一侧重写人类边界”这股潮流开设的对外橱窗。在接受其叙事之前，最古老的智识习惯——逐条核对主张是否经过同行评议或实证——依然有效。若其包装重在贩卖前景而非实质，保留怀疑是合理的。
查看依据
- 影响谁
- 想要一站追踪超人类主义最新视频的人
- 尚未确认
- 频道的运营方、更新频率以及其主张的可验证性均未提供。
- 原始来源
- r/artificial · u/Transhumanism-Hub · 1 points · 0 comments · Biotech
Linked: https://www.youtube.com/@Transhumanism-A/videos
阅读原文当AI摘要比顾问更早抵达客户,速度正在取代忠诚 ↗
10月1日 16:10 JST
澳大利亚企业家Mark Bouris发帖称,利率决议日早6点,客户已读过别家AI代理生成的摘要。他追问,卖出的并非忠诚度,而是速度。帖子随后转入对希伯来圣经押沙龙、大卫故事的联想式类比。
本站评价
从市场速度滑向经文类比的写法,暴露出自动化流程之下人仍会抓住古老叙事寻求安慰——这是再精简的技术栈也无法喂饱的饥渴。
查看依据
- 影响谁
- 在决议日与AI摘要工具争抢客户注意力的顾问
- 尚未确认
- 发帖者所在业务、覆盖市场及所指的AI代理均未说明。
- 原始来源
- r/artificial · u/cen6wkf · 1 points · 1 comments · Discussion
TL;DR: The rate decision lands. By 6 a.m. your client has already read someone else’s summary. Speed is selling. Is it loyalty? *I thought I can dig into my memories for a parallel. But my mind immediately brought me to the following story…* *David got wind of the death of his treacherous son, Absalom at the worst possible time of his life.* *David ran away into hiding when Absalom betrayed him and took the kingdom from him. David and his men found a friendly party in Mahanaim and set up defence.* *Absalom led the great rebellion army to find David. And David’s men met them in the woods.* *Of course, Absalom was no match with David’s men’s guerilla warfare tactics. Absalom died dangling with his long hair caught entangled with the tree branches.* *The scene was hilarious in itself – if not because of the tragedy.* *Ahimaaz asked Joab, the great general of David’s army, for permission to bring the good news back to David. But Joab flatly refused. Instead, he sends another messenger to deliver the news. Back then, there’s no AI agents to send email or digital newsletter. News was delivered on foot.* *Still Ahimaaz went anyway. He arrived earlier than the messenger, but said nothing. I think he’s smart – he didn’t want to be the bearer of bad news. Not helpful to David, though.* *When David finally got news from the messenger, he immediately went into a great moaning. He cried and lamented out loud.* *News went back to David’s men, as they file back to the camp. And suddenly, the celebratory vibe of the victory turns into deep shame. The men all felt they did something wrong.* *Joab saw it and perceive the existential crisis – because men are slowly leaving the camp, ditching David. So, Joab went and gave David a strong earful: "you love those who hate you and hate those who love you," and he warned that not o
阅读原文Anthropic机器人研究把“能做”与“划算”分开衡量 ↗
10月1日 14:34 JST
Anthropic 9月30日的研究估计，现有机器人在某些场景中可完成相当于美国工作时间34%的任务，但在成本上能与人类劳动力竞争的目前仅占工作时间的0.3%。研究使用 Claude 评估任务示例、运行环境与部署成本。
本站评价
在受控环境里运转和被嵌入真实流程是两回事——这就像偶尔为朋友下厨和每天撑起一家餐厅的区别。两个百分比之间的那段空白，才是真正的工作。如果机器人已经能在某些地方完成三分之一的任务，问题就不再是“能不能”，而是怎样的监督才能把这种可能变成流程。
查看依据
- 影响谁
- 想判断机器人能否真正落地自家业务的经营者
- 尚未确认
- 研究在“已评估的任务”与完整工作流程之间如何处理监督、故障与交接，仍未明确说明。
- 原始来源
- r/artificial · u/Crescitaly · 1 points · 0 comments · Discussion
Anthropic's September 30 study estimates that existing robots can perform tasks representing 34% of US working time in at least some settings. Yet it estimates they are cost-competitive with human labor for only 0.3% of working time today. Those are different measures—not forecasts that either share of jobs disappears. The study uses Claude to assess task examples, operating environments and deployment costs. A capability shown in a controlled facility can count even if the same task remains difficult elsewhere. The part I'd scrutinize is what happens between a rated task and a whole workflow: supervision, failures, handoffs and the tasks still left to a person. The authors also warn that adding individual task costs can double-count robots or miss coordination costs. Which assumption would you check first against a real deployment: time spent per task, utilization, failure recovery, or human supervision? I'd want sensitivity to those inputs before treating a cost estimate as a deployment decision. Source: [https://www.anthropic.com/research/what-work-can-robots-do](https://www.anthropic.com/research/what-work-can-robots-do) AI-assisted discussion; I haven't independently validated the estimates.
阅读原文Qwen Flash Next 的 MTP 工作已重新启动 ↗
10月1日 14:27 JST
Qwen Flash Next 在 llama.cpp 上的 MTP 相关工作已重新启动。新的量化文件已发布，相关 PR 也已提交。但该工作仍在进行中。
本站评价
这像是有人还没把整件工具拼完，就先换掉其中一个零件。调一个参数，就同时牵动另外三个变量。把主要用途押在一件尚未完成的零件上，等于让设计者的猜测替你定形。不过，这种局部的进展反而比一件光鲜的成品更有价值，因为它准确指出了哪个部位是坏的。
查看依据
- 影响谁
- 在 llama.cpp 上运行 Qwen Flash Next 的本地大模型使用者
- 尚未确认
- MTP 修复的具体内容、影响版本、性能差异、完成时间表
- 原始来源
- r/LocalLLaMA · u/jacek2023 · 1 points · 0 comments · News
If you're using MTP with Qwen Flash Next and llama.cpp, you can switch to: quants: [https://huggingface.co/ggml-org/Qwen3.8-Flash-Next-GGUF](https://huggingface.co/ggml-org/Qwen3.8-Flash-Next-GGUF) PR: [https://github.com/ggml-org/llama.cpp/pull/29761](https://github.com/ggml-org/llama.cpp/pull/29761) Please note that this is still wip
阅读原文