GitHub 正在开始限制部分先前公开的数据的访问权限。
5 分•作者: punkpeye•3 个月前
我收到一条数据库异常的警报：用于跟踪星标用户的一个表突然变空了。
原来是 GitHub 私自更改了获取星标用户的接口，使其返回空响应。
https://github.blog/changelog/2026-06-30-upcoming-access-restrictions-to-public-api-endpoints-and-ui-views/
GitHub 没有通过电子邮件或其他任何方式提前通知开发者。
由于我们每次获取星标用户时都会覆盖之前的数据，这导致我们多年来收集的所有数据被清空。在我们的案例中，这些数据用于在浏览 MCP 服务器目录时定制用户体验——GitHub 作为用户“收藏的服务器”的真实数据来源——这是一个完全合法的用例，可以围绕 GitHub 的公共数据构建社区。还有许多类似的用例。
用 GitHub 的话说，他们这样做是为了防止“垃圾信息”，但这实际上只是 GitHub 越来越严格地控制其数据和社区。可悲的是，这个为开源而生的平台已不再开放。
查看原文
I woke up to an alert about a database anomaly: one of the tables that we use to track stargazers was suddenly empty.<p>Turns out GitHub quietly made the endpoint that fetches stargazers return an empty response.<p>https://github.blog/changelog/2026-06-30-upcoming-access-restrictions-to-public-api-endpoints-and-ui-views/<p>No email or any other warning was shared with developers.<p>Because we were overriding stargazers every time we fetch them, this resulted in wiping all the data that we have collected over the years. In our case, this data was used to customize user experience when browsing MCP server catalog – GitHub served as the source of truth of their 'favorite servers' – a completely legitimate use case to building a community around GitHub's public data. Many more use cases like this exist.<p>In GitHub's own words, they are doing this to prevent "spam", but this is really just GitHub increasingly gatekeeping their data and community. Sadly, the platform that was built for open-source is no longer open.