Delvicious will make it easy to find what you’ve found before, no matter how disorganized you are.
A mashup of the Delicious API and the Google Custom Search Engine API, Delvicious will allow users to easily perform a full-content search of only the sites that they have bookmarked, freeing them to delve fearlessly into muddled memories of poorly-tagged favorites.
Links and Related Posts:
- Delvicious on Appspot (currently very incomplete)
- Delvicious on GitHub
- 05/04 — Programming A to Z — Delvicious Alpha
- 04/15 — Programming A to Z — A Delvicious Milestone
- 03/31 — Programming A to Z — Delvicious, Django and Assignment #8
- 03/10 — Programming A to Z — Delvicious, Initial Implementation Details
Over the years I have accumulated a couple thousand web bookmarks (also known as favorites in some browsers), and for a few months I’ve been looking for ways to make them more accessible. The in-browser folder-based bookmark organization tools were overwhelmed long ago by the sheer number of links, and I’ve more recently been exploring online tag-based services such as Delicious and Diigo. These sites offer solid tagging systems, cross-browser compatibility, and some interesting social features. Their search functionality, however, is relatively weak. You can search your bookmarks by tag or keyword, but the tags need to be user-defined and the keywords must be found in the title or description.
One of the many services Google offers is called Custom Search Engine, which allows you to create a Google search of the corner of the internet of your choosing. Google provides a powerful set of configuration options for specifying the site(s) to be searched and tweaking the results to your needs, as well as an API for creating and modifying these search engines programmatically.
My goal with this project is to use the Delicious API to fetch a user’s bookmarks and provide a dynamically-updated custom search tool for that user that indexes only those bookmarks. I plan to host Delvicious on the Google App Engine so that it can be a scalable tool for both myself and others.
Thanks to John Rutherford for for coming up with the name, which is often, but not always, the hardest part of doing anything on the web.