<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html" />
  <link rel="self" type="application/atom+xml" href="http://consumerist.com/atom.xml" />
  <id>tag:consumerist.com,2010:/1/tag:64.14.177.195,2009://1.5170410-</id>
  <updated>2010-01-24T13:12:23Z</updated>
  <title>Comments for This Is How All User Agreements Should Be Displayed</title>
  <subtitle>Shoppers bite back.</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.32-en</generator>
  <entry>
    <id>tag:64.14.177.195,2009://1.5170410</id>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://consumerist.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=5170410" title="This Is How All User Agreements Should Be Displayed" />
    <published>2009-03-16T19:20:54Z</published>
    <updated>2009-03-17T01:51:00Z</updated>
    <title>This Is How All User Agreements Should Be Displayed</title>
    <summary>--&gt;Aviary is a suite of web-based graphics programs, both free and subscription-based. What&apos;s awesome about Aviary from the Consumerist perspective, though, is their Terms of Use, which offers a plain English summary in bullet points alongside the legalese. It&apos;s brilliant, it&apos;s simple, it doesn&apos;t reduce the power of their legal agreement, and it helps users make informed decisions. Everyone should do this.</summary>
    <author>
      <name>Chris Walters</name>
      
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://consumerist.com/">
      <![CDATA[<p><!--<img src="http://consumerist.com/images/31/2009/03/031609-002-aviary158.jpg" height="158" width="158" class="left" />--><iframe src="http://digg.com/api/diggthis.php?u=http://digg.com/tech_news/This_Is_How_All_User_Agreements_Should_Be_Displayed" align="right" frameborder="0" height="82" scrolling="no" width="55"></iframe>Aviary is a suite of <a href="http://aviary.com/tools">web-based graphics programs</a>, both free and subscription-based. What's awesome about Aviary from the Consumerist perspective, though, is their <a href="http://aviary.com/terms">Terms of Use</a>, which offers a <a class="autolink" title="Click here to read more posts tagged PLAIN ENGLISH" title="Click here to read more posts tagged PLAIN ENGLISH" href="http://consumerist.com/tag/plain-english/">plain English</a> summary in bullet points alongside the legalese. It's brilliant, it's simple, it doesn't reduce the power of their legal agreement, and it helps users make informed decisions. Everyone should do this.</p>
<p><a href="http://aviary.com/terms">Aviary Terms of Use</a> [Aviary.com]</p>
]]>
      
    </content>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11405219</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11405219" />
    <title>Comment from Ezra Ekman on 2009-03-16</title>
    <author>
        <name>Ezra Ekman</name>
        <uri>http://www.ezraekman.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.ezraekman.com/">
        <![CDATA[<p><a href="http://www.pbwiki.com/" rel="nofollow">PB Wiki</a>, which is Ramit Sethi's company (of <a href="http://www.iwillteachyoutoberich.com/blog/" rel="nofollow">I will teach you to be rich</a> fame), also has a similar <a href="http://pbwiki.com/content/termsofservice" rel="nofollow">Terms of Service</a>.  In fact, they've been <a href="http://blogs.zdnet.com/Greenbaum/?p=156" rel="nofollow">written up</a> before as an example of how to do it right.</p>
<p>I think Aviary does it a little in a more user-friendly fashion (each bullet point is next to the paragraph it references), but the general purpose is the same.  It really makes clear who's side they're on, and what their goals really are.</p>]]>
    </content>
    <published>2009-03-17T04:15:02Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11404795</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11404795" />
    <title>Comment from Meester Deadletterb on 2009-03-16</title>
    <author>
        <name>Meester Deadletterb</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Check out our lease - we did this same kind of thing on the side for our Giant Industrial Arts Building...</p>
<p><a href="http://watershedpdx.com/Lease%204-3.doc" rel="nofollow">[watershedpdx.com]</a></p>]]>
    </content>
    <published>2009-03-17T03:58:13Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11401137</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11401137" />
    <title>Comment from HogwartsAlum on 2009-03-16</title>
    <author>
        <name>HogwartsAlum</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>That is awesome.</p>]]>
    </content>
    <published>2009-03-17T02:00:35Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11398918</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11398918" />
    <title>Comment from Whiskey Tango Foxtrot on 2009-03-16</title>
    <author>
        <name>Whiskey Tango Foxtrot</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Credit card companies could take a lesson from these guys.</p>]]>
    </content>
    <published>2009-03-17T01:00:20Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11393737</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11393737" />
    <title>Comment from CapitalC on 2009-03-16</title>
    <author>
        <name>CapitalC</name>
        <uri>http://</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://">
        <![CDATA[<p>LMAO!  The best part is at the end:</p>
<p>"We love you, but signing this agreement doesn't make us legal partners."</p>]]>
    </content>
    <published>2009-03-16T22:38:42Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11393358</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11393358" />
    <title>Comment from erratapage on 2009-03-16</title>
    <author>
        <name>erratapage</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>I don't know why they need the legalese. The summary seems comprehensive enough.</p></p>]]>
    </content>
    <published>2009-03-16T22:28:42Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11392913</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11392913" />
    <title>Comment from Inglix_the_Mad on 2009-03-16</title>
    <author>
        <name>Inglix_the_Mad</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c11387954" rel="nofollow">ADismalScience</a>: Some lawyers are beginning to fear the courts overturning EULA's (et al) because the common person CANNOT be expected to understand them. Having to hire a lawyer because little Suzie's $9.99 has a cryptic EULA in the beginning, if you really wanted to understand it before signing, is slowly becoming viewed by the courts with less than glowing appeal. Not only that but the click through licensing on websites cannot prove that a person of legal age is entering into the contract in most cases. Therein, the site is still technically liable if a 15 year old "clicks through" the agreement because they have no standing to agree to it.</p>
<p>This whole area is a mess with some pretty contradictory rulings (depending on state) according to my lawyer.</p>
<p>The fear of the EULA being summarily dismissed is why software companies were/are pushing so hard for <a href="http://en.wikipedia.org/wiki/UCITA" rel="nofollow">UCITA.</a></p>]]>
    </content>
    <published>2009-03-16T22:16:03Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11392348</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11392348" />
    <title>Comment from Sam G. Daniel on 2009-03-16</title>
    <author>
        <name>Sam G. Daniel</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>This is a great idea.  I was able to follow the legal version as well as the summary.  Made things very clear.  All companies should do this.</p>]]>
    </content>
    <published>2009-03-16T22:00:29Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11391599</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11391599" />
    <title>Comment from Brandon Colton on 2009-03-16</title>
    <author>
        <name>Brandon Colton</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>This is great!</p>]]>
    </content>
    <published>2009-03-16T21:36:22Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11391196</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11391196" />
    <title>Comment from Peter_Betts on 2009-03-16</title>
    <author>
        <name>Peter_Betts</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>Now this is a business that has confidence in the product they are peddling.</p></p>]]>
    </content>
    <published>2009-03-16T21:23:06Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11390951</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11390951" />
    <title>Comment from professorjonathan on 2009-03-16</title>
    <author>
        <name>professorjonathan</name>
        <uri>http://www.tourolaw.edu</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.tourolaw.edu">
        <![CDATA[<p>As someone who writes Terms of Use and Privacy Policies and EULAs for (part of) his living and teaches about how to write them for the rest of it, I remain firmly on the side of plain language whenever possible.  That said, summaries can be unintentionally misleading if they don't exactly match what the legalese means.  For that matter, there are certain phrases that have legally binding meaning ("work made for hire," for example, or "best efforts"), and summarizing or replacing them with plain language might not suffice.  {ProfJonathan}</p>]]>
    </content>
    <published>2009-03-16T21:15:33Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11390763</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11390763" />
    <title>Comment from nakedscience on 2009-03-16</title>
    <author>
        <name>nakedscience</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>That site is amazing. The TOS is great, but I mean the site itself. It's been bookmarked. I keep staring at the header image. So prettty.</p><br />
<p>I'm kind of loopy. I need coffee lol.</p></p>]]>
    </content>
    <published>2009-03-16T21:08:49Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11390134</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11390134" />
    <title>Comment from AfraidOfVelcro_GitEmSteveDave on 2009-03-16</title>
    <author>
        <name>AfraidOfVelcro_GitEmSteveDave</name>
        <uri>http://www.CanItKillTheGrimace.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.CanItKillTheGrimace.com">
        <![CDATA[<p>@<a href="#c11387767" rel="nofollow">verucalise</a>: Scott Adams has some stories about bosses who try to get their employees to change websites their site links to.  And then the bewilderment when they try to explain they don't work for yahoo/IBM/etc..., and can't change their pages.</p>]]>
    </content>
    <published>2009-03-16T20:49:01Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11389321</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11389321" />
    <title>Comment from metaled on 2009-03-16</title>
    <author>
        <name>metaled</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>ABSOLUTELY BRILLIANT!  If Microsoft did this, it woould read "We do not promise that any of this will work on anything.  You give up all rights by purchasing this software.  you give us full rights to do anything we want to any computers you install our software on, with no rights to legal recourse.  By using our software, you agree if you have to call us, we will jerk you around as much as possible for as long as possible."<br />
  I could go on for hours, but I haven't had my coffee yet.<br />
  This EULA is perfectly wonderful, I love these guys!  I'll have to check them out!  I wish google and others would follow this example. I would use their services before I would others with all the legal crap.  Everyone would prefer the summary of the full EULA, I can't remember the last time I actually read one. (the company's intentions!)</p>]]>
    </content>
    <published>2009-03-16T20:21:08Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11389284</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11389284" />
    <title>Comment from wildhalcyon on 2009-03-16</title>
    <author>
        <name>wildhalcyon</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c11389164" rel="nofollow">Avi Muchnick</a>: Great work Avi. Just for that, I took a closer look at your site, and I really dig it. Probably going to sign up.</p>
<p>See that other companies? See how positive consumer advocacy can work in your favor?</p>]]>
    </content>
    <published>2009-03-16T20:19:46Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11389164</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11389164" />
    <title>Comment from Avi Muchnick on 2009-03-16</title>
    <author>
        <name>Avi Muchnick</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Wow, I'm really happy people noticed this and were happy. It took a while of slogging through the agreement to do. :)</p>
<p>I was inspired by a moderator at WebmasterWorld.com, (username Jensense), who used to update the forums every time Google made a change to it's Adsense Terms of Service. As part of her update she would do a summary of each paragraph in plain English.</p>
<p>That service was invaluable to understanding what the agreement changes really meant and that left a mark on me. Credit is really due her.</p>
<p>Aviary's mission is to make creation accessible to the world - even those that can't afford digital software. It doesn't make sense in light of our mission to make understanding the legal ramifications of using our tools inaccessible to anyone without a law degree.</p>
<p>Anyways, I'm flattered that you guys thought enough of this to mention it. I agree, more companies should be doing it and I'm sure they'd have tighter relationships with their userbase as a result.</p>]]>
    </content>
    <published>2009-03-16T20:16:06Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11389067</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11389067" />
    <title>Comment from ophmarketing on 2009-03-16</title>
    <author>
        <name>ophmarketing</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Of course, just because something is in the "summary" doesn't mean it supersedes the actual legalese. It's like a salesman telling you something that differs from the contract you sign. The only thing that matters is the contract.</p>
<p>While this is a nice summary, it shouldn't absolve people from taking the responsibility to read the actual agreement.</p>]]>
    </content>
    <published>2009-03-16T20:13:06Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11388636</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11388636" />
    <title>Comment from dwhuntley on 2009-03-16</title>
    <author>
        <name>dwhuntley</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>BRILLANT!</p>]]>
    </content>
    <published>2009-03-16T19:57:24Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11388611</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11388611" />
    <title>Comment from ztoop on 2009-03-16</title>
    <author>
        <name>ztoop</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>The summary is clear, but still really long (about 1/3 the length of the legalese.)  It is a good first step, but there has to be something better.</p>]]>
    </content>
    <published>2009-03-16T19:56:41Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11388517</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11388517" />
    <title>Comment from Eyebrows McGee (now with more baby!) on 2009-03-16</title>
    <author>
        <name>Eyebrows McGee (now with more baby!)</name>
        <uri>http://eyebrowsmcgee.blogspot.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://eyebrowsmcgee.blogspot.com/">
        <![CDATA[<p>@<a href="#c11387954" rel="nofollow">ADismalScience</a>: Maybe. There's a movement among (some) lawyers to move to simpler, plainer English for contracts, etc.</p>
<p>One of the big reasons legalese exists is that lawyers are magpies who take bits of other people's contracts that they know work properly. It's slow work to create a provision from scratch using your own words instead of stock phrases. (I actually have a lovely set of five fat books full of stock phrases for contracts in Illinois. Terrifically useful.)</p>
<p>When I write wills, I try to do it without technical legal terms and without twisty legal sentences. There are only two unusual legal terms I've found myself unable to jettison ("ademption" and "per stirpes") and those are easy enough to explain to clients. Occasionally a client is disappointed, though, because they're paying for the fancy lawyer-talk and don't want this plain English crap. :)</p>]]>
    </content>
    <published>2009-03-16T19:53:10Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11388398</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11388398" />
    <title>Comment from Eyebrows McGee (now with more baby!) on 2009-03-16</title>
    <author>
        <name>Eyebrows McGee (now with more baby!)</name>
        <uri>http://eyebrowsmcgee.blogspot.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://eyebrowsmcgee.blogspot.com/">
        <![CDATA[<p>What I find particularly interesting is that they're clear in the bullet points where the terms favor Aviary. They're not weaseling. They seem to actually want you to understand the Terms.</p>]]>
    </content>
    <published>2009-03-16T19:49:01Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11388098</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11388098" />
    <title>Comment from James Johnston on 2009-03-16</title>
    <author>
        <name>James Johnston</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c11387767" rel="nofollow">verucalise</a>: Yes.  They should add... "If you have Comcast, quit yelling at us and start .... Well, you get the point..."</p>]]>
    </content>
    <published>2009-03-16T19:38:53Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11387986</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11387986" />
    <title>Comment from Acolyte on 2009-03-16</title>
    <author>
        <name>Acolyte</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>We love you, but signing this agreement doesn't make us legal partners.</p>
<p>A cute way of putting it....</p>]]>
    </content>
    <published>2009-03-16T19:34:45Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11387954</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11387954" />
    <title>Comment from ADismalScience on 2009-03-16</title>
    <author>
        <name>ADismalScience</name>
        <uri>http://adismalscience.blogspot.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://adismalscience.blogspot.com/">
        <![CDATA[<p><p>I think this is easy to do with a website and well-nigh-impossible to do with most EULAs, contractual agreements, terms of service, etc. Most lawyers would develop a fear that a court would interpret the clarifying points as the true legal language of the contract. There is a reason "legalese" exists, after all, and it's not just so lawyers pull salary.</p></p>]]>
    </content>
    <published>2009-03-16T19:33:35Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11387905</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11387905" />
    <title>Comment from Skankingmike on 2009-03-16</title>
    <author>
        <name>Skankingmike</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p>I would bet that could be used in a discrimination lawsuit against them as to say, psychologically one cannot not help who they are as a human and thus if being a jerk is their personality than this site is discriminated against jerks.</p>
<p>:P</p>]]>
    </content>
    <published>2009-03-16T19:31:14Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11387877</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11387877" />
    <title>Comment from mmmsoap on 2009-03-16</title>
    <author>
        <name>mmmsoap</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Oh, me likey.</p>
<p>It seems that those Terms of Use are pretty much recycled these days, without much change from one website to the next. I like how they've got a general "not-evil" vibe going, from reasonable timelines for notification of price increases, to a lack of a "this can change at any time without notice" policy.</p>]]>
    </content>
    <published>2009-03-16T19:30:11Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11387855</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11387855" />
    <title>Comment from Coles_Law on 2009-03-16</title>
    <author>
        <name>Coles_Law</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>"Don't be a jerk." Every site and business needs this clause.</p></p>]]>
    </content>
    <published>2009-03-16T19:29:05Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11387806</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11387806" />
    <title>Comment from Ameer Hashw on 2009-03-16</title>
    <author>
        <name>Ameer Hashw</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>they*, bleh.</p>]]>
    </content>
    <published>2009-03-16T19:27:06Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11387795</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11387795" />
    <title>Comment from Ameer Hashw on 2009-03-16</title>
    <author>
        <name>Ameer Hashw</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Thing is, if all companies did things like this, the wouldn't be able to get away with half the shit they pull.</p>]]>
    </content>
    <published>2009-03-16T19:26:46Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2009://1.5170410-comment:11387767</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2009://1.5170410" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2009/03/this-is-how-all-user-agreements-should-be-displayed.html#c11387767" />
    <title>Comment from Verucalise(countingcalories) on 2009-03-16</title>
    <author>
        <name>Verucalise(countingcalories)</name>
        <uri>http://www.geocities.com/verucalyse</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.geocities.com/verucalyse">
        <![CDATA[<p><p>"We arent' responsible if your internet access provider isn't working. :)"</p><br />
<p>In the words of Bill Engvall, here's your sign.</p></p>]]>
    </content>
    <published>2009-03-16T19:25:47Z</published>
  </entry>


</feed>



