Blacklisting lcharles node might be a bit extreme.  If it was done by lcharles setting his node then it probably wasn't intentional.  I don't think it's lcharles' blockchain reset because the blocks between 277021 and 278461 would have been forged with his account.  The last 100 blocks or so that I can see on both clients were forged by NAS-5HZF-TPQ5-GSHF-7GV33 (User123456789?).  Even if lcharles forged one fork, reset and forged the new fork, the blocks would still have his account on them from either fork.  I'd almost think lcharles was on a fork before the lease was set, started forging on his own and the rest of us didn't agree and accepted forged blocks from the 2nd highest forger.  That doesn't explain how I got stuck before the rest of you though...

To speed things up in getting this fixed quicker, I'd suggest we find a chat room for everyone with a node, compare chains, find a solution (hopefully without resetting bter) and going with it.  My access to IRC networks is limited most of the time being at work but I can join XMPP chat rooms any time.  If everyone agrees, let's set a time and discuss...