I have noticed a change with regards to the trends resource.

for reference please check the following URLs

1) http://api.twitter.com/1/trends/current.json
2) http://api.twitter.com/1/trends/current.json?callback=foo
3) http://search.twitter.com/trends.json?callback=foo

Currently, for me api.twitter.com trends/current.json is returning the
same pure JSON payload regardless of the callback parameter.  This is
new behavior that has changed since I last used this resource.

What I would expect, and is not the case, is that URL #2 with the
callback parameter specified would return JSON wrapped in a function
call, similar to how URL #3 behaves.

Has anyone else noticed this?  I have confirmed it myself with more
than one location.

Is this on purpose?  Was a bug rolled out to production in a release?
Am I missing the obvious. Please help.

Thank you very much.

Reply via email to