News for hackers. Stuff that matters.

A comment on Echochamber.js.

Re:Echochamber.js by nacs on Tuesday July 14, 2015 @07:06PM (#9888668)
It doesn't degrade gracefully on my Lynx browser and doesn't use any form of encryption when submitting comments, making it vulnerable to 3-letter agency interception.
[ Parent | on HN ]
Re:Echochamber.js by mjrbrennan on Tuesday July 14, 2015 @07:25PM (#9888757)
Richard Stallman is that you?
[ Parent | on HN ]
Re:Echochamber.js by phn on Tuesday July 14, 2015 @07:08PM (#9888676)
I don't know if you're being sarcastic, but you realize it doesn't actually submit anything, right?
[ Parent | on HN ]
Re:Echochamber.js by ekso on Tuesday July 14, 2015 @07:09PM (#9888681)
He was being sarcastic.
[ Parent | on HN ]
Re:Echochamber.js by abrown28 on Tuesday July 14, 2015 @07:11PM (#9888688)
Which 3 letter agency do you work for?
[ Parent | on HN ]
Re:Echochamber.js by irishcoffee on Tuesday July 14, 2015 @07:24PM (#9888752)
Do you not understand how this code works, or are you also being sarcastic?

I'm guessing sarcastic. =))

[ Parent | on HN ]
Re:Echochamber.js by bbcbasic on Wednesday July 15, 2015 @12:47AM (#9889764)
No in-memory encryption though. In-brain encryption is the workaround, just type the resulting base64 into the input field.
[ Parent | on HN ]