Version: 0.17 (using KDE KDE 3.3.0) Installed from: SuSE RPMs OS: Linux Some clients support CTCP sounds, which allow a sound to be played on a channel. The way it works is as follows: sender types /ctcp #channelname sound abc.wav clients make a DCC GET request for abc.wav clients play abc.wav on receiving end. All this happens seamlessly on the receiving end.
I think that having the clients do an automatic dcc-get would get quickly annoying to the ctcp'er. Imagine what would happen if someone did this in a channel of 50 or so, and 25 of them don't have the sound.
Useless.
Useless? Yes. Entertaining? Highly. mIRC is probably the only client around (that I know of) that supports ctcp-sound, and lots of people take advantage of it. The sounds add another dimension of communication and entertainment that regular text can't bring. And as opposed to this dcc-get request silently, mIRC supports using the format of "!<me> <sound>" in a PRIVMSG to initiate a dcc-send of the sound. Many people find this annoying, so it shouldn't be enabled by default.