jelambs

12 ms·

1.
by jelambs 1y ago
My hot take is that the SSO tax is totally legitimate because SSO is a clunky and complex feature to manage in a secure way. In fact many SSO implementations are actually not that secure because SAML is a dumpster fire when it comes to secu
2.
by jelambs 1y ago
interesting, does it let you manage multiple claude code agents without having to spin up different git worktrees? we were discussing the other day how that's an annoying limitation of claude code compared to codex, and the friction in
3.
by jelambs 1y ago
this is super interesting! MCP is really exciting in terms of what it can unlock for agent use cases, but still the wild west in terms of security. I was on a panel discussion yesterday where this topic came up, basically how do you trust t
4.
by jelambs 1y ago
Hi! I'm biased as one of the Stytch founders but wanted to share my POV in case it's helpful. As others mentioned, any of the open source options are not going to be low management overhead, but can be great in terms of cost and f
5.
by jelambs 1y ago
thanks for sharing! excited to help make the SAML ecosystem more secure. would love to hear any feedback people have!
6.
by jelambs 1y ago
So many use cases for this! Excited to see what people build.
7.
by jelambs 1y ago
Thanks for sharing! Would love to hear how others are thinking about this problem.
8.
by jelambs 2y ago
> Using apps like GitHub Co-pilot and Cursor to auto-complete code requires very little skill in hands-on coding. this is a crazy take in the context of coding interviews. first, because it's quite obvious if someone is blindly copy
9.
by jelambs 2y ago
we're looking at signals from the network, device, and browser as well as patterns across requests to identify these agents. in some cases, like operator today, it's quite trivial to identify based on the user agent but that'
10.
by jelambs 2y ago
author of the post here, yeah this is a really good point. I think we're going to see more people investing in building OAuth compatible apps and more thorough APIs to support agent use cases. but of course, not every site is going to
11.
by jelambs 2y ago
Thank you for sharing!
12.
by jelambs 2y ago
Have you checked out Stytch? I'm more than a little biased as the founder but would love to hear any feedback you have if you do. I thought your blog post covered a lot of really important points that are often forgotten when evaluatin
13.
by jelambs 3y ago
Thanks for sharing! We had a slightly different cost/benefit analysis for our use case with fairly straightforward APIs but know that might not be the same for everyone.
14.
by jelambs 3y ago
We recently built our own codegen solution to automatically create, maintain, and document our backend SDKs so that we didn’t have to compromise on either quality or maintenance burden. Also see part one of the series where we discuss how c
15.
How we built a codegen solution for SDKs to create humanlike code(stytch.com)
17 points by jelambs 3y ago|4 comments
16.
by jelambs 4y ago
hi! co-founder/cto here at Stytch, would love to help you get up and running with Stytch! If you have any feedback as well, would be awesome to hear it. If there are specific questions/use cases you're exploring, can share so
17.
by jelambs 4y ago
Hi! Disclaimer, I'm the co-founder/cto at Stytch[0]. We built Stytch because we went through the pain of building auth both in house and with incumbent players and wanted a better tool for developers building authentication. Stytc
18.
by jelambs 4y ago
Super excited for this launch! We'd love to hear any feedback you have.
19.
How to Go Passwordless(stytch.com)
10 points by jelambs 5y ago|1 comments
20.
Show HN: APIs for Passwordless Authentication(stytch.com)
7 points by jelambs 5y ago|1 comments
21.
by jelambs 5y ago
Hi HN! I’m one of the founders of Stytch ( https://stytch.com/?utm_source=social&utm_medium=hackernews&... ). We provide developer APIs and SDKs that make it simple to embed passwordless authentication in your apps. T
22.
by jelambs 5y ago
Stytch ( https://www.stytch.com ) | San Francisco & Remote (US only)| Full-time | Visa Transfer We build user infrastructure that makes it easy to onboard, authenticate, and engage your users. Improve security and user experie
23.
by jelambs 7y ago
I sold used golf balls, I was lucky to have a golf course just out the back door. You'd be surprised how many golf balls get abandoned just off the course, so I'd go for a walk after dinner when play slowed down and collect the ab
24.
by jelambs 8y ago
Agreed, computers are generally way better than humans at catching many style issues. We utilize linters extensively, those enforce many of our style guide rules. However, there are some, such as the example pictured in the article, that ar
25.
by jelambs 8y ago
Author here, I think that’s a great approach. We surface our guidelines for every PR by including a link to them in the description template. This acts as a reminder for people to be thoughtful about their review. I think the fact that our
26.
by jelambs 8y ago
Author here, that’s a great question! We approach this by ensuring that there are always multiple people that can review a given codebase or service. In practice what this looks like is we have teams that own our different services. Rather