Correct! To see what you might have missed, visit the fandom tag in question and put the following in the “Search within results” field:
Many more search codes can be found in our tutorial, The “Search Within Results” Field and You, Pt. 1.
As you may already know, we collect links to userscripts and other third-party tools for use with the Archive in our Cool Stuff FAQ. It’s a fairly hidden page, and we have plans to create a dedicated space for it, but until then, this is where you find links to scripts and add-ons like AO3 Savior.
Unfortunately, the most popular script repository (userscripts.org) has been down for a while and will probably not come back. As a result, some of our links are broken right now, and while some workarounds exist, we’d prefer to update our links to point to new, hopefully more stable locations.
If you’ve previously uploaded an AO3-related script to userscripts.org, you might want to consider Greasy Fork (review) to re-upload your script, or host it on GitHub, Pastebin or similar. If you do, please let us know through our Support form or as a comment on this post. We’ll update the list as soon as we can!
We also have some new tools waiting to be added, and we’ll be sure to highlight some nifty additions when we’ve made sure all links are working again. If you have built a tool that’s not on the list yet, please feel free to let us know!
i don’t understand why some authors put BOTH “no archive warnings apply” and “chose not to use archive warnings.” they’re kind of mutually exclusive, aren’t they?
if your work truly doesn’t have anything that falls under what should be warned about, then i guess i don’t really understand why you would ALSO put “chose not to use archive warnings.” are you going out of your way to say “well if there WERE triggering content, i wouldn’t warn you about it anyway.”
here’s where i’m coming from: because i need to avoid certain triggers, if an author puts BOTH of those things, i won’t read it, because i interpret it as “the author doesn’t understand the warning system and therefore the work may have triggering content and it’s not worth the risk.”
don’t get me wrong, i’m so, so grateful that the “author chose not to…” option is available, because it’s the perfect compromise for authors who don’t want to spoil the plot and people like me who need to know about a potential trigger. it’s an excellent thing to come out of fanfiction culture. just please use it correctly. you should only be using it when there IS content that would ordinarily be accompanied by a warning.
Alas, it’s entirely possible that someone will tick both “Choose Not To Use Archive Warnings” and “No Archive Warnings Apply” by accident, due to the way checkboxes work (and the way our posting form is set up).
The good news is, we’re going to tweak the Archive Warnings part of the posting form ever so slightly, to make accidental combinations like that less likely in the future. We hope that the Warnings section will be more helpful to you (and others) going forward!