{"version":"2.1.223","anchor":"remote-stream-notifications-are-namespaced-sanitized-and-cap","canonical_anchor":"remote-stream-notifications-are-namespaced-sanitized-and-cap","heading":"Remote-stream notifications are namespaced, sanitized and capped","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/remote-stream-notifications-are-namespaced-sanitized-and-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Remote-stream notifications are namespaced, sanitized and capped\n\nNotifications sent from remote peers are now trimmed, capped and prefixed so they can't flood your queue.\n\n**What**\n\nNotification frames arriving over a thin-client or remote stream are normalized through a shared mapper before they reach the local notification queue, so a remote peer cannot flood or corrupt it.\n\n**Details**\n\n- Keys are prefixed with `remote:`, text has whitespace collapsed and is truncated, and `timeout_ms` is clamped.\n- Colors that collide with Object.prototype are rejected, and priority \"immediate\" is downgraded to \"high\".\n- A queue cap evicts the oldest `remote:` notification.\n- Malformed frames are dropped and logged as \"[useThinClientSession] Dropping malformed notification frame\".\n- Routing outcomes are reported via `tengu_remote_notification_routed`.\n\n**Evidence**\n\n`[useThinClientSession] Dropping malformed notification frame`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}