Get live statistics and analysis of Konsti Wohlwend's profile on X / Twitter

just found out a company called Authfy copied Stack Auth's entire product, made a landing page, and is selling it as their own. they claim they're selling it to 2,000 customers. they didn't even bother rewriting the docs. the entire thing is 1:1 the same, not a single extra feature. they just ctrl+f replaced "Stack Auth" with "Authfy". oss builds on collaboration & composition but pretending you made something you didn't is just vile. actually impressive how lazy you can be while still trying to scam people. i'll take it as a compliment! according to their own landing page we are the most secure, scalable, and affordable auth service ;)

yc application tip: DO: ask your friends who you've worked with closely for a referral. a lot of people i know got in after a strong referral of a friend! DON'T: DM random people on linkedin and ask them for referrals. you won't get a good referral from them, so better to stick to people who know you well

Announcing login․new, the fastest way to set up auth. Just pick your auth providers, and click Create Pull Request. that's it. Currently supporting all Next․js projects, with preliminary support for React and vanilla JS. Try it out!

This needs some context. Founders sign two contracts when they join YC. First, when they start the program, they sign a contract along the lines of: "Founder agrees to sign the YC SAFE as soon as the company is incorporated." When that's done, the *company* signs the actual YC SAFE, which is along the lines of: "Company agrees to give X% in exchange for $Y." Both of these are legally-binding, written contracts sent via Docusign with a digital signature. The reason there's two steps is so founders can participate in YC before having finished the incorporation paperwork. No, you're not breaking a contract if you reject an offer from YC. But yes, you are breaking a contract if you accept the offer, sign the first set of documents, then decide that you don't want the investment anymore and don't sign the SAFEs.

This one seems to be taking off... Would y'all be interested in a blog post on "advanced" ways in which JS is cursed, going deeper than the oversaturated "type conversion and NaN bad" articles?

I bet you'll get this one wrong — what's the output of this snippet?

Lots of AI app builders for building apps *FOR* mobile phones, but are there any AI app builders for building apps *ON* a mobile phone?

DO NOT RUN `NPM INSTALL` TODAY. There's a huge wave of malware going around in npm packages right now — over 500 affected directly, and hundreds of thousands affected indirectly. It's likely that whatever dependencies you have have dependencies that have dependencies that depend on a malicious package. If you must run npm install, do so very carefully, and disable the ignore-scripts config option: `npm config set ignore-scripts true --global`

a lot of you asking if i regret open-sourcing Stack Auth after this whole thing. hell no. i actually hope MORE people copy us. they can fork the entire repo and steal every feature. they can try to compete. but here's the thing: we'll still win. they're spending their time parsing git commits trying to understand what we just shipped. by that time we're already three features ahead. they're debugging code they didn't write. we can ship 100x faster because we know exactly why everything works the way it does. let them copy, in the end it's free marketing for us. their customers will eventually discover that we are the original, and when Authfy struggles to fix their scaling issues, we're the ones they reach out to. the codebase is only 10% of our company. the other 90% is speed of execution. and if all you do is copy code, you'll never be *pushing* the boundary of what's possible. so yea. this was bound to happen at some point. no regrets! (although, i do ask that our copycats respect our open-source license, which afaict Authfy did not. oh well.)