Talk:Client-to-client protocol

Computing: Networking Stub‑class

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by Networking task force.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

A NOTICE is used to reply to a PRIVMSG, but what is used to reply to a NOTICE? The dcc resume protocol consists of a send offer, a resume reply, and then an acknowlegement. Would this be PRIVMSG, NOTICE, NOTICE, or PRIVMSG, NOTICE, PRIVMSG, or something else? Amaurea 12:52, 20 October 2005 (UTC)[reply]

You are never supposed to have anything automatically reply to a NOTICE. Also, you want to know about the "DCC resume protocol", not the CTCP protocol, so check that out instead. Oddity- 07:19, 8 August 2006 (UTC)[reply]

Is this article still a stub? It is pretty short, but I can't think of anything else to add, unless we are to specify how ctcp escapes work, which I think may be a tad too technical. The german version is longer, but that is just because it is more verbose, and I can't see anything of value to incorporate here. Amaurea 12:11, 2 January 2006 (UTC)[reply]

If you don't see anything else can be added, then remove the stub template from it. --Spook ^{(my talk | my contribs)} 10:46, 28 February 2006 (UTC)[reply]

It can definitely be expanded. It could include a list of conforming clients, what is most commonly implemented out of the spec (i.e. ACTION is the most common, escapes are (unfortunately) very uncommon, and sound is even less common). It can describe what the standard CTCP character is, it can describe the typical PRIVMSG/NOTICE pattern, it can go into standard uses (i.e. Lag pings, are-you-really-there pings, VERSION pings, etc). Yes, this is still a stub. — EtherealFlaim 09:40, 26 May 2007 (UTC)[reply]

PRIVMSG rule

"Since a PRIVMSG as a rule should not generate another PRIVMSG as a reply," Why not?

This page has no cited sources at all. 200.68.94.105 (talk) 14:18, 3 March 2009 (UTC)[reply]