Since yesterday a lot of users in Europe found their workflows failing due to Github seemingly randomly throwing HTTP/401 on git clone/git pull when interacting with public repos without authentication.
It was now confirmed by staff member that this indeed is intentional and no further steps are planned at this point.
Codeberg’s couldn’t be much worse than github’s reliability since 2019
Codeberg only targets a subset of projects. For example, I no longer want most of my self-written code to be publicly available, but Codeberg only supports public repos.
Codeberg allows private repositories: https://docs.codeberg.org/collaborating/repo-permissions/
https://docs.codeberg.org/getting-started/first-repository/
The problem with Codeberg now is that there is a spectrum of AI usage between manually coding and AI slop that Codeberg chooses to ignore with their new policy.
I get it that’s their platform and their choice, and at some point I even looked for ways to support them financially if that meant I could migrate all my repos from GitHub - I wouldn’t mind paying for my use, “vibe coded” or not - but an intransigent LLM ban creates uncertainty for many of my active projects, and I can’t consider them a viable alternative to GitHub anymore.
So sure, I’ll take 3h of GH actions downtime a month over a platform ban. I’m sure I’m not alone there.
So, you should be fine with the measures against scraping, then?
That doesn’t affect me, but you can’t eat your cake and have it too. I’d rather have open source content actually open and easy to access, but GitHub has an availability issue and they’re trying to address it, so I don’t see this as a hostile move.
I’m sure if codeberg was nearly as popular as github, they’d be forced to restrict some clones too. Their current load is unprecedented, even for their standards.