Live data from Hacker News

GitHub to Codeberg: my experience

eldred.fr

111–120 of 140 posts

Re: GitHub to Codeberg: my experience

#112
post #82

I lost what little respect I had for Codeberg when they tried to spin a teenager exploiting an opportunity to spam/troll[1] that GitHub had solved several years prior[2] into "hate campaigns from far-right forces" that "endanger free/libre software projects" so they could toot their own horn at how good they were in the face of adversity[3] (and generally have a good moan about the right-wing) instead of admitting th…

If they were genuinely just attempting to "troll" by spamming (which is a pretty lame thing to do to begin with), they wouldn't have had to use a racist slur in their message. The fact they did makes their intent pretty clear. If a project taking a stance against people spamming the n-word makes you lose respect for them, that says a lot more about you than the project.

Trolling is trying to piss off as many people as possible, using such a word achieved exactly that.

Re: GitHub to Codeberg: my experience

#113
post #105
post #104

Earlier quoted context omitted.

I don't think it's relevant to this specific instance, but AFAIK ActivityPub doesn't inherently prevent name portability. It's just that almost all implementations currently don't allow it (and I wouldn't expect Forgejo's either). Of course, the practical downside of Tangled is also that it only has network effects within the ATmosphere, i.e. you still can't reach GitHub users.

First of all, non-standard extensions to federated protocols have a pretty rough history. Even when an extension reaches median adoption (rare, I assert), the long-tail adoption is dismal. For something as fundamental as Second of all, how could this just be an implementation-specific extension? The failure mode (of a client not supporting the extension) would be outright broken. To have name portability, the client…

I'm not intimately familiar with the spec, so don't take my word as gospel, but as I understand it, current implementations already do name discovery. It's just that every implementation hardcodes the server name. IIRC some people have applied some kludge where they put a .well-known document on their own server to point to their instance's account, but it's still pretty spotty without that server being actively aware of that identifier. But (again, if I'm understanding correctly) servers could be updated/written to support that properly.

Re: GitHub to Codeberg: my experience

#114
post #113
post #105

Earlier quoted context omitted.

First of all, non-standard extensions to federated protocols have a pretty rough history. Even when an extension reaches median adoption (rare, I assert), the long-tail adoption is dismal. For something as fundamental as Second of all, how could this just be an implementation-specific extension? The failure mode (of a client not supporting the extension) would be outright broken. To have name portability, the client…

I'm not intimately familiar with the spec, so don't take my word as gospel, but as I understand it, current implementations already do name discovery. It's just that every implementation hardcodes the server name. IIRC some people have applied some kludge where they put a .well-known document on their own server to point to their instance's account, but it's still pretty spotty without that server being actively awar…

Not to split hairs, but that sounds more like plain hackery rather than proper extension. Let alone a viable future. I don't doubt what you say that it's possible in the most technical sense of possibility. But actually possible, in this world where we live? No, doesn't seem like it.

Re: GitHub to Codeberg: my experience

#115
post #75

Codeberg is a fork of Gitea, itself a fork of Gogs. Both forks originated for "philosophical" reasons, not technical ones and Joe Chen (@unknwon on GH) deserves a lot of the merit for building a clean forge in Go mostly by himself.

> Codeberg is a fork of Gitea, itself a fork of Gogs. Codeberg is a website powered by Forgejo which is a fork of Gitea. > Both forks originated for "philosophical" reasons, not technical ones Gitea forked because one developer was the only owner of Gogs' repository and refused to share maintaining rights. The fork was more "practical" than "philosophical". Forgejo forked when a leading developer secretly created a c…

Seems like a 'you either die a hero or you live long enough to become the villain' type of behaviour, which is not uncommon to see in projects like these. Let's hope Codeberg doesn't end up in the same bucket.

Re: GitHub to Codeberg: my experience

#116
post #75

Codeberg is a fork of Gitea, itself a fork of Gogs. Both forks originated for "philosophical" reasons, not technical ones and Joe Chen (@unknwon on GH) deserves a lot of the merit for building a clean forge in Go mostly by himself.

How long do you think until the inevitable community split into the Codeberg People's Front and the People's Front of Codeberg over some minor ideological disagreement?

Codeberg will use the forgejo fork that keeps being free, I guess.

Re: GitHub to Codeberg: my experience

#117

Are there any alternatives to Github that offer similar bang for the buck? Particularly for very small teams or solo devs that need private repos? The author here specifically mentions Codeberg, which seems like it's just for FOSS projects.

GitLab. There's also the option of self hosting it on a cheap server if you don't like cloud services.

Unfortunately, GitLab is no longer Fit for Purpose since it caps the maximum size of Merge Requests (aka PRs), and anything over that size just isn't shown in the Merge Request.

This bit us recently at my work where there was an important MR needing review, and over 1/2 of it couldn't be viewed in the GitLab web interface by any means.

It's a (mis) "feature" they're aware of, and have no plan to fix before 2027 at the earliest.

Needless to say, we're migrating off it and recommend others do the same.

Re: GitHub to Codeberg: my experience

#118

I've noticed that several projects on the front page today (and over the past few days) are migrating away from GitHub. Is there any recent event or broader trend that explains this shift?

I suspect GitHub - and, to some extent, Microsoft at large - is going through something of a trust thermocline[1] event right now. There's been frustration brewing with GitHub as an open source platform for a while, but not enough for any one project to leave by itself; but over time enough has built up that various projects decided they had the last straw, and it's getting to be a bit viral via the HN front page.

I think it remains to be seen how large this moment actually is, but it's something I've been thinking about re: GitHub for a while now. Also, I suspect the unrest around Windows' AI/adware enshittification and the forced deprecation of Windows 10 are casting a shadow on everything Microsoft-ish at the moment, too.

[1] The original Twitter thread that brought this up as a concept is https://threadreaderapp.com/thread/1588115310124539904.html. This is in the context of digital media outlets, but I think it's easy to see how it can apply more broadly. There are some other articles out there for the searching if you're interested.

Re: GitHub to Codeberg: my experience

#119
post #115

Earlier quoted context omitted.

> Codeberg is a fork of Gitea, itself a fork of Gogs. Codeberg is a website powered by Forgejo which is a fork of Gitea. > Both forks originated for "philosophical" reasons, not technical ones Gitea forked because one developer was the only owner of Gogs' repository and refused to share maintaining rights. The fork was more "practical" than "philosophical". Forgejo forked when a leading developer secretly created a c…

Seems like a 'you either die a hero or you live long enough to become the villain' type of behaviour, which is not uncommon to see in projects like these. Let's hope Codeberg doesn't end up in the same bucket.

That's the reason I don't want to jump on the Codeberg bandwagon just yet, although I'm very interested into self-hosting Forgejo.

I'd love to see something else though, a way to have repositories discoverable across all possible centralized or self-hosted services out there. What I actually do love about GitHub is that from time to time it manages to find for me some quite interesting projects and people to check out.

Post reply on HN