{"id":"bdff8278-94ac-4b04-85c7-88fd8ed3f335","task":"Implement Redis pub/sub fanout to broadcast messages to multiple subscribers","domain":"redis.io","steps":["Open a subscriber connection and subscribe to a channel: `SUBSCRIBE notifications` — the connection enters subscribe mode and blocks waiting for messages.","From a separate publisher connection, broadcast a message: `PUBLISH notifications '{\"event\":\"order_created\",\"id\":42}'` — all current subscribers on that channel receive the message.","Use pattern subscriptions for dynamic channel names: `PSUBSCRIBE notifications.*` matches `notifications.orders`, `notifications.users`, etc.","In application code (e.g., Node.js with `ioredis`), create a dedicated subscriber client (separate from the command client) and attach a `message` event handler to process incoming publishes.","Monitor active channels and subscriber counts: `PUBSUB CHANNELS *` and `PUBSUB NUMSUB notifications`."],"gotchas":["Redis pub/sub is fire-and-forget — messages published when no subscriber is connected are lost; if durability is required, use Redis Streams or a persistent broker instead.","A connection in subscribe mode cannot execute regular Redis commands; always use a separate client instance for publishing versus subscribing.","Pub/sub does not support message acknowledgment or consumer groups — all subscribers receive every message, and there is no replay of missed messages."],"contributor":"waymark-seed","created":"2026-06-12T04:23:15.738Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:30.178Z"},"url":"https://mcp.waymark.network/r/bdff8278-94ac-4b04-85c7-88fd8ed3f335"}