<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Twitter API updates, FireEagle and new Flickr API fun &#8230;</title>
	<atom:link href="http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/feed/" rel="self" type="application/rss+xml" />
	<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/</link>
	<description>Maps and Stuff</description>
	<lastBuildDate>Mon, 01 Mar 2010 11:16:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Twitter Search</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-2481</link>
		<dc:creator><![CDATA[Twitter Search]]></dc:creator>
		<pubDate>Wed, 27 May 2009 01:21:14 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-2481</guid>
		<description><![CDATA[thats great that you are talking about the twitter api,a good example of searching with the twitter api is on twiogle.com because you can search on twitter and google at the same time.]]></description>
		<content:encoded><![CDATA[<p>thats great that you are talking about the twitter api,a good example of searching with the twitter api is on twiogle.com because you can search on twitter and google at the same time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jon</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1851</link>
		<dc:creator><![CDATA[jon]]></dc:creator>
		<pubDate>Mon, 07 Jul 2008 01:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1851</guid>
		<description><![CDATA[I now very little to nothing about programming so this question is bound to be moronic:
after reading your post I wonder: can one geotag keywords on twitter?? Or what you described limits only to updating location on my profile??]]></description>
		<content:encoded><![CDATA[<p>I now very little to nothing about programming so this question is bound to be moronic:<br />
after reading your post I wonder: can one geotag keywords on twitter?? Or what you described limits only to updating location on my profile??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Cizek</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1831</link>
		<dc:creator><![CDATA[David Cizek]]></dc:creator>
		<pubDate>Tue, 27 May 2008 09:34:29 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1831</guid>
		<description><![CDATA[Very interesting article, thanks. Currently we have a demonstration of location enhanced browser for mobile phone ... updating status on twitter with location. It can be extended to update not just status but the location. Or anyone who wnat to play with this? Its easy: &lt;a href=&quot;http://blog.locify.com/2008/05/twitter-service-for-locify-updates.html&quot; rel=&quot;nofollow&quot;&gt;Locify and Twitter description - try it&lt;/a&gt;.
DavidC]]></description>
		<content:encoded><![CDATA[<p>Very interesting article, thanks. Currently we have a demonstration of location enhanced browser for mobile phone &#8230; updating status on twitter with location. It can be extended to update not just status but the location. Or anyone who wnat to play with this? Its easy: <a href="http://blog.locify.com/2008/05/twitter-service-for-locify-updates.html" rel="nofollow">Locify and Twitter description &#8211; try it</a>.<br />
DavidC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: geobloggers &#187; Yahoo Woe (Where On Earth, that is) IDs.</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1827</link>
		<dc:creator><![CDATA[geobloggers &#187; Yahoo Woe (Where On Earth, that is) IDs.]]></dc:creator>
		<pubDate>Mon, 12 May 2008 20:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1827</guid>
		<description><![CDATA[[...] more awesome than I&#8217;m going to make it sound in this blog post. I already did a little bit back here. But a quick call out to these two functions that&#8217;ll try and find you WoE IDs based on string [...]]]></description>
		<content:encoded><![CDATA[<p>[...] more awesome than I&#8217;m going to make it sound in this blog post. I already did a little bit back here. But a quick call out to these two functions that&#8217;ll try and find you WoE IDs based on string [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-05-02 &#171; Breyten&#8217;s Dev Blog</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1865</link>
		<dc:creator><![CDATA[links for 2008-05-02 &#171; Breyten&#8217;s Dev Blog]]></dc:creator>
		<pubDate>Fri, 02 May 2008 11:30:41 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1865</guid>
		<description><![CDATA[[...] geobloggers &quot; Twitter API updates, FireEagle and new Flickr API fun &#8230; (tags: geo readme) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] geobloggers &quot; Twitter API updates, FireEagle and new Flickr API fun &#8230; (tags: geo readme) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Turner</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1874</link>
		<dc:creator><![CDATA[Andrew Turner]]></dc:creator>
		<pubDate>Fri, 02 May 2008 01:34:21 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1874</guid>
		<description><![CDATA[Twitter doesn&#039;t include the location in Tweet updates - so you still have to query the user&#039;s profile to get the location with any new tweet. Hoping they add this perhaps using the XMPP-Geolocation spec.]]></description>
		<content:encoded><![CDATA[<p>Twitter doesn&#8217;t include the location in Tweet updates &#8211; so you still have to query the user&#8217;s profile to get the location with any new tweet. Hoping they add this perhaps using the XMPP-Geolocation spec.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RevDanCatt</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1880</link>
		<dc:creator><![CDATA[RevDanCatt]]></dc:creator>
		<pubDate>Thu, 01 May 2008 15:45:11 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1880</guid>
		<description><![CDATA[Oh yay, thanks Seth.

It did seem an odd omission, but I guess it&#039;s not. Which makes the steps involved above even easier, ty.]]></description>
		<content:encoded><![CDATA[<p>Oh yay, thanks Seth.</p>
<p>It did seem an odd omission, but I guess it&#8217;s not. Which makes the steps involved above even easier, ty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1879</link>
		<dc:creator><![CDATA[Seth]]></dc:creator>
		<pubDate>Thu, 01 May 2008 15:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1879</guid>
		<description><![CDATA[Actually, Fire Eagle does allow you to resolve WOE ids (and most place ids) via the &#039;lookup&#039; method.  Pass in &#039;woeid= 2487956&#039; and you&#039;ll get the matching location.]]></description>
		<content:encoded><![CDATA[<p>Actually, Fire Eagle does allow you to resolve WOE ids (and most place ids) via the &#8216;lookup&#8217; method.  Pass in &#8216;woeid= 2487956&#8242; and you&#8217;ll get the matching location.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt King</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1884</link>
		<dc:creator><![CDATA[Matt King]]></dc:creator>
		<pubDate>Wed, 30 Apr 2008 18:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1884</guid>
		<description><![CDATA[This is awesome, so glad they are finally getting that location is also important. It&#039;s going to greatly help my app TwitterLocal (http://www.twitterlocal.net). Excited!]]></description>
		<content:encoded><![CDATA[<p>This is awesome, so glad they are finally getting that location is also important. It&#8217;s going to greatly help my app TwitterLocal (<a href="http://www.twitterlocal.net" rel="nofollow">http://www.twitterlocal.net</a>). Excited!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Lazarus</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1886</link>
		<dc:creator><![CDATA[Joe Lazarus]]></dc:creator>
		<pubDate>Wed, 30 Apr 2008 16:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1886</guid>
		<description><![CDATA[Have you seen Brightkite.com?  They offer a way to update Twitter and FireEagle via the web or SMS.  Plus, they geo-tag each Twitter post in addition to your profile location.  I have a few invites.  Email me if you&#039;d like one.]]></description>
		<content:encoded><![CDATA[<p>Have you seen Brightkite.com?  They offer a way to update Twitter and FireEagle via the web or SMS.  Plus, they geo-tag each Twitter post in addition to your profile location.  I have a few invites.  Email me if you&#8217;d like one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RevDanCatt</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1864</link>
		<dc:creator><![CDATA[RevDanCatt]]></dc:creator>
		<pubDate>Wed, 30 Apr 2008 16:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1864</guid>
		<description><![CDATA[Ah, in an ideal world we&#039;d have easy available mappings between GeoNames IDs and WoeIDs :)

It does seem straight-forwards for Twitter to do that, but currently they don&#039;t, it&#039;s one location for everything, rather than each tweet.

I don&#039;t see so much of the &#039;cron&#039; like pining as a problem. When the location is coupled with tweets on twitter then whatever is listening for your twitter updates will receive them (and your new location if you have one) as you make them, with no pinging needed.

And while I&#039;m sure there are applications that want to constantly ping Fire Eagle for your location, I&#039;ve always seen that as a request location only when you need to know it thing. Even if that does turn out to be once a minute, while you&#039;re doing *something* I don&#039;t really see me needing something pinging it on a 24 hour basis. Or at least more than one thing anyway ;)]]></description>
		<content:encoded><![CDATA[<p>Ah, in an ideal world we&#8217;d have easy available mappings between GeoNames IDs and WoeIDs :)</p>
<p>It does seem straight-forwards for Twitter to do that, but currently they don&#8217;t, it&#8217;s one location for everything, rather than each tweet.</p>
<p>I don&#8217;t see so much of the &#8216;cron&#8217; like pining as a problem. When the location is coupled with tweets on twitter then whatever is listening for your twitter updates will receive them (and your new location if you have one) as you make them, with no pinging needed.</p>
<p>And while I&#8217;m sure there are applications that want to constantly ping Fire Eagle for your location, I&#8217;ve always seen that as a request location only when you need to know it thing. Even if that does turn out to be once a minute, while you&#8217;re doing *something* I don&#8217;t really see me needing something pinging it on a 24 hour basis. Or at least more than one thing anyway ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Turner</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1873</link>
		<dc:creator><![CDATA[Andrew Turner]]></dc:creator>
		<pubDate>Wed, 30 Apr 2008 12:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1873</guid>
		<description><![CDATA[Setting up WoeID to challenge GeoNames ID? :)

It seems straight-forward for Twitter to store your profile location along with any tweet, thereby creating a time-history of geotagged tweets.

The problem with both Twitter profile and even FireEagle currently is there isn&#039;t a mechanism for services to subscribe to location updates. So they are relegated to &quot;cron&quot; like constant pinging.]]></description>
		<content:encoded><![CDATA[<p>Setting up WoeID to challenge GeoNames ID? :)</p>
<p>It seems straight-forward for Twitter to store your profile location along with any tweet, thereby creating a time-history of geotagged tweets.</p>
<p>The problem with both Twitter profile and even FireEagle currently is there isn&#8217;t a mechanism for services to subscribe to location updates. So they are relegated to &#8220;cron&#8221; like constant pinging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bish</title>
		<link>http://geobloggers.wordpress.com/2008/04/29/twitter-api-updates-fireeagle-and-new-flickr-api-fun/#comment-1872</link>
		<dc:creator><![CDATA[bish]]></dc:creator>
		<pubDate>Wed, 30 Apr 2008 10:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://geobloggers.com/archives/?p=176#comment-1872</guid>
		<description><![CDATA[This also looks like an interesting project: http://www.lukator.com because it provides functions to set your current position, to write messages/blogs with location information and to track the surrounding area.]]></description>
		<content:encoded><![CDATA[<p>This also looks like an interesting project: <a href="http://www.lukator.com" rel="nofollow">http://www.lukator.com</a> because it provides functions to set your current position, to write messages/blogs with location information and to track the surrounding area.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

