Yes, our model does externalize some development and hosting costs onto
clients. But, we tend to only externalize cost when issues would be far
cheaper, in aggregate, to solve on the client, or would be intractable to
solve on our end and might otherwise prevent the launch of the feature. We
try
I understand. There's lots of sausage making going on behind the scenes. You
make it the best you can. Often for reasons that I cannot hope to understand.
;-)
Let me stop being metaphysical and boil this down to a simple bug report:
There is no documentation of how to get from the schema
In other words, if I want to disambiguate the stream, I have to filter it
myself. Well, humph…
Not impossible, just a pain in the butt.
From an information organization standpoint, it seems odd: The REST API is
broken out into separate calls. The stream has everything glommed together.
It
Roughly:
If the tweet is from a following, place it in the home timeline.
If the tweet refers to the user (to or from), or contains the @screenname
place it in mentions
If it's a message - messages.
What remains is probably a track term.
-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.
Hi,
I'm implementing user streams in my client and looking for some advice
on best practices. My client supports viewing multiple timelines at
the same time, so it's quite possible to, for example: view a saved
search, the user's own home timeline, and another user's recent
tweets.
Of course,
