Re: [twitter-dev] Unexpected search results from search.twitter.com and API

2010-05-14 Thread Damon Clinkscales
Naveen,

I saw a case with one of my searches this morning where a bit.ly url
appeared to have been expanded before Twitter Search matched on the
tweet.  Tim Haines said this morning on Twitter he had seen something
similar.

So, for the first tweet:

$ curl -I "http://bit.ly/cMsa7U";
HTTP/1.1 301 Moved
Server: nginx/0.7.42
Date: Fri, 14 May 2010 20:32:14 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: _bit=4bedb34e-00080-050e7-b4a08fa8;domain=.bit.ly;expires=Wed
Nov 10 15:32:14 2010;path=/; HttpOnly
Location: 
http://feedproxy.google.com/~r/TheBoyGeniusReport/~3/95JeYV6zcMk/?utm_source=SocialScope&utm_medium=SocialScope&utm_campaign=SocialScope&utm_term=SocialScope&utm_content=SocialScope
MIME-Version: 1.0
Content-Length: 443

The expanded bit.ly link contains 'SocialScope'.

-damon
-- 
http://twitter.com/damon
http://blog.damonc.com


On Fri, May 14, 2010 at 3:14 PM, Naveen Ayyagari
 wrote:
> Hello,
>    I have seen this a few times in the last couple of days and did
> not see it mentioned on the list. If it is a duplicate report I
> apologize.
>
> A simple search is on a keyword, the first result does not contain the
> keyword at all, here is a screen shot displaying the behavior on
> search.twitter.com website.
>
> http://dl.dropbox.com/u/27113/search_wierdness.jpg
>
> I have seen this strange behavior via the api as well and it is a bit
> confusing.
>
> --Naveen Ayyagari
> SocialScope
> @knight9


[twitter-dev] Unexpected search results from search.twitter.com and API

2010-05-14 Thread Naveen Ayyagari
Hello,
I have seen this a few times in the last couple of days and did
not see it mentioned on the list. If it is a duplicate report I
apologize.

A simple search is on a keyword, the first result does not contain the
keyword at all, here is a screen shot displaying the behavior on
search.twitter.com website.

http://dl.dropbox.com/u/27113/search_wierdness.jpg

I have seen this strange behavior via the api as well and it is a bit
confusing.

--Naveen Ayyagari
SocialScope
@knight9