Live data from Hacker News

Moving from GitHub to Codeberg, for lazy people

unterwaditzer.net

371–380 of 385 posts

Re: Moving from GitHub to Codeberg, for lazy people

#371

Earlier quoted context omitted.

> ...that really isn't that hard. Until the AI scrapers[1] come for you at 5k requests per second and you're doing operations in hard-mode. 1. Most forges have http pages for discoverability. I suppose one could hypothetically setup an ssh-only forge and statically generate a html site periodically, but this is already advanced ops for the average Github user

fail2ban

... is snakeoil in the era of (undeservedly) respected megacorporations operating botnets.

Re: Moving from GitHub to Codeberg, for lazy people

#372
post #208

Earlier quoted context omitted.

To me that sounds like Github does too many things, not that Codeberg does too few.

To me, and devs at large (given their market share), that sounds like convenience.

Either take some responsibility and properly evaluate what that convenience means for you long term or don't complain when they leverage that vendor lock in at your disadvantage.

Re: Moving from GitHub to Codeberg, for lazy people

#373
post #112

The truth is that I publish OSS projects on GitHub because that's where the community is, and the issues/pull requests/discussions are a bonus. If I just want to host my code, I can self host or use an SSH/SFTP server as a git remote, and that's usually what I do.

> I publish OSS projects on GitHub because that's where the community is And so we go, forever in circles, until enough of us move to other platforms regardless of where the existing community is. Just like how GitHub found its community in the early days, when most people (afaik) was using SourceForge, if anything. "The community" will always remain on GitHub, if everyone just upload code to where "the community" al…

There are plenty of projects that did just fine for decades without the network effects of a centralized forge. If you project is valuable, people will come to you.

Re: Moving from GitHub to Codeberg, for lazy people

#374
post #112

The truth is that I publish OSS projects on GitHub because that's where the community is, and the issues/pull requests/discussions are a bonus. If I just want to host my code, I can self host or use an SSH/SFTP server as a git remote, and that's usually what I do.

In particular a number of other projects assume that you have a GitHub account. https://github.com/rust-lang/crates.io/issues/326 has been open for literally a decade without any meaningful work. If you want to publish a Lean software packages on Reservoir, the official Lean package registry, their requirements ( https://reservoir.lean-lang.org/inclusion-criteria ) not only specify a GitHub project specifically, but…

That's one advantage of using "obsolete" programming languages - the community isn't designed about what online services are currently hip.

Re: Moving from GitHub to Codeberg, for lazy people

#375
post #156

Earlier quoted context omitted.

Considering that "the community" is now filled with vibe coding slop pull requesters, and non-coders bitching in issues, the filter that not-github provides becomes better and better. Of course, that mostly goes for projects big enough to already have an indepedent community.

Not to contradict you, but there's another important aspect to 'community' besides the bad contributors and the entitled complainers. That's discoverability. How do you discover a project that may be hosted anywhere on the dozens of independent forges out there? Searching each one individually is not a viable proposition. The search often ends on the biggest platform - Github. I'm not trying defend github here. The l…

I have not once searched for projects on GitHub specifically, it's always just a general web search or a referral from another website/forum/person.

Re: Moving from GitHub to Codeberg, for lazy people

#377
post #120

Earlier quoted context omitted.

I don't understand the hype around CI and that it's supposedly impossible to run something like that without Git, let alone Github. Like sure, a nice interface is fine, but I can do with a simpler one. I don't need a million features, because what is CI (in practice today, not in theory)? It's just a set of commands that run on a remote machine and then the output of those commands is displayed in the browser and it…

> just have some sane rules and make everyone follow them (like run unit tests before submitting a PR) and thus you discover the value of CI

You could also just get managers that are not worthless.

Re: Moving from GitHub to Codeberg, for lazy people

#378

Earlier quoted context omitted.

Maybe I'm too old school, but both GitHub and Codeberg for me are asyncronous "I want to send/share the code somehow", not "my active workspace I require to do work". But reading > the worst thing ever for me as a developer is having the urge to code and not being able to access my remote. Makes it seem like GitHub/Codeberg has to be online for you to be able to code, is that really the case? If so, how does that hap…

For me it's a soft block rather than a hard block. I use multiple computers so when I switch to the other one I usually do a git pull, and after every commit I do a push. If that gets interrupted, then I have resort to things like rsyncing over from the other system, but more than once I've lost work that way. I'm strongly considering just standing up a VM and using "just git" and foregoing any UI, but I make use of…

Git supports having multiple remotes so you can have your own private git repo on any ssh server for sharing between your own machines and only need to rely on the public host for sharing with others.

Re: Moving from GitHub to Codeberg, for lazy people

#379

Earlier quoted context omitted.

Maybe I'm too old school, but both GitHub and Codeberg for me are asyncronous "I want to send/share the code somehow", not "my active workspace I require to do work". But reading > the worst thing ever for me as a developer is having the urge to code and not being able to access my remote. Makes it seem like GitHub/Codeberg has to be online for you to be able to code, is that really the case? If so, how does that hap…

For some projects, the issue tracker is a pretty integral part of the documentation. Sure, you can host your own issue tracker somewhere, but that's still shifting a center point somewhere, in a theoretically decentralized system. I've frequently wished the issue tracker was part of the repository. Also -- love them or hate them -- LLMs would probably love that too.

If it's so integral then you should really make sure that its something you can control and operate longer than a single service provider feels like giving out freebies.

Re: Moving from GitHub to Codeberg, for lazy people

#380

Earlier quoted context omitted.

Either I am very lucky or what I am doing has zero value to bots, because I've been running servers online for at least 15 years, and never had any issue that couldn't be solved with basic security hygiene. I use cloudflare as my DNS for some servers, but I always disable any of their paid features. To me they could go out of business tomorrow and my servers would be chugging along just fine.

Sometime it is not security , it could be just bandwidth or CPU. I have website small enough not to attract too many bot, but sometime, something very innocent can bring my website down. For example, I put a php ical viewer.. and some crawler start loading the calendar page, taking up all the cpu cycle.

If your website has measurable CPU load before your uplink is saturated then you're probably doing something wrong.
Post reply on HN