Re: [twitter-dev] New Twitter API?
It surprises me that Twitter didn't simply push all developers to the top of that queue. Anyway, could someone push me to the top as well? (@tvdw) To answer the question of this thread: I *think* you will have to contact Twitter for that. Not the people here on the API list, but via http://twitter.com/about/contact Tom On 9/15/10 6:30 AM, Zac Bowling wrote: > I'm not sure about the question, but it has me thinking. > I know it's kind of a failed tech these days but wouldn't it be funny if > twitter could host an OpenSocial like container thing in the right pain based > on the a tweet link? It could open that right area to all sorts of dynamic > content. > > Either way, there is so much rick-rolling to be had now on twitter with the > video embedding. > > Zac Bowling > @zbowling > > > PS: Can someone at twitter bump my main @zbowling account up in the rollout > queue? > > > On Sep 14, 2010, at 8:57 PM, PeekURL.com wrote: > >> I run a URL shortener that plays Youtube videos. When someone clicks a >> link like http://peekURL.com/va1gk1h how do I play that video in the >> right pane on the New Twitter? Can I show ads there? >> >> The videos will all be coming from Youtube or Myspace, but if Twitter >> isn't going to allow third-party access to the right pane - after some >> form of vetting of course - then they'd seem to be unjustly helping >> Youtube. >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] New Twitter API?
I'm not sure about the question, but it has me thinking. I know it's kind of a failed tech these days but wouldn't it be funny if twitter could host an OpenSocial like container thing in the right pain based on the a tweet link? It could open that right area to all sorts of dynamic content. Either way, there is so much rick-rolling to be had now on twitter with the video embedding. Zac Bowling @zbowling PS: Can someone at twitter bump my main @zbowling account up in the rollout queue? On Sep 14, 2010, at 8:57 PM, PeekURL.com wrote: > I run a URL shortener that plays Youtube videos. When someone clicks a > link like http://peekURL.com/va1gk1h how do I play that video in the > right pane on the New Twitter? Can I show ads there? > > The videos will all be coming from Youtube or Myspace, but if Twitter > isn't going to allow third-party access to the right pane - after some > form of vetting of course - then they'd seem to be unjustly helping > Youtube. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: list api create_all method not working
Hi,
Can anyone suggest me that how i can integrate my Blackberry application
with twitter.
I am using Twitter me 1.4 api for this.
--
*Thanks & Regards*
*Zahid Naqvi | Senior Software Engineer*
--
*
G1-11, I.T.Park, M.I.A. (Extn.) Udaipur - 313003 Rajasthan India
(M) *+91-9799966000* | (R) *+91-141-2608333*
*zahidalina...@gmail.com | za...@arcgate.com
On Tue, Sep 14, 2010 at 10:41 PM, Ken wrote:
> Finally, after discovering this thread, I added /members/ to the
> create_all endpoint and was able to add 98 members to a list. As
> twitter would say, 'Yay'...
>
> I filed a bug to have the documentation corrected.
>
> Are there still problems adding lots of members, as reported earlier
> in this thread? Since rate-limiting as listed as false in the doc,
> would it be more reliable to just loop over :user/:list_id/members 100
> times? I need to go for "reliable" wherever possible... That way we
> could add up to the 500 members maximum. Recommended or not really?
>
> Thanks
> -Ken
>
>
> On Aug 23, 9:07 pm, Jim Chevalier wrote:
> > Hello,
> >
> > Ah-ha! I did not have /members/ in my POST URL. Thanks for pointing
> > that out!
> > This actually make it seem likehttp://
> dev.twitter.com/doc/post/:user/:list_id/create_all
> > should be changed to state:
> > POSThttp://
> api.twitter.com/version/:user/:list_id/members/create_all.format
> >
> > I also didn't realize I could/should check on $connection->http_code
> > so often. Thanks for pointing that out as well.
> > It's funny, now that you mention it, I notice the test.php file you
> > included in twitteroauth has that call *everywhere*.
> >
> > It seems like I should rewrite my calls to be more like the
> > "twitteroauth_row" function you define in the test.php file so that I
> > can use the $connection->http_code results as error-checking.
> > I'll also have to test if setting "public $retry = TRUE;" in the
> > twitteroauth.php file helps with the 502 response that comes when
> > attempting to push 99 users through the create_all call...
> >
> > Thanks for all the help!
> > -Jim
> >
> > On Aug 23, 2:44 pm, Abraham Williams <4bra...@gmail.com> wrote:
> >
> > > After each TwitterOAuth call you should check $connection->http_code to
> > > check what the result is. 200 on success, 404 on not found, etc.
> >
> > > My quick findings:
> > > Works: $connection->post('abraham/test3/members/create_all',
> array('user_id'
> > > => $user_ids));
> > > AKA: $connection->post('{$screen_name/{$list}/members/create_all',
> > > array('user_id' => $user_ids));
> >
> > > But with the 99 user_ids it would usually return a 502 after adding ~60
> > > users to the list:http://goo.gl/Zur3
> >
> > > Abraham
> > > -
> > > Abraham Williams | Hacker Advocate |http://abrah.am
> > > @abraham |http://projects.abrah.am|http://blog.abrah.am
> > > This email is: [ ] shareable [x] ask first [ ] private.
> >
> > > On Mon, Aug 23, 2010 at 10:54, Jim Chevalier
> wrote:
> > > > hrm, back to square one then...
> >
> > > > Abraham - the value of $users is:
> >
> > > >
> 2142731,14125623,15998931,19560364,16559320,17036420,14791918,16908659,5538992,14984281,20188175,14277276,111226850,14327961,20257060,94168006,107679193,54567920,18171797,8886022,16390772,69422500,171538302,818340,168929218,141333525,132534968,14124542,14408989,138293290,2039761,6752072,111896485,175801197,14912789,22907920,15099178,16583906,10870772,94269486,174521748,82002786,15395087,39407092,123734452,17193910,16362662,7762662,21514744,7596972,31563269,23147529,27440127,14337563,1528701,82497472,19251912,15292430,17005679,7192042,14600753,97484744,2023641,92086501,15447441,98735657,16950385,2023191,14411651,23111875,2900,15039436,14479810,16024218,57933102,8453452,18363508,16569530,21034443,17007607,7029452,54997124,47397228,15226527,18193201,22278762,15127641,14204449,60616288,16465359,10371312,15805506,14995035,27727035,19211127,35279958,18023868,9369722,8088412
> >
> > > > That's 99 users, in what I believe to be the correct format.
> >
> > > > I also ran a test with just 8088412 like this, with the same (blank)
> > > > result:
> > > > $users = 8088412;
> > > > $added = $connection->post("{$user->screen_name}/lists/$listid->id/
> > > > create_all", array('user_id' => $users));
> > > > print_r($added);
> >
> > > > Since it seems like the 'create_all' call itself that's the problem,
> I
> > > > decided to run another test:
> > > > $blahblah = $connection->post("{$user->screen_name}/{$list->id}/
> > > > qhweoi", array('user_id' => $users));
> > > > print_r($blahblah);
> >
> > > > This returned nothing, similar to my 'create_all' call. Since
> > > > 'qhweoi' is not a valid Twitter API call, I'm wondering if either
> > > > twitteroauth just doesn't do the "create_all" call for lists or if my
> > > > implementation of it is broken...
> >
> > > > Thanks everyone!
> > > > -Jim
> >
> > > > On Aug 23, 12:56 pm, Taylor Singletary >
> > > > wrote:
> >
[twitter-dev] New Twitter API?
I run a URL shortener that plays Youtube videos. When someone clicks a link like http://peekURL.com/va1gk1h how do I play that video in the right pane on the New Twitter? Can I show ads there? The videos will all be coming from Youtube or Myspace, but if Twitter isn't going to allow third-party access to the right pane - after some form of vetting of course - then they'd seem to be unjustly helping Youtube. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Too often 401 error
I have the same problem in Android platform. I implemented Key and Secrit into new OAuthSignpostClient.but OAuthSignpostClient not work. How can I client twitter with new API? any example demo for me ? 2010/9/15 MH > I implemented oAuth API and it workes. > But sometimes I get 401 Error. When I get this error, I retry with the > same application and it workes. > > Same Server, Same logic, usually workes well but sometimes I get > error. > What's the problem? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Too often 401 error
I implemented oAuth API and it workes. But sometimes I get 401 Error. When I get this error, I retry with the same application and it workes. Same Server, Same logic, usually workes well but sometimes I get error. What's the problem? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: iPhone::Incorrect oauth_signature for xAuth?
Can somebody recalculate test example from http://dev.twitter.com/pages/xauth
???
I'm looking for oauth_signature parameter
I'm getting different result and it does not make any sense so far
On Sep 13, 2:54 pm, Nikolay Klimchuk wrote:
> Thanks Tom
>
> I feel better now LoL
>
> On Sep 13, 2:41 pm, Tom van der Woerdt wrote:
>
>
>
> > 2010-09-13 20:39:11.190 Test[56513:207] NSData *HMAC: <3146268a 86d17682
> > bab34655 aa8e3140 d34ed7bc>
> > 2010-09-13 20:39:11.191 Test[56513:207] NSString *HMAC64:
> > MUYmiobRdoK6s0ZVqo4xQNNO17w=
>
> > Looks like you're right :-)
>
> > @episod: You should fix that! :-)
>
> > Tom
>
> > On 9/13/10 8:23 PM, Nikolay Klimchuk wrote:
>
> > > Still no luck
>
> > > With your code I'm gettings exactly the same result
> > > MUYmiobRdoK6s0ZVqo4xQNNO17w=
>
> > > Something really strange in example herehttp://dev.twitter.com/pages/xauth
>
> > > Nikolay Klimchuk
>
> > > On Sep 13, 7:19 am, Tom van der Woerdt wrote:
> > >> Oh, hehe, good point. That's because my Base String has one extra
> > >> urlencoded '&' on the end, and that shouldn't be there.
>
> > >> Tom
>
> > >> On Mon, 13 Sep 2010 04:18:06 -0700 (PDT), Nikolay Klimchuk
>
> > >> wrote:
> > >>> Thank you Tom
>
> > >>> I will try your algorithm and compare results.
> > >>> Quick question: why you do this [str substringToIndex:[str
> > >>> length]-3] ?
>
> > >>> Nikolay Klimchuk
>
> > >>> On Sep 13, 2:46 am, Tom van der Woerdt wrote:
> > Hi Nikolay,
>
> > The first part of your code looks fine. You may, however, like to do
> > some debugging on the HMAC part - it looks a bit too simple to me.
>
> > This works :
> > NSString *compKey = [NSString
> > stringWithFormat:@"%@&%@",secret,userSecret];
> > const char *cKey = [compKey
> > cStringUsingEncoding:NSUTF8StringEncoding];
> > const char *cData = [[str substringToIndex:[str length]-3]
> > cStringUsingEncoding:NSUTF8StringEncoding];
> > unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
> > CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData,
> > strlen(cData), cHMAC);
> > NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC
> > length:sizeof(cHMAC)];
> > (str being the Base String)
>
> > Hope it helps :-)
>
> > Tom
>
> > On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
>
> > > I'm trying to understand why algorithm for calculation of
> > > oauth_signature does not give me the same result as shown here:
> > >http://dev.twitter.com/pages/xauth
>
> > > In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
>
> > > If I URL encode such result it's still very different from
> > > yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
>
> > > I've tried different implementations, all of them give the same
> > > result. After few hours of exercises with all this stuff I completely
> > > run out of ideas, please help
>
> > > // Test with input data taken from Twitter page
>
> > > NSString *s= @"POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > > %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> > > %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> > > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> > > %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> > > %26x_auth_password%3D%2525%2526123%2521aZ%252B
> > > %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant";
>
> > > NSString *k = @"5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&";
>
> > > NSString *signedSK = [NetworkManager base64forData:[NetworkManager
> > > HMACSHA1withKey:k forString:s]];
>
> > > // Source code
>
> > > + (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
> > > *)string
> > > {
> > > NSData *clearTextData = [string
> > > dataUsingEncoding:NSUTF8StringEncoding];
> > > NSData *keyData = [key dataUsingEncoding:NSUTF8StringEncoding];
>
> > > uint8_t digest[CC_SHA1_DIGEST_LENGTH] = {0};
>
> > > CCHmacContext hmacContext;
> > > CCHmacInit(&hmacContext, kCCHmacAlgSHA1, keyData.bytes,
> > > keyData.length);
> > > CCHmacUpdate(&hmacContext, clearTextData.bytes,
> > > clearTextData.length);
> > > CCHmacFinal(&hmacContext, digest);
>
> > > return [NSData dataWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
> > > }
>
> > > //Sourcehttp://www.cocoadev.com/index.pl?BaseSixtyFour
>
> > > + (NSString *)base64forData:(NSData *)data
> > > {
> > > static const char encodingTable[] =
> > > "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
>
> > > if ([data length] == 0)
> > > return @"";
>
> > > char *characters = malloc((([data length] + 2) / 3) * 4);
> > > if (characters == NULL)
> > > return nil;
> > > NSUInteger length = 0;
>
> > > NSUInteger i = 0;
> > > while (i < [data length])
>
[twitter-dev] Re: list members cursor is wrong
Thanks, Matt,
This is the full request
http://api.twitter.com/1/endlesscities/urban/members.json?oauth_nonce=84284551&oauth_timestamp=1284515127&oauth_consumer_key=MgdaAGLAt4VQzGKvoczhA&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_token=18904533-Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx&oauth_signature=05FtplBSA2OosDkvt5nDBKfmjxI%3D
doing a urllib.urlopen( ) on that.
This is the Python request object {'http_url': 'http://api.twitter.com/
1/endlesscities/urban/members.json?cursor=1343981850785981701',
'http_method': 'GET', 'parameters': {'oauth_nonce': '68156293',
'oauth_timestamp': 1284515562, 'oauth_consumer_key':
'MgdaAGLAt4VQzGKvoczhA', 'oauth_signature_method': 'HMAC-SHA1',
'oauth_version': '1.0', 'oauth_token': '18904533-
Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx', 'oauth_signature':
'QkEP3+sCmz0C/djHJcdgUyTDbuI='}}
I get results back, so the auth is working, but the cursor stays the
same.
thanks for whatever insight you can give.
On Sep 14, 10:37 am, Matt Harris wrote:
> GET works fine for this method and when I test the cursors for your
> list below everything works correctly. So we can work out what is
> going on can you share the headers you are sending to the API.
>
> Also, you will want to update your URLs to the correct host. The
> correct URL to use ishttp://api.twitter.com/1/-- making your
> request:
> http://api.twitter.com/1/endlesscities/urban/members.json?cursor=-1
>
> Best,
> Matt
>
>
>
> On Sun, Sep 12, 2010 at 6:44 PM, Brad wrote:
> > maybe I'm doing something wrong, but the cursor returned from the list
> > members call seems to be misbehaving.
>
> > if I hit:
> >http://twitter.com/endlesscities/urban/members.json?cursor=-1
>
> > it returns
> > "next_cursor":1343981850785981701, "previous_cursor":0
>
> > if I pass it that new cursor:
> >http://twitter.com/endlesscities/urban/members.json?cursor=1343981850...
>
> > it returns the same thing:
> > "next_cursor":1343981850785981701, "previous_cursor":0
>
> > What's up with that? This has cropped up thanks to switching from
> > basic Auth to Oauth. I'm doing a GET because it won't allow me to do a
> > POST.
>
> > thanks in advance for any help.
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this
> > group:http://groups.google.com/group/twitter-development-talk?hl=en
>
> --
>
> Matt Harris
> Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Video of tonight's event?
I had to chuckle when Ellen Degeneres asked what the difference was between wearing an outfit made of meat and one made of leather. My response was that the poor couldn't eat leather. ;-) -- 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 Dana Contreras : I can't say it didn't cross my mind. ;) On Tue, Sep 14, 2010 at 4:04 PM, M. Edward (Ed) Borasky < zn...@borasky-research.net> wrote: As long as nobody is wearing a meat dress, I'll tune in. ;-) -- 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 Taylor Singletary : While Twitter is not providing a feed, @scobleizer is: http://www.ustream.tv/channel/scobleizer Taylor On Tue, Sep 14, 2010 at 3:04 PM, @twepe wrote: Any idea if anyone is streaming video of tonight's event? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Dana Contreras Twitter Platform Team http://twitter.com/DanaDanger -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Mentions and direct_messages cannot be acquired.
I have been trying to convert to OAuth using a sample code called Twitter-OAuth-iPhone without much success. I am able to obtain [user-timeline]/[friends] using NSXMLParser but I am NOT able to show [mentions]/[direct_messages] or any direct tweet to my account for that matter. Can someone tell me what I am doing wrong? Any assistant would be appreciated. Thank you in Advance. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Authentication failing for status POST in C#
Woops, sorry and the response that I get back is:
{"request":"/1/statuses/update.json","error":"Incorrect signature"}
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Authentication failing for status POST in C#
The base string is:
POST&http%3a%2f%2fapi.twitter.com%2f1%2fstatuses
%2fupdate.json&oauth_consumer_key%3dA5l9hSVM5Hznf5p1pBwNsg
%26oauth_nonce%3dJOCvtqemMQg1k0XnFjbH0MQPxr6Yme7zcei6mZO6ZP
%26oauth_signature_method%3dHMAC-SHA1%26oauth_timestamp
%3d1284512080%26oauth_token%3d189085164-
UGuVwmGtljgvSUg8q0aCOD4vrPibePTE7zVBlOMG%26oauth_version%3d1.0%26status
%3doogyboogy
The sent request is:
POST /1/statuses/update.json HTTP/1.1\r\n
Authorization: OAuth
oauth_nonce="JOCvtqemMQg1k0XnFjbH0MQPxr6Yme7zcei6mZO6ZP",oauth_signature_method="HMAC-
SHA1",oauth_timestamp="1284512080",oauth_consumer_key="A5l9hSVM5Hznf5p1pBwNsg",oauth_token="189085164-
UGuVwmGtljgvSUg8q0aCOD4vrPibePTE7zVBlOMG",oauth_signature="62%2BaTNj5jKWl7ajQrzM
%2FNQXV7Rw%3D",oauth_version="1.0"\r\n
Content-Type: application/x-www-form-urlencoded\r\n
Host: api.twitter.com\r\n
Content-Length: 16\r\n
\r\n
status=oogyboogy
On Sep 10, 12:00 pm, Tom van der Woerdt wrote:
> I like code, but I like seeing the results even more :-)
>
> Can you provide us (the twitter-dev list) with these :
> * A base string
> * A full request and response
>
> Tom
>
> On 9/10/10 8:22 PM, hyronymous wrote:
>
>
>
> > So far as I can tell, I'm following the instructions accurately
> > according tohttp://dev.twitter.com/pages/auth, but regardless of any
> > minute variations, I keep getting a 401, authorization error on
> > posting (i.e. the method pushMessage() fails). So far as I can tell,
> > I'm not doing anything different, other than using POST, than I did
> > during the initial authorization.
>
> > public class Twitter {
> > private string tokenSecret = "";
>
> > private string createTimestamp() {
> > var now = DateTime.UtcNow;
> > var then = new DateTime(1970, 1, 1);
> > var timespan = now - then;
> > return ("" + (long)timespan.TotalSeconds);
> > }
>
> > private string createNonce() {
> > const string ALPHANUMERIC =
> > "qwertyuiopasdfghjklzxcvbnm"
> > + "QWERTYUIOPASDFGHJKLZXCVBNM"
> > + "1234567890"
> > ;
>
> > var sb = new StringBuilder();
> > var random = new Random();
> > for (int L = 0; L < 42; L++)
> > {
> > sb.Append(
> > ALPHANUMERIC[random.Next(ALPHANUMERIC.Length)]
> > );
> > }
> > return sb.ToString();
> > }
>
> > private string createSignature(string signatureBase) {
> > string key = clientSecret + "&" + tokenSecret;
> > var keyBytes = Encoding.UTF8.GetBytes(key);
> > var sigMethod = new HMACSHA1(keyBytes);
>
> > byte[] data = Encoding.UTF8.GetBytes(signatureBase);
> > var hash = sigMethod.ComputeHash(data);
> > var sig = Convert.ToBase64String(hash);
>
> > sig = Uri.EscapeDataString(sig);
> > return sig;
> > }
>
> > private void myInit() {
> > int found = 0;
> > string[] words = sessionData.Split('&');
> > for (uint L = 0; L < words.Length; L++)
> > {
> > if (words[L].StartsWith("oauth_token="))
> > {
> > ++found;
> > accessToken = words[L];
> > }
> > else if (words[L].StartsWith("oauth_token_secret="))
> > {
> > ++found;
> > tokenSecret =
> > words[L].Substring("oauth_token_secret=".Length);
> > }
> > else if (words[L].StartsWith("user_id=")) {
> > ++found;
> > userID = words[L].Substring("user_id=".Length);
> > }
> > else if (words[L].StartsWith("screen_name=")) {
> > ++found;
> > screenName =
> > words[L].Substring("screen_name=".Length);
> > }
> > }
> > if (found != 4) {
> > throw new Exception("Unknown response from server");
> > }
> > }
>
> > public new void createSession(System.Web.UI.Page page)
> > {
> > if (
> >
> > !string.IsNullOrEmpty(page.Request.QueryString["oauth_token"])
> > ) {
> > string timestamp = createTimestamp();
> > string nonce = createNonce();
>
> > var sigBase =
> > "GET"
> > + "&" +
> > Uri.EscapeDataString("https://api.twitter.com/oauth/
> > access_token")
> > + "&" +
> > Uri.EscapeDataString("oauth_consumer_key=" + clientID)
> > + "%26" + Uri.EscapeDataString("oauth_nonce=" +
> > nonce)
> > + "%26" +
> > Uri.EscapeDataString("o
Re: [twitter-dev] Video of tonight's event?
I can't say it didn't cross my mind. ;) On Tue, Sep 14, 2010 at 4:04 PM, M. Edward (Ed) Borasky < zn...@borasky-research.net> wrote: > As long as nobody is wearing a meat dress, I'll tune in. ;-) > > -- > 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 Taylor Singletary : > > While Twitter is not providing a feed, @scobleizer is: >> http://www.ustream.tv/channel/scobleizer >> >> Taylor >> >> On Tue, Sep 14, 2010 at 3:04 PM, @twepe wrote: >> >> >>> Any idea if anyone is streaming video of tonight's event? >>> >>> -- >>> Twitter developer documentation and resources: >>> http://dev.twitter.com/doc >>> API updates via Twitter: http://twitter.com/twitterapi >>> Issues/Enhancements Tracker: >>> http://code.google.com/p/twitter-api/issues/list >>> Change your membership to this group: >>> http://groups.google.com/group/twitter-development-talk?hl=en >>> >>> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk?hl=en >> >> > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Dana Contreras Twitter Platform Team http://twitter.com/DanaDanger -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Video of tonight's event?
As long as nobody is wearing a meat dress, I'll tune in. ;-) -- 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 Taylor Singletary : While Twitter is not providing a feed, @scobleizer is: http://www.ustream.tv/channel/scobleizer Taylor On Tue, Sep 14, 2010 at 3:04 PM, @twepe wrote: Any idea if anyone is streaming video of tonight's event? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: POSTing problem
I am away from my work computer so i cant try out this suggestion just yet but is this what it should look like when i do? basestring: POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26 oauth_signature_method%3DHMAC-SHA1%26 oauth_timestamp%3D1284487942%26 oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 oauth_version%3D1.0%26 status%3Dsetting%2520up%2520my%2520twitter POST: POST /1/statuses/update.xml? HTTP/1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942", oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0" Content-Length: 40 status=setting%20up%20my%20twitter On Sep 14, 2:18 pm, Taylor Singletary wrote: > MTCoder: > > You've got a little bit of an escaping problem here.. > > First, "spaces" aren't valid characters for your POST body. Personally, I > recommend using %20 to represent a space. "+" would also be valid in a POST > body. > > Once your POST body is correct, the escaping for your OAuth signature base > string is then considered. > > If you used %20 to encode spaces in your POST body, then in your signature > base string, %2520 should be used where a %20 was before. If you used "+" in > your POST body, %2B should be used instead of "+" in your OAuth signature > base string. > > The OAuth signature base string's validity depends on the initial, valid > encoding of your POST body. > > Taylor > > > > On Tue, Sep 14, 2010 at 1:11 PM, MTCoder wrote: > > all the keys are the same that use when making calls to get the > > timeline. > > > Steve > > > On Sep 14, 1:08 pm, Tom van der Woerdt wrote: > > > Your Base String looks fine. Are you using the right keys to sign the > > > request? Is there any response from the API, except for 401? (Error > > > message?) > > > > Tom > > > > On 9/14/10 8:14 PM, MTCoder wrote: > > > > > still getting the 401 > > > > > basestring: > > > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > > > > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > > > > oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26 > > > > oauth_signature_method%3DHMAC-SHA1%26 > > > > oauth_timestamp%3D1284487942%26 > > > > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > > > > oauth_version%3D1.0%26 > > > > status%3Dsetting%2520up%2520my%2520twitter > > > > > POST: > > > > POST /1/statuses/update.xml? HTTP/1.1 > > > > Content-Type: application/x-www-form-urlencoded > > > > Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D", > > > > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942", > > > > oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > > > > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > > > > oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0" > > > > Content-Length: 40 > > > > > status=setting%2520up%2520my%2520twitter > > > > > On Sep 14, 11:39 am, Tom van der Woerdt wrote: > > > >> It says "setting up my twitter" in the Base String, not > > "status=setting > > > >> up my twitter". > > > > >> Tom > > > > >> On 9/14/10 7:30 PM, MTCoder wrote: > > > > >>> Im posting this again here to make sure its seen (other thread here > > >http://groups.google.com/group/twitter-development-talk/browse_thread...) > > > > >>> I have tried many different things and cant seem to get the status > > > >>> POST to work(thanks Tom for the help with getting the timeline). > > > > >>> my base string: > > > > >>> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > > > >>> oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > > > >>> oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26 > > > >>> oauth_signature_method%3DHMAC-SHA1%26 > > > >>> oauth_timestamp%3D1284483693%26 > > > >>> oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > > > >>> oauth_version%3D1.0%26setting%2520up%2520my%2520twitter > > > > >>> And the POST: > > > > >>> POST /1/statuses/update.xml? HTTP/1.1 > > > >>> Content-Type: application/x-www-form-urlencoded > > > >>> Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934", > > > >>> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693", > > > >>> oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > > > >>> oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > > > >>> oauth_signature="vZt0cwQJV%2FeZUPSRPAjfpEBhONM%3D", > > > >>> oauth_version="1.0" > > > >>> Content-Length: 40 > > > > >>> status=setting%2520up%2520my%2520twitter > > > > >>> Any help/ideas would be greatly appreciated. > > > > >>> Thanks > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitte
Re: [twitter-dev] Video of tonight's event?
While Twitter is not providing a feed, @scobleizer is: http://www.ustream.tv/channel/scobleizer Taylor On Tue, Sep 14, 2010 at 3:04 PM, @twepe wrote: > > Any idea if anyone is streaming video of tonight's event? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Video of tonight's event?
Any idea if anyone is streaming video of tonight's event? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Why is Basic Auth still enabled on some sources?
I appreciate the response, Ryan. I'll say that it's a bummer to find out about this in that way. Twitter made a big deal about how Basic Auth was being shut off, so finding out that there were exceptions like this is confusing and disconcerting. No matter the intent, it is hard to feel respected when you discover this kind of thing. In the end, whether that matters is up to Twitter (as an entity, not the individuals who work there, to whom I'm sure it does matter). -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Sep 14, 12:09 pm, Ryan Sarver wrote: > Ed, > > As part of the migration we worked with many developers to help them with > the transition and some of them, including our own Android app, had some > extenuating circumstances that made them unable to make the date. For those > few exceptions and extreme cases we granted them a stay of execution as long > as they provided a reasonable timeline to make the transition. > > It pained us to do it for one of our own applications, but I'll give you > some detail to help you understand why we needed to. And to be clear, we did > this for a number of non-Twitter applications as well if we deemed their > situation to be one that needed the stay as well. In the end all of the apps > that got the stay were mobile apps that were unable to flash new versions > out to devices on their own schedule and that includes the Android app on a > number of devices. > > We have a hard shut-off date from Google which is only a few weeks away and > from every other app that was given an exemption. Rest assured that EVERY > app will be moved over in a timely fashion, so using their keys will only > give you a short window to continue to use Basic Auth. > > When looking at all the possible options and scenarios, we think this was > the right decision in order to move the entire ecosystem over to the new > authentication model while also being reasonable when we needed to be. > > Best, Ryan > > > > On Mon, Sep 13, 2010 at 1:40 PM, funkatron wrote: > > Read on this post:http://blog.nelhage.com/2010/09/dear-twitter/ > > > Tested just now:http://gist.github.com/577273 > > > If I pass "source=twitterandroid", it appears to work on all API > > methods. > > > In light of basic auth being "disabled," why does this work? > > > -- > > Ed Finkler > >http://funkatron.com > > @funkatron > > AIM: funka7ron / ICQ: 3922133 / > > XMPP:funkat...@gmail.com > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Why is Basic Auth still enabled on some sources?
I would love to see Twitter implement essentially the http://SuperTweet.net approach, where I can set a separate password for use with Basic Auth credentials that do not use my real Twitter password and I can revoke or change that password independently of my real Twitter password. This would shut down the http://SuperTweet.net site/service which would be fine by me (as the one who funds that service out of my own pocket). :) On Sep 13, 10:33 am, Jeff Gladnick wrote: > There was a very easy solution, IMHO, to the basic auth issue that I > am surprised twitter didn't consider. > > 1) Add a new field to user profile settings that is "Allow basic > authentication for API." Set this to be false by default for all > users. You can even set a scary message here discouraging its use. > 2) If you try to post to this account with basic auth, it just wont > work, and will return a "basic auth is disabled" error. > 3) Even basic users would be capable to switching this to true so > their app would work. > > Its not too late twitter. > > On Sep 13, 10:07 am, isaiah wrote: > > > > > The bonus is that it's a way to still use plain old curl for testing. > > Awesome! > > > On Sep 13, 9:21 am, Dewald Pretorius wrote: > > > > They must have known that this was going to be discovered. We're > > > developers. We like building, testing, and breaking stuff. > > > > Unequal applications of the rules. Happens all the time. Months after > > > you've disabled something at the request of Twitter, you find well- > > > known services that do exactly the same thing with apparent impunity > > > in a much worse form than you did. > > > > On Sep 13, 10:40 am, funkatron wrote: > > > > > Read on this post:http://blog.nelhage.com/2010/09/dear-twitter/ > > > > > Tested just now:http://gist.github.com/577273 > > > > > If I pass "source=twitterandroid", it appears to work on all API > > > > methods. > > > > > In light of basic auth being "disabled," why does this work? > > > > > -- > > > > Ed Finklerhttp://funkatron.com > > > > @funkatron > > > > AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Missing entities in REST
The same thing happens to me when I use the favorites resources. It doesn't matter which user's favorites I am trying to get, entities are never there. Last time I saw entities for favorites was 11th September. Thanks Georgios Favorious - http://favorious.com - The best of Twitter, based on favorites On Sep 14, 6:33 pm, Jesse wrote: > i have > 17312534 (bangmarketing) > and > 13024412 (thewitness) > > thanks > > On Sep 14, 11:34 am, FearMediocrity wrote: > > > > > I've tried it on two accounts, from 2 oAuth REST API apps. > > > User id: > > > 11747852 (FearMediocrity) > > 18804420 (ThinkingInCode) > > > James > > > On Sep 14, 3:06 pm, Taylor Singletary > > wrote: > > > > Hi Everyone, > > > > We're still investigating this issue -- it is not happening > > > consistently across the board and has been difficult to track down. > > > > If you're *never* getting entities when requesting timelines, and you're > > > including include_entities=true then please leave your member id here for > > > additional investigation. > > > > Hope to have this fixed soon. > > > > Thanks, > > > Taylor > > > > On Tue, Sep 14, 2010 at 6:20 AM, FearMediocrity > > > wrote: > > > > I don't think your doing anything wrong. include_entities hasn't > > > > worked for me since late last week. @twitterapi mentioned a problem, > > > > but then nothing since. > > > > > Can we have an update please? > > > > > On Sep 13, 7:16 pm, Jesse wrote: > > > > > Hi, I'm trying to view my last tweet, but I can't seem to be able to > > > > > see the Tweet Entities. > > > > > > Here is what I'm trying to view: > > > >http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=(reda... > > > > > > But I don't see the "entities" element. > > > > > > Any help would be appreciated > > > > > Thanks > > > > > -- > > > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > > > API updates via Twitter:http://twitter.com/twitterapi > > > > Issues/Enhancements Tracker: > > > >http://code.google.com/p/twitter-api/issues/list > > > > Change your membership to this group: > > > >http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: 01:Authentication credentials were missing or incorrect. / ColdFusion + Twitter4J
Sounds like the oauth_callback parameter for /oauth/request_token is
wrong. ;-)
Tom
On 9/14/10 10:47 PM, Andy Reid wrote:
> Oddly enough. No. I just dumped the response toString():
>
> OAuthToken{token='z', tokenSecret='y',
> secretKeySpec=null}
>
> This is odd because it actually comes back to the correct page.
>
> However, when I manually set the default callback url (in
> dev.twitter.com) the oAuth worked completely fine and I was able to
> send updates, etc. The destination domain for the desired callback is
> in the list, and, like I said, it even came back to the correct page.
>
> Any idea what that could be?!
>
> Thanks,
> Andy
>
> On Sep 10, 3:11 pm, Tom van der Woerdt wrote:
>> Do you get a confirmation on the callback after request_token?
>>
>> Tom
>>
>> On 9/10/10 9:55 PM, Andy Reid wrote:
>>
>>
>>
>>> Hi --
>>
>>> I'm trying to get my oAuth working with twitter4j and ColdFusion.
>>
>>> Here's the code I use:
>>
>>>
>>>
>>>
>>> >> Twitter.setOAuthConsumer(TwitterConsumerKey,TwitterConsumerSecret)>
>>>
>>>
>>>>> myURL.com")>
>>>
>>>>> RequestToken.getTokenSecret()>
>>>>> addtoken="No">
>>>
>>>
>>>>> Twitter.getOAuthAccessToken(Session.oAuthRequestToken,Session.oAuthRequestT
>>> okenSecret)>
>>>
>>>
>>> >> Twitter.setOAuthAccessToken(Session.StoredAccessToken,Session.StoredAccessS
>>> ecret)>
>>>
>>>
>>>
>>>
>>
>>> It loads fine, and brings me to the Twitter authentication screen. I
>>> click "Agree" and am redirected back to my page.
>>
>>> When I return I am met with this error:
>>> 401:Authentication credentials were missing or incorrect. >> version="1.0" encoding="UTF-8"?> /oauth/access_token>> request> Invalid oauth_verifier parameter>
>>> Any ideas?
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: 01:Authentication credentials were missing or incorrect. / ColdFusion + Twitter4J
Oddly enough. No. I just dumped the response toString():
OAuthToken{token='z', tokenSecret='y',
secretKeySpec=null}
This is odd because it actually comes back to the correct page.
However, when I manually set the default callback url (in
dev.twitter.com) the oAuth worked completely fine and I was able to
send updates, etc. The destination domain for the desired callback is
in the list, and, like I said, it even came back to the correct page.
Any idea what that could be?!
Thanks,
Andy
On Sep 10, 3:11 pm, Tom van der Woerdt wrote:
> Do you get a confirmation on the callback after request_token?
>
> Tom
>
> On 9/10/10 9:55 PM, Andy Reid wrote:
>
>
>
> > Hi --
>
> > I'm trying to get my oAuth working with twitter4j and ColdFusion.
>
> > Here's the code I use:
>
> >
> >
> >
> > > Twitter.setOAuthConsumer(TwitterConsumerKey,TwitterConsumerSecret)>
> >
> >
> > > myURL.com")>
> >
> > > RequestToken.getTokenSecret()>
> > > addtoken="No">
> >
> >
> > > Twitter.getOAuthAccessToken(Session.oAuthRequestToken,Session.oAuthRequestT
> > okenSecret)>
> >
> >
> > > Twitter.setOAuthAccessToken(Session.StoredAccessToken,Session.StoredAccessS
> > ecret)>
> >
> >
> >
> >
>
> > It loads fine, and brings me to the Twitter authentication screen. I
> > click "Agree" and am redirected back to my page.
>
> > When I return I am met with this error:
> > 401:Authentication credentials were missing or incorrect. > version="1.0" encoding="UTF-8"?> /oauth/access_token > request> Invalid oauth_verifier parameter
> > Any ideas?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] home_timeline count
Hi all, I was wondering if there is an good way of getting a count of statuses in home_timeline. I have to implement a "Load more" feature which loads more tweets if they are available. The issue is with "available" part. The API doesn't reliably return 20 unfortunately so I can;t simply hide the button when I get back a count of less than 20. It also doesn't return a total count so that I can verify I've reached the end that way. Is there any way of doing this? The API keeps me guessing... :) Cheers, Matei -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: POSTing problem
MTCoder: You've got a little bit of an escaping problem here.. First, "spaces" aren't valid characters for your POST body. Personally, I recommend using %20 to represent a space. "+" would also be valid in a POST body. Once your POST body is correct, the escaping for your OAuth signature base string is then considered. If you used %20 to encode spaces in your POST body, then in your signature base string, %2520 should be used where a %20 was before. If you used "+" in your POST body, %2B should be used instead of "+" in your OAuth signature base string. The OAuth signature base string's validity depends on the initial, valid encoding of your POST body. Taylor On Tue, Sep 14, 2010 at 1:11 PM, MTCoder wrote: > all the keys are the same that use when making calls to get the > timeline. > > Steve > > On Sep 14, 1:08 pm, Tom van der Woerdt wrote: > > Your Base String looks fine. Are you using the right keys to sign the > > request? Is there any response from the API, except for 401? (Error > > message?) > > > > Tom > > > > On 9/14/10 8:14 PM, MTCoder wrote: > > > > > > > > > > > > > > > > > still getting the 401 > > > > > basestring: > > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > > > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > > > oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26 > > > oauth_signature_method%3DHMAC-SHA1%26 > > > oauth_timestamp%3D1284487942%26 > > > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > > > oauth_version%3D1.0%26 > > > status%3Dsetting%2520up%2520my%2520twitter > > > > > POST: > > > POST /1/statuses/update.xml? HTTP/1.1 > > > Content-Type: application/x-www-form-urlencoded > > > Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D", > > > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942", > > > oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > > > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > > > oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0" > > > Content-Length: 40 > > > > > status=setting%2520up%2520my%2520twitter > > > > > On Sep 14, 11:39 am, Tom van der Woerdt wrote: > > >> It says "setting up my twitter" in the Base String, not > "status=setting > > >> up my twitter". > > > > >> Tom > > > > >> On 9/14/10 7:30 PM, MTCoder wrote: > > > > >>> Im posting this again here to make sure its seen (other thread here > > >>> > http://groups.google.com/group/twitter-development-talk/browse_thread...) > > > > >>> I have tried many different things and cant seem to get the status > > >>> POST to work(thanks Tom for the help with getting the timeline). > > > > >>> my base string: > > > > >>> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > > >>> oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > > >>> oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26 > > >>> oauth_signature_method%3DHMAC-SHA1%26 > > >>> oauth_timestamp%3D1284483693%26 > > >>> oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > > >>> oauth_version%3D1.0%26setting%2520up%2520my%2520twitter > > > > >>> And the POST: > > > > >>> POST /1/statuses/update.xml? HTTP/1.1 > > >>> Content-Type: application/x-www-form-urlencoded > > >>> Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934", > > >>> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693", > > >>> oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > > >>> oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > > >>> oauth_signature="vZt0cwQJV%2FeZUPSRPAjfpEBhONM%3D", > > >>> oauth_version="1.0" > > >>> Content-Length: 40 > > > > >>> status=setting%2520up%2520my%2520twitter > > > > >>> Any help/ideas would be greatly appreciated. > > > > >>> Thanks > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: POSTing problem
all the keys are the same that use when making calls to get the timeline. Steve On Sep 14, 1:08 pm, Tom van der Woerdt wrote: > Your Base String looks fine. Are you using the right keys to sign the > request? Is there any response from the API, except for 401? (Error > message?) > > Tom > > On 9/14/10 8:14 PM, MTCoder wrote: > > > > > > > > > still getting the 401 > > > basestring: > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > > oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26 > > oauth_signature_method%3DHMAC-SHA1%26 > > oauth_timestamp%3D1284487942%26 > > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > > oauth_version%3D1.0%26 > > status%3Dsetting%2520up%2520my%2520twitter > > > POST: > > POST /1/statuses/update.xml? HTTP/1.1 > > Content-Type: application/x-www-form-urlencoded > > Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D", > > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942", > > oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > > oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0" > > Content-Length: 40 > > > status=setting%2520up%2520my%2520twitter > > > On Sep 14, 11:39 am, Tom van der Woerdt wrote: > >> It says "setting up my twitter" in the Base String, not "status=setting > >> up my twitter". > > >> Tom > > >> On 9/14/10 7:30 PM, MTCoder wrote: > > >>> Im posting this again here to make sure its seen (other thread here > >>>http://groups.google.com/group/twitter-development-talk/browse_thread...) > > >>> I have tried many different things and cant seem to get the status > >>> POST to work(thanks Tom for the help with getting the timeline). > > >>> my base string: > > >>> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > >>> oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > >>> oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26 > >>> oauth_signature_method%3DHMAC-SHA1%26 > >>> oauth_timestamp%3D1284483693%26 > >>> oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > >>> oauth_version%3D1.0%26setting%2520up%2520my%2520twitter > > >>> And the POST: > > >>> POST /1/statuses/update.xml? HTTP/1.1 > >>> Content-Type: application/x-www-form-urlencoded > >>> Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934", > >>> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693", > >>> oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > >>> oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > >>> oauth_signature="vZt0cwQJV%2FeZUPSRPAjfpEBhONM%3D", > >>> oauth_version="1.0" > >>> Content-Length: 40 > > >>> status=setting%2520up%2520my%2520twitter > > >>> Any help/ideas would be greatly appreciated. > > >>> Thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Fwd: REST API Server Headers wrong?
Hi there, Often when throwing error pages, it happens at a level that does not understand basic concepts like the disposition of content you are expecting back. When this happens, a generic error response is thrown, which in this case happens to be our HTML representation. We, obviously, don't like that this is the case. But it is right now. Thanks, Taylor On Tue, Sep 14, 2010 at 12:12 PM, yaemog Dodigo wrote: > > Hello, > (sorry for the resend but i did not see this message appear on the list) > > > It occurs from time to time that the rest api servers don't deliver > responses, and I'm not complaining about that. > > However, why would the server answer with a 500 Http status code, a content > type of application/json and the content being the html error page. > > E.g., > > GET /1/statuses/friends.json?cursor=1346292258256227567&user_id=33307124 > HTTP/1.1 > Accept-Encoding: identity > Host: api.twitter.com > Connection: close > User-Agent: Python-urllib/2.6 > > HTTP/1.1 500 Internal Server Error > Date: Sat, 11 Sep 2010 01:56:02 GMT > Server: hi > Status: 500 Internal Server Error > X-Transaction: 1284170160-87257-46051 > X-RateLimit-Limit: 2 > Last-Modified: Sat, 11 Sep 2010 01:56:00 GMT > X-RateLimit-Remaining: 11250 > Content-Type: application/json; charset=utf-8 > Content-Length: 4659 > Pragma: no-cache > > > > Connection: close > > http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> > http://www.w3.org/1999/xhtml"; lang="en" xml:lang="en"> > > > > Twitter / Error > http://s.twimg.com/images/favicon.ico"; rel="shortcut icon" > type="image/x-icon" /> > > > > thx > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Fwd: REST API Server Headers wrong?
Hello, (sorry for the resend but i did not see this message appear on the list) It occurs from time to time that the rest api servers don't deliver responses, and I'm not complaining about that. However, why would the server answer with a 500 Http status code, a content type of application/json and the content being the html error page. E.g., GET /1/statuses/friends.json?cursor=1346292258256227567&user_id=33307124 HTTP/1.1 Accept-Encoding: identity Host: api.twitter.com Connection: close User-Agent: Python-urllib/2.6 HTTP/1.1 500 Internal Server Error Date: Sat, 11 Sep 2010 01:56:02 GMT Server: hi Status: 500 Internal Server Error X-Transaction: 1284170160-87257-46051 X-RateLimit-Limit: 2 Last-Modified: Sat, 11 Sep 2010 01:56:00 GMT X-RateLimit-Remaining: 11250 Content-Type: application/json; charset=utf-8 Content-Length: 4659 Pragma: no-cache Connection: close http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> http://www.w3.org/1999/xhtml"; lang="en" xml:lang="en"> Twitter / Error http://s.twimg.com/images/favicon.ico"; rel="shortcut icon" type="image/x-icon" /> thx -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: POSTing problem
Your Base String looks fine. Are you using the right keys to sign the request? Is there any response from the API, except for 401? (Error message?) Tom On 9/14/10 8:14 PM, MTCoder wrote: > still getting the 401 > > basestring: > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26 > oauth_signature_method%3DHMAC-SHA1%26 > oauth_timestamp%3D1284487942%26 > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > oauth_version%3D1.0%26 > status%3Dsetting%2520up%2520my%2520twitter > > POST: > POST /1/statuses/update.xml? HTTP/1.1 > Content-Type: application/x-www-form-urlencoded > Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D", > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942", > oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0" > Content-Length: 40 > > status=setting%2520up%2520my%2520twitter > > > > On Sep 14, 11:39 am, Tom van der Woerdt wrote: >> It says "setting up my twitter" in the Base String, not "status=setting >> up my twitter". >> >> Tom >> >> On 9/14/10 7:30 PM, MTCoder wrote: >> >> >> >> >> >> >> >>> Im posting this again here to make sure its seen (other thread here >>> http://groups.google.com/group/twitter-development-talk/browse_thread...) >> >>> I have tried many different things and cant seem to get the status >>> POST to work(thanks Tom for the help with getting the timeline). >> >>> my base string: >> >>> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& >>> oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 >>> oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26 >>> oauth_signature_method%3DHMAC-SHA1%26 >>> oauth_timestamp%3D1284483693%26 >>> oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 >>> oauth_version%3D1.0%26setting%2520up%2520my%2520twitter >> >>> And the POST: >> >>> POST /1/statuses/update.xml? HTTP/1.1 >>> Content-Type: application/x-www-form-urlencoded >>> Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934", >>> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693", >>> oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", >>> oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", >>> oauth_signature="vZt0cwQJV%2FeZUPSRPAjfpEBhONM%3D", >>> oauth_version="1.0" >>> Content-Length: 40 >> >>> status=setting%2520up%2520my%2520twitter >> >>> Any help/ideas would be greatly appreciated. >> >>> Thanks > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Getting the latest status
Thanks Taylor!
{face palm}
Cheers,
Matei
On Sep 14, 10:58 am, Taylor Singletary
wrote:
> Hi Matei,
>
> The simplest way to accomplish this would be a single GET request.
>
> GEThttp://api.twitter.com/1/statuses/user_timeline.xml?screen_name=twitt...
>
> If you weren't interested in processing retweets, you could omit the
> include_rts=true parameter, but I would bump the count to at least 5 since
> disincluded retweets still apply to the count parameter's calculations.
>
> Taylor
>
>
>
> On Tue, Sep 14, 2010 at 9:51 AM, Matei wrote:
> > Hi all,
>
> > I was wondering what the best way to get a user's latest status is.
> > Right now I am using the verify_credentials call to do it, since I
> > don't really know the user Id from the OAuth flow. The trouble with
> > this approach is that the result doesn't always include the status. Is
> > there a better way of doing this, maybe I'm totally missing something
> > obvious.
>
> > BTW, the project I'm on uses heavy JavaScript and a C# backed to proxy
> > Twitter API calls.
>
> > Cheers,
> > Matei
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk?hl=en
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: OAuth Via AppleScript
Yes... I am currently working on testing its functionality and inclusion into the original ASTwitterLibrary suite. I am hoping for a release date in the next month or so... There will actually be two pieces of it. The heavy OAuth lifting will be performed by my main AppleScript library, ASObject. This will allow you to do just about any API call to Twitter that you would like (as long as you know the url and proper arguments). The second piece of it will be a re-release of the ASTwitterLibrary script that requires ASObject. Its primary function will be to give you an easy way to integrate twitter into your scripts without knowing much of anything about the Twitter API. On Tue, Sep 14, 2010 at 12:19 PM, Ankur Oberoi wrote: > have you finished the applescript for oauth? if you are planning on > releasing it, i would be interested to grab a copy. thanks! > > On Aug 11, 3:22 pm, isaiah1112 wrote: > > You were right! I forgot to sort them... Thanks! > > > > On Aug 11, 1:14 pm, Tom van der Woerdt wrote: > > > > > > > > > On 8/11/10 8:38 PM, isaiah1112 wrote: > > > > > > Ok... here is what I cam up with using the keys and secrets you > > > > provided in your previous post > > > > > > Base String is: > > > > > > GET&https%3A%2F%2Fapi.twitter.com%2F1%2Faccount > > > > %2Fverify_credentials.json&oauth_consumer_key%3DGDdmIQH6jhtmLUypg82g > > > > %26oauth_nonce > > > > %3D702fab381be61bb60f210dd07d80be722da33f05%26oauth_signature_method > > > > %3DHMAC-SHA1%26oauth_token%3D819797- > > > > Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_timestamp > > > > %3D1281551596%26oauth_version%3D1.0 > > > > > > consumersecret&usersecret is: > > > > > MCD8BKwGdgPHvAuvgvz4EQpqDAtx89grbuNMRd7Eh98&J6zix3FfA9LofH0awS24M3HcBYXO5nI > 1iYe8EfBA > > > > > > Thus the non-url encoded signature would be: > > > > XUNmLwpiC2W0xyrxPs4yAMmHO9c= > > > > > > And the HTTP header would be (signature is URL encoded): > > > > > > Authorization:OAuthoauth_consumer_key="GDdmIQH6jhtmLUypg82g", > > > > oauth_nonce="702fab381be61bb60f210dd07d80be722da33f05", > > > > oauth_signature_method="HMAC-SHA1", > > > > oauth_signature="XUNmLwpiC2W0xyrxPs4yAMmHO9c%3D", > > > > oauth_token="819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw", > > > > oauth_timestamp="1281551596", > > > > oauth_version="1.0" > > > > > > Let me know if you came up with the same thing > > > > > > On Aug 11, 10:00 am, Tom van der Woerdt wrote: > > > >> On 8/11/10 5:52 PM, isaiah1112 wrote: > > > > > >>> I have been developing a completeOAuthLibrary for Twitter in > > > >>>AppleScript(I know, some people thought it was impossible but it > > > >>> isn't). The trouble is, I can authorizeOAuthand get my token and > > > >>> secret from Twitter without any issues. However, once I try to make > a > > > >>> call to the API the script will not validate my signature. I am > using > > > >>> the exact same methods to create my base string and signature that > I > > > >>> used to authorizeOAuthso I know it has to be an issue with either > my > > > >>> header or base string parameters for this call... If someone could > > > >>> look this over and tell me if everything checks out that would be > > > >>> great! > > > > > >>> This is a simple call to gethttps:// > api.twitter.com/1/direct_messages.xml > > > >>> api > > > > > >>> Base string is > > > > > >>> GET&https%3A%2F%2Fapi.twitter.com > > > >>> > %2F1%2Fdirect_messages.xml&oauth_consumer_key%3D2qKWThvrdoDBKeQCmIMA2w > > > >>> %26oauth_nonce > > > >>> > %3D28e0ef3fec75d92e6fc95460ffef4581ffd1d8f1%26oauth_signature_method > > > >>> %3DHMAC-SHA1%26oauth_token%3D90908405- > > > >>> B0SOI7v64YMcx7VOPTOvSieUOztDNPStWVY9rnabJ%26oauth_timestamp > > > >>> %3D1281541844%26oauth_version%3D1.0 > > > > > >>> The header for this call is listed as > > > > > >>> Authorization:OAuthoauth_consumer_key="2qKWThvrdoDBKeQCmIMA2w", > > > >>> oauth_nonce="28e0ef3fec75d92e6fc95460ffef4581ffd1d8f1", > > > >>> oauth_signature_method="HMAC-SHA1", > > > >>> oauth_signature="%2B8UDpXZN9SwZsUBsFNv%2B518sLg0%3D", > > > >>> oauth_token="90908405-B0SOI7v64YMcx7VOPTOvSieUOztDNPStWVY9rnabJ", > > > >>> oauth_timestamp="1281541844", > > > >>> oauth_version="1.0" > > > > > >>> If you would like any other information to test this out for > yourself > > > >>> please let me know! > > > > > >> If your code works with non-authorized requests and not with > authorized > > > >> ones, then I think that the issue would have to be with generating > your > > > >> "key". Make sure that you use &. > > > > > >> If this is not the case, then please try generating a signature for > > > >> verify_credentials.json, using the consumer key > "GDdmIQH6jhtmLUypg82g", > > > >> consumer secret "MCD8BKwGdgPHvAuvgvz4EQpqDAtx89grbuNMRd7Eh98", user > > > >> token "819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw" and user > > > >> secret "J6zix3FfA9LofH0awS24M3HcBYXO5nI1iYe8EfBA". Please post the > base > > > >> string and the signature which you generate. > > > > > >> Tom > > > > > >> PS: T
[twitter-dev] Re: OAuth Via AppleScript
have you finished the applescript for oauth? if you are planning on releasing it, i would be interested to grab a copy. thanks! On Aug 11, 3:22 pm, isaiah1112 wrote: > You were right! I forgot to sort them... Thanks! > > On Aug 11, 1:14 pm, Tom van der Woerdt wrote: > > > > > On 8/11/10 8:38 PM, isaiah1112 wrote: > > > > Ok... here is what I cam up with using the keys and secrets you > > > provided in your previous post > > > > Base String is: > > > > GET&https%3A%2F%2Fapi.twitter.com%2F1%2Faccount > > > %2Fverify_credentials.json&oauth_consumer_key%3DGDdmIQH6jhtmLUypg82g > > > %26oauth_nonce > > > %3D702fab381be61bb60f210dd07d80be722da33f05%26oauth_signature_method > > > %3DHMAC-SHA1%26oauth_token%3D819797- > > > Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw%26oauth_timestamp > > > %3D1281551596%26oauth_version%3D1.0 > > > > consumersecret&usersecret is: > > > MCD8BKwGdgPHvAuvgvz4EQpqDAtx89grbuNMRd7Eh98&J6zix3FfA9LofH0awS24M3HcBYXO5nI > > > 1iYe8EfBA > > > > Thus the non-url encoded signature would be: > > > XUNmLwpiC2W0xyrxPs4yAMmHO9c= > > > > And the HTTP header would be (signature is URL encoded): > > > > Authorization:OAuthoauth_consumer_key="GDdmIQH6jhtmLUypg82g", > > > oauth_nonce="702fab381be61bb60f210dd07d80be722da33f05", > > > oauth_signature_method="HMAC-SHA1", > > > oauth_signature="XUNmLwpiC2W0xyrxPs4yAMmHO9c%3D", > > > oauth_token="819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw", > > > oauth_timestamp="1281551596", > > > oauth_version="1.0" > > > > Let me know if you came up with the same thing > > > > On Aug 11, 10:00 am, Tom van der Woerdt wrote: > > >> On 8/11/10 5:52 PM, isaiah1112 wrote: > > > >>> I have been developing a completeOAuthLibrary for Twitter in > > >>>AppleScript(I know, some people thought it was impossible but it > > >>> isn't). The trouble is, I can authorizeOAuthand get my token and > > >>> secret from Twitter without any issues. However, once I try to make a > > >>> call to the API the script will not validate my signature. I am using > > >>> the exact same methods to create my base string and signature that I > > >>> used to authorizeOAuthso I know it has to be an issue with either my > > >>> header or base string parameters for this call... If someone could > > >>> look this over and tell me if everything checks out that would be > > >>> great! > > > >>> This is a simple call to > > >>> gethttps://api.twitter.com/1/direct_messages.xml > > >>> api > > > >>> Base string is > > > >>> GET&https%3A%2F%2Fapi.twitter.com > > >>> %2F1%2Fdirect_messages.xml&oauth_consumer_key%3D2qKWThvrdoDBKeQCmIMA2w > > >>> %26oauth_nonce > > >>> %3D28e0ef3fec75d92e6fc95460ffef4581ffd1d8f1%26oauth_signature_method > > >>> %3DHMAC-SHA1%26oauth_token%3D90908405- > > >>> B0SOI7v64YMcx7VOPTOvSieUOztDNPStWVY9rnabJ%26oauth_timestamp > > >>> %3D1281541844%26oauth_version%3D1.0 > > > >>> The header for this call is listed as > > > >>> Authorization:OAuthoauth_consumer_key="2qKWThvrdoDBKeQCmIMA2w", > > >>> oauth_nonce="28e0ef3fec75d92e6fc95460ffef4581ffd1d8f1", > > >>> oauth_signature_method="HMAC-SHA1", > > >>> oauth_signature="%2B8UDpXZN9SwZsUBsFNv%2B518sLg0%3D", > > >>> oauth_token="90908405-B0SOI7v64YMcx7VOPTOvSieUOztDNPStWVY9rnabJ", > > >>> oauth_timestamp="1281541844", > > >>> oauth_version="1.0" > > > >>> If you would like any other information to test this out for yourself > > >>> please let me know! > > > >> If your code works with non-authorized requests and not with authorized > > >> ones, then I think that the issue would have to be with generating your > > >> "key". Make sure that you use &. > > > >> If this is not the case, then please try generating a signature for > > >> verify_credentials.json, using the consumer key "GDdmIQH6jhtmLUypg82g", > > >> consumer secret "MCD8BKwGdgPHvAuvgvz4EQpqDAtx89grbuNMRd7Eh98", user > > >> token "819797-Jxq8aYUDRmykzVKrgoLhXSq67TEa5ruc4GJC2rWimw" and user > > >> secret "J6zix3FfA9LofH0awS24M3HcBYXO5nI1iYe8EfBA". Please post the base > > >> string and the signature which you generate. > > > >> Tom > > > >> PS: Those keys which I named aren't actual keys, I took them from > > >> dev.twitter.com. > > > Hi, > > > Using exactly the same values as you provided (including the base > > string), I got XUNmLwpiC2W0xyrxPs4yAMmHO9c= as well. > > > However, when I applied sort(), I got zKLhRH6fz/p7UtVsS25KPQGJWD0= > > > Apparently, your oauth_token and oauth_timestamp are in the wrong order ;-) > > > Tom -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] i'm looking for a Twitter expert
My develop site is wetradetogether.com. I need help to: - Starts on listening to public statuses in particular tweets that contain the stock symbol preceded by $. - Implement twitter4j library - Assists me to ask Twitter the signed access agreement to access to the Firehose. Regards Alfredo -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Why is Basic Auth still enabled on some sources?
Ryan, Proactive transparency in situations like these is very important, because that is the only way not to undermine your own credibility. Is there any way that the enforcement of rules can be made more equal for all services and developers? The last issue I encountered (Brian has the details) is where, a full four months after he asked me to remove something, I noticed another service that is very well-known to you, that is still doing exactly the same thing in a more egregious form than what my service ever did. If it were a few days after I could have chalked it up to still being in the process, but 4 months cannot be chalked up to that. And this is the second time that this kind of inequality has happened to me. On Sep 14, 1:09 pm, Ryan Sarver wrote: > Ed, > > As part of the migration we worked with many developers to help them with > the transition and some of them, including our own Android app, had some > extenuating circumstances that made them unable to make the date. For those > few exceptions and extreme cases we granted them a stay of execution as long > as they provided a reasonable timeline to make the transition. > > It pained us to do it for one of our own applications, but I'll give you > some detail to help you understand why we needed to. And to be clear, we did > this for a number of non-Twitter applications as well if we deemed their > situation to be one that needed the stay as well. In the end all of the apps > that got the stay were mobile apps that were unable to flash new versions > out to devices on their own schedule and that includes the Android app on a > number of devices. > > We have a hard shut-off date from Google which is only a few weeks away and > from every other app that was given an exemption. Rest assured that EVERY > app will be moved over in a timely fashion, so using their keys will only > give you a short window to continue to use Basic Auth. > > When looking at all the possible options and scenarios, we think this was > the right decision in order to move the entire ecosystem over to the new > authentication model while also being reasonable when we needed to be. > > Best, Ryan > > > > On Mon, Sep 13, 2010 at 1:40 PM, funkatron wrote: > > Read on this post:http://blog.nelhage.com/2010/09/dear-twitter/ > > > Tested just now:http://gist.github.com/577273 > > > If I pass "source=twitterandroid", it appears to work on all API > > methods. > > > In light of basic auth being "disabled," why does this work? > > > -- > > Ed Finkler > >http://funkatron.com > > @funkatron > > AIM: funka7ron / ICQ: 3922133 / > > XMPP:funkat...@gmail.com > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: POSTing problem
still getting the 401 basestring: POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26 oauth_signature_method%3DHMAC-SHA1%26 oauth_timestamp%3D1284487942%26 oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 oauth_version%3D1.0%26 status%3Dsetting%2520up%2520my%2520twitter POST: POST /1/statuses/update.xml? HTTP/1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942", oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0" Content-Length: 40 status=setting%2520up%2520my%2520twitter On Sep 14, 11:39 am, Tom van der Woerdt wrote: > It says "setting up my twitter" in the Base String, not "status=setting > up my twitter". > > Tom > > On 9/14/10 7:30 PM, MTCoder wrote: > > > > > > > > > Im posting this again here to make sure its seen (other thread here > >http://groups.google.com/group/twitter-development-talk/browse_thread...) > > > I have tried many different things and cant seem to get the status > > POST to work(thanks Tom for the help with getting the timeline). > > > my base string: > > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > > oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26 > > oauth_signature_method%3DHMAC-SHA1%26 > > oauth_timestamp%3D1284483693%26 > > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > > oauth_version%3D1.0%26setting%2520up%2520my%2520twitter > > > And the POST: > > > POST /1/statuses/update.xml? HTTP/1.1 > > Content-Type: application/x-www-form-urlencoded > > Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934", > > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693", > > oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > > oauth_signature="vZt0cwQJV%2FeZUPSRPAjfpEBhONM%3D", > > oauth_version="1.0" > > Content-Length: 40 > > > status=setting%2520up%2520my%2520twitter > > > Any help/ideas would be greatly appreciated. > > > Thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: list api create_all method not working
Hello,
I find that pushing 99 users into a create_all call will fall over
fairly often with a 502 error. To get around that, I've backed down
as far as 5...
Although, and I might be just totally & completely wrong about this,
it seems like the response codes don't *completely* line up with the
actual result. It could be due to the methods I'm using, but it seems
like I could get 502 response codes & still have success. I haven't
had the time to set up strict testing on this, yet.
I've also found that the 500-user max for lists isn't a hard-set
rule. I've seen lists that I create go into the 600s... They usually
get corrected later on, though, so I'm not sure what causes that
glitch.
-Jim
On Sep 14, 1:11 pm, Ken wrote:
> Finally, after discovering this thread, I added /members/ to
> thecreate_allendpoint and was able to add 98 members to alist. As
> twitter would say, 'Yay'...
>
> I filed a bug to have the documentation corrected.
>
> Are there still problems adding lots of members, as reported earlier
> in this thread? Since rate-limiting as listed as false in the doc,
> would it be more reliable to just loop over :user/:list_id/members 100
> times? I need to go for "reliable" wherever possible... That way we
> could add up to the 500 members maximum. Recommended ornotreally?
>
> Thanks
> -Ken
>
> On Aug 23, 9:07 pm, Jim Chevalier wrote:
>
> > Hello,
>
> > Ah-ha! I didnothave /members/ in my POST URL. Thanks for pointing
> > that out!
> > This actually make it seem
> > likehttp://dev.twitter.com/doc/post/:user/:list_id/create_all
> > should be changed to state:
> > POSThttp://api.twitter.com/version/:user/:list_id/members/create_all.format
>
> > I also didn't realize I could/should check on $connection->http_code
> > so often. Thanks for pointing that out as well.
> > It's funny, now that you mention it, I notice the test.php file you
> > included in twitteroauth has that call *everywhere*.
>
> > It seems like I should rewrite my calls to be more like the
> > "twitteroauth_row" function you define in the test.php file so that I
> > can use the $connection->http_code results as error-checking.
> > I'll also have to test if setting "public $retry = TRUE;" in the
> > twitteroauth.php file helps with the 502 response that comes when
> > attempting to push 99 users through thecreate_allcall...
>
> > Thanks for all the help!
> > -Jim
>
> > On Aug 23, 2:44 pm, Abraham Williams <4bra...@gmail.com> wrote:
>
> > > After each TwitterOAuth call you should check $connection->http_code to
> > > check what the result is. 200 on success, 404 onnotfound, etc.
>
> > > My quick findings:
> > > Works: $connection->post('abraham/test3/members/create_all',
> > > array('user_id'
> > > => $user_ids));
> > > AKA: $connection->post('{$screen_name/{$list}/members/create_all',
> > > array('user_id' => $user_ids));
>
> > > But with the 99 user_ids it would usually return a 502 after adding ~60
> > > users to thelist:http://goo.gl/Zur3
>
> > > Abraham
> > > -
> > > Abraham Williams | Hacker Advocate |http://abrah.am
> > > @abraham |http://projects.abrah.am|http://blog.abrah.am
> > > This email is: [ ] shareable [x] ask first [ ] private.
>
> > > On Mon, Aug 23, 2010 at 10:54, Jim Chevalier wrote:
> > > > hrm, back to square one then...
>
> > > > Abraham - the value of $users is:
>
> > > > 2142731,14125623,15998931,19560364,16559320,17036420,14791918,16908659,5538992,14984281,20188175,14277276,111226850,14327961,20257060,94168006,107679193,54567920,18171797,8886022,16390772,69422500,171538302,818340,168929218,141333525,132534968,14124542,14408989,138293290,2039761,6752072,111896485,175801197,14912789,22907920,15099178,16583906,10870772,94269486,174521748,82002786,15395087,39407092,123734452,17193910,16362662,7762662,21514744,7596972,31563269,23147529,27440127,14337563,1528701,82497472,19251912,15292430,17005679,7192042,14600753,97484744,2023641,92086501,15447441,98735657,16950385,2023191,14411651,23111875,2900,15039436,14479810,16024218,57933102,8453452,18363508,16569530,21034443,17007607,7029452,54997124,47397228,15226527,18193201,22278762,15127641,14204449,60616288,16465359,10371312,15805506,14995035,27727035,19211127,35279958,18023868,9369722,8088412
>
> > > > That's 99 users, in what I believe to be the correct format.
>
> > > > I also ran a test with just 8088412 like this, with the same (blank)
> > > > result:
> > > > $users = 8088412;
> > > > $added = $connection->post("{$user->screen_name}/lists/$listid->id/
> > > >create_all", array('user_id' => $users));
> > > > print_r($added);
>
> > > > Since it seems like the 'create_all' call itself that's the problem, I
> > > > decided to run another test:
> > > > $blahblah = $connection->post("{$user->screen_name}/{$list->id}/
> > > > qhweoi", array('user_id' => $users));
> > > > print_r($blahblah);
>
> > > > This returned nothing, similar to my 'create_all' call. Since
> > > > 'qhweoi' isnota valid TwitterAPIcall, I'm wondering if either
> > > > twitteroauth
[twitter-dev] Re: Get All Followers Using twitteroauth
Hi
I tryed and I did this code.
$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET,
$access_token['oauth_token'], $access_token['oauth_token_secret']);
$content = $connection->get('account/verify_credentials');
$totalFollowers = $content->followers_count;
$cursor = -1;
$qtd = ceil($totalFollowers/100);
for($z=0;$z<$qtd;$z++){
$result = $connection->get('statuses/followers', array('cursor' =>
$cursor));
$cursor = $result->next_cursor_str;
$user = $result->users;
$total = count($user);
for( $i=0;$i<$total;$i++ ){
$users[] = $user[$i]->screen_name;
}
}
It works, but I'm afraid about people who has more than 35000
followers
everybody know that 350 is the maximum request that you can do
Someone know something about how around this?
Thanks
On 9 set, 13:49, Abraham Williams <4bra...@gmail.com> wrote:
> $connection = new TwitterOAuth('consumer_key', 'consumer_secret',
> 'access_token', 'access_token_secret');
> $result100 = $connection->get('statuses/followers', array('cursor' => -1));
> $result200 = $connection->get('statuses/followers', array('cursor' =>
> $result100->next_cursor));
>
> You will be best off writing a loop instead of manually specifying how many
> blocks of 100 it pulls in. $result100->users will be an array of users.
>
> Abraham
> -
> Abraham Williams | Hacker Advocate |http://abrah.am
> @abraham |http://projects.abrah.am|http://blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
>
> On Thu, Sep 9, 2010 at 08:59, Paulo Fernandes
> wrote:
>
> > Hi
>
> > I'm beggining in this API and in this group.
>
> > I downloaded 0.2.0-beta3 fromhttp://github.com/abraham/twitteroauth
>
> > I tryed to get all followers, but only retrieved 100 followers.
>
> > How can I get all followers? I saw something about cursor, but I don't
> > know how can I use it.
>
> > Please some help will be useful
>
> > Thanks
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk?hl=en
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] POSTing problem
It says "setting up my twitter" in the Base String, not "status=setting up my twitter". Tom On 9/14/10 7:30 PM, MTCoder wrote: > Im posting this again here to make sure its seen (other thread here > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fb1f29a6e43c48e3) > > I have tried many different things and cant seem to get the status > POST to work(thanks Tom for the help with getting the timeline). > > my base string: > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26 > oauth_signature_method%3DHMAC-SHA1%26 > oauth_timestamp%3D1284483693%26 > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > oauth_version%3D1.0%26setting%2520up%2520my%2520twitter > > And the POST: > > POST /1/statuses/update.xml? HTTP/1.1 > Content-Type: application/x-www-form-urlencoded > Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934", > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693", > oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > oauth_signature="vZt0cwQJV%2FeZUPSRPAjfpEBhONM%3D", > oauth_version="1.0" > Content-Length: 40 > > status=setting%2520up%2520my%2520twitter > > Any help/ideas would be greatly appreciated. > > Thanks > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] list members cursor is wrong
GET works fine for this method and when I test the cursors for your list below everything works correctly. So we can work out what is going on can you share the headers you are sending to the API. Also, you will want to update your URLs to the correct host. The correct URL to use is http://api.twitter.com/1/ -- making your request: http://api.twitter.com/1/endlesscities/urban/members.json?cursor=-1 Best, Matt On Sun, Sep 12, 2010 at 6:44 PM, Brad wrote: > maybe I'm doing something wrong, but the cursor returned from the list > members call seems to be misbehaving. > > if I hit: > http://twitter.com/endlesscities/urban/members.json?cursor=-1 > > it returns > "next_cursor":1343981850785981701, "previous_cursor":0 > > if I pass it that new cursor: > http://twitter.com/endlesscities/urban/members.json?cursor=1343981850785981701 > > it returns the same thing: > "next_cursor":1343981850785981701, "previous_cursor":0 > > What's up with that? This has cropped up thanks to switching from > basic Auth to Oauth. I'm doing a GET because it won't allow me to do a > POST. > > thanks in advance for any help. > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Oauth problems?
Is that your full request? I don't see a Host: header, I don't see an
User-Agent header, etc.
Tom
On 9/14/10 6:53 PM, MTCoder wrote:
> thanks, that did the trick for reading the timeline. Now I'm having
> problems writing to the account.
> Any ideas?
>
> basestring:
> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&
> oauth_consumer_key%3Dx%26
> oauth_nonce%3D444E51674F345149343D3D6A4D54304D%26
> oauth_signature_method%3DHMAC-SHA1%26
> oauth_timestamp%3D1284482849%26
> oauth_token%3DYY%26
> oauth_version%3D1.0%26
> status%3Dsetting%2520up%2520my%2520twitter
>
>
> Post:
> POST /1/statuses/update.xml? HTTP/1.1
> Content-Type: application/x-www-form-urlencoded
> Authorization: OAuth oauth_nonce="444E51674F345149343D3D6A4D54304D",
> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284482849",
> oauth_consumer_key="XXX",
> oauth_token="Yy",
> oauth_signature="ImTblfpYy7xD%2FZBk7%2BqPqwgILqU%3D",
> oauth_version="1.0"
> Content-Length: 28
>
> status=setting+up+my+twitter
>
>
>
>
>
>
> On Sep 10, 3:57 pm, Tom van der Woerdt wrote:
>> You should encode the values in the Authorization: header.
>>
>> Tom
>>
>> On 9/10/10 11:50 PM, MTCoder wrote:
>>
>>
>>
>>
>>
>>
>>
>>> i have written code (working code for a client app) up to the point of
>>> posting/reading to a twitter timeline.
>>> The user has allowed my app access and i have the token and token
>>> secret.
>>> Also i have double checked the signature and everything else and they
>>> all seem correct
>>> (http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
>>> is a awesome for this).
>>
>>> Now my problem:
>>> whenever i call to get the timeline or post a new status to the
>>> timeline i get the return of
>>> "Status: 500 Internal Server Error" in the response header and the
>>> body is an html page saying "Something is technically wrong."
>>
>>> So is them my problem or Twitters?
>>
>>> base string:
>>> GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
>>> %2Fhome_timeline.xml&oauth_consumer_key%3DK%26oauth_nonce
>>> %3D4E3431495445554D4E413D344E3D%26oauth_signature_method%3DHMAC-
>>> SHA1%26oauth_timestamp%3D1284154584%26oauth_token%3D
>>> %26oauth_version%3D1.0
>>
>>> my request:
>>
>>> GET /1/statuses/home_timeline.xml HTTP/1.1
>>> Authorization: OAuth realm="",
>>> oauth_nonce="4E3431495445554D4E413D344E3D",
>>> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284154584",
>>> oauth_consumer_key="K", oauth_token="",
>>> oauth_signature="zd8hazoYu5azlVDhnJ8/mr1jkwk=", oauth_version="1.0"
>>
>>> also, im using the Chilkat HTTP lib on this one, in C++:
>>
>>> CkHttp http;
>>> CkHttpRequest req;
>>> CkString header;
>>
>>>sig = CreateOauthSig(base_string);
>>
>>>// Build an HTTP POST Request:http://twitter.com/statuses/update.xml
>>>req.UseGet();
>>>req.put_Path("/1/statuses/home_timeline.xml");
>>
>>>//build the header
>>>header.append("OAuth realm=\"\", oauth_nonce=\"");
>>>header.appendStr(nonce);
>>>header.append("\", oauth_signature_method=\"HMAC-SHA1\",
>>> oauth_timestamp=\"");
>>>header.appendStr(time_str);
>>>header.append("\", oauth_consumer_key=\"KK\", oauth_token=
>>> \"");
>>>header.appendStr(token);
>>>header.append("\", oauth_signature=\"");
>>>header.appendStr(sig);
>>>header.append("\", oauth_version=\"1.0\"");
>>
>>>req.AddHeader("Authorization",header.getAnsi());
>>
>>>BOOL success=FALSE;
>>
>>>const char * domain;
>>>long port;
>>>bool ssl;
>>>domain = "api.twitter.com";
>>>port = 80;
>>>ssl = false;
>>
>>>CkHttpResponse *resp = 0;
>>>resp = http.SynchronousRequest(domain,port,ssl,req);
>>
>>> Please let me know what other info might help,
>>> MTCoder
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] POSTing problem
Im posting this again here to make sure its seen (other thread here http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fb1f29a6e43c48e3) I have tried many different things and cant seem to get the status POST to work(thanks Tom for the help with getting the timeline). my base string: POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26 oauth_signature_method%3DHMAC-SHA1%26 oauth_timestamp%3D1284483693%26 oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 oauth_version%3D1.0%26setting%2520up%2520my%2520twitter And the POST: POST /1/statuses/update.xml? HTTP/1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693", oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", oauth_signature="vZt0cwQJV%2FeZUPSRPAjfpEBhONM%3D", oauth_version="1.0" Content-Length: 40 status=setting%2520up%2520my%2520twitter Any help/ideas would be greatly appreciated. Thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Missing entities in REST
i have 17312534 (bangmarketing) and 13024412 (thewitness) thanks On Sep 14, 11:34 am, FearMediocrity wrote: > I've tried it on two accounts, from 2 oAuth REST API apps. > > User id: > > 11747852 (FearMediocrity) > 18804420 (ThinkingInCode) > > James > > On Sep 14, 3:06 pm, Taylor Singletary > wrote: > > > > > > > > > Hi Everyone, > > > We're still investigating this issue -- it is not happening > > consistently across the board and has been difficult to track down. > > > If you're *never* getting entities when requesting timelines, and you're > > including include_entities=true then please leave your member id here for > > additional investigation. > > > Hope to have this fixed soon. > > > Thanks, > > Taylor > > > On Tue, Sep 14, 2010 at 6:20 AM, FearMediocrity wrote: > > > I don't think your doing anything wrong. include_entities hasn't > > > worked for me since late last week. @twitterapi mentioned a problem, > > > but then nothing since. > > > > Can we have an update please? > > > > On Sep 13, 7:16 pm, Jesse wrote: > > > > Hi, I'm trying to view my last tweet, but I can't seem to be able to > > > > see the Tweet Entities. > > > > > Here is what I'm trying to view: > > >http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=(reda... > > > > > But I don't see the "entities" element. > > > > > Any help would be appreciated > > > > Thanks > > > > -- > > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Oauth problems?
thanks, that did the trick for reading the timeline. Now I'm having
problems writing to the account.
Any ideas?
basestring:
POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&
oauth_consumer_key%3Dx%26
oauth_nonce%3D444E51674F345149343D3D6A4D54304D%26
oauth_signature_method%3DHMAC-SHA1%26
oauth_timestamp%3D1284482849%26
oauth_token%3DYY%26
oauth_version%3D1.0%26
status%3Dsetting%2520up%2520my%2520twitter
Post:
POST /1/statuses/update.xml? HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth oauth_nonce="444E51674F345149343D3D6A4D54304D",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284482849",
oauth_consumer_key="XXX",
oauth_token="Yy",
oauth_signature="ImTblfpYy7xD%2FZBk7%2BqPqwgILqU%3D",
oauth_version="1.0"
Content-Length: 28
status=setting+up+my+twitter
On Sep 10, 3:57 pm, Tom van der Woerdt wrote:
> You should encode the values in the Authorization: header.
>
> Tom
>
> On 9/10/10 11:50 PM, MTCoder wrote:
>
>
>
>
>
>
>
> > i have written code (working code for a client app) up to the point of
> > posting/reading to a twitter timeline.
> > The user has allowed my app access and i have the token and token
> > secret.
> > Also i have double checked the signature and everything else and they
> > all seem correct
> > (http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
> > is a awesome for this).
>
> > Now my problem:
> > whenever i call to get the timeline or post a new status to the
> > timeline i get the return of
> > "Status: 500 Internal Server Error" in the response header and the
> > body is an html page saying "Something is technically wrong."
>
> > So is them my problem or Twitters?
>
> > base string:
> > GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
> > %2Fhome_timeline.xml&oauth_consumer_key%3DK%26oauth_nonce
> > %3D4E3431495445554D4E413D344E3D%26oauth_signature_method%3DHMAC-
> > SHA1%26oauth_timestamp%3D1284154584%26oauth_token%3D
> > %26oauth_version%3D1.0
>
> > my request:
>
> > GET /1/statuses/home_timeline.xml HTTP/1.1
> > Authorization: OAuth realm="",
> > oauth_nonce="4E3431495445554D4E413D344E3D",
> > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284154584",
> > oauth_consumer_key="K", oauth_token="",
> > oauth_signature="zd8hazoYu5azlVDhnJ8/mr1jkwk=", oauth_version="1.0"
>
> > also, im using the Chilkat HTTP lib on this one, in C++:
>
> > CkHttp http;
> > CkHttpRequest req;
> > CkString header;
>
> > sig = CreateOauthSig(base_string);
>
> > // Build an HTTP POST Request:http://twitter.com/statuses/update.xml
> > req.UseGet();
> > req.put_Path("/1/statuses/home_timeline.xml");
>
> > //build the header
> > header.append("OAuth realm=\"\", oauth_nonce=\"");
> > header.appendStr(nonce);
> > header.append("\", oauth_signature_method=\"HMAC-SHA1\",
> > oauth_timestamp=\"");
> > header.appendStr(time_str);
> > header.append("\", oauth_consumer_key=\"KK\", oauth_token=
> > \"");
> > header.appendStr(token);
> > header.append("\", oauth_signature=\"");
> > header.appendStr(sig);
> > header.append("\", oauth_version=\"1.0\"");
>
> > req.AddHeader("Authorization",header.getAnsi());
>
> > BOOL success=FALSE;
>
> > const char * domain;
> > long port;
> > bool ssl;
> > domain = "api.twitter.com";
> > port = 80;
> > ssl = false;
>
> > CkHttpResponse *resp = 0;
> > resp = http.SynchronousRequest(domain,port,ssl,req);
>
> > Please let me know what other info might help,
> > MTCoder
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] HttpRequest and Unshortening problems
Hi Everyone, I was trying to make httpRequst with shortened urls , but I think it is not possible So now I'm first unshorting the url and then making the httpRequest. I'm using http://untiny.me as unshortener server, but I'm getting Unshortener Errors at 80% of urls... So , dou you guys know any other better server or other way to make httpRequest with a shortened url ? Thanks -- João Paulo S. de Moraes +55 81 3432 3804 +55 81 9189 3814 (mobile) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: list api create_all method not working
Finally, after discovering this thread, I added /members/ to the
create_all endpoint and was able to add 98 members to a list. As
twitter would say, 'Yay'...
I filed a bug to have the documentation corrected.
Are there still problems adding lots of members, as reported earlier
in this thread? Since rate-limiting as listed as false in the doc,
would it be more reliable to just loop over :user/:list_id/members 100
times? I need to go for "reliable" wherever possible... That way we
could add up to the 500 members maximum. Recommended or not really?
Thanks
-Ken
On Aug 23, 9:07 pm, Jim Chevalier wrote:
> Hello,
>
> Ah-ha! I did not have /members/ in my POST URL. Thanks for pointing
> that out!
> This actually make it seem
> likehttp://dev.twitter.com/doc/post/:user/:list_id/create_all
> should be changed to state:
> POSThttp://api.twitter.com/version/:user/:list_id/members/create_all.format
>
> I also didn't realize I could/should check on $connection->http_code
> so often. Thanks for pointing that out as well.
> It's funny, now that you mention it, I notice the test.php file you
> included in twitteroauth has that call *everywhere*.
>
> It seems like I should rewrite my calls to be more like the
> "twitteroauth_row" function you define in the test.php file so that I
> can use the $connection->http_code results as error-checking.
> I'll also have to test if setting "public $retry = TRUE;" in the
> twitteroauth.php file helps with the 502 response that comes when
> attempting to push 99 users through the create_all call...
>
> Thanks for all the help!
> -Jim
>
> On Aug 23, 2:44 pm, Abraham Williams <4bra...@gmail.com> wrote:
>
> > After each TwitterOAuth call you should check $connection->http_code to
> > check what the result is. 200 on success, 404 on not found, etc.
>
> > My quick findings:
> > Works: $connection->post('abraham/test3/members/create_all', array('user_id'
> > => $user_ids));
> > AKA: $connection->post('{$screen_name/{$list}/members/create_all',
> > array('user_id' => $user_ids));
>
> > But with the 99 user_ids it would usually return a 502 after adding ~60
> > users to the list:http://goo.gl/Zur3
>
> > Abraham
> > -
> > Abraham Williams | Hacker Advocate |http://abrah.am
> > @abraham |http://projects.abrah.am|http://blog.abrah.am
> > This email is: [ ] shareable [x] ask first [ ] private.
>
> > On Mon, Aug 23, 2010 at 10:54, Jim Chevalier wrote:
> > > hrm, back to square one then...
>
> > > Abraham - the value of $users is:
>
> > > 2142731,14125623,15998931,19560364,16559320,17036420,14791918,16908659,5538992,14984281,20188175,14277276,111226850,14327961,20257060,94168006,107679193,54567920,18171797,8886022,16390772,69422500,171538302,818340,168929218,141333525,132534968,14124542,14408989,138293290,2039761,6752072,111896485,175801197,14912789,22907920,15099178,16583906,10870772,94269486,174521748,82002786,15395087,39407092,123734452,17193910,16362662,7762662,21514744,7596972,31563269,23147529,27440127,14337563,1528701,82497472,19251912,15292430,17005679,7192042,14600753,97484744,2023641,92086501,15447441,98735657,16950385,2023191,14411651,23111875,2900,15039436,14479810,16024218,57933102,8453452,18363508,16569530,21034443,17007607,7029452,54997124,47397228,15226527,18193201,22278762,15127641,14204449,60616288,16465359,10371312,15805506,14995035,27727035,19211127,35279958,18023868,9369722,8088412
>
> > > That's 99 users, in what I believe to be the correct format.
>
> > > I also ran a test with just 8088412 like this, with the same (blank)
> > > result:
> > > $users = 8088412;
> > > $added = $connection->post("{$user->screen_name}/lists/$listid->id/
> > > create_all", array('user_id' => $users));
> > > print_r($added);
>
> > > Since it seems like the 'create_all' call itself that's the problem, I
> > > decided to run another test:
> > > $blahblah = $connection->post("{$user->screen_name}/{$list->id}/
> > > qhweoi", array('user_id' => $users));
> > > print_r($blahblah);
>
> > > This returned nothing, similar to my 'create_all' call. Since
> > > 'qhweoi' is not a valid Twitter API call, I'm wondering if either
> > > twitteroauth just doesn't do the "create_all" call for lists or if my
> > > implementation of it is broken...
>
> > > Thanks everyone!
> > > -Jim
>
> > > On Aug 23, 12:56 pm, Taylor Singletary
> > > wrote:
> > > > I'm filled with misinformation today.
>
> > > > But after being set straight by my colleague Matt Harris, I can tell you
> > > > that the correct end point for this method is in actuality:
>
> > > >http://api.twitter.com/1/:user/:list_id/members/create_all.format
>
> > > > Our list methods are obviously confusing in their lack of a
> > > distinguished,
> > > > consistent namespace.
>
> > > > Taylor
>
> > > > On Mon, Aug 23, 2010 at 9:07 AM, Abraham Williams <4bra...@gmail.com>
> > > wrote:
> > > > > Jim,
>
> > > > > What is your value for $users?
>
> > > > > Abraham
> > > > > -
> > > > > Abraham Williams | Hacker Advocate |http://abrah.am
>
Re: [twitter-dev] Getting the latest status
Hi Matei, The simplest way to accomplish this would be a single GET request. GET http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=twitterapi&count=1&include_rts=true If you weren't interested in processing retweets, you could omit the include_rts=true parameter, but I would bump the count to at least 5 since disincluded retweets still apply to the count parameter's calculations. Taylor On Tue, Sep 14, 2010 at 9:51 AM, Matei wrote: > Hi all, > > I was wondering what the best way to get a user's latest status is. > Right now I am using the verify_credentials call to do it, since I > don't really know the user Id from the OAuth flow. The trouble with > this approach is that the result doesn't always include the status. Is > there a better way of doing this, maybe I'm totally missing something > obvious. > > BTW, the project I'm on uses heavy JavaScript and a C# backed to proxy > Twitter API calls. > > Cheers, > Matei > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Getting the latest status
Hi all, I was wondering what the best way to get a user's latest status is. Right now I am using the verify_credentials call to do it, since I don't really know the user Id from the OAuth flow. The trouble with this approach is that the result doesn't always include the status. Is there a better way of doing this, maybe I'm totally missing something obvious. BTW, the project I'm on uses heavy JavaScript and a C# backed to proxy Twitter API calls. Cheers, Matei -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Geo Search -> Tweet Search
I have the results from Geo Search coming back and I want to feed this
into a subsequent Search API query to base the tweet search radius on.
However, I'm not sure the best means to use the bounding box
coordinates. Given this:
"bounding_box": {
"coordinates": [
[[
-82.437165,
41.065485
], [
-82.387024,
41.065485
], [
-82.387024,
41.094768
], [
-82.437165,
41.094768
]
]
],
The (tweet) Search API requires a single lat/long for a geo radius,
not a bounding box. I am assuming that it would be best to calculate
the central point of the four coordinates and pass that onto Search?
I wonder what Twitter does in their advanced search, under the covers,
as they would have the same issue.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Why is Basic Auth still enabled on some sources?
Ed, As part of the migration we worked with many developers to help them with the transition and some of them, including our own Android app, had some extenuating circumstances that made them unable to make the date. For those few exceptions and extreme cases we granted them a stay of execution as long as they provided a reasonable timeline to make the transition. It pained us to do it for one of our own applications, but I'll give you some detail to help you understand why we needed to. And to be clear, we did this for a number of non-Twitter applications as well if we deemed their situation to be one that needed the stay as well. In the end all of the apps that got the stay were mobile apps that were unable to flash new versions out to devices on their own schedule and that includes the Android app on a number of devices. We have a hard shut-off date from Google which is only a few weeks away and from every other app that was given an exemption. Rest assured that EVERY app will be moved over in a timely fashion, so using their keys will only give you a short window to continue to use Basic Auth. When looking at all the possible options and scenarios, we think this was the right decision in order to move the entire ecosystem over to the new authentication model while also being reasonable when we needed to be. Best, Ryan On Mon, Sep 13, 2010 at 1:40 PM, funkatron wrote: > Read on this post: http://blog.nelhage.com/2010/09/dear-twitter/ > > Tested just now: http://gist.github.com/577273 > > If I pass "source=twitterandroid", it appears to work on all API > methods. > > In light of basic auth being "disabled," why does this work? > > -- > Ed Finkler > http://funkatron.com > @funkatron > AIM: funka7ron / ICQ: 3922133 / > XMPP:funkat...@gmail.com > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] twitter relationship
Hey Ashy, The system we use for doing this (flock) is open-sourced on github. It is a graph database designed for storing information like follows. You can find more information and the code at: http://github.com/twitter/flockdb Hope that is helpful, @themattharris On Sep 14, 2010, at 7:10, ashy wrote: > Hi All, > > I want to represent the relationship seen in twitter into the > database. For eg : user1 is following user2, user3, user 4, user 5 and > user6. But user5 and user6 are following user1 in turn. How would > design the database to represent this relationship. Any ideas? > > thanks >ashy > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Tweet Button counter url encoding
Hi Remo,
This is one of the known issues reported by some other users. We're working on
a fix for it.
Best,
Matt
On Sep 14, 2010, at 5:16, Remo wrote:
> Hi
>
> If I use a tweet button on a site with an url including a "+" sign,
> the counter is not working (always displays 0).
>
> It only works when I use the data-counturl parameter with the encoded
> url ("+" encoded to "%2B").
> But then, when i click the counter button, the search fails because
> the "%" sign is encoded to "%25".
>
> How is the tweet button supposed to work with urls including a "+"
> sign?
>
> Thank you in advance for your help
>
> Cheers
> Remo
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] remote server returned an error: (401) Unauthorized - Twiiter API - Error
Hey Yogesh, When we return an error like that we put a reason in the body of the response. Can you let us know what that reason is so we can help further. Best, Matt On Sep 14, 2010, at 8:21, YogeshG wrote: > hi, > > > I am posting Twitts, using Twitter API. My application is suppose to > post 4 status in a row at 11:00 o'clock .(I have tried giving 30 sec > delay between each status). However The first Status (Twitt) get > Posted Successfully. > > But for next subsequetn post it Returns - "remote server returned an > error: (401) Unauthorized ". Kindy suggest the solution.. > > > If the 1st status gets Authorized. How come next one - > "Unauthorized" ??? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] remote server returned an error: (401) Unauthorized - Twiiter API - Error
Are you generating random oauth_nonce values? Tom On 9/14/10 5:21 PM, YogeshG wrote: > hi, > > > I am posting Twitts, using Twitter API. My application is suppose to > post 4 status in a row at 11:00 o'clock .(I have tried giving 30 sec > delay between each status). However The first Status (Twitt) get > Posted Successfully. > > But for next subsequetn post it Returns - "remote server returned an > error: (401) Unauthorized ". Kindy suggest the solution.. > > > If the 1st status gets Authorized. How come next one - > "Unauthorized" ??? > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Missing entities in REST
I've tried it on two accounts, from 2 oAuth REST API apps. User id: 11747852 (FearMediocrity) 18804420 (ThinkingInCode) James On Sep 14, 3:06 pm, Taylor Singletary wrote: > Hi Everyone, > > We're still investigating this issue -- it is not happening > consistently across the board and has been difficult to track down. > > If you're *never* getting entities when requesting timelines, and you're > including include_entities=true then please leave your member id here for > additional investigation. > > Hope to have this fixed soon. > > Thanks, > Taylor > > > > On Tue, Sep 14, 2010 at 6:20 AM, FearMediocrity wrote: > > I don't think your doing anything wrong. include_entities hasn't > > worked for me since late last week. @twitterapi mentioned a problem, > > but then nothing since. > > > Can we have an update please? > > > On Sep 13, 7:16 pm, Jesse wrote: > > > Hi, I'm trying to view my last tweet, but I can't seem to be able to > > > see the Tweet Entities. > > > > Here is what I'm trying to view: > >http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=(reda... > > > > But I don't see the "entities" element. > > > > Any help would be appreciated > > > Thanks > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] remote server returned an error: (401) Unauthorized - Twiiter API - Error
hi, I am posting Twitts, using Twitter API. My application is suppose to post 4 status in a row at 11:00 o'clock .(I have tried giving 30 sec delay between each status). However The first Status (Twitt) get Posted Successfully. But for next subsequetn post it Returns - "remote server returned an error: (401) Unauthorized ". Kindy suggest the solution.. If the 1st status gets Authorized. How come next one - "Unauthorized" ??? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Displaying Friends Tweets Requires a log in each time
Thanks for the heads up... working perfectly! :)
On Sep 10, 6:51 pm, Taylor Singletary
wrote:
> Hi Ed,
>
> This is the perfect scenario for:
>
> a) You'll want to use OAuth to authorize a single account (the "owner" of
> the friends_timeline)http://dev.twitter.com/pages/oauth_single_token
> b) You'll store the access token for the owner of the account directly in
> the script you use to fetch friends_timeline
> c) You'll then use that access token, server-side every time you need to
> request the timeline
> d) You'll use some form of caching to prevent a fetch of the timeline on
> every page load
>
> And just wanted to add that friends_timeline is a very old resource and the
> /statuses/home_timeline is a superior resource, offering additional
> functionality not found in friends_timeline.
>
> Hope this helps!
> Taylor
>
> On Fri, Sep 10, 2010 at 3:41 PM, contact.edmur...@gmail.com <
>
> contact.edmur...@gmail.com> wrote:
> > Hi there, thanks for responding-
>
> > I'm using the following: $content = $connection->get("statuses/
> > friends_timeline", array());
>
> > This is a PHP script that displays friends tweets, as this is for a
> > company website, and we only follow certain employees with permission
> > of course.
>
> > Our home company timeline currently has no tweets, I simply use
> > Twitter to follow a select group of ppl and display said tweets.
>
> > Is there a work around that I missing when it comes to having visitors
> > of my site view these Tweets without having to log in? Thanks,
> > additional assistance is welcome.
>
> > On Sep 10, 11:38 am, Taylor Singletary
> > wrote:
> > > Hi,
>
> > > It depends on how you're accessing and displaying the tweets... are you
> > > trying to show your home timeline (the tweets you typically see on
> > > twitter.com's home page while logged in), or are you trying to show your
> > own
> > > tweets, or are you trying to show someone else's tweets?
>
> > > Showing your own home timeline requires authentication, as there must be
> > a
> > > perspective of who's home timeline is being viewed. Further, it's not
> > > appropriate to post your own home timeline where others can see it, as
> > you
> > > may be following protected accounts and putting those user's privacy at
> > > risk.
>
> > > Fetching an unprotected user's timeline (their tweets, your tweets) does
> > not
> > > require authentication.
>
> > > How are you currently integrating the streams into your site? A
> > server-side
> > > fetch, a client-side fetch? A widget?
>
> > > Taylor
>
> > > On Thu, Sep 9, 2010 at 6:53 PM, contact.edmur...@gmail.com <
>
> > > contact.edmur...@gmail.com> wrote:
> > > > Hi there- With the outdated Basic Authentication method, I was able
> > > > to display my freinds tweets on my web page without a problem. Now
> > > > with oAuth, unless already logged in, I have to click the login button
> > > > with Twitter each time to display that content. Multiple that for
> > > > each person that visits my web page. Headach City!
>
> > > > Is there something I am missing? Can the login be done once and
> > > > always display said content when someone visits my site? Thanks, any
> > > > help is appreciated!
>
> > > > --
> > > > Twitter developer documentation and resources:
> >http://dev.twitter.com/doc
> > > > API updates via Twitter:http://twitter.com/twitterapi
> > > > Issues/Enhancements Tracker:
> > > >http://code.google.com/p/twitter-api/issues/list
> > > > Change your membership to this group:
> > > >http://groups.google.com/group/twitter-development-talk?hl=en
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk?hl=en
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] get starting with xAuth for TwitterAPI
Hi Andreas, oauth_nonce is a random value. Just make sure that it's random enough and it'll be fine. There's no need to encrypt the password when using xAuth - if I am not mistaken, xAuth only allows https:// connections and these are encrypted enough. The token and secret are used to sign your requests to Twitter, to let Twitter verify that the request is actually coming from your application, and to verify the user (Although with xAuth the user part isn't available yet). Tom On 9/14/10 4:31 PM, andreas-wilkeme...@andreazw.de wrote: > Hello everyone, > > I have any problems to develop my desktop-Application with an own > Twitter Client. In my client to the user have the option to enter > their user data. I hope anyone can help me. > I have register an application on twitter and have get an Token_key > and token_secret after send a request to a...@twitter.com. > > > I read the documentation on http://dev.twitter.com/pages/xauth. > > Now I have a consumer-key, consumer_secret, token_key and > token_secret. > In the documentation there is a parameter who names "oauth_nonce". > Where can I get a key for this parameter. > > How should the password be transferred. Must it be encrypted? With a > particular procedure? (HMAC) > > When are token and seccret_token in use? > > > I using ActionScript 3.0. When I send a URLRequest with the example > from the documentation I will get an error. (Stream-Error). > > The following is a code example with the content from twitter > documentation: > > var url:String = "POST&https%3A%2F%2Fapi.twitter.com%2Foauth > %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw > %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth > %26x_auth_password%3D%2525%2526123%2521aZ%252B > %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant"; > > var request:URLRequest = new URLRequest(url2); > var loader:URLLoader = new URLLoader(); > loader.addEventListener(Event.COMPLETE, onUrlComplete); > loader.addEventListener(IOErrorEvent.IO_ERROR, onError); > loader.load(request); > > > I am grateful for any help > > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] get starting with xAuth for TwitterAPI
Hello everyone, I have any problems to develop my desktop-Application with an own Twitter Client. In my client to the user have the option to enter their user data. I hope anyone can help me. I have register an application on twitter and have get an Token_key and token_secret after send a request to a...@twitter.com. I read the documentation on http://dev.twitter.com/pages/xauth. Now I have a consumer-key, consumer_secret, token_key and token_secret. In the documentation there is a parameter who names "oauth_nonce". Where can I get a key for this parameter. How should the password be transferred. Must it be encrypted? With a particular procedure? (HMAC) When are token and seccret_token in use? I using ActionScript 3.0. When I send a URLRequest with the example from the documentation I will get an error. (Stream-Error). The following is a code example with the content from twitter documentation: var url:String = "POST&https%3A%2F%2Fapi.twitter.com%2Foauth %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth %26x_auth_password%3D%2525%2526123%2521aZ%252B %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant"; var request:URLRequest = new URLRequest(url2); var loader:URLLoader = new URLLoader(); loader.addEventListener(Event.COMPLETE, onUrlComplete); loader.addEventListener(IOErrorEvent.IO_ERROR, onError); loader.load(request); I am grateful for any help -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] how to convert basic auth to oauth
Hi Goraksha, There are probably a few developers here familiar with the AIR platform who can offer you some tips. I am aware that a number of developers have worked with the AS3 OAuth library here: http://code.google.com/p/oauth-as3/ You may find our introduction to the conversion process guide helpful: http://dev.twitter.com/pages/basic_to_oauth As for "the how" to convert: it's different for each application. Some applications are built in such a way that all API operations are handled by a request handler that can simply be augmented with OAuth. Other application designs can be significantly more difficult to convert. Taylor On Tue, Sep 14, 2010 at 4:00 AM, Goraksha Shinde wrote: > how to convert basic auth to oauth. I m using adobe AIR > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] twitter relationship
Hi All, I want to represent the relationship seen in twitter into the database. For eg : user1 is following user2, user3, user 4, user 5 and user6. But user5 and user6 are following user1 in turn. How would design the database to represent this relationship. Any ideas? thanks ashy -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Missing entities in REST
Hi Everyone, We're still investigating this issue -- it is not happening consistently across the board and has been difficult to track down. If you're *never* getting entities when requesting timelines, and you're including include_entities=true then please leave your member id here for additional investigation. Hope to have this fixed soon. Thanks, Taylor On Tue, Sep 14, 2010 at 6:20 AM, FearMediocrity wrote: > I don't think your doing anything wrong. include_entities hasn't > worked for me since late last week. @twitterapi mentioned a problem, > but then nothing since. > > Can we have an update please? > > On Sep 13, 7:16 pm, Jesse wrote: > > Hi, I'm trying to view my last tweet, but I can't seem to be able to > > see the Tweet Entities. > > > > Here is what I'm trying to view: > http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=(reda... > > > > But I don't see the "entities" element. > > > > Any help would be appreciated > > Thanks > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Missing entities in REST
I don't think your doing anything wrong. include_entities hasn't worked for me since late last week. @twitterapi mentioned a problem, but then nothing since. Can we have an update please? On Sep 13, 7:16 pm, Jesse wrote: > Hi, I'm trying to view my last tweet, but I can't seem to be able to > see the Tweet Entities. > > Here is what I'm trying to > view:http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=(reda... > > But I don't see the "entities" element. > > Any help would be appreciated > Thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Tweet Button counter url encoding
Hi
If I use a tweet button on a site with an url including a "+" sign,
the counter is not working (always displays 0).
It only works when I use the data-counturl parameter with the encoded
url ("+" encoded to "%2B").
But then, when i click the counter button, the search fails because
the "%" sign is encoded to "%25".
How is the tweet button supposed to work with urls including a "+"
sign?
Thank you in advance for your help
Cheers
Remo
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Help
hey i want to know how can i use OAuth Library with J2me application as i used Basic Auth but it's no longer be used and i used library Twitter_api_Me but it's also didn't work.so,what can i do??? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] how to convert basic auth to oauth
how to convert basic auth to oauth. I m using adobe AIR -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] How to use TwitterME on Blackberry....
Hello,
I am new with twitterme api and i am making an application on
blackberry which will post the articles on the twitter.
i registered my application with the twitter and get the token and
keys.
what i want in my application that whenever user provide there
credentials than i want to post one article on twitter. right now i m
providing the token like :
Token token = new Token("49990287-
c8KzOReuyZwMxSXr33R884wCpPAFWKYnsQVFgyWFZUw",
"KR8B9q92dxcdzGcNIugYYg645knu6b9HSR6vsh0lth0jE4");
these parameters i m putting hard coded
how i can get these parameters dynamically according to the user
credentials.
whenever i m running the below code than its posting on my twitter.
but i want that who ever will use my applcation provide the username/
pwd of twitter and than post article.
do u have any sample code which runs finely on blackberry and posting
on twitter according to the username/pwd.
sometimes i m getting the LimitExceedException.
My Code :
MainScreen screen = new MainScreen();
//Token token = new Token("token_access", "token_secret");
Token token = new Token("49990287-
c8KzOReuyZwMxSXr33R4wCpPAFWKYnsQVFgyWFZUw",
"KR8B9q92dxcdzGcNIugYYgknu6b9HSR6vsh0lth0jE4");
XAuthSigner xc=new
XAuthSigner("RbMzin97EOIe47kTiX3qpA","qn2vhn4xvErTx9qGw95sRPMcemFQUejw87g1lqGNYk");
xc.sign(new HttpRequest("http://api.twitter.com";), token);
Credential c = new Credential("zahidalinaqvi",
"RbMzin97EOIe47kTiX3qpA",
"qn2vhn4xvErTx9qGw95sRPMcemFQUejw87g1lqGNYk", token);
UserAccountManager m = UserAccountManager.getInstance(c);
try {
if (m.verifyCredential()) {
//GeoLocation loc = new GeoLocation("+37.5", "+26.7");
Tweet t = new Tweet("Cool! Geo-located tweet via Twitter
API ME.");
TweetER ter = TweetER.getInstance(m);
t = ter.post(t);
}
} catch (IOException e) {
System.out.println(e.getMessage());
e.printStackTrace();
} catch (LimitExceededException e) {
System.out.println(e.getMessage());
e.printStackTrace();
}
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Request Token Failure
Ah, ok. The header allows you to make one (1) call to Twitter, usually the verify_credentials.json page. This allows you to verify that the user has a Twitter account (and even get some information about the user), but it will not allow you to send messages etc. OAuth Echo is nothing more than a safe way to tell a service who the user is. Tom On 9/14/10 2:12 AM, sdenike wrote: > Hey Tom, > > I think I am falling into this pitfall myself. I don't have the users > information only the information that the iPhone twitter app sends me > for posting an image on a custom end point. With that header > information they send should be enough to send back to twitter to get > the user information? Or am I not understanding the process of doing > this? > > Thanks, > Shelby > > On Sep 10, 4:18 pm, Tom van der Woerdt wrote: >> You don't need request_token for Echo - unless you don't have the user's >> credentials yet, but in that case you aren't using OAuth Echo. >> >> Tom >> >> On 9/11/10 1:13 AM, AS_Drone wrote: >> >> >> >>> We have been trying to implement the OAuth Echo method, but cannot get >>> a request-token. It returns with "Failed to validate oauth signature >>> and token". >> >>> Below is our Post data. Our signature aligns with data on the API >>> document. Any thoughts as to why we fail to oauth signature? >> >>> Post data: >> >>> Request Header: >>> POST /oauth/request_token HTTP/1.1 >>> Content-Type: application/x-www-form-urlencoded >>> Authorization: >>> OAuth oauth_nonce="QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk", >>> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1272323042", >>> oauth_consumer_key="XX", >>> oauth_signature="Sr%2FKoecPb7D%2FnZNxt4qoM517Xjs%3D", >>> oauth_version="1.0" >>> Host: api.twitter.com >>> Content-Length: 0 >>> Connection: Keep-Alive >>> Cache-Control: no-cache >>> Cookie: k=12.22.61.130.1283734903045073; guest_id=128373490305755705; >>> __utma=43838368.1906297211.1283734907.1283734907.1283762670.2; >>> __utmz=43838368.1283734907.1.1.utmcsr=(direct)|utmccn=(direct)| >>> utmcmd=(n >>> one); __utmv=43838368.lang%3A%20en; __qca=P0-1782216308-1283735015637; >>> __utmb=43838368.3.10.1283762670 >>> Response Header: >>> HTTP/1.1 401 Unauthorized >>> Date: Mon, 06 Sep 2010 09:13:15 GMT >>> Server: hi >>> Status: 401 Unauthorized >>> X-Transaction: 1283764395-39211-63478 >>> Last-Modified: Mon, 06 Sep 2010 09:13:15 GMT >>> X-Runtime: 0.00573 >>> Content-Type: text/html; charset=utf-8 >>> Content-Length: 44 >>> Pragma: no-cache >>> X-Revision: DEV >>> Expires: Tue, 31 Mar 1981 05:00:00 GMT >>> Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, >>> post-check=0 >>> Set-Cookie: >>> _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCKEfUuYqAToHaWQiJWVhY2RjNDQ3NGNmMm >>> Mw%250ANjUwYWIzMGE3OWE4NDNlZTM3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy >>> %250A >>> OjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- >>> c7925282fe8f92e14b1a250c09ddff >>> e386a925be; domain=.twitter.com; path=/ >>> Vary: Accept-Encoding >>> Connection: close >>> Failed to validate oauth signature and token > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] PHP, Curl an OAuth Echo errors
I don't have an example, but you should use the X-Auth-Service-Provider
header for the URL and X-Verify-Credentials-Authorization for the
Authorization: header. If you use these, it should be fine.
Tom
On 9/14/10 2:03 AM, sdenike wrote:
> I have been trying for weeks here to get this going and cant seem to
> figure this out. I am trying to create a simple PHP/MySQL image
> uploader much like that of twitpic, yfrog etc etc to host my images on
> my own server. I am using the iPhone twitter app and have created a
> custom end point on my server, it handles the uploads fine. After
> shooting some emails back with twitter support I was told to look into
> the twitter oauth echo command to get such information like username
> etc etc from that tweet. To do so my understanding is that the iPhone
> twitter app sends header information to my script. my script should
> then take that header information as well as my consumer key and send
> that request back to twitter.
>
> That header that I create should include:
> X-Auth-Service-Provider:
> https://api.twitter.com/1/account/verify_credentials.json
> X-Verify-Credentials-Authorization OAuth oauth_consumer_key="...",
> oauth_token="...", oauth_signature_method="...",
> oauth_signature="...", oauth_timestamp="...", oauth_nonce="...",
> oauth_version="..."
>
> I am sending all this information back with curl in my php script and
> keep getting the following sent back to me
> {"request":"/1/account/verify_credentials.json","error":"Could not
> authenticate you."}
>
> Does anyone have a working example as I am not finding any PHP code
> that clearly outlines this whole statement, I cant imagine it being
> that hard thats why its bothering me that it has taken this long to
> figure out.
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Seeing duplicate Twitter User ID's under the same Username in our DB
Another thought. Are you feeding your DB with "normal" API endpoints and the "search" API endpoint? The search API returns different user_ids. http://dev.twitter.com/doc/get/search http://code.google.com/p/twitter-api/issues/detail?id=214 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
