How long should this fix take to propagate around, Taylor? I still see
a user with just an id property and nothing else when I call users/
show.
Matt
On May 6, 11:14 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
The bug is fixed. The cache, however, has to negotiate its way through
Seems like the cache has still not cleared.
Regards,
Rohit
On May 6, 6:14 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
The bug is fixed. The cache, however, has to negotiate its way through the
dusty corridors of memory.
Please let us know if you don't see a significant
It's taking a long time. We're investigating possible means to hasten the
resolution and any other reasons the cache might not be resolving.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Thu, May 6, 2010 at 3:17 AM, rohit mrro...@gmail.com wrote:
Seems like the
Just as a follow-up, I've just seen a userid/user again while
doing a verify_credentials.json call after I've retweeted some user.
The userid/user entry is inside the status entry of the calling
user's user entry. Oh, complex. It's like:
user
status
retweeted_status.../retweeted_status
I'm still seeing the errant userid/user node at noon EST.
On May 6, 10:03 am, janole s...@mobileways.de wrote:
Just as a follow-up, I've just seen a userid/user again while
doing a verify_credentials.json call after I've retweeted some user.
The userid/user entry is inside the status entry of
Also still seeing this as at 6th May 11:23pm GMT.
Over time I've learned it is a best practice to check the integrity of
a returned Twitter object despite the fact that the HTTP response code
is 200.
The bug is fixed. The cache, however, has to negotiate its way through the
dusty corridors of memory.
Please let us know if you don't see a significant improvement in regards to
the impact this had on your applications within a reasonable amount of
time.
Sorry about the mess.
Taylor
On Wed,
