iamdanw

I've had similar problems with other API contests in the past, either being canceled or the rules being changed post-deadline.

Generally this happens when the contest is run by marketing people as opposed to those from a developer background.

You've just got to build something you'll enjoy making and using regardless of the chance of winning.

Didn't CNet used to use http://com./?

Neat idea with the reader but I guess it'll be limited to the US market since it can't support chip & pin transactions.

I've seen prior art for this, so I should expect not

Plancast needs support for uncertainty. I might be going to this place sometime next week but I'm not sure yet. Perhaps if a friend also says they're going then I'll be more certain.

Similar to upcoming.org's interested vs attending.

There's a large glut of "this new service is like foursquare" submissions over the past few days.

Any idea if the amazon one used EBS for the database? Or the new shiny RDS?

The iPhone has to be on and the app open for it to work. No way around this limitation without 1) jailbreaking 2) digging around in private apis or 3) applying to be an approved accessory maker.

That $5 pre-order is far too easy to do. I bought one without stopping to research other products like the http://www.fitbit.com/. Brilliantly designed pricing.

It's a lot like Glastonbury ticketing. Deposits in autumn, full payment in January. This is extra profitable because in January many people are short on cash post-christmas and either can not or choose not to pay the full amount. You get to keep the non-refundable deposit and then sell the ticket/product again to another person.

As an aside, any idea on how hackable the Wakemate is? Presumably other devices could talk to it over bluetooth, eg a homemade arduino based alarm clock. Will the bluetooth protocol and data format used be published?

A few months ago I saw a bunch of drunken youths on a train heading to a party. Incredibly they were editing myspace profile layouts on their Sony Ericssons and exchanging CSS and html tips. So coding on handheld devices is possible but we are not the target audience. Perhaps more yahoo pipes/yql style coding.