<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: VeriSign Can Be Sued for Losing Your Domain Name</title>
	<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name/</link>
	<description>Comments on MetaFilter post VeriSign Can Be Sued for Losing Your Domain Name</description>
	<pubDate>Sun, 27 Jul 2003 14:33:57 -0800</pubDate>
	<lastBuildDate>Sun, 27 Jul 2003 14:33:57 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>VeriSign Can Be Sued for Losing Your Domain Name</title>
		<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name</link>	
		<description>&lt;a href="http://www.wired.com/news/business/0,1367,59788,00.html"&gt;VeriSign Can Be Sued for Losing Your Domain Name&lt;/a&gt; A Federal appeals court (Ninth Circuit) has ruled that the owner of the sex.com domain, who lost the domain when VeriSgin transferred it on the basis of a forged letter, can sue VeriSign for damages resulting from VeriSign&apos;s mistake.  The sex.com case is worth millions, but anyone who has lost a domain name due to VeriSign&apos;s incompetence may now be able to draw their pound of flesh straight from those entrusted with making sure the registry process works.</description>
		<guid isPermaLink="false">post:www.metafilter.com,2003:site.27268</guid>
		<pubDate>Sun, 27 Jul 2003 14:33:13 -0800</pubDate>
		<dc:creator>mikewas</dc:creator>		<category>verisign</category>		<category>domains</category>		<category>urls</category>		<category>sex</category>		<category>legal</category>		<category>legislation</category>
	</item>	<item>
		<title>By: mikewas</title>
		<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name#526622</link>	
		<description>The full opionion (in PDF) is &lt;a href=&quot;http://www.ca9.uscourts.gov/ca9/newopinions.nsf/999D1D5B0D734B6088256D6D0078CB88/$file/0115899.pdf?openelement&quot;&gt;available online&lt;/a&gt;.</description>
		<guid isPermaLink="false">comment:www.metafilter.com,2003:site.27268-526622</guid>
		<pubDate>Sun, 27 Jul 2003 14:33:57 -0800</pubDate>
		<dc:creator>mikewas</dc:creator>
	</item>	<item>
		<title>By: mathowie</title>
		<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name#526629</link>	
		<description>Actually, VeriSign is only liable for domains lost before NetSol changed the language in 2000 or so to say that you are basically &quot;leasing&quot; a domain from them and don&apos;t own it. The Sex.com debacle predates that change in agreement, but I&apos;m glad to see them held accountable finally.</description>
		<guid isPermaLink="false">comment:www.metafilter.com,2003:site.27268-526629</guid>
		<pubDate>Sun, 27 Jul 2003 14:59:22 -0800</pubDate>
		<dc:creator>mathowie</dc:creator>
	</item>	<item>
		<title>By: mikewas</title>
		<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name#526634</link>	
		<description>I don&apos;t think that&apos;s been resolved, Matt.  Clearly any cases which pre-date that agreement could move forward immediately; whether VeriSign&apos;s current contracts protect them from conversion claims hasn&apos;t been fully tested in light of this ruling.

In any event, VeriSign&apos;s current &quot;Service Agreement&quot; doesn&apos;t specifically say that anymore.  And their web site is loaded with terms like &quot;Purchase&quot; the domain name and so on.</description>
		<guid isPermaLink="false">comment:www.metafilter.com,2003:site.27268-526634</guid>
		<pubDate>Sun, 27 Jul 2003 15:25:18 -0800</pubDate>
		<dc:creator>mikewas</dc:creator>
	</item>	<item>
		<title>By: anathema</title>
		<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name#526635</link>	
		<description>Actually, they haven&apos;t been held accountable for anything yet. The case has been  remanded to determine if NSI has liability for giving away an intangible property to a third-party. Operative words being &quot;can&quot; and &quot;may.&quot;</description>
		<guid isPermaLink="false">comment:www.metafilter.com,2003:site.27268-526635</guid>
		<pubDate>Sun, 27 Jul 2003 15:26:33 -0800</pubDate>
		<dc:creator>anathema</dc:creator>
	</item>	<item>
		<title>By: quonsar</title>
		<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name#526772</link>	
		<description>well, i guarantee they can&apos;t be sued for losing mine.</description>
		<guid isPermaLink="false">comment:www.metafilter.com,2003:site.27268-526772</guid>
		<pubDate>Sun, 27 Jul 2003 22:37:08 -0800</pubDate>
		<dc:creator>quonsar</dc:creator>
	</item>	<item>
		<title>By: weston</title>
		<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name#526964</link>	
		<description>What about &lt;a href=&quot;http://leslie.harpold.com&quot;&gt;Leslie Harpold&lt;/a&gt; and Hoopla.com? That happened after 2000 (2002 sometime?) IIRC... anyone know anything about that case?</description>
		<guid isPermaLink="false">comment:www.metafilter.com,2003:site.27268-526964</guid>
		<pubDate>Mon, 28 Jul 2003 09:36:04 -0800</pubDate>
		<dc:creator>weston</dc:creator>
	</item>	<item>
		<title>By: crunchland</title>
		<link>http://www.metafilter.com/27268/VeriSign-Can-Be-Sued-for-Losing-Your-Domain-Name#526982</link>	
		<description>to be perfectly blunt, anyone who is still paying $35 a year for a domain name through verisign, when there are hundreds of cheaper, more reliable alternatives, deserves to be bumfucked.</description>
		<guid isPermaLink="false">comment:www.metafilter.com,2003:site.27268-526982</guid>
		<pubDate>Mon, 28 Jul 2003 10:03:59 -0800</pubDate>
		<dc:creator>crunchland</dc:creator>
	</item>
	</channel>
</rss>
