<?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: Tidepool download usability critique, part 2</title>
	<atom:link href="http://dowhatimean.net/2005/03/tidepool-download-usability-critique-part-2/feed" rel="self" type="application/rss+xml" />
	<link>http://dowhatimean.net/2005/03/tidepool-download-usability-critique-part-2</link>
	<description>Richard Cyganiak's Weblog</description>
	<pubDate>Wed, 07 Jan 2009 02:48:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Jon</title>
		<link>http://dowhatimean.net/2005/03/tidepool-download-usability-critique-part-2#comment-151</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Sat, 26 Mar 2005 04:12:13 +0000</pubDate>
		<guid isPermaLink="false">http://dowhatimean.net/2005/03/tidepool-download-usability-critique-part-2#comment-151</guid>
		<description>&lt;p&gt;BTW: some of the difficulties in creating a smooth sequence of download events lies in the following:
1) Tidepool needs to know the user&#8217;s URL to make unique tags from the get-go. (We decided not to try creating tags with local URL, then converting them on the fly when uploaded.)
2) going straight to a registration page might seem weird to an existing user who just needs to login. but maybe, if it is just username, password, email, we can get away with it.&lt;/p&gt;

&lt;p&gt;tim and i will have to ponder a few different scenarios.&lt;/p&gt;

&lt;p&gt;for now, simply trying to better explain it will be a good start, eh? (shoot, doesn&#8217;t everyone know what we mean?)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>BTW: some of the difficulties in creating a smooth sequence of download events lies in the following:
1) Tidepool needs to know the user&#8217;s URL to make unique tags from the get-go. (We decided not to try creating tags with local URL, then converting them on the fly when uploaded.)
2) going straight to a registration page might seem weird to an existing user who just needs to login. but maybe, if it is just username, password, email, we can get away with it.</p>

<p>tim and i will have to ponder a few different scenarios.</p>

<p>for now, simply trying to better explain it will be a good start, eh? (shoot, doesn&#8217;t everyone know what we mean?)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://dowhatimean.net/2005/03/tidepool-download-usability-critique-part-2#comment-150</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Sat, 26 Mar 2005 03:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://dowhatimean.net/2005/03/tidepool-download-usability-critique-part-2#comment-150</guid>
		<description>&lt;p&gt;Great ideas! where were you at beta time? You can post such feature ideas on the forum&#8230; but first you must register (ack!). you&#8217;ll love this: we don&#8217;t yet have it auto-linked to the same username/password ;=) &#8212; you don&#8217;t have to rant about that one :=)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great ideas! where were you at beta time? You can post such feature ideas on the forum&#8230; but first you must register (ack!). you&#8217;ll love this: we don&#8217;t yet have it auto-linked to the same username/password ;=) &#8212; you don&#8217;t have to rant about that one :=)</p>]]></content:encoded>
	</item>
</channel>
</rss>
