Sidingsound

Readers of Eee 701 Planetoid (my blog devoted to the Asus Eee 701 ‘netbook’) may be aware that I’m a big fan of Dropbox, the online storage/file synchronisation service which also happens to work perfectly with the 701. I just wanted to share a quick tip for Dropbox I learned from an article at Lifehacker, which may be of use to other users, especially if they’re running Linux or Mac OS X:

As you may know, installing the Dropbox client on your Mac, Linux or Windows computer, gives you a special folder into which you place other folders or files; these are then copied not only to the online Dropbox storage space, but to any other computers linked to your account. This is very handy, especially if you have a laptop or other portable machine; it’s perfect for my Eee netbook, as I can back up files to Dropbox and my Mac with very little effort.

But what if you wanted to link folders/files on one machine to Dropbox, which aren’t located within the Dropbox folder? For instance, my Eee (running the Eeebuntu Linux OS) has a “Documents” folder in my home directory, and I’d like this to be backed up to Dropbox (nothing sensitive or confidential there, BTW), even though the folder should really stay where it is.

The answer—certainly if you’re on Linux/Mac—is simple: you just create a symbolic link (or ’symlink’—like a Mac alias or Windows shortcut) within the Dropbox folder, which points to the folder (or file) you’d like to link to. In the Linux and Mac terminal, you would change to the Dropbox folder, and from there, enter:

ln -s /path/to/your/item

This would create a symlink in the Dropbox folder with the same name—if you wanted a different name, you enter the new name for your symlink after the path:

ln -s /path/to/your/item alternative_name

(I would recommend symlinking a folder rather than a file for this purpose, just to be ‘tidy’.)

I use this method to ‘place’ my Eee’s Documents folder within Dropbox, so it appears to exist in two places (within my home directory, and within the Dropbox folder). The contents of ‘Documents’ are backed up to Dropbox, and also to the Dropbox folder on our Mac, meaning that in effect I have three copies of each item in the folder.

Check out the original Lifehacker article (“Sync files and folders outside your Dropbox folder“) for more details, including how to achieve the symlinking effect on Windows (basically, if you’re on Vista or Win7, use MKLINK at the command prompt).

Last October, I posted about a small problem which I was trying to work out: how to synchronise the calendars on our Mac and my Nokia N95 mobile phone, with Google Calendar.

Four months on, and I’m sorry to say I haven’t made much progress in the interim. To recap, these are the essentials of the setup which existed prior to last October:

• The N95 calendar synced “over the air” with Google Calendar via the GooSync service.
• The Mac calendar synced with the N95 via iSync on Mac OS X.
• The Mac can also update Google Calendar directly via iCal, thanks to GC’s CalDAV interface.

You may have worked out that Google Calendar acts here as the de facto “master” calendar, i.e. the primary copy of the calendar data. In this setup, the Mac doesn’t have a “local” copy of this data (it connects to Google’s server and displays what’s there), whilst the N95 does have its own copy of the data, but still treats Google as the “master” version.

This arrangement worked fine until last October, when GooSync ended its free service level, in favour of “GooSync Lite” (£5.99 per year). I haven’t renewed my subscription to date, as I’ve been prevaricating on what would be the best option—a lifetime subscription to GooSync Premium is £40, with a fair number of additional features, so that might be worth consideration. (The same service costs £20 for 12 months, and £30 for two years; how likely is it that GooSync might disappear within that time?)

So, at present, I can access Google Calendar via the Web, or via CalDAV (using either iCal on our Mac, or Mozilla Thunderbird (via the Lightning calendar add-on) on my Linux-powered Asus Eee 701 netbook). If I want my calendar synced to the N95, at present I would have to sync the phone with the Mac rather than Google; this is all well and good, but what if I am away from home and therefore unable to access the Mac?

I am also unsure whether iSync will transfer calendar items which aren’t located in the Mac’s own iCal database—i.e. because they’re on Google’s servers instead. For me, this is a wider issue: the Mac and netbook can only display the calendar if they have Internet access (more of a problem for the netbook, as the Mac stays at home). Therefore, I would like to find out whether it’s possible to sync the Mac and netbook calendars with Google (i.e. create synchronised copies on these machines of the events on Google), so that the events can be viewed and interacted with when the machines are offline.

I think I have a few options at this stage:

• “Admit defeat”, and cough up for a GooSync subscription. Otherwise known as the “path of least resistance”, at least this would sort out the N95/Google sync issue. If there are SyncML-compatible clients for Mac and Linux, I suspect GooSync Premium might also solve the “local copies on Mac and netbook” issue above, as GP allows up to four “devices” to use the service; this may require an email to GooSync to clarify.
• Sync the N95 with the Mac (and/or netbook) instead of Google. This would rely on a few “ducks in a row”: for one, clarifying whether iSync on the Mac needs the calendar items to be present in the Mac’s iCal database first. There is apromising-looking “one ring to rule them all” syncing utility for the Linux GNOME desktop—Conduit—which looks like it might be able to act as the go-between for Google, the netbook and the N95, but so far it appears that mobile phones are not yet supported explicitly (no doubt that will follow).
• Some combination of the above—e.g. GooSync for the N95, and other methods for the Mac and netbook.

So, the saga continues—just hope I can come up with a suitable solution before that vein in my head goes “pop”…

Steve Litchfield, the mobile technology journalist and creator/presenter of The Phones Show, made a somewhat poignant comment on his Twitter feed a few days back:

Kind of sad that in 2009, I choose my smartphone based on the premise of “Which one sucks the least” 8-(

I replied via Twitter that the net effect of finding out about the smartphones currently on the market, has been to strengthen my inclination to hang onto my venerable Nokia N95 “classic” until it falls utterly to pieces, expires in a puff of smoke or otherwise “goes to join the choir invisible”. (Obviously, I expressed that within the 140 characters allowed, but you catch my drift )

Whilst it’s no secret that I like my gadgets, I don’t feel the need to ensure that they are the “latest, greatest and up-to-datest”—put simply, if they do what I want them to do, they could look like a potato or run on clockwork as far as I care. The N95 is a case in point: it does many things, it does most of them very well, it is still working fine, the firmware (operating software) is now mature and reliable, and I am genuinely happy with it (and yes, I have watched the competition closely, as you’ll see).

I upgraded to my N95 in the summer of 2007, and whilst it has been superseded by seemingly countless models in the ensuing two years, there hasn’t been a single handset from any manufacturer in my view, which has matched the range of features (and competency at them) which the N95 offers, for a price which doesn’t leave me glancing nervously at the monthly household budget.

Oh, there have been a couple of phones which “came close”, and to name but three:

• the Nokia N82 offered most of the same features as the N95, and added a xenon flash to make it possibly the most capable cameraphone on the market;
• the Samsung i8910 packs HD (720p) video recording and a great screen, but is expensive and only available in the UK on Orange, who apparently “could’ve done better” with the software; and
• the new Nokia N900 “internet tablet” looks great, but again the price is likely to be eye-watering, and we’ll have to see if my network offers it (as I don’t want to switch).

When it comes down to basics, though: quite simply, I’m generally content with my N95, and even more so with the monthly tariff I’m on with my network, which is now really quite modest whilst suiting my needs nicely.

Of course, there’s the question of what I’d do if my N95 failed, broke beyond repair, suffered some nasty accident (dropped in the toilet, fell in a cement mixer, etc.), and I had to replace it. Assuming I couldn’t get a replacement N95 without going on eBay or the like, and I wanted a new phone, there’s only really one handset which I think would offer me similar features (though not all of them) at a fairly low cost, and that’s the Nokia E75. I would be sacrificing two megapixels of camera resolution (and the Carl Zeiss lens) and video editor of the N95, but I would be gaining a slide-out QWERTY keyboard and USB charging (and possibly more), and retaining many of the N95 features I use.

I don’t know if my network would offer the E75 at the time I would “need” it, or if there will be a better alternative by that stage. However, I’m hoping that my N95 has at least a year or two more in it, so I can make the most of possibly the best all-round smartphone Nokia has ever produced. And nearly three years on from its introduction, I think that’s no small achievement.

Last night, I wrote a blog post about the rumours swirling around, that T-Mobile UK was about to be bought by one of its rivals. I put the post together on my Nokia N95 (my wife was on the Mac), but it appears that for some reason my post failed to publish.

Actually, I don’t really mind—partly because the piece was rather poorly-written in my view, but mostly because it has been overtaken by events. This morning, the BBC is reporting that the UK arms of T-Mobile and Orange are to merge, in a deal which would make the combined network the UK’s largest.

My first reaction was dismay—ironically, I left Orange for T-Mobile in 2004, partly because the former had a data package which was behind the times even back then. I have always been very content with the service I receive from T-Mobile, especially in recent months as I’ve been able to go on a very reasonable monthly tariff with Web’n'Walk (T-Mobile’s excellent “all you can eat (within reason)” 3G data package, and I am very disappointed that this might all be about to change.

I suppose we will just have to see what happens from here—particularly, whether this is a “merger” as the report says, or simply T-Mobile getting “Borg-ed” by its larger rival. My special concern is with Orange, as they have a poor reputation in certain quarters for the modifications they make to the firmware of the phones they carry (the Samsung i8910 is but one case in point), though if I stay with my N95 as long as possible, this would be a moot point.

Anyway, whatever happens, I think I’ll start “shopping around” the other mobile networks to see what’s on offer, and hope that for the time being at least, there won’t be much change (if any) to the service I am currently receiving.

Who would’ve thought it—I go away on holiday with my family for a week, ready to photo/video/audio-blog the whole proceedings with my N95, and… well, knock me down with a pot of Mumbles’ legendary ice cream parlour’s finest, if I wasn’t so busy having fun with everyone that I didn’t have time to upload more than a couple of photos to Twitpic. (Incidentally, if you’re ever in the Swansea area and have a bit of a ’sweet tooth’, Joe’s ice cream parlour in Mumbles is an absolute must-visit. Just take our friends’ advice and go for the ‘plain’ vanilla one first, then work your way through the menu…)

So, how did it go? Well, we had a pretty good time, I think, topped off by my (impossible-odds-defying) unexpectedly meeting one of my favourite musician/composers in a folk music instrument store… oh, you mean how the N95 content uploads went? Well, pretty good overall, although I did encounter two “flies in the ointment” with the system:

• Perhaps a bit obvious, but even where you’re fortunate enough (as I am) to be on a 3G network with an “all you can eat” usage policy, that still doesn’t help if the area you’re going to has a low or variable signal strength. I’d almost forgotten the frustration (from my 56k modem-using days) of having a long upload fail almost at the end, because the sputtering mobile data connection gave out at the last minute; clearly, a good WiFi connection is useful here, if you can find one and (if appropriate) don’t mind paying for it.
• Pixelpipe seems to have its fair share of quirks when uploading the same content to multiple different content sites (which is basically the point of the service), using the Nokia Share Online utility on the N95. There’s probably a whole post I could write about these in detail, but in a nutshell, the items you fill out for a new NSO upload (tags, summary, etc.) don’t always appear where you would expect them, when you check your content sites later. For instance, when you upload a video to YouTube, your ’summary’ text doesn’t appear for the uploaded video—YouTube just shows the title of your video where the summary should be.
  To be fair, the problems are almost certainly as much (if not more) due to the content services’ application interfaces (i.e. how Pixelpipe interacts with them), but I have to keep a mental note of what works well and what doesn’t, so I can correct the glitches later.

Oh, and I’m pleased to report that I finally invested in a new 8Gb Sandisk Mobile Ultra MicroSD memory card for the N95 (four times more capacity than the previous card), so no more mad scrambles to find more storage space on long trips where I’m taking lots of video (and perhaps more room for the odd movie or three!).

Must go—I’m installing Xubuntu on an old PC for Naomi. Lots of fun…

A quick update on the weekend ahead: according to the friends we’re staying with, the area where we’ll be going may not have 3G network coverage (or at least not as much as I’m used to), and we won’t have any WiFi.

This means that whilst I should be able to get some Twitter and blog posts out (providing there’s at least GPRS or GSM data), I may have to wait a couple of days to upload any batches of photos (and more likely, any videos) I take while we’re away. Be sure to keep an eye on my Twitter feed and this blog for updates as I have them, and hopefully I’ll have more 3G access than I’m expecting to.

Posted by Wordmobi

This seems to be a time for following up on previous blog posts, so here’s another one “revisited”:

Back in May (when this blog was still run off Blogger), I wrote about how I’d really like to find a “hard” carrying case for my Apple wireless keyboard, which I use a lot with my Nokia N95 as an alternative to a laptop.

Basically, I haven’t been able to find one to date—I suspect my particular application for the keyboard isn’t a very common one—so at present I use the cardboard box which the keyboard came in, to protect the keyboard when it’s being carried in my gadget bag (and believe me, without protection, it would really get beaten up in there).

The box works, but I’d rather like a more elegant solution. The nearest I’ve found online is a padded “sleeve” case made especially to fit the Apple wireless keyboard, but nice though this is, it wouldn’t necessarily prevent the keys being pressed whilst the keyboard’s in the gadget bag, and I’d rather avoid this happening to save the keyboard’s batteries (and the N95 responding to unwanted key signals).

I’ve been thinking more about what I’d want in a hard case for the Apple keyboard, and here are a few of my ideas:

• The case’s dimensions should be quite close to that of the cardboard box which the keyboard came in, including the recess to accommodate the cylindrical part of the keyboard which holds the batteries and the power switch, and tilts the keys off the desktop.
• There should be some measure of foam rubber padding inside, if that can be done without increasing the case’s size much.
• I’d like to be able to use the keyboard inside the case (i.e. lift the lid, and it’s ready to go)—think of how a laptop works, and you’re on the right track.
• Related to the above point: if possible, the lid should be “angle-able” like a laptop’s screen, and I’d like to be able to place the N95 on the lid so that I can see it while controlling it with the keyboard. (In concept, this would be a bit like the phone holder on the Nokia SU-8W Bluetooth keyboard.)
• Definitely not essential, but a carry-handle might be useful, a bit like those you see on briefcases (and preferably smaller than those).

I wouldn’t really mind what material the case was made from, as long as it worked as set out above (and wasn’t liable to give me splinters or damage anything near it).

It’s at times like these that I wish I were more “handy” with DIY, software-coding and that sort of thing…

Posted by Wordmobi

Musician Bing Futch has just posted a blog entry, marking fifteen years since he first went online at home, which got me thinking about a few of my own “Internet milestones”. Set the time machine going…

• I don’t know the exact date, but I am sure that I got my first Internet connection from home in 1996. My PC at the time was running OS/2 (long story), and the internal 28.8k modem cost around £200—this was relatively cutting-edge technology in the UK at that time (with a price tag to match), and the 28.8k standard was still relatively new.
  (As an aside, the Web server space I was given by my ISP was a disk-stretching 500Kb. Many single Web pages I visit these days weigh in at more than that alone.)
• We think of data services via mobile phone networks as a fairly recent phenomenon, but by 2001 I was getting online via my Nokia 6210i (and shortly afterwards, a 6310i, which gave me GPRS speeds) and my Psion Series 5mx, over an infrared link. I vividly recall spending Christmas 2001 with family at a cottage in the wilds of Dorset, sending festive greeting e-mails from the Psion over a shaky GPRS/GSM data link, to my then fiancée in South Korea—we would marry in Seoul just over two months later.
• Thanks to the positively mediaeval cable network in the town I was living in from 1996, I didn’t get broadband Internet at home until we moved to our current home town in late 2003. (This was despite seeing my first “always-on” cable modem connection on a visit to a US colleague’s California home in 1998, and coveting it massively (the cable modem, that is).) We finally got a cable modem in our first house here, switching to ADSL in 2006 when we moved to where we now live (there’s no cable TV in this new part of the town yet).

Now, of course, in 2009 I take ADSL and 3/3.5G mobile data more or less for granted, and it’s hard to believe that I didn’t even own a PC until 1993 (and didn’t get a ‘modern’ one until after Easter 1994). I can only imagine what I’ll be using by my fiftieth birthday, but I’m pretty sure it will be as unremarkable by then as a telephone or TV set is today.

It’s coming up for two weeks since I migrated my blog site across to a new host, and to a new blog ‘platform’ (WordPress). So far, I’d say I’ve managed to realise most of my early aims, which to a great extent revolved around creating a blog with tie-ins to the various multimedia services I send stuff to, and which as far as possible I could maintain from my Nokia N95 without needing a desktop or laptop.

Whilst I’ve got a fair amount of the ‘auto-update’ functionality working (insofar as I can send something to YouTube, Qik, Flickr, etc. and it’ll appear somewhere on this site automatically), there are still a couple of ‘holes’ which I hope I can work out how to fix:

• I haven’t yet found whether it’s possible for YouTube to post automatically to WordPress, when I upload a new video. YT can update Twitter and Facebook automatically, and you can set up a WordPress blog on your YouTube account, which gives you a “blog this” feature on a video’s page. However, I have yet to try YT’s mobile site to see if the “blog this” feature is present there; if not, it’s not easy to access the “full-fat” YT pages from a Nokia N95, so some kind of totally automatic feature for posting new YT videos to a WP blog upon upload, would be useful. I’m guessing it already exists, but just haven’t tracked it down yet.
• In a previous post, I referred to my search for an audio equivalent of YouTube—i.e. a Web service where I could upload short, impromptu voice recordings which would then be cross-posted to this blog. After I posted this here and on Twitter, someone from ipadio dropped me a line—this is the service which allows you to make a voice phone call, and have the audio from that call uploaded straight to the Web (they call this “phlogging”). Apparently, ipadio is working on allowing users to upload pre-recorded MP3 audio clips, which may address my primary concern with ipadio (the limited audio quality of a phone call), so I may well be giving their service a try shortly.

Otherwise, I feel I have more or less got the whole infrastructure to where I wanted it at this stage. Other future developments I have in mind are:

• a “music” section, where you’ll be able to listen to some of my recordings (probably via an embedded Flash music player at first);
• an expansion of the “lifestream” feature, so that each day on the main blog page will carry a summary of the day’s content from the lifestream;
• the “contact” page, which I know I haven’t implemented yet, but I have to make as sure as possible that I won’t expose myself to any more spam than I already get (no offence meant, incidentally )

Anyway, I think that’s enough to be going on with for the moment, wouldn’t you agree…?

Posted by Wordmobi

A very quick note (as I’m entering this on the mobile via predictive text input!) to say that the Sidingsound e-mail addresses should be back to normal now, for those who know them.

Users of mobile devices may also like to know that they can now visit the usual URL for this blog, and get a mobile-friendly version served up for them. (WordPress rules )

Posted by Wordmobi