> 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 * ckai...@floodgap.com
-- The only abnormality
Can't star it, do I need some kind of access to do so?
On Apr 23, 11:19 pm, Doug Williams 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
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
On Thu, Apr 23, 2009 at 8:11 PM, Carlos wrote:
>
> Still not working from the results I'm seeing.
Still not working from the results I'm seeing. Has this issue been re-
opened?
On Apr 19, 9:07 pm, Dossy Shiobara 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 "followin
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 node instead
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 wrote:
> Hi there,
>
>
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
datab
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 c
I'm seeing it in XML though. The bugs are for JSON format.
--
Hwee-Boon
On Mar 21, 12:06 am, Doug Williams 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/t
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
On Fri, Mar 20, 2009 at 11:54 AM
Same problem here. I guess it's a bug.
Eberhard
On Mar 20, 9:40 am, Hwee-Boon Yar wrote:
> 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
11 matches
Mail list logo
