[twitter-dev] Re: Streaming API with start_date and end_date

2011-06-23 Thread Vags
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 from previous
date because Streaming API sends only tweets posted now. As far as
I'm aware you can't get past tweets using Streaming. You might think
about Search API in this case.

Seb

On Jun 23, 8:13 pm, JackRabbit yacobus.reinh...@gmail.com wrote:
 Hi Guys,

 is it possible to query streaming api with filter and include
 start_date and end_date, so that developer can track or filter by date
 range? If yes, that could be awesome, if no, would you mind please to
 add this feature?

 Why it is needed because it would be great if we can track keyword
 from previous date where we have missed the tweets. For event
 organizer and finance reports application like us, this feature is
 very valuable.

 Many Thanks,
 Jack

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk


[twitter-dev] Re: Streaming API, Following just a couple of people

2011-06-09 Thread Ray Slakinski
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 else using python.

On Jun 7, 9:26 am, Ray Slakinski ray.slakin...@gmail.com wrote:
 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 tweets. Only public tweets created after you open a connection 
  will be delivered.

  Have the users you are following Tweeted since you connected, and are they 
  public accounts (not protected)?

  On Jun 6, 2011, at 6:04, Ray Slakinski ray.slakin...@gmail.com wrote:

   I I start following just 1 or 2 people using the streaming API I do
   not get any of their tweets. Is there a buffer that needs to be filled
   before I get these?

   Ray Slakinski

   --
   Twitter developer documentation and resources:https://dev.twitter.com/doc
   API updates via Twitter:https://twitter.com/twitterapi
   Issues/Enhancements 
   Tracker:https://code.google.com/p/twitter-api/issues/list
   Change your membership to this 
   group:https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk


Re: [twitter-dev] Re: Streaming API, Following just a couple of people

2011-06-09 Thread Matt Harris
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 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 else using python.

 On Jun 7, 9:26 am, Ray Slakinski ray.slakin...@gmail.com wrote:
  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 tweets. Only public tweets created after you open a connection will
 be delivered.
 
   Have the users you are following Tweeted since you connected, and are
 they public accounts (not protected)?
 
   On Jun 6, 2011, at 6:04, Ray Slakinski ray.slakin...@gmail.com
 wrote:
 
I I start following just 1 or 2 people using the streaming API I do
not get any of their tweets. Is there a buffer that needs to be
 filled
before I get these?
 
Ray Slakinski
 
--
Twitter developer documentation and resources:
 https://dev.twitter.com/doc
API updates via Twitter:https://twitter.com/twitterapi
Issues/Enhancements Tracker:
 https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
 https://groups.google.com/forum/#!forum/twitter-development-talk

 --
 Twitter developer documentation and resources: https://dev.twitter.com/doc
 API updates via Twitter: https://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 https://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 https://groups.google.com/forum/#!forum/twitter-development-talk


-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk


[twitter-dev] Re: Streaming API, Following just a couple of people

2011-06-07 Thread Ray Slakinski
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 nor my co-workers streams are private.

Ray Slakinski

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 
 tweets. Only public tweets created after you open a connection will be 
 delivered.

 Have the users you are following Tweeted since you connected, and are they 
 public accounts (not protected)?

 On Jun 6, 2011, at 6:04, Ray Slakinski ray.slakin...@gmail.com wrote:



  I I start following just 1 or 2 people using the streaming API I do
  not get any of their tweets. Is there a buffer that needs to be filled
  before I get these?

  Ray Slakinski

  --
  Twitter developer documentation and resources:https://dev.twitter.com/doc
  API updates via Twitter:https://twitter.com/twitterapi
  Issues/Enhancements 
  Tracker:https://code.google.com/p/twitter-api/issues/list
  Change your membership to this 
  group:https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk


[twitter-dev] Re: Streaming API, Following just a couple of people

2011-06-07 Thread Ray Slakinski
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 
 tweets. Only public tweets created after you open a connection will be 
 delivered.

 Have the users you are following Tweeted since you connected, and are they 
 public accounts (not protected)?

 On Jun 6, 2011, at 6:04, Ray Slakinski ray.slakin...@gmail.com wrote:



  I I start following just 1 or 2 people using the streaming API I do
  not get any of their tweets. Is there a buffer that needs to be filled
  before I get these?

  Ray Slakinski

  --
  Twitter developer documentation and resources:https://dev.twitter.com/doc
  API updates via Twitter:https://twitter.com/twitterapi
  Issues/Enhancements 
  Tracker:https://code.google.com/p/twitter-api/issues/list
  Change your membership to this 
  group:https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk


[twitter-dev] Re: Streaming API credentials

2011-05-23 Thread Craig Walls
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.

What I'm looking for is a token/secret that belongs to the app and can
only be used to do things that required authentication, but not access
an individual's data (accessing the streaming API, for instance).
Perhaps I create a bogus user that represents the application and use
their credentials?

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk


Re: [twitter-dev] Re: Streaming API credentials

2011-05-23 Thread James Estes
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 twitter users to administer/manage the app.

James


On Mon, May 23, 2011 at 4:14 PM, Craig Walls hab...@gmail.com wrote:
 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.

 What I'm looking for is a token/secret that belongs to the app and can
 only be used to do things that required authentication, but not access
 an individual's data (accessing the streaming API, for instance).
 Perhaps I create a bogus user that represents the application and use
 their credentials?

 --
 Twitter developer documentation and resources: https://dev.twitter.com/doc
 API updates via Twitter: https://twitter.com/twitterapi
 Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 https://groups.google.com/forum/#!forum/twitter-development-talk


-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk


[twitter-dev] Re: Streaming API 420 error

2011-04-22 Thread Josiah Carlson
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 our different hosts in ec2, 
but they all seem to get a 420 error.

 - Josiah

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API statuses/fileter method, follow parameter

2011-04-21 Thread Kumar

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)

 Arnaud / @rno http://twitter.com/rno







 On Tue, Apr 19, 2011 at 9:35 PM, Kumar kumar...@gmail.com wrote:
  Hi All,

  The streaming api documentation says that mentions, implicit retweets
  and implicit replies will NOT be returned. However, it looks like they
  are being returned. For our application we do need to keep track of
  mentions and the streaming api seems to work fine. Can we rely on it
  being present always? Is the documentation dated and need to be
  updated?

  Thanks,
  Kumar.

  -
 http://dev.twitter.com/pages/streaming_api_methods#follow

  References unmatched are statuses that were:
  Mentions (“Hello @user!”)
  Implicit retweets (“RT @user Says Helloes” without pressing a retweet
  button)
  Implicit replies (“@user Hello!”, created without pressing a reply
  “swoosh” button to set the in_reply_to field)

  ---

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API Rate Limiting

2011-04-04 Thread Khandelwal
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 
 documentationhttp://docs.gnip.com/w/page/35663947/Power-Trackat 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 streaming api for equivalent
 geolocalized searches. See this 
 threadhttp://groups.google.com/group/twitter-development-talk/browse_thread...

 My results showed that the streaming API returns a very small fraction
 (3% in my tests) of what the search API returns. This is because the
 streaming API only uses the geotagging API to locate tweets, but the
 search API uses both the geotagging API and the user location field.

 For example, I can get around 250 000 tweets/day for San Francisco
 using the search api but the streaming api will return around 7000
 tweets/day.

 At 7000 tweets/day for San Francisco, 50 000 for the whole US seems
 small.

 Colin

 On Apr 1, 2:40 pm, Augusto Santos augu...@gemeos.org wrote:







  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 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 is but I would
   think 50% seem reasonable and would result in ~2.5M tweets/day. Even
   if we lower that proportion, your 50 000 tweets/day seems way off.

   There are 3 possibilities, 1) you are being rate limited more than you
   think, 2) your bounding box is wrong or 3) your bounding box is too
   large and Twitter has reduced it somehow. I remember I read somewhere
   in the api doc that each bounding box could not be more than 1 degree
   square enough to cover most metropolitan areas - but I cannot find
   that back.

   Colin

   On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote:
We have a bounding box set for the United States. Even though it's a
large box, we only receive about 50,000 tweets a day. However, I see
that we get rate limited at least once a week already. The box is
large, but the number of matching results is fairly low.  Knowing how
the rate limiting works more specifically would be important when
trying to gather data for other projects (more bounding boxes, other
keywords).

On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote:

 On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org
   wrote:
  No it won't. Streaming has rate limit with around 1% of firehose, if
   your
  search term os too much generic.
  If your search term or bouding box get too many tweets, you will
   start
  receive 'limit' status message as doc said.
 http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses

 Sure, I understand that, I just meant to say that 1% of all tweets is
 a lot (140M average per day now).

 If your terms are not very general, you have a lot of head room.

   --
   Twitter developer documentation and resources:http://dev.twitter.com/doc
   API updates via Twitter:http://twitter.com/twitterapi
   Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
   Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk

  --
  氣

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API Rate Limiting

2011-04-04 Thread Augusto Santos
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, 3:49 pm, Colin Surprenant colin.surpren...@gmail.com
 wrote:
  Well, first, In the Gnip Power Track documentationhttp://
 docs.gnip.com/w/page/35663947/Power-Trackat 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 streaming api for equivalent
  geolocalized searches. See this threadhttp://
 groups.google.com/group/twitter-development-talk/browse_thread...
 
  My results showed that the streaming API returns a very small fraction
  (3% in my tests) of what the search API returns. This is because the
  streaming API only uses the geotagging API to locate tweets, but the
  search API uses both the geotagging API and the user location field.
 
  For example, I can get around 250 000 tweets/day for San Francisco
  using the search api but the streaming api will return around 7000
  tweets/day.
 
  At 7000 tweets/day for San Francisco, 50 000 for the whole US seems
  small.
 
  Colin
 
  On Apr 1, 2:40 pm, Augusto Santos augu...@gemeos.org wrote:
 
 
 
 
 
 
 
   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 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 is but I
 would
think 50% seem reasonable and would result in ~2.5M tweets/day. Even
if we lower that proportion, your 50 000 tweets/day seems way off.
 
There are 3 possibilities, 1) you are being rate limited more than
 you
think, 2) your bounding box is wrong or 3) your bounding box is too
large and Twitter has reduced it somehow. I remember I read somewhere
in the api doc that each bounding box could not be more than 1 degree
square enough to cover most metropolitan areas - but I cannot find
that back.
 
Colin
 
On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote:
 We have a bounding box set for the United States. Even though it's
 a
 large box, we only receive about 50,000 tweets a day. However, I
 see
 that we get rate limited at least once a week already. The box is
 large, but the number of matching results is fairly low.  Knowing
 how
 the rate limiting works more specifically would be important when
 trying to gather data for other projects (more bounding boxes,
 other
 keywords).
 
 On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote:
 
  On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos 
 augu...@gemeos.org
wrote:
   No it won't. Streaming has rate limit with around 1% of
 firehose, if
your
   search term os too much generic.
   If your search term or bouding box get too many tweets, you
 will
start
   receive 'limit' status message as doc said.
  
 http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses
 
  Sure, I understand that, I just meant to say that 1% of all
 tweets is
  a lot (140M average per day now).
 
  If your terms are not very general, you have a lot of head room.
 
--
Twitter developer documentation and resources:
 http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
   http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
   http://groups.google.com/group/twitter-development-talk
 
   --
   氣

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
氣

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API Rate Limiting

2011-04-01 Thread Colin Surprenant
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 is but I would
think 50% seem reasonable and would result in ~2.5M tweets/day. Even
if we lower that proportion, your 50 000 tweets/day seems way off.

There are 3 possibilities, 1) you are being rate limited more than you
think, 2) your bounding box is wrong or 3) your bounding box is too
large and Twitter has reduced it somehow. I remember I read somewhere
in the api doc that each bounding box could not be more than 1 degree
square enough to cover most metropolitan areas - but I cannot find
that back.

Colin

On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote:
 We have a bounding box set for the United States. Even though it's a
 large box, we only receive about 50,000 tweets a day. However, I see
 that we get rate limited at least once a week already. The box is
 large, but the number of matching results is fairly low.  Knowing how
 the rate limiting works more specifically would be important when
 trying to gather data for other projects (more bounding boxes, other
 keywords).

 On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote:







  On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org wrote:
   No it won't. Streaming has rate limit with around 1% of firehose, if your
   search term os too much generic.
   If your search term or bouding box get too many tweets, you will start
   receive 'limit' status message as doc said.
  http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses

  Sure, I understand that, I just meant to say that 1% of all tweets is
  a lot (140M average per day now).

  If your terms are not very general, you have a lot of head room.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API Rate Limiting

2011-04-01 Thread Augusto Santos
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 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 is but I would
 think 50% seem reasonable and would result in ~2.5M tweets/day. Even
 if we lower that proportion, your 50 000 tweets/day seems way off.

 There are 3 possibilities, 1) you are being rate limited more than you
 think, 2) your bounding box is wrong or 3) your bounding box is too
 large and Twitter has reduced it somehow. I remember I read somewhere
 in the api doc that each bounding box could not be more than 1 degree
 square enough to cover most metropolitan areas - but I cannot find
 that back.

 Colin

 On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote:
  We have a bounding box set for the United States. Even though it's a
  large box, we only receive about 50,000 tweets a day. However, I see
  that we get rate limited at least once a week already. The box is
  large, but the number of matching results is fairly low.  Knowing how
  the rate limiting works more specifically would be important when
  trying to gather data for other projects (more bounding boxes, other
  keywords).
 
  On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote:
 
 
 
 
 
 
 
   On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org
 wrote:
No it won't. Streaming has rate limit with around 1% of firehose, if
 your
search term os too much generic.
If your search term or bouding box get too many tweets, you will
 start
receive 'limit' status message as doc said.
   http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses
 
   Sure, I understand that, I just meant to say that 1% of all tweets is
   a lot (140M average per day now).
 
   If your terms are not very general, you have a lot of head room.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
氣

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API Rate Limiting

2011-04-01 Thread Adam Green
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 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 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 is but I would
 think 50% seem reasonable and would result in ~2.5M tweets/day. Even
 if we lower that proportion, your 50 000 tweets/day seems way off.

 There are 3 possibilities, 1) you are being rate limited more than you
 think, 2) your bounding box is wrong or 3) your bounding box is too
 large and Twitter has reduced it somehow. I remember I read somewhere
 in the api doc that each bounding box could not be more than 1 degree
 square enough to cover most metropolitan areas - but I cannot find
 that back.

 Colin

 On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote:
  We have a bounding box set for the United States. Even though it's a
  large box, we only receive about 50,000 tweets a day. However, I see
  that we get rate limited at least once a week already. The box is
  large, but the number of matching results is fairly low.  Knowing how
  the rate limiting works more specifically would be important when
  trying to gather data for other projects (more bounding boxes, other
  keywords).
 
  On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote:
 
 
 
 
 
 
 
   On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org
   wrote:
No it won't. Streaming has rate limit with around 1% of firehose, if
your
search term os too much generic.
If your search term or bouding box get too many tweets, you will
start
receive 'limit' status message as doc said.
   http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses
 
   Sure, I understand that, I just meant to say that 1% of all tweets is
   a lot (140M average per day now).
 
   If your terms are not very general, you have a lot of head room.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk



 --
 氣

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Analyst
http://140dev.com, @140dev
http://2012twit.com, @2012twit
781-879-2960

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API Rate Limiting

2011-04-01 Thread Augusto Santos
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% geotagged tweets. And now I'am getting values very
 similar with you Adam.


 On Fri, Apr 1, 2011 at 3:56 PM, Adam Green 140...@gmail.com wrote:

 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 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 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 is but I would
  think 50% seem reasonable and would result in ~2.5M tweets/day. Even
  if we lower that proportion, your 50 000 tweets/day seems way off.
 
  There are 3 possibilities, 1) you are being rate limited more than you
  think, 2) your bounding box is wrong or 3) your bounding box is too
  large and Twitter has reduced it somehow. I remember I read somewhere
  in the api doc that each bounding box could not be more than 1 degree
  square enough to cover most metropolitan areas - but I cannot find
  that back.
 
  Colin
 
  On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote:
   We have a bounding box set for the United States. Even though it's a
   large box, we only receive about 50,000 tweets a day. However, I see
   that we get rate limited at least once a week already. The box is
   large, but the number of matching results is fairly low.  Knowing how
   the rate limiting works more specifically would be important when
   trying to gather data for other projects (more bounding boxes, other
   keywords).
  
   On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote:
  
  
  
  
  
  
  
On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos 
 augu...@gemeos.org
wrote:
 No it won't. Streaming has rate limit with around 1% of firehose,
 if
 your
 search term os too much generic.
 If your search term or bouding box get too many tweets, you will
 start
 receive 'limit' status message as doc said.

 http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses
  
Sure, I understand that, I just meant to say that 1% of all tweets
 is
a lot (140M average per day now).
  
If your terms are not very general, you have a lot of head room.
 
  --
  Twitter developer documentation and resources:
 http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk
 
 
 
  --
  氣
 
  --
  Twitter developer documentation and resources:
 http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk
 



 --
 Adam Green
 Twitter API Consultant and Analyst
 http://140dev.com, @140dev
 http://2012twit.com, @2012twit
 781-879-2960

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




 --
 氣




-- 
氣

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API Rate Limiting

2011-04-01 Thread Colin Surprenant
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 streaming api for equivalent
geolocalized searches. See this thread
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/a4bf3b7c6373657b#

My results showed that the streaming API returns a very small fraction
(3% in my tests) of what the search API returns. This is because the
streaming API only uses the geotagging API to locate tweets, but the
search API uses both the geotagging API and the user location field.

For example, I can get around 250 000 tweets/day for San Francisco
using the search api but the streaming api will return around 7000
tweets/day.

At 7000 tweets/day for San Francisco, 50 000 for the whole US seems
small.

Colin

On Apr 1, 2:40 pm, Augusto Santos augu...@gemeos.org wrote:
 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 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 is but I would
  think 50% seem reasonable and would result in ~2.5M tweets/day. Even
  if we lower that proportion, your 50 000 tweets/day seems way off.

  There are 3 possibilities, 1) you are being rate limited more than you
  think, 2) your bounding box is wrong or 3) your bounding box is too
  large and Twitter has reduced it somehow. I remember I read somewhere
  in the api doc that each bounding box could not be more than 1 degree
  square enough to cover most metropolitan areas - but I cannot find
  that back.

  Colin

  On Mar 31, 4:08 pm, Data Gatherer gatherer...@gmail.com wrote:
   We have a bounding box set for the United States. Even though it's a
   large box, we only receive about 50,000 tweets a day. However, I see
   that we get rate limited at least once a week already. The box is
   large, but the number of matching results is fairly low.  Knowing how
   the rate limiting works more specifically would be important when
   trying to gather data for other projects (more bounding boxes, other
   keywords).

   On Mar 31, 3:50 pm, Jeremy Dunck jdu...@gmail.com wrote:

On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org
  wrote:
 No it won't. Streaming has rate limit with around 1% of firehose, if
  your
 search term os too much generic.
 If your search term or bouding box get too many tweets, you will
  start
 receive 'limit' status message as doc said.
http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses

Sure, I understand that, I just meant to say that 1% of all tweets is
a lot (140M average per day now).

If your terms are not very general, you have a lot of head room.

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 氣

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API access level limit

2011-02-24 Thread AA
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 guidance.

 The number of connections you are allowed to the Streaming API is described
 in the Streaming API Concepts document:
    http://dev.twitter.com/pages/streaming_api_concepts

 It says:
 Each account may create only one standing connection to the Streaming API.
 Subsequent connections from the same account may cause previously
 established connections to be disconnected. Excessive connection attempts,
 regardless of success, will result in an automatic ban of the client's IP
 address. Continually failing connections will result in your IP address
 being blacklisted from all Twitter access.

 When tracking users using the Streaming API the default level allows 5000
 follower IDs to be tracked. Make sure the user_ids are specified with the
 follow parameter and not the track parameter.

 Best,
 @themattharris
 Developer Advocate, Twitterhttp://twitter.com/themattharris







 On Tue, Feb 22, 2011 at 11:22 PM, aquajach aquaj...@gmail.com wrote:
  Hi,

  Just started to play with streaming API, but get confused on how many
  followers id could be tracked with one connection. In basic level of
  filter,
 http://dev.twitter.com/doc/post/statuses/filtersays 400 followers ids
 http://dev.twitter.com/pages/streaming_api_methodssays 5,000
  followers ids

  Then I tried in local machine, could only follow around 320 ids
  ( receive 413 if more)  and seems multiple connections in one IP are
  not allowed. Any body here know: Is there any ways to follow a few
  thousands ids for each authenticated account (with oauth)? Or how to
  apply for higher access level?

  Any experience share or answers are appreciated!

  J

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API access level limit

2011-02-24 Thread Taylor Singletary
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) 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 guidance.
 
  The number of connections you are allowed to the Streaming API is
 described
  in the Streaming API Concepts document:
 http://dev.twitter.com/pages/streaming_api_concepts
 
  It says:
  Each account may create only one standing connection to the Streaming
 API.
  Subsequent connections from the same account may cause previously
  established connections to be disconnected. Excessive connection
 attempts,
  regardless of success, will result in an automatic ban of the client's IP
  address. Continually failing connections will result in your IP address
  being blacklisted from all Twitter access.
 
  When tracking users using the Streaming API the default level allows 5000
  follower IDs to be tracked. Make sure the user_ids are specified with the
  follow parameter and not the track parameter.
 
  Best,
  @themattharris
  Developer Advocate, Twitterhttp://twitter.com/themattharris
 
 
 
 
 
 
 
  On Tue, Feb 22, 2011 at 11:22 PM, aquajach aquaj...@gmail.com wrote:
   Hi,
 
   Just started to play with streaming API, but get confused on how many
   followers id could be tracked with one connection. In basic level of
   filter,
  http://dev.twitter.com/doc/post/statuses/filtersays 400 followers ids
  http://dev.twitter.com/pages/streaming_api_methodssays 5,000
   followers ids
 
   Then I tried in local machine, could only follow around 320 ids
   ( receive 413 if more)  and seems multiple connections in one IP are
   not allowed. Any body here know: Is there any ways to follow a few
   thousands ids for each authenticated account (with oauth)? Or how to
   apply for higher access level?
 
   Any experience share or answers are appreciated!
 
   J
 
   --
   Twitter developer documentation and resources:
 http://dev.twitter.com/doc
   API updates via Twitter:http://twitter.com/twitterapi
   Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
   Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API access level limit

2011-02-24 Thread Alejandro Alessi
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 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) 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 guidance.
 
  The number of connections you are allowed to the Streaming API is
 described
  in the Streaming API Concepts document:
 http://dev.twitter.com/pages/streaming_api_concepts
 
  It says:
  Each account may create only one standing connection to the Streaming
 API.
  Subsequent connections from the same account may cause previously
  established connections to be disconnected. Excessive connection
 attempts,
  regardless of success, will result in an automatic ban of the client's
 IP
  address. Continually failing connections will result in your IP address
  being blacklisted from all Twitter access.
 
  When tracking users using the Streaming API the default level allows
 5000
  follower IDs to be tracked. Make sure the user_ids are specified with
 the
  follow parameter and not the track parameter.
 
  Best,
  @themattharris
  Developer Advocate, Twitterhttp://twitter.com/themattharris
 
 
 
 
 
 
 
  On Tue, Feb 22, 2011 at 11:22 PM, aquajach aquaj...@gmail.com wrote:
   Hi,
 
   Just started to play with streaming API, but get confused on how many
   followers id could be tracked with one connection. In basic level of
   filter,
  http://dev.twitter.com/doc/post/statuses/filtersays 400 followers ids
  http://dev.twitter.com/pages/streaming_api_methodssays 5,000
   followers ids
 
   Then I tried in local machine, could only follow around 320 ids
   ( receive 413 if more)  and seems multiple connections in one IP are
   not allowed. Any body here know: Is there any ways to follow a few
   thousands ids for each authenticated account (with oauth)? Or how to
   apply for higher access level?
 
   Any experience share or answers are appreciated!
 
   J
 
   --
   Twitter developer documentation and resources:
 http://dev.twitter.com/doc
   API updates via Twitter:http://twitter.com/twitterapi
   Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
   Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-20 Thread Karussell
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 whatever
 post-processing you'd like.

 -John Kaluckihttp://twitter.com/jkalucki
 Twitter, Inc.

 On Thu, Feb 17, 2011 at 12:15 AM, Karussell 
 tableyourt...@googlemail.comwrote:

  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 investingated this a bit more and it seems to be intendend (?):
  these tweets are 'only' retweets. As example here is one too short
  tweet returned from the streaming API:

  RT @bcoders: Episode 33 onsite from @JFokus with @neal4d @nicksieger
  @brjavaman  Kirk Pepperdine is out!http://bit.ly/eikmuxis
  #Java ...

  and the same tweet (id == 37959896615886848) was more complete when
  returned from the search API:

  RT @bcoders: Episode 33 onsite from @JFokus with @neal4d @nicksieger
  @brjavaman  Kirk Pepperdine is out!http://bit.ly/eikmuxis #Java a
  dead-end?

  So, when I use search API I'll miss tweets and when using streaming
  API I'll miss text? Do I need to use both?

  Regards,
  Peter.

  **
  37952879822110720 Architecte Java J2EE: Priorité sera donnée à un
  candidat de la région nantaise. Merci de tran...http://bit.ly/dQhIoK
  #freelance #offres
  37954149668622336 به روز رسانی: Nimbuzz اکنون با پشتیبانی از اتصال
  رسمی API فیس بوکhttp://t.co/ICgTAXX
  37954912847400960 『Java Hangs When Converting 2.2250738585072012e-308』
 http://zennin.blog55.fc2.com/blog-entry-2773.html
  37956641609621504 Mastering Grails: Grails in the enterprise
 https://www.ibm.com/developerworks/java/library/j-grails12168/#grails
  37956994061176832 NEW! FileNet - Java/J2EE Developer - Vigilant
  Technologies:  ( #Columbus , OH)http://bit.ly/e6ULEw#OpenSource
  #Jobs #Job #TweetMyJOBS
  37957325557989376 After a day of Java programming in Eclipse, C++
  programming in Visual Studio just feels slow and crappy :(

  more examples in the given file:
 https://github.com/karussell/TestTwitterAPI/blob/master/discrepancy.txt

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-18 Thread John Kalucki
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.


On Thu, Feb 17, 2011 at 12:15 AM, Karussell tableyourt...@googlemail.comwrote:

 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 investingated this a bit more and it seems to be intendend (?):
 these tweets are 'only' retweets. As example here is one too short
 tweet returned from the streaming API:

 RT @bcoders: Episode 33 onsite from @JFokus with @neal4d @nicksieger
 @brjavaman  Kirk Pepperdine is out! http://bit.ly/eikmux is
 #Java ...

 and the same tweet (id == 37959896615886848) was more complete when
 returned from the search API:

 RT @bcoders: Episode 33 onsite from @JFokus with @neal4d @nicksieger
 @brjavaman  Kirk Pepperdine is out! http://bit.ly/eikmux is #Java a
 dead-end?

 So, when I use search API I'll miss tweets and when using streaming
 API I'll miss text? Do I need to use both?

 Regards,
 Peter.

 **
 37952879822110720 Architecte Java J2EE: Priorité sera donnée à un
 candidat de la région nantaise. Merci de tran... http://bit.ly/dQhIoK
 #freelance #offres
 37954149668622336 به روز رسانی: Nimbuzz اکنون با پشتیبانی از اتصال
 رسمی API فیس بوک http://t.co/ICgTAXX
 37954912847400960 『Java Hangs When Converting 2.2250738585072012e-308』
 http://zennin.blog55.fc2.com/blog-entry-2773.html
 37956641609621504 Mastering Grails: Grails in the enterprise
 https://www.ibm.com/developerworks/java/library/j-grails12168/ #grails
 37956994061176832 NEW! FileNet - Java/J2EE Developer - Vigilant
 Technologies:  ( #Columbus , OH) http://bit.ly/e6ULEw #OpenSource
 #Jobs #Job #TweetMyJOBS
 37957325557989376 After a day of Java programming in Eclipse, C++
 programming in Visual Studio just feels slow and crappy :(

 more examples in the given file:
 https://github.com/karussell/TestTwitterAPI/blob/master/discrepancy.txt

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-17 Thread Karussell
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: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-17 Thread Karussell
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 investingated this a bit more and it seems to be intendend (?):
these tweets are 'only' retweets. As example here is one too short
tweet returned from the streaming API:

RT @bcoders: Episode 33 onsite from @JFokus with @neal4d @nicksieger
@brjavaman  Kirk Pepperdine is out! http://bit.ly/eikmux is
#Java ...

and the same tweet (id == 37959896615886848) was more complete when
returned from the search API:

RT @bcoders: Episode 33 onsite from @JFokus with @neal4d @nicksieger
@brjavaman  Kirk Pepperdine is out! http://bit.ly/eikmux is #Java a
dead-end?

So, when I use search API I'll miss tweets and when using streaming
API I'll miss text? Do I need to use both?

Regards,
Peter.

**
37952879822110720 Architecte Java J2EE: Priorité sera donnée à un
candidat de la région nantaise. Merci de tran... http://bit.ly/dQhIoK
#freelance #offres
37954149668622336 به روز رسانی: Nimbuzz اکنون با پشتیبانی از اتصال
رسمی API فیس بوک http://t.co/ICgTAXX
37954912847400960 『Java Hangs When Converting 2.2250738585072012e-308』
http://zennin.blog55.fc2.com/blog-entry-2773.html
37956641609621504 Mastering Grails: Grails in the enterprise
https://www.ibm.com/developerworks/java/library/j-grails12168/ #grails
37956994061176832 NEW! FileNet - Java/J2EE Developer - Vigilant
Technologies:  ( #Columbus , OH) http://bit.ly/e6ULEw #OpenSource
#Jobs #Job #TweetMyJOBS
37957325557989376 After a day of Java programming in Eclipse, C++
programming in Visual Studio just feels slow and crappy :(

more examples in the given file:
https://github.com/karussell/TestTwitterAPI/blob/master/discrepancy.txt

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming Api returning tweets with NULL value for object place

2011-02-17 Thread Eric Charles
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 with
 the place tag of the tweet object.

 I was just wondering if it's just me or is there some sort of bug or
 changes have been made in the API?

 Aci Cartagena

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming Api returning tweets with NULL value for object place

2011-02-17 Thread Matt Harris
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 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 with
  the place tag of the tweet object.
 
  I was just wondering if it's just me or is there some sort of bug or
  changes have been made in the API?
 
  Aci Cartagena

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming Api returning tweets with NULL value for object place

2011-02-17 Thread Augusto Santos
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 thematthar...@twitter.comwrote:

 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.com
  wrote:

 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 with
  the place tag of the tweet object.
 
  I was just wondering if it's just me or is there some sort of bug or
  changes have been made in the API?
 
  Aci Cartagena

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


  --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
氣

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming Api returning tweets with NULL value for object place

2011-02-17 Thread 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 17, 2011 at 9:39 AM, Augusto Santos augu...@gemeos.org wrote:

 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 thematthar...@twitter.comwrote:

 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.com wrote:

 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 with
  the place tag of the tweet object.
 
  I was just wondering if it's just me or is there some sort of bug or
  changes have been made in the API?
 
  Aci Cartagena

 --
 Twitter developer documentation and resources:
 http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


  --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




 --
 氣


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-16 Thread Karussell
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:

https://github.com/karussell/TestTwitterAPI/blob/master/discrepancy.txt

Why are they lost?

You can build the java mini programm via (or via your favourite IDE):
mvn clean install

and call it via:
./myjava -Dtwitter4j.oauth.consumerKey=key -
Dtwitter4j.oauth.consumerSecret=value de.jetwick.tw.NewClass java
token tokenSecret

to see what I mean ...

Another strange fact is that a lot of long tweets retrieved via the
streaming api have a text which is ~15 character shorter than the
identical tweet from the search API !

Regards,
Peter.

--

http://jetwick.com Twitter Search without Noise

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-15 Thread Karussell
Hi John, hi Adam,

thanks for your responses.

 To increase recall, search sometimes includes keywords in followed links and 
 other techniques

ah, ok. this would explain the differences between C and B (but not
betweet C and A). I'll investigate ...

 Also, are you getting rate limit messages on the Streaming API?

no.
I saw track limits (or something) when my keyword was 'java' or a
similar high frequent term.

Regards,
Peter.

On 15 Feb., 18:30, John Kalucki j...@twitter.com wrote:
 If you examine set C, do they contain matches on fields other than the Tweet
 text? To increase recall, search sometimes includes keywords in followed
 links and other techniques.

 Also, are you getting rate limit messages on the Streaming API?

 -John Kaluckihttp://twitter.com/jkalucki
 Twitter, Inc.

 On Tue, Feb 15, 2011 at 3:36 AM, Karussell 
 tableyourt...@googlemail.comwrote:

  Hi,

  this problem was already posted to the twitter4j mailing list [1]. Not
  sure if it is an issue with my code, twitter4j or an API issue... user
  reported similar problems in the past [2].

  First:

  I'm doing a 100 tweet search (without paging) every 5 minutes e.g.
  against 'twitter search'. I get a set of tweets A - excluding the
  duplicates, of course. I get approx 5 new tweets for every 5 minutes,
  so 100 tweets as pageSize should be perfectly sufficient to get all
  tweets.

  Second:
  When I'm doing a streaming filter request for the same terms 'twitter
  search' then I'm getting a set of tweets B.

  The problem is: combining A and B ('C=A v B') gives me a set C where
  the count of C is more than 10% larger then A or B, which means that
  neither with search nor streaming API I can catch a nearly complete
  set of tweets.

  E.g. doing this for 3 hours I'm getting 254 tweets (A) for the search
  and 257 tweets (B) for the streaming but the combined set C has 337
  tweets!

  Is this a bug in my code or could this be an API issue?

  BTW: I don't assume 100% correctness, I only want something above
  90% :) especially for such relatively infrequent terms, where users
  can, should and have noticed it.

  Regards,
  Peter.

  [1]
 http://groups.google.com/group/twitter4j/msg/d959e6257ceb452f

  [2]

 http://groups.google.com/group/twitter-development-talk/browse_thread...

 http://blog.tweetsmarter.com/twitter-downtime/twitters-dirty-secret-t...

  --

 http://jetwick.comTwitter Search without Noise

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-15 Thread Colin Surprenant
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 start at the same item. A
trick, if you want to grab as much similar results at possible from
the start is to request only a single item on the first poll (using
rpp=1) (or use only the most recent item of your result) then use this
item to seed your since_id on the following polls. Another idea might
be to start your stream reader first and use the first item returned
by your reader to again seed your since_id in your poller. Also you
can simply ignore this during collection but cleanup your data once
your done collecting and make sure both data sets start and end with
the same item ID.

In any case, if your difference is in fact related to the handling of
the first poll, it will become marginal as your data grow.

I also ran some tests to compare results between both methods using a
single keyword. With result sets of about 15000 ids, both sets are
identical at 98.3%. For testing purposes both my poller and stream
reader only output IDs so I can use cat, sort, uniq, wc and diff to
compare results.

Colin

On Feb 15, 2:33 pm, Karussell tableyourt...@googlemail.com wrote:
 Hi John, hi Adam,

 thanks for your responses.

  To increase recall, search sometimes includes keywords in followed links 
  and other techniques

 ah, ok. this would explain the differences between C and B (but not
 betweet C and A). I'll investigate ...

  Also, are you getting rate limit messages on the Streaming API?

 no.
 I saw track limits (or something) when my keyword was 'java' or a
 similar high frequent term.

 Regards,
 Peter.

 On 15 Feb., 18:30, John Kalucki j...@twitter.com wrote:







  If you examine set C, do they contain matches on fields other than the Tweet
  text? To increase recall, search sometimes includes keywords in followed
  links and other techniques.

  Also, are you getting rate limit messages on the Streaming API?

  -John Kaluckihttp://twitter.com/jkalucki
  Twitter, Inc.

  On Tue, Feb 15, 2011 at 3:36 AM, Karussell 
  tableyourt...@googlemail.comwrote:

   Hi,

   this problem was already posted to the twitter4j mailing list [1]. Not
   sure if it is an issue with my code, twitter4j or an API issue... user
   reported similar problems in the past [2].

   First:

   I'm doing a 100 tweet search (without paging) every 5 minutes e.g.
   against 'twitter search'. I get a set of tweets A - excluding the
   duplicates, of course. I get approx 5 new tweets for every 5 minutes,
   so 100 tweets as pageSize should be perfectly sufficient to get all
   tweets.

   Second:
   When I'm doing a streaming filter request for the same terms 'twitter
   search' then I'm getting a set of tweets B.

   The problem is: combining A and B ('C=A v B') gives me a set C where
   the count of C is more than 10% larger then A or B, which means that
   neither with search nor streaming API I can catch a nearly complete
   set of tweets.

   E.g. doing this for 3 hours I'm getting 254 tweets (A) for the search
   and 257 tweets (B) for the streaming but the combined set C has 337
   tweets!

   Is this a bug in my code or could this be an API issue?

   BTW: I don't assume 100% correctness, I only want something above
   90% :) especially for such relatively infrequent terms, where users
   can, should and have noticed it.

   Regards,
   Peter.

   [1]
  http://groups.google.com/group/twitter4j/msg/d959e6257ceb452f

   [2]

  http://groups.google.com/group/twitter-development-talk/browse_thread...

  http://blog.tweetsmarter.com/twitter-downtime/twitters-dirty-secret-t...

   --

  http://jetwick.comTwitterSearch without Noise

   --
   Twitter developer documentation and resources:http://dev.twitter.com/doc
   API updates via Twitter:http://twitter.com/twitterapi
   Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
   Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-15 Thread Karussell
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
'feature'? It shouldn't take into account that. Although the title of
the web site should taken into account ... like it is done in
jetwick ;)

I'll investigate for other keywords now.

 Typically your first poll will return 100 items then subsequent polls
 will return only new data if using since_id and/or dedupping.

I already removed these early tweets, of course ...

 I also ran some tests

with which keywords do you ran the tests?

 For testing purposes both my poller and stream reader only output IDs
  so I can use cat, sort, uniq, wc and diff to compare results.

Yes, I went the same way :)

Regards,
Peter.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-15 Thread M. Edward (Ed) Borasky
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 operational instability, the Streaming API returns 100% of 
the

tweets requested, or sends a limit message to let you know what has
been dropped.


What has been dropped, or how many have been dropped? ;-)

--
http://twitter.com/znmeb http://borasky-research.net

A mathematician is a device for turning coffee into theorems. -- Paul 
Erdős


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API maintenance: brief delivery pause and an increased likelihood for duplicate tweets

2011-02-10 Thread John Kalucki
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 about two
minutes.

-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.



On Wed, Feb 9, 2011 at 1:15 PM, John Kalucki j...@twitter.com wrote:

 We are performing a maintenance activity shortly that will increase the
 likelihood of duplicate tweets and other messages on all Streaming APIs:
 User Streams, Site Streams, and stream.twitter.com. There may also be a
 brief pause in delivery. No tweets or other messages will be lost during
 this maintenance event.

 The maintenance window is predicted to be approximately 2 minutes long and
 may occur between 1:15pm PST / 21:15 UTC and 3:30pm PST / 23:15 UTC.

 Note that this possibility of duplications has always been documented on
 the Streaming API at:
 http://dev.twitter.com/pages/streaming_api_concepts#quality-of-service.

 -John Kalucki
 Twitter, Inc.
 http://twitter.com/jkalucki




-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API stopwords

2011-02-07 Thread Kenny Buckler
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 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 googlehttp://www.lextek.com/manuals/onix/stopwords1.html

 - Mohan

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API stopwords

2011-02-04 Thread L. Mohan Arun
 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
http://www.lextek.com/manuals/onix/stopwords1.html

- Mohan

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API - Multiple connections on 1 IP?

2010-12-16 Thread epomqo
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 same machine? The official
  document seems don't say this clearly:

  Each account may create only one standing connection to the Streaming
  API. Subsequent connections from the same account may cause previously
  established connections to be disconnected. Excessive connection
  attempts, regardless of success, will result in an automatic ban of
  the client's IP address. Continually failing connections will result
  in your IP address being blacklisted from all Twitter access.

  Many thanks for the help!
  epomqo

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 氣

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API and OAuth

2010-11-09 Thread Dewald Pretorius
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 you can
use any access token, or must request a token from an endpoint
specific to the Streaming API.

On Nov 8, 7:46 pm, Tom van der Woerdt i...@tvdw.eu wrote:
 Streaming API doesn't differ from the REST API with it's authentication.
 Both use OAuth 1.0.

 Tom

 On 11/8/10 11:55 PM, Dewald Pretorius wrote:

  Please update your documentation [1] for more detail information on
  authenticating on the Streaming API with OAuth.

  We need to know the same type of information that you currently
  provide [2] for REST OAuth.

  [1]http://developer.twitter.com/pages/stre0aming_api_concepts#authentica...
  [2]http://developer.twitter.com/pages/auth

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API and OAuth

2010-11-09 Thread Taylor Singletary
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 streaming API
- In most cases, you need only use an access token generated from the my
access token feature available on dev.twitter.com for an app belonging to
an account with the access you need

Here's an example of connecting to the filter endpoint, tracking the terms
twitter and apple:

== signature_base_string
POSThttp%3A%2F%2Fstream.twitter.com
%2F1%2Fstatuses%2Ffilter.jsonoauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DIb3Z5EQtPAMBC4h98xYxzCUyKa18oE1VOu94qoIW4No%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1289319159%26oauth_token%3D819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw%26oauth_version%3D1.0%26track%3Dtwitter%252Capple

== authorization_header
OAuth oauth_nonce=Ib3Z5EQtPAMBC4h98xYxzCUyKa18oE1VOu94qoIW4No,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1289319159,
oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ,
oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw,
oauth_signature=pVYJDfAeCrQhrv8aTksV6PsKdA8%3D, oauth_version=1.0

== POST Body
track=twitter%2capple

Taylor

On Tue, Nov 9, 2010 at 7:43 AM, Dewald Pretorius dpr...@gmail.com wrote:

 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 you can
 use any access token, or must request a token from an endpoint
 specific to the Streaming API.

 On Nov 8, 7:46 pm, Tom van der Woerdt i...@tvdw.eu wrote:
  Streaming API doesn't differ from the REST API with it's authentication.
  Both use OAuth 1.0.
 
  Tom
 
  On 11/8/10 11:55 PM, Dewald Pretorius wrote:
 
   Please update your documentation [1] for more detail information on
   authenticating on the Streaming API with OAuth.
 
   We need to know the same type of information that you currently
   provide [2] for REST OAuth.
 
   [1]
 http://developer.twitter.com/pages/stre0aming_api_concepts#authentica...
   [2]http://developer.twitter.com/pages/auth

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API, Basic Auth Ok, OAuth Unauthorized?

2010-10-25 Thread bradley.meck
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 yet un-answered
 sadly) question I have in the mailing list about  my client (which
 iirc you're using)

 See :
    http://github.com/ciaranj/node-oauth/issues#issue/7
 and
    http://groups.google.co.uk/group/twitter-development-talk/browse_thre...
 oh and also ( :( )
    http://groups.google.co.uk/group/twitter-development-talk/browse_thre...

 The bad news is twitter don't seem to want to tell me if I'm wrong, or
 they're wrong (I don't care, just want to know what to fix ! :( ) ..
 the good news is the work around is to url encode your parameters
 before you pass them off to my client ( you won't need to do this with
 any other OAuth provider I've yet come across fwiw, but if they come
 back and say yes, thats deliberate, yes its different, I'll hardcode
 it into the client so you don't need to worry about it *sigh* (or even
 better, the client is wrong, we're right and we do it the same as
 everyone else..which would be an ideal outcome) )

 Take Care
 - cj.







 On Mon, Oct 25, 2010 at 10:20 PM, bradley.meck bradley.m...@gmail.com wrote:
  I have a simple oauth client that I use to post status updates
  currently, however, when I added the ability to track statuses with
  the Stream api using OAuth I noticed I could not connect, with
  Unauthorized 401 being the reply to anything I sent it. I looked into
  the documentation and it seems to be a simple request using the same
  OAuth style as the normal api. After searching threads I noticed the
  rate limiting and so I have left my app alone for extended periods of
  time and still I get 401s. I tested against basic auth, and the code
  worked! M, that was odd. So unless I am mistaken I am doing
  something wrong, but I am posting to the right url and mirroring my
  basic auth test to no avail. The code is at:

 http://github.com/bmeck/Simple-Bot/blob/master/modules/twitter.js
  the track() function is the boilerplate that is in question
  oa.post is a simple rest wrapper for oauth POST.

  Any help or directions as to where to go from here is much
  appreciated.

  Cheers,
  Bradley

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list
  Change your membership to this 
  group:http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API, Basic Auth Ok, OAuth Unauthorized?

2010-10-25 Thread Ciaran
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 track=+tracking.join(,)+count=0 should work ?
-cj.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API, Basic Auth Ok, OAuth Unauthorized?

2010-10-25 Thread bradley.meck
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 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 track=+tracking.join(,)+count=0 should work ?
 -cj.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API, Basic Auth Ok, OAuth Unauthorized?

2010-10-25 Thread themattharris
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

Assuming my parameters are POST parameters and are as follows:

key | value

track | twitter
follow | 1528912,9512582
oauth_consumer_key | Oauth_Consumer_Key
oauth_nonce | nonce123
oauth_signature_method | HMAC-SHA1
oauth_timestamp | 1288042714
oauth_token | My_tokeN
oauth_version | 1.0

Now following 3.4.1.3.2
1. Parameter names and values are encoded according to Section 3.6.
Section 3.6 of the spec says:
The values are then escaped using the [RFC3986] percent-encoding
(%XX) mechanism as follows:
  *  Characters in the unreserved character set as defined by
[RFC3986], Section 2.3 (ALPHA, DIGIT, -, ., _, ~) MUST NOT be
encoded.
  *  All other characters MUST be encoded.
  *  The two hexadecimal characters used to represent encoded
characters MUST be uppercase.

Knowing this our parameters therefore become:
key | value

track | twitter
follow | 11528912%2C9512582
oauth_consumer_key | OauthConsumerKey
oauth_nonce | nonce123
oauth_signature_method | HMAC-SHA1
oauth_timestamp | 1288042714
oauth_token | My_tokeN
oauth_version | 1.0

2. The parameters are sorted by name, using ascending byte value
ordering.  If two or more parameters share the same name, they are
sorted by their value.

key | value

follow | 11528912%2C9512582
oauth_consumer_key | OauthConsumerKey
oauth_nonce | nonce123
oauth_signature_method | HMAC-SHA1
oauth_timestamp | 1288042714
oauth_token | My_tokeN
oauth_version | 1.0
track | twitter

3. The name of each parameter is concatenated to its corresponding
value using an = character (ASCII code 61) as a separator, even if
the value is empty.

key=value

follow=11528912%2C9512582
oauth_consumer_key=OauthConsumerKey
oauth_nonce=nonce123
oauth_signature_method=HMAC-SHA1
oauth_timestamp=1288042714
oauth_token=My_tokeN
oauth_version=1.0
track=twitter

4. The sorted name/value pairs are concatenated together into a single
string by using an  character (ASCII code 38) as separator.

follow=11528912%2C9512582oauth_consumer_key=OauthConsumerKeyoauth_nonce=nonce123oauth_signature_method=HMAC-
SHA1oauth_timestamp=1288042714oauth_token=My_tokeNoauth_version=1.0track=twitter


This concatenated string of parameters is the result of the
normalization part of 3.4.1.1.5. We still have to complete stage 5
which says to encode that string.

Doing this gives:
follow%3D11528912%252C9512582%26oauth_consumer_key%3DOauthConsumerKey
%26oauth_nonce%3Dnonce123%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1288042714%26oauth_token%3DMy_tokeN
%26oauth_version%3D1.0%26track%3Dtwitter

In this example, assuming we are POSTing to 
http://stream.twitter.com/1/statuses/filter.json
with the parameters already processed - our basestring becomes:

POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D11528912%252C9512582%26oauth_consumer_key
%3DOauthConsumerKey%26oauth_nonce%3Dnonce123%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1288042714%26oauth_token%3DMy_tokeN
%26oauth_version%3D1.0%26track%3Dtwitter

I hope that helps,
@themattharris



On Oct 25, 3:20 pm, bradley.meck bradley.m...@gmail.com wrote:
 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 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 track=+tracking.join(,)+count=0 should work ?
  -cj.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API, Basic Auth Ok, OAuth Unauthorized?

2010-10-25 Thread Ciaran
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 post this, I agree OAuth can
be /  is  confusing ;)


 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

 Assuming my parameters are POST parameters and are as follows:

 key | value
 
 track | twitter
 follow | 1528912,9512582
 oauth_consumer_key | Oauth_Consumer_Key
 oauth_nonce | nonce123
 oauth_signature_method | HMAC-SHA1
 oauth_timestamp | 1288042714
 oauth_token | My_tokeN
 oauth_version | 1.0

 Now following 3.4.1.3.2
 1. Parameter names and values are encoded according to Section 3.6.
 Section 3.6 of the spec says:
 The values are then escaped using the [RFC3986] percent-encoding
 (%XX) mechanism as follows:
  *  Characters in the unreserved character set as defined by
 [RFC3986], Section 2.3 (ALPHA, DIGIT, -, ., _, ~) MUST NOT be
 encoded.
  *  All other characters MUST be encoded.
  *  The two hexadecimal characters used to represent encoded
 characters MUST be uppercase.

 Knowing this our parameters therefore become:
 key | value
 
 track | twitter
 follow | 11528912%2C9512582
 oauth_consumer_key | OauthConsumerKey
 oauth_nonce | nonce123
 oauth_signature_method | HMAC-SHA1
 oauth_timestamp | 1288042714
 oauth_token | My_tokeN
 oauth_version | 1.0

 2. The parameters are sorted by name, using ascending byte value
 ordering.  If two or more parameters share the same name, they are
 sorted by their value.

 key | value
 
 follow | 11528912%2C9512582
 oauth_consumer_key | OauthConsumerKey
 oauth_nonce | nonce123
 oauth_signature_method | HMAC-SHA1
 oauth_timestamp | 1288042714
 oauth_token | My_tokeN
 oauth_version | 1.0
 track | twitter

 3. The name of each parameter is concatenated to its corresponding
 value using an = character (ASCII code 61) as a separator, even if
 the value is empty.

 key=value
 
 follow=11528912%2C9512582
 oauth_consumer_key=OauthConsumerKey
 oauth_nonce=nonce123
 oauth_signature_method=HMAC-SHA1
 oauth_timestamp=1288042714
 oauth_token=My_tokeN
 oauth_version=1.0
 track=twitter

 4. The sorted name/value pairs are concatenated together into a single
 string by using an  character (ASCII code 38) as separator.

Indeed, Steps 1,2, 3 + 4 as described above are the ones I know from
the Spec, however on this page: http://dev.twitter.com/pages/auth %3d
and %26 are used during the concatenation process, and ...


 follow=11528912%2C9512582oauth_consumer_key=OauthConsumerKeyoauth_nonce=nonce123oauth_signature_method=HMAC-
 SHA1oauth_timestamp=1288042714oauth_token=My_tokeNoauth_version=1.0track=twitter


 This concatenated string of parameters is the result of the
 normalization part of 3.4.1.1.5. We still have to complete stage 5
 which says to encode that string.

... This step apparently does not occur ? (again according to that
web-page)... it appears that it is considered equivalent to escape the
'' and the '=' during the loop, rather than escape the whole string
at once (which will re-escape the individually escaped keys and values
as per [I believe] the spec)


 Doing this gives:
 follow%3D11528912%252C9512582%26oauth_consumer_key%3DOauthConsumerKey
 %26oauth_nonce%3Dnonce123%26oauth_signature_method%3DHMAC-
 SHA1%26oauth_timestamp%3D1288042714%26oauth_token%3DMy_tokeN
 %26oauth_version%3D1.0%26track%3Dtwitter

 In this example, assuming we are POSTing to 
 http://stream.twitter.com/1/statuses/filter.json
 with the parameters already processed - our basestring becomes:

 POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
 %2Ffilter.jsonfollow%3D11528912%252C9512582%26oauth_consumer_key
 %3DOauthConsumerKey%26oauth_nonce%3Dnonce123%26oauth_signature_method
 %3DHMAC-SHA1%26oauth_timestamp%3D1288042714%26oauth_token%3DMy_tokeN
 %26oauth_version%3D1.0%26track%3Dtwitter

 I hope that helps,
 @themattharris

It will do, if what you say is happening is what *really* happens on
the server (and that web page is wrong / or I mis-understand it) ..
then I'll have to find some other reason why escaping the url
parameters fixes things ;)

Cheery-bye, and again, thank you for taking the time to talk this through :)

-cj

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API test: Adding new_id field to statuses at 17:00 UTC Sept 29

2010-10-04 Thread Walter Santos
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 will provide a way to backfill from the streaming API. ...

Thanks!

On 28 set, 18:34, John Kalucki j...@twitter.com wrote:
 Tomorrow, Wednesday September 29, at 10:00 AM PDT / 17:00 UTC, we will
 briefly introduce a field called new_id to statuses delivered over 
 theStreamingAPI. If this 10 minute test is successful, we will enable
 the new_id field continuously on Thursday September 30th at about the
 same time. Note that timelines returned by the REST and Search APIs
 will not contain this field. This new_id field will allow applications
 to preview thenewstatusidgeneration scheme before the primary key
 transition scheduled for Tuesday October 12th.

 For more information on our statusidtransition:

 http://groups.google.com/group/twitter-api-announce/browse_thread/thr...http://groups.google.com/group/twitter-api-announce/browse_thread/thr...

 -John Kaluckihttp://twitter.com/jkalucki
 Twitter, Inc.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API test: Adding new_id field to statuses at 17:00 UTC Sept 29

2010-10-04 Thread John Kalucki
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
http://twitter.com/jkalucki
Twitter, Inc



On Sun, Oct 3, 2010 at 9:28 PM, Walter Santos walte...@gmail.com wrote:
 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 will provide a way to backfill from the streaming API. ...

 Thanks!

 On 28 set, 18:34, John Kalucki j...@twitter.com wrote:
 Tomorrow, Wednesday September 29, at 10:00 AM PDT / 17:00 UTC, we will
 briefly introduce a field called new_id to statuses delivered over 
 theStreamingAPI. If this 10 minute test is successful, we will enable
 the new_id field continuously on Thursday September 30th at about the
 same time. Note that timelines returned by the REST and Search APIs
 will not contain this field. This new_id field will allow applications
 to preview thenewstatusidgeneration scheme before the primary key
 transition scheduled for Tuesday October 12th.

 For more information on our statusidtransition:

 http://groups.google.com/group/twitter-api-announce/browse_thread/thr...http://groups.google.com/group/twitter-api-announce/browse_thread/thr...

 -John Kaluckihttp://twitter.com/jkalucki
 Twitter, Inc.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API skips users

2010-09-27 Thread Matt Harris
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 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 resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API skips users

2010-09-27 Thread Ginny Hendry

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 pretty random which ones get through and
which ones don't.

Here's how to fix it:

First update the gem and see if it is a version later than 0.7.7.  If
it is, you should be OK.  If it's 0.7.7 or earlier, change one line of
code:

Look in the gem source code on your system for the yajl-ruby gem and
find the file lib/yajl/http_stream.rb.

Edit line 151 from
   break if line.match /0.*?\r\n/
to
   break if line.match /^0.*?\r\n/

Adding that one character will correct the error.


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Re: Streaming API skips users

2010-09-27 Thread Tim Haines
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 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 pretty random which ones get through and
 which ones don't.

 Here's how to fix it:

 First update the gem and see if it is a version later than 0.7.7.  If
 it is, you should be OK.  If it's 0.7.7 or earlier, change one line of
 code:

 Look in the gem source code on your system for the yajl-ruby gem and
 find the file lib/yajl/http_stream.rb.

 Edit line 151 from
   break if line.match /0.*?\r\n/
 to
   break if line.match /^0.*?\r\n/

 Adding that one character will correct the error.


 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API skips users

2010-09-26 Thread Ginny Hendry

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 resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API skips users

2010-09-24 Thread Ginny Hendry
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, almost always with very low latency,
 unless they are protected accounts or otherwise filtered from search and
 streaming. Once an account is filtered, it should remain filtered for a very
 long time and not bounce back and forth.

 If you perform the same request with curl, and study the output, do you see
 the data that you expect?

 -John Kaluckihttp://twitter.com/jkalucki
 Twitter, Inc.



 On Thu, Sep 23, 2010 at 8:59 PM, Ginny Hendry ginnyhen...@gmail.com wrote:
  We are new to the Twitter API.  In early stages of testing an app, we
  reading from the streaming API to get tweets for a list of users.  It
  seems to work for some users and not others, and if it fails for one
  or two users today it will work for them tomorrow.

  We are doing a post to this url with four user IDs in the post data in
  the format shown:

  http://username:passw...@stream.twitter.com/1/statuses/filter.json

  follow=111,222,333,444

  We start the stream and then enter tweets manually from several of the
  Twitter accounts.  Some of the accounts work some of the time, that
  is, for some of the accounts the tweets appear in our stream.  If we
  test the same thing later a different selection of accounts work.  We
  haven't seen any pattern.  None of the accounts are set to be private.

  So our question is:  Is this supposed to work?  Are all new tweets
  entered for the four users supposed to appear in the stream within a
  short time?  How can we debug this?

  Any suggestions welcome.  Thanks.

    -Ginny

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] Re: Streaming API (filter) and retweets, JSON Output

2010-09-06 Thread JorisW
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 of TMobile_NL
starting with Vanaf vandaag

Coming from the API, after json_decode() in PHP:


Array
(
[place] =
[geo] =
[text] = RT @TMobile_NL: Vanaf vandaag kosteloos de
MobileNavigator app van Navigon voor alle iPhone klanten van T-Mobile
http://bit.ly/9P9LEv
[coordinates] =
[retweet_count] =
[favorited] =
[source] = web
[contributors] =
[created_at] = Mon Sep 06 12:47:12 + 2010
[in_reply_to_status_id] = 0
[retweeted_status] =
[in_reply_to_screen_name] =
[user] = Array
(
[time_zone] = Amsterdam
[profile_sidebar_border_color] = C0DEED
[screen_name] = Mobieleeenheid
[notifications] =
[listed_count] = 0
[profile_background_image_url] =
http://a1.twimg.com/profile_background_images/140319202/iphone-mania-twitter-background12.jpg
[location] = Eibergen, Netherlands
[statuses_count] = 11
[profile_background_color] = 31a3d4
[description] = Wij zijn Mobieleeenheid.nl.
U vindt hier 6271 scherp geprijsde accessoires voor 2541 gsm modellen.

Dagelijks voegen wij nieuwe accessoires toe.

[show_all_inline_media] =
[profile_background_tile] = 1
[contributors_enabled] =
[geo_enabled] =
[created_at] = Thu Aug 26 11:02:40 + 2010
[profile_text_color] = 1f191f
[followers_count] = 2
[profile_use_background_image] = 1
[url] = http://www.mobieleeenheid.nl
[friends_count] = 12
[profile_link_color] = 0084B4
[protected] =
[lang] = en
[verified] =
[name] = Mobieleeenheid
[follow_request_sent] =
[following] =
[favourites_count] = 0
[profile_sidebar_fill_color] = ddeef6
[profile_image_url] =
http://a0.twimg.com/profile_images/171140/top-5-cell-phones_normal.jpg
[id] = 183189171
[utc_offset] = 3600
)

[retweeted] =
[in_reply_to_user_id] =
[truncated] =
[id] = 23141738445
[entities] = Array
(
[hashtags] = Array
(
)

[user_mentions] = Array
(
[0] = Array
(
[screen_name] = TMobile_NL
[indices] = Array
(
[0] = 3
[1] = 14
)

[name] = T-Mobile Nieuws
[id] = 39199794
)

)

[urls] = Array
(
[0] = Array
(
[expanded_url] =
[indices] = Array
(
[0] = 113
[1] = 133
)

[url] = http://bit.ly/9P9LEv
)

)

)

[retweetid] = 0
)

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en


[twitter-dev] Re: Streaming api returning 401 error on phrase tracking(logical AND)

2010-08-31 Thread Karthik K
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: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en


Re: [twitter-dev] Re: Streaming api returning 401 error on phrase tracking(logical AND)

2010-08-31 Thread Tom van der Woerdt
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 your URL encoding is wrong. You should encode the space as
%20, not as +

Tom

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en


[twitter-dev] Re: Streaming API and lists

2010-08-12 Thread Decklin Foster
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 a list is 500 members, but we can only follow 400 user
ids
by default with the streaming API. Is there any way around this?


Re: [twitter-dev] Re: Streaming API and lists

2010-08-12 Thread Tom van der Woerdt
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 server to recreate the list.
 
 The limit for a list is 500 members, but we can only follow 400 user
 ids
 by default with the streaming API. Is there any way around this?

You could create two connections, but this is not allowed. So, no.
Although it depends on the type of application - if it is a server-based
application, you can request a raise of these limits.

Tom


[twitter-dev] Re: streaming API help (regular API works)

2010-08-09 Thread Tom
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 a question that has previously been answered -
 I tried searching the archives but to no avail.

 I am trying to get the 'sample' stream API working but am getting 401
 Unathorized errors.  For debugging purposes, I am using curl for now.
 The following command fails (401):

 curl 'http://stream.twitter.com/1/statuses/sample.json?
 delimited=length' -H 'Authorization: OAuth realm=Twitter API,
 oauth_nonce=24599946, oauth_timestamp=1281319798,
 oauth_consumer_key=, oauth_signature_method=HMAC-SHA1,
 oauth_version=1.0, oauth_token=175905996-
 JkrGAl8ZXCgIjeZl3o7fMCD8HbyfVeDbkP9Y13mX, oauth_signature=i
 %2BVzWX23sp5t8%2Fz0swJl%2FDHloOo%3D'

 However, I believe that my OAuth stuff is (hopefully) correct because
 the following command works, where I have reused the exact same OAuth
 header (all I changed was the URL):

 curl 'http://api.twitter.com/1/statuses/user_timeline.json'-H
 'Authorization: OAuth realm=Twitter API, oauth_nonce=24599946,
 oauth_timestamp=1281319798, oauth_consumer_key=,
 oauth_signature_method=HMAC-SHA1, oauth_version=1.0,
 oauth_token=175905996-JkrGAl8ZXCgIjeZl3o7fMCD8HbyfVeDbkP9Y13mX,
 oauth_signature=i%2BVzWX23sp5t8%2Fz0swJl%2FDHloOo%3D'

 So what does this mean?  Are the authentication requirements at all
 different for these two API calls?  In case its relevant, note that I
 am using my account's single access token to create these OAuth
 signatures as opposed to a real customer key/secret pair.  Any
 suggestions on what else I can do to try and debug this?

 Many thanks!
 - Ian


[twitter-dev] Re: Streaming API time drifting problem and possible solutions

2010-07-09 Thread Larry Zhang
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 that's not the 
 issue, you should absolutely check if you have simplejson with c extension 
 installed. The python included version is 1.9 which is decidedly slower than 
 the new 2.x branch. You might see json decoding load drop by 50% or more.

 Pascal

 On Jul 8, 2010, at 17:31 , Larry Zhang wrote:



  Hi everyone,

  I have a program calling the statuses/sample method of a garden hose
  of the Streaming API, and I am experiencing the following problem: the
  timestamps of the tweets that I downloaded constantly drift behind
  real-time, the time drift keeps increasing until it reaches around 25
  minutes, and then I get a timeout from the request, sleep for 5
  seconds and reset the connection. The time drift is also reset to 0
  when the connection is reset.

  One solution for this I have now is to proactively reset the
  connection more frequently, e.g., if I reconnect every 1 minute, the
  time drift I get will be at most 1 minute. But I am not sure whether
  this is allow by the API.

  So could anyone tell me if you have the same problem as mine or I am
  using the API in the wrong way. And is it OK to reset connection every
  minute?

  I am using Tweepy (http://github.com/joshthecoder/tweepy) as the
  library for accessing the Streaming API.

  Thanks a lot!
  -Larry


Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-29 Thread Mark McBride
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, Matt Harris thematthar...@twitter.com wrote:
 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, 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
 doing the signature verification thing huh?

 Thanks a lot for helping! (though TweetSharp has another problem of
 dropping off the stream connection prematurely... that's another topic
 to discuss after I do more poking)

 Regards,
 Wil

 On Jun 29, 12:49 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  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 for
  it
  that I'm unaware of. Without the source parameter, I'm able to make this
  call work.
 
  Taylor
 
 
 
  On Mon, Jun 28, 2010 at 9:40 AM, Wil willi...@gmail.com wrote:
   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: ufywbndxv0qevuh0
 
   Base String:
 
   POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
   %2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
   %3DTwitterConsumerKey%26oauth_nonce
   %3Dufywbndxv0qevuh0%26oauth_signature_method%3DHMAC-
   SHA1%26oauth_timestamp%3D1277742686%26oauth_token%3DTwitterAccessToken
   %26oauth_version%3D1.0%26source%3DWildfire%2520by%2520Implication
 
   Signature:
   YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D
 
   Packet Capture:
   - Http: Request, POST /1/statuses/filter.json , Using OAuth
   Authorization
      Command: POST
    + URI: /1/statuses/filter.json
      ProtocolVersion: HTTP/1.1
    - Authorization: OAuth
     + Authorization:  OAuth
 
  
   oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oa
   uth_nonce=ufywbndxv0qevuh0,oauth_timestamp=1277742686,oauth_signature_m
   ethod=HMAC-
  
   SHA1,oauth_signature=YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D,oauth_version=1.0,
     + ContentType:  application/x-www-form-urlencoded
      Host:  stream.twitter.com
      ContentLength:  51
 
   - Http: HTTP Payload, URL: /1/statuses/filter.json
    - payload: HttpContentType =  application/x-www-form-urlencoded
        source: Wildfire%20by%20Implication
       follow: 156934710
 
   It still looks correct though...
 
   Regards,
   Wil
 
   On Jun 29, 12:21 am, Wil willi...@gmail.com wrote:
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
   
%3DTwitterAccessToken%26oauth_version%3D1.0%26source%3DWildfire%2520by
%2520Implication
 
Signature (escaped):
rYGiA6H2UXog0nYOzTeUKwJSssM%3D
 
Authorization Header:
 
  
   oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oa
  
   uth_nonce=abcdefgh,oauth_timestamp=1277739588,oauth_signature_method=H
   MAC-
SHA1,oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM
%3D,oauth_version=1.0
 
Post content:
source=Wildfire%20by%20Implicationfollow=156934710
 
On Jun 28, 11:45 pm, Taylor Singletary
taylorsinglet...@twitter.com
wrote:
 
 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: TwitterAccessToken
 Access Token Secret: TwitterAccessTokenScret
 OAuth Nonce: abcdefgh
 OAuth Timestamp: 1277739588
 
 URL:http://stream.twitter.com/1/statuses/filter.json
 
 POST Body:
 follow=156934710source=Wildfire%20by%20Implication
 
 Assuming these exact values, the following should be the result:
 
 POST body:
 follow=156934710source=Wildfire%20by%20Implication
 
 Signature Base String:
 

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Taylor Singletary
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 j...@twitter.com wrote:

 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 than 5 minutes.
 The code works with the following which I've used:
 1) OAuth authentication methods
 2) statuses/user_timeline
 3) 1/favorites/create

 (3) is a bit wierd since TweetSharp sends favorite requests in this
 form:
 http://api.twitter.com/1/favorites/create/##.json

 and the POST body contains this:
 source=Wildfire%20by%20Implication

 Yet it still works. I haven't tried other things in TweetSharp that
 does POST though.
 I thought that it was probably the read/write permissions that's
 causing the problem because I initially set the App as read-only (I
 changed it to write-access when I implemented the favorite). I then
 recreated the client information with readwrite access. So I guess
 permissions weren't the problem.

 I did some packet sniffing to be extra sure that it's sending the data
 as POST... and I got this: (using Microsoft NetMon 3.3)
 - Http: Request, POST /1/statuses/filter.json , Using OAuth
 Authorization
Command: POST
  + URI: /1/statuses/filter.json
ProtocolVersion: HTTP/1.1
  - Authorization: OAuth
   - Authorization:  OAuth
 oauth_consumer_key=##,oauth_token=34216267-

 BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,oauth_timestamp=1277542341,oauth_signature_method=HMAC-
 SHA1,oauth_signature=PeKBoS3uYgL9p7oJ%2
  WhiteSpace:
  AuthorizationData: OAuth
 oauth_consumer_key=###,oauth_token=34216267-

 BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,oauth_timestamp=1277542341,oauth_signature_method=HMAC-
 SHA1,oauth_signature=PeKBoS3uYgL9p7o
  + ContentType:  application/x-www-form-urlencoded
Host:  stream.twitter.com
ContentLength:  51
Connection:  Keep-Alive
HeaderEnd: CRLF


 The next frame was the HTTP payload
 - Http: HTTP Payload, URL: /1/statuses/filter.json
  - payload: HttpContentType =  application/x-www-form-urlencoded
 source: softwarename
 follow: ###

 On Jun 26, 5:50 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  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 POSTing the POST body along with
 the
  request?
 
  Seems like you are really close.
 
 
 
  On Fri, Jun 25, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:
   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 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
 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;
 charset=ISO-8859-1/
 titleError 401 UNAUTHORIZED/title
 /head
 body
 h2HTTP ERROR: 401/h2
 pProblem accessing /1/statuses/filter.json. Reason:
 preUNAUTHORIZED/pre/p
 hr /ismallPowered by Jetty:///small/i
 
 Here's what I POSTed(oauth tokens are filtered out):
 
 REQUEST: POSThttp://stream.twitter.com/1/statuses/filter.json
 Authorization: OAuth
 
  
 oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth
   _timestamp=#,oauth_signature_method=HMAC-
 SHA1,oauth_signature=,oauth_version=1.0,
 Content-Type: application/x-www-form-urlencoded
 Vary: Accept-Encoding
 Connection: close
 
 source=softwarenamedelimited=1follow=156934710
 
 On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
  OAuthshould work fine onstream.twitter.com
 
  -John Kaluckihttp://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 tostream.twitter.com usingOAuth
   (particularly, I've been trying to access
  

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Wil
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-
SHA1%26oauth_timestamp%3D1277735188%26oauth_token%3D156934710-
J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
%3DWildfire%2520by%2520Implication

calculated signature: %2FgqbnKcwmnpFMGnqNUK3kr6waI0%3D

Sniffed authorization header:
oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
oauth_nonce=6qzbdouhrz40dqs4
oauth_timestamp=1277735291
oauth_signature_method=HMAC-SHA1
oauth_signature=2yRkYN7j8YpS0%2FgrFSNKnoCrk7Y%3D
oauth_version=1.0

You're right, something seems to be wrong with the signature. I'll
continue to investigate this

Regards,
Wil
On Jun 28, 10:23 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 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 j...@twitter.com wrote:
  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 than 5 minutes.
  The code works with the following which I've used:
  1) OAuth authentication methods
  2) statuses/user_timeline
  3) 1/favorites/create

  (3) is a bit wierd since TweetSharp sends favorite requests in this
  form:
 http://api.twitter.com/1/favorites/create/##.json

  and the POST body contains this:
  source=Wildfire%20by%20Implication

  Yet it still works. I haven't tried other things in TweetSharp that
  does POST though.
  I thought that it was probably the read/write permissions that's
  causing the problem because I initially set the App as read-only (I
  changed it to write-access when I implemented the favorite). I then
  recreated the client information with readwrite access. So I guess
  permissions weren't the problem.

  I did some packet sniffing to be extra sure that it's sending the data
  as POST... and I got this: (using Microsoft NetMon 3.3)
  - Http: Request, POST /1/statuses/filter.json , Using OAuth
  Authorization
     Command: POST
   + URI: /1/statuses/filter.json
     ProtocolVersion: HTTP/1.1
   - Authorization: OAuth
    - Authorization:  OAuth
  oauth_consumer_key=##,oauth_token=34216267-

  BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
   auth_timestamp=1277542341,oauth_signature_method=HMAC-
  SHA1,oauth_signature=PeKBoS3uYgL9p7oJ%2
       WhiteSpace:
       AuthorizationData: OAuth
  oauth_consumer_key=###,oauth_token=34216267-

  BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
   auth_timestamp=1277542341,oauth_signature_method=HMAC-
  SHA1,oauth_signature=PeKBoS3uYgL9p7o
   + ContentType:  application/x-www-form-urlencoded
     Host:  stream.twitter.com
     ContentLength:  51
     Connection:  Keep-Alive
     HeaderEnd: CRLF

  The next frame was the HTTP payload
  - Http: HTTP Payload, URL: /1/statuses/filter.json
   - payload: HttpContentType =  application/x-www-form-urlencoded
      source: softwarename
      follow: ###

  On Jun 26, 5:50 am, Taylor Singletary taylorsinglet...@twitter.com
  wrote:
   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 POSTing the POST body along with
  the
   request?

   Seems like you are really close.

   On Fri, Jun 25, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:
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 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
  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;
  charset=ISO-8859-1/
  titleError 401 UNAUTHORIZED/title
  /head
  body
  h2HTTP ERROR: 401/h2
  pProblem accessing /1/statuses/filter.json. 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Wil
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
%3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce%3Deodjuo8ystdcyl3f
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1277736634%26oauth_token%3D156934710-
J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
%3DWildfire%2520by%2520Implication

Signature:
nt%2F5itdHGoVr8gRloaBOakSmUbM%3D

Sent:
oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
oauth_nonce=eodjuo8ystdcyl3f
oauth_timestamp=1277736634
oauth_signature_method=HMAC-SHA1
oauth_signature=nt%2F5itdHGoVr8gRloaBOakSmUbM%3D
oauth_version=1.0


On Jun 28, 10:35 pm, Wil willi...@gmail.com wrote:
 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-
 SHA1%26oauth_timestamp%3D1277735188%26oauth_token%3D156934710-
 J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
 %3DWildfire%2520by%2520Implication

 calculated signature: %2FgqbnKcwmnpFMGnqNUK3kr6waI0%3D

 Sniffed authorization header:
 oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
 oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
 oauth_nonce=6qzbdouhrz40dqs4
 oauth_timestamp=1277735291
 oauth_signature_method=HMAC-SHA1
 oauth_signature=2yRkYN7j8YpS0%2FgrFSNKnoCrk7Y%3D
 oauth_version=1.0

 You're right, something seems to be wrong with the signature. I'll
 continue to investigate this

 Regards,
 Wil
 On Jun 28, 10:23 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:



  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 j...@twitter.com wrote:
   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 than 5 minutes.
   The code works with the following which I've used:
   1)OAuthauthentication methods
   2) statuses/user_timeline
   3) 1/favorites/create

   (3) is a bit wierd since TweetSharp sends favorite requests in this
   form:
  http://api.twitter.com/1/favorites/create/##.json

   and the POST body contains this:
   source=Wildfire%20by%20Implication

   Yet it still works. I haven't tried other things in TweetSharp that
   does POST though.
   I thought that it was probably the read/write permissions that's
   causing the problem because I initially set the App as read-only (I
   changed it to write-access when I implemented the favorite). I then
   recreated the client information with readwrite access. So I guess
   permissions weren't the problem.

   I did some packet sniffing to be extra sure that it's sending the data
   as POST... and I got this: (using Microsoft NetMon 3.3)
   - Http: Request, POST /1/statuses/filter.json , UsingOAuth
   Authorization
      Command: POST
    + URI: /1/statuses/filter.json
      ProtocolVersion: HTTP/1.1
    - Authorization:OAuth
     - Authorization:  OAuth
   oauth_consumer_key=##,oauth_token=34216267-

   BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
auth_timestamp=1277542341,oauth_signature_method=HMAC-
   SHA1,oauth_signature=PeKBoS3uYgL9p7oJ%2
        WhiteSpace:
        AuthorizationData:OAuth
   oauth_consumer_key=###,oauth_token=34216267-

   BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
auth_timestamp=1277542341,oauth_signature_method=HMAC-
   SHA1,oauth_signature=PeKBoS3uYgL9p7o
    + ContentType:  application/x-www-form-urlencoded
      Host:  stream.twitter.com
      ContentLength:  51
      Connection:  Keep-Alive
      HeaderEnd: CRLF

   The next frame was the HTTP payload
   - Http: HTTP Payload, URL: /1/statuses/filter.json
    - payload: HttpContentType =  application/x-www-form-urlencoded
       source: softwarename
       follow: ###

   On Jun 26, 5:50 am, Taylor Singletary taylorsinglet...@twitter.com
   wrote:
Wil,

Does yourOAuthcode 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 POSTing the POST body along 
with
   the
request?


[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Wil
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:
 POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
 %2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
 %3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce%3Deodjuo8ystdcyl3f
 %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
 %3D1277736634%26oauth_token%3D156934710-
 J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
 %3DWildfire%2520by%2520Implication

 Signature:
 nt%2F5itdHGoVr8gRloaBOakSmUbM%3D

 Sent:
 oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
 oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
 oauth_nonce=eodjuo8ystdcyl3f
 oauth_timestamp=1277736634
 oauth_signature_method=HMAC-SHA1
 oauth_signature=nt%2F5itdHGoVr8gRloaBOakSmUbM%3D
 oauth_version=1.0

 On Jun 28, 10:35 pm, Wil willi...@gmail.com wrote:



  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-
  SHA1%26oauth_timestamp%3D1277735188%26oauth_token%3D156934710-
  J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
  %3DWildfire%2520by%2520Implication

  calculated signature: %2FgqbnKcwmnpFMGnqNUK3kr6waI0%3D

  Sniffed authorization header:
  oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
  oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
  oauth_nonce=6qzbdouhrz40dqs4
  oauth_timestamp=1277735291
  oauth_signature_method=HMAC-SHA1
  oauth_signature=2yRkYN7j8YpS0%2FgrFSNKnoCrk7Y%3D
  oauth_version=1.0

  You're right, something seems to be wrong with the signature. I'll
  continue to investigate this

  Regards,
  Wil
  On Jun 28, 10:23 pm, Taylor Singletary taylorsinglet...@twitter.com
  wrote:

   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 j...@twitter.com wrote:
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 than 5 minutes.
The code works with the following which I've used:
1)OAuthauthentication methods
2) statuses/user_timeline
3) 1/favorites/create

(3) is a bit wierd since TweetSharp sends favorite requests in this
form:
   http://api.twitter.com/1/favorites/create/##.json

and the POST body contains this:
source=Wildfire%20by%20Implication

Yet it still works. I haven't tried other things in TweetSharp that
does POST though.
I thought that it was probably the read/write permissions that's
causing the problem because I initially set the App as read-only (I
changed it to write-access when I implemented the favorite). I then
recreated the client information with readwrite access. So I guess
permissions weren't the problem.

I did some packet sniffing to be extra sure that it's sending the data
as POST... and I got this: (using Microsoft NetMon 3.3)
- Http: Request, POST /1/statuses/filter.json , UsingOAuth
Authorization
   Command: POST
 + URI: /1/statuses/filter.json
   ProtocolVersion: HTTP/1.1
 - Authorization:OAuth
  - Authorization:  OAuth
oauth_consumer_key=##,oauth_token=34216267-

BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
 auth_timestamp=1277542341,oauth_signature_method=HMAC-
SHA1,oauth_signature=PeKBoS3uYgL9p7oJ%2
     WhiteSpace:
     AuthorizationData:OAuth
oauth_consumer_key=###,oauth_token=34216267-

BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
 auth_timestamp=1277542341,oauth_signature_method=HMAC-
SHA1,oauth_signature=PeKBoS3uYgL9p7o
 + ContentType:  application/x-www-form-urlencoded
   Host:  stream.twitter.com
   ContentLength:  51
   Connection:  Keep-Alive
   HeaderEnd: CRLF

The next frame was the HTTP payload
- Http: HTTP Payload, URL: /1/statuses/filter.json
 - payload: HttpContentType =  application/x-www-form-urlencoded
    source: softwarename
    follow: ###

On Jun 26, 5:50 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 Wil,

 Does yourOAuthcode work against other aspects of the Twitter API? Can
you
 verify if your system's clock is within 5 

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Taylor Singletary
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 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
  %3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce%3Deodjuo8ystdcyl3f
  %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
  %3D1277736634%26oauth_token%3D156934710-
  J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
  %3DWildfire%2520by%2520Implication
 
  Signature:
  nt%2F5itdHGoVr8gRloaBOakSmUbM%3D
 
  Sent:
  oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
  oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
  oauth_nonce=eodjuo8ystdcyl3f
  oauth_timestamp=1277736634
  oauth_signature_method=HMAC-SHA1
  oauth_signature=nt%2F5itdHGoVr8gRloaBOakSmUbM%3D
  oauth_version=1.0
 
  On Jun 28, 10:35 pm, Wil willi...@gmail.com wrote:
 
 
 
   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-
   SHA1%26oauth_timestamp%3D1277735188%26oauth_token%3D156934710-
   J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
   %3DWildfire%2520by%2520Implication
 
   calculated signature: %2FgqbnKcwmnpFMGnqNUK3kr6waI0%3D
 
   Sniffed authorization header:
   oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
   oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
   oauth_nonce=6qzbdouhrz40dqs4
   oauth_timestamp=1277735291
   oauth_signature_method=HMAC-SHA1
   oauth_signature=2yRkYN7j8YpS0%2FgrFSNKnoCrk7Y%3D
   oauth_version=1.0
 
   You're right, something seems to be wrong with the signature. I'll
   continue to investigate this
 
   Regards,
   Wil
   On Jun 28, 10:23 pm, Taylor Singletary taylorsinglet...@twitter.com
   wrote:
 
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 j...@twitter.com
 wrote:
 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 than 5 minutes.
 The code works with the following which I've used:
 1)OAuthauthentication methods
 2) statuses/user_timeline
 3) 1/favorites/create
 
 (3) is a bit wierd since TweetSharp sends favorite requests in
 this
 form:
http://api.twitter.com/1/favorites/create/##.json
 
 and the POST body contains this:
 source=Wildfire%20by%20Implication
 
 Yet it still works. I haven't tried other things in TweetSharp
 that
 does POST though.
 I thought that it was probably the read/write permissions that's
 causing the problem because I initially set the App as read-only
 (I
 changed it to write-access when I implemented the favorite). I
 then
 recreated the client information with readwrite access. So I
 guess
 permissions weren't the problem.
 
 I did some packet sniffing to be extra sure that it's sending the
 data
 as POST... and I got this: (using Microsoft NetMon 3.3)
 - Http: Request, POST /1/statuses/filter.json , UsingOAuth
 Authorization
Command: POST
  + URI: /1/statuses/filter.json
ProtocolVersion: HTTP/1.1
  - Authorization:OAuth
   - Authorization:  OAuth
 oauth_consumer_key=##,oauth_token=34216267-
 

 BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
 auth_timestamp=1277542341,oauth_signature_method=HMAC-
 SHA1,oauth_signature=PeKBoS3uYgL9p7oJ%2
  WhiteSpace:
  AuthorizationData:OAuth
 oauth_consumer_key=###,oauth_token=34216267-
 

 BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
 auth_timestamp=1277542341,oauth_signature_method=HMAC-
 SHA1,oauth_signature=PeKBoS3uYgL9p7o
  + ContentType:  application/x-www-form-urlencoded
Host:  stream.twitter.com
ContentLength:  51
Connection:  Keep-Alive
HeaderEnd: CRLF
 
 The next frame was the HTTP payload
 - Http: HTTP Payload, URL: /1/statuses/filter.json
  - payload: HttpContentType =  application/x-www-form-urlencoded
 source: 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Wil
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 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
  %3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce%3Deodjuo8ystdcyl3f
  %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
  %3D1277736634%26oauth_token%3D156934710-
  J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
  %3DWildfire%2520by%2520Implication

  Signature:
  nt%2F5itdHGoVr8gRloaBOakSmUbM%3D

  Sent:
  oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
  oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
  oauth_nonce=eodjuo8ystdcyl3f
  oauth_timestamp=1277736634
  oauth_signature_method=HMAC-SHA1
  oauth_signature=nt%2F5itdHGoVr8gRloaBOakSmUbM%3D
  oauth_version=1.0

  On Jun 28, 10:35 pm, Wil willi...@gmail.com wrote:

   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-
   SHA1%26oauth_timestamp%3D1277735188%26oauth_token%3D156934710-
   J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
   %3DWildfire%2520by%2520Implication

   calculated signature: %2FgqbnKcwmnpFMGnqNUK3kr6waI0%3D

   Sniffed authorization header:
   oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
   oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
   oauth_nonce=6qzbdouhrz40dqs4
   oauth_timestamp=1277735291
   oauth_signature_method=HMAC-SHA1
   oauth_signature=2yRkYN7j8YpS0%2FgrFSNKnoCrk7Y%3D
   oauth_version=1.0

   You're right, something seems to be wrong with the signature. I'll
   continue to investigate this

   Regards,
   Wil
   On Jun 28, 10:23 pm, Taylor Singletary taylorsinglet...@twitter.com
   wrote:

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 j...@twitter.com wrote:
 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 than 5 minutes.
 The code works with the following which I've used:
 1)OAuthauthentication methods
 2) statuses/user_timeline
 3) 1/favorites/create

 (3) is a bit wierd since TweetSharp sends favorite requests in this
 form:
http://api.twitter.com/1/favorites/create/##.json

 and the POST body contains this:
 source=Wildfire%20by%20Implication

 Yet it still works. I haven't tried other things in TweetSharp that
 does POST though.
 I thought that it was probably the read/write permissions that's
 causing the problem because I initially set the App as read-only (I
 changed it to write-access when I implemented the favorite). I then
 recreated the client information with readwrite access. So I guess
 permissions weren't the problem.

 I did some packet sniffing to be extra sure that it's sending the 
 data
 as POST... and I got this: (using Microsoft NetMon 3.3)
 - Http: Request, POST /1/statuses/filter.json , UsingOAuth
 Authorization
    Command: POST
  + URI: /1/statuses/filter.json
    ProtocolVersion: HTTP/1.1
  - Authorization:OAuth
   - Authorization:  OAuth
 oauth_consumer_key=##,oauth_token=34216267-

 BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
  auth_timestamp=1277542341,oauth_signature_method=HMAC-
 SHA1,oauth_signature=PeKBoS3uYgL9p7oJ%2
      WhiteSpace:
      AuthorizationData:OAuth
 oauth_consumer_key=###,oauth_token=34216267-

 BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,o
  auth_timestamp=1277542341,oauth_signature_method=HMAC-
 SHA1,oauth_signature=PeKBoS3uYgL9p7o
  + ContentType:  application/x-www-form-urlencoded
    Host:  stream.twitter.com
    ContentLength:  51
    Connection:  Keep-Alive
    HeaderEnd: CRLF

 The next frame was the HTTP payload
 - Http: HTTP Payload, URL: /1/statuses/filter.json
  - payload: HttpContentType =  application/x-www-form-urlencoded
     source: 

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Taylor Singletary
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: TwitterAccessToken
Access Token Secret: TwitterAccessTokenScret
OAuth Nonce: abcdefgh
OAuth Timestamp: 1277739588

URL:
http://stream.twitter.com/1/statuses/filter.json

POST Body:
follow=156934710source=Wildfire%20by%20Implication

Assuming these exact values, the following should be the result:

POST body:
follow=156934710source=Wildfire%20by%20Implication

Signature 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%3DTwitterAccessToken%26oauth_version%3D1.0%26source%3DWildfire%2520by%2520Implication

Signing Secret
TwitterConsumerSecretTwitterAccessTokenSecret

Signature
rYGiA6H2UXog0nYOzTeUKwJSssM=

Authorization Header
OAuth oauth_nonce=abcdefgh, oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1277739588, oauth_consumer_key=TwitterConsumerKey,
oauth_token=TwitterAccessToken,
oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM%3D, oauth_version=1.0

Using these values do you get the same signature and other values?

Taylor

On Mon, Jun 28, 2010 at 8:21 AM, Wil willi...@gmail.com wrote:

 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 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
   %3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce%3Deodjuo8ystdcyl3f
   %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
   %3D1277736634%26oauth_token%3D156934710-
   J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
   %3DWildfire%2520by%2520Implication
 
   Signature:
   nt%2F5itdHGoVr8gRloaBOakSmUbM%3D
 
   Sent:
   oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
   oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
   oauth_nonce=eodjuo8ystdcyl3f
   oauth_timestamp=1277736634
   oauth_signature_method=HMAC-SHA1
   oauth_signature=nt%2F5itdHGoVr8gRloaBOakSmUbM%3D
   oauth_version=1.0
 
   On Jun 28, 10:35 pm, Wil willi...@gmail.com wrote:
 
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-
SHA1%26oauth_timestamp%3D1277735188%26oauth_token%3D156934710-
   
 J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
%3DWildfire%2520by%2520Implication
 
calculated signature: %2FgqbnKcwmnpFMGnqNUK3kr6waI0%3D
 
Sniffed authorization header:
oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
oauth_nonce=6qzbdouhrz40dqs4
oauth_timestamp=1277735291
oauth_signature_method=HMAC-SHA1
oauth_signature=2yRkYN7j8YpS0%2FgrFSNKnoCrk7Y%3D
oauth_version=1.0
 
You're right, something seems to be wrong with the signature. I'll
continue to investigate this
 
Regards,
Wil
On Jun 28, 10:23 pm, Taylor Singletary taylorsinglet...@twitter.com
 
wrote:
 
 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 j...@twitter.com
 wrote:
  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 than 5 minutes.
  The code works with the following which I've used:
  1)OAuthauthentication methods
  2) statuses/user_timeline
  3) 1/favorites/create
 
  (3) is a bit wierd since TweetSharp sends favorite requests in
 this
  form:
 http://api.twitter.com/1/favorites/create/##.json
 
  and the POST body contains this:
  source=Wildfire%20by%20Implication
 
  Yet it still works. I haven't tried other things in TweetSharp
 that
  does POST though.
  I 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Wil
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
%3DTwitterAccessToken%26oauth_version%3D1.0%26source%3DWildfire%2520by
%2520Implication

Signature (escaped):
rYGiA6H2UXog0nYOzTeUKwJSssM%3D

Authorization Header:
oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oauth_nonce=abcdefgh,oauth_timestamp=1277739588,oauth_signature_method=HMAC-
SHA1,oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM
%3D,oauth_version=1.0

Post content:
source=Wildfire%20by%20Implicationfollow=156934710


On Jun 28, 11:45 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 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: TwitterAccessToken
 Access Token Secret: TwitterAccessTokenScret
 OAuth Nonce: abcdefgh
 OAuth Timestamp: 1277739588

 URL:http://stream.twitter.com/1/statuses/filter.json

 POST Body:
 follow=156934710source=Wildfire%20by%20Implication

 Assuming these exact values, the following should be the result:

 POST body:
 follow=156934710source=Wildfire%20by%20Implication

 Signature Base String:
 POSThttp%3A%2F%2Fstream.twitter.com
 %2F1%2Fstatuses%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key%3DTwi 
 tterConsumerKey%26oauth_nonce%3Dabcdefgh%26oauth_signature_method%3DHMAC-SH 
 A1%26oauth_timestamp%3D1277739588%26oauth_token%3DTwitterAccessToken%26oaut 
 h_version%3D1.0%26source%3DWildfire%2520by%2520Implication

 Signing Secret
 TwitterConsumerSecretTwitterAccessTokenSecret

 Signature
 rYGiA6H2UXog0nYOzTeUKwJSssM=

 Authorization Header
 OAuth oauth_nonce=abcdefgh, oauth_signature_method=HMAC-SHA1,
 oauth_timestamp=1277739588, oauth_consumer_key=TwitterConsumerKey,
 oauth_token=TwitterAccessToken,
 oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM%3D, oauth_version=1.0

 Using these values do you get the same signature and other values?

 Taylor



 On Mon, Jun 28, 2010 at 8:21 AM, Wil willi...@gmail.com wrote:
  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 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
%3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce%3Deodjuo8ystdcyl3f
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1277736634%26oauth_token%3D156934710-
J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
%3DWildfire%2520by%2520Implication

Signature:
nt%2F5itdHGoVr8gRloaBOakSmUbM%3D

Sent:
oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
oauth_nonce=eodjuo8ystdcyl3f
oauth_timestamp=1277736634
oauth_signature_method=HMAC-SHA1
oauth_signature=nt%2F5itdHGoVr8gRloaBOakSmUbM%3D
oauth_version=1.0

On Jun 28, 10:35 pm, Wil willi...@gmail.com wrote:

 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-
 SHA1%26oauth_timestamp%3D1277735188%26oauth_token%3D156934710-

  J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
 %3DWildfire%2520by%2520Implication

 calculated signature: %2FgqbnKcwmnpFMGnqNUK3kr6waI0%3D

 Sniffed authorization header:
 oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
 oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
 oauth_nonce=6qzbdouhrz40dqs4
 oauth_timestamp=1277735291
 oauth_signature_method=HMAC-SHA1
 oauth_signature=2yRkYN7j8YpS0%2FgrFSNKnoCrk7Y%3D
 oauth_version=1.0

 You're right, something seems to be wrong with the signature. I'll
 continue to investigate this

 Regards,
 Wil
 On Jun 28, 10:23 pm, Taylor Singletary taylorsinglet...@twitter.com

 wrote:

  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 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Wil
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: ufywbndxv0qevuh0

Base String:

POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
%3DTwitterConsumerKey%26oauth_nonce
%3Dufywbndxv0qevuh0%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1277742686%26oauth_token%3DTwitterAccessToken
%26oauth_version%3D1.0%26source%3DWildfire%2520by%2520Implication

Signature:
YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D

Packet Capture:
- Http: Request, POST /1/statuses/filter.json , Using OAuth
Authorization
Command: POST
  + URI: /1/statuses/filter.json
ProtocolVersion: HTTP/1.1
  - Authorization: OAuth
   + Authorization:  OAuth
oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oauth_nonce=ufywbndxv0qevuh0,oauth_timestamp=1277742686,oauth_signature_method=HMAC-
SHA1,oauth_signature=YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D,oauth_version=1.0,
  + ContentType:  application/x-www-form-urlencoded
Host:  stream.twitter.com
ContentLength:  51

- Http: HTTP Payload, URL: /1/statuses/filter.json
  - payload: HttpContentType =  application/x-www-form-urlencoded
 source: Wildfire%20by%20Implication
 follow: 156934710


It still looks correct though...

Regards,
Wil

On Jun 29, 12:21 am, Wil willi...@gmail.com wrote:
 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
 %3DTwitterAccessToken%26oauth_version%3D1.0%26source%3DWildfire%2520by
 %2520Implication

 Signature (escaped):
 rYGiA6H2UXog0nYOzTeUKwJSssM%3D

 Authorization Header:
 oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oa 
 uth_nonce=abcdefgh,oauth_timestamp=1277739588,oauth_signature_method=H 
 MAC-
 SHA1,oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM
 %3D,oauth_version=1.0

 Post content:
 source=Wildfire%20by%20Implicationfollow=156934710

 On Jun 28, 11:45 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:



  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: TwitterAccessToken
  Access Token Secret: TwitterAccessTokenScret
  OAuth Nonce: abcdefgh
  OAuth Timestamp: 1277739588

  URL:http://stream.twitter.com/1/statuses/filter.json

  POST Body:
  follow=156934710source=Wildfire%20by%20Implication

  Assuming these exact values, the following should be the result:

  POST body:
  follow=156934710source=Wildfire%20by%20Implication

  Signature Base String:
  POSThttp%3A%2F%2Fstream.twitter.com
  %2F1%2Fstatuses%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key%3DTwi 
  tterConsumerKey%26oauth_nonce%3Dabcdefgh%26oauth_signature_method%3DHMAC-SH 
  A1%26oauth_timestamp%3D1277739588%26oauth_token%3DTwitterAccessToken%26oaut 
  h_version%3D1.0%26source%3DWildfire%2520by%2520Implication

  Signing Secret
  TwitterConsumerSecretTwitterAccessTokenSecret

  Signature
  rYGiA6H2UXog0nYOzTeUKwJSssM=

  Authorization Header
  OAuth oauth_nonce=abcdefgh, oauth_signature_method=HMAC-SHA1,
  oauth_timestamp=1277739588, oauth_consumer_key=TwitterConsumerKey,
  oauth_token=TwitterAccessToken,
  oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM%3D, oauth_version=1.0

  Using these values do you get the same signature and other values?

  Taylor

  On Mon, Jun 28, 2010 at 8:21 AM, Wil willi...@gmail.com wrote:
   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 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
 %3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce%3Deodjuo8ystdcyl3f
 %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
 %3D1277736634%26oauth_token%3D156934710-
 J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E%26oauth_version%3D1.0%26source
 %3DWildfire%2520by%2520Implication

 Signature:
 nt%2F5itdHGoVr8gRloaBOakSmUbM%3D

 Sent:
 oauth_consumer_key=rHYIlqotmSfiGc6OfFtw
 oauth_token=156934710-J4HkTzZOaHk7ZBnXPzmqopoQS9pm2NjDJmMDEw4E
 

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Taylor Singletary
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 for it
that I'm unaware of. Without the source parameter, I'm able to make this
call work.

Taylor

On Mon, Jun 28, 2010 at 9:40 AM, Wil willi...@gmail.com wrote:

 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: ufywbndxv0qevuh0

 Base String:

 POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
 %2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
 %3DTwitterConsumerKey%26oauth_nonce
 %3Dufywbndxv0qevuh0%26oauth_signature_method%3DHMAC-
 SHA1%26oauth_timestamp%3D1277742686%26oauth_token%3DTwitterAccessToken
 %26oauth_version%3D1.0%26source%3DWildfire%2520by%2520Implication

 Signature:
 YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D

 Packet Capture:
 - Http: Request, POST /1/statuses/filter.json , Using OAuth
 Authorization
Command: POST
  + URI: /1/statuses/filter.json
ProtocolVersion: HTTP/1.1
  - Authorization: OAuth
   + Authorization:  OAuth

 oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oauth_nonce=ufywbndxv0qevuh0,oauth_timestamp=1277742686,oauth_signature_method=HMAC-
 SHA1,oauth_signature=YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D,oauth_version=1.0,
   + ContentType:  application/x-www-form-urlencoded
Host:  stream.twitter.com
ContentLength:  51

 - Http: HTTP Payload, URL: /1/statuses/filter.json
  - payload: HttpContentType =  application/x-www-form-urlencoded
  source: Wildfire%20by%20Implication
 follow: 156934710


 It still looks correct though...

 Regards,
 Wil

 On Jun 29, 12:21 am, Wil willi...@gmail.com wrote:
  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
  %3DTwitterAccessToken%26oauth_version%3D1.0%26source%3DWildfire%2520by
  %2520Implication
 
  Signature (escaped):
  rYGiA6H2UXog0nYOzTeUKwJSssM%3D
 
  Authorization Header:
 
 oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oa
 uth_nonce=abcdefgh,oauth_timestamp=1277739588,oauth_signature_method=H
 MAC-
  SHA1,oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM
  %3D,oauth_version=1.0
 
  Post content:
  source=Wildfire%20by%20Implicationfollow=156934710
 
  On Jun 28, 11:45 pm, Taylor Singletary taylorsinglet...@twitter.com
  wrote:
 
 
 
   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: TwitterAccessToken
   Access Token Secret: TwitterAccessTokenScret
   OAuth Nonce: abcdefgh
   OAuth Timestamp: 1277739588
 
   URL:http://stream.twitter.com/1/statuses/filter.json
 
   POST Body:
   follow=156934710source=Wildfire%20by%20Implication
 
   Assuming these exact values, the following should be the result:
 
   POST body:
   follow=156934710source=Wildfire%20by%20Implication
 
   Signature Base String:
   POSThttp%3A%2F%2Fstream.twitter.com
  
 %2F1%2Fstatuses%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key%3DTwi
 tterConsumerKey%26oauth_nonce%3Dabcdefgh%26oauth_signature_method%3DHMAC-SH
 A1%26oauth_timestamp%3D1277739588%26oauth_token%3DTwitterAccessToken%26oaut
 h_version%3D1.0%26source%3DWildfire%2520by%2520Implication
 
   Signing Secret
   TwitterConsumerSecretTwitterAccessTokenSecret
 
   Signature
   rYGiA6H2UXog0nYOzTeUKwJSssM=
 
   Authorization Header
   OAuth oauth_nonce=abcdefgh, oauth_signature_method=HMAC-SHA1,
   oauth_timestamp=1277739588, oauth_consumer_key=TwitterConsumerKey,
   oauth_token=TwitterAccessToken,
   oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM%3D, oauth_version=1.0
 
   Using these values do you get the same signature and other values?
 
   Taylor
 
   On Mon, Jun 28, 2010 at 8:21 AM, Wil willi...@gmail.com wrote:
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 couple more tests just to be sure and the
 signatures
  match the sent sniffed one guess I missed something
 previously...
 
  Base:
  

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Wil
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
doing the signature verification thing huh?

Thanks a lot for helping! (though TweetSharp has another problem of
dropping off the stream connection prematurely... that's another topic
to discuss after I do more poking)

Regards,
Wil

On Jun 29, 12:49 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 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 for it
 that I'm unaware of. Without the source parameter, I'm able to make this
 call work.

 Taylor



 On Mon, Jun 28, 2010 at 9:40 AM, Wil willi...@gmail.com wrote:
  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: ufywbndxv0qevuh0

  Base String:

  POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
  %2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
  %3DTwitterConsumerKey%26oauth_nonce
  %3Dufywbndxv0qevuh0%26oauth_signature_method%3DHMAC-
  SHA1%26oauth_timestamp%3D1277742686%26oauth_token%3DTwitterAccessToken
  %26oauth_version%3D1.0%26source%3DWildfire%2520by%2520Implication

  Signature:
  YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D

  Packet Capture:
  - Http: Request, POST /1/statuses/filter.json , Using OAuth
  Authorization
     Command: POST
   + URI: /1/statuses/filter.json
     ProtocolVersion: HTTP/1.1
   - Authorization: OAuth
    + Authorization:  OAuth

  oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oa 
  uth_nonce=ufywbndxv0qevuh0,oauth_timestamp=1277742686,oauth_signature_m 
  ethod=HMAC-
  SHA1,oauth_signature=YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D,oauth_version=1.0,
    + ContentType:  application/x-www-form-urlencoded
     Host:  stream.twitter.com
     ContentLength:  51

  - Http: HTTP Payload, URL: /1/statuses/filter.json
   - payload: HttpContentType =  application/x-www-form-urlencoded
       source: Wildfire%20by%20Implication
      follow: 156934710

  It still looks correct though...

  Regards,
  Wil

  On Jun 29, 12:21 am, Wil willi...@gmail.com wrote:
   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
   %3DTwitterAccessToken%26oauth_version%3D1.0%26source%3DWildfire%2520by
   %2520Implication

   Signature (escaped):
   rYGiA6H2UXog0nYOzTeUKwJSssM%3D

   Authorization Header:

  oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oa
  uth_nonce=abcdefgh,oauth_timestamp=1277739588,oauth_signature_method=H
  MAC-
   SHA1,oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM
   %3D,oauth_version=1.0

   Post content:
   source=Wildfire%20by%20Implicationfollow=156934710

   On Jun 28, 11:45 pm, Taylor Singletary taylorsinglet...@twitter.com
   wrote:

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: TwitterAccessToken
Access Token Secret: TwitterAccessTokenScret
OAuth Nonce: abcdefgh
OAuth Timestamp: 1277739588

URL:http://stream.twitter.com/1/statuses/filter.json

POST Body:
follow=156934710source=Wildfire%20by%20Implication

Assuming these exact values, the following should be the result:

POST body:
follow=156934710source=Wildfire%20by%20Implication

Signature Base String:
POSThttp%3A%2F%2Fstream.twitter.com

  %2F1%2Fstatuses%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key%3DTwi
  tterConsumerKey%26oauth_nonce%3Dabcdefgh%26oauth_signature_method%3DHMAC-SH
  A1%26oauth_timestamp%3D1277739588%26oauth_token%3DTwitterAccessToken%26oaut
  h_version%3D1.0%26source%3DWildfire%2520by%2520Implication

Signing Secret
TwitterConsumerSecretTwitterAccessTokenSecret

Signature
rYGiA6H2UXog0nYOzTeUKwJSssM=

Authorization Header
OAuth oauth_nonce=abcdefgh, oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1277739588, oauth_consumer_key=TwitterConsumerKey,
oauth_token=TwitterAccessToken,

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-28 Thread Matt Harris
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, 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
 doing the signature verification thing huh?

 Thanks a lot for helping! (though TweetSharp has another problem of
 dropping off the stream connection prematurely... that's another topic
 to discuss after I do more poking)

 Regards,
 Wil

 On Jun 29, 12:49 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  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 for
 it
  that I'm unaware of. Without the source parameter, I'm able to make this
  call work.
 
  Taylor
 
 
 
  On Mon, Jun 28, 2010 at 9:40 AM, Wil willi...@gmail.com wrote:
   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: ufywbndxv0qevuh0
 
   Base String:
 
   POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
   %2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
   %3DTwitterConsumerKey%26oauth_nonce
   %3Dufywbndxv0qevuh0%26oauth_signature_method%3DHMAC-
   SHA1%26oauth_timestamp%3D1277742686%26oauth_token%3DTwitterAccessToken
   %26oauth_version%3D1.0%26source%3DWildfire%2520by%2520Implication
 
   Signature:
   YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D
 
   Packet Capture:
   - Http: Request, POST /1/statuses/filter.json , Using OAuth
   Authorization
  Command: POST
+ URI: /1/statuses/filter.json
  ProtocolVersion: HTTP/1.1
- Authorization: OAuth
 + Authorization:  OAuth
 
  
 oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oa
 uth_nonce=ufywbndxv0qevuh0,oauth_timestamp=1277742686,oauth_signature_m
 ethod=HMAC-
  
 SHA1,oauth_signature=YRXJUMYs0bRzkDZSTXesGfIWhQ8%3D,oauth_version=1.0,
 + ContentType:  application/x-www-form-urlencoded
  Host:  stream.twitter.com
  ContentLength:  51
 
   - Http: HTTP Payload, URL: /1/statuses/filter.json
- payload: HttpContentType =  application/x-www-form-urlencoded
source: Wildfire%20by%20Implication
   follow: 156934710
 
   It still looks correct though...
 
   Regards,
   Wil
 
   On Jun 29, 12:21 am, Wil willi...@gmail.com wrote:
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
   
 %3DTwitterAccessToken%26oauth_version%3D1.0%26source%3DWildfire%2520by
%2520Implication
 
Signature (escaped):
rYGiA6H2UXog0nYOzTeUKwJSssM%3D
 
Authorization Header:
 
  
 oauth_consumer_key=TwitterConsumerKey,oauth_token=TwitterAccessToken,oa
  
 uth_nonce=abcdefgh,oauth_timestamp=1277739588,oauth_signature_method=H
   MAC-
SHA1,oauth_signature=rYGiA6H2UXog0nYOzTeUKwJSssM
%3D,oauth_version=1.0
 
Post content:
source=Wildfire%20by%20Implicationfollow=156934710
 
On Jun 28, 11:45 pm, Taylor Singletary taylorsinglet...@twitter.com
 
wrote:
 
 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: TwitterAccessToken
 Access Token Secret: TwitterAccessTokenScret
 OAuth Nonce: abcdefgh
 OAuth Timestamp: 1277739588
 
 URL:http://stream.twitter.com/1/statuses/filter.json
 
 POST Body:
 follow=156934710source=Wildfire%20by%20Implication
 
 Assuming these exact values, the following should be the result:
 
 POST body:
 follow=156934710source=Wildfire%20by%20Implication
 
 Signature Base String:
 POSThttp%3A%2F%2Fstream.twitter.com
 
  
 %2F1%2Fstatuses%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key%3DTwi
  
 tterConsumerKey%26oauth_nonce%3Dabcdefgh%26oauth_signature_method%3DHMAC-SH
  
 A1%26oauth_timestamp%3D1277739588%26oauth_token%3DTwitterAccessToken%26oaut
   h_version%3D1.0%26source%3DWildfire%2520by%2520Implication
 
 Signing Secret
 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-26 Thread Wil
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) 1/favorites/create

(3) is a bit wierd since TweetSharp sends favorite requests in this
form:
http://api.twitter.com/1/favorites/create/##.json

and the POST body contains this:
source=Wildfire%20by%20Implication

Yet it still works. I haven't tried other things in TweetSharp that
does POST though.
I thought that it was probably the read/write permissions that's
causing the problem because I initially set the App as read-only (I
changed it to write-access when I implemented the favorite). I then
recreated the client information with readwrite access. So I guess
permissions weren't the problem.

I did some packet sniffing to be extra sure that it's sending the data
as POST... and I got this: (using Microsoft NetMon 3.3)
- Http: Request, POST /1/statuses/filter.json , Using OAuth
Authorization
Command: POST
  + URI: /1/statuses/filter.json
ProtocolVersion: HTTP/1.1
  - Authorization: OAuth
   - Authorization:  OAuth
oauth_consumer_key=##,oauth_token=34216267-
BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,oauth_timestamp=1277542341,oauth_signature_method=HMAC-
SHA1,oauth_signature=PeKBoS3uYgL9p7oJ%2
  WhiteSpace:
  AuthorizationData: OAuth
oauth_consumer_key=###,oauth_token=34216267-
BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,oauth_timestamp=1277542341,oauth_signature_method=HMAC-
SHA1,oauth_signature=PeKBoS3uYgL9p7o
  + ContentType:  application/x-www-form-urlencoded
Host:  stream.twitter.com
ContentLength:  51
Connection:  Keep-Alive
HeaderEnd: CRLF


The next frame was the HTTP payload
- Http: HTTP Payload, URL: /1/statuses/filter.json
  - payload: HttpContentType =  application/x-www-form-urlencoded
 source: softwarename
 follow: ###

On Jun 26, 5:50 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 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 POSTing the POST body along with the
 request?

 Seems like you are really close.



 On Fri, Jun 25, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:
  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 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
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;
charset=ISO-8859-1/
titleError 401 UNAUTHORIZED/title
/head
body
h2HTTP ERROR: 401/h2
pProblem accessing /1/statuses/filter.json. Reason:
pre    UNAUTHORIZED/pre/p
hr /ismallPowered by Jetty:///small/i

Here's what I POSTed(oauth tokens are filtered out):

REQUEST: POSThttp://stream.twitter.com/1/statuses/filter.json
Authorization: OAuth

  oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth
  _timestamp=#,oauth_signature_method=HMAC-
SHA1,oauth_signature=,oauth_version=1.0,
Content-Type: application/x-www-form-urlencoded
Vary: Accept-Encoding
Connection: close

source=softwarenamedelimited=1follow=156934710

On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
 OAuthshould work fine onstream.twitter.com

 -John Kaluckihttp://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 tostream.twitter.com usingOAuth
  (particularly, I've been trying to access
 http://stream.twitter.com/1/statuses/filter.json?follow=). I
  used
  the access keys obtained fromhttps://
api.twitter.com/oauth/access_token
  however, I've been getting 401 errors. I've tried basic
  authentication
  and it works fine.

  Does that mean thatstream:statuses/filter is still can only accept
  basic authentication?

  Regards,
  Wil

  On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
  We haven't announced our plans for streaming andoAuth, beyond
  stating
that
  User Streams will only be onoAuth.

  On Mon, May 24, 2010 at 1:57 PM, 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-26 Thread Wil
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 taylorsinglet...@twitter.com
wrote:
 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 POSTing the POST body along with the
 request?

 Seems like you are really close.



 On Fri, Jun 25, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:
  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 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
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;
charset=ISO-8859-1/
titleError 401 UNAUTHORIZED/title
/head
body
h2HTTP ERROR: 401/h2
pProblem accessing /1/statuses/filter.json. Reason:
pre    UNAUTHORIZED/pre/p
hr /ismallPowered by Jetty:///small/i

Here's what I POSTed(oauth tokens are filtered out):

REQUEST: POSThttp://stream.twitter.com/1/statuses/filter.json
Authorization: OAuth

  oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth
  _timestamp=#,oauth_signature_method=HMAC-
SHA1,oauth_signature=,oauth_version=1.0,
Content-Type: application/x-www-form-urlencoded
Vary: Accept-Encoding
Connection: close

source=softwarenamedelimited=1follow=156934710

On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
 OAuthshould work fine onstream.twitter.com

 -John Kaluckihttp://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 tostream.twitter.com usingOAuth
  (particularly, I've been trying to access
 http://stream.twitter.com/1/statuses/filter.json?follow=). I
  used
  the access keys obtained fromhttps://
api.twitter.com/oauth/access_token
  however, I've been getting 401 errors. I've tried basic
  authentication
  and it works fine.

  Does that mean thatstream:statuses/filter is still can only accept
  basic authentication?

  Regards,
  Wil

  On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
  We haven't announced our plans for streaming andoAuth, beyond
  stating
that
  User Streams will only be onoAuth.

  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 toOAuthat the end of June?

   On Mon, May 24, 2010 at 4:50 PM, Mark McBride 
  mmcbr...@twitter.com

   wrote:
   OAuthis now enabled onstream.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 enablingoauthonstream.twitter.com?

Thanks,
Aaron

On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote:
OAuthis not enabled onstream.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++ basedOAuthlibrary.  I know there
  is
liboauth
 but I like to do things myself to learn.

 Anyhow I am trying to accesshttp://
  stream.twitter.com/1/statuses/sample.xml
 and I keep getting 401.

 I have verified pretty much every parameter, and used the
  tool
on

   http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin.
  ..
 to verify my signature is correct. I used twurl to obtain
  the
user
 access tokens to my account.

 After doing some reading I'm no longer convinced that
thestreaming
 server even supportsoauth.

 can you fill me in on the current status
  ofstream.twitter.comand
oauth?

 thanks!
 Lucas

 On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com
wrote:
 Thanks Taylor for the very detailed and helpful response!

 

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-26 Thread John Kalucki
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 than 5 minutes.
 The code works with the following which I've used:
 1) OAuth authentication methods
 2) statuses/user_timeline
 3) 1/favorites/create

 (3) is a bit wierd since TweetSharp sends favorite requests in this
 form:
 http://api.twitter.com/1/favorites/create/##.json

 and the POST body contains this:
 source=Wildfire%20by%20Implication

 Yet it still works. I haven't tried other things in TweetSharp that
 does POST though.
 I thought that it was probably the read/write permissions that's
 causing the problem because I initially set the App as read-only (I
 changed it to write-access when I implemented the favorite). I then
 recreated the client information with readwrite access. So I guess
 permissions weren't the problem.

 I did some packet sniffing to be extra sure that it's sending the data
 as POST... and I got this: (using Microsoft NetMon 3.3)
 - Http: Request, POST /1/statuses/filter.json , Using OAuth
 Authorization
Command: POST
  + URI: /1/statuses/filter.json
ProtocolVersion: HTTP/1.1
  - Authorization: OAuth
   - Authorization:  OAuth
 oauth_consumer_key=##,oauth_token=34216267-

 BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,oauth_timestamp=1277542341,oauth_signature_method=HMAC-
 SHA1,oauth_signature=PeKBoS3uYgL9p7oJ%2
  WhiteSpace:
  AuthorizationData: OAuth
 oauth_consumer_key=###,oauth_token=34216267-

 BDNO9E9Ayd3IDnzRsDgU0wwwcuxO3trNecmblpNQo,oauth_nonce=d8qtvqz2sefipbsu,oauth_timestamp=1277542341,oauth_signature_method=HMAC-
 SHA1,oauth_signature=PeKBoS3uYgL9p7o
  + ContentType:  application/x-www-form-urlencoded
Host:  stream.twitter.com
ContentLength:  51
Connection:  Keep-Alive
HeaderEnd: CRLF


 The next frame was the HTTP payload
 - Http: HTTP Payload, URL: /1/statuses/filter.json
  - payload: HttpContentType =  application/x-www-form-urlencoded
 source: softwarename
 follow: ###

 On Jun 26, 5:50 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  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 POSTing the POST body along with
 the
  request?
 
  Seems like you are really close.
 
 
 
  On Fri, Jun 25, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:
   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 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
 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;
 charset=ISO-8859-1/
 titleError 401 UNAUTHORIZED/title
 /head
 body
 h2HTTP ERROR: 401/h2
 pProblem accessing /1/statuses/filter.json. Reason:
 preUNAUTHORIZED/pre/p
 hr /ismallPowered by Jetty:///small/i
 
 Here's what I POSTed(oauth tokens are filtered out):
 
 REQUEST: POSThttp://stream.twitter.com/1/statuses/filter.json
 Authorization: OAuth
 
  
 oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth
   _timestamp=#,oauth_signature_method=HMAC-
 SHA1,oauth_signature=,oauth_version=1.0,
 Content-Type: application/x-www-form-urlencoded
 Vary: Accept-Encoding
 Connection: close
 
 source=softwarenamedelimited=1follow=156934710
 
 On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
  OAuthshould work fine onstream.twitter.com
 
  -John Kaluckihttp://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 tostream.twitter.com usingOAuth
   (particularly, I've been trying to access
  http://stream.twitter.com/1/statuses/filter.json?follow=).
 I
   used
   the access keys obtained fromhttps://
 api.twitter.com/oauth/access_token
   however, I've been getting 401 errors. I've tried basic
   authentication
   and it works fine.
 
   Does that mean thatstream:statuses/filter is still can only
 accept
   basic authentication?
 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-25 Thread Wil
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
%2Ffilter.jsondelimited%3D1%26follow%3D156934710%26oauth_consumer_key
%3D%26oauth_nonce%3Dtljnew4g283c50gv%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1277483909%26oauth_token%3D34216267-
QihEsUq7jxULnJzMbn1EC1AliHVkktPXjqgYHw8Zt%26oauth_version
%3D1.0%26source%3Dsoftwarename

oauth_consumer_key:##
oauth_token:34216267-QihEsUq7jxULnJzMbn1EC1AliHVkktPXjqgYHw8Zt
oauth_nonce:tljnew4g283c50gv
oauth_timestamp:1277483909
oauth_signature_method:HMAC-SHA1
oauth_signature:ljXbh0wozsHBV6PRowsuZQUHXQs%3D
oauth_version:1.0
source:softwarename
delimited:1
follow:156934710

which looks almost like yours.

Thanks,
Wil
On Jun 24, 11:59 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 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
 POSThttp%3A%2F%2Fstream.twitter.com
 %2F1%2Fstatuses%2Ffilter.jsondelimited%3D1%26follow%3D156934710%26oauth_co 
 nsumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DVBOxfmeKM2mgMeou28zK78M 
 Klfrkvc7Wo4Hx8BAkf0%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp% 
 3D1277394877%26oauth_token%3D819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTm 
 lw%26oauth_version%3D1.0%26source%3Dsoftwarename

 Authorization Header
 OAuth oauth_nonce=VBOxfmeKM2mgMeou28zK78MKlfrkvc7Wo4Hx8BAkf0,
 oauth_signature_method=HMAC-SHA1, oauth_timestamp=1277394877,
 oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ,
 oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw,
 oauth_signature=cLdFEiEy16d2HdWnb5dPBtuxvko%3D, oauth_version=1.0

 How do your values for signature base string differ, if at all? (other than
 the tokens, timestamp, and nonce being different).

 Thanks,
 Taylor



 On Thu, Jun 24, 2010 at 8:17 AM, 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 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
  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;
  charset=ISO-8859-1/
  titleError 401 UNAUTHORIZED/title
  /head
  body
  h2HTTP ERROR: 401/h2
  pProblem accessing /1/statuses/filter.json. Reason:
  pre    UNAUTHORIZED/pre/p
  hr /ismallPowered by Jetty:///small/i

  Here's what I POSTed(oauth tokens are filtered out):

  REQUEST: POSThttp://stream.twitter.com/1/statuses/filter.json
  Authorization: OAuth

  oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth
   _timestamp=#,oauth_signature_method=HMAC-
  SHA1,oauth_signature=,oauth_version=1.0,
  Content-Type: application/x-www-form-urlencoded
  Vary: Accept-Encoding
  Connection: close

  source=softwarenamedelimited=1follow=156934710

  On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
   OAuthshould work fine onstream.twitter.com

   -John Kaluckihttp://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 tostream.twitter.com usingOAuth
(particularly, I've been trying to access
   http://stream.twitter.com/1/statuses/filter.json?follow=). I used
the access keys obtained fromhttps://
  api.twitter.com/oauth/access_token
however, I've been getting 401 errors. I've tried basic authentication
and it works fine.

Does that mean thatstream:statuses/filter is still can only accept
basic authentication?

Regards,
Wil

On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
We haven't announced our plans for streaming andoAuth, beyond stating
  that
User Streams will only be onoAuth.

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 toOAuthat the end of June?

 On Mon, May 24, 2010 at 4:50 PM, Mark McBride 
  mmcbr...@twitter.com
 wrote:
 OAuthis now enabled onstream.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 enablingoauthonstream.twitter.com?

  Thanks,
  Aaron

  On May 13, 1:11 pm, John 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-25 Thread Wil
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 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
  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;
  charset=ISO-8859-1/
  titleError 401 UNAUTHORIZED/title
  /head
  body
  h2HTTP ERROR: 401/h2
  pProblem accessing /1/statuses/filter.json. Reason:
  pre    UNAUTHORIZED/pre/p
  hr /ismallPowered by Jetty:///small/i

  Here's what I POSTed(oauth tokens are filtered out):

  REQUEST: POSThttp://stream.twitter.com/1/statuses/filter.json
  Authorization: OAuth

  oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth 
  _timestamp=#,oauth_signature_method=HMAC-
  SHA1,oauth_signature=,oauth_version=1.0,
  Content-Type: application/x-www-form-urlencoded
  Vary: Accept-Encoding
  Connection: close

  source=softwarenamedelimited=1follow=156934710

  On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
   OAuthshould work fine onstream.twitter.com

   -John Kaluckihttp://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 tostream.twitter.com usingOAuth
(particularly, I've been trying to access
   http://stream.twitter.com/1/statuses/filter.json?follow=). I used
the access keys obtained fromhttps://
  api.twitter.com/oauth/access_token
however, I've been getting 401 errors. I've tried basic authentication
and it works fine.

Does that mean thatstream:statuses/filter is still can only accept
basic authentication?

Regards,
Wil

On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
We haven't announced our plans for streaming andoAuth, beyond stating
  that
User Streams will only be onoAuth.

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 toOAuthat the end of June?

 On Mon, May 24, 2010 at 4:50 PM, Mark McBride mmcbr...@twitter.com

 wrote:
 OAuthis now enabled onstream.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 enablingoauthonstream.twitter.com?

  Thanks,
  Aaron

  On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote:
  OAuthis not enabled onstream.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++ basedOAuthlibrary.  I know there is
  liboauth
   but I like to do things myself to learn.

   Anyhow I am trying to accesshttp://
stream.twitter.com/1/statuses/sample.xml
   and I keep getting 401.

   I have verified pretty much every parameter, and used the tool
  on

 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
   to verify my signature is correct. I used twurl to obtain the
  user
   access tokens to my account.

   After doing some reading I'm no longer convinced that
  thestreaming
   server even supportsoauth.

   can you fill me in on the current status 
   ofstream.twitter.comand
  oauth?

   thanks!
   Lucas

   On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com
  wrote:
   Thanks Taylor for the very detailed and helpful response!

   Jonathon

   On Apr 20, 1:17 pm, Taylor Singletary 
  taylorsinglet...@twitter.com

   wrote:

Hi Jonathon,

ForStreamingAPI access that isn't from the perspective of a
  user's
account, you would use two-leggedOAuthto establish
  authentication
 instead
of basic auth.

A two-leggedOAuthrequest is very similar to
  otherOAuthrequests:
 you have
a specific resource you are trying to access, you have some
 parameters you
want to pass to that resource, and you have anOAuthconsumer
  key
 andOAuth
consumer secret. Which is unlike three-leggedOAuthwhere you
  also
 have
oauth_tokens representing either a user/access_token or a
  request
 token in
addition to the rest.

But the rules remain the same. You take all
  theOAuthparameters and
 the
parameters you are sending to the resource, organize them,
  build a
 signature
base string, then sign 

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-25 Thread Taylor Singletary
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 POSTing the POST body along with the
request?

Seems like you are really close.

On Fri, Jun 25, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:

 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 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
   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;
   charset=ISO-8859-1/
   titleError 401 UNAUTHORIZED/title
   /head
   body
   h2HTTP ERROR: 401/h2
   pProblem accessing /1/statuses/filter.json. Reason:
   preUNAUTHORIZED/pre/p
   hr /ismallPowered by Jetty:///small/i
 
   Here's what I POSTed(oauth tokens are filtered out):
 
   REQUEST: POSThttp://stream.twitter.com/1/statuses/filter.json
   Authorization: OAuth
 
  
 oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth
 _timestamp=#,oauth_signature_method=HMAC-
   SHA1,oauth_signature=,oauth_version=1.0,
   Content-Type: application/x-www-form-urlencoded
   Vary: Accept-Encoding
   Connection: close
 
   source=softwarenamedelimited=1follow=156934710
 
   On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
OAuthshould work fine onstream.twitter.com
 
-John Kaluckihttp://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 tostream.twitter.com usingOAuth
 (particularly, I've been trying to access
http://stream.twitter.com/1/statuses/filter.json?follow=). I
 used
 the access keys obtained fromhttps://
   api.twitter.com/oauth/access_token
 however, I've been getting 401 errors. I've tried basic
 authentication
 and it works fine.
 
 Does that mean thatstream:statuses/filter is still can only accept
 basic authentication?
 
 Regards,
 Wil
 
 On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
 We haven't announced our plans for streaming andoAuth, beyond
 stating
   that
 User Streams will only be onoAuth.
 
 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 toOAuthat the end of June?
 
  On Mon, May 24, 2010 at 4:50 PM, Mark McBride 
 mmcbr...@twitter.com
 
  wrote:
  OAuthis now enabled onstream.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 enablingoauthonstream.twitter.com?
 
   Thanks,
   Aaron
 
   On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote:
   OAuthis not enabled onstream.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++ basedOAuthlibrary.  I know there
 is
   liboauth
but I like to do things myself to learn.
 
Anyhow I am trying to accesshttp://
 stream.twitter.com/1/statuses/sample.xml
and I keep getting 401.
 
I have verified pretty much every parameter, and used the
 tool
   on
 
  http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin.
 ..
to verify my signature is correct. I used twurl to obtain
 the
   user
access tokens to my account.
 
After doing some reading I'm no longer convinced that
   thestreaming
server even supportsoauth.
 
can you fill me in on the current status
 ofstream.twitter.comand
   oauth?
 
thanks!
Lucas
 
On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com
   wrote:
Thanks Taylor for the very detailed and helpful response!
 
Jonathon
 
On Apr 20, 1:17 pm, Taylor Singletary 
   taylorsinglet...@twitter.com
 
wrote:
 
 Hi Jonathon,
 
 ForStreamingAPI access that isn't from the perspective
 of a
   user's
 account, you would use two-leggedOAuthto establish
   authentication
  instead
 of basic auth.
 
 A two-leggedOAuthrequest is very similar to
   otherOAuthrequests:

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-24 Thread Wil
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;
charset=ISO-8859-1/
titleError 401 UNAUTHORIZED/title
/head
body
h2HTTP ERROR: 401/h2
pProblem accessing /1/statuses/filter.json. Reason:
preUNAUTHORIZED/pre/p
hr /ismallPowered by Jetty:///small/i

Here's what I POSTed(oauth tokens are filtered out):

REQUEST: POST http://stream.twitter.com/1/statuses/filter.json
Authorization: OAuth
oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth_timestamp=#,oauth_signature_method=HMAC-
SHA1,oauth_signature=,oauth_version=1.0,
Content-Type: application/x-www-form-urlencoded
Vary: Accept-Encoding
Connection: close

source=softwarenamedelimited=1follow=156934710


On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
 OAuthshould work fine onstream.twitter.com

 -John Kaluckihttp://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 tostream.twitter.com usingOAuth
  (particularly, I've been trying to access
 http://stream.twitter.com/1/statuses/filter.json?follow=). I used
  the access keys obtained fromhttps://api.twitter.com/oauth/access_token
  however, I've been getting 401 errors. I've tried basic authentication
  and it works fine.

  Does that mean thatstream:statuses/filter is still can only accept
  basic authentication?

  Regards,
  Wil

  On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
  We haven't announced our plans for streaming andoAuth, beyond stating that
  User Streams will only be onoAuth.

  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 toOAuthat the end of June?

   On Mon, May 24, 2010 at 4:50 PM, Mark McBride mmcbr...@twitter.com
   wrote:
   OAuthis now enabled onstream.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 enablingoauthonstream.twitter.com?

Thanks,
Aaron

On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote:
OAuthis not enabled onstream.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++ basedOAuthlibrary.  I know there is 
 liboauth
 but I like to do things myself to learn.

 Anyhow I am trying to accesshttp://
  stream.twitter.com/1/statuses/sample.xml
 and I keep getting 401.

 I have verified pretty much every parameter, and used the tool on

  http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
 to verify my signature is correct. I used twurl to obtain the user
 access tokens to my account.

 After doing some reading I'm no longer convinced that thestreaming
 server even supportsoauth.

 can you fill me in on the current status ofstream.twitter.com and
oauth?

 thanks!
 Lucas

 On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
 Thanks Taylor for the very detailed and helpful response!

 Jonathon

 On Apr 20, 1:17 pm, Taylor Singletary 
 taylorsinglet...@twitter.com

 wrote:

  Hi Jonathon,

  ForStreamingAPI access that isn't from the perspective of a 
  user's
  account, you would use two-leggedOAuthto establish 
  authentication
   instead
  of basic auth.

  A two-leggedOAuthrequest is very similar to otherOAuthrequests:
   you have
  a specific resource you are trying to access, you have some
   parameters you
  want to pass to that resource, and you have anOAuthconsumer key
   andOAuth
  consumer secret. Which is unlike three-leggedOAuthwhere you also
   have
  oauth_tokens representing either a user/access_token or a 
  request
   token in
  addition to the rest.

  But the rules remain the same. You take all theOAuthparameters 
  and
   the
  parameters you are sending to the resource, organize them, 
  build a
   signature
  base string, then sign that with your consumer secret and send 
  the
   request
  on to Twitter properly signed. The only difference is that there
   is no
  oauth_token and oauth_token_secret getting involved in the mix.

  This is essentially what a two-legged request to thestreamingAPI
   would
  look like:

  Signature Base String
  GEThttp%3A%2F%2Fstream.twitter.com

   %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2

   

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-24 Thread John Kalucki
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
 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;
 charset=ISO-8859-1/
 titleError 401 UNAUTHORIZED/title
 /head
 body
 h2HTTP ERROR: 401/h2
 pProblem accessing /1/statuses/filter.json. Reason:
 preUNAUTHORIZED/pre/p
 hr /ismallPowered by Jetty:///small/i

 Here's what I POSTed(oauth tokens are filtered out):

 REQUEST: POST http://stream.twitter.com/1/statuses/filter.json
 Authorization: OAuth

 oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth_timestamp=#,oauth_signature_method=HMAC-
 SHA1,oauth_signature=,oauth_version=1.0,
 Content-Type: application/x-www-form-urlencoded
 Vary: Accept-Encoding
 Connection: close

 source=softwarenamedelimited=1follow=156934710


 On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
  OAuthshould work fine onstream.twitter.com
 
  -John Kaluckihttp://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 tostream.twitter.com usingOAuth
   (particularly, I've been trying to access
  http://stream.twitter.com/1/statuses/filter.json?follow=). I used
   the access keys obtained fromhttps://
 api.twitter.com/oauth/access_token
   however, I've been getting 401 errors. I've tried basic authentication
   and it works fine.
 
   Does that mean thatstream:statuses/filter is still can only accept
   basic authentication?
 
   Regards,
   Wil
 
   On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
   We haven't announced our plans for streaming andoAuth, beyond stating
 that
   User Streams will only be onoAuth.
 
   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 toOAuthat the end of June?
 
On Mon, May 24, 2010 at 4:50 PM, Mark McBride mmcbr...@twitter.com
 
wrote:
OAuthis now enabled onstream.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 enablingoauthonstream.twitter.com?
 
 Thanks,
 Aaron
 
 On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote:
 OAuthis not enabled onstream.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++ basedOAuthlibrary.  I know there is
 liboauth
  but I like to do things myself to learn.
 
  Anyhow I am trying to accesshttp://
   stream.twitter.com/1/statuses/sample.xml
  and I keep getting 401.
 
  I have verified pretty much every parameter, and used the tool
 on
 
   
 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
  to verify my signature is correct. I used twurl to obtain the
 user
  access tokens to my account.
 
  After doing some reading I'm no longer convinced that
 thestreaming
  server even supportsoauth.
 
  can you fill me in on the current status ofstream.twitter.comand
 oauth?
 
  thanks!
  Lucas
 
  On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com
 wrote:
  Thanks Taylor for the very detailed and helpful response!
 
  Jonathon
 
  On Apr 20, 1:17 pm, Taylor Singletary 
 taylorsinglet...@twitter.com
 
  wrote:
 
   Hi Jonathon,
 
   ForStreamingAPI access that isn't from the perspective of a
 user's
   account, you would use two-leggedOAuthto establish
 authentication
instead
   of basic auth.
 
   A two-leggedOAuthrequest is very similar to
 otherOAuthrequests:
you have
   a specific resource you are trying to access, you have some
parameters you
   want to pass to that resource, and you have anOAuthconsumer
 key
andOAuth
   consumer secret. Which is unlike three-leggedOAuthwhere you
 also
have
   oauth_tokens representing either a user/access_token or a
 request
token in
   addition to the rest.
 
   But the rules remain the same. You take all
 theOAuthparameters and
the
   parameters you are sending to the resource, organize them,
 build a
signature
   base string, then sign that with your consumer secret and
 send the
request
   on to Twitter properly signed. The only difference is that
 there
is no
   oauth_token and oauth_token_secret getting involved in the
 mix.
 
   This is essentially 

Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-24 Thread Taylor Singletary
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
POSThttp%3A%2F%2Fstream.twitter.com
%2F1%2Fstatuses%2Ffilter.jsondelimited%3D1%26follow%3D156934710%26oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DVBOxfmeKM2mgMeou28zK78MKlfrkvc7Wo4Hx8BAkf0%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1277394877%26oauth_token%3D819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw%26oauth_version%3D1.0%26source%3Dsoftwarename

Authorization Header
OAuth oauth_nonce=VBOxfmeKM2mgMeou28zK78MKlfrkvc7Wo4Hx8BAkf0,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1277394877,
oauth_consumer_key=ri8JxYK2ddwSV5xIUfNNvQ,
oauth_token=819797-torCkTs0XK7H2Y2i1ee5iofqkMC4p7aayeEXRTmlw,
oauth_signature=cLdFEiEy16d2HdWnb5dPBtuxvko%3D, oauth_version=1.0

How do your values for signature base string differ, if at all? (other than
the tokens, timestamp, and nonce being different).

Thanks,
Taylor

On Thu, Jun 24, 2010 at 8:17 AM, 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 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
 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;
 charset=ISO-8859-1/
 titleError 401 UNAUTHORIZED/title
 /head
 body
 h2HTTP ERROR: 401/h2
 pProblem accessing /1/statuses/filter.json. Reason:
 preUNAUTHORIZED/pre/p
 hr /ismallPowered by Jetty:///small/i

 Here's what I POSTed(oauth tokens are filtered out):

 REQUEST: POST http://stream.twitter.com/1/statuses/filter.json
 Authorization: OAuth

 oauth_consumer_key=#,oauth_token=,oauth_nonce=#,oauth_timestamp=#,oauth_signature_method=HMAC-
 SHA1,oauth_signature=,oauth_version=1.0,
 Content-Type: application/x-www-form-urlencoded
 Vary: Accept-Encoding
 Connection: close

 source=softwarenamedelimited=1follow=156934710


 On Jun 23, 1:33 am, John Kalucki j...@twitter.com wrote:
  OAuthshould work fine onstream.twitter.com
 
  -John Kaluckihttp://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 tostream.twitter.com usingOAuth
   (particularly, I've been trying to access
  http://stream.twitter.com/1/statuses/filter.json?follow=). I used
   the access keys obtained fromhttps://
 api.twitter.com/oauth/access_token
   however, I've been getting 401 errors. I've tried basic authentication
   and it works fine.
 
   Does that mean thatstream:statuses/filter is still can only accept
   basic authentication?
 
   Regards,
   Wil
 
   On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
   We haven't announced our plans for streaming andoAuth, beyond stating
 that
   User Streams will only be onoAuth.
 
   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 toOAuthat the end of June?
 
On Mon, May 24, 2010 at 4:50 PM, Mark McBride 
 mmcbr...@twitter.com
wrote:
OAuthis now enabled onstream.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 enablingoauthonstream.twitter.com?
 
 Thanks,
 Aaron
 
 On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote:
 OAuthis not enabled onstream.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++ basedOAuthlibrary.  I know there is
 liboauth
  but I like to do things myself to learn.
 
  Anyhow I am trying to accesshttp://
   stream.twitter.com/1/statuses/sample.xml
  and I keep getting 401.
 
  I have verified pretty much every parameter, and used the
 tool on
 
   
 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
  to verify my signature is correct. I used twurl to obtain the
 user
  access tokens to my account.
 
  After doing some reading I'm no longer convinced that
 thestreaming
  server even supportsoauth.
 
  can you fill me in on the current status
 ofstream.twitter.com and
 oauth?
 
  thanks!
  Lucas
 
  On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com
 wrote:
  Thanks Taylor for the very detailed and helpful response!
 
 

[twitter-dev] Re: Streaming API OAuth explanation?

2010-06-22 Thread Wil
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 getting 401 errors. I've tried basic authentication
and it works fine.

Does that mean that stream:statuses/filter is still can only accept
basic authentication?

Regards,
Wil

On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
 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 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

     ---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 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 wrote:
I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
but I like to do things myself to learn.

Anyhow I am trying to accesshttp://
  stream.twitter.com/1/statuses/sample.xml
and I keep getting 401.

I have verified pretty much every parameter, and used the tool on

 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
to verify my signature is correct. I used twurl to obtain the user
access tokens to my account.

After doing some reading I'm no longer convinced that thestreaming
server even supportsoauth.

can you fill me in on the current status of stream.twitter.com and
   oauth?

thanks!
Lucas

On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
Thanks Taylor for the very detailed and helpful response!

Jonathon

On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com

wrote:

 Hi Jonathon,

 ForStreamingAPI access that isn't from the perspective of a user's
 account, you would use two-leggedOAuthto establish authentication
  instead
 of basic auth.

 A two-leggedOAuthrequest is very similar to otherOAuthrequests:
  you have
 a specific resource you are trying to access, you have some
  parameters you
 want to pass to that resource, and you have anOAuthconsumer key
  andOAuth
 consumer secret. Which is unlike three-leggedOAuthwhere you also
  have
 oauth_tokens representing either a user/access_token or a request
  token in
 addition to the rest.

 But the rules remain the same. You take all theOAuthparameters and
  the
 parameters you are sending to the resource, organize them, build a
  signature
 base string, then sign that with your consumer secret and send the
  request
 on to Twitter properly signed. The only difference is that there
  is no
 oauth_token and oauth_token_secret getting involved in the mix.

 This is essentially what a two-legged request to thestreamingAPI
  would
 look like:

 Signature Base String
 GEThttp%3A%2F%2Fstream.twitter.com

  %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2 
  ­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatu 
  r­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

 Signature
 Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

 Authorization Header
OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
 oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
 oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
 oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D,
  oauth_version=1.0

 Taylor Singletary
 Developer Advocate, Twitterhttp://twitter.com/episod

 On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill 
  jhill9...@gmail.com wrote:
  One thing I meant to find out @chirp last week--what
  willoauthlook
  like for theStreamingAPI? I'm having a hard time visualizing how
  that will work.

  Thanks,

  Jonathon Hill
  @compwright
  Company52
 http://company52.com

  --
  Subscription settings:

 http://groups.google.com/group/twitter-development-talk/subscribe?hl=en


Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-06-22 Thread John Kalucki
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 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 getting 401 errors. I've tried basic authentication
 and it works fine.

 Does that mean that stream:statuses/filter is still can only accept
 basic authentication?

 Regards,
 Wil

 On May 25, 5:51 am, John Kalucki j...@twitter.com wrote:
 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 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

     ---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 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 wrote:
I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
but I like to do things myself to learn.

Anyhow I am trying to accesshttp://
  stream.twitter.com/1/statuses/sample.xml
and I keep getting 401.

I have verified pretty much every parameter, and used the tool on

 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
to verify my signature is correct. I used twurl to obtain the user
access tokens to my account.

After doing some reading I'm no longer convinced that thestreaming
server even supportsoauth.

can you fill me in on the current status of stream.twitter.com and
   oauth?

thanks!
Lucas

On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
Thanks Taylor for the very detailed and helpful response!

Jonathon

On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com

wrote:

 Hi Jonathon,

 ForStreamingAPI access that isn't from the perspective of a user's
 account, you would use two-leggedOAuthto establish authentication
  instead
 of basic auth.

 A two-leggedOAuthrequest is very similar to otherOAuthrequests:
  you have
 a specific resource you are trying to access, you have some
  parameters you
 want to pass to that resource, and you have anOAuthconsumer key
  andOAuth
 consumer secret. Which is unlike three-leggedOAuthwhere you also
  have
 oauth_tokens representing either a user/access_token or a request
  token in
 addition to the rest.

 But the rules remain the same. You take all theOAuthparameters and
  the
 parameters you are sending to the resource, organize them, build a
  signature
 base string, then sign that with your consumer secret and send the
  request
 on to Twitter properly signed. The only difference is that there
  is no
 oauth_token and oauth_token_secret getting involved in the mix.

 This is essentially what a two-legged request to thestreamingAPI
  would
 look like:

 Signature Base String
 GEThttp%3A%2F%2Fstream.twitter.com

  %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2
   
  ­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatu
   
  r­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

 Signature
 Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

 Authorization Header
OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
 oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
 oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
 oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D,
  oauth_version=1.0

 Taylor Singletary
 Developer Advocate, Twitterhttp://twitter.com/episod

 On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill 
  jhill9...@gmail.com wrote:
  One thing I meant to find out @chirp last week--what
  willoauthlook
  like for theStreamingAPI? I'm having a hard time visualizing how
  that will work.

  Thanks,

  Jonathon Hill
  @compwright
  Company52
 http://company52.com

  --
  Subscription settings:

 http://groups.google.com/group/twitter-development-talk/subscribe?hl=en



[twitter-dev] Re: Streaming API OAuth explanation?

2010-05-24 Thread Aaron Rankin
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 
 wrote:
  I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
  but I like to do things myself to learn.

  Anyhow I am trying to accesshttp://stream.twitter.com/1/statuses/sample.xml
  and I keep getting 401.

  I have verified pretty much every parameter, and used the tool on
 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
  to verify my signature is correct. I used twurl to obtain the user
  access tokens to my account.

  After doing some reading I'm no longer convinced that thestreaming
  server even supportsoauth.

  can you fill me in on the current status of stream.twitter.com and
 oauth?

  thanks!
  Lucas

  On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
  Thanks Taylor for the very detailed and helpful response!

  Jonathon

  On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
  wrote:

   Hi Jonathon,

   ForStreamingAPI access that isn't from the perspective of a user's
   account, you would use two-leggedOAuthto establish authentication instead
   of basic auth.

   A two-leggedOAuthrequest is very similar to otherOAuthrequests: you have
   a specific resource you are trying to access, you have some parameters 
   you
   want to pass to that resource, and you have anOAuthconsumer key andOAuth
   consumer secret. Which is unlike three-leggedOAuthwhere you also have
   oauth_tokens representing either a user/access_token or a request token 
   in
   addition to the rest.

   But the rules remain the same. You take all theOAuthparameters and the
   parameters you are sending to the resource, organize them, build a 
   signature
   base string, then sign that with your consumer secret and send the 
   request
   on to Twitter properly signed. The only difference is that there is no
   oauth_token and oauth_token_secret getting involved in the mix.

   This is essentially what a two-legged request to thestreamingAPI would
   look like:

   Signature Base String
   GEThttp%3A%2F%2Fstream.twitter.com
   %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

   Signature
   Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

   Authorization Header
  OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
   oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
   oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
   oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

   Taylor Singletary
   Developer Advocate, Twitterhttp://twitter.com/episod

   On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill jhill9...@gmail.com 
   wrote:
One thing I meant to find out @chirp last week--what willoauthlook
like for theStreamingAPI? I'm having a hard time visualizing how
that will work.

Thanks,

Jonathon Hill
@compwright
Company52
   http://company52.com

--
Subscription settings:
   http://groups.google.com/group/twitter-development-talk/subscribe?hl=en


Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-05-24 Thread Mark McBride
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 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 
 wrote:
  I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
  but I like to do things myself to learn.

  Anyhow I am trying to accesshttp://stream.twitter.com/1/statuses/sample.xml
  and I keep getting 401.

  I have verified pretty much every parameter, and used the tool on
 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
  to verify my signature is correct. I used twurl to obtain the user
  access tokens to my account.

  After doing some reading I'm no longer convinced that thestreaming
  server even supportsoauth.

  can you fill me in on the current status of stream.twitter.com and
 oauth?

  thanks!
  Lucas

  On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
  Thanks Taylor for the very detailed and helpful response!

  Jonathon

  On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
  wrote:

   Hi Jonathon,

   ForStreamingAPI access that isn't from the perspective of a user's
   account, you would use two-leggedOAuthto establish authentication 
   instead
   of basic auth.

   A two-leggedOAuthrequest is very similar to otherOAuthrequests: you have
   a specific resource you are trying to access, you have some parameters 
   you
   want to pass to that resource, and you have anOAuthconsumer key andOAuth
   consumer secret. Which is unlike three-leggedOAuthwhere you also have
   oauth_tokens representing either a user/access_token or a request token 
   in
   addition to the rest.

   But the rules remain the same. You take all theOAuthparameters and the
   parameters you are sending to the resource, organize them, build a 
   signature
   base string, then sign that with your consumer secret and send the 
   request
   on to Twitter properly signed. The only difference is that there is no
   oauth_token and oauth_token_secret getting involved in the mix.

   This is essentially what a two-legged request to thestreamingAPI would
   look like:

   Signature Base String
   GEThttp%3A%2F%2Fstream.twitter.com
   %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

   Signature
   Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

   Authorization Header
  OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
   oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
   oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
   oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

   Taylor Singletary
   Developer Advocate, Twitterhttp://twitter.com/episod

   On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill jhill9...@gmail.com 
   wrote:
One thing I meant to find out @chirp last week--what willoauthlook
like for theStreamingAPI? I'm having a hard time visualizing how
that will work.

Thanks,

Jonathon Hill
@compwright
Company52
   http://company52.com

--
Subscription settings:
   http://groups.google.com/group/twitter-development-talk/subscribe?hl=en



Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-05-24 Thread 140dev
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

   ---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 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 
 wrote:
  I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
  but I like to do things myself to learn.

  Anyhow I am trying to 
  accesshttp://stream.twitter.com/1/statuses/sample.xml
  and I keep getting 401.

  I have verified pretty much every parameter, and used the tool on
 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
  to verify my signature is correct. I used twurl to obtain the user
  access tokens to my account.

  After doing some reading I'm no longer convinced that thestreaming
  server even supportsoauth.

  can you fill me in on the current status of stream.twitter.com and
 oauth?

  thanks!
  Lucas

  On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
  Thanks Taylor for the very detailed and helpful response!

  Jonathon

  On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
  wrote:

   Hi Jonathon,

   ForStreamingAPI access that isn't from the perspective of a user's
   account, you would use two-leggedOAuthto establish authentication 
   instead
   of basic auth.

   A two-leggedOAuthrequest is very similar to otherOAuthrequests: you 
   have
   a specific resource you are trying to access, you have some parameters 
   you
   want to pass to that resource, and you have anOAuthconsumer key 
   andOAuth
   consumer secret. Which is unlike three-leggedOAuthwhere you also have
   oauth_tokens representing either a user/access_token or a request 
   token in
   addition to the rest.

   But the rules remain the same. You take all theOAuthparameters and the
   parameters you are sending to the resource, organize them, build a 
   signature
   base string, then sign that with your consumer secret and send the 
   request
   on to Twitter properly signed. The only difference is that there is no
   oauth_token and oauth_token_secret getting involved in the mix.

   This is essentially what a two-legged request to thestreamingAPI would
   look like:

   Signature Base String
   GEThttp%3A%2F%2Fstream.twitter.com
   %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

   Signature
   Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

   Authorization Header
  OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
   oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
   oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
   oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

   Taylor Singletary
   Developer Advocate, Twitterhttp://twitter.com/episod

   On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill jhill9...@gmail.com 
   wrote:
One thing I meant to find out @chirp last week--what willoauthlook
like for theStreamingAPI? I'm having a hard time visualizing how
that will work.

Thanks,

Jonathon Hill
@compwright
Company52
   http://company52.com

--
Subscription settings:
   http://groups.google.com/group/twitter-development-talk/subscribe?hl=en




Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-05-24 Thread John Kalucki
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 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
 
---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 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 wrote:
   I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
   but I like to do things myself to learn.
 
   Anyhow I am trying to accesshttp://
 stream.twitter.com/1/statuses/sample.xml
   and I keep getting 401.
 
   I have verified pretty much every parameter, and used the tool on
  
 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
   to verify my signature is correct. I used twurl to obtain the user
   access tokens to my account.
 
   After doing some reading I'm no longer convinced that thestreaming
   server even supportsoauth.
 
   can you fill me in on the current status of stream.twitter.com and
  oauth?
 
   thanks!
   Lucas
 
   On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
   Thanks Taylor for the very detailed and helpful response!
 
   Jonathon
 
   On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
 
   wrote:
 
Hi Jonathon,
 
ForStreamingAPI access that isn't from the perspective of a user's
account, you would use two-leggedOAuthto establish authentication
 instead
of basic auth.
 
A two-leggedOAuthrequest is very similar to otherOAuthrequests:
 you have
a specific resource you are trying to access, you have some
 parameters you
want to pass to that resource, and you have anOAuthconsumer key
 andOAuth
consumer secret. Which is unlike three-leggedOAuthwhere you also
 have
oauth_tokens representing either a user/access_token or a request
 token in
addition to the rest.
 
But the rules remain the same. You take all theOAuthparameters and
 the
parameters you are sending to the resource, organize them, build a
 signature
base string, then sign that with your consumer secret and send the
 request
on to Twitter properly signed. The only difference is that there
 is no
oauth_token and oauth_token_secret getting involved in the mix.
 
This is essentially what a two-legged request to thestreamingAPI
 would
look like:
 
Signature Base String
GEThttp%3A%2F%2Fstream.twitter.com
   
 %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0
 
Signature
Xi5jfuw2XqtU5KpNX9ZCtTptJS0=
 
Authorization Header
   OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D,
 oauth_version=1.0
 
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
 
On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill 
 jhill9...@gmail.com wrote:
 One thing I meant to find out @chirp last week--what
 willoauthlook
 like for theStreamingAPI? I'm having a hard time visualizing how
 that will work.
 
 Thanks,
 
 Jonathon Hill
 @compwright
 Company52
http://company52.com
 
 --
 Subscription settings:

 http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
 
 



[twitter-dev] Re: Streaming API OAuth explanation?

2010-05-24 Thread Jonathon Hill
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 aran...@gmail.com wrote:
  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 
  wrote:
   I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
   but I like to do things myself to learn.

   Anyhow I am trying to 
   accesshttp://stream.twitter.com/1/statuses/sample.xml
   and I keep getting 401.

   I have verified pretty much every parameter, and used the tool on
  http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
   to verify my signature is correct. I used twurl to obtain the user
   access tokens to my account.

   After doing some reading I'm no longer convinced that thestreaming
   server even supportsoauth.

   can you fill me in on the current status of stream.twitter.com and
  oauth?

   thanks!
   Lucas

   On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
   Thanks Taylor for the very detailed and helpful response!

   Jonathon

   On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
   wrote:

Hi Jonathon,

ForStreamingAPI access that isn't from the perspective of a user's
account, you would use two-leggedOAuthto establish authentication 
instead
of basic auth.

A two-leggedOAuthrequest is very similar to otherOAuthrequests: you 
have
a specific resource you are trying to access, you have some 
parameters you
want to pass to that resource, and you have anOAuthconsumer key 
andOAuth
consumer secret. Which is unlike three-leggedOAuthwhere you also have
oauth_tokens representing either a user/access_token or a request 
token in
addition to the rest.

But the rules remain the same. You take all theOAuthparameters and the
parameters you are sending to the resource, organize them, build a 
signature
base string, then sign that with your consumer secret and send the 
request
on to Twitter properly signed. The only difference is that there is no
oauth_token and oauth_token_secret getting involved in the mix.

This is essentially what a two-legged request to thestreamingAPI would
look like:

Signature Base String
GEThttp%3A%2F%2Fstream.twitter.com
%2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatu­r­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

Signature
Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

Authorization Header
   OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod

On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill jhill9...@gmail.com 
wrote:
 One thing I meant to find out @chirp last week--what willoauthlook
 like for theStreamingAPI? I'm having a hard time visualizing how
 that will work.

 Thanks,

 Jonathon Hill
 @compwright
 Company52
http://company52.com

 --
 Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en


Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-05-24 Thread Zac Bowling
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 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 aran...@gmail.com wrote:
  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 
  wrote:
   I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
   but I like to do things myself to learn.

   Anyhow I am trying to 
   accesshttp://stream.twitter.com/1/statuses/sample.xml
   and I keep getting 401.

   I have verified pretty much every parameter, and used the tool on
  http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
   to verify my signature is correct. I used twurl to obtain the user
   access tokens to my account.

   After doing some reading I'm no longer convinced that thestreaming
   server even supportsoauth.

   can you fill me in on the current status of stream.twitter.com and
  oauth?

   thanks!
   Lucas

   On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
   Thanks Taylor for the very detailed and helpful response!

   Jonathon

   On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
   wrote:

Hi Jonathon,

ForStreamingAPI access that isn't from the perspective of a user's
account, you would use two-leggedOAuthto establish authentication 
instead
of basic auth.

A two-leggedOAuthrequest is very similar to otherOAuthrequests: you 
have
a specific resource you are trying to access, you have some 
parameters you
want to pass to that resource, and you have anOAuthconsumer key 
andOAuth
consumer secret. Which is unlike three-leggedOAuthwhere you also have
oauth_tokens representing either a user/access_token or a request 
token in
addition to the rest.

But the rules remain the same. You take all theOAuthparameters and 
the
parameters you are sending to the resource, organize them, build a 
signature
base string, then sign that with your consumer secret and send the 
request
on to Twitter properly signed. The only difference is that there is 
no
oauth_token and oauth_token_secret getting involved in the mix.

This is essentially what a two-legged request to thestreamingAPI 
would
look like:

Signature Base String
GEThttp%3A%2F%2Fstream.twitter.com
%2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatu­r­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

Signature
Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

Authorization Header
   OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod

On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill 
jhill9...@gmail.com wrote:
 One thing I meant to find out @chirp last week--what willoauthlook
 like for theStreamingAPI? I'm having a hard time visualizing how
 that will work.

 Thanks,

 Jonathon Hill
 @compwright
 Company52
http://company52.com

 --
 Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en



[twitter-dev] Re: Streaming API OAuth explanation?

2010-05-13 Thread Lucas Vickers
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
http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/
to verify my signature is correct. I used twurl to obtain the user
access tokens to my account.

After doing some reading I'm no longer convinced that the streaming
server even supports oauth.

can you fill me in on the current status of stream.twitter.com and
oauth?

thanks!
Lucas



On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
 Thanks Taylor for the very detailed and helpful response!

 Jonathon

 On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:

  Hi Jonathon,

  ForStreamingAPI access that isn't from the perspective of a user's
  account, you would use two-leggedOAuthto establish authentication instead
  of basic auth.

  A two-leggedOAuthrequest is very similar to otherOAuthrequests: you have
  a specific resource you are trying to access, you have some parameters you
  want to pass to that resource, and you have anOAuthconsumer key andOAuth
  consumer secret. Which is unlike three-leggedOAuthwhere you also have
  oauth_tokens representing either a user/access_token or a request token in
  addition to the rest.

  But the rules remain the same. You take all theOAuthparameters and the
  parameters you are sending to the resource, organize them, build a signature
  base string, then sign that with your consumer secret and send the request
  on to Twitter properly signed. The only difference is that there is no
  oauth_token and oauth_token_secret getting involved in the mix.

  This is essentially what a two-legged request to thestreamingAPI would
  look like:

  Signature Base String
  GEThttp%3A%2F%2Fstream.twitter.com
  %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

  Signature
  Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

  Authorization Header
 OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
  oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
  oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
  oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

  Taylor Singletary
  Developer Advocate, Twitterhttp://twitter.com/episod

  On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill jhill9...@gmail.com wrote:
   One thing I meant to find out @chirp last week--what willoauthlook
   like for theStreamingAPI? I'm having a hard time visualizing how
   that will work.

   Thanks,

   Jonathon Hill
   @compwright
   Company52
  http://company52.com

   --
   Subscription settings:
  http://groups.google.com/group/twitter-development-talk/subscribe?hl=en


Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-05-13 Thread John Kalucki
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 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
 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/
 to verify my signature is correct. I used twurl to obtain the user
 access tokens to my account.

 After doing some reading I'm no longer convinced that the streaming
 server even supports oauth.

 can you fill me in on the current status of stream.twitter.com and
 oauth?

 thanks!
 Lucas



 On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
 Thanks Taylor for the very detailed and helpful response!

 Jonathon

 On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:

  Hi Jonathon,

  ForStreamingAPI access that isn't from the perspective of a user's
  account, you would use two-leggedOAuthto establish authentication instead
  of basic auth.

  A two-leggedOAuthrequest is very similar to otherOAuthrequests: you have
  a specific resource you are trying to access, you have some parameters you
  want to pass to that resource, and you have anOAuthconsumer key andOAuth
  consumer secret. Which is unlike three-leggedOAuthwhere you also have
  oauth_tokens representing either a user/access_token or a request token in
  addition to the rest.

  But the rules remain the same. You take all theOAuthparameters and the
  parameters you are sending to the resource, organize them, build a 
  signature
  base string, then sign that with your consumer secret and send the request
  on to Twitter properly signed. The only difference is that there is no
  oauth_token and oauth_token_secret getting involved in the mix.

  This is essentially what a two-legged request to thestreamingAPI would
  look like:

  Signature Base String
  GEThttp%3A%2F%2Fstream.twitter.com
  %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

  Signature
  Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

  Authorization Header
 OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
  oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
  oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
  oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

  Taylor Singletary
  Developer Advocate, Twitterhttp://twitter.com/episod

  On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill jhill9...@gmail.com 
  wrote:
   One thing I meant to find out @chirp last week--what willoauthlook
   like for theStreamingAPI? I'm having a hard time visualizing how
   that will work.

   Thanks,

   Jonathon Hill
   @compwright
   Company52
  http://company52.com

   --
   Subscription settings:
  http://groups.google.com/group/twitter-development-talk/subscribe?hl=en



Re: [twitter-dev] Re: Streaming API OAuth explanation?

2010-05-13 Thread Lucas Vickers
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++ 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
 http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/
 to verify my signature is correct. I used twurl to obtain the user
 access tokens to my account.

 After doing some reading I'm no longer convinced that the streaming
 server even supports oauth.

 can you fill me in on the current status of stream.twitter.com and
 oauth?

 thanks!
 Lucas



 On Apr 20, 11:02 pm, Jonathon Hill jhill9...@gmail.com wrote:
 Thanks Taylor for the very detailed and helpful response!

 Jonathon

 On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:

  Hi Jonathon,

  ForStreamingAPI access that isn't from the perspective of a user's
  account, you would use two-leggedOAuthto establish authentication instead
  of basic auth.

  A two-leggedOAuthrequest is very similar to otherOAuthrequests: you have
  a specific resource you are trying to access, you have some parameters you
  want to pass to that resource, and you have anOAuthconsumer key andOAuth
  consumer secret. Which is unlike three-leggedOAuthwhere you also have
  oauth_tokens representing either a user/access_token or a request token in
  addition to the rest.

  But the rules remain the same. You take all theOAuthparameters and the
  parameters you are sending to the resource, organize them, build a 
  signature
  base string, then sign that with your consumer secret and send the request
  on to Twitter properly signed. The only difference is that there is no
  oauth_token and oauth_token_secret getting involved in the mix.

  This is essentially what a two-legged request to thestreamingAPI would
  look like:

  Signature Base String
  GEThttp%3A%2F%2Fstream.twitter.com
  %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

  Signature
  Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

  Authorization Header
 OAuthoauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
  oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
  oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
  oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

  Taylor Singletary
  Developer Advocate, Twitterhttp://twitter.com/episod

  On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill jhill9...@gmail.com 
  wrote:
   One thing I meant to find out @chirp last week--what willoauthlook
   like for theStreamingAPI? I'm having a hard time visualizing how
   that will work.

   Thanks,

   Jonathon Hill
   @compwright
   Company52
  http://company52.com

   --
   Subscription settings:
  http://groups.google.com/group/twitter-development-talk/subscribe?hl=en




[twitter-dev] Re: Streaming API

2010-04-25 Thread epomqo
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 with , or have curl do it for you by specifying
 multiple -d @ pairs:

 adrift.local:/tmp head foo bar
 == foo ==
 follow=1234

 == bar ==
 track=north
 adrift.local:/tmp curl -v -x  -d @foo -d @bar
 stream.twitter.com/1/statuses/filter.xml

 -John Kaluckihttp://twitter.com/jkalucki
 Infrastructure, Twitter Inc.

 On Sat, Apr 24, 2010 at 5:27 AM, epomqo wenzi0...@gmail.com wrote:
  Dear Sirs,

  Hello! My name is Xiaowen, I have been playing with Twitter for some
  time and I am writing to ask a small question regarding Streaming
  API :)

  From the documentation I know we can use the command curl -d
  @locationshttp://stream.twitter.com/1/statuses/filter.json-
  uAnyTwitterUser:Password to filter geo-tagged tweets in a bounded box
  area, we could also use similar method to follow tweets of specific
  users. These are two parameters which can be implemented by statuses/
  filter method. My question is, if I want to incorporate both of these
  two parameters in one command, how to put them together? I have tried
  something like

  curl -d @locations 
  @followinghttp://stream.twitter.com/1/statuses/filter.json
  -uAnyTwitterUser:Password

  but it doesn't work :(

  Later I got response from Twitter support, suggesting that:

  One Streaming API connection can filter both geo-tagged tweets and
  tweets from specific users. You may want to combine both of your
  parameters into one file so that you do not need to reference two in
  your command (for example @locandfollow instead of @locations
  @following).

  But then what is the correct way to put the parameters in one file? I
  tried simply put them together, like this:

  locations=-122.75,36.8,-121.75,37.8;
  follow=...,...,...

  but still it doesn't work.

  Many thanks for your advices!

  --
  Subscription 
  settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en


[twitter-dev] Re: Streaming API OAuth explanation?

2010-04-21 Thread Jonathon Hill
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 instead
 of basic auth.

 A two-legged OAuth request is very similar to other OAuth requests: you have
 a specific resource you are trying to access, you have some parameters you
 want to pass to that resource, and you have an OAuth consumer key and OAuth
 consumer secret. Which is unlike three-legged OAuth where you also have
 oauth_tokens representing either a user/access_token or a request token in
 addition to the rest.

 But the rules remain the same. You take all the OAuth parameters and the
 parameters you are sending to the resource, organize them, build a signature
 base string, then sign that with your consumer secret and send the request
 on to Twitter properly signed. The only difference is that there is no
 oauth_token and oauth_token_secret getting involved in the mix.

 This is essentially what a two-legged request to the streaming API would
 look like:

 Signature Base String
 GEThttp%3A%2F%2Fstream.twitter.com
 %2F1%2Fstatuses%2Fsample.jsonoauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatur­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0

 Signature
 Xi5jfuw2XqtU5KpNX9ZCtTptJS0=

 Authorization Header
 OAuth oauth_nonce=SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8,
 oauth_signature_method=HMAC-SHA1, oauth_timestamp=1271783743,
 oauth_consumer_key=ri8JxYK2zzwSV5xIUfNNvQ,
 oauth_signature=Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D, oauth_version=1.0

 Taylor Singletary
 Developer Advocate, Twitterhttp://twitter.com/episod



 On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill jhill9...@gmail.com wrote:
  One thing I meant to find out @chirp last week--what will oauth look
  like for the Streaming API? I'm having a hard time visualizing how
  that will work.

  Thanks,

  Jonathon Hill
  @compwright
  Company52
 http://company52.com

  --
  Subscription settings:
 http://groups.google.com/group/twitter-development-talk/subscribe?hl=en


[twitter-dev] Re: Streaming API not returning any data

2010-04-19 Thread Amitab


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 should happen is if a load balancer restarts.
 I don't think this happened at 4pm -- rather, there was a Hosebird
 deploy at around this time. If anything, you should have received an
 HTTP error code, a TCP RST or TCP CLOSE at this time.

Thanks, I will check whether my session is terminating on a TCP RST/
CLOSE.

 If you were connecting twice with the same username, your earlier
 connection may have been dropped due to duplication.

I use different usernames and different IPs in my test and production
environments. Thanks for clarifying.


 -John Kaluckihttp://twitter.com/jkalucki
 Infrastructure, Twitter Inc.



 On Mon, Apr 19, 2010 at 8:28 PM, Amitab hiamita...@gmail.com wrote:
  Hi,

  There was a thread about this before in which Twitter folks mentioned
  that there was a problem with the load balancers.

  This happened at about 4pm PDT. The streaming API didnt send anything
  and neither terminated the connection. I restarted my streaming and it
  started working again. I have two streaming sessions, one from my host
  machine and another from my test machine, and both sessions had the
  same issue at the same time.

  Does Twitter recommend that we break the connection if no data arrives
  in some time and then restart it?

  /Amitab

  Twaller.com(@mytwaller)

  --
  Subscription 
  settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en


Re: [twitter-dev] Re: Streaming API TOS

2010-04-11 Thread John Kalucki
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) Borasky
zn...@comcast.netwrote:

 There is also the issue of what we can do with the Sample and Filter
 endpoints regarding, for example, tweets per day or tweets per second.
 It's not all that difficult or inaccurate to multiply Sample
 (Spritzer) tweet counts by 20. ;-) I think I'll post this one to the
 question list on Google Moderator.

 --
 M. Edward (Ed) Borasky
 http://borasky-research.net/m-edward-ed-borasky/ @znmeb

 A mathematician is a device for turning coffee into theorems. ~ Paul
 Erdős


 On 04/11/2010 05:54 PM, Dewald Pretorius wrote:
  Thanks for the quick response, John.
 
  The best will then be to wait for post-Chirp.
 
  As is, the current EULA could also be interpreted to prevent such
  uses, and that kind of nebulous wording is no basis upon which to
  expend any creative or development effort.
 
  On Apr 11, 9:20 pm, John Kalucki j...@twitter.com wrote:
  Both of those use cases are fine. The intent was to prevent people from
  publishing counts of Tweets per day or similar metrics. (I make no
 pretense
  at defending this intent, I'm the messenger.) Go forth and wordle.
 
  This EULA is near the end of its life and has been rewritten into the
  Commercial Data License, which Doug and Barkari will be discussing on
 day
  two of Chirp. If you have questions about how access under the EULA will
  evolve to access under the License, that would be a good place to start.
 
  -John Kaluckihttp://twitter.com/jkalucki
  Infrastructure, Twitter Inc.
 
 
 
  On Sun, Apr 11, 2010 at 4:22 PM, Dewald Pretorius dpr...@gmail.com
 wrote:
  With reference to:
  http://twitter.com/pdfs/streaming_api_eula.pdf
 
  Section 5 (ii) (e):
  You may only use the Content and Content Feed and any data resulting
  or provided therefrom for internal purposes only and, unless expressly
  authorized herein, you may not publicly release or disclose any data
  or usage statistics or other information (in the aggregate or
  otherwise) regarding the Content.
 
  Question:
 
  Assumimg I build a website that uses the Streaming API, is my
  interpretation correct that the following is against the TOS?
 
  1) Counting and displaying to the website users how many times the
  word earthquake occurs in tweets over a certain period of time.
 
  2) Building and displaying to the website users a tag cloud of words/
  phrases in tweets.- Hide quoted text -
 
  - Show quoted text -
 
 


 --
 M. Edward (Ed) Borasky
 borasky-research.net/m-edward-ed-borasky

 A mathematician is a device for turning coffee into theorems. ~ Paul
 Erdős


 --
 To unsubscribe, reply using remove me as the subject.



[twitter-dev] Re: Streaming API running dry again?

2010-04-01 Thread stephane
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 tweets
 arrive. If I manually kill the connection and reconnect everything
 works properly again (so I don't think my account somehow got banned).

 I know this issue popped up and was squashed not too long ago, but is
 anyone else experiencing this again recently?

 -Chad


Re: [twitter-dev] Re: Streaming API running dry again?

2010-04-01 Thread Mark McBride
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
 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 tweets
  arrive. If I manually kill the connection and reconnect everything
  works properly again (so I don't think my account somehow got banned).
 
  I know this issue popped up and was squashed not too long ago, but is
  anyone else experiencing this again recently?
 
  -Chad



-- 
To unsubscribe, reply using remove me as the subject.


[twitter-dev] Re: Streaming API running dry again?

2010-04-01 Thread Damon C
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 hour period the
 stream has run dry... the connection remains open but no tweets
 arrive. If I manually kill the connection and reconnect everything
 works properly again (so I don't think my account somehow got banned).

 I know this issue popped up and was squashed not too long ago, but is
 anyone else experiencing this again recently?

 -Chad


-- 
To unsubscribe, reply using remove me as the subject.


Re: [twitter-dev] Re: Streaming API running dry again?

2010-04-01 Thread Mark McBride
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 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
 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 tweets
  arrive. If I manually kill the connection and reconnect everything
  works properly again (so I don't think my account somehow got banned).
 
  I know this issue popped up and was squashed not too long ago, but is
  anyone else experiencing this again recently?
 
  -Chad





-- 
To unsubscribe, reply using remove me as the subject.


[twitter-dev] Re: Streaming API -- filtering with punctuation

2010-03-26 Thread Dewald Pretorius
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
  thrown against a HashMap to determine delivery. It's not really feasible to
  also throw arbitrary combinations of tokens against the HashMap. If we ever
  support AND, then you could search for ow AND ly.

  You'll have to over-request and filter on your end.

 This may have to wait till Chirp, but as long as we're on the subject of
 filtering at the consumer end, how good is *Cassandra* at that sort of
 filtering, relative to all the other databases, NoSQL and traditional
 ACID-compliant RDBMS? And how good is Cassandra relative to Hadoop?

 I've been thinking PostgreSQL in my designs, mostly because it's the one
 I know best, it's solid as a rock and I have friends who will disown me
 if I use MySQL. ;-) But using the same DB as Twitter has an appeal to it
 just because you *do* use it. And, of course, because NoSQL databases
 are cool and geeky. ;-)

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words REMOVE ME as the subject.


Re: [twitter-dev] Re: Streaming API -- filtering with punctuation

2010-03-26 Thread M. Edward (Ed) Borasky
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 text search, but I haven't seen a large community built up
around that like I have with the others.

In the end, I'll most likely end up with my own custom Perl / PostgreSQL
code, because most open-source licenses are too restrictive, I don't
know Python or Java well, and Ruby is too slow. PostgreSQL uses a BSD
license, which is a good thing. ;-)

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words REMOVE ME as the subject.


  1   2   3   >