sxa's Technical Musings

[ Short link to this article if you need it - http://goo.gl/kfESIw ] Just in case anyone sees a tweet of mine tagged with #OneFortyOne , it came about when one night I was listening to music into the early hours and decided to post a tweet with some lyrics from the song I was listening to at the time ♫. Afterwards I added the text "(No-one will read this at 1:41am will they?)" So from then on I decided that if I was listening to music at 1:41am my time I'd tweet some lyrics from whatever I was listening to, and it'll always be tagged one #onefortyone. So now you know. Why not try it too - lets be honest - any followers in your local time zone up at that time aren't going to be looking for any particularly intellectual tweets anyway :-) (Having said that , rather inevitably someone in another time zone (Canada) pointed out that it wasn't 1:41am!) If you want to follow my listening habits, which will usually include any #OneFortyOne entries, then you...

*UPDATE* it seems they may have backtracked on this change . *UPDATE 2 1 Mar 2011* And are now going to re-enable it anyway after the initial storm has blown over: I just read the Inquirer article on Facebook's address/phone exposing to apps. It appears that they now allow 'application' developers to gain access to your address and mobile number. Now I suspect it's not coincidence that the new facebook profile encourages you at the top to specify your hometown ... I guess we now know why. Along with places information in your profile, it's all a criminal needs... Facebook's privacy options are rapidly becoming unacceptable. It's bad enough that the average user has more interest in being allowed to play games or see 'OMG look what Justin Beiber did...' than bother to think about what the 'allow this app to access your information' actually means. Seriously, what proportion of facebook users do you think have ever looked at the list of thin...

Shortened link to this page if you need it - http://goo.gl/D1Ijz [ EDIT 9 Feb 2011: A leaked memo from Nokia's CEO admits problems, and confirms several of the points I made in this article. They're making a significant announcement this Friday] [ EDIT: 11 Feb 2011: Nokia have offically announced a tie up with Microsoft to use Windows Phone] Nokia has had a lead in the worldwide smartphone market for some time. With a range of Symbian devices they had an exceptional amount of market share and held a dominant position. But then it all went wrong, and fundamentally it was because they didn't push the product in the correct directions. I wish it wasn't the case. Here are my top reasons why the Nokia/Symbian combination is declining: Binary incompatibility - The change from S60v2 to S60v3 meant that all applications had to be recompiled for the new devices, and that meant that developers had to ship and support two versions of their software to cover all devices. And a...