Quipu

Quipu is a simple Pinboard powered session manager.

Add to Chrome | Add to Firefox

Notice: Currently the chrome build is broken due to the manifest 2/3 issue. I don't have the time to fix the chrome builds, but there is an issue for it: #56

I have too many tabs open. I struggle to keep them organised. If I have to switch context, I often keep a group of tabs related to a topic open, or I save them in an email, or a slack message or a variety of different bookmarking services, and lose them. I fear my browser crashing and losing work.

Quipu allows me to save some tabs for later, arranged in a simple, two level hierarchy. It doesn't require me to spend too much time curating them, but it does make saving and having them available quickly.

Quipu also closes old tabs. It keeps track of the last time that a tab was active and defines a probabilistic lifetime – based on a half-life setting. The tab is 50% likely to be closed by the time the half-life has passed since the tab was last active.

Quipu uses pinboard tags to organise bookmarks in pages and cards. A bookmark can appear in multiple pages and cards if it is so tagged. Pages and cards provide no formal structure, they are for the user's visual convenience only. Bookmarks are ordered according to when they were saved.

The name quipu comes from an andean record keeping – and perhaps writing – system, which organises information in strings and knots.

Credits

Built with Svelte & Tailwind, the fantastic Iosevka typeface, drag and drop via svelte-dnd-action scaffolding using browser-extension-template

Prior Art

This extension was inspired by different tools that I have used in the past, but haven't quite done it. Here is a list of some of them:

• tab decay - where the idea of using half-lives to decay old tabs came from.
• toby – keep track of old bookmarks

Contributing

This is a simple tool that I built because I need it. I would like to keep it simple, but if you find it and you like it, and have ideas on how to improve it, I'd love to hear them.

Some notes on how to get things running:

Install dependencies

npm install

Interactively build the extension for development

npm run watch

Run a version of Firefox that hot-reloads the extension

web-ext run

or just build it:

npm run build

You can load a temporary extension on both Firefox and Chrome by pointing them to the manifest.json file on the /distribution directory after you have built it.

Make sure that your code conforms to the lint settings

npm run lint