-There is an alias for rebuilding FF3Searches.txt -- it is f3sx
-There is an alias for viewing content similar to what's here -- it is f3sreadme
-Values in ExtractFF3Searches.ini, should be specifiable using
environment variables such as %APPDATA%.
-ExtractFF3Searches.exe may be run with command line arguments (the
values override any values in the .ini file). A value for ProfileDir
may be specified and optionally -v which is equivalent to Debug=1.
-The extraction utility analyzes daily backups of bookmarks that
Firefox creates. The extracted information may be out-of-date
because the backups are too. The most up-to-date information is
stored in a file which Firefox locks while it is running in a manner
that appears to prevent other programs from accessing it.
I presume many people often have Firefox running, so I looked for
another way to access information which might often be comparably
good. For more details, please read the following posts: https://www.donation....msg195345#msg195345
One work-around is to wait 24 hours and extract again.
Another might be to use the Backup functionality via Firefox's
Organize Bookmarks window (though, I've found the latter to be
somewhat, delayed (may be?) in opeartion).
A longer-term work-around might be to convince Firefox developers to
make bookmark data more readily accessible -- preferably without
users having to install anything additional or make any configuration
I wasn't keen on copying the locked file to another location and then
accessing it. Perhaps my leanings on this matter might be
-Firefox 3.6 seems to generate invalid JSON -- at least the bookmark
backups in alleged JSON format are not necssarily strictly JSON. My
local copies have trailing commas in places where there should not be
-- at least, that's my current understanding. This led me to pass on
using Douglas Crockford's json_parse.js, sadly.
-Tested with Firefox 3.6 and FARR 2.86.01 around 2010-03-01 on Windows XP