Thiago Macieira

Hey Alex You're missing the point. That setting shouldn't exist at all, since libc already has the setting and it's system-wide. Example: ``` python import socket import pprint pprint.pprint(socket.getaddrinfo("chat.freenode.net", 7000,...

Indeed, while getaddrinfo(3) won't randomise, the DNS reply itself is already randomising the results. If nscd is running, then the DNS request isn't retried until TTL expires, so you get...

Right, it needs to respect the order from getaddrinfo. And it needs to try multiple servers returned from that function, not just the first one.

So, when are you guys going to fix this? It's been nearly 6 years.

Proper networking support should be at the basis of any networking application. I understand that irssi was not properly architected when it was first written, but we're in 2020 and...

#290 already exists. It's been reverted.

#290 has been working for me for 6 years. In this time, I have not seen any issues that didn't exist before with irssi. Irssi can't connect at all when...

It's what I just said: as far as I can tell it's always been like that, even before this change. So it's not a regression.

That option shouldn't exist. The order from `getaddrinfo()` must be obeyed.

If there is an option, the option should be a tri-state. For example, `resolve_prefer` of values "auto", "ipv6" and "ipv4", with the default being "auto" meaning no filtering or reordering.