Update 15 October: https is now being enforced at diglloyd.com; all non-https access is redirected to secure https access.
In place at diglloyd.com is support for TLS/SSL aka https.
There should be no difference in behavior other than the little lock icon in the address bar, but please report any anomalies with https, since server-side code could possibly have a bug in some oddball case involving URL handling.
There is nothing sensitive to secure here on this site, since diglloyd.com never sees credit card info*, does not store personal data other than email (even offline)*, thus there is nothing of any sensitivity on the server at all.
Still, some people like everything encrypted (cookies and such), and Google now makes https support a factor of about 1% in page rankings. Assuming no difficult issues crop up, I’ll be moving to https for MacPerformanceGuide.com and WindInMyFace.com as well (these sites can use https right now if specified, and you accept the certificate when prompted).
* Diglloyd.com never (never!) sees customer financial information (PayPal handles all this), so auto renew is impossible, nor can diglloyd.com accept credit cards directly (PayPal can).
** The diglloyd.com web server contains only username, email, and cryptographically hashed password for login purposes— the bare minimum.