The Dependency That Only Broke in Production

In July we found out that Loracle’s welcome email had never once been capable of sending in production. Every attempt, for the feature’s whole life, died on its first line with No module named 'resend'. CI was green the entire time. The tests passed the entire time. The code was fine the entire time. The bug lived somewhere most teams never look: in the gap between two requirements files. If you deploy Python with Docker, there is a decent chance you have this exact gap open right now. This is the postmortem, plus the five-minute check that tells you whether you’re carrying the same bug. ...

November 1, 2026 · 6 min · Loracle

The Unsubscribe Link Your D&D Bot Owes You

When you add a reminder bot to your campaign, you make a decision about five other people’s inboxes. They were never asked. They never created an account, never typed an email into a form, never saw a checkbox. You invited a bot to the table, and the bot inherited the whole table. That arrangement is normal in D&D tooling and it deserves more suspicion than it gets. If you’ve ever wondered whether a bot you’re about to install will spam your players, this post is the audit we ran on our own product, what we found, and the checklist we’d now hold any bot to, ours included. ...

October 30, 2026 · 5 min · Loracle

The Webhook That Said Everything Was Fine

If a Discord bot takes your money, you should get to see how its billing breaks. This is the postmortem of the July incident where every Stripe webhook handler in Loracle started throwing on its first line, our own endpoint told Stripe everything was fine anyway, and the only evidence in the entire system was a single telemetry event whose error string was one word: get. Nothing about this failure is exotic. It is three ordinary decisions, each defensible on the day it was made, that interlocked into silent data loss. If you run a service that charges people, there is a decent chance you have all three in production right now. Here is how to check. ...

October 29, 2026 · 6 min · Loracle

Your Table Doesn't Play in English

Picture a table in Munich. Five friends, a Thursday night, a campaign two years deep. The whole session happens in German: the threats, the bad accents, the argument about whether the paladin’s oath covers arson. Then the recap arrives, and it reads like a BBC correspondent summarizing their game from across the channel. If you play D&D in German, French, Portuguese, or anything else that gets called a “non-English market” in a planning doc, you already know this experience. Every tool in this hobby assumes your table speaks English. Character builders, VTT interfaces, AI note-takers: English in, English out, and if your session happens to be in another language, you get whatever falls out of the machine. ...

September 15, 2026 · 5 min · Loracle

13 Ways a Recording Bot Can Lose Your Session

Your table’s session has exactly one copy. Six people spent four hours making something that will never happen again, and the only record of it lives inside a bot that promised to be listening. If you’re a GM deciding whether to trust a recording bot with that, you should want to know how these things fail. So here is how ours fails, all thirteen ways, because the day we started paying for traffic we commissioned an adversarial audit of our own recording pipeline with one mandate: “from /record to /end we minimize the data we lose, always, and always package it up correctly.” ...

September 13, 2026 · 7 min · Loracle