<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: How To Create A PR Nightmare</title>
	<atom:link href="http://howtosplitanatom.com/news/how-to-create-a-pr-nightmare/feed/" rel="self" type="application/rss+xml" />
	<link>http://howtosplitanatom.com/news/how-to-create-a-pr-nightmare/</link>
	<description>Exploring The Intersections Of Technology and Society</description>
	<lastBuildDate>Thu, 24 May 2012 19:59:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: How To Upgrade AOL &#124; How To Split An Atom</title>
		<link>http://howtosplitanatom.com/news/how-to-create-a-pr-nightmare/comment-page-1/#comment-1418</link>
		<dc:creator>How To Upgrade AOL &#124; How To Split An Atom</dc:creator>
		<pubDate>Tue, 19 Jun 2007 08:32:54 +0000</pubDate>
		<guid isPermaLink="false">http://howtosplitanatom.com/?p=34#comment-1418</guid>
		<description>[...] Fresh of the rumor mill is an update from our friends at AOL. No, they have not made another privacy blunder nor have they lost anyone&#8217;s person information. Instead, the company that brought you AIM is looking for a new killer app. Lets take a peek under the hood. [...]</description>
		<content:encoded><![CDATA[<p>[...] Fresh of the rumor mill is an update from our friends at AOL. No, they have not made another privacy blunder nor have they lost anyone&#8217;s person information. Instead, the company that brought you AIM is looking for a new killer app. Lets take a peek under the hood. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How To Make An AOL Password &#124; How To Split An Atom</title>
		<link>http://howtosplitanatom.com/news/how-to-create-a-pr-nightmare/comment-page-1/#comment-789</link>
		<dc:creator>How To Make An AOL Password &#124; How To Split An Atom</dc:creator>
		<pubDate>Tue, 08 May 2007 18:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://howtosplitanatom.com/?p=34#comment-789</guid>
		<description>[...] AOL has problems, it has for a while now. Starting from a year ago it had a crazy privacy fiasco, flagging business model, and a crazy customer service nightmare. AOL doesn&#8217;t need anymore flack. [...]</description>
		<content:encoded><![CDATA[<p>[...] AOL has problems, it has for a while now. Starting from a year ago it had a crazy privacy fiasco, flagging business model, and a crazy customer service nightmare. AOL doesn&#8217;t need anymore flack. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How To Split An Atom &#124; How To Surf Anonymously</title>
		<link>http://howtosplitanatom.com/news/how-to-create-a-pr-nightmare/comment-page-1/#comment-35</link>
		<dc:creator>How To Split An Atom &#124; How To Surf Anonymously</dc:creator>
		<pubDate>Wed, 13 Sep 2006 06:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://howtosplitanatom.com/?p=34#comment-35</guid>
		<description>[...] urinate on everything&#8220;.     Bookmark- BlinkList - del.icio.us - Digg it - Furl - reddit - Yahoo MyWeb- [...]</description>
		<content:encoded><![CDATA[<p>[...] urinate on everything&#8220;.     Bookmark- BlinkList &#8211; del.icio.us &#8211; Digg it &#8211; Furl &#8211; reddit &#8211; Yahoo MyWeb- [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How To Split An Atom &#124; How To Spy On AT&#38;T</title>
		<link>http://howtosplitanatom.com/news/how-to-create-a-pr-nightmare/comment-page-1/#comment-20</link>
		<dc:creator>How To Split An Atom &#124; How To Spy On AT&#38;T</dc:creator>
		<pubDate>Thu, 31 Aug 2006 05:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://howtosplitanatom.com/?p=34#comment-20</guid>
		<description>[...] How To Spy On AT&amp;T ATT, blunders privacyAT&amp;T might be used to giving over information to anyone who flashes government identification, but earlier this week they decided to give AOL a run for its money when hackers broke into one of their systems and made off with the personal data of about 19,000 customers. [...]</description>
		<content:encoded><![CDATA[<p>[...] How To Spy On AT&#38;T ATT, blunders privacyAT&#38;T might be used to giving over information to anyone who flashes government identification, but earlier this week they decided to give AOL a run for its money when hackers broke into one of their systems and made off with the personal data of about 19,000 customers. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How To Split An Atom &#124; How To Help AOL Save Face</title>
		<link>http://howtosplitanatom.com/news/how-to-create-a-pr-nightmare/comment-page-1/#comment-9</link>
		<dc:creator>How To Split An Atom &#124; How To Help AOL Save Face</dc:creator>
		<pubDate>Tue, 22 Aug 2006 16:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://howtosplitanatom.com/?p=34#comment-9</guid>
		<description>[...] The Guardian reports that AOL has finally found someone to help suck the poison out of the gaping wound left by their recent customer data privacy fiasco. Maureen Govern, who has been Chief Technology Officer since last September and two of her colleagues have been let go (the employees were fired, there is still no word as to whether Maureen merely resigned) as those primarily responsible for the AOL data leaks. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Guardian reports that AOL has finally found someone to help suck the poison out of the gaping wound left by their recent customer data privacy fiasco. Maureen Govern, who has been Chief Technology Officer since last September and two of her colleagues have been let go (the employees were fired, there is still no word as to whether Maureen merely resigned) as those primarily responsible for the AOL data leaks. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
