<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.thegisforum.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tags 'twitter' and 'linkedin'</title><link>http://www.thegisforum.com/search/SearchResults.aspx?a=1&amp;o=DateDescending&amp;tag=twitter,linkedin&amp;orTags=0</link><description>Search results matching tags 'twitter' and 'linkedin'</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 SP1 (Build: 31106.3070)</generator><item><title>Foursquare – Teetering On the Edge of YASN</title><link>http://www.thegisforum.com/blogs/communitymashup/archive/2009/12/30/foursquare-teetering-on-the-edge-of-yasn.aspx</link><pubDate>Wed, 30 Dec 2009 16:33:44 GMT</pubDate><guid isPermaLink="false">ea949c24-ae5b-4586-8736-e4fb3bd2352f:7165</guid><dc:creator>Anonymous</dc:creator><description>I read with interest this article that was brought to my attention by @gis_Todd on Twitter. I have been playing with Foursquare for a few weeks now and I think this article is in sync with some observations I have had about it but also misses the mark on one key point.
I am one of [...]&lt;img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=geobabble.wordpress.com&amp;amp;blog=588413&amp;amp;post=769&amp;amp;subd=geobabble&amp;amp;ref=&amp;amp;feed=1" /&gt;</description></item></channel></rss>