| This is the talk page for discussing improvements to the Client-to-client protocol article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
| ||||||||
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)
- 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)
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)
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)
- 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)