Strategy re hypothes.is

I wondered if you might revisit your plans re integration with hypothes.is (mentioned in a response to a [feature request][1] back in July) given the strength of their [recent announcement][2]?

I like the way that metaPDF is shaping up but I fear there will be a duplication of mark-up options and hypothes.is has certainly got considerable traction now.

Thanks.
[1]: Automagically check for corrections, corrigendums, and retractions
[2]: https://hypothes.is/annotating-all-knowledge/ “recent announcement”

No we currently don’t have plans to integrate with hypothes.is.

We only can focus on what our customers want and even though there might be some overlap it will never be 100% the same what a coalition with the goal to “annotate all knowledge” wants.

For a small company like us it would be a huge risk to base a core feature of our product on somebody else’s technology. In the case of hypothes.is we can’t do that. A press announcement is not traction.

MetaPDF uses a well established open ISO standard to save its data and it can be exported as JSON. That seems to be a safe strategy for us and our customers.