1. X
  2. Fränz Friederes
Log inSign up
Fränz Friederes
2,849 posts
user avatar
Fränz Friederes
@ffraenz
Solo Software Engineer building a SaaS for DMARC monitoring dmarced.eu, deciphering cryptograms, and chasing sneaker drops, he/him 🏳️‍🌈
Luxembourg, EU
wierk.lu
Joined May 2009
737
Following
535
Followers
RepliesRepliesMediaMedia

New to X?

Sign up now to get your own personalized timeline!

Create account

By signing up, you agree to the Terms of Service and Privacy Policy, including Cookie Use.

Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
Don't miss what's happening
People on X are the first to know.
Log inSign up
  • Pinned
    user avatar
    Fränz Friederes
    @ffraenz
    Jan 29
    I’m freezing this account. It’s time. If you want to keep in touch: 🦋 Bluesky: bsky.app/profile/fraenz… 🐘 Mastodon: chaos.social/@friends
    Image
    Fränz Friederes (@fraenz.frieder.es)
    From bsky.app
    85
  • user avatar
    Fränz Friederes
    @ffraenz
    Jan 15
    Building an email monitoring SaaS, I need uncached, fresh DNS data using Node.js. Over time, I realize that the entire approach is flawed.
    Screenshot of a DNS record detail view, showing the TXT DMARC record value, the exact TTL, DNSSEC validation status, and the time range during which the record was observed.
    84
  • user avatar
    Fränz Friederes
    @ffraenz
    Oct 15, 2025
    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.
    57
  • user avatar
    Fränz Friederes
    @ffraenz
    Oct 2, 2025
    👋 from @nordicjs
    The audience and stage of the Nordic.js conference, in blue/pink mood
    280
  • user avatar
    Fränz Friederes
    @ffraenz
    Jul 14, 2025
    Yes, #serverless still runs on servers. The difference? They’re not mine to worry about.
    Diagram titled “My responsibilities with a serverless stack” showing a vertical stack of labeled boxes. Only “Application code” is left unmarked, indicating it’s the developer’s responsibility. The other layers “Operating system,” “Virtualization,” “Physical hardware,” and “Data center access control” are each crossed out, illustrating that these are not managed by the developer when using a serverless setup.
    68
Advertisement
Advertisement