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

1.1       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
                      5: href="http://www.mozilla.org/blue-sky/ui/199805/bookmarks.html">good
                      6: bookmarking</a> and <a
                      7: href="http://www.mozilla.org/blue-sky/misc/199805/collaborative-bookmark-index.html">collaborative
                      8: bookmark indexing</a>.  In addition, there are sites which attack this
                      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>.
                     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.
                     20: 
                     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.
                     27: 
1.2       will       28: <p> Of course, this is barely scratching the surface of what Bookie could do.
                     29: 
                     30: <p>It could invalidate useless bookmarks.
                     31:  
                     32: <p>It could keep private bookmark folders which you could only see by
                     33: typing a password. 
                     34: 
                     35: <p>It could provide folders with multiple parents so that you could have the 
                     36: equivalent of symlinks in folders. 
                     37: 
                     38: <p>It could rearrange or delete bookmarks according to your own criteria. 
                     39: 
                     40: <P>You could have limited access to bookie allowing you to add only
1.1       will       41: annotations to a bookmark, or submit links on an honor system so that the
1.2       will       42: most popular float to the top.  (See 
1.3     ! will       43: <a href="http://www.ilrt.bris.ac.uk/discovery/2000/09/rudolf/recommender.html">this paper</a>
1.2       will       44: for more information).
                     45: 
                     46: <p>You could adjust your filter so that only the oldest or the newest bookmarks 
                     47: show up.
1.1       will       48: 

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>