AO3 News

Post Header

Published:
2018-05-09 16:40:08 -0400
Tags:

Outlines of a man and woman speaking with word bubbles, one of which has the OTW logo and the other which says 'OTW Announcement

The Legal committee of the Organization for Transformative Works (OTW, the AO3's parent organization) worked with the Archive of Our Own team to update AO3's Terms of Service (ToS). This update is focused on data privacy, and on explaining in more detail how we process the data you give us while you use AO3. Below, you can read a summary of the changes. There's also a full version of the updated ToS available for your review (HTML, PDF, Word).

Data collection

We only collect the information we need to offer certain features (such as kudos, which require us to log IP addresses for guests), and to share the content you provide in your works, comments, and profile pages.

We will never sell your personal information to third parties. The OTW does not run ads on AO3, and will never use your information to market third-party content to you. To learn more about what we can and cannot do with the data you provide, please read the Privacy Policy section in the proposed ToS text. Although we've added quite a bit to clarify the policy, the ToS represent current and longstanding OTW and AO3 practice.

Age policy

We've also made some changes to the minimum age at which you can create an AO3 account, in accordance with the European Union's new data privacy regulations (GDPR). While the general minimum age remains at 13 years old, there are specific requirements for those who reside in the EU. We’re very sorry to inconvenience current users who may be in this age range; you are very welcome to rejoin AO3 once you're old enough to do so!

If you are under 16 years old and live in the European Union, please check your country's current age of consent for data processing. You must be of age in your country of residence to give us consent to use your data in order to use the Archive, or else we can't legally, for example, store your kudos or comments (even as a guest!). This is very, very important: If you live in the European Union, please check whether you are of age to use the Archive without us having to ask your legal guardian and/or parent(s) for their written consent.

Once these ToS changes have gone into effect, everyone who visits the Archive will be asked to confirm that they agree with the new ToS, which includes stating that they are of age to use AO3.

We are legally required to remove accounts belonging to age-barred users. Now is a good time to review your profile and works for any outdated information about your age!

Summary of changes

The proposed Terms of Service contain some minor language changes (such as capitalization and punctuation) for clarification, and the following significant additions and changes:

  • We added an item to the 'What We Believe' section stating that we do not sell data, and clarifying that different OTW websites have their own ToSs, adding links to them.
  • We clarified that future changes to the AO3 Terms of Service should be published on AO3. (They always were anyway, but we figured we should make it explicit.)
  • We added the new AO3 age policy (as described above) in compliance with the GDPR for EU users between the ages of 13 and 16, and added references to hiding/deleting accounts and content submitted by age-barred users.
  • We defined data processing in the context of AO3 and explained that by using the Archive, you are giving us your consent to process the data you submit in order to maintain the site. This includes things like displaying your works and comments to others. Please remember that any information you choose to share publicly (for example, in your open works, profile or comments) will be available to everyone.
  • We explained in which contexts we collect your IP address, e-mail address and other user-specific information such as Favorite Tags and any errors you may encounter while browsing, and what we use this information for.

This ToS update essentially underscores a commitment we have always made: the Archive is not here to profit from fans, or to collect data about your fanwork browsing habits and sell them. We have never done that; we will never do that.

It is part of our mission and values to respect your privacy, and to collect and store as little data as we can. That being said, we know that our community routinely shares information about personal relationships, religious beliefs, political affiliations, and sexual orientation in profiles, work notes, bookmarks, tags, comments and works. Since these are "special categories of personal data" under the GDPR, we needed to add that information explicitly to the ToS.

If you've ever made a donation to the OTW, our parent organization, rest assured that we don't match up any data about the Archive's users and the OTW's donors. We take our commitment to preserving your fannish identities very seriously.

Please read the proposed changes to our ToS (HTML, PDF, Word) and leave your comments on this post with any questions, suggestions or feedback you might have about the proposed text. All comments must be received by May 23, 2018. After that, the OTW Board will vote on the final text of the Terms of Service.

Comment

Post Header

Published:
2016-05-16 14:52:27 -0400
Tags:

Banner by Diane with the outlines of a man and woman speaking with word bubbles, one of which has the OTW logo and the other which says 'OTW Announcement'

Our hard-working, all-volunteer Abuse team has asked for a change in how abuse reports are submitted. Based on the past seven years’ experience, it has determined that anonymous complaints are unhelpful and highly burdensome. First, the majority of anonymous reports are duplicates. Second, a large number of anonymous reports have, in the past, been rejected, but we have no way to contact the reporters to explain what is and is not a violation of the Terms of Service. Finally, many anonymous reports do not include the necessary information, which means Abuse closes them without investigating since there is nothing else it can do—the team can’t follow up to get more information. We realize some people may not feel comfortable reporting things under their own name. However, reports may still be made using a throwaway or dedicated email account, as long as there is a way to contact the person making the complaint.

Current text:

1. Submitting a complaint

Complaints may be submitted to our abuse team. Except in the case of copyright complaints, a complainant may submit a complaint via the web form, which does not require identifying information. Depending on the nature of the complaint, however, anonymity may hinder our ability to verify the complaint or affect the credibility of the complaint. In order for the abuse team to follow up on any allegation, the exact location (URL) and nature of the alleged violation must be supplied in the original complaint. Repeated unverified abuse complaints from the same source may be subject to summary rejection.

2. Treatment and investigation of complaints

Only people who need to know about a complaint will be informed about it. The details of any individual complaint are confidential and must be used only in resolving that complaint. The subject of a complaint may also be among those who need to know about it. Only information provided in the complaint will be passed on. The complainant has complete control over what information is submitted to Abuse, and can submit the complaint anonymously. (Legal names and other information sufficient to identify a person in the physical world will never be disclosed as part of a standard abuse complaint. For further clarification, please refer to our privacy policy.)

Proposed text:

1. Submitting a complaint

Complaints may be submitted to our abuse team. Except in the case of copyright complaints, a complainant may submit a complaint via the web form, which does not require identifying information. Depending on the nature of the complaint, however, anonymity may hinder our ability to verify the complaint or affect the credibility of the complaint. In order for the abuse team to follow up on any allegation, the exact location (URL) and nature of the alleged violation must be supplied in the original complaint. Repeated unverified abuse complaints from the same source may be subject to summary rejection.

2. Treatment and investigation of complaints

Only people who need to know about a complaint will be informed about it. The details of any individual complaint are confidential and must be used only in resolving that complaint. The subject of a complaint may also be among those who need to know about it. Only information provided in the complaint will be passed on. The complainant has complete control over what information is submitted to Abuse, and can submit the complaint anonymously. (Legal names and other information sufficient to identify a person in the physical world will never be disclosed as part of a standard abuse non-copyright complaint. For further clarification, please refer to our privacy policy.) Except in the case of copyright complaints, the name and contact information provided by the complainant will not be disclosed to the user.

Comment

Post Header

Published:
2016-01-25 20:43:38 -0500
Tags:

Banner by Diane with the outlines of a man and woman speaking with word bubbles, one of which has the OTW logo and the other which says 'OTW Announcement'

The OTW Board of Directors has approved changes to the Archive of Our Own’s Terms of Service and Frequently Asked Questions. Proposed additions in bold; bracketed to be deleted.

This post marks the start of a two-week public comment period. Your comments and questions will be reviewed in order to evaluate whether further changes need to be made.

Thank you for your assistance.

III. Archive Privacy Policy

E. What we will do:

1. We may collect personally identifying information when you register for a user account with the Archive, visit any of the Archive sites, or use any of the Archive services. We may use third-party services to store, process, or transmit data, or perform other technical functions related to operating the site. These services may include spam detectors, backup services, icon hosting, and e-mail services. We endeavor to use only services with comprehensive privacy policies but cannot guarantee their performance. We or the services we use may store or process your personally identifying information in data centers which may be located in the United States or other countries.

2. We will use your e-mail address internally, and if you make it public on the site, anyone can access it and use it for any purpose. We may occasionally send e-mails to you from the Archive. We reserve the right to send you notice of complaints or violations [or suspensions] of the Terms of Service, as well as to reply to any e-mail message you send to the Archive.

3. We may retain:

a. the e-mail addresses of those who communicate with us via e-mail;
b. user-specific information about what pages users access or visit;
c. the IP address of each visitor to our sites;
d. any information that a person sends to OTW or Archive e-mail addresses (i.e., any e-mail to an administrator or other official address).

….

V. Assorted Policies

A. Collections, Challenges, and Exchanges

Archive users may create collections and encourage other users to submit fanworks to those collections. The collection maintainer can set any constraints they want on the collection, including rules about anonymous works (see A.4 below) but must otherwise follow the content policy (e.g., if the collection content is explicit, it should be marked as “explicit” or “choose not to rate”). The collection maintainer may be able to ask users for suggestions for new fanworks (“prompts”), collect prompts, match participants with prompts (including contacting them via the contact information provided to the Archive or to the collection maintainer), and show the prompts on the Archive, following the general rules governing works on the Archive. Where collection rules allow, prompts may be anonymous or limited-visibility, as detailed in A.4 and A.5 below.

A challenge maintainer can communicate with challenge participants. The challenge maintainer may have access to participants’ email addresses for this purpose.

FAQ:

Assorted Specialized Policies

Collections

What do you mean by "collections"?

Collections are groups of works collected together under one heading. Collections can be fic or art fests, exchanges, 'big bangs' matching artists, authors, and/or podficcers, or other types of creative challenges, as well as simple collections of fanworks chosen by the collection maintainer. Learn more about collections.

What information can the collection/challenge maintainer see about participants?

The maintainer can see prompts as well as the username and email address that participants use to sign up, in case the maintainer needs to communicate with participants.

What's the point of having separate rules for collections/challenges?

The rules are basically the same as for everything else on the Archive. This just allows another way to group fanworks by areas of interest. There is one important special rule: if the collection maintainer says in the rules that submissions are final, then you can't withdraw your contribution from the collection, though you can always orphan it. We put this rule in place to allow gift exchanges. Ordinarily, removing a fanwork from the Archive is sad, but it's up to you. But when you've added a fanwork as a gift, and possibly received a fanwork as a gift in return, we think it's fair to say that the other participants should continue to enjoy the benefit of your contribution. In those cases, orphaning allows you to sever your connection with the fanwork while not removing it from the collection. This policy was based on prior experience with the Yuletide Rare Fandoms gift exchange.

I think my fanwork would be perfect for a collection, but the maintainer won't add it to the collection!

Unless there's an independent violation of the Content Policy, we won't intervene in collection decisions, even if they are arbitrary, biased, or wrong. You may want to add tags to your fanwork that will be of interest to people who are fans of relevant collections.

How can I start a collection?

Please consult our Tutorials. Please note that participants may provide information to the maintainer for purposes of participating in a collection or challenge. Any use of this information other than to manage the collection or challenge is a violation of our Terms of Service and can result in the termination of the maintainer's account.

Other Changes

 

Can orphaning be reversed?

Usually not. [If you orphan a work inadvertently, or wish to rewrite it and repost under your name, and you can verify your identity as the author in a way we consider reliable enough, we may be able to reverse the orphaning. But orphaning may be irreversible in some cases,] Orphaning is irreversible in most cases, so please use this option carefully.

What if what I want to post isn’t similar to one of the examples listed in the Terms of Service FAQ?

In general, you can post any non-ephemeral, transformative content that is fannish in nature. If you have doubts about any particular examples and you don’t want to risk posting it, you can always contact our [Support] Abuse team to ask, using the [Support] Abuse form.

Comment

Post Header

Published:
2014-07-09 07:12:01 -0400
Tags:

Our upcoming code deploy will include a change to the default setting for Archive Warnings when posting a new work. Warnings are added to a work by selecting the relevant checkboxes in the "Archive Warnings" section of the form, either when creating or editing a work.

It is mandatory to choose at least one of the options, even if it's just to indicate that you do not wish to warn. Currently, the checkbox "Choose Not To Use Archive Warnings" is checked by default, allowing users who do not want to use warnings to skip straight to subsequent sections of the form. Unfortunately, this means that users who want to add warnings (or indicate that no warnings apply) must also remember to de-select "Choose Not To Use Archive Warnings." Because this isn't entirely obvious, a lot of works were unintentionally set to both "Choose Not To Use Archive Warnings" and "No Archive Warnings Apply".

After our code update, however, "Choose Not To Use Archive Warnings" will no longer be checked by default, requiring users to actively select it (or another option) in order to proceed. We hope this change will encourage creators to interact more meaningfully with the Archive warnings field, and ensure "Choose Not To Use Archive Warnings" is only ever applied to a fanwork deliberately.

Please note that other combinations that are seemingly contradictory are actually allowed by our Terms of Service. For example, you can tick both "Underage" and "Choose Not To Use Archive Warnings" if you want to warn for situations involving characters under 18, but not for other aspects of the work. You are always free to include more details about the content of your work in the Additional Tags, or in your Notes.

For more information about our Archive Warnings, please check the Warnings and Archive Warnings section of the ToS.

Comment

Post Header

Published:
2013-02-25 13:17:12 -0500
Tags:

There has been a very active and thoughtful response to our recent announcement in favor of allowing meta on the AO3. We'd like to take this opportunity to express our gratitude to everyone for raising their concerns, showing their support, and otherwise engaging with us as we work to define our policies, refine our processes, and improve our communication. In addition, we'd like to respond to a number of the issues raised and clarify how this decision was reached and what the process will be from this point forward.

For the purposes of this and the previous post, the term "meta" refers to nonfictional fanworks in all media. While text-based nonfiction fanworks have been a frequent focus, this decision and the surrounding commentary is meant to encompass fanworks in all media; this is one reason why multimedia hosting, posting, and filtering will be referenced frequently in conjunction with the decision to support meta.

There is still a long way to go before meta can be fully supported on the AO3, and we will address a number of the concerns about implementation and timing below. Determining how meta should be supported — for example, the details of how multimedia hosting on the AO3 will ultimately look — is a matter for our committees and users to decide through committee collaboration and user input. However, determining whether supporting meta on the Archive is consonant with the OTW’s mission falls squarely within the Board’s purview and duty.

History of the discussion

When the initial question of meta was posed to Board, it was framed as a request for clarification on whether meta fell under transformative works as we defined them for the AO3, and how to proceed with reports of meta as a violation of our Terms of Service (ToS). The Board voted last August to send the meta issue back to the committees for more discussion, in the hope that the committees could work out among themselves issues that the Board had found insoluble. The decision called for balancing the competing concerns of several committees, and the Board had been unable to reach a satisfactory agreement. However, the execution of that plan dragged on for months as we dealt with Board member hiatuses, resignations, and appointments on top of other day-to-day business, and the vote was never put into action.

When the Board reconvened in 2013, we initially had intended to continue with the plan set out by the 2012 Board, but we quickly realized that — partly as a result of the Board’s dramatically changed composition and partly because of a new focus on clarifying the Board's purview — we no longer felt it to be the best course of action. We looked at the conversations that had been happening within and outside the organization for the previous six months and came to the conclusion that it was in the best interests of both our users and our personnel that a basic decision be made as soon as possible, rather than occupy staff and volunteer time in further stretching out a question that we felt it was our responsibility as Board to settle: the question of the scope of the OTW and AO3's missions with respect to meta.

We had many users who had been waiting all that time to find out if their meta could stay on the Archive, and several committees who needed a determination in order to perform their duties. We took a fresh vote, which was unanimously in favor of interpreting the OTW and AO3's missions as inclusive of owing meta the same protections and support as other fanworks. Once that vote had been taken, sending the issue back to committees for a discussion that would not have changed the Board’s stance would have been disingenuous. We felt it was preferable to state a firm decision and engage the committees in determining how best to carry it out.

We are aware that the Board's decision seemed very abrupt to people both inside and outside the OTW, and we acknowledge that more transparency would have been preferable. The Board’s overall workload and the emotional burnout many of us have experienced as a result of the length and intensity of the meta discussion were obstacles that prevented us from communicating effectively. We regret our shortcomings in this area and will strive to do better in the future; we are working to reduce workload and burnout and clarify policies and purview in an effort to prevent this from recurring.

We are committed to fully engaging committees and users in determining how the decision will be implemented, and a revised Archive TOS and FAQ are currently being drafted under the leadership of the Content Policy Workgroup. As with other TOS and FAQ revisions, they will be posted for public comment before they are formally adopted.

Replies to some questions and concerns

We recognize that this decision will not be popular with all users, members, or even OTW personnel. Conversely, the choice to allow meta — and turning over the ability to define and craft specific policy to our committees — is a decision many support. The concerns raised by those leaving comments are ones the Board spent a great deal of time discussing, and we are happy to share our reasoning and to continue answering questions to the best of our ability. Here are some responses to common concerns and questions:

  • Meta does not require new code to be hosted in its bare form — unlike image or video hosting no new code is required for a basic level of service. For example, a nonfiction essay can be uploaded just like a fictional story, or a meta comic can be linked just like a fictional one is now, or a vid focused on commenting on the canon can be embedded like vids that build fictional narratives currently are. While there are ways the AO3 could be better organized to deliver meta, a basic level of hosting is already available.
  • The AO3 is intended to eventually have filtering based on work type/medium, allowing meta to be found and filtered. The intention is to expand the AO3 functionality to better host non-textual fanworks (e.g. vids, podfics, art, etc.), and the most-requested behaviors with respect to meta (filtering, tagging, etc.) all intersect with what will be in place for multimedia hosting and posting.
  • Refusing to host meta and waiting until we have sufficient code for works types would unduly punish users who have already posted meta works in good faith. In addition to posting meta based on good-faith interpretation of the TOS, users have been posting many types of works the AO3 is not strictly prepared to deal with on a technical and usability level, which includes meta of all media and most non-textual fanworks. Allowing and encouraging users to post all types of fanworks has been a cornerstone of the AO3's philosophy as an archive, and it would be disingenuous and unfair to punish one type of fanwork or creator but not others on this basis.
  • While text-based meta faces much less legal challenge than some other fanwork types, it still faces other challenges such as loss of hosting due to failing archives or discontinued blogging platforms. Non-text-based meta, such as meta art and vids, shares many of the same legal challenges as other non-text-based fanworks.
  • Fans should be able to archive all their fanworks together. Besides this general principle, there are specific instances of at-risk archives that include meta fanworks. Grandfathering in previously posted meta or disallowing meta except for that taken in through Open Doors leads to an inconsistent policy likely to cause confusion, conflict, and difficulty in enforcement.

We hope this answers some of your comments and concerns. We welcome further input and look forward to working with our personnel and our users in continuing to welcome a broad range of fannish endeavors under the OTW umbrella.

Comment

Post Header

Published:
2013-02-15 14:05:33 -0500
Tags:

After a long period of discussion, the OTW Board has voted to allow the posting of meta on the Archive of Our Own. We considered a range of issues while making this decision, including how this move would fit into the overall mission of the OTW, the technical and financial resources required, and demand from users of the Archive and members of the OTW. We determined that there is already a demand for meta on the Archive, and that this use of our resources is consonant with our purview and mission.

We're aware that this decision has taken some time, and we sincerely apologize for the delay. We had hoped to reach a decision sooner, but the complexity of the discussion meant we needed to think carefully about the issues. As the term of some OTW Board members ended while the discussion was ongoing, we also needed time for the new Board members to get up-to-speed with all the issues involved.

What will happen next?

Agreeing to include meta on the Archive is just the first step in this journey. The Board will now work with all related committees to define exactly how meta will be handled. Our committees, including AD&T (which will be doing the work on the technical side), Abuse, Support, and others, will be working with our Content Policy workgroup to design a workable policy.

One of the main tasks ahead of us is to agree on some definitions and policies. We need to agree on definitions that are usable and enforceable. While any category is inevitably fuzzy, we want to preserve the Archive as a site for fanworks (so for example, we don't want it to become a general blogging site). Once we've agreed on these definitions, our committees will have a whole range of tasks ahead of them, including:

  • Drafting revisions to our Terms of Service and FAQ. Revisions to the Archive TOS will be subject to a public review period (as detailed under Section IB of the TOS) before becoming final.
  • Determining technical plans for making meta more accessible. We are already planning changes to posting and browsing on the Archive to allow for multimedia hosting. We do not expect meta to require any additional coding to implement beyond what will be required for these changes, and allowing meta won't change the existing prioritization of these features, but we will need to factor it into our design.
  • Determining tagging policies to allow for multimedia and meta browsing.

What will be allowed?

Our Content Policy workgroup will be posting guidelines on what will fall under the 'meta' category and the policies which will apply to it in the next two weeks.

What does this mean for me?

Going forward, we hope that this will mean you can find and enjoy fannish meta more easily (and screen it out if you're not interested).

If you currently have meta posted on the Archive, or you plan to post some in the near future, you should be aware that our policies are still being finalized. As action on existing meta posts was suspended while Board deliberated on this issue, in the coming months some users may be contacted in connection to how their posts fit the new policies. We recommend that users wait until these policies are made public before putting a lot of effort into new meta posts. However, we hope that, long term, meta writers will feel their contributions to the archive are welcome and can join other fanworks in finding an audience at the AO3.

Thoughts?

If you have thoughts and feedback you'd like us to consider, we ask that you comment here on the AO3 version of this post, to make it easier for the various committees involved to answer you and collate your replies.

Comment

Post Header

Published:
2012-11-25 15:14:53 -0500
Tags:

The Content Policy workgroup is presenting a set of proposed changes to the Archive of Our Own’s Terms of Service and Frequently Asked Questions. These are largely clarifications and changes made to deal with functionality as the Archive has developed. This post marks the start of a two-week public comment period. The Content Policy group will track any comments or questions made here and will then evaluate if further revisions need to be made.

The content change files are available in either a FAQ revision PDF and and ToS revision PDF or a FAQ revision doc file and ToS revision doc file format and will show proposed changes to the language at different points in the document.

The proposed changes do not include any discussion of meta, which is still under review by the Board. This document is mostly a matter of language cleanup and putting the answers to some common Support questions in the AO3’s FAQ.

Comment

Post Header

Published:
2011-09-03 19:00:10 -0400
Tags:

In preparation for hosting fanart on the AO3 (that is, you will soon be able to upload art directly to our servers and not just link it from elsewhere), we are revising the official Terms of Service and our FAQ!

As always, we actively seek and very much appreciate feedback on all archive policies. The coding for fanart is still underway, and there is time to make changes, so if there's anything in this draft that concerns you, please let us know.

Here are the proposed additions to the FAQ:

* When can I use pictures I have made on the archive?

The basic rule is that a fanwork based on an existing work should be transformative. Transformation means adding something new, in meaning or message, to the original. We consider that fanart, like fan fiction, is generally transformative. Please remember that the ratings and warnings policies apply to images.

You can also use pictures you've made to complement a fanwork--so, if you are illustrating a story, you can use illustrations of the setting, the original characters, or anything else that fits with the story, as long as you otherwise follow the content policy.

We do not allow sexually explicit photos of minors, nor images manipulated so that they look like sexually explicit photos of minors (even if the manipulation is obvious). This is necessary for us to comply with US law, which has special rules for photographs and video of human beings under age 18. In addition, under Section IV.H of the Terms of Service, we may remove content, including photos or drawings, when we determine that it is necessary to resolve a threatened or pending lawsuit. We will not screen or ban images for offensiveness.

 

* When can I use existing (nonmanipulated) pictures in my fanworks on the archive?

The basic rule is that a fanwork should be transformative. Transformation means adding something new, in meaning or message, to the original. Existing works, including pictures, can be part of a transformative work. Please remember that the ratings and warnings policies apply to images.

When you're using an existing picture, commentary and critique are particularly favored kinds of transformativeness. A use that highlights the way that framing, angle, or other pictorial elements affect the pictures’ meaning; a use that draws attention to the roles of different people in the pictures; and a use that contrasts different pictures are all examples of potential transformation. Humor can also be transformative: unlikely subtitles may change the meaning of the picture substantially. Commentary can be explicit or implicit, as when it’s done by pointed contrasts between images, where the use of a picture recontextualizes it and gives it new meaning.

The number of pictures should be appropriate to the purpose: if you’re illustrating the relationship of a character’s costumes to her story arc, then you are likely to need more pictures than if you merely want to introduce the character so your audience knows what s/he looks like.

Where possible, credit or attribution to the original source of your image is also helpful.

We have drawn on the American University Center for Social Media’s Code of Best Practices in Fair Use for Online Video in our discussion here. You may find a full copy of the code here http://www.centerforsocialmedia.org/fair-use/related-materials/codes/code-best-practices-fair-use-online-video if you want to see more detailed discussion and examples, though they are focused on video.

 

* When can I use pictures in my skins on the archive?

We generally consider skins containing pictures to be fanworks, so please follow the guidelines in the sections above. In addition, since skins are created by individual users, the OTW does not endorse particular skins in any way. We do screen public skins for technical compliance, to limit the proliferation of public skins in order to keep the public skins feature usable for other people, and for obvious violations of the content policy, but it's the user's responsibility to make sure a skin complies.

You can use pictures you've made for skins, even if they aren't fanworks, as long as you otherwise follow the content policy--e.g., you can use a picture of the view from your window.

You can put attributions for images in your skins into a comment like this:

/* This image comes from SOURCE and is used here for INSERT TRANSFORMATIVE PURPOSE */
header { background: url(http://url/of/image.jpg); }

 

Here is the current text in the Terms of Service about user icons, which are the only artworks currently on the archive:

J. User Icons

User icons should be appropriate for general audiences. They should not contain depictions of genital nudity or explicit sexual activity. For more information, please refer to the ToS FAQ.

Here is the proposed new text of the Terms of Service for our new expanded set of artwork:

J. Images

A. User icons

User icons should be appropriate for general audiences. They should not contain depictions of genital nudity or explicit sexual activity. For more information, please refer to the ToS FAQ.

B. Other images

Other images are subject to the general content policy, including the ratings and warnings policy. No sexually explicit photographs of minors (people under age 18) or sexually explicit photomanipulations that appear to be pictures of minors (people under age 18) are allowed. For more information, please refer to the ToS FAQ.

Relatedly, we propose to delete the last paragraph of Section IV.D, which currently reads:

Please note that the first version of the Archive will only host text and user icons. Future policies will focus on other media.

Mirrored from an original post on the OTW Blog.

Comment


Pages Navigation