Many of you will recognize the title – borrowed from "Enterprise 2.0 a Crock" Dennis Howlett.

Needless to say I was quite interested in his discussion with David Terrar, who is more of an E20 fan.

Hm…hard to watch.  Dennis is too loud while David is barely audible.  I kept on turning the volume up and down, until I quit after a few minutes.  But it’s not just the technical issues.  It’s a long video for the message it delivers, and I hate to admit but it could not glue me to my chair for 8 minutes. 

His opinions and sometimes abrasive style aside Dennis is a great analytical thinker, but he is (as I suspect all of us are) simply more organized, more concise in writing.  Simply more convincing – or thought provoking – and definitely easier to "consume" in writing, than this video-torture.  So now you see where my title comes from.  If Dennis says E20 is a crock, then I say so is video. It’s simply not the best medium for a lot of messages.

But I am not picking on Dennis.  Here’s a video by Allen Stern of the CenterNetworks fame:

Continue reading…

My 4-year old how-to guide, Picasa Photo Sync on Multiple Computers has attracted tens of thousands of viewers, and is still quite popular.  In fact too popular, thanks to Google.  I can’t believe people actually read it today and try to follow the advice therein… it’s and OLD post with outdated information.  I’ve long struggled trying to find a better solution… and now that I have it … drumroll … but wait, first things first:

What’s the problem with Picasa?

Picasa is my favorite photo management program, and hey, it’s hard to beat free!  Yes, I believe SaaS is the future of computing, and I do keep many photos online (just canceled Flickr Pro in favor of PicasaWeb), but quick-and-dirty manipulation of large image files en masse is still easier, faster on a local PC.  Or one of the computers I use – if only I could.  It’s hard to believe that Google, an undeniably Web-centric company would create an application that’s designed to be used by one single user and one single computer – that’s stone-age vision, and again, is very antagonistic to being a visionary Web company. 

Picasa does not save your edits in the image file itself, rather it uses a set of system files: picasa.ini files in every photo folder and a bunch of proprietary databases in two hidden system directories.  This is actually a good concept, you can experiment and safely revert back to the original –  trouble starts when you want to move to a new computer, or God forbid access your photos from multiple computers – some of the associated changes will come through, others won’t.  You will soon have multiple versions of the databases and sometimes of the images themselves, and that leads to chaos. 

Early Solutions

The original concept in my previous guide was based on syncing the hidden Picasa databases between all computers involved. It worked for a while… then I started to see corrupted databases, so I abandoned synchronization.  In the meantime wireless home networks became more robust, so instead of redundant chaos, the next best option was maintaining once central Picasa home-base, and accessing it from other computers via the network.  This could quite easily be done by mapping the main computer’s drive as a network drive, say P: (for Photos or Picasa), setting Picasa on all the satellite computers to forget the local Pictures folders and only scan the new P: drive. 

In this setup Picasa still had to index all images it read from the network and recreate a local database on the individual computers, so the solution was quite redundant – but worked relatively well.  Through a succession of new releases Google moved more information on user edits into the per-folder Picasa.ini files, so the system was able to rebuild the database almost completely.  Cropping and some other information was still missing, so you could never be 100% certain you were looking at identical version of your images.  The safest way to avoid confusion and different views of the same photos was to make a policy of only editing images on the “main computer” where they were stored, thus rendering all other networked computers to passive viewers only. 

There has to be a better solution.. one that allows any member of the family (and any user account) using any computer on a network to share the one and only Picasa database – view and edit all the same, with any changes, tagging, editing immediately saved no matter which computer is being used.   Yes, there is one – keep on reading   But first some disclaimers:

• I’ve tested the solutions below in Windows 7
• They should work on Vista, too, and I believe there is a logical equivalent under XP, but I’ve never checked it
• These solutions work for me, but I can not guarantee they will work for you – experiment at your own risk
• Before making any changes, do back up your Picasa database (both photos and the system data)
• Even if everything works, there’s no way knowing if a future Picasa release will change it all…
• I’m not a Windows Guru, and make no claims that this is the best or most elegant solution – just one that works for me
• I cannot provide individual support – you are welcome to comment / contribute below, and may get a response from another reader, but I can not make promises.

Now, we’re ready to rock and roll …

Sharing Picasa Between Multiple User Accounts on the Same Computer

You may only be interested in the multi-computer setup, but please read this chapter anyway, as we will build on the logic outlined here when we expand to a network setup.

Move your photo library to a public location

By default most photos are stored at user account specific image libraries, with a default path similar to this in Windows 7 and Vista:

C:\Users\username\Pictures  

You could fiddle around with sharing / security properties to enable other user accounts access this image folder, but moving your photos to the public folder is a much cleaner solution.  The new destination is:

C:\Users\public\Pictures

Although the easiest way to move folders is from Windows, it’s always better to do it within Picasa, to allow it’s databases be updated properly.   If you use nested folders, you’re in luck, you can just right click on the top-level folder, select “Move Folder”, pick the new destination, and you’re done.  (If you have nested folders but don’t see them in Picasa, change from “Flat View” to “Tree View” in the main View menu.)  If you have a lot of flat folders, this may be a cumbersome process, but it’s one-time only.

This was easy … now close Picasa and let’s get really started   Two reminders before we start:

• you’ll need to do all this using an account with Admin privileges
• backup, backup, backup (your photos and system folders / files)

Move Picasa’s internal databases to a public folder

The internal Picasa databases are originally in two system folders in Windows 7 / Vista:

C:\Users\username\AppData\Local\Google\Picasa2

C:\Users\username\AppData\Local\Google\Picasa2Albums

You’ll need to create a new home for these two folders, for example this:

C:\Users\Public\PicasaLib

Now move the Picasa2 and Picasa2Albums folders to the newly created PicasaLib folder, so their new locations are:

C:\Users\Public\PicasaLib\Picasa2

C:\Users\Public\PicasaLib\Picasa2Albums

Well done. Too bad Picasa is still looking for these databases in the old place…

Trick Picasa into finding the new database location

At this point you should no longer have a Picasa2 and Picasa2Albums folder in your C:\Users\username\AppData\Local\Google\ folder – if you do, you likely copied them to the new destination instead of moving.  If that’s the case, please delete them now – we can’t have real folders with those names here, since we are going to replace them with Symbolic Links that look just like the deleted folders but will actually redirect Picasa  to the new location.

For the next steps even though you’re logged into a user account with Admin rights,  you will need an elevated command prompt. If you’re like me and can’t remember hot-key combinations, here’s how to get it: Click the Start menu and type cmd in the run box, but do not hit enter. Instead, find cmd.exe at the top of the list, right-click on it, then left-click Run as Administrator.

Now you’re in a command box that reminds you of good old DOS.  Navigate to the original Appdata folder:

cd  \Users\username\AppData\Local\Google   

Now type these lines exactly as you see them:

mklink /d Picasa2  C:\Users\Public\PicasaLib\Picasa2

mklink /d Picasa2Albums C:\Users\Public\PicasaLib\Picasa2Albums

You have just created two entries that look like the Picasa2 and Picasa2Albums folders but actually point to their newly created location.

Update and verify Picasa for each user

Open Picasa, go to Tools > Folder Manager and make sure only the new public destination is selected, nothing else – certainly not user specific libraries.

Repeat the above relocation steps for all other users on the same computer, and check their Folder Manager setting in Picasa.

You’re all set!  All users now have shared access to all public photos, and edits, changes, thumbnails..etc are all maintained in a central database instantly available to all users.

Warning: I have not tested what happens if multiple users try to update the databases at the same time, but I assume it is not a very good idea.  Best practice is probably avoid using quick User switching all, rather log out of one user before logging into another one, but at a minimum, even if you do quick switch, don’t leave Picasa open in two user accounts at the same time.

Picasa on Multiple Computers

This is what you’ve been waiting for…  we’re actually very close, the logic is surprisingly simple: map the drive that has our Picasa library and databases as a network drive, say P, then apply the tricks we’ve just learned doing the multi-user setup on the same computer, but now the symbolic links will point to the public folders on the P: drive, and voila!

Well, almost…too bad there are a number of quirks that we have to deal with first.  Let’s take them up one by one.

Your network layout

If you have a NAS drive, which is for passive storage only, accessed by several computers on the network, than the above solution will work, since you can map the NAS drive to the same drive letter on all computers.  But if your network is like mine, i.e. there is no NAS,  Picasa resides on one of the actively used computers which all others access, then you run into all sorts of trouble.  Here’s why:  Picasa stores the result of your “watched folders” configuration in a plain text file named watchedfolders.txt in the Picasa2Albums folder.  But we’ve just moved that folder to our shiny new PicasaLib to be shared by all instances of Picasa – that means they can not have different “watched folders” set per instances.

The problem is, the “main” computer will consider Picasa storage as its C: drive, while all others have to refer to it by another drive letter, since C: is reserved for their own hard disk.  If you have both P: and C: drives as “watched folders”, all hell breaks loose: Picasa will start copying the folders to the local computers, in the wrong folders, wrong labels, resulting in total chaos (I’ve been there…).  So once again, we’ll cheat: find a way to refer to the central PicasaLib under the same drive letter from all computers.

Re-mapping the “server”

Not a true server, but playing that role in this case: this is the computer that has all the Picasa files and that we’ve just set up for multi-user access in the previous exercise.  We want to use the P: designation, but can’t simply rename our main hard disk, nor can we map it as a network drive, so we’ll apply the symbolic link trick again: set up a link from the root folder to the public folder.  Steps:

Get an elevated cmd prompt (see details above)

cd \   (back to root folder)

mklink /d P  C:\Users\Public\   (create the symbolic link)

You now have what the system thinks is a P folder, and can use it in the Picasa “watched folders” definition.  Which means you need to start Picasa, then navigate to Tools > Folder Manager, and select \P\Pictures as the folder to watch – unselect everything else.  For a few minutes you’ll see heavy activity, and for a while Picasa may show duplicate folders, double the number of pictures you really have, but will eventually sort it all out. 

Setting up the “clients” or “satellite” computers

These are the computers that have no local Picasa information, we just use them to access our main libraries from the “server”.  Ideally we would just map the public drive on the server as a network drive under P: but we’ll run into a syntax problem.  On the main computer Picasa will prefix our watched folder setting, changes \P\Pictures to C:\P\Pictures, which works just fine on the main computer but not on the satellite ones.   Picasa’s watchedfolders.txt does not accept a \\Computername\Foldername designation, it has to look all local.

So we go back to our friend… yes, you guessed it right, symbolic links. But now even this old friend lets us down: we cannot define a symbolic link to a network folder, only a local one. Oh, well, we’ll outsmart the system again, by combining network mapping with symbolic linking: we’ll map the network drive to an interim name first, then link to this interim drive-name.  Steps:

From windows, map the \\MainComputername\Users\Public\ folder as drive O:

Make sure there is no Picasa2 or PicasaLib folder in \Users\username\AppData\Local\Google

Get an elevated cmd prompt

cd \  

mklink /d P  O

cd  \Users\username\AppData\Local\Google

mklink /d Picasa2  O:\PicasaLib\Picasa2

mklink /d Picasa2Albums O:\PicasaLib\Picasa2Albums

Repeat the last three steps for all user accounts that should access Picasa from this computer.  Logically now you would have to open Picasa and changed the watched folders to P\Pictures, but there’s no need: it’s already set up on the server machine and you’ve just told Picasa to pick all parameters and data from there.

In other words, you’re all set.  Needless to say, this only works as long as your “server” is turned on:-) but then all computers on your network will see the very same photos, and all editing, manipulation, face or geo-tags, albums… are immediately updated in the central database and reflected on all computers, no matter where you originate them.

Warning:  as stated before, I have not tested what happens when multiple users access / attempt to update Picasa data at the same time, but I assume it’s not a very good idea.  We’re ‘cheating’ here, Picasa was not designed to work in a multi-user environment, so let’s plat safe: only one computer and one user should access it any one time.

Conclusion

We’ve just turned a hopelessly single-user, single-computer product into a networked one. Sort of.   It’s obviously just a workaround, and…well, read my disclaimers again.

Now, let’s remember, Google isn’t really a PC or local network software company. They are The Web Pioneers. I think the long term solution will be much stronger integration with Picasa Web Albums.  Currently you can mark your folders / albums to synchronize with the Web version, but it’s one way, from PC to Web only.  That’s not what I call full synchronization.  If you change anything in Web Albums, it’s not reflected back to your local Picasa library.  I believe the future is full two-way – actually multi-directional – synchronization, where Web Albums become the conduit between any number of client computers that access Picasa.  It’s not impossible, services like Syncplicity do similar synchronization – Google Picasa has to embed it in their Web capabilities.  It’s time for Google to create the seamless online / offline photo management environment.

(This how-to guide was originally posted as Part 1: the Problem and Part 2: the Solution @ CloudAve)

Image via Wikipedia

Fellow Americans, you just received the unexpected gift of a few free hours: don’t have to sit glued to your TV sets watching President Obama deliver his State of the Union address. He’s got more important things to do: Jury Duty back at home, Chicago.

Or not … the Court relieved him of duty when notified by the White House that he’d be quite busy for the next few years.

Summoning a sitting President is not that unusual: former Presidents Reagan, Bush and Clinton were all summoned, but relieved of duty. Which is all right. We’re electing Presidents to run the country. Everyone gets this – except one blogger at The US News and World Report, who happens to be a former White House speechwriter for President George H.W. Bush (surprise?): she thinks President Obama should serve. She speaks out of experience:

When I was a spokesman at the Department of Justice in the early 1990s, I was called for jury duty. Because I was promoting the attorney general’s pro-victim, anti-crime positions daily, I figured the judge would take one look at me and I’d be let off. No such thing. He asked if any potential jurors knew the prosecutor or the defense lawyer personally, and hearing no affirmative answers, started the trial. I couldn’t believe I was kept on the jury, but I have to say, it was an eye-opening experience. I learned a heck of a lot about our criminal justice system–good and bad–and I now think everyone should serve on a jury, whether they’re the president or not.

Sour grapes? She was not let off, so the President shouldn’t either. Gotta love her perspective thought, comparing the DOJ spokesman (shouldn’t it be spokesperson?) position to that of the President. Lady, get a life!