8rian
Re:Big oil will die when it becomes cheaper to hail an electric self-d...
on Friday July 07, 2017 @12:29AM (#14716060)
Gasoline is 100 times more energy dense than a battery. The Tesla roadster adds 800 lbs to the lotus elise upon which it is built. Batteries have a long way to go.
Re:How Yahoo came up with its new name: Altaba
on Monday January 09, 2017 @11:43PM (#13362637)
Rural areas rely on dial up internet
Re:Comodo CEO Forum Post on Lets Encrypt Trademark
on Thursday June 23, 2016 @08:52PM (#11965457)
community.letsencrypt.org
Is secured with Comodo.
Re:Microsoft uses malware tactics to foist Windows 10 on more PCs
on Thursday June 02, 2016 @05:09PM (#11826086)
Left to their own devices, people would never upgrade. This is a security risk for MS. (Win 8 support ends January 2018). Chrome was championed for auto updating, and now all browsers do the same. Web apps can auto update whenever they want. Mobile apps auto update. Why shouldn't operating systems?
Re:Of “Bomb Clocks,” Engineers and the $70M High School Football Stadium
on Friday September 18, 2015 @12:10AM (#10237437)
In North Texas some (< 10%) of these large high school football stadiums generate positive revenue.
http://www.dallasnews.com/sports/high-schools/football-news/...
Re:Show HN: Free, instant, secure, disposable chat rooms built in Go
on Tuesday April 14, 2015 @07:19AM (#9373359)
New keypairs would be generated on the client every time you join a chatroom. Another member of the chatroom sends you the shared_key encrypted by your public key. Server knows nothing, stores no keys. Keys exchanged between users.
Javascript crypto is still a problem though: http://matasano.com/articles/javascript-cryptography/
When you re-download the codebase on every use, there is no way to ensure integrity of the code. This is the reason cryptocat ships as a chrome extension, because it is downloaded once. Even with these issues, I'd take javascript crypto + open source over nothing (or just SSL).
Re:Show HN: Free, instant, secure, disposable chat rooms built in Go
on Tuesday April 14, 2015 @06:53AM (#9373278)
I only feel safe using end-to-end encrypted chatrooms. Currently, niltalk can read every message. At the very least, AES encrypting messages by the chatroom's password will reduce reliance on SSL. But it really should use public key crypto for a key exchange between users. This is what's done by other disposable chatrooms:
https://ephemeral.pw/chat/ (Also written in Go)