This is another thing there appear to be differences of opinion all over on.. Which means it'll probably end up configurable , :)

For the record, I neither need nor use the ID or nodetype in the node headers, Id also prefer barts suggestion, and add a 'displaycode' or something to it. (which I would like at least for scratchpads, where the link looks kinda out of place, but I couldnt think of a better way to do it).

Although, I have occasionally needed to know the nodetype, and scrolled to the bottom to find it. I'd still prefer both ID and nodetype in the editors nodelet, which is where I use them.

I can see the argument that it would be nicer code-wise to have the stuff in one place, but I just dont think its practical usage-wise. Editors need them near editing tools/links, pmdevs near pmdev stuff etc. pp. Having them in Node Status is nice, but thats not on every page, whereas editor/pmdev nodelets are..

Just to recap on the Node Status Nodelet. Its point was (and still is, IIRC), to show users < level 5 the information that the approval nodelet had, such as if their node had been considered/approved and so on. Removing this nodelet should not be an option.

Adding another nodelet just adds to the clutter, IMO. I already have so many that I cant have them all within sensible reachable range or proximity of each other (even with CB and other users turned off now)

Hmm, someone should implement the 'rollup' nodelet feature properly. (For those not in the know, its possible to make the nodelet content 'disappear' and just show its title, saving space when not in use.. Except this 'feature' has no usable GUI..)

C.