Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OTR #51

Open
nb333 opened this issue Mar 13, 2014 · 7 comments
Open

OTR #51

nb333 opened this issue Mar 13, 2014 · 7 comments

Comments

@nb333
Copy link
Member

nb333 commented Mar 13, 2014

Based on the feedback we've received from multiple people regarding our current structure, we are trying to implement OTR, instead of the custom protocol we had in mind.

Please let me know if you're interested in helping. :)

@tarqd
Copy link

tarqd commented Mar 14, 2014

Implementing it yourself is definitely not the way to go. Why not use the already battle-tested otr4 library. It's been compiled to javascript with emscriptlen so it's pretty much ready to go! There's also a javascript binding to the native library if you're using node.js server-side

@dsoprea
Copy link

dsoprea commented Mar 14, 2014

How is OTR useful in a communications library? Isn't it just for IM?

Dustin

On Thu, Mar 13, 2014 at 9:34 PM, Chris Tarquini [email protected]:

Implementing it yourself is definitely not the way to go. Why not use the
already battle-tested otr4 library. It's been compiled to javascripthttps://www.npmjs.org/package/otr4-emwith emscriptlen so it's pretty much ready to go! There's also a javascript
binding to the native library if you're using node.js server-side

Reply to this email directly or view it on GitHubhttps://github.com//issues/51#issuecomment-37606816
.

@nb333
Copy link
Member Author

nb333 commented Mar 14, 2014

@dsoprea It can't be repurposed for HTTP?

@dsoprea
Copy link

dsoprea commented Mar 14, 2014

I asked two questions. I'm not asserting anything.

Dustin

On Thu, Mar 13, 2014 at 11:24 PM, Nathan Bernard
[email protected]:

@dsoprea https://github.com/dsoprea It can't be repurposed for HTTP?

Reply to this email directly or view it on GitHubhttps://github.com//issues/51#issuecomment-37613582
.

@dsoprea
Copy link

dsoprea commented Mar 14, 2014

On Mar 13, 2014 9:34 PM, "Chris Tarquini" [email protected] wrote:

Implementing it yourself is definitely not the way to go. Why not use the
already battle-tested otr4 library. It's been compiled to javascript with
emscriptlen so it's pretty much ready to go! There's also a javascript
binding to the native library if you're using node.js server-side

@ilsken My question was directed to you, since you seemed to be comfortable with
the idea: Is it practical to map encryption meant for an established IM
system to HTTP pipelines?

Dustin

Reply to this email directly or view it on GitHub.

@zsmahi
Copy link

zsmahi commented Apr 26, 2014

Hi,
I've googled about OTR messaging, I've found an implementation of it on Js here is it
https://github.com/arlolra/otr perhaps it can help.

Best regards.

@zlatanvasovic
Copy link

Thanks. It may be helpful.

2014-04-26 22:36 GMT+02:00 Zakaria SMAHI [email protected]:

Hi,
I've googled about OTR messaging, I've found an implementation of it on Js
here is it
https://github.com/arlolra/otr perhaps it can help.

Best regards.


Reply to this email directly or view it on GitHubhttps://github.com//issues/51#issuecomment-41480126
.

Zlatan Vasović - ZDroid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants