From a67baa71f40139c9f13f468103596e2a383f241f Mon Sep 17 00:00:00 2001
From: Julien Herr
The practical stuff — subscribing, privacy, troubleshooting, and how kill-the-news differs.
+Create a feed in the admin UI and you get a unique address on your domain (e.g. newsletter.42@yourdomain.com) plus an RSS and an Atom feed. Any email sent to that address is turned into entries in those feeds.
Confirmation emails arrive as feed entries — open the entry in your reader and click the confirmation link. If a publisher requires a reply, subscribe with your normal inbox instead and set up a filter that auto-forwards its mail to your feed address.
+Yes. Each feed URL carries an unguessable ID, it is served from your own domain on your own Cloudflare account, and the admin UI is password-protected. Treat the feed URL like a password — anyone who has it can read your newsletters.
+Feeds honor an optional size and time-to-live cap so RSS readers stay happy — some readers choke on feeds that grow too large. When a limit is reached, the oldest entries (and their R2 attachments) are purged automatically.
+Don't. Anyone with the URL can read your newsletters and even unsubscribe you. Share the project instead, so others can self-host and create their own feeds.
+Send a test email to the feed address. If it shows up within a minute, the delay is on the newsletter publisher's side, not kill-the-news. Readers that support WebSub get near-instant push updates instead of waiting for the next poll.
+kill-the-news is self-hosted on your own Cloudflare account: your data, your domain, RSS and Atom output, attachments served as enclosures, WebSub push updates — all running on the free tier.
+It runs on Cloudflare's free tier (Workers + KV + R2) plus the cost of your domain. With Cloudflare Email Routing, no third-party service is required at all.
+From the password-protected admin UI — open the Feeds tab and delete it there. Its entries and attachments are removed along with it.
+