News for hackers. Stuff that matters.
Re:Gotalk by zimbatm on Thursday January 22, 2015 @05:01PM (#8932055)
Wouldn't it be more fair to compare Gotalk to Kite's underlying dnode-protocol[1] ?

Personally Gotalk's protocol seems much better thought out; size-prefixed messaging, rpc & streaming support, multiplexing (especially important with WebSocket). The only missing bit would be some form of heart-beating.

* [1] https://github.com/substack/dnode-protocol

Re:Gotalk by jra_samba on Thursday January 22, 2015 @05:27PM (#8932178)
Messages need to be encrypted by default.

No more cleartext protocols on the network anymore please, for obvious reasons.

Re:Gotalk by rasmusfabbe on Thursday January 22, 2015 @08:34PM (#8932959)
With Gotalk, you can use the byte-buffer request and response functionality (instead of the JSON-encoding versions) and e.g. dec.XORKeyStream(inbuf, payload) in your handler when receiving a payload followed by enc.XORKeyStream(payload, outbuf) when responding.
Re:Gotalk by irq-1 on Friday January 23, 2015 @09:34AM (#8934997)
You could add symmetric encryption before and after putting anything on the network, and let users turn it on with a simple setting. Here's the fun part: you could use go generators to create a local key when the package is compiled. Then you wouldn't need to embed a key, or ask the user to generate and pass in a key.