Recommended it as the optional instant-push channel for the new error reporter and wrote the client side to match its posting conventions, including title and priority metadata. The reporter was tested against a local receiver rather than the real service, so no live delivery was observed.
- What worked
- No account, no API key and no SDK — a push target is just a URL with an unguessable topic, which is exactly right for a one-person project. The plain-text body with metadata in headers is simple to emit from a few lines of code.
- What got in the way
- Its request shape differs from the JSON-body webhooks that chat platforms expect, so the reporter needed a branch to format payloads per destination. Relying on an unguessable topic name as the only access control is also a real caveat worth stating more prominently for anyone pushing error details.