<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Oodle Blog &#187; Open</title>
	<atom:link href="http://blog.oodle.com/category/open/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.oodle.com</link>
	<description>News &#38; Views from Oodle - A Whole New Way To Shop Classifieds</description>
	<lastBuildDate>Fri, 20 Nov 2009 01:37:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Local Twitter</title>
		<link>http://blog.oodle.com/2009/11/19/local-twitter/</link>
		<comments>http://blog.oodle.com/2009/11/19/local-twitter/#comments</comments>
		<pubDate>Fri, 20 Nov 2009 01:37:06 +0000</pubDate>
		<dc:creator>Craig Donato</dc:creator>
				<category><![CDATA[Open]]></category>
		<category><![CDATA[Social Networking]]></category>

		<guid isPermaLink="false">http://blog.oodle.com/?p=595</guid>
		<description><![CDATA[Today Twitter updated its API to enable applications like Oodle to geo-code tweets.    Now, when someone posts a local listing through Oodle we can help them share it on Twitter and automatically note where the listing is located.  This local context is key for enabling the discovery of local content (like classifieds listings) on [...]]]></description>
			<content:encoded><![CDATA[<p>Today Twitter <a href="http://apiwiki.twitter.com/Twitter-REST-API-Method:-statuses%C2%A0update">updated its API</a> to enable applications like Oodle to geo-code tweets.    Now, when someone posts a local listing through Oodle we can help them share it on Twitter <em>and</em> automatically note where the listing is located.  This local context is key for enabling the discovery of local content (like classifieds listings) on Twitter.</p>
<p>For example,  I may use Oodle to sell my car.  When I do,  Oodle will automatically tweet my listing.   Prior to today, this helped me generate word-of-mouth referrals from my network (someone that follows me may want my car or know someone that does).  Now, anyone searching Twitter for a Prius for sale near Burlingame can easily find my tweet (and my listing).</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.oodle.com/2009/11/19/local-twitter/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Oodle’s Real-time Stream of Classifieds Listings</title>
		<link>http://blog.oodle.com/2009/06/17/real-time-classifieds/</link>
		<comments>http://blog.oodle.com/2009/06/17/real-time-classifieds/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 20:50:31 +0000</pubDate>
		<dc:creator>Craig Donato</dc:creator>
				<category><![CDATA[Classifieds]]></category>
		<category><![CDATA[Oodle]]></category>
		<category><![CDATA[Open]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://blog.oodle.com/?p=428</guid>
		<description><![CDATA[

From a platform perspective, Oodle has a lot in common with Twitter…
1. We index a real-time a stream of perishable, unique &#8220;tweets&#8221; (800-900k new messages a day) in the form of classifieds listings. Actually, we do more than just index these listings.  Our real-time infrastructure tags, enhances and prunes the messages flowing through our system.  [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--><!--[if !mso]><span class="mceItemObject"   classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></span><br />
<mce:style><!  st1\:*{behavior:url(#ieooui) } --></p>
<p><!--[endif]--></p>
<p>From a platform perspective, Oodle has a lot in common with Twitter…</p>
<p><strong>1. We index a real-time a stream of perishable, unique &#8220;tweets&#8221; (800-900k new messages a day) in the form of classifieds listings.</strong> Actually, we do more than just index these listings.  Our real-time infrastructure tags, enhances and prunes the messages flowing through our system.  For example, if someone posts a listing a for “2006 Prius,” we determine that it&#8217;s a car listing (hybrid subcompact), year=2006, manufacturer=Toyota, make=Prius and enhance the listing with all the standard features, including a stock photo if one was not submitted.  (In other words, we auto-apply hash tags.)  Moreover, if someone posts a listing that is fraudulent or inappropriate, we have a range of proprietary technologies that automatically detect, flag and remove the message.</p>
<p><strong>2. Users search and browse our stream. </strong> Due to the volume and structured nature of our stream, we enable users to quickly slice and dice the stream both through keyword search and by selecting attributes (or tags).   Moreover, we&#8217;ve applied our parsing technology to search, so if someone searches for a 2006 Mercedes, we convert the query into year=2006, manufacturer=Mercedes Benz to deliver the most relevant results.</p>
<p><strong>3. Users post &#8220;tweets&#8221; (classified listings) into our stream.  And the post is a quick and simple process. </strong> Recently, as part of the work we did with Facebook Marketplace, we streamlined our post process to make it as lightweight as possible.  It’s not quite 140 characters but we’re getting close. More importantly, <a href=" http://blog.oodle.com/2009/06/02/people-want-to-see-all-the-listings/">we bring the user’s identity into the listing</a>.  So rather than a stream of anonymous content, listings are tied to the identity of the poster (on Oodle, Facebook, MySpace, etc.).  Someone can also see the previous listings posted by that user.</p>
<p><strong>4. Users follow relevant topics in the stream.</strong> When you’re looking for a car, you want to see all the listings that are currently posted, as well as new listings as soon as they get introduced into the stream.   With a single click on Oodle, users can easily follow any search (e.g., Acura TLs for under $10k within 60 miles of Burlingame, CA).</p>
<p><strong>5. Users share and discuss &#8220;tweets.&#8221; </strong> It’s easy to share an Oodle listing with your friends on MySpace, Facebook and Twitter.  You may see a listing you think a friend would be interested in &#8212; or want feedback from a friend (should I buy this car?).   Having said that, <a href="http://blog.oodle.com/2009/06/04/sparking-conversations-around-listings/">we’re really only just getting started in this area</a>.  There are a lot of interesting features coming soon…</p>
<p>It&#8217;s exciting to see users become more comfortable with metaphors around streaming, subscribing and sharing.  It not only enables us to better represent the cool stuff we&#8217;ve built over the last few years, it serves as a wonderful launch pad for where we&#8217;re going with &#8220;social classifieds.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.oodle.com/2009/06/17/real-time-classifieds/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Jeremy Zawodny leaving Yahoo! for Craigslist</title>
		<link>http://blog.oodle.com/2008/06/20/jeremy-zawodny-leaving-yahoo-for-craigslist/</link>
		<comments>http://blog.oodle.com/2008/06/20/jeremy-zawodny-leaving-yahoo-for-craigslist/#comments</comments>
		<pubDate>Fri, 20 Jun 2008 19:15:40 +0000</pubDate>
		<dc:creator>Matt Dearborn</dc:creator>
				<category><![CDATA[Classifieds]]></category>
		<category><![CDATA[Open]]></category>

		<guid isPermaLink="false">http://blog.oodle.com/2008/06/20/jeremy-zawodny-leaving-yahoo-for-craigslist/</guid>
		<description><![CDATA[We recently heard that Jeremy Zawodny is leaving Yahoo! for Craigslist. We&#8217;re hoping that with Jeremy’s influence, Craigslist decides to become more open. Historically, the company has not only blocked search engines (like Oodle), but has also tightly restricted user activity. It will be interesting to see if Craigslist’s stance on openness changes in the [...]]]></description>
			<content:encoded><![CDATA[<p>We recently heard that <a href="http://www.searchenginejournal.com/zawodny-landing-at-craigslist-opening-up-an-open-market/7166/">Jeremy Zawodny is leaving Yahoo! for Craigslist</a>. We&#8217;re hoping that with Jeremy’s influence, Craigslist decides to become more open. Historically, the company has not only blocked search engines (like Oodle), but has also tightly restricted user activity. It will be interesting to see if Craigslist’s stance on openness changes in the next few months.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.oodle.com/2008/06/20/jeremy-zawodny-leaving-yahoo-for-craigslist/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
