<?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: My ideal 802.11 phone</title>
	<atom:link href="http://blog.matthewgast.com/2007/02/13/my-ideal-80211-phone/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.matthewgast.com/2007/02/13/my-ideal-80211-phone/</link>
	<description>A former physicist tries to make sense of technology</description>
	<pubDate>Thu, 28 Aug 2008 02:26:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Surfing the Luminiferous Ether &#187; Blog Archive &#187; Oh, no, OpenMoko delayed!</title>
		<link>http://blog.matthewgast.com/2007/02/13/my-ideal-80211-phone/#comment-895</link>
		<dc:creator>Surfing the Luminiferous Ether &#187; Blog Archive &#187; Oh, no, OpenMoko delayed!</dc:creator>
		<pubDate>Sat, 03 Mar 2007 21:00:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.matthewgast.com/2007/02/13/my-ideal-80211-phone/#comment-895</guid>
		<description>[...] On February 12, I went to check up on the status of the OpenMoko project. With my likely disappointment on the iPhone, I&#8217;ve been looking for a replacement for my aging four-year-old Nokia 6600. Based on my set of ideal features for an 802.11 phone, I&#8217;ve been looking seriously at the Nokia E series, but they are quite expensive. The recent announcement of the &#8220;i&#8221; models in the E series lineup (E61i, etc) has shifted my allegiance slightly. I&#8217;ve been working with an E series, but it has limited battery life and a flaky SIP stack. My thoughts increasingly turn towards OpenMoko, since it would embrace SIP and open telephony in a way that is still alien to the telcos and their big suppliers. Unfortunately, the project has been delayed a short while. There are good reasons for this, namely that the team is dedicated to having a completely open system from hardware specs up through the toolchain before finally getting to the phone software itself. All commendable, but it doesn&#8217;t make it sting any less. [...]</description>
		<content:encoded><![CDATA[<p>[...] On February 12, I went to check up on the status of the OpenMoko project. With my likely disappointment on the iPhone, I&#8217;ve been looking for a replacement for my aging four-year-old Nokia 6600. Based on my set of ideal features for an 802.11 phone, I&#8217;ve been looking seriously at the Nokia E series, but they are quite expensive. The recent announcement of the &#8220;i&#8221; models in the E series lineup (E61i, etc) has shifted my allegiance slightly. I&#8217;ve been working with an E series, but it has limited battery life and a flaky SIP stack. My thoughts increasingly turn towards OpenMoko, since it would embrace SIP and open telephony in a way that is still alien to the telcos and their big suppliers. Unfortunately, the project has been delayed a short while. There are good reasons for this, namely that the team is dedicated to having a completely open system from hardware specs up through the toolchain before finally getting to the phone software itself. All commendable, but it doesn&#8217;t make it sting any less. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
