Hi Doug,

I'm getting reports of this "from:user" delay happening again, so here
are some relevant request/response headers and screengrabs of the
results.

There are some cases where it can be out of sync for up to 8-10 minutes.

This is for the search query "from:resourcefulmom"



Request Headers
----------------

Host: search.twitter.com
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:1.9.0.17) Gecko/2009122115 Firefox/3.0.17
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://search.twitter.com/
Cookie: __utma=43838368.580929392773971800.1239516392.1262479801.1267595157.514;
__utmz=43838368.1267595157.514.159.utmcsr=push.ly|utmccn=(referral)|utmcmd=referral|utmcct=/home;
__utmv=43838368.lang%3A%20en;
__utma=110314503.2301945900846264600.1239516535.1262063897.1269652388.170;
__utmz=110314503.1258388229.140.5.utmcsr=twitter.com|utmccn=(referral)|utmcmd=referral|utmcct=/;
rpp=100; __qca=1239588110-79825009-53773698; lang=all;
_twitter_sess=BAh7DToMY3NyZl9pZCIlZDY4ZTY2YjI5ZDRkODgxOGM2ZWZlMWUxM2Y2MDA5%250AYzQ6DnJldHVybl90byJeaHR0cDovL3R3aXR0ZXIuY29tL29hdXRoL2F1dGhv%250Acml6ZT9vYXV0aF90b2tlbj1CbTB6c1YwZGgxTGdRWXNIcGJjNG94bnV0SnRN%250AdzJXRG1nMUVXclR4ekU6E3Bhc3N3b3JkX3Rva2VuIi00OWU2MGRhMDdhZDBk%250AZWNlNzJjNGUwNjlkNjJhYmYyN2E5NmFhYzc4Ogl1c2VyaQNUOWUiCmZsYXNo%250ASUM6J0FjdGlvbkNvbnRyb2xsZXI6OkZsYXNoOjpGbGFzaEhhc2h7AAY6CkB1%250Ac2VkewA6B2lkIiU3YTlmZjBlY2EzNTc2MTczMGZlNTFmMjYxZTJiZWJmZDoP%250AY3JlYXRlZF9hdGwrCH0QjyInAToRdHJhbnNfcHJvbXB0MA%253D%253D--265270e77f05570f78d081813c118b21eee077b9;
__utmc=43838368; __utmb=110314503.1.10.1269652388; __utmc=110314503


Response Headers
----------------

Date: Sat, 27 Mar 2010 01:13:06 GMT
Server: hi
Status: 200 OK
X-Served-From: b022
X-Runtime: 2.41047
Content-Type: text/html; charset=utf-8
X-Served-By: c070.twitter.com
X-Timeline-Cache-Hit: Miss
Cache-Control: max-age=15, must-revalidate, max-age=300
Expires: Sat, 27 Mar 2010 01:18:03 GMT
Content-Encoding: gzip
Content-Length: 16677
Vary: Accept-Encoding
X-Varnish: 3015348245
Age: 0
Via: 1.1 varnish
X-Cache-Svr: c070.twitter.com
X-Cache: MISS
Set-Cookie: rpp=100; path=/; expires=Sun, 27 Mar 2011 01:13:03 GMT
lang=all; path=/; expires=Sun, 27 Mar 2011 01:13:03 GMT
Connection: close


Screengrab of Twitter Search results:
http://grab.by/3ln7


Screengrab of Twitter profile page:
http://grab.by/3ln8



Please let me know if you need more info to help debug.

Thanks,
-Chad


On Mon, Mar 15, 2010 at 2:55 PM, twitterdoug <dc...@twitter.com> wrote:
> Hi Chad,
>
> I didn't get there in time, the results looked fine to me. Should you
> be able to reproduce this, could you please send more information?
> dumps of results would be most useful, with complete HTTP requests/
> responses...
>
> best,
>
> doug
>
> On Mar 12, 6:22 pm, Chad Etzel <jazzyc...@gmail.com> wrote:
>> Hi dev team,
>>
>> I've gotten progressively more complaints from TweetGrid users about
>> searches in the form of "from:username" not updating in a timely
>> fashion. I haven't changed my code in a while, so after investigating
>> it appears that the search index does lag behind a bit for "from:"
>> searches as compared to just keywords.
>>
>> Is this a bug, or intentional?
>>
>> Example (if you read this in time):http://twitter.com/resourcefulmom
>> compared tohttp://search.twitter.com/search?q=from:resourcefulmom
>>
>> Thanks,
>> -Chad
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Reply via email to