Talk:Personal image filter/LQT Archive 1

Name
Brandon raised a good point about the name, saying that "Controversial content management system" could be read as "Controversial content management system". To avoid the ambiguity with a CMS, what about "Controversial content hiding system"? guillom 07:21, 1 March 2011 (UTC)
 * I like "obfuscation" better than "hiding"; I'm not sure "system" is needed at all. --MZMcBride 19:14, 1 March 2011 (UTC)
 * I don't think "obfuscation" is a good term. "Controversial Content Display Behavior System" is probably best and most accurate.--Jorm (WMF) 19:15, 1 March 2011 (UTC)
 * Obfuscation cracks me up. I would actually like to get away from the term "controversial content" in general; it's a useful shorthand but also has pejorative connotations. Image hiding system? -- Phoebe 05:15, 4 March 2011 (UTC)
 * I'm thinking of going with "Personal image filter". It seems to me this is really what the feature allows: to empower the user to enable or disable filters, according to their preference, to hide images or not. guillom 09:18, 4 March 2011 (UTC)


 * It's applicable to videos as well. That may not be a good enough reason to rename the project, but it's something to bear in mind in user interfaces and such.--Eloquence 22:16, 16 March 2011 (UTC)
 * I think "Personal Media Filter" is probably best.--Jorm (WMF) 00:32, 18 March 2011 (UTC)

Objections
This is way more restrictive than would be acceptable in at least the part of the enWP community with which I am familiar. First, I do not think the entire project acceptable as a matter of principle. We have the obligation to create properly descriptive metadata for material; we have the obligation to aggregate the descriptors in logical and useful ways. We recognize that these descriptors can and will be used by outside parties to filter our material according to their own purposes, but the possible misuse of the descriptors should no more prevent their making than the possible misuse of any other content prevents it. We probably even have the obligation not to construct our system in such way as to frustrate this use (we do not judge the virtue of a type of use), and possibly even to give links to the various systems available for those who want to use them. (we provide information to help our users make use of the material in whatever way they want to).

But for the WMF itself to make such filters is a gross abuse and contradiction to our principles. Our business is the provision of information, not its restriction. We do not censor, except as we are compelled to. Therefore, we do not make filters for censoring. We do not implement filters others may make. We do not make categories designed specifically to facilitate censoring that we would not make otherwise.

I shall do what I can to urge the community to reject this entire proposal. My idea of the proper objectionable content policy is just two provisions: 1.we do not host material that is illegal according to the governing law where our servers are located. 2.we do not force any project to include material it does not want to include, but they must adopt a policy as close to NOT CENSORED as their principal readers and editor communities permit.

The most objectionable part
The most objectionable part is the default filter. Even were we to have this project, there is one default filter setting and one only that is consonant with the principles of NOT CENSORED -- that is "Allow everything". Otherwise we are censoring in the sense of segregating material in a private back room.

The second most objectionable part
The second most objectionable part is to compel the different Wikipedias to implement the necessary overhead for this policy. If the policy is thought necessary for some culture areas, a position I disagree with very strongly but can image the WMF adopting, that still does not give those areas the right to impose their standards on others, or to compel them to participate in a project against their own mores. In other words, if the xxWP decides to use such categories, the enWP does not have to provide equivalents of them. In such a case, what to do with Commons is a difficult question, but I would still say the Commons should not use it. The various WPs can use such images from commons as they choose, and not use others. (I believe this is already the case with respect to copyright, and even the enWP has long required permission to use certain particularly provocative images.)  DGG 23:01, 19 March 2011 (UTC)


 * Hi DGG, Thanks for your thoughts.

-- Phoebe 23:15, 19 March 2011 (UTC)
 * 1) There's no default filter; default is the status quo. (I think the spec says it could be possible to make a default if wikis wanted to, but most of this spec is about how to enable readers to filter images only for themselves, in which case the default for the whole project stays the same).
 * 2) You're objecting to people hiding images *for themselves* (not for others?) I think the system described is so readers can make their own choices about what to see. Editorial policy remains the same, of course.