I love the banter between the dozen or so people that make up most of
these chats, but it seriously clutters up comp.os.linux.misc and alt.comp.os.windows-11 to the point that they are practically unusable
for the technical questions that they are supposed to serve, and for
which I also do occasionally need them.
I *really* wish people would move all the wildly off-topic chatter to alt.unix.geeks *as soon as they go off-topic. I also with they would
change the subject line when the follow-up becomes completely unrelated
to what the subject line says.
If you don't know how to do it:
Start a followup. Change the subject line to what you want it to be.
Add a "Followup-To: alt.unix.geeks" header.
I occasionally try to move a thread over, but usually I don't find such
a thread until 20+ messages down, and by then it seems to be too late to move it, because it has already split into 5 or more branches.
BTW, now we're 'complaining', *my* pet peeve is people quoting endless cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
I love the banter between the dozen or so people that make up most of
these chats, but it seriously clutters up comp.os.linux.misc and >alt.comp.os.windows-11 to the point that they are practically unusable
for the technical questions that they are supposed to serve, and for
which I also do occasionally need them.
I *really* wish people would move all the wildly off-topic chatter to >alt.unix.geeks *as soon as they go off-topic. I also with they would
change the subject line when the follow-up becomes completely unrelated
to what the subject line says.
If you don't know how to do it:
Start a followup. Change the subject line to what you want it to be.
Add a "Followup-To: alt.unix.geeks" header.
I occasionally try to move a thread over, but usually I don't find such
a thread until 20+ messages down, and by then it seems to be too late to >move it, because it has already split into 5 or more branches.
I *really* wish people would move all the wildly off-topic chatter to alt.unix.geeks *as soon as they go off-topic. I also with they would
change the subject line when the follow-up becomes completely unrelated
to what the subject line says.
BTW, now we're 'complaining', *my* pet peeve is people quoting endless cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
[snip]
BTW, now we're 'complaining', *my* pet peeve is people quoting endless
cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
Serious undersnippage, which I find much worse than top-posting.
On 4/3/2026 8:31 PM, Lars Poulsen wrote:
I *really* wish people would move all the wildly off-topic chatter to
alt.unix.geeks *as soon as they go off-topic. I also with they would
change the subject line when the follow-up becomes completely unrelated
to what the subject line says.
New comers will not know about alt.unix.geeks, and instead head to Linux advocacy groups. Even old-timers might forget. :)
On 4/3/26 12:05, Mark Lloyd wrote:
[snip]
BTW, now we're 'complaining', *my* pet peeve is people quoting endless >> cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
Serious undersnippage, which I find much worse than top-posting.
But if you DO trim then the OP will scream about
you undermining their "context", what they see as
relevant info :-)
Sorry, no pleasing everyone.
c186282 <c186282@nnada.net> wrote:
On 4/3/26 12:05, Mark Lloyd wrote:
[snip]
BTW, now we're 'complaining', *my* pet peeve is people quoting endless >>>> cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
Serious undersnippage, which I find much worse than top-posting.
But if you DO trim then the OP will scream about
you undermining their "context", what they see as
relevant info :-)
Note that I was (mostly) complaining about *cumulative* quotes, often
many levels 'deep'.
As to people screaming about snipping relevant info: Yes, that kind of snipping happens and IME is often intentional and hence dishonest. A
dead giveaway is often that they don't mark what they snipped, resulting
in misrepresenation and lying by ommision.
I always use snip marks ('[...]') and as you can see, Mark did the
same.
Moral: One *can* behave responsibly and honestly on Usenet.
Sorry, no pleasing everyone.
But one can please (the majority of) the Good Guys and Girls.
[Followup to alt.unix.geeks ignored.]
Lars Poulsen <lars@beagle-ears.com> wrote:
I love the banter between the dozen or so people that make up most of
these chats, but it seriously clutters up comp.os.linux.misc and
alt.comp.os.windows-11 to the point that they are practically unusable
for the technical questions that they are supposed to serve, and for
which I also do occasionally need them.
I *really* wish people would move all the wildly off-topic chatter to
alt.unix.geeks *as soon as they go off-topic. I also with they would
change the subject line when the follow-up becomes completely unrelated
to what the subject line says.
I think it's not logical if Windows users, who are a part of said audience, have to move to a Unix group.
Anyway, moving threads to another group hardly ever - if ever - works.
On 2026-04-03 16:45, Frank Slootweg wrote:
[Followup to alt.unix.geeks ignored.]
Lars Poulsen <lars@beagle-ears.com> wrote:
I love the banter between the dozen or so people that make up most of
these chats, but it seriously clutters up comp.os.linux.misc and
alt.comp.os.windows-11 to the point that they are practically unusable
for the technical questions that they are supposed to serve, and for
which I also do occasionally need them.
I *really* wish people would move all the wildly off-topic chatter to
alt.unix.geeks *as soon as they go off-topic. I also with they would
change the subject line when the follow-up becomes completely unrelated
to what the subject line says.
I think it's not logical if Windows users, who are a part of said
audience, have to move to a Unix group.
It is an empty group, there were no messages there for years. Just a convenient place by agreement, instead of creating a new group.
Anyway, moving threads to another group hardly ever - if ever - works.
It does, albeit slowly :-)
I only monitor 2 groups, Windows and Android, and both have been a bit dead
recently.
New comers will not know about alt.unix.geeks, and instead head to Linux
advocacy groups. Even old-timers might forget. :)
Not if you do what I just did
[Followup to alt.unix.geeks ignored.]
Lars Poulsen <lars@beagle-ears.com> wrote:
I love the banter between the dozen or so people that make up most of
these chats, but it seriously clutters up comp.os.linux.misc and
alt.comp.os.windows-11 to the point that they are practically unusable
for the technical questions that they are supposed to serve, and for
which I also do occasionally need them.
I *really* wish people would move all the wildly off-topic chatter to
alt.unix.geeks *as soon as they go off-topic. I also with they would
change the subject line when the follow-up becomes completely unrelated
to what the subject line says.
I think it's not logical if Windows users, who are a part of said
audience, have to move to a Unix group.
[Followup to alt.unix.geeks ignored.]
pee
In comp.os.linux.misc Carlos E.R. <robin_listas@es.invalid> wrote:
On 2026-04-03 16:45, Frank Slootweg wrote:
I think it's not logical if Windows users, who are a part of said
audience, have to move to a Unix group.
It is an empty group, there were no messages there for years. Just a
convenient place by agreement, instead of creating a new group.
The sad thing is occasionally I peek into the huge threads in comp.os.linux.misc that I start always marking as read once
they go too OT, and discover about 500 posts down people have
actually started talking about something I'm interested in. Often
I'm subscribed to a group dedicated to that topic which has been
dead for years, but here people _are_ talking about it in a place
I'm unlikely to find, and where I won't reply because it only
commits me to wading through hundreds more OT posts later to find
the responses (plus it's just contributing to the problem for other
people).
At least it would be more organised if such talk was separated from
Linux questions, but it'd be real nice if people actually started
using groups relevent to the topics again. A hopeless dream, I
know.
On 3 Apr 2026 14:45:38 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
[Followup to alt.unix.geeks ignored.]
<<snipped>>
pee
<<snipped>>
Yeah, and then there's those who don't quote enough of the previous
post, or who don't quote *any* of it so you have to retrieve it,
sometimes using their Headers to find out *which* post their reply
is referring to.
Then they rant on and on for aeons. Or, even worse, make extremely
short, terse, curt comments that mean absolutely nothing without
context.
That's bad, too.
Also, "top posters". Top posters are just evil.
But, as I said in a.c.o.win-10, I'm not commenting any more. So I
never said that. :)
In my 40 years of Usenet, the number of people who have tried to make it
At least it would be more organised if such talk was separated from
Linux questions, but it'd be real nice if people actually started
using groups relevent to the topics again. A hopeless dream, I
know.
"A hopeless dream' .... as long as no one tries to MAKE IT happen!!
Sure, you're NOT everyone's keeper but you ARE one persons keeper!!
On 2026-04-03, Frank Slootweg <this@ddress.is.invalid> wrote:
BTW, now we're 'complaining', *my* pet peeve is people quoting endless
cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
And then using that as a justification for top-posting. Grrr...
I can't help but recall that Windows NT does (or at least did) come out
of the box with a partial POSIX subsystem :-P
On 2026-04-03 11:10, Charlie Gibbs wrote:
On 2026-04-03, Frank Slootweg <this@ddress.is.invalid> wrote:
BTW, now we're 'complaining', *my* pet peeve is people quoting endless >> cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
And then using that as a justification for top-posting. Grrr...
TBH, it depends a lot on which newsreader you are using.
ThunderBird makes it easy, /slrn/ makes it next to impossible.
On 3 Apr 2026 14:45:38 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
[Followup to alt.unix.geeks ignored.]
<<snipped>>
pee
<<snipped>>
Yeah, and then there's those who don't quote enough of the previous
post, or who don't quote *any* of it so you have to retrieve it,
sometimes using their Headers to find out *which* post their reply is referring to.
Also, "top posters". Top posters are just evil.
But, as I said in a.c.o.win-10, I'm not commenting any more. So I
never said that. :)
Lars Poulsen <lars@beagle-ears.com> wrote:
On 2026-04-03 11:10, Charlie Gibbs wrote:
On 2026-04-03, Frank Slootweg <this@ddress.is.invalid> wrote:
BTW, now we're 'complaining', *my* pet peeve is people quoting endless >> >> cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
And then using that as a justification for top-posting. Grrr...
TBH, it depends a lot on which newsreader you are using.
ThunderBird makes it easy, /slrn/ makes it next to impossible.
It doesn't matter if it's easy/easier or hard for the multitude of
(human) readers, the *poster* should spent the effort to make it easy
for *all* readers. Why should umpteen readers suffer, just because a
poster (i.e. *one* person) can't be bothered to do the right thing?
In article <10qrd58.1dig.1@ID-201911.user.individual.net>,
Frank Slootweg <this@ddress.is.invalid> wrote:
Lars Poulsen <lars@beagle-ears.com> wrote:
On 2026-04-03 11:10, Charlie Gibbs wrote:
On 2026-04-03, Frank Slootweg <this@ddress.is.invalid> wrote:
BTW, now we're 'complaining', *my* pet peeve is people quoting endless
cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
And then using that as a justification for top-posting. Grrr...
TBH, it depends a lot on which newsreader you are using.
Just to clarify, the "it" in the previous sentence is referring to the practice of not top posting.
And yes, most "modern" (and/or GUI) newsreaders default to MS style (i.e., top posting).
ThunderBird makes it easy, /slrn/ makes it next to impossible.
This surprises me. I'd have thought exactly the opposite would be true,
but I've never used either one.
It doesn't matter if it's easy/easier or hard for the multitude of >>(human) readers, the *poster* should spent the effort to make it easy
for *all* readers. Why should umpteen readers suffer, just because a
poster (i.e. *one* person) can't be bothered to do the right thing?
I think you lost the thread here. I don't see how the previous poster's words could be interpreted as having to do with the ease of reading.
Of course, we are talking about the ease of posting. And, of course, if software makes it difficult (or impossible) to do something, users of that software will shy away from (and not make any effort to correct the
problem) using that functionality. It is just the way the world works.
John <Man@the.keyboard> wrote:
On 3 Apr 2026 14:45:38 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
[Followup to alt.unix.geeks ignored.]
<<snipped>>
pee
<<snipped>>
Yeah, and then there's those who don't quote enough of the previous
post, or who don't quote *any* of it so you have to retrieve it,
sometimes using their Headers to find out *which* post their reply is
referring to.
Well, those people should get a *real* newsreader! :-)
BTW, I didn't know that Forte Agent doesn't have a 'go to parent' function! In my newsreader (tin), I just press 'u' (up the thread) to
display the parent post.
Frank Slootweg wrote:There *is* a way ...
I didn't know that Forte Agent doesn't have a 'go to parent'
function! In my newsreader (tin), I just press 'u' (up the thread) to
display the parent post.
Thunderbird doesn't have a button or key to do that. You have to
visually find it in threaded mode. And if the thread is big, it is impossible (the lines are out of the window). You have to examine post
by post, going backwards.
Also, "top posters". Top posters are just evil.
As has been mentioned, *bottom* posters are the most evil of them all.
On 2026-04-03 11:10, Charlie Gibbs wrote:
On 2026-04-03, Frank Slootweg <this@ddress.is.invalid> wrote:
BTW, now we're 'complaining', *my* pet peeve is people quoting
endless
cumulative sections of previous text - often tens and tens to some
hundred lines - without commenting on the text they quote and then
adding only a few lines of new text.
And then using that as a justification for top-posting. Grrr...
TBH, it depends a lot on which newsreader you are using. ThunderBird
makes it easy, /slrn/ makes it next to impossible.
On 4 Apr 2026 14:19:23 GMT, Frank Slootweg wrote:
[snip]
Also, "top posters". Top posters are just evil.
As has been mentioned, *bottom* posters are the most evil of them all.
The WORST being bottom-posters who don't snip, requiring the reader to scroll down several hundred lines to find ANY original material.
Restoring groups.
On 2026-04-04 16:19, Frank Slootweg wrote:
John <Man@the.keyboard> wrote:
On 3 Apr 2026 14:45:38 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
[Followup to alt.unix.geeks ignored.]
<<snipped>>
pee
<<snipped>>
 Yeah, and then there's those who don't quote enough of the previous
post, or who don't quote *any* of it so you have to retrieve it,
sometimes using their Headers to find out *which* post their reply is
referring to.
  Well, those people should get a *real* newsreader! :-)
  BTW, I didn't know that Forte Agent doesn't have a 'go to parent'
function! In my newsreader (tin), I just press 'u' (up the thread) to
display the parent post.
Thunderbird doesn't have a button or key to do that. You have to
visually find it in threaded mode. And if the thread is big, it is impossible (the lines are out of the window). You have to examine post
by post, going backwards.
Carlos E.R. wrote:
Frank Slootweg wrote:There *is* a way ...
I didn't know that Forte Agent doesn't have a 'go to parent'
function! In my newsreader (tin), I just press 'u' (up the thread) to
display the parent post.
Thunderbird doesn't have a button or key to do that. You have to
visually find it in threaded mode. And if the thread is big, it is
impossible (the lines are out of the window). You have to examine post
by post, going backwards.
If you have Compact Headers add-on, you need to expand the twisty, so
you can see the References: header
Then click the rightmost reference link, which is always the parent.
The WORST being bottom-posters who don't snip, requiring the reader to scroll down several hundred lines to find ANY original material.
On 2026-04-04, Kenny McCormack <gazelle@shell.xmission.com> wrote:
In article <10qrd58.1dig.1@ID-201911.user.individual.net>,
Frank Slootweg <this@ddress.is.invalid> wrote:
Lars Poulsen <lars@beagle-ears.com> wrote:
On 2026-04-03 11:10, Charlie Gibbs wrote:
On 2026-04-03, Frank Slootweg <this@ddress.is.invalid> wrote:
BTW, now we're 'complaining', *my* pet peeve is people quoting endless
cumulative sections of previous text - often tens and tens to some >>>>>> hundred lines - without commenting on the text they quote and then >>>>>> adding only a few lines of new text.
And then using that as a justification for top-posting. Grrr...
TBH, it depends a lot on which newsreader you are using.
Just to clarify, the "it" in the previous sentence is referring to the
practice of not top posting.
And yes, most "modern" (and/or GUI) newsreaders default to MS style (i.e., >> top posting).
ThunderBird makes it easy, /slrn/ makes it next to impossible.
This surprises me. I'd have thought exactly the opposite would be true,
but I've never used either one.
In the slrn.rc(configuration) file, this will set the cursor at the
bottom of messages... set editor_command "vim -c %d '%s'"
Next to impossible ;)
It doesn't matter if it's easy/easier or hard for the multitude of
(human) readers, the *poster* should spent the effort to make it easy
for *all* readers. Why should umpteen readers suffer, just because a
poster (i.e. *one* person) can't be bothered to do the right thing?
I think you lost the thread here. I don't see how the previous poster's
words could be interpreted as having to do with the ease of reading.
Of course, we are talking about the ease of posting. And, of course, if
software makes it difficult (or impossible) to do something, users of that >> software will shy away from (and not make any effort to correct the
problem) using that functionality. It is just the way the world works.
I was using /slrn/ for a long time, because I wanted to be able to
read News from desktop PCs at several different locations (using SSH
to get into my Linux desktop). I have now resigned myself to only
read when I am at my desktop at home.
On 2026-04-04 08:57, Adison Vohn Caterson wrote:
On 2026-04-04, Kenny McCormack <gazelle@shell.xmission.com> wrote:
My testimony was not addressing the ease of top-posting versus bottom- posting, but the ease of looking up an earlier post in the thread if
that level of "previous" had been snipped.
/slrn/ (because it runs on a TTY socket) does not allow you to click
through via a "References: " header, nor indeed via *any* embedded URL.
The second of these can be remedied via the features of the terminal
program on the user end (highlight, copy and then paste into a browser address line) but the "References:" has no easy solution.
I was using /slrn/ for a long time, because I wanted to be able to read
News from desktop PCs at several different locations (using SSH to get
into my Linux desktop). I have now resigned myself to only read when I
am at my desktop at home.
On 2026-04-04 23:00, Lars Poulsen wrote:
On 2026-04-04 08:57, Adison Vohn Caterson wrote:
On 2026-04-04, Kenny McCormack <gazelle@shell.xmission.com> wrote:
My testimony was not addressing the ease of top-posting versus bottom-
posting, but the ease of looking up an earlier post in the thread if
that level of "previous" had been snipped.
/slrn/ (because it runs on a TTY socket) does not allow you to click
through via a "References: " header, nor indeed via *any* embedded
URL.
Terminal clients like Alpine allow "clicking" on an URL (actually,
pressing [enter] on it), and then call a terminal web browser to
display it.
The second of these can be remedied via the features of the terminal
program on the user end (highlight, copy and then paste into a
browser address line) but the "References:" has no easy solution.
I was using /slrn/ for a long time, because I wanted to be able to
read News from desktop PCs at several different locations (using SSH
to get into my Linux desktop). I have now resigned myself to only
read when I am at my desktop at home.
John <Man@the.keyboard> wrote:
On 3 Apr 2026 14:45:38 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
[Followup to alt.unix.geeks ignored.]
<<snipped>>
pee
<<snipped>>
Yeah, and then there's those who don't quote enough of the previous
post, or who don't quote *any* of it so you have to retrieve it,
sometimes using their Headers to find out *which* post their reply is
referring to.
Well, those people should get a *real* newsreader! :-)
BTW, I didn't know that Forte Agent doesn't have a 'go to parent' function! In my newsreader (tin), I just press 'u' (up the thread) to
display the parent post.
[...]
Also, "top posters". Top posters are just evil.
As has been mentioned, *bottom* posters are the most evil of them all.
On 5/04/2026 1:19 am, Frank Slootweg wrote:[...]
John <Man@the.keyboard> wrote:
On 3 Apr 2026 14:45:38 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
Also, "top posters". Top posters are just evil.
As has been mentioned, *bottom* posters are the most evil of them all.
Sorry! WHAT?? "top posters" are just evil!! But "bottom posters" are the most evil!! .... so "interspersed posters" should be *most correct* .
And that *IS* what you do when you bottom post .... as long as you've
got nothing to say about the upper portions of the post!! ;-)
Mark Lloyd <not.email@all.invalid> writes:
The WORST being bottom-posters who don't snip, requiring the reader to scroll down several hundred lines to find ANY original material.
Generally, if I don't see any fresh input in the first two screenfuls of text, I press n to move to the next article.
Anybody worth reading don't quote two screenfuls before commenting it.
My testimony was not addressing the ease of top-posting versus bottom- posting, but the ease of looking up an earlier post in the thread if
that level of "previous" had been snipped.
/slrn/ (because it runs on a TTY socket) does not allow you to click
through via a "References: " header, nor indeed via *any* embedded URL.
The second of these can be remedied via the features of the terminal
program on the user end (highlight, copy and then paste into a browser address line) but the "References:" has no easy solution.
I was using /slrn/ for a long time, because I wanted to be able to read--- Synchronet 3.21d-Linux NewsLink 1.2
News from desktop PCs at several different locations (using SSH to get
into my Linux desktop). I have now resigned myself to only read when I
am at my desktop at home.
On Sat, 4 Apr 2026 14:00:54 -0700, Lars Poulsen wrote:
I was using /slrn/ for a long time, because I wanted to be able to
read News from desktop PCs at several different locations (using SSH
to get into my Linux desktop). I have now resigned myself to only
read when I am at my desktop at home.
Other possibilities would be screen/tmux (for remote non-GUI access)
or VNC or RDP (for remote GUI access) or like that.
I used to share the Linux box's desktop with TigerVNC. It worked well
for years, but broke (actually disappeared) around the time of a version >upgrade that turned into a re-install on new hardware; I think this was >related to the X11-to-Wayland transition, but when re-installing
TigerVNC server, it no longer generated the systemd service module
template, and I have not had the patience to track down what the new
best way to share the desktop.
| Sysop: | Scott Duensing |
|---|---|
| Location: | Freeburg, IL, USA, Earth |
| Users: | 5 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 493213:09:36 |
| Calls: | 5 |
| Messages: | 18,934 |