jack: (Default)
[personal profile] jack
I use Firefox at home and at work. Is there a way to have common bookmarks between the two?

* There are a couple of firefox plugins (bookmark sort and sync and foxmarks) which puport to do this, but I haven't quite got them to work. I'm not sure if something is inherently wrong.

* Both use ftp, and require an ftp-to-sftp bridge. (Alternatively, interactive http (I can't remember the real name) which the server doesn't. Foxmarks by default stores your bookmarks on their server, but I'd rather not do that. Google does something similar? I have a perfectly good server. And I don't really want to make either of my computers an ftp-server, even indirectly.)

* I could sync the profile bookmark files elsehow. In fact, I generally bookmark something less than once a day, so simply periodically copying the files to/from a remote location would be fine. But it should EITHER be automatic, OR not break if I forget.

* At least one of the computers must be a windows computer.

* It would be *nice* if it could sync most things, but leave the bookmark toolbar alone.

So, it seems like it should be so obvious. But what is the right method? I could have a script which copies the files, but will it break if I go home early and bookmark something?

Date: 2007-01-16 11:50 am (UTC)
From: [identity profile] cartesiandaemon.livejournal.com
Ah, hmm. I assumed that would be ok. Come to think of it, I did that manually while restoring. But I don't know if it borks if it non-atomically writes a bookmark, or similar.

Date: 2007-01-16 01:55 pm (UTC)
simont: A picture of me in 2016 (Default)
From: [personal profile] simont
Coincidentally enough, it bit me just now when I incautiously ran my synchroniser. The problem appears to be that when Firefox edits its bookmark file, it loads it into memory, and saves it out again on process exit. So I ran my synchroniser while Firefox was running; it pulled down a change from the server; I then quit Firefox, which wrote out the version of the file from before that change, effectively undoing the change. To make matters worse, I then ran the synchroniser again and it uploaded that change to the server, backing out the change I'd been trying to pull down.

Sorted it all out now, of course, but bah.