Switching to Codeberg From Github

I've had a Codeberg account for quite some time, but never really used it. I'm changing that though! A few days ago, I decided to move everything away from Github. Why? Because Github supports ICE, Microsoft sucks, and AI is being shoved down our throats. Codeberg is a non-profit, which does help. (I think most non-profits are still garbage but that's a can of worms for later).

To quote Andrew Kelley, who decided to migrate Zig to Codeberg,

In this modern era of acquisitions, weak antitrust regulations, and platform capitalism leading to extreme concentrations of wealth, non-profits remain a bastion defending what remains of the commons.

Right now, my code is on both Github and Codeberg, and I'm maintaining both remotes. I'll soon stop pushing to Github though. There is a slight problem though - most of the times, I can't push to Codeberg. Not on my first try at least!

emacs-lisp-blog $ git push
Connection closed by 217.197.84.140 port 22
fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

trying again immediately however gives me this

emacs-lisp-blog $ git push
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Delta compression using up to 16 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 247 bytes | 247.00 KiB/s, done.
Total 2 (delta 1), reused 0 (delta 0), pack-reused 0 (from 0)
To codeberg.org:astrobeast/emacs-lisp-blog.git
   533eb57..01386bb  main -> main

Sometimes, it takes more than two or three tries. But honestly, it's worth knowing that I don't have to depend on Github.

Edit: Codeberg Status posted this on Mastodon on :

You might have noticed that SSH connections are no longer being served at the moment.

As part of our investigation into the most recent slowness of Codeberg (which usually results in 504s being given), we have temporarily stopped those. This confirms a suspicion of ours that SSH connections have become, for whatever reason, heavy on the CPU.

We will resume serving SSH connections with a smaller queue to preserve the availability of Codeberg.