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
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.
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
I use Mulvad, and seeding seems to work for me. Am I missing something?
That shouldn't be possible in theory unless I don't know it well enough. Care to provide a screenshot?
VPNs log your IP.
But they don't log the data going through. The IP alone will not be enough for a conviction at all. They also need to prove that you acquired/shared copyrighted content. Any proper VPN isn't going to log that.
But if you think like that I suppose you aren't very interested in running TOR relays or exits either.
No, I'm not at all interested in that either. I don't want to risk any nefarious traffic that I have no control over running through my network.
I get the appeal of I2P for torrenting and I can absolutely see the value it can bring. But as long as I will have to be a node for other random peoples traffic, I'll pass.
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 set it up earlier and it felt like a highschool project. The AiO bloat, the GUI, lots of little bugs everywhere... The service didn't even stop when I ran
i2p stop.I'm not against it, but I do hope it gets a lot better.
The OG I2P program is written in Java, which might show behavior like you mentioned (didn't stop immediately when stopping the service).
Please try I2PD, it's written in C++
I agree, i2pd is so much better than the legacy Java client, it should really become the default client for I2P.
Another question would be how to make a seedbox service use I2P. I have seem some but none of those didn't mention I2P as a feature
Yes, that's a bit of a problem on the average seedbox. You'd have to modify your torrent to seed on I2P by adding I2P trackers (just a couple of them, nothing much), and then run either BiglyBT or I2PSnark to seed them on I2P. Unfortunately, most seedboxes don't give you root access, neither do they bundle these apps. Qbittorrent doesn't have good support for it yet unfortunately.
If you have an SBC/spare computer at home, would be great if you could attach a hard drive to it, install i2p/i2pd and either of the mentioned torrent clients, and seed from there in the meantime. Qbittorrent has seen community interest in I2P, unfortunately it's just not there yet
I have lots of questions. I’ve always heard to use a VPN that doesn’t keep logs, this is the first I’ve heard of i2p. If I add i2p trackers that implies I still have non-i2p trackers so can still be identified. I feel like I need way more information on how to do this safely before I change anything.
Obviously, this doesn't change anything if you're still seeding to the clearnet. All this would do is cross-seed your torrents to the I2P network. I assume you have a suitable torrenting strategy already for the clearnet. If some day you were to abandon the clearnet for I2P, you would no longer need to take the precautions you do now because I2P is inherently private.
Please skim through the documentation for a high-level overview on I2P, and ask here if you don't understand something
