I'll go ahead with setting up Drupal then. I don't think we should make the site https by default. It's still very unusual for the public part of sites to be https, probably because it introduces potential technical complications, delays and greater server load. As a user I'm a little annoyed when it takes time to verify the identity of some no-name site I casually came across. For me it seems like https sites fail to load a lot more often. The important thing is to have SSL available for those who need it. Those who need SSL I think know to try inserting an "s" after http and see if it works. SMF has code that changes all the links to https if the URL handed in is https. We could add a note on the registration page that if you want SSL, you can change http to https at any time and approve the self-signed certificate, or a link that does it, and the TOR page can mention it too. We can look into getting a certificate later when things have settled down. With Class 1, no changes are allowed for a year, which is a risk if we find issues with the current host and have to change IP. mmalmi@cc.hut.fi wrote:
Sponsors 
