<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: pete-prodoehl</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/pete-prodoehl.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-08-31T20:49:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>RasterWeb: Lanyrd</title><link href="https://simonwillison.net/2010/Aug/31/rasterweb/#atom-tag" rel="alternate"/><published>2010-08-31T20:49:00+00:00</published><updated>2010-08-31T20:49:00+00:00</updated><id>https://simonwillison.net/2010/Aug/31/rasterweb/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://rasterweb.net/raster/2010/08/31/lanyrd/"&gt;RasterWeb: Lanyrd&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Pete Prodoehl calls me out on Lanyrd’s integration with the Twitter auth API at the expense of OpenID. I’ve posted a comment with my justification—essentially, tying to Twitter’s ecosystem means I can actually implement the features I’ve been talking about building on top of OpenID for years, with far less engineering effort.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oauth"&gt;oauth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recovered"&gt;recovered&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/pete-prodoehl"&gt;pete-prodoehl&lt;/a&gt;&lt;/p&gt;



</summary><category term="identity"/><category term="oauth"/><category term="openid"/><category term="twitter"/><category term="recovered"/><category term="pete-prodoehl"/></entry></feed>