Toucan

A superb example.

I used to work at a tech firm, we used this SSL Certificates to authenticate against our internal CA. Sysadmins got it wrong, devs got it wrong, qa got it wrong and nobody else stood a chance.

The worst thing about it by far was managing keys between machines. For example, it made it impossible to work from home on an impromptu basis without someone available to help you out.

To answer the question on how to train it, the RN believes that it's done by pushing people through difficult situations during training and showing what's possible. I'm not convinced it's possible to self-improve grit to any significant level.

It's also reasonably well advertised on TV, radio and at service stations.

I'll check to make sure I'm an idiot by seeing what I can generate from Amazon itself.

openssl rsa -in test.pem > test.rsa

Not sure what the equivalent is on windows though.

I wonder if things have changed or if it was a regional difference. I was in Shenyang at the time.

As for having features missing in the first version, that's also been the Apple way. Release early, release often. See what the consumer actually wants and complains about and include that in the next version.

I do think that the sync cable still isn't very Apple though. I've been hoping that will vanish ever since iOS devices first had wifi capability across the board.

Django phrase it in their tutorial as:

"We've included this with Django so you can develop things rapidly, without having to deal with configuring a production server -- such as Apache -- until you're ready for production.

Now's a good time to note: DON'T use this server in anything resembling a production environment. It's intended only for use while developing. (We're in the business of making Web frameworks, not Web servers.)"

As long as the PHP documentation includes similar caveats and guidance, an HTTP server isn't a bad thing.

You may want to send an e-mail to the http://london.hackspace.org.uk/ list. Depending on size you may be able to use their venue also.

I find this very telling. As far as I can tell, Google made the first public announcement of the Open Handset Alliance in November 2007 and HTC released the first handset in October 2008.

Nokia and Microsoft who should both have more experience and resources specific to the mobile industry than HTC and Google did in 2007 are "hopeful" to even meet this timescale, let alone beat it.

In a year, Nokia will have even further to catch up. I'll admit I may be underestimating the difficulty of getting a new device to market, but it seems to indicate an aversion to risk-taking which may set Nokia even further back than they need to be.

A little clunky, I'll admit. I'd like to hear any more graceful solutions.

Options are:

Application and Distribution signed by: (None/Signed/Signed by Apple)

Apple ID Authentication: (iTunes, MacBuddy)

Server: (Porco, Localhost, Custom)

Show install progress in dock: (Firenze, App, App no launch, Applications stack)

You can also "take the piss" if you're lying, exaggerating or any number of other social mistakes. If someone said that they had 5 years experience in PHP on their CV and you later found out they didn't, you could say they were taking the piss.

Obviously, it's quite an informal phrase. It's also one that just sounds wrong out of context, the correct context being quite hard to define. Like all slang you have to live amongst people using it before you pick up correct usage.

There are pay as you go options, but other than the lightest of users, I don't know many people who find it cheaper than a contract, especially if they use any data.