Re: [twitter-dev] Status format stream API vs. REST API

2010-09-09 Thread Taylor Singletary
Entities will be back soon -- temporary glitch. Thanks, Taylor On Thu, Sep 9, 2010 at 10:07 AM, yaemog Dodigo wrote: > 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

Re: [twitter-dev] Status format stream API vs. REST API

2010-09-09 Thread yaemog Dodigo
> > 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

Re: [twitter-dev] Status format stream API vs. REST API

2010-09-08 Thread Taylor Singletary
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 sup

[twitter-dev] Status format stream API vs. REST API

2010-09-08 Thread yaemog Dodigo
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_mention