Okay but there are plenty of real-world reasons that you might not be able to download from those seeds.
No spare bandwidth. Their bandwidth might be saturated on other peers, other torrents, or other applications entirely.
Bandwidth limits. All torrent clients have ways to limit bandwidth. Most often have a UI button to switch between a high and low option. Some also have schedulers for that as well.
Connection limits. All torrent clients have a maximum limit for open connections (ie peers) because large amounts can be very taxing on resources. There are also generally ‘upload slot’ limits too, further limiting those connections that can be used for seeding.
ISP Port throttling. ISPs are constantly trying to block P2P traffic, the seed might need to change their port to become unblocked.
Misconfigured UPnP/Port Forwarding/Firewall settings blocking the seed’s incoming connections, while it still reports to the tracker as this is an outgoing connection.
Geographical distance can also make a huge difference.
Public trackers amplify some of these issues more than private ones. Hence why you often see network configuration knowledge needed for interviews.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Yes, or at least 9 when the seed numbers were last checked, which shouldn’t change too quickly.
As for why seed numbers listed on trackers are significantly larger than those found by actual clients, who knows.
Okay but there are plenty of real-world reasons that you might not be able to download from those seeds.