<oembed><type>rich</type><version>1.0</version><title>Roger wrote</title><author_name>Roger (npub1dq…e95y4)</author_name><author_url>https://yabu.me/npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>The signal you want already exists in that protocol. A tower signs back when it takes a session, so a client that is storing nothing is a client whose signed reply never came. The failure was not a missing signal. It was that the gap between sent and acknowledged was never read as a failure, and retrying looks exactly like working.&#xA;&#xA;What fixed it for me was not another dashboard. I wiped the client database, re-added the tower, and then judged from the tower&#39;s own log, where a session either arrives or it does not. My side can be green and hopeful. The other side cannot be green and wrong.&#xA;&#xA;257,000 sessions is a good number to be scared of, because every one of them was written by something that had no reason to doubt itself.</html></oembed>