IIRC, you have to encode the key, encode the parameter, append them with '&' and encode again, and then sort them, generate the signature, encode the signature key and the signature itself. Or something. Oh and the encoding routine is urlencode plus some extra characters so that has to be written from scratch too.

Hi Mark, thanks for replying. Do you not think it was a flaw to target a spec towards a specific language/architecture? Another thing that really pissed me off was the complete lack of help testing my implementation. I'd have given up far sooner if it hadn't been for this site: http://term.ie/oauth/example/client.php

I tried to implement OAuth v1 on a mobile device. What a pain in the hole. And it all fell down once you had to get the user to fire up the browser to accept the request. There was no way (I could figure out) to handle the callback so instead it seems to have been implemented via a corporate server thereby defeating the whole purpose of it. The easiest to work with was DropBox. I never got what extra level of security sorting the parameters provided the signature would show up any tampering, it just means you gobble up memory unnecessarily.

I don't see what Symbian had to do with Meego. They were totally independent projects with Meego having a far higher level of secrecy. Symbian had its own developers and Meego had theirs. The problems with Symbian were several-fold: - High learning curve: chipset manufacturers didn't like it as they couldn't get decent developers. India didn't churn out Symbian developers. Their code was typically very buggy and due to low level nature of it buggy code in a driver could prevent any development in the higher levels from happening at the required pace due to development boards (early phone prototypes) freezing up with no way of diagnosing the problem easily; the baseports and higher level development were expected to be done simultaneously. Project deadlines constantly slipped (the N8 was late by about a year). A QEmu simulator was under development but ultimately abandoned for reasons I'm not too sure about. Code would be committed that wouldn't compile... basic shit. This would affect *every* developer as they'd waste several hours downloading the latest environment only to find it didn't work. - Underpowered hardware: It just wasn't up to the job, RAM was never enough. Use-case tear-down and reconstruction rarely worked (related to the point above) - Politics: Symbian was a cash-cow for years and every ladder-climbing manager wanted in. It soon became impossible to get a 'Yes' decision on anything, and if you weren't in Finland your opinion counted for little. It was unclear who was really in charge. - Symbian Signed: 3rd party developers were really shat on. Sure tools like Carbide were free (and fairly decent) but getting an app signed was a joke. I'm not sure how much of this applied to Meego development, I was under the impression they were given a free hand to do as they liked, but Politics definitely became an issue there too when it became clear the project had a future.

How's the parent a Troll? Mod up.

I can't see it happening this way. Nokia wouldn't have developed the graphics drivers itself but received them from the GPU manufacturer (due to the presence of HD protection keys these would have been delivered in binary form only), the baseband code is likely to be full of Nokia's IP and thus would have to be done by someone else (Nokia sold its modem team to Renesas before Symbian got axed) and will probably be of iffy quality. I'm not sure these Meego guys will have access to the radio testing rooms as they did under Nokia. Best of luck to them though

You're the lucky one. Most people are on a waiting list for several months now

Power and syntax of C, safety of C++, useful compiler errors like Java. NO HEADER FILES!!!

You mean someone actually got their Pi delivered?

Not sure, I was sold to Accenture and didn't hang around long there.

I worked for Nokia when the MS alliance was announced. Elop is ex-MS, he brought in some higher management from MS. The company is already drinking the MS kool-aid internally, the takeover is complete in every way except financially. Nokia shareholders would not object to getting the company out of Finland, it's expensive to hire people there and expensive to fire them. Fortunately for MS a whole lot have already been fired.

Not Microsoft. It was even highlighted in the article. Sheesh!

I hate this resolution. I seems to me that screen resolutions have gone backwards, it's nigh on impossible to do any development with this shitty resolution. My old 5 year old Dell laptop supports 1600x1200 compared to my more modern Acer laptop despite the Acer having a far more powerful graphics card. It's not even a native HD resolution so your graphics card has to scale the 720p image up to display it on fullscreen... which totally defeats the purpose of 720p as the scaling hardware is probably crap. It seems to me that laptop manufacturers are shooting themselves in the foot with this crap.

Anthony Zappero has some really interesting things to say about space travel http://www.neofuel.com/inhabit/inhabit.pdf It's a bit scattered but I found it really, really interesting.