<?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: Lessons from photography in experience design</title>
	<atom:link href="http://www.purecaffeine.com/2009/08/lessons-from-photography-in-experience-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.purecaffeine.com/2009/08/lessons-from-photography-in-experience-design/</link>
	<description>Interaction experience design blog - web, social, gov 2.0</description>
	<lastBuildDate>Wed, 28 Jul 2010 10:53:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: NathanaelB</title>
		<link>http://www.purecaffeine.com/2009/08/lessons-from-photography-in-experience-design/comment-page-1/#comment-15</link>
		<dc:creator>NathanaelB</dc:creator>
		<pubDate>Sun, 30 Aug 2009 09:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://purecaffeine.com/?p=51#comment-15</guid>
		<description>Thanks Chris; it&#039;s certainly a start. TwitterVision will detect the L: machine tag in tweets to update your location there but it&#039;s not very useful. Even if it updated your Twitter bio it doesn&#039;t really expose that context to users.

The problem I&#039;m grappling with is that we need the solution to be usable in that we can&#039;t be asking and expecting people to provide all this metadata. For it to really work all this context should be sensed and provided by the system rather than the user explicitly maintaining this stuff.

Geo-aware devices are a start - but not everyone has one, not everyone messages from one and not everyone wants all this information made available. But perhaps we will get to that next level of privacy disclosure and relaxation now that we&#039;re getting comfortable with Facebook.

And then how to present it? We don&#039;t want a paragraph accompanying every tweet with textual information like &lt;em&gt;&quot;When Nathanael tweeted this he was 20 miles west of Hana on Maui. His girlfriend was driving the car at the time and it was just starting to rain. The temperature was a comfortable 30 degrees outside although they had the A/C on in the car&quot;.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Thanks Chris; it&#8217;s certainly a start. TwitterVision will detect the L: machine tag in tweets to update your location there but it&#8217;s not very useful. Even if it updated your Twitter bio it doesn&#8217;t really expose that context to users.</p>
<p>The problem I&#8217;m grappling with is that we need the solution to be usable in that we can&#8217;t be asking and expecting people to provide all this metadata. For it to really work all this context should be sensed and provided by the system rather than the user explicitly maintaining this stuff.</p>
<p>Geo-aware devices are a start &#8211; but not everyone has one, not everyone messages from one and not everyone wants all this information made available. But perhaps we will get to that next level of privacy disclosure and relaxation now that we&#8217;re getting comfortable with Facebook.</p>
<p>And then how to present it? We don&#8217;t want a paragraph accompanying every tweet with textual information like <em>&#8220;When Nathanael tweeted this he was 20 miles west of Hana on Maui. His girlfriend was driving the car at the time and it was just starting to rain. The temperature was a comfortable 30 degrees outside although they had the A/C on in the car&#8221;.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.purecaffeine.com/2009/08/lessons-from-photography-in-experience-design/comment-page-1/#comment-14</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 30 Aug 2009 08:21:59 +0000</pubDate>
		<guid isPermaLink="false">http://purecaffeine.com/?p=51#comment-14</guid>
		<description>I think these contexts are being dealt with now via multiple accounts - at least in terms of intended audience. The profile gives a very broad context (permanent location and bio), but I can really see the benefit of some kind of built-in commands for changing that. Wouldn&#039;t it be cool if twitter allowed you to enter something like &quot;^location hawaii&quot; in a tweet, and knew then that every tweet that followed was in hawaii (until you gave it another ^location update). 

These &quot;context updates&quot; might also include:

^group (for targeting specific follower groups, assuming they existed)
^location 
^activity
^mood (to be very myspace)

What do you think?

Cheers,
Chris</description>
		<content:encoded><![CDATA[<p>I think these contexts are being dealt with now via multiple accounts &#8211; at least in terms of intended audience. The profile gives a very broad context (permanent location and bio), but I can really see the benefit of some kind of built-in commands for changing that. Wouldn&#8217;t it be cool if twitter allowed you to enter something like &#8220;^location hawaii&#8221; in a tweet, and knew then that every tweet that followed was in hawaii (until you gave it another ^location update). </p>
<p>These &#8220;context updates&#8221; might also include:</p>
<p>^group (for targeting specific follower groups, assuming they existed)<br />
^location<br />
^activity<br />
^mood (to be very myspace)</p>
<p>What do you think?</p>
<p>Cheers,<br />
Chris</p>
]]></content:encoded>
	</item>
</channel>
</rss>
