[syndicated profile] otw_news_feed

Posted by xeno

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we’re posting a weekly spotlight series about the TOS and our policies. We’ll also be reading comments and answering questions on this and our other spotlight posts.


For our last post in this series, we’ll be talking about our non-commercialization policy. AO3 doesn’t allow users to engage in commercial promotion of any type, which includes everything from paywalls to tip jars, and quite a lot in between. In this post, we’ll discuss why AO3 doesn’t allow commercialization, what kinds of activities are considered to be commercial promotion, and what to do if you see commercial promotion on AO3.

Don’t go looking for things to report.

Please do not start searching for works to report after reading this post. We know that commercial promotion frequently appears on AO3. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

What is commercial promotion?

Commercial promotion covers all references or links to commercial sites, monetized features of non-commercial sites, and anything else that makes it clear someone is asking for or has received financial contributions.

On AO3, you can’t encourage anyone to give other people money, or talk about anyone having given people money in the past. This applies whether you are promoting yourself or a friend, or even if you’re collecting donations for other people or causes. If there is money changing hands, then it likely violates AO3’s TOS.

AO3 is a non-commercial space.

AO3 was created and is managed by the Organization for Transformative Works (OTW), a nonprofit organization committed to the defense and protection of fanworks from commercial exploitation and legal challenges. The OTW is entirely staffed by unpaid volunteers, and AO3 is itself entirely non-commercial. No one involved in AO3’s creation or management profits from it. The site is made available free of charge to all fans who wish to share their works with other fans and fan communities.

We understand that many people today choose to monetize their creative activities. However, in order to keep AO3 as the non-commercial space it was designed to be, users are not permitted to engage in any commercial activity on the site.

When you use AO3, you agree to follow our Terms of Service, which includes the non-commercialization policy. This applies to all parts of the site, whether you’re posting a work based on an existing source or creating content entirely original to you.

AO3’s non-commercialization policy applies to the entire site.

Real-world commercialization is banned everywhere on AO3. This includes:

  • Profile pages
  • Usernames, pseuds, and pseud descriptions
  • Works (including all tags, beginning or end notes, chapter notes, summaries, and titles)
  • Series (including titles, summaries, descriptions, and notes)
  • Bookmarks (including tags and notes)
  • Comments
  • Prompt memes, gift exchanges, and other collections
  • Any other part of AO3

It’s okay for fictional characters in fanworks to talk about fictional monetization. For example, it’s fine if a character has a fictional OnlyFans or Patreon within the story, as long as that commercial reference doesn’t direct the reader to a real-world OnlyFans or Patreon account for the work creator or anyone else.

What are some examples of commercial activities?

There is a wide variety of things that are not allowed under AO3’s non-commercialization rules.

Links or references to any commercial site or service. A “commercial site” is any site whose primary purpose is to facilitate the transfer of money. This includes, but is not limited to:

  • Storefronts like Amazon or Etsy
  • Crowd fundraisers like Kickstarter or GoFundMe​​
  • Tip jars or membership subscriptions like Ko-Fi or Patreon
  • ​​Payment platforms like PayPal or Venmo

Links or references to the monetized features of non-commercial sites. This covers any site that has features you can enable or opt-in to earn revenue, but the primary purpose of the site is social media, sharing artwork, or anything else that isn’t inherently payment-focused. This includes, but is not limited to:

  • Paywalls or early-access content like Wattpad Paid Stories or Webtoon Canvas
  • Storefronts like DeviantArt Shop or Instagram Shop
  • Tip jars or membership subscriptions like TikTok Donation Stickers or Twitch Prime

Previews and other promotions for paid content. This covers situations like excerpts or teasers shared in an attempt to entice people to purchase a book or become a paying subscriber. It also includes references to paywalled or early-access content (e.g. “Patreon subscribers get the new chapter one week early before I post it on AO3”).

Advertising content or services involving an exchange of money, such as buying merchandise, collecting donations, offering paid commissions, or selling published works.

Any other language which one might interpret as requesting or having requested financial contributions, whether for yourself or others. This covers indirect references, euphemisms, or other language intended to get around the TOS. Some examples of this include:

  • Thanks for the coffee!
  • My ☕ username is the same as my username here
  • This chapter is brought to you by my patrons
  • You know where to find me if you want early or bonus chapters
  • Check out my Twitter to learn how you can donate to me since I’m not allowed to discuss it here
  • If you want to hear more about my ideas, talk about fandom, or find more of my stuff for a coin, visit my Tumblr

Solicitation is not allowed, whether it’s for yourself or on behalf of someone else.

Commercial activity is not permitted on AO3. It doesn’t matter if you’re promoting yourself or a friend, or even if you’re collecting donations for other people or causes.

This means that if you paid an artist to create artwork for your fanfic, you’re not allowed to mention that they have a Patreon or use any other language that suggests people should also commission or donate to them. If you like a book by a particular author, you are certainly welcome to gush about what a great book it is, but you can’t link to the Amazon page where it’s for sale or encourage others to buy it.

What is the difference between a commercial site and a non-commercial site that has monetization features?

As mentioned above, a commercial site is a platform that is first and foremost intended to facilitate the exchange of money. For example, while you can use Ko-Fi as a blog, the site’s primary purpose is to encourage people to give each other money. Ko-Fi’s social features are secondary to its purpose as a donation and paid membership platform. This means you cannot link to or mention your or anyone else’s actual Ko-Fi on AO3 whatsoever.

An example of a non-commercial site that has monetization features is DeviantArt, an art gallery that is mainly intended as a place to share artworks. DeviantArt also allows its users to opt-in to additional monetization features, such as the DeviantArt Shop. Because DeviantArt’s paid features are both optional and not the primary reason people use the site, you can talk about or link to DeviantArt on AO3 – as long as you aren’t directing anyone to a paywalled post or referencing DeviantArt’s paid features in any way.

Can I link or mention a social media site where I talk about making money or collecting donations?

You’re allowed to link or mention social media like Tumblr or personal websites like WordPress, even if you sometimes post about commercial activities on those sites. However, you cannot reference commercial promotion on AO3 itself, nor may you link, mention, or give instructions for finding an account, page, or post that is solely promoting paid content.

Statements such as “Follow me on social media” or “Check out my Linktree” are fine. Directing people to an Amazon author page or to the Ko-fi link in your Twitter bio would not be allowed. This includes things like “Check out my Linktree to learn how you can support me” in cases where you are clearly referring to monetary support.

Can I post a fanwork created for a charity drive or for-profit zine?

While you cannot promote, solicit, or otherwise ask for donations on AO3, you are allowed to add your work to a collection or otherwise briefly mention why you created a fanwork, as long as you do so in a non-commercial manner. This means you can say “This was created for [Event]” or “Originally Written for [Name of Person/Zine]” as long as you do not directly link to a donation page or ask others to donate to them.

Keep in mind we also do not permit mentions of monetary transactions, regardless of when they occurred. A note such as “This was a $100 bid for Fandom Trumps Hate” would still be considered commercialization.

I’ve seen authors say their works are commissions. Is this allowed?

You are allowed to gift your work to someone else or otherwise briefly mention why you created a fanwork, as long as you do so in a non-commercial manner. Because not all commissioned fanworks were created for pay, we do permit usage of the word “commission” as long as there is no indication that a monetary transaction was involved in the creation of the work or that you are available to create other paid commissions.

For example, phrasing like “This is a commission for X” is acceptable, but “Commission for my Gold Tier Patron, Julie” or “My client agreed to let me post the first chapter of their commission” isn’t. The context makes it clear that both “patron” and “client” are references to a paying sponsor.

I’ve seen others ask for donations or advertise paid commissions. Why can’t I?

As our TOS FAQ explains, we don’t review content until it’s reported to us. You may have seen somebody else mentioning their paywalled content or otherwise engaging in commercial activities on AO3, but that doesn’t mean that it’s allowed. All it means is that nobody has reported that content to us yet, or that we haven’t finished processing the report.

What will happen if I get reported for commercial promotion?

First, we’ll review the reported work to confirm that you violated our TOS by engaging in commercial activities on AO3. If we determine that you did, we’ll send you an email telling you to remove the violating material.

If your work can be edited to fix the issue, you’ll be asked to edit the work. Your work may be hidden from other users until you do. If you choose not to edit the work, or if your work cannot be edited into compliance with the TOS, it will be deleted.

PAC will only ever contact you by email, and only after we’ve determined that your work violates our Terms of Service. We will never comment on your work or contact you through social media. Please make sure to keep your account’s email address up to date and check it regularly (including your spam folder), or else you may miss our warning email.

If you repeatedly post works that violate our commercial promotion policies, you may be temporarily suspended. Continuing to violate the TOS will result in your being permanently banned from AO3. You can learn more about warnings and suspensions in our TOS FAQ.

What should I do if I encounter commercial activity on AO3?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can report the work to us.

What about spam comments?

The best way to deal with spam comments, commercial or otherwise, depends on whether the comments are from registered accounts or guests.

How do I report commercial activity?

Although we ask that you do not deliberately seek out commercial promotion to report, if you come across commercial activity while browsing, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3.

Please don’t report more than one user at a time or submit multiple reports about the same user. When reporting multiple works by the same user, please submit only one report with links to each work you’re reporting, so that all information about that user is in the same place.

Please tell us exactly where in the work the commercialization is. The best way to do this is to give us a description or short quote that we can search for in order to immediately find the content. If you are reporting multiple works by the same creator, please group all the works into one report and provide this information for each work.

For example, a report of commercial promotion might look like this:

Link to the page you are reporting: https://archiveofourown.org/works/00000000

Brief summary of Terms of Service violation: Commercial promotion

Description of the content you are reporting:
This work by USERNAME advertises a ko-fi in the end notes of chapter 3.

If you are reporting additional works, please include all relevant links and other information in your report description:

Description of the content you are reporting:
This work by USERNAME advertises a ko-fi in the end notes of chapter 3.

Some of their other works also contain commercial promotion:

https://archiveofourown.org/works/23456789 encourages readers to purchase their book on Amazon: “If you’re curious what else I’ve been working on or want to support me elsewhere, check out my new short story on Kindle Unlimited!”

https://archiveofourown.org/works/34567890 contains an embedded image with a Patreon watermark. Underneath, the sentence “If you want more like this, click here” takes you to their commissions price sheet.

You can add more details if you like, but this example provides the basic information we need:

  • Who posted the commercial promotion: Tell us their username or if the work is anonymous or orphaned.
  • Where we can find the work(s): Enter one URL in the “Link to the page you are reporting” field, and (if applicable) include links to any other violating works in the description of your report.
  • What violates the TOS: Explain why you think commercial promotion has occurred, for example by including a quote and/or providing context for a comment exchange. A brief description of the situation is fine; you don’t need to be very detailed or quote an entire TOS or FAQ section.

You’ll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same work. While PAC investigates every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about commercial promotion?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you’ve found commercial promotion on AO3, or if you want to know whether a particular work contains commercial promotion, please report the work to us as described above. For more information, you can read our TOS FAQ on Commercial Promotion.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

[syndicated profile] otw_news_feed

Posted by choux

In May and June, we made some security additions for user accounts by adding email notifications when an account’s username or password is changed. We also made some improvements around tag sets and challenge signups. As one more security change, we also permanently disabled image embedding in guest comments.

A special thank you to our new contributors Ashley Tan, dismayonnaise, Grayson von Goetz, Jen Mann, kitbur, and ryelle!

Credits

  • Coders: Ashley Tan, Bilka, Brian Austin, Ceithir, Connie Feng, dismayonnaise, EchoEkhi, Grayson von Goetz, Hamham6, Jen Mann, kitbur, marcus8448, ryelle, Sarken, Scott, slavalamp, weeklies
  • Code reviewers: Bilka, Brian Austin, Ceithir, james_, lydia-theda, redsummernight, slavalamp, Sarken, weeklies
  • Testers: Bilka, Brian Austin, choux, Deniz, Eskici, LilyP, Lute, lydia-theda, Maine, megidola, Runt, Sam Johnsson, Sarken, Scott, Tal, Teyris, therealmorticia, wichard

Details

0.9.409

On May 11, we deployed some improvements to tag sets and added an email notification whenever the username on your account is changed.

  • [AO3-5513] – Admins can now successfully create and rename media tags without running into 500 errors or caching issues.
  • [AO3-5714] – When a canonical fandom and a non-canonical character or relationship were added to the same tag set, the non-canonical tags were automatically listed under the fandom. However, this is just how the tags were displayed in the tag set. They weren’t really connected to the fandom, which meant they weren’t included in autocompletes and couldn’t be used in challenge sign-ups. We’ve stopped automatically listing the non-canonical tags under the fandom and will instead only do it if the tag set moderators set up an association (which will also make the non-canonical tags usable in sign-ups and help ensure they appear in the autocomplete).
  • [AO3-5919] – We updated the code for kudos emails to avoid using a method that wasn’t particularly efficient.
  • [AO3-6757] – When an admin hides a comment, any embedded images in the hidden comment will now be replaced with the image URLs.
  • [AO3-6844] – We fixed a whole bunch of display and page structure issues on pages that list the tags in a tag set.
  • [AO3-6977] – We’ve started spam checking edits to comments from new users and stopped spam checking any comments a work creator leaves on their own work.
  • [AO3-6981] – To improve account security, we now send you an email when you (or someone logged in to your account) change your username.
  • [AO3-6984] – Our dependency updater bumped our version of net-imap to 0.5.7. It’s not something we use, but keeping dependencies up to date is good.
  • [AO3-6988] – We started caching the package installs involved in our automated tests, making each test run faster.
  • [AO3-6990] – We bumped our version of the rack gem to 2.2.14 to get the latest security fix.

0.9.410

On May 16, we added an email notification whenever the password of your account is changed. We also made a number of small improvements all around the site.

  • [AO3-5712] – Under certain circumstances, it was possible to sign up for a challenge using a character or relationship that wasn’t permitted by the challenge’s tag set. Now you’ll get an error if you try to do that.
  • [AO3-6267] – If a draft chapter was added to a work in your History, your History would lie to you and say an update to the work was available. Now it will only tell you an update is available if a new chapter has been published since you last accessed the work.
  • [AO3-6627] – Whenever a site admin tried to update the roles for a user who already had roles outside the admin’s purview, those existing roles would be removed. (For example, when a Tag Wrangling admin gave the tag wrangler role to a user who had the Open Doors archivist role, the user would lose their archivist role.) We’ve fixed it so any existing roles will stay in place.
  • [AO3-6994] – We fixed an issue that was causing our spam checker to run on comments from accounts with recently changed email addresses.
  • [AO3-6005] – We used feature tests somewhere we should’ve been using unit tests, so we changed them over.
  • [AO3-6975] – At some point the admin setting for how long to keep around unactivated accounts had become disconnected from the code it was meant to control. We fixed this so the setting once again affects the right piece of code.
  • [AO3-6970] – When the Policy & Abuse committee hides a work, you get an automatic email to notify you. To prepare for some future changes, we’ve updated the email text to allow for multiple works in the same email.
  • [AO3-6973] – Another account security enhancement: you’ll now get an email when you (or someone accessing your account) change or reset your password.

0.9.411

On May 24, we deployed an improvement to word counts for multichapter works on the Statistics page. We also took steps to fight abuse in guest comments by preventing them from ever displaying embedded images.

  • [AO3-3818] – On some specific browsers on certain devices, leaving comments or submitting support tickets would result in an error. We’ve now fixed that.
  • [AO3-4190] – Every time invitations were sent, the log on the site settings page updated to say the settings had been modified. We’ve fixed it so it will only say the settings have been updated when an admin updates them.
  • [AO3-7000] – One of the external links in the Creating a Skin help pop-up pointed to a site that had been taken over by a crypto magazine, so we’ve replaced it with a new resource for learning about CSS.
  • [AO3-6995] – In a previous release, we tried to drop an unused database column. Unfortunately, we had to put it back when it turned out Rails was still looking for the column due to caching. We’ve now made a code change that will let us drop the column for real after a future release.
  • [AO3-5270] – The yearly word counts on your Statistics page will now only count words written in chapters posted in that year. That means if you add a chapter to a WIP you started last year, the words you wrote last year will still count toward 2024’s total instead of being added to 2025’s total.
  • [AO3-5347] – The notification you get when someone cites your work as a related work has now been prepared for translation.
  • [AO3-6092] – A while ago, we unintentionally fixed a bug where the chapter title didn’t display in Entire Work mode if the work only had one posted chapter. Now we’ve added an automated test to make sure we don’t unintentionally break it again.
  • [AO3-6684] – The close button on the banner we use for sitewide announcements uses an ×, which typically makes sense if you’re looking at the page, but which gets read as “multiplication sign” if you’re using a screen reader. That was confusing, so we’ve made sure screen readers will now say “hide banner” instead.
  • [AO3-6967] – We’ve added a second save button to the top of tag edit pages to make things a little more convenient when the page is long and a wrangler is just changing something at the top of the form.
  • [AO3-6987] – Under certain circumstances, we strip embedded images from certain fields. We used to just show the image URL when we did that, but now we show all of the HTML.
  • [AO3-6991] – As a safety measure, guest comments with embedded images will always show the HTML instead of embedded images. (This includes existing guest comments.)

0.9.412

On June 5, we deployed a small release with some bug fixes.

  • [AO3-6166] – If you knew the ID of an unrevealed work you could access a few subpages of the work, such as the collections page, and find out the title of the work that way. Since that’s meant to be unrevealed, we’ve changed these pages so you can no longer access them if the work is unrevealed.
  • [AO3-6937] – We changed the browser page title on inbox pages to a format that matches other user pages: “username – Inbox | Archive of Our Own.”
  • [AO3-6953] – We made sure you’ll get an error message if you attempt to clear your History and it fails.
  • [AO3-6993] – The Edit Multiple Works page will no longer display a bunch of unusable options when you don’t have any works. Instead, it will simply tell you you don’t have any works.
  • [AO3-6550] – When displaying work titles, we used to call a function on them that had already been called. We’ve stopped doing that since it’s redundant.
  • [AO3-6948] – We added some code to enable us to monitor the performance of the job that sends invitations to people in the invitation queue.

0.9.413

Our June 16 deploy added the ability to embed media from audio.com in works.

  • [AO3-6515] – We fixed an error 500 that occured when a work with end notes was marked as published, but only had draft chapters.
  • [AO3-6912] – We changed the browser page title for unrevealed works to include the site name at the end.
  • [AO3-6437] – We removed some unused database tables.
  • [AO3-6996] – We finally dropped that unused database column and removed the code we added to make that go smoothly.
  • [AO3-6235] – Admins from the Policy & Abuse committee can now turn invitation requests on and off from the site settings page.
  • [AO3-6588] – Admins from the Open Doors and Support committees can now give users the role that disables password reset emails for their account.
  • [AO3-7003] – You can now add embeds from audio.com to your works.

OTW Signal, June 2025

24 Jun 2025 09:35
[syndicated profile] otw_news_feed

Posted by callmeri

Every month in OTW Signal, we take a look at stories that connect to the OTW’s mission and projects, including issues related to legal matters, technology, academia, fannish history and preservation issues of fandom, fan culture, and transformative works.

In the News

The Conversation’s article “The lore of ‘lore'” explores how fandom fueled the reinvention of a 1,000-year-old word:

Now essential online slang, [“lore”] can be traced back to Old English, where it referred primarily to learning, as in the act of teaching or being taught. Over time, lore came to be associated with more informal knowledge, passed on through word of mouth … [but then it] largely slipped out of common usage … So, how did “lore” come to hold such contemporary relevance?

“Lore” still carries shades of its original meaning, but just as fans expand and transform canon, modern usage reimagines it. Oxford University Press—which shortlisted “lore” for their 2024 word of the year—explains:

In recent years, people have been using “lore” in different ways and in new contexts. For example, they might now talk about the lore surrounding a particular celebrity, or a character in a book or film, or even refer to their own personal history as their lore. Online cultures and social media have seen the emergence of new kinds of celebrities and highly-engaged fandoms, and the word has been applied much more widely.

From its popularity in K-pop to the semi-eponymous Fanlore, the rise of “lore” is a great example of how fans build cultural meaning through shared language and creative reinterpretation.


The Geekiary’s article on fandom holidays speaks on how fans mark time within their communities. Be it May the Fourth (Star Wars Day) or Destiel’s confession anniversary, fandom holidays are not an uncommon phenomenon. Some humorous, some profound, these unofficial yet widely beloved holidays are often tied to moments from canon (such as a character’s birthday or an in-universe event) and serve to foster community building.
These observances turn the ordinary calendar into a timeline of shared emotion and meaning. As an act of tradition, they become ritual anchors that give structure to the fan’s calendar, offering a sense of comfort and familiarity in an ever-changing world. The article notes how this act of building new traditions and creating opportunities for community bonding forges a sense of cultural memory for fans.

In her book Rogue Archives: Digital Cultural Memory and Media Fandom, Abigail De Kosnik describes how “Memory has gone rogue in the sense that it has come loose from its fixed place in the production cycle. It now may be found anywhere, or everywhere, in the chain of making”. Celebrating holidays online or by digitizing photographs/experiences allows these memories to be accessed later on, rather than be fixed to just a specific person or place. It lets our fandoms live outside of us as individuals.

Like lore, fandom holidays demonstrate how participation itself becomes a form of authorship—each contribution adding another thread to the tapestry.

OTW Tips

Fandom is global, and many amazing fanworks are written, drawn, or subtitled in languages other than one’s own. Whether you’re tagging fanfiction in your native language or collaborating with international fans, your efforts enrich fandom’s diversity and inclusivity.
The OTW is recruiting for Tag Wrangling Volunteers (Russian), Internal Complaint and Conflict Resolution Volunteers, and Support Volunteers (Chinese).
Consider volunteering for one of the OTW’s teams to support and celebrate global fan participation!


We want your suggestions for the next OTW Signal post! If you know of an essay, video, article, podcast, or news story you think we should know about, send us a link. We are looking for content in all languages! Submitting a link doesn’t guarantee that it will be included in an OTW post, and inclusion of a link doesn’t mean that it is endorsed by the OTW.

[syndicated profile] otw_news_feed

Posted by Caitlynne

Candidates Announcement

The Organization for Transformative Works is pleased to announce the following candidates for the 2025 Election (in alphabetical order by given name):

  • C. Ryan S.
  • Elizabeth W.
  • Harlan L.B.

Because we have 2 seats to be filled and 3 candidates, the 2025 election will be contested – that is, the members of the OTW will vote on which candidates fill the seats.

The Elections Committee is excited to introduce the candidates to all of the members of the OTW! Included in this post are links to short Bios and Platforms written by the candidates. This post also marks the beginning of our Q&A period, during which we invite the public to submit questions for the candidates. Additionally, we will be holding a series of live chats – dates and times for those are to be announced based on candidate availability. Information on the voting period and how to vote will also be posted shortly.

In the meantime, there is a timeline of Elections events available here for your reference. Read on to learn more about our candidates and how you can submit questions for them!

Platforms and Bios

We asked each candidate to provide us with a Bio that sums up their professional and fannish experience, as well as to write a Platform about their goals for their term on the Board by answering the following questions:

  • Why did you decide to run for election to the Board?
  • What skills and/or experience would you bring to the Board?
  • Choose one or two goals for the OTW that are important to you and that you would be interested in working on during your term. Why do you value these goals? How would you work with others to achieve them?
  • What is your experience with the OTW’s projects and how would you collaborate with the relevant committees to support and strengthen them? Try to include a range of projects, though feel free to emphasize particular ones you have experience with.
  • How would you balance your Board work with other roles in the OTW, or how do you plan to hand over your current roles to focus on Board work?

You can read both the candidates’ answers to these questions and their bios by following the links below.

Question & Answer (Q&A)

To better accommodate the time constraints of the election and the workload for candidates, we are asking voters to limit to one question per message. Additional questions in the same message will be discarded. Limit of three questions per person.

Anyone may submit questions via the Elections form. Please submit all questions by 11:59pm UTC on June 29 (what time is that where I live?). All candidates will answer each question submitted, subject to the following restrictions:

  • Questions must be a maximum of 50 words long.
  • Any submitted questions repeating what is already addressed on Platforms will be ignored. This is to allow candidates to dedicate more time to answering new questions.
  • Similar questions will be grouped together to avoid candidates giving repetitive answers. Elections volunteers will decide which questions are similar enough to group.
  • If you have a follow-up to a Platform question, please specifically mention it is a follow-up so Elections volunteers know not to treat it as a repeat.
  • One question per message. Additional questions in the same message will be discarded.
  • Maximum of three questions per person.

The posting date for answers will be chosen depending on the number of questions received. Posts will be spread out, arranged by topic, to make it easier for voters to read all the answers.

[syndicated profile] otw_news_feed

Posted by xeno

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we’re posting a weekly spotlight series about the TOS and our policies. We’ll also be reading comments and answering questions on this and our other spotlight posts.


In today’s post, we’ll discuss two categories of TOS violations that have a lot of overlap: plagiarism and copyright infringement.

Don’t go looking for things to report.

Please do not start searching for plagiarized or infringing works to report after reading this post. We know that plagiarism and copyright infringement can happen on AO3, as on any site. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

AO3 is for transformative fanworks

AO3 is an archive for fanfiction and other transformative fanworks. Transforming a work means that you are adding a new expression, different purpose, or alternate perspective to the source work. A transformative fanwork doesn’t copy the original source; instead, it uses the characters, setting, or other inspiration from an existing work to make a new, distinct creative work.

Transformative fanworks can be posted without requiring permission from the creator of the original work. When considering whether a work is transformative, we apply the same standards to fanworks as to professional works. This means that a fanwork based on another fanwork is allowed, just as much as a fanwork of a professionally published novel is. You are allowed to write a story or create fanart about someone else’s original character, or to use the same general ideas, tropes, or story structures as someone else. Two works can share the same premise, setting, and plot while still being transformative.

However, replacing names, swapping out words for their synonyms, or making other superficial changes to the source work is not considered transformative. A transformative work needs to have a large amount of creative expression that is original to you.

Plagiarism vs copyright infringement

Plagiarism occurs when a person reproduces large portions of someone else’s work or very heavily bases their work on another without adequately transforming it, and doesn’t credit the source. This lack of credit makes it appear as though the copied work is entirely their own original, unique idea and expression.

To avoid potential issues of plagiarism, you can cite your source by linking back to the original, for example by using AO3’s Inspired By feature. However, just because you provided credit doesn’t mean you’re automatically okay: your work may still be in violation of our other policies, such as copyright infringement.

Copyright infringement occurs when a work reproduces large portions of a different work, whether verbatim or with very little alteration (i.e. not in a transformative manner), without the authorization of the copyright owner. Even if you credit the source, reproducing too much of someone else’s content is still a violation of their copyright unless you have the copyright owner’s explicit permission.

Permission is not required for short quotations. Use a limited amount that’s reasonable for your purpose, such as:

  • 2-3 lines of lyrics per song
  • 2-3 lines of text per short chapter of a novel
  • 10 minutes of screentime per TV episode or movie

If you want to include longer excerpts, you will need the copyright owner’s permission. This applies regardless of whether the original work is a fanwork or published professionally.

Permission to reuse fanworks

Some fan creators will give other people permission to reproduce larger portions of their works than would ordinarily be permitted by copyright laws alone. They may do this by granting blanket permissions for particular uses (for example, “Anyone can translate or podfic my work, but I don’t allow reposts or nameswaps”) or by applying an official license (such as Creative Commons) to the work, which grants various permissions based on terms specific to the exact license.

If permission to reproduce the work is accompanied by specific terms, then you must follow those terms. For example, a creator may say, “You can translate my fic so long as you link back to the original.” In that case, if you post your translation without providing a link, you’re violating our policies. In order for your translation to be allowed, you would need to include the link as requested.

Common types of infringement

Unauthorized reposts

If you want to upload someone else’s work to AO3, you need to have their permission. It doesn’t matter how difficult it might be to contact them: even if the original creator posted their work a decade ago and then vanished from the internet, they still have copyright over their own work.

If you can’t get permission but you still want to save or share somebody else’s fanwork from another site, you can create an external bookmark that links to the work on that site, and add tags and notes to your bookmark so that other AO3 users can also find and enjoy the work.

Minor edits and adaptations

Making minor changes to a work doesn’t make the work original to you. If you’ve only changed the characters’ names and/or pronouns, or corrected the original author’s grammar or formatting, that isn’t transformative. You’ll need the creator’s permission to adapt their work like this and post it to AO3.

Too many quotes: transcripts and “character reaction” works

Transcripts (whether of TV episodes, movies, plays, video games, etc.) are protected by copyright. You cannot repost canon material on AO3, as this is typically a violation of our copyright infringement and/or non-fanwork policies.

If you’re creating a fanwork where the characters are reacting to another piece of media (such as by reading or watching the book, show, or movie that they were originally from), then that is allowed if and only if you don’t include too many quotes from the original source. Even if the lines of the original book or script are broken up by the characters’ reactions, you still can’t reproduce more than a few lines of the original text. If you’d like to post a work in which characters read or watch another work, then we suggest heavily reducing the number and length of your quotes, and/or briefly summarizing the events they’re reacting to instead of quoting directly from the original work.

Songfics with lyrics

Song lyrics are protected by copyright, which means you can’t reproduce large portions of lyrics without permission. This includes both songfics where the lyrics are interspersed throughout the story text and fics with characters singing songs as part of their dialogue. If the part of the song you want to highlight is more than a few lines, we suggest instead linking to a licensed source, such as the artist’s official YouTube channel.

Embedded artwork

Copyright doesn’t just apply to written text, but to all types of creative work regardless of the medium. In order to embed or upload someone else’s images, audio, or videos onto your AO3 account, you must have the original creator’s permission and credit them appropriately.

If you don’t have permission, or don’t know how to credit the original creator, then we suggest instead using HTML or AO3’s Inspired By feature to link directly to the creator’s own original post.

Unauthorized podfics & translations

If you want to podfic or translate someone else’s work, you need their permission to do so. According to United States law, audio recordings and translations are considered derivative, not transformative. AO3 welcomes fan-podficcers and fan-translators. However, your content must comply with U.S. law for us to be able to host it, which means that you must have the permission of the copyright owner in order to post your podfic or translation on AO3.

Infringing on orphaned works

Orphaning a work does not mean the original creator is giving up their copyright, even if their username is no longer displayed on the work. The only thing the original creator did when orphaning their work was agree to transfer that specific copy of their work to AO3’s orphan_account.

Just like with any other work, if you wish to podfic or translate an orphaned work, you will need permission from the original creator. This can come in the form of an author’s note on the work or an additional tag such as Podfic Welcome. If the work contains no such statement, and you don’t know or can’t find the original creator to ask for permission, then you may not podfic or translate the work.

If you plan on orphaning your works and you want to ensure that other users can continue to adapt or translate them, consider adding a permission statement to each of your works before orphaning them.

Posting public domain works

While public domain works are no longer protected by copyright, reposting someone else’s work is not transformative. AO3 is an archive for fanworks and for original works created in a fannish context. Therefore, you cannot upload other people’s public domain works to AO3.

However, as public domain works are not protected by copyright, some types of derivative works (such as your own translation) may be posted on AO3.

I’ve seen others post plagiarized or infringing works. Why can’t I?

As our TOS FAQ explains, we don’t review content until it’s reported to us. You may have seen somebody else posting an unauthorized translation or public domain work on AO3, but that doesn’t mean that it’s allowed. All it means is that nobody has reported that work to us yet, or that we haven’t finished processing the report.

What will happen if I get reported for plagiarism or copyright infringement?

First, we’ll review the reported work and any provided sources to confirm whether or not your work contains plagiarized or infringing material. If we determine that your work is in violation, we’ll send you an email telling you to remove the violating material.

If your work can be edited to fix the issue, you’ll be asked to edit the work. Your work may be hidden from other users until you do. If you choose not to edit the work, or if your work cannot be edited into compliance with the TOS, it will be deleted.

PAC will only ever contact you by email, and only after we’ve determined that your work violates our Terms of Service. We will never comment on your work or contact you through social media. Please make sure to keep your account’s email address up to date and check it regularly (including your spam folder), or else you may miss our warning email.

If you repeatedly post works that violate our copyright and/or plagiarism policies, you may be temporarily suspended. Continuing to violate the TOS will result in you being permanently banned from AO3. You can learn more about warnings and suspensions in our TOS FAQ.

What should I do if I encounter a work that contains plagiarized or infringing material?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can report the work to us.

How do I report a work for plagiarism or copyright infringement?

Although we ask that you do not deliberately seek out violating works to report, if you encounter one while browsing, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3. The copyright owner or their authorized legal representative can also file a DMCA claim, as explained on our DMCA Policy page.

In order for us to uphold a complaint, we need you to provide us with specific information about exactly what was copied and from where. Without these details, we may not be able to action your report.

If the work in question is no longer available online, but you have a copy of the work (such as a PDF), please say so. We may ask you to provide that copy to help us in our investigation.

Please be specific in your report. If you send us a link to an 80,000-word fic and say only “This work rips off mine!” without providing any details (such as a link to your own work), that’s not enough information for us to act on. We will need to email you back asking for more information, and if you don’t provide us with that information, we won’t be able to investigate. If we can’t verify the infringement for ourselves, then we won’t take any action.

Please don’t report more than one user at a time or submit multiple reports about the same user. When reporting multiple works by the same user, please submit only one report with links to each work you’re reporting (correctly matched up with the original source), so that all information about that user is in the same place.

If you give us a link to one work and say “All of their other works look like plagiarism too!” without giving us details about those works or their sources, that isn’t enough information for us to act on those other works. If you give us a jumbled or incomplete list of links, or if you report each work by the same user separately, this makes our volunteers’ work much harder.

For example, a report might look like this:

Link to the page you are reporting: https://archiveofourown.org/works/00000000

Brief summary of Terms of Service violation: Plagiarism

Description of the content you are reporting:
This work by Ernie is plagiarized from Bert’s work, “Fifty Shades of Oatmeal”: https://archiveofourown.org/works/23456789

The entire thing is copied, Ernie just swapped out Elmo’s name for the Count’s and changed some of the colors.

If you are reporting additional works, please include all relevant links and other information in your report description:

Brief summary of Terms of Service violation: Plagiarism and Copyright Infringement

Description of the content you are reporting:
This work by Ernie is plagiarized from Bert’s work, “Fifty Shades of Oatmeal”: https://archiveofourown.org/works/23456789

The entire thing is copied, Ernie just swapped out Elmo’s name for the Count’s and changed some of the colors.

Another of Ernie’s works plagiarizes from Big Bird’s “If You Give a Monster a Cookie”:

Ernie’s work (plagiarism): https://archiveofourown.org/works/34567890
Big Bird took down their fic when they published it as an original story. Here’s a link to the published version: https://www.monstercookiebooks.com/books/9876543210/if-you-give-a-monster-a-cookie

I also have a downloaded copy of the original fic I can give you if you need it.

The plagiarized section is in Ernie’s chapter 2, where it starts at “Every time that Cookie Monster goes to the store, he can’t resist going and picking up more chocolate chip cookies.”

This is plagiarizing chapter 3 of Big Bird’s work, which starts, “Whenever Cookie Monster went to the store, he couldn’t resist buying more chocolate chip cookies.”

The entire rest of the fic is like that, with only minor edits to each sentence. It’s over ten thousand words long!

Finally, this other work contains the full lyrics of “I Love Trash” as sung by Oscar the Grouch: https://archiveofourown.org/works/45678901

Here’s a link to the song on YouTube: https://www.youtube.com/watch?v=zJekxVILnhw

You can add more details if you like, but this example provides the basic information we need:

  • Who posted the violating work(s): Tell us their username or if the work is anonymous or orphaned.
  • Where we can find the violating work(s): Enter one URL in the “Link to the page you are reporting” field, and (if applicable) include links to any other violating works in the description of your report.
  • Where we can find the original source material: Include a link to each original source and tell us what parts of the source were copied, for example by including chapter numbers or quotes from the relevant scenes.
  • What violates the TOS: Explain why you think each work you’re reporting is infringing and match each reported work to its original source. A set of links and a brief description of each work is fine; you don’t need to be very detailed or quote an entire page.

You’ll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same incident. While PAC investigates every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about plagiarism and copyright infringement?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you’ve found a plagiarized or infringing work, or if you want to know whether a particular work qualifies as plagiarism and/or copyright infringement, please report the work to us as described above. For more information, you can read our TOS FAQ on Copyright Infringement and Plagiarism.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

ETA: Edited to improve wording

[syndicated profile] otw_news_feed

Posted by an

Would you like to wrangle AO3 tags? Can you read and translate from Indonesian to English? Can you read and translate from Russian to English? Are you interested in actively contributing to the creation and maintenance of a safer volunteering environment within the OTW? Would you like to help your fellow fans use AO3? Are you fluent in Chinese? If you answered “yes” to any of these, you’re in luck: the OTW is recruiting!

We’re excited to announce the opening of applications for:

  • Tag Wrangling Volunteer – closing 25 June 2025 at 23:59 UTC [or after 130 applications]
  • Tag Wrangling (Indonesian) Volunteer – closing 25 June 2025 at 23:59 UTC [or after 30 applications]
  • Tag Wrangling (Russian) Volunteer – closing 25 June 2025 at 23:59 UTC [or after 30 applications]
  • Internal Complaint and Conflict Resolution Volunteer – closing 25 June 2025 at 23:59 UTC
  • Support Volunteer – closing 25 June 2025 at 23:59 UTC [or after 30 applications]
  • Support (Chinese) Volunteer – closing 25 June 2025 at 23:59 UTC [or after 30 applications]

We have included more information on each role below. Open roles and applications will always be available at the volunteering page. If you don’t see a role that fits with your skills and interests now, keep an eye on the listings. We plan to put up new applications every few weeks, and we will also publicize new roles as they become available.

All applications generate a confirmation page and an auto-reply to your e-mail address. We encourage you to read the confirmation page and to whitelist our email address in your e-mail client. If you do not receive the auto-reply within 24 hours, please check your spam filters and then contact us.

If you have questions regarding volunteering for the OTW, check out our Volunteering FAQ.

Tag Wrangling Volunteer

The Tag Wranglers are responsible for helping to connect and sort the tags on AO3! Wranglers follow internal guidelines to choose the tags that appear in the filters and auto-complete, which link related works together. This makes it easier to browse and search on the archive.

If you’re an experienced AO3 user who likes organizing, working in teams, or having excuses to fact-check your favorite fandoms, you might enjoy tag wrangling! To join us, click through to the job description and fill in our application form. There will also be a short questionnaire that will help us assess whether you have the skills and attributes that will lead to your success in this role.

Please note: you must be 18+ in order to apply for this role. For this role, we’re currently looking for wranglers for specific fandoms only, which will change each recruitment round. Please see the application for which fandoms are in need.

Wranglers need to be fluent in English but we welcome applicants who are also fluent in other languages, especially Čeština (Czech), Español (Spanish), isiZulu (Zulu), Italiano (Italian), Polski (Polish), Português brasileiro (Brazilian Portuguese), Suomi (Finnish), Tiếng Việt (Vietnamese), Türkçe (Turkish), Українська (Ukrainian), ไทย (Thai), беларуская (Belarusian), 한국어 (Korean) and 中文 (Chinese – we welcome all dialects) — but help with other languages would be much appreciated!

Applications are due 25 June 2025 [or after 130 applications]

Apply for Tag Wrangling Volunteer at the volunteering page! If you have further questions, please contact us.

Tag Wrangling (Indonesian) Volunteer

The Tag Wranglers are responsible for helping to connect and sort the tags on AO3! Wranglers follow internal guidelines to choose the tags that appear in the filters and auto-complete, which link related works together. This makes it easier to browse and search on the archive.

If you’re an experienced AO3 user who likes organizing, working in teams, or having excuses to fact-check your favorite fandoms, you might enjoy tag wrangling! To join us, click through to the job description and fill in our application form. There will also be a short questionnaire that will help us assess whether you have the skills and attributes that will lead to your success in this role.

Please note: you must be 18+ in order to apply for this role. For this role we’re currently looking for applicants who are fluent in both English and Indonesian. We welcome all Indonesian dialects. The work will involve both regular Tag Wrangling work and translating tags from Indonesian into English.

Applications are due 25 June 2025 [or after 30 applications]

Apply for Tag Wrangling (Indonesian) Volunteer at the volunteering page! If you have further questions, please contact us.

Tag Wrangling (Russian) Volunteer

The Tag Wranglers are responsible for helping to connect and sort the tags on AO3! Wranglers follow internal guidelines to choose the tags that appear in the filters and auto-complete, which link related works together. This makes it easier to browse and search on the archive.

If you’re an experienced AO3 user who likes organizing, working in teams, or having excuses to fact-check your favorite fandoms, you might enjoy tag wrangling! To join us, click through to the job description and fill in our application form. There will also be a short questionnaire that will help us assess whether you have the skills and attributes that will lead to your success in this role.

Please note: you must be 18+ in order to apply for this role. For this role we’re currently looking for applicants who are fluent in both English and Russian. We welcome all Russian dialects. The work will involve both regular Tag Wrangling work and translating tags from Russian into English.

Applications are due 25 June 2025 [or after 30 applications]

Apply for Tag Wrangling (Russian) Volunteer at the volunteering page! If you have further questions, please contact us.

Internal Complaint and Conflict Resolution Volunteer

Are you passionate about fostering a safer and more supportive volunteering environment within the OTW?

As an Internal Complaint and Conflict Resolution (“ICCR”) volunteer, you will play a key role in maintaining fair and respectful interactions across the Organization. Your work will include reviewing, investigating, and adjudicating complaints, and mediating conflicts. Our team is also in the process of refining the OTW’s policies to create a more effective and inclusive volunteer experience. Our goal is to serve as an objective, neutral party for personnel-related issues to help resolve situations with compassion and equity.

Please note that due to the nature of the work, current OTW volunteers who apply for the role will have to resign from all other roles within the OTW to serve on this subcommittee.

Applications are due 25 June 2025

Apply for Internal Complaint and Conflict Resolution Volunteer at the volunteering page! If you have further questions, please contact us.

Support Volunteer

The Support team is responsible for handling the feedback and requests for assistance we receive from users of the Archive of Our Own. We answer users’ questions, help to resolve problems they’re experiencing, and pass on information to and from coders, testers, tag wranglers and other teams involved with AO3. If you enjoy helping others to learn how to use AO3 and figuring out solutions to problems, you might enjoy being a Support volunteer!

Applications are due 25 June 2025 [or after 40 applications]

Apply for Support Volunteer at the volunteering page! If you have further questions, please contact us.

Support Volunteer (Chinese)

The Support team is responsible for handling the feedback and requests for assistance we receive from users of the Archive of Our Own. We answer users’ questions, help to resolve problems they’re experiencing, and pass on information to and from coders, testers, tag wranglers and other teams involved with AO3.

We’re currently recruiting for applicants who are fluent in both English and Chinese (We welcome all Chinese dialects!). If you are a fluent Chinese speaker who enjoys helping others to learn how to use AO3 and figuring out solutions to problems, you might enjoy being a Support volunteer!

Applications are due 25 June 2025 [or after 40 applications]

Apply for Support Volunteer (Chinese) at the volunteering page! If you have further questions, please contact us.

March 2025

S M T W T F S
      1
2345678
9101112 13 1415
16171819202122
23242526272829
3031     

Style Credit

Page generated 30 Jun 2025 14:55
Powered by Dreamwidth Studios