> The point of the law here _is_ to make an example of people. Those two things aren't mutually exclusive.
Whether they're mutually exclusive or not, I don't think that was even the point of the law. The point of statutory damages is supposed to be to address the problem of proving an exact amount of actual damages, by instead providing what was supposed to be a plausible estimate of them. But then they got applied in a context where the number hard-coded into the law is an exorbitant overestimate.
> I believe your claims about network speeds and peer count are largely inaccurate when it comes to torrents (and any other block based protocol that involves the equivalent of swarms) but I won't belabor it.
I'm pretty confident that's accurate for small files like a 3MB MP3. They literally do get fully transferred before the client has time to connect to a non-trivial number of peers. A lot of torrents use a 4MB chunk size, and even when the chunk size is smaller, you're still going to get multiple chunks from any given peer. Even with e.g. a 512kB chunk size a 3MB file has an upper limit of 6 peers, if you can even connect to that many before the first one has sent the whole file.
Large files could use more peers, but "hundreds of thousands" is still a crazy number. There are a non-trivial number of consumer junk routers that will outright crash if you try to open that number of simultaneous connections.
And I regularly use BitTorrent for Linux ISOs (I know it's a cliche but it's true), which are decently large files. The median number of connected peers when seeding really is zero, and the active number rarely exceeds 1, for anything that isn't a very recent release. Even if I leave the thing on indefinitely, until it's no longer a supported release and no one wants it anymore, on a connection with a gigabit upload, the average ratio will end up around 1. Because of course it is, because that's inherently the network-wide average.
> I'll also ask how you reasonably expect a court to go about performing the partial attributions you describe for data torrented from a large swarm. Like how would that even work in practice?
I mean this isn't really that hard, right? If getting the exact number for a specific person is unrealistic, we still know that total copies (and therefore total uploads) per user is ~1. So to do the normal punitive damages amount you take that number and multiply it by 3 instead of hundreds or hundreds of thousands.
> Damages aren't reduced if I only illegally reproduce 25% of a book. A single chapter and the entire work are treated as equivalent here.
But the entire work is being reproduced. The issue is that in the cases where it's a group effort, they're trying to double dip.
Suppose Alice, Bob, Carol and Dan work together to break into your shop like Ocean's 11 and steal four $1 cookies. They each get a cookie and you lost four. (Never mind whether you actually lost them or not.) If you only catch Carol, it's not always reasonable to put her on the hook for the entire amount instead of only her portion of it, but at least you could plausibly argue for it. But if you catch two of them, or all of them, expecting them to each pay the total for the whole group instead of collectively pay the total for the whole group is definitely unreasonable.