codedust
commented
6 years ago Hi Adrian,
Sorry for the late response. In Signal-Browser, end-to-end encryption is handled client-side using Javascript. Hosting Signal-Browser on a webserver wouldn't change that behaviour since all data is stored client-side in the browser. Storing the key material and the messages server-side would require major changes to the client.
If you plan to do so, I think it would be easier to use an existing Signal protocol implementation and provide REST bindings for a simple web app (like https://github.com/codedust/WebTox for the Tox protocol)
Hey Codedust,
Your projects and interests align with mine so I thought it best to contact you here and ask if you've got any plans to make a signal web client since the move to electron?
It'd be awesome to be able to host some files yourself, include a configuration / auth file of some kind and be able to run the electron interface exposed over a TLS / digest auth protected website - the server you deploy it on holding the enc key and message queue.
Your thoughts? I have the sysadmin side of things but not the dev knowledge.