ElixirWeekly

Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #531
This week in Elixir

What the Emudhra CA Compromise Means for Elixir Developers
Spoiler: Update every CA store your application uses.

Monitoring the Health of Oban Applications
Søren are drawing from tips that they’ve given to Oban users over the years in this article on monitoring Oban health.

Even more from around the Elixir community

Data Sovereignty & Local-First AI: Building Eldrim with Erik Stenman Video

Designing Human-Computer Interactions with Ash - Alex Slade | AshConf 2026 Video

Code BEAM Europe Started: 15% off Virtual Tickets with 15foryou Conference

GitHub Formatter for Sobelow Blog post

Making Your own Atproto Backlink Index Blog post

Making dns_erlang Fast: Binary Tricks for the BEAM Blog post

What the Emudhra CA Compromise Means for Elixir Developers Blog post

Introducing Parlora: Build Voice AI Agents with Elixir Blog post

What’s new on BetterTyping, and how its Bots Work Blog post

131,072 Hops Deep: Semurg Walks a Social Graph up to 1,826 Times Faster than the Incumbents Blog post

JosePamplona/Dockerized-Elixir-Workbench: Create and run Phoenix Projects on Localhost with Nothing Installed but Docker, and Keep What you Learn About the Elixir Ecosystem as Cartridges: Installers you can Insert, Read and Remove, one Commit Each. Project update

pix_brcode/CHANGELOG.md at Main · igorgbr/pix_brcode Project update

Camelot — Public Beta is Open Project update

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)

Contact

Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).