We’ve had some exciting days over at the Archive and are slowly recovering from a search index malfunction, which forced us to disable filtering & sorting for a while.
We talk about our search engine a little more in the second half of this news post about recent site issues. It’s basically an extra layer of organization between our database and the search results or work listings you see. We built in a fail-safe when we added this layer, so in the event of an interesting crash we can turn off filtering and just access the database directly. That’s what we’re currently doing for bookmarks, but it means all the fancy sorting options are unavailable.
We’re rebuilding the bookmark index right now (well, the server is), which is a staggering amount of data and will take a few more days. When the index is complete, we will turn on filtering again. Please keep an eye on our Twitter account @AO3_Status for the newest developments!
While emergency fixes are ongoing, we’ve also been looking into possible causes for these issues, and have tweaked some server settings. Things should now be stable again. In the long term, we will have to make changes to how our database handles bookmarks, and spend some quality time on optimizing our search engine back-end. As all things, this will take a while, as we’re also looking at a backlog of smaller bug fixes and some crucial features we have to add and tweak before we can launch the big 1.0 (see also our Roadmap).
We can only ask for your patience as we continue to work on the site, even if things seem to be moving slowly sometimes. Many thanks to everyone who’s sent kind messages of encouragement via Twitter, Tumblr, or our Support form. It’s really appreciated. :-)
If you’re sad or upset that AO3 is down right now, I totally get that. I’m sad too.
Can I take you on a little trip through the internet to the other side?
The Archive is partly down /o\ and we’re working on it. \o/
Please consider reading the above post if you feel like making an angry post on Tumblr or Twitter about the outage, and know we’re just as keen as you are on keeping our servers happy and stable (if not keener). Many apologies for the hassle!
Why does wattpad have its own app but archive doesn’t?
There’s actually a good reason for this! The long, official explanation is on the AO3 Tumblr, but the short and totally unofficial version is it’s a lot of work, since it’s not just designing and coding one app (which is a significant project on its own), but creating the API that lets the app interact with the Archive’s data, and then making separate apps for each platform (e.g. Android, iOS) we want to support.
Wattpad’s in a better position to get this work done simply because they have full-time, paid coders: Wattpad’s About Us page says the have over 30 people on their team, although it doesn’t say exactly how many of those people are developers. Meanwhile, the Archive of Our Own has about a dozen regular contributors, and we’re all unpaid volunteers, so we can only work on the Archive in our free time.
So it’s not a case of the Archive not wanting to have an app — it’s something we get asked about frequently, and we feel bad when our users are unhappy — but with our limited resources, we have to prioritize. For now, we’re focusing on features and bug fixes for the site, since the awesomeness of any future AO3 apps depends heavily on having our major features not only working, but working well.
Reblogging this for any interested newcomers, hi. :-)
If you’d like to read more about the time and money usually involved in creating an iPhone/iPad app and don’t mind some jargon-y programming talk, there’s a relevant thread on Stack Overflow. (It’s a bit like Google + Wikipedia for programmers, with points for helpful answers.)
Reminder that you can chat with Open Doors about the Stargatefan import into AO3 on Nov 23 20:00 UTC: http://bit.ly/1bXunxf
The Open Doors people are awesome and this is a super belated reblog. Chat is going on right now and will be going for another two hours. Feel free to hop in for fannish chit-chat or import-related questions!
Hey folks, very unofficial post here from an Agents of SHIELD wrangler on AO3. I’ve noticed some confusion in the relationship tags and just wanted to make sure shippers have the full info on how the relationship tags are set up there.
On AO3, a ship can only have one tag. But some of you have noticed that there’s an & version and a / version of some ships. Good catch! That & is for platonic ships, like BroTPs, friends, family-style relationships, that sort of thing. Gen stuff.
If you’re tagging a ship that’s romantic or sexual (even if they’re also friends, which we hope they are, because everyone on this Bus is adorable!), other fans who prefer BroTPs would probably really appreciate it if you stuck to the / version of the ship only, and didn’t use the & version. Otherwise, surprise romance in their BroTP! Not exactly something everyone wants to find.
In short: / = OTP, Romance, Sex! & = Friends, Family, Teammates, Bros! (and whatever other platonic relationships your work focuses on)
So for an example, SkyeWard fans! If you’re posting a work about Skye and Ward awkwardly flirting that also has Fitz and Ward hanging out and doing friend stuff, you’ll get the most happy readers by tagging like this:
Skye/Grant Ward, Leo Fitz & Grant Ward
That way, SkyeWard OTPers and FitzWard BroTPers will find your work. People who prefer Skye & Ward as friends or FitzWard as sexy/romantic won’t.
More info here in the Tag FAQ.