Identity 2.0 Keynote

> Well, the solutions offered then have failed, but did they systematically rule out all possible technologies and business models? Of course not. In fact, business models were only considered tangentially in most cases because the general goal was to create an ecosystem of federated identity providers transacting over open protocols. Differentiation would come from the relationship between customers and their providers - charging for background checks to add extra confidence to third-party claims, for example. Or, by selling enterprises more secure identity claim brokers for their employees. > One problem is username and password proliferation. Another is filling out the same information over and over, like phone number, email address, and so on. E-commerce sites will often not bother checking email addresses and not require accounts because unnecessary obstacles drive potential customers away. I'd love to see the Digital Identity discussion revived, and between high-profile security breaches (Adobe, Target...) and the NSA, I think it might be time. I know you don't have or necessarily want a preconceived idea of what a 3rd-party account/identity provider should be, but I encourage you to look at what's been done & discussed before. Dick Hardt's keynote from the 2006 Identity 2.0 conference is entertaining and informative: [VIDEO] - it's also the talk that got me hooked on Vanilla Stoli for a couple of years. Kim Cameron's "Laws of Identity" were the cornerstone of the discu

For reasons completely unrelated to the content, Identity 2.0: [VIDEO] Watching that talk brought me over to the "a picture or a few words per slide" style of presentation, rather than the "wall of bullet points" style. It also helped me move from "stop talking, change slides, start talking again", to smooth transitions while talking.

The most effective presentation style I have ever seen used literally hundreds (if not thousands) of slides, but in a way I had never encountered before. I’ve heard it described as the Lawrence Lessig presentation style, but my introduction to it was a presentation about “Identity 2.0” by Dick Hardt, and his is still the best I’ve seen. It absolutely blew me away, both as a presentation style and a mechanism for conveying information/message (ideally they’re the same thing, but I have sat through some presentations that are entertaining but devoid of content). Dick Hardt’s presentation is at [VIDEO] - the content has aged a little (though less than I expected before I just rewatched it) but if you’ve never seen it, I encourage you to watch it; it’s not that long, it will feel even shorter than it is because it’s so engaging, and it certainly illustrated to me how important communication skills are and improved my own presentation style.

Too many words on a slide and too small a font (contrast Lawrence Lessig's slides [0] or Dick Hardt's [1]). Looping animated gifs (especially when they're overused). Bad fonts, colors, layout. Monotonous delivery (e.g. saying ”I'm excited” without excitement in your voice). NOTE, I just sat through 2 days of slides, so I'm a little cranky. [0] [LINK] [1] [VIDEO]

Your question is missing a couple key inputs. Q: Is your SaaS app targeting enterprise use cases, where the customer will want to enable SSO and centralized provisioning? Keybase is a reasonable choice in this case because of the SAML and SCIM support. Q: What is your expected revenue per user? Auth0 solves many problems out of the box, but is priced on MAU which can be prohibitive if your revenue per user is low, but deals with lots of complicated issues if not and lets you focus on building your app. I'm the founder of Hellō[0], and if you are targeting consumers or individual professionals and want to give them choice, check it out. As some background, I cofounded the OpenID Foundation, drove creation of OAuth 2.0 and what became JWT, and gave a popular Identity 2.0[1] talk years ago. [0] [LINK] & [LINK] [1] [VIDEO]

Hi HN! I’m Dick Hardt[1]. Over the last twenty years, I’ve led the design of identity standards (OAuth 2.0, JWT) and systems that you and billions of others use every day.[2] You know that these systems don’t always work in your favor. Each is bespoke and most, if not all, of your identity is locked up in these silos. I called this out in my Identity 2.0 OSCON talk in 2005 where I popularized a user-centric identity vision.[3] Unfortunately, we have failed to realize the vision of user-centric identity: of giving you control of your identity. We have far too many passwords. Identity theft is rampant. Online interactions are either tedious or risky. In short, internet identity is a disaster today. Most proposals today to give you control of your identity require you, your applications, and the issuers of claims about you (such as your bank or government), to adopt a new technology - a three-sided cold start problem. I founded Hellō to take a different approach -- an abstraction layer that lets you use the technology and identity you already have -- that’s operated by a not-for-profit co-operative. The Hellō journey did not start with building a product -- it started with exploring how to resolve the risks of a central service, and finding organizations aligned on the vision. Once three industry-leading organizations joined as founding corporate members of the co-operative, we built and tested our PoC, our MVP, and then our developer console. Hellō is available for you to use t

Hey HN, I’m Dick Hardt[1][2][3], and I’m the founder of Hellō. Hellō is a new paradigm in Identity as a Service that empowers the user, simplifies development, and has a much lower cost structure. If you are building a new app, Hellō is faster (minutes) and cheaper (free) than the alternatives. [LINK] ... especially if you are building with Next.js, Express, or Fastify and using our Quickstart which removes all the manual configuration so that you are running locally in a minute, and can be deployed fully configured a minute later. We posted about our co-operative approach on HN last year [LINK] Since then we have added support for Discord, GitHub, GitLab, Mastodon, and Twitter. If you are on a mobile device, you can enroll a passkey for future logins on that device. On the desktop, you can scan a QR code to login with your phone. We expect you have more questions. [LINK] describes: - Our approach - How the cooperative works - How we’ll fund Hellō with smart contracts - Our guiding tenets - How we protect people’s privacy - Our architecture Thanks for reading and trying! Please share your questions, impressions, criticisms, and requests here, or you can email me @ dick.hardt@hello.coop [1] [LINK] [LINK] [LINK] [2] [LINK] , [LINK] , [LINK] [3] [VIDEO]