Saturday, January 15, 2011

How I synchronize OS X Contacts with Google Contacts and my iPhone

Abandon all hope, ye who enter here. Dante.

This one is for Martin.

I have synchronized my OS X Address Book entries with Google Contacts and MobileMe/iPhone for over a year. It mostly works. This is how I would do the Google Calendar part of it if I were starting out today. The MobileMe stuff is relatively easy [1] and I won't describe it further.

Before I begin, however, I require any reader to pass through three gates of informed consent ...

Gate 1. “Do I feel lucky?” Well do ya, punk?

If there's anything in this post you don't understand, you shouldn't try this. It could blow your Address Book apart. You might spend months reassembling it.

Gate 2. Read my 2011 resolution on managing complexity.

This is on the premature adoption end of things. It's taken about twenty years of boring, career destroying committee work to develop an incomplete and flawed standard sharing calendars and invitations. We're ten years of pain away from a similar standard for exchanging contact information.

Gate 3: Scan my Synchronization is Hell post.

Ok, you're informed. If you proceed, as a fringe benefit, you may come to understand why healthcare, a trillion dollar industry, seems stuck in the dark ages of IT. If it's hard to get address books to communicate, how much harder is it to send patient records from system A to system B? You may start to understand things like Halamka's post on a "Universal Exchange Language" for healthcare (heavens, but he's an optimist).

I use OS X Address Book as the "source of truth". That's where I add new addresses, and that's where I define what gets pushed to Google. If most of your contacts are in Google you would take a different approach.

Step 1: Buy Spanning Sync's Contact Cleaner ($5, App store) and try Spanning Sync ($25 a year, $20 if you use my referral code NXC8PS, 15 day free trial). I don't use it sync calendars, just contacts.

Step 2: Back up Address Book. Then use Contact Cleaner to clean it up; note warnings about unusual suffixes and the like. Sync works best with a first name, last name for individuals (no spaces) and a string (with spaces) for "companies".

Step 3: Define a group in Address Book that you'll sync to Google Contacts. Start small and build up. I call mine "Google Sync. Configure Spanning sync to only sync that group:

Screen shot 2011-01-15 at 11.00.46 AM.png

Step 4: After sync used Contact Cleaner again. Try a few reps until you're no longer getting duplicate or messed up contacts.

Step 5: As you use Google, keep an eye out for duplicates. Use Google's merge tool opportunistically. It works well, better than OS X Address Book merge.

Step 6: Over time add more names to the Address Book Google Sync group. Until you've got every address you care about synchronizing.

- fn --

[1] Apple controls both data models and they're roughly congruent, at least if you're on 10.6.6. I don't sync via iTunes because I already own MobileMe and it lets me sync to my accounts on multiple machines. The rest of my family can't sync directly because we all share one iTunes account, they have to sync to MobileMe and separately to their OS X accounts on multiple machines.

Spanning Sync contacts cleaner - a quick review

I bought Spanning Sync's Contact Cleaner for $5 from the OS X App Store.

I've used their flagship product for years to sync my OS X Address Book to Google. It's relatively expensive ($25 or so a year) but it mostly works. Since synchronization between differing data models is an impossible problem, "mostly works" is excellent.

So I was willing to give this utility a try.

Briefly, for an early product, it works pretty well. It has a few bugs, but it's definitely worth $5. The app offers to make an Address Book backup on 1st use -- that's a good idea.

I'm a pretty good test case because

  • I sync my OS X Address Book to both Google (Spanning Sync) and MobileMe
  • I have over 800 cards in my personal book (more in my separate corporate directory)
  • I routinely define a "Family" as a "Business" to get around the first name, last name problem.
  • For individuals I often link them into "Families" by use of the "Business" field to hold a family name (or, in my case, the domain name for our family)

These are the bugs I found:

  1. If you choose open in Address Book, then change type from individual to business in Address Book, Contact Cleaner will crash
  2. Details view for "one name" errors omits email addresses
  3. Details formatting not always optimal
  4. Can't manage the individual to company conversion

I'm also a bit suspicious about how it manages group memberships when it merges or alters contacts. This may just be my paranoia coming out.

Some advice on using Contact Cleaner

  • Turn off all other sync while using this tool. I sync my OS X Address Book to both MobileMe (and thus to my iPhone) and to Google Contacts [1]. Just disable your network connection.
  • If you edit in the Address book, save your changes (click out of edit mode) then Rescan in Contacts Cleaner. Otherwise it won't pick up your edits.
  • I like to make changes in Address Book then rescan - gives me more control and I can see the full results
  • Be wary if you use non-default Address Book fields. This kind of cleanup is a very hard problem.

[1] I sync a selected subset of my entire Address Book to Google Contacts. I create new addresses in OS X and then let them sync to Google. Once they sync I can safely make smaller edits on either side (esp. email address updates). I can also do merges safely on the Google side. Group assignments are independent. I define a "Family" entry as a type of "Business", that seems to work.

Thursday, January 13, 2011

iTunes PDF books won't sync to your iBooks app?

You are frustrated.

You can drag and drop PDFs to the iTunes Library icon (iTunes open). They get organized into the Books section. They seem to sync to your iPhone (iPad). Except they don't. Nothing shows up.

You've tried everything. Maybe even inspected permissions.

Try this.

Open iBooks.app.

See that lovely little button that says "Books"?

Tap it.

Now you see your PDFs.

You are welcome.

PS. You can create a collection called "All" and, using Edit, tap on items, then tap Move you can put your Books and PDFs together.

Wednesday, January 12, 2011

Authenticate your Google Apps email - and help finish email spam

The web is overwhelmed by splogs and garbage sites full of noiseware (emphases mine) ...

Why We Desperately Need a New (and Better) Google

... Content creation is big business, and there are big players involved. For example, Associated Content, which produces 10,000 new articles per month, was purchased by Yahoo! for $100 million, in 2010. Demand Media has 8,000 writers who produce 180,000 new articles each month. It generated more than $200 million in revenue in 2009 and planning an initial public offering valued at about $1.5 billion. This content is what ends up as the landfill in the garbage websites that you find all over the web. And these are the first links that show up in your Google search results.

Google is falling, because it's trapped by its own business model.

It looks bad, just as bad as email spam was just three years ago. Today, though, email spam is dying.  The cure was clear by the late 90s, but it's taken ten years to really work. The answer was differential filtering based on the managed reputation of an authenticated sending service. Today we call that Domain Keys Identified Mail or DKIM. DKIM doesn't identify the sender, it identifies the sending service. The sending service then assumes responsibility for the sender (they know who the sender is). If the service doesn't police its users, it gets a bad reputation -- and starts being filtered aggressively.

Gmail accounts have used DKIM for a while, but Google Apps email has made do with SPF -- an inferior solution. Google has only now rolled DKIM out to Google Apps users. If you use Google APps you should enable this (it's not automatic yet). Without it the email you send will be increasingly "second class" and more likely to be filtered out.

It took about two minutes  activate DKIM for our free Google Apps family domain. We were able to use the automated method because that domain is managed through Google's Registrar partner - eNom. It sounds like it might be trickier to activate for domains managed by my favorite registrar/hosting service - DreamHost though I expect it will eventually be automatic everywhere.

We beat email spam. It wasn't that hard, though the fix did take a long time implement. It's clear we could do the same thing with garbageware sites. That fix, however, may require a company other than Google ...

Saturday, January 08, 2011

Replacing a broken 3G iPhone screen: what iFixit doesn't tell you

I used the iPhone 3G Front Panel Assembly from iFixit $70) to successfully replace a broken 3G iPhone screen. I followed the iFixit assembly directions, watched a video for a related procedure and improvised when both omitted critical steps.

You shouldn't try this. I estimate the average non-obsessive geek has a 50% chance of ending up with a fixed phone, a 30% chance of ending up with a more broken phone, and a 20% chance of ending where they started less $70 or so. Once you do this successfully once the odds of success increase dramatically, but the learning curve is steep. If you insist, then please read this post carefully. It will boost your success rate to 75%.

I recommend finding someone who's done this before and paying them to fix your phone. Or see how much you call sell the broken phone for, the buyers will easily fix it. Or buy a 3G display assembly instead ($100) and avoid about 30% of the repair hassle.

I did not attempt the $40 front panel procedure. iFixit rates that as "difficult". In English this translates to "impossible".

Lastly you can pay Apple $200 and they'll do a perfect job. Keep in mind that a new 4G iPhone costs about $700 out of contract and a new working 3G is probably worth at least $350.

If you do proceed consider also replacing the battery at the same time. About half of the hardest steps are common.

I hope by this time you've stopped, but perhaps you're already committed. Or maybe you want to make a business out of this. That would make sense, especially for someone in college where broken iPhones must be common. Here's what I learned (this supplements, but does not replace, the video and the ifixit directions)

Ordering and shipping

  • The front panel assembly does NOT include tools. I missed that, because I started out looking at the insane option of the "front panel" only kit. You definitely need the plastic spudger. You could use a very slender flexible knife or a scalpel blade in place of the metal spudger. I had a magnetic 00 philips screwdriver, I don't know if their's is magnetic.
  • It's surprisingly hard, with a worn black 3G iPhone, to identify that it is, in fact, a 3G iPhone! Elders will need a magnifying glass.
  • The model numbers on Apple's site are only for the first batch of devices. I visited Apple's site and followed their external identifier directions.
  • The assembly came inside loose bubble wrap and a simple envelope; I'm surprised it made it.
  • The parts don't say Apple anywhere.

Preparation

Here's what I laid out. I was able to make up for the parts I didn't order, I had an old spudger that was fine. I think the screws are all the same but I had a different bowl for each and a picture of the step behind each bowl. The tweezers and compressed air were essential. The white paper is sticker backing to hold the cursed black tape removed during the procedure. I wish I had had a magnifying glass, but I'm 51. A bright light source should suffice for the under 40 crowd.

It took me about 2.5 hours to do this with several breaks when I ran into problems. An expert could do it in under 20 minutes.

IMG_0303.JPG

iFixit front panel assembly directions

Read the directions very carefully several times and watch the video for the similar but harder front panel assembly. This is what they left out:

  • My panel came with a screw in place. Look for this and remove the screw. If you don't know this you'll discover the screw when you do the reassemby; and you'll have to take it all apart again.
  • The panel has plastic covers you'll want to remove only at the time of assembly.
  • The video is an edited series of cuts. It omits several key operations.
  • Reassembly is harder than disassembly.
  • I wore latex gloves (powder free) to reduce hand oils and sweat getting on things.
  • The relevant portion of the video is from about 1:13 to 2:06. Watch that several times, unfortunately key parts were excised.
  • Manufacturing changes over time. There are differences between the very first 3Gs and later models.
  • There are two forms of cable connection. There's a standard pressure join and there's the iPhone destroying FPC connector (see below). When reassembling you really need to visually line up the pressure connectors. It takes a modest push to seat them; you will then feel a soft but obvious "thunk". If you don't clearly feel this they're not really connected.

The treacherous black tape

  • Study this carefully before your remove it.
  • At one point you are instructed to remove some black tape. This is very hard to do, I had to work one end up. A scalpel might help. Use tweezers. The tape will curl; but mine curled in a benign way. Leave the curled loop on your paper. When you reassemble, either have someone hold the phone for you or put it in a clamp of some sort. I think the best approach would use a light locking clamp to hold the tape and tweezers. Reposition it, hold it in place, try to flatten it out.

The FPC connector

As of 1/2011 there is a key image missing from the assemblydirections at "step 6". if you haven't done this before you will have NO idea what is meant by the "PFC lock"

I have tried to capture it below, but I should have used a macro lens. It is that small. The PFC lock is a 1mm x 3-4 mm white bar that sits over the distal end of cable 3 as it emerges from a black connector cover. It is shown here in the unlocked, upright position. A simple flick of the plastic spudger will flip it up. Then cable 3 will slide out.

20110108_PFC lock_7690.jpg

To reinsert cable 3 I suggest using fine tweezers on the black cable sheath to push it into the black housing above until the white line on PFC cable is about at the proximal side of the black cable cover. Then flip the PFC lock down.

Good luck.

Tuesday, January 04, 2011

Kensington USB hub maxes out at 4 iPhones

3 kids, 2 parents = 5 iPhones (2 used as iTouch, 2 with data plan, 1 voice only).

Charge and sync is a pain. I tried connecting all five to one Kensington 7 port dome USB hub. It worked ok until the fifth connection, then the newer iPhones (4, 3GS) started complaining that they couldn't charge of an unsupported peripheral.

So four is the practical maximum for this hub. I suspect that's about as good as any hub will do.

Monday, January 03, 2011

How to reset a passcode locked iPhone

After I got home with my stolen iPhone I found I couldn't reset it. iTunes told me I had to enter the passcode. What could I do?

Cough. Ok, seriously. For the 2nd time our good friend C. has given one of our kids her ex-iPhone [1]. C. is a wonderful person, but she has been heck on iPhones. This one has a broken screen, I'll attempt a FixIt repair after I've tested the phone. I didn't want to bug C. for her passcode (after all, it could be her bank PIN too), but Apple documents a procedure for initiating recovery mode on a device that won't mount in iTunes: iPhone and iPod touch: Unable to update or restore.

Be sure to hold the home button as you connect the cable. If you do it correctly the recover dialog appears quickly.

[1] When both her brothers had iPhones, it was clear my daughter's wrath was building. That is not something any sane human would choose to face. Getting this one for free was a lifesaver.

Sunday, January 02, 2011

What can you redownload from Apple's iTunes store?

You only get one download of songs, videos (includes movies), iPod games and albums ...

iTunes Store: Purchased songs, videos, iPod Games, and albums can be downloaded only once: "When you buy a song, video, iPod Game, or album from the iTunes Store, you are entitled to download it only once...."

On the other hand, iOS apps can be redownloaded as long as they are still sold [1] ...

How to redownload purchased apps from the App Store

Click the Buy button. ... You will then see a dialog similar to one below. Click OK to continue with the download.

The rules variation is a bit confusing. There have been reports, by the way, of Apple allowing redownloading of lost music under some circumstances. Those reports, however, reference a form that no longer exists.  I suspect Apple has discontinued that service.

At 1-2 GB each movies can add up fast. If Apple were to allow redownloads we could delete movies we don't often watch, and retrieve them from Apple. Of course this may not be Apple's decision to make, I suspect the rights holders are the issue.

This policy is one reason I prefer DVDs to iTunes purchases, though I fear the days of the DVD are numbered.

[1] It's not easy to find a record of all purchased apps, but if you keep the invoice emails Apple sends Spotlight will help.

 

 

Saturday, January 01, 2011

Rogue Twitter/Google feedburner connection - a casualty of the Great Google Identity Integration Initiative

My Google Reader Share Twitter (re)stream is being updated -- but the posts are coming from a rogue Feedburner bot. None of my Google Identities have control of this feed burn. I think I've run into a bug related to the (covert) Great Google Identity Integration Initiative (GGIII) of 2011.

What, you may wonder, is the Great Google Identity Integration Initiative of 2011? Why do I say it's covert  (covert)? I'll provide some background before I give my take on this alleged bug.

The GGIII is covert, first of all, because Google hasn't named it, much less documented what's going on. Three Google articles provide some limited context (emphases mine) ...

More Google applications - Google Apps Help

After your Google Apps accounts are converted, your users will have access to most Google products. Previously, many Google products -- such as Blogger, Reader, and Picasa Web Albums [jg: and Feedburner] -- were available only in personal (consumer) Google Accounts...

Get ready to transition - Google Apps Help

... If any of your users have a conflicting account, they will be required to rename their conflicting accounts the next time they sign in to their personal Google Account...

... Any Picasa Web Album, Profile, or Wave usernames cannot be moved from an existing account to your Google Apps account

If your users used Picasa Web Albums with personal Google Accounts, they will not be able to reuse their old Picasa Web Album display usernames. They will have to sign up for new display usernames....

Known Issues - Google Apps Help

Reading between the lines there are two aspects to GGII ...

  1. Unification of usernames across Google properties where username is an email address. (example - jgordon@kateva.org). So if this username is used for both a Google Apps account and a traditional Google Account then the two accounts will be unified.
  2. Tie all Google services to a Google Profile. This was recently mandated for all Picasa web album users, even paying customers. Not all customers were happy about this.

Phew. So, if you're still with me, this is what I think happened to a feedburner bot associated with jgordon@kateva.org. That "identity" used to be split between a Google Apps domain (email, etc) and a true Google Account (blogging, feedburner). When I (carefully [1]) activated "More Google applications" for my Google Apps domain kateva.org Google merged two distinct identities that shared a single "name"

  • jgordon@kateva.org - Google Apps kateva.org
  • jgordon@kateva.org - Google Account

My guess is there's a bug with this process when a user has a Feedburner bot linked to a Twitter account using the Feedburner "socialize" feature. I think I have two feedburner services associated with jgordon@kateva.org, but one of them is unreachable.

I doubt there's anything I can do, I just have to wait for Google to fix this. In the meantime I've posted questions with somewhat different angles on two forums ...

See also:

-- fn --
[1] I expected problems. Since this is going to be mandatory in the next few months, including for our family domain where we have similar distributed identity issues, I chose to make kateva.org a test case. I expected bugs like this.

Update 1/2/2011: The problem stopped. I suspect it was related to another Google identity of mine, and so this is probably not a Google bug ... (see below)

Update 1/3/2011: Mary, in comments, points out that this article has more details. It in turn references an article on "conflicting accounts" that tells us

Account merge and data move options : Basics and getting started - Accounts Help

Unfortunately, it is not possible to combine two accounts or to merge data.

Except that Google also tells us ....

Moving product data : Managing and using Google products - Accounts Help

... In most cases, it's not possible to move products from one Google Account to another ... This may change over time, so check back here for updates...

Right. Clearly, this is a flaming mess.

So what happened was that the feedburner configuration in my google (jgordon@kateva.org) account was vaporized when the transfer process destroyed that account's data, but it took a while for the bot to die. Hence the duplicates.

This transition should be avoided as long as possible. If you do make the merge I suggest:

  1. Give the old account a new email address (you'll have to dig one up somewhere).
  2. Delete the old account after you've gotten all your data out of it and after you've ensured that any associated blogs have an admin user with the new identity.

Friday, December 31, 2010

Farewell to Nisus Writer Pro?

Fleeing Microsoft Word, and wary of proprietary file formats, I started using Nisus Writer Express in 2005. Years later I switched to Nisus Writer Pro. It's improved along the way, but import/export remains a real problem. Today I tried using NWP to do a yearly solstice letter. It did a nice job formatting the letter, it even let me create hyperlinks.

When I went to export as HTML however, all I got was text. The images were attached in a subfolder, but not referenced in the HTML. PDF export gave me the images, but no hyperlinks.

I had to dump the HTML ouput text into Word 2007 (Windows, more's the pain) and recreate the letter from the source images. How humiliating.

Nisus Writer Pro is a wonderful product, but they've been stuck for years when it comes to import/export tools. I really need decent HTML export.

It's time for me to try iWork. Then I'll have a really tough choice -- the unreliability of Microsoft Office or the data lock of iWork. Neither choice appeals.

Update: iWork doesn't export as HTML at all. So in this regard it has no advantage over Nisus. I'll wait and see what the expected 2011 version of Pages will include.

Tuesday, December 28, 2010

There are no great task managers for the iPhone - but there's hope for 2011

I'm surprised by the conclusion of my recent survey [3] of iPhone/OS X/Web task management solutions. There are still no great task managers for the iPhone.

Neither Things, nor Appigo's ToDo.app (which I have used incessantly since 2008), nor OmniFocus, nor Remember the Milk.app nor Toodledo.app are a great solution. They all fall short. None of them are the equal of the venerable, simple minded, task manager that came with the PalmOS in 1994 and was improved with integration into DateBk in the late 1990s.

You may wonder why I condemn all of our current options. I'll start by listing the base requirements.

  1. Simple enough for a non-geek to use with at least basic task attributes (due date, priority, task name, description, category [1]) and views (filters, sorts).
  2. Data freedom: import/export capabilities for all tasks.
  3. Synchronization to a desktop or web version that matches the "data model" of the iPhone version and has the same usability standards. [2]
  4. Affordable (total solution costs < $50)
  5. Calendar integration, even if that's only an "agenda" type view of tasks and dates.
  6. Search across all "fields" (attributes).
  7. Utter, absolute reliability.
  8. Instant on, no delays in task entry.
  9. Archiving of completed tasks.
  10. Local iPhone app with synchronizatio -- not dependent on a data connection to work.

Sounds easy, doesn't it?  Palm did most of this fifteen years ago, and Pimlico's DateBk delivered the complete package (and more) over ten years ago. Must be easy [4]...

Evidently not. Nobody does it for the iPhone today. Let me name the failures ...

  1. OmniFocus is too expensive ($100 for iPhone/desktop pair) and is too complex. At a lower price point though I'd seriously consider them despite the complex. I'm an Omni Group fan.
  2. Things has reliability issues, is too expensive and doesn't support data freedom. Their iTunes ratings continue to decline.
  3. Appigo's ToDo.app doesn't have a robust and reliable web or desktop solution and lacks data freedom. The best option is to sync with Toodledo's web app, but that app has a different data model than ToDo.app. This is what I use every day however.
  4. Toodledo's own iPhone/web solution is limited by their complex (and, sadly, ugly) web app. The web app search is field specific and so almost useless.
  5. Remember the Milk has a bad reputation as a business partner, their iTunes ratings are poor (?reliability), they are relatively costly at $25/year, and there's no data freedom. (Corrected from original - see comments.)

It's a sad situation. The best option is still the combination of Appigo's ToDo.app and Toodledo's web service; I pay for both. I do, however, grit my teeth every time I use Toodledo's web client, especially if I need to search for something.

I'm hopeful we'll see a fix in 2011. There are at least three ways the logjam could break.

Apple's OS X app store could reenergize the flagging OS X desktop, and new desktop products might appear at better price points. If Apple were to provide OS X App Store developers with a standard way to synchronize to iOS devices I'd expect a great solution. Alternatively,  Apple could forget it hates its customers, and finally put a bullet through iCal (sadly, will require 10.7). Lastly, and least likely, Jobs might decide he doesn't totally hate task managers after all.

Google might finally provide an API for Google Tasks, allowing iOS client development. Or they might provide HTML 5 (Gears-like) offline Google Tasks web app with synchronization support for Safari. [6]

Lastly, the Omni Group could create a "lite" version of OmniFocus for the App Store and sell both an iPhone and desktop OmniFocus Lite for under $50.  Or some other current vendor will fill out an existing solution.

If we assume an average probability of each of these outcomes of 50%, there's an almost 90% probability [5] we'll get finally get a great iPhone task management solution next year.

I'll raise a beer when it happens.

See also (mostly not about tasks, but all about PIM functions and the amazingly hard Palm to iPhone migration)

- fn -

[1] The big "breakthrough" change to the Palm ToDo (task) list was the radical addition of up to 16 categories. For quite some time Palm tasks lacked "categories" (single tag). The original Palm design team were even more radical minimalists than Apple's modern iPhone OS team.
[2] This is huge. If data models don't match perfectly non-geeks, and even geeks, will eventually be frustrated -- even if they don't understand why they are frustrated.
[3] Looking for a good solution for Emily, and deciding none existed.
[4] I'm being sarcastic of course. One of the hardest things in software development is deciding what to omit. It's the old line about sculpture - great art consists of removing the inessential.
[5] 1 - (1/2*1/2*/2) = 7/8
[6] More likely now that the Google/Apple war is over.

Friday, December 24, 2010

How information leaks on Facebook: a semi-private URL vs. Picasa web albums

This is mundane, but worth noting.

For years we kept some shared family material private by not sharing the URL. It worked, the site was never indexed -- until recently.

I'd shared one of the album URLs on Facebook. That did it. Even though my page contents are shared only with friends, I suspect Facebook indexes any URLs it comes across. Probably most of my friend's Pages are not themselves public, so their view of my post was probably shared.

It's not a surprise that the URL leaked, but it's noteworthy that it remained private through tend years of Google. It only broke when I started using Facebook.

I renamed the URL, so it's secret again. I won't publish the new URL to Facebook, I'll return to sharing by email.

So what about Picasa Web Albums? They are also commonly shared by exchanging a "secret" URL, and I've shared some on Facebook. Interestingly these aren't indexed in Google, perhaps because Google doesn't index non-shared albums.

Thursday, December 23, 2010

Google IMAP and the intractable duplicate IMAP email problem

I've only recently returned to using Mail.app; for a couple of years I was almost pure Google. Since I integrated my personal Contacts across OS X Address Book/MobileMe/iPhone/Google Contacts however I've returned to enjoying the power of a dedicated email client.

Alas, there's a catch. In my time away I'd forgotten the Gmail IMAP to Mail.app sync duplicate email problem. It's not really a Mail.app specific problem, every IMAP client has the same problem.

This is an intractable problem. The standard model for email is that that every message belongs to exactly one folder. Folders can contain folders. It's very much like traditional directories since the days of DOS and well before. (Tree data structure)

Google has a very different model. Google's mail "folders" are an illusion, in reality all Gmail messages are in a single repository. Each message can have many tags, and a single tag can be used for many messages. Each tag is treated in the UI like a "folder", but a message belongs equally to each "folder' (they're just tags).

This is more than a mere "physics" problem -- it's a math problem. 7 != 3, and a tree-type folder hierarchy cannot represent a tag collection.

There are two approaches to "synchronizing" a traditional email application with Gmail. You could make the first tag of an message the "folder" tag, and ignore the other tags. The other approach, which Google took, is to replicate emails. So a single message in Gmail with 4 tags becomes 4 messages in Mail.app in 4 folders.

Of course this wastes space, but space is cheap. Much worse, however, is that it clogs up searches.

I don't see this problem going away - unless Google admits defeat and regresses to using standard folders. For now, however, I'd love to see a program that would go through my Mail.app database and remove all the duplicate emails - even if it randomly assigned them to a single folder.

See also:

Monday, December 20, 2010

Why are my Canon images names with a _MG_ prefix instead of IMG_?

This happened to me a while ago.

My Digital Rebel images started having the prefix _MG_ instead of IMG_.

I figured I'd run by some strange numbering threshhold. It was odd though. Sometimes I'd see IMG_ again ...

It bugged me.

I should have googled it long ago. Photo.net explains - this is what Canon does when you switch from sRGB to Adobe 1998 RGB color space. It's a JEITA specification mandate. I probably see IMG_ when I shoot JPEG instead of RAW.

Thanks photo.net.

Sunday, December 19, 2010

Blogger lives - mobile templates in draft

Last June I put Google's Blogger on the Dead list, in part because of the lack of a mobile template. This morning Blogger in draft offered me a mobile template.

Blogger isn't dead after all.