<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Salon.com > Tarleton Gillespie</title>
	<atom:link href="http://www.salon.com/writer/tarleton_gillespie/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.salon.com</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 19:19:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Don&#8217;t ignore Facebook&#8217;s silly-sounding policies</title>
		<link>http://www.salon.com/2012/02/22/dont_ignore_facebooks_silly_sounding_policies/</link>
		<comments>http://www.salon.com/2012/02/22/dont_ignore_facebooks_silly_sounding_policies/#comments</comments>
		<pubDate>Wed, 22 Feb 2012 21:38:00 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Life]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[All Salon]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[Internet Culture]]></category>

		<guid isPermaLink="false">http://www.origin.railrode.net/?p=12406051</guid>
		<description><![CDATA[A leaked manual reveals the shadowy and powerful role social media sites play in shaping public discourse]]></description>
			<content:encoded><![CDATA[<p>Last week, <a href="http://gawker.com/5885714/">Gawker received a curious document</a>. Turned over by an aggrieved worker from the online freelance employment site oDesk, the document iterated, over the course of several pages and in unsettling detail, exactly what kinds of content should be deleted from the social networking site that had outsourced its content moderation to oDesk’s team. The social networking site, as it turned out, was Facebook.</p><p>The antiseptically titled “Abuse Standards 6.1: Operation Manual for Live Content Moderators” (along with an updated version 6.2 subsequently shared with <a href="http://gawker.com/5885836/">Gawker</a>, presumably by Facebook) is still available on Gawker. It represents the implementation of the Facebook’s <a href="http://www.facebook.com/communitystandards">Community Standards</a>, which present the social media site's priorities around acceptable content, but stay miles away from actually spelling them out. In the Community Standards, Facebook reminds users that “We have a strict ‘no nudity or pornography’ policy. Any content that is inappropriately sexual will be removed. Before posting questionable content, be mindful of the consequences for you and your environment.” But, an oDesk freelancer looking at hundreds of pieces of content every hour needs more specific instructions on what exactly is “inappropriately sexual” — such as removing “Any OBVIOUS sexual activity, even if naked parts are hidden from view by hands, clothes or other objects. Cartoons / art included. Foreplay allowed (Kissing, groping, etc.). even for same sex (man-man / woman-woman" (sic).</p><p><a href="http://www.salon.com/2012/02/22/dont_ignore_facebooks_silly_sounding_policies/">Continue Reading...</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.salon.com/2012/02/22/dont_ignore_facebooks_silly_sounding_policies/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Our misplaced faith in Twitter Trends</title>
		<link>http://www.salon.com/2011/10/19/our_misplaced_faith_in_twitter_trends/</link>
		<comments>http://www.salon.com/2011/10/19/our_misplaced_faith_in_twitter_trends/#comments</comments>
		<pubDate>Wed, 19 Oct 2011 21:20:00 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Politics]]></category>
		<category><![CDATA[All Salon]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[Occupy Wall Street]]></category>
		<category><![CDATA[Social Media]]></category>

		<guid isPermaLink="false">http://www.origin.railrode.net/?p=10127666</guid>
		<description><![CDATA[#OccupyWallStreet probably isn't being censored, but it's time to stop worshiping algorithms]]></description>
			<content:encoded><![CDATA[<p>The interesting question is not whether Twitter is censoring its Trends list. The interesting question is, what do we think the Trends list is, what it represents and how it works, that we can presume to hold it accountable when we think it is "wrong"? What are these algorithms, and what do we want them to be?</p><p>It's not the first time it has been asked. <a href="http://blog.socialflow.com/post/7120244374/data-reveals-that-occupying-twitter-trending-topics-is-harder-than-it-looks">Gilad Lotan</a> at SocialFlow (and erstwhile Microsoft researcher), spurred by <a href="http://theconversation.edu.au/did-twitter-censor-occupy-wall-street-3822">questions</a> raised by participants and supporters of the Occupy Wall Street protests, asks the question: Is Twitter censoring its <a href="http://twitter.com/#!/trends">Trends</a> list to exclude #occupywallstreet and #occupyboston? While the protest movement gains traction and media coverage, and participants, observers and critics turn to Twitter to discuss it, why are these widely known hashtags not trending? Why are they not trending in the very cities where protests have occurred, including New York?</p><p><a href="http://www.salon.com/2011/10/19/our_misplaced_faith_in_twitter_trends/">Continue Reading...</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.salon.com/2011/10/19/our_misplaced_faith_in_twitter_trends/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>
