I don't think this is an option available within Streaming API but you
might create a short program that would start a request (e.g. cURL) at
the desired time/date start_date and you can manually stop it (or
also with a program) at end_date.
I'm just concerned about what you mean by track keyword
Turns out that urllib2's readline has a buffer which you can work
around by creating a custom readline that uses read(1)
Example:
def readline():
buffer = ''
while True
char = conn.read(1)
if '\n' == char:
return buffer
else:
buffer += char
Hope this helps out anyone
Hey Ray,
Thanks for sharing the solution for the problem you hit. Glad everything
worked out.
Best
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Thu, Jun 9, 2011 at 10:17 AM, Ray Slakinski ray.slakin...@gmail.comwrote:
Turns out
Hey guys, thanks for chiming in here to this thread. I've been
following two accounts, my own and a co-workers. Since starting the
stream and sending a number of tweets my connection has not seen any
of them. If I follow a large number of uses (including myself) I do
see my tweets come through. My
I should add the account I'm using to follow my account and my co-
workers is not the same one as either of these 2. Its completely
separate.
On Jun 6, 12:46 pm, Matt Harris mhar...@twitter.com wrote:
Hi Ray,
There isn't a buffer that has to be filled before the Streaming API delivers
Correct me if I'm mistaken, but I believe that access token/secret
pair are still *my* access token and secret for that application. That
is, they can be used to access my personal Twitter data. I'm
uncomfortable using my personal credentials (or those of any
individual user) for this purpose.
You're right. The simplest (only?) way would be to create an account
specifically for managing your app. I believe there was a recent post
on this list talking about that being the norm, but I couldn't find
it. I'd love for the app to have it's own credentials, and allow for
assigning multiple
A small update...
After letting it rest over night, I was able to get /statuses/filter.json to
work on my office machine using any set of keys, but attempting to run with
any keys on ec2 gets us a 420. Immediately after the 420 in ec2, I can run
without issue in the office. I've tried a few of
Thanks, Arnaud. Didn't think about the 'track' parameter. Will use it
now.
On Apr 21, 1:32 am, Arnaud Meunier arn...@twitter.com wrote:
With the follow parameter, you should only get real replies retweets.
If you need to track all mentions, try the track parameter (i.e.
track=@user)
So, it turns out that I was an order of magnitude off when I mentioned
numbers above. We receive 500,000 tweets/day not 50,000.
On Apr 1, 3:49 pm, Colin Surprenant colin.surpren...@gmail.com
wrote:
Well, first, In the Gnip Power Track
I'm getting very similar count to United States, my average is 499,380
tweets/day.
On Mon, Apr 4, 2011 at 3:08 PM, Khandelwal khandel...@gmail.com wrote:
So, it turns out that I was an order of magnitude off when I mentioned
numbers above. We receive 500,000 tweets/day not 50,000.
On Apr 1,
As a side note, currently only 3-4% of the total tweets (firehose) are
geo-tagged and are eligible to be selected in a stream location
bounding box. If the current firehose rate is about 140M tweets/day,
that makes ~5M eligible tweets/day.
I do not know what the proportion of tweets from the US
Sorry Colin, but where did you get this information? Doesn't match with the
reality. Not at all.
On Fri, Apr 1, 2011 at 12:35 PM, Colin Surprenant
colin.surpren...@gmail.com wrote:
As a side note, currently only 3-4% of the total tweets (firehose) are
geo-tagged and are eligible to be
All of my experiences with geotagging show that about 0.3% to 0.5% of
tweets have these codes. I'd be curious to know if that matches what
others have found.
On Fri, Apr 1, 2011 at 2:40 PM, Augusto Santos augu...@gemeos.org wrote:
Sorry Colin, but where did you get this information? Doesn't
Clearer Information:
From 10th Mar to 31th Mar the average was 1,1M/day and 860K/day of these
with lat/long information.
On Fri, Apr 1, 2011 at 4:03 PM, Augusto Santos augu...@gemeos.org wrote:
Since 6th March setting location via Broswer has been disable, which
correponded of around 50%
Well, first, In the Gnip Power Track documentation
http://docs.gnip.com/w/page/35663947/Power-Track at the has:geo
section they say Currently, 'has:geo' is about 2-4% of the full
firehose.
Also, I ran some tests a few weeks ago to see the difference in
content between the search api and the
Hello Matt.
Could you tell me (us) what the limit is on track parameter?
Thank you in advance.
Regards.
Alejandro.
On Feb 23, 6:52 pm, Matt Harris thematthar...@twitter.com wrote:
Hi J,
The authoritative information for the Streaming API is under the /pages/
path and you should use that for
Alejandro,
You can track up to 400 keywords/terms at the basic level, with each term up
to 60 bytes.
@episod http://twitter.com/episod - Taylor Singletary - Twitter Developer
Advocate
On Thu, Feb 24, 2011 at 5:46 AM, AA alejandro.ale...@gmail.com wrote:
Hello Matt.
Could you tell me (us)
Taylor:
Thanks for your answer!
Is it possible to be allowed to track more keyword/terms than 400?
How can I do it?
Thank you in advance.
Regards.
Alejandro.
2011/2/24 Taylor Singletary taylorsinglet...@twitter.com
Alejandro,
You can track up to 400 keywords/terms at the basic level, with
Thanks for the update John!
On 18 Feb., 19:08, John Kalucki j...@twitter.com wrote:
http://dev.twitter.com/pages/streaming_api_concepts#result-quality
Search filters for relevance and is not intended as a source of all tweets.
Streaming provides the complete record to all you to perform
http://dev.twitter.com/pages/streaming_api_concepts#result-quality
Search filters for relevance and is not intended as a source of all tweets.
Streaming provides the complete record to all you to perform whatever
post-processing you'd like.
-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.
sorry, once more again:
With 'only in async' I meant tweets which were only retrieved via the
streaming API but not via search API
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
Hi Matt,
sorry for being unspecific. By 'only in async' I meant tweets which
were only found by the streaming API ('asynchronous retrieval') but
were not in the search results **
Why are they missing when using search API?
Also can you give an example of what you mean by a long Tweet.
I
Same question here.
Eric
On Feb 17, 12:59 am, aci acicartag...@gmail.com wrote:
Hello,
I am using the streaming api in order to be able to save tweets that
uses the geoJSON place key of the returned json object. Tt was working
fine last Tuesday, Feb 15, But now, there seems to be a problem
Hi Eric and Aci,
Do you have some example tweets showing what you mean?
Thanks,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, Feb 16, 2011 at 11:22 PM, Eric Charles
eric.umg.char...@gmail.comwrote:
Same question here.
Eric
On Feb 17, 12:59 am, aci
We are reporting similar problem at this thread
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/8fbab48c3172b88d#
and got no answer from twitter dev team.
Need more information? I can give some if needed.
On Thu, Feb 17, 2011 at 3:31 PM, Matt Harris
Our support team confirms that Tweeting with locations is disabled at the
moment.
https://twitter.com/#!/Support/status/37747170618785793
When the service is restored @support will post an update.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Thu, Feb
Hi John,
Well, for a search term 'java' the async API is 'ok' and the
differences 'only in search' can be easily explained: the keywords are
in the URL.
But the differences 'only in async' (tweets grabbed only via streaming
API) are strange to me:
First your test set is a bit small. Did you take into account the
extra data you will get in your first search api poll? Typically your
first poll will return 100 items then subsequent polls will return
only new data if using since_id and/or dedupping.
Make sure both your poller and stream reader
Hi Colin, hi John,
To increase recall, search sometimes includes keywords in followed links and
other techniques.
This is indeed the case. and 'twitter search' is a lot in urls ala:
http://search.twitter.com/search?q=jetwick
that is where the big differences came from. Can I turn off this
On Tue, 15 Feb 2011 21:01:07 -0800, John Kalucki j...@twitter.com
wrote:
On every occasion where I've tested the Firehose and track terms from
the Streaming API against the Tweet database and against each other,
there is no loss -- all the sources match exactly. Unless there's
some
unusual
Yesterday's maintenance resulted in about of 5 seconds of latency on Tweets,
and about 10% of social events were delayed by about 10 minutes. No data was
lost.
We're going to perform another maintenance on social events now. You may
experience duplicate social events for several seconds up to
Thanks Mohan. That's definitely a better list then the I'm currently
using. I'll try that out and post some results later.
Cheers! -Kenny
On Feb 4, 7:15 pm, L. Mohan Arun mar...@gmail.com wrote:
Does anyone have experience using a list of stopwords to reduce noise
when making streaming API
Does anyone have experience using a list of stopwords to reduce noise
when making streaming API requests to statuses/filter? I have a basic
list (e.g. a,an, and, etc.) but wonder if anyone out there is
using something more comprehensive.
Thanks,
Kenny
Kenny,
Simply google
Many thanks!
On Dec 16, 12:18 pm, Augusto Santos augu...@gemeos.org wrote:
Yes you can.
On Thu, Dec 16, 2010 at 8:23 AM, epomqo wenzi0...@gmail.com wrote:
Hello everyone,
Just a simple question: can I launch multiple connections to Streaming
API using different accounts, but on the
Does that mean the application can use any active token that was
granted via the normal OAuth connections process to authenticate on
the Streaming API?
If that is so, then even just that information in the documentation
will be a help.
From reading the documentation one cannot figure out whether
Hi Dewald,
Agree that we could have more explicit documentation here.
- Yes you must use an access token.
- Streaming privileges and roles are given to accounts at this time, not API
keys.
- As such, the account represented by the access token determines what level
of access is available to the
So in my case i just encodeURIComponent somewhere? I tried on the POST
params and it did not work, nor did the 4 permutations of api-key/
secret and access-token-key/secret.
.
On Oct 25, 4:31 pm, Ciaran ciar...@gmail.com wrote:
Hey Bradley,
This is another instance of the the ongoing (and as
On Mon, Oct 25, 2010 at 10:53 PM, bradley.meck bradley.m...@gmail.com wrote:
So in my case i just encodeURIComponent somewhere? I tried on the POST
params and it did not work, nor did the 4 permutations of api-key/
secret and access-token-key/secret.
Odd, Escaping
Correct, I still had the issue when escaping track= Escaping
params individually did not work either. Still able to tweet though...
Maybe it is a hint at the trouble being more/different than double
encoding?
Cheers,
Bradley
On Oct 25, 4:59 pm, Ciaran ciar...@gmail.com wrote:
On Mon, Oct
Hey everyone,
So OAuth encoding can get confusing and lead to situations like this
so i'll go through a very verbose walkthrough to hopefully explain how
it all works.
The key section of the specification explaining this part is
3.4.1.3.2:
http://tools.ietf.org/html/rfc5849#section-3.4.1.3.2
On Mon, Oct 25, 2010 at 11:28 PM, themattharris
thematthar...@twitter.com wrote:
Hey everyone,
So OAuth encoding can get confusing and lead to situations like this
so i'll go through a very verbose walkthrough to hopefully explain how
it all works.
First, thank you for taking the time to
Hi, John
Does Twitter still plan to implement backfill support in streaming
API? In an older post from
Mark McBride (April, 2010), he said:
To alleviate some of the concerns raised in this
thread we thought it would be useful to give more details about how we
plan
to generate IDs ...
... 4) We
I dug back to Mark's email for context, but I still can't puzzle out
what Mark was referring to and what you are asking for. The answer
might be buried somewhere in that 74 message thread. Could you restate
your question?
Does the count parameter do what you need?
-John Kalucki
Hey Ginny,
Thanks for letting us know it was the ruby gem at fault - and for correcting it.
Best
Matt
On Sun, Sep 26, 2010 at 12:17 PM, Ginny Hendry ginnyhen...@gmail.com wrote:
FYI, we found the bug! Twitter API was fine, but yajl-ruby gem has an
error that causes it to skip tweets of some
For anyone else who is having this problem, the fix has been
identified but has not yet been published as a new gem version. What
happens is that it skips some tweets. The ones it skips are the ones
that happen to have a message length in hex that includes a zero
character so it will seem
Thanks for following up with this Ginny. Brian has just pushed version
0.7.8 of the gem, which fixes this.
Tim.
On Tue, Sep 28, 2010 at 5:16 AM, Ginny Hendry ginnyhen...@gmail.com wrote:
For anyone else who is having this problem, the fix has been
identified but has not yet been published
FYI, we found the bug! Twitter API was fine, but yajl-ruby gem has an
error that causes it to skip tweets of some lengths, which accounts
for the weird way it let some through and not others.
We're heading off to correct the Ruby gem now.
-Ginny
--
Twitter developer documentation and
John-
Thanks for confirming the way this should work. We'll work on the
client side code to see what it's doing with the stream data and how
it compares to the raw stream from curl.
-Ginny
On Sep 24, 12:01 pm, John Kalucki j...@twitter.com wrote:
Accounts should work all of the time,
Am I the only one who has found retweeted_status to be very
unreliable?
I have a constant streaming API connection, and the majority of tweets
that
are retweets (and are displayed as such on the web), have empty
retweeted_status values.
Example:
http://twitter.com/Mobieleeenheid - The retweet
for example:
trackwords: {starwars,obama}
authorization with username,password: working
using oauth :working
trackwords: {star wars,obama}
authorization with user name,password: working
using oauth i get 401 error
Thanks,
Karthik
--
Twitter developer documentation and resources:
On 8/31/10 8:01 AM, Karthik K wrote:
for example:
trackwords: {starwars,obama}
authorization with username,password: working
using oauth :working
trackwords: {star wars,obama}
authorization with user name,password: working
using oauth i get 401 error
Thanks,
Karthik
Sounds like
On Aug 12, 11:46 am, Matt Harris thematthar...@twitter.com wrote:
The streaming API allows you to follow user IDs and track keywords but not
lists directly. Instead you need to follow all the user IDs of the list and
then assemble their Tweets on your server to recreate the list.
The limit for
On 8/12/10 9:33 PM, Decklin Foster wrote:
On Aug 12, 11:46 am, Matt Harris thematthar...@twitter.com wrote:
The streaming API allows you to follow user IDs and track keywords but not
lists directly. Instead you need to follow all the user IDs of the list and
then assemble their Tweets on your
You can't re-use signatures. Signatures use a nonce which is unique, a
timestamp that will invalidate the request after about 5 minutes, and
a signature that is based on the request you do (including URL).
Tom
On Aug 9, 4:22 am, ianrose ianros...@gmail.com wrote:
Hi -
I hope I am not posting
Thank everyone for the quick reply, I have implemented a downloading
program which uses curl, and it is fast enough to avoid the time
drift.
-Larry
On Jul 8, 5:00 pm, Pascal Jürgens
lists.pascal.juerg...@googlemail.com wrote:
Larry,
moreover, I assume you checked I/O and CPU load. But even if
This likely wasn't due to adding the source parameter. It was more
likely but due to a bug I had in the streaming OAuth implementation.
Java's URLEncoder converts spaes to '+' instead of '%20'. This got
fixed yesterday.
---Mark
http://twitter.com/mccv
On Mon, Jun 28, 2010 at 5:08 PM,
Wil: Can you retrieve the signature base string (again, from your current
work) from your library when attempting the call that returns 401? There
must be something minor going amiss there with this parameter for some
reason.
Thanks,
Taylor
On Sat, Jun 26, 2010 at 12:08 PM, John Kalucki
Hi Taylor,
Ok. Here's the entire thing:
Generated base string:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
%3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce
%3Dmvzi5szav5dciif4%26oauth_signature_method%3DHMAC-
Ah wait, I ran a couple more tests just to be sure and the signatures
match the sent sniffed one guess I missed something previously...
Base:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a couple more tests just to be sure and the signatures
match the sent sniffed one guess I missed something previously...
Base:
Great! Let me know if you still need assistance.
Taylor
On Mon, Jun 28, 2010 at 8:10 AM, Wil willi...@gmail.com wrote:
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a couple more tests
Oh wait, it does include them I just missed it.
So much for premature celebration...
On Jun 28, 11:10 pm, Wil willi...@gmail.com wrote:
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a
Let's start from a common point. By using the same inputs, we can try and
meet in the middle with exactly the same signature, signature base string,
and authorization header.
Using the following values:
Consumer Key: TwitterConsumerKey
Consumer Secret: TwitterConsumerSecret
Access Token:
Hi,
I got exactly the same values:
Base string:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
%3DTwitterConsumerKey%26oauth_nonce%3Dabcdefgh%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1277739588%26oauth_token
Hi again,
I made a real request this time because in the previous one, I
couldn't control the nonce and timestamp generation directly so I copy-
pasted the code it used and modified it a bit. This is the real
generated data which has a non-mock nonce and timestamp.
Timestamp: 1277742686
Nonce:
Hi Wil,
Did some more tests. Why are you passing source in this context? I don't
recall this being an operator for the Streaming API. If you're passing it as
some kind of analogue to a source parameter you'd pass in basic auth on
tweet creation, it's unnecessary here unless there's some other use
Hi Taylor,
Finally! It now works. TweetSharp includes the source parameter by
default on all requests (I think). Thus, I overrode the
TwitterClientInfo just for that request and cleared out the
ClientName field. Now it works!
I guess on your side, the code filters out unknown parameters before
Wil,
Fantastic. So glad you got it working, and thanks for sharing the solution
which worked for you.
Matt
On Mon, Jun 28, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:
Hi Taylor,
Finally! It now works. TweetSharp includes the source parameter by
default on all requests (I think). Thus,
Hi,
@John: I removed the delimited=1 parameter and it still gave me 401's.
@Taylor: I checked my system clock and does not differ from the server
time by more than 5 minutes.
The code works with the following which I've used:
1) OAuth authentication methods
2) statuses/user_timeline
3)
Just a short follow-up:
I tried the streaming API again with OAuth and statuses/sample
(instead of statuses/filter) and it works...
however the statuses/filter still doesn't work (I get 401) even if I
access the stream using the same account.
Thanks,
Wil
On Jun 26, 5:50 am, Taylor Singletary
An invalid delimited parameter is ignored, and won't cause a 401.
On Sat, Jun 26, 2010 at 2:04 AM, Wil willi...@gmail.com wrote:
Hi,
@John: I removed the delimited=1 parameter and it still gave me 401's.
@Taylor: I checked my system clock and does not differ from the server
time by more
Hi,
Sorry it took me a while since I'm using TweetSharp and am stepping
through the (unfamiliar) code.
The moment you said about the signature, I'm suspecting that the
problem is somewhere with that. However, I got this:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
Hi John,
Uhh, care to elaborate? I don't quite get what you meant...
Thanks,
Wil
On Jun 24, 11:17 pm, John Kalucki j...@twitter.com wrote:
Aside from the oAuth issue, which others can address, the only valid
delimited value is length.
-John
On Thu, Jun 24, 2010 at 7:58 AM, Wil
Wil,
Does your OAuth code work against other aspects of the Twitter API? Can you
verify if your system's clock is within 5 minutes or so of the times
returned by our system? (You can see the current server time in an HTTP
header of any of our responses).
Are you sure that your code is actually
I'm getting this response:
HTTP/1.1 401 Unauthorized
Content-Length: 1296
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html; charset=iso-8859-1
Server: Jetty(6.1.17)
WWW-Authenticate: Basic realm=Firehose
html
head
meta http-equiv=Content-Type content=text/html;
Aside from the oAuth issue, which others can address, the only valid
delimited value is length.
-John
On Thu, Jun 24, 2010 at 7:58 AM, Wil willi...@gmail.com wrote:
I'm getting this response:
HTTP/1.1 401 Unauthorized
Content-Length: 1296
Cache-Control: must-revalidate,no-cache,no-store
Hi Wil,
I can help you with the OAuth component of this. Can you share your
signature base string for the request?
Here's an example of a few of the steps of a functioning OAuth request
against this endpoint:
POST body
source=softwarenamedelimited=1follow=156934710
Signature Base String
I'm a bit dumbfounded here...
I've been trying to login to stream.twitter.com using OAuth
(particularly, I've been trying to access
http://stream.twitter.com/1/statuses/filter.json?follow=). I used
the access keys obtained from https://api.twitter.com/oauth/access_token
however, I've been
OAuth should work fine on stream.twitter.com
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Tue, Jun 22, 2010 at 10:00 AM, Wil willi...@gmail.com wrote:
I'm a bit dumbfounded here...
I've been trying to login to stream.twitter.com using OAuth
(particularly, I've
Hi,
Is there an ETA for enabling oauth on stream.twitter.com?
Thanks,
Aaron
On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote:
OAuthis not enabled on stream.twitter.com. You can try on
chirpstream.twitter.com.
On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com
OAuth is now enabled on stream.twitter.com. I'll also send a note out
to the announce list
---Mark
http://twitter.com/mccv
On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin aran...@gmail.com wrote:
Hi,
Is there an ETA for enabling oauth on stream.twitter.com?
Thanks,
Aaron
On May
Does this mean that the streaming API will also make the switch from
basic authentication to OAuth at the end of June?
On Mon, May 24, 2010 at 4:50 PM, Mark McBride mmcbr...@twitter.com wrote:
OAuth is now enabled on stream.twitter.com. I'll also send a note out
to the announce list
We haven't announced our plans for streaming and oAuth, beyond stating that
User Streams will only be on oAuth.
On Mon, May 24, 2010 at 1:57 PM, 140dev 140...@gmail.com wrote:
Does this mean that the streaming API will also make the switch from
basic authentication to OAuth at the end of
Hey we need documentation!
Jonathon
On May 24, 4:50 pm, Mark McBride mmcbr...@twitter.com wrote:
OAuth is now enabled on stream.twitter.com. I'll also send a note out
to the announce list
---Mark
http://twitter.com/mccv
On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin
The format is fairly simple and almost self explanatory.
Check out this for a working sample:
http://github.com/zbowling/earlybird
Zac Bowling
On Mon, May 24, 2010 at 7:23 PM, Jonathon Hill jhill9...@gmail.com wrote:
Hey we need documentation!
Jonathon
On May 24, 4:50 pm, Mark McBride
I am writing my own c++ based OAuth library. I know there is liboauth
but I like to do things myself to learn.
Anyhow I am trying to access http://stream.twitter.com/1/statuses/sample.xml
and I keep getting 401.
I have verified pretty much every parameter, and used the tool on
OAuth is not enabled on stream.twitter.com. You can try on
chirpstream.twitter.com.
On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com wrote:
I am writing my own c++ based OAuth library. I know there is liboauth
but I like to do things myself to learn.
Anyhow I am trying
Excellent, it works!
thanks
On Thu, May 13, 2010 at 2:11 PM, John Kalucki j...@twitter.com wrote:
OAuth is not enabled on stream.twitter.com. You can try on
chirpstream.twitter.com.
On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com
wrote:
I am writing my own c++
It works! Now I know how to put multiple parameters. Thanks very much!
Best,
epomqo
On Apr 24, 4:39 pm, John Kalucki j...@twitter.com wrote:
The curl man page explains how to send multiple parameters. If you
just put them in one file, curl runs then all together. You have to
separate them
Thanks Taylor for the very detailed and helpful response!
Jonathon
On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Jonathon,
For Streaming API access that isn't from the perspective of a user's
account, you would use two-legged OAuth to establish authentication
On Apr 19, 8:37 pm, John Kalucki j...@twitter.com wrote:
The Streaming API is currently configured to send a keep-alive newline
every 30 seconds. If you don't receive any data or the keep-alive in
perhaps 60 or 90 seconds, you should drop and reconnect. The only case
where what you observed
The existing EULA has its confusing parts and is at the end of its life. The
Commercial License is much better conceived and is aligned with where
Twitter is going, and is not based on where we were 12+ months ago when the
EULA first was released.
On Sun, Apr 11, 2010 at 6:16 PM, M. Edward (Ed)
Yes, we just experienced the same issue today... twice too...
@sphilipakis
http://www.twazzup.com
On Apr 1, 3:46 pm, Chad Etzel jazzyc...@gmail.com wrote:
Hi all,
I am using the filter stream, and twice in the last 24 hour period the
stream has run dry... the connection remains open but no
Are newlines (the ones that come every 30 seconds) still coming through, or
no data at all?
---Mark
http://twitter.com/mccv
On Thu, Apr 1, 2010 at 4:36 PM, stephane stephane.philipa...@gmail.comwrote:
Yes, we just experienced the same issue today... twice too...
@sphilipakis
Saw this as well right around 3pm PST. Not sure if newlines were
coming through or not, traffic graph shows a small amount of traffic
coming in as opposed to 0 so possibly.
On Apr 1, 3:46 pm, Chad Etzel jazzyc...@gmail.com wrote:
Hi all,
I am using the filter stream, and twice in the last 24
This appears to have been a load balancing issue that we just resolved. Let
us know if this recurs.
---Mark
http://twitter.com/mccv
On Thu, Apr 1, 2010 at 4:46 PM, Mark McBride mmcbr...@twitter.com wrote:
Are newlines (the ones that come every 30 seconds) still coming through, or
no data
Ed,
For app side filtering, you may want to look at Sphinx Search:
http://www.sphinxsearch.com/
On Mar 26, 2:41 pm, M. Edward (Ed) Borasky zzn...@gmail.com wrote:
On 03/26/2010 10:32 AM, John Kalucki wrote:
The combinatorics don't work out here until we offer boolean AND. Tokens are
On 03/26/2010 11:54 AM, Dewald Pretorius wrote:
Ed,
For app side filtering, you may want to look at Sphinx Search:
http://www.sphinxsearch.com/
Yeah, I've seen Sphinx and all the Lucene clones and Namazu and half a
dozen others. My natural inclination has been toward PostgreSQL's
built-in
What do you guys consider low quality?
Jonathon
On Mar 16, 9:46 am, John Kalucki j...@twitter.com wrote:
Do those same users show in search? If not, chances are that those users are
filtered for quality from both Search and Streaming.
If the users do show in Search, there's probably
1 - 100 of 261 matches
Mail list logo
