Delicious linked with Yahoo account

[GoogleCodeExporter]

If your delicious account is linked with you Yahoo account, is there any
way to use it?

Original issue reported on code.google.com by bramhubb...@gmail.com on 30 Apr 2010 at 8:22

[GoogleCodeExporter]

QSB does not seem to work with new delicious users nor users who link their 
delicious and yahoo accounts. I tried entering my yahoo account info as well as 
variations of my username without the @yahoo.com, but to no avail. There is 
another login page one must visit in order to login using one's yahoo ID 
<http://tinyurl.com/3yodngm> one would think after 5 years that Yahoo/Delicious 
would figured something more unified (Yahoo bought Delicious in 2005) :(

Original comment by iotaio...@gmail.com on 28 Aug 2010 at 3:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have an updated version that seems to work for me - would anyone else like to 
give it a shot and see how it goes?

There is a new account type (Delicous Yahoo), and instead of entering your 
password you have to visit a Yahoo page to get a code that you then plug into 
QSB.

If this works for other folks I'll push up the updated code.

Original comment by npa...@gmail.com on 17 Sep 2010 at 1:50

Attachments:

• QSB-Delicious-Yahoo-OAuth-preview.zip

[GoogleCodeExporter]

Nathan,

Thanks so much.  I installed the new plugin last night and have been using it 
for about twelve hours now.  It's working perfectly.

Original comment by bramhubb...@gmail.com on 17 Sep 2010 at 2:19

[GoogleCodeExporter]

Thanks Nathan,
Things seem to be working well. Gotta do due diligence though and ask about 
privacy issues. The PIN page lists two items that will be shared:

(1) "Allow sharing of your Yahoo! profile and connections info with QSB 
Delicious plugin."
(2) "Allow QSB Delicious plugin to share information with Yahoo!"

This brings up a several questions:
(1) What scope of information does the plugin see at Yahoo? Does it just see 
Delicious bookmark or does it also look at profiles, connections, email, etc.?

(2) What scope of information does Yahoo pull from the plugin/QSB? Does Yahoo 
have access to other local QSB information like address book data, etc. 

(3) How do you "unshare" this info if you want to stop using the Delicious 
plugin. One could just delete the plugin, but it would be nice to know how to 
close up the access door left on the Yahoo side of things.

(4) This is the first I've heard of Yahoo sharing info with a third party with 
a PIN number. Where can users find out more about this and the above questions? 
Is there a reference on Yahoo?

Original comment by iotaio...@gmail.com on 17 Sep 2010 at 4:45

[GoogleCodeExporter]

Good questions - 

1) The QSB plugin only gets access to your Delicious bookmarks.  I'm attaching 
a screenshot of the prompt I get from Yahoo when I use the plugin.  When I 
registered the plugin with Yahoo I had to select the access level it needed, 
and I only picked Delicious.  I think it is impossible to increase the scope of 
access without registering anew, which would cause any existing PINs to be 
invalidated.

2) The plugin authenticates with Yahoo and issues requests to Delicious, but it 
doesn't send any other info.  So I guess Yahoo would be able to tell you are 
using the plugin and when, but they would not get any other info.

3) The PIN is only good for the instance of QSB you are using - just the PIN by 
itself won't work in other apps, even QSB on another machine.  If I remember 
correctly, I also got an email from Yahoo confirming that I had allowed access 
that included a "Revoke access" link.

4) Yahoo is using a system called OAuth for authentication - this is designed 
so folks don't have to share their password with other application - instead it 
uses the revokable PIN/token.  It works a bit better for webapps where the PIN 
exchange happens behind the scenes - it is a bit clunky for desktop apps where 
you have to manually enter the PIN.  There is some developer focused info at 
http://developer.yahoo.com/oauth/ and http://oauth.net/about/ seems to have a 
bit more general purpose info.

Original comment by npa...@gmail.com on 18 Sep 2010 at 2:47

Attachments:

• yahoo_screenshot.png

[GoogleCodeExporter]

Nathan,
Thanks for explaining.

@3) I verified that this e-mail did come and does include a revoke link. I 
poked around my Yahoo account settings and couldn't find any reference to QSB, 
so thus far this may be the only way to disconnect the two.

@4) Thanks for the additional info

Original comment by iotaio...@gmail.com on 18 Sep 2010 at 4:17

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

In other news . . .
QSB recently began throwing an error message regarding the Delicious plugin 
saying that "fetch" has failed for my account. Since then I can no longer 
access Delicious bookmarks through QSB. I clicked the "update" button in my 
account settings but behavior remans the same. I attached a screenshot of the 
error message.

Original comment by iotaio...@gmail.com on 18 Sep 2010 at 4:28

Attachments:

• [QSB Delicious Yahoo Fail.png](https://storage.googleapis.com/google-code-attachments/qsb-mac-plugins/issue-5/comment-9/QSB Delicious Yahoo Fail.png)

[GoogleCodeExporter]

I'll check it out, I think I can reproduce a similar issue locally.  Out of 
curiosity, did this start happening after QSB was shut down for a while?

Original comment by npa...@gmail.com on 19 Sep 2010 at 8:37

[GoogleCodeExporter]

Hmm . . . I think I remember that it stopped working the day after I installed 
it. In between the initial working install and the errors I likely turned of my 
computer overnight.

Original comment by iotaio...@gmail.com on 20 Sep 2010 at 8:21

[GoogleCodeExporter]

I think I tracked this down to a bug in how the oauth library I was using was 
persisting the expiration time for its oauth access token.  Long story short, 
I'm attaching an updated version that looks promising for me.

Original comment by npa...@gmail.com on 22 Sep 2010 at 2:15

Attachments:

• QSB-Delicious-Yahoo-OAuth-preview-2.zip

[GoogleCodeExporter]

Fixed in http://code.google.com/p/qsb-mac-plugins/source/detail?r=34

Original comment by npa...@gmail.com on 26 Sep 2010 at 10:43

• Changed state: Fixed

[GoogleCodeExporter]

Been testing the second update for a couple of days through logins/outs and 
restarts. Things seem to work well thus far!

Original comment by iotaio...@gmail.com on 27 Sep 2010 at 2:57