If you are specifically targeted, you're probably screwed no matter how good your security is. If the attack isn't getting through remotely, it may escalate into social engineering, or even into physical attack, up to and including physical keyboard bugs and monitor signal sniffing.
If you're not specifically targeted, and are merely part of the crowd, you don't have so much to worry about, because you can play the numbers game. All you need to be is more secure (a couple of standard deviations) than the average. In these circumstances, security through obscurity is statistically measurable: yes, in the binary sense it's wrong to think of obscurity giving you security, but in the practical sense, it measurably decreases your risk of being compromised.
Means that the client is not only authenticating the server, but the server is also authenticating the client.
Client cert interfaces in browsers are fairly user friendly, and github already has user keys, so they may as well make it an account option.
The solution to FireSheep is something akin to SSL (robust, fast encryption with authentication). Could be SSL, or a VPN, or an SSH tunnel doing SOCKS.
Beware the MITM attack if you think all you need is encryption without authentication.