Wednesday, May 28, 2014

I Can Almost Hear the Collective Sigh Already

This coming Saturday, 31 May 2014, is the date chosen for #LookBackRA.
We will be using the timetable from the last #LookBack:

Prime Time USA
USA East CoastUSA West CoastUnited KingdomAustralia NSW
Ep 1    8 PM  5:00 PM1:00 AM10:00 AM
Ep 2    9 PM  6:00 PM2:00 AM11:00 AM
Ep 3  10 PM  7:00 PM3:00 AM12:00 PM
Ep 4  11 PM  8:00 PM4:00 AM1:00 PM

There were many more votes for US evening times* than any other time zone so that's the "official" schedule, but if you want to find some friends and use the UK evening timetables (or a table for any other timezone - see timetables tab above or click here) feel free to use the #LookBackRA hashtag and get organizing. I only ask that you don't overlap with the US times above so as to avoid confusion.

If you have any questions about how the Armitage Watches work, please see tabs above, look through previous posts, or tweet @ArmitageWatch. I'm not sure how well TweetChat works anymore (they did some re-programming over there when Twitter made API changes and things may be different now) but I'm going to give it a chance. Another option is

If you don't have North & South on DVD, you can find it on Netflix or Amazon streaming.

Did I forget anything? 

OH YES, what about #GuyWatch and #LucasWatch? (That's Robin Hood and Spooks/MI-5) The consensus seemed to be "Schedule them and we will come." Most people wanted the option to be able to drop in when they have the chance, so I will get them back on the calendar for the summer and we'll get the ball rolling again in a couple of weeks.

*I don't know exactly what the poll numbers were, but I do know that Saturday, 31 May was ahead and I don't think June had more than one or two votes.

The votes were coming in and being counted.
Then Blogger ate them.
The next time I say I am doing a poll, someone please slap me remind me to find another way to do it other than using the widget provided by Blogger. Seriously. The polls were rocking along and the votes were tallying up, and the next time I went to check them - all values had been reset to zero! This happened here at least twice in the past, but I guess I'm just an optimist, with a poor memory. Apologies. 

No comments:

Post a Comment