<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: registration</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/registration.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-12-15T20:35:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>Instapaper requiring email and passwords for new accounts</title><link href="https://simonwillison.net/2010/Dec/15/instapaper/#atom-tag" rel="alternate"/><published>2010-12-15T20:35:00+00:00</published><updated>2010-12-15T20:35:00+00:00</updated><id>https://simonwillison.net/2010/Dec/15/instapaper/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.instapaper.com/post/2318776738"&gt;Instapaper requiring email and passwords for new accounts&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Instapaper are changing from their novel “enter a username or email address, only enter a password if you really want one” registration scheme to a more traditional email and password required model. Messing with registration forms is a risky business—in this case, the non-obvious support issues that resulted were a net negative.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/forms"&gt;forms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/instapaper"&gt;instapaper&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/registration"&gt;registration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/usability"&gt;usability&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recovered"&gt;recovered&lt;/a&gt;&lt;/p&gt;



</summary><category term="forms"/><category term="instapaper"/><category term="registration"/><category term="usability"/><category term="recovered"/></entry><entry><title>Stack Overflow Blog: OpenID, One Year Later</title><link href="https://simonwillison.net/2010/Apr/14/openid/#atom-tag" rel="alternate"/><published>2010-04-14T20:46:02+00:00</published><updated>2010-04-14T20:46:02+00:00</updated><id>https://simonwillison.net/2010/Apr/14/openid/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.stackoverflow.com/2010/04/openid-one-year-later/"&gt;Stack Overflow Blog: OpenID, One Year Later&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Google’s support is a huge deal—61% of Stack Overflow accounts use Google. Google’s implementation of directed identity has caused problems though, since Google provide a different OpenID for each domain making it hard for Stack Overflow, Server Fault and Super User to correlate accounts. Their solution is to require a (verified) e-mail address from Google OpenID users using sreg and use that as a key for the accounts.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/directedidentity"&gt;directedidentity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/email"&gt;email&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/login"&gt;login&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/registration"&gt;registration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sreg"&gt;sreg&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/stackoverflow"&gt;stackoverflow&lt;/a&gt;&lt;/p&gt;



</summary><category term="directedidentity"/><category term="email"/><category term="google"/><category term="login"/><category term="openid"/><category term="registration"/><category term="sreg"/><category term="stackoverflow"/></entry><entry><title>Quoting Bruce Tognazzini</title><link href="https://simonwillison.net/2009/Nov/5/tog/#atom-tag" rel="alternate"/><published>2009-11-05T19:22:15+00:00</published><updated>2009-11-05T19:22:15+00:00</updated><id>https://simonwillison.net/2009/Nov/5/tog/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://www.asktog.com/columns/081Registration.html"&gt;&lt;p&gt;If you are demanding registration before checkout, you need to cease this practice immediately. It is costing you a fortune.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.asktog.com/columns/081Registration.html"&gt;Bruce Tognazzini&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/bruce-tognazzini"&gt;bruce-tognazzini&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/information-architecture"&gt;information-architecture&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/login"&gt;login&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/registration"&gt;registration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/signup"&gt;signup&lt;/a&gt;&lt;/p&gt;



</summary><category term="bruce-tognazzini"/><category term="information-architecture"/><category term="login"/><category term="registration"/><category term="signup"/></entry><entry><title>Want Proof OpenID Can Succeed? Just Scroll Down</title><link href="https://simonwillison.net/2009/Jan/16/aargh/#atom-tag" rel="alternate"/><published>2009-01-16T12:16:03+00:00</published><updated>2009-01-16T12:16:03+00:00</updated><id>https://simonwillison.net/2009/Jan/16/aargh/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.wired.com/business/2009/01/want-proof-open.html"&gt;Want Proof OpenID Can Succeed? Just Scroll Down&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
“It’s easier for blogs, which don’t need a lot of demographic information about a user, to let people jump in and start participating socially without filling out a registration form.” Aargh. Repeat after me: supporting OpenID does not mean you can’t require additional registration details through a signup form.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/registration"&gt;registration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/wired"&gt;wired&lt;/a&gt;&lt;/p&gt;



</summary><category term="openid"/><category term="registration"/><category term="wired"/></entry><entry><title>8 More Design Mistakes with Account Sign-in</title><link href="https://simonwillison.net/2008/Jan/17/more/#atom-tag" rel="alternate"/><published>2008-01-17T16:35:38+00:00</published><updated>2008-01-17T16:35:38+00:00</updated><id>https://simonwillison.net/2008/Jan/17/more/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.uie.com/articles/account_design_mistakes_part2/"&gt;8 More Design Mistakes with Account Sign-in&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Second of a two part series by Jared Spool. I agree with all of them with the possible exception of #15 which advocates providing a non-email password recovery solution. Security “questions” are usually dreadfully insecure, and introduce the need to lock users out of their accounts after just a few tries.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://www.uie.com/articles/account_design_mistakes/"&gt;Account Sign-in: 8 Design Mistakes&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/design"&gt;design&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jared-spool"&gt;jared-spool&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/registration"&gt;registration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/signin"&gt;signin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/usability"&gt;usability&lt;/a&gt;&lt;/p&gt;



</summary><category term="design"/><category term="jared-spool"/><category term="registration"/><category term="security"/><category term="signin"/><category term="usability"/></entry></feed>