Live data from Hacker News

Viewing profile — colinclerk

colinclerk

HN member
Joined
Mon, Aug 19, 2019, 6:02 PM UTC
HN karma
998
Public activity
130 items

About colinclerk

Cofounder https://clerk.dev

Email: colin@clerk.dev

Recent public activity

  1. comment
    Comment #48044312

    Clerk cofounder here - appreciate the feedback and forwarding to the mobile team!

  2. comment
    Comment #48044279

    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. comment
  4. story
  5. comment
    Comment #42545499

    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…

  6. story
  7. comment
    Comment #41927589

    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…

  8. comment
    Comment #41927386

    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…

  9. comment
    Comment #41927132

    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 no…

  10. comment
    Comment #41856668

    Fun! I just put our logo up. It took me two tries before it took, so maybe a twodollarhomepage :) What's the stack?

  11. comment
    Comment #41202484

    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 se…

  12. comment
    Comment #41183697

    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. t…

  13. story
  14. comment
    Comment #39566070

    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…

  15. comment
    Comment #39562999

    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 authen…

  16. comment
    Comment #35988593

    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…

  17. comment
    Comment #34266565

    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 a…

  18. comment
  19. comment
    Comment #33165534

    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 subd…

  20. comment
    Comment #33103591

    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 jus…

  21. story
  22. comment
    Comment #33063155

    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 yo…

  23. comment
    Comment #33063048

    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 att…

  24. story
  25. comment
    Comment #32910784

    > 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…