<?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"
	>
<channel>
	<title>Comments on: Another TLD Landrush</title>
	<atom:link href="http://www.shulist.com/2008/11/tld-landrush/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shulist.com/2008/11/tld-landrush/</link>
	<description>Consultants to leaders</description>
	<pubDate>Sun, 05 Feb 2012 00:17:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: .tel? Do Tell &#124; Shulist Group Inc.</title>
		<link>http://www.shulist.com/2008/11/tld-landrush/#comment-1988</link>
		<dc:creator>.tel? Do Tell &#124; Shulist Group Inc.</dc:creator>
		<pubDate>Tue, 06 Oct 2009 18:29:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.shulist.com/?p=1235#comment-1988</guid>
		<description>[...] might recall from prior scribblings here we fiddled about with a new TLD that holds out hope to create a global address [...]</description>
		<content:encoded><![CDATA[<p>[...] might recall from prior scribblings here we fiddled about with a new TLD that holds out hope to create a global address [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Hayward</title>
		<link>http://www.shulist.com/2008/11/tld-landrush/#comment-32</link>
		<dc:creator>Justin Hayward</dc:creator>
		<pubDate>Fri, 28 Nov 2008 13:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.shulist.com/?p=1235#comment-32</guid>
		<description>It is the second point on the .tel for individuals information on the front page of our website - the link explains how that is possible and achieved.  Sorry if I wasn't clear in the first post.

Regards,

Justin</description>
		<content:encoded><![CDATA[<p>It is the second point on the .tel for individuals information on the front page of our website - the link explains how that is possible and achieved.  Sorry if I wasn&#8217;t clear in the first post.</p>
<p>Regards,</p>
<p>Justin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Hayward</title>
		<link>http://www.shulist.com/2008/11/tld-landrush/#comment-31</link>
		<dc:creator>Justin Hayward</dc:creator>
		<pubDate>Fri, 28 Nov 2008 08:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.shulist.com/?p=1235#comment-31</guid>
		<description>There's no need to suspect anything - an individual has complete control over who sees what information through the ability to encrypt the contact information in the DNS and allocate who can see it through a friending mechanism.  Further information is available on our developer website here:  http://dev.telnic.org/docs/privacy.pdf

Therefore, a .tel domain provides even more protection from spammers whilst being able to share your contact information dynamically with whomever you want, reactively or proactively.

Regards,

Justin Hayward
Telnic
&lt;hr /&gt;
Thanks for that update Justin. Perhaps that page should be more prominent on your website? Most interested parties would not think of drilling down the "developer' path. --&gt;ed </description>
		<content:encoded><![CDATA[<p>There&#8217;s no need to suspect anything - an individual has complete control over who sees what information through the ability to encrypt the contact information in the DNS and allocate who can see it through a friending mechanism.  Further information is available on our developer website here:  <a href="http://dev.telnic.org/docs/privacy.pdf" rel="nofollow">http://dev.telnic.org/docs/privacy.pdf</a></p>
<p>Therefore, a .tel domain provides even more protection from spammers whilst being able to share your contact information dynamically with whomever you want, reactively or proactively.</p>
<p>Regards,</p>
<p>Justin Hayward<br />
Telnic</p>
<hr />
Thanks for that update Justin. Perhaps that page should be more prominent on your website? Most interested parties would not think of drilling down the &#8220;developer&#8217; path. &#8211;>ed</p>
]]></content:encoded>
	</item>
</channel>
</rss>

