The science of working together

At the launch event for Interop: The Promise and Perils of Highly Interconnected Systems, the authors John Palfrey and Urs Gasser gave an overview of interop and provided several relevant examples. Though they began years ago on a theoretical level (does increased interop lead to increased innovation?), interop is a deeply practical topic.

“Interop” here is short for interoperability, defined as “the ability to transfer or render useful data and other information across systems (including organizations), applications, or components.” The authors decided that this initial definition, however, could be broadened into “the science of working together” on many layers: institutional, human, data, and technological.

Though it may sound abstract, there are many good examples of how interoperability is important in daily life. Solutions to big societal problems depend on interop, said Palfrey and Gasser. They talked first about “smart cities,” which depend on sharing information: between police, firefighters, and ambulances, for example, and between various forms of transit (does your bus pass also work for the subway and the commuter rail systems?).

Next they talked about open platforms, such as Facebook, which made its API available so that anyone could build an app. However, this interconnectedness has a down side: many points of connection means more vulnerability to privacy and security breaches. (This is also true of credit cards – another example of interop – which are vulnerable to identity theft.)

Facebook is an example from the private sector, but the public sector can drive interop as well, by regulation and legislation, as Europe has done for standardized cell phone chargers.

Naturally, one of the areas in which I am most interested is that of libraries. Libraries, said Palfrey, are facing two large interop problems: preservation of knowledge over time, and the lack of an open standard for e-lending.

The first issue has to do with reformatting; over the past decade or two, data has been stored not just in print, but in a whole variety of other ways, including floppy disks, microfilm, microfiche, CDs, and on computers in a variety of formats, some of which are no longer readable because the software necessary is no longer in use. Libraries must be vigilant to make sure that the information they have is preserved in an accessible form.

The second problem is one that has been in the news more or less constantly for a few years: there is no open standard for e-lending. Instead, there are a lot of proprietary formats that are not interoperable at all (e.g. you can’t read a kindle book on a nook device). “This is crazy,” Palfrey said. “Why is this [print book] still better technology?”

I hope and trust that, in the next few years, an open standard for e-lending will develop. In an ideal world, both libraries and individuals would be able to buy and lend any e-book, which could be read on any device.

Fingers crossed.

Hand over your password? Er…no.

Every week I get an e-mail from LinkedIn with the top five articles of the week. Usually these are along the lines of “what makes a remarkable boss,” “how to be a great employee,” “what interview mistake are you making?” etc. But this week there was a link to an article called “Job seekers getting asked for Facebook passwords,” and yes, this is exactly what it sounds like.

If you, like any smart person, have your Facebook or other social media site settings set to “private” so that only the people you want to see your profile and other information can see it, it turns out you may be asked in an interview to hand over your login and password. To me, this is an outrageous violation of privacy and an unreasonable request – it is simply over the line. (More reasonable requests that potential employers might make include asking you to “friend” someone in Human Resources. Or, if you have your profile set to “public,” you can safely assume they’ve looked at it before they called you in for the interview.)

What legal recourse do you have to say no? Is this like the Fourth Amendment where they have to establish probable cause? On the other hand, if you refuse, that job opportunity might be lost to you, and in this economy, who can afford that? Well, giving anyone else your login information is a violation of the Facebook terms of service, but right now that’s the only obstacle in these invasive employers’ way. The ACLU has protested the practice, and some states – Maryland and Illinois – are working on legislation to forbid public agencies from asking for access to social networks, but private companies could continue it.

This touches on a larger issue. I was horrified to read about this practice, and even in an interview situation where I really wanted or needed the job, I think I would say no if asked for my password to Facebook (let alone e-mail!). It’s not that I have anything to hide, but rather the principle of personal privacy that’s at stake.

The whole idea of privacy may be eroding; it seems to be less important to “Millennials”  (just Google “Millennials + privacy” – some articles about how savvy they are at protecting it, others about how their views on it are simply different from traditional views of personal privacy). From personal observation, it seems that teenagers and those in their early 20s are less protective of their personal information – and with so much of it available online, it might seem like a hopeless effort to keep any information private.

However, for a potential employer to ask you for personal information that you have deemed private seems beyond the pale. (It may also allow them to find answers to questions they are not legally allowed to ask in interviews, such as your age, marital status, or religion.) They already have your resume, your cover letter, your application, as well as whatever they have gleaned from what is publicly available online; they can contact your references and ask you questions in an interview; they can even give you a drug test (with your consent). Is it really necessary to hand over your passwords as well? I think not.

Facebook and Privacy

On January 9, all Facebook users who haven’t already changed their profiles over to the new Timeline format will see their pages change anyway. As always with changes to Facebook, there have been mixed reactions, but Facebook at least ought to get credit for giving users a heads-up this time, instead of their usual MO (i.e., “it’s easier to get forgiveness than permission”).

Every time Facebook makes even a minor change is a good time to check your privacy settings (if you’re a Facebook user; not everyone is); with a major change like Timeline, definitely look at your privacy settings, because changes to the site mean changes to your privacy. Users can experiment with Timeline for a seven-day period before it goes live on the 9th – it’s not a bad idea to use this time not just to play around with the new layout, but also to see how the privacy settings have changed or been re-set. Unfortunately (intentionally?), these settings aren’t the easiest to manipulate or change, but it can be done.

And while you’re doing that, you might also reconsider what kind and how much personal information you share voluntarily – not just on facebook, but elsewhere on the internet. Geoff Duncan’s article in Digital Trends, “Why 2012 is starting to look like 1984,” is informative and sobering on the topic of personal privacy (or lack thereof). He also provides an excellent overview of the SOPA and PIPA bills (Stop Online Piracy Act and Protect IP Act, respectively), and this year’s National Defense Authorization Act (NDAA), which expands on the Patriot Act.

In a nutshell, it seems that whereas sharing personal information used to be an “opt-in” process, it’s now more “opt-out” – and sometimes you can’t.

Edited to add: While we’re on the topic of privacy, the Daring Librarian reminds us that it’s probably time to change all of our passwords. You may have dozens for all the different sites you go to; think about creating a formula so they’re easier to remember. (Here’s some more advice on password strength from xkcd.)