<?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: Ubiquitous information &#8211; Part 1</title>
	<atom:link href="http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/</link>
	<description>And Other Unfocused Things</description>
	<lastBuildDate>Sun, 22 Aug 2010 12:36:31 +1200</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Gustavo</title>
		<link>http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/#comment-308</link>
		<dc:creator>Gustavo</dc:creator>
		<pubDate>Sat, 14 Feb 2009 23:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=118#comment-308</guid>
		<description>This is exactly what I want implemented.  This would be phenomenal.  I&#039;m looking forward to the API post.  How were you able to convert the prefs string to json?...or did you just insert it as { key:val,key2:val2 } instead of &quot;{key:val, key2:val2}&quot;..etc?</description>
		<content:encoded><![CDATA[<p>This is exactly what I want implemented.  This would be phenomenal.  I&#8217;m looking forward to the API post.  How were you able to convert the prefs string to json?&#8230;or did you just insert it as { key:val,key2:val2 } instead of &#8220;{key:val, key2:val2}&#8221;..etc?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weekly Focus: Email Commands &#171; chimney</title>
		<link>http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/#comment-221</link>
		<dc:creator>Weekly Focus: Email Commands &#171; chimney</dc:creator>
		<pubDate>Thu, 05 Feb 2009 06:36:03 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=118#comment-221</guid>
		<description>[...] The default email provider will be based on your browsing history - the email account with the highest frecency (see the detect-email-provider command). But you can change your default by simply telling Ubiquity &#8220;my email is yahoo&#8221;. [...]</description>
		<content:encoded><![CDATA[<p>[...] The default email provider will be based on your browsing history &#8211; the email account with the highest frecency (see the detect-email-provider command). But you can change your default by simply telling Ubiquity &#8220;my email is yahoo&#8221;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Labs Update - January 2009 &#124; about ICT</title>
		<link>http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/#comment-209</link>
		<dc:creator>Labs Update - January 2009 &#124; about ICT</dc:creator>
		<pubDate>Sun, 01 Feb 2009 15:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=118#comment-209</guid>
		<description>[...] McBride put together a high-level look at information storage in [...]</description>
		<content:encoded><![CDATA[<p>[...] McBride put together a high-level look at information storage in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mozilla Labs &#187; Blog Archive &#187; Labs Update - January 2009</title>
		<link>http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/#comment-207</link>
		<dc:creator>Mozilla Labs &#187; Blog Archive &#187; Labs Update - January 2009</dc:creator>
		<pubDate>Sun, 01 Feb 2009 00:28:50 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=118#comment-207</guid>
		<description>[...] McBride put together a high-level look at information storage in [...]</description>
		<content:encoded><![CDATA[<p>[...] McBride put together a high-level look at information storage in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Here&#8217;s to the lazy ones: a semantic LazyBar &#171; chimney</title>
		<link>http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/#comment-199</link>
		<dc:creator>Here&#8217;s to the lazy ones: a semantic LazyBar &#171; chimney</dc:creator>
		<pubDate>Mon, 26 Jan 2009 10:12:37 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=118#comment-199</guid>
		<description>[...] The OpenCalais results are then cached for the session. I stored the JSON object as a preference. Blair McBride promises to give us a better way to store data in Ubiquity. [...]</description>
		<content:encoded><![CDATA[<p>[...] The OpenCalais results are then cached for the session. I stored the JSON object as a preference. Blair McBride promises to give us a better way to store data in Ubiquity. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abi</title>
		<link>http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/#comment-195</link>
		<dc:creator>Abi</dc:creator>
		<pubDate>Sat, 24 Jan 2009 14:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=118#comment-195</guid>
		<description>This is indeed a very important step forward for the usability of Ubiquity. Looking forward to the developer API details, too. Right now, I&#039;m always storing JSON objects in preferences which is kinda annoying.</description>
		<content:encoded><![CDATA[<p>This is indeed a very important step forward for the usability of Ubiquity. Looking forward to the developer API details, too. Right now, I&#8217;m always storing JSON objects in preferences which is kinda annoying.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
