Show HN: Node.js port of WhisperSystem's libsignal

Re:Show HN: Node.js port of WhisperSystem's libsignal by TheAceOfHearts on Monday October 16, 2017 @04:15AM (#15481630)

One of the nice things about JS versions of stuff is being able to run it everywhere. With that being said, I'd be skeptical of using this since it doesn't appear to have any tests at all. How do we know it's actually compatible with libsignal?

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by mschulze on Monday October 16, 2017 @05:38AM (#15481965)

> One of the nice things about JS versions of stuff is being able to run it everywhere.

To my knowledge node does not run on SPARC processors (because V8 doesn't).

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by Zoon on Monday October 16, 2017 @07:06AM (#15482362)

I remember reading that they made it engine-agnostic a while ago.

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by kristiandupont on Monday October 16, 2017 @10:50AM (#15483561)

That doesn't (yet) work with native libraries though.

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by jdc0589 on Monday October 16, 2017 @10:37AM (#15483464)

yep. example: https://github.com/nodejs/node-chakracore

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by egeozcan on Monday October 16, 2017 @04:20AM (#15481656)

This has a native part written in c and only runs on node.js v8 and up, according to the package.json.

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by qznc on Monday October 16, 2017 @05:00AM (#15481793)

So it is "bindings", but not a "port"?

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by tooker on Monday October 16, 2017 @11:44AM (#15484005)

The C components are just a few emscripten compiled curve25519-donna and ed25519 functions for elliptic curve routines. It comes directly from the web library without any alteration. Honestly I was surprised at how well it works and the performance isn't too shabby. I did several investigations of replacing it with libsodium and others but the the emscripten builds have been pretty reliable for us..

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by jszymborski on Monday October 16, 2017 @11:28AM (#15483869)

The original version is written in Java, which sorta invented "run-it-everywhere"

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by dabockster on Monday October 16, 2017 @12:09PM (#15484267)

Meh, I personally prefer "complie-it-everywhere" since you gain all the speed benefits of running it native.

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by justinjlynn on Monday October 16, 2017 @02:45PM (#15485652)

Well, to be fair, with Java you are compiling bytecode everywhere before and while you run. So, you're not wrong.

[ Parent | on HN ]

Re:Show HN: Node.js port of WhisperSystem's libsignal by dabockster on Tuesday October 17, 2017 @02:07PM (#15493190)

Still in the JVM, though. I was thinking more bare metal.

[ Parent | on HN ]