The issue is marked as WontFix, but comment 71 mentions the existence of a
closed beta. Any info on this?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
If you are going to deprecate this method, can you at least return a
user not found error as opposed to returning user twitter.com/show?
I have received numerous complaints that users we lookup are being
assigned to user show and their TonsOfWeed.com website -- which
for obvious reasons is not
Seconding this.
On Apr 3, 4:51 am, Todd Sampson toddsampson2...@gmail.com wrote:
If you are going to deprecate this method, can you at least return a
user not found error as opposed to returning user twitter.com/show?
I have received numerous complaints that users we lookup are being
Welcome the users/show returns data when no user is specified issue to
the crew [1].
1. http://code.google.com/p/twitter-api/issues/detail?id=416
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Fri, Apr 3, 2009 at 6:50 AM, Tim Rosenblatt trose...@gmail.com wrote:
Seconding
Thank you for the clarity and for putting greater detail on the
deprecation of user/show (find by email). I completely agree to
Twitter wanting to protect its user's privacy. I'd like to think that
the value created by whitelisted applications is far greater than the
pain being caused by
