Regular users in Sweden are in danger because a corporation needs to fill their pockets. Studios are suing your ISPs to get to you.
Use I2P. It will hide your IP address (among the many things it can do), afford you more privacy and allow you to torrent freely, even without a VPN/seedbox. The catch? You’ll have to add the I2P trackers to your torrent.
I believe I2P is the way forward for piracy and I look forward to it getting bigger than it already is.
A proper VPN provider is sufficient to protect against this though. If you, as a Swedish citizen, weren’t already using a VPN, you were being an idiot.
I mean, it still makes sense to also use I2P, but it is currently not good enough as a full replacement.
A VPN company can easily give up your details to the police who are now actively going after citizens. VPNs are not enough anymore.
Is there a problem with I2P adoption? I’m sensing a massive lack of interest from this thread
If there are no logs, there is nothing to give up. There is no law that they have to keep logs as far as I know.
Don’t get me wrong, I’m interested in i2p. Thanks for posting.
The point is that logs are generated and then deleted but companies who do not wish to keep such logs (e.g. IP address of client who connects to the VPN). I2P sure to it’s design, doesn’t even generate such incriminating logs (it might generate other kinds of logs which is a different discussion).
Thanks
If there are no logs, there is nothing to give up. There is no law that they have to keep logs as far as I know.
You have to trust that the VPN provider doesn’t store logs. I2P is pretty much trustless besides where the binary comes from, but you can even compile it yourself.
I admit that I’m skeptical since everyone is a node. It probably is fine, but I don’t know the risks that I take by volunteering as a node. I thought that VPNs can be fine as long as they don’t store logs, but I could be mistaken.
VPNs usually do store your IP when you connect to them, even if they delete it later (it is technically impossible to not know the IP address of whoever is connecting to the VPN). And the likes of Mullvad and IVPN do not allow port-forwarding.
I will repeat what I said to the other commenter: please read the documentation. Being a router doesn’t mean that traffic and its contents can be linked to your identity. Data is broken down into chunks and encrypted along with metadata being scrambled. Unless there’s a zero day I’m unaware of, you are perfectly safe.
Being a node isn’t an issue. The traffic is encrypted, the destinations are unknown to the nodes themselves, and the traffic does not leave the overlay network (I2P). In TOR, you also have something similar, but the traffic can exit the overlay network but to do so, your node must be an exit node. I2P nodes are internal by default and it’s not that easy to make it an exit node.
You are very safe being a node in I2P.
A good VPN won’t have any details to hand over that will convict you, even if they wanted to (e.g. mullvad), so they most definitely are enough.
And police are not going after citizens, rights holders are (like they always have been) by suing ISPs in hopes of getting your info.
What in don’t like about I2P, is being a node for other peoples traffic.
VPNs log your IP. And Mullvad doesn’t allow port-forwarding, which means you can’t seed.
Being a node for traffic doesn’t mean it can be linked to your identity, because everything is encrypted and metadata is scrambled. TOR node operators take much greater risks because depending on how they have set it up, it can lead to their identity being compromised. It’s a small chance but it can happen.
I can’t convince you. I only hope that people start seeing the need for it and begin reading the documentation to see its strengths
You also need to fully encrypt the traffic in your bit torrent client. You will get fewer peers, but it’s much safer
Does anyone know of a fairly uncomplicated method to set up my seedbox, so I can seed on the clearnet and I2P at the same time, without having to store two copies of all my torrents? I already seed terrabytes of torrent data, and I don’t want to store duplicates of all that.
Unfortunately, Qbittorrent’s I2P support is still experimental. Assuming your seedbox provider can let you run BiglyBT or any other client that can cross-seed, all you have to do is add I2P trackers to your torrent file. You can also upload your torrent files to Postman on I2P for them to be registered.
I know nothing about seedboxes, but on a computer you can point multiple torrents to the same directory. If you make it read-only, by permission or mount options or whatever, the torrent client can’t even fuck it up
I know nothing about seedboxes
It’s basically just a cheap virtual server running e.g. Deluge or ruTorrent, hosted by a torrent-friendly provider in some country that doesn’t give a fuck about DMCA notices. Most don’t allow the user to access the underlying Linux system though, but mine does actually give me a root shell.
I’m gonna have to look into deploying another torrent client on the seedbox, besides my current ruTorrent installation. My provider also offers dedicated servers. They’re more expensive, but I might go with one so I can seed on the clearnet and I2P. It will probably have enough overhead CPU, RAM and bandwidth, so I can also run a Tor node and maybe IPFS.
I’m assuming your seedbox providers allows you root access to the server? Which provider is this?
remember kids do what johnny appleseed did and always seed more than you take.
https://geti2p.net/en/ looks like Tor. but it is not the same?
similar yes but not the same. tor held together by volunteer that run nodes, i2p everyone is a node. tor good for clearnet things, i2p good for in-network things. torrenting in i2p is good for i2p, not tor. torrenting in i2p stays in the i2p network, doesn’t go through exit nodes. there’s only about 3 of those. it’s torrenting as a darknet hidden service.
Yeah, thanks for clearing this up. I was also reading: https://geti2p.net/en/comparison/tor if people want to know more in depth.
After reading that whole page, I think your point is missing… The use case of Tor and i2p isn’t correctly explained on that site.
No, since they don’t act as exit nodes (they’re called outproxies in I2P), unless you specifically configure that. It’s like running a Tor middle/guard relay. I2P was specifically designed that way, so everyone can use I2P and be a node by default without causing any trouble.
I tried to find the answer to this in i2p docs, maybe you would know more
As I understand, i2p traffic still needs to send packets over TCP/IP, so what stops the nodes you communicate with from knowing your IP? Its the only thing that makes me cagey about it since other p2p services like local game servers require sharing your IP to work. Hoping to get back into torrenting, thanks!
Here’s the scary sounding part that can be counterintuitive. The routers you’re communicating with do know your ip, since they have to like you mentioned. Your ip address is also in i2p’s DHT as a “router info” which functions as a network addressbook for routers and services so things can be found without needing a centralized lookup service. Again, because for the network to work, routers need to be able to find eachother, or they can’t communicate.
But, routers function on a need to know basis. i2p uses separate up and down links for each tunnel, and your side of the tunnel by default has 3 hops. other side usually also has 3 hops. typical unidirectional tunnel looks like this with total of 7 hops:
A-x-x-x=x-x-x-B
None of the chains in the link know what position they’re in (except for the endpoints). They also don’t know how long the whole tunnel is. The sender and receiver only know their parts of the tunnel. On the dht side, by design no single router has a whole view of the network, but there isn’t a whole lot of information you get from that other than knowing that person at stated ip address uses i2p, which your isp would be able to tell for example anyway just like using tor or a vpn. There’s no reason to try to obfuscate that except for getting around restrictive countries firewalls.
The way i made sense of it was like you have an envelope that is inside several other envelopes, with each envelope representing a layer of encryption. You get an envelope from kevin, so you know kevin. You open the envelope and see another envelope addressed to george, you give the envelope to him. So you know kevin and george. But the rest is unknown to you. You don’t know who the true originator of the envelope is or where the message is ultimately going.
Not a perfect analogy, but because of this the ultimate sender and receiver are blind to each others ip address. It’s layered encryption allowing this to happen which is similar to onion routing. Called garlic routing in i2p since there are some tweaks.
It’s not big at all. But agree, this is the way.
