<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>intereye - Web Analytics &#187; Twitter</title>
	<atom:link href="http://www.intereye.de/category/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.intereye.de</link>
	<description></description>
	<lastBuildDate>Fri, 27 Aug 2010 10:00:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>We need local hashtags for Twitter Geo-API</title>
		<link>http://www.intereye.de/2009/11/we-need-local-hashtags-for-twitter-geo-api/</link>
		<comments>http://www.intereye.de/2009/11/we-need-local-hashtags-for-twitter-geo-api/#comments</comments>
		<pubDate>Sat, 21 Nov 2009 13:12:53 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
				<category><![CDATA[Twitter]]></category>
		<category><![CDATA[geolocation]]></category>

		<guid isPermaLink="false">http://www.intereye.de/?p=530</guid>
		<description><![CDATA[Twitter launched its geolocation API yesterday. ReadWriteWeb wrote about possible uses of  geotaged tweets.
I did some testing yesterday. In my eyes,  a big problem is, that most clients use the default location for all tweets. That means that you get lots of geotagged tweets, but the content is not really in a local context.
I think [...]]]></description>
			<content:encoded><![CDATA[<p>Twitter launched its geolocation API yesterday. ReadWriteWeb wrote about <a title="ReadWriteWeb Twitter Geo API" href="http://www.readwriteweb.com/archives/twitter_location_api_possible_uses.php" target="_blank">possible uses of  geotaged tweets</a>.</p>
<p>I did some testing yesterday. In my eyes,  a big problem is, that most clients use the default location for all tweets. That means that you get lots of geotagged tweets, but the content is not really in a local context.</p>
<p>I think we need some common local hashtags for filtering to really take advantage of the new geolocation API:</p>
<ul>
<li>#news: For local news and information</li>
<li>#drink: For recommendations on bars, pubs, etc.</li>
<li>#food: For restaurants, fastfood, etc.</li>
<li>#gov: For messages from public authorities</li>
<li>#traffic: Traffic information, traffic jams, parking, etc.</li>
<li>#music: For information on music, concerts, bands, etc.</li>
<li>#party: For parties</li>
<li>#movie: For cinema and movie news</li>
<li>#museum: For exhibitions and museums</li>
<li>#art: For exhibitions, vernissages, etc.</li>
<li>#shop: For shopping, offers, vouchers, coupons, etc.</li>
<li>#gsales: For garage sales and flea markets</li>
</ul>
<p>Now your turn: Any more &#8211; or better ideas? Comments are very welcome.</p>
<hr />
<p><small>© Peter for <a href="http://www.intereye.de">intereye - Web Analytics</a>, 2009. |
<a href="http://www.intereye.de/2009/11/we-need-local-hashtags-for-twitter-geo-api/">Permalink</a> |
<a href="http://www.intereye.de/2009/11/we-need-local-hashtags-for-twitter-geo-api/#comments">No comment</a> |
Add to
<a href="http://del.icio.us/post?url=http://www.intereye.de/2009/11/we-need-local-hashtags-for-twitter-geo-api/&title=We need local hashtags for Twitter Geo-API">del.icio.us</a>
<br/>
Post tags: <a href="http://www.intereye.de/tag/geolocation/" rel="tag">geolocation</a>, <a href="http://www.intereye.de/tag/twitter/" rel="tag">Twitter</a><br/>
</small></p>
<p><small>Feed enhanced by <a href='http://planetozh.com/blog/my-projects/wordpress-plugin-better-feed-rss/'>Better Feed</a> from  <a href='http://planetozh.com/blog/'>Ozh</a></small></p>
]]></content:encoded>
			<wfw:commentRss>http://www.intereye.de/2009/11/we-need-local-hashtags-for-twitter-geo-api/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.249 seconds -->
