I never expected anything from AR really, so I’m never really Shocked. There are things that happened that I couldn’t have ever predicted in my wildest dreams/nightmares. It’s a ride! TBH I’m still excited about every single one, even when I don’t like them, bc I want to see where AR is taking us, on her macadamia nut high lol.
That’s true, art is different than writing in terms of the immediate engagement of seeing it. And yet, in galleries/museums, I can only remember a handful of times I’ve ever seen warnings for art that could be potentially upsetting in the context we’re using. With paintings like Judith Slaying Holofernes by Artemisia Gentileschi, you round a corner, and !!! someone’s getting brutally beheaded in vividly gorey detail. However, to attempt to discuss [fanworks] vs. [museum (or gallery)-displayed artwork and published fiction], that’s a potentially long and difficult discussion, and your blog is about fanfiction specifically, so I won’t go there.
But I do think we have to drag published fiction into the discussion as that’s what the fanworks are based on. As you wrote:
My concern is always that a tag like that is going to change how people interpret my work into something I didn’t intend. Like, I’ve been asked to tag things as abuse before that I really didn’t agree WERE abuse, just regular conflict in a relationship. I can appreciate that that might be upsetting someone, and would like to give them a way to avoid it, but I don’t want to label something as abuse if it’s not, either.
I agree with you on this. As “beauty is in the eye of the beholder,” so is “abuse is in the eye of any given reader,” whether or not the author intends it to be a depiction of abuse. Our fandom is based on works that contain plenty of problematic elements (including abuse) that the author most likely does not consider problematic, even when many of the fans are in agreement that they are problematic. Still, “many” is not “all,” and I choose not to trample on fans/fanficwriters/fanartists who ship A/B by tagging every depiction of
A/B
with {#abuse}, even when other fans condemn A/B as being a problematic and specifically abusive ship.
When fanartists and fanwriters take these same problematic elements from canon and extrapolate, they’re handling the same “tainted” material, whether or not they depict A/B as abusive, and therefore bear the brunt of the demands for tagging their works with {#abuse}.
So I don’t know what the answer is bc as I said above, I would not want to needlessly upset someone, but I also see it from the shipper/fanficwriter/fanartist/creator’s POV.
If we can’t agree on what should be tagged as {#abuse}, I feel like Dead Dove: Do Not Eat should apply:
I guess that writing is a little different, since it’s unlikely people are going to just glance at the work and be upset by something there. They sort of have to engage with it.
My concern is always that a tag like that is going to change how people interpret my work into something I didn’t intend. Like, I’ve been asked to tag things as abuse before that I really didn’t agree WERE abuse, just regular conflict in a relationship. I can appreciate that that might be upsetting someone, and would like to give them a way to avoid it, but I don’t want to label something as abuse if it’s not, either.
Dead Dove: Do Not Eat is a warning or tag used to indicate that a fanwork contains tropes or elements that may be deemed “problematic” without explicitly condemning the problematic aspects.
The “Dead Dove: Do Not Eat” tag would essentially be a “what it says on the tin” metatag, indicating “you see the tropes and concepts tagged here? they are going to appear in this fic. exactly as said. there will not necessarily be any subversion, authorial commentary condemning problematic aspects, or meditation on potential harm. this fic contains dead dove. if you proceed, you should expect to encounter it.”
I don’t feel that a
(published or fanfic)
writer is required to condemn abuse in the narrative, especially when, as you point out, they may perceive the abuse in question as regular conflict in a relationship. “Regular” is also up for debate, of course. As a fandom’s lifeblood is its fanworks, my feeling is to try to find some compromise between allowing the shipper/fanficwriter/fanartist/creators to create the fanworks they want to create, and for that to be done in a way that offers the most protection possible for people who might be upset by those fanworks.
Sometimes, in fandom, we just want to write id-tastic fic that rolls around in tropes that might be viewed as problematic. But we don’t want to address the problematic side of things in this particular fanwork; we just want to roll around and wallow.
It is considered courteous to give readers a heads-up via use of AO3 tags. I propose a tag that signals that a given fanwork is for rolling around, not giving a measured evaluation of anything. The MCU has carved out a space for this sort of fic with the “HYDRA Trash Party” tag, for which I commend them. Trash Party is a bit too specific to cover all of the ground I’m thinking of here, though; I propose “Dead Dove: Do Not Eat.”
For those of you not familiar with Arrested Development, Michael Bluth finds a paper bag in the freezer labeled “Dead Dove: Do Not Eat.” He opens the bag, finds a dead dove, and reacts as follows:
[gif of a white man saying “I don’t know what I expected” in a deadpan manner]
The “Dead Dove: Do Not Eat” tag would essentially be a “what it says on the tin” metatag, indicating “you see the tropes and concepts tagged here? they are going to appear in this fic. exactly as said. there will not necessarily be any subversion, authorial commentary condemning problematic aspects, or meditation on potential harm. this fic contains dead dove. if you proceed, you should expect to encounter it.”
I-want-my-IWTV 