Generally, it would be really interesting to know a user on a webpage has a twitter account. Clearly, you should patch security holes, but a tiny piece of javascript to tell the front end whether the user just has a twitter account would be great.
We have a tiny alert on the top of http://tipjoy.com that tells people about our twitter payments. Let's just say the font would be a lot bigger if we knew they had a twitter account. We might even redirect them to another page. This is one failing of Facebook Connect actually. Real estate in widgets like ours is limited ( http://tipjoy.com/banners ), which means adding a connect button is costly unless we know they have a Facebook account. They could do it, but they haven't made this functionality AFAIK. Ivan http://tipjoy.com On Jan 12, 6:59 pm, Matt Sanford <[email protected]> wrote: > Here are the changes launched today, 2009-01-12: > > Fixed: some methods were defaulting to JSON when no format was > specified. A format must be specified for all API calls. > > Security: it was possible to discover the currently logged-in user via > an unauthenticated call to the /statuses/user_timeline method. This is > a potential privacy concern, and was disabled. > > Fixed: Atom feeds for timelines incorrectly reported all user profile > pictures as image/png. This may take up to a day to propagate through > all of our caches. > > Fixed: Requests with &id= and no value returned a user rather than an > error. Now an error is returned. > > As always you can review changes by checking the change log > athttp://apiwiki.twitter.com/REST+API+Changelog. > > Thanks; > — Matt Sanford / @mzsanford
