27.03.2014 Views

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

How Social Network APIs Have Ended the Age of Privacy<br />

Derek Doran, Sean Curley, and Swapna S. Gokhale<br />

Dept. of Computer Science & Engineering<br />

University of Connecticut, Storrs, CT, 06269<br />

{derek.doran,smc08002,ssg}@engr.uconn.edu<br />

Abstract<br />

Online Social Networks (OSNs) have captured our imagination<br />

by offering a revolutionary medium for communication<br />

and sharing. Skeptics, however, contend that these<br />

OSNs pose a grave threat to privacy. This paper seeks to examine<br />

the veracity of this skepticism by analyzing the APIs<br />

of six popular OSNs for their propensity to violate user privacy.<br />

Our analysis lends substantial support to this skepticism<br />

by finding that OSNs: (i) facilitate an extensive collection<br />

of user information; (ii) provide default access to information<br />

of new users; (iii) do not seek comprehensive permissions;<br />

(iv) request these permissions ambiguously; and<br />

(v) offer privacy settings that enable only limited control.<br />

1 Introduction and Motivation<br />

Online Social Networks (OSNs) are now tightly knit<br />

into the fabric of our society. People are overwhelmingly<br />

participating in these OSNs regardless of their age, socioeconomic,<br />

and demographic status [10]; approximately 50%<br />

of all U.S. adults, and over 90% of all Gen-Y members use<br />

OSNs. Moreover, the growth in the user base is staggering,<br />

and is occurring in unconventional segments; recent data<br />

suggests a 90% increase in users over 50 years old, while<br />

only a 13% increase in users aged 18 to 29 [9].<br />

OSNs can be designed for a variety of purposes. Some<br />

such as Facebook and Orkut offer a platform to stay connected<br />

with friends and acquaintances. Microblogging sites<br />

such as Twitter provide a modern news ticker to simultaneously<br />

stream current events and friends’ updates [4].<br />

OSNs also offer portals to share opinions and recommendations<br />

about products and brands; and users vastly aff rm<br />

their trust in these peer recommendations over advertisements<br />

[1]. Many organizations thus seek to harness OSNs<br />

to raise brand awareness, build reputation, and stay relevant.<br />

Besides their commercial potential, OSNs can also serve as<br />

channels of societal transformation; the recent Egyptian political<br />

unrest may have been precipitated with the support of<br />

social media such as Facebook and Twitter [13].<br />

The API of an OSN is a collection of public and open<br />

access methods for third parties to interact with the OSN.<br />

These APIs can be used to systematically harvest user information,<br />

and hence, commercial organizations exploit these<br />

APIs to collect user data for several purposes [2, 4, 14].<br />

Most APIs also expose methods to enhance the usability of<br />

OSN services; the Twitter API enables posts from mobile<br />

devices, the YouTube API allows integration with TVs, and<br />

the Facebook API facilitates photo uploads directly from<br />

digital cameras. OSNs design their APIs to attract third parties<br />

to harvest user data or to integrate their social features<br />

into commercial products. Thus, through these APIs, OSNs<br />

seek to embed themselves deeper into the daily experiences<br />

of their users. These APIs thus need to be sophisticated for<br />

third parties to collect meaningful information to offer novel<br />

services. However, the higher the porosity of the APIs, the<br />

greater is the chance that third parties will misuse them to<br />

acquire unnecessary personal data and compromise user privacy.<br />

OSNs thus have to balance the conf icting priorities of<br />

providing a rich API against protecting user privacy.<br />

OSNs balance these competing concerns through a careful<br />

consideration of three aspects in the design of their APIs.<br />

First, they build these APIs to expose a wealth of user information.<br />

However, they then cede control back to their users<br />

by offering a range of privacy settings on their accounts, and<br />

by requiring third parties to seek permissions from users before<br />

collecting their information. Users can protect their privacy<br />

through these settings and permissions by limiting the<br />

information that third parties can retrieve. Figure 1 shows<br />

how privacy settings and permissions form a protective barrier<br />

between access queries and user information.<br />

Most users, especially certain groups such as seniors and<br />

minors, are very fascinated by the novel communication capabilities<br />

of OSNs, and do not appreciate their wide reach<br />

and impact [5]. They do not realize that their shared information<br />

may be used to their detriment by various agencies<br />

(law enforcement, insurance, and employers) and even criminals.<br />

For example, the Center for American Progress suggests<br />

that had the Egyptian movement been unsuccessful,<br />

the same OSNs that supported this movement would have<br />

provided adequate information to track down and persecute<br />

the protesters [13]. Even worse, they do not acknowledge<br />

the necessity to adjust and benef t from the privacy settings<br />

on their accounts [12]. Finally, third parties usually seek<br />

400

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!