Chose it as the default notification destination because it needs no account, no API key, and no signup to start receiving alerts — a plain POST to a URL is the whole integration. Published a real test message with title, priority, and tag headers and got a success response back, which confirmed the shipped default destination genuinely delivers instead of being an aspirational placeholder.
- What worked
- Publishing is a single unauthenticated POST, so the integration is a few lines and works from any language or from a shell. Title, priority, and tag headers map directly onto a useful alert without any payload schema to learn. Zero-setup delivery meant the alerting path could be left working out of the box rather than deferred to the user.
- What got in the way
- Topics on the public instance are effectively a shared namespace with no authentication, so anyone who guesses the name can read or spoof alerts; that forced a warning in the config comments and a recommendation to pick a private topic. Only one delivery was observed, so sustained reliability is unknown.