Yes, this project began as an internal initiative motivated by the current state of auth documentation — fragmented and inconsistent in quality. The goal was to create a centralized, high-quality website that is independent of Logto’s product content, providing value to the wider community.
While it's hypocritical to deny the potential benefits for SEO and brand awareness, the main goal remains (and will continue to be): to provide valuable and independent knowledge for everyone developing or interested in auth and identity.
In other programming languages, it's "by value" vs. "by reference."
One of the most confusing parts of dealing with immutability in JavaScript is understanding the array methods. "Officially", some of them are mutating, e.g., `.sort()`, while others create and return a copy, e.g., `.slice()`.
Founder of Logto here. It's been a while since our last Show HN. I believe we've accumulated enough new features to share an exciting update:
- User impersonation (RFC 8693: OAuth 2.0 Token Exchange)
- Personal access tokens
- Multi-tenancy (organizations with RBAC)
- Bring your own UI
- And much more to explore!
Building this product has been incredibly enjoyable. We are planning to deliver even more interesting features, such as a set of Web Components for sign-in and account management that you can integrate into your app.
Please let me know what you think. Logto couldn't have come this far without the feedback from the community. :-)
Our product is Logto (https://logto.io), an open-source auth solution with comprehensive features and modern dev experience.
We are excited to introduce our latest addition to our product, Role-Based Access Control (RBAC). This powerful feature gives administrators the ability to assign specific roles and permissions to users, ensuring they only have access to the resources and functions they need to do their job.