Alexander Barton

Hi @ewired ! Without looking closer, I guess you have to test to send the `NAMES` and `TOPIC` to server-local clients only to make this work in a network with...

I'm hitting this with Mitogen 0.3.0-rc.0 and ansible 2.10.5 on Python 3.9.1 with a Debian 9 target (Python 3.5.3): ``` fatal: […]: FAILED! => { "ansible_facts": {}, "changed": false, "failed_modules":...

I definitely have to circle back to this PR, sorry for the loooooong delay @ewired !

I'm seeing this as well, VIM 9.0 on Linux. And thanks a lot, @jeebak, your workaround works great for me, too!

Closing this as duplicate of PR #287.

@thesamesam thanks for offering to help! But one goal of ngIRCd was to support really old systems, like old versions of Apple A/UX, AIX, SunOS, … some of which do...

Closing this bug report as **"won't fix":** this only affects the server-server protocol and can't happen during normal operation (without "faking" a buggy server). And the server-server protocol is "secure...

Closing this pull request as **"won't fix":** this patch doesn't fix the issue, and the issue only affects the server-server protocol and can't happen during normal operation (without "faking" a...

Not yet sure about this … Just for my understanding: you want to ensure that a client, which becomes `NJOIN`ed by a remote server/service, receives the same messages like when...

Thanks a lot for your contribution, @annmuor!