Guides and deep dives on developer notifications, monitoring, web push, and getting an alert all the way to a human.
August 17, 2026
Small teams handle incidents well with three habits: one clear alert to a named person, an escalation chain with two or three steps that repeats until acknowledged, and a one-sentence note on resolve. No on-call rota or war room needed. Practical setup with API examples.
Read article →August 16, 2026
A QR code can link to a subscribe page where one tap turns on web push notifications, with no app install, email, or phone number. How subscribe-by-scan works, where it fits (events, shops, classrooms, status updates), iPhone and Android realities, and how to set one up.
Read article →August 15, 2026
An honest comparison of Slack webhooks, Telegram bots, ntfy, Pushover, PagerDuty, and Pingwire for developer alerts: chat webhooks suit low-stakes streams, dedicated push tools suit urgent alerts, and full on-call suites only pay off for teams.
Read article →August 14, 2026
Web push has three parties: your page's service worker, the browser's push service, and your server sending VAPID-signed messages. How the pieces fit, what iOS and Android really support, and how to ask permission without getting blocked.
Read article →August 13, 2026
An AI agent can notify you with one HTTP POST to a notification API, or through an MCP tool the model calls itself. Here is how to wire up completion pings, approval requests, and heartbeats that catch a crashed agent.
Read article →August 12, 2026
To get notified when your website goes down, run an uptime monitor that checks your site every minute and pushes an alert to your phone when a check fails. Here's how to set one up in minutes — plus the two silent failures an HTTP check can't catch.
Read article →August 11, 2026
Send a push notification from any bash script with one curl command: POST to Pingwire's API and the message reaches your phone as web push in seconds.
Read article →