Re: [twitter-dev] Re: Retweet API methods returning 404

2009-12-17 Thread Michael D. Ivey

I say I say I say, it was a joke, son. - Foghorn Leghorn

Sent from my iPhone

On Dec 17, 2009, at 6:07 PM, Dimebrain daniel.cre...@gmail.com wrote:


Interesting, how do you approach API testing if not live? Wouldn't
mind comparing notes.

On Dec 17, 7:07 am, Andrew Badera and...@badera.us wrote:

Personally, my unit's testes don't call the Twitter API ...

Seeing the same 404s on retweet calls however.

∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me:http://www.google.com/search?q=andrew%20badera

On Thu, Dec 17, 2009 at 7:05 AM, Dimebrain  
daniel.cre...@gmail.com wrote:
The following retweet methods have started returning 404's in our  
unit

testes:



http://api.twitter.com/1/statuses/retweeted_by_me.json
http://api.twitter.com/1/statuses/retweeted_to_me.json
http://api.twitter.com/1/statuses/retweets_of_me.json
http://api.twitter.com/1/statuses/retweets/[any_status_id].json



Anyone else having this issue, or know what happened to these API
methods?


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael D. Ivey


Not just you. Every machine I've tried times out, but  
istwitterdown.com says No and Seesmic Web works. Seems to be  
connectivity issue.


Sent from my iPhone

On Oct 18, 2009, at 8:40 AM, Dewald Pretorius dpr...@gmail.com wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?

Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael D. Ivey


Yes. Unable to connect via Tweetie from home (one of my traceroutes  
was from home) and lots of reports from iPhone, ATT and Comcast users  
in Southeast.


Sent from my iPhone

On Oct 18, 2009, at 9:56 AM, John Kalucki jkalu...@gmail.com wrote:



And here's the next question:

Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.


On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote:

OK. I think we have enough traceroutes for now. Thanks for sending
them in!

If we need more datapoints or information, I'll update this thread.

On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:


I don't see any operational issues from here, but I'm not an
operational guy. At first glance the system looks fine, and the
operational team isn't in response mode. This is puzzling.



Seems like a connectivity issue upstream from twitter. At lest a few
developers: please send a traceroute to this list. Also, if you  
aren't

timing out, but rather are getting an HTTP error, send the response
headers. After say 4 or 5 responses, they'll probably have enough  
info

to triage this.



-John Kaluckihttp://twitter.com/jkalucki
Services, Twitter Inc.



On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?



Dewald