If your ad blocker has somewhere you can copy-paste filters (like a “My filters” section) just stick your statements there.
Your ad blocker will block any story with tags that contain those words.
More details under the cut!
Block by exact tag
The statement above blocks any tags that contain your keywords. For example, if you use it to block ‘Angst’, it will cover tags like ‘Heavy Angst’, but also ones like ‘No Angst’. This may or may not be what you’re going for, depending on the tag.
To block exact tags, put them in a statement like this:
This statement blocks the ‘Angst’ tag. (Or ‘angst’ - the ‘i’ option makes it case insensitive.) It doesn’t block other tags like ‘No Angst‘.
We’re also blocking ‘Hurt/No Comfort’ to show how special characters look with this method. You have to replace spaces with %20, forward slashes with *s*, question marks with *q*, periods with *d*, and hashtags with *h*.
If you’re on desktop you can Right Click - Inspect the tag, and just copy how it looks there.
Importing as a custom filter list
If your ad blocker doesn’t have a place to copy-paste your statements, check if it has a place where you can import custom filters. With this method, you’ll have to make your own filter list and upload it somewhere like google drive or github. I have an example on github here that blocks fics with an explicit rating, and a couple of links here that walk you through how to make your own.
The cool thing about doing it this way is that you can have your list in one place and link to it from multiple devices. Then, if you update your list, you only need to do it once, instead of on each separate device.
I really hadn’t realised I was on someone’s actual blacklist until today when I stumbled upon a fic rec. Could neither kudos nor comment as I was… yes you guessed it… blocked!!!
Guess my own little fics have caused a lot of harm for someone to go to such lengths as I really have no recollection of ever reading any of their fics before. Seems like targeting more than anything for whatever reason unfathomable to me as I really have not had any dealings with the author of said piece in question. Not to my knowledge anyway.
Guess this person doesn’t want their fic to be tainted or whatever if I was to leave a kudos or a nice comment having perhaps written questionable content in their mind?
There is such a thing as filtering by tags in ao3 so not to stumble upon triggering fics so why bother to block individual writers?
Twitter I can understand to some extent. The blocking part. Then again for me personally it’s too much of a hassle to block rather simply scrolling past the content I don’t care too much for.
Oh well, live and learn.
Frankly I’m too old to deal with scheisse like that, but yeah, guess I still had to write this post😈
Oh ao3, thou art a heartless bitch but I love you just the same.
In case anyone is worried about being blocked from commenting on my works, I want to be clear that I’ll be blocking the accounts who have commented with threats of physical violence against me and/or repeatedly demanded content that I’m not comfortable with even after I said no
Basically if you’re a decent human being who doesn’t threaten violence or overstep boundaries, you’re fine and I love you, keep calm and comment on <3
Do you wish you had the ability on AO3 to block works by tag, author, title, or words in the summary? You need AO3 Savior.
Step One: Install the Tampermonkey extension on your browser (link is for the Chrome extension, so if you use a different browser, just search for it). This will allow you to install the AO3 Savior userscript.
Step Two: Install AO3 Savior. Click on the link and hit the Install this Script button (image below)
This will open the userscript in Tampermonkey. Click the install button there too (screenshot below)
Step Three: Install AO3 Savior config the same way. It’s a separate file because if you update the code, it resets all of your blocks so you need to input them again. By having the config separate from the rest of the code, the other code can update while leaving your block settings in tact.
Step Four: restart your browser
Step Five: Click on the puzzle piece at the top right corner of your browser. Click on Tampermonkey and then into your Dashboard. From there, find ao3 savior config in your list of installed scripts and click on the edit button (screenshot below)
Step Six: edit the code to block the things you want to block. This might sound intimidating, but it’s okay!
In this config file, scroll down and read through the text. The first settings are turning options on or off. Use “true” to have that feature or “false” to turn that feature off. For example:
// Set to false if you don't want to see why works were hidden.
showReasons: true,
When the code starts with // that means that it’s a comment or instructions to you. Read that line and then make the change on the line below it. In this case, change the word “true” to “false” if you don’t want to see the reason why the work was hidden from you.
To block on author, edit this part:
// Exclude works with an author that exactly matches at least one term.
authorBlacklist: ['Hated Author 1', 'smeyer'],
Find the author’s name on AO3 and copy it so that you get the spelling right. Then paste it in here. To make sure your syntax is right, make sure that the author name is inside the square brackets [ ] and also inside apostrophes ‘. Separate each author name with a comma , like you see in the example provided.
You can do the same thing with tags by copy/pasting the full tag and putting it inside apostrophes in the tag blacklist section. Same thing for specific fic titles or for words that appear in summaries.
Step Seven: After you have made all of your changes, go up to File and remember to Save.
Step Eight: You can now close that tab and head on over to AO3 where the only sign of those fics/authors/tags etc you blocked will be a little box telling you a fic has been hidden, and why. If you don’t want to see those boxes, change those settings to false in step 6.
In future, if you ever want to block a tag, author, or work from your AO3 experience, just go back into your config file and edit them in there.
Note: in order to get this on mobile, use Firefox. Other browsers do not allow userscripts on mobile
