>If I run a website for a small town public library that only serves information, ie no user accounts and no logins on our domain, is there a valid reason for m

>If I run a website for a small town public library that only serves information, ie no user accounts and no logins on our domain, is there a valid reason for me to go through the process of https and certificates? Absolutely. The privacy of library searches has long been viewed as one of the archetypal examples of why privacy matters. A user's ISP shouldn't be able to learn what sort of books, movies, and music a library patron is interested in. And that's before we get into matters like injection of malicious content by local miscreants at your favorite cafe, or ads by mobile networks. Fundamentally, it's an issue of your users being the ones deciding what they do and do not care about being secure, and security being the default (could you imagine the emotional hurdle someone who has a real need for their privacy when using the library website would have to go through to explicitly ask for it?). The Library Freedom Project, who has been in the news a lot as of late, was in part started to push the use of SSL in all libraries, even if you "don't need it." https://libraryfreedomproject.org/ourwork/digitalprivacypledge/ https://libraryfreedomproject.org/ourwork/digitalprivacypled... https://github.com/EbookFoundation/library-privacy-pledge/wiki https://github.com/EbookFoundation/library-privacy-pledge/wi...