Hi Peter, The idea is interesting and the organisation behind hypothesis seems to be interesting too. The vision video is great, but imo the implementation has some flaws atm.
I have 3 major issues: 1) There is no official API to communicate with the service. .. At least I couldn't find one. ... TiddlyWiki is not a web page, it's an application. So TW needs to be in control of its content. ... 2) To get the annotation working you need to call your own web page using theirs eg: https://via.hypothes.is/h/http://tiddlywiki.com/ So I pay for a nice domain name, just to get it hijacked. For my taste this behaviour is very aggressive. 3) IMO the TiddlyWiki workflow contradicts the annotations value. TiddlyWiki is highly dynamic. For me tiddlers only make sense, if they are refactored (according to feedback) If the tiddler content changes enough, imo the annotation linking mechanism doesn't work anymore. Having a look at there roadmap <https://hypothes.is/roadmap/> it seems they see this problem. See: "Archive annotated pages, recover orphans <https://github.com/hypothesis/vision/issues/76>" ... They want to store the old version of a page ... Which is fine in the first view. ... - But what if the original content isn't licensed that way? - What if the author of the original content doesn't want this behaviour? I really like the idea, to play nice with them but I have some concerns. just my 2 cents. have fun! mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
