On Original Content and Gray-Area Fanworks

In our last newsletter, we mentioned that we were evaluating the policy on hosting original fic on the Archive of Our Own. This has generated a lot of awesome and passionate discussion, but also a lot of confusion, so we’d like to clarify a few things. (A personal note from Rebecca Tushnet: I phrased the inquiry badly, and I apologize. I’m 100% committed to supporting transformative works, as is everyone on the Archive.)

To address one of the main causes for concern — we are all on the same page in terms of caring about fanworks FIRST. That is why all of us here are working on the OTW and the AO3. That is our main goal and that is always going to be the main goal. The question we’re chewing over is not whether to make the AO3 also into a site for hosting original works but what to do when fans using the AO3 also use it to post works which aren’t clearly transformative works, but which are considered part of the fannish experience by some fans.

We’re talking about things like anthropomorfic, works which are in a mixed archive that needs rescuing via Open Doors, doujinshi from yaoi fandom, and other examples (there’s a longer discussion below, if you want to read on). There are a lot of works in this grey area which are hard to pin down. Among other things, this makes our current policy a practical problem of enforcement. We don’t want people who are posting works that they consider fannish to have to wonder if Abuse is suddenly going to show up and say “take that down.” This is the reason why we started to consider changing the policy — not because we actively want to host original fiction.

Many people have expressed a concern that loosening the policy on original works might weaken our legal position. We would not even be considering a change if we felt in any way that this would be the case (see below for a more detailed explanation of why we’re not concerned on this score). We also wouldn’t consider a change if doing so would consume more of our resources. In fact, it’s the other way around. What would consume more of our resources in this case would be policing fannishness. We don’t have a giant Support and Abuse team (we always are looking for more volunteers!) and we don’t really want to be making fine-line judgments about the fannishness of content.

Obviously we would have to reinstate a more aggressive policy and come up with some way to police it if original fiction did somehow start to take over the archive or consume too many resources. But we think that this is very unlikely. The archive is fundamentally designed for fanworks, and that’s what our coding resources are always going to go towards.

Specifically — since this also seems relevant — this is not a choice between hosting original fic vs. hosting fanart or vids. If it were, of course we would choose fanart and vids, without question. We’re already working on that; but this conversation has no bearing on that at all. Hosting fanart and vids is a major technical project that we are working on (as fast as we can!). A lot of design and content policy and coding groundwork is being done towards that goal and has been for some time. You can help us out on that, in fact, by giving us ideas!

Your comments and suggestions are very welcome, either now or later on. All proposed TOS changes are posted for public comment, and we are only now beginning to consider what a change might look like.

For those who are interested in even more detailed discussion, read on to learn why we are thinking about this now.

The archive is not a place for all fictional works and it will never be. Since we began planning for the Archive, though, some fans have been asking for the ability to archive certain non-canon-based works along with their canon-based works. Archivists with mixed collections have told us that they want to use Open Doors, but want to make sure that their contributors are all welcome on an ongoing basis. We try to take such requests from fans seriously, just as we decided very early on to accept real-person fiction despite the fact that the legal and social issues surrounding RPF differ substantially from those surrounding fictional-person fiction.

We’re thinking about various types of fannish activity (in art and vids as well as text) and how we can write a policy that is inclusive of those traditions while not opening us up to original creative works in general.

We are also running into persistent problems of blurry edges and enforcement, as noted above. In practice, archive users seem to be using the tag “original” in multiple ways.

1. Mission

The main question is whether a change would interfere with our mission, something we take very seriously. The OTW is committed to protecting fanworks and serving fans, and fans define themselves (and the things they create) in a lot of different ways. In particular, we are trying to do a better job of making welcome international fans and fans from other communities that clearly are making transformative fanworks, but that don’t always look exactly like the fannish communities many of our Board and volunteers come from.

When we started getting input on this topic, we found that in many parts of fandom, the distinction between original work and fanfic is kept very clear; in other parts of fandom, this distinction is extremely unclear, and archives (the kinds of archives which might ask Open Doors for help preserving them) include both kinds of works.

Here are some examples on a spectrum — probably to each of you some of these will seem more worth hosting and protecting, and others less so, but hopefully they illustrate the broad grey area we are concerned about:

  • Some Xena writers have embraced the idea that “the characters of Xena and Gabrielle were in fact archetypes that could be explored in different times and diverse cultural backgrounds.” In such “uber” fic, it is apparently common not to mention Xena or Gabrielle by name, not to have flashbacks or other direct references to the show characters, and otherwise to proceed by creating new archetypal female heroes and companions. The context provides the fannish linkage.
  • In major fannish challenges like Yuletide that we want the archive to be able to host, participants often push the edges of fannish sources — things like the song “Jesse’s Girl” become inspiration for stories, without really being something we can call fandoms.
  • Similarly, in Anthropomorfic, we have stories not just in the fairly clearly defined Mac/PC fandom, which has a source, but about characters like “Fandom” and “LJ”, and pairings like “Coffee/Milk/Sugar” which don’t clearly fall into the category of transformative fanworks, and yet are part of clearly fannish experiences like the Porn Battles and challenges.
  • In Japan, “BL” (“Boys Love”, often called “yaoi” outside of Japan) fandom includes a broad range of creators and formats. Fanfic/art/comics and original fic/art/comics are often seen as two genres of the same fan activity. Also, Doujinshi (sometimes referred to as Japanese “fan comics”) are defined mostly by production, distribution, and audience rather than by content. (Some feature original characters; some feature pre-existing ones.) The crucial distinction is that they are self-published outside of the mainstream manga industry. Both English-speaking and German yaoi fandoms similarly have a genre of original work, sometimes called “original fandom,” that is very popular and strongly connected to fanfic-producing fandom.
  • Jane Austen fandom boards often integrate original work into their forums, mostly Regency romance. In at least one board, the sub-forum for original fic is for original fic and fanfiction of other canons that are not Austen. They’re similar in style, similarly considered, and written and read by the same people.
  • Some writers of original slash consider their work to be a variant of their fanfiction, and it’s hard to draw an obvious line between for instance, an RPF story with the characters renamed, versus a completely original slash story.

In short: if someone strongly considers their output fannish, we don’t want to be the fandom police telling them that it isn’t. We don’t want to have a policy that would force Open Doors to say to a fannish archivist who needs our help that we would only save half her archive, even if we think the archive as a whole is an important part of fannish history and the stories in the archive talk to one another even if some are original and some are specifically fannish.

2. Our legal and nonlegal missions are overlapping, but not identical

Not all fan fiction, even very narrowly defined, needs the legal advocacy to which we are committed: Jane Austen fanworks, for example, are based on sources in the public domain, and they are welcome on the archive, along with works based on multiple other public domain sources. RPF for 18th century people, too, has no conceivable legal issues.

Additionally, though we’ve seen some concerns expressed on this point, we do not think that allowing non-canon based fiction weakens the Archive’s legal position any more than allowing fiction based on public domain sources or RPF does. Transformative works are valuable for the specific insights they offer, whether into a work or a whole culture, and that’s true even though there are also good stories that don’t count as transformative works. If a particular fanwork were challenged, we would defend the choice of that particular source.

3. Resources

The Archive is designed for fanworks and fandom; all our features are designed to serve them best; that is our continued commitment. Our tech people do not anticipate a technical/hosting/tagging burden from allowing the kinds of original works under discussion. If that changed, we would always prioritize core fanworks (though we would not remove any works already in the archive that didn’t violate the content policy — that is, there would be no purging).

In terms of resources, enforcing a ban also presents continuing challenges. For example, if an author selects a fandom and claims that a work is just an extreme AU, like the Xena Ubers discussed above, we would rather not start evaluating content. We might not even have staff familiar with the fandom.

Side note: This issue has also provided a useful preview of art policy: our discussions have made it pretty clear that we don’t want to spend much time judging a creator’s choice of connection with a fandom in visual art, any more than we’d want to evaluate whether a piece of fan fiction was in character. So, if White Collar inspires a fanartist to draw a picture, absent any other concerns, such as spamming, we would honor “White Collar” as a fandom tag for that artwork.

If we moved to a rule that works on the Archive are allowed as long as they fit into some identifiable fannish tradition, even if they don’t belong to a specific canon, we would alleviate most or all of our enforcement issues. Deciding whether something is meta/commercial spam/a personal journal is easier than deciding whether fiction by fans is “fannish enough.” We also anticipate enforcing our noncommercialization policy strictly: authors would not be allowed to promote sale of non-Archive works by “advertising” on the archive with stories.

4. Where do we go from here?

For those who are concerned about original fiction, we would welcome your suggestions for policy lines that we would be able to easily enforce. We encourage your thoughts on how you would deal with some or all of the gray-area categories mentioned above, from anthropomorfic to original slash.

Calling fanartists! Tell us about your ideal archive!

The Archive of Our Own entered Open Beta in November 2009; in the six months since we’ve had 18 code releases and have seen 5929 users, 5031 fandoms and 64347 new works added to the Archive. \0/ We’ve had a bunch of new features, big and small, and have made big improvements in performance, cross-browser compatibility and accessibility. We still have some big features to roll out, but now the first rush is over, we’re planning further ahead. One of the key things we’re thinking about for our longer-term planning is opening up the Archive to fanart and other media, and we’re looking for ideas from artists!

Fanartists – what features would you like in your ideal archive? We want to know:

  • If we were to replace the story box with an upload tool, would that do most of what you want, or are there other things you need?
  • What sites would you like to be able to import from automatically, and how should a multi-upload tool work?
  • What types of art would you want to host on the Archive? What special requirements would these have?
  • What things about the existing interface would work well for you, and what would you need to see changed / added?
  • What are your DREAMS? Whether you’ve seen a cool feature on another Archive, or it’s something you’re not even sure is possible, we want to hear from you.

Hosting fanart and (eventually) fanvids has always been an important part of the plan for the Archive, but up until now we’ve focused on building the text-based aspects of the site because, well, we had to learn to walk before we could run. Hosting other media represents a much bigger technical challenge, as well as additional legal complexity, and actually hosting fanart on the Archive itself is still some way off (we need to learn a LOT more about performance). In the meantime, though, it’s really important to us to make the Archive a more welcoming place for the whole fannish community, and we want to make sure that our design and development is working towards a truly inclusive site. So – tell us your dreams! We’ll work to make them a reality (and if you’d like to help in that work, we always welcome volunteers.

Mirrored from an original post on the Archive of Our Own, where you can comment with or without an Archive account. We’d like everyone to share in the same discussion, so comments are disabled on the mirrored version of this post.

Accessibility, Design and Technology Meeting – 27 March 2010

All the latest news on the Archive of Our Own below the cut! Mirrored from an original post on the Archive of Our Own.

This was a bit of a gruelling meeting, because it was held immediately after our All-Org meeting (two hours of hearing about the awesome things going on in other teams \0/). Because my team are totally insane extremely dedicated, we then had an extra-long meeting. We overwork because we care, people.


  • We’re currently reviewing the Archive FAQ to ensure it’s clear, accessible and comprehensive. The best people to tell us whether it does its job are the people who will use it – you, the Archive users! If you’d like to help us out, check out our post on how to help review the Archive FAQ.
  • We are currently reviewing the Archive of Our Own roadmap and updating it. The roadmap maps out the main features which will be built into the Archive, and shows roughly where they fit into our plans. The version currently available to the public is a bit outdated, so once we finish revising it we’ll post a shiny new copy for people to see and comment on. 😀
  • Archive user punk has created a Firefox search plugin for the Archive. (Thanks, punk!) We’re planning to create a new page where we can feature cool stuff created by users \0/.
  • We launched our new import from brain feature on the Archive – oh, how we wish it were real!

Recent changes

We just deployed a ‘small’ release of 50 issues to the main Archive – check out Release notes for Release Highlights in this release include the new plain text skin (yeay Cesy \0/) and commits from new coders Amy, queenypolita and linbot. Many thanks to all the coders and testers for the increible hard work that went into this release.

If you’d like to help check that all this new code works, please check out our post on verifying new code.

Deploy schedule

  • Sunday 4 April: We hope to deploy the next block of code for Collections and Challenges to our Test archive.
  • Saturday 10 April: All being well, we will deploy the new Collections and Challenges code to the main Archive – this will include the ability to match compatible participants in exchange challenges.

If there are things you’d like to do or say, please share them in comments, via the AO3 support and feedback form, by volunteering, or in whatever medium you feel comfortable with. Everyone is welcome to this party!

Mirrored from an original post on the Archive of Our Own, which is commentable with or without an Archive account.