It's not about being inflammatory, but about illustrating a key risk - child porn is pretty much unique compared to other illicit content in that possession alo

It's not about being inflammatory, but about illustrating a key risk - child porn is pretty much unique compared to other illicit content in that possession alone immediately makes you into a felon; it's not a civil issue like pirated movies but a crime, and malicious intent or even knowing about the content is not necessary to make you guilty, unlike pretty much everything else. On the other hand, attempts to distribute child abuse imagery are sufficiently common so as to consider it a real risk, not some unlikely hypothetical issue that's not going to materialize. So for any service that's going to put random files on an end user device it's very relevant to ask the particular question "how are you going to ensure that child porn does not get put there?", with the explicit focus on child porn - it's acceptable if the service has no solution for pirated movies, because if pirated movies get put on someone's PC without their knowledge, that's not going to them in jail, but for child porn at least some answer is mandatory. For example, at the very minimum, censorship of known bad file hashes, such databases exist - of course, that's circumventable by e.g. encryption, but it would help from the legal perspective.