AO3 News

Post Header

Daire’s Fanfic Refuge header

HL Raven’s Nest header

Two Highlander fanfiction archives, Daire's Fanfic Refuge and HL Raven's Nest, are being imported to the Archive of Our Own (AO3).

In this post:

Background explanation

Daire's Fanfic Refuge and HL Raven's Nest were Highlander fanfic archives that were started in 1997 and 1998 respectively. Their moderator, Daire, decided to move their stories to a more long-term home: AO3!

Open Doors will be working with Daire to import Daire's Fanfic Refuge and HL Raven's Nest into separate, searchable collections on the Archive of Our Own. Eventually the links going to the old site will redirect to the collection on AO3 so the works can continue to be found with their old URLs.

We will begin importing works from Daire's Fanfic Refuge and HL Raven's Nest to the AO3 after May 2017.

What does this mean for creators who had work(s) on Daire's Fanfic Refuge or HL Raven's Nest?

We will send an import notification to the e-mail 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 invite 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. Open Doors will then set up the URL redirects, and we will permanently close down the site.

Please contact Open Doors with your Daire's Fanfic Refuge or HL Raven's Nest pseud(s) and e-mail 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 archives
  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.
  5. You are happy for us to preserve your works on the AO3, but would like us to remove your name.
  6. If 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've posted the works elsewhere, or have an easy way to verify that they're yours, that's great. If you don't, we will work with the moderator 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, contact the Open Doors committee, or leave a comment on this post and we'll respond as soon as we can.

We'd also love it if fans could help us preserve the stories of Daire's Fanfic Refuge and HL Raven's Nest 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 Daire's Fanfic Refuge and HL Raven's Nest!

- The Open Doors team and Daire

Comment

Post Header

Published:
2017-05-16 03:30:02 -0400
Tags:

In this big batch of bug fixes and enhancements, we sorted out several issues with collaboration on chaptered works, reduced errors when trying to download works, took another small step toward sitewide https support, and kept making improvements to our automated tests.

Credits

  • Coders: Cesy, cosette, cresenne, james_, redsummernight, Sarken, ticking instant
  • Code reviewers: Ariana, bingeling, james_, Sarken
  • Testers: Alison Watson, james_, Lady Oscar, mumble, Sammie, Sarken, Stephanie Godden

Details

Enhancements

  • [AO3-4847] - To help users who are receiving abusive comments, Abuse staff can now find a commenter's IP address without having to ask for a database admin's help.
  • [AO3-4999] - It is now easier to manage co-creators you collaborated with on chaptered works. When adding or editing a chapter, a list of checkboxes will suggest users who are already co-creators on another chapter. For works without any previous co-creators, you can still add users in the "Add co-creators?" autocomplete field. (This also fixes the previous behavior, where a co-creator on any chapter was getting added to the whole work.)
  • [AO3-3359] - We've added a Search button to the top of the Work Search form, so you don't have to scroll all the way down if you're only using a few options on the top half of the page.
  • [AO3-4885] - Challenge assignment emails can now be translated (for when we introduce that functionality).

Work Bug Fixes

  • [AO3-4943] - Users kept running into error 500s when trying to download works. /o\ This deploy should fix several common causes for these errors: hyphens in work titles, a deleted parent work (i.e. the inspiration for a remix, or the original of a translation), or a deleted series that included the work. Fingers crossed!
  • [AO3-4986] - We discovered that it was theoretically possible to add yourself as a co-creator to a work you did not actually co-create. We fixed this as soon as our coders found it, and we have no reports of it being exploited, or any reason to believe that it was.
  • [AO3-3176] - If you were listed as the co-creator of a work and you tried to edit a chapter you were not explicitly listed on, you'd get a 500 error. Now you can edit it successfully.
  • [AO3-3733] - Orphaning a co-created work would add the orphan_account as a creator to every chapter, even if the orphaning user was not a co-creator on the entire work. We've now added a check to only display the orphan_account on the appropriate chapters.
  • [AO3-4174] - The same would happen for works in an orphaned series, where the orphan_account would suddenly be attached to all works. Fixed that too!
  • [AO3-4963] - After a change we made to speed up the posting process behind the scenes, new fandom tags on works showed up on the wrangling interface as intended, but fandom tags on bookmarks of external works did not. Oops! We made sure all new fandom tags are treated equally now.
  • [AO3-4105] - It used to be possible to completely delete a series (not the works in it!) when editing a single work in that series. We decided that this was maybe a little weird and removed the "Delete" button from that part of the interface.

Other Bug Fixes

  • [AO3-4712] - Trying to filter collections by fandom would lead to an error 500. Now it actually produces a list of collections containing works for that fandom.
  • [AO3-4985] - While the buttons to mark or unmark a comment as spam are hidden from everyone but site admins and the work's creators, it was theoretically possible to access those actions while logged out. We have now put in the appropriate checks.
  • [AO3-4718] - In a similar vein, if they had the direct link to a tag comment, logged out users could potentially see replies to and also cancel the edits on that tag comment (not comments on works!). Now they'll see the appropriate error message if they try.
  • [AO3-4956] - The redirect tool Open Doors uses to manage imported works would throw up an error 404 when being presented with a faulty URL. Now it responds with a much friendlier error message. We also extended test coverage for this feature!
  • [AO3-4407] - To keep spammers at bay, the feature that lets you request invites to friends has been disabled for a while now. We've finally adjusted the code for the front page copy to correctly reflect your options in getting an AO3 account.
  • [AO3-4621] - User icons, which we're storing on AWS servers, will now be fetched over https, making it less likely that you will get a mixed security warnings message on a page.
  • [AO3-4863] - The message you'd get when trying to access the Reindex Work action without being logged in as an admin or tag wrangler was a friendly blue instead of the appropriately dangerous red. It will flash the right color at you now.

Automated Tests

  • [AO3-4997] - In a previous deploy, we made it possible to test JavaScript features with our automated Cucumber tests. This fix brings back scenarios that were commented out when we were still grappling with JavaScript testing.
  • [AO3-4993] - We used to test URL caching with Cucumber tests. What were we thinking! Now we're using the RSpec framework for this, like normal.
  • [AO3-4992] - To start each automated test with a blank slate, we've added a little clean-up step before each test is run. Previously, that step only applied to tests of the autocomplete functionality.
  • [AO3-4990] - We've added some coverage for easy-to-test parts of various models.
  • [AO3-4982] - The service we use for our continuous integration needs, Travis CI, upgraded their operating system. We made sure we're still compatible.
  • [AO3-4981] - We added an automated test for invitation emails.
  • [AO3-4714] - We also extended coverage for the series feature.
  • [AO3-5004] - And we've added a test for work URL detection in abuse reports.
  • [AO3-4733] - The test for the public Wrangling Guidelines has been updated (and the related code received a small correction).
  • [AO3-5003] - The RSpec test for the reindexing button available to admins was broken, and we fixed it.
  • [AO3-5010] - The bookmark search test was very short and used fixtures. It is now longer (in this case, that does mean better), and uses factories instead.
  • [AO3-5014] - We now use the same factories for unit and feature tests. If this means anything to you and you have some free time on your hands, shoot us a message and join the team!

Code Clean-Up

  • [AO3-4942] - The code for viewing and editing locales on the Archive included some unused cruft. Now it's all neat and tidy. (Or neater and tidier, anyway.)
  • [AO3-4480] - We've added caching to the redirect code for imported works and made sure the cache gets updated when a work is deleted.
  • [AO3-4978] - Cleaned up duplicate definitions.
  • [AO3-5009] - We had a /docs folder that hadn't been used for anything in years. It sleeps with the fishes now.

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2017-05-14 14:15:17 -0400
Tags:

5 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 Rebecca Sentance, who volunteers as chair of the AO3 Documentation Committee.

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

I'm a co-chair with the AO3 Documentation committee, also known as "Docs", which handles the user-facing documentation for Archive of Our Own -- things like FAQs, tutorials and screencasts. You can find our work over on the Archive FAQ page. Our job is to make sure that there's clear and accessible documentation explaining the different functions of the Archive, which users can consult if they run into any issues.

For this we work closely with the Support Committee, making sure that our docs address the user queries that they're getting; Accessibility, Design & Technology, to take interface changes and feature updates into account; and Translation, who make our documentation available in all sorts of languages.

I also wear another hat which is as a layout editor for the Transformative Works and Cultures academic journal, where I'm responsible for HTML tagging articles for publication in each issue. I've learned a lot about the world of academic HTML in the process!

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

Every week is a little bit different. I do the bulk of my work for Docs at the weekends, so during the week I'll take care of smaller tasks like replying to and resolving comments on documents I'm betaing, checking in with the newer members of Docs that I'm mentoring in my capacity as chair, and looking over documents on "Free For All" -- that's the last internal beta stage our documents go through, where everyone in the committee goes over them with a fine-tooth comb and provides feedback.

Then every Saturday, Docs chairs will have a meeting to touch base and discuss anything that needs our attention. There are three of us, based in Australia, the UK (me!) and Canada respectively, so finding a time of day that works for all of us is a fun task! On the plus side, it means one of us is always awake and available if we're needed. We also have committee-wide meetings about once every two months.

At weekends I'll sit down to do more in-depth beta and drafting work. Drafting is the process of creating a document from scratch, after which it passes through five beta rounds which focus on different areas: Testing, Accessibility & Internationalisation, Coherency & Consistency, Readability and SPAG (Spelling, Punctuation and Grammar). From there a doc moves into Free-For-All, and finally into External beta where other committees will take a look and provide feedback. My favourite beta stage is Testing, because I'm a hands-on sort of person, and I like to poke about with the Archive and find out what works and what doesn't!

What was your path to becoming chair of AO3 Docs?

Haha, to be honest, it was a path I hadn't even realised I was on at the time. Right from when I joined the committee, I was interested in training to be a chair someday, but imagined it would be a long way down the line. But I was proactive in volunteering to help with any admin tasks that needed doing, attending committee meetings (I love meetings), and offering my opinion on issues to do with the committee's direction and future. I was also keen to get involved with the wider OTW, which is a plus point for a prospective chair.

This must have caught the eye of our incumbent chairs, because eight months after I joined Docs I was approached about training to become a chair, and I delightedly said yes. That was in April of last year, so from then on I became a "chair-track trainee" (as we like to call it) and carried out hands-on training with my fellow chairs, Sammie and Claire, and in January of this year I was officially "chaired up" to the level of a full Docs co-chair. However, I still consider myself a "junior chair" and there's always more for me to learn.


2 new and 2 revised docs in 2014; 4 revised and 6 new docs in 2015; 5 revised and 1 new doc in 2016

User-facing documentation uploaded to the Archive between 2014 and 2016 by the AO3 Docs team. The Docs team is responsible for creating and editing help documentation in multiple formats, from text-based FAQs and tutorials to video tutorials, or 'screencasts'. Revised refers to existing docs that were rewritten or amalgamated, and New refers to brand new docs that were created from scratch. Statistics start midway through 2014.


What do you enjoy the most about your work?

The best thing about being a chair in an OTW committee - and about being part of the OTW as a whole - is the feeling of doing something tangible to give back to the fannish community. That was the reason I applied to join Docs in the first place, and the reason that I pour so much of my time and energy into the OTW.

Docs is also the perfect committee for me because I'm a writer and editor in my day job, and I get a lot of joy out of tinkering with language and helping to improve the way something is communicated. The Docs committee is a haven for word nerds, and we have members who love to delve into the intricacies of spelling and grammar or spend ages debating the perfect wording for a single sentence. I used to be a beta reader for fanfiction, which I got into because I love to edit and help improve the quality of someone's writing. Docs work is really similar, but with a bigger team -- and we're in the business of creating as well as editing.

Plus, I get a kick out of knowing that the documentation that we create is the same documentation that countless Archive users refer to whenever they have a problem, or want to learn about a feature. So we contribute directly to helping people use the Archive -- which is a big responsibility but also very cool.

What fannish things do you like to do?

I've been an avid reader and writer of fanfic ever since I was a teenager (well, there were also a few fanfics I wrote at a younger age before I discovered the wider online fanfic community, but we won't talk about those...), and fandom has always been a big part of how I spend my free time. I started out reading fanfic on Quizilla, which was written as a second-person narrative with occasional responses to choose from, sort of like a fanfic choose-your-own-adventure. From there I progressed to Fanfiction.net, LiveJournal and AO3. My early fannish experiences were mainly in anime fandoms and Harry Potter, but I've since dabbled in all sorts of fandoms from The Road to El Dorado to Pirates of the Caribbean, Marvel Cinematic Universe and Inception.

In the past I've written some journalistic articles about fandom and fanworks for Paper Droids, an online magazine for geeky ladies. I also love to read about fandom, and record my fannish recollections over on Fanlore.


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.

Comment

Post Header

Published:
2017-05-10 12:44:40 -0400
Tags:

OTW Recruitment Banner by Erin

Are you fluent in a language other than English, or have experience with research methods, problem solving or nonprofit governance?

We would like to thank everyone who responded to our previous call for Tag Wrangling Volunteers, Elections Staff, and Volunteers & Recruiting Staff.

Today, we're excited to announce the opening of applications for:


  • Strategic Planning Staff - closing Wednesday 17 May 23:59 UTC


  • Translation Volunteers - closing Wednesday 17 May 23:59 UTC

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

All applications generate a confirmation page and an auto-reply to your e-mail address. We encourage you to read the confirmation page and to whitelist volunteers -(at)- transformativeworks -(dot)- org 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.

Strategic Planning Staff

The Strategic Planning Committee is recruiting for new staff members! We are a close-knit and collaborative committee of people who are tasked with researching, developing, and supporting the implementation of the strategic plan. We are looking for organized people well-versed in problem-solving and research methods, with knowledge of or a background in nonprofit governance. A strong background in informational interviewing is a plus, but not a requirement. We welcome all perspectives and are actively interested in people with diverse views on fandom and the OTW!

Applications are due Wednesday 17 May 23:59 UTC

Translation Volunteers

If you enjoy working collaboratively, if you're fluent in a language other than English, if you’re passionate about the OTW and its projects, and want to help us reach more fans all around the world, working with Translation might be for you! Translation volunteers help make the OTW and its projects accessible to a wider global audience. We work on translating content by the OTW and its projects from English to other languages, such as site pages, news posts, AO3 FAQs and AO3 Support emails. (However, we do not translate fanworks.)

We really need volunteers who speak Arabic, Bengali, Croatian, Japanese, Kiswahili, Korean, Latvian, Malay, Marathi, Romanian, Serbian, Turkish, Vietnamese and Welsh—but help with other languages would be much appreciated.

(Please note that our Chinese, Czech, Dutch, Finnish, French, German, Indonesian, Italian, Polish, Brazilian Portuguese, European Portuguese, Russian, Spanish and Swedish teams are not accepting new members at this time.)

Applicants may be asked to translate and correct short text samples and will be invited to a chatroom interview as part of the selection process.

More information about us can be found on the Translation committee page.

Applications are due Wednesday 17 May 23:59 UTC

Read more and apply at the Organization for Transformative Works' Volunteering page!

Comment

Post Header

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

I. Membership Drive Success and April Showers

Thank you to everyone who helped make our recent OTW Membership Drive a rousing success! We raised US$146,595.80 from 5,660 donors in 73 countries. Whether you donated or helped spread the word about the drive, your support means the world to us. You can see how your donations will be put to use in our budget post.

Thanks to Development & Membership, Communications, Translation, and everyone else who worked hard on this drive.

Fanlore was also busy hosting the month-long April Showers celebration. The event was to encourage people to contribute their own stories and experiences to Fanlore, especially those from smaller fandoms. Kudos to everyone who created or expanded an article this month. You can learn more about April Showers at Fanlore's Dreamwidth community or new Tumblr account.

II. At the AO3

The Archive of Our Own hit a major milestone in April: 3 million fanworks! To celebrate, we're asking to hear from you, our users. It's the people who make AO3 what it is, so tell us your #myAO3 story about what the Archive means to you and help spread the squee.

Also during April, Accessibility, Design & Technology deployed three batches of fixes, which were summed up in the most recent Release Notes. They also had some extra fun when the database that holds everyone's AO3 History ran out of numbers.

While the aim is always to fix urgent bugs and take care of performance issues that make AO3 unstable, the focus has been on backend upgrades for several months now, and progress has been made. The first step towards running the latest version of Ruby on Rails was completed (converting all our code to work with strong parameters, for the curious). \o/ Also, the contractor started the actual Rails upgrade process, which will happen in several steps to get us from Rails 3.2 to Rails 5.

Tag Wrangling made minor updates to the wrangling guidelines. These updates included changes to when (Character) is used as a disambiguation, as well as a project to un-subtag show-specific RPF fandoms from the RPF fandoms for specific countries. Since many actors work in shows from many different places, it was leading to confusion, so show-specific RPF fandoms are now subtagged directly to Actor RPF.

The implementation of some earlier guideline updates was also completed to standardize the treatment of fusion settings in the Alternate Universe tag tree, which involved the removal of a few character-specific tags that didn’t really belong in the Alternate Universe tree.

Lastly, Support received over 770 tickets, and Abuse received roughly 600.

III. Legal Advocacy and Scholarly Fandom

In the tail-end of March, Legal filed a comment with the U.S. Copyright Office, responding to a Copyright Office inquiry asking whether the U.S. should adopt additional “moral rights” laws requiring that authors be identified in connection with their works (known as a right of “attribution”) and requiring an author’s permission to make changes to copyrighted works (known as a right of “integrity”). In their comment, they argued that a right of integrity would harm free expression, and that while in general attribution norms are often beneficial and common within fan communities, they should not be given the force of law.

In April, together with our allies in the Re:Create Coalition, Legal sent letters to the U.S. House, Senate, and Executive Branch advocating for balanced copyright laws. The letter laid out a set of key values to help guide copyright policy, including the value of free expression. “We support the Constitutional promise that all people should be able to express themselves freely and believe that such expression includes fair use of works created by others, as protected by the Copyright Act and the courts. Overly-burdensome copyright laws stifle free speech, expression and the diffusion of knowledge in society."

Are you interested in meta about fanfiction? Transformative Works and Cultures staffer Francesca Coppa recently published a new book, The Fanfiction Reader, and all royalties are being donated to the OTW! So if you'd like to read some fanworks and writing about those fanworks, check out the link or let interested friends know it's available.

IV. GOVERNANCE

Elections announced the 2017 election timeline this month. This year's election will be held August 11-14. The membership deadline for being eligible to vote is June 30. Candidates running for the Board of Directors will be announced on June 21. Check out Elections' Twitter and Tumblr for updates throughout the election season.

V. IT’S ALL ABOUT THE PEEPS

As of the 30th of April, the OTW has 604 volunteers. \o/ Recent personnel movements are listed below.

New Committee Staff: pyrrhical (Fanlore), 1 Fanlore Staff, capitola (Tag Wrangling), Stephanie Godden (Elections), JessicaLovesSocks2658 (Abuse), Jonny H. (Abuse), 8 Abuse staff, adustyspectacle (Tag Wrangling), Solovei (Tag Wrangling), rachelisce (Tag Wrangling), 1 Translation, 1 Tag Wrangling
New Fanlore Gardener Volunteers: SavannahM, 1 other
New Translator Volunteers: Silarona

Departing Committee Staff: Cat Goodfellow (Communications), Patrycja Zarzecka (Elections), Sofia (Abuse), Aline Carrão (Translation), 1 Tag Wrangling, 3 Abuse
Departing AD&T Coder Volunteers: alicefung & 1 Other
Departing Communications Volunteers: doughtier
Departing Tag Wrangler Volunteers: Cadkitten and 5 others
Departing Translator Volunteers: XxArt, Chloë C, Quincette, 1 other

For more information about the purview of our committees, please access the committee listing on our website.

Comment

Post Header

Death-Marked Love site banner

Death-Marked Love, a Buffy the Vampire Slayer fanfiction archive, is being imported to the Archive of Our Own - AO3.

In this post:

Background explanation

Death-Marked Love was a prominent Buffy/Spike website which was active from 2001-2007 and hosted a lot of fanfiction which was published during this era. Until recently the website was being privately hosted but was, unfortunately, shut down without notice. In order to preserve the stories which were hosted there, a lot of which cannot be found elsewhere, the decision has been made to migrate all the hosted fiction onto AO3.

Open Doors will be working with the moderator, Hils, to import the Death-Marked Love archive into a separate, searchable collection on the Archive of Our Own.

We will begin importing works from Death-Marked Love to the AO3 after May 2017.

What does this mean for creators who had work(s) on Death-Marked Love?

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 invite 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 Death-Marked Love 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.
  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 Death-Marked Love 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 Death-Marked Love 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, contact the Open Doors committee.

We'd also love it if fans could help us preserve the story of Death-Marked Love 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 Death-Marked Love!

- The Open Doors team and Hils

Comment

Post Header

Published:
2017-04-28 10:09:12 -0400
Tags:

AO3 3 million fanworks

Partial screenshot of the AO3 homepage showing 3 million fanworks

The Archive of Our Own is thrilled to announce that it is now home to 3 million fanworks! This amazing accomplishment could not have happened without the support and engagement of you, our incredible users.

A bit of history about the Archive:

  • The idea for a fan-owned archive was first suggested in May 2007
  • The Archive of Our Own went into closed beta almost a year and a half later, in October 2008
  • A little over a year after that, in November 2009, AO3 entered open beta, where anyone could request an invitation and make an account
  • Before open beta, there were 347 user accounts and 6598 fanworks from 674 fandoms
  • Two days after open beta started, there were 1076 user accounts and 9506 fanworks from 886 fandoms
  • The millionth fanwork was posted to AO3 on February 15, 2014, just under four and a half years after going into open beta
  • The two millionth fanwork was posted to AO3 on December 20, 2015, less than two years after reaching one million fanworks

And now, less than a year and a half after reaching 2 million fanworks, we're celebrating 3 million! The past decade has been an incredible journey, and the AO3 has grown more than we ever could have hoped back when it first started.

Help Us Celebrate

It's the people who make the Archive of Our Own what it is. Our more than 1 million registered users--and countless unregistered users--are some of the most enthusiastic and passionate folks around, giving so much of themselves in the works, comments, and kudos that they share. So we want to hear your stories. What does AO3 mean to you?

You can share your answer in a word. You can share it in an essay. In a drawing. A song. However you want to celebrate your experience, we want to know about it. Leave a comment or use the hashtag #myAO3 on social media so we can hear what you have to say.

Three million thank yous to everyone who helped the Archive get to where it is today!

Comment

Post Header

OTW April 2017 Membership Drive

Thank you for supporting the OTW! Our April 2017 drive has come to a close, and we have raised over US$145,000 from over 5,600 individual donations representing 72 countries. Over 3,040 of these donations came from first-time donors.

This week, we updated you on exciting developments in several OTW projects. We also told you about additional ways you can donate: corporate matching to amplify your impact, and recurring donations to get that amazing thank you gift you'll love!

We would like to recognize all the OTW volunteers working behind the scenes to make this drive, and everything we do, possible. This drive couldn't have been successful without them, or without you. Once again, thank you for your generosity and support as we continue to grow as an organization.

(Although the drive has ended, your donations are accepted at any time.)

Comment


Pages Navigation