RE: hijacked threads

["jt" <jt@xxxxxx>]

Phillip,

Point is that most email readers can sort by the actual subject-line, so
it's a non-issue.  Or, rather, it's not the big issue it's being made out to
be.  It shows up in the archives as a problem, but who uses the archives as
the PRIMARY source of this information?  (Non-list-members.. anybody else?)
Now, if GMANE or whatever also shows this up as a problem, then mebbe GMANE
is a crappy info-distribution-system, also.


I recently started using the <new> button technique, btw, except where I
wanted to "bury" a post.  Even tho the posts arrive in my email
identically...  No, it's not hard to do but it's easier to screw up than
hitting a <reply> button.  Ever notice posts unintentionally going public or
to wrong list??  <Reply> button might save some-a those, and what have been
the consequences of intended-private mail going public??  Vs. the
consequences of posts getting threaded incorrectly??

(Which, again, is only necessary because a listserv is a LOUSY data store.
EVERY CMS I've ever seen HAS both a <reply to this> AND <new thread>
buttons, iirc.)

jt

| -----Original Message-----
| [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Philipp Rusch

| I don't quite understand your point :
|
| Where is the problem when you want to write on a new subject to go to
| the NEW button and to start writing from there, and then putting the
| midrange-l address in ? Is it that people want to save the effort to
| put in this "midrange-l@xxxxxxxxxxxx" that causes them to use the
| reply-to method ?
| This is ridiculous to me, when I knew about how threads are organized
| and how well it is to be followed after in your(my) own mail-folder(s),
| thread-wise sorting seems the most sophistidcated way for me.
|
| And I am not alone ...   sigh
|
| Philipp