Best practices for using TiddlyWiki as a bookmark repository

#1

Hello all

I’ve decided I want to slowly migrate my 2800+ bookmarks from Pinboard into TiddlyWiki. For context, I’ve already spent a significant portion of time doing this in a different TiddlyWiki where I was storing full text local copies of each article, converted into markdown. At the time I was not really using best TiddlyWiki practices (not storing anything in fields).

I created a button to make a new tiddler for each link. The title is generated with YYYY0MM0DD0hh0mm to make a unique title. I have three fields, headline, url, and local-copy. If anyone has any examples or suggestions of how I should structure the tiddlers for bookmarks would be appreciated.

pinboard-202203061538.tid (1.3 KB)

For example I still haven’t figured out how to best display the url.

#2

I don’t have a best practice yet but I am accruing tips and tricks so sooner or later I do hope to develop a solution that should be a runner up at least for best practice.

My feeling is you/we face two issues;

  1. Bulk import from various sources
  • Perhaps only one off or occasionally
  • Perhaps from a bookmark html or favourites file
  1. The ongoing acquisition and use of the bookmarks in the repository.

Personally I would focus on the second first and once this is designed well do your bulk imports to match the design.

A good bookmarking solution should in my view allow

  • Icons against the bookmarks
  • Previews of the destination
  • Open in named target windows (stopping tab proliferation in the browser)
  • Show prety links without the protocol eg https://
  • Allow annotation, keywords, snipits from the destination and notes
  • Cataloguing and indexing your bookmarks (optional extra for any bookmark)
  • Allow you to store bookmarklets and/or drag links to or from the browser bookmarks/ favorites.

I key tool I want to develop is a “generic” tiddlywiki listing method that extracts a link field from a tiddler and uses this to list the bookmark, Ie its clickable from a list to open the URL.

Another I am developing is what I call a protocol handler. Any field holding something with a protocol prefix such as http:// https:/ mailto:// tel:// email:// is formatted into a clickable link. Extracting a friendly name, adding a default “target” and even a tooltip.

  • With a companion that allows one to paste or to drop links on a named tiddler eg; “Code Research” and add that link automatically in a field that the above protocol handler then lists within the tiddler.
  • perhaps one day a generic drop zone that looks at what is dropped and proposes one or more appropriate actions to take depending on the content.