DISQUS

Brendan O'Connor · 10 months ago

Good work so far; I'll look forward to when this becomes a more open flow, such that those of us who use non-Google OpenIDs and Google Email, for instance, can still use this nice flow.

On a slightly separate note, why is there no OpenID commenting option on this blog? :-)

pauljacobson · 10 months ago

I don't believe Disqus supports OpenID yet which is a little odd given that it supports Facebook Connect.

Joseph Smarr · 10 months ago

Ugh, they do support OpenID in the sense that you can sign up for Disqus using OpenID and then login to leave your comment via Disqus, but they don't make it easy to do from their widget, which drives me crazy. I've mentioned it before but it hasn't risen to the top of their stack, so please help me provide "vocal user feedback" that this is a desired feature! :D

pauljacobson · 10 months ago

Hi Joseph

I sent in a request via Identi.ca (for a change) and will keep reminding them. I have been pushing them to incorporate Creative Commons licensing support into Disqus so people can license their comments. I would like to be able to set a default CC license for comments posted on my sites in line with my terms of use.

On that note, what about CC license support in Pulse?

fredbascunana · 10 months ago

agreed and how strange !
I am looking forward to such improvement!
Disqus developers!! To you HEAR us please?

developdaly · 10 months ago

Uh oh, you left the images private.

therealmccrea · 10 months ago

Oops. The photos are now public. Sorry about that!

chris chabot · 10 months ago

color me impressed, this is very exciting stuff!

Ken Kennedy · 10 months ago

Nice, John. I like it. The fact that people are frequently already signed into Google is a bonus here, as being pre-authenticated avoids the potential phishing issue with delegated logins ("am I really being sent to Google/Yahoo/myopenid/etc.?) I always pre-login to myOpenID before I use OpenID logins, but that's pretty disruptive to the flow at times. This is nice and smooth if you're logged into Gmail; good idea.

Tom McCrea · 10 months ago

A good colaboration for sure. It should be a great timesaver for the Social "Tablehopping" we all do.

therealmccrea · 10 months ago

Agreed!

Chris · 10 months ago

This is really cool & exciting, the next big step is to allow the broader community to set-up similar connections with Google.

therealmccrea · 10 months ago

Absolutely. This is not about any particular pair-wise interop, but about all interops!

Chris · 10 months ago

Looks like in the Google Blog about this there are some libraries to test this out in other client implementations.

Olly S · 10 months ago

This is excellent. Glad to see the open stack coming together.

Marc Worrell · 10 months ago

That is interesting. We implemented the same strategy for the open community interface project at Mediamatic Lab. Here the flow is that people logon to a site using OpenID, whilst also approving an OAuth token at the provider. After that we do not use the Google contacts API but we do subscribe to the user's profile using XMPP. By subscribing, an Atom with the user's profile is pushed to the site and subsequent updates are pushed as well. The OAuth token is used to enable the user to update his profile, or add new contacts, whilst staying at the consuming site, enabling cross-site edits of his profile.

We think that adding XMPP publish&subscribe is essential for keeping data up to date and preventing continuous polling.

Open-CI is now live and connecting multiple social networks in the Netherlands.

See http://open-ci.nl/ for more information.

Mikko Lehto · 10 months ago

Sounds and seems great!

Should I already be able to import Google contacts to my existing Plaxo account?
Or is it possible only during new user registration?

Mark · 10 months ago

Yes it is possible: http://twurl.nl/hz3btv But it's a one-way sync only.

Mikko Lehto · 10 months ago

Step 4: "Enter a your Google username and password (click "Next" to continue). "

I was sort of hoping to not insert my Google password...

therealmccrea · 10 months ago

We do have Gmail import today, but not yet with the Oauth. We'll roll that out soon as out this experiment succeeds.

burnayev · 10 months ago

Do you have plans to use OAuth for Google sync point for existing Plaxo accounts?

pauljacobson · 10 months ago

I was about to ask that same question. I would like to have the benefit of this new thing in my existing account if possible.

Bertil · 10 months ago

Great!

Just one thing: not every body knows that Pulse is a Plaxo service, so you might want to explain what's the connexion between the two words to newcomers. You already have two services on one page, not connecting those two dots might be too confusing.

Plaxo management might think this is heresy, but a button:
"Please tell Hong that I'm not interested —
Or that I'd love to, but I'm mostly using that other webservice;
or that I only use Plaxo for professional use, and he is a booty call so he should be offended, but I'll connect on another service."
would be great. Better (well, simpler) would be an explanation that if you close the page, Hong won't get a notification you snubed him, but he might notice the lack of reply by himself.

I'd also prefer a light-grey round-cornered frame around "Or, use another e-mail. . ." because otherwise it feels little bit like those single-choice message box, with only one button: "All your data are belong to us. [OK]"

Chris · 10 months ago

Question: Do you see the hybrid OpenID + OAuth as the best method for implementing this or is it a stop gap until a new workflow is created?

Thank You.

Jerker Widmark · 10 months ago

In theSocialWeb TV episode 20, there was a similar thing presented with Plaxo and Yahoo, using extention to openID to carry user data back in the openID iteraction sequence. Isn't thsi just another variant of that, this time though "embedding" Oauth as extentions to the OpenID messages?
Thanks for great shows !

Joseph Smarr · 10 months ago

The Yahoo integration was also using an OpenID extension to share more user data during onboarding, but it was using the existing "simple registration extension" ("sreg") whereas with Google we're using an OAuth extension and then calling their API. Complicating matters further is we're also using the "Attribute Exchange" (AX) extension with Google to get some additional info, e.g. the user's validated e-mail address. AX is a generalized version of what sreg provides, and they're both complementary to providing an OAuth token, which involves more work but leads to greater flexibility in the data that can be shared. These are all different ways of basically doing the same thing, so over time things may sort themselves out more, but for now that's the way things are all working, and our general philosophy has been to just try and make progress along as many promising fronts as we can, so the market can sort out what ultimately works best. :)

Athar A. Khan · 10 months ago

John,

Thanks for working more closely with Google. I couldn't really keep things in order without using Google and Plaxo. Does this mean that a true bi-directional contacts sync (between Plaxo and Google) is coming soon?

-Athar.

ralfborchert · 4 months ago

Hi, it would be awesome if you could work with gigya.com and create a "plaxo-connect" API

best,
Ralf

Whoeverur · 3 months ago

What is this? Why do you do this? You do not even have a way to opt-out, or make it clear how you have our emails. Is this shady business? Rhetorical. PLEASE REMOVE the EMAIL I PUT BELOW. Thank You!! Otherwise, lawsuits will abide/abound...This is spamming..And the good ole' U.S has laws against this. Thank You!! And, Good Luck!!