At least not one that’s hosted in a country where the IP mafia has any power, which is unfortunately most countries excluding places like Russia or China where you probably wouldn’t want to host it anyhow due to a variety of other, uh… issues
As long as you host the checksums elsewhere so that users can verify the repo hasn’t been tampered with, you can host files in China or Russia just fine.
You can definitely care about whatever you want. Human rights aren’t the only potential issue though, but there’s things like eg. do you trust that you’ll be able to retain control of the site. So for example if you set it up in Russia and you’re not Russian, do you trust the Russian government not to pull the rug out from under your feet at some point?
I highly suggest starting to familiarize ourselves with federated git repos. I‘m testing forgejo atm hoping to be able to host it publicly at some point. That way, once something is out there, its pretty much everywhere.
Federated git repos doesn’t mean that the source code will be replicated across instances. It just means you can do things like create tickets and pull requests across instances.
hmmmm… I see your point. Maybe I wasnt explaining my point clear enough. Right now, I cant see someones fork of some software if I’m on some gitlab which is not federated afaik. I should have said discoverability I guess. Does that make more sense?
I mean, not saying anyone should, because evading copyright is bad. But technically, you could run say forgejo as an onion service. Connecting git to clone from it would take some extra steps but, if hidden well it’d make it somewhat harder to take down.
archive.org is cool and all, but a centralized service will never be a reliable way to truly archive something.
At least not one that’s hosted in a country where the IP mafia has any power, which is unfortunately most countries excluding places like Russia or China where you probably wouldn’t want to host it anyhow due to a variety of other, uh… issues
As long as you host the checksums elsewhere so that users can verify the repo hasn’t been tampered with, you can host files in China or Russia just fine.
That’s assuming that the only potential issue you care about is tampering though
What else would I care for? We’re talking about piracy, so I wouldn’t turn the choice of a server location into a human rights debate.
You can definitely care about whatever you want. Human rights aren’t the only potential issue though, but there’s things like eg. do you trust that you’ll be able to retain control of the site. So for example if you set it up in Russia and you’re not Russian, do you trust the Russian government not to pull the rug out from under your feet at some point?
I wonder if IPFS would help in this case…
Anti Commercial AI thingy
CC BY-NC-SA 4.0
Your license thingy broke since that thread where you explained your script. It doesn’t spoiler anymore.
What does it look like for you? I’m on the web client
Anti Commercial AI thingy
CC BY-NC-SA 4.0
Maybe it’s just the Boost app I’m using
this repo still lives and we still have Suyu that looks promising, So, no worries atm https://github.com/pineappleEA/pineapple-src/releases/tag/EA-4176
Github probably didn’t receive a cease and desist yet, but I doubt they’ll put up a fight against Nintendo.
I highly suggest starting to familiarize ourselves with federated git repos. I‘m testing forgejo atm hoping to be able to host it publicly at some point. That way, once something is out there, its pretty much everywhere.
Federated git repos doesn’t mean that the source code will be replicated across instances. It just means you can do things like create tickets and pull requests across instances.
Not sure I understand. I should be able to fork a public repo across instances, no? Why bother otherwise?
Federation has nothing to do with that capability.
git clone
exists since the beginning of git.hmmmm… I see your point. Maybe I wasnt explaining my point clear enough. Right now, I cant see someones fork of some software if I’m on some gitlab which is not federated afaik. I should have said discoverability I guess. Does that make more sense?
I mean, not saying anyone should, because evading copyright is bad. But technically, you could run say forgejo as an onion service. Connecting git to clone from it would take some extra steps but, if hidden well it’d make it somewhat harder to take down.