I’ve been on Codeberg for over a year now and the experience has been great. It has been around for a while, it’s fast, thanks to Forgejo, the self-hostable open-source software that Codeberg uses, which also offers great features.
However, it lacks a good CI/CD system. I feel like Woodpecker (the CI/CD system Codeberg uses) can’t do more complex things. Forgejo/Gitea have their own CI/CD system which is better, but Codeberg still uses Woodpecker.
But other than that, why isn’t Codeberg more widely adopted? Even privacy advocates continue to use GitHub, despite its acquisition by Microsoft. I agree with the sentiment that GitHub has a large user base, and its widespread adoption is undeniable, but I still think more people should try Codeberg or even self-host their own Forgejo/Gitea instances.
So, I’m curious to hear your perspective. What are the reasons that keep you tied to GitHub? Do the features and network outweigh the privacy concerns? Are there specific functionalities that you rely on and haven’t found elsewhere?
Holding back? I’m not held back. Codeberg would be a step back, I self host Forgejo and am so hyped up for forgefed.
I set up mirrors for my more important stuff to Codeberg and GitHub for visibility.
About CI/CD: does Codeberg not let you enable actions, which are basically the same as GitHub actions but for self hosting? That’s what I use for my self hosted CI. I think you can add your own workers for orgs, repos, and profiles too on Forgejo, should be doable on Codeberg too. (I don’t use Codeberg CI, only my own)
How do you feel about privacy/GDPR in relation to federated services like this? Seems a bit of a minefield and probably most all of those services are not technically legal.
Why exactly would it not be ok with the gdpr? I can’t think of anything right now. Having a few diverse isn’t really a new idea, it’s basically the www all over again and mastodon and lemmy &Co exist already.
Or are you referring to registering CI workers? That might be a bit of a problem, yeah, as you’re basically giving the git hoster remote code execution (on a docker container). Not really a problem if you host your own of course.
For one there’s no incentive for individuals running an instance to care about compliance in the first place, regardless of the actual issues at play. One obvious issue that comes to mind is the right to be forgotten. FOSS software can be easily modified and if servers don’t comply with such requests properly then your rights are being violated and good luck doing anything useful about it.
Does GDPR even apply to instances not hosted in countries covered by it? No.
It does. It applies to any service that has a single EU user. And that doesn’t mean someone in the EU. It means an EU citizen, even if they are living abroad.
I mean, they can say it but good luck enforcing it outside the EU’s legal jurisdiction.
Anyone who ever hopes to actually move or operate in the EU will be forced to comply. So an instance owner in the fediverse might operate their instance out of the US. Then the US enacts some law to force handing over user data. The server owner wants to move (themselves or the server) to the EU. Well, they’re now fucked.
Or if an instance owner wants to sell something on the site, guess you’re not selling to 50% of your users.
@tyler @AustralianSimon
GDPR applies only to people (even non-EU citizens) who “live” on the territory of EU. EU citizens who leave, don’t have the GDPR protection anymore. There was an affair last year when google started notifying people about transferring their account data to non-EU datacenters after it detected them connecting from a foreign IP when they went for a holiday to Thailand for a month. So clearly you have some misunderstandings of GDPR. Also GDPR prevents selling stuff??