Wikipedia's Cleanup of AI-Generated Content
维基百科 WikiProject AI Cleanup 志愿者正在开发工具,识别并移除违反网站规范的 AI 生成内容,排查重点包括细微写作结构和不支持正文主张的引文。
维基百科 WikiProject AI Cleanup 志愿者正在开发工具,识别并移除违反网站规范的 AI 生成内容,排查重点包括细微写作结构和不支持正文主张的引文。
WD 内部测量显示,一段 8 秒 AI 视频(用户拿到的是 3.97MB 的 720p 文件)在后端留下超过 500MB 关联数据,是输出文件体积的 130 倍。
A Reddit post argues small-model agent stacks are not default for business reasons, not capability limits: Gemma 4 31B reaches 86.4% on tau2-bench, and DeepSeek V4-Flash output tokens are priced about 89x below Claude Opus 4.6. The operational risk is verification, because 7–9B models produced broken reasoning for roughly half to two-thirds of correct answers in a cited audit.
Why it matters: The post argues small-model agent stacks stay niche because of business risk and validation cost, not capability, citing Gemma 4 31B's 86.4% on tau2-bench and DeepSeek V4-Flash pricing.
The article frames agent filesystems as a three-stage shift from raw context to memory systems to filesystem-as-context, covering design choices from Turso, Anthropic, Vercel, and Manus, and listing four overlooked blind spots.
Why it matters: The piece traces external agent memory through three generations, from filling the context window to vector databases to treating the file system as context.
Karpathy uses Obsidian and local Markdown to build a personal wiki, stores source material in a RAW folder, then has an LLM generate summaries, indexes, concept pages, links, and visualizations. The setup can answer questions over the wiki and write reports or new files, but the post also says AI-generated content can pollute the corpus and should be separated from trusted sources; the post does not disclose the model, scale, or automation details.
Why it matters: Karpathy published his full pipeline for turning raw material into a local Markdown wiki with an LLM, from summaries and indexing to asking questions and generating reports.
Jack Clark says his research agents processed thousands of papers while he hiked or slept, and Claude finished site scraping, embeddings, local vector search, and a GUI in under one hour. The post confirms multi-agent retrieval, cross-checking, and report generation; it does not disclose model versions, cost, failure rate, or benchmark data. The point to watch is workflow friction dropping enough for AI to shift from single prompts to ongoing delegated work.
Why it matters: A concrete account of research agents running unattended, with the time saved and the tooling built around them.