Hi,

> I don't think that programs should use IPv6 always when it's available.

IPv6 is supposed to replace IPv4, so using it when it is available is the way things are supposed to work.

> What if the IPv6 connection is tunneled with for example, Miredo? Then the connection might be slower and more unstable than usually.

The user will know that, as he set it up that way. If he notices any problems with it, he is free to set weechat to use IPv4 only.
IMHO that is not a very good point as the same might happen when connecting via a VPN or a proxy or whatever. It’s not IPv6 that is the problem in that case, but the general network setup. Disabling IPv6 generally because it might not work in some scenarios the user might have set up seems rather counterproductive to me…

> If people want to use IPv6 they should modify their system wide settings

People will have to do that sooner or later anyway, as IPv4 will be gone some day. IMHO it works the other way round: if people with an IPv6-enabled but broken setup do not want to do The Right Thing[TM] and fix their setup, they can modify their system to ignore IPv6.

IMHO disabling IPv6 by default will just have the effect of most connections to whatever service it may be being done via IPv4. The result will be that most service administrators think their users/clients do not have a working IPv6-setup and thus feel the need to keep the service on IPv4 alive as well. I don’t think that helps the migration to IPv6 at all, but rather puts stones in its way.

Thanks for reading and commenting!

Best regards

henk

Hi,

Most programs capable of using IPv6 prefer IPv6 where possible and fall back to IPv4 where IPv6 is not possible, i.e. no AAAA record exists but A record does e.g.
AFAICT weechat does not work that way but expects the user to tell whether IPv6 can be used. IMHO this is counterproductive as IPv6 won't automatically be used once it becomes available on a network, but only after the user changed the option again.
I don't see any advantage in this behaviour over falling back to IPv4, so I'd suggest renaming the setting to something like 'force_ipv4' so broken IPv6 setups can still be connected to. But as long as this option is unset, I'd expect weechat to behave as most other IPv6-capable applications and try IPv6 and fall back to IPv4 if IPv6 is unsuccessful.

Thank you for reading and considering!
Keep up the great work please, I really appreciate it!

henk