DROP ALERT NOTES
Build a digest from the drop stream
Not every alert deserves its own ping. Buffer the stream into a window, group by match, and send one message that reads like a report.
Per-alert messages are right for moves you must act on in minutes. Everything else reads better as a digest: a window of alerts, grouped by match, sent as one message that reads like a report. The stream is the same stream; what changes is when your phone buzzes.
When a digest beats a ping
The live-versus-prematch split is the first cut, because the two rhythms differ so much, as the live vs prematch page lays out. Live drops age in seconds and belong in per-alert messages or nowhere. Prematch drops develop over minutes and hours, and a move that happened at 06:40 reads just as well at 07:00 alongside everything else that moved overnight.
A digest also suits the reader who wants market awareness without a reaction loop: a morning summary of what moved, grouped and sorted, is a briefing, not an alarm.
The window and the grouping
The machinery is small. Accumulate alerts into a buffer keyed by match, flush the buffer on a timer, send one message per window. The dedupe guide defines the event key, the match alone, which is exactly the grouping key the digest wants. Inside a match, keep one line per selection with its two prices and the fair price, biggest percentage first.
Fifteen to sixty minutes is the sensible window range for prematch. Shorter windows drift back toward per-alert noise; longer ones turn the digest into a newspaper.
The message itself
The relay guide message discipline applies unchanged: the match name, the market, the side, the two prices and the fair price, printed compactly. A digest adds a header per match and a sort order, and that is all. If a selection moved twice in the window, show the net move from the first price to the last, and note the count.
Discord and Slack webhooks both take longer bodies than a phone notification, but the phone-length version still wins: ten lines of report beat forty lines of log.
Keep the urgent lane separate
A digest and an alarm are different products, and the cleanest setups run both: big confirmed moves page immediately, everything else waits for the window. The routing table decides which lane each alert enters; the digest is just another destination with a timer attached.
What you should never do is digest the urgent lane. A move that needed you in ninety seconds reads as archaeology in a morning summary.
Buffer, group, flush, send. The stream keeps its tempo; the digest gives you yours.