Mick A | 18 Oct 2013 11:45 a.m. PST |
Anyone know why its been locked? |
Tango01 | 18 Oct 2013 11:51 a.m. PST |
This has to be a mistake. Angel is locked? What a bad news!! Amicalement Armand |
Mick A | 18 Oct 2013 11:56 a.m. PST |
He's certainly not happy about it and has no idea why
|
John the OFM | 18 Oct 2013 12:14 p.m. PST |
Stifling an Editor is one way to get your account locked. Try it. I dare you! So is apostrophe abuse. (Or it would be, if Dear Editor had made ME an Assistant Editor!) I find it a bit odd that minor DH offenses say right on your profile page WHY you are serving time, but a much more serious Account Lock is mum on the subject. Hell, I KNOW why mine was back 2 years ago! But then I provoked it. Deliberately. |
Silent Pool | 18 Oct 2013 12:22 p.m. PST |
TMP is in meltdown. Quick, women, poets and cowards first out – although not necessarily in that order. If it is true, then
It worked for me. |
MrHarold | 18 Oct 2013 12:28 p.m. PST |
|
20thmaine | 18 Oct 2013 12:31 p.m. PST |
Must be a mistake – he is reasonableness personified (and I should know – after all it takes one to know one ) |
MrHarold | 18 Oct 2013 12:32 p.m. PST |
Angel Barracks just sent me this:
Ha Ha, my fault!! Could you post this on my behalf please? "Hi.
Just found out why my account has been locked. My fault. I read somewhere in a thread that the new editors can't be stifled and did not think this was correct. So I quickly stifled one to see if you could stifle them, it turns out you can, so I unstifled her right away, but it seems you DO get your account locked for trying
Totally my fault, could you be a gent and return me to trusted status please Bill? Michael."
|
Doug em4miniatures | 18 Oct 2013 12:39 p.m. PST |
It's not safe to do ungood in this regime
Doug |
Mick A | 18 Oct 2013 12:44 p.m. PST |
|
richarDISNEY | 18 Oct 2013 12:47 p.m. PST |
WHEW! I knew it had to be a mistake.
|
Col Durnford | 18 Oct 2013 12:50 p.m. PST |
No, I would hand you a loaded gun. Hey, watch where you point that thing. Oops. Glad to hear it was a case of friendly fire. |
20thmaine | 18 Oct 2013 12:55 p.m. PST |
"No, it wasn't the bullets and the planes – It was Curiosity that killed the beast" Never press the Red Button marked "Do Not Press This Button" |
79thPA | 18 Oct 2013 1:05 p.m. PST |
In other news, your hand really will get burned if you stick it in fire. |
RavenscraftCybernetics | 18 Oct 2013 1:43 p.m. PST |
|
dragon6 | 18 Oct 2013 3:54 p.m. PST |
Ah
good. Something else I don't need to try. Thanks ticking that one for me |
John the OFM | 18 Oct 2013 5:34 p.m. PST |
I have ALSO been asked to post this:
Just found out why my account has been locked. My fault. The OFM is correct.
I read somewhere in a thread that the new editors can't be stifled and did not think this was correct. So I quickly stifled one to see if you could stifle them, it turns out you can, so I unstifled her right away. Totally my fault, could you be a gent and return me to trusted status please Bill? Michael."
I TRIPLE DOG DARE you to lick the flagpole! That's Bill being Bill. |
Wellspring | 18 Oct 2013 6:17 p.m. PST |
Can't saying the phrase, "The OFM is correct." also get your account locked? I'm sure I read that somewhere. |
Editor in Chief Bill | 18 Oct 2013 7:32 p.m. PST |
I think it's silly and figured it would be an easy enough thing to disable or make the button visible=false for editors. There's actually a good reason for it – if someone is mad enough to stifle a staff member, this creates a situation where we can ask them what the problem is, and hopefully resolve it. And, of course, announcements from any of the editors could be vital information to our members. |
15th Hussar | 18 Oct 2013 7:32 p.m. PST |
Never press the Red Button marked "Do Not Press This Button" PUSH THE BUTTON, MAX! (Which, if I'm not mistaken is actually a quote from both "The Great Race" and a Duck Rogers Looney Tune Cartoon.) |
Editor in Chief Bill | 18 Oct 2013 7:35 p.m. PST |
And yes, his account has been unLocked. The only delay was due to (a) Editor Julia was attending a festival today, and (b) when Mike wrote me about the problem, he forgot to tell me his membername. |
15th Hussar | 18 Oct 2013 7:44 p.m. PST |
if someone is mad enough to stifle a staff member So you have to be mad (angry???) to want to stifle an Editor? Odd, I thought stifles (which would be better termed Ignored), were a combination of: 1) Japes, pranks and jests on the part of Fellow TMP'rs. 2) Not really wanting or caring to hear from or about Person X. 3) Anger at a person for what they posted. In my book then, mathematically, approx. 33% of the time someone may be mad/angry at a member and want to Stifle them. Are you assuming that all Stifles are from MAD (angry) members? (I'm using angry, as MAD also alludes to crazy people and I'm sure we're all sane on this site). Also, it is quite possible to not stifle an Editor (or anyone else) and never read a word they wrote
other than the subject line; you can just scroll right by the announcement/post. |
20thmaine | 19 Oct 2013 1:45 a.m. PST |
The three strands may not be weighted evenly – it is possible (even more than possible) that japes form a small part of the equation, whilst not want ing to hear from / angry at someone are significantly higher. My unscientific wet finger guess would be 1% / 75% / 24%. It might be interesting to ask this question via a poll. |
15th Hussar | 19 Oct 2013 6:51 a.m. PST |
20thMaine
yeah, you're most probably correct, I was just doing a basic odds division. Which is why IGNORE would be a better term to use instead of the rather rude "Stifle". |
Joes Shop | 19 Oct 2013 8:37 a.m. PST |
|
Gearhead | 19 Oct 2013 8:21 p.m. PST |
Never press the Red Button marked "Do Not Press This Button" Oh, it's not so bad. All you get is a little sign lighting up that says "Please don't press this button again." |