Is Codeberg actually effective at preventing crawling of public code they host?

https://docs.codeberg.org/ci/

None of this is a defence of GitHub. But if you want to enact change, you have to understand the reasons why people remain in the status quo.

Personally I use Gitlab.

Also: GitHub is so established that for many people git and GitHub are the same thing.

Aside from previously established dominance and associated network effects, a whole lot of individually little things which add up to a lot.

> It's a shame this isn't as popular. It seems like developers, of all people, are willingly letting their code be AI piggybacked.

So long as the AI firms operate under the assumption (and courts so far in the US at least seem inclined to favor this view) that training AI on copyright-protected material isn't infringement, any publicly-exposed code is going to be subject to AI piggybacking, not just code hosted on Github.

I really created a github account to star other people's project and my keepassxc had got deleted by me messing around in my linux so I had lost access to my codeberg previous account and I think even my previous github account too but I went around to create a new github account but never a new codeberg account untill just recently (literally 1 hour ago lol)

for me I could star a lot of projects and show support and there is even github donations. Its not as if I like github but I am giving my reasoning as to why I think the reason is that github won and codeberg hadn't.

There are still a lot of people which use codeberg but a lack of awareness is also one part and the lack of people on codeberg. To me, like, I thought that if my project is on codeberg then it would get less stars (I was really chasing stars back then lol) and it would get less visibility and less people contributing and so on I think...

Doesn't also help when you need a github account anyways to contribute to a git project in the sense that you ask them an issue.

IIRC I wanted to ask a github issue on some project and that's why I had created my original account but then started hosting some code between codeberg and github from exclusively codeberg to then all code on github...

Now I am starting to take back on that by hosting things on codeberg again from a fresh account.

They are so fanatical that many groups are unable to use them.

Sourcehut for example is hostile towards cryptocurrency related projects.

Coderberg is hostile towards private repos.

The idea that I would choose a company because is from Europe instead of America, is kinda insane to be honest, I'm from Spain, Europe and my only peeve with products from America is that sometimes the cost to send products here is a bit too much for products like kinesis, aeron, books from nostarch, etc.

Good for Codeberg for giving the hosting service for free to FOSS projects, but there is no way I'm giving so much power to a few volunteers over my projects.

I wish GitHub would implement a feature to hide/private the projects I follow/star, that's the only thing I miss in GitHub.

That said, what can codeberg really protect against if they’re just a European take on GitHub?

[1] https://forgefed.org/

It was FUD when the fork was announced, it is FUD now. Look at commercial images and what differentiates them from MIT — it's pretty much just SAML and not much else. Their actual development policy is "you pay us for the feature you need — we build it under MIT and ship for everyone"; their collaboration with Blender is the most prominent example of this that I know of.

I've also been wondering whether to jump ship, and have been going by comparing release notes — how many features were shipped within the same period of time, which bugs were fixed, etc. I've seen no reason to migrate, Gitea continues to advance faster, even though Forgejo copies some of their commits that still apply relatively easily.

Forget about commit counts, issues closed, and other artificial metrics — they're significantly inflated on Forgejo's side by heavy use of bots (like bumping dependencies) and merge commits (which Gitea development process doesn't use). Look at release notes.