<?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: Twitter introduces Hovercards</title>
	<atom:link href="http://www.igeek.co.za/2010/02/04/twitter-introduces-hovercards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.igeek.co.za/2010/02/04/twitter-introduces-hovercards/</link>
	<description>A Capetonian geek living the life</description>
	<lastBuildDate>Thu, 02 Feb 2012 05:51:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Kloon</title>
		<link>http://www.igeek.co.za/2010/02/04/twitter-introduces-hovercards/comment-page-1/#comment-961</link>
		<dc:creator>Kloon</dc:creator>
		<pubDate>Thu, 04 Feb 2010 05:59:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.igeek.co.za/?p=739#comment-961</guid>
		<description>Yea Twitter stated on their blog that they are introducing this feature because there is still allot of users using Twitter.com to read and write tweets.</description>
		<content:encoded><![CDATA[<p>Yea Twitter stated on their blog that they are introducing this feature because there is still allot of users using Twitter.com to read and write tweets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Scott</title>
		<link>http://www.igeek.co.za/2010/02/04/twitter-introduces-hovercards/comment-page-1/#comment-960</link>
		<dc:creator>Paul Scott</dc:creator>
		<pubDate>Thu, 04 Feb 2010 05:52:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.igeek.co.za/?p=739#comment-960</guid>
		<description>These are cool, but redundant in the bigger context. Twitter already exposes all user details as an hCard microformat, which means that you have all the details for any compatible site/datastore. The trick is that most &quot;regular&quot; users will not know about that, and this is probably the reason for the introduction of these things.

As microformats become more ubiquitous, we will see less of this type of thing and more interaction of users between more apps.</description>
		<content:encoded><![CDATA[<p>These are cool, but redundant in the bigger context. Twitter already exposes all user details as an hCard microformat, which means that you have all the details for any compatible site/datastore. The trick is that most &#8220;regular&#8221; users will not know about that, and this is probably the reason for the introduction of these things.</p>
<p>As microformats become more ubiquitous, we will see less of this type of thing and more interaction of users between more apps.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

