<?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: The .mobi Domain is a Big Mistake</title>
	<atom:link href="http://obviousdiversion.com/general/mobi-domain/feed/" rel="self" type="application/rss+xml" />
	<link>http://obviousdiversion.com/general/mobi-domain/</link>
	<description></description>
	<pubDate>Fri, 16 May 2008 20:37:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Christian</title>
		<link>http://obviousdiversion.com/general/mobi-domain/#comment-14388</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Thu, 25 May 2006 19:48:34 +0000</pubDate>
		<guid isPermaLink="false">http://obviousdiversion.com/general/mobi-domain/#comment-14388</guid>
		<description>I've carried both PDAs and mobile phones over the years with a web browser and currently carry an EVDO phone with a reasonable browser, so assuming ignorance on my part, choose your own adventure style, doesn't exactly help your argument.

The problem isn't with the domain extension.  It's the crappy markup behind it.  Instead of developing a whole second version of your app for a 'mobile' which will vary widely in specs, why not fix the app you've already got.  It'll save you time, money and your users grief when they're forced to guess if they should go to .com or .mobi.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve carried both PDAs and mobile phones over the years with a web browser and currently carry an EVDO phone with a reasonable browser, so assuming ignorance on my part, choose your own adventure style, doesn&#8217;t exactly help your argument.</p>
<p>The problem isn&#8217;t with the domain extension.  It&#8217;s the crappy markup behind it.  Instead of developing a whole second version of your app for a &#8216;mobile&#8217; which will vary widely in specs, why not fix the app you&#8217;ve already got.  It&#8217;ll save you time, money and your users grief when they&#8217;re forced to guess if they should go to .com or .mobi.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Castle</title>
		<link>http://obviousdiversion.com/general/mobi-domain/#comment-14387</link>
		<dc:creator>Steve Castle</dc:creator>
		<pubDate>Thu, 25 May 2006 19:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://obviousdiversion.com/general/mobi-domain/#comment-14387</guid>
		<description>The idea behind .mobi is conformity to standards and accepting those standards.  Using .mobi as a scapegoat for other bogus extensions like saying most networks (.net) fall under commercial entities (.com).  To debate the point and further healthy discussion, I pose the following questions.

Do you have an internet capable device?

If no, I recommend you get one, then you might have a little more of an understanding of the issue, whether or not it comforms with Web Standards.

If yes, continue

When is the last time you took your mobile device and surfed without reaching a page that was not mobile-friendly?

Chances are, never.  There's not enough of them out there.  By introuducing .mobi, there is a push for the publishing of mobile-friendly websites.  I understand your point about "yahoo.com should be both the regular and mobile-friendly website".  In a perfect world, that would definitely be the case.  I'm not asking you to be an early-adopter or even an early part of the early majority, but at least think about how this could affect mobile computing as a whole regardless in the end if .mobi sinks or floats.</description>
		<content:encoded><![CDATA[<p>The idea behind .mobi is conformity to standards and accepting those standards.  Using .mobi as a scapegoat for other bogus extensions like saying most networks (.net) fall under commercial entities (.com).  To debate the point and further healthy discussion, I pose the following questions.</p>
<p>Do you have an internet capable device?</p>
<p>If no, I recommend you get one, then you might have a little more of an understanding of the issue, whether or not it comforms with Web Standards.</p>
<p>If yes, continue</p>
<p>When is the last time you took your mobile device and surfed without reaching a page that was not mobile-friendly?</p>
<p>Chances are, never.  There&#8217;s not enough of them out there.  By introuducing .mobi, there is a push for the publishing of mobile-friendly websites.  I understand your point about &#8220;yahoo.com should be both the regular and mobile-friendly website&#8221;.  In a perfect world, that would definitely be the case.  I&#8217;m not asking you to be an early-adopter or even an early part of the early majority, but at least think about how this could affect mobile computing as a whole regardless in the end if .mobi sinks or floats.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Vogt</title>
		<link>http://obviousdiversion.com/general/mobi-domain/#comment-13118</link>
		<dc:creator>Dave Vogt</dc:creator>
		<pubDate>Wed, 03 May 2006 05:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://obviousdiversion.com/general/mobi-domain/#comment-13118</guid>
		<description>I agree with Ansel that even the best xhtml isn't going to make Amazon useful on a 1 in screen, but for that matter, what is? I don't believe Amazon could provide a useful service that would not completely overwhelm a mobile browser with sheer volume of information. I believe wholeheartedly that the answer is clean code and &lt;em&gt;accessibility considerations&lt;/em&gt;. Make a site that's accessible to a screen reader or text browser and you'll be accessible to mobiles. It also removes the trouble of maintaining seperate sites with (nearly) identical content. As we've seen in the past, seperate is rarely, if ever, equal.</description>
		<content:encoded><![CDATA[<p>I agree with Ansel that even the best xhtml isn&#8217;t going to make Amazon useful on a 1 in screen, but for that matter, what is? I don&#8217;t believe Amazon could provide a useful service that would not completely overwhelm a mobile browser with sheer volume of information. I believe wholeheartedly that the answer is clean code and <em>accessibility considerations</em>. Make a site that&#8217;s accessible to a screen reader or text browser and you&#8217;ll be accessible to mobiles. It also removes the trouble of maintaining seperate sites with (nearly) identical content. As we&#8217;ve seen in the past, seperate is rarely, if ever, equal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ginnie</title>
		<link>http://obviousdiversion.com/general/mobi-domain/#comment-12950</link>
		<dc:creator>ginnie</dc:creator>
		<pubDate>Fri, 28 Apr 2006 17:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://obviousdiversion.com/general/mobi-domain/#comment-12950</guid>
		<description>I agree with your notion of web standards, CG, but given the lameness of reality and its lack of standardization, this article sorta helps, I think:

http://webmonkey.com/webmonkey/04/12/index4a.html?tw=design</description>
		<content:encoded><![CDATA[<p>I agree with your notion of web standards, CG, but given the lameness of reality and its lack of standardization, this article sorta helps, I think:</p>
<p><a href="http://webmonkey.com/webmonkey/04/12/index4a.html?tw=design" rel="nofollow"></a><a href='http://webmonkey.com/webmonkey/04/12/index4a.html?tw=design'>http://webmonkey.com/webmonkey/04/12/index4a.html?tw=design</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ansel</title>
		<link>http://obviousdiversion.com/general/mobi-domain/#comment-12877</link>
		<dc:creator>Ansel</dc:creator>
		<pubDate>Tue, 25 Apr 2006 16:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://obviousdiversion.com/general/mobi-domain/#comment-12877</guid>
		<description>Agreed 100%.

My additional 2 cents is that sites should also be publishing APIs that allow developers for mobile gadgets (or anything else) to figure out what to do with data; sometimes even super standards-compliant XHTML markup isn't the most useful format for information to be in, depending on what you want to do.  (Think Amazon: can you really imagine trying to do anything on Amazon from a 1-inch screen?)</description>
		<content:encoded><![CDATA[<p>Agreed 100%.</p>
<p>My additional 2 cents is that sites should also be publishing APIs that allow developers for mobile gadgets (or anything else) to figure out what to do with data; sometimes even super standards-compliant XHTML markup isn&#8217;t the most useful format for information to be in, depending on what you want to do.  (Think Amazon: can you really imagine trying to do anything on Amazon from a 1-inch screen?)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
