I'm also always seeing next_cursor=0 both using twitter4j and curl.
On Apr 17, 7:26 am, Dan Checkoway wrote:
> When using the "GET list memberships" API
> (http://api.twitter.com/1/twitterapi/lists/memberships.*), it looks like
> paging is broken. If the user is a member of >20 lists, you can
It's 10 days later and next_cursor on
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-list-memberships
is still always 0, even when the user is being followed by far more
than 20 lists. This is completely broken and prevents 3rd party apps
from discovering all lists that follow a given u
t; Sent from mobile device
>
> On Apr 17, 2010, at 7:08 AM, Zach wrote:
>
> > It's 10 days later and next_cursor on
> >http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-list-member...
> > is still always 0, even when the user is being followed by far more
> &g
I'm going to 3rd Sebastian's POV. This is a serious problem that
needs to be addressed now. Mobile app developers want to integrate
their native apps with sites like Twitter and Facebook, but the
current user experience is so unacceptable that no one is going to use
it in its current form.
For
Use case:
User logs in via oauth/authenticate
User logs out via accounts/end_session. Cookies on my site containing
access tokens are cleared.
Same user logs back in later (in the same browser session) with
oauth_authenticate.
However, this last step produces a 403 forbidden: server understood
r
>
> On Aug 12, 2:53 pm, aschobel wrote:
>
>
>
> > We are having the same issue, getting a 403 forbidden.
>
> > I tried another OAuth enabled site and they have the same issue,
>
> >http://www.twitlonger.com/
>
> > Maybe there is some type of
expiration date. Our rate limit remaining was back at 149 out of 150
with an expiration at 1:35 AM as expected.
I was wondering if anyone has experienced something similar, or am I
just missing something entirely. I can provide the headers in full if
necessary..
Thanks,
-Zach
--
Twitter de
that our request was just lucky to be sent one second
before our reset, but I find the one second different a little too
close to ignore.
-Zach
On Jan 14, 9:32 am, Zach Gardner wrote:
> We've been having problems recently with going over our rate limit
> when making API calls. We do
there a better place I should be posting this? Like some sort of
bug tracking application rather than just a development talk?
-Zach
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http
