AO3 News

Post Header

Published:
2019-12-21 12:16:00 UTC
Tags:

The last several code deploys introduced some exciting changes to work posting: a big update to our rich text editor, support for the HTML5 audio and video tags, a little tweak in how we handle language selection, and some less confusingly labeled buttons! In addition, a whole lot of challenge improvements and behind-the-scenes infrastructure upgrades.

Credits

  • Coders: Alix R, cosette, Elz, Enigel, james_, redsummernight, Sarken, Tal, tickinginstant
  • Code reviewers: Ariana, bingeling, Enigel, james_, redsummernight, Sarken, Scott, tickinginstant
  • Testers: bingeling, Briar, CJ Record, GoldenFalls, Izzy, james_, Lady Oscar, lydia-theda, MagnusIsMyRock, McBangle, Nary, nimadge, Paula, Rebecca Sentance, redsummernight, Relle, Sarken

Details

Rich Text Editor

  • [AO3-5191] - We upgraded the version of TinyMCE that we use for our Rich Text Editor.
  • [AO3-5809], [AO3-5811] - The new version of TinyMCE overrides the browser's default context menu, which prevents desktop users from right-clicking to copy, paste, spell check, etc. We disabled this behavior.
  • [AO3-5812] - The same new version of TinyMCE defaults to a reduced interface for users on mobile devices. We disabled this behavior too.

Collections and Challenges

  • [AO3-4353] - Some inconvenient caching was affecting the display of tag set content (e.g. Character or Relationship tags) on challenge sign-up pages. Now the correct tags are shown.
  • [AO3-5786] - Trying to access the list of allowed tags from a challenge sign-up would throw an error 500, which is now fixed as well!
  • [AO3-5785] - Owners of collections were previously able to add works in other, anonymous collections to their own, which enabled them to see the work's creator. We've now made it impossible to add anonymous works to your collection.
  • [AO3-5101] - Trying to save a challenge with sign-ups open and a closing date set, but no opening date, would throw an error 500. Now the challenge profile correctly states that you can sign-up and until what date.
  • [AO3-5102] - If you closed sign-ups for a challenge before the set closing date, the challenge profile would show that sign-ups were closed, but ~in the future~~~ (i.e. the set closing date). Now the date just isn't displayed anymore, to avoid any confusion.
  • [AO3-5593] - When fetching a list of all collections a work had been approved to be in, we used an unnecessary query, which was not good for database performance. Much better now!
  • [AO3-4571] - You have two open assignments, and they both happen to be for the same recipient. You post a work fulfilling one of the assignments. However, the other assignment's ticky box is also checked in the posting form. If you don't notice this, you post the work and suddenly your other assignment is fulfilled as well. But it's really not! (Aww.) We now make sure only the correct ticky is ticked and you still have to write a second work for the other assignment. *\o/*

Language

  • [AO3-5702] - We previously had English set as the default language when posting a new work. This led to a lot of miscategorized works, since creators often wouldn't notice the language selection when posting non-English works. We now require all users to manually set the language their work is in.
  • [AO3-4605] - The form used for work imports now sports a mandatory "Choose a language" field as well.
  • [AO3-5790] - We accidentally broke filtering for works in português brasileiro or português europeu, so we intentionally fixed it.
  • [AO3-5616] - In our lists of FAQ categories available in Arabic or Hebrew, the first category name was misaligned. We've put it back in line.

Misc.

  • [AO3-5693] - Posting audio or video fanworks? Now you can use the HTML5 audio and video tags!
  • [AO3-4080] - We had a very peculiar bug where our devs weren't able to use multiple CSS box shadows on their development environments despite it being possible on the Archive itself. Turns out we had a broken regular expression in our code, but the fact that we had box-shadow in the wrong part of the production configuration file was hiding the issue. The bug has been fixed and the production config file updated, so now box-shadow works the same for everyone.
  • [AO3-4560] - We renamed the buttons for posting works: "Post Without Preview" becomes "Post", and "Save Without Posting" becomes "Save As Draft".
  • [AO3-5632] - When you follow a link from the Archive to another site or go to a page with the Twitter widget (e.g. a work), some information is automatically sent to the site (or Twitter). We have now limited referrer information and won't tell the site you clicked on (or Twitter) which page you were on.
  • [AO3-5761] - We have added the Rack::Attack gem, which enables us to control how many requests to the database an IP address can send before we firmly tell it to not (and serve an error page instead).
  • [AO3-5639] - Trying to visit an unrevealed work (and getting a helpful message instead) or accessing a hidden work (as an admin) would increase that work's hit count, potentially giving the creator of said work quite the scare. We have removed that particular source of panic now.
  • [AO3-3617] - Tags that begin with a capital letter with an accent or other diacritical mark (e.g. Éomer) wouldn't show up in the autocomplete if no fandom was entered in the posting form. Now they should!
  • [AO3-5825] - Dashboard sidebars retrieve work and bookmark counts from Elasticsearch, which ties up Elasticsearch in long queries, making everyone sad. We are now caching those counts, creating a little less work for the search engine every time a page with the sidebar is loaded. \o/ (Note: This means the count will no longer go up immediately when you add or delete a work or bookmark. The delay should currently be about half an hour, but we may adjust it in the future.)

Infrastructure

  • [AO3-5789] - Updated Database Cleaner and other test-only gems.
  • [AO3-5795] - Updated MySQL2 to 0.5.2 to support libmariadb and Debian 10.
  • [AO3-5798] - Updated Loofah from 2.2.3 to 2.3.1.
  • [AO3-5749] - Updated Elasticsearch to 6.8.5 and its gem to 6.8.0.
  • [AO3-5826] - Updated Nokogiri to 1.10.5.
  • [AO3-5797], [AO3-5800] - Updated the staging server names in our deploy script.
  • [AO3-5194] - Updated schema and structure files.
  • [AO3-5787] - We've put the code for the public site skins Reversi, Snow Blue, and Low Vision Default in our code repository for safe keeping and better tracking of changes.

Tests

  • [AO3-5788] - We had previously been using Ubuntu Xenial for tests on our CI service, but now we've switched to Bionic, which is closer to our production environment.
  • [AO3-5814] - Sometimes we make changes that we don't need our automated tests to check. We've made it so we can include a note in the commit message that will tell one of our CI services to skip running the tests and deploy the changes straight to our staging environment.
  • [AO3-5815] - The automated tests for our emails had a lot of redundancy, so we reduced that.
  • [AO3-5758] - We changed some settings on our automated code style checker to make its formatting suggestions more useful.
  • [AO3-5772] - We've stopped running automated code style checks on JavaScript files for third-party plugins, since we didn't write them and aren't going to address style violations found in them. We've also stopped checking minified JavaScript files because, seriously, we know it's one giant long line without spaces or indentation -- that's the whole point.

Comment

Post Header

Banner by caitie of a newspaper with the name and logos of the OTW and its projects on the pages

I. MILESTONES FOR FANLORE AND AO3

This month, two of the OTW's projects celebrated major milestones, as Fanlore hit 50,000 pages and AO3 turned 10 years old.

Communications made a series of posts marking the AO3's 10-year anniversary, which fell on November 14. We spoke to a number of staffers who have been with the OTW since the early days about some of the challenges they had faced, as well as about their favorite parts of working for the OTW and some of their predictions for the future. The hard work of the Translation committee meant that we were able to publish these posts in 24 languages.

A little later in the month, we were happy to see the 50,000th page published on the Fanlore wiki. The committee marked the occasion with social posts across Tumblr, Twitter and Dreamwidth as well as a post on AO3 news. Check out the post to see the special banner that the team's graphic designers created for the occasion!

Fanlore's next goal is to reach one million edits; they are already at 900,000 and climbing. If you are interested in contributing, you can find more information at Fanlore's Portal for new visitors.

II. AT THE AO3

The Accessibility, Design and Technology committee and the Systems committee have been dealing with some intermittent site slowness on the AO3 over the past few weeks. This is due to strain on the Elasticsearch servers, which became more acute under the heavy traffic of the American Thanksgiving weekend. The OTW had already been planning to purchase new servers and these have now been ordered (as of 27 November) but we ask for users' patience over the next few months until they are delivered and installed. In the meantime, we are working to upgrade the Elasticsearch software in the hope that this will at least alleviate the issue.

We'd like to thank everybody whose generous donations enabled this purchase: this is a real example of what we are able to do with the money entrusted to us by our users.

Continuing the work they began last month, our Open Doors staffers have been working hard (in collaboration with the Board of Directors and the Legal committee) to preserve as much content as possible in advance of the Yahoo Groups closure, currently scheduled for December 14. This work has included expanding archive import procedures to include procedures for importing Yahoo Groups and/or storing their contents.

The Tag Wrangling team created a new team of Chinese-speaking wranglers, who work to translate tags for the rest of the committee. They're also working to standardize these translations so that the same terms remain consistent regardless of who is working on them. That was in November; in October, the wranglers handled around 244,000 tags in more than 34,000 fandoms!

Meanwhile, Policy & Abuse handled 2,000 tickets in October and Support around 1,200 tickets.

III. ELSEWHERE AT THE OTW

A few additional updates from our other committees: the Board has been working with Legal, Systems and Finance to explore how we can push back against the recent sale of ".org" domains to a private company. Translation conducted a very successful recruitment round, receiving an unprecedented number of applications and bringing the team to a total of 236 volunteers!

Lastly, Transformative Works and Cultures is working hard on the finishing touches for their next issue, which will be published on December 15.

IV. IT’S ALL ABOUT THE PEEPS

Volunteers & Recruiting: As of 27 October the OTW has 812 volunteers. \o/ Recent personnel movements are listed below.

New Committee Chairs: Aenya, AliceJane (Policy & Abuse)
New Committee Staff: ami, BooksAreLife, Cerberusia, Haunt_Haunt_Haunt, interstitial, Mars, Seakittens & Zixin Zhang (all Policy & Abuse) and 10 other Policy & Abuse staffers, Beth Boisvert, Gillian Webster, Irina, Jen S, Megan Q, Zoë Renee (all Tag Wrangling) and 2 other Tag Wrangling staffers, Laure (Translation), Hanna White (AO3 Documentation)
New Fanlore Volunteers: Marion McGowan
New Translation Volunteers: Aqilah Norain, aruna, Beste Karataş, Bruna, Cynassa, Cypher, dxdim, Felix Engler, Joyce Zhao, Lauritz, lemoncave, Masha Yankovych, Maya Habee, Melifluo, Reptile Ruler, siobhrag, solrosan, soumyaa, Tygermine, Vincent, wildflower01, Winchester1989, Zoey and 20 other Translation volunteers

Departing Committee Staff: SarkaS (Translation), Cyn (Support), Muriel Kalliokoski (Policy & Abuse), Makari Crow (AO3 Docs), Ona Lu (Legal), Aris Gemenetzis (Fanlore), 1 AO3 Docs Staffer, 2 Communications staffers, 4 Development & Membership staffers, 1 Fanlore staffer, 1 Legal staffer, 1 Translation staffer
Departing Communications Volunteers: 2 volunteers
Departing Development & Membership Volunteers: 1 volunteer
Departing Fanlore Volunteers: 2 volunteers
Departing Tag Wrangler Volunteers: BeautifulMistake3, cest_what, Flynn Germain, Giana, Hannah Miro, Minkster, Sam Bailey and 25 other Tag Wranglers
Departing Translation Volunteers: Anya Z, SimK
Departing TWC Volunteers: 2 volunteers

For more information about the purview of our committees, please access the committee listing 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.

Comment

Post Header

Published:
2019-12-12 15:46:00 UTC
Tags:

Five Things an OTW Volunteer Said

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 Anhaita, who volunteers with the Translation Committee.

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

As a volunteer, I'm part of the Translation Committee. Our main objective is making the site and its content available in different languages for easy accessibility and understanding to all those whose first language isn't English. We help in cross lingual communications with other Committees as well! (Support and Abuse, for example).

Translation is also subdivided into smaller language teams, so no matter what language you wish to communicate in, we most likely have someone to make sure the message gets interpreted correctly. As the OTW is geared towards fans from various communities and cultures, our goal is to make sure people can access our website in languages they feel comfortable with.

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

As I'm part of a very small team (literally, it's just two of us here), we mainly have a large number of documents to sort through and translate. So usually, I spend the week translating a document, perhaps a webpage for the OTW site, like the FAQs or a News post. At times, I may get contacted to help translate a text-image, or fic-tags in my language, for a different Committee -- we are kind of the go-between here!

Translating some words into my language, Marathi, can be pretty tough, and sometimes hilarious even. We have to figure out how sentence structures have to be changed to fit a text, or the closest possible translation is used. Fun fact: Fanvid is literally translated to mean "Western Picture Gallery" in Marathi (because that's a word English totally dreamt up one day and refused to inform the other languages).

On the whole, it's a pretty relaxing workload, and is easily managed side by side with university life (with some good time management skills; seriously, if it's one thing I've learnt as a volunteer, it's that!).

What made you decide to volunteer?

I've always wanted to, I think. On some level, I wanted to give back to the community that has been there for me in little ways, throughout my formative years, providing encouragement and companionship when I needed it. And volunteering for the OTW was a way to do that, to be a part of something that allows fans to have a wholesome and positive environment to exercise their creativity in! It also allowed me to actively support the site that I'd grown so fond of!

What's the most fun thing to you about volunteering for the OTW?

The sense of community! Seriously, imagine hundreds of people with like minded interests and passion for fannish activities -- it's a wonderful feeling. Another thing I've really enjoyed is taking part in the annual International Fanworks Day celebration -- hosting games and interacting with people who've come to enjoy this site so much. It's lovely to see how this site has brought fans together!

What fannish things do you like to do?

Oh, a myriad of things! I've read, written and even beta-read many fanfictions over the years. I've taken part in and helped organise a couple of fanwork challenges, and I love browsing through the truly wonderful fan art created by artists out there!

But mainly, reading (devouring) fanfiction has become a very integral part of my life. I've officially read more fanfiction than books by now!


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

Comment

Post Header

Published:
2019-12-02 14:05:10 UTC
Tags:

Spotlight on Open Doors banner

The OTW Open Doors Committee has sent the following letter to leadership at Verizon to request that they extend the deadline for deletion of existing archives of Yahoo Groups files and messages by at least six months. This request follows Yahoo's announcement that Yahoo Groups will be permanently closing, and deleting all previously posted material on December 14, 2019. The OTW previously reported on the Yahoo Groups closure in its posts Yahoo Groups Closure - What You Can Do and Yahoo Groups Closure - What You Can Do - Part 2.

Please respectfully contact Verizon's Executive Team via email or Twitter with a link to this post requesting an extension through May 14, 2020. If you are tweeting, be certain to include news groups that have covered the Yahoo shutdown, such as CNET (@CNET), TechRadar (@TechRadar), Boing Boing (@BoingBoing), or The Telegraph (@Telegraph).

---

Dear Verizon,

We are writing regarding the impending closure of Yahoo Groups on behalf of the Organization for Transformative Works (OTW), a nonprofit organization run by and for fans to provide access to and preserve the history of fanworks and fan cultures.

Due to its unique status as a large nonprofit focused on fandom advocacy, the OTW has a major presence in fandom. The OTW is made up of over 800 volunteers from all over the world, and our best-known project, the Archive of Our Own (AO3), has over five million fanworks, two million registered users, and over 1.4 million unique visitors per month. This year, the AO3 won a Hugo Award for Best Related Work, and, along with Yahoo, was listed by Popular Mechanics as one of the 50 most important websites of all time (https://www.popularmechanics.com/culture/g29575328/most-important-websites/). Other OTW projects include Fanlore, the fandom history wiki, and Open Doors, which rescues fanworks archives that are at risk of disappearing from the Internet.

The OTW's main concern regarding the effective closure of Yahoo Groups is for its long-term impact on online fandom history and online history as a whole. Yahoo Groups was a fandom hub for more than two decades, and many of the fanworks saved there are not duplicated anywhere else, to say nothing of the conversations and other ephemera. While the OTW is primarily concerned with fandom, there are over 5 million Groups in total with countless messages and files, and hundreds of millions of people who will be affected by the loss of almost 20 years of data and history.

Open Doors and Fanlore, among other projects, are currently working hard to help preserve these works, messages, and other data, but saving everything before the time limit is simply impossible. Open Doors normally receives one or two requests each month from moderators seeking to transfer their archives to the AO3; since the announcement on October 16 that Yahoo Groups was closing, we have received over 40 requests from Yahoo Groups moderators alone.

We are using all of our official channels to inform people about the closure, as well as coordinating with other preservation projects such as YahooGeddon and the Archive Team. We are also fielding requests from members and moderators to help download and save files and messages from their Groups, and discussing the creation of a dark archive to store these downloads until more permanent methods of preservation can be found. Unfortunately, the Archive Team's automated download program has been blocked by the Yahoo Groups servers, so we are forced to do what we can by hand and are therefore extremely limited in what we can save.

Saving Yahoo Groups is going to require a great deal more time and support from Verizon. Although Verizon promised users they could download their Groups data via the Privacy Dashboard, many users are being told, "Your download request has been completed, but no data of this type is available in your account." The GetMyData sets are also incomplete, often missing files and photos. Instead, people are having to copy-paste, manually download, or utilize specialized software in order to save their Groups. To make matters worse, because Verizon has chosen to limit downloads to a few weeks, moderator and members, along with the Archive Team and Wayback Machine, are being locked out or blocked and prevented from accessing their data.

Furthermore, many Groups—especially in the EU, South America, and Asia—have not yet been informed of the Yahoo Groups closure. This is in part because Verizon has not made an official, widely posted announcement and in part because the Yahoo Groups mailing lists have been broken since 2013, with mail arriving days or weeks late, or not at all.

Therefore, Verizon needs to extend the deadline to allow time to get the word out to Yahoo Groups owners about the closure, time to fix its download request feature, and time for users to access their data. Based on the number of groups these teams' combined efforts are trying to save, the rate at which they are being saved, and the fact that many Yahoo Group moderators are still being informed of the closure, we are requesting that six months be added to Verizon's deadline, so that data from Yahoo Groups will not be deleted until May 14, 2020.

There is a long history of large websites losing information without a trace. One of Open Doors' first projects was a last-minute scramble to rescue GeoCities sites. MySpace deleting a decade of content is a recent example. This is not uncommon in new media that is not yet considered worthy of preservation, but with your assistance, Yahoo Groups can be saved from being the latest entry on a tragic list of websites that simply disappeared forever. Other tech companies have shown a callous disregard for the value of user's memories, experiences, and history, but by granting this extension, Verizon can demonstrate that it truly values its users and the important role that Yahoo Groups has played in their online lives.

Sincerely,
The Organization for Transformative Works

Comment

Post Header

Published:
2019-11-25 14:11:58 UTC
Tags:

Fanlore: 50,000 pages

Fanlore, the collaborative fandom wiki from the Organization for Transformative Works that anyone can edit, is celebrating a huge milestone: 50,000 pages! Would you like to come celebrate with us?

If you haven’t heard of Fanlore, it’s a multi-fandom, free and open wiki that was designed to be a living, evolving record of fandom’s past and present: created by fans, and maintained by fans. Like AO3, Fanlore was launched in 2008, and since then, fans have made more than 900,000 edits across more than 50,000 pages to record tropes, communities, meta, memes, fanworks, fannish perspectives and much more.

Fanlore is open for anyone to edit – all you need to do is create an account. Any edits, big or small, are welcome! You don’t need to be an expert, or have been in fandom for a long time, to contribute. The wiki wouldn’t have gotten to where it is without the dedication, perseverance and experiences of thousands of fans over the years who have added to and edited Fanlore.

Recently, Fanlore editors have been working to document hundreds of fannish Yahoo! Groups before they’re deleted in December, and last year fans took to Fanlore to document the history of fandom on Tumblr in the midst of the Tumblr NSFW Content Purge. But it isn’t just about big historical events or fandom migrations – every corner of fandom, from the Hanahaki Disease trope to A/B/O, massive fan archives to tiny niche ships, has a place on Fanlore. Try searching for your favorite character or ship! You could add something of your own to those pages.

If you’d like to edit Fanlore but aren’t sure where to start, our New Visitor Portal has a bunch of tips and links to get you started. We also have a how-to on editing pages, and a tutorial for creating new pages if you’d like to help us start down the road to 100,000 pages! Every single edit helps Fanlore preserve more of fandom’s history and experiences, and helps ensure that the amazing creativity and passion of fandoms old and new is recorded and remembered.

The Fanlore team have set our sights on one million edits next – we hope you’ll join us!

To learn more about what Fanlore’s volunteers do behind the scenes, check out our previous spotlight posts:

Comment

Post Header

Did you know you can post and browse works in over 70 languages on the Archive? In fact, AO3 is home to roughly 400,000 fanworks in languages other than English, with more posted every day! To help everyone find works in their preferred language, we've made some small changes to posting and searching.

Previously, the "Choose a language" field on the posting form was set to English by default, which made it easy to accidentally post a non-English work with the language set to English.

To fix this, we've updated the "Choose a language" field so English is no longer the default. Instead, everyone will need to select the correct language when posting a new work. If you forget, don't worry -- we've also added a friendly error message to remind you.

We've also made it a little easier to search or filter for works based on language! While we provide a "Language" field on our various search and filter forms, sometimes it's not enough -- for example, if you want works in either Spanish or Italian.

A search like that used to require knowing some numerical codes unique to the Archive. Now you can use these standard language codes with the search operators described in our cheatsheet. For example, to find works tagged with "Friendship" in either Italian or Spanish, you would enter language_id: es OR language_id: it in the "Search within results" field on the work listing for the "Friendship" tag. (The old numerical codes will continue to work, so there's no need to update bookmarks or links.)

We hope these changes will make the Archive a bit better for everyone, regardless of which languages you use for creating and consuming fanworks. And as always, if you notice a work with the wrong language, you can contact our Policy & Abuse team and they will help correct any mislabeled works.

Comment

Post Header

Published:
2019-11-15 23:54:27 UTC
Tags:

Over the last few weeks, you may have noticed a few brief periods when the Archive has been slow to load (or refusing to load at all). This is because our Elasticsearch servers are under some strain. We've made some adjustments to our server setup, but because this is our busiest time of year, we expect the problems to continue until we're able to have new servers delivered and installed in a few months.

We've been planning this server purchase for a while now, but the machines we wanted -- AMD's Epyc Rome CPUs, which have an increased core count and are cheaper than the Intel equivalent -- didn't come on the market until August. Now that they've been released, we're working on finding the best price to help us make the most of your generous donations. We expect to order them very soon.

While we're waiting for our new servers, we plan to upgrade the Elasticsearch software to see if the newer version offers any performance improvements. We hope this upgrade and the changes to our server setup will keep things from getting much worse during our end-of-year traffic influx.

Thank you for your patience, and for all the donations that allow us to buy new hardware when these situations arise!

Update 27 November: The servers have been ordered, but it will still be a few months before they are delivered and installed.

Comment

Post Header

10 Years of AO3

Michele Tepper’s contribution is the final post in our series celebrating 10 years since the launch of the Archive of Our Own. Michele was a founding member of the OTW and helped create much of AO3’s “look” in her role as head of design in the early days. Her contribution provides a nice conclusion to the series, emphasizing the importance of working together in order to make such a big project a success.

I got involved with the OTW because I knew some of the other founders already. I had designed a discussion board for Buffy fans (buffistas.org) a few years earlier, and so I had an understanding of the challenges of working with a remote team of volunteers on a project for a fan community. Also, I was working for a digital product design studio, where I saw the wave of commercialization around "user-generated content", and I liked the idea of doing something that helped keep transformative works in the hands of the creators. So I told Naomi Novik I was interested in helping out, and that's how I ended up as a founding board member for the OTW!

What I remember most about the early days of the Archive was the collaboration. Naomi, cmshaw, and I spent long hours coming up with the core functions of the archive; technologists and user experience designer collaborating to find the best solution. We built out a roadmap that saw the Archive through its earliest years, as well as an experience that people point to as exceptional, and I'm proud of that.

My favorite thing about AO3 is the tagging and the tag wranglers. I have the tag page for "feels" as a bookmark on my phone, and when I need an emotional boost, I go and look at all the different ways people have tagged for feels, all listed out and merged by the wranglers. It makes me ridiculously happy every time.

I don't pretend to know what the OTW's future will be, because I couldn't have predicted its past! Fanworks are much more accepted in the mainstream than they were 10 years ago, and the OTW and the Archive are a big part of the reason why.

So that’s all for our series from behind the scenes at the AO3. We are so appreciative of all our contributors, as well as the other volunteers who have been working hard since the OTW was founded to make the Archive a haven for fanworks of all types. We agree with Michele that fanworks and fan culture are much more widely accepted than they were 10 years ago and we are proud to think that the OTW and the AO3 have contributed to that. Cheers to 10 years of AO3!

Comment


Pages Navigation