Oh, never mind.  I've answered my own question.  It looks like yFrog only 
supports XML for the 
https://api.twitter.com/1/account/verify_credentials.xml

In other words, they don't accept 
https://api.twitter.com/1/account/verify_credentials.json
At least that's my understanding from their docs.  Someone correct me if I'm 
wrong here.

So, I've dropped 'em for now from Kiwi.

Just too much pain all around.  For those interested I've had really good luck 
with TwitPic, TwitrPix, and TwitGoo -- all seem to support echo well.  I've 
implemented support using both my own OBJ-C and on the iPhone using Aral's 
X-Auth libs on GitHub.

isaiah
http://twitter.com/isaiah

On Jul 26, 2010, at 4:49 PM, Isaiah Carew wrote:

> 
> Did you ever get to the bottom of this?  I've been getting this same response 
> from yFrog -- but all of the other oAuth Echo supporting services seem to be 
> working just fine.
> 
> isaiah
> http://twitter.com/isaiah
> 
> On Jul 20, 2010, at 4:21 PM, DWF wrote:
> 
>> Anyone else seeing this?
>> 
>> We're implementing OAuth Echo for uploading photos. We've knocked down
>> Posterous & TwitPic with few issues.  So we know our signing is
>> working.
>> 
>> We now have an ImageShack API key and when we attempt to upload we get
>> this response:
>> 
>> <?xml version="1.0" encoding="UTF-8"?>
>> <rsp stat="fail">
>> <err code="1001" msg=" Invalid username or verification URL specified"/
>>> 
>> </rsp>
>> 
>> There's one comment on their Google Group with someone else getting
>> this suddenly after having successful code for a while.
>> 
>> Thoughts?
>> --dwf
> 

Reply via email to