Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #228914
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] |
| Date | 2020-11-22 16:10 +0100 |
| Message-ID | <BdZa1-2hC-9@gated-at.bofh.it> (permalink) |
| References | <BdTeh-6Yv-7@gated-at.bofh.it> <BdYH0-1S7-5@gated-at.bofh.it> |
| Organization | occasionally |
On Sun, 22 Nov 2020 14:36:06 +0000 "Gareth Evans" <donotspam@fastmail.fm> wrote: > ...but what did I do wrong re thread hijacking? > > I understand that to mean changing the content of an existing thread, > as a quick google seems to confirm. Correct. > > I did delete the content and change the subject of an existing email, > which appears to me to create a new thread, rather than preserving > "conversation" links to the deleted content/subject. Yes. Which is how one usually hijacks a thread. The problem is that among the headers in emails is one that provides an identifier for the thread. So properly written mail user agents (MUA, your email client) will put the freshly hijacked message right into the thread anyway. Why this is wrong: * It interrupts the flow of the thread by interpolating a completely new subject in the middle of an existing thread. * It makes it harder for searchers later on to find your subject, hence to find any solution to your problem. * Starting a new email is usually easier than hijacking a thread, so why bother? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: rsync link corruption with -H and --link-dest <tomas@tuxteam.de> - 2020-11-22 09:50 +0100
Re: rsync link corruption with -H and --link-dest "Gareth Evans" <donotspam@fastmail.fm> - 2020-11-22 15:40 +0100
Re: rsync link corruption with -H and --link-dest Celejar <celejar@gmail.com> - 2020-11-22 15:50 +0100
Re: rsync link corruption with -H and --link-dest "D. R. Evans" <doc.evans@gmail.com> - 2020-11-22 16:20 +0100
Re: rsync link corruption with -H and --link-dest Andrei POPESCU <andreimpopescu@gmail.com> - 2020-11-22 16:00 +0100
Re: rsync link corruption with -H and --link-dest tomas@tuxteam.de - 2020-11-22 16:00 +0100
Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Charles Curley <charlescurley@charlescurley.com> - 2020-11-22 16:10 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-11-22 16:20 +0100
csiph-web