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
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.
