14 ms·
What did Persona get right? Why did Persona fail to gain wide adoption?
- woah 13y agoI really hope it works out. So easy
- Osiris 13y agoA classic case of less is more (or better).
- gcb0 13y agonot really. the biggest problem was no adoption from larger sites, while most of them offer facebook login... quote: We looked at Facebook Connect as our main competitor, but we can't offer the same incentives (access to user data).
- patio11 13y agoThat quote is alarming to me, because it fundamentally misunderstands why companies choose to use Facebook Connect. Absolutely no B2C company in the Valley has ever decided to use Connect because it lets you slurp in demographic information. They do it because of a) a mostly mistaken belief that it increases conversion rate to a signup and b) a mostly accurate belief that after you get someone to Connect you're going to be much, much more successful at getting your content on their wall as a viral distribution mechanism.
- gcb0 13y agoyour second point is almost the same as the quote but worded differently. access to user data and/or easier access to their fb wall...
- octatone2 13y agoMost users have a facebook account, supporting a facebook oauth sigup/login flow means one less set of credentials the user has to remember. It simply reduces the barrier to entry into an app for the average user.
- agilebyte 13y agoHuh, I never saw them as competing with Facebook Connect. I use Persona as a way to login to our blogs admin, and it is just so easy to have an array of white listed email addresses in the config and not have to worry about the rest. With Facebook Connect you have to have a Facebook account, with Persona you do not care.
- aragot 13y agoThere are plenty of situations when using Facebook Connect is inappropriate. If I wanted to look professional, I wouldn't associate myself with fb (Is that a personal perception or is it shared among the public that Fb is intensely a consumer platform?). If I wanted to have control over my own assets, including the userbase, I wouldn't use fb. Even if you look into consumer market, Snapchat went out of their way to _avoid_ Facebook Connect. So I think Mozilla could have done more marketing against Facebook Connect.
- kybernetikos 13y agoI don't see why you shouldn't let people add a small amount of personal data to their personas at their own option. I'd like to see public key/profile picture/blog url.
- patio11 13y agoIn the spirit of helping out my fellow developers at Mozilla, who I respect a lot, I would like to add one additional cause of failure, in the knowledge that it is a bit bracing but is really important and should inform project selection in the future: Persona fails to solve a problem which either end-users or people who operate websites for profit actually have.
- _delirium 13y agoPerhaps not enough people who operate websites for profit, but there are a reasonable number of us working on PaaS/SaaS products where using Facebook Connect is out of the question because of data-protection laws, which does leave a pain-point around user management. The current gold standard is "roll your own", but Persona is an interesting alternative. Why aren't people using it even in that sphere? One issue is that it's precisely when you need to take advantage of the federated aspect that the win on up-front effort is weakened. By the time you're setting up your own in-house Persona server rather than using Mozilla's, you're probably at the point where it's less effort to just use some crappy off-the-shelf account-management system that comes as a CMS plugin. This might be counteracted if using Persona improved conversion, but that's a chicken-and-egg problem as long as users don't recognize Persona. The other bit imo is that the security downsides of roll-your-own are a bit of an unpriced externality. If you have a password breach, it's bad PR for a bit, but legal liability around it is relatively toothless: data-protection laws seem not to care about mere incompetence in keeping users' data private. Make your users pick passwords with at least 2 digits and 2 non-digit characters and you've "done your part". So rolling your own crappy login system doesn't have as big a downside for you the provider as for your users. The users, for their part, are oblivious to the risk before the fact, and lack serious legal recourse after the fact, so they'll go along with your crappy in-house signup system, and shoulder the risk.
- StavrosK 13y agoAre you talking about a login mechanism to a site, or about authenticating yourself to other sites? I don't understand what "roll your own" is referring to.
- 13y ago
- cryptolect 13y agoIt failed to get wider adoption because the average consumer doesn't see the problem they solve as a problem. There's a far small potential userbase who recognize the privacy benefits of the Persona system.
- return0 13y agoI don't think privacy is the main problem they solve, but the user's need to skip the tedious signups all the time.
- nzp 13y agoWhich they can already do with accounts they most likely already have: Facebook, Google, Twitter, LinkedIN any OpenID provider... So the only potential benefit of Persona is the privacy, and if a user doesn't care about that then it's just another account you have to worry about (i.e. the very problem it tries to solve). As it stands, Persona's problem is that it just reinvents the wheel with slightly different spokes when people already have wheels that they consider good enough.
- rpwverheij 13y ago"We made Persona a user-visible brand but that competed with a site's own brand." This would indeed have been the main reason for me not to use it. I have not been in a position to implement login functionalities recently, but when I do, I will still strongly consider Persona, and even more so if the Persona brand can become almost invisible as it says in the post.
- aaronsnoswell 13y agoWhat was Persona?
- deleted 13y ago[deleted]
- inopinatus 13y agoI rejected Persona out of hand at the time[1] for the design gaffe of using HTTPS at the root of a corporate website[2] (worse, via a DNS apex A record[3]) as the identity-provider infrastructure discovery mechanism. I haven't reviewed the protocol since maybe a year ago, but my view then was that system administrators within enterprises could only adopt Persona as identity providers if federated discovery was via records in the DNS, as the lords of protocol design intended, preferably SRV records at that. Not the only barrier to adoption, perhaps, but definitely one of them. No-one substantial was likely going to use anything but the Fallback server, and there is no commercial reason to choose that rather than social-media-SSO where you'll enjoy the marketing bonus of reaching their outbound feed. [1] https://news.ycombinator.com/item?id=5447097 https://news.ycombinator.com/item?id=5447097 [2] a !! blunder because marketing won't let you in many organisations. also because most sites won't even have a port 443 https listener, let alone a valid certificate, on the apex A record. all this indicative of lack of real-world experience by the designers. [3] a !!!! blunder see e.g. https://devcenter.heroku.com/articles/apex-domains https://devcenter.heroku.com/articles/apex-domains
- StavrosK 13y agoDNS is a good option, but you'd need DNSSEC, which not many people have.
- inopinatus 13y agoPersona is already using DNS for resolution, just very badly. I just went looking. There's a whole thread over here: https://github.com/mozilla/persona/issues/1523 https://github.com/mozilla/persona/issues/1523 & https://groups.google.com/forum/#!msg/mozilla.dev.identity/dP44TDzBnhI/3MijAKI1oR8J https://groups.google.com/forum/#!msg/mozilla.dev.identity/d... where the developers effectively shitcanned the idea of using SRV records because they fear DNSSEC. Hilariously ignoring the huge elephant in the room viz. that they were already relying on DNS to resolve endpoints. The verification, the trust, comes from TLS with a valid cert, and that doesn't change, however you located the https listener in the first place. Even better, though, if you did use DNSSEC you can validate a self-signed cert via DANE/TLSA rather than having to buy one from CrappyCA. And that would make the ISPs very happy.
- buro9 13y agoWe use Persona at Microcosm, so you can see it in action on sites such as http://forum.espruino.com/ http://forum.espruino.com/ and http://forum.islington.cc/ http://forum.islington.cc/ , just click sign-in and you're there. For our use-case Persona is great. I've personally built the "web account" solution several times for different clients and I did not want to build it again. Persona is the lightest drop-in and easiest to implement solution you can imagine, and it works extremely well. We've had a couple of issues, but nothing of significance. Mostly these have been us doing things unexpected, i.e. pre-loading user accounts obtained face-to-face and the case of the user@ part of the email address differing from the Persona provided email address. I personally also wish that persona.js is added to CDNJS to increase the speed by which it's served. What we found through asking, was that people feel very protective of their Google, Twitter, and Facebook accounts. They will sign in with them, but there's a wariness of doing so as they do not want to be spammed, have things posted on their behalf, etc. These fears mostly apply when people first arrive on one of our sites. We wanted a lower friction to that initial sign-in, and we feel that Persona gives us this. We also found that on interest-based communities there is a reticence to associate real-identity to the nerdiest of their interests. This meant that not using Facebook and Google is a good thing in our scenario. One of the things we like about Persona is the user experience. For our product, simplicity and ease are core goals. Persona helps rather than hinders on this front. We really like Persona and hope that it remains under active development for a long-time. We are not of the belief that it's failed, simply that it's a slow-burner and needs some marketing support.
- StavrosK 13y agoI 100% agree with all of this. I think Persona needs some native support in browsers/etc and will succeed. I find it the easiest login system to implement, bar none. I also wrote a post on how you can use it with disposable email addresses: http://www.stavros.io/posts/persona-accounts-disposable-email-addresses/ http://www.stavros.io/posts/persona-accounts-disposable-emai... If disposable email providers (mailinator, 33mail, etc) implement it, you will just be able to log in with your disposable email address everywhere. If the browser implements "remember which address I signed up to this site with", it will be the most transparent login system available.
- 13y ago
- return0 13y agoI was put off by the name. BrowserId was an OK name, but FirefoxId would be better, to leverage the good name of firefox in the user's mind.
- ChrisAntaki 13y agoDefinitely. Persona sounds too Personal.
- tommorris 13y agoIt's also confusing branding because Mozilla used to refer to browser branding as "personas".
- inopinatus 13y agoI'd totally be willing to trust a service called Impersona.
- AndrewDucker 13y agoExcept that it's not only functional in Firefox. It works in any browser.
- return0 13y agoUnlike 'mozilla' or 'persona', firefox is a household name. I think people would be willing to sign up for "firefox identity" to use around the web, and the persona project should capitalize on that. People use fb connect because of the combination of ease-of-use and trust. Persona has the ease-of-use but users don't recognize it as trustable. What is needed to push it further is a landing page to "create firefox identity" and a campaign to push it as "the nonprofit, safe authentication provider". Instead of trying to make the protocol completely transparent, it had better be promoted as a recognizable identity provider Couple that with spreading persona servers as far away from the NSA as possible and transparency that guarantees that data are not being logged by mozilla, and i can see "firefox connect" being a legitimate fbconnect and twitter-sign-in killer
- 13y ago
- maho 13y agoI never even knew what it was, because I confused Mozilla Persona (some authentication thing) with Firefox Personas (themes for Firefox - note the s).
- dcc1 13y agoI use it on several sites, and it works quite fine, The problem is with users they are so used to registering with "omgonies/1234568" into sites that federated login is weird to them
- anonymfus 13y agoThe right way to solve problem of disposable logins on your site is to support anonymous access for everything that registered users can do.
- muyuu 13y agoLack of promotion. Most people don't know what is it. Possibly this will improve over time. Also, why are you guys talking about Persona in past tense? sounds like you're dropping the project.
- StavrosK 13y agoI agree with the first part, and was also puzzled by the second part. Are you guys dropping it? I don't think there was enough of an effort made to consider it a failure, creating a new login system for the web won't take three months.
- Pacabel 13y agoIf it were truly useful, it would have generated its own promotion. It'd be more like the early years of Firefox, where the benefits it provides are so overwhelming that the early adopters are very willing to spread the word and get others to use it. But Persona clearly isn't that useful to enough people. Even those who've known about it for a long time now just haven't found it practical enough to try to get others to use it.
- aragot 13y agoI have hard times explaining the added value of Persona over OpenID. It's just the privacy and even tech people don't see that as a point. So I searched on Google, and this probably didn't help Mozilla: http://security.stackexchange.com/questions/5323/what-are-the-downsides-of-browserid-persona-compared-to-openid-oauth-facebook http://security.stackexchange.com/questions/5323/what-are-th...
- RaphiePS 13y agoI think they're spot-on with the idea that it needs to be integrated into sites rather than appearing as a separately branded popup. I tried it out on a site I was building a couple months ago. Every time I had a non-"techie" user try it out, they got confused. What's this popup? What's Persona? What am I signing up for exactly? It was just bad UX. That said, I think there's a very real need for what they're offering. I don't want to store passwords myself, even if they're hashed. I also don't want to re-implement forgotten usernames, passwords, reset emails, etc. It's a bother, I'd rather focus on my app rather than a solved problem like this, and to be honest I don't quite trust myself enough to get it 100% right. So, I think it would be the best of both worlds to offer auth as an API rather than providing their own experience. As in, I could just call Persona.login("username", "password", ...) and get back an assertion. I really hope they go in this direction.
- sirn 13y agoUX is one major problem with Persona. I built a small site that used Persona a while back (without offering any other login choices) and most user can't figure out how to sign up. Facebook login as a separate brand works because user already knows and uses Facebook. This is completely opposite in Persona case. User don't already have Persona "account" and they don't understands why should they sign up for it. IMO, Persona should aim to replace classic login instead of social login, e.g. by making Persona nearly invisible to the user.
- yggdrasil 13y agoHeartily second the idea of Persona being re-rolled as classic login replacement, with emphasis on standardizing login best practices, such as password strength, password format disclosure, input naming that plays nicely with other password management systems, etc. The sheer amount of cruft and non-standardization involved with basic site login actively discourages user involvement. If Persona solved that unobtrusively, they would be adopted and evangelized all over the land.
- mgreg 13y ago
- onli 13y agoI really like Persona. I use it (with the browserid gem for sinatra) for a couple of my side projects, as the only login option. It works great when it works and developing without having to bother about password management is great, though I first had to get my head around how that concepts works, serverside, that I have to remember an email address of a user in the database to assign him special rights (example: admin of a blog). What I didn't like, though granted, some of that is not very universal: 1. I made a small user test with it, and all user failed to complete the login, iff the email was new to persona. Because then, the new account has to be activated by email, and the link in that email lead to the persona account management. All users were confused by that and asked for confimation what to do, when confronted with the email confirmation message, and all of them got stuck in the new tab with that account management and were unable to return to the registration page on its own. I understand that it is possible to change that link, though I didn't find that parameter at that time and marked it as an issue to fix later (A quick search just now showed nothing). And it might be a gem thing. Still, bothered me. 2. I would have loved a demo mode that works offline (maybe that exists?). Had spotty internet for a while and it was very bothersome to test the persona part of the project, as the registration/login worked only every 10th time, if at all. That was so cumbersome that I stopped working on it till I got a better connection. Which also means that a user with a bad connection won't have fun with persona, not resilient enough. 3. I don't like that the name was used for another FF-Project before (FF-designs, if I'm not mistaken) - if that confused me at first, it might confuse users. Have no better alternative though (maybe I would just brand it Email Login). 4. The browserid-gem for sinatra doesn't work with ruby > 1.9.3, and the maintainer does not fix the issue even though there is a working patch in a pull request. So instead of just having to specify the gem in my gemfile, I have to provide the link to the alternate github implementation. I hate that, that does not feel safe. I tried to look up how a gem might be replaced with another one and found nothing about how that (or the gem infrastructre in general, note that this was while having no really usable internet connection) work.
- enewc 13y agoWhat did it get right? It can be useful and it's backed by a solid brand. Why did Persona fail to gain wide adoption? For the most obvious reason: because nobody cares. People don't want to use something new unless there's a pressing reason. Trivial conveniences don't cut it.
- Aissen 13y agoAnother point. Not everything is web-based (I know it might be hard to believe at Mozilla), and the fact that you have to use javascript to access the API is also a limiting factor.
- sehr 13y agoThis is a service specifically for web based applications. Most, if not all users have JavaScript enabled. The ones savvy enough to turn it off, will also be able to turn it back on.
- jamesgeck0 13y agoWhen I first looked at Persona/BrowserID eons ago, there were non-web ways to use it. I remember some examples given that worked in a terminal or with an embedded device.
- jchrisa 13y agoI've been using it in my mobile apps and getting very little support. A single sign on that doesn't support native mobile apps is dead in the water.
- lukeh 13y agoWell, we did build a Persona SSP so you could use it with Outlook, Exchange, CIFS. The protocol spec is in draft-howard-gss-browserid. Very little interest though.
- muzlol 13y agoI've been waiting for a solution for non-browser use-cases before exploring Persona/browserid. I've never seen a hint of this drafts existence on the Persona website. In the presentations I've seen, Mozilla personnel have never mentioned this or have indicated that no solution is available. Maybe I've looked in the wrong places or have not been paying attention, but it seems to me like there's a communication gap here.
- 13y ago
- TazeTSchnitzel 13y agoThe session management Persona does is a pain. It's great for single-page apps and awful for traditional web apps.
- jessaustin 13y agoIt does seem inelegant that I can't seem to avoid having two sessions: Persona's and whatever I have for my site. I'm not sure how the two ought to be combined, or even if the Persona session is necessary. I guess maybe Persona can just confirm the email association whenever the site requires it and just stay out of the loop otherwise.
- belorn 13y agoWhen Persona was released, they split the FOSS crowd between OpenID and Persona adoption. Having two similar tools that solve the same problems (regardless of which one is better) did nothing beyond create two incompatible camps, each advocating for one while discouraging adoption of the other. I see it as a rather large blind spot of Mozilla to not recognize this. As an administrator, I would also like to complain about this behavior from a practical viewpoint. Spending first mindshare and time implementing OpenID to solve a real problem, Persona came like an unwanted alternative to a solved issue. Had they joined like an upgrade (i.e. backward compatible with OpenID), my reaction would to be an advocate rather than skeptic.
- StavrosK 13y agoWhen Persona was released, OpenID is already dead. I implemented OpenID on a few sites (I was an early proponent) and had nothing but trouble. Nobody could remember their OpenID URL, whereas everyone knows their email address.
- paulftw 13y agoIt is really great that they have guts to admit the failure. Though this confession is a bit overdue, I hope they've learned the lesson and some day will come back with a better solution. No doubt that the problem is really worth solving.
- usrusr 13y agoUsers are very much accustomed to accepting the security and privacy implications of conventional web logins. Persona promises to improve on that by introducing itself as a third party. However, users with a trace of security awareness will be skeptical of promises like that and will subconsciously do a simple equation in their heads: if everything else fails (the promised improvements), then more involved parties imply less privacy/security. Getting beyond that point requires at least a level of understanding that allows for a rough estimation on a scale between "totally bogus" and "this might actually work if done right".
- clarkevans 13y agoI simply don't understand this blog entry. I guess it's their official project resignation... OK. Even so, it seems misinformed about the adoption problems. Persona, to me, seems a truly lovely solution to a difficult problem. It was successful, just at the beginning of a hard adoption curve. What's missing is fully functional, advertised implementations of the Service Provider, that work with LDAP and ideally older Kerberos backends. What's missing is the native, built-in interface. What's also missing is a SLA... big players can't adopt it unless Mozilla says they are going to support it. What's missing in Persona is a promise to have the code security audited and get it passed federal agencies. What's missing is some grass-roots effort to get it into universities. What they list as failures aren’t exactly. So, there are some UI issues.. but those aren’t the problem. The Persona service was meant as transitional, till native implementations appeared. It's not going to adopt itself, they need a "Sales Engineer" full time working on adoption. Hell, they could even charge people for that sales engineer and many would pay for it. The alternative to Persona is Shibboleth/Kerberos, and Persona kicks it.
- Spearchucker 13y ago...with LDAP and ideally older Kerberos backends. If that's what I need I'd rather use WS-Federation or SAML. Both have been around for longer, and I consequently have a lot more faith in them. Sure, they're XML-based, but that's quite ok for what I'm getting.
- 616c 13y agoWith all due respect you probably do not work in an institution where you have to rely on SAML for day-to-day operations (I work in a uni, so Shibboleth). If you did, you would realize why SAML is lauded as a great solution, but in reality can be very fragile and needs to be rolled out all or nothing. I have been part of a multi-year piecemeal deployment and it has rough edges.
- Spearchucker 13y agoI have, and know exactly what the issues are. It's why (if given the choice) I prefer WS-Fed and Active Directory. ADFS 2 for .Net is phenomenally good.
- talex5 13y agoThe page is more positive than the title. It recommends: * Persona should be pared down to its core: a decentralized email verification and login API for the web. No more session management, no attribute exchange. * Persona should be built natively into Firefox, Fennec and Firefox OS to make the JavaScript shim unnecessary on these platforms. The base functionality should be cross-browser, but the experience should be optimized for the native platforms. * Sites should control most of the user flow and Persona should be almost invisible to users. * Sites should be able to offer these benefits to their users with a native UA implementation: better UX, reduced login friction and phishing protection. All of which sound great! BTW, has Persona reached 1.0 yet? Last I was aware, it was still in beta, which might partly explain the lack of adoption.
- kmfrk 13y agoI don't find Persona compelling, but I do think they offer an interesting value proposition for people - and framework developers - who have to implement their own user authentication. Even Django - which is about as close to the proverbial bicycle with training wheels as you can get - can be a pain, especially after django-registration was abandoned. The Django documentation was never really good either, to make matters worse. It also makes writing guides that much simpler, so although Persona doesn't hold much sway in a vaccum, it's great to have as a pragmatic option.
- blueskin_ 13y agoBecause it's Yet Another Pointless Single Signon. I don't see the point compared to having separate logins so if one is compromised, others aren't. Even past that, that space is already hugely cluttered with OpenID, OAuth, Facebook, Gmail, Twitter... Persona is a solution in search of a problem.
- petercooper 13y agoI hope I'm wrong but Firefox OS feels similarly to me so far.
- blueskin_ 13y agoFirefox OS seems like a joke, and I'm sure it only being on low-end Chinese phones reinforces that.
- mgreg 13y agoI disagree. Facebook connect, google+ sing on, sign on with Twitter, and username / password reuse all demonstrate the demand from 'normal' users for a SSO solution. There is also a distrust of these companies and the lock they have on your data so I believe there is room for an SSO solution that doesn't leak private info. Unfortunately for Persona a simple, fast, convenient user experience is not optional and that is where Persona has failed. I also believe getting to a great UX will be difficult or impossible with the decentralized system currently behind persona.
- jeena 13y agoI'm not sure why I don't see other people complaining about this but I myself tried to be my own Browser ID provider and after trying to install it for a couple of days I failed. Now I still have to use it with Persona which is just another centralized login system.
- TeMPOraL 13y agoHow about * we didn't give some people a way to join? I don't know whether it is my Internet disability manifesting, or some kind of weird region limiting or sth., but in last 6 months I tried to create a "Persona account" several times, followed the instructions precisely, and always ended up with a nonexistent "register"/"create account" button. Was Persona account creation disabled at some point in time? Why wasn't it clearly stated anywhere on the page? Or am I that stupid and can't see a register button?
- Osmose 13y agoThis highlights another one of the problems, which was explaining what Persona was to people. See, there's _technically_ no such thing as a "Persona account". Persona is a system that lets you log in with an account that works with the system. Someone who provides an account that supports Persona logins is called an Identity Provider, or IdP. However, most places don't work with the system when it first comes out, so Mozilla provided a "Fallback IdP" that just did straight up email verification. Getting your account from the Fallback IdP is what you probably wanted to do, and AFAIK the only way to do that was to essentially attempt to login with an email that didn't have an account with the Fallback IdP, which would trigger the verification step for you to create an account. This is a bad mixture of a) A confusing concept that's really hard to explain, and b) Bad UX around the fallback IdP and getting an account with it, especially if you don't assume clicking "Sign Up" will work for you. It's complicated by the fact that, if one of your goals is to get other login systems (like Facebook or Google) to support Persona as an IdP, you don't necessarily want to push people towards creating accounts with the fallback. It's hard to get all these things right, and I agree that Persona needs some more work to find a good solution to the problem of creating accounts that work with Persona.
- mgreg 13y agoYou hit the nail on the head here. I'd add that if part of persona's success is tied to getting email providers to adopt it by becoming an IdP then it's likely a flawed model. Why would google support/promote something that competes with Google+ sign up bit offers a poorer ux and robs th of the data they crave?
- chris-at 13y agoDoes Persona support native iOS/Android apps? And if not, why?
- deleted 13y ago[deleted]
- Siecje 13y agoSo I want to use Persona. So I go to https://login.persona.org/ https://login.persona.org/ and there is no "Sign Up" just "Sign In". So I enter my email which is through GMail and it is asking me to choose one of my Google Accounts. 1: I want Persona not permission to use my Google Account with another service. 2: I entered an email why would I want to use a Google Account with a different email?
- jamesgeck0 13y ago1. It's decentralized; email providers provide the authentication. Google doesn't directly support Persona right now, so Mozilla is supporting them via an Identity Bridge that hooks into Google's OAuth functionality. Google doesn't see what site you're signing into, just that you logged into a thing using Persona. Before Identity Bridges, you had to click a verification link in an email; this is a lot better. 2. I don't think Google exposes a way to use OAuth and skip past the list of accounts.
- Oculus 13y agoWait, is this a postmortem as in Persona is being discontinued?
- quadrangle 13y agoIt sure reads like that. What the heck‽ It is a good system and just needs continued work and support. This is a very poor way to announce a discontinuation or a very poor writing style for a reflection on an ongoing project.
- brianbreslin 13y agoAs a FORMER firefox developer (add-ons), I think my reasons for persona not taking off are as follows: 1. value proposition for developers was never clear 2. many saw it as a firefox only thing 3. chrome usage is overtaking firefox 4. I felt burned by developing for firefox in the past, why was I going to do it again (this is me personally, and is likely my #1 reason) 5. Never saw how it simplified my users lives. 6. I saw it as another waste of time like openID ended up being (and I loved the idea of openID, but so few people ever used it). /rant
- neil_s 13y agowhat would make Persona a killer solution for me is if it could hand out disposable email addresses to every site I sign into, that forward transparently to my main address (a la Gishpuppy). This way, I can identify which site is the cause of me suddenly receiving a bunch of spam (whether they're doing it themselves or their email database was hacked). Then its a simple question of disabling that disposable address from forwarding to my private one, and notifying the site that their database might be exposed.
- zobzu 13y agofor the record the main reason for adoptions issues around me seem to be: i got a fb/googke/twitter account that let me login too. i aint making a new account/pass. privacy? i care but not enough for that
- crystaln 13y agoSounds like persona should have just been a trusted oauth2 provider.
- drdaeman 13y agoCould we please consider not implementing something completely new, but fixing TLS client certificate auth, finally making it usable? Every browser out there supports this already, but UX is horrendous. All what was relatively polished over the years was the presentation of server certificate when you click on lock icon in location bar. The rest (selection of client certificate, generation of a new one, viewing a backing up of installed ones) remains needlessly scary to use by ordinary humans, so it can't be used except if we know users are quite tech-savvy. Instead of bringing a new technology with known downsides (like https://news.ycombinator.com/item?id=7219034 https://news.ycombinator.com/item?id=7219034) we could give a second life to a known and provably working one. Doing so we could promote security (HTTPS), anonymity (not giving email address by default, unless one's provided with a signed certificate, chosen by user's decision) and independence from any service providers (including email and domain registrars) at the same time. (Added after an hour) To illustrate my point: https://www.dropbox.com/s/fn4nuwszt5buuzd/tls_auth_ui.png https://www.dropbox.com/s/fn4nuwszt5buuzd/tls_auth_ui.png (mad design skills and windows 8, sorry for both; wording is not changed but I suppose it needs improvements, too)
- hippich 13y agoTried to register on forums posted here as an example of Persona integration. Have gmail email, so no password authentication (OAuth or OpenID instead.) Did not work due third-party cookies blocked in my browser. Sorry, this is not going to work for me.
- novaleaf 13y agomake it work with oauth, then at least i can support it without redoing my entire session system.
- alanh 13y agoIs Persona dead? Why does the post say “did fail” instead of “has failed (so far)”? The latter would imply that ongoing efforts will be made.
- abofh 13y ago"Users and developers trust Mozilla and want us to fix identity on the web." Maybe it's just me, but I trust iceweasel, a firefox derived browser that originates from Mozilla, but their continued increased interest in accumulation of browser and user data (albeit more anonymized than google et al), does not lead me to trust them. I accept persona is designed to protect against id-provider leakage, but when my id provider also has hooks to my browsers anonymous statistics and crash logs - I don't accept it's really private or trusted. (Same reason I don't login to chrome either...)