@mdw
Using HTTPS means people between you and the server cannot see the contents being sent back and forth, it is encrypted. It does not prevent man-in-the-middle attacks.
It does offer slightly better protection from snooping parties, but you still must trust in a very untrustworthy system - digital certificates & CAs. Hate to say it but the benefits are slight in this case. Not very useful to waste your money supporting a broken X.509 certificate system.
I would be delighted to assist with setting up a backup of this site on a .BIT domain. @adam is this domain yours? We can plan for a .p2p one as well if BitsharesDNS ever puts out their offering.
I posted an article yesterday that's now being edited introducing this very topic. I am writing more even now. Tune in to read more about the political and technical issues around privacy, identity, security and censorship on the Internet today, and how blockchain technology can alleviate or solve many of the main issues.
The certificate authority system might be broken.. assuming your also trying to keep totally private from the government and powerful corporations. HTTPS still protects you for the vast majority of use cases though (i.e, most hackers and script kiddies). Encrypting the data over the wire is vastly better then sending it all plaintext..
.bit and similar domain systems would be great, but it would be kind of pointless at this stage since 99% of people that come to the site will have no idea about it or no way to even access it (your browser cant natively read info for .bit)
