Case (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
case) wrote in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
fandomsecrets2015-09-15 06:58 pm
case) wrote in fandomsecrets2015-09-15 06:58 pm
[ SECRET POST #3177 ]
⌈ Secret Post #3177 ⌋
Warning: Some secrets are NOT worksafe and may contain SPOILERS.
01.
__________________________________________________
02.
__________________________________________________
03.
__________________________________________________
04.
__________________________________________________
05.
__________________________________________________
06.
__________________________________________________
07.
__________________________________________________
08.
__________________________________________________
09.
__________________________________________________
10.
__________________________________________________
11.
__________________________________________________
12. http://i57.tinypic.com/35chf9c.jpg
[penis]
__________________________________________________
13. http://i.imgur.com/OB1EeH5.jpg
[porn - furry/illustrated]
Notes:
Secrets Left to Post: 02 pages, 042 secrets from Secret Submission Post #454.
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.
Re: CAPSLOCK THREAD
actually, i have visual issues and caps lock after awhile is difficult. from what people are posting here, it's not so bad. but i used to be in communities where caps lock days were super popular, and people would *wait* for those days for stuff that they wanted to talk about but thought didn't warrant a post of its own. that's how we ended up with 100-200 comment caps lock threads weekly, with long comment threads that were often very long comments (as in, some of them would have to use more than one comment back on LJ with their character limit).
solution! i found... oh, i can't remember if it was an add-on or a stylish script, but something like that, so i had a button to turn all caps to all lowercase, which made it easier to read. it poofed at some point, though, probably in an OS reinstall, because this was back in... 2008-2010? while i hate using this as a reference, it was back when wrath of the lich king was the major expansion for wow, because the community that did it most was a wow-related one that i also happened to be a moderator for... so i sorta needed to be able to read them.
breaking para for readability. it wasn't uncommon for people to get into tiffs and needing a mod step-in. since i was the night owl mod, i was usually the only one available if it happened at those times, and, wow, you would not believe how many people invented major drama that spun WAY out of control if not caught within an hour or so, at *thinks* between 3-6am PST.
it is possible i'm taking "can't you read" a bit too literally :P but i figured i'd point it out. however! as evidenced by the number of comments those threads would get back in the heyday (and it wasn't just that community, lots of others had em, but it was the one i HAD to read because i take my mod responsibilities seriously), people LOVED them. if the mod who usually made the caps lock post weekly missed it, someone would either a) ask in another post where the caps lock thread was, b) IM one of the mods, c) make a new post if one wasn't up by 3pm PST. so i wasn't gonna say, "hey guys, this is hard for me to read, can we not?" when i could find an extension or script or something to just switch to lower case. (which i would provide the link for frequently so that anyone else with a similar issue could join in the fun.)
... long comment is long. wow.