[git.fuwafuwa.moe](https://git.fuwafuwa.moe)([onion](http://git.fwfwqtpi2ofmehzdxe3e2htqfmhwfciwivpnsztv7dvpuamhr72ktlqd.onion))|✅|Gitea 1.13.6|n|n|n|n|SSH port: 22; SSH over Tor [broken](http://git.fwfwqtpi2ofmehzdxe3e2htqfmhwfciwivpnsztv7dvpuamhr72ktlqd.onion/levena/fuwafuwa/issues/1); HTTPS over Tor works|
[forge.april.org](https://forge.april.org)|❌|Gitea 1.15.6[⚠][gitea-bug]|n|n|n|n|French is the primary language; no registration form; access is for [April](https://www.april.org) members -- but perhaps April membership is open to all?|
[git.nogafam.es](https://git.nogafam.es)([onion](http://git.hsdtecd4h2b5z732pvkg2yw3746epap4qusgvjjze6nhmfcdpz2suiad.onion/))|✅|Gitea 1.15.6[⚠][gitea-bug]|n|n|n|n|[SSH disabled](https://git.nogafam.es/deCloudflare/deCloudflare/issues/18#issuecomment-75); large repos are [git-inaccessible over Tor](https://git.nogafam.es/deCloudflare/deCloudflare/issues/18#issuecomment-48); onion site is down|
[gitlab.torproject.org](https://gitlab.torproject.org)|✅|Gitlab (CE)|n|n|n|n|open registration; repo creation possibly restricted; Google reCAPTCHA is [allegedly](https://lists.gnu.org/archive/html/repo-criteria-discuss/2021-03/msg00000.html) used, but [not at registration time](https://gitlab.onionize.space); it’s possible to [create an anonymous bug report](https://anonticket.onionize.space)|
[notabug.org](https://notabug.org)([onion](http://qs3zumwfci4tntnd.onion))|✅|Gogs|n|n|n|n|based on [liberated](https://notabug.org/hp/gogs) fork of Gogs; [supports Tor](https://notabug.org/tor) (the *onion* web UI is currently disabled in response to attack but the onion site accepts git connections); supports SSH keys and SSH over Tor to NAB's onion service; no e-voting; NAB doesn't associate PGP keys to users, so PGP signed commits may be unavailable or more manual work needed.|
[gitee.com](https://gitee.com)|✅|OSCHINA|n|n|n|n|based in China; registration over Tor with throwaway email works; no automatic mirror (unlike Gitea); some areas written in simplified chinese|
These forges are not as seriously flawed as the blacklisted ones, but they should still be avoided if possible. Non-Cloudflare sites that use a Cloudflare NS server pose a risk for disruptions because they can trivially and spontaneously flip a switch and route all your traffic through Cloudflare, potentially cutting access to some of your contributors. Sites that are dead or previously dead are also graylisted because if they come back online, they are known to be unreliable. Resource deprived instances are graylisted because they may become unstable or unreliable in the future, or if your repo is resource heavy you may be asked to leave. Codeberg is graylisted for falsely accusing a repository of illegal conduct and deleting the content of all forks from that project without evidence or redress.
[gitnet.fr](https://gitnet.fr)|✅|Gitea|n|n|n|n|Forge is resource deprived. The admin (simonv) had to ask a project to leave his forge for [performance reasons](https://framagit.org/dCF/deCloudflare/-/issues/46)|
[git.openprivacy.ca](https://git.openprivacy.ca)([onion](http://gitopcybr57ris5iuivfz62gdwe2qk5pinnt2wplpwzicaybw73stjqd.onion))|✅|Gitea 1.12.4|n|n|n|n|Tor users get 404 - suspected botnet if visiting the clearnet site from a browser that does not act on the “onion-location” header; [listed](https://framagit.org/dCF/deCloudflare/-/blob/master/cloudflare_users/cloudflare_supporter.md) as a Cloudflare supporter for spontaneously deleting the repo of an anti-Cloudflare project without warning.|
[git.sdf.org](https://git.sdf.org)|✅|Gitea 1.14.1[⚠][gitea-bug]|n|n|n|n|git.sdf.org [censored](https://git.sdf.org/deCloudflare/deCloudflare) the deCloudflare project without warning, reason, or recourse. So git.sdf.org apparently unwelcoming of projects driven by privacy, netneutrality, or anti-tech-giant types of activism. Performance is sluggish and the website often times out (perhaps because SDF is also tar-pitting many Tor IPs in defense of attack & it’s unclear if this is a temporary measure); SSH over Tor broken but HTTPS over Tor works|
[try.gitea.io](https://try.gitea.io)|✅|Gitea 1.16.0[⚠][gitea-bug]|n|n|n|n|**Cloudflare NS server** (they can route all traffic via CF at the flip of a switch); Intended only for Gitea experimentation; no expectation of future availability|
[forge.chApril.org](https://forge.chApril.org)|✅|Gitea 1.16.6[⚠][gitea-bug]|n|n|n|n|Censorship: spontaneously deletes people’s repos without warning, reason, or recourse. Forge is unsuitable for activism. French UI.|
[git.shivering-isles.com](https://git.shivering-isles.com)|❌|Gitlab (CE)|n|n|n|n|**Cloudflare NS server** (they can route all traffic via CF at the flip of a switch); Registration is open but broken-- requires 2FA using a device that can QR-scan, and the email verification link is DoA: !(images/shivering-isles_broken_reg.png) That stale link error triggers even when accessed immediately.|
[mypdns.org](https://mypdns.org)|✅|Gitlab (EE)|n|n|n|?|Previously down-- sudden death of website without warning to repo admins. Came back online months later but people’s accounts and repos were mysteriously gone; Was home of the deCloudflare and /Right to be Offline/ projects; It was open reg but considered a “private system” whereby the option to create a new repo was not immediately available.|
github.com|❌ (exclusive walled garden)||y|n|n|☣|**access granted or denied based on national origin**; [copious ethical issues](github.md)|
⚠ Gitea versions note: Gitea 1.13.8 [breaks][gitea-bug] emoji in some browsers. The developers [believe](https://codeberg.org/Codeberg/Community/issues/444#issuecomment-198199) that by not supplying fonts to the web visitors who need them, they are improving server performance. Of course the server load is only reduced when talking to a browser that does not have the needed fonts. The idiots could also simply arbitrarily deny service to users at random to get a performance increase. Obviously they have misunderstood the point of performance in the first place: availability!