dickhardt

Joined 17 years ago

Karma
119
Submissions
47
Member since
Oct 26
20 years exploring idea maze for identity

Founder/CEO Hellō - https://hello.coop

Ported Perl 5 to Windows Founder/CEO ActiveState & Sxip Identity Led design of OAuth 2.0 and JWTs Identity 2.0 https://www.youtube.com/watch?v=RrpajcAgR1E https://www.linkedin.com/in/dickhardt/ @DickHardt ex-MSFT, ex-AMZN

View on Hacker News

Recent submissions

Comment · 2 years ago
Eartho sounds like a something a user wants. We have found that privacy is an added bonus, but that it is only one of many features a developer wants.

Adding yet another button that users don't understand confuses users.

I'm the founder of Hellō and we have a similar service that has cooperative governance. https://hello.coop/

FWIW it is a myth that Google uses where you login with Google for retargeting. Big Tech is always concerned about having to share user specific usage with US agencies. Google considers knowing where you login to be toxic data that they want to dump as quickly as possible. There are more than enough other signals from re-targetting.

Comment · 3 years ago
Comment · 3 years ago
Nice to hear that has stood the test of time. :)
Comment · 3 years ago
OAuth 2.1 has no new features. It is OAuth 2.0 rolled up with all the specs since 2.0. It is the better place to start for learning about delegated authorization.
Comment · 3 years ago
OAuth 2.0 took the best features of what was already being deployed by Google, Microsoft, Yahoo, etc. and added in scopes and refresh tokens. The objective was to standardize how to delegate authorization so that developers did not have to learn slightly different ways of doing effectively the same thing.

Typing your username and password into a 3P website so it could crawl your contacts was horrible anti-pattern.

Comment · 3 years ago
thanks! ... just like SSO -- it does not seem hard in a demo that has made it easy!
Comment · 3 years ago
Comment · 3 years ago
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.

https://www.hello.dev/docs/comparison/

... 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 https://news.ycombinator.com/item?id=33177705

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. https://www.hello.coop/pages/approach.html 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 @ [email protected]

[1] https://www.linkedin.com/in/dickhardt/ https://en.wikipedia.org/wiki/Dick_Hardt https://twitter.com/DickHardt

[2] https://datatracker.ietf.org/doc/html/rfc6749, https://datatracker.ietf.org/doc/html/rfc6750, https://datatracker.ietf.org/doc/draft-ietf-oauth-v2-1/

[3] https://www.youtube.com/watch?v=RrpajcAgR1E

Comment · 3 years ago
Tl;dr: If you are a developer considering adding World ID to your project. Wait.

If you see an app using World ID. Be safe.

The OAuth Best Security Current Practices have not been followed. Combined with the following point, applications using World ID may be vulnerable to attacks.

The implementation is not compliant with the OpenID Connect specification. Times are in milliseconds instead of seconds, requests can be made without required parameters. Update Aug 9, these have been addressed.

The user’s privacy is being violated. The authorization page presents no information on what the application is requesting, nor on what worldcoin.org is releasing. There are no application terms of service and privacy policy links.

Comment · 3 years ago
The OP conflates the fediverse with Mastodon, and my understanding of his key point is that it is doomed because Mastodon is complicated to run. As the operator of https://press.coop, I agree. Mastodon is 10 yr old web tech (Ruby on Rails with Postgres) that does not take advantage of modern cloud architectures. (The streaming service is written in nodejs and is efficient and just works)

But software continues to evolve. There are numerous other software projects on the fediverse, Cloudflare's Wildebeest being an example of a more efficient, and easier to manage implementation. Crowdfunding has become a common means for instances to be funded. It is still early days for the fediverse, and the pace of innovation continues to accelerate. Remember that Twitter was twttr when it launched, and was an SMS based app. Flickr was a Flash app.

Comment · 3 years ago
ActivityPub is the core protocol and is a W3C standard

Mastodon is the most popular implementation currently, but there are many other implementations in the fediverse

Comment · 3 years ago
Comment · 4 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton