Just looked at the update. "we have migrated Cryptocat's network into new servers inside a Swedish nuclear bunker" Holy Crap!

Also love the photo of said bunker.

https://blog.crypto.cat/wp-content/uploads/2013/02/Port_sn_0...

Upon visiting that blog.crypto.cat URL, Chrome tells me "Incorrect certificate for host / Error 150 (net::ERR_SSL_PINNED_KEY_NOT_IN_CERT_CHAIN): The server's certificate appears to be a forgery."

The main crypto.cat page loads fine over HTTPS (certificate has sha1 thumbprint ‎d1aa1c1037202e359f224e407d7f84a0e8a94dd7 which i see is advertised on the erroring blog.crypto.cat page).

Why has the certificate changed? Why did the CA signing the SSL certificate change? Is there any forwarding message signed by the original certificate?

It's a bug in the Chrome 25 Beta. Will be fixed on stable release.

en.wikipedia.com/wiki/Pionen

Don't think this can be profitable in any way. What would you do with the dead tree books?

Ship in bulk to poor countries for use as bricks. There's clearly no other profit to be had for them.

Sell them?

Old books have essentially no value. Cracked (of all places) did a story of how hard libraries work to get rid of books, and all the problems that they face just trying to even put them in the trash.

http://www.cracked.com/article_19453_6-reasons-were-in-anoth...

any suggestions for better implementation? we're for sure looking for ways to improve.

I use a custom application engine built from ground up to create beautiful Swing and Java2D powered apps, i also use a very fast DB engine called H2, that's pretty much it honestly, this is the accumulation of around a year's work creating the back-end and front-end all on my own