What does "following" in user information do?

[Hwee-Boon Yar]

So if I do, http://twitter.com/users/show/XXX.xml

What does the value of following (true/false) mean? I tried
authenticating as someone that both follows and is followed by XXX and
yet the value of following is still false.

Docs say: boolean indicating if a user is following a given user

Any thoughts?

--
Hwee-Boon

[Pleasant Software]

Same problem here. I guess it's a bug.

Eberhard

On Mar 20, 9:40 am, Hwee-Boon Yar <hweeb...@gmail.com> wrote:
> So if I do,http://twitter.com/users/show/XXX.xml

[Doug Williams]

Looking at the issues, this is known [1], [2]. Add a star to show it's a priority:

1. http://code.google.com/p/twitter-api/issues/detail?id=157
2. http://code.google.com/p/twitter-api/issues/detail?id=99

Doug Williams
Twitter API Support
http://twitter.com/dougw

[Hwee-Boon Yar]

I'm seeing it in XML though. The bugs are for JSON format.

--
Hwee-Boon

On Mar 21, 12:06 am, Doug Williams <d...@twitter.com> wrote:
> Looking at the issues, this is known [1], [2]. Add a star to show it's a
> priority:
>
> 1.http://code.google.com/p/twitter-api/issues/detail?id=157

> 2.http://code.google.com/p/twitter-api/issues/detail?id=99
>
> Doug Williams
> Twitter API Supporthttp://twitter.com/dougw

[krwhite]

I can report that it's definitely broken in XML. The XML output I see
shows a random following result, which suggests to me that the entire
result set is a cache from something else.

If I may suggest a fix to twitter, how about an extra parameter for
'show_the_right_results' as a boolean? The command would only be slow
and uncached for those who would rather have the correct following
information. In the future the parameter can just be ignored when
it's faster with proper caching. This command is only sent when the
user wants extended user information, so it's probably issued the
least out of all of them I have implemented. I would assume that's a
similar case for other clients.

It would be pretty rough on the server as well to use the brute force
method of getting ALL followers before displaying follow/unfollow, so
I don't see many options right now aside from having multiple,
confusing buttons.

[Matt Sanford]

Hi there,

This is a known issue [1] that I have been working on for some
time. I have a fix ready to be deployed next week so hopefully this
will start working correctly. Every API user wants and deserves the
correct data and the cache should work correctly to keep load off the
databases and still return you the correct results. The fix for this
bug is a long time coming because we wanted to be sure it would fix
the issue, perform well, and be resistant to breaking again in the
future. Sorry for the long delay.

Thanks;
— Matt Sanford

[1] - http://code.google.com/p/twitter-api/issues/detail?id=157

[Arnaud]

Hi Matt,

And thank you for the update.
Unfortunately, it still doesn't seem to be fixed.
I still receive a lot of incorrect "following" values (INT and NULL
instead of BOOL) using the "statuses/followers" method.

All the best,
Arnaud.

On Mar 27, 5:18 pm, Matt Sanford <m...@twitter.com> wrote:
> Hi there,
>
>      This is a known issue [1] that I have been working on for some  
> time. I have a fix ready to be deployed next week so hopefully this  
> will start working correctly. Every API user wants and deserves the  
> correct data and the cache should work correctly to keep load off the  
> databases and still return you the correct results. The fix for this  
> bug is a long time coming because we wanted to be sure it would fix  
> the issue, perform well, and be resistant to breaking again in the  
> future. Sorry for the long delay.
>
> Thanks;
>    — Matt Sanford
>

> [1] -http://code.google.com/p/twitter-api/issues/detail?id=157

>
> On Mar 26, 2009, at 05:15 PM, krwhite wrote:
>
>
>
> > I can report that it's definitely broken in XML.  The XML output I see

> > shows a randomfollowingresult, which suggests to me that the entire

[Dossy Shiobara]

On 4/19/09 11:34 AM, Arnaud wrote:
> And thank you for the update.
> Unfortunately, it still doesn't seem to be fixed.
> I still receive a lot of incorrect "following" values (INT and NULL
> instead of BOOL) using the "statuses/followers" method.

+1 ... users/show method returning empty <following/> node instead of
boolean true/false.

Can Matt re-open issue #157, or should we create a new issue to track this?

--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)

[Carlos]

Still not working from the results I'm seeing. Has this issue been re-
opened?

On Apr 19, 9:07 pm, Dossy Shiobara <do...@panoptic.com> wrote:
> On 4/19/09 11:34 AM, Arnaud wrote:
>
> > And thank you for the update.
> > Unfortunately, it still doesn't seem to be fixed.

> > I still receive a lot of incorrect "following"values(INT and NULL

[Doug Williams]

Please star Issue 419 [1]  so you will be notified when the fix is shipped.

1. http://code.google.com/p/twitter-api/issues/detail?id=419

Doug Williams
Twitter API Support
http://twitter.com/dougw

[Carlos]

Can't star it, do I need some kind of access to do so?

On Apr 23, 11:19 pm, Doug Williams <d...@twitter.com> wrote:
> Please star Issue 419 [1]  so you will be notified when the fix is shipped.
>

> 1.http://code.google.com/p/twitter-api/issues/detail?id=419
>
> Doug Williams
> Twitter API Supporthttp://twitter.com/dougw

[Cameron Kaiser]

> Can't star it, do I need some kind of access to do so?

Yes, you need to be signed in with a Google account.

--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * cka...@floodgap.com
-- The only abnormality is the inability to love. -- Anais Nin ----------------