3 ms·
I'm still waiting to see an argument for why a content provider who is making something available to others for free and without obligation has any obligation i
by Silhouette 11y ago
I'm still waiting to see an argument for why a content provider who is making something available to others for free and without obligation has any obligation in return, either legally or ethically, beyond the same basic decency that we all owe to each other. I think a site that is neither actively malicious nor grossly negligent has satisfied that basic decency requirement.
Ultimately, it's just not realistic to expect every little store and niche blogger to either monitor every third party service they depend on full-time just to protect the users who are giving them little if anything in return or to discontinue using any third party services that are technically capable of distributing malware. The former is demonstrably impossible anyway, and if you take the latter to its logical conclusion you undermine substantial parts of what has made the modern web so successful, far beyond using ads as a revenue stream.
Put another way, malware writers themselves may be the scum of the earth, but I don't see why someone writing a blog about how to bake cakes and using a well-known and generally reputable ad network to fund the hosting costs is any more ethically responsible for the consequences of a malware incident than, say, a browser developer whose also freely offered product had a vulnerability that could be exploited in the first place. I don't see anyone calling for any browser with a track record of serious security vulnerabilities (which is all of them, of course) to be banned to protect users from malware, though.
- kd0amg 11y agoan argument for why a content provider who is making something available to others for free and without obligation has any obligation in return, either legally or ethically, beyond the same basic decency that we all owe to each other. A grocery store handing out free samples still has an obligation to make sure it's not contaminated, and I really don't buy idea that "don't send people malware" is significantly less a part of a common decency than "don't feed people tainted food" is.
- Silhouette 11y agoIf the malware was created by and distributed by the site hosts, that might be a reasonable argument. But of course, it isn't. In fact, there is no way the site owner can guarantee to avoid the indirect distribution of malware without ceasing all use of third party resources on their site. Given the usefulness of third party resources (not just ad networks) and the relative rarity of malware being distributed through those channels, I don't think the argument that the only decent choice is to eschew all the third party functionality of the modern web is reasonable here.