<?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/start/2009/10/handshakes-versus-noise-the-va.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/start/atom.xml" />
  <id>tag:www.readwriteweb.com,2012:/start//7/tag:www.readwriteweb.com,2009:/readwritestart//7.16779-</id>
  <updated>2012-02-03T20:01:19Z</updated>
  <title>Comments for Handshakes vs. Noise: The Value of Real-Time Location-Based Data</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.35-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009:/readwritestart//7.16779</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/start/2009/10/handshakes-versus-noise-the-va.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=16779" title="Handshakes vs. Noise: The Value of Real-Time Location-Based Data" />
    <published>2009-10-15T20:37:00Z</published>
    <updated>2009-10-15T21:42:04Z</updated>
    <title>Handshakes vs. Noise: The Value of Real-Time Location-Based Data</title>
    <summary>Similar to the real-time stream itself, ReadWriteWeb&apos;s Real-Time Web Summit dares to tackle a collective stream of consciousness. As the official live bloggers, the ReadWriteWeb team is aggregating some of today&apos;s highlights. One of the great things about this event is that many of the disparate voices in the stream are meeting face to face...</summary>
    <author>
      <name>Dana Oshiro</name>
      
    </author>
    
    <category term="Events" />
    
    <category term="Startups" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/start/">
      <![CDATA[<p><img alt="lead1_readwriteweb_oct09.jpg" src="http://www.readwriteweb.com/readwritestart/images/lead1_readwriteweb_oct09.jpg" width="150" height="143">Similar to the real-time stream itself, ReadWriteWeb's <a href="http://readwriteweb.com">Real-Time Web Summit</a> dares to tackle a collective stream of consciousness. As the official live bloggers, the ReadWriteWeb team is aggregating some of today's highlights. One of the great things about this event is that many of the disparate voices in the stream are meeting face to face (or in the flesh) for the first time. Naturally, this morning's event sessions included a discussion about location-based real-time data. </p>]]>
      <![CDATA[<p><img alt="geo_readwriteweb_oct09.jpg" src="http://www.readwriteweb.com/readwritestart/images/geo_readwriteweb_oct09.jpg" width="300" height="162" align="right">Led by WhereCamp founder <a href="http://hook.org/">Anselm Hook</a>, this session dealt with what <a href="http://twitter.com/dianneisnor">Waze's Diann Eisnor</a> coined "transactional cartography." Rather than being used simply to collect data from an unruly river, we agreed that the strength of location-based data is that it is actionable. The geo-locational stream solves a number of physical problems including:</p>

<p>1. <b>Getting Around:</b> Users can move from place to place by obtaining real-time data on traffic jams through sites like <a href="http://waze.com">Waze</a>.<br />
2. <b>Meeting Others:</b> Real-time updates from friends allow users to organize meetings through sites like <a href="http://travelandgather.com/">Travel and Gather</a> and <a href="http://platial.com/">Platial</a>. <br />
3. <b>Finding Items and Services:</b> Real-time services allow users to gain instant information on nearby services and products. For example, users can get free food through updates from Portland-based <a href="http://urbanedibles.org">Urban Edibles</a> </p>

<p>While real-time location-based information could greatly improve how we navigate the world, the unique facets of this type of stream also bring with them a number of issues. </p>

<p>From a business standpoint, data is unfortunately often treated like a closed commodity, used by commercial companies to fund development. Nevertheless, for consumers to get a holistic view of the stream, it seems as if these decentralized services need to be merged. </p>

<p>From a consumer standpoint, users need to broker trust between themselves before meetings can take place, and sometimes this trust isn't easy to verify. According to <a href="http://twitter.com/ross">SocialText's Ross Mayfield</a>, the barriers to adoption include privacy, safety and taste filtering. As more real-time location data becomes available, users need better tools to filter information and friend feeds that are pushed to them. </p>

<h2>What Is the Point?</h2>

<p>Perhaps the most important component of this discussion is why people are willing to share their location-based information. One fear about the real-time Web is that it allows anonymous weirdos to stalk you. However, many users see location-based sharing as "strength in numbers" and a vessel for collective solutions. While some speculate that we are sharing our whereabouts simply to recreate a sense of community, others believe that we are building up a grassroots marketplace. In your opinion what are the unique pros and cons of the location-based real-time Web? </p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009:/readwritestart//7.16779-comment:163063</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009:/readwritestart//7.16779" type="text/html" href="http://www.readwriteweb.com/start/2009/10/handshakes-versus-noise-the-va.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/start/2009/10/handshakes-versus-noise-the-va.php#c163063" />
    <title>Comment from haxpor on 2009-10-15</title>
    <author>
        <name>haxpor</name>
        <uri>http://haxpor.org</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://haxpor.org">
        <![CDATA[<p>It's more dangerous than we could thought of.<br />
Like the article said about it, someone can stalk.</p>

<p>If we really need the collaboration, we should devise some security such as only member can see the information. Use the particular and specific app only.</p>

<p>This is just an idea out of million.<br />
So don't get mad with me. :)</p>]]>
    </content>
    <published>2009-10-16T03:02:18Z</published>
  </entry>

</feed>
