July 7, 2026
Star-struck and locked out
Ask HN: Is GitHub preparing to go behind a login wall?
GitHub users are spiraling over signs the site may be harder to browse without signing in
TLDR: GitHub users noticed some public pages now fail or demand a sign-in, sparking fears that browsing open projects may get harder. Commenters are split between "this is anti-spam cleanup," "AI traffic is breaking everything," and "please stop calling a login screen a paywall."
Panic, paranoia, and a tiny bit of "calm down, everybody" broke out after a Hacker News user asked whether GitHub — the giant website where millions of people store and share code — is quietly sliding behind a sign-in screen. The spark? Some public pages, especially lists of people who "starred" a project, have started showing errors or asking users to log in. For open-source fans, that hit a nerve fast: if public projects become less public, that is a big cultural shift.
The comments instantly split into camps. The prepper crowd basically said: don’t wait around for Microsoft and GitHub to explain themselves, just make backup plans and keep copies elsewhere. Others rushed in with a less sinister theory, pointing to GitHub’s own note saying some public lists are being restricted because spammers were scraping user data. That triggered the classic internet argument: is this the beginning of a wall, or just anti-spam housekeeping?
Then came the hottest blame game of all: AI. One commenter claimed the whole platform is "cracking under the AI boom," while another said AI has made GitHub more exciting because they now browse trending projects more. And in peak nitpick energy, one user jumped in to remind everyone that a login wall is not the same thing as a paywall — a very Hacker News move. The result: a thread full of suspicion, survival tips, and the usual deliciously nerdy semantics war.
Key Points
- •The Ask HN post reports that GitHub stargazer pages sometimes return 404 errors for users who are not logged in.
- •The poster asks whether GitHub has started blocking access to some functions or pages for users without accounts.
- •The article includes a specific example: the stargazers page for the repository tirrenotechnologies/tirreno.
- •A cited GitHub changelog says public lists of stargazers and watchers are being restricted.
- •GitHub’s quoted reason is that these public lists have been misused to collect user data for spam activities.