Over the past couple or so weeks my Macbook air has started to develop a minor, but irritating, hardware problem. Simply put, the left shift key fails now and again. I can press it and it does nothing. It's irritating because it messes with the flow of typing (especially when writing code) and the key also feels like it's sticking or clicking in a way that's different from all the other keys.

Given that I pass through Edinburgh on a pretty regular basis I thought I'd drop in and have a quick chat with someone about it. While I didn't expect a fix there and then (although finding out it was a trivial issue would have been nice) I was hoping someone could take a quick look and let me know what might be going on.

So, this morning, on the way to Waverley Station, I dropped in to the Apple store on Princes Street.

I walked in and looked for a member of staff, all seemed to be busy to start with but one soon noticed that I looked a little lost and asked me if they could help. I explained the issue and she said I needed to pop upstairs to chat with the staff up there.

So far so good.

So, I headed up to the first floor and caught the attention of another member of staff. Having explained the exact same thing to them I was told I needed to speak with yet another staff member. The chap I needed to speak to had a queue (yes, a physical queue of people) waiting to speak to him.

I joined the queue.

About five minutes later I got to speak with him. I, again, explained the problem and was told that looking at it would be no problem and they could do so at around 4pm. This was at about 10am. Having gone through 3 people and spent 10 minutes doing so I found out that there was a six hour queue to have someone actually take a quick look at the issue.

By that time I wouldn't even be in the same country, let alone the same city. So I had to say thanks but no thanks.

So now it looks like I have to make an appointment for some point in the future and make a special trip into Edinburgh just so someone can check out a sticky key on my Macbook.

Remind me again how the nice thing with Apple gear is that it "just works"...

Earlier on today I needed a copy of wget on my iMac. It's not "native" to it so I got to wondering how you go about getting something like that onto it. Sure, I could have just grabbed the source and built myself, but really it's a lot nicer to use some sort of package manager.

A quick search lead me to Homebrew and I was then up and running in no time.

This in turn got me to thinking about how it might be fun to get some of the software I used to use on my GNU/Linux machine up and running again. The first one that came to mind was slrn. Sure enough slrn is available via Homebrew and installing it was dead simple.

But then I was faced with a problem: I needed an NNTP server. Way back I used to run a local one in my office that fed from and to my ISP's. Back then my ISP was Demon Internet; these days I'm with BT. A quick search lead me to an article or two that BT had a NNTP server, of sorts, provided by a third party. So I did a quick check:

Yay! This looked good.

After that I fired up slrn and.... problems. It kept asking me to log in, to provide a user name and password. The only problem was that I'd read in more than one place that a user name and password weren't needed for BT's server; all that was required was you be on a BT IP address. Checking the slrn docs I found force_authentication but ensuring that was off made no difference.

At this point I removed slrn and gave up.

Later, thinking it might be an issue with just slrn and perhaps it was worth trying a native NNTP client, I grabbed Unison (which is no longer supported but seems to work fine). I got that set up and ran into the same issue: it wanted login details.

Finally, after a bit more digging, I stumbled on the reason why I was struggling to make any of this work: BT had closed support for the server back in December last year!

A quick search around the web and I stumbled on Eternal September. Given all I was interested in was the good old text groups this looked perfect. I quickly registered an account, ran up Unison again and plugged in my details and....

Now that's all sorted I should try again with slrn. At which point I'll need to drag out and tidy up post.el (the version that was being maintained by some other people seems to have gone very stale, sadly).

A little earlier today I decided it was time that I read up a little more about the abilities of OS X's Spotlight facility. I use it a little -- it's a handy tool to get at some often-used applications that I don't really need laying around in the dock -- but I was starting to wonder if I could get more out of it.

The obvious first place to look was in the HelpViewer; all the information I'm ever going to need will be on the local machine, right?

So I open the HelpViewer, from the Spotlight bar, and type in that I want information about Spotlight. The page comes up blank. The page was pretty small so, while I pondered why it might be blank, I resized it and it disappeared! I tried to open it again and.... nothing. Nothing I did would make the HelpViewer show again.

I then tried following the advice on this page but none of that appeared to help. I then looked for the HelpViewer in the Activity Monitor and killed it with that.

Running it again after that got me back to where I started. I tried the while process again and, sure enough, trying to resize the window made it disappear. I can make it happen every single time:

So it looks like another fine example of the Apple "it just works" thing. For "doesn't always just work" values of "just works".

As much as I like my iMac, and as much as I am generally impressed with OS X the more I use it, I'm constantly frustrated by the little issues I run into that make life so much more interesting and which fly in the face of the "it just works with Apple" fandom thing. The more I use the iMac, the more I appreciate that Macs and OS X are just as "fun" as anything running Windows.

A little earlier was a good example. I wanted to share part of the iMac's filesystem using SMB. This seemed easy enough, the instructions on how to do it were clear and, after following them, it utterly failed.

Brilliant.

So I Googled the issue a bit and ran into this handy forum post. Apparently you can't actually connect with SMB if the account you're going to be using to connect with is using iCloud login rather than a separate login.

Brilliant.

Not an obvious thing. Nothing said this was the case. According to the forum post even Apple couldn't help the person who'd been trying to make it work. But at least there was a workaround. All I'd need to do is split the password, have a login for the machine that wasn't the iCloud login and I'd be all good.

I did it, it worked. I could browse the iMac's filesystem from my Windows machine and all was good (I'd been able to do this the other way around for ages and with no problems whatsoever).

Then I got curious.

What would happen if, once I had this set up, I "unsplit" the password and went back to using the iCloud password to log in? That's when it got really fun.

To do this it asks you for the current password and also your iCloud password. I entered both and...

Yup. It refuses, every single time, to accept that the iCloud password I'm entering is valid. Trust me, it is. I'm entering the correct password. I can log in to the iCloud website with it just fine. But when I use it to try and "unsplit" my password.... nope.

Brilliant.

I've even tried disabling SMB sharing for my account, and even turning off SMB sharing altogether. This doesn't seem to make any difference. Right now, as far as I can see, now that I've split the password I can't go back despite the fact that there's a method of doing it made available.

Brilliant.

Apparently that famous Apple obsession with design doesn't apply to the time display on the OS X login screen (the wake-from-sleep password confirmation one anyway):

I've never noticed it before. I'm not sure if this came about with the upgrade to El Capitan or not. But now I've seen it I can't unsee it.

Almost a week ago (yes, I have being meaning to write something down about this and have kept failing to do so) my iMac told me that there was a new version of the OS waiting for me. While this is doubtless no big deal for most Mac owners, this was interesting to me because it's the first time I've experienced an OSX upgrade since I got the iMac.

The download took a while and, while the install had a couple of curious bumps along the way, nothing seemed to actually go wrong.

The two main things I noticed were that it seemed to take the installer an absolute age to close down all running apps before it got to doing the installation. The other was that Mac progress bars seem to have a very odd way of calculating things. Often it would tell me that there was (for example) 28 minutes to go, it'd stay like that for 20 minutes, then drop 5 minutes, then appear to finish very soon after.

Mostly though I just left it alone and let it do its own thing. While the whole process took quite a while, it came back just fine (if I'm fair I'm not sure it took much more time than when I upgraded my laptop from Windows 8.1 to Windows 10).

The changes and improvements aren't really that obvious. I think I would say that the machine feels a little quicker in places, but nothing I can really put my finger on. One of the things I do like is the new split-screen facility for full-screen apps. While I don't use the full-screen facility that much I have found the need to split the screen before.

Some of the other improvements I've read about seem to involve things I'm never going to use: either improvements to Safari (Chrome all the way for me), the Mac Mail app (Gmail all the way for me, with Kiwi for Gmail being my client of choice on the iMac) or various iOS-oriented things which are of little use (while I do own an iOS device it's not one I use much).

Overall the thing I'm taking away from this is that the upgrade was smooth, nothing was obviously broken or changed in a way that was confusing (unlike some Windows or ChromeOS updates I've experienced in the past) and I didn't have to do anything that required much in the way of knowledge to keep it all going.

Doubtless that won't always be the case, such is the nature of OS upgrades.

Oh goodie! An update for Adobe Creative Cloud on the iMac!

Oh! Improved update experience too! I really must install this then...

Well fuck.

Last night, before heading for bed, I noticed that there was an update available for OS X on the iMac, and also for iTunes. Despite the late hour I decided to do the update anyway. OS X updated pretty smoothly (albeit with some rather unhelpful progress bars that appear to give estimated times that have no relation to reality), as did iTunes.

I was then told that there was an update for my iPod as well (all part of this new thing where Apple have invented Spotify, obviously). I let that start doing its thing and that's where things got odd. First it started the update and the iPod appeared to insist that it wasn't plugged into the iMac, even though it was. Then I gave it a second go (after unplugging it and plugging it in again) and it all seemed to go through just fine, only...

...while the iPod was pretty sure it was now running iOS 8.4, iTunes on the iMac had other ideas:

The following morning iTunes kept insisting that it needed to do the update so, even though the iPod was obviously up to date, I let it do it anyway. After it'd gone through the update process again it still insisted that the iPod was running 8.3 rather than 8.4. Until, that is, I unplgged it and plugged it back in again.

So now it all seems fine. I just had to do a variation on "have you tried turning it off and on again?"

Once again I find myself running into things on a Mac that are very common elsewhere, on other operating systems, and which Mac owners would often have you believe weren't an issue.