<?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>Beta Labs - AT&#38;T Interactive &#187; ip address</title>
	<atom:link href="http://betalabs.attinteractive.com/tag/ip-address/feed/" rel="self" type="application/rss+xml" />
	<link>http://betalabs.attinteractive.com</link>
	<description></description>
	<lastBuildDate>Tue, 09 Mar 2010 18:50:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Where You At? (Predict Location)</title>
		<link>http://betalabs.attinteractive.com/2008/11/17/where-you-at-part-i/</link>
		<comments>http://betalabs.attinteractive.com/2008/11/17/where-you-at-part-i/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 18:42:11 +0000</pubDate>
		<dc:creator>Coby Randquist</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[ip address]]></category>
		<category><![CDATA[predictive locality]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[where]]></category>

		<guid isPermaLink="false">http://ypcblog.wc1.yellowpages.com/?p=14</guid>
		<description><![CDATA[When users visit yellowpages.com, we present them with a search form that asks them to tell us not just what they&#8217;re looking for, but where they want us to search for it.
However, not all search queries arrive at our servers in such neat and tidy packages. In some cases, queries arrive as an undifferentiated jumble [...]]]></description>
			<content:encoded><![CDATA[<p>When users visit <a href="http://www.yellowpages.com/">yellowpages.com</a>, we present them with a search form that asks them to tell us not just <em>what</em> they&#8217;re looking for, but <em>where</em> they want us to search for it.</p>
<p>However, not all search queries arrive at our servers in such neat and tidy packages. In some cases, queries arrive as an undifferentiated jumble of terms that <em>may</em> contain both types of information. If we&#8217;re lucky, we can <a href="http://betalabs.yellowpages.com/2008/11/17/single-search-box/">identify and use</a> any geographical information embedded in the text. Other times, the queries simply don&#8217;t contain geographic information that we can extract—they&#8217;re all <em>what</em> but no <em>where</em>.</p>
<p>In those cases, all we&#8217;ve got to go on is the IP address of the user&#8217;s computer—which isn&#8217;t great, but it&#8217;s certainly better than nothing! So we have deployed a new feature that takes the users&#8217;s IP address, then looks it up in a database of known IP addresses to find the real-world location associated with that address. It&#8217;s not foolproof, and it&#8217;s not exhaustive, but in many cases it does a fairly good job of identifying a user&#8217;s location.</p>
<p>If you&#8217;re curious, you can try this out now—go ahead, see if we can <a href="http://webbeta.yellowpages.com/predictive_locality/">guess where you&#8217;re sitting</a>. (And let us know how we did in the comments!)</p>
]]></content:encoded>
			<wfw:commentRss>http://betalabs.attinteractive.com/2008/11/17/where-you-at-part-i/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>
