safe gitea instances

i suppose this fits in /sec/ too. as a programmer, i've recently made the decision to prioritize my privacy, so i wanna move my code from github to a private, reliable gitea instance. the only one i know of so far is git.fuwafuwa.moe, but i was wondering if there were more, preferably tor-only instances out there.

Why not host it yourself? Any sbc can handle a private gitea.

>>40187 >i've recently made the decision to prioritize my privacy, so i wanna move my code from github to a private, reliable gitea instance. What do you think privacy is? If it's on the internet it's not private. Either you want people to look at your code or you don't.

>>40189 you think your bank account is public cause it has online access?

>>40190 >you think your bank account is public cause it has online access? You're going to setup usernames and passwords for your gitea instance? If you don't want to share your code with the whole world then it doesn't need to be online. If you do want to share your code then github is the biggest platform. It sounds like OP is just using "privacy" as an empty buzzword without understanding what he actually wants.

Given the "Anyone can host" nature of Gitea I'd highly recommend you just host it yourself. While I doubt anyone would actually go and do something malicious at services like Github, individuals don't have a public image to uphold. Just spin up a Debian/Alma VM and run it as a container. Assuming you're only coding on the host machine this won't be an issue. If you are editing it on various systems (desktop, laptop, etc) then just get a cheap VPS or NAS and install Tailscale. Deny any and all connections from addresses that aren't Tailscale, and you're good to go. If you're unfamiliar with containers then check Yacht. They provide a easy installation guide and allow you to just spin up Gitea with no friction.

I just run my own local instance of Gitea on my home server. I upload my own code there and mirror whatever projects I find interesting. Migrating from GH was fairly trivial, specially after the release of Gitea Actions which utilize the same configuration syntax as GitHub. Afterwards, it was just a matter of setting up a Windows VM to service Windows-specific CI pipelines and a Linux box for everything else. I'm very happy with how it all turned out.

I've noticed some papers using https://anonymous.4open.science/ to host their code. Some of them use this to facilitate double-blind peer review while they are in pre-print.

>>40187 "public domain" means "other people's domain". so other people's server means public server.

git init --bare access over ssh

>>40187 self-host, with cheap privacy focused VPS like kyun-host or use codeberg