Thanks for the feedback Brian. Late response here, but I'd be more
than willing to provide you with more details regarding our
application in a private email. You should be receiving said email
shortly.
Regards,
Corey
On Apr 14, 1:12 pm, Brian Sutorius wrote:
> While the Streaming API may not p
While the Streaming API may not provide processed results to you in
the way that search queries can (logical ORs, etc.), it's a more
scalable solution for returning a lot of Tweets. Our search system can
rate limit queries if they become too computationally expensive (in
addition to the normal quer
On Apr 13, 10:28 am, Corey Ballou wrote:
> I'm still looking for a community leader answer on this one.
>
> On Apr 11, 5:50 pm, Corey Ballou wrote:
>
>
>
> > Thanks for the reply, I appreciate it.
>
> > I have concerns regarding the streaming APIs, which mainly concern the
> > following:
>
> >
I'm still looking for a community leader answer on this one.
On Apr 11, 5:50 pm, Corey Ballou wrote:
> Thanks for the reply, I appreciate it.
>
> I have concerns regarding the streaming APIs, which mainly concern the
> following:
>
> * usage of logical OR when using locations
> * firehose limitat
Thanks for the reply, I appreciate it.
I have concerns regarding the streaming APIs, which mainly concern the
following:
* usage of logical OR when using locations
* firehose limitations
* the user’s location field is not used to filter tweets
* increased application complexity for parsing the re
