After an API Key Leak in 2026 — Establish Actual Touches with Postgres Logs

·2 views

An API key leak creates two competing operational constraints: stop further access, but preserve enough trustworthy evidence to learn what the key already touched. Revoke too early without capturing the relevant records and responders may lose the easiest correlation handle; wait without containment and the exposure continues. TL;DR: create a replacement credential, deploy it alongside the still-valid old one, verify the replacement is serving production traffic, then revoke the leaked key. For the investigation, build one UTC-ordered usage series from immutable gateway, application, data-acce

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

I Tested 11 HTTP Resilience Libraries

When I started building ffetch, I had a fairly simple goal: make HTTP requests more resilient without turning a fetch wrapper into a complicated piece of machinery. Retries, backoffs, circuit breaking, and the other patterns could live around a small core, with plugins adding whatever a particular application needed. I liked the elegance of that design, and keeping the library lightweight was a big part of the appeal. The trouble started when I went back through the code looking for correctness issues. I found subtle bugs and edge cases, then more of them as I looked at what happens when you c

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Receipt PDF Background Jobs: Signed Evidence for Attached Order Confirmations

The page says confirmation_without_receipt, and the on-call view is brutally small: an order identifier, a queue age, and a message stating that email delivery finished while its PDF attachment did not. The customer has a confirmation, support has a complaint, and a dashboard full of green averages cannot answer the first useful question: what page fired, and which durable fact proves the redacted receipt was the file actually sent? TL;DR: accept the order in the web request, enqueue an immutable receipt job, render the PDF in a worker, redact personal data before the document crosses the shar

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Hive - A Local AI Life Assistant for My Family, Running on a Raspberry Pi

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend Hive is a private, multi-user AI life assistant that runs entirely on a Raspberry Pi 4B — no cloud, no subscriptions, no data leaving your home network. I built it for my family. We needed a shared space to manage our week: upcoming events, daily expenses, and a clear picture of what actually matters each day. Every existing tool either costs money every month, sends your data somewhere, or needs a good internet connection. Hive does none of those things — it lives on a Pi on the shelf and is accessible from any p

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Panic2Pass An AI Cramming Tool I Built for a Panicking Friend

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend We've all been there, it's late at night, the exam is tomorrow, and there's way too much to study. I built Panic2Pass for my roommate, who had an Operating Systems exam coming up, 200+ pages of notes, and only a few hours left. He didn't need another chatbot. He needed to know what to study first. So I built a small AI tool with four modes: ⚡ 30-Min Crash Plan : Focus on the most important topics first.

0 comments Read more at DEV Community