Browsers could implement a service that backs up your personas and syncs them across your devices. Ideally the syncing should be cross browser too and allow me to use my own servers for this if I choose.
Unfortunately, it was shut down in 2016 due to lack of interest. (Coincidentally, I just spent this past week hacking on its source code.)
You're suggesting some different backend details, but the UX you describe is already in place.
With the browser acting as your user agent, it can manage multiple contexts (work, personal) and let you choose which is sent to each site, without the need for separate browsers for each.
As an added tangent, consider that browsers are one of the few places where we can do things like "temporarily log me out of everything" (Incognito Mode / Private Browsing). They have some level of sophistication in session management already.
I would go even further than this, and say that a cryptocurrency might be among the best ways to build a universal login system. Imagine an Ethereum-like coin where the wallet is the username, and you spend the coins while authenticating, gaining privileges, and the blockchain stores your public info like a username and avatar that you can bring to any website.
What is a better solution than building a tamper proof workflow in the blockchain? Examples include:
1. I sign a contract and the notary signs and uploads a copy to the blockchain to validate the contract contents, that it was signed and by whom, and when.
2. An auditor validates a piece of evidence a client provides that proves its in compliance with a particular control in some regulatory framework. The auditor uploads a SHA256 hash of the evidence in a transaction memo to the blockchain to validate against later in peer review, a lawsuit, etc.
Edit: My examples here refer to a valid use case of a blockchain and not cryptocurrencies which is what you mention, but based on context of this discussion it looks like we all actually mean blockchain and not necessarily cryptocurrency.
Blockchains have several uses but to date they are narrow. Everywhere outside of their core use cases (essentially contracts or keeping track of tokens of value) they are a hindrance. Blockchains are also hugely inefficient by design (if they were they’d be easy to crack or to perform a 51% attack on), so when you are communicating with a single third party which you trust to provide a service to you, you absolutely do not need a blockchain. We have seen time and time again people trying to throw this solution at all the problems from DNS to buying groceries and yet the only solutions still worth talking about remain cryptocurrencies. Turns out well defined client/server APIs and databases actually do work about as well as anything else.
In the spirit of discussion, what could you do if you involve a blockchain in logging into GMail that you absolutely cannot do without it? If the answer is nothing, then there is zero reason to go down that path.
> crypto currencies are a good solution for one thing only: electronic currencies.
You contradict yourself by stating above you believe there's only one valid use case for blockchain, but in your most recent comment you obviously admit there are several valid use cases (though admittedly a limited number). Maybe your initial comment was meant for emphasis and not literally that you believe there is only one use case, but be careful using quantifiable verbiage or hard numbers to portray emphasis without explicitly stating that's what you're doing, your credibility gets called into question when doing so.
That being said, if this was /self hostable/, I'd see myself using it on a few projects.
HN ‘markup’ diversity is always a joy for the punctuation mark enthusiast.
\Hooray for markup/
Then I've seen lots of people offload that to Auth0 or other managed services.
- If I cant make enough money per user to even pay for Auth0, why am I working on this?
- Auth0 provides more than login, its got logic related to token re-validation, signup pipelines, social platform integration, etc... sure, I could build each of these as I needed them, in fact I did previously build them for myself. However by using Auth0 I know in advance that all this kind of functionality will be available when/if I need it.
- Easy cross system auth. If I want to build something using separate services, like a front end in one tech stack and a backend/admin using a completely different stack, Auth0 makes it so easy to share logins, roles, and permissions between the two systems without having to work out how to handle it myself, or within having to run my own third system like my own installation of Keycloak or building my own equivalent to it.
Managed services like Auth0 are a great alternative, although Auth0 is one of the more expensive ones. For small apps I found Firebase Auth to be great, for larger projects things like Amazon Cognito or Azure AD B2C are probably the better choice (although Azure AD B2C still doesn't support custom domains). They are worth a try imho, since Amazon as well as Microsoft offer a generous free teir (50k MAUs for free)
I'd rather set up login functionality on my own server. If you use a third party service, their downtime becomes your downtime. Worse, you're injecting another company into your relationship with your users. If that were necessary, I'd choose one the customer was already familiar with, like Google, Facebook or Twitter.
Setting up login isn't very difficult and libraries exist for most webdev languages to make it even easier. It's definitely not worth 5% of my revenue.