Yes, this would be very cool. Any ideas on when this would be rolled out? 1) It would be nice to have the profile_image_url in it as well. I can imagine a lot of nice visual enhancements with that.
2) +1 for making it optional. A lot of people are suggesting additional stuff, so maybe it would even be nicer to not just have a include/don't include param, but to be able to specify which data you would like to have included... jarón On May 14, 6:29 am, Rich <rhyl...@gmail.com> wrote: > +1 for it being optional as well. Whilst I will probably use it, it's > nice to be able to keep the bandwidth download to a minimum for > scenarios where it's not needed > > On May 14, 1:52 am, Naveen Ayyagari <nav...@getsocialscope.com> wrote: > > > +1 on the additional parameter to optionally request the data. Every > > byte counts for mobile device battery life and download time. > > > --Naveen Ayyagari > > @knight9 > > > On May 13, 8:13 pm, Dewald Pretorius <dpr...@gmail.com> wrote: > > > > Raffi, > > > > This is all good, but can you please make the inclusion in the tweet > > > payload optional? Meaning, only include it if it is requested by an > > > additional parameter? > > > > I, and I'm sure a lot of others, are already parsing the tweet text. > > > This is just going to consume additional bandwidth and not add any > > > value for us. It will add value for folks who are not already doing > > > the parsing or don't know how. So, they can just request this > > > additional payload.