@nosherwan I'm going to be hated for this, but if you actually limit the choice between these four, I would pick GitHub.

GitLab frontend is badly designed, and also it's very heavy JavaScript.

BitBucket has very low limits as far as I remember (haven't used it for years) and for me it always had slow connection speed.

SourceForge inserted ads in installers once, the website itself is riddled with ads, they just can't be trusted at this point. They also do send unwanted emails with various FOSS-related news, but it's not always FOSS-related, and it's very low journalism in general (even by tech journalism standards)

GitHub still has the largest user base, but they will take your code to learn their AI (but at this point, it's not something you're safe from on other hostings either)

From what's not here:

Codeberg actually has somewhat large user base, but knowing it's non-profit... makes you kinda want to donate to them and it's not something everybody can do.

SourceHut is paid. And it has patches-over-email thing, something that's not for everybody. But their CI is great, includes all the well-known BSDs, Alpine and even arm64 machine (I guess it's emulated though)

@nosherwan >it's not something you're safe from on other hostings either

gonna elaborate here. I'm running closed Gitea for myself and my friends that barely has any presense in search engines, which still gets hammered by AI bots. There is literally just Linux and QEMU mirrors and they're still requesting random commits, logs and blames, which is the heaviest request for Gitea.

@nosherwan I don't get why they have to scan random pages, instead of cloning the whole repo and training their half assed LLMs on it.

But, yeah, imagine the intellectual skills of your typical LLM developer. You can't expect good technical solutions from this kind of people.

@a1ba @nosherwan Pretty sure if I'd run any kind of forge at this point I'd definitely disable/block the blame endpoint.

It's useful to just query remote servers for it, but if you consider spammy requests and the fact that blame is a bit too close to infinite ressource usage… better just make people clone the repo, specially as worst case a read-only git server can be mirrored, while git webview/frontend not so much.

@lanodan @nosherwan actually, yeah, I should look into how to disable it. Ideally only for not logged in users.