Annotation of bookie/www/purpose.html, revision 1.6

1.5       will        1: <p>
                      2:  Bookie is a personal attempt to keep the bookmarks that I have at home
                      3:  synced with the bookmarks I have at work, and also to have shared bookmarks.  
                      4: </p>
                      6: <p>
                      7:  It is an outgrowth of the bluesky <a href="">good
                      8:  bookmarking</a> and <a href="">collaborative
1.6     ! will        9:  bookmark indexing</a>.  
        !            10: </p>
        !            11: 
        !            12: <p>
        !            13:  In addition, there are sites which attack this
        !            14:  problem from another angles: 
1.5       will       15:  <a href="">Bookmarker</a> and 
1.6     ! will       16:  <a href="">Web-Based Bookmark Managers</a>.  The most promising competitor to Bookie is probably
1.5       will       17:  <a href="">Xbelette</a>, 
1.6     ! will       18:  which has a very nice user interface although I haven't tried it myself.  
        !            19:  You may also wish to try 
        !            20:  <a href="">olbookmarks</a>, which is a Mozilla sidebar thingy.
1.5       will       21: </p>
                     23: <p>
                     24:  Quite frankly, bookmark management sucks.  Every person I know has a
                     25:  collection of bookmarks which have grown over months if not years.  Not only
                     26:  the bookmarks themselves but the structure of the bookmark directory is
                     27:  critical.  Yahoo's origin and real, underlying purpose is as a huge
                     28:  collection of well organized bookmarks.  Yet while it is easy to send a URL
                     29:  over the web, sending branches or entire trees is impossible.  It is
                     30:  impossible to share the same bookmarks folder with several people, so that
                     31:  all information can be synced over a department.  And it's really hard to
                     32:  keep bookmarks synced between several locations.
                     33: </p>
                     35: <p>
                     36:  The roaming access feature in Netscape goes in the right direction of
                     37:  solving these problems, but RDF is the perfect answer to these problems.
                     38:  Whenever a browser wants to see bookmarks, it can make a request to a
                     39:  central bookmark server, and receive streamed RDF.  Likewise, whenever a
                     40:  bookmark or branch is submitted, RDF can be sent to the server and synced
                     41:  with all the other clients.
                     42: </p>
                     44: <p>
                     45:  Ergo, Bookie.  It's a crude work in progress, but it teaches me a lot about what
                     46:  I should be doing, and lets me read and understand code written by people way 
                     47:  smarter than me.
                     48: </p>

FreeBSD-CVSweb <>