<?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: Tucows problem still is not fixed at Afternic</title>
	<atom:link href="http://www.dotweekly.com/tucows-problem-still-is-not-fixed-at-afternic/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dotweekly.com/tucows-problem-still-is-not-fixed-at-afternic/</link>
	<description></description>
	<lastBuildDate>Mon, 14 May 2012 18:40:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Pages tagged "fixed"</title>
		<link>http://www.dotweekly.com/tucows-problem-still-is-not-fixed-at-afternic/#comment-1441</link>
		<dc:creator>Pages tagged "fixed"</dc:creator>
		<pubDate>Sat, 12 Jul 2008 18:14:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=387#comment-1441</guid>
		<description>[...] bookmarks tagged fixed Tucows problem still is not fixed at Afternic&#160;saved by 10 others  &#160;&#160;&#160;&#160;janlukky bookmarked on 07/12/08 &#124; [...]</description>
		<content:encoded><![CDATA[<p>[...] bookmarks tagged fixed Tucows problem still is not fixed at Afternic&nbsp;saved by 10 others  &nbsp;&nbsp;&nbsp;&nbsp;janlukky bookmarked on 07/12/08 | [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Schafer - Tucows</title>
		<link>http://www.dotweekly.com/tucows-problem-still-is-not-fixed-at-afternic/#comment-1439</link>
		<dc:creator>Ken Schafer - Tucows</dc:creator>
		<pubDate>Sat, 12 Jul 2008 15:16:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=387#comment-1439</guid>
		<description>Hi Jamie,


You said &quot;If Tucows has nothing to hide, I do not see the reason for the Contact Privacy on the Tucows “owned” domains.&quot;


Point taken.


The decision to apply Contact Privacy to our names pre-dates me by quite a bit so I&#039;ll need to dig into the facts when folks are back in the office next week, but here are a few reasons why I think we made this decision:


1.  We think ALL names should have WHOIS Privacy.  We encourage our resellers to add Contact Privacy to all domain names by default - in fact we offer Contact Privacy to resellers for free to allow more people to protect their privacy online.  So it&#039;s part of our culture that Contact Privacy is a natural state for a domain.


2.  Because we own over 100,000 names, if we made a real email address widely viewable via WHOIS it would get overwhelmed by spam VERY quickly making it useless for anyone legitimately wanting to contact us.


3.  Someone added it because they could and they didn&#039;t give any thought that it might raise cause people to question our integrity years later. :)


In any case, I&#039;ll talk to the team next week and we&#039;ll take a fresh look at this to see if we can get greater transparency around Tucows vs. non-Tucows names.


Cheers,


Ken.</description>
		<content:encoded><![CDATA[<p>Hi Jamie,</p>
<p>You said &#8220;If Tucows has nothing to hide, I do not see the reason for the Contact Privacy on the Tucows “owned” domains.&#8221;</p>
<p>Point taken.</p>
<p>The decision to apply Contact Privacy to our names pre-dates me by quite a bit so I&#8217;ll need to dig into the facts when folks are back in the office next week, but here are a few reasons why I think we made this decision:</p>
<p>1.  We think ALL names should have WHOIS Privacy.  We encourage our resellers to add Contact Privacy to all domain names by default &#8211; in fact we offer Contact Privacy to resellers for free to allow more people to protect their privacy online.  So it&#8217;s part of our culture that Contact Privacy is a natural state for a domain.</p>
<p>2.  Because we own over 100,000 names, if we made a real email address widely viewable via WHOIS it would get overwhelmed by spam VERY quickly making it useless for anyone legitimately wanting to contact us.</p>
<p>3.  Someone added it because they could and they didn&#8217;t give any thought that it might raise cause people to question our integrity years later. <img src='http://www.dotweekly.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>In any case, I&#8217;ll talk to the team next week and we&#8217;ll take a fresh look at this to see if we can get greater transparency around Tucows vs. non-Tucows names.</p>
<p>Cheers,</p>
<p>Ken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tucows still pulling domains from Afternic &#124; Dominik Mueller</title>
		<link>http://www.dotweekly.com/tucows-problem-still-is-not-fixed-at-afternic/#comment-1436</link>
		<dc:creator>Tucows still pulling domains from Afternic &#124; Dominik Mueller</dc:creator>
		<pubDate>Sat, 12 Jul 2008 08:11:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=387#comment-1436</guid>
		<description>[...] http://www.dotweekly.com/2008/07/11/tucows-problem-still-is-not-fixed-at-afternic/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.dotweekly.com/2008/07/11/tucows-problem-still-is-not-fixed-at-afternic/" rel="nofollow">http://www.dotweekly.com/2008/07/11/tucows-problem-still-is-not-fixed-at-afternic/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Schafer - Tucows</title>
		<link>http://www.dotweekly.com/tucows-problem-still-is-not-fixed-at-afternic/#comment-1435</link>
		<dc:creator>Ken Schafer - Tucows</dc:creator>
		<pubDate>Sat, 12 Jul 2008 03:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=387#comment-1435</guid>
		<description>Hi Jamie,

Adam from Afternic already offered an apology for the confusion that our auction&#039;s teething pains have caused, but I wanted to extend a personal apology as well. 

I&#039;d like to reiterate that because Afternic caught the mistake before any names left Pre-bid, NO names were removed from the auction after bidding started. Therefore I guess the greatest concern about possible impropriety on our part is with names that got Pre-bids and were subsequently withdrawn.  One of the four names you mentioned (fagm.com) falls into that category.  The other three were listed but had not received any Pre-bids so we gained no &quot;market knowledge&quot; by listing them.

The incorrectly listed Tucows names that had Pre-bids in the last few days were fagm.com, adwrap.com, storeaway.com, 8xp.com.  To show that we&#039;re not up to something nefarious I&#039;m going to ask the team to resubmit these to the auction next week.

I also wanted to point out that seeing contactprivacy.com and/or mdnsservice.com in the WHOIS doesn&#039;t mean the name is OWNED by Tucows.  It means it is protected by our WHOIS Privacy Service and it could be owned by any of the millions of registrants using our service.  Nameservers like parking1.mdnsservice.com tell you the name is parked with us, but once again, it could be a Tucows&#039; owned name or it could be a registrant&#039;s name that is in our Parking Service.

Therefore it is possible that a non-Tucows domain expires, is listed for Pre-bids on Afternic, then withdrawn when it is renewed with WHOIS Privacy and parked on our Parking Service.  That&#039;s a perfectly legitimate situation.  It will LOOK exactly like the examples you&#039;ve shown here though - hence my caveat not to assume the names are always owned by Tucows when you see this kind of situation.

Once again - sorry for all the confusion!

Cheers,

Ken.

**Jamie Says**
Thank you for posting Ken. Although I do not agree with most of your answer I do think the right thing is to talk publicly about it, which Tucows does. 

The &quot;could&quot; stuff doesn&#039;t fly with me and I&#039;m sure most others, because I &quot;could&quot; be the president of the United States Of America as well. If Tucows has nothing to hide, I do not see the reason for the Contact Privacy on the Tucows &quot;owned&quot; domains.

The most common pattern for Tucows owned (wharehoused, stolen, kept, moved or how ever anybody wants to put it) domains is Contact Privacy and the servers of parking1.mdnsservice.com . It does appear in the past that Many Tucows owned domains were won at auction and then Tucows reclaimed the domains. TheDomains.com is one of the bigger buyers and has expressed his feelings. I also ran across two more threads on DnFourm.com that the bidders Won the domains and didn&#039;t get them. I do not know the domains, so I can not say they were or were not Tucows domains..
http://www.dnforum.com/f31/tucows-again-thread-310722.html</description>
		<content:encoded><![CDATA[<p>Hi Jamie,</p>
<p>Adam from Afternic already offered an apology for the confusion that our auction&#8217;s teething pains have caused, but I wanted to extend a personal apology as well. </p>
<p>I&#8217;d like to reiterate that because Afternic caught the mistake before any names left Pre-bid, NO names were removed from the auction after bidding started. Therefore I guess the greatest concern about possible impropriety on our part is with names that got Pre-bids and were subsequently withdrawn.  One of the four names you mentioned (fagm.com) falls into that category.  The other three were listed but had not received any Pre-bids so we gained no &#8220;market knowledge&#8221; by listing them.</p>
<p>The incorrectly listed Tucows names that had Pre-bids in the last few days were fagm.com, adwrap.com, storeaway.com, 8xp.com.  To show that we&#8217;re not up to something nefarious I&#8217;m going to ask the team to resubmit these to the auction next week.</p>
<p>I also wanted to point out that seeing contactprivacy.com and/or mdnsservice.com in the WHOIS doesn&#8217;t mean the name is OWNED by Tucows.  It means it is protected by our WHOIS Privacy Service and it could be owned by any of the millions of registrants using our service.  Nameservers like parking1.mdnsservice.com tell you the name is parked with us, but once again, it could be a Tucows&#8217; owned name or it could be a registrant&#8217;s name that is in our Parking Service.</p>
<p>Therefore it is possible that a non-Tucows domain expires, is listed for Pre-bids on Afternic, then withdrawn when it is renewed with WHOIS Privacy and parked on our Parking Service.  That&#8217;s a perfectly legitimate situation.  It will LOOK exactly like the examples you&#8217;ve shown here though &#8211; hence my caveat not to assume the names are always owned by Tucows when you see this kind of situation.</p>
<p>Once again &#8211; sorry for all the confusion!</p>
<p>Cheers,</p>
<p>Ken.</p>
<p>**Jamie Says**<br />
Thank you for posting Ken. Although I do not agree with most of your answer I do think the right thing is to talk publicly about it, which Tucows does. </p>
<p>The &#8220;could&#8221; stuff doesn&#8217;t fly with me and I&#8217;m sure most others, because I &#8220;could&#8221; be the president of the United States Of America as well. If Tucows has nothing to hide, I do not see the reason for the Contact Privacy on the Tucows &#8220;owned&#8221; domains.</p>
<p>The most common pattern for Tucows owned (wharehoused, stolen, kept, moved or how ever anybody wants to put it) domains is Contact Privacy and the servers of parking1.mdnsservice.com . It does appear in the past that Many Tucows owned domains were won at auction and then Tucows reclaimed the domains. TheDomains.com is one of the bigger buyers and has expressed his feelings. I also ran across two more threads on DnFourm.com that the bidders Won the domains and didn&#8217;t get them. I do not know the domains, so I can not say they were or were not Tucows domains..<br />
<a href="http://www.dnforum.com/f31/tucows-again-thread-310722.html" rel="nofollow">http://www.dnforum.com/f31/tucows-again-thread-310722.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Gross</title>
		<link>http://www.dotweekly.com/tucows-problem-still-is-not-fixed-at-afternic/#comment-1431</link>
		<dc:creator>Adam Gross</dc:creator>
		<pubDate>Fri, 11 Jul 2008 18:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=387#comment-1431</guid>
		<description>Adam from NameMedia here. There were technical issues in Afternic&#039;s implementation that occurred.  The result was that Afternic was not updating the mutual inventory as frequently as it should have, so Afternic made names available for preorder that should not have been.

We apologize for these issues, and for any time that hasn&#039;t been spent well on our site.  We have now resolved the issue which prevented Afternic from updating every day.  

NameMedia highly values our partnership with Tucows; they are an outstanding company to work with.

Again, we are very sorry for inconveniences.  We&#039;re confident that our service will deliver for the entire community.

Thanks,
Adam Gross</description>
		<content:encoded><![CDATA[<p>Adam from NameMedia here. There were technical issues in Afternic&#8217;s implementation that occurred.  The result was that Afternic was not updating the mutual inventory as frequently as it should have, so Afternic made names available for preorder that should not have been.</p>
<p>We apologize for these issues, and for any time that hasn&#8217;t been spent well on our site.  We have now resolved the issue which prevented Afternic from updating every day.  </p>
<p>NameMedia highly values our partnership with Tucows; they are an outstanding company to work with.</p>
<p>Again, we are very sorry for inconveniences.  We&#8217;re confident that our service will deliver for the entire community.</p>
<p>Thanks,<br />
Adam Gross</p>
]]></content:encoded>
	</item>
</channel>
</rss>

