Fränz Friederes

I’m freezing this account. It’s time. If you want to keep in touch: 🦋 Bluesky: bsky.app/profile/fraenz… 🐘 Mastodon: @friends" target="_blank" rel="nofollow noopener">chaos.social/@friends

When correctness and trust matter, leaning on well-established libraries is usually the better choice, even if that means stepping outside the usual stack. As a bonus, picking up a new language again turns out to be a very welcome detour. #BuildInPublic #DNS #Rust

My main takeaway is that reimplementing core Internet protocols in high-level languages can be interesting and educational, but often leads to unreliable results.

Building an email monitoring SaaS, I need uncached, fresh DNS data using Node.js. Over time, I realize that the entire approach is flawed.

@DrizzleORM @kulkarniankita9 throw 'rollback pls'

@kulkarniankita9 You can’t go back, because we didn’t implement rollbacks yet

Okay I can see why devs like @DrizzleORM I used it in a project and now I can’t go back!!

How do we solve this securely, without introducing #WebAuthn in a way that weakens the login flow? Would love to hear how others are approaching this problem.

If we return credential IDs based on an email address, we leak whether an account exists for that email. That’s introducing an account-enumeration risk when implementing a new authentication method that is supposed to strengthen security. Many providers seem to accept it.

Inspired by a #NordicJS talk on #Passkeys, I started implementing them for my passwordless SaaS. While working through the database schema and complex server logic, I noticed that key parts of the login flow are still under debate.

👋 from @nordicjs

We’re going live! Couldn’t make it to Stockholm? Don’t worry, you can still join #NordicJS from wherever you are. Tune in to our livestream today and catch all the talks, inspiration, and JavaScript magic in real time. 👉 nordicjs.com/live

Serverless doesn’t mean no servers. It means no servers I need to manage. It shifts responsibility to experts, so I can focus on what I do best: building the product. #BuildInPublic #Serverless

Serverless (for me, AWS Lambda) lets me draw a clear boundary: Code is my responsibility. The OS, hardware, and network security? Amazon’s. It’s not a shortcut, it’s a conscious tradeoff.

Yes, #serverless still runs on servers. The difference? They’re not mine to worry about.