gnok

All I see is a message that says "This video is not authorized for playback on this device". I'm using an iPhone to try and view the page. Not sure what content the video has, but I'm pretty confident I'm no longer interested.

Not to be a pedant, but that's 'wary' and not 'weary'. :)

Second that. I especially liked the last chapter where the author discusses some implementation techniques to get you going.

Amazon link: http://www.amazon.com/Introduction-Genetic-Algorithms-Comple...

How about a tabbar at the bottom? Presumably with tabs for settings and transaction histories and so on? You could have your own tab bar design to go with the design of your app.

I'm continuing to test your app out (its Friday; great excuse to go out drinking with buddies! ;) ). I'll get you more review later I suppose.

Quick short Review:

* Great idea. This sort of app is extremely useful, especially for students at univs * I'm not sure I like the app title at the top of the page. Its a low-res picture and doesn't look good on my iPhone 4. I realize you're going for a skeuomorphic design with the UI, but I somehow feel the title feels "out of place". Can't really put my finger on it though.

* I find it a little confusing to enter total amount with tax and then enter the tax again. When I split with friends, I usually don't think too much about the tax.. Perhaps you could ask for the "amount to split" and leave the tax bit to the user?

* The two buttons at the bottom seem out of place, given the design of the rest of the app.

* This is more of a 'feature request' i guess, but it would be nice to have a history of transactions, with support for IOUs. Very often, one of us in my group won't have cash or be owed money or something of the sort, and an IOU gets in the way.

* Could you let the user email this to contacts? This way, all members in the group have a record of what happened.

Motorola's official response is that the eFuse device exists to disable the phone (aka switch to recovery mode) when unauthorized software is run, and _re-enable_ it when the original Motorola-approved software is installed. They claim that the phone is disabled only temporarily and not bricked. Source: http://www.engadget.com/2010/07/16/motorola-responds-to-droi...

(Sorry, I couldn't find the original Motorola post)

Does anyone know what material is used in making those cone-like pokey things? My immediate guess would be that its some form of dense foam to damp waves; but what exactly are they?

My bad; I had misread the other story. Thanks for the correction..

That's a bit of a strawman argument. There's a wide gap between the "totally trust" and "do not trust" groups. I would think most people would fit in that gap. The ones who do go elsewhere are in the "do not trust" group. I can't be sure, but I would think the "totally trust" and "do not trust" groups are minorities in Google's user-verse.

This is not entirely true. The seal in place is considered temporary until a pressure test can be completed. This is expected to be completed within the next 48 hours. If that test is not successful, then this seal comes straight off and the leak resumes.

The release notes themselves don't have any mention of a fix to the proximity sensor, but I see conflicting reports of "its fixed!" and "its still there" on blogs all around. I guess it will be at least a day before people start to notice any difference.

I wouldn't go so far as to say 'overrun', but I'm certainly seeing a lot more spam recently (last 3 months or so) than before.