we get the incorrect message - so we just confirm it so Tunnelbroker will remove it from it's queue

invalid Tunnelbroker message - this could happen when the client has an older version and is not capable of processing recently added new messages, we can consider informing the user to somehow update the app, but for now, confirming is the best we can do

peerToPeerMessageHandler is designed so that it will not throw, we confirm regardless of success or error while processing

Should we add an in-code comment describing this scenario?

socket.current is falsy then this code shouldn't be executed as it's called only as a response to the received message - when socket.current is defined, ? is only to satisfy flow

that's not true - I need to update this diff, ignore my comment