Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
colinclerk
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
colinclerk
4mo ago
Clerk cofounder here - appreciate the feedback and forwarding to the mobile team!
2.
▲
by
colinclerk
4mo ago
Clerk cofounder here: I hope this isn’t a Clerk stakeholder! It’s definitely misaligned with our culture around not speaking about competitors and instead playing our own game.
3.
▲
Client Trust: Clerk's free credential stuffing killer
(clerk.com)
2 points
by
colinclerk
10mo ago
|
0 comments
4.
▲
by
colinclerk
2y ago
I wrote the tweet that Brandur quoted... I think the bigger shifts are that developers use Checkout more, and complete more admin tasks in Stripe's Dashboard. By providing end-user UX (for both customers and backoffice), Stripe has red
5.
▲
Easie SSO (SAML Alternative over Google/Microsoft OIDC)
(easie.dev)
2 points
by
colinclerk
2y ago
|
0 comments
6.
▲
by
colinclerk
2y ago
Appreciate that. We have many thousands of apps like yours on the platform, and I’m glad to hear the free plan is working for you. Forgetting about your auth provider is indeed the dream!
7.
▲
by
colinclerk
2y ago
Cofounder of Clerk. I agree - our pricing has been significantly reduced since this was written (partially in response to this post) We do intend to build more products, but if you're using us for pureplay auth we shouldn't cost 1
8.
▲
by
colinclerk
2y ago
Cofounder of Clerk here - we dramatically lowered our prices starting December 2023: https://clerk.com/blog/new-pricing-plans 10,000 MAUs are now included in every plan. We also now offer "First Day Free", s
9.
▲
by
colinclerk
2y ago
Fun! I just put our logo up. It took me two tries before it took, so maybe a twodollarhomepage :) What's the stack?
10.
▲
by
colinclerk
2y ago
Cofounder of Clerk here - we definitely want free plan users to be aware of this limitation - any suggestions to improve visibility? On https://clerk.com/pricing , “Customizable session duration” is listed as a primary bene
11.
▲
by
colinclerk
2y ago
Hey - cofounder of Clerk here Glad we were able to mitigate this one for our customers, but have also been a bit surprised this vulnerability hasn't been generating more chatter. tl;dr: if you use Google OAuth, any XSS on your site can
12.
▲
Mitigating OAuth's recently discovered Open Response Type vulnerability
(clerk.com)
7 points
by
colinclerk
2y ago
|
1 comments
13.
▲
by
colinclerk
3y ago
Answering 2 first because it's easier: Yes. 1. It's a great question and we're still learning the answer. But, I believe the approach is ~95% compatible, and the last 5% just needs tweaking on the margins vs a major overhaul.
14.
▲
by
colinclerk
3y ago
Clerk | Frontend & Backend SWE | Remote or in-person in SF Clerk is hiring frontend and backend engineers, remote or in-office in San Francisco We build developers tools for authentication. We're known for our React components like
15.
▲
by
colinclerk
3y ago
Does the crowd on HN expect passkey support to become more ubiquitous in the future, similar to Google OAuth today? I’ve been surprised at how few sites seem to be adopting rapidly since there are UX gains, but I suppose Google had a fairly
16.
▲
by
colinclerk
4y ago
If anyone's facing this in their auth flows, we're happy to help at https://clerk.dev We're in the same cat-and-mouse game with the attackers as everyone else, but since we're an auth company, we have full-ti
17.
▲
by
colinclerk
4y ago
SameSite=Lax plus CORS does the trick. Block requests where origin=helpdesk.mysite.com. Also, since you're concerned about subdomain attacks, make sure you set the cookie on a subdomain rather than the naked domain to prevent it from l
18.
▲
by
colinclerk
4y ago
I don’t agree that the complex system is mediocre. I like it because it’s faster and it’s enabling more powerful integrations. We (Clerk) abstracted away the complexity so it’s just an implementation detail, and think other tools should do
19.
▲
Let's stop arguing about JWTs and just fix them
(clerk.dev)
5 points
by
colinclerk
4y ago
|
2 comments
20.
▲
by
colinclerk
4y ago
Usually people experience this when they're using a React frontend that's served from a CDN, while the backend is served from a separate service. If that's the case, the pattern you're describing is pretty normal and not
21.
▲
by
colinclerk
4y ago
Disclosure: cofounder @ https://clerk.dev Auth isn't "hard" per se, but it's still a big struggle because there's just so much to implement. For example, one of the most common attacks today is "cre
22.
▲
Why the Uber hack may lead to a decline in Magic Links
(twitter.com)
2 points
by
colinclerk
4y ago
|
0 comments
23.
▲
by
colinclerk
4y ago
> In practice, almost all cross-origin API requests will require these preflight requests, notably including At Clerk, we took the opposite approach, and restructured our API so it fits within the narrow window that does not require a pr
24.
▲
A ‹Component/› is worth a thousand APIs
(clerk.dev)
7 points
by
colinclerk
4y ago
|
0 comments
25.
▲
by
colinclerk
4y ago
Will edgedb ever launch frontend querying with JWTs like Supabase, Hasura, Fauna?
26.
▲
by
colinclerk
4y ago
Nice, love that you launched with React components! I need to decide to show a button before I decide to allow a button's action :)
27.
▲
by
colinclerk
4y ago
The main benefit is that we're much, much easier to use with React. Since the Okta acquisition, we've also had several migrate over for better pricing. If you're interested in the technical reasons why & how: Auth0 is str
28.
▲
by
colinclerk
4y ago
https://clerk.dev is hiring remote frontend engineers, US or EU timezones only, in-person in San Francisco if desired We're a small team (<20) and have seen consistent customer growth since January We build drop-in auth
29.
▲
by
colinclerk
4y ago
The use case is just speed of development. We looked at several Billing implementations and found consistent patterns for exposing available plans and subscription management to the frontend. use-stripe-subscription simply packages one impl
30.
▲
by
colinclerk
4y ago
Hey HN - in addition to the linked codebase, we wrote a blog about the general challenges involved with "refactoring" a backend-facing REST API to also provide a frontend-facing React API (of hooks and components): https:/&#
More ›