Realistically, this is slipping to V2.

What does this refer to exactly?

If you're intending on removing JSON callback capability for all methods which
require authentication, then I would *strongly* vote against that. 

That will single-handedly kill every pure-Javascript Twitter client out there. There
aren't many, but I am working on one and I would be very disappointed if this happened.

I agree 100% with shazow, being in the same case. I am working on a JS-based client
and that would be VERY bad news for me.

This issue has been recoreded in the future roadmap:
http://apiwiki.twitter.com/V2-Roadmap

(No comment was entered for this change.)

Marking "Invalid" so these issues don't clutter the main view of issues. All are tracked on http://apiwiki.twitter.com/V2-Roadmap

can you please elaborate per shazow's comment. if this is indeed for all 
authenticated calls it is a big issue for us as well.

thanks,
udi

Note: I needed to log into Google to post a comment here, 
but login couldn't complete because of "Unsupported URL scheme".
But I took a chance and backtracked to here and refreshed this page
and discovered I was in fact logged in just fine. Anyway:
What I wanted to say in this topic is that IMO any call-back
should be public-key encrypted so that only the intended (authorized)
viewer is able to see it. But is JavaScript even capabble of the
big-integer arithmetic needed for public-key cryptosystem??