Since my repos are spread across multiple instances, I deal won codeberg only intermittently and it looks like the 504s are about 2-3 weeks old. Not good, but just outside of the time I got busy in a repo that's not on codeberg.
As for gitlab's interface, I guess it's like switching from new reddit to lemmy, it's different and you babe to get used to it. While quitting Github, I actually came to really appreciate Gitlab's interface. It wasn't easy at the beginning, but now I actually prefer it to GitHub's interface.
If the people you asked are longtime Github users and only use or used Gitlab a few times, I'm not surprised they don't like it.
Radicle is better than it was when I first tried it. For a person who doesn't like the CLI, it's probably utterly horrific, but feature-wise, it's a distributed sourceforge. They still have a ways to go:
no notifications for anything like patches or comments
no CI
web interface is read-only
electron GUI is... Electron but makes its usage sane(r) but I tested that long ago
doesn't support huge repos e.g >1GB and it just won't distribute
But if the goal is just to publish code and have a distributed backup, radicle is very good at that.
You think it sucks because you're used to GitHub's interface. I really dislike the github interface after having left it a few years ago. Gitlab's interface is, to me, so much better and a breath of fresh air (even though it might look like the old old Github).
As for forgejo, I agree, once they get functional federation and a good CI (not a shitty Github actions clone), github and Gitlab can really fuck off. Gitlab might become a "competitor" once they have federation, but they only will do that if forgejo takes off sue to federation.
I use codeberg too and am not experiencing the problems you have, but it might be a location thing.
Otherwise, Gitlab has been good to me. Despite their descent into AI and rejection of federation, they have are still a better than GitHub. The CI is still light years ahead of GitHub Actions. What's your beef with Github?
Why are you referencing students BTW? Are you a professor? Do you have any pull? Then you should get your university to setup a forgejo instance and CI so that students don't have to even question it. Make them put their assignments on the forgejo instance on one semester, the next semester on gitlab, and the next on radicle or have a course where they get access to a VM and have to setup and host a soueceforge of their choosing. You can assign a subdomain of the uni to them and help them setup SSL certs via a DNS or HTTP challenge.
Otherwise, the easiest thing to do is let them use radicle. They don't have to host a thing and the repos will be distributed across the radicle network, accessible from nearly anywhere.
I'm just reading "I don't want to leave, whatever happens". There's nothing I can say that you will agree with, so we might as well not waste that energy.
Bad, but not the same, IMO. Microslop could shove it under the rug as a glitch. Oh wait... they would do that in this case too. Yeah, maybe it'd have to be more severe than that, but I don't know what's more severe to a private company than getting their IP leaked because of slopcoding.
Microslop does it again! But it will take much more than this for people to leave GitHub. Someone will have to start making private repositories public to show that GitHub can't be trusted for companies to leave. And someone will have to insert malware into GitHub releases from inside the system to make opensource people leave.
When you explore an API in a team and would like to collaborate on that with somebody. If you've worked on any big tech API, with Oauth, and have secrets, writing a script for every request combination takes way too long. Simply pasting the URL and using the stored oauth token within the session is easy with a frontend. And it's reusable and sharable within your team.
I feel like people who make these arguments in earnest are simply terrible at change and lack empathy. "Works for me, so I refuse to understand why it doesn't work for others".
It's so conservative neckbeard and offputting.
Does it do things like no-op privacy invasive JavaScript API? There are APIs that reveal a whole lot about the device you're running, extensions installed, dark mode active, etc.
Edit: uhhhh, it was archived 5 years ago and hasn't been updated since.
I think they are legally in the wrong, trying to impose restrictions om AGPL, but I'm not a lawyer. Probably, anybody making a fork will ignore that and see how far OnlyOffice wants to take it.
I think a better comment would've been "required google services to connect meaning google also has to know who I am in order to connect. Please remove the google services requirement so I can use this without google play"
If it's possible, you can also lodge a complaint at a relative authority in Lithuania.
Since my repos are spread across multiple instances, I deal won codeberg only intermittently and it looks like the 504s are about 2-3 weeks old. Not good, but just outside of the time I got busy in a repo that's not on codeberg.
As for gitlab's interface, I guess it's like switching from new reddit to lemmy, it's different and you babe to get used to it. While quitting Github, I actually came to really appreciate Gitlab's interface. It wasn't easy at the beginning, but now I actually prefer it to GitHub's interface.
If the people you asked are longtime Github users and only use or used Gitlab a few times, I'm not surprised they don't like it.
Radicle is better than it was when I first tried it. For a person who doesn't like the CLI, it's probably utterly horrific, but feature-wise, it's a distributed sourceforge. They still have a ways to go:
But if the goal is just to publish code and have a distributed backup, radicle is very good at that.