Though I doubt anyone would bother to try to hack this site... (warning: nerdiness follows)

I've recently shifted things such that all the actively-used bits of this site are now available over SSL. Been hanging out in too many coffee shops lately with unencrypted wifi lately that I figured that I'd try to make the switch towards more frequent encryption for web traffic.

Strangely, unlike for web servers where you've long been able to serve many a web site from a single IP, this wasn't the case until recently for web sites. Server Name Indication now allows multiple secure sites to share a single IP and is supported by the more recent browsers. Basically it works in all the browsers I use meaning that I can access those locked-down domains (wiki, biblio) that I use and any non-supported browsers should default to this site.

One thing that's a little annoying is that I'm basically stuck using a self-signed certificate, dealing with too many error messages, or forking out way to much money. A basic SSL certificate can be had fairly cheap -$8-9.5/year - but the wildcard SSL certificate that's needed to handle a single certificate for multiple subdomains without spitting out errors is more than $100/year. (Though server-name indication allows multiple certificates to be used for the same IP, at the moment that's not supported by my web host's control panel - and I figured that I've pestered tech support more than enough already to get the current SSL support working). Of course I'm probably the only one crazy-enough to start accessing this thing over SSL so I'm not too worried about ensuring that those accessing the site get ahold of the right SSL certificate.