You'll notice
Useful3 Signal2
Cross-session messaging startup warnings now name the actual cause instead of always blaming sockets.
What's wrong with this entry?
Anonymous. No account, no email.
What
When cross-session messaging fails to start, the warning used to always blame the socket directory setup. It now reports the specific cause: a refused socket path, a bind failure, a failure to publish this session's peer key, or a problem after binding. The old text remains as the fallback when the cause is unknown.
Details
- A companion helper records the degraded cause and declines to overwrite an existing one when the key publish failed after the primary directory was already refused.
Evidence
its peer key could not be published
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.