Most attacks on servers are on the connections. All IPs are owned by entities part of countries, so your IP is always under someones jurisdiction. The same is true for regulsr DNS entries, so the domain of that server.

For getting the data however, there also isn’t any protection in international waters. Someone would just raid you and you could do nothing about it. What good is lawlessness if you don’t have the ability to enforce your own “laws” about not having your data taken away?

You could lay low so noone bothers with that, but then you could also just lay low with regular secretive hosting.

The admin team is distributed and the infra is in europe iirc.
So no

sure

I have that exact setup working. qbittorrent (and -nox) are a lot more involved to set up with I2P, but there is some material on how and once you get it running it works quite well at this point.

I don’t use docker for it, but that should work too. For browsing I use a maintained fork of proxy switchy omega, which allows to choose a proxy profile based on the url, making it easy to pipe i2p pages into the i2pd socks port (I use I2Pd not I2P, don’t think it matters much). qbittorrent can be configured in the same way to statically use the the local (4447 on i2pd) port as a proxy to prevent any clearnet communication. In addition it needs the dedicated I2P host 127.0.0.1 and port 7656 (the sam bridge, giving deeper access to I2P).

Don’t expect to do anything on the clearnet over I2P, the exits are not good and it’s not what I2P is meant for. For that reason don’t set I2P up as something like a system proxy/vpn, instead pipe the specific programs you want using I2P into the proxy ports using their proxy settings.

To get rid of the firewalled status in the I2P daemon, you will need to forward ports. Maybe you have seen advice for servers that are not behind a firewall and nat, so that effectively have all ports “forwarded” already. The mythical dedicated IPv4 address.
In your case you need to pick the port your I2P daemon uses for host to host communication randomly, then forward both TCP and UDP for it on IPv4. Also make sure you even can forward ports, depending on region ISPs no longer hand out dedicated IPv4 even per router, so you might have to specifically ask your ISP for one (I had to). But that is all generic hosting, if you can set up a minecraft server you can make I2P have full connectivity.

works

Look into I2P.
It’s a network similar to TOR, but more suited for usecases like torrenting.
For anything you do on I2P, you can rest assured noone else can even in theory trace it back to you.
Go visit http://tracker2.postman.i2p for a large collection of public domain content.

The only issue is that there is also a lot of content available in german and english language which is not in the public domain, and due to the anonymous nature of I2P noone would be able to warn you of that. So take care you don’t accidentally seed the content to others, keeping it online for even more people to commit the same mistake with noone the wiser.

away

Like, from you personally?

Aside from Australia or Japan, a move should improve the average ping users experience.
Most people are not from the us, and given its geographic location nowhere close to it either.

You can always parallelize, this would be more beneficial for latency.

ISPs on a voluntary basis, not the nation

Only ones I’ve ever heard are Radiohead and Rage against the Machine.
Sincerely, genZ

Anyway are yall telling me there are no bands that are both horny and angry?

Edit:
I was probably wrong about Radiohead. Maybe I mixed them up with radioactive by imagine dragons?