Message from discussion
#newtwitter and the API
Received: by 10.216.93.77 with SMTP id k55mr461889wef.7.1285260933848;
Thu, 23 Sep 2010 09:55:33 -0700 (PDT)
X-BeenThere: twitter-development-talk@googlegroups.com
Received: by 10.216.237.165 with SMTP id y37ls540669weq.1.p; Thu, 23 Sep 2010
09:55:16 -0700 (PDT)
Received: by 10.216.150.223 with SMTP id z73mr108201wej.0.1285260916762;
Thu, 23 Sep 2010 09:55:16 -0700 (PDT)
Received: by 10.216.150.223 with SMTP id z73mr108200wej.0.1285260916732;
Thu, 23 Sep 2010 09:55:16 -0700 (PDT)
Return-Path: <dam...@gmail.com>
Received: from mail-wy0-f175.google.com (mail-wy0-f175.google.com [74.125.82.175])
by gmr-mx.google.com with ESMTP id s70si348289weq.5.2010.09.23.09.55.15;
Thu, 23 Sep 2010 09:55:15 -0700 (PDT)
Received-SPF: pass (google.com: domain of dam...@gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dam...@gmail.com designates 74.125.82.175 as permitted sender) smtp.mail=dam...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by wyg36 with SMTP id 36so21278wyg.34
for <twitter-development-talk@googlegroups.com>; Thu, 23 Sep 2010 09:55:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:sender:received
:in-reply-to:references:date:x-google-sender-auth:message-id:subject
:from:to:content-type;
bh=K9yH4EbWaUbCDe645yg8v6fLSTY3BhwuZPOak550wic=;
b=iA62++Y2GZGEIw/74z4x+qsz8eH7lDb/YK8mRUcRdMNoU7+Y51SDKhMr2p08aueSL3
iH/GWRY+/FTGzrfop+Fp5VWuutSPYv5JFiBRQbalAZxjYm4e7qpnZLdX+jjrPZKVUxsg
TntAQDxacJq+iaQrQaeo9YZTBghsOrgpXlYX8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:content-type;
b=HBVkD7FLhBiXEOMN1up88YQGw3m64XtaoyJYiXhgMmWWHjAJo+bsrvgyf9ikHeMFzf
hazYfna9c1C39PYGxVdklFS9NaSQN/EM3wCviBEMD3AdfgZZ1ZRo9l5i4ijLh8sNYBwB
59KtwMS6Er6yXC0hD1bedeCI+vX0dTtXiXbQo=
MIME-Version: 1.0
Received: by 10.216.49.212 with SMTP id x62mr1741975web.55.1285260915477; Thu,
23 Sep 2010 09:55:15 -0700 (PDT)
Sender: dam...@gmail.com
Received: by 10.216.186.18 with HTTP; Thu, 23 Sep 2010 09:55:15 -0700 (PDT)
In-Reply-To: <AANLkTi=gLdcFpV0mADDq5nDcTziwz=R8LOk=iYN_R...@mail.gmail.com>
References: <AANLkTi=gLdcFpV0mADDq5nDcTziwz=R8LOk=iYN_R...@mail.gmail.com>
Date: Thu, 23 Sep 2010 11:55:15 -0500
Message-ID: <AANLkTi=Uv+cf9GB0wz_y=+oYj_4CUH6jyAYKy2+97...@mail.gmail.com>
Subject: Re: [twitter-dev] #newtwitter and the API
From: Damon Clinkscales <sca...@pobox.com>
To: twitter-development-talk@googlegroups.com
Content-Type: text/plain; charset=UTF-8
Brian,
Thanks for the info.
> retweet_count
> The status object now includes a retweet_count field. When enabled
> this field will indicate the number of times a Tweet has been
> retweeted using the Twitter retweet function.
What does "when enabled" mean?
I have a couple of tweets for which I am trying to find out the
absolute count of retweets. All I know is that the Twitter UI says
"100+ retweets".
But when I pull the status objects, <retweet_count> is blank. These
tweets are from 2 days ago.
Can someone point me to the best way to find out?
Thanks!
/damon