cordelia_v: my default icon (Default)
cordelia_v ([personal profile] cordelia_v) wrote in [community profile] fanlore2010-04-23 08:33 pm
Entry tags:

Draft of Image Policy for Discussion

As Meri commented in an earlier post, we've been working on several projects in committee, and we're far enough along now to ask for your input on a few things. Today, I wanted to ask you to read and comment on a draft of our new Image Policy, which we've posted for discussion on Fanlore.



There are several areas we needed to develop clearer guidelines for, but we decided to make the image policy an earlier priority because some of you had expressed concern (rightly!) that Fanlore had no policy regarding explicit images, including those which might be triggering or offensive (or illegal to view) for some users.

It's only a matter of time before someone uploaded an image of Fenrir/Draco chan noncon fanart, mean to say. And while we'll host any art that is legal for us to host, we want to make it possible for those who find such images disturbing to avoid seeing them.

Once we started working on it, we realized that an image policy needed to address not only explicit/possibly offensive images, but also questions about uploading copyrighted images, fair use, and images that were being uploaded with the consent of the artist. So, the policy also covers all of those questions as well.

The draft we've posted to Fanlore has been vetted by the OTW's legal committee, and also relies heavily on Wikipedia's robust set of image policies. When you check it out, you'll see that it's pretty long and detailed, but please don't be put off by that!

We're going to post a link on the Editing Help and Tutorial pages to a much more streamlined "Cliffnotes" version of this policy, that contains links to get users started who don't need to read the whole policy, but just want answers to questions like: what templates should I use for art that has explicit images? or what templates do we use for images that are copyrighted or how can I filter out or avoid images that I might find disturbing?. But before we create the short version, we needed to get the full policy approved and in place.

We also wanted to ask your input on a question that is still open: how should we define "high res" and "low res" images in these guidelines? Images can be high res if they're uploaded with permission of the creator, or are in the public domain, or licensed for free distribution by their creator. But copyrighted images must be uploaded in low res, thumbnail versions in order to comply with standards for "fair use." We have our own ideas about what size a thumbnail image is, but we wanted your input about how you'd define "high res" and "low res" images for Fanlore.

OK, now that the intro is out of the way, here's the link to the full draft of the image policy. We wanted to leave this open for discussion until April 30th, and then we'll revise the policy to reflect the discussion and post a final draft to Fanlore.

ETA: a list of the various threads developing in this discussion

1. Some commenters asked whether we planned to recommend deleting already uploaded images that don't fit this policy, and my answer was no, although we hope that eventually new image summaries might be added for uploaded images that currently have little or no information. Some commenters pointed out that we do have some pages with explicit images on Fanlore already, and I responded that we'd set up a page for people to post links to explicit images that are already on the site, so that over time, those images pages could be edited to include the appropriate warning template. See the discussion here.

2. One commenter raised the question of images that might appear to be non-con taken alone, but which actually depict a consensual act in a story; you'd need to read the story to see that, and the image taken on its own would seem to be noncon. Clarification added to note that images should be categorized as explicit, non con, etc. based on what they appear to depict here.

3. One commenter made the suggestion that some images are NSFW while still not meeting the definition of explicit given in the policy. This person suggested that editors should include a note at the top of the article that it included NSFW images further down (so that they could choose not to scroll down, if they were at work), although such images wouldn't require the use of any explicit images templates.

4. There is discussion starting here about what category images depicting BDSM would fall into. The consensus seems to be that such images are possibly "explicit" but do not fall into the category of "non con," although commenters acknowledged that some readers would feel that BDSM was inherently non con. The consensus is that we should add a warning to the policy for such users, warning them that if they click through to "explicit" images, they may see images depicting BDSM.

5. A few commenters made the suggestion that we could add a warning category for extreme violence (where no sexual activity is involved) which strikes me a good suggestion, and I'll take it back to the committee.

6. There is a discussion here about why the policy addresses issues of copyright and asks for copyright tags in image summaries. Some commenters wondered whether it was necessary to include a discussion of copyrighted images in the policy.

7. There is a discussion thread here about one commenter's suggestion that instead of using warning categories and templates for explicit images, that the site as a whole should just have a click-through warning that the site contains adult comment.

8. Clarification added here that the image template for linking to explicit images of all sorts would result in a thumbnail that has a colored border around it (color coding for warnings) and not a line through the thumbnail.

9. A suggestion here that we add an alt text field to the template, to make Fanlore more accessible. I agree.

10. A discussion here about just putting all explicit images on subpages in articles.


ETA 2: You've all contributed a lot here, in terms of pointing out some things that need to be added or clarified in the draft. But I've got to go tend to RL stuff, since I've been responding to comments now for seven hours with very few breaks! I'll respond to any new comments tomorrow or later in the weekend.
ratcreature: Flail! (flail)

[personal profile] ratcreature 2010-04-23 10:27 pm (UTC)(link)
I meant to illustrate the type of picture slavefic often has, not that BDSM pictures would be inherently more problematic.

I love slavefic, but the situation where someone fucks their slave is sexual assault, because slaves can't five consent freely. So the pictures with the background knowledge taken into account depict sexual assault (a master puts a slave in chains and displays them without the slave consenting to anything) but the image itself is fairly harmless. Explicit, yes, but from what is shown it might as well be consensual. I just want the final policy to be clearer what is meant with "depict".
morgandawn: (Default)

[personal profile] morgandawn 2010-04-23 10:40 pm (UTC)(link)
Boys in Chains is a problematic example because it covers all types of 'chain' scenarios - slavefic, d/s and BDSM. Hard to determine what is going on from a brief image - so you either lump all of this type of sexual activity into the questionable consent category or you allow some ambiguity. which is why explicit vs non explicit might be the better focus and reserve consent/non consent for more unambiguous examples.

BTW, where do images of violence fit in? not sexual violence. I may have skipped past that part.
ratcreature: The lurkers support me in email. (lurkers)

[personal profile] ratcreature 2010-04-23 10:52 pm (UTC)(link)
I wondered the same thing. I didn't see any proposed warning template in the draft, but I think there probably should be for extreme violence, because I suspect depending on the visitors theyy might appreciate warnings for say a dismembered child corpse even more than for some alien tentacled penis... especially as you would expect the former less in much of media fandom.
morgandawn: (Default)

is anyone looking at usability and inclusiveness?

[personal profile] morgandawn 2010-04-23 11:09 pm (UTC)(link)
buried in all this is a key question - all these templates....will they be as easy as checking a checkbox? or will the poor user have to travel to the template page to copy 3 different codes (making 3 trips)? (one for copyright, one for explicit and one for triggery images)

I;d like the policies to be rooted in real life usability and inclusiveness. We're already struggling to get fans to participate. I;ve heard from one person that they're re-evaluating their plans to do a huge set of image scans and uploads because of how overwhelming this is - just from the technical stand point of having to navigate so many screens to get one image up. This is not even addressing their horror over how to apply 3 different policies

I;d like to see - one checkbox for copyright/non copyright. one checkbox for explicit (either violence or sex). and a fill in box for source. And if we don't have the ability to do checkboxes - this policy needs to be put on hold until you can get the tools in place so this does not shove people out the door.

and as for the idea of plastering red lines through either explicit or triggery art ....many artists will not go for that. it would be better to require a 'click through and accept' that there will be violent/sexual images on the entire website.
ext_3626: (orion - doro)

Re: is anyone looking at usability and inclusiveness?

[identity profile] frogspace.livejournal.com 2010-04-23 11:16 pm (UTC)(link)
I;d like the policies to be rooted in real life usability and inclusiveness.

Seconded.
ratcreature: hiding under my blanket (hiding under my blanket)

Re: is anyone looking at usability and inclusiveness?

[personal profile] ratcreature 2010-04-23 11:47 pm (UTC)(link)
it would be better to require a 'click through and accept' that there will be violent/sexual images on the entire website.

A setting or preference the wiki remembers would be nice. Though I think I would like it more fine grained, at least if you're logged in, so that maybe on your setting page you could set that you are okay to view explicit pictures, but don't want to see those with an underage label, or that you are okay to see underage, but not sexual assault or whatever.

And yeah, the code for including images should not get too complicated. It often has trouble as it is now already with the sizing, the thumbnail position, the subtitle...
morgandawn: (Default)

Re: is anyone looking at usability and inclusiveness?

[personal profile] morgandawn 2010-04-24 12:59 am (UTC)(link)
I was thinking more of how the majority of websites handle adult content, that is not dependent on logging in. Warning: this site contains adult themed content and explicit images. Click here to enter.
morgandawn: (Default)

Re: is anyone looking at usability and inclusiveness?

[personal profile] morgandawn 2010-04-24 01:51 am (UTC)(link)
you are correct , I am thinking of a single click through, with a general warning. and I think by focusing on creating a customized user experience for every viewer you are making it much harder for people to participate. The amount of negative feedback I've received in the last few hours alone is not promising. I've been working hard to get other fans to start adding more content to Fanlore - new volunteers have a huge learning curve and adding a 4 part peer review test to upload a single image seems to be the opposite of encouraging greater diversity of content and participation.

Bottom line: you need a simpler policy, that is easier to understand and easier to apply. And more importantly, you need automated set of tools. And I mean automated - buttons that users can check that will apply the multiple codes to the image for the user.
(deleted comment)
ratcreature: RL? What RL? RatCreature is a net addict.  (what rl?)

Re: is anyone looking at usability and inclusiveness?

[personal profile] ratcreature 2010-04-24 02:15 am (UTC)(link)
Yeah, a blanket warning would not be helpful at all for me. And on fannish archives that is actually not how it is implemented either. Journals neither. I mean, archives warn usually you for every story separately (like the javascript boxes you have to click through on eFiction archives), and on journal sites you see adult flags and the like entry specific. You can disable the warnings on some sites, but I do not just get a single warning here on DW for example, but labels on every entry the owner marked.
morgandawn: (Default)

Re: is anyone looking at usability and inclusiveness?

[personal profile] morgandawn 2010-04-24 02:23 am (UTC)(link)
What I worry about is that Fanlore is designing a policy without usability concerns or feedback from the people who are actually going to use the system. If the policy is sound but it is designed in a vacuum and is impossible to implement, then you *are* creating barriers to participation and exclusion on a very practical and real level. and it seems to me that *that* is the big shift in Fanlore policy that is not being addressed head on.

the point of Fanlore offering up the policy as a draft is to get the exact type of feedback that I and others have been giving. to be told that we are pre-judging something because we are raising an issue that does not seem even been adequately addressed (usability), is off-putting.

morgandawn: (Default)

Re: is anyone looking at usability and inclusiveness?

[personal profile] morgandawn 2010-04-24 12:57 am (UTC)(link)
Run me an example of how this would work:

Ex: copyrighted, violent underage explicit image. I am staring at the upload page. I click on.....??? what???? to create the code? there are so many variables, so I am assuming you'll have some series of buttons that I can push or checkboxes I select to create a custom code that only has the variables I need (for example a non copyrighted, violent, triggery image would use a different series of codes than my first example).

Once there on this new page, there will be a single nicely formatted series of codes for my specific set of variables together in a single box. I then copy. Hit the back button??, go back to the upload page. paste the code. then upload the image.

then, once this is done, I need to copy the image URL, go to the entry page and paste the image URL?

did I get the workflow correct? miss any steps?
christycorr: Merlin (Merlin) (*beams*)

Re: is anyone looking at usability and inclusiveness?

[personal profile] christycorr 2010-04-24 04:57 am (UTC)(link)
Done! :D
christycorr: Toothless (How to Train Your Dragon) (123)

Re: is anyone looking at usability and inclusiveness?

[personal profile] christycorr 2010-04-24 04:56 am (UTC)(link)
Hi! Here's the thing: creating a checkbox system would require customizing the software far beyond what I'd trust myself with. It's going to be a template much like our current zine/character/etc. profiles, really.

So you upload an image, and copy/paste the template and fill it out, like:

{{image
description=Kirk and Spock, sitting on a tree
fandom=Star Trek: TOS
author=morgandawn
copyright=Uploaded by author.
date=July 2009
}}

or

{{image
warning={{underage}}*
description=Snape and Harry, sitting on a tree
fandom=Harry Potter
author=morgandawn
copyright=Uploaded by author.
date=July 2009
}}

Something like that. Nothing's set in stone, obviously, but that's the idea we started out working with.

* "{{underage}}" being a template that will put a colourful warning box like this on the image page, so that editors adding that image to pages will remember to add it with the proper warning template.
morgandawn: (Default)

Re: is anyone looking at usability and inclusiveness?

[personal profile] morgandawn 2010-04-24 05:28 am (UTC)(link)
so...if I read this correctly .... we would need to custom hand insert each warning code into the template for each image? for this to be accessible, I was thinking of us clicking on a series of warning boxes, the custom template being created in connection with those checked boxes which would then be inserted into the upload page for me to fill out with the actual details. worse case, I would have to hand copy and paste the custom code that was created for me onto the upload page after having to navigate away from the template page.

the last idea would be tagging via check boxes.

FYI.... this is what I mean about making policy work hand in hand with design/usability. We need to consider how a policy will actually be carried out - not wait until the policy has been decided to find out the design will be cumbersome or unworkable. Thank you for taking the time to explain the template process (and the design limits we're facing).

Edited 2010-04-24 05:38 (UTC)
christycorr: Toothless (How to Train Your Dragon) (It's so pretty!)

Re: is anyone looking at usability and inclusiveness?

[personal profile] christycorr 2010-04-24 06:48 am (UTC)(link)
I would love to create a more AO3-like system like the ones you're suggesting, really, and I plan to look into how the Commons image upload pages are set up—an upload form like that would be far more ideal and user-friendly—but I just don't know if we'd be able to implement that. I'll get back to you on this :)

In any case, if we end up doing it the traditional way, I will certainly edit the image upload page with basic instructions, and probably a fill-in-the-blanks copy of the template so that users don't have to click away from the upload page.
Edited 2010-04-24 06:49 (UTC)
ext_3626: (Default)

Re: is anyone looking at usability and inclusiveness?

[identity profile] frogspace.livejournal.com 2010-04-24 01:22 pm (UTC)(link)
Christy, thank you for the explanation. :)

I think it would be helpful if we could have examples of the templates you are thinking of and try them on images we already have on the wiki to figure out if and how practicable they are. Image formatting is incredibly complicated already (what, with floating left not working, no explanations on how to add galleries, group pictures, change display sizes, etc.) and most people feel a bit intimidated by that. So it would be good if we could try these templates *before* we decide on a final version of the policy.

Here are a few examples of images uploaded to Fanlore. It would be nice to know where they fit in your policy and if and what kind of information should be added to them:

http://fanlore.org/wiki/Image:Terma1.jpg This is an old archive banner that I saved years ago. It might or might not be still available via wayback. I have no idea when it was made or what the copyright status information should be. It's a manip made by The Theban Band. Manips use copyrighted images as source. I haven't asked for permission, but neither did the people who used Theban Band images at conventions, in professional magazines or on TV shows. I think the most important thing was the stealing bandwidth thing.

http://fanlore.org/wiki/Gayle_F An artist page that includes a gallery of art created by this fanartist. Many of the images are explicit (so is a lot of art in museums).

http://fanlore.org/wiki/Image:Spock_Enslaved.jpg Cover of a gen zine, source is mentioned in the comments. No idea about dates (do we need the date when the artist made the image? when the zine was published? when the picture of the zine was taken?), licenses or copyright information.

http://fanlore.org/wiki/Image:Rhapsdosy.jpg Zine cover with link to the ebay seller who uploaded it.

http://fanlore.org/wiki/Image:Holmes%26Watson.jpg Scan from artist's personal collection, uploaded with permission.

http://fanlore.org/wiki/Image:Buckwheat1and3.jpeg Scans from the personal collection of someone who owns the copies of the zines these scans are made from.

http://fanlore.org/wiki/Image:Box_of_Magic-A_Merlin_Big_Bang_Challenge.jpg Screenshot of a website, bigger than 150 KB, no additional information on the image page.
ext_3626: (merlin - dragon spell)

[identity profile] frogspace.livejournal.com 2010-04-23 11:07 pm (UTC)(link)
I didn't see anything about violence either...