Just one suggestion - remove the F-bombs from the testimonials on your homepage. There are various firewall intel providers that will put you on the bad lists because of this. You usually learn this the hard way :/
Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
61–70 of 112 posts
Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#62Earlier quoted context omitted.
- Not right now, but there’s already an open issue and a PR in progress. - We don’t use JWTs directly, and sessions always require state (it’s not stateless). And yeah, both the client and server handles automatic session refresh. - Yes, we support both multiple sessions or having different organizations open in different tab: https://www.better-auth.com/docs/plugins/multi-session - Yes, that’s possible, you just nee…
> We don’t use JWTs directly Why?
Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#63Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#64However I'm not entierly sold on this being an actual alternative to auth0 and such - at least for now. For a drop-in solution lack of mail and dashboard can be a real deal breaker.
Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#65Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#66Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#67Congrats on the launch! Better Auth has a level of universal love from developers that's really seen. Just one suggestion - remove the F-bombs from the testimonials on your homepage. There are various firewall intel providers that will put you on the bad lists because of this. You usually learn this the hard way :/
Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#68Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#69Re: Launch HN: Better Auth (YC X25) – Authentication Framework for TypeScript
#70Is there support for dynamic sign in provider urls? One of the deal breakers (in addition to federated sign in/sign out being a pain) for us with next-auth was that we have certain customers whose security requirements include pointing subdomains that they own at our servers. So we would need to be able to use some logic to determine where the sign-in redirect should take a given user.