<?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>Betabeat &#187; Legalese</title>
	<atom:link href="http://betabeat.com/tag/legalese/feed/" rel="self" type="application/rss+xml" />
	<link>http://betabeat.com</link>
	<description>Just another WordPress.com site</description>
	<lastBuildDate>Sun, 19 May 2013 01:29:40 +0000</lastBuildDate>
	<language></language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='betabeat.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Betabeat &#187; Legalese</title>
		<link>http://betabeat.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://betabeat.com/osd.xml" title="Betabeat" />
	<atom:link rel='hub' href='http://betabeat.com/?pushpress=hub'/>
		<item>
				
		<title>&#8216;Contributors&#8217; File Class Action Lawsuit Against Yahoo for July Hack</title>

		<comments>http://betabeat.com/2012/08/class-action-suit-filed-against-yahoo-for-yahoo-contributor-network-hack/#comments</comments>
		<pubDate>Fri, 03 Aug 2012 14:14:24 -0400</pubDate>
					<link>http://betabeat.com/2012/08/class-action-suit-filed-against-yahoo-for-yahoo-contributor-network-hack/</link>
			<dc:creator>Steve Huff</dc:creator>
				
		<guid isPermaLink="false">http://betabeat.com/?p=57208</guid>
		<description><![CDATA[<p><div id="attachment_43864" class="wp-caption alignleft" style="width: 220px"><a href="http://nyobetabeat.files.wordpress.com/2012/05/yahoogetty.jpg"><img class="size-full wp-image-43864" title="Yahoo Reportedly Considering Laying Off Hundreds" src="http://nyobetabeat.files.wordpress.com/2012/05/yahoogetty.jpg" alt="" width="210" height="134" /></a><p class="wp-caption-text">Yahoo! (Getty)</p></div></p>
<p>That was fast. In mid-July hackers calling themselves "the D33Ds Company" gave Yahoo a spanking for lax security by posting the login information of some of the 453,000 mostly unpaid bloggers working for Yahoo and Associated Content's contributor network. Less than a month later, we've got the first <a href="http://www.courthousenews.com/2012/08/03/48967.htm">class-action lawsuit</a> related to the breach.</p>
<p>New Hampshire resident Jeff Allan is the named plaintiff in the case. In papers <a href="http://www.courthousenews.com/2012/08/03/Yahoo.pdf" target="_blank">filed July 31</a> in a U.S. District Court in Northern California, attorneys detailed how Mr. Allan discovered his information was compromised:<!--more--></p>
<blockquote><p>Within days of the breach, Mr. Allan received an alert of account fraud on his eBay account, which used the same login credentials as disclosed in the Yahoo breach. Mr. Allan does not know what other information the hackers and others have gathered about<br />
him.</p></blockquote>
<p>The lawsuit also quotes IT security expert Jason Rhykerd. Addressing the SQL injection hack that grabbed the info from Yahoo's database, Mr. Rhykerd said the "amount of network traffic this attack would have generated should of (sic) set off the lightest of [intrusion detection system] rules."</p>
<p>The suit's "Prayer for relief" indicates Mr. Allan is seeking unspecified damages for himself and anyone else affected by Yahoo!'s "negligence."</p>
<p>Between this suit and the <a href="http://allthingsd.com/20120802/revolving-door-yahoo-departures-begin-even-as-mayers-team-still-tbd/" target="_blank">exodus of high-ranking staffers</a>, new CEO Marissa Mayer may well be offering up some prayers of her own.</p>
]]></description>
		<content:encoded><![CDATA[<p><div id="attachment_43864" class="wp-caption alignleft" style="width: 220px"><a href="http://nyobetabeat.files.wordpress.com/2012/05/yahoogetty.jpg"><img class="size-full wp-image-43864" title="Yahoo Reportedly Considering Laying Off Hundreds" src="http://nyobetabeat.files.wordpress.com/2012/05/yahoogetty.jpg" alt="" width="210" height="134" /></a><p class="wp-caption-text">Yahoo! (Getty)</p></div></p>
<p>That was fast. In mid-July hackers calling themselves "the D33Ds Company" gave Yahoo a spanking for lax security by posting the login information of some of the 453,000 mostly unpaid bloggers working for Yahoo and Associated Content's contributor network. Less than a month later, we've got the first <a href="http://www.courthousenews.com/2012/08/03/48967.htm">class-action lawsuit</a> related to the breach.</p>
<p>New Hampshire resident Jeff Allan is the named plaintiff in the case. In papers <a href="http://www.courthousenews.com/2012/08/03/Yahoo.pdf" target="_blank">filed July 31</a> in a U.S. District Court in Northern California, attorneys detailed how Mr. Allan discovered his information was compromised:<!--more--></p>
<blockquote><p>Within days of the breach, Mr. Allan received an alert of account fraud on his eBay account, which used the same login credentials as disclosed in the Yahoo breach. Mr. Allan does not know what other information the hackers and others have gathered about<br />
him.</p></blockquote>
<p>The lawsuit also quotes IT security expert Jason Rhykerd. Addressing the SQL injection hack that grabbed the info from Yahoo's database, Mr. Rhykerd said the "amount of network traffic this attack would have generated should of (sic) set off the lightest of [intrusion detection system] rules."</p>
<p>The suit's "Prayer for relief" indicates Mr. Allan is seeking unspecified damages for himself and anyone else affected by Yahoo!'s "negligence."</p>
<p>Between this suit and the <a href="http://allthingsd.com/20120802/revolving-door-yahoo-departures-begin-even-as-mayers-team-still-tbd/" target="_blank">exodus of high-ranking staffers</a>, new CEO Marissa Mayer may well be offering up some prayers of her own.</p>
]]></content:encoded>
		<wfw:commentRss>http://betabeat.com/2012/08/class-action-suit-filed-against-yahoo-for-yahoo-contributor-network-hack/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:thumbnail url="http://nyobetabeat.files.wordpress.com/2012/05/yahoogetty.jpg?w=150" />
		<media:content url="http://nyobetabeat.files.wordpress.com/2012/05/yahoogetty.jpg?w=150" medium="image">
			<media:title type="html">Yahoo Reportedly Considering Laying Off Hundreds</media:title>
		</media:content>

		<media:content url="http://1.gravatar.com/avatar/12d391316d94afeef01bd9a987c847fe?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">shuffobserver</media:title>
		</media:content>

		<media:content url="http://nyobetabeat.files.wordpress.com/2012/05/yahoogetty.jpg" medium="image">
			<media:title type="html">Yahoo Reportedly Considering Laying Off Hundreds</media:title>
		</media:content>
	</item>
		<item>
				
		<title>Google Isn’t Making Any Promises About Stuff Working, Okay?</title>

		<comments>http://betabeat.com/2012/04/google-isnt-making-any-promises-about-stuff-working-okay/#comments</comments>
		<pubDate>Thu, 26 Apr 2012 13:47:33 -0400</pubDate>
					<link>http://betabeat.com/2012/04/google-isnt-making-any-promises-about-stuff-working-okay/</link>
			<dc:creator>Kelly Faircloth</dc:creator>
				
		<guid isPermaLink="false">http://www.betabeat.com/?p=42426</guid>
		<description><![CDATA[<p><a href="http://www.betabeat.com/2012/04/26/google-isnt-making-any-promises-about-stuff-working-okay/screen-shot-2012-04-26-at-1-45-54-pm/" rel="attachment wp-att-42447"><img class="alignleft  wp-image-42447" title="Screen Shot 2012-04-26 at 1.45.54 PM" src="http://nyobetabeat.files.wordpress.com/2012/04/screen-shot-2012-04-26-at-1-45-54-pm.jpg?w=400&h=240" alt="" width="320" height="192" /></a>The advent of Google Drive has prompted the Internet to take another look at those recently updated terms of service, and the Internet<a href="http://news.cnet.com/8301-1023_3-57421406-93/google-drive-terms-of-service-a-toxic-brew/" target="_blank"> does not like what it sees</a>. Written largely in legalese (which we like to think of as “lawyer wizard-speak”), the document isn’t entirely clear regarding whether users retain ownership of the content they upload and what Google can do with that content. The result: A tempest in a teapot, <a href="https://twitter.com/#!/search/google%20drive" target="_blank">Twitter being the teapot</a>--when in fact, the policy<a href="http://www.theverge.com/2012/4/25/2973849/google-drive-terms-privacy-data-skydrive-dropbox-icloud" target="_blank"> isn’t substantively that different</a> than those from Dropbox and SkyDrive. It's just far less plainspoken. (Though there is a chance <a href="http://www.wired.com/cloudline/2012/04/google-drive-privacy/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+wired%2Findex+%28Wired%3A+Index+3+%28Top+Stories+2%29%29" target="_blank">files set as "public" could end up in </a>Google promotional materials.)</p>
<p>But while nosing around Google’s <a href="http://www.google.com/intl/en/policies/terms/" target="_blank">terms of service</a>, Betabeat found something rather interesting/amusing nestled under “Our Warranties and Disclaimers.” And that's a pretty clear refusal to make a blanket promise that their products will work like you want, when you want.<!--more--></p>
<p>First comes a gentle introduction, cautioning, “We provide our Services using a commercially reasonable level of skill and care and we hope that you will enjoy using them. But there are certain things that we don’t promise about our Services.” Then down comes the hammer:</p>
<blockquote><p>OTHER THAN AS EXPRESSLY SET OUT IN THESE TERMS OR ADDITIONAL TERMS, NEITHER GOOGLE NOR ITS SUPPLIERS OR DISTRIBUTORS MAKE ANY SPECIFIC PROMISES ABOUT THE SERVICES. FOR EXAMPLE, WE DON’T MAKE ANY COMMITMENTS ABOUT THE CONTENT WITHIN THE SERVICES, THE SPECIFIC FUNCTION OF THE SERVICES, OR THEIR RELIABILITY, AVAILABILITY, OR ABILITY TO MEET YOUR NEEDS. WE PROVIDE THE SERVICES “AS IS”.</p></blockquote>
<p>But Google isn’t done yet. The all-caps continue under “Liability for our Services”:</p>
<blockquote><p>WHEN PERMITTED BY LAW, GOOGLE, AND GOOGLE’S SUPPLIERS AND DISTRIBUTORS, WILL NOT BE RESPONSIBLE FOR LOST PROFITS, REVENUES, OR DATA, FINANCIAL LOSSES OR INDIRECT, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES.</p></blockquote>
<p>Translation: Quit whining when Gmail, a product you probably paid $0.00 for, goes down for two hours.</p>
]]></description>
		<content:encoded><![CDATA[<p><a href="http://www.betabeat.com/2012/04/26/google-isnt-making-any-promises-about-stuff-working-okay/screen-shot-2012-04-26-at-1-45-54-pm/" rel="attachment wp-att-42447"><img class="alignleft  wp-image-42447" title="Screen Shot 2012-04-26 at 1.45.54 PM" src="http://nyobetabeat.files.wordpress.com/2012/04/screen-shot-2012-04-26-at-1-45-54-pm.jpg?w=400&h=240" alt="" width="320" height="192" /></a>The advent of Google Drive has prompted the Internet to take another look at those recently updated terms of service, and the Internet<a href="http://news.cnet.com/8301-1023_3-57421406-93/google-drive-terms-of-service-a-toxic-brew/" target="_blank"> does not like what it sees</a>. Written largely in legalese (which we like to think of as “lawyer wizard-speak”), the document isn’t entirely clear regarding whether users retain ownership of the content they upload and what Google can do with that content. The result: A tempest in a teapot, <a href="https://twitter.com/#!/search/google%20drive" target="_blank">Twitter being the teapot</a>--when in fact, the policy<a href="http://www.theverge.com/2012/4/25/2973849/google-drive-terms-privacy-data-skydrive-dropbox-icloud" target="_blank"> isn’t substantively that different</a> than those from Dropbox and SkyDrive. It's just far less plainspoken. (Though there is a chance <a href="http://www.wired.com/cloudline/2012/04/google-drive-privacy/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+wired%2Findex+%28Wired%3A+Index+3+%28Top+Stories+2%29%29" target="_blank">files set as "public" could end up in </a>Google promotional materials.)</p>
<p>But while nosing around Google’s <a href="http://www.google.com/intl/en/policies/terms/" target="_blank">terms of service</a>, Betabeat found something rather interesting/amusing nestled under “Our Warranties and Disclaimers.” And that's a pretty clear refusal to make a blanket promise that their products will work like you want, when you want.<!--more--></p>
<p>First comes a gentle introduction, cautioning, “We provide our Services using a commercially reasonable level of skill and care and we hope that you will enjoy using them. But there are certain things that we don’t promise about our Services.” Then down comes the hammer:</p>
<blockquote><p>OTHER THAN AS EXPRESSLY SET OUT IN THESE TERMS OR ADDITIONAL TERMS, NEITHER GOOGLE NOR ITS SUPPLIERS OR DISTRIBUTORS MAKE ANY SPECIFIC PROMISES ABOUT THE SERVICES. FOR EXAMPLE, WE DON’T MAKE ANY COMMITMENTS ABOUT THE CONTENT WITHIN THE SERVICES, THE SPECIFIC FUNCTION OF THE SERVICES, OR THEIR RELIABILITY, AVAILABILITY, OR ABILITY TO MEET YOUR NEEDS. WE PROVIDE THE SERVICES “AS IS”.</p></blockquote>
<p>But Google isn’t done yet. The all-caps continue under “Liability for our Services”:</p>
<blockquote><p>WHEN PERMITTED BY LAW, GOOGLE, AND GOOGLE’S SUPPLIERS AND DISTRIBUTORS, WILL NOT BE RESPONSIBLE FOR LOST PROFITS, REVENUES, OR DATA, FINANCIAL LOSSES OR INDIRECT, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES.</p></blockquote>
<p>Translation: Quit whining when Gmail, a product you probably paid $0.00 for, goes down for two hours.</p>
]]></content:encoded>
		<wfw:commentRss>http://betabeat.com/2012/04/google-isnt-making-any-promises-about-stuff-working-okay/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://nyobetabeat.files.wordpress.com/2012/04/screen-shot-2012-04-26-at-1-45-54-pm.jpg?w=400&#38;h=240" medium="image">
			<media:title type="html">Screen Shot 2012-04-26 at 1.45.54 PM</media:title>
		</media:content>
	</item>
	</channel>
</rss>
