| date |
description |
mp-syndicate-to |
post_meta |
resources |
tags |
title |
type |
url |
| 2022-12-08 19:20:00+00:00 |
A 2nd alpha release of a joplin/hypothes.is integration plugin |
|
|
| name |
src |
| feature |
notes.jpg |
|
|
| open-source |
| indieweb |
| hypothesis |
| pkm |
| tools-for-thought |
| digital-garden |
|
Joplin Hypothesis v0.0.2 |
posts |
/2022/12/08/joplin-hypothesis-0-0-2 |
I've just released v0.0.2 of my Joplin Hypothesis plugin.
This version adds a couple of fixes that make it a lot more useful. Firstly, users can now import all of their annotations to Joplin rather than just the most recent 20, This is because I am now grabbing annotations via the annotations API instead of the user's Atom feed. If you have 10,000 annotations this might take a little while, but it does mean that you could practically and easily import all of your hypothes.is annotations into Joplin so that you have a local copy of everything.
The second, related fix prevents the plugin from re-generating notes that have been deleted (in v0.0.1 if you deleted any annotations they would be recreated the next time the plugin ran). Now, I am keeping track of the date of creation for the most recent annotation in each batch and using this to filter API results. That means that if no new annotations have been added since the last run time, the plugin will not do anything. In the case that the user wants to get old annotations back they can reset this timestamp via the Tools menu.
I'm really excited about the plugin, but I feel that there's one final piece of technology missing before it is viable as a really useful tool: the ability to aggregate multiple annotations into a single note - one Joplin note per document/website. That way if I make 10 annotations on a single document I don't end up filling Joplin with lots of tiny notes. I plan to work on this feature for the next release v0.1.0 - then I will also approach the Joplin dev team about getting my plugin listed on the marketplace.