[syndicated profile] otw_news_feed

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.

[syndicated profile] otw_news_feed

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.

birdylion: picture of an exploding firework (Default)
[personal profile] birdylion posting in [community profile] fancake
Fandom: Leverage
Pairings/Characters: Alec Hardison/Parker/Eliot Spencer, Peggy Milbank, Amy Palavi
Rating: General Audiences
Length: 21452 words
Creator Links: [archiveofourown.org profile] page_runner
Theme: food & cooking, casefic, competence, outsider pov

Summary:
She was only here for a long weekend, using this convention as an excuse to see Alice for the first time in over a year, or using Alice as an excuse to get away for a convention, or using both as a reason to finally take a vacation, because it was about damn time.
At least, that was the original plan.

Reccer's Notes:
Peggy Milbank is a side character who appears in 2 episodes: once when Parker's alias "Alice White" gets called in for jury duty, and once when Parker, Sophie and Tara sneak into a ball at an embassy for an event where Peggy does the catering.

This fic has her meeting the team once more, and has her involved in a job in Portland when they investigate a sketchy business man who drives independent food cart owners out of business, not shying away from inflicting violence on them in the process.

While the team does their thing, Peggy offers to take over the food cart, and does so with remarkable competence - learning a whole new cuisine on the fly. Food plays a big role in the whole story, because of their case, but also because now there are several people in one place who care a lot about food. It's also about a community of food cart owners. And just like Eliot found a way out of his violent life by learning how to cook, there's a side plot in this story how he does that for others too.

While the ship Eliot/Parker/Hardison isn't the main focus, it is definitely in the background, and Peggy's perspective is a really nice outsider POV on them, so I tagged it as such as well.

Fanwork Links: The Food Cart Job on ao3
birdylion: picture of an exploding firework (Default)
[personal profile] birdylion posting in [community profile] fancake
Fandom: Leverage
Pairings/Characters: Maggie Collins, Eliot Spencer, Alec Hardison, Parker (Leverage), Amy Palavi
Rating: General Audiences
Length: 711 words
Creator Links: [archiveofourown.org profile] Hagar
Theme: food & cooking, gen

Summary: Her ex-husband's associates are occasionally useful. For example, when Maggie has a really bad feeling about her latest client.

Reccer's Notes:
Maggie visits the brewpub looking for help regarding a client of hers. It's lovely how the food she is served there acts as kind of character description for the relationship between her, Eliot, Hardison and Parker.

Fanwork Links: What friends are for on ao3
full_metal_ox: Lan Wangji from Mo Dao Zu Shi, with his bunnies. (bunnies)
[personal profile] full_metal_ox posting in [community profile] fancake
Fandom: Mo Dao Zu Shi
Pairings/Characters: Gen; M/M; Lan Wangji/Wei Wuxian; Lan Yuan, Wei Wuxian, Lan Wangji, OCs
Rating: General Audiences
Length: 2,442 words
Content Notes: No Archive Warnings Apply, anonymous author, autobiographical incident, Chinese diaspora feels, inappropriate choice of rabbit food, racist microaggression, secondhand embarrassment
Creator Tags:
Based on a True Story, yes my mom really couldn't find a basic cake and so we had to go with bread, Fluff, Family Feels, Family Fluff, Baking, Icing, Frosting, AHAHAHAAHAHAHAHH THOSE ARE TAGS, Michael's (the store) makes a big appearance, Father's Day, but idc if it's not father's day yet, I was inspired, Inspired by Real Events
Creator Links: none
Theme: Food & Cooking, Cultural Differences, Family, Fluff, Modern AU, Slice of Life

Summary: In which Sizhui and his Baba ice a loaf of bread for Father's Day (plus some angst, but we don't really have to get into specifics do we?)

Author’s Notes:

something i wrote while having writers block

enjoy

(also stay safe and wash your hands and quit going outside if you are)

this isn't really asian rep it just happened when i was 10 and i typed for two hours also its may and here we are with a fictionalized crackheaded version of what happened

yes there were mean girls

… lan zhan's the one getting the cake because his personality's the closest to my dad's but like my dad cut off the frosting and we ended up using the bread for other stuff


Reccer’s Notes: The Chinese-American author posted this anonymously on 8 May 2020 for U.S. Asian and Pacific Islander Month, apologizing that “this isn’t really asian rep”; given that the canon creator is Asian, her target audience is Asian, the characters are Asian, and the OP is Asian fictionalizing their Asian family’s real-life experience, I personally don’t see how it can avoid being Asian Rep.

The author’s self-consciousness—both at the time of writing and in retrospect—is flying from the ramparts, and arguably an integral part of the story. They never did emerge from anonymity, and they’ve since deleted the story—which is a shame, because this is a valid slice-of-life in the Lynda Barry vein, with the OP’s imaginary friends as proxies. Since there seems to be no identifying information that could be used to trace them, I don’t think posting a Wayback Machine capture will expose them to further embarrassment.

And let’s not be like the Mean Girls at Michael’s, okay?

Fanwork links: a loaf of bread is not a substitute for a blank cake

Forging Ghost is Moving to the AO3!

Sep. 11th, 2025 06:06 pm
[syndicated profile] otw_news_feed

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.

pronker: barnabas and angelique vibing (Default)
[personal profile] pronker posting in [community profile] fancake
Fandom: Dark Shadows

Pairings/Characters: Roger Collins, CC Female, Which Would Give Away Too Much If Named

Rating: G

Length: 2,394 words

Creator Links: AO3 Profile

Theme: Food & Cooking

Summary: Roger meets a friend for dinner who shares his discomfort regarding marriages.

Reccer's Notes: Roger remains one of my favorite Dark Shadows characters, acted superbly by Louis Edmonds, a veteran of stage costume dramas. He always wears period clothing with impeccable insouciance despite figure-hugging trousers, wing collars, and Victorian handlebar moustaches. In this fic, we see how much food presents an opportunity for revealing, soul searching reflections with a sympathetic friend, in fact so much that they don't even eat until the last paragraph or so. The universality of sharing food provides a letting down of the hair, so to speak, voluminous in his friend's case and not-so-much in his. There's an absolutely delightful twist at fic's end. Also, the AO3 profile mentions Author's website, WickerManStudios which contains stories along with more personal content.

Fanwork Links: Mysterious Circumstances

SGA: Battle Potato by fiercelydreamed

Sep. 11th, 2025 11:09 pm
mific: (Teyla serious)
[personal profile] mific posting in [community profile] fancake
Fandom: Stargate Atlantis
Characters/Pairings: Gen. Teyla Emmagan & Rodney McKay & John Sheppard & Ronon Dex
Rating: G
Length: 7229
Content Notes: No AO3 warnings apply.
Creator Links: fiercelydreamed on AO3, anatsuno on AO3, anatsuno on Audiofic Archive
Themes: Food and cooking, Team as family, Friendship, Hurt/comfort

Summary: The thing was, John had never been good at patient, and Teyla looked like okay was a couple galaxies over from wherever she was now.

Reccer's Notes: A touching hurt/comfort story set after the team rescues Teyla from Michael. Although Teyla and her baby are back in Atlantis, she's slow to recover and remains low and depleted. Rodney has a plan to cheer her up, though, involving food, and he ropes John in to help. It was I think written in the hiatus before the last season so a few minor details have been jossed, but that doesn't matter. This is the best sort of found family story, with them all rallying around to support Teyla. Lovely.

Fanwork Links: Battle Potato, and there's an excellent podfic read by anatsuno.

chibifukurou: (Psyduck Mystery Dungeon)
[personal profile] chibifukurou posting in [community profile] fancake
Fandom:The Scum Villain's Self-Saving System
Pairings/Characters: Luo Binghe/Shen Yuan
Rating: T
Length: 14.5k
Creator Links: [archiveofourown.org profile] CheckersXIV
Theme: Food and cooking, (Five) Things, Complete AU

Summary: Luo Binghe has accepted his life for what it is: a dull repetition of a burned-out passion for a job. Back when he started his "Not Your Mother's" cooking channel on youtube, he had been ready to face the world. Now he just wants the world out of his face. When he hits one more bump in the road, he can't really say it's too surprising considering that the universe seems to just hate him.

And yet, the universe sends him to Shen Yuan.
_
Or 5 times Shen Yuan accidentally distracts Luo Binghe's attention from his videos, and the one time Luo Binghe gets his.

Reccer's Notes: This theme was a good excuse to go back for a reread. I love a fic where the point isn't so much falling in love as growing into the kind of person ready to love and be Loved. 

5+1 is always a fun framing device. Particularly when combined with in universe comment section. And I love that this js a broad world with various people who know each other from various settings in it. 

Fanwork Links: The Way to a Man's Heart is His Stomach
[syndicated profile] otw_news_feed

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.