Posted by Lute

In the last year, AO3 has seen a rise in “art commission” spambot comments. The bots leaving these comments pretend to be artists who want to make comics or illustrations for a fan’s fic. After convincing their targets to contact them off AO3, they scam their targets into paying for that art. Fans have reported that after sending payment, they either received AI-generated art or nothing at all.

AO3 has been working on various methods that we hope will reduce the spam. However, these scammers are persistent and creative about circumventing our protections.

To avoid falling victim to one of these scams, the Policy & Abuse committee recommends:

  1. Do not commission art from someone who solicits you by commenting on your work on AO3. Commercial activity is prohibited on AO3. If someone is encouraging behavior that violates our Terms of Service, it’s a good idea to be cautious. They likely do not have your best interests in mind.
  2. Do not provide your email or social media contact information to a commenter who asks for it, even if they say they’d just like to discuss your work further. Scammers try to get you to talk to them privately, because it is often easier to deceive or manipulate people in a one-on-one conversation.

Example of this type of scam

An example AO3 comment exchange with a spambot.

Elizabethbrown123: Wow, this fic was amazing! The way you describe things is so vivid and really brought the characters to life. Your work moved me to tears.
cool_username_42069: Thanks! I’m glad you enjoyed it. <3
Elizabethbrown123: You’re welcome! I’m so glad you responded. Do you use Discord or Twitter, or could you tell me your email so we can chat more? I’ve got some ideas I’d love to share with you, but I don’t want to spoil anything.

This is just one example of how a scammer tries to lure the work creator onto a different platform where they can pressure the creator into commissioning art. These scammers use AI to generate realistic-sounding comments. The comments often contain generic praise or statements that could apply to any work, but sometimes they are extremely lengthy and/or specific. If the creator is suspicious and asks why the scammer wants to move the conversation off-site, they will typically claim that they aren’t a scammer and/or that they can explain things better in private.

However, unlike a regular user, a scammer will always do at least one of two things:

  1. They will ask you to commission art from them, or
  2. They will share their contact information and/or ask for your information (such as an email address or username on a site that supports private messaging, like Instagram or Discord)

If you suspect that you’ve received a spam comment on your work, don’t reply and especially do not provide them with your contact information. Just report the comment to Policy & Abuse so that we can take care of it.

What to do if you encounter this scam

If you receive a scam comment from a guest, you can press the “Spam” button on the comment. This helps train our automated spam-checker to better detect this type of behavior.

If you encounter a scammer that has a registered account, or if you encounter a guest posting scam comments on someone else’s work, please report them to the Policy & Abuse committee. To do so:

  1. Select the “Thread” button on the scammer’s comment. This will take you to the specific comment page.
  2. Scroll to the bottom of the page and select Policy Questions & Abuse Reports.
  3. In the “Brief summary of Terms of Service violation” field, enter “Spambot”.
  4. In the “Description of the content you are reporting” field, enter “This is a spambot, their username is USERNAME.”

Reporting in this fashion helps us auto-sort your report so that it can be handled as soon as a Policy & Abuse volunteer is available. To help us address reports about these types of bots as fast as possible, please only submit one report per account, and don’t include multiple accounts in the same report.

If you encounter a scam commenter on someone else’s work, you can let the work creator know the commenter is likely a bot and link them to this news post.

We also encourage you to share this post on social media and help spread the word about how to protect yourself from scammers and reduce spam on AO3.

Posted by therealmorticia

The Pinky and the Brain Page, a Pinky and the Brain fanfiction and fanart archive, is being imported to the Archive of Our Own (AO3).

In this post:

Background explanation

James, the archivist, used to run and maintain a Pinky and the Brain fandom site from around 1995 to 2000. When he recently found some of the stories in an old hard drive he searched the Internet for some of them, but his searches came up empty. Rather than letting those stories sit unread he thought he would rather they be shared on the AO3 for people to enjoy and remember.

The purpose of the Open Doors Committee’s Online Archive Rescue Project is to assist moderators of archives to incorporate the fanworks from those archives into the Archive of Our Own. Open Doors works with moderators to import their archives when the moderators lack the funds, time, or other resources to continue to maintain their archives independently. It is extremely important to Open Doors that we work in collaboration with moderators who want to import their archives and that we fully credit creators, giving them as much control as possible over their fanworks. Open Doors will be working with James to import The Pinky and the Brain Page into a separate, searchable collection on the Archive of Our Own. As part of preserving the archive in its entirety, all fanfics and fanart currently in the The Pinky and the Brain Page will be hosted on the OTW’s servers, and embedded in their own AO3 work pages.

We will begin importing works from The Pinky and the Brain Page to the AO3 after September 2025. However, the import may not take place for several months or even years, depending on the size and complexity of the archive. Creators are always welcome to import their own works and add them to the collection in the meantime.

What does this mean for creators who had work(s) on The Pinky and the Brain Page?

We will send an import notification to the email address we have for each creator. We’ll do our best to check for an existing copy of any works before importing. If we find a copy already on the AO3, we will add it to the collection instead of importing it. All works archived on behalf of a creator will include their name in the byline or the summary of the work.

All imported works will be set to be viewable only by logged-in AO3 users. Once you claim your works, you can make them publicly-viewable if you choose. After 30 days, all unclaimed imported works will be made visible to all visitors.

Please contact Open Doors with your The Pinky and the Brain Page pseud(s) and email address(es), if:

  1. You’d like us to import your works, but you need the notification sent to a different email address than you used on the original archive.
  2. You already have an AO3 account and have imported your works already yourself.
  3. You’d like to import your works yourself (including if you don’t have an AO3 account yet).
  4. You would NOT like your works moved to the AO3, or would NOT like your works added to the archive collection.
  5. You are happy for us to preserve your works on the AO3, but would like us to remove your name.
  6. You have any other questions we can help you with.

Please include the name of the archive in the subject heading of your email. If you no longer have access to the email account associated with your The Pinky and the Brain Page account, please contact Open Doors and we’ll help you out. (If you’ve posted the works elsewhere, or have an easy way to verify that they’re yours, that’s great; if not, we will work with the The Pinky and the Brain Page mod to confirm your claims.)

Please see the Open Doors Website for instructions on:

If you still have questions…

If you have further questions, visit the Open Doors FAQ, or contact the Open Doors committee.

We’d also love it if fans could help us preserve the story of The Pinky and the Brain Page on Fanlore. If you’re new to wiki editing, no worries! Check out the new visitor portal, or ask the Fanlore Gardeners for tips.

We’re excited to be able to help preserve The Pinky and the Brain Page!

– The Open Doors team and James

Commenting on this post will be disabled in 14 days. If you have any questions, concerns, or comments regarding this import after that date, please contact Open Doors.

OTW Board Meeting, October 5, 2025

  • Sep. 19th, 2025 at 3:02 PM

Posted by Elintiriel

The OTW Board will be holding its next public meeting at 00:00 UTC on October 5 (what time is that for me?).

This meeting will be held in the Board Discord server. The server will have a team of moderators and a set of rules (including question rules) and community guidelines. The server will remain open even after the meeting, but the channels for meeting and asking questions will be read-only. Board will be posting replies to questions that do not get addressed during the scheduled meeting two weeks after the meeting in the server’s #questions-answers channel.

The agenda will include:

  • Decisions made since the last public board meeting
  • 2025 OTW Board Election wrap-up
  • OTW Culture Roadmap Update
  • Board Roadmap Update
  • Any other business (Questions & Answers)

Prior to this meeting, there is an opportunity to ask questions in advance to be answered as part of the meeting. This allows anyone who wishes to ask the Board questions, whether they will be able to attend the meeting live or not. Board will also accept questions during the meeting.

Questions submitted to this Google Form will be accepted up to three days before the meeting begins or until 50 questions have been submitted. At that point, the form will be turned off. You need to be logged in to a Google account to submit a question. In the future, these rules may be amended as needed.

Further information will be available in the OTW Board Discord server.

Posted by therealmorticia

Do you have experience copyediting or proofreading academic journals? Would you like to wrangle AO3 tags? Can you read and translate from Chinese to English? Can you read and translate from Italian to English? Do you have experience in managing or leading people?

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

  • TWC Committee Copyeditor – closing 24 September 2025 at 23:59 UTC
  • Tag Wrangling Volunteer – closing 24 September 2025 at 23:59 UTC or after 125 applications
  • Tag Wrangling Volunteer (Chinese) – closing 24 September 2025 at 23:59 UTC or after 45 applications
  • Tag Wrangling Volunteer (Italian) – closing 24 September 2025 at 23:59 UTC or after 30 applications
  • Fanlore Chair Track Volunteer – closing 24 September 2025 at 23:59 UTC or after 40 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.

TWC Committee 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.

Applications are due 24 September 2025

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

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 Bahasa Indonesia (Indonesian), Čeština (Czech), Español (Spanish), isiZulu (Zulu), Polski (Polish), Português brasileiro (Brazilian Portuguese), Suomi (Finnish), Tiếng Việt (Vietnamese), Türkçe (Turkish), Українська (Ukrainian), ไทย (Thai), Русский (Russian), беларуская (Belarusian) and 한국어 (Korean) — but help with other languages would be much appreciated!

Applications are due 24 September 2025 or after 125 applications

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

Tag Wrangling Volunteer (Chinese)

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 Chinese.We welcome all Chinese dialects! The work will involve both regular Tag Wrangling work and translating tags from Chinese into English.

Applications are due 24 September 2025 or after 45 applications

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

Tag Wrangling Volunteer (Italian)

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 Italian. The work will involve both regular Tag Wrangling work and translating tags from Italian into English.

Applications are due 24 September 2025 or after 30 applications

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

Fanlore Chair Track Volunteer

Do you have experience in managing or leading people? Are you an organizational wizard? Do you have an interest in preserving fannish history or experience in wiki editing? The Fanlore committee is looking for new Chair Track Volunteers to join our team!

Fanlore is the committee responsible for maintaining and promoting the Fanlore wiki. We promote Fanlore on social media, run Fanlore editing challenges, support Fanlore editors, write the wiki’s policy and help pages, and respond to emails from editors and readers. The Chair Track Volunteer position is for people who have the time and dedication to learn all about our operations so that they can be considered for the role of committee Chair.

We’re looking for someone who has experience in wiki editing and an understanding of social media, who is comfortable with personnel management and training new recruits, and who is experienced in leadership or management whether in a business or nonprofit environment. Candidates also need strong time management skills and the ability to work on and track multiple tasks at a time. If that’s you, please apply!

For your application to be considered, you will be required to complete a short task within one week of submitting your application.

Applications are due 24 September 2025 or after 40 applications.

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

Posted by Lute

AO3 Tag Wranglers continue to test processes for wrangling canonical additional tags (tags that appear in the auto-complete) which don’t belong to any particular fandom (also known as “No Fandom” tags). This post will provide an overview of some of these upcoming changes.

In this round of updates, we continued a method which streamlines creation of new canonical tags, prioritizing more straightforward updates which would have less discussion compared to renaming current canonical tags or creating new canonical tags which touch on more complex topics. This method also reviews new tags on a regular basis, so check back on AO3 News for periodic “No Fandom” tag announcements.

None of these updates change the tags users have added to works. If a user-created tag is considered to have the same meaning as a new canonical, it will be made a synonym of one of these newly created canonical tags, and works with that user-created tag will appear when the canonical tag is selected.

In short, these changes only affect which tags appear in AO3’s auto-complete and filters. You can and should continue to tag your works however you prefer.

New Canonicals

The following concepts have been made new canonical tags:

In Conclusion

While all these new tags have already been made canonical, we are still working on implementing changes and connecting relevant tags, so it’ll be some time before these updates are complete. We thank you in advance for your patience!

While we won’t be announcing every change we make to No Fandom canonical tags, you can expect similar updates in the future on the tags we believe will most affect users. If you’re interested in the changes we’ll be making, you can continue to check AO3 News or follow us on Bluesky @wranglers.archiveofourown.org or Tumblr @ao3org for future announcements.

You can also read previous updates on “No Fandom” tags as well as other wrangling updates, linked below:

Got Questions?

For more information about AO3’s tag system, check out our Tags FAQ.

In addition to providing technical help, AO3 Support also handles requests related to how tags are sorted and connected.​ If you have questions about specific tags, which were first used over a month ago and are unrelated to any of the new canonical tags listed above, please contact Support instead of leaving a comment on this post.

Lastly, as mentioned above, we’re still working on connecting relevant user-created tags to these new canonicals. If you have questions about specific tags which should be connected to these new canonicals, please refrain from contacting Support about them until at least two months from now.

OTW Guest Post: Fandoms in the Classroom

  • Sep. 13th, 2025 at 2:22 PM

Posted by therealmorticia

Every month the OTW hosts guest posts on our OTW News accounts to provide an outside perspective on the OTW or aspects of fandom. These posts express each individual’s personal views and do not necessarily reflect the views of the OTW or constitute OTW policy.

Karis Jones, PhD (she/her) is an educator, literacy consultant, public humanities scholar, and community activist, as well as Assistant Professor of Secondary English Language Arts at Baylor University. She has published widely, including in the journal of Transformative Works and Culture, and won several scholarly awards from the American Educational Research Association.

Scott Storm, PhD (he/him) is an Assistant Professor of Literacy in the School of Education at the University at Albany, State University of New York. Scott is a former high school teacher with 15 years of experience designing, founding, and sustaining urban public schools; his work has appeared in Journal of Literacy Research, Literacy Research: Theory, Method, and Practice, Journal of Adolescent & Adult Literacy, and English Teaching Practice & Critique, among others.

Today, Dr. Karis Jones and Dr. Scott Storm, authors of the book Fandoms in the Classroom: A Social Justice Approach to Transforming Literacy Learning—join us to talk about how bringing fandom into the classroom can turn student passion into real learning.

How did you first find out about fandom and fanworks?

As fans of fantasy and science fiction genres ourselves, we have long been interested in fandoms and fan cultures. Even as teens, we wrote our own creative fanworks inspired by the stories that we loved. Once we became teachers, we noticed that our students had incredible passionate intensities around the fandoms that they loved. Moreover, they were participants in fan cultures, reading memes, analyzing discourse, and writing fanfiction. As English language arts teachers, we noticed that students were not only excited about participating in fandoms, but also that these were spaces of rich literacy learning. For example, students posting their original writing online often revised their stories based on feedback from the community in order to strengthen the writing and deepen connections. Reflecting on how important fandoms had been to us and in seeing how important fandoms were to our students, we knew that we had to think about how to make school a place that could support these passionate student interests for literacy learning.

Your book highlights how bringing fandoms into the classroom can shift the focus toward student experiences and interests. How does this approach support a more student-centered form of pedagogy, and what kinds of transformations have you seen as a result?

Many English teachers create lectures focused on the teacher’s interpretations of often-read canonical literature. This puts the thrust of intellectual work on teachers. However, it is students who need to be doing the learning and who should therefore do much more of the daily intellectual work of the classroom. We use students’ interests in fandoms in order to center student expertise. Students come with much knowledge about how the texts that they love were created and about some of the different ways to interpret those texts. We have students lead inquiry-based discussions with their peers to dig even deeper into these texts. Then they build off these discussions by reading extensively, writing analytic papers, and presenting their work to the local community. As students engage with fandoms they love, we note when they are using literary elements to create deeper interpretations. For example, sometimes a student will trace the metaphors or characterization in a fandom but might not use those exact words to do so. During student-led class discussions, we sit in the circle with students and chime in when they are using an analytic tool and that literary scholars have given a special name like metaphor, hyperbole, archetypes, or tropes. In this way, over a few weeks, we build a large set of analytic tools that students use to make sense of texts. Thus, throughout all the discussion, reading, and writing that students are doing in our classes, students are learning deeply because it is the students who are doing the crux of the intellectual work.

One of the intriguing ideas in your book is the reframing of academic disciplines as fandoms. How might this way of thinking open up new possibilities for teaching across different disciplines?

In Chapter 6 “Imagining Academic Disciplines as Fandoms,” we give examples of ways that teachers can put their academic disciplines in conversation with media fandoms. This helps students navigate across disciplinary practices, which may at first feel distant or strange, by comparing them with media fandom practices, which may feel more familiar. Guiding youth to compare communities and think through ways to improve or remix their practices can be a productive pathway for making sense of the academic disciplines. For example, teachers can take up a participatory fandom lens to help youth understand disciplinary conversations happening on social media (e.g. the controversy around Charlotte the Stingray’s pregnancy in March 2024), or schools can take up fandom formats like conventions to help youth dialogue around current disciplinary topics (e.g. a school academic history conference including symposium panels moderated by historians at local universities).

Integrating fandom into the classroom sounds exciting—but we know it’s not always straightforward. From your perspective, what are some of the challenges educators face when trying to incorporate fandom-based practices in their teaching?

As educators who have been teaching with fandoms for a long time, we absolutely understand the challenges. In Chapter 8 “Tackling Barriers to Fandom-Based Teaching,” we walk readers through a series of questions that educators have asked us about this kind of work. We give strategies for advocating with one’s administration, even in light of standardized curricula. We talk about ways that educators can bring fandom media into classroom spaces even if they are not familiar with those fandoms themselves. We consider how to balance issues of mature content with issues of censorship. We guide readers through issues of student resistance to publishing their work in fandom communities. We talk readers through suggestions of ways to engage youth with local conventions — or ways to create your own!

How did you hear about the OTW and what do you see its role as?

We are obsessed with OTW! This may not be surprising, but we first encountered OTW as fanfiction readers. We love how this platform is built for fans by fans, and have a special appreciation of how it is organized in a bottom-up way that lifts up fan-created genres (e.g. Magnifico & Jones, 2025). Additionally, Karis is a big fan of Naomi Novik’s writing. At a local author talk, she learned more about Novik’s role in the platform’s founding. This led her to explore current academic work on fandoms in the JTWC. Later, Karis went on to publish her own work in the JTWC. We hope that new trajectories of media and fandom studies continue to remain in close conversation with the field of education, engaging in interdisciplinary conversation and research, because we believe this strengthens our understanding of fandoms and their implications across fields.

What fandom things have inspired you the most?

We have been most inspired by fan acts that move the world toward justice. We are excited by fandoms that bring attention to issues of representation and work to make sure that all kinds of people are represented in creative and fanworks. We love fandoms that think about how to make communities more inclusive and are drawn to fan communities that focus on opening doors for everyone to participate instead of being gatekeepers who want to limit fandoms to only the most diehard fans or exclude groups of people from participating. What inspires us most is when fandoms can be spaces that bring people together in order to follow their passions, and perhaps even change the world.


We encourage suggestions from fans for future guest posts, so contact us if you have someone in mind! Or if you’d like, you can check out earlier guest posts.

Forging Ghost is Moving to the AO3!

  • Sep. 11th, 2025 at 6:06 PM

Posted by callmeri

Forging Ghost, a Spike/Angel fanfiction archive, is being imported to the Archive of Our Own (AO3).

In this post:

Background explanation

Forging Ghost was a Yahoo! Group dedicated to fanfiction for Spike/Angel from Buffy the Vampire Slayer and Angel: the Series. Ghostsforge, the moderator, preserved Forging Ghost when Yahoo! Groups was shut down in 2019 and asked Open Doors for assistance in importing its works to AO3.

The purpose of the Open Doors Committee’s Online Archive Rescue Project is to assist moderators of archives to incorporate the fanworks from those archives into the Archive of Our Own. Open Doors works with moderators to import their archives when the moderators lack the funds, time, or other resources to continue to maintain their archives independently. It is extremely important to Open Doors that we work in collaboration with moderators who want to import their archives and that we fully credit creators, giving them as much control as possible over their fanworks. Open Doors will be working with Ghostsforge to import Forging Ghost into a separate, searchable collection on the Archive of Our Own. As part of preserving the archive in its entirety, all fanart currently in Forging Ghost will be hosted on the OTW’s servers, and embedded in their own AO3 work pages.

We will begin importing works from Forging Ghost to the AO3 after September. However, the import may not take place for several months or even years, depending on the size and complexity of the archive. Creators are always welcome to import their own works and add them to the collection in the meantime.

What does this mean for creators who had work(s) on Forging Ghost?

We will send an import notification to the email address we have for each creator. We’ll do our best to check for an existing copy of any works before importing. If we find a copy already on the AO3, we will add it to the collection instead of importing it. All works archived on behalf of a creator will include their name in the byline or the summary of the work.

All imported works will be set to be viewable only by logged-in AO3 users. Once you claim your works, you can make them publicly viewable if you choose. After 30 days, all unclaimed imported works will be made visible to all visitors.

Please contact Open Doors with your Forging Ghost pseud and email address(es), if:

  1. You’d like us to import your works, but you need the notification sent to a different email address than you used on the original archive.
  2. You already have an AO3 account and have imported your works already yourself.
  3. You’d like to import your works yourself (including if you don’t have an AO3 account yet).
  4. You would NOT like your works moved to the AO3, or would NOT like your works added to the archive collection.
  5. You are happy for us to preserve your works on the AO3, but would like us to remove your name.
  6. You have any other questions we can help you with.

Please include the name of the archive in the subject heading of your email. If you no longer have access to the email account associated with your Forging Ghost account, please contact Open Doors and we’ll help you out. (If you’ve posted the works elsewhere, or have an easy way to verify that they’re yours, that’s great; if not, we will work with the Forging Ghost mod to confirm your claims.)

Please see the Open Doors Website for instructions on

If you still have questions…

If you have further questions, visit the Open Doors FAQ, or contact the Open Doors committee.

We’d also love it if fans could help us preserve the story of Forging Ghost on Fanlore. If you’re new to wiki editing, no worries! Check out the new visitor portal, or ask the Fanlore Gardeners for tips.

We’re excited to be able to help preserve Forging Ghost!

– The Open Doors team and Ghostsforge

Commenting on this post will be disabled in 14 days. If you have any questions, concerns, or comments regarding this import after that date, please contact Open Doors.

AO3 Releases 0.9.420 – 0.9.426: Change Log

  • Sep. 10th, 2025 at 11:01 PM

Posted by callmeri

Over the past month, we rolled out behind-the-scenes upgrades and quality-of-life improvements across the site, including the addition of username links and chapter numbers to kudos and comment emails, respectively. We also made some major privacy and security enhancements, such as removing the email, birthday, and location fields from profiles and checking new passwords against known data breaches.

Special thanks and welcome to first-time contributors anna, Liz Watkins, Riya K, and theamandawang!

Credits

  • Coders: Abhinav Gupta, anna, Amy Lee, Bilka, Brian Austin, Ceithir, Connie Feng, Domenic Denicola, EchoEkhi, Hamham6, kitbur, Liz Watkins, marcus8448, Riya K, sarken, Scott, slavalamp, talvalin, theamandawang, weeklies
  • Code reviewers: Bilka, Brian Austin, Ceithir, HamHam6, james_, lydia-theda, marcus8448, redsummernight, sarken, Scott, weeklies
  • Testers: Allonautilus, ana, Anh P, Aster, Bilka, Brian Austin, calamario, choux, Dre, Keladry, Lute, lydia-theda, Pent, redsummernight, Runt, Sanity, sarken, Teyris, therealmorticia, weeklies, wichard

Details

0.9.420

On July 15, we massively improved the user search used by admins.

  • [AO3-6565] – We’ve improved the user search feature available to admins by moving it to Elasticsearch and adding the ability to search by past email addresses and usernames.
  • [AO3-7042] – Instead of redirecting to the main Collections page, we now give a 404 error if you try to access the collections page for a nonexistent user, work, or collection.
  • [AO3-7004] – We’ve added a database index to make it faster for database admins to search for comments using a specific guest name.

0.9.421

Following some email-related changes in our July 24 deploy, embedded images are now always stripped from comment emails, and usernames in kudos emails now link to the users’ dashboards.

  • [AO3-3154] – When you receive a kudos notification email, the names of users who have left kudos now link to the users’ dashboards.
  • [AO3-6060] – Even though they no longer had access to tag comment pages, former tag wranglers would still receive email and inbox notifications of replies to their old tag comments. This was both annoying and confusing, so we’ve stopped it from happening.
  • [AO3-6746] – If you changed your username or pseud name and you had some chapters that you co-created with another user, the chapter bylines would not always get updated with your new name. We’ve changed this so the cache is refreshed more reliably.
  • [AO3-6929] – The list of gift exchange sign-ups visible to collection maintainers now includes the pseud and username of signed-up users, instead of just their pseud.
  • [AO3-7011] – Using the Tab key to navigate in desktop Safari used to select hidden inputs, causing the focus indicator to temporarily disappear. We’ve fixed it so only visible links and inputs receive focus.
  • [AO3-7032] – If you tried to add your email to the invitation queue when it was already part of the queue, you would see two copies of the same error message. Now it only shows the error once.
  • [AO3-7065] – We fixed some intermittent failures in the automated tests for the bookmark importing tool used by Open Doors.
  • [AO3-7052] – We did a schema dump to capture what the current data structure looks like before we upgrade to Rails 7.2.
  • [AO3-7053], [AO3-7054], [AO3-7067], [AO3-7068] – We updated a whole bunch of gems and GitHub actions: reviewdog/action-rubocop, awalsh128/cache-apt-pkgs-action, nokogiri, and thor.
  • [AO3-5352] – We prepared the preface of work downloads that are attached to work deletion emails for translation.
  • [AO3-7001] – As an anti-abuse measure, we now strip embedded images from comment notification emails even when image embeds are enabled on the site itself.

0.9.422 & 0.9.423

On July 28, we made a number of small improvements all around the site. There were some issues while deploying these changes, so we did another release to fix it all up on the same day.

  • [AO3-5609] – We stopped sending subscription notifications for works hidden by admins, since hidden works are inaccessible to other users.
  • [AO3-7006] – When a comment contains an HTML list, the list numbers or bullet points no longer overlap with the commenter’s icon.
  • [AO3-7024] – You’ll no longer get an incorrect success message if you mark items in your inbox as read without selecting any comments.
  • [AO3-5476] – We cleaned up some unused code in the works controller.
  • [AO3-7064] – We updated the gems we use for automated testing.
  • [AO3-7072] – We updated the unicode gem to solve some issues with developing the AO3 software on Macs with Apple Silicon chips.
  • [AO3-5346] – Collection maintainers get an email notification when matches in a gift exchange have finished generating. We’ve improved the text of this email and prepared it for translation.
  • [AO3-6484] – We made a small change to the code that generates the HTML class names we use for hiding work blurbs by muted users. We were hoping this tweak would improve performance, but unfortunately it had no effect, so we’ll have to try again.
  • [AO3-6997] – If an Open Doors archivist tries to leave kudos while logged in to an archivist account, they’ll get an error message telling them to log in with their personal account instead.
  • [AO3-7015] – Work blurbs now contain an invisible code comment with the work’s update date, to make it easier for developers of third-party tools to automate downloads from index pages like tags, bookmarks, and search result listings.
  • [AO3-7021] – To make it easier to filter or search using work languages, we’ve added the language codes on the Languages page.
  • [AO3-7057] – We now provide any applicable error messages when an admin attempts to send an invitation directly to an email and something goes wrong.

0.9.424

On August 5, we deployed another batch of miscellaneous fixes.

  • [AO3-5025] – The Tag Wrangling committee can now use the Rich Text editor to edit the Wrangling Guidelines pages.
  • [AO3-7076] – We fixed some unwanted shadows that Chrome was adding to radio buttons and checkboxes.
  • [AO3-7088] – We fixed some flaky automated tests related to importing works from LiveJournal.
  • [AO3-7074] – We removed some unused CSS from our default site skin.
  • [AO3-6580] – We updated the account creation confirmation page’s title from “Create Registration” to “Account Created” so that it’s clearer you’ve successfully made an account.
  • [AO3-6818] – When an admin bans an email from being used for guest comments, that email is now also banned from requesting invitations.
  • [AO3-7026] – When we run a spam check on edited comments by new users, we now tell the spam checker that it’s an edit.
  • [AO3-7046] – We migrated the subscriptions table so it can hold more rows and we won’t run out of room in the future.

0.9.425

On August 19, we deployed an important change to account security that checks new AO3 passwords to see if they’ve been part of a known data breach. We also began allowing CSS variables in site skins.

  • [AO3-7073] – To better protect users’ privacy, we’ve removed the preferences and fields to display emails, birthdays, and locations on user profiles.
  • [AO3-7091] – We stopped using fixtures in our integration tests.
  • [AO3-7098] – We updated cache-apt-pkgs-action again.
  • [AO3-7099] – We bumped the version of actions/checkout – a utility that helps run automated tests on our code – from version 4 to version 5.
  • [AO3-3071] – Comment emails now include the chapter number, so you don’t have to follow the comment link to know where exactly it was left.
  • [AO3-7087] – To improve account security, we updated our password change process to prevent users from choosing passwords that are known to be compromised on other sites. (If you missed our post back on World Password Day, we also have some tips for keeping your AO3 account secure!)
  • [AO3-7090] – We changed links in emails to be HTTPS instead of HTTP.
  • [AO3-7093] – We added an automated test to make sure the fixtures used for seeding development databases result in valid records.
  • [AO3-7094] – We now allow limited use of CSS custom properties in site skins! You can find more information in the skins help text.

0.9.426

We upgraded to Rails 7.2 on August 26.

  • [AO3-7058] – We updated our version of Rails from 7.1 to 7.2.
  • [AO3-7095] – We added more example admin and user accounts with a greater variety of roles to our basic development dataset, which will make it easier for coders to work on things that require specific access levels.

Profile

cali: (Default)
[personal profile] cali
cali (theantimodel)
My Slash Fic Recs

Latest Month

May 2010
S M T W T F S
      1
2345678
9101112131415
16171819202122
23242526272829
3031     
Powered by Dreamwidth Studios
Designed by [personal profile] chasethestars