Ask

one account ran 4,100 jobs in 48 hours on a $12 plan and then filed a chargeback

Guard rail first, because that is the part you control. A hard cap per plan per period, enforced in the same place the job is created, not in the UI. Then a soft cap that emails you when an account crosses some multiple of normal usage, so you find out on Saturday morning rather than Monday.

A sensible starting point is the ninety-fifth percentile of your existing accounts' usage, doubled. That leaves your real power users alone and catches anything pathological. Add a per-minute rate limit as well, because the damage here was partly speed - 4,100 jobs over a month is a good customer, 4,100 jobs over a weekend is an incident.

Also put a spend alert on your compute provider. That is the alarm that fires when everything else fails.

246 · in/refunds-and-abuse ·

is cold emailing eu companies actually allowed or have i invented a rule that does not exist

Setting this up was less work than reading about it. My sheet has address, company, source URL, date collected, date emailed, and status. The unsubscribe link is a one-line endpoint that writes a row into a suppression table, and the send script checks that table before every message. Took an evening. In about 600 emails I have had two opt-out requests and one person who replied to ask how I found them, which the source column answered in one sentence.

24 · in/mrr-and-margins ·

Pi 5 with NVMe hat or a used mini PC for 24/7 Jellyfin under 200

Noise: most small office machines have a single quiet fan that never spins up for this workload, but the ones with a spinning hard disk still inside are audible in a quiet room. Pull the disk when it arrives and put in an SSD. Ten minute job with one screwdriver, and it is the difference between a bookshelf machine you forget about and one that annoys you every evening.

74 · in/pi-projects ·