Locus Awards Live

[kevin_standlee]

I'll be acting as one of the "studio moderators" for the live coverage of the Locus Awards this afternoon at 2 PM Pacific Daylight Time. I'm not in Seattle; I'm just helping manage the CoverItLive coverage.

The last time I pointed people at a CoverItLive event (the Hugo Award Nomination announcements), at least one person looked at the page in question, said (approximately), "I didn't click on it because it looked like some sort of video streaming thing." CiL is not a audio/video streaming thing (although you can put such things into a CiL event). At its simplest, CiL is an online text chat session, and it's not a bandwidth hog as far as I can tell. The Hugo Awards coverage later this year is likely to use the same technology, so if you're thinking of watching the Hugo results come in live but can't get to Reno for Worldcon, you might want to watch the Locus Awards coverage this afternoon to get an idea as to how the live-chat technology we're using works.

Comments

[kevin-standlee.livejournal.com]

Oh, I'm going to do some of that. (One of the Hugo Administrators is on the Hugo Awards Marketing Committee and has access to THA.org, but her time is likely to be as limited as mine post-ceremony.) I'll create the blank and put the winners into it as I can. The challenge is that I'll be also managing the online live coverage, and while some people think the Hugo ceremony is too slow, it's blazingly fast when you're trying to keep up with the live coverage and also drop winner names into the winner announcement. But I'll manage.

Ever since being involved with a technical glitch on the web site a few years ago (SF AwardsWatch posted the nominees a few hours earlier than when they were formally announced due to a "post at X time" direction to the software not working properly, which is not quite as bad as posting the winners early, but still bad), I've been cut off from embargoed Hugo announcements.

[kalimac.livejournal.com]

My scenarios don't require your being privileged under embargo ... though it's a shame about that glitch; depending on the reason for a mistake, the person who made it might be the most, or might be the least, likely person to make the same mistake again.

The main point is, which you surely already know, is that there's all kinds of prep work for something like this which can be done before the necessary information arrives, where one might think that you can't do any of it without that information.

[kevin-standlee.livejournal.com]

The unfortunate lesson learned by us was that the post-at-future-date/time feature doesn't always work as a delayed post, and sometimes will generate cross-links (to, say, Twitter, Facebook, and LiveJournal) as soon as you hit Publish even if you told the software to not do so until, say, 12:01 AM the next morning.

Although I still use the delay-publish feature now and then, I don't risk it with anything that would cause a fuss if posted early. I've mainly used it when we've had multiple pieces of information about Westercon to publish and I haven't wanted to make three posts in five minutes but instead spread them out over three days. (Convention news has tended to come to me in spurts, coinciding with committee meetings.)