Hey Jovan,

1) "include_entities" controls Tweet Entities output (in the status object).
For some User accounts, we're also testing & outputting User Entities (for
the description attribute). The "include_entities" parameter doesn't affect
the output of these User Entities.

2) The Status object included in users/show is the user's last tweet. Now if
you really need to get a user's last tweet (caching issues can happen) use
the "statuses/user_timeline" method.

3) We're working on this one, thanks for reporting.

Arnaud / @rno <http://twitter.com/rno>



On Wed, Apr 20, 2011 at 2:14 AM, jovandoj <jovan...@yahoo.com> wrote:

> Hi everybody,
>
> I started developing a twitter application and I bumped into 3 issues:
> 1. When I send a request like the following:
>
> http://api.twitter.com/1/users/show.json?screen_name=someScreenName&include_entities=false
> ,if one of hashtags, usermentions or urls are not empty in the most
> recent status message, I get the "entities" JSON object although I
> specifically say "include_entities=false"
> Is this a bug, or am I doing something wrong?
> 2. How long lasts the "...most recent status..." (http://
> dev.twitter.com/doc/get/users/show) ?
> 3. Sometimes twitter sends back "states" when doing a users/show.
> Where can I read about this property (nothing available on docs)?
> In this "states" JSON object we get:
> bouncing_email
> detached_email
> needs_employee_email_update
> suspended
> pending_email
>
> Cheers,
> Jovan
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to