Messages injected by a host are now treated as their own class, separate from messages from peer sessions.
What's wrong with this entry?
Inbound 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.
"host-injected"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Oversized cross-session messages fail with a specific error
Both mention cross
-
v2.1.236
Idle notices between sessions can carry the sender's permission mode, switched off here
Both mention cross
-
v2.1.236
Cross-session messages check who they are writing to
Both mention cross