Why is the AO3 Year in Review Not Working?
If you’re having trouble with AO3’s Year in Review, there are several things you can try. AO3’s year-in-review data collection isn’t an official account. It merely gathers data that has been made publicly accessible. If you’re still having trouble, you can check the wiki’s FAQ for possible causes and solutions. In addition, you can contact the AO3 administration if you’re experiencing problems.
AO3’s abuse policies don’t mention race
In an article on AO3’s abuse policy, the site’s creators explain that they “reject racist or bigoted content and behavior.” While they acknowledge that the site’s policy does not mention race, they are unsure how to enforce it. Many people would like to see more comprehensive policies to ensure that abuse doesn’t lead to harassment or expulsion. They’ve also asked for a warning system for racially offensive content, like dehumanizing fic and casual racism.
While the site has historically been permissive towards abusive content, the recent controversies about a fic have caused a stir. It’s unclear what exactly triggered this uproar, but the author has promised to return with a vengeance. In the meantime, there’s nothing to be done to fix the problem. Here’s what the site has done. In a recent meta essay, stopthatimp discussed the issue of hateful fanfiction and the AO3’s abuse policies.
AO3’s tagging system is limited
The tagging system in AO3 is relatively limited. While tags are supposed to indicate what kind of content is being added, they can be confusing at times. There is a way to simplify the tagging process. AO3’s tags are pre-populated. This means that you don’t have to manually add tags when you create an article. Instead, you can use an autocomplete menu or a small drop down menu to create a list of suggested tags.
Currently, user tagging is not limited to tags that AO3 has approved. It would require a wrangler to create new tags for users, and this would require a tremendous amount of time. In fandoms such as Homestuck, five new relationships could be created each day, and wranglers would have to work quickly to approve and post these tags. Another option is to add a way to prioritize tag requests.
A similar problem exists in the tagging system of AO3. The site’s abuse policy FAQ does not mention race. This is unfortunate because many AO3 users would want to avoid engaging with racist writers. It would be useful to have some way to notify readers that a story is racially charged or has other content that could be offensive. In addition to warning readers about racially charged content, this feature would allow authors to avoid engaging in debates on AO3.
AO3’s open source code isn’t fully functional
AO3 is run on open source code and is programmed by volunteers using Ruby on Rails. Its developers allow users to submit feature requests via a Jira dash board. The website boasts over 700 volunteers and three volunteer committees that are responsible for various aspects of the site. Those committees include Communications, Documentation, and Policy & Abuse. You can contribute to these groups and help the project run smoothly.
One of the major concerns about AO3 is that it won’t be able to run in the Apple App Store due to its strict NSFW content rules. If the Apple App Store bans AO3 because of its content, it will push it to the purge. The same issue can be applied to Tumblr, which recently banned NSFW content. Those problems may make AO3’s open source code unusable in the future.