{"version":"2.1.232","anchor":"keepalive-can-now-kill-a-silent-socket-but-nothing-turns-it-","canonical_anchor":"keepalive-can-now-kill-a-silent-socket-but-nothing-turns-it-","heading":"Keepalive can now kill a silent socket, but nothing turns it on","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/keepalive-can-now-kill-a-silent-socket-but-nothing-turns-it-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Keepalive can now kill a silent socket, but nothing turns it on\n\nDead WebSocket connections could be killed after a silence deadline, but nothing sets one.\n\n**What**\n\nThe WebSocket monitor's keepalive gained a deadline: if no message arrives within it, the socket is terminated rather than pinged again. The only keepalive configuration in this build supplies opening frames, the ping frame and an interval, and no deadline, so no connection currently uses this.\n\n**Evidence**\n\n`openFrames`\n\n- Area: Remote Control\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}