date:20100721

Cant figure out if this is a problem with Twitter4J or the Twitter
API. I am trying to create an OAuth callback activity, started by a
RequestToken, but the Request Token request is failing. DOES ANYONE
KNOW IF GOOGLE HAS MADE THE TWITTER CLIENT AVAILABLE BY OPEN SOURCE
YET?

Twitter4J 2.1.2
Android Froyo 2.2

package com.sightlyinc.oauth.android;

import java.util.Date;

import twitter4j.Twitter;
import twitter4j.TwitterFactory;
import twitter4j.http.AccessToken;
import twitter4j.http.RequestToken;
import android.app.Activity;
import android.content.Intent;
import android.content.SharedPreferences;
import android.content.SharedPreferences.Editor;
import android.net.Uri;
import android.os.Bundle;
import android.preference.PreferenceManager;
import android.util.Log;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.EditText;
import android.widget.Toast;

public class SightlyOauthActivity extends Activity {

private static final String TAG =
SightlyOauthActivity.class.getName();

private Twitter twitter;
private RequestToken requestToken;
private SharedPreferences mSharedPreferences;

private String CONSUMER_KEY =   yfKRsmTgi8UT8eHoV5Khrw;
private String CONSUMER_SECRET =
4MIf93Wv35Choa5zXM0gQqIUD8uUFNcvAq1TPuBc;
private String CALLBACK_URL =   sightlyoauth://oauth;

private EditText tweetTextView;
private Button buttonLogin;

/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);

mSharedPreferences =
PreferenceManager.getDefaultSharedPreferences(
getApplicationContext());

tweetTextView =
(EditText)findViewById(R.id.TweetView);
buttonLogin = (Button)findViewById(R.id.ButtonLogon);
buttonLogin.setOnClickListener(new OnClickListener() {
public void onClick(View v) {
askOAuth();
}
});

}

/**
 * Open the browser and asks the user to authorize the app.
Afterwards, we
 * redirect the user back here!
 */
private void askOAuth() {
try {

//setup properties, https was attempted and I
was advised to
//use HTTPS instead.
 
System.setProperty(twitter4j.http.useSSL,false);
 
System.setProperty(twitter4j.oauth.consumerKey,MYKEY);
 
System.setProperty(twitter4j.oauth.consumerSecret,MYSECRET);
 
System.setProperty(twitter4j.oauth.requestTokenURL,http://
api.twitter.com/oauth/request_token);
 
System.setProperty(twitter4j.oauth.accessTokenURL,http://
api.twitter.com/oauth/access_token);
 
System.setProperty(twitter4j.oauth.authorizationURL,http://
api.twitter.com/oauth/authorize);

//get the instance
Twitter twitter =
new TwitterFactory().getInstance();

//THIS EXCEPTS WITH PERMISSION DENIED
requestToken =
twitter.getOAuthRequestToken(CALLBACK_URL);

//set the request token info
Toast.makeText(this, Please authorize this
app!,
Toast.LENGTH_LONG).show();

this.startActivity(new
Intent(Intent.ACTION_VIEW, Uri

.parse(requestToken.getAuthenticationURL(;

} catch (Exception e) {
Log.e(TAG, e.getMessage(),e);
Toast.makeText(this, e.getMessage(),
Toast.LENGTH_LONG).show();
}
}

/**
 * As soon as the user successfully authorized the app, we are
notified
 * here. Now we need to get the verifier from the callback
URL,
retrieve
 * token and token_secret and feed them to twitter4j (as well
as
consumer
 * key and secret).
 */
@Override
protected void onNewIntent(Intent intent) {

super.onNewIntent(intent);

Uri uri = intent.getData();
if (uri != null 
uri.toString().startsWith(CALLBACK_URL)) {

String verifier = uri
.getQueryParameter(oauth_verifier);

try {

//this user has verified
AccessToken accessToken =
 
twitter.getOAuthAccessToken(requestToken, verifier);

//save the access token
Editor e = mSharedPreferences.edit();
e.putString(AccessToken.token,
accessToken.getToken());

[twitter-dev] [search api] is it possible to search replies from a certain status_id?

2010-07-21 Thread arian

hi guys,
I need monitor replies from certain status.
I would like to use search api, but according to search api doc it's
impossible.
I only ask you to know for sure.

for example, I would like to be able ask for search api for replies
from a status providing in_reply_to_status_id value.

the only way I found is to ask for user timeline and check manually
the in_reply_to_status_id attribute.
is it the better way?

tks in advance
Arian

[twitter-dev] Twitter Stream API - Location filtering limited to the Western Hemisphere?

2010-07-21 Thread James

I'm attempting to stream Tweets from the UK as a whole(filtering
further with tracking words), using Twitters stream API, however I'm
having trouble with my bounding box.

The LAT/LON pairs I'm using to define a bounding box of the whoe
UK(Ire included) is as follows.

-9.05, 48.77, 2.19, 58.88

However when I try to use this with the Twitter stream API, it states
the following error message.

Location track must be less than 1 degrees on a side:
LocationTrack(48.77,-9.05,58.88,2.19)

I can't imagine that Twitter do not allow you a specify a bounding box
that covers an area that crosses between the negative/positive LAT. Am
I missing something here, or would this mean that Twitter only allow
you to stream if you are in the Wester hemishphere, effectively?

If anyone has a suggest as to how I might be able to over-come this,
I'd be very interested in hearing you out.

[twitter-dev] Re: Issues with OAuth

2010-07-21 Thread Kostya Nikolayev

Hi Matt,

Very appreciate your response!

It is working now after I quoted the oauth values.
So, the quoting matters.

Also, Consumer token was in place of OAuth one, and vice versa.

Thanks a lot,
Kostya

On Jul 21, 1:13 am, Matt Harris thematthar...@twitter.com wrote:
 Hey Kostya,

 I've taken a quick look at your POST headers and noticed a couple of things:

 1) Whilst it shouldn't matter the streaming API can be very particular about
 the headers you send so I recommend you quote your OAuth values,
 e.g. oauth_nonce=Rb34D3rVEetj

 2) Your OAuth token looks like a consumer token rather than a user one. Are
 you authenticating against the streaming API using your user token and
 secret?

 Hope that helps,

 Matt

 On Tue, Jul 20, 2010 at 3:04 PM, Taylor Singletary 



 taylorsinglet...@twitter.com wrote:
  Hi Kostya,

  I'm unable to reproduce your issue, unfortunately. Are you still getting a
  500 error when trying to connect to streaming via OAuth? Have you tried
  using a different access token or even API key? Does the same code/keys work
  against the REST API?

  Taylor

  On Tue, Jul 20, 2010 at 2:58 PM, Kostya Nikolayev 
  kostya1...@gmail.comwrote:

  Taylor,

  Did the details I posted help to identify the issue?

  Thanks,
  Kostya

  On Jul 20, 9:56 pm, ap aashish.pa...@gmail.com wrote:
   Looks like the oAuth access token issue is back! Started getting 500's
   from Twitter API a few minutes ago.

   On Jul 20, 11:38 am, Kostya Nikolayev kostya1...@gmail.com wrote:

Taylor!

This is what I'm sending:

POST /1/statuses/filter.json HTTP/1.1\r\nHost: stream.twitter.com\r
\nUser-Agent: TweetStream\r\nAuthorization: OAuth
oauth_nonce=0IblKRcN17LUBG6zMnQk6DVrObhzcZowIVpPLtsRviU,
oauth_signature=rbGAlSp1VIbuXbk4Wr99jumyi5o%3D,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279640138,
oauth_consumer_key=150423549-eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn,
oauth_token=tnruTl8uNRwGvICnzYpww, oauth_version=1.0\r\nContent-type:
application/x-www-form-urlencoded\r\nContent-length: 13\r\n\r
\ntrack=twitter

Signature base string is:

POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonoauth_consumer_key%3D150423549-
eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn%26oauth_nonce

  %3D0IblKRcN17LUBG6zMnQk6DVrObhzcZowIVpPLtsRviU%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1279640138%26oauth_token
%3DtnruTl8uNRwGvICnzYpww%26oauth_version%3D1.0%26track%3D

Thanks,
Kostya

On Jul 20, 6:18 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:

 Hi Kostya,

 I'm able to connect to the streaming API over OAuth fine at the
  moment.

 Can you share the full URL, HTTP method, and parameters that you are
  trying
 to access? If possible, also your signature base string?

 Taylor

 On Tue, Jul 20, 2010 at 8:09 AM, Kostya Nikolayev 
  kostya1...@gmail.comwrote:

  Taylor,

  Has Sreaming API OAuth been affected ?

  Authenticating with the following oauth header gives 500 to me:
  OAuth oauth_nonce=N9wgHt2uPw8HqRwtOpjuVDSeuVYmc8UGDF8H0237v0,
  oauth_signature=ALUT7tKXK%2Fw57SnJulj8x1l%2F7%2Fk%3D,
  oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279638245,

  oauth_consumer_key=150423549-eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn,
  oauth_token=tnruTl8uNRwGvICnzYpww, oauth_version=1.0

  Is it Streaming API OAuth issue?

  Thanks,
  Kostya

  On Jul 19, 10:59 pm, Taylor Singletary 
  taylorsinglet...@twitter.com
  wrote:
   Hi Ap,

   This is the right place for reporting issues like this -- well,
  one of
  the
   right places anyway -- we have some issues with OAuth today that
  are
  related
   to some wider issues related to updating objects associated with
  users
  (like
   access tokens).

   We hope to have this fixed soon!

   Thanks,
   Taylor

   On Mon, Jul 19, 2010 at 12:53 PM, ap aashish.pa...@gmail.com
  wrote:
I've been experiencing OAuth issues with my app today. If I'm
  already
logged into twitter, the OAuth redirects to my app just fine.
  However,
if I have to land on the authentication page and enter my
  username and
password and click submit, I get the following error:

Mon Jul 19 15:40:47 EDT 2010 : Twitter exception:
TwitterException{message=500:Something is broken.  Please post
  to the
group so the Twitter team can investigate.[Some HTML here],
statusCode=500, retryAfter=0, rateLimitStatus=null}

I'm not sure if this is the group that the message is asking
  me to
post in, if not, please let me know the correct group to post
  to so I
can get some assistance.

Thanks!

 --

 Matt Harris
 Developer Advocate, Twitterhttp://twitter.com/themattharris

[twitter-dev] Re: Coming soon: a solution for Open Source applications using OAuth with the Twitter API

2010-07-21 Thread Johnson Earls

Any further news on this?  It's been three weeks since you were
hoping to roll [it] out more widely this week.  I've got an app
registered and am starting to code it up, but would like to use the
key_exchange method instead, since there's no way at all to hide the
consumer secret in a python script.

Thanks,
- Johnson

On Jun 28, 8:02 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 The answer is soon! :) We hope to roll this out more widely this week.

 On Mon, Jun 28, 2010 at 7:56 AM, Decklin Foster deck...@red-bean.comwrote:

  Taylor Singletary wrote:
   We're waiting on a few minor bug fixes to be in place before rolling this
   out to a wider audience. I'll post a new message when things are good to
  go
   and we're ready to accept applications into the feature.

  Any update or ETA on this? I have an app that I'm eager to test out.
  (I notice that if you openhttp://dev.twitter.com/apps/key_exchange
  with a valid oauth_consumer_key, instead of a 404 there is a page that
  says Sorry, key exchange is not permitted for this application. Does
  this mean the answer is soon?)

  --
  things change.
  deck...@red-bean.com

Re: [twitter-dev] Twitter Stream API - Location filtering limited to the Western Hemisphere?

2010-07-21 Thread Dave Ingram

On 07/21/10 15:13, James wrote:
 I'm attempting to stream Tweets from the UK as a whole(filtering
 further with tracking words), using Twitters stream API, however I'm
 having trouble with my bounding box.

 The LAT/LON pairs I'm using to define a bounding box of the whoe
 UK(Ire included) is as follows.

 -9.05, 48.77, 2.19, 58.88

 However when I try to use this with the Twitter stream API, it states
 the following error message.

 Location track must be less than 1 degrees on a side:
 LocationTrack(48.77,-9.05,58.88,2.19)

 I can't imagine that Twitter do not allow you a specify a bounding box
 that covers an area that crosses between the negative/positive LAT. Am
 I missing something here, or would this mean that Twitter only allow
 you to stream if you are in the Wester hemishphere, effectively?

 If anyone has a suggest as to how I might be able to over-come this,
 I'd be very interested in hearing you out.
   
Just a thought, but the error says that the bounding box must be at most
one degree on each side... and that box is about 11x10. It does seem
like a bit of a restriction, but still...


D

[twitter-dev] Statuses/friends previous cursor broken

Hi. I am having the same problem as several others reported, where the
result of a statuses/friends sends back a previous cursor which is not
correct. The thread on this, from april or may, died with no
resolution. I notice that twitter itself has this same problem,
although twitter seems to use page=nnn instead of cursor=nnn, if you
try to go back to previous, it will list no users.

Is a fix planned for this?

thanks,

Mark

Re: [twitter-dev] Statuses/friends previous cursor broken

2010-07-21 Thread Scott Marshall

Yup, I encountered this as well while trying to figure out count
differences in what twitter reports on the number of followers and
what the api gives.  Seems to be off by one number.  So flipping
between pages on twitter itself (followers list) I did get those blank
results.  I found I had blocked a user a while back with twitter, and
this person was still being listed with results in the api but not on
twitter itself.  Might have thrown off the count that way.  Took care
of the so called blocked user, but unblocking and reblocking it.
count was still off.  But the follower was no longer in my api
results. Which is a good thing.  Still not sure why counts differ.

anyways, sorry for bringing up this count difference.  I just wanted
to say that I've came across the blank pages issue while flipping
back thru the followers list like Mark had mentioned.

On Wed, Jul 21, 2010 at 11:17 AM, Mark Krieger markskrie...@gmail.com wrote:
 Hi. I am having the same problem as several others reported, where the
 result of a statuses/friends sends back a previous cursor which is not
 correct. The thread on this, from april or may, died with no
 resolution. I notice that twitter itself has this same problem,
 although twitter seems to use page=nnn instead of cursor=nnn, if you
 try to go back to previous, it will list no users.

 Is a fix planned for this?

 thanks,

 Mark

Re: [twitter-dev] Twitter Stream API - Location filtering limited to the Western Hemisphere?

2010-07-21 Thread John Kalucki

If you need larger bounding boxes, you can request a higher access
level. You can also assemble a number of smaller bounding boxes into a
larger box to cover more area. So, you can divvy up your allocation
into a contiguous area, or multiple discontinuous regions.

If there's a bug on creating a legally-sized bounding box that
straddle one or both of the prime meridian or the equator, we'll
certainly fix that.

Given the proportion of geo-tagged tweets, perhaps we should indeed
make these boxes bigger for the default access role.

-John



On Wed, Jul 21, 2010 at 8:08 AM, Dave Ingram d...@dmi.me.uk wrote:
 On 07/21/10 15:13, James wrote:
 I'm attempting to stream Tweets from the UK as a whole(filtering
 further with tracking words), using Twitters stream API, however I'm
 having trouble with my bounding box.

 The LAT/LON pairs I'm using to define a bounding box of the whoe
 UK(Ire included) is as follows.

 -9.05, 48.77, 2.19, 58.88

 However when I try to use this with the Twitter stream API, it states
 the following error message.

 Location track must be less than 1 degrees on a side:
 LocationTrack(48.77,-9.05,58.88,2.19)

 I can't imagine that Twitter do not allow you a specify a bounding box
 that covers an area that crosses between the negative/positive LAT. Am
 I missing something here, or would this mean that Twitter only allow
 you to stream if you are in the Wester hemishphere, effectively?

 If anyone has a suggest as to how I might be able to over-come this,
 I'd be very interested in hearing you out.

 Just a thought, but the error says that the bounding box must be at most
 one degree on each side... and that box is about 11x10. It does seem
 like a bit of a restriction, but still...


 D

Re: [twitter-dev] Twitter Stream API - Location filtering limited to the Western Hemisphere?

2010-07-21 Thread M. Edward (Ed) Borasky


Quoting John Kalucki j...@twitter.com:


Given the proportion of geo-tagged tweets, perhaps we should indeed
make these boxes bigger for the default access role.


Any numbers you'd be willing to share? I'd hate to see you go with  
bigger boxes only to have to shrink them again when location picks up  
in Twitter hot-spots like PDX and SFO. Spritzer dropping from 5% to  
1% is kinda fresh in my mind. ;-)


--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos

[twitter-dev] Re: Twitter Stream API - Location filtering limited to the Western Hemisphere?

2010-07-21 Thread James

Ah, very true - apologies I mis-understood the meaning of 'degree'.
Thanks, I understand the problem now.

Seidr

On Jul 21, 4:08 pm, Dave Ingram d...@dmi.me.uk wrote:
 On 07/21/10 15:13, James wrote:

  I'm attempting to stream Tweets from the UK as a whole(filtering
  further with tracking words), using Twitters stream API, however I'm
  having trouble with my bounding box.

  The LAT/LON pairs I'm using to define a bounding box of the whoe
  UK(Ire included) is as follows.

  -9.05, 48.77, 2.19, 58.88

  However when I try to use this with the Twitter stream API, it states
  the following error message.

  Location track must be less than 1 degrees on a side:
  LocationTrack(48.77,-9.05,58.88,2.19)

  I can't imagine that Twitter do not allow you a specify a bounding box
  that covers an area that crosses between the negative/positive LAT. Am
  I missing something here, or would this mean that Twitter only allow
  you to stream if you are in the Wester hemishphere, effectively?

  If anyone has a suggest as to how I might be able to over-come this,
  I'd be very interested in hearing you out.

 Just a thought, but the error says that the bounding box must be at most
 one degree on each side... and that box is about 11x10. It does seem
 like a bit of a restriction, but still...

 D

[twitter-dev] Re: Issues with OAuth

2010-07-21 Thread Kostya Nikolayev

Matt,

Another question I believe you may clarify.

Streaming API over OAuth works fine if track only one item:
track=sun
When I want to track multiple items like track=sun,microsoft I'm
getting 401

There is what I'm sending:

POST /1/statuses/filter.json HTTP/1.1\r\nHost: stream.twitter.com\r
\nUser-Agent: TweetStream\r\nAuthorization: OAuth
oauth_nonce=mTzWO7xxDbK11EvFJ1d90jXI2MMM8jN1b3Eh4KTZk,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279727860,
oauth_signature=SpY5JkbnWBWkI5qCzOWUMHUTNgM%3D,
oauth_consumer_key=tnruTl8uNRwGvICnzYpww, oauth_token=150423549-
eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn, oauth_version=1.0\r
\nContent-type: application/x-www-form-urlencoded\r\nContent-length:
21\r\n\r\ntrack=sun%2Cmicrosoft

Signature base string is:

POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonoauth_consumer_key%3DtnruTl8uNRwGvICnzYpww%26oauth_nonce
%3DmTzWO7xxDbK11EvFJ1d90jXI2MMM8jN1b3Eh4KTZk%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1279727860%26oauth_token%3D150423549-
eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn%26oauth_version%3D1.0%26track
%3Dsun%2Cmicrosoft

Thanks,
Kostya

On Jul 21, 5:17 pm, Kostya Nikolayev kostya1...@gmail.com wrote:
 Hi Matt,

 Very appreciate your response!

 It is working now after I quoted the oauth values.
 So, the quoting matters.

 Also, Consumer token was in place of OAuth one, and vice versa.

 Thanks a lot,
 Kostya

 On Jul 21, 1:13 am, Matt Harris thematthar...@twitter.com wrote:

  Hey Kostya,

  I've taken a quick look at your POST headers and noticed a couple of things:

  1) Whilst it shouldn't matter the streaming API can be very particular about
  the headers you send so I recommend you quote your OAuth values,
  e.g. oauth_nonce=Rb34D3rVEetj

  2) Your OAuth token looks like a consumer token rather than a user one. Are
  you authenticating against the streaming API using your user token and
  secret?

  Hope that helps,

  Matt

  On Tue, Jul 20, 2010 at 3:04 PM, Taylor Singletary 

  taylorsinglet...@twitter.com wrote:
   Hi Kostya,

   I'm unable to reproduce your issue, unfortunately. Are you still getting a
   500 error when trying to connect to streaming via OAuth? Have you tried
   using a different access token or even API key? Does the same code/keys 
   work
   against the REST API?

   Taylor

   On Tue, Jul 20, 2010 at 2:58 PM, Kostya Nikolayev 
   kostya1...@gmail.comwrote:

   Taylor,

   Did the details I posted help to identify the issue?

   Thanks,
   Kostya

   On Jul 20, 9:56 pm, ap aashish.pa...@gmail.com wrote:
Looks like the oAuth access token issue is back! Started getting 500's
from Twitter API a few minutes ago.

On Jul 20, 11:38 am, Kostya Nikolayev kostya1...@gmail.com wrote:

 Taylor!

 This is what I'm sending:

 POST /1/statuses/filter.json HTTP/1.1\r\nHost: stream.twitter.com\r
 \nUser-Agent: TweetStream\r\nAuthorization: OAuth
 oauth_nonce=0IblKRcN17LUBG6zMnQk6DVrObhzcZowIVpPLtsRviU,
 oauth_signature=rbGAlSp1VIbuXbk4Wr99jumyi5o%3D,
 oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279640138,
 oauth_consumer_key=150423549-eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn,
 oauth_token=tnruTl8uNRwGvICnzYpww, oauth_version=1.0\r\nContent-type:
 application/x-www-form-urlencoded\r\nContent-length: 13\r\n\r
 \ntrack=twitter

 Signature base string is:

 POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
 %2Ffilter.jsonoauth_consumer_key%3D150423549-
 eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn%26oauth_nonce

   %3D0IblKRcN17LUBG6zMnQk6DVrObhzcZowIVpPLtsRviU%26oauth_signature_method
 %3DHMAC-SHA1%26oauth_timestamp%3D1279640138%26oauth_token
 %3DtnruTl8uNRwGvICnzYpww%26oauth_version%3D1.0%26track%3D

 Thanks,
 Kostya

 On Jul 20, 6:18 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:

  Hi Kostya,

  I'm able to connect to the streaming API over OAuth fine at the
   moment.

  Can you share the full URL, HTTP method, and parameters that you 
  are
   trying
  to access? If possible, also your signature base string?

  Taylor

  On Tue, Jul 20, 2010 at 8:09 AM, Kostya Nikolayev 
   kostya1...@gmail.comwrote:

   Taylor,

   Has Sreaming API OAuth been affected ?

   Authenticating with the following oauth header gives 500 to me:
   OAuth oauth_nonce=N9wgHt2uPw8HqRwtOpjuVDSeuVYmc8UGDF8H0237v0,
   oauth_signature=ALUT7tKXK%2Fw57SnJulj8x1l%2F7%2Fk%3D,
   oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279638245,

   oauth_consumer_key=150423549-eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn,
   oauth_token=tnruTl8uNRwGvICnzYpww, oauth_version=1.0

   Is it Streaming API OAuth issue?

   Thanks,
   Kostya

   On Jul 19, 10:59 pm, Taylor Singletary 
   taylorsinglet...@twitter.com
   wrote:
Hi Ap,

This is the right place for reporting issues like this -- well,
   one of
   the
right places anyway -- we have

Re: [twitter-dev] Re: Issues with OAuth

Hi Kostya,

You're close on getting the comma-separation to work. You've correctly
URL encoded it for your POST body, but for the OAuth signature base
string, it'll need to be doubly encoded.

Your base string should be something like:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonoauth_consumer_key%3DtnruTl8uNRwGvICnzYpww%26oauth_nonce
%3DmTzWO7xxDbK11EvFJ1d90jXI2MMM8jN1b3Eh4KTZk%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1279727860%26oauth_token%3D150423549-
eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn%26oauth_version%3D1.0%26track
%3Dsun%252Cmicrosoft

%2C becomes %252C..

Taylor

On Wed, Jul 21, 2010 at 9:09 AM, Kostya Nikolayev kostya1...@gmail.com wrote:
 Matt,

 Another question I believe you may clarify.

 Streaming API over OAuth works fine if track only one item:
 track=sun
 When I want to track multiple items like track=sun,microsoft I'm
 getting 401

 There is what I'm sending:

 POST /1/statuses/filter.json HTTP/1.1\r\nHost: stream.twitter.com\r
 \nUser-Agent: TweetStream\r\nAuthorization: OAuth
 oauth_nonce=mTzWO7xxDbK11EvFJ1d90jXI2MMM8jN1b3Eh4KTZk,
 oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279727860,
 oauth_signature=SpY5JkbnWBWkI5qCzOWUMHUTNgM%3D,
 oauth_consumer_key=tnruTl8uNRwGvICnzYpww, oauth_token=150423549-
 eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn, oauth_version=1.0\r
 \nContent-type: application/x-www-form-urlencoded\r\nContent-length:
 21\r\n\r\ntrack=sun%2Cmicrosoft

 Signature base string is:

 POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
 %2Ffilter.jsonoauth_consumer_key%3DtnruTl8uNRwGvICnzYpww%26oauth_nonce
 %3DmTzWO7xxDbK11EvFJ1d90jXI2MMM8jN1b3Eh4KTZk%26oauth_signature_method
 %3DHMAC-SHA1%26oauth_timestamp%3D1279727860%26oauth_token%3D150423549-
 eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn%26oauth_version%3D1.0%26track
 %3Dsun%2Cmicrosoft

 Thanks,
 Kostya

 On Jul 21, 5:17 pm, Kostya Nikolayev kostya1...@gmail.com wrote:
 Hi Matt,

 Very appreciate your response!

 It is working now after I quoted the oauth values.
 So, the quoting matters.

 Also, Consumer token was in place of OAuth one, and vice versa.

 Thanks a lot,
 Kostya

 On Jul 21, 1:13 am, Matt Harris thematthar...@twitter.com wrote:

  Hey Kostya,

  I've taken a quick look at your POST headers and noticed a couple of 
  things:

  1) Whilst it shouldn't matter the streaming API can be very particular 
  about
  the headers you send so I recommend you quote your OAuth values,
  e.g. oauth_nonce=Rb34D3rVEetj

  2) Your OAuth token looks like a consumer token rather than a user one. Are
  you authenticating against the streaming API using your user token and
  secret?

  Hope that helps,

  Matt

  On Tue, Jul 20, 2010 at 3:04 PM, Taylor Singletary 

  taylorsinglet...@twitter.com wrote:
   Hi Kostya,

   I'm unable to reproduce your issue, unfortunately. Are you still getting 
   a
   500 error when trying to connect to streaming via OAuth? Have you tried
   using a different access token or even API key? Does the same code/keys 
   work
   against the REST API?

   Taylor

   On Tue, Jul 20, 2010 at 2:58 PM, Kostya Nikolayev 
   kostya1...@gmail.comwrote:

   Taylor,

   Did the details I posted help to identify the issue?

   Thanks,
   Kostya

   On Jul 20, 9:56 pm, ap aashish.pa...@gmail.com wrote:
Looks like the oAuth access token issue is back! Started getting 500's
from Twitter API a few minutes ago.

On Jul 20, 11:38 am, Kostya Nikolayev kostya1...@gmail.com wrote:

 Taylor!

 This is what I'm sending:

 POST /1/statuses/filter.json HTTP/1.1\r\nHost: stream.twitter.com\r
 \nUser-Agent: TweetStream\r\nAuthorization: OAuth
 oauth_nonce=0IblKRcN17LUBG6zMnQk6DVrObhzcZowIVpPLtsRviU,
 oauth_signature=rbGAlSp1VIbuXbk4Wr99jumyi5o%3D,
 oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279640138,
 oauth_consumer_key=150423549-eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn,
 oauth_token=tnruTl8uNRwGvICnzYpww, 
 oauth_version=1.0\r\nContent-type:
 application/x-www-form-urlencoded\r\nContent-length: 13\r\n\r
 \ntrack=twitter

 Signature base string is:

 POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
 %2Ffilter.jsonoauth_consumer_key%3D150423549-
 eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn%26oauth_nonce

   %3D0IblKRcN17LUBG6zMnQk6DVrObhzcZowIVpPLtsRviU%26oauth_signature_method
 %3DHMAC-SHA1%26oauth_timestamp%3D1279640138%26oauth_token
 %3DtnruTl8uNRwGvICnzYpww%26oauth_version%3D1.0%26track%3D

 Thanks,
 Kostya

 On Jul 20, 6:18 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:

  Hi Kostya,

  I'm able to connect to the streaming API over OAuth fine at the
   moment.

  Can you share the full URL, HTTP method, and parameters that you 
  are
   trying
  to access? If possible, also your signature base string?

  Taylor

  On Tue, Jul 20, 2010 at 8:09 AM, Kostya Nikolayev 
   kostya1...@gmail.comwrote:

   Taylor,

   Has Sreaming API

[twitter-dev] Re: is it possible to search replies from a certain status_id?

2010-07-21 Thread tsmango

Unfortunately, there isn't a single API method that allows this.

From the FAQ: http://dev.twitter.com/pages/api_faq#replies

Q: How do I get all replies to a particular status?
A: For now, there's not a great way to do this. We've heard the
requests, though, and we'll be providing a solution for it before too
long.

On Jul 21, 8:15 am, arian arianpasqu...@gmail.com wrote:
 hi guys,
 I need monitor replies from certain status.
 I would like to use search api, but according to search api doc it's
 impossible.
 I only ask you to know for sure.

 for example, I would like to be able ask for search api for replies
 from a status providing in_reply_to_status_id value.

 the only way I found is to ask for user timeline and check manually
 the in_reply_to_status_id attribute.
 is it the better way?

 tks in advance
 Arian

[twitter-dev] Re: Statuses/friends previous cursor broken

Matt,

Thank you. This has been open for about 4 months. I hope it will be
fixed soon. For now I think I will need to do something on my own to
program around it. Wish me good luck (:

Mark

On Jul 21, 1:37 pm, Matt Harris thematthar...@twitter.com wrote:
 Thanks for the emails on this one. It is a known issue which our engineering
 team are looking into. It is being tracked on our issue tracker 
 here:http://code.google.com/p/twitter-api/issues/detail?id=1572

 When we have news on the progress we'll update the ticket.

 Best,
 Matt



 On Wed, Jul 21, 2010 at 8:32 AM, Scott Marshall marsh...@gmail.com wrote:
  Yup, I encountered this as well while trying to figure out count
  differences in what twitter reports on the number of followers and
  what the api gives.  Seems to be off by one number.  So flipping
  between pages on twitter itself (followers list) I did get those blank
  results.  I found I had blocked a user a while back with twitter, and
  this person was still being listed with results in the api but not on
  twitter itself.  Might have thrown off the count that way.  Took care
  of the so called blocked user, but unblocking and reblocking it.
  count was still off.  But the follower was no longer in my api
  results. Which is a good thing.  Still not sure why counts differ.

  anyways, sorry for bringing up this count difference.  I just wanted
  to say that I've came across the blank pages issue while flipping
  back thru the followers list like Mark had mentioned.

  On Wed, Jul 21, 2010 at 11:17 AM, Mark Krieger markskrie...@gmail.com
  wrote:
   Hi. I am having the same problem as several others reported, where the
   result of a statuses/friends sends back a previous cursor which is not
   correct. The thread on this, from april or may, died with no
   resolution. I notice that twitter itself has this same problem,
   although twitter seems to use page=nnn instead of cursor=nnn, if you
   try to go back to previous, it will list no users.

   Is a fix planned for this?

   thanks,

   Mark

 --

 Matt Harris
 Developer Advocate, Twitterhttp://twitter.com/themattharris

Re: [twitter-dev] Re: Problems Loading Profile Images

Hi Everyone,

We had some issues with profile updates and image uploads last week
and early this week. Some images uploaded in that time period resulted
in incorrect image URLs, and while this should now be fixed for more
recently updated/created images, those with avatars saved while in
this state will likely remain in that state until they re-upload their
image.

What kind of percentages are you seeing in regards to missing/broken images?

Taylor

On Wed, Jul 21, 2010 at 5:35 AM, luisg luisfmgoncal...@gmail.com wrote:
 I'm having the same problem too... But just sometimes.
 Anyway, looks like Twitter is better now... At least is not so slow as
 was a couple of weeks ago.

 On Jul 21, 4:59 am, Ron rbther...@gmail.com wrote:
 Anyone noticing problems loading profile images (slow, no image
 returned, hanging...)?  Seems to show up mostly on Public and Search
 endpoints.

Re: [twitter-dev] Problems with Twitter4J and OAuth on Android

Hi Clay,

Just noticed that you have an API secret in this code sample you've
provided -- you'll want to go to your application record and
regenerate a new key/secret pair.

As for the code itself -- I see you setting your consumer key and
secret as constants near the top, but then in askOAuth you're using
different values -- is this just a result of a bad paste?

Taylor

On Tue, Jul 20, 2010 at 11:18 PM, Clay Graham claytan...@sightlyinc.com wrote:
 Cant figure out if this is a problem with Twitter4J or the Twitter
 API. I am trying to create an OAuth callback activity, started by a
 RequestToken, but the Request Token request is failing. DOES ANYONE
 KNOW IF GOOGLE HAS MADE THE TWITTER CLIENT AVAILABLE BY OPEN SOURCE
 YET?

 Twitter4J 2.1.2
 Android Froyo 2.2

 package com.sightlyinc.oauth.android;

 import java.util.Date;

 import twitter4j.Twitter;
 import twitter4j.TwitterFactory;
 import twitter4j.http.AccessToken;
 import twitter4j.http.RequestToken;
 import android.app.Activity;
 import android.content.Intent;
 import android.content.SharedPreferences;
 import android.content.SharedPreferences.Editor;
 import android.net.Uri;
 import android.os.Bundle;
 import android.preference.PreferenceManager;
 import android.util.Log;
 import android.view.View;
 import android.view.View.OnClickListener;
 import android.widget.Button;
 import android.widget.EditText;
 import android.widget.Toast;

 public class SightlyOauthActivity extends Activity {

    private static final String TAG =
 SightlyOauthActivity.class.getName();

    private Twitter twitter;
    private RequestToken requestToken;
    private SharedPreferences mSharedPreferences;

    private String CONSUMER_KEY =           yfKRsmTgi8UT8eHoV5Khrw;
    private String CALLBACK_URL =           sightlyoauth://oauth;

    private EditText tweetTextView;
    private Button buttonLogin;

        /** Called when the activity is first created. */
       �...@override
        public void onCreate(Bundle savedInstanceState) {
                super.onCreate(savedInstanceState);
                setContentView(R.layout.main);

                mSharedPreferences =
                        PreferenceManager.getDefaultSharedPreferences(
                                        getApplicationContext());

                tweetTextView =
 (EditText)findViewById(R.id.TweetView);
        buttonLogin = (Button)findViewById(R.id.ButtonLogon);
        buttonLogin.setOnClickListener(new OnClickListener() {
                public void onClick(View v) {
                        askOAuth();
                }
        });

        }

        /**
         * Open the browser and asks the user to authorize the app.
 Afterwards, we
         * redirect the user back here!
         */
        private void askOAuth() {
                try {

                        //setup properties, https was attempted and I
 was advised to
                        //use HTTPS instead.

 System.setProperty(twitter4j.http.useSSL,false);

 System.setProperty(twitter4j.oauth.consumerKey,MYKEY);

 System.setProperty(twitter4j.oauth.consumerSecret,MYSECRET);

 System.setProperty(twitter4j.oauth.requestTokenURL,http://
 api.twitter.com/oauth/request_token);

 System.setProperty(twitter4j.oauth.accessTokenURL,http://
 api.twitter.com/oauth/access_token);

 System.setProperty(twitter4j.oauth.authorizationURL,http://
 api.twitter.com/oauth/authorize);

                        //get the instance
                        Twitter twitter =
                                new TwitterFactory().getInstance();

                        //THIS EXCEPTS WITH PERMISSION DENIED
                        requestToken =
 twitter.getOAuthRequestToken(CALLBACK_URL);

                        //set the request token info
                        Toast.makeText(this, Please authorize this
 app!,
                                        Toast.LENGTH_LONG).show();

                        this.startActivity(new
 Intent(Intent.ACTION_VIEW, Uri
                                        
 .parse(requestToken.getAuthenticationURL(;

                } catch (Exception e) {
                        Log.e(TAG, e.getMessage(),e);
                        Toast.makeText(this, e.getMessage(),
 Toast.LENGTH_LONG).show();
                }
        }

        /**
         * As soon as the user successfully authorized the app, we are
 notified
         * here. Now we need to get the verifier from the callback
 URL,
 retrieve
         * token and token_secret and feed them to twitter4j (as well
 as
 consumer
         * key and secret).
         */
       �...@override
        protected void onNewIntent(Intent intent) {

                super.onNewIntent(intent);

                Uri uri = intent.getData();
                if (uri != null 
 uri.toString().startsWith(CALLBACK_URL)) {

                        String verifier = uri
                                        .getQueryParameter(oauth_verifier);

                        try {

[twitter-dev] Trying to do a GET after autenticating via OAuth

2010-07-21 Thread clinisbut

Hello everybody.

I just achieved to autenticate via OAuth, and I'm trying to get user's
data through account/verify_credentials but I think I'm not building
correctly the composite signing key or something, mainly because I'm
not able to fully understand all the different tokens I receive from
Twitter.

After I got my access token, I got:

An oauth_token in the form of: /¿User-ID?/-/letters+numbers/
An oauth_token_secret

Which one I should use to built the composite key? In 
http://dev.twitter.com/pages/auth
they use the first oauth_token getted in the request token, and in the
Resource request example they use the oauth_token_secret.


These is the headers I sent:

OAuth oauth_consumer_key=XX,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279738886,
oauth_nonce=a97ff8b71a313a03a650068e1e6b9bd8f31ad04f,
oauth_version=1.0, oauth_token=-
X, oauth_signature=0OFTpLp8o
%2BL9%2B6o8mkRdBSS8I84%3D

and then I do a GET request to: 
http://api.twitter.com/1/account/verify_credentials.json


But all I got is:
401 Unauthorized
Failed to validate oauth signature and token

Re: [twitter-dev] Whitelist confirmation . . .

Hi there,

We're a bit behind on processing whitelisting requests, as we had a
hiatus of approving requests during the World Cup. Whitelisting is a
privilege granted on a case-by-case basis (criteria and acceptance
rates change over time), but we don't generally provide whitelisting
for research or academic purposes.

In most cases, researchers (and developers) wanting expanded access to
the Search API would be better served by implementing the Streaming
API instead. Rate limits are in place to ensure best performance for
the highest number of users. While higher limits would benefit the
speed at which many research projects may be completed, the vast
majority will have to make do with the current rate limits.

Rate limiting, whitelisting and their role within the Twitter
ecosystem are reviewed frequently.

Thanks,
Taylor

On Tue, Jul 20, 2010 at 7:34 PM, hkimscil hkims...@gmail.com wrote:
Hello, this is a followup message to the previous post at
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/36a11ab23b42f22/48c15312a2aab773?lnk=gstq=hkimscil#48c15312a2aab773
.

I am not still getting a confirmation for whitelist; and beginning to
think that I may not be approved :( . And I am worried about not
clarifying enough about my research work to the twitter.

What I am trying to do is not builidn applications or services;
Rather, want to gather some data (tweets and retweets messages with
specific topics) in order to see how messages are diffused and how
they are possibly categorised or classified (if any, SEARCH API); and
how they are compared to agenda set by traditional mass media such as
newspapers and television. I am also interested in what kinds of
social relations exists in the message diffusion processes (REST
API).

I have setup about 20 computers in order to collect necessary data --
so that I don't have to use APIs for a long period of time. I have
setup the brief explanation about my research at
http://wiki.commres.org/Project~Twitter

I would appreciate if anyone shed a light on what I went wrong (if I
did while requesting) and give some advice on how to persuade the
twitter for putting me on the whitelist.

[twitter-dev] Re: Trying to do a GET after autenticating via OAuth

2010-07-21 Thread clinisbut

I'm using an OAuth library I've developed in PHP.

Do I need to pass all the parameters through the query also?




On Jul 21, 9:25 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 Hi there,

 If you've gotten to the point of retrieving an access token, it's
 likely you managed to get the composite signing key right (or your
 library handled it for you) -- as when you're exchanging the request
 token for an access token, you use the oauth_token_secret from the
 request token as part of the signing key. Are you using an OAuth
 library?

 When you're making a resource request such as one to
 verify_credentials, you'll use the oauth_token_secret you received in
 the access token step as part of the signing key: $consumer_secret +
  + $oauth_token_secret

 Taylor

 On Wed, Jul 21, 2010 at 12:13 PM, clinisbut clinis...@gmail.com wrote:
  Hello everybody.

  I just achieved to autenticate via OAuth, and I'm trying to get user's
  data through account/verify_credentials but I think I'm not building
  correctly the composite signing key or something, mainly because I'm
  not able to fully understand all the different tokens I receive from
  Twitter.

  After I got my access token, I got:

  An oauth_token in the form of: /¿User-ID?/-/letters+numbers/
  An oauth_token_secret

  Which one I should use to built the composite key? 
  Inhttp://dev.twitter.com/pages/auth
  they use the first oauth_token getted in the request token, and in the
  Resource request example they use the oauth_token_secret.

  These is the headers I sent:

  OAuth oauth_consumer_key=XX,
  oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279738886,
  oauth_nonce=a97ff8b71a313a03a650068e1e6b9bd8f31ad04f,
  oauth_version=1.0, oauth_token=-
  X, oauth_signature=0OFTpLp8o
  %2BL9%2B6o8mkRdBSS8I84%3D

  and then I do a GET request 
  to:http://api.twitter.com/1/account/verify_credentials.json

  But all I got is:
  401 Unauthorized
  Failed to validate oauth signature and token

[twitter-dev] TweetBox on my site

2010-07-21 Thread cody wilmoth

Can someone help me get the tweetbox working on my site please? It
will not show up after I click on a link that brings a jQuery pop-up
and displays the tweetbox in their, but it won't work.

My site is http://lowprogaming.codywd.com

Thanks,
@Cody_Wilmoth

[twitter-dev] Re: Trying to do a GET after autenticating via OAuth

2010-07-21 Thread clinisbut

Ok, I just discovered http://dev.twitter.com/console, I'm matching the
composite signing key created by this console and mine and don't match
(obviously I'm using the same visible parameter values (timestamp,
nonce, oauth_token and consumer key) and my composite signing it's not
hte same...

On Jul 21, 10:03 pm, clinisbut clinis...@gmail.com wrote:
 I'm using an OAuth library I've developed in PHP.

 Do I need to pass all the parameters through the query also?

 On Jul 21, 9:25 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:

  Hi there,

  If you've gotten to the point of retrieving an access token, it's
  likely you managed to get the composite signing key right (or your
  library handled it for you) -- as when you're exchanging the request
  token for an access token, you use the oauth_token_secret from the
  request token as part of the signing key. Are you using an OAuth
  library?

  When you're making a resource request such as one to
  verify_credentials, you'll use the oauth_token_secret you received in
  the access token step as part of the signing key: $consumer_secret +
   + $oauth_token_secret

  Taylor

  On Wed, Jul 21, 2010 at 12:13 PM, clinisbut clinis...@gmail.com wrote:
   Hello everybody.

   I just achieved to autenticate via OAuth, and I'm trying to get user's
   data through account/verify_credentials but I think I'm not building
   correctly the composite signing key or something, mainly because I'm
   not able to fully understand all the different tokens I receive from
   Twitter.

   After I got my access token, I got:

   An oauth_token in the form of: /¿User-ID?/-/letters+numbers/
   An oauth_token_secret

   Which one I should use to built the composite key? 
   Inhttp://dev.twitter.com/pages/auth
   they use the first oauth_token getted in the request token, and in the
   Resource request example they use the oauth_token_secret.

   These is the headers I sent:

   OAuth oauth_consumer_key=XX,
   oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279738886,
   oauth_nonce=a97ff8b71a313a03a650068e1e6b9bd8f31ad04f,
   oauth_version=1.0, oauth_token=-
   X, oauth_signature=0OFTpLp8o
   %2BL9%2B6o8mkRdBSS8I84%3D

   and then I do a GET request 
   to:http://api.twitter.com/1/account/verify_credentials.json

   But all I got is:
   401 Unauthorized
   Failed to validate oauth signature and token

Re: [twitter-dev] getStatusesMentions not working today....???

2010-07-21 Thread Matt Harris

Hi Mark,

We aren't seeing any errors like this when we run some tests. Could you
elaborate on what the bogus headers are?

Matt

On Wed, Jul 21, 2010 at 12:51 PM, Mark Krieger markskrie...@gmail.comwrote:

 My application has used getStatusesMentions for many months, it is
 only failing when twitter has had some problem, like two days ago, and
 in that case, everything is flaky. Today it is failing, but everything
 else works fine. Is this a known problem today? getStatusesMentions
 always comes back today with bogus headers

 Mark




-- 


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

[twitter-dev] Re: getStatusesMentions not working today....???

Matt,

Thanks for the quick response. The call uses EpiTwitter.php, it looks
like:

Call Oauth to authenticate (this works), then:

$val = $twitterObj-get_statusesMentions(array('since_id' =
$lastid));
$arr = json_decode($val-responseText, true);
if (empty($arr)) { $error = error text; log_message(...)}
else ...

It logs the error text showing the response through EpiTwitter was
empty. Also, when I print $val-responseText, it is EMPTY.

I've tried it on 4 twitter accounts I have, all of which have worked
for many months in code which has not changed, it has only failed
before when the api was down (like tuesday). And all other api calls
which use similar code all work fine. I am stumped.

I can send more data, like the $lastid, and my credentials for oauth
to you, I would of course do that privately. I will run some more
tests from here first I guess.

Thanks,

Mark
On Jul 21, 4:49 pm, Matt Harris thematthar...@twitter.com wrote:
 Hi Mark,

 We aren't seeing any errors like this when we run some tests. Could you
 elaborate on what the bogus headers are?

 Matt

 On Wed, Jul 21, 2010 at 12:51 PM, Mark Krieger markskrie...@gmail.comwrote:

  My application has used getStatusesMentions for many months, it is
  only failing when twitter has had some problem, like two days ago, and
  in that case, everything is flaky. Today it is failing, but everything
  else works fine. Is this a known problem today? getStatusesMentions
  always comes back today with bogus headers

  Mark

 --

 Matt Harris
 Developer Advocate, Twitterhttp://twitter.com/themattharris

[twitter-dev] Re: getStatusesMentions not working today....???

Matt,

I found the problem, sorry, I believe it is on my end. I found a line
of code someone here changed. Argh. I will be more careful with your
time in the future.

Mark

On Jul 21, 6:00 pm, Mark Krieger markskrie...@gmail.com wrote:
 Matt,

 Thanks for the quick response. The call uses EpiTwitter.php, it looks
 like:

 Call Oauth to authenticate (this works), then:

 $val = $twitterObj-get_statusesMentions(array('since_id' =
 $lastid));
 $arr = json_decode($val-responseText, true);
 if (empty($arr)) { $error = error text; log_message(...)}
 else ...

 It logs the error text showing the response through EpiTwitter was
 empty. Also, when I print $val-responseText, it is EMPTY.

 I've tried it on 4 twitter accounts I have, all of which have worked
 for many months in code which has not changed, it has only failed
 before when the api was down (like tuesday). And all other api calls
 which use similar code all work fine. I am stumped.

 I can send more data, like the $lastid, and my credentials for oauth
 to you, I would of course do that privately. I will run some more
 tests from here first I guess.

 Thanks,

 Mark
 On Jul 21, 4:49 pm, Matt Harris thematthar...@twitter.com wrote:

  Hi Mark,

  We aren't seeing any errors like this when we run some tests. Could you
  elaborate on what the bogus headers are?

  Matt

  On Wed, Jul 21, 2010 at 12:51 PM, Mark Krieger 
  markskrie...@gmail.comwrote:

   My application has used getStatusesMentions for many months, it is
   only failing when twitter has had some problem, like two days ago, and
   in that case, everything is flaky. Today it is failing, but everything
   else works fine. Is this a known problem today? getStatusesMentions
   always comes back today with bogus headers

   Mark

  --

  Matt Harris
  Developer Advocate, Twitterhttp://twitter.com/themattharris

Re: [twitter-dev] Re: getStatusesMentions not working today....???

2010-07-21 Thread Matt Harris

Hey Mark,

Not a problem. Glad you found the source of the error.
Best,
Matt

On Wed, Jul 21, 2010 at 3:11 PM, Mark Krieger markskrie...@gmail.comwrote:

 Matt,

 I found the problem, sorry, I believe it is on my end. I found a line
 of code someone here changed. Argh. I will be more careful with your
 time in the future.

 Mark

 On Jul 21, 6:00 pm, Mark Krieger markskrie...@gmail.com wrote:
  Matt,
 
  Thanks for the quick response. The call uses EpiTwitter.php, it looks
  like:
 
  Call Oauth to authenticate (this works), then:
 
  $val = $twitterObj-get_statusesMentions(array('since_id' =
  $lastid));
  $arr = json_decode($val-responseText, true);
  if (empty($arr)) { $error = error text; log_message(...)}
  else ...
 
  It logs the error text showing the response through EpiTwitter was
  empty. Also, when I print $val-responseText, it is EMPTY.
 
  I've tried it on 4 twitter accounts I have, all of which have worked
  for many months in code which has not changed, it has only failed
  before when the api was down (like tuesday). And all other api calls
  which use similar code all work fine. I am stumped.
 
  I can send more data, like the $lastid, and my credentials for oauth
  to you, I would of course do that privately. I will run some more
  tests from here first I guess.
 
  Thanks,
 
  Mark
  On Jul 21, 4:49 pm, Matt Harris thematthar...@twitter.com wrote:
 
   Hi Mark,
 
   We aren't seeing any errors like this when we run some tests. Could you
   elaborate on what the bogus headers are?
 
   Matt
 
   On Wed, Jul 21, 2010 at 12:51 PM, Mark Krieger markskrie...@gmail.com
 wrote:
 
My application has used getStatusesMentions for many months, it is
only failing when twitter has had some problem, like two days ago,
 and
in that case, everything is flaky. Today it is failing, but
 everything
else works fine. Is this a known problem today? getStatusesMentions
always comes back today with bogus headers
 
Mark
 
   --
 
   Matt Harris
   Developer Advocate, Twitterhttp://twitter.com/themattharris




-- 


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

Re: [twitter-dev] Re: Trying to do a GET after autenticating via OAuth

Hi,

Know it sounds strange, but I'd stay away from the dev.twitter.com
console when trying to debug an issue like this. Even if it weren't
buggy, the execution path it uses to perform OAuth operations is a bit
different than what you typically would do in your own implementation.

Are you married to the idea of using a homebrew OAuth library? Not to
dissuade you too much, but there are a number of good libraries in PHP
out there both for Twitter and OAuth -- at the very least, I would
recommend using one of these as a reference for your own
implementation. OAuth is difficult for many even when using
well-written libraries.. (See
http://dev.twitter.com/pages/oauth_libraries#php and
http://dev.twitter.com/pages/libraries#php )

If you are set on writing your own library, I recommend using HTTP
header based OAuth (as opposed to attaching OAuth parameters to the
query string) -- it keeps your concerns separate, making it much
easier to debug when things go wrong.

Taylor

On Wed, Jul 21, 2010 at 1:39 PM, clinisbut clinis...@gmail.com wrote:
 Ok, I just discovered http://dev.twitter.com/console, I'm matching the
 composite signing key created by this console and mine and don't match
 (obviously I'm using the same visible parameter values (timestamp,
 nonce, oauth_token and consumer key) and my composite signing it's not
 hte same...

 On Jul 21, 10:03 pm, clinisbut clinis...@gmail.com wrote:
 I'm using an OAuth library I've developed in PHP.

 Do I need to pass all the parameters through the query also?

 On Jul 21, 9:25 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:

  Hi there,

  If you've gotten to the point of retrieving an access token, it's
  likely you managed to get the composite signing key right (or your
  library handled it for you) -- as when you're exchanging the request
  token for an access token, you use the oauth_token_secret from the
  request token as part of the signing key. Are you using an OAuth
  library?

  When you're making a resource request such as one to
  verify_credentials, you'll use the oauth_token_secret you received in
  the access token step as part of the signing key: $consumer_secret +
   + $oauth_token_secret

  Taylor

  On Wed, Jul 21, 2010 at 12:13 PM, clinisbut clinis...@gmail.com wrote:
   Hello everybody.

   I just achieved to autenticate via OAuth, and I'm trying to get user's
   data through account/verify_credentials but I think I'm not building
   correctly the composite signing key or something, mainly because I'm
   not able to fully understand all the different tokens I receive from
   Twitter.

   After I got my access token, I got:

   An oauth_token in the form of: /¿User-ID?/-/letters+numbers/
   An oauth_token_secret

   Which one I should use to built the composite key? 
   Inhttp://dev.twitter.com/pages/auth
   they use the first oauth_token getted in the request token, and in the
   Resource request example they use the oauth_token_secret.

   These is the headers I sent:

   OAuth oauth_consumer_key=XX,
   oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279738886,
   oauth_nonce=a97ff8b71a313a03a650068e1e6b9bd8f31ad04f,
   oauth_version=1.0, oauth_token=-
   X, oauth_signature=0OFTpLp8o
   %2BL9%2B6o8mkRdBSS8I84%3D

   and then I do a GET request 
   to:http://api.twitter.com/1/account/verify_credentials.json

   But all I got is:
   401 Unauthorized
   Failed to validate oauth signature and token

[twitter-dev] Re: Search within followers / following

2010-07-21 Thread Sam

does anyone know of a way to search just among the people you are
following?

[twitter-dev] Re: Problems with Twitter4J and OAuth on Android

Dooh. I thought I changed that.

Thanks. Luckily its a test pair.

Clay

On Jul 21, 12:13 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 Hi Clay,

 Just noticed that you have an API secret in this code sample you've
 provided -- you'll want to go to your application record and
 regenerate a new key/secret pair.

 As for the code itself -- I see you setting your consumer key and
 secret as constants near the top, but then in askOAuth you're using
 different values -- is this just a result of a bad paste?

 Taylor

 On Tue, Jul 20, 2010 at 11:18 PM, Clay Graham claytan...@sightlyinc.com 
 wrote:
  Cant figure out if this is a problem with Twitter4J or the Twitter
  API. I am trying to create an OAuth callback activity, started by a
  RequestToken, but the Request Token request is failing. DOES ANYONE
  KNOW IF GOOGLE HAS MADE THE TWITTER CLIENT AVAILABLE BY OPEN SOURCE
  YET?

  Twitter4J 2.1.2
  Android Froyo 2.2

  package com.sightlyinc.oauth.android;

  import java.util.Date;

  import twitter4j.Twitter;
  import twitter4j.TwitterFactory;
  import twitter4j.http.AccessToken;
  import twitter4j.http.RequestToken;
  import android.app.Activity;
  import android.content.Intent;
  import android.content.SharedPreferences;
  import android.content.SharedPreferences.Editor;
  import android.net.Uri;
  import android.os.Bundle;
  import android.preference.PreferenceManager;
  import android.util.Log;
  import android.view.View;
  import android.view.View.OnClickListener;
  import android.widget.Button;
  import android.widget.EditText;
  import android.widget.Toast;

  public class SightlyOauthActivity extends Activity {

     private static final String TAG =
  SightlyOauthActivity.class.getName();

     private Twitter twitter;
     private RequestToken requestToken;
     private SharedPreferences mSharedPreferences;

     private String CONSUMER_KEY =           yfKRsmTgi8UT8eHoV5Khrw;
     private String CALLBACK_URL =           sightlyoauth://oauth;

     private EditText tweetTextView;
     private Button buttonLogin;

         /** Called when the activity is first created. */
        �...@override
         public void onCreate(Bundle savedInstanceState) {
                 super.onCreate(savedInstanceState);
                 setContentView(R.layout.main);

                 mSharedPreferences =
                         PreferenceManager.getDefaultSharedPreferences(
                                         getApplicationContext());

                 tweetTextView =
  (EditText)findViewById(R.id.TweetView);
         buttonLogin = (Button)findViewById(R.id.ButtonLogon);
         buttonLogin.setOnClickListener(new OnClickListener() {
                 public void onClick(View v) {
                         askOAuth();
                 }
         });

         }

         /**
          * Open the browser and asks the user to authorize the app.
  Afterwards, we
          * redirect the user back here!
          */
         private void askOAuth() {
                 try {

                         //setup properties, https was attempted and I
  was advised to
                         //use HTTPS instead.

  System.setProperty(twitter4j.http.useSSL,false);

  System.setProperty(twitter4j.oauth.consumerKey,MYKEY);

  System.setProperty(twitter4j.oauth.consumerSecret,MYSECRET);

  System.setProperty(twitter4j.oauth.requestTokenURL,http://
  api.twitter.com/oauth/request_token);

  System.setProperty(twitter4j.oauth.accessTokenURL,http://
  api.twitter.com/oauth/access_token);

  System.setProperty(twitter4j.oauth.authorizationURL,http://
  api.twitter.com/oauth/authorize);

                         //get the instance
                         Twitter twitter =
                                 new TwitterFactory().getInstance();

                         //THIS EXCEPTS WITH PERMISSION DENIED
                         requestToken =
  twitter.getOAuthRequestToken(CALLBACK_URL);

                         //set the request token info
                         Toast.makeText(this, Please authorize this
  app!,
                                         Toast.LENGTH_LONG).show();

                         this.startActivity(new
  Intent(Intent.ACTION_VIEW, Uri
                                         
  .parse(requestToken.getAuthenticationURL(;

                 } catch (Exception e) {
                         Log.e(TAG, e.getMessage(),e);
                         Toast.makeText(this, e.getMessage(),
  Toast.LENGTH_LONG).show();
                 }
         }

         /**
          * As soon as the user successfully authorized the app, we are
  notified
          * here. Now we need to get the verifier from the callback
  URL,
  retrieve
          * token and token_secret and feed them to twitter4j (as well
  as
  consumer
          * key and secret).
          */
        �...@override
         protected void onNewIntent(Intent intent) {

                 super.onNewIntent(intent);

                 Uri uri =

[twitter-dev] Re: Problems with Twitter4J and OAuth on Android

Taylor,

So the permission failure is on the request token. Not on the
callback, so even though my callback code is a little different it
shouldnt matter because it never gets to it.

Thanks again for catching that I posted my keys.

Clay


On Jul 21, 12:13 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
 Hi Clay,

 Just noticed that you have an API secret in this code sample you've
 provided -- you'll want to go to your application record and
 regenerate a new key/secret pair.

 As for the code itself -- I see you setting your consumer key and
 secret as constants near the top, but then in askOAuth you're using
 different values -- is this just a result of a bad paste?

 Taylor

 On Tue, Jul 20, 2010 at 11:18 PM, Clay Graham claytan...@sightlyinc.com 
 wrote:
  Cant figure out if this is a problem with Twitter4J or the Twitter
  API. I am trying to create an OAuth callback activity, started by a
  RequestToken, but the Request Token request is failing. DOES ANYONE
  KNOW IF GOOGLE HAS MADE THE TWITTER CLIENT AVAILABLE BY OPEN SOURCE
  YET?

  Twitter4J 2.1.2
  Android Froyo 2.2

  package com.sightlyinc.oauth.android;

  import java.util.Date;

  import twitter4j.Twitter;
  import twitter4j.TwitterFactory;
  import twitter4j.http.AccessToken;
  import twitter4j.http.RequestToken;
  import android.app.Activity;
  import android.content.Intent;
  import android.content.SharedPreferences;
  import android.content.SharedPreferences.Editor;
  import android.net.Uri;
  import android.os.Bundle;
  import android.preference.PreferenceManager;
  import android.util.Log;
  import android.view.View;
  import android.view.View.OnClickListener;
  import android.widget.Button;
  import android.widget.EditText;
  import android.widget.Toast;

  public class SightlyOauthActivity extends Activity {

     private static final String TAG =
  SightlyOauthActivity.class.getName();

     private Twitter twitter;
     private RequestToken requestToken;
     private SharedPreferences mSharedPreferences;

     private String CONSUMER_KEY =           yfKRsmTgi8UT8eHoV5Khrw;
     private String CALLBACK_URL =           sightlyoauth://oauth;

     private EditText tweetTextView;
     private Button buttonLogin;

         /** Called when the activity is first created. */
        �...@override
         public void onCreate(Bundle savedInstanceState) {
                 super.onCreate(savedInstanceState);
                 setContentView(R.layout.main);

                 mSharedPreferences =
                         PreferenceManager.getDefaultSharedPreferences(
                                         getApplicationContext());

                 tweetTextView =
  (EditText)findViewById(R.id.TweetView);
         buttonLogin = (Button)findViewById(R.id.ButtonLogon);
         buttonLogin.setOnClickListener(new OnClickListener() {
                 public void onClick(View v) {
                         askOAuth();
                 }
         });

         }

         /**
          * Open the browser and asks the user to authorize the app.
  Afterwards, we
          * redirect the user back here!
          */
         private void askOAuth() {
                 try {

                         //setup properties, https was attempted and I
  was advised to
                         //use HTTPS instead.

  System.setProperty(twitter4j.http.useSSL,false);

  System.setProperty(twitter4j.oauth.consumerKey,MYKEY);

  System.setProperty(twitter4j.oauth.consumerSecret,MYSECRET);

  System.setProperty(twitter4j.oauth.requestTokenURL,http://
  api.twitter.com/oauth/request_token);

  System.setProperty(twitter4j.oauth.accessTokenURL,http://
  api.twitter.com/oauth/access_token);

  System.setProperty(twitter4j.oauth.authorizationURL,http://
  api.twitter.com/oauth/authorize);

                         //get the instance
                         Twitter twitter =
                                 new TwitterFactory().getInstance();

                         //THIS EXCEPTS WITH PERMISSION DENIED
                         requestToken =
  twitter.getOAuthRequestToken(CALLBACK_URL);

                         //set the request token info
                         Toast.makeText(this, Please authorize this
  app!,
                                         Toast.LENGTH_LONG).show();

                         this.startActivity(new
  Intent(Intent.ACTION_VIEW, Uri
                                         
  .parse(requestToken.getAuthenticationURL(;

                 } catch (Exception e) {
                         Log.e(TAG, e.getMessage(),e);
                         Toast.makeText(this, e.getMessage(),
  Toast.LENGTH_LONG).show();
                 }
         }

         /**
          * As soon as the user successfully authorized the app, we are
  notified
          * here. Now we need to get the verifier from the callback
  URL,
  retrieve
          * token and token_secret and feed them to twitter4j (as well
  as
  consumer
          * key and

[twitter-dev] Re: Problems with Twitter4J and OAuth on Android