Re: [twitter-dev] Re: Provide a spam score (or rathe r a “good citizen” flag)
I don't know about a "karma" score, but Twitalyzer does have an API and so does Klout. For that matter, Viralheat has an API and they can get both Twitalyzer and Klout scores. That said, I don't know that there's ever really going to be a "one size fits all" Twitter user metric. But there are quite a few "crowdsourcing" and "curation" tools starting to show up, some of them open source. But personally, I think it's more fun to just collect raw data via the API and roll your own. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb "A mathematician is a device for turning coffee into theorems." - Paul Erdos Quoting Justin : Rating/scoring users is something I'm working on as well and I agree. I've found sorting out bots and pure spammers to be very difficult. Some folks tweet so much they resemble bots/spam. Feels like a pipe dream but if they can I'd love a karma scoring system directly from the API. On Oct 16, 4:28 am, Dave-twiends wrote: I really like the option of reporting spam via the api. I’ve been blocking spam on my site for a long time but this gives me an option to report it now, and hopefully get these account suspended quicker so that they don’t come back. It would be really great if we could have a proactive api function as well, where we could get the likelihood of a user being a spammer. I know this is really difficult to do, and wrought with pitfalls, but perhaps it could be structured in some way? Maybe you could provide a “good citizen” flag for a user (i.e a user that hasn’t had any complaints, and has a certain account age). That way you don’t negatively impact any users, but we can then at least treat these users differently when they sign up with our site. I’m seeing more and more the need to provide different limits to users based on private trust/karma score we develop for each user. This would be a very valuable input for us to detect potential problem users before they can cause damage. Thanks Dave -- 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: Provide a spam score (or rather a “good citizen” flag)
Rating/scoring users is something I'm working on as well and I agree. I've found sorting out bots and pure spammers to be very difficult. Some folks tweet so much they resemble bots/spam. Feels like a pipe dream but if they can I'd love a karma scoring system directly from the API. On Oct 16, 4:28 am, Dave-twiends wrote: > I really like the option of reporting spam via the api. I’ve been > blocking spam on my site for a long time but this gives me an option > to report it now, and hopefully get these account suspended quicker so > that they don’t come back. > > It would be really great if we could have a proactive api function as > well, where we could get the likelihood of a user being a spammer. I > know this is really difficult to do, and wrought with pitfalls, but > perhaps it could be structured in some way? Maybe you could provide a > “good citizen” flag for a user (i.e a user that hasn’t had any > complaints, and has a certain account age). That way you don’t > negatively impact any users, but we can then at least treat these > users differently when they sign up with our site. > > I’m seeing more and more the need to provide different limits to users > based on private trust/karma score we develop for each user. This > would be a very valuable input for us to detect potential problem > users before they can cause damage. > > Thanks > Dave -- 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] t.co question
What are the plans to implement the automatically t.co url shortening feature via tweets that are sent in via the API? I am getting ready to add this ability to my application, but if Twitter is going to make it an automatic feature then I can save myself the trouble if they will have it implemented soon. I looked at the announcements and did not see any recent updates on this feature. Looking forward to your comments. Dave -- 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: https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 not working
Hey guys,
Thank you so much for your prompt response!
The URL that I provided came from Twitter+OAUTH sdk that I'm using on
my iPhone App. I was assuming that this library was going to create
the correct URL for me... but it seems that it is generating something
else or could it be that that my library is not updated?
Do you recommend that I modify the Twitter+OAUTH to use an
https://api.twitter.com/1/statuses/user_timeline.json?
I only had this problem with some user timelines, for other timelines
I didnt have this problem. Even when using an URL of type:
https://twitter.com/statuses/user_timeline/justinbieber.json?count=20
The URL that I provided is coming from the following function in
SA_OAuthTwitterEngine.m
- (NSString *)_sendRequestWithMethod:(NSString *)method
path:(NSString *)path
queryParameters:(NSDictionary *)params
body:(NSString *)body
requestType:
(MGTwitterRequestType)requestType
responseType:
(MGTwitterResponseType)responseType
{
NSString *fullPath = path;
NSLog(@"SA_OAuthTwitterEngine - fullPath - pre:%@", fullPath);
//
// modification from the base clase
// the base class appends parameters here
//
if(requestType == MGTwitterUserTimelineRequest || requestType ==
MGTwitterUserTimelineForUserRequest || requestType ==
MGTwitterSearchRequest || requestType ==
MGTwitterSearchCurrentTrendsRequest) //added by Carlos to get correct
count of status
{
if (params) {
fullPath = [self _queryStringWithBase:fullPath
parameters:params prefixed:YES];
}
}
//
//copied from MGTwitterEngine.m:465
#if YAJL_AVAILABLE
NSString *domain = nil;
NSString *connectionType = nil;
if (requestType == MGTwitterSearchRequest || requestType ==
MGTwitterSearchCurrentTrendsRequest)
{
domain = _searchDomain;
connectionType = @"http";
}
else
{
domain = _APIDomain;
if (_secureConnection)
{
connectionType = @"https";
}
else
{
connectionType = @"http";
}
}
#else
NSString *domain = _APIDomain;
NSString *connectionType = nil;
if (_secureConnection)
{
connectionType = @"https";
}
else
{
connectionType = @"http";
}
#endif
NSLog(@"SA_OAuthTwitterEngine - fullPath - post:%@", fullPath);
//cchacon: original
//NSString *urlString = [NSString stringWithFormat:@"%@://%@/%@",
// (_secureConnection) ? @"https" : @"http",
// _APIDomain, fullPath];
//cchacon: copied from MGTwitterEngine.m:499
NSString *urlString = [NSString stringWithFormat:@"%@://%@/%@",
connectionType,
domain, fullPath];
NSURL *finalURL = [NSURL URLWithString:urlString];
NSLog(@"SA_OAuthTwitterEngine - finalURL:%@", [finalURL
absoluteString]);
if (!finalURL) {
return nil;
}
//
// modificaiton from the base clase
// the base class creates a regular url request
// we're going to create an oauth url request
//
//NSMutableURLRequest *theRequest = [NSMutableURLRequest
requestWithURL:finalURL
//
cachePolicy:NSURLRequestReloadIgnoringCacheData
//
timeoutInterval:URL_REQUEST_TIMEOUT];
//
OAMutableURLRequest *theRequest = [[[OAMutableURLRequest alloc]
initWithURL:finalURL
consumer:self.consumer
token:_accessToken
realm: nil
signatureProvider:nil] autorelease];
if (method) {
[theRequest setHT
Re: [twitter-dev] https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 not working
In addition make sure you add the parameter include_rts=1 to the request. The include_rts flag instructs the API to include retweets in the response. Looking at the timeline you requested it looks as if the last 20 Tweets by that user are retweets - which, by default, are not included in the timeline but are included in the count. Best, Matt On Oct 16, 2010, at 12:24, Taylor Singletary wrote: > It should be pointed out that those aren't valid API URLs.. > > You want to execute these requests against API.twitter.com/1/resource... > > The best way to construct your URL would be like this: (it reduces ambiguity) > > https://api.twitter.com/1/statuses/user_timeline.json?screen_name=justinbieber&count=20 > > Finally, we are having some strange issues with certain timelines. If you're > running into this, it means the timeline is being a bit erratic. Try > requesting a higher count, like 100. We are looking into this behavior and > hope to fix it soon. > > Taylor > > On Sat, Oct 16, 2010 at 2:35 AM, CarlosChacon wrote: > I'm trying to access justinbieber timeline but its returning "[]"... > I'm using this URL: > https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 > > If I try the timeline for other users it works fine. for example: > https://twitter.com/statuses/user_timeline/cnn.json?count=20 > > Any idea why this is happening? > > If I go to http://twitter.com/justinbieber it seems to be okay, but > when using > https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 > it keeps returning an empty array... > > -- > 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] Follow-back should always be private
I’m looking to implement this feature on my site as I can really see the value in it. But as you have pointed out I can also see the danger in it. If spammers knew who had follow-back turned on they would seek out these users and follow them, knowing they would get followed back. They could then potentially do this at a very accelerated rate, not hitting follow limits. I think the only way this feature can be kept safe is if it is completely private. Users can turn it on but neither they nor the application should tell other others that its enabled. There should be no way for spammers to figure this out either. I’m not sure if this has been spelled out in the twitter rules but if it hasn’t it probably should. Users mustn’t be allowed to put it in their bio, etc. as this could be easily be parsed by a crawler.. Would be interested to hear how others are keeping this feature “safe”..? Thanks Dave -- 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] https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 not working
It should be pointed out that those aren't valid API URLs.. You want to execute these requests against API.twitter.com/1/resource... The best way to construct your URL would be like this: (it reduces ambiguity) https://api.twitter.com/1/statuses/user_timeline.json?screen_name=justinbieber&count=20 Finally, we are having some strange issues with certain timelines. If you're running into this, it means the timeline is being a bit erratic. Try requesting a higher count, like 100. We are looking into this behavior and hope to fix it soon. Taylor On Sat, Oct 16, 2010 at 2:35 AM, CarlosChacon wrote: > I'm trying to access justinbieber timeline but its returning "[]"... > I'm using this URL: > https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 > > If I try the timeline for other users it works fine. for example: > https://twitter.com/statuses/user_timeline/cnn.json?count=20 > > Any idea why this is happening? > > If I go to http://twitter.com/justinbieber it seems to be okay, but > when using > https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 > it keeps returning an empty array... > > -- > 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] https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 not working
I'm trying to access justinbieber timeline but its returning "[]"... I'm using this URL: https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 If I try the timeline for other users it works fine. for example: https://twitter.com/statuses/user_timeline/cnn.json?count=20 Any idea why this is happening? If I go to http://twitter.com/justinbieber it seems to be okay, but when using https://twitter.com/statuses/user_timeline/justinbieber.json?count=20 it keeps returning an empty array... -- 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] Provide a spam score (or rather a “g ood citizen” flag)
I really like the option of reporting spam via the api. I’ve been blocking spam on my site for a long time but this gives me an option to report it now, and hopefully get these account suspended quicker so that they don’t come back. It would be really great if we could have a proactive api function as well, where we could get the likelihood of a user being a spammer. I know this is really difficult to do, and wrought with pitfalls, but perhaps it could be structured in some way? Maybe you could provide a “good citizen” flag for a user (i.e a user that hasn’t had any complaints, and has a certain account age). That way you don’t negatively impact any users, but we can then at least treat these users differently when they sign up with our site. I’m seeing more and more the need to provide different limits to users based on private trust/karma score we develop for each user. This would be a very valuable input for us to detect potential problem users before they can cause damage. Thanks Dave -- 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] User name and password
When creating a free website what is the user name and password you need to use when it asks for it in the twitter widget? -- 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: Extreme caching of deleted tweets in 'statuses/home_timeline'
My game application also deletes tweets within 1-2 minutes of creation, and all still appear in the timeline after a refresh. The only exception is that if I create then immediately delete the tweet, it does not appear. On Oct 13, 3:38 am, CWorster wrote: > Thanks a lot for your replies.and confirmation! -- 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] Incorrect signature while getting home tweets
The syntax of that header is wrong.
Please look at http://dev.twitter.com/pages/auth for the correct syntax.
Tom
On 10/16/10 9:23 AM, Georgooty varghese wrote:
>
> * Now I set to Http header value
> Header name = "Authorization"
> value =
> http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=*&oauth_nonce=QyRr
>
> PmridwwSG6oEsr4EI&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1287212752&oauth_token=***&oauth_version=1.0&oauth_signature=WMYyqUYpD4lIfe8f3v3u1o2r2uk%3D
>
> Now i got {"error":"Could not authenticate
> you.","request":"/1/statuses/home_timeline.json"} exception message.
>
> What can I do for resolve this exception.
>
>
> On Thu, Oct 14, 2010 at 7:30 PM, Taylor Singletary
> mailto:taylorsinglet...@twitter.com>> wrote:
>
> Without getting to deep into this, some advice:
>
> * Use HTTP header based authentication instead of attaching OAuth
> parameters to the query string. It makes it much more difficult to
> receive assistance from others when you use query-string based auth
> and increases the chances of an encoding error exponentially.
>
> * Avoid strange characters in an oauth_nonce. When possible, avoid
> the "~" character entirely -- depending on the language and
> libraries you are using, some are less spec compliant than others on
> characters like tilde
>
> * That you were able to negotiate oauth_tokens through xAuth is a
> good sign that your code does something right. POSTs are harder than
> GETs. There must be something simple wrong with your GET. Look very
> closely. Compare to the spec if necessary. Compare to other code
> that produces the correct results.
>
> Taylor
>
> On Thu, Oct 14, 2010 at 4:06 AM, Georgooty varghese
> mailto:georgo...@gmail.com>> wrote:
>
> Before I have implemented a twitter client in C# using xAuth
> authentication . At that application I have used xauth params
> for each url signin. Any problem I didn't get. That aclient
> application works fine.
>
> Now I have changed language C# to C. I have used liboauth
> library. I got oauth_token and oauth_token_secret values
> successfully. Then I have try to get home tweets. But i got
> incorrect signature.
>
> Base URL
> --
>
> GET&http%3A%2F%2Fapi.twitter.com
>
> %2F1%2Fstatuses%2Fhome_timeline.json&oauth_consumer_key%3DOm
>
>
> TQVOKDomNbrHuuudS4Q%26oauth_nonce%3DuQTDMWP-6tFdwTAbDwiHeyrP7NEZ%26oauth_signature_method%3DHMAC-SH
>
>
> A1%26oauth_timestamp%3D1287053858%26oauth_token%3D144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7%26oauth_version%3D1.0
>
> Signature
> -
> FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324RE&dirvhD970MRu
>oQxPM2uOfzocpkRT3m0LKn0HPDcKkM
>
> URL
> --
>
> http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Q&o
>
>
>
>
> auth_nonce=uQTDMWP-6tFdwTAbDwiHeyrP7NEZ&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1287053858
>
>
> &oauth_token=144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7&oauth_version=1.0&oauth_signature=wgRPZqaIJU%2BrkHOSAN99JreWLr4%3D
>
> Error response look like below.
> ---
>
> Header received header name:Date Value:Thu, 14 Oct 2010
> 10:57:39 GMT
> NN 2010-10-14 16:27:39.700 Header received header
> name:Server Value:hi
> NN 2010-10-14 16:27:39.700 Header received header
> name:Status Value:401 Unauthorized
> NN 2010-10-14 16:27:39.700 Header received header
> name:WWW-Authenticate Value:Basic realm="Twitter API"
> NN 2010-10-14 16:27:39.700 Header received header
> name:Content-Type Value:application/json; charset=utf-8
> NN 2010-10-14 16:27:39.700 Header received header
> name:Content-Length Value:350
> NN 2010-10-14 16:27:39.700 Header received header
> name:Cache-Control Value:no-cache, max-age=300
> NN 2010-10-14 16:27:39.700 Header received header
> name:Set-Cookie Value:k=121.241.181.70.1287053859204701; path=/;
>expires=Thu, 21-Oct-10 10:57:39
> GMT; domain=.twitter.com
> NN 2010-10-14 16:27:39.700 Header received header
> name:Set-Cookie Value:guest_id=128705385920759845; path=/;
> expires=Sat, 13
>
[twitter-dev] Re: Search with geocode does not respect search radius?
Update: the ticket is closed and @TweepsAround seems to be working fine again. Details: http://code.google.com/p/twitter-api/issues/detail?id=1930 Quote: Comment 3 by project member tokofu, Today (13 hours ago) We've deployed some changes which should have fixed this issue so i'm closing the ticket. Many thanks! On Oct 11, 9:38 pm, themattharris wrote: > Thanks for filing the ticket on this, we'll post there when a fix is > deployed. Progress wise I checked in with the team today and they > continue to work on a fix. > > To keep things connected there is another thread that was discussing > the issue with geocoded search here: > http://groups.google.com/group/twitter-development-talk/browse_thread... > > More information will be filed on the ticket here: > http://code.google.com/p/twitter-api/issues/detail?id=1930 > > Thanks for bearing with us whilst we work out what went wrong with the > location index and how to resolve it. > > Best, > @themattharris > > On Oct 10, 9:29 pm, Nick wrote: > > > We are having issues with this as well and it has completely broken > > our system. > > > We have sent many support tickets but have received no response to > > them. > > > It looks to be breaking plain searches to not just those requested via > > the API. > > > Some examples of broken searches are: > > >http://search.twitter.com/search?q=bigpond+near%3Aaustralia > > >http://search.twitter.com/search.json?q=bigpond&geocode=-27.766513,13... > > > These were working before this issue. > > > Best Regards > > Nick Fritzkowski > > > On Oct 6, 2:42 am, Matt Harris wrote: > > > > This is a know issue which the team is working on at the moment. I'll > > > post an update when a fix is deployed. > > > > --- > > > @themattharris > > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > On Mon, Oct 4, 2010 at 8:36 PM, _ado wrote: > > > > For what it's worth, I'm seeing the same issue. Radius parameter is > > > > completely ignored. Data returned for, for example, a 1 mile radius > > > > will return results spanning 60 miles. > > > > > -- > > > > 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] Incorrect signature while getting home tweets
* Now I set to Http header value
Header name = "Authorization"
value =
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=
*&oauth_nonce=QyRr
PmridwwSG6oEsr4EI&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1287212752&oauth_token=***&oauth_version=1.0&oauth_signature=WMYyqUYpD4lIfe8f3v3u1o2r2uk%3D
Now i got {"error":"Could not authenticate
you.","request":"/1/statuses/home_timeline.json"} exception message.
What can I do for resolve this exception.
On Thu, Oct 14, 2010 at 7:30 PM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:
> Without getting to deep into this, some advice:
>
> * Use HTTP header based authentication instead of attaching OAuth
> parameters to the query string. It makes it much more difficult to receive
> assistance from others when you use query-string based auth and increases
> the chances of an encoding error exponentially.
>
> * Avoid strange characters in an oauth_nonce. When possible, avoid the "~"
> character entirely -- depending on the language and libraries you are using,
> some are less spec compliant than others on characters like tilde
>
> * That you were able to negotiate oauth_tokens through xAuth is a good sign
> that your code does something right. POSTs are harder than GETs. There must
> be something simple wrong with your GET. Look very closely. Compare to the
> spec if necessary. Compare to other code that produces the correct results.
>
> Taylor
>
> On Thu, Oct 14, 2010 at 4:06 AM, Georgooty varghese
> wrote:
>
>> Before I have implemented a twitter client in C# using xAuth
>> authentication . At that application I have used xauth params for each url
>> signin. Any problem I didn't get. That aclient application works fine.
>>
>> Now I have changed language C# to C. I have used liboauth library. I got
>> oauth_token and oauth_token_secret values successfully. Then I have try to
>> get home tweets. But i got incorrect signature.
>>
>> Base URL
>> --
>>
>> GET&http%3A%2F%2Fapi.twitter.com
>> %2F1%2Fstatuses%2Fhome_timeline.json&oauth_consumer_key%3DOm
>>
>> TQVOKDomNbrHuuudS4Q%26oauth_nonce%3DuQTDMWP-6tFdwTAbDwiHeyrP7NEZ%26oauth_signature_method%3DHMAC-SH
>>
>> A1%26oauth_timestamp%3D1287053858%26oauth_token%3D144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7%26oauth_version%3D1.0
>>
>> Signature
>> -
>> FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324RE&dirvhD970MRu
>>oQxPM2uOfzocpkRT3m0LKn0HPDcKkM
>>
>> URL
>> --
>>
>> http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Q&o
>>
>> auth_nonce=uQTDMWP-6tFdwTAbDwiHeyrP7NEZ&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1287053858
>>
>> &oauth_token=144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7&oauth_version=1.0&oauth_signature=wgRPZqaIJU%2BrkHOSAN99JreWLr4%3D
>>
>> Error response look like below.
>> ---
>>
>> Header received header name:Date Value:Thu, 14 Oct 2010 10:57:39 GMT
>>> NN 2010-10-14 16:27:39.700 Header received header name:Server Value:hi
>>> NN 2010-10-14 16:27:39.700 Header received header name:Status Value:401
>>> Unauthorized
>>> NN 2010-10-14 16:27:39.700 Header received header name:WWW-Authenticate
>>> Value:Basic realm="Twitter API"
>>> NN 2010-10-14 16:27:39.700 Header received header name:Content-Type
>>> Value:application/json; charset=utf-8
>>> NN 2010-10-14 16:27:39.700 Header received header name:Content-Length
>>> Value:350
>>> NN 2010-10-14 16:27:39.700 Header received header name:Cache-Control
>>> Value:no-cache, max-age=300
>>> NN 2010-10-14 16:27:39.700 Header received header name:Set-Cookie
>>> Value:k=121.241.181.70.1287053859204701; path=/;
>>>expires=Thu, 21-Oct-10 10:57:39 GMT; domain=.
>>> twitter.com
>>> NN 2010-10-14 16:27:39.700 Header received header name:Set-Cookie
>>> Value:guest_id=128705385920759845; path=/; expires=Sat, 13
>>>Nov 2010 10:57:39 GMT
>>> NN 2010-10-14 16:27:39.700 Header received header name:Set-Cookie
>>>
>>> Value:_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCI9ZY6orAToHaWQiJWNhNWJkMWFkNWNkZDQ0%250ANzkzZTUxZTdmMD
>>>
>>> AxY2YwMDNhIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--39a08a
>>>fc637e1b3666e4066c100f477a9bfbd5b4; domain=.
>>> twitter.com; path=/
>>> NN 2010-10-14 16:27:39.700 Header received header name:Expires Value:Thu,
>>> 14 Oct 2010 11:02:39 GMT
>>> NN 2010-10-14 16:27:39.700 Header received header name:Vary
>>> Value:Accept-Encoding
>>> NN 2010-10-14 16:27:39.700 Header received header name:Connection
>>> Value:close
>>> NN 2010-10-14 16:27:39.700 Data:{"error":"Incorrect
>>>
>>> signature","request":"/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Q&oauth
>>>
>>> _nonce=uQTDMWP-6tFdwTAbDwiHeyrP7NEZ&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1287053858&oau
>>>
>>> th_token=144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7&
Re: [twitter-dev] Incorrect signature while getting home tweets
Any body please help me?
On Fri, Oct 15, 2010 at 11:00 AM, Georgooty varghese wrote:
> * Now I have removed oauth parameters in query string and added it to HTTP
> header.
> * Removed ~ char from auth nonce (reserved chars)
>
>
> Now i got another exception "Could not authenticate you"
>
>
>
> Could u please help me..
>
>
>
> On Thu, Oct 14, 2010 at 7:30 PM, Taylor Singletary <
> taylorsinglet...@twitter.com> wrote:
>
>> Without getting to deep into this, some advice:
>>
>> * Use HTTP header based authentication instead of attaching OAuth
>> parameters to the query string. It makes it much more difficult to receive
>> assistance from others when you use query-string based auth and increases
>> the chances of an encoding error exponentially.
>>
>> * Avoid strange characters in an oauth_nonce. When possible, avoid the "~"
>> character entirely -- depending on the language and libraries you are using,
>> some are less spec compliant than others on characters like tilde
>>
>> * That you were able to negotiate oauth_tokens through xAuth is a good
>> sign that your code does something right. POSTs are harder than GETs. There
>> must be something simple wrong with your GET. Look very closely. Compare to
>> the spec if necessary. Compare to other code that produces the correct
>> results.
>>
>> Taylor
>>
>> On Thu, Oct 14, 2010 at 4:06 AM, Georgooty varghese
>> wrote:
>>
>>> Before I have implemented a twitter client in C# using xAuth
>>> authentication . At that application I have used xauth params for each url
>>> signin. Any problem I didn't get. That aclient application works fine.
>>>
>>> Now I have changed language C# to C. I have used liboauth library. I got
>>> oauth_token and oauth_token_secret values successfully. Then I have try to
>>> get home tweets. But i got incorrect signature.
>>>
>>> Base URL
>>> --
>>>
>>> GET&http%3A%2F%2Fapi.twitter.com
>>> %2F1%2Fstatuses%2Fhome_timeline.json&oauth_consumer_key%3DOm
>>>
>>> TQVOKDomNbrHuuudS4Q%26oauth_nonce%3DuQTDMWP-6tFdwTAbDwiHeyrP7NEZ%26oauth_signature_method%3DHMAC-SH
>>>
>>> A1%26oauth_timestamp%3D1287053858%26oauth_token%3D144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7%26oauth_version%3D1.0
>>>
>>> Signature
>>> -
>>> FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324RE&dirvhD970MRu
>>>oQxPM2uOfzocpkRT3m0LKn0HPDcKkM
>>>
>>> URL
>>> --
>>>
>>> http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Q&o
>>>
>>> auth_nonce=uQTDMWP-6tFdwTAbDwiHeyrP7NEZ&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1287053858
>>>
>>> &oauth_token=144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7&oauth_version=1.0&oauth_signature=wgRPZqaIJU%2BrkHOSAN99JreWLr4%3D
>>>
>>> Error response look like below.
>>> ---
>>>
>>> Header received header name:Date Value:Thu, 14 Oct 2010 10:57:39 GMT
NN 2010-10-14 16:27:39.700 Header received header name:Server Value:hi
NN 2010-10-14 16:27:39.700 Header received header name:Status Value:401
Unauthorized
NN 2010-10-14 16:27:39.700 Header received header name:WWW-Authenticate
Value:Basic realm="Twitter API"
NN 2010-10-14 16:27:39.700 Header received header name:Content-Type
Value:application/json; charset=utf-8
NN 2010-10-14 16:27:39.700 Header received header name:Content-Length
Value:350
NN 2010-10-14 16:27:39.700 Header received header name:Cache-Control
Value:no-cache, max-age=300
NN 2010-10-14 16:27:39.700 Header received header name:Set-Cookie
Value:k=121.241.181.70.1287053859204701; path=/;
expires=Thu, 21-Oct-10 10:57:39 GMT; domain=.
twitter.com
NN 2010-10-14 16:27:39.700 Header received header name:Set-Cookie
Value:guest_id=128705385920759845; path=/; expires=Sat, 13
Nov 2010 10:57:39 GMT
NN 2010-10-14 16:27:39.700 Header received header name:Set-Cookie
Value:_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCI9ZY6orAToHaWQiJWNhNWJkMWFkNWNkZDQ0%250ANzkzZTUxZTdmMD
AxY2YwMDNhIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--39a08a
fc637e1b3666e4066c100f477a9bfbd5b4; domain=.
twitter.com; path=/
NN 2010-10-14 16:27:39.700 Header received header name:Expires
Value:Thu, 14 Oct 2010 11:02:39 GMT
NN 2010-10-14 16:27:39.700 Header received header name:Vary
Value:Accept-Encoding
NN 2010-10-14 16:27:39.700 Header received header name:Connection
Value:close
NN 2010-10-14 16:27:39.700 Data:{"error":"Incorrect
signature","request":"/1/statuses/home_timeline.json?oauth_consumer_key=OmTQVOKDomNbrHuuudS4Q&oauth
_nonce=uQTDMWP-6tFdwTAbDwiHeyrP7NEZ&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1287053858&oau
th_token=144717423-P3to4wvZPFsgrIQWBAZPjlEAm39tfEtaao7HQWA7&oauth_version=1.0&oauth_signature=wgRPZ
