this post was submitted on 10 Jul 2023
735 points (100.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54462 readers
272 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd rather pay for a decent Usenet backbone and use exclusively SSL downloads than rely on a VPN with torrents.
You don't want a free VPN. I'd cough up for Mullvad if I was going that route.
Mullvad got rid of port-forwarding so it's not good for torrenting anymore. IVPN, which is where the Mullvad refugees fled to, just got rid of it as well. I think AirVPN is the next option people are flocking to, but who knows when they'll do that next.
I've also seen stuff about torrenting over I2P which shouldn't have this limitation, but I'm not sure how usable it is right this moment.
Why do I need port-forwarding for torrents?
Torrenting happily on Mullvad right now.
For peers to connect to each other, at least one of the two connecting needs to be port-forwarded, so if everyone were on Mullvad, now no one would be able to reach each other. Right now you can still torrent on Mullvad, but only with (non-Mullvad) users who use port-forwarding.