As a nice follow-up to my Thanksgiving Day post, LGF Gets Punked, I thought it’d be fun to play a little game. For this contest, I’m going to post a question, and the first commenter to answer correctly is going to win a fabulous prize. First though, a little background…
In our first episode, I had gotten the Lizardoid’s undies in a bunch by rogering up the LGF Dictionary blog with a couple of cute little items, like a my own YouTube video, a short LGF bio on myself, and a vandalized header. Oh, and I also moved the dictionary itself over to the Chamber (I did give it back, just for the record). Anyway, after a bit of drama in the Thanksgiving thread over on the main site, the blog key holder Zombie arrived to calm the horde, and blithely posted the following:
I heard a rumor the LGF Dictionary had been hacked, so I just went in 5 minutes ago and unhacked it.
if it gets hacked again, I’ll probably just take it offline.
Too many people knew the password, so it was floating around a little loose.
(Password changed, needless to say.)
At the moment, the dictionary itself is no longer there (just the blog); I may re-upload it, may not.
Wait and see what happens.
The fact that a wordpress.com blog has no “password” and that it wasn’t “hacked” notwithstanding, Zombie did manage to remove my mess (something that really took only a couple of clicks, no doubt), and the dictionary itself is now posted at LGF proper (why it wasn’t there all along, I’m not sure).
But “wait and see” we did, and when you go to the blog now you can check out my little encore:
I’m going to take the liberty of utilizing the LGF Dictionary one last time and say….
How the heck did I do it?
Update: It took a few days, but the LGFers finally got word:
Ah yes, that’s the question. But again, no “hack”. Please, let’s review the facts:
1) On Thanksgiving, I was granted admin privileges to LGF-D by one of the handful of other admins on that blog
2) Once I was in, I performed a few actions, including booting the other admins (save Zombie), replacing the header, posting a new thread (”The Legend Of ChenZhen”), pasting my “you’ve been punked” youtube video in place of the dictionary page (and moving the dictionary text to my own, password-protected page), and grabbing a few screenshots along the way. (nothing that couldn’t have been put back to normal without too much trouble)
3) I post the “LGF Gets Punked” thread here in the Chamber, displaying the screenshots and providing a forum for discussion
4) after sitting that way for a few hours, Zombie was eventually alerted, quickly moved in to erase all those things, booted me as the last remaining admin (leaving only herself), and posted her aforementioned comment on LGF
5) a few days ago, my encore appeared at LGF-D (and only remains posted because, presumably, Zombie hasn’t been alerted to it yet)
And with that, I give everyone a big…fat…HINT. (Since no one had noticed, and the post is likely to be gone soon)
Update: The blog is gone, as Zombie promised. Time to reveal the answer. Not too complicated…
Since I knew that it would be easy for Zombie to fix all those things I listed in #2 above, and that I’d be promptly blocked, I thought it might be fun to “schedule” an encore as long as I was in there. For wordpress.com blogs, the scheduling part is easy to do from the post editor:
The problem was, any new thread that I penned would have shown up at the top of the list in the dashboard, (even if it hadn’t been published yet), meaning that it probably would have been caught when she was deleting the other stuff. What I needed was something that would have been buried a little to avoid detection.
Now, what many wp.com bloggers might not realize is that you can use the above interface to reschedule a post that has already been published. So, all I did was look for an older post that I could use to drop in my video and set a new date. And as luck would have it, Zombie unwittingly gave me a little gift over a year ago, ’cause I found a thread aptly titled “I’m Ba-a-a-a-a-ack”. Destiny? I dunno. But I figured the chances of catching that were slim to none, and even the fact that I was subsequently blocked wouldn’t stop the post from appearing at the specified date and time.
In other words, what you saw here was a brave nomadic warrior’s voice from the blogospheric grave coming back to issue another punking, and certainly NOT another “hack”.