> > You can obtain entities from most API methods that return tweets by > appending an ?include_entities=true parameter to the request. Eventually, > entities should be part of the default response. > > You can read more about entities here: > http://dev.twitter.com/pages/tweet_entities > > Methods that should support this query parameter generally indicate > compatibility on the documentation page corresponding to the resource. > > Including entities on the REST API can sometimes increase total processing > time, so if you're asking for a large amount of data, you might want to > lower the total count you ask for at a time so that your request doesn't > time out. > > Thanks, > Taylor > > On Wed, Sep 8, 2010 at 3:17 PM, yaemog Dodigo <yae...@gmail.com> wrote: > >> Hello, >> >> I'm wondering why the format of status messages that get delivered via the >> stream API differs from status elements that are retrieved via the REST API >> (e.g., public_timeline or user_timeline). >> More precisely, status elements from the stream API contain an 'entities' >> object with user_mentions, hashtags, and urls properties. This information >> is missing from status messages that are retrieved from the REST API. Are >> there plans to unify these formats? >> >> Hi,
as of this morning I don't see entities anymore in the spritzer stream ( http://stream.twitter.com/1/statuses/sample.json). Is this expected behavior? Appending include_entities=true does not help either. thx -- 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?hl=en
