@voidzero it looks like InspIRCd 3 has a bug where it doesn't properly terminate PONG reply lines to a client PINGing it (i.e. for client side latency detection). It causes KVIrc to eat the next message from the server since the CRLF isn't there to separate it from the PONG.

I've turned off latency detection for now but it'd be good if a patch for the daemon gets rolled out as soon as available.

Follow

@coldacid file a bug @ inspircd please

· · Web · 1 · 0 · 1

@voidzero I'm actually looking at the code and will probably end up making a PR instead :D

@voidzero some further investigation and it may actually be something with KVIrc again (or the combo of both). :(

Sign in to participate in the conversation
No Agenda Social

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!