Last tended on 30 December, 2019 (first created 30 December, 2019)

This is a project I started in December 2019 for myself. The goal is to create my own “ideal” bookmarking tool. If and when it works it might be useful as a service to others too. I optimistically registered a domain name for that eventuality: linqurator.eu

I see three layers to it:

  1. individual bookmark collections,
  2. a social layer like Delicious used to have,
  3. and a visualisation and analysis layer.

The latter is something that currently doesn’t exist as far as I’m aware (though examples of analysing / visualising bookmark collections do exist, just not as a regular feature of a bookmarking tool)

Key elements I am taking as starting points for the design:

  • Can be used offline (working with bookmarks that is, not the bookmarking itself obviously)
  • Fully based on PHP/Mysql as most commonly available web infrastructure
  • Useful stand-alone
  • More useful if connected to others (why?)
  • Using IndieWeb protocols for connection and interaction where useful
  • GDPR compliant, and on EU based servers (why?)

First I will attempt to build something I can and want to use myself. After that I’ll decide on adding the ‘social’ part, and beyond that the visualisation / analytical part across multiple collections.
I want to approach this in a number of small sprints, otherwise it will never happen. Two week sprints, with 13 of them to get to a working prototype for myself.

The first sprint is doing a first general plan working backwards from the imagined final service to first steps.

Currently imagined elements to sprint towards:

  1. General plan working backwards from imagined result
  2. Basic database design
  3. Basic API creation
  4. Import my Delicious archive through API
  5. Display page
  6. First add bookmark form
  7. First bookmarklet
  8. Basic timeline view of bookmarks and tags
  9. First search form
  10. Attempt Threading, for e.g. a Linkpost, or as input for a draft blog posting
  11. Parse original metadata / microformats of a bookmark
  12. Put a saved bookmark in archive.org for a permanent external reference (might not work for paywalled pages)
  13. Save the full page of a bookmark locally (to not bump into linkrot/paywall later, and for local full text search options)

5 reactions on “Linqurator Project

”

  1. A (short) list of applications that were very useful to me at one time, but then went away or astray. The question is, could one redo these in a current and useful way?

    Dopplr: showing simple travel plans (city and dates) to facilitate serendipitous meet-ups outside your regular movements. (went away after being acquired)
    Delicious: social bookmarking (went astray by dropping/breaking-by-redoing the social functionality, then went away). Have a project on the shelf to redo this for myself, called Linqurator.

    Skype: p2p voip (went astray by dropping p2p in favor of centralised servers, after acquisition by Microsoft). See this and this posting asking questions about the current p2p voip space.

  2. This is the frontpage of my emerging wiki-like collection of semi-permanent content. Where blogposts form a ‘river’ of items, for reference it is useful to have a range of more static ‘pools’ of content. Both to provide additional context and background to blogposts, as well as a useful documentation in itself. Documentation of ongoing work, reading, research, or experiments. (April 2018).
    Topics

    Networked Agency
    Ethics by Design
    Indieweb
    Information strategies and PKM
    Site tweaks
    Linqurator bookmarking tool
    Bringing Slides home / self-hosting my presentation slides
    Federated bookshelves

  3. Bookmarked A Visual History of Delicious Bookmarks by Sarah Hibner
    Surprised to see a capture of my old Delicious profile in this sequence of screen shots. I still think there’s room for a Delicious remake, and I even at some point started sketching out my own approach under the moniker Linqurator (currently way way back beyond the furthest backburner)

    After his acquisition of Delicious, Cegłowski made the decision to shut down its functionality while leaving it in read-only mode as of June 15, 2017. He explained that his motivation was to preserve an important piece of internet history, something I agree with and appreciate wholeheartedly.
    Sarah Hibner

  5. On #2022/11/12 I have created a VPS running Debian 11. It is a CX41 from Hetzner.com, and I installed Yunohost on it using this description.
    Yunohost then provides a GUI to maintain the VPS. It also does the diagnosis and provides the infromation to fix issues. The first experiences are encouraging.
    From 2014 I’ve used a VPS for a few years, but it became too much of a chore, and in the end I shut down the entire VPS, because it became unmanageable. I stil haven’t fully deleted it, but I should.
    Yunohost also supports the installation of all kinds of applications (like softaculous on cpanel for hosting environments), which makes things easier.
    It’s an experimental space first and foremost.
    I moved my (and E’s) Mastodon instance over to it (and save on the monthly fee I paid for Masto.host before, folding it into this one). I’m also interested to see if using e.g. Bookwyrm and Pixelfed over it brings use value. These are all AP based applications. Or it can be a testing ground for other projects, e.g. Linqurator.
    I have installed Fresh RSS read on it, and a personal NextCloud instance on it, both for my own use as well as for experimenting with apps in Nextcloud, before running them in my business’ Nextcloud.

Comments are closed.

Mentions

Bookmarks

Likes