Kerrz

The OP's link is from Dec 27, 2007, while this link is from Aug 2007.

The actual presentation from 24C3 is available at https://www.youtube.com/watch?v=8lywXCZogsg

This submitted link bypasses the LWN paywall.

If you support articles like these, please consider subscribing at https://lwn.net/subscribe/Info

It was less of an immediate safety concern and more a case of trying to limit the variables. They were only doing tests under ideal conditions, rather than testing in all conditions. I imagine the plan involves testing in all conditions eventually, but they need to fine-tune their equipment in ideal conditions to make sure they know what "good" and "bad" look like before potentially feeding some atmospheric action that they didn't anticipate.

I actually worked in the lab with Louis' team this past summer (completely unrelated projects.)

If the wind was going faster than a couple miles per hour, they couldn't even turn their prototype on to run their tests. I think the biggest problem they're having with going big-picture with this is doing the due-diligence to prove it's not a tornado machine.

I actually set Google Calendar to send me an email at 6pm every day to update the tracker.

But I'd rather it didn't send me an email if I'd already updated.

Hi Matt,

It looks great. I really like that there are simple answers (yes/no!)

I wish there were a notification system, though. Like an option for "If I haven't made a report by ?pm, send me an email to remind me."

Or "If I haven't made a report for x number of hours, remind me."

Maybe implement it as an opt-in and opt-out list that's stored separately, so that your server doesn't have to poll every single account all the time.

The hardest part I have of tracking is remembering to track, and that would really help.