On Tue, 4 Aug 2020 11:03:28 -0700, Mike Easter wrote:
> This is silly.
Hi Mike,
We're both reasonable & sensible logical & eminently rational people.
o If you see it as "silly" and I see it as "useful"... let's discuss why.
Regarding this telnet sequence in Ubuntu which I screenshotted as I did it:
o <
https://i.postimg.cc/kGG8W31b/telnetnntp01.jpg>
I think I understand why you assess that process as "silly"; but I don't
see any evidence that you included in that assessment key factors where I
consider it rather useful (particularly for the permanent Usenet archives).
After reading this detailed explanation, please see the ending question.
> The purpose of threading is generally so that if the people who are
> subscribed to a ng and reading it and are also sorting their messages by
> Reference will see the previous message/s in the associated References
> thread.
The references header, AFAIK, is for Usenet readers to "thread" properly:
o <
https://cr.yp.to/immhf/thread.html>
o References: <original@id> <message-4@id> <message-3@id> <message-2@id> <message-1@id>
"Writers use References to indicate that a message has a parent.
The last identifier in References identifies the parent.
The first identifier in References identifies the first article in the
same thread.
There may be more identifiers in References, with grandparents preceding
parents, etc. (The basic idea is that a writer should copy References
from the parent and append the parent's Message-ID. However, if there
are more than about ten identifiers listed, the writer should eliminate
the second one.)"
> When you reply/ one replies/ to a 'stale' message, whether the staleness
> is by several years or by several months, the 'purpose' of threading is
> lost to 'generic' readers.
Ah. I see. I think.
What you're saying is that, since the article I'm responding to is
"expired" in my news servers, that you assume that it's expired in all news
servers (which is a reasonable assumption on your part).
Hence, the article will shows up all alone anyway, for "most" people
(although some news servers go back far more than just 2018, but not mine).
Agreed.
o But, what other option do I have if I have UPDATED information?
a. I can post a new thread - which shows up as a new thread, or,
b. I can append to the old thread - which shows up as a new thread.
Notice there's no difference in either method, for most people, _other_
than the "Re:" in front of the subject line, as far as I can tell.
And yet, there _are_ key differences in the update method:
1. Those whose servers still have the thread, see it as threaded, and,
2. The all-important permanent archives see it as threaded <== important!
> That is, there are many different kinds of reasons that referenced
> articles which are not 'reasonably' fresh lose their threading 'vitality'.
And yet, in the permanent Usenet archives, they're threaded properly:
Which is my main purpose (always)...
o That is, my threads are _intended_ to be permanently UPDATED over time.
Given my threads are _intended_ to be useful components of the permanent
archive so that others may benefit (years into the future) by finding them
via a search - you seem to have not used that fact in your assessment of
"silly"... (AFAICT)
(e.g., search for the word "tutorial" in the archives for this ng:
o <
https://groups.google.com/forum/#!searchin/alt.os.linux/tutorial>
o <
https://alt.os.linux.narkive.com/search?q=tutorial>
and you'll find, oh, I'd better not say how many... or the number trolls
like Cybe(r) Wizard will be infesting this thread to death like Snit, so
let's just say you'll find some usefully UPDATED threads for sure). :)
> First; not everyone maintains a list of all of the articles in a given
> group for years and years.
I am trying to figure out why you assess permanent archives as "silly",
where I see you assume people save the archives on their own system.
I don't.
Dejagoogle _is_ a permanent archive - and - it's web searchable!
o <
http://tinyurl.com/alt-os-linux>
All the known permanent Usenet archives will have the UPDATED article:
o <
http://alt.os.linux.narkive.com>
Hence, we're working off of different assumptions:
a. You seem to assume people save the archives on their own machine
b. I assume the archives are saved by dejagoogle and other domains
> Second; not everyone threads by References,
> some people choose to thread by subject (which is normally very similar
> to references) plus chronology and choose the orderliness of chronology
> over the references tree-like function (as opposed to chronology), which
> is the way I do it.
I agree with you, and, in fact, essentially, Marek wrote my "newsreader",
which can randomly call any one of six thousand VPN servers but which
doesn't "thread" all that much either (it's pretty much LIFO).
Nonetheless, the _permanent_ Usenet archives _do_ thread.
> In the case of your article which has expired at neodome; that article
> was posted in 2018 Dec. That is VERY stale. Neodome's articles go back
> less than a year.
Yup. I agree.
However, dejagoogle goes way back, as does
narkive.com, which are the two
"permanent" (for as much as anything is permanent on the net anyway)
archives that I'm aiming to UPDATE.
> While the 'exercise' which you are trying to accomplish w/ telnet can be
> performed, its value is virtually nil to anyone but you.
Mike... I think I figured out _why_ you assess the effort as "silly"; but I
also think that you didn't take into account the key reasons that I assess
it as useful.
You need to bear in mind I'm not on Usenet for idle "chat" and that most of
the threads I participate in (likely over 98%) are threads that I started.
I don't generally participate in other peoples' threads, as my threads are
usually solving problems. None are idle chitchat.
An example of a thread that is intended to be a useful thread might be, oh:
o Tutorial for setting up Ubuntu as a Windows Subsystem for Linux WSL in Windows 10
<
https://groups.google.com/forum/#!topic/alt.comp.freeware/rOT8xBWo9dk>
Or, for example...
o Tutorial: How to enable the Telnet Client in Windows 10
<
https://groups.google.com/forum/#!topic/alt.comp.freeware/pEhuvzzFBTU>
Those threads are intended to be _permanent_ references which I update as
new information comes in.
If I don't update those threads, and if I want them to still be permanent
and useful archives, how _else_ do you suggest I update those topics?
--
Two kinds of people are on Usenet: those who add value & those who chat.