BlackHeart Biohazards

Absolutely Rancid Garbage. But you love that.
  • Sample Page

Recent Posts

  • (no title)
  • (no title)
  • (no title)
  • (no title)
  • (no title)

Archives

  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022

( No Title )

by admin on February 4, 2024 at 12:55 pm
Posted In: Uncategorized

steddie-island:

aplacetoreblogthingsto:

blackheartbiohazards:

➡️ Content warnings on fiction are a courtesy. 

➡️ Not every medium of fiction and storytelling has or is expected to have content warnings or extensive tagging.

➡️ Print novels do not traditionally warn for content in any way.

➡️ Until AO3 came along, fanfiction did not traditionally warn for content in any significant way.

➡️ An author is only obligated to warn for content to the degree mandated by the format they publish their fiction on.

➡️ Content warnings beyond the minimum are a courtesy, not an obligation.

➡️ ‘Creator chose not to warn’ is a valid tag that authors are allowed to use on AO3. It means there could be anything in there and you have accepted the risk. ‘May contain peanuts!’

➡️ Writers are allowed to use ‘Creator chose not to warn’ for any reason, including to maintain surprise and avoid spoilers.

➡️ ‘Creator chose not to warn’ is not the same thing as ‘no archive warnings apply’.

➡️ It is your responsibility to protect yourself and close a book, or hit the back button if you find something in fiction that you’re reading that upsets you.

➡️ You are responsible for protecting yourself from fiction that causes you discomfort.

(commenting on tags)

I think my issue with the wording of this is the contradiction between “You are responsible for protecting yourself from fiction that causes you discomfort.” and the rest of it. Like, yeah. We want to protect ourselves from fiction that we wouldn’t want to read. That’s why we’d like content warnings.

Empowering people to make their own choices by giving them the necessary information to do so is good. It should be generally the standard that we give people that necessary information. Just because something was done a certain way in the past doesn’t mean that way was good. It doesn’t mean that way is or should be unchangeable. Just because people have always done it one way doesn’t mean that way is better and can’t be improved. I, personally, think the standard of content warnings is good, and both publishing and fanfic should move towards that as standard.

(I should say that I’m a relatively “Fandom Old” person who started reading fanfic more than 25 years ago. So don’t come at me like I’m some youngin who wasn’t there for the Wild West days)

Just because something was done a certain way in the past doesn’t mean that way was good. It doesn’t mean that way is or should be unchangeable. Just because people have always done it one way doesn’t mean that way is better and can’t be improved.

Content warnings should absolutely be the standard. I have never heard any argument against them that has made any damn sense or changed my mind.

If you really think your book/ fic/ whatever is better spoiler free, then let people know that there are spoiler-y triggers and put them under a read more or something. But just saying “Nope not gonna use CWs” could not only lead to people getting triggered out of nowhere, but it’s turning people who might vibe perfectly well with your content away.

“Creator chose not to warn” IS a warning all by itself.

It is a warning that anything could be in the story and if you don’t accept that risk the author doesn’t want you to read it.

Some authors value maintaining the surprise in their work over making the work accessible to absolutely everyone who might be comfortable with its contents.

And that’s a valid choice to make on AO3.

 Comment 

( No Title )

by admin on February 4, 2024 at 12:54 pm
Posted In: Uncategorized

kullimos-the-despoiler:

blackheartbiohazards:

➡️ Content warnings on fiction are a courtesy. 

➡️ Not every medium of fiction and storytelling has or is expected to have content warnings or extensive tagging.

➡️ Print novels do not traditionally warn for content in any way.

➡️ Until AO3 came along, fanfiction did not traditionally warn for content in any significant way.

➡️ An author is only obligated to warn for content to the degree mandated by the format they publish their fiction on.

➡️ Content warnings beyond the minimum are a courtesy, not an obligation.

➡️ ‘Creator chose not to warn’ is a valid tag that authors are allowed to use on AO3. It means there could be anything in there and you have accepted the risk. ‘May contain peanuts!’

➡️ Writers are allowed to use ‘Creator chose not to warn’ for any reason, including to maintain surprise and avoid spoilers.

➡️ ‘Creator chose not to warn’ is not the same thing as ‘no archive warnings apply’.

➡️ It is your responsibility to protect yourself and close a book, or hit the back button if you find something in fiction that you’re reading that upsets you.

➡️ You are responsible for protecting yourself from fiction that causes you discomfort.

Counter point: do it anyway and be nice to strangers on the Internet? And not make someone feel shitty because you wanted to keep your super special plot twist a secret? Typing a sentence at the start of a paragraph doesn’t fucking ruin a story bro, meanwhile if I wrote fanfic I’d rather not risk causing an episode in my potential audience.

“Creator chose not to warn” IS a warning all by itself.

It is a warning that anything could be in the story and if you don’t accept that risk the author doesn’t want you to read it.

Some authors value maintaining the surprise in their work over making the work accessible to absolutely everyone who might be comfortable with its contents.

And that’s a valid choice to make on AO3.

 Comment 

( No Title )

by admin on February 4, 2024 at 12:17 pm
Posted In: Uncategorized

The “chose not to warn” post has reached the sort of people I am going to start blocking. Ha ha

└ Tags: blog updates, fandom wank, 🔍⚔️
 Comment 

( No Title )

by admin on February 4, 2024 at 12:10 pm
Posted In: Uncategorized

cemeterything:

i don’t know why i love characters who cause mass societal and/or ecological damage so much i’m just drawn to bitter stars who poisoned a third the earth’s waters when they fell

└ Tags: villain f/o
 Comment 

( No Title )

by admin on February 4, 2024 at 4:02 am
Posted In: Uncategorized


Tension Act – thesavagesabretooth – Persona 3 [Archive of Our Own]

Tension Act (3260 words) by thesavagesabretooth
Chapters: 1/1
Fandom: Persona 3, Persona Series
Rating: Teen And Up Audiences
Warnings: No Archive Warnings Apply
Relationships: Kirijo Mitsuru/Takeba Yukari
Characters: Kirijo Mitsuru, Takeba Yukari
Additional Tags: Emotional Hurt/Comfort, Getting Back Together, Post-Canon, Emotional Roller Coaster, Angst with a Happy Ending

Summary:

Yukari is busy with her acting career, but she knows exactly what Mitsuru wants when she shows up on set to talk to her. She’s come to pull her back into the shadows.

└ Tags: ao3, archive of our own, fan fiction, fanfic, fanfiction, femslash february, kirijo mitsuru, mitsuru kirijo, persona, persona 3, persona 3 reload, persona series, takeba yukari, toxic yuri, yukamitsu, yukari takeba
 Comment 
  • Page 1,650 of 7,039
  • « First
  • «
  • 1,648
  • 1,649
  • 1,650
  • 1,651
  • 1,652
  • »
  • Last »

©2022-2024 BlackHeart Biohazards | Powered by WordPress with ComicPress | Subscribe: RSS | Back to Top ↑