I can confirm that this happens whether the lookup is by screen_name or id.
Incidentally, any progress on Twitter's side? Way over a month now, and it
only seems to be getting worse.
Cheers,
Adrian
On Tue, Mar 22, 2011 at 1:18 AM, Nischal Shetty
nischalshett...@gmail.comwrote:
Anything on
Anything on this? It's been quite some time and user lookup I believe would
be used by a lot of apps.
-N
On 16 March 2011 05:46, Taylor Singletary taylorsinglet...@twitter.comwrote:
Still working on it, unfortunately. No ETA for a fix yet. I know it's an
aggravating bug for anyone who runs
Hi Taylor,
Not trying to be pushy or anything, but have you guys uncovered anything
related to this issue? It's still happening quite regularly for a couple of
weeks now.
Thanks,
Adrian
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter:
Still working on it, unfortunately. No ETA for a fix yet. I know it's an
aggravating bug for anyone who runs into it. Thanks for being patient.
Taylor
On Mar 15, 2011, at 5:09 PM, Adrian Petrescu apetr...@gmail.com wrote:
Hi Taylor,
Not trying to be pushy or anything, but have you guys
When using users/lookup with 100 random screen_names, I often get duplicate
records, as well as missing records for valid users that are not deleted,
suspended, or non-existent. Ive tested this with python-twitter as well as
twurl. The responses I receive are non-deterministic; different users are
Hi Kurt,
Thanks for the great detailed bug report. We're investigating this issue.
Taylor
@episod http://twitter.com/episod - Taylor Singletary - Twitter Developer
Advocate
On Tue, Mar 1, 2011 at 10:36 AM, Kurt Thomas kurt.a.tho...@gmail.comwrote:
When using users/lookup with 100 random