<?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/"
		>
<channel>
	<title>Comments on: A Manifesto for Mobile and Location Based Social Networks</title>
	<atom:link href="http://technosailor.com/2008/06/04/a-manifesto-for-mobile-and-location-based-social-networks/feed/" rel="self" type="application/rss+xml" />
	<link>http://technosailor.com/2008/06/04/a-manifesto-for-mobile-and-location-based-social-networks/</link>
	<description>Business and Technology with Common Sense</description>
	<lastBuildDate>Thu, 24 May 2012 21:21:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-beta4-20883</generator>
	<item>
		<title>By: Aaron Brazell</title>
		<link>http://technosailor.com/2008/06/04/a-manifesto-for-mobile-and-location-based-social-networks/comment-page-1/#comment-44158</link>
		<dc:creator>Aaron Brazell</dc:creator>
		<pubDate>Wed, 04 Jun 2008 19:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://technosailor.com/?p=2992#comment-44158</guid>
		<description>Martin- would be happy to update the post when Brightkite releases the RESTful API. Also happy to mangle data when it comes around. Thanks for stopping by.</description>
		<content:encoded><![CDATA[<p>Martin- would be happy to update the post when Brightkite releases the RESTful API. Also happy to mangle data when it comes around. Thanks for stopping by.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin May</title>
		<link>http://technosailor.com/2008/06/04/a-manifesto-for-mobile-and-location-based-social-networks/comment-page-1/#comment-44157</link>
		<dc:creator>Martin May</dc:creator>
		<pubDate>Wed, 04 Jun 2008 19:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://technosailor.com/?p=2992#comment-44157</guid>
		<description>Hey Aaron,

Great write-up. A couple of clarifications regarding Brightkite:

Phone Support - Brightkite actually works on pretty much any US phone that supports text messaging, and we provide the same functionality via mobile e-mail. We also have (as you mention) a generic WAP version of our site, and an iPhone-specific site. I&#039;d argue that we have most bases covered when it comes to phone support.

GPS compatible - Brightkite already understands latitude/longitude information, and we&#039;ll have native clients for phones coming out within the next month.

Location Data easy for Users to Use - we provide GeoRSS and KML feeds for all of the activity within Brightkite, making it really easy to share location data, and users have built widgets and other visualizations around it:

http://blog.brightkite.com/2008/06/02/new-blog-widgets-plugins/
http://blog.brightkite.com/2008/05/30/brightkite-widgets-are-no-longer-a-pipe-dream/
http://blog.brightkite.com/2008/05/27/brightkite-kml-support-and-google-earth-visualizations/

We also have a REST-based API coming. I would argue that we deserve a &quot;Yes&quot; in that category. ;)

Low Impact Monetization - As you know, we have very concrete plans for monetization that will be very low-impact on the user, and goes beyond the obvious &quot;location-based ads&quot; model.

Overall, I have to agree with the white paper...those are critical areas for location-based social networks to get right, and rest assured that we&#039;re working on making it happen.

Martin
brightkite.com</description>
		<content:encoded><![CDATA[<p>Hey Aaron,</p>
<p>Great write-up. A couple of clarifications regarding Brightkite:</p>
<p>Phone Support &#8211; Brightkite actually works on pretty much any US phone that supports text messaging, and we provide the same functionality via mobile e-mail. We also have (as you mention) a generic WAP version of our site, and an iPhone-specific site. I&#8217;d argue that we have most bases covered when it comes to phone support.</p>
<p>GPS compatible &#8211; Brightkite already understands latitude/longitude information, and we&#8217;ll have native clients for phones coming out within the next month.</p>
<p>Location Data easy for Users to Use &#8211; we provide GeoRSS and KML feeds for all of the activity within Brightkite, making it really easy to share location data, and users have built widgets and other visualizations around it:</p>
<p><a href="http://blog.brightkite.com/2008/06/02/new-blog-widgets-plugins/" >http://blog.brightkite.com/2008/06/02/new-blog-widgets-plugins/</a><br />
<a href="http://blog.brightkite.com/2008/05/30/brightkite-widgets-are-no-longer-a-pipe-dream/" >http://blog.brightkite.com/2008/05/30/brightkite-widgets-are-no-longer-a-pipe-dream/</a><br />
<a href="http://blog.brightkite.com/2008/05/27/brightkite-kml-support-and-google-earth-visualizations/" >http://blog.brightkite.com/2008/05/27/brightkite-kml-support-and-google-earth-visualizations/</a></p>
<p>We also have a REST-based API coming. I would argue that we deserve a &#8220;Yes&#8221; in that category. ;)</p>
<p>Low Impact Monetization &#8211; As you know, we have very concrete plans for monetization that will be very low-impact on the user, and goes beyond the obvious &#8220;location-based ads&#8221; model.</p>
<p>Overall, I have to agree with the white paper&#8230;those are critical areas for location-based social networks to get right, and rest assured that we&#8217;re working on making it happen.</p>
<p>Martin<br />
brightkite.com</p>
]]></content:encoded>
	</item>
</channel>
</rss>

