I am confused by your use of "OTR". Based on [1] this doesn't seem to be an OTR implementation as those concerned with encryption might define "off-the-record", correct? I think the term may be confusing.
I understand the name is confusing. I was a long way into naming everything about the project QOTR before I realised that OTR is best used if the protocol is implemented, instead of taking it as general concept.
I plan to re-write the application (at least the front-end, which does all the encryption stuff) based on the reviews and if people think that it is actually an idea worth pursuing. May change the name as well.
Haven't we already established that crypto served over the internet is not a good idea (because a malicious actor can own the server and provide bad JS)?
I understand the name is confusing. I was a long way into naming everything about the project QOTR before I realised that OTR is best used if the protocol is implemented, instead of taking it as general concept.
I plan to re-write the application (at least the front-end, which does all the encryption stuff) based on the reviews and if people think that it is actually an idea worth pursuing.
Currently the README file states that `AES-CES` is being used.
[1] https://github.com/crodjer/qotr/blob/master/app/models/chann... [2] https://github.com/digitalbazaar/forge/blob/e14eb1e17fbabcc8...