The "Library Privacy Pledge" has been finalized. See my blog post at http://go-to-hellman.blogspot.com/2015/08/update-on-library-privacy-pledge.html <http://go-to-hellman.blogspot.com/2015/08/update-on-library-privacy-pledge.html> and note that I've set the "description" attribute on the blog to "Move Blogspot to HTTPS NOW." Anyhoo... Here's the status of Code4lib services: www.code4lib.org <http://www.code4lib.org/> HTTPS NOT SUPPORTED. Insecure login! planet.code4lib.org <http://planet.code4lib.org/> HTTPS NOT SUPPORTED jobs.code4lib.org <http://planet.code4lib.org/> HTTPS NOT SUPPORTED listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB <http://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB> HTTPS ONLY. Yay. http://journal.code4lib.org/ <http://journal.code4lib.org/> HTTPS NOT SUPPORTED code4lib.spreadshirt.com <http://code4lib.spreadshirt.com/> HTTPS SUPPORTED, but serving insecure resoures. wiki.code4lib.org <http://planet.code4lib.org/> HTTPS NOT SUPPORTED. Insecure login! So can we start setting an example, now? If cost of certificates is an issue, I am willing to step up. Eric Hellman President, Free Ebook Foundation Founder, Unglue.it https://unglue.it/ http://go-to-hellman.blogspot.com/ twitter: @gluejar