#hypothes.is

<mprinc> Hi, guys, I started the local instance of the h, it is nicely answering on the http://localhost:5000/ managed to signup and login (would be easier if i got instruction to check demo /mail folder :sun_small_cloud: )

<mprinc> Now I am wondering where is some diagram or description describing in greater details architecture

<mprinc> for example currently we cannot understand even where and how (schemas, …) accounts are stored, similar with annotations, etc

<mprinc> NOTE: we just installed h, client, browser_extension so we are quite new with code, and therefore would appreciate more architectural-wise documentation

<mprinc> we need to experiment with extending `client` with tagging, etc, then extending `h` to follow up, or expand, or redirect to our knowledge storage, etc

<mprinc> do we need to go through code to figure out the way to do it or is there more detailer documentation than http://h.readthedocs.io/en/latest/ , http://h.readthedocs.io/en/latest/developing/in..., http://h.readthedocs.io/projects/client/en/late... ? Thanks!

<mprinc> Another challenge: I want to connect `browser_extension` with the local instance of `h`. I followed the http://h.readthedocs.io/projects/client/en/late... When I choose the `sign up / log` in in the browser extension, i get the OAuth popup :

http://localhost:5000/oauth/authorize?origin=ch... I get the error: Error authorizing application Missing client_id parameter. TEST: When I add it manually in a separate tab:

http://localhost:5000/oauth/authorize?origin=ch... it works, but extension is still not recognizing, etc Where I can configure the: `client_id` inside the `browser_extension` or `client` (btw, i did `npm link hypothesis` inside the `browser-extension` fol

<dwhaley> @mprinc

<dwhaley> Here are a few diagrams:

<dwhaley> https://drive.google.com/open?id=1iwa1oox0sMO1o...

Hey all. Is there a way to use the JS-Client with a completely different backend? Background is that we already have a comment system and would like to include comments from the website there

<mprinc> Thanks, @dwhaley this helped to understand the structure!

<mprinc> Is there any chance that there are similar diagrams, maybe on a bit closer level, with the name and relationship between software components, etc?

<robertknight> Yes, if you implement a compatible API in your alternate backend then you could configure the JS client to use it.

<robertknight> The other option would be to build a system that syncs data between an “h” instance and some other service.