[twitter-dev] Re: Twitter lists fails
Thanks guys. Really appreciate it. On Apr 12, 2:02 pm, Mark McBride wrote: > Correct. We've actually identified the issue, are working on a fix and will > deploy as soon as possible. Unfortunately that probably means early next > week. > > ---Mark > > http://twitter.com/mccv > > > > On Mon, Apr 12, 2010 at 2:00 PM, Raffi Krikorian wrote: > > I believe we confirmed this - we're looking into it. > > > On Apr 12, 2010, at 3:49 PM, Spraycode wrote: > > > We are seeing the same issue with list cursors not working and have > >> also reported it and heard nothing back. Very frustrating since we've > >> done a lot of work to properly support lists in our App. Would love > >> it if someone at Twitter could give us an idea of when this might be > >> fixed? > > >> On Apr 12, 8:49 am, fdelpozo wrote: > > >>> Sorry my english, this is an automatic Google Translate: > > >>> For at least 2 weeks and stopped working the lists of Twitter. El > >>> fallo está a la hora de ver la lista de listas (valga la > >>> redundancia). The ruling is the time to see the list of lists > >>> (forgive the redundancy). > > >>> Fail both the API and the Twitter interface. > >>> Twitter lists are recovered through lists 20 pages each, at the end of > >>> each page, Twitter returns a cursor that will be used to request the > >>> next and so on until you run out (cursor = 0).Twitter Now only return > >>> the 1st page, nothing more, but it does randomly, sometimes returns a > >>> page more. > > >>> If you are over 20 lists you can check yourself on Twitter.com, shows > >>> you there is no page 20 for more. > > >>> We have reported to support the API for days but has not yet been > >>> solved. If anyone knows anything about this and want to share is > >>> appreciated. > > > -- > > To unsubscribe, reply using "remove me" as the subject.
[twitter-dev] Re: Twitter lists fails
We are seeing the same issue with list cursors not working and have also reported it and heard nothing back. Very frustrating since we've done a lot of work to properly support lists in our App. Would love it if someone at Twitter could give us an idea of when this might be fixed? On Apr 12, 8:49 am, fdelpozo wrote: > Sorry my english, this is an automatic Google Translate: > > For at least 2 weeks and stopped working the lists of Twitter. El > fallo está a la hora de ver la lista de listas (valga la > redundancia). The ruling is the time to see the list of lists > (forgive the redundancy). > > Fail both the API and the Twitter interface. > Twitter lists are recovered through lists 20 pages each, at the end of > each page, Twitter returns a cursor that will be used to request the > next and so on until you run out (cursor = 0).Twitter Now only return > the 1st page, nothing more, but it does randomly, sometimes returns a > page more. > > If you are over 20 lists you can check yourself on Twitter.com, shows > you there is no page 20 for more. > > We have reported to support the API for days but has not yet been > solved. If anyone knows anything about this and want to share is > appreciated.
[twitter-dev] Re: Mad about lists and cursors... please help
Has anyone been able to solve this issue? This is still crippling us. Thanks! On Apr 2, 5:25 am, luisfigo wrote: > Having the same problem... > > Triedhttp://api.twitter.com/1/avinashkaushik/lists/memberships.xml > and get 0 for cursor. This guy is followed by ton of lists in fact > > Below is the snapshot of the end result I got... This is screwing up > our app right now... > > . > http://a1.twimg.com/profile_background_images/79104366/twitter_backgr... > > false > false > false > false > false > 3208 > en > false > > > > 0 > 0 > > > On Apr 1, 6:00 pm, Diego Rin Martin wrote: > > > I think it's a API bug, even in the twitter page the paginator doesn't work > > as expected, sometimes > > appears, sometines not, and when appears it makes in a random manner. > > > i'm getting cursor 0 from API, using int or string representation, the bug > > is in the API that sends > > the cursor 0 randomly. > > > regards, diego. > > > On Thu, Apr 1, 2010 at 2:38 AM, jmathai wrote: > > > Are you sure you're using the string representation of the cursor > > > instead of the int? The API's cursor exceeds PHP's max integer value > > > (generally). > > > > jmathai ~ $ php -r '$x = > > > json_decode(1); > > > echo $x; echo "\n"; > > > var_dump($x===1); > > > var_dump($x===1.111E+52);' > > > 1.111E+52 > > > bool(false) > > > bool(true) > > > > jmathai ~ $ php -r '$x = > > > 1; echo $x; echo > > > "\n"; > > > var_dump($x===1); > > > var_dump($x===1.111E+52);' > > > 1.111E+52 > > > bool(true) > > > bool(false) > > > > On Mar 31, 2:03 am, Diego Rin Martín wrote: > > > > Hi there, > > > > > this is my first post to this group, i'm a spanish developer dealing > > > > with twitter api surprises, excuse my poor english, i'will do my best > > > > to comunicate nicest. > > > > > So, to the problem, I'm trying to retrieve the lists for a user, via > > > > list/memberships get method, and passing cursor as parameter, I'm > > > > having got random results, I explain myself, sometimes I made a > > > > request (for user edans, that have a huge amount of pages to paginate) > > > > and I get one page, I pass cursor -1 and I get cursor 0, sometimes I > > > > get one page, I pass cursor -1 i get cursor 1331431515904087602, then > > > > I pass it and I get 0, sometimes I get a random number of pages, but > > > > never, never, be able to retrieve the total amount of pages. > > > > > I use php twitter-async classes to comunicate with API, I thought that > > > > it could be the cause of the problem, but using direct curl (via php5- > > > > curl extension) calls I'm having the same issues. > > > > > Same using json or xml. > > > > > I'm always getting 200 responses, so the call finish in a correct way. > > > > > any clue? > > > > > I'm turning mad. > > > > > Thanks in advance. > > > > diego. > > > > -- > > > To unsubscribe, reply using "remove me" as the subject.
Getting rate limit on status update posts. Thought these were excluded?
Hi, my understanding from the discussion here (http:// groups.google.com/group/twitter-development-talk/browse_thread/thread/ bf65a7160a8a44c9?hl=en, third and fourth item in the thread) was that status update requests would not be limited by the 20,000 requests per hour rule. Today we are getting this error: XML Error: http://twitter.com/statuses/show/1158263569.xml HTTP Status: 400 /statuses/show/1158263569.xml Rate limit exceeded. Clients may not make more than 2 requests per hour. Is this a bug in the API or is this limit now in place? Appreciate any feedback anyone can provide. Thanks!
