Oh, dear. That's not good news: " There is no current projected date for
the return of Dewey.info right now. We apologize for the inconvenience."
Dated June 9, 2015.
kc
On 6/12/15 10:54 AM, LeVan,Ralph wrote:
This is as close to an official statement as I can find:
http://www.oclc.org/develo
I think that this is a very good idea.
Cherry Hill has committed to going all HTTPS this year. As a hosted service
provider, the challenge is getting our clients to do their part, as they own
their domains. We are now at the point where they just need to respond to an
email. This is easy if the
Jeremy's response made me think.
What do people think about formulating a "Library Digital Privacy Pledge" that
libraries, publishers and vendors could sign onto?
Or perhaps a set of pledges. I'd start with moving services to SSL.
Principle:
Library Services and Resources should be delivered, w
The referer-linked privacy leakage that I'm mostly concerned with is associated
with embedded resources, not resources that a user clicks on to access. But I
agree moving to SSL has many benefits.
> On Jun 12, 2015, at 11:38 PM, Andrew Anderson wrote:
>
> I was not suggesting mixing HTTP/HTTP
