Annotation of bookie/www/index.html, revision 1.12
1.4 will 1: Bookie is a personal attempt to keep the bookmarks that I have at home
2: synced with the bookmarks I have at work, and a way of solving my
3: frustrations in sharing bookmarks with other people over computers. It also
4: is an outgrowth of the bluesky <a
1.3 will 5: href="http://www.mozilla.org/blue-sky/ui/199805/bookmarks.html">good
6: bookmarking</a> and <a
1.4 will 8: bookmark indexing</a>. In addition, there are sites which attack this
1.5 will 9: problem from another angle: <a href="http://renaghan.com/bookmarker/">Bookmarker</a> and <a href="http://www.webwizards.net/useful/wbbm.htm">Web-Based Bookmark Managers</a>.
1.4 will 10:
11: <p>Quite frankly, bookmark management sucks. Every person I know has a
12: collection of bookmarks which have grown over months if not years. Not only
13: the bookmarks themselves but the structure of the bookmark directory is
14: critical. Yahoo's origin and real, underlying purpose is as a huge
15: collection of well organized bookmarks. Yet while it is easy to send a URL
16: over the web, sending branches or entire trees is impossible. It is
17: impossible to share the same bookmarks folder with several people, so that
18: all information can be synced over a department. And it's really hard to
19: keep bookmarks synced between several locations.
21: <p>The roaming access feature in Netscape goes in the right direction of
22: solving these problems, but RDF is the perfect answer to these problems.
23: Whenever a browser wants to see bookmarks, it can make a request to a
24: central bookmark server, and receive streamed RDF. Likewise, whenever a
25: bookmark or branch is submitted, RDF can be sent to the server and synced
26: with all the other clients.
28: <p> Of course, this is barely scratching the surface of what Bookie could do
29: -- it could invalidate useless bookmarks, keep a cache of bookmarks for
30: you... it could keep private bookmark folders which you could only see by
31: typing a password... It could provide folders with multiple parents so that
32: you could have the equivalent of symlinks in folders... It could rearrange
33: or delete bookmarks according to your own criteria (popularity, last
34: updated)... You could have limited access to bookie allowing you to add only
35: annotations to a bookmark, or submit links on an honor system so that the
36: most popular float to the top... You could adjust your filter so that only
37: the oldest or the newest bookmarks show up.
1.7 will 39: <p>
1.12 ! will 41: <li>The server is working, although it still is read-only.
1.10 will 42: <li>You can import bookmarks into the database via a perl script[<a href="#script">1</a>].
1.8 will 43: <li>You can read bookmarks out of the server[<a href="#server">2</a>], using the
44: included client[<a href="#client">3</a>].
1.7 will 45: </ul>
1.4 will 46:
47: The mozilla client will connect to the server, but I've had some troubles
1.7 will 48: getting the RDF from the server synced up with the user interface.
1.11 will 50: <p>Will Sargent <<a href="mailto:firstname.lastname@example.org">email@example.com</a>>
1.7 will 51:
1.2 will 53:
1.8 will 54:  <a name="server">/scripts/server.bat, assuming you have the database up and working...
1.7 will 55: <p>
1.8 will 56:  <a name="script">/scripts/perl/importdb.pl
1.7 will 57: <p>
1.8 will 58:  <a name="client">/scripts/client.bat
1.2 will 59: