Well, the title says it all, I guess. IPv6 shouldn't be really hard to implement I think, and it's a really nice protocol, already being used, too. Besides, can't hurt to be prepared for the future... It also gives the people with IPv6 access on an IPv6-supporting server a certain 'leetness' factor ;p, as your IPv6 address shows when you enter a channel and when someone whois-es you ^_^. Wow, doesn't that make you cool or what? Hehehe...
UTF-8 may be a bit harder (then again, it may not), but unicode is becoming more and more commonly used, and very useful at that. Some friends of mine have an IRC server running on Linux, and they have all set UTF-8 as codepage, but unfortunately my OS (Windows XP) does not support that, and neither does mIRC, while at least one should for me to be able to use it. UTF-8 support in mIRC would be a much better alternative to setting the Windows' codepage to JIS for example, as it does not change the system locale or anything, and also supports a wider range of characters. And then maybe I can finally understand what they're typing outside of ASCII (or well... at least try to understand
), and type accented characters etc. without getting a 'we don't understand windows-extended ascii' remark.
XChat2 can already do both, but well, to be honest... it sucks
. Anyways at the moment neither are being supported or used very well, but mIRC being a big player on the IRC market it could change for the better. I think that right now especially the lack of UTF-8 support in mIRC is holding back people from using it.
~Grauw