Wired thinks it's "probably a complex bug"? I think probably not, it's probably something blindingly simple, and stupid.

because it would be so delicious to see spammers fubar themselves.

SSH login attempts from hundreds of different IP addresses. Could not get my IT department to block the port at the firewall. It's an old Mac OSX server - thus, why the POS locked up within minutes of the attack starting. Come to think of it, I haven't used SSH for ages. I always ARD into it to administer. CLICK. No more SSH.

At least it made me review my server security. I was way too lax, knowing how little value the data, or even the server itself, has. But the attack itself still annoyed me, so I tightened that bitch up real good (well, as good as you can tighten up an old Mac server).

Yeah, where are mod points when I need them? Mod parent up.

A touchscreen - especially one on a voting machine - that supposedly needs re-calibrated every few users is pure bullshit. PURE bullshit.

I work in A/V control systems and deal with touchscreens every day. Some are used very heavily - not quite as much as a voting machine on voting day, but probably gets as many touches within a few days time. The need for re-calibration is rare; I'm talking once a year maybe? The worst touchscreen I've ever seen is a the wacom overlay on a Modbook (Macbook repackaged as a touchscreen tablet PC). That POS needs re-calibrated about... once a month. Add other's comments about all the touchscreen kiosks in airports, etc.; same f*ing technology, but they don't need recalibrated every 10 minutes.

There's just no way this isn't a case of either gross negligence / incompetence, or criminal vote rigging.

= Redundant Array of EXPENSIVE Drives.

Up Friday normal, go to work, pack up a truck full of tech stuff, travel to event site, spend the entire day, evening, night with physical setup work and dealing with registration data, then keep at it next morning more regitstration data, running event, more physical breakdown labor, then spend all night doing results data and making a presentation, then spend the rest of that day breaking everything down and hauling it back to work. About 70 hours. I did this 5-6 times, usually got injured doing breakdown work the 2nd day, and the event results? They sucked, and I always got my ass chewed out about it. I finally quit the job. Now, in my mid 40's, I can't even do 24 hours straight. Oh well.

I think my son would find that VERY cool.

We had those on Star Trek 50 years ago too. Just figure those out, and everything will be all right.

Wouldn't that be freaking crazy if gravity changed +/- 30% on a not-very-predictable schedule?

Avg. 6.7 productive REALLY working for my paycheck hours per day. Rounded up to the 7-8 option. This is based on almost 2 solid years of daily time logs. I'm even writing down on my log for this time "surfing slashdot." w00t!

Man, look a BBedit go! And 5 of those votes now are mine!

It's the best way to expose the problems so they can be fixed (instead of hand-wringing and confusion). Glad to read that some stations are turning off analog anyway.

But that's OK, I can wait a few more years for my life to be that fucked up.

You might think injecting the money at the bottom of the economy would do better at stimulating the economy than letting it gather at the top. Until you realize that Wal-Mart is just a short-circuit from the bottom to the top. Next idea, please...