Plaxo - just not a good feeling

An informed comment on my latest Project Contacts windmill tilt led me to take another look at Plaxo. I ended up deciding to wait and see what happens elsewhere over the next few months.

Plaxo launched about 6-8 years ago, and had a very nasty reputation for quasi-spyware behavior about 4-5 years ago. They've cleaned up their act and since been acquired by Comcast.

Nowadays they're sort of a cross between LinkedIn and Facebook -- leaning more to the former. Their secret sauce is contact synchronization across Outlook, OS X Address Book, and some phones. It sounds like that's reasonably robust. They also provide some calendaring services, but there's no support for CalDAV, calendar subscription, feeds, etc. It's all proprietary. Their only outward link is to Facebook, and you can share status updates with FB (so a Tweet can go to FB and then to Plaxo).

They can authenticate with a Gmail or OpenID account -- so I didn't need a new un/pw to try them. Based on my Gmail address they suggested links to everyone who has that address in their Plaxo Contacts -- which turned out to be a lot of people I know.

So what turned me off for now?

1. It's really unclear how they make money. Their premium services are pretty mediocre. I know how LinkedIn, Google and Facebook make money.
2. The complete lack of standards support (ICS, CalDAV, Feeds, vCal, etc).
3. No clear way to subscribe to calendars, just their sync.
4. All their sync and import/export require that they get my Google un and password!! Huh? In Jeff Atwood's words, that's a total FAIL. I'd sooner give them my DNA.
5. The stuff I care about seems to be an increasingly distant second thought to their Facebook-play.
6. They are incredibly obnoxious and persistent about trying to get me to give them access to my Gmail and other accounts and the rights to invite everyone in those accounts to Plaxo using my name.

So I'll give this one a pass for now. Let's see if Google gets their Contacts act together in the next few months -- even if that means I have to shell out for a year of Apple's sub-mediocre MobileMe while the smoke clears.

Update: Faheem responds in comments. He avoids all the Google and other password issues, strictly deals with iCal and Outlook and Address Book sync. He avoids all the social stuff and Plaxo arm twisting and just concentrates on Contact sync. He sure is persuasive; I'm convinced he knows this turf at least as well as I do.

Blogger editing madness

Switching between editing posts using Windows Live Writer, Blogger in Draft with Safari 4, and Blogger draft/standard using Firefox 3.x leads, sooner or later, to bizarre line space problems.

Not to mention applying blockquote operators to Blogger in Draft text with Safari causes new space doubling.

I fear it's all tied up in the ancient wars between unix, mac and dos (yes, DOS) around CR, LF and CR/LF pairs.

Interestingly IE 8 behaves like Safari 4, so Firefox may be a bad actor.

Update: It's worse than I'd thought. I wonder if Google is screwing this up again, I remember a period about a year ago when the line spacing behavior went berserk.

Update 5/23/09: I've experimented further. It's fubared. I have learned that if one uses the rich text "remove formatting" tool the formatting becomes more predictable. It's the interaction between source text formatting and the rich text editor that makes things really messy. I wonder if Google is giving up on blogger.

Project Contacts: Now mixing Outlook/Exchange, PST file, Outlook/Home, MobileMe Sync, OS X Address Book and the iPhone.

A recent Apple Discussion Thread led me to take a new direction with Project Contacts.

To put it mildly, there’s a lot of complexity in this post. However initial results are very positive. This method will require me to purchase a MobileMe account, something I was hoping to avoid. (See below for a partial index to past efforts.)

The end result is that I have a single collection of work/home contacts across iPhone and OS X Address book at home. The work contacts portion of this collection is updated weekly. At this time the update is one way, from Work to Home.

For anyone who may be facing these challenges, I have provided a skeletal outline here of what I did and what I would do if starting from scratch. You will see how insanely complex this is. Note that as of this writing the care PIM data that was once in Palm/Desktop is now scattered across Google (Calendar and a detached set of Contacts), Outlook/corporate, Toodledo and MobileMe. Everything does come together in my iPhone. The current solution involves a wide variety of vendors. For example, Apple's MobileMe calendaring is pathetic; far weaker than Google Calendar and a joke compared to Outlook (which makes Apple's no-show on tasks even more crazy). On the other hand Apple's Contact framework is very robust, much stronger than Google and a rival to Outlook.

This ruddy mess is a real indictment of Apple and a fat opportunity for the PalmPre.

So much for prelude. Here’s the outline, strictly for the uber-geek:

Here’s what I actually did:

• Copying contacts from Outlook/Exchange root to Outlook PST caused the EX (Exchange server x.500) email addresses to be updated to SMTP (standard internet) email addresses.
• PST on thumb drive to home (simple)
• Copy into Home Contacts
• Sync to MobileMe
• In MobileMe web assign all to a Group
• Sync to OS X Address Book (small conflicts)
• Sync to iPhone (ok)
• Sync to Outlook Home: Each Group in OS X Address Book became a Contacts Subfolder in Office 2003. This means the cardinality relationship to Address to Group may have to be One to One.

Expected problem:

• Contact belongs to two Groups in OS X Address Book (multiple inheritance)
• Contact assigned to ONE Subfolder in Office 2003.
• In OS X change Group assignments.
• What happens in Outlook?

Here’s what I suggest doing (LOTS of backups of OS X Address Book as go along)

1. Outlook/Corporate create PST file, copy work contacts. Do not copy lists or groups of contacts, only contacts.
   
2. PST file to thumb drive
3. Home Outlook mount PST data file. Make sure Contacts folder is empty
4. Sync iPhone to OS X Address Book
5. Create new group in OS X Address Book that will hold corporate contacts
6. Sync to fresh MobileMe Account
7. Sync fresh MobileMe account to home Outlook
8. Now Outlook will have an empty subfolder. Dump the Contacts transported into the PST file into that empty folder.
9. Sync from Outlook to MobileMe
10. Sync from MobileMe to OS X Address Book
11. Sync to iPhone

A partial index to past and related efforts at work/home Contact integration:

• Synchronization (all)
• MobileMe (all)
• Outlook (all)
• Contacts (all)
• Synchronization is Hell.
• Root causes: Why you can't sync your work and home calendars to your phone
• Project Contacts: Integration across iPhone, Google and whatever
• Work home contact integration: Outlook to Google to OS X Address Book (X.500 EX email problem)
• Synchronization case study: Address Book, the iPhone, and Google Contacts
• iPhone sync to Google contacts - 3 methods and work/home implications
• Outlook contacts to OS X Address Book - 3 techniques
• Google saves my iPhone (Google Exchange Server emulation for iPhone)
• Googaby: Novel approach to Google Contacts and OS X Address Book integration
• OS X Address Book to Google Apps Contacs using Google ActiveSync
• Work home contact integration: Outlook to Google to OS X Address Book
• Access OS X Address Book records using OpenOffice database?
• Synchronizing iPhone and Gmail contacts: getting OS X Address Book into Gmail
• gSyncit vs Google Calendar Sync with Outlook 2007
• gSyncit for Outlook 2007 to Google Calendar and Contacts Sync
• Prediction: We won’t see a fixed MobileMe until 10.6 is out
• MobileMe alternatives – including for iPhone Sync (MacWorld)
• Palm Pre is Exchange sync based
• iPhone: MobileMe vs. Google services
• MobileMe, Microsoft Outlook, Exchange, iTunes and yes, sync Hell
• Is it too late to go back to Palm 1994?
• Palm to iPhone - the update
• Synchronization is hard - more evidence
• Palm to iPhone migration - address book and notes
• Spanning Sync tells us what's wrong with Google's free CalDAV sync
• Apple can't do synchronization - again
• MobileMe syncs with Outlook (but then Apple turned it off for Exchange clients)
• Interoperability and my Contact information: Microsoft Outlook and Access, FileMaker Pro and Palm Contacts

Update 5/15/09: Now that I've got this working I'm trying various optimizations. For example, my contacts don't change that often. It's easy to create a view in Outlook that sorts by modified date. It's fairly trivial to send out a few changed .msg in an email and let Outlook at home merge them in. I still have to think about how to work with Google's Contacts, but I'm seeing a few interesting options.

It's weird how powerful MobileMe contacts are, yet how feeble MobileMe calendaring is. We're due for a MobileMe relauch, so I expect some developments before September.

Lastly, I should probably mention why I took this route. The more I looked at the workarounds for getting Outlook/Exchange corporate contact data to Google or the OS X Address Book the worse they looked. Their are problems with data models, problems with the intractable horror of the Outlook Add-In architecture, problems with Exchange server and problems with corporate access. This approach is crude, but for me, once I figure it out, fairly painless. I think it will fly until we get something better.

In the meantime, I'm rooting for the PalmPre to humiliate Apple and make them reconsider the direction they're taking.

Update 5/15/09b: Now that I've got this setup working I can see weird new affordances. For example, one of my top 10 OS X frustrations is the inability of FileMaker to work with the Address Book SQLite data stores. Ahh, but now my address data is synchronized between Outlook/Home and Address Book, and I can use Microsoft Access with Outlook/Home. So I can clean things up there, and MobileMe sync will propagate my fixes. I think I'll find a way now to get my Google Contacts into the battlefront.

Update 5/16/09: Great comment by Faheem, who's achieved a similar outcome using Plaxo without paying for MobileMe. I took a look, but Plaxo didn't feel right for me.

Outlook contacts to OS X Address Book - 3 techniques

In 2006 MacWorld outlined 3 ways to move Outlook contacts to OS X Address Book. It's rather annoying that Microsoft doesn't provide a standards-compliant export from Outlook; they're usually a bit better about data mobility of this sort.

Outlook contacts to Address Book | Root | Mac 911 | Macworld

... Under Outlook 2002 you could simply open your contacts and drag them to the desktop to turn them into vCards. No longer. Try this and the contacts are converted to messages.

While you can select a single Outlook contact, choose File -> Save As and, in the resulting dialog box, choose vCard Files from the Save as Type pop-up menu, this works only for individual contacts—you can’t export a group of contacts this way.

You have a few options for eventually getting the things out of Outlook. The first is to select all your contacts and choose Action -> Forward as vCard. Outlook will create a new email message that contains all your contacts as individual vCard attachments. Send this message to yourself, pick it up on the Mac, drag these files into Address Book or Entourage’s Address Book and you’re good to go.

Or Sperry Software can lend a hand with its $20 vCard Converter Add-in for Microsoft Outlook. This adds a service that enables Outlook to export all your contacts as a single vCard. (Yes, it’s galling that OS X’s Address Book lets you do this for free.)

Or you can use a go-between application to get the contacts out of Outlook and into an application that offers more flexible export options. That application is the Windows version of the free cross-platform email client, Thunderbird. Within Thunderbird you’ll find the Tools -> Import command. Choose it, select the Address Book option, click Next, and in the Import window select Outlook and click Next to import your Outlook contacts into Thunderbird...

I tried the Action - Mail feature, but it doesn't work for 980+ contacts.

Next on the list is the now $25 vCard Converter Add-in for Microsoft Outlook, but I fear all Oulook Add-Ins. I think the Outlook Add-In architecture is 75% unstable antimatter. (Alternate source?)

It's not on this list, but a few months ago I tried the export to Google to Address Book route. It was "ok", but I ran into problems with EX style x.500 email addresses.

So this time I think I'll try the Thunderbird option first, and if that's not satisfactory I'll try the (currently) $25 vCard converter add-in.

Once I have the Work contacts in OS X Address book, then they'll go to my iPhone ...

Update: Thunderbird had the same X.500 (EXchange server) email address translation problem as CSV export. Also, I couldn't limit import to a single contacts collection, it brought them all in. Lastly, it was very slow. If the Sperry product can do the x.500 to internet standard email translation I'll give it a try.

Also, this export utility has a 30 day trial.

Make iTunes window more like a standard OS X window

iTunes started out as a pretty un-Mac like application, but over the years the platform and iTunes have grown together.

Except for one real oddity.

Every Mac application has 3 "ball" icons in the upper left side of the window - red, yellow, green. In Safari if you mouse-over they display a symbol as well.

Red closes the window. Yellow hides it. So far, so boring. But what about green?

Green is the expand window button. This isn't well documented, the OS X zoom window (expand window) behavior is quite different from windows. A well behaved app doesn't necessarily zoom to full screen, it zooms to the maximal logical size (which for many apps is full screen). It doesn't always work as expected, and I think apps are behaving more like Windows zoom over time, but I personally like this smart zoom.

So the green button is the expand button ... except in iTunes, where it instead launches the iTunes mini-player! How annoying.

Happily, there's a workaround, which I came across here  and have since added to an old post of mine on iTunes shortcuts and modifier keys...

Gordon's Tech: iTunes keyboard shortcuts, safe mode, prevent mounting, and more

.... option-click the top-left round green window (+) icon: instead of switching to a mini player, the iTunes window adjust to an optimal size for the current display. In other words, it behaves like the green icon on every other OS X app...

I'd prefer iTunes behave like a standard Mac app, but option-click is better than nothing.

Retrospect restore failing, network flaky – a hardware problem?

Maybe it’s the incipient dementia, but I’m having a hard time telling hardware problems from software problems these days.

It didn’t used to be this way. Even ten years ago if something went wrong, it was almost always a software problem.  The only exception was the slowly dying drive, but you could usually hear that going.

Now, who can say? Systems can run hot, solder isn’t what it used to be, and quality is an issue everywhere. Software is very complex now, and software changes can make latent hardware issues into active problems.

It’s also true that hardware is much older than it used to be. Moore’s Law failed a while back; my 6 yo XP box just keeps on being useful. I don’t ask much of it since we’re largely an OS X shop, but it’s good enough for basic work.

It all adds up. Oh, and the dementia too. Being an OS X shop means it’s been a very long time since I’ve had to think about BIOS age, memory maps, interrupts, and the like.

My latest experience is a case in point. It began when I replaced my old USB backup drive and enclosure with a LaCie 1TB drive/enclosure. My old XP box wouldn’t boot! It simply hung in early startup. I found I had to turn the drive off to boot, then turn it on again when XP was up. Then it all worked.

Ominous.

Next I started getting oddball network problems. I beat them back and things seemed to settle down, but then a Retrospect Professional restore of a 50GB iTunes Library failed with a typically cryptic Retrospect error code of "-519". I had to throttle my 100 gbps network back to 10 mbps to get the restore to work.

That got my attention. I can’t live with unreliable backup/restore.

In some earlier testing I’d eliminated cabling and my Netgear gigabit switch as contributors. So the problem lay in my 3 yo G5 iMac or my 6 yo XP box. Neither had had major software changes recently, so I bet on hardware. Since some network glitches had required power cycling the XP box I put my bet on that.

So I bought the Intel PWLA8391GT PRO/1000 GT PCI Network Adapter. It came from Amazon in about 2 days (free shipping!) in a plain package with a single DVD. Nothing fancy here.

So I swapped out the old 100 mbps SMC NIC for the Intel and rebooted and got a … turquoise screen.

Nothing. The drives were spinning, the CPU fan was spinning, but the system locked pre-BIOS! I pulled the card, restarted and things looked good.

So then in desperation, I moved the NIC to a different slot, and then rebooted and looked through all my BIOS settings. I made one change. The BIOS had previously been set to manage devices, now I set it to ignore PnP devices and let the OS handle them.

So I did two things at once – but I wasn’t trying to identify the root cause. I wanted the thing to work.

I then restarted with the LaCie 1TB drive attached and … it worked.

I’m really getting tired of figuring this stuff out.

The Intel adapter requires drivers, so I installed from the CD and … wait for it …. found a bug.

Immediately.

It’s a gift.

The installer bombed with a poorly written complaint about my “S:” drive.

Turns out I’d mapped the “My Documents” folder to a (now inaccessible) network share that I’d mapped to the “S:” drive. So of course there was nothing there. Even when I dismounted the “S:” drive, the installer still bombed. I had to reset “My Documents” to the default setting.

So, pretty dumb coding on the installer. On the other hand, once the install completed, I was impressed by the diagnostics suite. The NIC, cabling and network passed every test.

These hardware diagnostic tests are critical in the modern era, so this utility was a definite plus.

I then repeated the restore that had previously failed at the 200MB mark. This time it went easily past 1GB, with a throughput of about 830 MB/min (probably limited by the USB drive).

So I think my problem is solved. Was it really a problem with the IDE slot? Or the old NIC? Or the 1TB USD peripheral causing some problem with the 8 yo BIOS? Was the fix the new card, changing the BIOS settings, or moving to a new slot?

I don’t know.

Don’t care.

My network’s much faster now…

Why I'm downloading Windows 7 RC tonight ...

It works on VMWare -- and it's free ...

VMware: Team Fusion: Windows 7 on Mac with VMware Fusion: A Practical Guide Revisited

... More important, I am excited that the Windows 7 Release Candidate is the easiest way for you to try out Windows on your Mac for FREE (at least until the beta expires). That’s right, you can download Windows 7 Release Candidate through July 1^st and it’s free to use until it expires on June 1, 2010...

The VMWare post has more details, but basically the RC works fine with some trivial and standard configuration options.

A very nice surprise for me. I've been tracking Windows 7 from a distance, but primarily as my way to avoid Vista (Windows 7 is Vista 2.0 of course, but I'm good with that). In the meantime I've had Parallels 1.x and Windows 2000 (!) running on my MacBook for about 2 years (man, does Win2K ever boot fast on that machine.) This setup worked for the handful of times I've needed it, and the two take up very little CPU or disk space. Windows 2000, of course, is essentially immune to modern viruses.

That's a good setup and it cost me nothing but Parallels 1.x since I have several unused Win2K licenses. It probably won't work on 10.6 though, and I'm about due for a new iMac.

So I'll put my unused VMWare license on the new machine, install Windows 7 RC, and be good for a year or so. Then I can decide if I want to buy Win 7 or regress to Win2K ...

(I wonder if I need to get more than one copy of Win 7 RC, in case I put it on two Macs ...)

5/26/09: Updated to remove a stupid mistake where I confused 2009 with 2010. The RC1 download is good for one year. That's just fine.

iPhone incompatible with old auto adapter? Salvation from Griffin

I like Griffin stuff, so I was willing to take a gamble on the just released Griffin Firewire to USB Charge Converter for iPod and iPhone 3G.

In short, it works. One of the truly infuriating iPhone aggravations has been ameliorated.

The $20 device is a bit bigger than the proverbial postage stamp, about an inch square. It's quite light. The standard iPhone/iPod adapter is the modern friction-only style, no lock feature. (I'd prefer the positive lock for this use, but Apple has moved away from them.)

I plugged one end into my SONY car stereo with iPod adapter cable and the other end into my 3G iPhone. The iPhone began charging. More importantly, the kludgy but useful iPod control software works, and the sound quality really is better through that cable than through the AUX in mini-jack connector.

I did get an error message from my iPhone saying the device was not compatible with the iPhone and offering to reduce audio interference by putting my phone into airplane mode. This is not related to the Griffin converter, I get this message without it. It's different from the "can't charge" message -- it's saying that the radios built into the iPhone can cause interference with many devices not built for the 3G iPhone. In my case there's no hum or other problem in standard mode.

The adapter does make the cable to iPhone connection long and somewhat fragile. It would be easy to whack the end of this longish lever and injure a connector. It would be best used when the iPhone is securely mounted.

It's probably not worth buying this device to extend the utility of a firewire charger -- it costs almost as much as a Griffin USB charger and cable. It's really made for an automotive head unit, and it works on mine.

Note that Griffin makes no claims that the automotive head unit controls and audio inputs will work -- only that charging will work. I took a chance that everything would work, and it did.

Lost phones: advice for everyone

Although this article is written about a lost iPhone, it's really applicable to all phones: Six things I learned from losing my iPhone 3G.

Be sure to read the comments as well. I'd already followed most of the recommended practices, but I hadn't checked with my home owner's insurance to ask what it would cost to insure the phone against loss. One comment mentioned their policy increase was only $10 a year, another said the deductible was prohibitive. Note that most high end phones cost about $500 to replace unless your contract is nearing its two year renewal date. (I think for AT&T in Minnesota they'll provide the new phone subsidy if the renewal date is less than 4 months away).

I didn't realize that under some conditions AT&T will mark a phone as stolen, and may be able to retrieve it if someone tries to use it with a new account.

I photographed a business card and turned it into my wall paper. Dull, but effective. I also implemented the "delete data on 10 password retries", but some of us have young children who may try to hack a phone. If you implement this be sure to have sync regularly.

Apple's iPhoto and MobileMe photo blunder: when full quality isn't.

Adam Engst is far too kind to Apple in this article (emphases mine) ...

TidBITS Media Creation: How to Share Full-Quality Photos via iPhoto

A reader recently sent me email asking why sending a photo via email using the "Actual Size (Full Quality)" option in iPhoto resulted in a photo that was significantly smaller than the size of the photo within iPhoto...

A quick test on my system confirmed his results. My Canon PowerShot SD870IS's test photo started out at 3.1 MB and 180 dpi before dropping to 1.7 MB and 72 dpi. When I opened both the original and the reprocessed photos, Preview's inspector window showed the change in dpi and file size, though the dimensions of the photos were indeed identical.

... iPhoto always compresses photos sent via email to reduce the file size...

... posting the photo to your MobileMe Gallery won't help either, since iPhoto compresses uploaded photos there as well, even when you use the Actual Size option in the Advanced preferences for a MobileMe Gallery album...

... is an EmailCompressionQuality key in the com.apple.iPhoto.plist file that's set to 0.75 ... When I bumped it up, the size of photos sent via email did increase, but when I set it to 1.0, the file size nearly doubled from the original....

Arggghhhh.

Adam is glossing over some key points in an understandable effort to be sweet to Apple.

The problem is not that "iPhoto [always] compresses photos", it's that iPhoto is decompressing the original JPEG (SD870 is JPEG, not RAW), then recompressing it at a severe .75 JPEG compression factor. The decompression/recompression factor is why, when Adam moved the quality index to 1, the resulting JPEG was twice as big as the original. (You'll see the same thing with any image managed this way.)

This is a big deal for photo geeks. Try putting an image through four sequential JPEG 0.75 save/edit cycles and you'll get a mess. When I put "full quality" images on Picasa Web Albums or SmugMug one of the things I get is a high quality backup of my image. We now know that's not true of MobileMe -- it only looks that way.

The discovery that "full quality" images posted on MobileMe are being put through the same decompress/recompress cycle, while being sold as "full quality", ought to be red meat for a lawyer. Anyone know of a hungry lawyer taking charitable contributions for yet another Apple lawsuit? I don't care about winnings, I just want them to suffer.

For my part I'm going to give this a try with Google's Picasa Web uploader and see what I get back. I don't use MobileMe, and I'm not likely to start now.

Incidentally, a more subtle version of this stupidity occurs in Aperture. If you import a JPEG image into Aperture, don't apply any edits, then export it from Aperture using a standard JPEG setting with quality 1 you'll see the same (pointless) decompression/recompression at work.

Update 5/26/09: Apple doesn't apologize, but it effectively confesses to the blunder. No promises of a fix, however.

Yikes! Disastrous iTunes 8.1.1 AppleScript bug!

Wow.

This iTunes 8.1.1 bug is probably the nastiest bug that's bitten me in years.

I have long used an AppleScript to delete the first 'n' characters from an iTunes column string for all selected columns.

In iTunes 8.1.1 it ignores the selection, it processes all the items in a playlist.

So about 300 items have lost the first few characters of their name.

I'll have to restore from backup.

Update: Well, isn't that sweet. My backups appear to be good, but my restores are failing with a Retrospect error code of "-519", which means network error. I have reason to suspect this is actually a hardware error on the old Windows XP machine that runs my Retrospect Professional backup server.

Looks like this is going to be one of those days.

Update b: I dropped the XP to 10mbps and rebooted the XP box and the iMac. The backup is now crawling along; it will take about 12 hours (!) to complete if it continues. I'll delete all the AppleScripts associated with iTunes and see if can figure out if this is a known bug.

As for the networking issue -- it's not the first odd networking problem I've seen lately. Sad thing is this is just as likely to be hardware (switch, XP box, iMac) as software! If Retrospect 8 were in better shape (still no PPC version!) I'd probably buy a modern iMac and get rid of the XP box.

Update 5/4/09: The 45GB restore at 10 mbps took about 12 hours, but it worked. Interesting lesson about modern apps -- the script bug only knocked out a few bytes of data distributed across about 300 MB of music, but I had to restore all 45GB.

So now I have to address the network problem that blocked restores at 100 mbps. In the past I'd have been confident this was a software bug in either the iMac or the XP box. Nowadays nothing's so simple. It could be an emergent bug. It could be an XP BIOS problem triggered by the 1 TB external USB drive, a drive that's far out of spec for that old system. It could be a subtle motherboard problem on the iMac -- the G5 iMac line is notorious for mb failures (one of Apple's crappiest products).

I've already ruled out switch or cable problems.

I'm going to take a semi-informed gamble and install a new 1 gbps Intel NIC in the XP box and retest. If that doesn't work I'll have to start testing the iMac for a motherboard failure.

Update 5/6/09: New NIC worked, but not exactly sure why.

Testing Firefox 3.5b4

Firefox 3 has been very slow on a single CPU PPC G5 iMac. It quickly pegs my CPU.

Happily Safari 4beta has been a great improvement over Safari 3, and Google's Safari (4) support is finally respectable. So I've been using Safari -- really for the first time. (Camino runs into too many Google oddities, otherwise I'd use it over FF 3. We do use Camino on an ancient G3 iBook running 10.3 -- and it's marvelous there.)

Now, however, James Fallows reminds me that FF 3.5b4 is a real option. I've started testing ...

Welcome to Firefox 3.5 Beta 4

... This release is being made available for testing purposes only. You should read the release notes before getting started.

We want to hear all of your thoughts about this beta, especially if you encounter broken sites or other web weirdness. Drag this feedback button onto your bookmarks toolbar and click on it when you have something to tell us...

I know how to test it.

First impressions? It's fast and responsive so far, and my CPU is running at about 35-50% -- which is about the same as Safari. The mouse wheel scrolling is particularly smooth, and Macintosh copy/cut shortcuts work in the rich text editor (not sure that's new, I switch platforms so often it's all a bit automatic).

The release notes mention ...

• There are Gmail oddities, fix by refresh
• Uses Tracemonkey - so faster Javascript, maybe fewer memory leaks
• Location aware browsing (I'll turn it on of course)
• HTML 5 offline storage (like webkit and chrome)
  

Updates to come, but this feels like a good one.

Update: Google Gears is not compatible with the beta (unsurprisingly). So you'll lose offline Gmail if you install. Also I found one bug. In a multi-user OS X machine the install reports a privileges error if another user is active, even if FF is not in use in the the other session.

OS X parental controls - bug?

Yes, my eldest is of that age.

So I'm checking out the Parental Controls ... and I discover they only go back a month. When I change the date range to anything over a month no information is displayed at all!

Since you can't export or otherwise analyze the logs they're not terribly useful anyway -- but they also don't work.

Apple really doesn't take children seriously -- I'm not sure they believe in them! This didn't used to be true -- parental features in Classic were excellent, as was Simple Finder.

None of that survived OS X, and it's clear Apple doesn't really test this stuff. I figure they put it in to keep regulators of their backs.

FMTouch – the closest thing to FileMaker for iPhone?

I’d been hoping FileMaker would do an iPhone version, like the one they did for the Palm.

They haven’t. This morning I decided on a whim to look if there was any rumor in the blogs I read. Google Reader search turned up an older post that led me to FMTouch - FileMaker Mobile Software for the iPhone and iPod touch.

They’re at version 1.35 now; it is supposed to work with FileMaker 8 – 10 (I’m on version 8; FM Inc hasn’t done anything of interest to me for a while – I’m only on v8 because OS X required an update).

Problem is, it’s $70, and there’s no “LITE” version to test with.

Other signs are not incredibly encouraging.

The App Store reviews are marginal; some of the more positive ones smell suspicious. The app is reasonably popular, but the vendor’s blog has been pretty quiet and the web site has been poorly maintained (ex. “A new updated user Guide will be available 9/12” and I don’t think they mean 9/12/09). The “tutorial” on sync is a screencast only. I can’t find any reviews from my usual trusted sources.

I’m tempted ... but it smells wrong. I’m going to see if FileMaker does anything when version 3.0 comes out.

Update 4/27/09: An FMTouch developer wrote in with a detailed response to this post. I'll update with an excerpt later, but for now see also an unrelated comment below.

So FMTouch is not "smelly" to me any more, and I'm even more tempted. They'd benefit enormously from a web site refresh and a "LITE" version that would serve as a "trial" app (since the app store doesn't support trial versions). I'm going to review the app store money-back guarantee procedure; maybe that will make it easier for me to pull the trigger.

Update 4/27/09b: The FMTouch developer posted a response in comments, and also wrote a less diplomatic response on the FMTouch blog (subsequently amended so it's quite diplomatic now). This is a passionate group of developers, and that's a good thing.

Update 4/27/09c: Six more passionate comments from happy users. Ok, Ok, I'll buy the damned thing tonight! Sheesh. Review to come in future. This was not one of my better posts!

Firefox for OS X bug: non-admin user and auto-update

With Firefox 3 a non-admin OS X user cannot uncheck the "update Firefox" advanced option. The checkbox is grayed out.

Only admin users can uncheck "update Firefox".

This is wrong.