Messaging an unknown peer now explains that sessions on other machines could not be checked, so retry.
What's wrong with this entry?
The old "reply-only bridge session" refusal was removed, and unresolved peer names now explain that Remote Control sessions on other machines could not be checked, with a suggestion to retry.
- Unresolved names no longer fall back to the send_message connector.
- Timeouts are now reported as
"timeout"instead ofnot_reachable. - The isolatePeerMachines prompt is assembled from whichever of the cloud or bridge lookups actually failed.
sessions on other machines could not be checked just now, so they were not searched.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.