I am using the search API,
-- getting 409 conflict, once in a while.
-- getting no json could be decoded sometimes, I guess thats coz of
the HTML in response error.
JV
On Aug 9, 10:34 pm, Ryan Sarver rsar...@twitter.com wrote:
I wanted to send an update to everyone who is monitoring this
On Aug 9, 2:34 pm, Ryan Sarver rsar...@twitter.com wrote:
I will continue to give ongoing updates
every 5-6 hours throughout the day even if nothing has changed so that you
know we are still focused on it.
Now THAT'S what we're talking about!
Thank you Ryan. It may not seem important to busy
When calling http://twitter.com/statuses/user_timeline.xml via OAuth
(no id passed, looking for information on the authenticated user), I
am seeing this response:
?xml version=1.0 encoding=UTF-8? statuses type=array /
statuses
Not sure if that's in the list of things being monitored, but there
1. OAuth rarely works - I tried a number of your apps and it seems
to work 1 out of 6-7 times. As a note, it worked better with Safari,
but not every time.
-Not applicable
2. 302 redirect
- not sure anymore since our code has been updated to follow them
automatically.
3.
Not to mention that http://search.twitter.com still appears to be completly
blocked from the app engine.
Paul
2009/8/9 Naveen Ayyagari knig...@gmail.com
1. OAuth rarely works - I tried a number of your apps and it seems to work
1 out of 6-7 times. As a note, it worked better with Safari,
Hi Ryan,
Some details from my perspective...
1. OAuth rarely works - I tried a number of your apps and it seems
to work 1
out of 6-7 times. As a note, it worked better with Safari, but not
every
time.
Sporadic all day today. At its worst I'd agree that about 1 in 7
succeeds, but it
Appreciate your updates Ryan, here are the issue we are still
experiencing at HootSuite
1. 302 redirect. We still have to follow redirects in order to
retrieve proper contents, but not a big deal
2. Rate Limiting. All of our server IPs (supposed to be whitelisted)
are bound with 150 limit
3.
Hi Ryan,
Many thanks for the update.
On twitscoop, we have issues with the search api, which apparently
returns erroneous or ill-formed timestamps.
eg. http://www.twitscoop.com/search?twitter you'll see the latest
tweet will be dated 14465 days ago :))
Cheers
On Aug 9, 7:34 pm, Ryan Sarver
I'm actually clean - no problems for the last 2 days. I do, however
have my app just following all re-directs. If it would help I can pull
the follow on 302 and let you know what happens.
Brian Roy
justSignal
On Aug 9, 10:42 am, Dewald Pretorius dpr...@gmail.com wrote:
On Aug 9, 2:34 pm, Ryan
Ryan,
Many thanks for the continued updates. You guys are handling this far
better than most would.
Regarding OAuth: I'm also having difficulty updating OAuth app
properties on the website -- the update form continues to return a
400 Bad Request when it's submitted.
Obviously not a huge
We are getting timeouts via appengine for search api calls for
LinksAlpha.com. All our data aggregation activities are ending up with
almost no data for the past 3 days.
Thanks
Vivek Puri
http://LinksAlpha.com
The 302 issue has not been made very clear:
1. does the redirect need to be re-signed?
2. is this only the token calls, or all calls to the API methods?
Also, I don't know if it's related or not, but paging on the blocks/
blocking method does not work. i.e. all page parameters return a full
1. I'm finding that OAuth breaks for periods, then works for periods
(not 1/6 requests, more like works 6 times, then breaks 6 times). When
it doesn't work in Safari, if I dump my twitter.com cookies it usually
works the next try.
5. Unexpected rate limiting / blacklisting
Mostly I'm noticing rate limiting.
- Ben
search.twitter.com is not working for me from either API or directly
in the browser. Is it working for others? If I am blacklisted, how
does one go about getting it fixed?
5. Unexpected rate limiting / blacklisting
Most annoyed issue for me. Rate is 150/hour for my whitelist ip now.
16 matches
Mail list logo
