{"version":"2.1.234","anchor":"messages-injected-by-a-host-are-classified-separately-from-p","canonical_anchor":"messages-injected-by-a-host-are-classified-separately-from-p","heading":"Messages injected by a host are classified separately from peer messages","tier":"internal","area":"Cross-Session Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/messages-injected-by-a-host-are-classified-separately-from-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Messages injected by a host are classified separately from peer messages\n\nMessages injected by a host are now treated as their own class, separate from messages from peer sessions.\n\n**What**\n\nInbound messages from another session used to be classified as peer traffic purely by origin kind. Messages marked as host-injected are now recognised as their own class and run through the coordinator acceptance and opt-out rules instead of the peer ones.\n\n**Evidence**\n\n`\"host-injected\"`\n\n- Area: Cross-Session Control\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5"}