Re: Bring up a screen giving option to open a series of orgmode files

[Jean Louis]

* Ihor Radchenko <yantar92@gmail.com> [2020-12-13 03:39]:
> Jean Louis <bugs@gnu.support> writes:
> 
> > For private annotations with hypothes.is one can install it on own
> > server and protect system for one's own group. That will do only a
> > group that is serious enough or have serious demands for annotations.
> 
> > Myself I do not prefer having too much software installed online
> > especially not databases that are private. What is private I keep off
> > the Internet. If I wish to communicate over Internet to somebody I
> > always establish first encrypted line.
> 
> I have hypothes.is installed inside docker container locally. No serious
> protection is required in such case (at least, no more than one would
> use to protect private files from dangerous software like browsers).

I can install it on VPS which is definitely in plan. Locally I do not
think so, as locally I have dynamic knowledge repository that may
export to Org if necessary or accessed by collaborative group of
people. 

> Public annotations would better be just exported to a public server
> (automatically or not).

When they are public yes. I have it rather private.

> > example.com/1/2/3/4 for ID 1234
> >
> > That would be HTML with PDF annotation where user could open PDF
> > inside of that HTML or click on the PDF to open it. I do hope that
> > pdfjs does support specific page jumps. And such annotation on HTML
> > should work with or without Javascript. Those without can simply open
> > PDF file and manually jump to specific page as annotated and
> > instructed.
> 
> I am not sure how it is different from using hypothes.is for the same
> purpose. Note that hypothes.is uses pdf fingerprinting, so you don't
> even need to store pdf on server side. If user can open the pdf
> (obtained from you directly, for example), hypothes.is will
> automatically show the up-to-date annotations shared via public
> hypothes.is instance for that particular user.

The difference is that annotation is separate from file, and there is
no need for Javascript. Hyperdocument may contain the PDF file and the
annotation together, dispatched to somebody, or referenced from WWW
page. It is lightweight. HTML file can be very small and speedy
loaded. 

> > Then I would inject web server password protection and protect it from
> > public. But that does not protect the document of those who could
> > intrude into the server and also does not protect from cracking
> > attempts as username and password are not alone well secure. Better
> > would be having the encrypted HTML that is protected by user's private
> > PGP key, but I have no idea if such technology exists yet.
> 
> hypothes.is uses OAuth mechanism with fine-grained control over the
> access to various annotations. Also, one can run it inside encrypted
> docker container (or even inside virtual machine) reducing the risk if
> server is compromised.

That is great yet introduces 2 different tools for one purpose. While
I support Hypothesi.is in general and will be using its hyperlinks for
some public purposes, those private purposes will remain off line and
I need not have any extra software to have my group of people learning
from annotated PDFs. They would be in local area network or VPN in
collaborative environment backed by database where they can open and
read PDFs without browser, Emacs is enough to browse it or exported to
some other format I can make it as well HTML or provide hyperlinks as
I wish, including to open it with the PDF in a built-in browser.  Each
software for its purpose. I recommended hypothesi.is but I already
have similar system built on same principles of Engelbart just as
Hypothes.is

Jean