[ SECRET POST #5230 ]

[case]

⌈ Secret Post #5230 ⌋

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


01.



__________________________________________________



02.


__________________________________________________


03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.



__________________________________________________



07.







Notes:

Secrets Left to Post: 02 pages, 48 secrets from Secret Submission Post #749.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Comments

[(Anonymous)]

you cannot possibly be serious

[(Anonymous)]

I am serious.
A different anon already said they could have used the warning, and I am serious about it being warned for elsewhere too.

[(Anonymous)]

It's a BALLOON.

[(Anonymous)]

Asking for warnings is always better than demanding them, particularly when it’s for something outside the norm. That said, people have asked for warnings for less graphic artwork that was actually relevant to the secret it was attached to, so no idea why people have decided to let their asshole flags fly for you specifically.

[(Anonymous)]

part of it is the distinction between asking if something could have a warning going forth (since case does not assign warnings, we do) and demanding a warning with no understanding of how this community policies itself

the other part is that it is a fucking balloon

da

[(Anonymous)]

That person wasn't asking, they were stating it needs a warning. It's none of my business why they're triggered by balloon art, but trying to control the content warnings on someone else's secret is rude. But like you said, they can ASK, which again, is not what they did.