whoops. don't know how that happened

I found a task that was created after this incident as an exact duplicate and merged it. As mentioned in the original post it was discovered on 1.32.0 (production) and is still present as of 1.33.0-rc.0 on a development install. I will be upgrading production to 1.33.0 soon but given the change log since rc.0 I do not anticipate any improvement.

the IRC account name on freenode doesn't matter, the ssh user is what must match that field

1559347684 00:08:04 [card] -!- stashbot [~stashbot@wikimedia/bot/stashbot]

I'm a complainer, not a hacker :D

surely this can be fixed after 10 years? :)

The original errors are gone, however new ones have appeared in their place:

I can redirect this channel to one more appropriate per consensus

still an ongoing issue

I am more familiar with oident but I believe either would be suitable

after speaking with a staffer today there is no issue adding an iline but the box needs to ensure an ident daemon is running for so each individual user with access has a unique identity for them or their bots. if staff see refusals they will easily up the limit for the host, but with a workaround in place they aren't likely to see such

You have no right to decline this, you are not the extension maintainer.

Yes, indeed. An all encompassing Wikimedia IRC project is the intention behind this :)

based on edit volume it should probably be flagged on meta as well