this post was submitted on 01 Apr 2025
11 points (57.7% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
59774 readers
260 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):
🏴☠️ Other communities
Torrenting/P2P:
- !seedboxes@lemmy.dbzer0.com
- !trackers@lemmy.dbzer0.com
- !qbittorrent@lemmy.dbzer0.com
- !libretorrent@lemmy.dbzer0.com
- !soulseek@lemmy.dbzer0.com
Gaming:
- !steamdeckpirates@lemmy.dbzer0.com
- !newyuzupiracy@lemmy.dbzer0.com
- !switchpirates@lemmy.dbzer0.com
- !3dspiracy@lemmy.dbzer0.com
- !retropirates@lemmy.dbzer0.com
💰 Please help cover server costs.
![]() |
![]() |
---|---|
Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You can keep on seeding after downloading and your torrenting program will still manage to upload to any member of the swarm for that torrent that it connected to (even if only to check their status) during the download phase.
This should be enough to get you consistently above a 1:1 upload to download ratio for any popular public torrents, though for those with very few leechers you might never get there.
The lack of port forwarding is only a problem for remote machines your program has not connected to during the current session for a torrent (i.e. not yet seen machines that try to connect to your client), which means you can't seed at all in a purely for seeding session or upload to machines that joined the swarm after your download was done in a mixed session.
If your pattern of usage is that of mainly a downloader of public torrents who tries to give back to the communy at least as much as they took and whose not mainly into obscure stuff, it works fine.
You are not exactly right, but going in the right direction. Not having a forwarded port means you aren't 'connectable' by peers as your firewall will block incoming traffic. What this means is that only 'connectable' peers will be able to connect to you (your client can reach out to them as their port is forwarded). You are however invisible to peers that also aren't 'connectable'. You might also experience some degradation in time to connect as people can't reach out to you.
To sum it up: