The assumption is that client services will, in any case, have to
parse and route statuses to potentially multiple end-users. Providing
this sort of hint wouldn't eliminate the need to parse the status and
would likely result in duplicate effort. We're aware that we are, in
some use cases, externalizing development effort, but the uses cases
for the Streaming API are so many, that it's hard to define exactly
how much this feature would help and therefore how much we're
Services, Twitter Inc.
On Nov 3, 1:53 am, Fabien Penso <fabienpe...@gmail.com> wrote:
> Would it be possible to include the matched keywords in another field
> within the result from the streaming/keyword API?
> It would prevent matching those myself when matching for multiple
> internal users, to spread the tweets to the legitimate users, which
> can be time consuming and tough to do on lots of users/keywords.