AO3 Blocking and Muting

Blocking and Muting are a set of software improvements for the Archive of Our Own. As of February 2023, both features are now available on the archive, but future adjustments are still being planned.
==Current and Proposed Functionality==
In 2021, the OTW laid out its plan to develop features giving users "the ability to block other users from interacting with you, or hide content by users you specify". The functionality would be split into two sets of features: "blocking" would prevent the blocked user from interacting with you, and "muting" would hide archive content or users you don't want to see., 2021-04-01. Accessed 26 June 2022.
As of June 2022, fan creators can now block specific (logged-in) users from commenting on their works or replying to their comments elsewhere on the site. The announcement indicated that more functionality would be added to the block button in the future.
Visible IDs were also added to AO3 user accounts; the plan was to use the IDs for the archive's native muting feature, but in the meantime allow users to create site skins to hide users, works, series, or external works. 
As of February 2023, the muting feature is live and allows logged-in users to hide content they see from other logged-in users, including: a muted user's bookmarks, other users' bookmarks of the muted user's works, the muted user's comments, and all works where the muted user is listed as a creator in search results and tag lists., AO3 News, 2023-02-06.
==Planned Feature?==
In May 2007, Astolat's original post proposing the idea that became AO3 included brainstorming the features needed; one she mentioned was a feature "allowing users to leave comments with the poster able to delete and ban particular users/IPs but not edit comment content (ie, lj style)". 
However, banning users from commenting was not implemented in the archive's software for many years, and for a long time the committee in charge allegedly believed that it was not worth doing. A public road map was posted in 2010 and revised in 2013; blocking or muting users or works was not mentioned in either road map.
A 2012 FAQ for new users from fanfiction.net provides clues to site philosophy at a time when the invite queue was overwhelmed and site admins were discovering their code wasn't scalable. The FAQ noted that users could not turn off anonymous comments: "For several reasons, including avoiding the exclusion of users who have not yet been able to get an invite, this is not a preference we offer to authors." Among the 90 comments, no one mentioned this was a problem., 2012-06-21. Accessed 24 July 2022. (However, this decision was reversed the following year.)
Gossip about the status of the block feature was shared on fail_fandomanon several times. In 2015:
As of October 2016, someone quoted an OTW communication (AO3 Support email? no date given):
Meanwhile, in 2014 the official AO3 News tumblr posted an answer to the question "Is there a way to block a user? At the very least prevent their stories from showing up when browsing?":
In 2016 a user asked about a blocking function, and a volunteer replied, "I know that's on the radar, but it isn't part of this proposed change. If you haven't already let Support know that you desire this as a feature, please do, because we do track interest in features.", 20 May 2016. 
In a June 2020 statement on racism and the archive the OTW indicated that they were already considering a blocking feature.
In a 2023 fail_fandomanon discussion about the 2022 CSEM attack against the OTW, former PAC volunteer azarias reported that Board member "Danielle Strong was calling requests for a block function to curb harassment 'whining about unimportant distractions' right up until the Board was forced to promise it in June 2020.", fail_fandomanon, 2023-05-28.
==Development Timeline==
===2020===
*June 24: An OTW statement made in response to recent racism discussions includes a promise to "continue our design work on additional features like user muting and blocking"., 2020-06-24.
===2021===
*February 4: AO3 Support responds to a question on the AO3 News post about comment freezing with an update on the status of the blocking feature: "The ability to block a specific user from interacting with you is a planned feature that we have been actively working on developing for the past few months. However, since it is a complex feature that will affect multiple parts of the site, we can't give a specific timeline for when it will be implemented. We will be publishing a news post in the next few weeks which will give a general update on this topic and our progress.", 4 February 2021. Accessed 29 June 2022.
*February 16: AO3-6131: Add user and work IDs to work blurbs to allow muting or highlighting - project ticket created
*February 16: AO3-6132: Add user IDs to series blurbs - project ticket created
*March 14: At the open session of the OTW Board meeting, someone asks for an update on when the blocking feature update would be posted. Answer from the meeting minutes: "At the moment we don’t have an exact date for you but it’s in the process of being finalised and translated". Accessed 29 June 2022.
*March 16: Ticket to add user and work IDs to work blurbs is deployed. Includes the display of the user ID on the user profile page.
*April 1: The OTW posts an official announcement: An update on blocking and muting 
===2022===
*January 6: Ticket to add user IDs to series blurbs is deployed.
*April 7: AO3-6323: Add user ID to comments - project ticket created
*April 10: AO3-6325: Add user ID to bookmarks - project ticket created 
*April 11: AO3-6327: Allow users to block other users from commenting - project ticket created
*June 5: The OTW posts an official announcement: Comment blocking is coming
*June 10: Comment blocking feature goes live.
*July 9: AO3-6365: Add interface for muting users via CSS - project ticket created
===2023===
*February 6: The OTW posts an official announcement: Introducing the ability to mute users
*February 8: The mute button is live.
*April 4: AO3-6502: Blocked users should not be able to give gift works to blocker - project ticket created
*April 19: AO3-6517: Prevent blocked users from leaving kudos on blocker's work - project ticket created
*June 16: Blocked users are no longer able to leave kudos on blocker's work.
===2024===
*April 1: Blocked users can no longer gift works to blocker.
==Fan Discussions==
===Early Discussions and Growing Harassment===
Fans were discussing the need for blocking or muting for many years before AO3 features were developed.
In a November 2014 fail_fandomanon thread titled "Features you'd add to AO3", several fans listed blocking, although some of the functionality they desired ("Certain authors certain pairings certain tags") is closer to the muting feature. In a January 2015 fail_fandomanon thread titled "AO3 wish list", several fans asked for the ability to block other users from commenting.
In 2016 a reddit user asked the AO3 subreddit, "Is it Possible to Block Personally Objectionable Content Through Preferences?", 22 November 2016. A few comments on a 2017 r/fanfiction post mentioned blacklisting or blocking content on AO3 in answer to the question "What would you change about fanfiction sites?", 18 June 2017.
On Twitter, calls for the ability to block users, fanworks, or tags can be found dating back to 2012, tweet by smolcomfort, 28 April 2012., tweet by simplyn2deep, Sep 4, 2013., but the frequency of tweets on blocking users increased starting in 2015-2016., twitter search, 6 July 2022., twitter search, 6 July 2022.
As the site grew, so did harassment. Many, many fans have complained about harassment and AO3's failure to address it. In particular, fans of color have described experiencing racist harassmentFor example, the interracial kink Hockey fic posted in 2014 where the author then used racial slurs to describe the RPF characters in reply to comments from concerned readers. Because the slurs were not directed at specific users, the AO3 Abuse team decided that the author's actions did not constitute harassment. Many fans disagreed with this judgment. the prompt that inspired the fic, the fic itself, hockeyrpfanon thread, stopthatimp 2014 post, post from themardia, AO3 & Censorship by stopthatimp in 2016. 2014 twitter discussion. 2021 tweet.A 2021 example of receiving racist comments, shared on reddit: , 24 August 2021., tweet by LadyofReylo, Jul 17, 2021., tweet by hammerhertls, Mar 12, 2019., and some have criticized the OTW for not taking them seriously"I have seen thread after thread of people talking about contacting the AO3's Abuse Team to report what they have experienced as targeted racist harassment in particular tags." (Possibly a reference to the 2014 racist hockey trollfic, which was tagged "interracial kink".) What's up with the AO3 and racism? by Naye, 17 June 2020.. Meanwhile, the rise of purity culture led to many complaints that anti-shippers were harassing AO3 users who posted fanworks featuring ships believed to be problematic.Example of a perpetrator's confession: , tweet by lovingmyirene, 15 July 2022. Stories have circulated about writers getting chased off the website by persistent trolls (see Shinocchi, for example)."Speaking as someone who had to delete an entire identity worth of fanfic and a complete persona due to receiving months of threats and harassment from an underage user who never received any visible discipline whatsoever? Speaking as someone who found the abuse mods' responses increasingly ineffectual and eventually expressing annoyance toward me for letting them know I was still being abused? I do not donate to AO3 anymore either." , 30 Apr 2016.Reddit examples: "Basically I wrote a series of Explicit fanfics for a pairing I liked, of which both participants are around 15-16. I tagged and put all the necessary warnings on these fics. It still didn't stop people from getting angry at me, sending me hate, and basically harassing me out of AO3." , posted by Gold_Win in r/fanfiction, 24 September 2019. , 18 April 2019. Fans have described receiving death threats over the wrong character topping, among other things., fail_fandomanon thread, 2022-09-15. In some fandoms like MCYT, strategic mistagging became widespread in part because fans were trying to avoid the attention of haters (they were also trying to avoid mis-wrangled tags and YouTubers looking at fic of themselves)."the unspoken rule in a majority of mcyt and mcyt adjacent nsfw and pnsfw fanbases is to keep the creators completely separate but still be accessible to people who want to find it.... we all do this to keep our community safe from doxxing and death threats that comes with being associated with RPF." , 03 Mar 2022. Accessed 29 June 2022.fail_fandomanon discussion about why MCYT fans are putting "lol no" in the fandom tag field of their fic: , 2021-11-15., tweet by TheWebernutter, 6 March 2022.
Many different groups of fans have complained about seeing fanworks on the site that they didn't want to see (such as badfic, NOTPs, underage RPF, slavefic, bigoted trollfic, or unflattering portrayals of their fave"As a reminder, AO3 will not remove works solely because they portray characters or relationships in a bad light." , 2016-02-13.). Some people have argued that having better curation tools (such as the muting function) might reduce harassment, as some of the harassment is coming from people being confronted with material that they find upsetting. Trollfic is itself considered by many fans to be a form of harassment, but does not violate AO3's current policies.
===After June 2020===
After the OTW's June 2020 post indicating that the feature would be developed, fans were also critical about the lack of apparent progress on the features:
In early 2021 the overtagging on the fic Sexy times with Wangxian led to renewed calls for a tool to hide certain fics from tags and search results. A Reddit example:
Although many fans wanted a blocking feature, not everyone agreed on what users should be able to block:
===Fan Responses to 2021 Blocking and Muting Update===
The OTW posted an official update describing how they planned to implement the feature: An update on blocking and muting. Many commenters declared their support for the features, especially the idea of separating the functionality of blocking vs. muting, and thanked the OTW for providing the update.
The announcement was posted on April 1, 2021, so some users were initially skeptical and thought it was an April Fool's Day joke., 1 April 2021."This better not be an April fools joke" , 2 April 2021. For example: "I really, really hope this is a legitimate update post with an unfortunate timing and not a poorly thought out April Fool's joke.", 1 April 2021. In response to one of the skeptics, another commented, "i don't think they would do a prank like that. people have been asking for this feature for a while, and it would be unnessesarily cruel to get people's hopes up like that.", 1 April 2021. Commenters were relieved when assured that the post was genuine, 1 April 2021., apart from one anon who worried that antishippers might misuse the feature to harass people somehow, 2 April 2021..
===Fan Responses to Comment Blocking Rollout===
https://twitter.com/AO3_Status/status/1533257572668608513
https://twitter.com/AO3_Status/status/1535369869960835072
https://ao3org.tumblr.com/post/686179597345341440/comment-blocking-is-coming
https://fail-fandomanon.dreamwidth.org/549040.html?thread=3337598384#cmt3337598384
===Fan Responses to User Muting Rollout===
The AO3 News announcement post generated 400+ comments, with many excited and thankful fans. A number of people asked whether the archive would implement muting by work or tag., 05 Feb 2023., 06 Feb 2023. A few people also asked to be able to block certain users from seeing their works, 06 Feb 2023., 06 Feb 2023. or to prevent blocked users from bookmarking their works, 07 Feb 2023..
@ao3_status's tweets generated a lot of replies.
ao3org's Tumblr post had over 16 thousand notes. by ao3org, 6 February 2023. As of 6 July 2024, this tumblr post has 16,810 notes.
Discussions on fail_fandomanon: 2023-02-05, 2023-02-08.
==Third-party tools==
Various AO3 users have created scripts and browser extensions to make up for functionality that AO3 lacks. Tools that can simulate a block or mute function include
*AO3 Savior
*AO3 Personal Hellban
*AO3 Series Collapser
*AO3 kudosed and seen history
==Related AO3 Updates==
Blocking is one of the few anti-harassment features to be added that targets specific users. However, the AO3 has implemented other tools designed to prevent harassment and other unwanted user interactions: 
*Users can turn off anonymous comments on their works. (Previously users were forced to archive-lock their works if they wanted to prevent anonymous comments.) Added April 2013.
*Users can moderate comments on their works. Added late 2015.
*Users can reject a gift. Added December 2015.
*Users can no longer be added automatically as co-creators on a work; instead a co-creator request is sent. Users must opt-in to allow co-creator requests. Added September 2019.
*Users can turn off comments on a work. Added August 2020.
*Users can freeze a comment thread on their work. Added February 2021.
*Users can opt out of receiving gifts. New user accounts default to not receiving gifts and must update their preferences to opt in. Added February 2022.
*Users with the "protected user" role cannot have their works cited as related works. Added August 2022.
*Users can no longer choose the option to have their works automatically added to collections. Users must opt-in to allow their works to be invited to collections. Added March 2023.
*Users can prevent guests from replying to their comments on news posts and other users' works. Added October 2023.
*The default comment setting is changed to registered users only for posting new works. Added April 2024.
==Meta/Further Reading==
*every time I see more of the ‘ao3 is evil’ crap circulating I think, ‘well, tumblr is evil too and I don’t see you stop using it’
*AO3's Filtration System
*Timeline of the Archive of Our Own
==References==
Category:Archive of Our Own