Sentiment for/against GitHub aside... "Why X are doing Y" articles like these pretend that the premise of "X are doing Y" is true, conveniently skipping to the "Why" before proving that the premise is even accurate in any meaningful way. This is why I never buy headlines that start out with "Why". > developers are ditching Proceeds to list but a handful of remotely meaningful repos against the hundreds of thousands o…
I can't help but think at this point that Ghostty's "departure" from GitHub is unserious. It's been two and a half months now and not even a single peep of discussion about where they may be migrating to or what they may be doing.
Why developers are ditching GitHub for Codeberg and self-hosting alternatives
251–260 of 289 posts
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#252Sentiment for/against GitHub aside... "Why X are doing Y" articles like these pretend that the premise of "X are doing Y" is true, conveniently skipping to the "Why" before proving that the premise is even accurate in any meaningful way. This is why I never buy headlines that start out with "Why". > developers are ditching Proceeds to list but a handful of remotely meaningful repos against the hundreds of thousands o…
You can just insert the word "some" as required.
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#253Earlier quoted context omitted.
You’re so right. I have a public-facing Forgejo server. Before configuring Anubis, scrapers were sending it about 600K requests per day. Copying and pasting from my blog post about it: * For every Git commit, fetch the version of every file in the repository at that commit. * See git blame for every file at every commit. * Attempt to download the archive of each repo at every commit. * Run every possible pull request…
What do you use to monitor this? I don't really keep a close enough eye on my services to know what the traffic is doing (and haven't had any issues) but maybe I should start
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#254Earlier quoted context omitted.
You’re so right. I have a public-facing Forgejo server. Before configuring Anubis, scrapers were sending it about 600K requests per day. Copying and pasting from my blog post about it: * For every Git commit, fetch the version of every file in the repository at that commit. * See git blame for every file at every commit. * Attempt to download the archive of each repo at every commit. * Run every possible pull request…
That's crazy. So 600,000 someones are absolutely starved for data. Or one someone with too much money and too little sense misplaced a decimal point in their ScraPy setup?
And the cruel irony is that these are FOSS Git repos I'm publicly sharing. I'd've been fine with them cloning the repo and analyzing away to their heart's content. That's not the way their scraper's wired, though.
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#255Earlier quoted context omitted.
one reason (among others) — compliance. a corporate/b2b saas environment without stuff like this is often a non starter. - SOC2 - ISO/IEC 27001:2022 - ISO/IEC 27017:2015 - ISO/IEC 27018:2019 - VPAT 508 https://about.gitlab.com/security/ no mention of these on the forejo site, so i can’t put “our internal software is all SOC2/ISO NUMBER compliant” as a bullet point on a slide deck. it is theatre. but it’s industry the…
Aren't those about organizational processes instead of just specific software features? For example, I don't think self-hosting gitlab is enough to claim ISO/IEC 27001, just based on this snippet from wikipedia: > ISO/IEC 27001 requires that management: > Systematically examine the organization's information security risks, taking account of the threats, vulnerabilities, and impacts; > Design and implement a coherent…
probably not. but it does mean you can focus on the rest of your stack rather than having to go through every single process from the ground up.
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#256Earlier quoted context omitted.
codeberg's one job gets interfered with by freeloaders hammering expensive views (like git blame) inconsiderately.
Couldn't they just rate limit them? Are they literally using a new IP for every request?
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#257Earlier quoted context omitted.
Github is an extra layer of backup, among normal backups. [edit] Notable reasons: - Github runners went oftenly out of space & they were slow. With self hosted runners I don't have these issues anymore because I control the hardware. Previously I was paying Docker Build Cloud/Depot for performance + Github Pro for extra minutes. Now it's zero cost, superb performance and unlimited minutes. - I have a centralized regi…
If you're using github as a backup, then whatever you say you own, they also own. So I still don't understand why you are self-hosting and using github as an extra layer of backup. Seems philosophically inconsistent.
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#258Earlier quoted context omitted.
Which early adopters exactly? The most prominent example they gave is ghostty which has existed for just a couple of years, notwithstanding the fact that the owner published a spiel about how he's personally been using it for longer.
An early adopter is someone who is first in line to try something new, usually because they're willing to build part of the new thing with their own hands. Just look at what projects are on any of the third-party forges, those are the early adopters of post-github tech. I would also be one of them, but I'm not actually off Github yet. That's because I haven't quiite finished building the thing I'm going to move to.
I'm saying that Ghostty, which is ~5 years old, cannot be called an early adopter of GitHub, which is 18 years old.
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#259Earlier quoted context omitted.
Github is an extra layer of backup, among normal backups. [edit] Notable reasons: - Github runners went oftenly out of space & they were slow. With self hosted runners I don't have these issues anymore because I control the hardware. Previously I was paying Docker Build Cloud/Depot for performance + Github Pro for extra minutes. Now it's zero cost, superb performance and unlimited minutes. - I have a centralized regi…
If you're using github as a backup, then whatever you say you own, they also own. So I still don't understand why you are self-hosting and using github as an extra layer of backup. Seems philosophically inconsistent.
I own the git, the runners, the registry etc and just use GH for backup. GH cannot interrupt suddenly my business.
Re: Why developers are ditching GitHub for Codeberg and self-hosting alternatives
#260As a developer who ditched Github and decided to self-host, there is only one reason. It's not technical difficulties, politics, nor AI. It's Microsoft. Like Apple, Facebook etc, I have a deep loathing for Microsoft and I want to remove as much of it from my life as I am able. I now run Git on a pi using Gitea and Forgejo. I can now upload files of a size unheard of in GitHub, Claude can make a PR by itself that I ca…