Comments for Wackylabs.net http://www.wackylabs.net Mostly code, sometimes something else, always slightly wacky. Thu, 02 Feb 2012 13:00:53 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on OAuth and Flickr – Part 2 by Sam http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-13316 Sam Thu, 02 Feb 2012 13:00:53 +0000 http://www.wackylabs.net/?p=301#comment-13316 No, that's probably the simplest. Obviously if you wrap the call to getPhotos in a function and pass in the page number and per page number then it shouldn't be too hard to do it either way really. No, that’s probably the simplest. Obviously if you wrap the call to getPhotos in a function and pass in the page number and per page number then it shouldn’t be too hard to do it either way really.

]]> Comment on OAuth and Flickr – Part 2 by John http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-13309 John Thu, 02 Feb 2012 12:04:07 +0000 http://www.wackylabs.net/?p=301#comment-13309 Ok Sam engaged brain.. Download all images and store the links in a collection. Show first 20. When a'Next page' button is clicked simply show the next 20...only make a fresh call once the limit...500 has been reached. Any other way of achieving the same thing ? Ok Sam engaged brain.. Download all images and store the links in a collection. Show first 20. When a’Next page’ button is clicked simply show the next 20…only make a fresh call once the limit…500 has been reached. Any other way of achieving the same thing ?

]]> Comment on OAuth and Flickr – Part 2 by John http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-13308 John Thu, 02 Feb 2012 11:32:19 +0000 http://www.wackylabs.net/?p=301#comment-13308 Hi Sam, I want to paginate images in groups of 20. When I call flickr.photosets.getPhotos I need to pass it a page number which will be created dynamically . Do I have to go through all the process of creating a list of parameters, and generate a new signature everytime I call for the next page ? Hi Sam,
I want to paginate images in groups of 20. When I call flickr.photosets.getPhotos I need to pass it a page number which will be created dynamically . Do I have to go through all the process of creating a list of parameters, and generate a new signature everytime I call for the next page ?

]]> Comment on OAuth and Flickr – Part 2 by John http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-12767 John Wed, 25 Jan 2012 08:33:22 +0000 http://www.wackylabs.net/?p=301#comment-12767 Sam, you are a gem... came in this morning and reread your blog. I noticed the phrase, 'As this is the first stage you have neither, so your token secret is simply an empty string.' Added the oauth_token_secret and voila, the expected string is returned. I guess I should create a blog to save others from the pain... Many thanks, you don't know how relieved I am :-). Sam, you are a gem… came in this morning and reread your blog. I noticed the phrase,

‘As this is the first stage you have neither, so your token secret is simply an empty string.’

Added the oauth_token_secret and voila, the expected string is returned.

I guess I should create a blog to save others from the pain…

Many thanks, you don’t know how relieved I am :-).

]]> Comment on OAuth and Flickr – Part 2 by Sam http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-12737 Sam Tue, 24 Jan 2012 16:56:17 +0000 http://www.wackylabs.net/?p=301#comment-12737 If you base string matches exactly the debug_sbs then you either have the signature secret wrong (consumer secret + "&" + request token secret) or you aren't adding the signature to the final URL correctly (not urlencoded perhaps?) If you base string matches exactly the debug_sbs then you either have the signature secret wrong (consumer secret + “&” + request token secret) or you aren’t adding the signature to the final URL correctly (not urlencoded perhaps?)

]]> Comment on OAuth and Flickr – Part 2 by John http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-12734 John Tue, 24 Jan 2012 16:21:51 +0000 http://www.wackylabs.net/?p=301#comment-12734 This feels like nailing jelly to a wall... Anyway I send the appropriate string: GET &http%3A%2F%2Fwww.flickr.com%2Fservices%2Foauth%2Faccess_token &oauth_consumer_key%3Dbe211209a5054354064bfec8fb0cada6 &oauth_nonce%3D35197928 &oauth_signature_method%3DHMAC-SHA1 &oauth_timestamp%3D1327421466 &oauth_token%3D72157629013334217-4a83d8a75d6764d1 &oauth_verifier%3D755-955-488 &oauth_version%3D1.0 This generates a signature of 6FDW75A0amJrpnlR+85GkmnmTCg= I get an error back of oauth_problem=signature_invalid&debug_sbs=GET&http%3A%2F%2Fwww.flickr.com%2Fservices%2Foauth%2Faccess_token&oauth_consumer_key%3Dbe211209a5054354064bfec8fb0cada6%26oauth_nonce%3D35197928%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1327421466%26oauth_token%3D72157629013334217-4a83d8a75d6764d1%26oauth_verifier%3D755-955-488%26oauth_version%3D1.0 If I take the string returned in the error message and generate a signature from it I get EXACTLY the same signature...so why the error ? Unless they use a different encryption algorthm to the one used in the request token I'm loosing the will to live ... This feels like nailing jelly to a wall…
Anyway I send the appropriate string:
GET
&http%3A%2F%2Fwww.flickr.com%2Fservices%2Foauth%2Faccess_token
&oauth_consumer_key%3Dbe211209a5054354064bfec8fb0cada6
&oauth_nonce%3D35197928
&oauth_signature_method%3DHMAC-SHA1
&oauth_timestamp%3D1327421466
&oauth_token%3D72157629013334217-4a83d8a75d6764d1
&oauth_verifier%3D755-955-488
&oauth_version%3D1.0

This generates a signature of 6FDW75A0amJrpnlR+85GkmnmTCg=

I get an error back of

oauth_problem=signature_invalid&debug_sbs=GET&http%3A%2F%2Fwww.flickr.com%2Fservices%2Foauth%2Faccess_token&oauth_consumer_key%3Dbe211209a5054354064bfec8fb0cada6%26oauth_nonce%3D35197928%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1327421466%26oauth_token%3D72157629013334217-4a83d8a75d6764d1%26oauth_verifier%3D755-955-488%26oauth_version%3D1.0

If I take the string returned in the error message and generate a signature from it I get
EXACTLY the same signature…so why the error ? Unless they use a different encryption algorthm to the one used in the request token

I’m loosing the will to live …

]]> Comment on OAuth and Flickr – Part 2 by Sam http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-12729 Sam Tue, 24 Jan 2012 13:45:44 +0000 http://www.wackylabs.net/?p=301#comment-12729 The "perms" parameter is passed to the authorize URL, not to the access_token URL. http://www.flickr.com/services/oauth/authorize?oauth_token=72157626737672178-022bbd2f4c2f3432&perms=write But generally ALL parameter sent in the URL need to be added to the signature. The “perms” parameter is passed to the authorize URL, not to the access_token URL.

http://www.flickr.com/services/oauth/authorize?oauth_token=72157626737672178-022bbd2f4c2f3432&perms=write

But generally ALL parameter sent in the URL need to be added to the signature.

]]> Comment on OAuth and Flickr – Part 2 by John http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-12724 John Tue, 24 Jan 2012 09:41:39 +0000 http://www.wackylabs.net/?p=301#comment-12724 Hi Sam, Just read my previous post and if it appears unpolite/testy I apologize. You have been a great help in this. I've already tried adding the 'three-dash' number as the verifier but still no joy. Two further questions tho'. The verifier in the documentation is a 16 figure digit, so I was uncertain this actually was the oauth_verifier. Is the documentation incorrect ? Also, do I include the dashes? The documentation says I should use : http://www.flickr.com/services/oauth/access_token ?oauth_nonce=37026218 &oauth_timestamp=1305586309 &oauth_verifier=5d1b96a26b494074 &oauth_consumer_key=653e7a6ecc1d528c516cc8f92cf98611 &oauth_signature_method=HMAC-SHA1 &oauth_version=1.0 &oauth_token=72157626737672178-022bbd2f4c2f3432 &oauth_signature=UD9TGXzrvLIb0Ar5ynqvzatM58U%3D Here's my version: http://www.flickr.com/services/oauth/access_token &oauth_consumer_key=be211209a5054354064bfec8fb0cada6 &oauth_nonce=64631345 &oauth_signature_method=HMAC-SHA1 &oauth_timestamp=1327398023 &oauth_token=72157629009648509-80723eb271cd2bc6 &oauth_verifier=873-728-592 &oauth_version=1.0 &oauth_signature=41kdqcqpqhl2f2IM/kxKB//0Gr8= &perms=write The response is a message from Flickr stating 'You don't have permission to access this URL on this server' . Does the 'perms=write' have to be part of the signature ? Hi Sam, Just read my previous post and if it appears unpolite/testy I apologize. You have been a great help in this.
I’ve already tried adding the ‘three-dash’ number as the verifier but still no joy.
Two further questions tho’. The verifier in the documentation is a 16 figure digit, so I was uncertain this actually was the oauth_verifier. Is the documentation incorrect ?
Also, do I include the dashes?
The documentation says I should use :
http://www.flickr.com/services/oauth/access_token
?oauth_nonce=37026218
&oauth_timestamp=1305586309
&oauth_verifier=5d1b96a26b494074
&oauth_consumer_key=653e7a6ecc1d528c516cc8f92cf98611
&oauth_signature_method=HMAC-SHA1
&oauth_version=1.0
&oauth_token=72157626737672178-022bbd2f4c2f3432
&oauth_signature=UD9TGXzrvLIb0Ar5ynqvzatM58U%3D

Here’s my version:
http://www.flickr.com/services/oauth/access_token
&oauth_consumer_key=be211209a5054354064bfec8fb0cada6
&oauth_nonce=64631345
&oauth_signature_method=HMAC-SHA1
&oauth_timestamp=1327398023
&oauth_token=72157629009648509-80723eb271cd2bc6
&oauth_verifier=873-728-592
&oauth_version=1.0
&oauth_signature=41kdqcqpqhl2f2IM/kxKB//0Gr8=
&perms=write

The response is a message from Flickr stating ‘You don’t have permission to access this URL on this server’ .

Does the ‘perms=write’ have to be part of the signature ?

]]> Comment on OAuth and Flickr – Part 2 by Sam http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-12689 Sam Mon, 23 Jan 2012 16:31:39 +0000 http://www.wackylabs.net/?p=301#comment-12689 Once you have the number with three-dashes that is the oauth_verifier. You then send that, along with the request token to the access_token URL. Once you have the number with three-dashes that is the oauth_verifier. You then send that, along with the request token to the access_token URL.

]]> Comment on OAuth and Flickr – Part 2 by John http://www.wackylabs.net/2011/12/oauth-and-flickr-part-2/#comment-12682 John Mon, 23 Jan 2012 14:09:11 +0000 http://www.wackylabs.net/?p=301#comment-12682 Hi, Finally managed to get the Request token from Flickr. I understand from the Flickr documentation that if I need to view private photos I now need to exchange the request token for an access token . I send to flickr http://www.flickr.com/services/oauth/authorize?oauth_token=... with all relevant request parameters. Flickr responds with the authorisation page and I click the authorise this app button. Flickr responds again by saying that I am authorised and displays three -dash- seperated numbers and asks that I add this to my app. The actual documentation doesn't mention this response instead it indicates I should expect a simple string ... ie . "Flickr returns a response similar to the following: fullname=Jamal%20Fanaian &oauth_token=72157626318069415-087bfc7b5816092c &oauth_token_secret=a202d1f853ec69de &user_nsid=21207597%40N07 &username=jamalfanaian" Have you come across this ? What is supposed to happen now ? Anybody ? Hi, Finally managed to get the Request token from Flickr. I understand from the Flickr documentation that if I need to view private photos I now need to exchange the request token for an access token . I send to flickr http://www.flickr.com/services/oauth/authorize?oauth_token=... with all relevant request parameters. Flickr responds with the authorisation page and I click the authorise this app button. Flickr responds again by saying that I am authorised and displays three -dash- seperated numbers and asks that I add this to my app. The actual documentation doesn’t mention this response instead it indicates I should expect a simple string … ie .
“Flickr returns a response similar to the following:

fullname=Jamal%20Fanaian
&oauth_token=72157626318069415-087bfc7b5816092c
&oauth_token_secret=a202d1f853ec69de
&user_nsid=21207597%40N07
&username=jamalfanaian”

Have you come across this ? What is supposed to happen now ? Anybody ?

]]>