Re: [SLE] Does SuSE deviate from "standards"
On Mon, Jun 09, 2003 at 10:34:28AM +0100, Ted Harding wrote:
On 09-Jun-03 Patrick Shanahan wrote: And *your* question has what to do with the thread "Enabling /home/*/public_html to be seen in my web page" which you have responded?
I think Patrick and others are being unduly harsh with Zach Smith's alleged "hijacking" of a thread. When I received his message it had simply the Subect:
[SLE] Does SuSE deviate from "standards"
However, from the headers in his message I see:
In-Reply-To: <3EE3EF56.30404@okstate.edu> References:
<20030608214341.GU5294@wahoo.no-ip.org> <3EE3DEB8.9080302@okstate.edu> <20030608233346.GY5294@wahoo.no-ip.org> <3EE3EF56.30404@okstate.edu>
What seems to have happened here is that Zach sent a new message to the list by "reply"ing to an existing one (perhaps to save typing/looking up the list address), then clearing everything he could see (including the subject) and creating a totally new message (or so it seemed) -- but not realising that hidden below the surface there might be headers that referenced other messages in a thread.
Hence _some_ people whose mail reader can identify the thread from these headers (which presumes that they have already retained other messages from the thread) will get the impression that the thread has been changed.
But in Zach's message and headers as received by me there is no mention of "Enabling /home/*/public_html to be seen in my web page". So presumably anyone who saw that in the "Subject:" line as received by them had it put in there by their own system.
Right or wrong ... ?
Ted.
On Mon, 9 Jun 2003 5:23 EST, Jerry A!
: : : What seems to have happened here is that Zach sent a new message to the : list by "reply"ing to an existing one (perhaps to save typing/looking up : the list address), then clearing everything he could see (including the : subject) and creating a totally new message (or so it seemed) -- but not : realising that hidden below the surface there might be headers that : referenced other messages in a thread. : : Hence _some_ people whose mail reader can identify the thread from these : headers (which presumes that they have already retained other messages : from the thread) will get the impression that the thread has been changed. : : But in Zach's message and headers as received by me there is no mention : of "Enabling /home/*/public_html to be seen in my web page". So presumably : anyone who saw that in the "Subject:" line as received by them had it : put in there by their own system. : : Right or wrong ... ?
I'm guessing that many of the people that had issue (and rightfully so) were using mutt or MH, which correctly track via "References" and the Message-Id's that the header contains. The text of the subject may have been changed, but for all intents and purposes, the mail still "said" that it was part of a previous thread.
For further clarification, I suggest checking out RFC 2822.
--Jerry
Jerry and Ted, As you well know, the problem isn't _some_ people whose mail reader can identify the thread from these headers. (those using mutt or MH) It is also the fact that the SuSE mailing list archieves get messes up. http://lists.suse.com/archive/ And I don't understand all the permutations, but I do know with the Netscape email program I use if I hit reply, edit my text, change the "To" line and modify the Re line, i can break the thread on the archieve dispite the "hidden" headers --- and that is not what I wanted to do with my earlier reply to Zach Smith entitled: RE: [SLE] Does SuSE deviate from "standards" (long) BTW -- Zack did apologize -- but he broke the thread too. Zack -- what email program are you using ??? Was it mutt or MH ??? __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
.. I beg forgiveness, I originally posted this mistakenly to
GarUlbricht7@netscape.net ..
* GarUlbricht7@netscape.net
Jerry and Ted, As you well know, the problem isn't _some_ people whose mail reader can identify the thread from these headers. (those using mutt or MH)
It is also the fact that the SuSE mailing list archieves get messes up. http://lists.suse.com/archive/ And I don't understand all the permutations, but I do know with the Netscape email program I use if I hit reply, edit my text, change the "To" line and modify the Re line, i can break the thread on the archieve dispite the "hidden" headers --- and that is not what I wanted to do with my earlier reply to Zach Smith entitled: RE: [SLE] Does SuSE deviate from "standards" (long)
But you would not *break* the thread if you would delete the following
headers from your reply before posting:
References:
On Mon, Jun 09, 2003 10:10:27 at 10:10:27AM -0500, Patrick Shanahan (WideGlide@FastMail.fm) wrote:
Threading is very important and desirable in a *support* list, especially one which is archived/searchable. It provides the means to find answers to problems immediately, without waiting for someone on the list to repeat a previously discussed issue, and, perhaps, flame you for not attempting the research yourself. Broken threads make that research *very* difficult. It's like someone tearing several random pages from a research book and placing them in different locations or just destroying them.
Have you ever read a mystery book and found that the last 3 or 4 pages were missing?
Amen to that! Thanks to Patrick for reminding the real reasons to avoid and fight broken threading!! Ciao, Marco Fioretti -- Marco Fioretti m.fioretti, at the server inwind.it Red Hat for low memory http://www.rule-project.org/en/ There is more to life than increasing its speed. -- Mahatma Gandhi
On Monday 09 June 2003 11:50, M. Fioretti wrote:
On Mon, Jun 09, 2003 10:10:27 at 10:10:27AM -0500, Patrick Shanahan (WideGlide@FastMail.fm) wrote:
Threading is very important and desirable in a *support* list, especially one which is archived/searchable. It provides the means to find answers to problems immediately, without waiting for someone on the list to repeat a previously discussed issue, and, perhaps, flame you for not attempting the research yourself. Broken threads make that research *very* difficult. It's like someone tearing several random pages from a research book and placing them in different locations or just destroying them.
Have you ever read a mystery book and found that the last 3 or 4 pages were missing?
Amen to that! Thanks to Patrick for reminding the real reasons to avoid and fight broken threading!!
Ciao, Marco Fioretti
And thanks to all of you who waste more bandwidth trying to keep threads in alignment and NOT on the main purpose of this list...........
-- Marco Fioretti m.fioretti, at the server inwind.it Red Hat for low memory http://www.rule-project.org/en/
There is more to life than increasing its speed. -- Mahatma Gandhi
On Mon, Jun 09, 2003 11:49:54 at 11:49:54AM -0400, Bruce Marshall (bmarsh@bmarsh.com) wrote:
And thanks to all of you who waste more bandwidth trying to keep threads in alignment and NOT on the main purpose of this list...........
I don't know about Patrick, but personally, I waste much more (PAID per MINUTE!) bandwidth and reading time on broken threads than because of spam. DAILY, and for the very same reasons that Patrick explained! Spam is easily stoppable with the right setup, info hidden by broken threads (=human stupidity/ignorance/carelessness/whatever) can be stopped (even theoretically) only explaining why it is bad. Making helpful information easily reachable, ie keeping threads in alignment, should be the very *first* effort, if not the main purpose, of any support list. Of course, this is the last list message on this issue by me (until someone screws it up again :-) ). Ciao, Marco Fioretti -- Marco Fioretti m.fioretti, at the server inwind.it Red Hat for low memory http://www.rule-project.org/en/ I doni ricevuti dal Padreterno, servono se utilizzati: chi li contempla gode, ma chi ne fa uso probabilmente aiuta altri a godere.
On Monday 09 June 2003 18.10, M. Fioretti wrote:
Of course, this is the last list message on this issue by me (until someone screws it up again :-) ).
If someone does, and you feel the irresistible urge to correct it, do it *off list*. There is absolutely no reason to waste more bandwidth by creating yet another thread on netiquette. History has proven that it doesn't do any good anyway. The only person likely to read it and be corrected by it is the person you're flaming, so you'll get the *exact* same result by correcting him off list
On Monday 09 June 2003 18.10, M. Fioretti wrote:
Of course, this is the last list message on this issue by me (until someone screws it up again :-) ).
If someone does, and you feel the irresistible urge to correct it, do it *off list*. There is absolutely no reason to waste more bandwidth by creating yet another thread on netiquette. History has proven that it doesn't do any good anyway. The only person likely to read it and be corrected by it is the person you're flaming, so you'll get the *exact* same result by correcting him off list
Actually I think the correction should be made on list. Until somebody corrected somebody else about thread-breaking, I had done it a few times myself. I was educated by reading the thread that broke out between the other guy and the irritated "broken thread" police. Posting on list can be educational about the issue. -Jim-
On Mon, Jun 09, 2003 09:32:09 at 09:32:09AM -0700, Jim Norton (jrn@oregonhanggliding.com) wrote:
Actually I think the correction should be made on list. Until somebody corrected somebody else about thread-breaking, I had done it a few times myself.
PRECISELY: from a private reply on the same subject: The reason to immediately reply *on* the list as soon as you see someone screwing threads exists. The real damage (in the sense specified by Patrick, ie hiding useful info) is *not* done by the *single* person that, often unvoluntarily, hijacks the original thread. It is done by the five, ten, fifteen knowledgeable guys that, invariably, *answer* to that badly placed question, hiding the *solution*. They are the ones that must be stopped and teached better: since they are many, and one doesn't know them in advance, it *is* necessary to say ASAP to them all, and only once, "please don't answer until the OP starts a new thread": the only way to do it is answering on the list. Ciao, Marco Fioretti -- Marco Fioretti m.fioretti, at the server inwind.it Red Hat for low memory http://www.rule-project.org/en/ Excuse me for being greedy, but I want freedom and good government. Both a flourishing economy and a well-cared-for earth. A society that is diverse and communal.. that offers both privacy and accountability. One that can afford a big conscience, along with lots of neat toys. -- David Brin -- The Transparent Society
* Anders Johansson
On Monday 09 June 2003 18.10, M. Fioretti wrote:
Of course, this is the last list message on this issue by me (until someone screws it up again :-) ).
If someone does, and you feel the irresistible urge to correct it, do it *off list*. There is absolutely no reason to waste more bandwidth by creating yet another thread on netiquette. History has proven that it doesn't do any good anyway. The only person likely to read it and be corrected by it is the person you're flaming, so you'll get the *exact* same result by correcting him off list
There are *many* repeated threads on subjects other than netiquette that could be construed as to 'waste more bandwidth'. At least this action has the potential to improve the list environment. Why would only the concerned party read the post? Why is providing information *flaming*, even if it is instructional? In the case you present, I believe that you reach false conclusions. -- Patrick Shanahan Please avoid TOFU and trim >quotes< http://wahoo.no-ip.org Registered Linux User #207535 icq#173753138 @ http://counter.li.org Linux, a continuous *learning* experience
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I broke a thread the other day...now I have to figure out where to find a button that matches the rest on my shirt. (just trying to bring a little humor into this, so it don't get blowed all out of proportion). John - -- I needed fresh bugs for my SuSE gecko, and Linux penguin. So I went out and caught this huge ugly blue and red and green and yellow butterfly. They won't need fresh food for 3 months now. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+5Rm8H5oDXyLKXKQRAjhcAKCh6DEuMJyawf/MLQKghFQU90xmqwCeMyPm BvPivKzwz1vegvHLFdNbkQU= =/qyM -----END PGP SIGNATURE-----
participants (8)
-
Anders Johansson
-
Bruce Marshall
-
GarUlbricht7@netscape.net
-
John
-
jrn@oregonhanggliding.com
-
M. Fioretti
-
Patrick Shanahan
-
Zach Smith