<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    >

<channel>
    <title>Webmonkey &#187; plaxo</title>
    <atom:link href="http://www.webmonkey.com/tag/plaxo/feed/" rel="self" type="application/rss+xml" />
    <link>http://www.webmonkey.com</link>
    <description>The Web Developer&#039;s Resource</description>
    <lastBuildDate>Mon, 06 May 2013 17:29:19 +0000</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>http://wordpress.org/?v=3.4.2</generator>
    
    <item>
        <title>Yahoo Improves Its OpenID Support</title>
        <link>http://www.webmonkey.com/2008/11/yahoo_improves_its_openid_support/</link>
        <comments>http://www.webmonkey.com/2008/11/yahoo_improves_its_openid_support/#comments</comments>
        <pubDate>Fri, 21 Nov 2008 00:46:20 +0000</pubDate>

                <dc:creator>Adam Duvander</dc:creator>

        <guid isPermaLink="false">http://www.webmonkey.com/blog/yahooimprovesitsopenidsupport</guid>
        		<category><![CDATA[Web Basics]]></category>
		<category><![CDATA[jyte]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[plaxo]]></category>
		<category><![CDATA[Yahoo]]></category>
        <description><![CDATA[Yahoo continues to make strides to improve its OpenID implementation. Thursday it announced limited testing for Simple Registration, which supplies profile data once a user logs in with their Yahoo OpenID. Currently it is only testing Plaxo and Jyte. The experience logging in with Jyte is remarkable. It only takes a few clicks and I&#8217;m [...]]]></description>

            <content:encoded><![CDATA[<p><!-- wpautop enabled -->Yahoo continues to make strides to improve its OpenID implementation. Thursday it announced <a href="http://developer.yahoo.net/blog/archives/2008/11/yahoo_openid_test.html">limited testing for Simple Registration</a>, which supplies profile data once a user logs in with their Yahoo OpenID. Currently it is only testing <a href="http://www.plaxo.com/">Plaxo</a> and <a href="http://jyte.com/">Jyte</a>.</p>
<p><img class="blogimg" src="http://howto.wired.com/mediawiki/images/Jyte-openid.png" alt="OpenID sign in screen at Jyte" class="full" /></p>
<p>The experience logging in with Jyte is remarkable. It only takes a few clicks and I&#8217;m started using the site. It receives my preferred nickname from Yahoo, so I&#8217;m not even asked to fill in anything else.</p>
<p>Plaxo, on the other hand, requires a process that feels like signing up. Requiring info after signing in with OpenID makes moot one of the best things about OpenID for website owners. You can lower the barrier to entry for users by letting them use the site as soon as they arrive from their provider.</p>
<p>To that end, Simple Registration should be able to help solve the double signup issue, assuming sites treat the process like Jyte and not like Plaxo. Other OpenID providers have been sharing user&#8217;s profile information, with permission, for some time.</p>
<p>This part of OpenID is important, and it&#8217;s good to see one of the big boys on board. Still, it&#8217;ll be hard to say OpenID has really made it until I can <a href="http://www.webmonkey.com/blog/Dear_Open_ID:_You_Deserve_Better"><strong>sign on</strong> to Yahoo with any OpenID</a>.</p>
<p><strong>See also:</strong></p>
<ul>
<li><a href="http://www.webmonkey.com/blog/OpenID_Is_HereDOT_Too_Bad_Users_Can_t_Figure_Out_How_It_Works">OpenID Is Here. Too Bad Users Can&#8217;t Figure Out How It Works</a></li>
<li><a href="http://www.webmonkey.com/blog/Yahoo_Users_Befuddled_by_OpenID">Yahoo Users Befuddled by OpenID</a></li>
<li><a href="http://www.webmonkey.com/blog/Yahoo_Users__You_ve_Got_OpenID">Yahoo Users, You&#8217;ve Got OpenID</a></li>
</ul>
<div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2008/11/yahoo_improves_its_openid_support/feed/</wfw:commentRss>
        <slash:comments>0</slash:comments>

        
    </item>
    
    <item>
        <title>Netflix API Gets Love From Plaxo</title>
        <link>http://www.webmonkey.com/2008/10/netflix_api_gets_love_from_plaxo/</link>
        <comments>http://www.webmonkey.com/2008/10/netflix_api_gets_love_from_plaxo/#comments</comments>
        <pubDate>Thu, 23 Oct 2008 19:01:02 +0000</pubDate>

                <dc:creator>Adam Duvander</dc:creator>

        <guid isPermaLink="false">http://www.webmonkey.com/blog/netflixapigetslovefromplaxo</guid>
        		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[netflix]]></category>
		<category><![CDATA[plaxo]]></category>
        <description><![CDATA[When Netflix released its API, I said the coolest thing was that it gave developers access to a database of movies and actors. It also uses OAuth to let third parties create applications that build off of a user&#8217;s account. Plaxo has done just that, by adding ratings integration into its Pulse social network. When [...]]]></description>

            <content:encoded><![CDATA[<p><!-- wpautop enabled --><img class="blogimg" src="http://howto.wired.com/mediawiki/images/Plaxo-netflix.png" style="border: 1px solid black;" />When <a href="http://www.webmonkey.com/blog/Netflix_API_Brings_Movie_Catalog_to_Your_App">Netflix released its API</a>, I said the coolest thing was that it gave developers access to a database of movies and actors. It also uses OAuth to let third parties create applications that build off of a user&#8217;s account.</p>
<p>Plaxo has done just that, by <a href="http://blog.plaxo.com/archives/2008/10/joseph_rated_ne.html">adding ratings integration</a> into its Pulse social network. When you add it to your Pulse account, you are taken to Netflix to login, so Plaxo doesn&#8217;t get your login details. Then you choose which of your Pulse contact groups you want to give access. You can just make the ratings public, but then we&#8217;ll know your affinity for Harold and Maude (and I totally get it).</p>
<p>The Plaxo team got this Netflix integration done <em>fast</em>, which Plaxo credits to the way Netflix created the API:</p>
<blockquote><p>&#8220;Netflix chose to build it with existing, open standards. Specifically, they&#8217;re using OAuth to let users grant Plaxo access to their non-public data, and they&#8217;re using protected ATOM feeds for the ratings (along with RESTful APIs for getting additional data). Since Plaxo already knows how to crawl ATOM feeds, and we already know how to take users through the OAuth flow, it was trivial for us for hook this all up.&#8221;</p></blockquote>
<p>This is good stuff from Plaxo, too, which has a bit of a reputation to get over. Now attempting to be known for openness, to many Plaxo is still seen as a spammer due to emails that made us update our friends&#8217; address books.</p>
<p>There are probably many who wouldn&#8217;t join Plaxo, let alone give it access to their Netflix queue, but for those willing to give them a shot, it looks like the sort of place where you&#8217;ll see fun new features sooner than later.</p>
<p><strong>See also:</strong></p>
<ul>
<li><a href="http://www.webmonkey.com/blog/Plaxo_To_Launch_Facebook_Killer">Plaxo To Launch Facebook Killer</a></li>
<li><a href="http://www.webmonkey.com/blog/Plaxo:_One_PIM_App_To_Rule_Them_AllDOT_MaybeDOT">Plaxo: One PIM App To Rule Them All. Maybe.</a></li>
<li><a href="http://www.webmonkey.com/blog/Netflix_API_Brings_Movie_Catalog_to_Your_App">Netflix API Brings Movie Catalog to Your App</a></li>
</ul>
<div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2008/10/netflix_api_gets_love_from_plaxo/feed/</wfw:commentRss>
        <slash:comments>0</slash:comments>

        
    </item>
    </channel>
</rss>
