{"id":222,"date":"2008-10-09T10:07:15","date_gmt":"2008-10-09T14:07:15","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/digitalnatives\/?p=222"},"modified":"2008-10-09T10:08:45","modified_gmt":"2008-10-09T14:08:45","slug":"out-of-our-hands-privacy-and-internet-gossip","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/2008\/10\/09\/out-of-our-hands-privacy-and-internet-gossip\/","title":{"rendered":"Out of Our Hands: Privacy and Internet Gossip"},"content":{"rendered":"

\u201cThank you for screwing up my freshman year.\u201d
\n-Addressed to JuicyCampus.com, from a CNN profile<\/a> of a college student who was a target of posts on the site.<\/p>\n

So tempting is a juicy piece of gossip. Despite assurances to the original informer to keep it on the down-low, the juiciest tidbits will always manage to slip out. But there is a tinge of a guilty conscience when one violates the trust of a friend. What happens when even this bit of accountability is entirely removed and anonymity is rule? You\u2019ve got JuicyCampus.com <\/p>\n

JuicyCampus is a repository of gossip and rumors; organized by school, it presents information in a way that is maximally useful to gossip-seekers. Hot topics invariably include keywords like \u201cgay,\u201d \u201csex,\u201d and \u201csorority.\u201d It prides itself on complete anonymity and even directs users to proxies to mask their IP addresses. When I last JuicyCampus here<\/a>, the site had just taken off, attracting media and legal controversy<\/a>. I haven\u2019t been able to find any recent news on the legal developments, so I can only assume they haven\u2019t made much headway. <\/p>\n

(A quick legal aside: JuicyCampus is protected by free speech and can claim immunity under Section 230(c) of the Communications Decency Act, which states \u201cNo provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider.\u201d This means that JuicyCampus is not legally responsible for potentially libelous content on its site. What the New Jersey AG was attempted to do was sue JuicyCampus for consumer fraud in misrepresenting how it deals with content removal.)<\/p>\n

We generally like to think that privacy is in our hands. We control the information about ourselves \u2013 Facebook has robust privacy controls, we choose what we put about ourselves online, etc. We do not, however, have any control over what others say about us. In this way, the existence a public forum like JuicyCampus allows others to invade our privacy. There are really two separate issues here, the posting of true information (invasion of privacy) and the posting of false content (libel). Let\u2019s see how JuicyCampus deals with the former in its FAQs <\/a>(my emphasis added):<\/p>\n

How do I remove a post that someone else made?
\nYou can’t. Only we can remove posts made by others, and generally we don’t. We do remove spam, but otherwise it’s pretty rare.<\/p>\n

What if my contact information is posted?
\nIf someone posts your email address, your home address, your home phone number, or other contact information (no, your full name doesn’t count), we’ll consider deleting it if you notify us<\/em>. Shoot an email to us at cs@juicycampus.com with “Contact Info” in the subject, give us as much info as you can about the post so we can find it, and we’ll see what we can do. FYI, we may or may not read your complaint, and we may or may not respond to it. The decision of what action to take, if any, is at the sole discretion of JuicyCampus.<\/em><\/p><\/blockquote>\n

JuicyCampus\u2019s FAQs and privacy policy are remarkably cavalier. I personally find it a little upsetting to see a site flaunt its CDA immunity with such blatant disregard for privacy. So how to deal with something like JuicyCampus? The Colonialist<\/a> at George Washington University has come up with one strategy to combat JuicyCampus: spam. With spam the downfall of many message boards in the past, there is some poetic justice in fighting the malefactors of the Internet with their own weapons. But the strategy requires a corps of volunteers dedicating their time to\u2026.posting spam, not a particularly sustainable enterprise.<\/p>\n

Or we can just ignore it. Every controversy surrounding it elevates its profile; every attempt to ban brings more curious visitors. I\u2019m probably doing a disservice by mentioning JuicyCampus here. But there is a distinction I\u2019d like to make. Posting on JuicyCampus is actually quite different from exchanging gossip with friends and acquaintances. Gossip is a kind of social currency \u2013 it\u2019s showing off your exclusive knowledge and bringing a select circle into your confidence. These anonymous postings on the Internet, however, have no benefit to the poster, except perhaps the satisfaction of personal retribution. It\u2019s the digital equivalent of nasty messages scrawled in the bathroom, only worse because the potential audience is the entire world. But as any smart student would realize, JuicyCampus really just an outlet for the spiteful and the bored. I\u2019d like to think, anyways, that the site has only limited utility and thus limited appeal. That\u2019s not to say terrible consequences can\u2019t come out of its limited user base, but it\u2019s never going to be the center of our online social live. Or am I being too optimistic?
\n-Sarah Zhang <\/p>\n","protected":false},"excerpt":{"rendered":"

\u201cThank you for screwing up my freshman year.\u201d -Addressed to JuicyCampus.com, from a CNN profile of a college student who was a target of posts on the site. So tempting is a juicy piece of gossip. Despite assurances to the original informer to keep it on the down-low, the juiciest tidbits will always manage to […]<\/p>\n","protected":false},"author":1636,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[279,2872],"tags":[],"class_list":["post-222","post","type-post","status-publish","format-standard","hentry","category-privacy","category-safety"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/posts\/222","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/users\/1636"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/posts\/222\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/media?parent=222"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/categories?post=222"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/tags?post=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}