iPhoto feature: drag folder create event or album

I've back on iPhoto 2008, but I suspect this is still true.

If you drag a desktop folder of images to an empty area on the iPhoto album list you get an album named after the folder.

If you drag the same desktop folder to the iPhoto Library:Photos icon you get an Event named after the folder.

I used to do the former, lately I prefer the latter.

iPhone development - an overview for the curious

via DF: Matt Legend Gemmell – iPhone Development Emergency Guide.

I'm not an iPhone developer, but I still enjoyed this. It's a great way to understand more about how the iPhone is put together.

Great article.

Time Capsule's nearly Fatal Flaw

Apple customers need more spine. This fanboy isn't nearly ballistic enough (emphases mine)...

Mac 301: Time Machine backups after your Mac's brain surgery

... Replacing the logic board is essentially like getting a whole new Mac; though all the data on the hard drive is identical, the new logic board will have different hardware identifiers (specifically, the MAC address) that will tell your Time Capsule, "This is a new Mac that's never been backed up before. Please treat it as such." The Time Capsule, doing as it's told, will fumble along and create a new Time Machine backup while ignoring the old backups completely.

Your options then are these:

1. Scrap your old Time Machine backups and start fresh. There may be an allure to this, but it's almost certainly unnecessary, and you can lose months of perfectly good backups. Plus, you then have to deal with the incredibly long first Time Machine backup all over again.

2. Hack your Time Machine backup using the following procedure, which will allow you to resume Time Machine backups as though your logic board was never replaced.

So you send your machine to Apple to get fixed, confident that you're fully backed up with Time Capsule.

Your machine returns in great shape with a wiped drive. No problem, you think, you've got Time Capsule ...

Oops. Your backup is worthless unless you can hack the backup image...

Excuse me, I need to breathe into a paper bag now.

Ok, I'm back.

Apple's forums have lots of threads on the topic, like this one. It seems poorly documented, but if you have the Time Machine icon in the menu bar (set via Time Machine preferences) and you option-click on it you get a "Browse Other Time Machine Disks" option.

I found one kb article with some information for Time Machine and another for Time Capsule ...

Restoring an existing Time Capsule backup to a new Mac
When your new Mac starts up for the first time, you are asked if you want to transfer information from another Mac or volume (in the "Do You Already Own a Mac?" window).
Click "From a Time Machine backup or other disk."...
... Time Capsule appears as a Backup Volume. Select it, then click Continue to proceed.
Enter the password for your Time Capsule...

Except that doesn't make sense. What if there are multiple machine backups on the Time Capsule?

I suspect there are workarounds, but it confirms my feeling that Time Capsule is half-baked.

BTW, there are interesting issues with FileVault such as ...

Note: If you use FileVault, your Home folder is backed up only when you are logged out.... If you use FileVault, you cannot browse for individual items in your Home folder. However, you can restore all files and folders by using the Restore System from Backup feature of the Mac OS X Installer

iPhone encryption is 3GS only – and how the data disappears

I read of iPhone 3 encryption at launch time, then heard no more of it.

I wondered where it had gone.

Turns out it's 3GS only dedicated hardware encryption, and it's invisible to the user ...

TidBITS Safe Computing: iPhone 3GS Offers Enterprise-Class Security for Everyone:

... According to Apple, all data on the iPhone 3GS is encrypted by default...

Great feature, though I'd like to see the ability of 3rd party apps to use it app-specific longer pass-phrases.

Update 7/21/09: I think Gruber pointed out that remote wiping doesn't require removing all the data, just the unique decryption key. So the data is still there, but it might as well be on the far side of the moon (unless there's a backdoor or a big math breakthrough ...). A NYT article on ‘vanishing’ data is relevant – the way to make data “vanish” is to require access to a centralized decryption key that can itself disappear. See also – DRM and the case of the vanishing Orwell.

MobileMe (.mac) and the OS X Console - bug and the console dock bounce

I've been trying to track down an odd 10.5.7 software bug.

Every 1-3 days, my user session browsers hang. I can ping the net and browse the LAN, but Safari and Firefox are unable to get secure sessions or access the net (I need next time to check if email works).

Weird.

Anyway, to investigate this I launched the OS X Console app (called ... "Console) and studied the output. I didn't see that much about the browsers, but I saw a series of recurrent ".mac" sync requests that were failing. I looked into my MobileMe PreferencePane (new name for .mac) and I still had the credentials of a MobileMe account I was trying. I'd canceled the trial account, but the OS was still trying to sync it. I clicked 'log out' (or equivalent) and the problem went away.

So there's a 10.5.7 bug with discontinued MobileMe accounts. If you discontinue your MobileMe account, be sure to "log out" of the old account in the MobileMe PreferencePane

The Console's an interesting place to look for odd problems, in much the same way as in XP one checks the admin event monitors. It does, however, have issues of its own. It transiently uses 100% of my G5 CPU, and it has a very obnoxious bounce behavior. Every time a line is written to the Console it bounces in the dock to get my attention. I admit, I can't ignore the bounce.

I'm sure there's a way to kill the Console dock bounce, but a Google search didn't turn it up. (You can, however, toggle all bounces via the terminal).

Now back to that networking/browser/http bug ...

Update: I have to laugh. There's a Console.app preference for "when an open log is updated" that toggles the bounce. My expectations were too low; I didn't even look.

Update 7/20/09: The weird bug struck again. I tried to hit an https resource and both Firefox and Safari couldn't get a secure session -

Safari can’t establish a secure connection to the server...

In the past the next step is losing all http access. It's as though something were consuming a finite http related resource ...

I switch users and there's no problem, so it's a resource in my user session.

Then I check Console and find this ...

7/20/09 1:56:21 PM DashboardClient[23283] (ca.aquabox.widget.twidget) file:///Users/jfaughnan/Library/Widgets/Twidget.wdgt/Scripts/prototype.js: SyntaxError: Badly formed JSON string ... Twitter is over capacity

Huh?!

Yes, sure enough, I once installed a Twitter Dashboard client, Twidget, -- then forgot about it. It's making http requests in the background - constantly.

I wonder if it's consuming some resource ...

I've deleted it. Never occurred to me that the Dashboard client was sucking cycles -- I rarely run the db.

Update 7/25/09: Fixed. Turns out it was a Parental Controls bug.

Firefox 3.5 slow startup: It's a big bug

Firefox 3.5 can take up to 15 seconds to launch the first time each day I use it at home, but at work it can take, literally, minutes.

Disabling update checking seems to fix the problem. It's in Tools:Options:Advanced:Updates.

I disabled all update checking. Of course this is not optimal, I'm hoping FF comes out with a fix shortly (I'll have to manually request the fix update though!).

(Credit to a work colleague for this fix.)

Update 7/24/09: After a few days I realized removing update checking didn't really fix things. Another colleague spotted the bug report. Wow.

It's remarkable how long it took the Firefox team to admit there was a serious problem, and how egregiously bad the original security related design decision was. Per my colleague:

Apparently the issue is that the Firefox 3.5 NSS (Network Security System) reads all the files in the IE cache and the Windows Temp folder to generate a seed for its PRNG. Not only is that expensive in and of itself but it also might (!) cause your AV scanners to re-scan every one of the touched files. Apparently clearing your IE cache and Windows temp files may or may not help.

This should be a wake-up call for Firefox. How did this design make it into production? Why was there so much resistance to admitting something was badly wrong?

Update 7/24/09b: The newest release may have a fix.

Update 7/24/09c: It was a bad design flaw, but I now see why I was so affected by it. Some IE install glitch had given me a HUGE IE cache -- one that was above the IE 8 1GB limit! I only discovered this when trying to reset it, and discovering IE shrunk it to 1GB. I set it to 50MB and deleted what was in there. As usual my Windows Temp folder also held quite a bit of junk, but it was the IE cache that was huge.

The five incomplete ways to search a Google Blogger blog

There are several ways to search a Blogger blog, including the search box gadget, Google Custom Search, Google Blog Search, and and the Blogger editor search.

I'm just starting to use the search box gadget, but I suspect it's similar to Google Custom Search -- it turns out to use the very mediocre Google Blog Search indexing.

Google Custom search coverage of my blogs varies from very good to fair. It all depends on how Google feels about my blogs on a particular day. Sometimes it's keen, sometimes not so interested. When it's keen the material is well indexed, when I'm out of favor the indexing is shallow. It's never comprehensive however. (Google's variable affections reminds me of my 7yo daughter, but that's another story.)

Google Blog search has extremely poor coverage of my blogs. It seems to largely index the popular blogs.

The search function that's displayed in Blogger's NavBar is sometimes better than Google Custom Search, but it's shallower -- biased to newer stuff.

Finally there's the search function that's part of the Blogger editing environment. I thought that one was really comprehensive. I'd never known it to fail -- until today.

Google Custom Search found one of my very old (2003) posts in Gordon's Notes, but the Blogger editing search couldn't find it. I did some probing and it looks like I'm indexed from 2004 on, but it fails in 2003.

So from Google alone I count five different ways to search my Blogger posts, but none of them is perfect. The Blogger editor search is most comprehensive, but the Google Custom Search will sometimes turn up posts it misses.

Of course if this material were all on my hard drive Spotlight would index it all. The Cloud is not always your friend.