<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:www.readwriteweb.com,2011:/1/tag:www.readwriteweb.com,2009://1.17034-</id>
  <updated>2011-08-16T16:20:53Z</updated>
  <title>Comments for Seesmic Web Gets Lists and Geolocation</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.35-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009://1.17034</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=17034" title="Seesmic Web Gets Lists and Geolocation" />
    <published>2009-11-06T16:49:41Z</published>
    <updated>2009-11-06T19:31:25Z</updated>
    <title>Seesmic Web Gets Lists and Geolocation</title>
    <summary>Seesmic just announced the launch of Twitter lists in its browser-based Seesmic Web Twitter client. Earlier this week, Seesmic released the first desktop Twitter client with support for lists. Despite Seesmic&apos;s best efforts, Brizzly managed to become the first company to release a web client with support for lists earlier today. Seesmic Web offers another...</summary>
    <author>
      <name>Frederic Lardinois</name>
      
    </author>
    
    <category term="News" />
    
    <category term="Twitter" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img alt="seesmic_logo_jul09.png" src="http://www.readwriteweb.com/images/seesmic_logo_jul09.png"  /><a href="http://seesmic.com">Seesmic</a> just announced the launch of Twitter lists in its browser-based <a href="http://seesmic.com/app">Seesmic Web Twitter</a> client. Earlier this week, Seesmic <a href="http://www.readwriteweb.com/archives/seesmic_adds_support_for_twitter_lists.php">released</a> the first desktop Twitter client with support for lists. Despite Seesmic's best efforts, <a href="http://brizzly.com">Brizzly</a> managed to become the first company to release a web client with support for lists earlier today. Seesmic Web offers another first for web-based Twitter clients, however: support for <a href="http://blog.twitter.com/2009/08/location-location-location.html">Twitter's geolocation API</a>.</p>]]>
      <![CDATA[<h2>Lists With Auto-Updates</h2>

<p><img alt="seesmic_web_lists.jpg" align="right" src="http://www.readwriteweb.com/images/seesmic_web_lists.jpg"  />In Seesmic's web interface, users can now simply hover their cursor over profile pictures and a menu will appear. This menu, among other things, allows Seesmic's users to add others to lists. One nice aspect of the web interface is that it auto-updates lists when new tweets come in. The desktop app - at least in the current version - doesn't do this and forces users to manually refresh lists to see updates.</p>

<h2>Geolocation</h2>

<p>In addition to supporting lists, the new version of the web client also supports Twitter's <a href="http://blog.twitter.com/2009/08/location-location-location.html">geolocation API</a>. Seesmic users can't share their locations, but whenever a Twitter user broadcasts location data, a little pin will appear underneath the profile picture, and hovering over this pin will bring up a map. Only a few <a href="http://twitter.com/rsarver">users</a> actually have the ability to broadcast their locations at this point. Twitter is only giving platform developers access to this feature for now, but it should soon become a standard feature in mobile clients like Tweetie 2 and Twitterrific.</p>

<p><img alt="twitter_geo_seesmic_web.jpg" src="http://www.readwriteweb.com/images/twitter_geo_seesmic_web.jpg"  /></p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.17034-comment:167683</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.17034" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php#c167683" />
    <title>Comment from Jason Goodrich on 2009-11-09</title>
    <author>
        <name>Jason Goodrich</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>GPS and list auto update is cool. But how about an auto list creator that's content based? Now there's an app for that: </p>

<p>Awesome Lists is a new release (as in today) that makes creating and populating Twitter lists effortless and intuitive. It also spells doom for #hashtags. Gives you a full 140 to work with and get more RTs.</p>

<p>It was created by Abraham Williams and Team Awesome during SocialDevCamp Chicago. (#SDCChi) Check it: @awesomelists.</p>]]>
    </content>
    <published>2009-11-10T05:35:39Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.17034-comment:167405</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.17034" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php#c167405" />
    <title>Comment from Lawrence @ CRB on 2009-11-07</title>
    <author>
        <name>Lawrence @ CRB</name>
        <uri>http://www.creditrestorationbureau.comtionbureau.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.creditrestorationbureau.comtionbureau.com">
        <![CDATA[<p>I think this application is pretty cool but am worried about it slowing things down. Can anyone touch on this?</p>]]>
    </content>
    <published>2009-11-07T08:40:48Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.17034-comment:167332</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.17034" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php#c167332" />
    <title>Comment from Sam on 2009-11-06</title>
    <author>
        <name>Sam</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Congratulations to Loic and the Seesmic team for integrating lists and geo-location so fast. So how long before we have a Seesmic iPhone client with the same features.  </p>

<p>However I still prefer Tweetdeck for now and hope Iain Dodsworth can bring these same features out for the desktop and iPhone client but lets not have buggy update again like today.  Personally I really don't care about a website version. </p>

<p>As for twitter pls - lists are good but other clients have had groups for a while now and as for RT function about time. </p>

<p>Personally in a years time I think we will be focusing more on federated XMPP platforms like Wave, Identi.ca and others.</p>]]>
    </content>
    <published>2009-11-06T23:51:37Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.17034-comment:167305</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.17034" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/seesmic_web_gets_lists_and_geolocation.php#c167305" />
    <title>Comment from ipedia on 2009-11-06</title>
    <author>
        <name>ipedia</name>
        <uri>http://indopedia.gunadarma.ac.id</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://indopedia.gunadarma.ac.id">
        <![CDATA[<p>im prefer using digsby...</p>]]>
    </content>
    <published>2009-11-06T20:26:33Z</published>
  </entry>

</feed>
