fandomsecrets | [ SECRET POST #1614 ]

⌈ Secret Post #1614 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.

01.

__________________________________________________

02.

__________________________________________________

03.

__________________________________________________

04.

__________________________________________________

05.

__________________________________________________

06.

__________________________________________________

07.

__________________________________________________

08.

__________________________________________________

09.

__________________________________________________

10.

__________________________________________________

11.

__________________________________________________

12.

__________________________________________________

13.

__________________________________________________

14.

__________________________________________________

15.

__________________________________________________

16.

__________________________________________________

17.

__________________________________________________

18.

__________________________________________________

19.

__________________________________________________

20.

__________________________________________________

21.

__________________________________________________

22.

__________________________________________________

23.

__________________________________________________

24.

__________________________________________________

25.

__________________________________________________

26.

__________________________________________________

27.

__________________________________________________

28.

__________________________________________________

29.

__________________________________________________

30.

Notes:

Secrets Left to Post: 09 pages, 218 secrets from Secret Submission Post #231.
Secrets Not Posted: [ 0 - broken links ], [ 1 2 3 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ], [ 1 - posted twice ].
Current Secret Submissions Post: here.
Suggestions, comments and concerns should go here.

Flat | Top-Level Comments Only

background-colour: white;
colour: white;

That way it can be highlighted by someone who wants to find out, and ignored by someone who doesn't.

And what do we do when posting a fic to an archive, say FFN or AO3?

Isn't AO3 pretty good about allowing some html? Not sure if this text box thing still works on lj let's see

Just throwing out there that some people really don't like AO3 for various reasons, so this doesn't solve the "problem" of FFN. Though really, if someone puts "dark" as a warning/genre, I think most people are going to assume they could be triggered by it, if their triggers fall under that heading, so I don't see the need for all of this?

I don't particularly care actually. Warn, not warn, spoiler tags, whatever.

I just saw "OH HEY HTML THREAD" and piped in.

Haha, yeah. I wish more sites were HTML-friendly in their "summary" sections. If for no other reason, so I could italicize things. FFN is especially egregious in its random stripping of symbols...

I did spoilery warnings in binary once with a link to a translator. It was a bit silly, but most people can't just read binary, so it worked not badly.

At AO3 you can say that you choose not to warn. People who have issues will just avoid the fics.

I think you can do this anywhere by, say, adding a line in the description.

True, sorry, I was just directly answering the person's question about AO3, not making some ad for AO3 or whatever. Also AO3 forces you to choose. You can't just not warn. You have to either warn, say that no warnings apply, or say that you are choosing not to warn. But you can't leave it blank.

But yes, you can do this anywhere, including your own journal.

Post the warning at the bottom of the story, or something. Easy enough to find alternatives.

Bottom of the story, or as part of notes at the top? The former method seems counterproductive since... wouldn't the reader have already finished the fic at that point?

Not it you put a note at the top saying that the warnings are at the bottom and to scroll down if you want them. Readers with triggers should be reading the authors note's thoroughly.

You put the warnings at the bottom of the story. Plenty of alternatives.

doesn't solve the problem. Warning that there are warnings elsewhere means the reader is pre-alerted to the fact it needs warnings so reduces impact. Warning that you don't do warnings means the reader is pre-alerted to the possibility of it needing warnings, so reduces impact. The idea is that the reader should feel a visceral metaphorical gut punch.

If you are too feeble to deal with the idea then you shouldn't be reading anything at all, probably because your reading level is "See Spot Run" and still need checking to see if toilet training has successfully taken. Anyone over the age of five or six should be able to cope with the concept of death, and anyone over the age of fourteen the darker concepts of life.

Whatever you say. I'm still convinced it's nothing but lazy writing on the ficwriters' part. You (generic you) want to slam the reader in the face while lacking in the talent/ability department, so you need to resort to all the tricks available to you. The problems is, in most such cases it's not the death itself that impacts the reader, but the surprise. Which is not the same, agree?

The first thing that comes to mind might be a little bit unexpected, and still. Sabatini mentions Hagthorpe's death fleetingly; it's given just one sentence. It's not even that major a character. Still it's an impact every time I re-read "Captain Blood". I know for sure Hagthorpe's going to die in the final battle. Still every single time I still hope that this time he would live.

And there are more examples like this. The difference is the way to tell the story. If you need the crutches and need to rely on the surprise part, then you need to work on your storytelling skills and not wage war on warnings, because your problem lies elsewhere.

P.S. - Sorry for the extremely late reply. :)

[ SECRET POST #1614 ]

CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.

Re: CSS works in many cases.