<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Mar 10, 2014, at 5:33 PM, Jon Buckley <<a href="mailto:jon@mozillafoundation.org">jon@mozillafoundation.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Almost all of the software we build our software on is community supported to some extent. If Mozilla decides to stop running Persona, we’ll get at least 6 months notice so I’m not concerned about a surprise shutdown notification.</div><div><br></div><div>The argument against using Persona has nearly always been “user experience sucks”. It uses popups, sometimes it uses a password you assign, sometimes you need to sign in to your yahoo or gmail account. And these pain points haven’t significantly changed in the past 1-2 years we’ve been using Persona.</div><div><br></div><div>However, this does need to be weighed against the costs of switching. Expanding on what William said:</div><div><br></div><div>* We would need to store our own passwords</div><div>* We would need to build password reset functionality. This would also be how you’d migrate your account from Persona to our own password</div><div>* We would need to build new sign in ui & backend functionality</div><div>* We would need to verify email addresses</div><div><br></div><div>And rather than my entire email be negative, here are some of the other opportunities Webmaker could look at if we decided to move away from Persona</div><div><br></div><div>* Maybe support Twitter or Facebook sign in?</div><div>* Support multiple sign ins for one account (ideal for shared group accounts, like @webmaker, @mozteach, or partners in the future)</div><div>* Implement Oauth 1.0a or 2.0 and allow anyone to write a website that uses Webmaker accounts</div></div></blockquote><div><br></div>Yup. I would add, to be provocative: support people with no email address but with phones. Those are going to be (strangely?) more common for us both in badge scenarios, in developing world scenarios, and in marginalized population scenarios.</div><div><br></div><div>My take is there’s no urgent need to do anything just because of the Persona announcement — but we should noodle on it, and maybe see if we can try different auth models in some scenarios so we can learn more about the impact (esp. on UX & conversion) of alternatives.</div><div><br></div><div>For example, as Appmaker has overlap but not 100% alignment w/ Webmaker audience, maybe it’d make sense to try (Persona+Facebook+Twitter) auth there, and use some A/B testing to see if it’s having a major or minor impact? Let’s learn from the quantitative analysis that Andrea did for fundraising for example. In that world, slight wording changes resulted in 10x changes in user behavior. </div><div><br></div><div>—da</div><div><br></div></body></html>