Talk:Comparison of IRC clients

There should be a table for support of ipv6, utf8 and ssl too, and probably something about scriptability. I'll try to start adding some of it. Amaurea 05:45, 21 September 2005 (UTC)[reply]

The information here should probably be reflected on the individual pages for the irc clients. Perhaps a template for irc clients, with fields corresponding to the table sections here, would help organize that? Right now they use a general software template. Amaurea 09:28, 22 September 2005 (UTC)[reply]

It seems like there is more to DCC than I thought, enough to warrant its own table, perahps. These things could be covered as dcc subtypes: Normal, Resume, Passive, DCCServer, RDC, Reverse?, Secure. And for each of these there might be send, get, chat, fserve, whiteboard, it seems. I am not qualified to deal with all of that, but perhaps someone who knows more about this could take care of the dcc portion. Amaurea 11:06, 22 September 2005 (UTC)[reply]

Documentation of RDC protocol: http://www.sysreset.com/rdcc-protocol.txt 210.168.185.69 13:07, 22 September 2005 (UTC)[reply]

reverse spec: http://cvs.prbh.org/cgi/viewcvs.cgi/*checkout*/epic4/doc/DCC_REVERSE?rev=1.4

Is DCCserver and passive dcc really seperate things? mIRC seems to use what it calls DCCserver to do passive transfers. The ftp-like file sharing server mode is called fserver there, but perhaps it is called DCCserver other places? It would be nice if someone could clarify, perhaps making articles about Passive DCC (probably best done as a section of the dcc-article) and dccserver, if it really is something else. Amaurea 06:17, 30 September 2005 (UTC)[reply]

Xchat text mode ui

If you don't believe me that xchat doesn't have a usuable text mode ui, here's a screenshot: Image:Xchat-text.png If everyone insists on giving xchat a Yes for text ui, then irssi would need to get a Yes for GUI - there is some xirssi stuff on svn.

I don't believe the issue is usability; that's POV. X-Chat does come with both a GUI and CLI, therefore it seems reasonable to have both listed in the table. As for Irssi, I know very little about it, so I cannot comment about its entry. Michael 08:42, 29 September 2005 (UTC)[reply]

Sure it's pov, but I'd agree with above post that it is helpful to weight this in the feature comparison table. You wouldn't add an entry for telnet with Text UI: yes just because it can connect to IRC.84.16.231.42 20:20, 1 October 2005 (UTC)[reply]

I'd like to discuss this further, especially considering also debian's deicision to get rid of that useless xchat-text http://packages.debian.org/changelogs/pool/main/x/xchat/xchat_2.4.4-0.1/changelog 83.216.199.120 14:59, 18 November 2005 (UTC)[reply]

mIRC utf-8 conversion script

If there had been a mirc script capable of adding utf-8-support, then I agree that that should be listed as something else than "No", but the script mentioned only translates between the tiny charset mirc is set to use and utf-8. That is, it only supports a small subset of unicode at a time, and will not let you write, for example, Russian and Japanese at the same time. This isn't unicode-support, but I guess it might still deservee a footnote, since it atleast lets you participate in a limited manner in a utf-8-based channel. Amaurea 03:55, 20 October 2005 (UTC)[reply]

Operating system support

I thought we don't count cygwin emulated versions? then where could one get native BX and ircII Windows version?