+1 On Fri, Apr 8, 2011 at 4:31 AM, maxf3r <massimo.ferr...@gmail.com> wrote:
> I agree with you. > > For sure a large part of data "inside" the tweet object is redundant > for any apps want to "parse only" tweet data to achieve more derivate > information > > For example, to be clear and to open some sort of discussion: > > tweet info (id; created_at; text; entities) > coordinates & place (if any, I really hope so) > minimal user info (screen_name; profile_url;... ) > > massimo > > > On Apr 8, 1:12 am, Mamadou Bobo Diallo <dia...@gurumades.com> wrote: > > Actualy, we need access to the Site Streaming api to be able to start > > building our start-up product, we've been waiting for week now. I > > understand that the beta is about to improve the system and make sure > > it is able to scale when it goes live. > > > > One way to make the system scale better would be to allow some special > > streaming access: for example, for our product, we don't need all > > details of a tweet: having only some basic information on the tweet is > > enough, no need to have the information of the author attached. > > Allowing us to connect to the Streaming API with this minimalistic way > > will make less data (data that we don't need) goes througth the > > systeme and increase throughtput by 40%. > > > > I'm sure that there is many app out there that don't need all those > > informations. > > -- > 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
