Subject | Re: Will Tony apologize?? (was: Re: Colonial Photo & Hobby) |
From | Eric Stevens |
Date | 05/03/2014 23:35 (05/04/2014 09:35) |
Message-ID | <i0nam9181q0a1o31bd8n6pq19vs1qqu75o@4ax.com> |
Client | |
Newsgroups | rec.photo.digital |
Follows | Sandman |
Followups | Sandman (13h & 21m) |
SandmanThe form of my response was dictated by your question (" ... according to whom?") and and is a logical response. There was no request for data: hence none was given.
In article <6n38m9h8tl8vjqu9fglk80i1q9122mi9rj@4ax.com>, Eric Stevens wrote:SandmanEric StevensSandmanIt does so by default.Eric Stevens
It's got to have one setting or another and Forte have picked the one which makes the most sense.
Most sense... according to whom?
Those who want to keep their subjects separate.
What data are you basing your claim upon? "Those" isn't specific. Show me the data.
Not only have you changed the form of my question, you have carefully evaded answering it.SandmanNot "mixed", and certainly not "mixed up". In a logical and straight-up hierarchical view.Eric Stevens
So if I change the subject and launch off on a discussion of pyramids with others following you will be happy to have this displayed as part of your attempt to get Tony to apologise over some aspect Colonial Photo & Hobby?
If you reply to one of my posts, don't alter the references header, and change the subject and all quoted material and start talking about something completely different, I'd call you weird.
But if the thread is about travel photography, and the subthread has drifted to many different topics, and you hit reply, keep the quoted material and edit the subject line to reflect the current subject of this sub thread, I would most certainly want it kept as per the RFC.Whatever you think that means. Another evasive answer.
In the first scenario, it would be in the same thread, and it would be weird, but fortunately, people aren't usually that stupid to make what they themselves consider a new thread as a reply and thus a part of an old thread.You write as though you don't have much experience of Usenet. You seem to have even forgotten you have done it yourself.
So you keep saying, even though you have never been able to find text to confirm that idea.SandmanEric StevensSandmanNo. A lot of hand waving from you, and no actual "definitions" other than the ones I've provided.Eric Stevens
At the moment what makes a thread is in the eye of the beholder.
No.
Why not?
Because the RFC defines what is a thread.
Nor is it the answer to this question.SandmanEric StevensEric StevensSandman
I've already given you my view.
I've never asked for it.
Well, so what? Is this discussion you ramming your opinion down the throat of others while steadfastly ignoring what they say?
The RFC is not "my opinion".
Liar.SandmanEric StevensEric StevensSandman
It is likely that there is no single source definition.
Single, no. Multiple.
None of which you have been able to find.
All of which I have found, and shown you.
Not if you have aany brains.SandmanEric StevensEric StevensSandman
We are talking about display, not sequencing.
In a hierarchy, it's the same thing. And we've never talked about display. Perhaps you have wanted to divert it into display, but I've always talked abotu what constitutes a thread, and provided suport for my claims.
Not so.
Exactly so.SandmanEric StevensEric StevensSandman
What you are seeing are small branch threads.
I.e. *not* in chronological order.
They are, within the threads.
But that wasn't the claim. And they're not chronological within the thread either, since subthreads can disturb that.
What list are you talking about? It doesn't really matter: we were only two types of lists, threads and articles within threads. In either case they are both sorted chronologically.SandmanEric StevensSandman<>Is that what you call "chronologically"?Eric Stevens
Yes. The first message in a new thread goes to the top of the display, in reverse sequential order. That way I don't have to scan down through zillions of threads to find new ones. Messages within threads (once they have been expanded) are listed in sequential order so you can read them as a conversation, from beginning to end.
Which means that the list is NOT sorted chronologically. Most newsreaders work this way, few sort them chronologically.
Of course the list of threads is sorted chronologically, in reverse order.
I didn't say "list of threads". I said "the list". Why can't you read?
Here Jonas has snipped a block of thread to make what follows meaningless. I will save time by ignoring him.SandmanEric StevensEric StevensSandman
There is no indication of threading and subjects are all mixed up.
Since it's chronologically sorted.
Which is why a strict chronological sort of all messages is no use to the ordinary reader.
Which is my point. And a threaded view is not a list of chronologically sorted articles. Every top-level and then every branch in it is (hopefully) sorted, and usually descending on the top level and ascending in the tree.
I'm sorry. I don't do squink and arm waving. --SandmanEric StevensSandmanEric StevensSandman
People who read them. The 'References: ' header is fine until somebody branches off with a subthread.
I need some cites here from these people. Can you name them? This is an explicit claim from you, you know. You're saying that "people who read them" has determined that a thread is not defined by the References header.This will be regarded as hot air and hand waving (read: Bullshit) until you provide such support.Eric Stevens
You know my opinion.
No one has asked for your opinion, Eric. You made a claim about OTHER people here, not yourself.
That's bullshit, as you know very well.
It's still quoted above: "People who read them".
Stop referring to some imaginary "people" and show me some real data instead. You know, like I have.