Have you considered embedding some explanation field for each trend
the way Brizzly does it, or would you rather let such clients handle
this? I imagine the real problem for Twitter would be curating trend
explanations.
On Nov 9, 4:13 pm, Raffi Krikorian ra...@twitter.com wrote:
We've heard
Yes. I imagine Twitter would rather not be forced to do the legwork on
offering explanations for trends.
On Nov 10, 7:34 am, Raffi Krikorian ra...@twitter.com wrote:
by trend explanations, do you meanhttp://whatthetrend.com/?
Have you considered embedding some explanation field for each
The latest announcement mentions include_rts for /1/statuses/
user_timeline and /1/statuses/friends_timeline but not for /1/statuses/
home_timeline. Am I alone in desiring include_rts for /1/statuses/
home_timeline as well? I find the current method of blocking retweets
per user to be somewhat
method.
Best,
@themattharris
On Fri, Sep 24, 2010 at 7:39 AM, @giromide girom...@gmail.com wrote:
The latest announcement mentions include_rts for /1/statuses/
user_timeline and /1/statuses/friends_timeline but not for /1/statuses/
home_timeline. Am I alone in desiring include_rts for /1
I put a star on this thread. Will this count as a favorite?
On Dec 6, 2:17 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
Quoting John Kalucki j...@twitter.com:
As previously announced, XML has been disabled on the Streaming API. The few
remaining consumers should move to
