Re: threadiquette - thread etiquette
by Corion (Patriarch) on Mar 18, 2008 at 14:37 UTC
|
Personally, I want nodes to have a common title because I track discussions and the level of replies through their title. I could be using Recently Active Threads to find nodes pertaining to a thread, but I'm not using it. Also I think that even RAT does not indicate at which level a reply sits. Which is why I ask authors not to erase the original thread title but to keep their additions or the relevant topic in parentheses. As an example, many nodes by tye have this.
I don't see that there is any technical need for preventing changing of the subject. The system does not need to be idiot-proof - completely erasing the title of a node rarely happens at all and there might be even a situation where I consider the complete eradication of the "level information" appropriate.
| [reply] |
|
|
Which is why I ask authors not to erase the original thread title but to keep their additions or the relevant topic in parentheses. As an example, many nodes by tye have this.
I tend to augment titles briefly with parenthetical comments because I very rarely make replies that completely change the subject from that of the thread. But I'm also happy to see node titles that are new but include a brief connection to the parent node title in parens.
I prefer the "Re^$x:" prefix for titles to be inviolate (I find it very useful information) but the less-desirable "New title (Re^5: Old title)" is at least unlikely to get thread ettiquitte explained to you (or your node simply considered for a title change). But really, leaving the "Re^$x:" in front scales better.
Note my use of the word "brief" more than once. I'd hate to see a proliferation of "New title (originally was Re^5: Some really long title that was way too long to begin with (including parenthetical asides for some strange reason))" titles. The point of the connection between titles of replies and their parent is for the benefit of humans so complete literalness is not a benefit.
Also note that I'd like to see more (useful) title decoration / adjustment. It is annoying, for example, to have an extended flame fest about orbital mechanics all under titles of "Re^$x: Best practices" (or whatever original subject lead to the severe tangent). And it would be nice to be able to more often tell subthreads apart just from the node titles (which is nearly all that is displayed in most places that list nodes -- search results, Newest Nodes, list of nodes by a specific author, links to nodes via id://NNN w/o the annoying "|this", etc.).
Also, in my experience, completely replacing the title almost always results in rather poor documentation as to the subject of the node. It leads to the title being more about how the node is different from the parent and discarding that part of the point of the node is the original topic that motivated it. So keeping the original title mentioned in a new title is a good idea even beyond the above considerations.
If you reply to a node titled "Re^$x: New title (old title summary)", feel free to drop the "(old title summary)" (or, even better, replace it with a brief clue as to how your reply relates to the new title).
| [reply] |
|
|
Recently Active Threads does show reply level through indentation, which is one of the reasons I prefer it to Newest Nodes. At least, that's how it works in the "Node Ancestors" view mode, which I believe is the default; other modes may vary, and I don't have time just now to explore them all.
| [reply] |
Re: threadiquette - thread etiquette
by kyle (Abbot) on Mar 18, 2008 at 15:02 UTC
|
I usually hang around on Newest Nodes. On that page, all the replies to everything are all jumbled together (ordered by time), but I can tell what thread they go in and what level they are at if they still have the default title. Your replies, on the other hand, have had their context removed.
It is easy enough to go to the node and see what its parent is, what thread it's in. Nevertheless, this is an extra step I'd have to take to find that out for your nodes, and not anyone else's.
| [reply] |
Re: threadiquette - thread etiquette
by halfcountplus (Hermit) on Mar 18, 2008 at 14:48 UTC
|
I presume Corion's compliant IS NOT because of some technical difficulty in maintaining the site (eg, with mailing lists one must take into account email clients). But as far as I know PerlMonks is not used as a mailing list.
That being the case, i wouldn't mind at all if people changed the subject in replies to be more informative, as metaperl did, since the nodes remain threaded together properly anyway. It would probably also be better for title searches about a specific topic (if they occur).
However, being quite new here and having learnt a recent lesson about "codequette" (Re^4: regexp for directory), i am willing to comply with a general consensus if people have strong feelings about it (leaving the Re: header as is).
(otherwise metaperl may start a trend...) | [reply] |
Re: threadiquette - thread etiquette
by jdporter (Paladin) on Mar 18, 2008 at 15:55 UTC
|
I generally agree with Corion and tye (and documented policy) on this matter — though I'm in the opposite camp as tye on the question of what should go in parentheses and where.
However, in this case, I refrained from raising the issue (considering the node for retitle) because it looked to me like a case of someone purposefully constructing a family of closely related nodes. Sometimes you want a set of topically autonomous nodes, but use the root + children structure to bind them together. Anyway,
it looked to me like a work in progress, so I thought I'd at least wait to see how it all settled down; maybe the sense of it would become apparent.
A word spoken in Mind will reach its own level, in the objective world, by its own wei ght
| [reply] |
|
|
though I'm in the opposite camp as tye on the question of what should go in parentheses and where.
On the first part, my node documented my approval for new or old title in parens (depending on whether the new title is a major shift in subject or just a minor annotation) so I guess this means that your position is neither new nor old title in parens. "and where"? So I guess you want the parens at the front of the title? That was widely frowned upon in the past and I agree (in hindsight).
But I actually guess that neither of the above guesses is correct.
| [reply] |
|
|
Or maybe I don't disagree with you. It's hard for me to tell,
since your post is so rambling.
At any rate, I think the pattern
"Re^n: New title (Old title summary)"
is a very, very bad idea, because it implies that the parent was
"Re^n-1: New title".
| [reply] |
|
|
Re: threadiquette - thread etiquette
by shmem (Chancellor) on Mar 18, 2008 at 19:55 UTC
|
- a system must be idiot-proof.
As soon as we get idiots to be idiot-proof, we might want to begin expanding that concept to other realms, and, lastly, apply it to systems.
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
| [reply] |
Re: threadiquette - thread etiquette
by eric256 (Parson) on Mar 19, 2008 at 14:55 UTC
|
Since the conversations here are threaded there is no real reason you can't change your title. If readers want to know how nodes are connected they can use the threaded view. If your node is so significantly different as to deserve a different subject then it realy isn't any lose of information if it shows up on Newest Nodes without the original subject (as it IS a new subject). So I think you are fine and your node titles have been fine by me. I believe this is one of those topics where the minority wins out normaly just because they are more vocal about the issue. The fact is, if they want to see relationship between nodes on NN then they should patch it to use the meta-data available in other parts of the node (not the subject) to determine and display those relationships. (or use the handy Recent Threads which does exactly that)
| [reply] |
|
|
Since the conversations here are threaded there is no real reason you can't change your title. If readers want to know how nodes are connected they can use the threaded view.
Yes, I'm inclined to agree. I dropped in here -- as I presume you did -- because I just received a nag message from "jdporter" (which I suspect was automatically generated), and I'm trying to figure out what the issue is here, and I still don't get it. It would appear that the system is broken (at least from the point of view of people who track "newest nodes"), and rather than fix the system they would rather bitch at us clueless newbies.
If you guys want a particular type of subject renaming style you should write up a style guide -- you know, like a SYNOPSIS section -- don't make us hunt around for examples of the approved ways of doing it.
You also might want to ponder that for several decades netiquette has strongly recommended changing subject names to reflect the content of a posting.
| [reply] |