Engineering deep-dives from the SlashFeed team — Elixir, Phoenix, and how the product is built.
How SlashFeed blocks an account everywhere at once — sessions, API tokens, MCP, background jobs — while deleting nothing, so unblocking restores it exactly. One timestamp, a handful of choke points, a query macro for the workers, and an email list with no foreign key on purpose.
How SlashFeed stops hammering a publisher that has started saying no — Hammer counters for the error rate, Postgres for the breaker state, a worker gate that cancels or snoozes jobs, a per-domain request budget, and an admin page to drive it all.
How SlashFeed delivers new-entry events to user-configured HTTP endpoints — the user_webhooks schema, an HMAC-SHA256 signing protocol receivers can verify, an Oban worker with retries and per-attempt delivery logging, and the fan-out that fires from the parser only for genuinely new entries.
How SlashFeed pulls entries from JavaScript-rendered SPA sites that have no RSS feed, using a headless Chrome sidecar and a dedicated Oban worker.
How SlashFeed detects feeds that quietly stopped publishing and files self-resolving Kanban tickets with an idempotent Oban cron worker.