To answer point 3: the chatterbox does not keep a long history by design.
If you want to get a little bit of context on a chatterbox conversion that you missed the start of, use cblast35.

This particular point has been discussed several times in the past.
For starters, see:

• No CB comment is serious, and should not be reproduced in a node without research
• Who owns your words? A resolution is needed.
• Is it a good idea to log the chatterbox?

Cheers.

BazB

Sorry, I've always wanted to say that. But we are. The Site Documentation Clan is renewing efforts at maintaining the docs, and I'm working on the Chatterbox FAQs. Meanwhile, you might want to check out turnstep's Chatterbox FAQ++ and ybiC's CB links.

Yes, the documentation seems to be going out of date. I just typed in Chatterbox Clients and bam, just like that, I got the list of chatterbox clients. But fullpage chat is not listed there. A little more searching brings up Other CB Clients, which does list fullpage chat. The two lists differ in a couple ways as well.

On a completelty related matter, why isn't the documentation kept as up-to-date as possible? If the answer is 'because there is too much to keep track of updating', then that tells me that the information isn't organized well-enough :) Considering that some information is posted in more than one place and each version is different leads to some disappointment...

      C:\>shutdown -s
      >> Could not shut down computer:
      >> Microsoft is logged in remotely.
    

Part of the problem is that the people working on the documentation aren't the same people making the code changes (for the most part). Then there's also the fact that a lot of documentation is somewhat duplicated, and it requires that a member of the documentation clan see a change and remember which documentation it will affect, and then change it all. So far as I know there is no general outline of all documentation--something I'd especially like to see written (but note that I've been inactive for the last couple of months due to moving).

Therefore, the best thing to do when you note some documentation which is out of date is to mention it to the site documentation clan. If you find that you're doing this a lot, you could request to join sdc.

So Long
blackstarr

displaytype=raw prevents the display of the nodelets.

Update: I stand corrected - theorbtwo++.

Note to self: must grok Everything source

---

If the information in this post is inaccurate, or just plain wrong, don't just downvote - please post explaining what's wrong.
That way everyone learns.

While that is true, it's woefuly incomplete, to the point of being misleading. Displaytype=raw not only disables the display of the nodelets, it disables the display of /everything/ except the actualy node contents. If you go to fullpage chat without the displaytype parameter, and view source, you'll notice where the content of the node would normaly be, there's a complete XHTML document. To be more exact, displaytype=raw tells the server to use the raw displaytype node, rather then the normal displaytype for that nodetype. Also avaliable is the edit displaytype (but not for that nodetype, for non-gods), the xml displaytype, and the print displaytype.

---

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).