Yes, I don't like the "jumpy experience" either. In fact, it's plain painful. The idea of loading the initial nn bytes is good, but perhaps they could be displayed "tooltip"-style, when the user points at the link (use a DHTML layer or something with some script). Or, perhaps when a link is expanded, its entire subtree contents could be downloaded to the client. Expansions of further subtree elements is then handed on the client. For most discussion trees we're not talking about huge numbers of bytes so this seems workable. Heck, encode the discussion tree in XML and simply make an XSL style sheet to generate the client HTML... (ok, well, I guess not _everyone_ uses IE5 so its not _that_ simple).