Subject | Re: nospam still not admitting to an error (was: The closest we'll get to nospam admitting to an err |
From | Eric Stevens |
Date | 01/25/2016 04:23 (01/25/2016 16:23) |
Message-ID | <kp4bab9mfs7h9o81qhd8df125e6i5ga5h9@4ax.com> |
Client | |
Newsgroups | rec.photo.digital |
Follows | PeterN |
PeterNThen why do you keep needling nospam over and over about topics which have long since passed? I've felt like poking my oar in, and asking you why you keep doing it, on many ocasions but have restrained myself.
On 1/24/2016 7:29 PM, Eric Stevens wrote:Eric StevensPeterN
On Sun, 24 Jan 2016 16:58:55 -0500, PeterN <peter.new@verizon.net> wrote:PeterNEric Stevens
On 1/24/2016 4:26 PM, Eric Stevens wrote:Eric StevensPeterN
On 24 Jan 2016 09:48:07 GMT, Sandman <mr@sandman.net>wrote:SandmanEric Stevens
In article <jed8abthsp5obu1c85dc4f66b5idehgqi4@4ax.com>, Eric Stevens wrote:SandmanEric StevensSandmanEric StevensnospamSandman
it has a different subject heading.
So?
As far as the reader is concerned, you have changed the subject and it's now a different thread.
This again, Eric? You got your ass handed to you last time via screen shots, RFC's and a multitude of links.
That's your opinion.
No opinion included. You made an explicit statement back then that was disproven. No opinion needed, it was just factually incorrect.Eric StevensSandman
What was made clear was that there are two ways of looking at the subject and I use the conventional method of going by the header setting out the thread topic. You go by the chain of references which most people never see. You are welcome to your method just as 'we' are welcome to ours.
"I" don't have a "method". Threads are defined by the References header as per the RFC. This is why the vast vast VAST majority of news clients show it this way. You just happen to use the only known client that doesn't, and you have formed your own personal opinion based on its non-adherence behavior. Which is fine, you are free to your own opinions, but you shouldn't make explicit statements based upon them.
Your definition of threading is not compulsory. Section 2.2.5 of RFC 1036 https://www.ietf.org/rfc/rfc1036.txt states:
" User interfaces need not make use of this header, but all automatically generated follow-ups should generate the "References" line for the benefit of systems that do use it, ..."
Note the use of the word 'should' as opposed the use of 'must'. It's not compulsory.
We have been over all this before. There is no point in going over it again.
So why respond. WTF is the importance.
So why are you putting your oar in?
Because that type of BS drives away the people who have photography as a prime interest, and could be helpful to others.