{"version":"2.1.234","anchor":"clearer-messages-when-sending-to-another-session","canonical_anchor":"clearer-messages-when-sending-to-another-session","heading":"Clearer messages when sending to another session","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/clearer-messages-when-sending-to-another-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Clearer messages when sending to another session\n\nSends to another session now report a rewritten message separately from an outright denial.\n\n**What**\n\nMessages sent to another session now go through the permission handler, which may rewrite them; a rewrite is reported separately from an outright denial. One-way sends distinguish \"Remote Control is not connected\" from a remote container that has no address to reply to.\n\n**Details**\n\n- The recipient is passed to the permission handler as a label, so the ask names who the message is going to.\n- Sending to an unnamed remote session adds a note that the receiver can only answer using the address carried on the message.\n\n**Evidence**\n\n`this session has no reply address`\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}