Archive of Our Own ^beta

March brought a handful of noteworthy changes to AO3 in addition to the usual assortment of bug fixes and enhancements: we increased the maximum tag length from 100 to 150 characters, expanded the wrangling status options in tag search, and added the ability to have your invitation resent if it didn't arrive. Then we wrapped up the month with some changes to help combat an increase in spam, including spam checks on new users' comments and a rate limit on comments from all logged-in users. Thank you and welcome to first-time contributor Metallicity!

Credits

• Coders: Bilka, Brian Austin, EchoEkhi, Indes, james_, lou, lydia-theda, Metallicity, Sarken, slavalamp, warlockmel, weeklies
• Code reviewers: Bilka, Brian Austin, james_, redsummernight, Sarken, slavalamp
• Testers: Bilka, Brian Austin, C. Ryan Smith, calamario, choux, Claire P. Baker, Deniz, Dre, Lute, lydia-theda, Rhine, Runt, Sam Johnsson, Sanity, Sarken, spacegandalf, Tal, Teyris, therealmorticia, Vio, wichard

Details

0.9.399

On March 7, we increased the maximum length of tags from 100 to 150 characters and made it possible to resend unused invitations, among some other smaller fixes.

• [AO3-3945] - Tag landing pages now list subtags in alphabetical order. (They used to be ordered by the date they were subtagged.)
• [AO3-6712] - In January 2024, we tried to make it so checking the status of your invitation would give you the option of having it resent to you, assuming you hadn't used it yet and it was sent more than 24 hours ago. Unfortunately, we ran into a performance issue and had to remove the feature. We've fixed the performance problem and now you can resend your invitations for real!
• [AO3-6737] - On the bookmark pages for tags and collections, the section containing the bookmarker's notes and other information was too narrow. We made it fill the available space.
• [AO3-6748] - When using the Low Vision Default skin, the stats in the work meta would be very long and cause horizontal scrolling on narrow screens. We've changed the stats to wrap onto the next line instead.
• [AO3-6791] - Admins used to get a 500 error when trying to access the pseud edit page for a user that didn't exist. Nonexistent pages should give 404 errors, not 500 errors (which occur when there's a bug or other problem), so we fixed the bug and started giving the right error.
• [AO3-6836] - To make testing and translation easier, we made a preview of the email users receive when one of their works has been deleted by an admin.
• [AO3-6867] - Tags can now be 150 characters long instead of 100. That's 50% more tag!
• [AO3-6915] - Our dependency updater bumped our version of nokogiri from 1.18.2 to 1.18.3.

0.9.400

On March 17, we deployed a number of small fixes and improvements for admins. Additionally, we expanded the tag search with a few more wrangling status options.

• [AO3-6544] - To improve our spam checker's accuracy, we've started telling it whether the data we're sending it is from a user or a guest, and what sort of data it is (e.g., a support request or a comment on a news post).
• [AO3-6934] - We updated one of our dependencies to incorporate a security fix.
• [AO3-931] - When someone used an invitation and then later deleted their account, the invitation would have a confusingly empty "Redeemed by" field. Now it correctly says that a deleted user redeemed the invitation.
• [AO3-5498] - When an admin views an invitation, the "Redeemed by" field now conveniently links to the redeemer's account administration page.
• [AO3-6129] - We've added a very low rate limit to the login page for admins for a little extra security. (We haven't had any issues, but it's good to be prepared just in case.)
• [AO3-6313] - The FAQ pages used to tell an admin when the FAQ category was last updated. A reasonable person would think that meant when questions in that category were updated, but it actually only tracked when something like the category's name or position changed. Since this was pretty confusing, we've stopped including that information.
• [AO3-6775] - We now have a handy preview for the email a user receives when they (or their co-creator) delete a work.
• [AO3-6875] - We added three new options to tag search, so now you can filter for tags that are (or are not) synonyms of another tag.
• [AO3-6922] - We updated the Policy Questions & Abuse Reports page to better align with the November 2024 Terms of Service update.
• [AO3-6923] - We updated our DMCA Policy to include an extra link to the Terms of Service FAQ.
• [AO3-6204] - Sometimes, users orphan works with their pseuds attached and later wish they hadn't. We've made it easier for certain admins to remove the identifying pseuds.
• [AO3-6943] - We fixed some automated tests that were failing half the time, which was just plain annoying.

0.9.401

On March 20, we finished off the last part of the Rails 7 upgrade by deploying a single change.

• [AO3-6687] - After we changed cookies to a more modern format in November, we now removed the support for the old format.

0.9.402

On March 24, we implemented comment rate limits for logged-in AO3 users to address an increase in spam comments.

• [AO3-6926] - We changed our rate limiting code to make it possible to specify rate limits per user.

0.9.403

On March 28, we deployed spam checking for comments posted by newly registered users to further combat the spam comments.

• [AO3-6439] - We changed how the code accesses the currently logged-in user to make our automatic tests behave more consistently.
• [AO3-6946] - In some very rare scenarios, the Manage Items page for a collection could show a completely unrelated work instead of the bookmark that was really part of the collection. We've made it always show the right item.
• [AO3-6951] - We bumped our version of reviewdog/action-rubocop from 2.21.0 to 2.21.2.
• [AO3-6933] - We added spam checking for comments from new users on works and admin posts.

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with orphan_account, who has been part of the OTW for 16 years—ever since the beginning! Originally a member of the Accessibility, Design, and Technology committee, they went on to serve with the Policy & Abuse committee for over a decade, before joining the Support committee in 2021.

How does what you do as a volunteer fit into what the OTW does?

Sometimes, writers and artists on AO3 don't want to be associated with one of their fanworks or their fannish identity anymore. If they don't want to delete their works, then they can turn them over to me instead. They can decide to either remove their name from the work entirely or leave behind a pseud identifying them as the original creator. Either way, after the creator confirms the transfer, the work is moved over to my own account so that it won't be connected to their account anymore. I've sworn to never edit a single work under any circumstances, so once a work is in my care, it's preserved permanently.

The exception to this is if the work is in violation of the Terms of Service. I'm not responsible for checking that! If a work with a TOS violation makes its way into my hands and somebody reports it to the Policy & Abuse committee, then PAC volunteers will edit the tags, take down the work, or do whatever else needs to be done to make it compliant.

What is a typical week like for you as a volunteer?

Busy, busy, busy! I get requests at all times of the day, although since AO3 is usually busiest between 14:00 to 06:00 UTC, so am I.

When somebody makes an orphaning request, first I'll ask them if they're sure. Then I'll ask them if they're really, REALLY sure, because while I can take over works, I'm not able to give them back—part of my role is forgetting who gave me the work in the first place, after all.

If they agree, then first I’ll edit the bylines on the work. If the original creator doesn't want their name associated with the work at all, then I'll just stick it under my main pseud. If they still want to be credited, I'll make a new pseud that's the same as their name, and place the work on my account under that pseud instead. (For example, here's a work that is ascribed to my good friend, testy.)

Once that's done, I'll take care of the creator's old comments by going through and editing the bylines so that the comments are attributed to me instead. This means that the creator won't be bothered by any comment notification emails. I don't touch the work's comment settings, so if the creator left comment moderation on when they gave me the work, then any new comments will remain unreviewed forever.

I can't edit what is in my works at all, so if somebody decides to leave their contact information in the notes or summary, then there's nothing I can do about it. I do warn people about this ahead of time, however! If you've given me one of your works in the past but you forgot to remove personally identifying information from it, you can ask my fellow volunteers on the Support committee to redact it from the work.

What made you decide to volunteer?

I was just a baby fan back when the OTW was first founded, but I immediately knew how I wanted to help out. Sometimes people just want to be able to move on from a work they made, but I would always feel disappointed when that meant they decided to delete it. After all, our mission as an archive is to preserve fanworks, and I wanted to provide a way for other fans to safely leave their works behind to be preserved on AO3. I feel so fortunate that the OTW has provided a lot of support and assistance over the years to help me preserve over 750,000 fanworks that otherwise might have been deleted by their creators.

Fun fact: I was one of the first ten people to sign up for an AO3 account—my account's user ID is 9! Sadly, most of the others have already deleted their accounts, though :’(

What has been your biggest challenge doing work for the OTW?

AO3 has grown to be a lot larger than anyone dared dream way back in the beginning. At the time, we all wanted to build an archive that would last, but we never expected way back then that it would get this big. It's like winning the lottery! Which is to say, it is AMAZING we've all come so far, but along the way there have been some unexpected pitfalls we've had to work around. These days, I have so many works that it can take me a couple of minutes to list them all out when somebody asks!

Probably the biggest challenge has been the sheer number of pseuds I've collected over the years. Because of this, you're not able to see my profile page directly—if you try, it will give you a 404 error, because I have so many pseuds. (But I'm told our technical volunteers are working on this!) Instead, if you'd like to browse the many fanworks that creators have passed into my hands, you can use a work search on my username.

What fannish things do you like to do?

I love reading, viewing, and listening to fanworks of all sorts! No matter how many fanworks I've seen or heard, I always have room for more. A couple of times, people have mistaken me for the creator of the works in my care, but I've never felt the need to make a fanwork myself. At heart, I'm a curator, and I'm happy to keep your works safe.

Happy April Fools! This post was written from the perspective of AO3's orphan account, which is a real account but not a real person. Read our Orphaning FAQ to learn more about the orphan_account, or you can check out previous Five Things posts by our actual volunteers.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan-run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

In February, we upgraded Ruby and Rails to their next major versions. In between those large upgrades, we made a variety of small bug and performance fixes all around AO3.

Special thanks and welcome to first-time contributors CJ Gorey, Connie Feng, Kayla Camacho, lou, marcus8448, and unsafe_deref!

Credits

• Coders: Amy Lee, Bilka, Brandon W, Brian Austin, calm, Ceithir, Cesium-Ice, CJ Gorey, Connie Feng, David Bilsky/Ironskink, EchoEkhi, Indes, Jake Faulkner, Kayla Camacho, lou, marcus8448, Potpotkettle, redsummernight, sarken, Scott, slavalamp, Stephen Lewis, unsafe_deref, weeklies
• Code reviewers: Bilka, Brian Austin, james_, redsummernight, sarken, slavalamp
• Testers: alien, Bilka, Brian Austin, C. Ryan Smith, calamario, Claire P. Baker, Deniz, Dre, Fishy, LilyP, Lute, megidola, Rhine, runt, Sanity, sarken, Tal, Teyris, therealmorticia, wichard

Details

0.9.394

On February 7, we deployed a release with some small improvements while the Systems team focused on the Ruby 3.2 upgrade.

• [AO3-5792] - The page that lists a tag set's tags had some unreadable text and oversized buttons in several skins due to some incorrect HTML classes. We've fixed the classes and therefore the display issues.
• [AO3-6518] - When an abuse report was submitted, the spam checker would run if the capitalization of the email listed in the report didn't exactly match the email listed on the user's account. Now, it doesn't.
• [AO3-6777] - It was possible to create blank and invisible tags. Now it's no longer possible.
• [AO3-6814] - The email sent to the creator when an Open Doors archivist adds their work to a collection can now be translated.
• [AO3-6820] - Sometimes when creating a bookmark, the information about who is creating the bookmark can get lost. This used to result in an ugly 500 error, but now it results in a nice error message that tells you what's wrong.
• [AO3-6859] - While we were limiting access to tag wrangling admin features, we accidentally restricted admins without certain roles from accessing tag landing pages. We've now let them back on those pages.
• [AO3-6872] - Open Doors archivists can now add bookmarks to a collection they control without running into an error.
• [AO3-6585] - We optimized the piece of code that displays work information in certain emails.
• [AO3-6870] - We updated the notice shown on proxy sites to include Russian and Ukrainian translations.
• [AO3-6766] - You can now use the color-scheme property in site and work skins.
• [AO3-6863] - The emails you get when someone adds you as or invites you to be a co-creator had confusing subject lines. We've made them clearer.

0.9.395

On February 11, we finished the Ruby 3.2 upgrade.

• [AO3-6884] - After the Systems team installed Ruby 3.2 (alongside Ruby 3.1) on our servers, we updated AO3 to use the new version instead of the old one.

0.9.396

On February 14, we deployed some performance and security fixes.

• [AO3-6880] - The gem we use for pagination on the site is no longer maintained, so we're trying a new gem on certain pages to help us decide if it's the one we'd like to switch to.
• [AO3-6901] - We changed an asynchronous process in an attempt to be nicer to the database server.
• [AO3-6905], [AO3-6908] - We upgraded net-imap and rack to address some potential security vulnerabilities found by our dependency checker.

0.9.397

On February 17, we upgraded to Rails 7.1.

• [AO3-6893] - We upgraded our gems and configuration files to Rails 7.1!
• [AO3-6904] - We added some logins to our default development environment so that coders can easily use those accounts for testing.
• [AO3-6909] - We updated the version of one of our automated code checks.

0.9.398

In the deploy on February 21, we made some small changes, fixed a few confusing 500 errors so they'll instead give nice error messages, and added a treat for the Tag Wrangling team.

• [AO3-2898] - We fixed the character count below the editing window so that it updates when you use the Rich Text editor.
• [AO3-3810] - We made it possible for admins to edit skins with the word "Archive" in the title.
• [AO3-4735] - Searching for a work title with a hyphen would result in a 500 error. We made it ignore the hyphen instead.
• [AO3-4820] - When users would try to create skins with the word "Archive" in the title, they'd get a 500 error page or even a blank screen. Now they'll get a nice error message telling them the word is reserved for official skins.
• [AO3-6004] - When an admin would hide a bookmark from public view, it would also be hidden from admins. That made it difficult to unhide. We changed it so that admins can now see hidden bookmarks.
• [AO3-6450] - Tags on unrevealed works used to show up in the wrangling bins, which made tag wranglers' jobs more difficult. Now those tags don't show up in the wrangling bins until the work is revealed.
• [AO3-6769] - The browser page titles for unrevealed series were missing the "| Archive of Our Own" at the end, so we added it.
• [AO3-6790] - We fixed a 500 error when a user or an admin would try to edit a pseud that didn't exist.
• [AO3-6810] - When our Policy & Abuse team manually marks a spam work as hidden, the creator now gets sent the correct email.
• [AO3-6846] - To make testing easier, we added a preview for the automatic email that's sent out when a Policy & Abuse admin hides a work.
• [AO3-6847] - We also added a preview for the email you receive about your work in a collection when the maintainer sets the collection as anonymous or unrevealed.
• [AO3-6850] - We removed some unused code from assignments in gift exchanges. We were happy to discover that this sped up loading the assignment pages for large exchanges.
• [AO3-6856] - Admins can no longer edit AO3's default language to change its name or abbreviation, or to stop including it in the list of languages Support and Policy & Abuse handle tickets in.
• [AO3-6868] - We fixed a 500 error when admins edited a language and provided an invalid abbreviation or display name.
• [AO3-6888] - We made sure that the tags and stats above a work are nicely left aligned after line-breaks.
• [AO3-6902] - We updated the after_commit_everywhere gem for a new feature that made our code a little cleaner.
• [AO3-6903] - We removed some pesky extra spaces after the colons of labels in a few emails.

Over the past several months, the Archive of Our Own has been experiencing an increase in spam comments left by registered users. To help prevent these comments, which typically ask for contact information and offer art commissions or collaboration, we'll be introducing limits on commenting and other activities for logged-in users. We expect to have these limits in place within the next few days.

As a result of these limits, you may get error messages telling you to "Retry later," especially when leaving or editing multiple comments over a short period of time. Our aim is to slow down the spammers with minimal impact on legitimate commenters, so we'll be monitoring the situation and adjusting the rate limits as needed once the code is in place. (This also means we can't tell you exactly what the limits are. However, we recommend waiting at least 15 minutes before trying again.)

Once these limits are in place, we'll also be looking into other methods that we hope will reduce spam with even less disruption to legitimate users. We apologize for the inconvenience and appreciate your understanding as we work to find a balance that meets everyone's needs.

Update 21:45 UTC 24 March 2025: Rate limiting for logged-in comments is now in place.

Would you like to assist AO3 users by resolving complaints? Are you fluent in a language other than English and passionate about making OTW more accessible? Do you have experience copyediting or proofreading academic journals? Or do you have experience with research methods, problem solving or nonprofit governance? The Organization for Transformative Works is recruiting!

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

• PAC Volunteer - closing 26 March 2025 at 23:59 UTC
• Translation Volunteer - closing 26 March 2025 at 23:59 UTC
• TWC Copyeditor - closing 26 March 2025 at 23:59 UTC
• Strategic Planning Volunteer - closing 26 March 2025 at 23:59 UTC

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.

PAC Volunteer

The Policy & Abuse committee (PAC) is responsible for addressing questions and concerns about potential violations of the AO3 Terms of Service. We determine whether reports are about legitimate violations of the Terms of Service, and what to do about them if they are. PAC volunteers correspond directly with AO3 users and collaborate on projects both within PAC and with other OTW committees.

Our main goals as a committee are:

• to adhere to the AO3 Terms of Service
• to make our reasoning and processes as clear and transparent as possible
• to handle all user reports consistently, no matter which volunteer is doing the work
• to keep every case we work on completely confidential

We are seeking people who can:

• Commit to working on cases regularly
• Be patient with rephrasing explanations
• Ask for help when needed
• Collaborate both inside the team and with other committees
• Act in accordance with established rules, policies, and procedures
• Treat confidentiality and user privacy as a priority

You must be 18+ in order to apply for this role. While English proficiency is required, we welcome applicants who are fluent in other languages, especially Spanish (Español), Brazilian Portuguese (Português brasileiro), Russian (Русский), Chinese (中文), or Indonesian (Bahasa Indonesia).

Applications are due 26 March 2025

Translation Volunteer

If you enjoy working collaboratively, if you're fluent in a language other than English, if you’re passionate about the OTW and its projects, and want to help us reach more fans all around the world, working with Translation might be for you!

Translation volunteers help make the OTW and its projects accessible to a wider global audience. We work on translating content by the OTW and its projects from English to other languages, such as site pages, news posts, AO3 FAQs and AO3 Support emails. (However, we do not translate fanworks.)

We really need volunteers who speak Afrikaans, Arabic, Basque, Bengali, Bulgarian, Catalan, Estonian, Filipino, French, Galician, Hebrew, Hindi, Hungarian, Indonesian, Japanese, Korean, Latvian, Lithuanian, Macedonian, Malay, Marathi, Norwegian, Persian, Portuguese-PT, Romanian, Serbian, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian, and Welsh—but help with other languages would be much appreciated. If you're interested in starting a team for a language we don't have yet, you're very welcome to!

(Please note that our Chinese, Croatian, Czech, Danish, Dutch, Finnish, German, Greek, Italian, Polish, Portuguese-BR, Russian and Vietnamese teams are not accepting new members at this time. If you are fluent in one of these languages and interested in volunteering, please consider volunteering for another team within the organization instead.)

Applicants will be asked to translate and correct short text samples and will be invited to a chatroom interview as part of the selection process. More information about us can be found on the Translation committee page.

Applications are due 26 March 2025

TWC Copyeditor

Transformative Works and Cultures (TWC) is an international peer-reviewed Diamond Open Access online publication about fan-related topics that seeks to promote dialogue between the academic community and fan communities. Copyeditors professionally copyedit submissions for TWC according to Chicago Manual of Style (CMOS) 18, Merriam-Webster online, and the TWC style guide. Editorial standards are those of a university press.

The copyeditor's main responsibility will be to carefully copyedit word-processed manuscripts to correct errors of grammar, usage, style; normalize presentation of information; check the literature; and ensure consistency of usage of, e.g., presentation, capitalization, italic, and numbers.

Applicants are required to pass a brief copyediting test that will be drawn from live copy (a not yet published article that is currently in production). All returned tests will be assessed and the applicant provided with feedback.

You must be 18+ in order to apply for this role.

Applications are due 26 March 2025

Strategic Planning Volunteer

The Strategic Planning Committee is recruiting for new volunteers! We are a close-knit and collaborative committee of 6-9 people who are tasked with researching, developing, and supporting the implementation of the OTW's strategic plan, which is a written document that articulates the OTW's priorities and direction. The process to establish priorities involves many people across the organization and is an important part of aligning the organization around shared goals; monitoring implementation also provides accountability to the organization's mission and our user community. We are in the implementation monitoring phase of the 2023-2026 Strategic Plan and are looking for organized people well-versed in communication and project management, with experience in goal management and feedback response. Knowledge of data analysis and understanding how to complete research are helpful as well, as is experience using various project management tools, document collaboration software and text-based messaging platforms.

We typically review around 50 applications, induct 2-3 new volunteers and provide training on the committee's tools and processes. We welcome all perspectives and are actively interested in people with diverse views on fandom and the OTW! The Strategic Planning Committee is committed to diversity, equity, and inclusion, and will make reasonable accommodations for candidates who may require them.

You must be 18+ in order to apply for this role.

Applications are due 26 March 2025

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

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan-run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

At the start of the year, we upgraded our library for managing pseud and collection icons. To follow that large effort, we deployed some smaller fixes and improvements while we worked to address some performance issues due to increased traffic. We also did some preparations for the next big Ruby and Rails upgrades.

Special thanks and welcome to first-time contributors Indes, Jeslyn See, John Mathai, and Sekoia!

Credits

• Coders: Amy Lee, Bilka, Brian Austin, Cesium-Ice, Indes, Jake Faulkner, james_, Jeslyn See, John Mathai, lydia-theda, mystyrust, Scott, Sekoia, slavalamp
• Code reviewers: Bilka, Brian Austin, james_, redsummernight, Sarken, Scott
• Testers: Bilka, Brian Austin, Deniz, Indes, Keladry, Lute, lydia-theda, megidola, redsummernight, Rhine, Runt, Sanity, Sarken, Taki, Teyris, therealmorticia, Vio

Details

0.9.388

On January 14, we migrated to a new library for managing icon uploads.

• [AO3-5843] - The browser page title of the Invitation Requests page is now -- wait for it -- "Invitation Requests."
• [AO3-5578] - The library we were using to manage uploading pseud and collection icons, as well as skin preview images, was in maintenance mode and not getting improvements. Rails' built-in solution, Active Storage, got a lot of improvements with Rails 7, so we switched to it.
• [AO3-6873] - The Elasticsearch version we were using wasn't compatible with the newest Linux kernel when running in Docker for development, so we upgraded our development setup to a fixed version.

0.9.389

We deployed a fix for a performance issue on January 21.

• [AO3-6878] - By default, Active Storage tries to extract metadata from every uploaded image. We don't need or want that behavior, and it was causing major strain on the database because we'd just reuploaded every icon on the site as part of our migration from Paperclip, so we disabled it.

0.9.390

On January 26, we deployed a number of small fixes and improvements to take it easy while we recovered from the Active Storage changes.

• [AO3-5977] - Admins who can access unreviewed moderated comments on works could see the "Approve All Unreviewed Comments" button even though they absolutely do not have the ability to approve unreviewed comments. We've hidden that button.
• [AO3-6238] - The "Random Items" button didn't work on the collection's homepage. We've now made it work, like on all other collection pages.
• [AO3-6378] - The browser page title when looking at all series by a pseud didn't mention series at all. Now it does!
• [AO3-6874] - The browser page titles for the TOS pages and the TOS FAQ were missing the "| Archive of Our Own" at the end, so we added it.
• [AO3-6755] - We removed some unused stylesheets.
• [AO3-6871] - We updated one of our Rails dependencies to incorporate a small security fix.
• [AO3-5502] - We made the browser page title on the adult content warning page for chapters more informative.
• [AO3-6529] - It was possible to import a work from a URL on AO3, resulting in two copies of the work. Bookmarks are much better suited for saving other AO3 works, so we prevented importing works from AO3 and the error helpfully mentions bookmarking the work instead.
• [AO3-6587] - When our Policy & Abuse team edits a user's pseud or profile in response to a ticket, they have to enter the ticket ID to authorize the action and create a log of the changes. To make it easier to copy and paste the ID from the ticket tracker, the field now accepts a leading #.
• [AO3-6774] - To make testing easier, we added a preview for the email that is sent when an admin manually grants invitations to users.
• [AO3-6848] - We also added a preview for the email sent when you're assigned a request in a challenge.
• [AO3-6801] - We clarified the text of the error message banned and suspended users receive when they try to do something they're not allowed to do (e.g., posting a work).
• [AO3-6862] - We updated the example URLs in some of our help text to use example.com, which is a domain that exists specifically for that purpose.

0.9.391

With our deploy on February 3, we prepared to upgrade to Ruby 3.2 and addressed some performance issues.

• [AO3-6882] - To prepare for upgrading to Ruby 3.2, we made it possible to run the Archive with both Ruby 3.1 and Ruby 3.2.
• [AO3-6889], [AO3-6890] - We added some gems to try to work around some performance issues.
• [AO3-6892] - We did a schema dump to capture what the current data structure looks like before we upgrade to Rails 7.1.
• [AO3-6897] - In an attempt to address regular database load spikes, we adjusted the schedule of a regularly running task.

0.9.392

In an attempt to address some more performance issues, we deployed a second release on February 3.

• [AO3-6898] - We disabled some functionality in Active Storage that may cause some threading issues, but allowed us to cache icons to reduce traffic.

0.9.393

And then, on February 4, we undid the change we made on February 3.

• [AO3-6900] - Our previous change led to some 500 errors related to missing pseud icons, so we took the change back out.

I. INTERNATIONAL FANWORKS DAY 2025

On and leading up to February 14th, Communications celebrated the 11th annual International Fanworks Day (IFD)! Translation helped make IFD content available in 26 languages.

Celebrations included a Feedback Fest, Discord server chatting and games, the IFD Fanlore Challenge in collaboration with Fanlore, and more. Thanks to everyone who participated and joined the festivities, and to the volunteers from across the OTW who helped with its organization. We hope you enjoyed!

II. AT THE AO3

In February, Accessibility, Design & Technology implemented a few performance improvements and focused on important software updates (Ruby and Rails). Systems continued to work on keeping AO3 stable while waiting on new Elasticsearch servers. Jointly, they published an update on Intermittent site slowness and errors, which Translation helped make available in 22 languages.

Open Doors finished importing the memorial archive Remembering Tiger Lily Roar. It was enthusiastically received, especially from fans of Batman, Young Justice, and Nightwing.

In January, Policy & Abuse received 2,957 tickets, while Support received 3,595. AO3 surpassed 70,000 canonical fandoms, and Tag Wrangling wrangled over 465,000 tags: more than 1,100 tags per wrangling volunteer!

In February, Tag Wrangling also collaborated with Communications on a page for the OTW website about the Tag Wrangling Committee, which gives an overview of their work, who they collaborate with most, and explains the "lifecycle of a tag."

III. ELSEWHERE AT THE OTW

In addition to the annual IFD editing challenge, Fanlore also ran a themed Femslash February month! Check out the highlighted posts on their Tumblr.

Legal worked with others to advocate against legal proposals requiring ID checks and age verification for websites in various jurisdictions. They also responded to a number of questions from the public.

TWC announced a new upcoming special issue this month, titled "Latin American Fandoms"! The deadline for submissions is January 1, 2026, and the issue is slated for publication in 2027.

IV. GOVERNANCE

Board held the first quarter public meeting on January 26, with 69 attendees and 13 questions asked. All questions were answered live and the official meeting minutes are available on the OTW website.

Board Assistants Team worked hard on several ongoing projects this month: a review of the Board Discord server, non-profit training research, and OTW emergency procedures as part of the OTW culture roadmap.

In February, Strategic Planning provided Volunteers & Recruiting with research on volunteer retention at organizations similar to the OTW. This is a step in the Strategic Plan's Retention goal to better support OTW volunteers and keep them engaged throughout their time volunteering. They’ve also worked on research for goals related to Paid Staff positions.

Development & Membership arranged OTW's attendance at Ret-Con in Durham, North Carolina, U.S., this month where one of their volunteers ran a panel on searching for lost media. Come see the OTW soon at the Tucson Festival of Books in Arizona, U.S.; Chicago Entertainment and Comic Expo (C2E2) in Illinois, U.S.; Supanova Melbourne in Australia; CitrusCon (online); and more—our tables have plenty of goodies and shenanigans to share!

V. IT'S ALL ABOUT THE PEEPS

Volunteers & Recruiting conducted recruitment for three committees in January: Communications, User Response Translation, and Volunteers & Recruiting.

From January 22 to February 19, Volunteers & Recruiting received 135 new requests and completed 91, leaving them with 72 open requests. As of February 19, 2025, the OTW has 863 volunteers. \o/ Recent personnel movements are listed below.

New Committee Chairs: Apple and choux (Communications)
New Communications Volunteers: Indes (Posting Specialist) and 1 Site Moderator-Weibo
New Volunteers & Recruiting Volunteers: corr (Senior Volunteer), Ehryn, Gwendolyn, Kalincka, Kathleen B, and 2 other Volunteers

Departing Directors: Jenni D. (Paid Staff Transition Lead)
Departing Committee Chairs: Prisca (Translation Chair), Jenni D. (QA&T Lead)
Departing Communications Volunteers: 1 TikTok Moderator
Departing Development & Membership Volunteers: 1 Shipping Specialist and 1 Volunteer
Departing Open Doors Volunteers: 4 Import Assistants
Departing Tag Wrangler Volunteers: Roland, Inrainbowz, Sijing, and 20 other Tag Wranglers, and 1 Supervisor
Departing Translation Volunteers: A_I, Hao and 2 other Translators

For more information about our committees and their regular activities, you can refer to the committee pages on our website.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan-run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with GenreCat, who volunteers as part of the Policy & Abuse Committee.

How does what you do as a volunteer fit into what the OTW does?

The Policy & Abuse committee is responsible for interpreting and enforcing the Terms of Service on AO3. When users report content that they believe isn't allowed on AO3, that report comes to us. We then investigate independently and determine if the report is about something that is actually against AO3's Terms of Service. If it is, then we'll contact the person who posted it and tell them what they need to remove and why. If it's not a violation, we'll let the reporter know, and provide information about how they can avoid seeing similar content in future. We also answer questions about what is or isn't allowed on AO3.

Because we're an all-volunteer team, and not a very large one, the wait-times on tickets can be lengthy. Here's some advice if you want your ticket to be processed more quickly:

1. Provide us a direct link to the thing you want to report. If that's a work, provide us a link to the work. If you want to report multiple works, provide links to each work in your report description. If it's a comment, select the 'Thread' button on the comment to get the direct link to that comment. If you only report the user's profile instead of the thing they posted, we have to go track it down, which immediately makes a case take longer.
2. Don't report more than one user at a time (unless they're co-creators on the same violating work). Having multiple unrelated users on one report complicates the paperwork for us.
3. Don't encourage other people to also report it. We investigate every report we receive, and we don't make rulings based on how many people reported it. All mass-reporting does is give us more admin work that has to be handled before we can actually address the problem.
4. If you're reporting plagiarism or copyright infringement, give us a link to the source material. Please don't make us guess!
5. Be succinct. We only need a short description of what and where the problem is -- a single sentence is usually sufficient.

What is a typical week like for you as a volunteer?

I usually do PAC work every day, sometimes in long chunks and sometimes just quick check-ins. If I only have a short period of time, I'll catch up on messages from other volunteers and check new tickets that have come in. If there's tickets that haven't been categorized, I'll categorize them—categories help PAC volunteers decide what tickets to work on next. If there's higher-priority tickets, I'll quickly glance at them to attach evidence and see if there's something that we can resolve quickly.

When I have more time to work in a stretch, I'll review cases that other volunteers are handling and sign off on their plans of action, or I may pick up new tickets of my own to handle. I also spend quite a lot of my time working on documentation. PAC is constantly reviewing portions of our internal policies, training, and guidance material, which I like being involved in; it helps us determine better methods of doing things and ensures that we stay consistent in our rulings.

What made you decide to volunteer?

I'd been on AO3 for about a decade, and I'd always wanted to volunteer, because I feel like AO3 is a really important thing for fandom to have. I've been in fandom long enough to remember how slash fiction was banned or highly censored on a lot of older sites explicitly because of homophobia, and compared to that AO3 was a much-needed breath of fresh air. However, the stars had never quite aligned for me to apply—until the middle of 2020, when like many people, I suddenly had a lot more time where I was supposed to be at home. So when the next round of applications opened, I sent mine in.

What has been your biggest challenge doing work for the OTW?

The OTW is a very big organization, and it has a lot of inertia. At times, trying to push for necessary change—procedural or cultural—has been very frustrating. However, since I've joined the OTW I've seen this improve a lot, both within PAC and within the OTW overall. I'm very hopeful that we've got a brighter future ahead of us.

On a much less serious note: in terms of tickets that are challenging, personally it is the ones that are labelled only 'spam'. This is because many, many things get called 'spam', so I never know what the ticket is about until I go and investigate the link. A small sample of things I have seen called 'spam' includes: donation requests, duplicate postings of works, fanworks that have deliberately terrible grammar and spelling, fanworks that have the wrong pairing tag, comments consisting entirely of emojis, works that are just "WIP coming soon", works that are solely requests for prompts, copyright infringement, plagiarism, works with dozens of extra fandom tags, death threats, and comments from actual spambots. Some of these are violations, some of them aren't. It's nice to have a better idea of what I'm getting into before I open a report. So a request for anyone reading this—if you're reporting actual spambot spam, please say 'spambot' somewhere in your report instead of just 'spam'! And if it's not an actual spambot, please include an extra 2-3 words of description. Your ticket-handler will appreciate it!

What fannish things do you like to do?

I spend a lot of time reading and writing fic! Fellow PAC volunteers introduced me to several new fandoms in the last couple of years, the biggest of which are MXTX's novels. One of the things I love about big fandoms is that there's so much fic, it would be really difficult for me to work through it all—there's always something new to read.

Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in the comments. Or if you'd like, you can check out earlier Five Things posts.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan-run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.