<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/css" media="screen" href="http://s2.wp.com/wp-content/themes/vip/newyorkobserver/stylesheets/rss.css"?>
<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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Observer &#187; user data</title>
	<atom:link href="http://observer.com/term/user-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://observer.com</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 20:05:03 +0000</lastBuildDate>
	<language></language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='observer.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://1.gravatar.com/blavatar/dac0f3722a48a53be75eb06c0c4f5119?s=96&#038;d=http%3A%2F%2Fs2.wp.com%2Fi%2Fbuttonw-com.png</url>
		<title>Observer &#187; user data</title>
		<link>http://observer.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://observer.com/osd.xml" title="Observer" />
	<atom:link rel='hub' href='http://observer.com/?pushpress=hub'/>
		<item>
				
		<title>Zappos Hacked! Millions of Accounts Potentially Compromised</title>

		<comments>http://observer.com/2012/01/zappos-hacked-millions-of-accounts-potentially-compromised/#comments</comments>
		<pubDate>Sun, 15 Jan 2012 23:18:01 -0400</pubDate>
					<link>http://observer.com/2012/01/zappos-hacked-millions-of-accounts-potentially-compromised/</link>
			<dc:creator>Steve Huff</dc:creator>
				
		<guid isPermaLink="false">http://www.observer.com/?p=212054</guid>
		<description><![CDATA[<p><div id="attachment_212056" class="wp-caption alignleft" style="width: 304px"><a rel="attachment wp-att-212056" href="http://www.observer.com/2012/01/zappos-hacked-millions-of-accounts-potentially-compromised/zapposimage/"><img class="size-full wp-image-212056" title="zapposimage" src="http://nyoobserver.files.wordpress.com/2012/01/zapposimage.jpg" alt="" width="294" height="172" /></a><p class="wp-caption-text">Zappos.com</p></div></p>
<p>According to <a href="http://blogs.zappos.com/securityemail" target="_blank">an entry</a> posted on the company blog on Sunday, online shoe and clothing giant Zappos has suffered a massive security breach compromising some data on as many as 24 million customer accounts. In an email to employees, CEO Tony Hsieh said the company was attacked by "a criminal who gained access to parts of our internal network and systems through one of our servers in Kentucky." Hsieh also said the company was cooperating with authorities in an "exhaustive investigation."<!--more--></p>
<p>Hsieh continued:</p>
<blockquote><p>Because of the nature of the investigation, the information in this email is being sent a bit more formally, and unfortunately we are not able to provide any more details about specifics of the attack beyond what is in this email and the link at the end of this email, but we can say that THE DATABASE THAT STORES OUR CUSTOMERS' CRITICAL CREDIT CARD AND OTHER PAYMENT DATA WAS NOT AFFECTED OR ACCESSED.</p></blockquote>
<p>Below the notice to employees, Hsieh attached the text of the email sent to customers. Zappos account holders were advised that unauthorized access had been gained to "one or more of the following: your name, e-mail address, billing and shipping addresses, phone number, the last four digits of your credit card number (the standard information you find on receipts), and/or your cryptographically scrambled password (but not your actual password)."</p>
<p>Customers were advised--capslock advised, no less--to "PLEASE CREATE A NEW PASSWORD," as one of the company's security measures was to go ahead and existing passwords.</p>
<p>Zappos also clearly anticipates a huge customer response (perhaps backlash?) to the news:</p>
<blockquote><p>Due to the volume of inquiries we are expecting, we realized that we could serve the most customers by answering their questions by email. We have made the hard decision to temporarily turn off our phones and direct customers to contact us by email because our phone systems simply aren't capable of handling so much volume. (If 5% of our customers call, that would be over 1 million phone calls, most of which would not even make it into our phone system in the first place.)</p></blockquote>
<p>[<a href="http://blogs.zappos.com/securityemail">Zappos</a>]</p>
]]></description>
		<content:encoded><![CDATA[<p><div id="attachment_212056" class="wp-caption alignleft" style="width: 304px"><a rel="attachment wp-att-212056" href="http://www.observer.com/2012/01/zappos-hacked-millions-of-accounts-potentially-compromised/zapposimage/"><img class="size-full wp-image-212056" title="zapposimage" src="http://nyoobserver.files.wordpress.com/2012/01/zapposimage.jpg" alt="" width="294" height="172" /></a><p class="wp-caption-text">Zappos.com</p></div></p>
<p>According to <a href="http://blogs.zappos.com/securityemail" target="_blank">an entry</a> posted on the company blog on Sunday, online shoe and clothing giant Zappos has suffered a massive security breach compromising some data on as many as 24 million customer accounts. In an email to employees, CEO Tony Hsieh said the company was attacked by "a criminal who gained access to parts of our internal network and systems through one of our servers in Kentucky." Hsieh also said the company was cooperating with authorities in an "exhaustive investigation."<!--more--></p>
<p>Hsieh continued:</p>
<blockquote><p>Because of the nature of the investigation, the information in this email is being sent a bit more formally, and unfortunately we are not able to provide any more details about specifics of the attack beyond what is in this email and the link at the end of this email, but we can say that THE DATABASE THAT STORES OUR CUSTOMERS' CRITICAL CREDIT CARD AND OTHER PAYMENT DATA WAS NOT AFFECTED OR ACCESSED.</p></blockquote>
<p>Below the notice to employees, Hsieh attached the text of the email sent to customers. Zappos account holders were advised that unauthorized access had been gained to "one or more of the following: your name, e-mail address, billing and shipping addresses, phone number, the last four digits of your credit card number (the standard information you find on receipts), and/or your cryptographically scrambled password (but not your actual password)."</p>
<p>Customers were advised--capslock advised, no less--to "PLEASE CREATE A NEW PASSWORD," as one of the company's security measures was to go ahead and existing passwords.</p>
<p>Zappos also clearly anticipates a huge customer response (perhaps backlash?) to the news:</p>
<blockquote><p>Due to the volume of inquiries we are expecting, we realized that we could serve the most customers by answering their questions by email. We have made the hard decision to temporarily turn off our phones and direct customers to contact us by email because our phone systems simply aren't capable of handling so much volume. (If 5% of our customers call, that would be over 1 million phone calls, most of which would not even make it into our phone system in the first place.)</p></blockquote>
<p>[<a href="http://blogs.zappos.com/securityemail">Zappos</a>]</p>
]]></content:encoded>
		<wfw:commentRss>http://observer.com/2012/01/zappos-hacked-millions-of-accounts-potentially-compromised/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://2.gravatar.com/avatar/becf95fa833b8aeb13f7720732bd6dc6?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jhanasobserver</media:title>
		</media:content>

		<media:content url="http://nyoobserver.files.wordpress.com/2012/01/zapposimage.jpg" medium="image">
			<media:title type="html">zapposimage</media:title>
		</media:content>
	</item>
		<item>
				
		<title>Romance is Gone Between iPad and Magazine Industry</title>

		<comments>http://observer.com/2010/12/romance-is-gone-between-ipad-and-magazine-industry/#comments</comments>
		<pubDate>Fri, 03 Dec 2010 21:48:27 -0400</pubDate>
					<link>http://observer.com/2010/12/romance-is-gone-between-ipad-and-magazine-industry/</link>
			<dc:creator>admin</dc:creator>
				
		<guid isPermaLink="false">http://www.observer.com/2010/12/romance-is-gone-between-ipad-and-magazine-industry/</guid>
		<description><![CDATA[<p><img class="alignleft" src="http://nyoobserver.files.wordpress.com/2011/06/broken-ipad_1.jpg?w=238&h=300" />Magazine publishers were some of the first big believers in the potential of Apple's iPad, with Conde Nast saying they expected as much as <a href="/2010/media/conde-nast-steve-jobs-sorry-we-love-adobe">40% of their revenues would come from tablet devices</a> in the future.</p>
<p>But the romance has quickly soured, as publishers push back against Apple's increasingly domineering stance to subscriptions and advertising.</p>
<p>Pete Kafka over at All Things D has a nice breakdown of the growing gap between <a href="http://mediamemo.allthingsd.com/20101203/apple-publishers-still-miles-apart-on-itunes-subscriptions/">publishers and Apple over subscription sales on the iPad</a>. Kafka says that Apple has been offering the following for months.</p>
<p>* The ability to sell app subscriptions through iTunes.<br /> * 70 percent of the revenue from each sale.<br /> * The ability to offer an opt-in form for subscribers that would ask them for a limited amount of information: Name, mailing address, email address.</p>
<p>Hence the recent move by publishers to cozy up to Google and its Android operating system, which will be running on a slew of new tablets in 2011.</p>
<p>The issue, as Kafka points out, is that publishers don't want to be cut out of customer information and subscription sales that could be equally as valuable when applied to print. iPad-only projects like News Corp's The Daily won't have such hang ups.</p>
<p>bpopper [at] observer.com | <a href="http://twitter.com/#!/benpopper/">@benpopper</a></p>
]]></description>
		<content:encoded><![CDATA[<p><img class="alignleft" src="http://nyoobserver.files.wordpress.com/2011/06/broken-ipad_1.jpg?w=238&h=300" />Magazine publishers were some of the first big believers in the potential of Apple's iPad, with Conde Nast saying they expected as much as <a href="/2010/media/conde-nast-steve-jobs-sorry-we-love-adobe">40% of their revenues would come from tablet devices</a> in the future.</p>
<p>But the romance has quickly soured, as publishers push back against Apple's increasingly domineering stance to subscriptions and advertising.</p>
<p>Pete Kafka over at All Things D has a nice breakdown of the growing gap between <a href="http://mediamemo.allthingsd.com/20101203/apple-publishers-still-miles-apart-on-itunes-subscriptions/">publishers and Apple over subscription sales on the iPad</a>. Kafka says that Apple has been offering the following for months.</p>
<p>* The ability to sell app subscriptions through iTunes.<br /> * 70 percent of the revenue from each sale.<br /> * The ability to offer an opt-in form for subscribers that would ask them for a limited amount of information: Name, mailing address, email address.</p>
<p>Hence the recent move by publishers to cozy up to Google and its Android operating system, which will be running on a slew of new tablets in 2011.</p>
<p>The issue, as Kafka points out, is that publishers don't want to be cut out of customer information and subscription sales that could be equally as valuable when applied to print. iPad-only projects like News Corp's The Daily won't have such hang ups.</p>
<p>bpopper [at] observer.com | <a href="http://twitter.com/#!/benpopper/">@benpopper</a></p>
]]></content:encoded>
		<wfw:commentRss>http://observer.com/2010/12/romance-is-gone-between-ipad-and-magazine-industry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://2.gravatar.com/avatar/becf95fa833b8aeb13f7720732bd6dc6?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jhanasobserver</media:title>
		</media:content>

		<media:content url="http://nyoobserver.files.wordpress.com/2011/06/broken-ipad_1.jpg?w=238&#38;h=300" medium="image" />
	</item>
	</channel>
</rss>
