Brucewar -- your entire argument boils down to: "I have good sitters and have never had a problem, therefore this isn't an issue." It's like saying you've never been robbed so you don't see why we need locks on doors. It's absurd.

So one major problem:

Let's say Dukasaur is sitting for me.

If there is a switch for me to turn him on and off, then he can't just sit my turns when I am away from home for an extended time (since I would have to activate him in advance).

If there isn't a switch, and I can just have another ...

Any solution would be better than what we have now. We just had a total mess in my clan because of this absurd security failure.

Here's my suggestion for a relatively small project: start with games. Allow a method for assigned sitters to take turns (including in game chat) using their login ...

get someone you trust exchange passwords and cell phone numbers, call them tell them to take your turn if u have something un expected come up

This is not a fix. This is a bad hack. Everyone who knows anything about security will tell you never to share your password. There is no reason that ...

Concise description:
The sitter situation is a massive flaw. It is absurd that I should have to give someone full access to my account, including my password, to have them take one turn for me.

Specifics/Details:
There have been several great ideas on how to implement this. Any of them will be ...

Correction, the game to watch looks like 12349640 -- that should be 31. So hyposquasher can stop worrying about Hive.

Sorry if I was misunderstood here. If you look at my original comment (which I admit came out sounding a little salty) really all I meant was that you guys are going to beat us in ...

Correction, the game to watch looks like Game 12349640 -- that should be 31. So hyposquasher can stop worrying about Hive.

If you're not watching the hive game Game 12388459, you 're missing out. It's about to get really good. Both sides fully loaded with cards and the first cash about to happen.

Time for a scoreboard update. Gone from 18-17 to 18-22. Still far from over but increasingly looking good for us.

AFOS has had as good of a second round as we had a first round. This is looking like it's going to be extremely close.

Dako wrote:

Emmdizzle wrote:12215034 3 Kingdoms of Korea....another win for AFoS.....7-1 now

What is the forecast for 1st batch? This looks like a disaster for AoC.

Not as quite the blowout as we're seeing right now but still pretty serious. My best guess is 14-6.

And it's now a 5-1 lead for AFOS!

Amazing match. Huge skill and huge luck on both sides. Regardless of how these last two end up; it's been a great match!

Just what I wanted for father's day -- a fisting! Oh, and the really nice breakfast that my daughter & wife made me.

An absolutely untrue and abusive accusation. rbelgrod is exactly the sort of pro-active organizer that makes this site work!

Sorry for the delay. Score has been updated.

Score updated.

Leehar wrote:12-7 now, tho it sucks that you look like sweeping all the home quads

Score updated; this is actually going to be pretty close for the first half.

Leehar wrote:Xayton missed a turn in one of our games? Is everything ok with him? Think he managed to take all his other clan turns in the similar period tho.

We asked a couple of our guys to skip turns, just to make it a bit more fair.

Well at least we can't say they don't have a cheering squad

In spite of that, I'm actually surprised how well my away trips are going, and I know it's not gonna last, but it's nice that you guys haven't won on any of our home games yet :ugeek:

Only one has finished so far! Do you want a list of ...

OK -- figured it out. I was looking for conflicts in other GreaseMonkey scripts. It was actually the firebug console -- no idea why.

Even with that disabled, I'm still getting the "window.initLightbox is not a function" but it doesn't seem to impact the functionality so I don't really care.

Upgrading to 0.9.11 fixed the problem.

Bizarrely, I'm now getting the error message (as a popup alert): "window.initLightbox is not a function" but it doesn't seem to impact the functionality.

Got something hopefully useful with the script error console:

"Error: Greasemonkey access violation: unsafeWindow cannot call GM_getValue."

Here's the source of that link:

<api>
<page>1 of 1</page>
<games total="1">
<game>
<game_number>9687050</game_number>
<game_state>A</game_state ...

I'm getting the endless "Processing watched games" spinner.

Using WTG 1.4.2 w/ Firefox 6.0.2 and Greasemonkey 0.9.10. I am using other CC plugins but I get the same error when they are disabled.

Here are my current applicable preference values:
greasemonkey.scriptvals.http://userscripts.org ...

First blood to Nemesis but I'd recommend they not get cocky. We've got leads in several other games.