Orange AI@oran_ge · 4月27日48

昨天参加开放麦，听到最好笑的分享： GitHub 正在成为 AI 界的小红书。 三个维度论证： 1. Star 从"我用了好使"退化成"这个故事让我兴奋"， 2. README 从技术文档变成营销 Landing Page， 3. Star 数还能花钱买，20块钱就能买100个。 笑完之后发现，好像真的是这样。

译推文以开放麦分享为引，尖锐指出GitHub在AI浪潮中正演变为类似“小红书”的社区。核心论证围绕“星标”功能异化展开：其一，Star从实用价值认可退化为对项目叙事的情感共鸣；其二，项目README从技术文档转变为营销导向的落地页；其三，Star数量出现可购买现象，市场价约20元人民币可购100个。这一观察揭示了开源平台在热度驱动下，其核心评价体系与内容生态正在发生显著偏移。

Peter Steinberger 🦞@steipete · 4月27日40

Excited that GitHub shows real numbers here again. We been closing over 10k issues and close to 5k PRs this week thanks to clawsweeper and clownfish. Overall since December: 27k issues / 30k PRs closed.

译很高兴看到GitHub再次在此展示真实数据。本周我们借助clawsweeper和clownfish已关闭超过1万个问题及近5千个PR。 自12月以来总计：关闭2.7万个问题 / 3万个PR。

Peter Steinberger 🦞@steipete · 4月19日

🎚️CodexBar 0.21 Abacus AI provider, Codex Pro $100 support, safer OpenAI web extras, fixed local cost scanning, z. ai 5h quotas, Antigravity/Cursor/Ollama fixes, faster refreshes, macOS 26 icon fix and more. The big issue with too much CPU usage was an OpenAI web fetch and is now disabled for new installs. Also keychain issues are resolved. Shoutout to @RatulSarna for maintaining. https://github.com/steipete/CodexBar/releases/tag/v0.21

译🎚️CodexBar 0.21 Abacus AI 提供商、Codex Pro $100 支持、更安全的 OpenAI 网页扩展、修复本地成本扫描、z. ai 5小时配额、Antigravity/Cursor/Ollama 修复、更快的刷新、macOS 26 图标修复等等。 CPU 占用过高的主要问题是 OpenAI 网页获取，现已对新安装禁用。钥匙串问题也已解决。感谢 @RatulSarna 的维护。https://github.com/steipete/CodexBar/releases/tag/v0.21

Rohan Paul@rohanpaul_ai · 4月16日

This paper shows that GitHub stars can be bought at scale, and that the distortion now bleeds into security. The authors identify 6 million suspected fake stars tied to 18,617 repositories. That matters because stars are not just vanity on GitHub. They are a shortcut people use to decide what looks credible, useful, or safe enough to try, even though earlier work already suggested stars are only a rough proxy for real adoption. The problem is not just inflated popularity, but the way a weak social signal becomes infrastructure for malware, spam, and low-effort hype once enough people treat it as evidence. The paper’s detection strategy is clever because it does not need to prove intent account by account. It looks for behavioral signatures that are hard to fake at scale: throwaway accounts with almost no activity, and coordinated “lockstep” bursts where many accounts star many repositories within short windows. What they find is ugly. Fake-star activity surged in 2024, most flagged repositories were later deleted, many appear to have been phishing or spam, and the surviving non-malicious-looking targets cluster in predictable status games like AI, blockchain, tools, and demos. The most interesting result is about incentives. Fake stars do appear to buy a little real attention for less than two months, but the effect is far smaller than genuine popularity and turns negative over time, which suggests that social proof can open the door but cannot compensate for weak underlying substance. Once a platform’s easiest visible number starts standing in for trust, attackers do not need to beat the system completely; they only need to be believable for a moment. ---- Paper Link – arxiv. org/abs/2412.13459 Paper Title: "Six Million (Suspected) Fake Stars in GitHub: A Growing Spiral of Popularity Contests, Spams, and Malware"

译研究识别出GitHub上600万个疑似伪造星标，涉及18,617个仓库。2024年此类活动激增，大量被用于钓鱼、垃圾信息及恶意软件传播，重灾区集中在AI、区块链等领域。检测通过分析一次性账户和"同步"爆发等行为特征实现。假星标虽能在短期内带来真实关注，但长期效应为负，无法弥补内容匮乏。当星标这类易见的社交信号被当作信任基础设施，攻击者只需制造瞬间可信性即可实施攻击，这对开源生态构成系统性威胁。

Satya Nadella@satyanadella · 4月11日

In GitHub Copilot CLI, you can now leverage a multi-model reflection loop as a reviewer. Super helpful for catching issues early before they compound.

译GitHub Copilot CLI 推出"Rubber Duck"代理功能，支持多模型反思循环审查。系统自动调用不同 AI 家族模型进行交叉评审，官方数据显示该机制能有效提前发现代码问题，避免错误累积。

Peter Steinberger 🦞@steipete · 4月9日

GUYS WE FOUND THE GUY WHO BUILT THE GITHUB MCP SERVER

译大伙快看，我们找到了那个构建 GitHub MCP Server 的开发者！推文以兴奋的语气宣布了这一发现，并附上了相关链接。

Jeff Dean@JeffDean · 4月8日

Hedged requests (apparently inspired by the Tail at Scale paper by myself and Luiz Barroso) applied within a single machine to replicating data across DRAM channels and issuing reads to all channels, using the one that comes back first. ~5-15X reduction in p99.99 read latency. https://github.com/LaurieWired/tailslayer/blob/main/README.md Cool stuff, @lauriewired! Accompanying video forwarded to me by a friend, which is how I learned about it: https://www.youtube.com/watch?v=QFi2WVGfXMQ

译受 Tail at Scale 论文启发的 Hedged requests 技术被用于单机 DRAM 多通道场景，通过向所有通道并发发送读取请求并采用最快响应，将 p99.99 读取延迟降低 5-15 倍。实现该方案的 tailslayer 项目已开源。

Peter Steinberger 🦞@steipete · 4月8日

CodexBar 0.20 is out! 🎚️ 🆕 New providers: Perplexity + OpenCode Go 🔄 Switch Codex accounts without re-login 🔧 Fixed Claude token/cost inflation from dupes 📊 Cost history merges session usage into provider history 16 providers tracked. One menu bar. https://github.com/steipete/CodexBar/releases

译CodexBar 0.20 版本发布，新增 Perplexity 和 OpenCode Go 提供商支持，无需重新登录即可切换 Codex 账户，并修复 Claude token 重复计费导致的成本虚高问题。成本历史记录现支持合并会话数据，目前共追踪 16 家提供商。

OpenAI Developers@OpenAIDevs · 4月1日

Review issues Address feedback Commit changes Open pull requests @GitHub plugin in the Codex app.

译Codex 应用新增 @GitHub 插件，支持在应用内直接审查 Issues、处理反馈、提交代码更改及发起 Pull Requests，实现 GitHub 工作流一站式操作。

Deedy@deedydas · 3月25日

There’s a GitHub repo called MoneyPrinter with 20k+ stars. Its entire purpose is generating internet slop for profit (yes, including Twitter bots).

译GitHub 仓库 MoneyPrinter 获星超 2 万，其唯一功能是通过自动生成互联网垃圾内容（包括 Twitter 机器人）来牟利。

Andrej Karpathy@karpathy · 3月9日

The next step for autoresearch is that it has to be asynchronously massively collaborative for agents (think: SETI@home style). The goal is not to emulate a single PhD student, it's to emulate a research community of them. Current code synchronously grows a single thread of commits in a particular research direction. But the original repo is more of a seed, from which could sprout commits contributed by agents on all kinds of different research directions or for different compute platforms. Git(Hub) is *almost* but not really suited for this. It has a softly built in assumption of one "master" branch, which temporarily forks off into PRs just to merge back a bit later. I tried to prototype something super lightweight that could have a flavor of this, e.g. just a Discussion, written by my agent as a summary of its overnight run: https://github.com/karpathy/autoresearch/discussions/43 Alternatively, a PR has the benefit of exact commits: https://github.com/karpathy/autoresearch/pull/44 but you'd never want to actually merge it... You'd just want to "adopt" and accumulate branches of commits. But even in this lightweight way, you could ask your agent to first read the Discussions/PRs using GitHub CLI for inspiration, and after its research is done, contribute a little "paper" of findings back. I'm not actually exactly sure what this should look like, but it's a big idea that is more general than just the autoresearch repo specifically. Agents can in principle easily juggle and collaborate on thousands of commits across arbitrary branch structures. Existing abstractions will accumulate stress as intelligence, attention and tenacity cease to be bottlenecks.

译autoresearch的演进方向应是异步大规模协作，类似SETI@home模式，目标并非模拟单个PhD学生，而是构建多agents研究社区。当前Git/GitHub的主分支机制限制了分布式创新，未来应允许agents在任意分支并行探索不同方向，通过Discussion或PR分享发现而非合并代码。随着智能体算力与注意力瓶颈消失，现有代码协作抽象将面临根本性重构。