A few hours ago I couldn't open Fargo in Chrome or Safari any longer--it would show me the pre-login stuff but never drop my name into the upper right or add the icons on the left. My first guess was that tinkering with an old copy of TiddlyWiki on the same browser had messed things up--it too operates in the browser, I believe, but I didn't imagine the conflict until later. Anyway, that's my guess. When I tried to open my published pages, I started getting error codes that said something like tag opml incomplete line 2. I know, I should have written it down exactly.

I tried restarting the computer. I tried emptying browser caches. I picked up a new browser and then another. I logged into Fargo via another Dropbox account, finally, in one of those browsers, and it did operate. I inspected the opml files from the original Dropbox account in that handy OPML software from deep in Dave's site and saw that the named outline was full of code and looked kind of like RSS but the other outlines were just outlines. So I guessed that the named outline was corrupted. I was able to load a backup copy of the named outline from Dropbox into the OPML editor and see that it was not wrapped in code but looked like a regular outline.

So I guessed that a backup copy from earlier in the day of the named outline might load, and I tried it, and it did. Fargo opened again and all the files were there, all the tabs, all the scripts, etc. Current theory: somehow the named outline became corrupt, and it wouldn't surprise me if it had to do with tinkering with TiddlyWiki while Fargo with sitting in another tab. Something like that. Browser memory wars?

My impression: the Dropbox backup is strong, with so many copies on hand to use if needed. From a position of ignorance I will guess that there is a danger if two apps that play in the browser memory are in the room at once. Or maybe if the two apps both use Java? I don't know, but in trying to be a good citizen I report the afternoon's festivities! It's good to be home safe.