<?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: Mobile TLD .mobi Open to Public Registrations</title>
	<atom:link href="http://www.mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/</link>
	<description>All About Mobile 2.0</description>
	<pubDate>Thu, 04 Dec 2008 01:50:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Jason Coleman</title>
		<link>http://www.mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-50235</link>
		<dc:creator>Jason Coleman</dc:creator>
		<pubDate>Wed, 17 Jan 2007 23:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-50235</guid>
		<description>Late to this post, but the issue is current for me.

Sadly, websites like mine will need to get the .mobi version simply as a defensive act. I can't setup mob.winelog.net and then let someone else create a website at winelog.mobi.

In any case, I'm currently trying to figure out what the best address for a mobile version of a site is. What is the de-facto standard out there. Google seems to like .../mobile, I've seen some mob.whatever.com's. Lots of sites just use server processing to figure out if the connecting device is mobile. That sounds fun and easy, but I like letting the user decide if their device is mobile (this will actually get harder as time goes on. for instance, I would prefer to view a mobile version of a site on some of those crazy small Vaio laptops). Also, most of these sites that autodetect, provide a link anyway. So we still have the question.

I'd appreciate any feedback you guys would have. Comment here or wander over to my post on the topic:

http://www.strangerstudios.com/blog/2007/01/17/what-address-to-use-for-winelog-mobile/

Thanks.</description>
		<content:encoded><![CDATA[<p>Late to this post, but the issue is current for me.</p>
<p>Sadly, websites like mine will need to get the .mobi version simply as a defensive act. I can&#8217;t setup mob.winelog.net and then let someone else create a website at winelog.mobi.</p>
<p>In any case, I&#8217;m currently trying to figure out what the best address for a mobile version of a site is. What is the de-facto standard out there. Google seems to like &#8230;/mobile, I&#8217;ve seen some mob.whatever.com&#8217;s. Lots of sites just use server processing to figure out if the connecting device is mobile. That sounds fun and easy, but I like letting the user decide if their device is mobile (this will actually get harder as time goes on. for instance, I would prefer to view a mobile version of a site on some of those crazy small Vaio laptops). Also, most of these sites that autodetect, provide a link anyway. So we still have the question.</p>
<p>I&#8217;d appreciate any feedback you guys would have. Comment here or wander over to my post on the topic:</p>
<p><a href="http://www.strangerstudios.com/blog/2007/01/17/what-address-to-use-for-winelog-mobile/" rel="nofollow">http://www.strangerstudios.com/blog/2007/01/17/what-address-to-use-for-winelog-mobile/</a></p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>http://www.mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-8533</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Thu, 28 Sep 2006 10:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-8533</guid>
		<description>Mark,  You clearly aren't seeing the critical points here.  First while mobile devices definitely have different functional requirements seperating them out from the rest of the web only insure confusion, additional expense on multiple levels, and further guarantee that the sort of real integration that we require for a seemless browsing experience across all devices will never come to fruition if artifices like .mobi support non-conforming standards for web development, particular any which differ from those developed by the W3C and agreed upon by the majority of web developers world wide.

Beyond this it is pretty clear to me and many of my fellow mobilists agree that beyond being unnecessary and costly for entrepreneurs, this is mainly just an initiative that is first and foremost a means to line the pockets of those that are operating this TLD.  The pricing model that they've established, which is vastly different from the rational one used for all other domains is pretty clear evidence of this fact.

I only wish that people would see this for what it is and resist the temptation to provide revenue to people that are taking advantage of a system and making it worse for all concerned in the process.

I can't stress strongly enough how much I object to this idea and how objectionable I find the tactics being employed by those behind this TLD.

Oliver</description>
		<content:encoded><![CDATA[<p>Mark,  You clearly aren&#8217;t seeing the critical points here.  First while mobile devices definitely have different functional requirements seperating them out from the rest of the web only insure confusion, additional expense on multiple levels, and further guarantee that the sort of real integration that we require for a seemless browsing experience across all devices will never come to fruition if artifices like .mobi support non-conforming standards for web development, particular any which differ from those developed by the W3C and agreed upon by the majority of web developers world wide.</p>
<p>Beyond this it is pretty clear to me and many of my fellow mobilists agree that beyond being unnecessary and costly for entrepreneurs, this is mainly just an initiative that is first and foremost a means to line the pockets of those that are operating this TLD.  The pricing model that they&#8217;ve established, which is vastly different from the rational one used for all other domains is pretty clear evidence of this fact.</p>
<p>I only wish that people would see this for what it is and resist the temptation to provide revenue to people that are taking advantage of a system and making it worse for all concerned in the process.</p>
<p>I can&#8217;t stress strongly enough how much I object to this idea and how objectionable I find the tactics being employed by those behind this TLD.</p>
<p>Oliver</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-8490</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 28 Sep 2006 00:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-8490</guid>
		<description>I think this is actually a great idea.  Mobile devices will always have different needs than 'traditional' computers, namely, the small screen size.  I think .mobi is the first new TLD with a lot of promise.</description>
		<content:encoded><![CDATA[<p>I think this is actually a great idea.  Mobile devices will always have different needs than &#8216;traditional&#8217; computers, namely, the small screen size.  I think .mobi is the first new TLD with a lot of promise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>http://www.mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-8455</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Wed, 27 Sep 2006 17:41:16 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-8455</guid>
		<description>Amen to that.  And no amount of propagandizing on the part of the dotmobi consortium will alter this fundamental truth.

Everything required for mobile standards has been clearly and adequately laid out by the W3C.

Oliver</description>
		<content:encoded><![CDATA[<p>Amen to that.  And no amount of propagandizing on the part of the dotmobi consortium will alter this fundamental truth.</p>
<p>Everything required for mobile standards has been clearly and adequately laid out by the W3C.</p>
<p>Oliver</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjun</title>
		<link>http://www.mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-8449</link>
		<dc:creator>Arjun</dc:creator>
		<pubDate>Wed, 27 Sep 2006 17:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2006/09/27/mobile-tld-mobi-open-to-public-registrations/#comment-8449</guid>
		<description>Yeah, real smart ... use 4 characters for a domain extension meant for _mobile devices_.  they could have at least acquired '.m' instead.

seriously, we don't need another TLD.  .com is more than sufficient.  this is just another way for 'dotmobi' to make a ton of cash.</description>
		<content:encoded><![CDATA[<p>Yeah, real smart &#8230; use 4 characters for a domain extension meant for _mobile devices_.  they could have at least acquired &#8216;.m&#8217; instead.</p>
<p>seriously, we don&#8217;t need another TLD.  .com is more than sufficient.  this is just another way for &#8216;dotmobi&#8217; to make a ton of cash.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
