Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c++ > #88804

Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set)

From David Brown <david.brown@hesbynett.no>
Newsgroups comp.lang.c++, news.admin.net-abuse.usenet
Subject Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set)
Date 2023-01-24 14:20 +0100
Organization A noiseless patient Spider
Message-ID <tqoluk$5cht$2@dont-email.me> (permalink)
References (13 earlier) <tqm247$3kqcf$2@dont-email.me> <JaMukkKxSBcM7VPWN@bongo-ra.co> <02q63458-1orq-4135-9358-994371poq6o8@zvaqfcevat.pbz> <z8dmrhuM9xNk7FY=M@bongo-ra.co> <730105qr-2qrs-oo6q-30r7-p3o6r8p793p4@zvaqfcevat.pbz>

Cross-posted to 2 groups.

Show all headers | View raw


On 23/01/2023 21:46, David Ritz wrote:
> On Monday, 23 January 2023 20:06 -0000,
>   in article <z8dmrhuM9xNk7FY=M@bongo-ra.co>,
>   Spiros Bousbouras <spibou@gmail.com> wrote:
> 
>> On Mon, 23 Jan 2023 13:03:52 -0600
>> David Ritz <dritz@mindspring.com> wrote:
> 

>>>   You will never find an article posted only to rec.arts.books, in
>>>   comp.lang.c++.
> 
>> Not under normal circumstances but the claim is that a temporary
>> glitch on eternal-september caused it to happen and that David Brown
>> saw it with his own eyes.
> 
> I'm of the "Show Me" school.  I do not care about spurious,
> unsupported claims.  The only glitch was human error.
> 

I'm sorry, but you are wrong.

If you think servers - hardware and/or software - can never fail, you 
are naïve beyond comprehension.

If you think it is appropriate to accuse one person you have never met 
of lying, and another of trolling, based solely on your belief in the 
perfection of all Usenet servers, then you should not be involving 
yourself in any kind of abuse resolution or advice.  You should be 
asking questions first - not passing arbitrary judgement.

Someone of the "Show me" school would ask for more information.  You 
appear to be in the "Jump to conclusions" school.



There are limits to how much I can "show you" what happened.  But I can 
describe things in as much detail as practical.

I use news.eternal-september.org as a Usenet server, with Thunderbird as 
the client.  I am currently looking at the thread with subject "Re: 
Compute Unique Numbers in a Set" started (via a cross-post from 
comp.lang.c) on 08.01.2023.  On one branch, posters "Bonita Montero" and 
"Muttley@dastardlyhq.com" had been arguing back and forth, here in 
comp.lang.c++.  The penultimate post in the branch was made by Bonita 
18.01.2023, 18:23, message id "tq99tp$vtqp$1@dont-email.me".  Everything 
looks normal.

When downloading message headers, the next message on the thread appears 
to be the expected reply from Muttley.  It has the same subject, and the 
timestamp 19.01.2023, 10:31.

The message body here is, however, completely unexpected.  It's headers 
do not match the previously downloaded headers.  In the message body, 
the subject is "Change and Choice", the poster is "Ilya Shambat", the 
newsgroup is "rec.arts.books", the id is 
"36403165-3cf1-4b73-8ad1-da339b960339n@googlegroups.com", there are no 
reference links to the other messages in the thread.  The message 
contains a rambling essay.


If I attempt to follow-up the message in Thunderbird, the Thunderbird 
client sets the newsgroup to "rec.arts.books", the subject to "Re: 
Compute Unique Numbers in a Set" (i.e., from the pre-downloaded headers, 
not the body), and the quotation is given as "Muttley@dastardlyhq.com 
wrote:".  The body of the quotation is the rambling essay.  This is 
entirely consistent with Bonita's post - she replied to what she 
believed to be a message from Muttley.



It is quite clear that there has been a glitch on the 
news.eternal-september.org server.  Somehow, a message body from 
rec.arts.books has been crosslinked, was delivered as though it matched 
the normal-looking pre-downloaded header in the thread.  (I'm guessing 
Muttley actually made a post in the original thread, but I am unable to 
see the real message body.)  The glitch appears to be limited to 
news.eternal-september.org - other users of that server have said they 
saw it, while it did not appear on other servers.  People have reported 
the existence of the rambling essay post in rec.arts.books, made by Ilya 
Shambat - it was a real post, but on news.eternal-september.org the 
message body was accidentally attached to the wrong header summaries for 
comp.lang.c++.


Usenet server glitches are rare - client glitches are more likely.  The 
same glitch occurring for at least three different people is, however, 
highly unlikely.  And the idea that Bonita would jumped through hoops to 
repost some random post from another group but made to look like it came 
from Muttley so that she could comment on it - it's ridiculous.



> I recommend a visit to an optician.
> 

I recommend you either listen to what happened, or bow out of this 
conversation.  It is possible that you have experiences or knowledge 
that could help explain things - but if you think you know all the 
answers before you've heard the question, there's no point in commenting.

Back to comp.lang.c++ | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Compute Unique Numbers in a Set Bonita Montero <Bonita.Montero@gmail.com> - 2023-01-19 15:42 +0100
  Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-19 16:18 +0100
    Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-19 16:32 +0000
      Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-19 19:22 +0100
        Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-19 20:00 +0000
        Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-20 15:48 +0000
      Re: Compute Unique Numbers in a Set Richard Harnden <richard.nospam@gmail.com> - 2023-01-25 13:00 +0000
        Re: Compute Unique Numbers in a Set James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 14:52 -0500
          Re: Compute Unique Numbers in a Set Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-01-25 14:13 -0800
            Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-26 00:03 +0100
              Re: Compute Unique Numbers in a Set ikook <iKook@GMAIL.COM> - 2023-01-25 23:17 +0000
                Re: Compute Unique Numbers in a Set scott@slp53.sl.home (Scott Lurndal) - 2023-01-25 23:37 +0000
                Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-26 09:19 +0100
          Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-26 00:09 +0000
            Re: Compute Unique Numbers in a Set James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 23:55 -0500
    Re: Compute Unique Numbers in a Set Öö Tiib <ootiib@hot.ee> - 2023-01-19 08:40 -0800
      Re: Compute Unique Numbers in a Set red floyd <no.spam.here@its.invalid> - 2023-01-19 08:42 -0800
        Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-19 20:10 +0000
          Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-19 20:17 +0000
            Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-20 15:49 +0000
              Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-20 17:21 +0000
                Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-21 15:50 +0000
              Re: Compute Unique Numbers in a Set "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-01-20 11:35 -0800
                Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-21 13:06 +0100
                Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-21 15:56 +0000
                Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-22 13:33 +0100
                Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-23 09:34 +0000
                Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-23 14:29 +0100
                Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-23 14:21 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-23 13:03 -0600
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-23 20:06 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-23 14:46 -0600
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-23 22:00 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 14:20 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) scott@slp53.sl.home (Scott Lurndal) - 2023-01-24 15:36 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-01-24 08:06 -0800
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 18:30 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) scott@slp53.sl.home (Scott Lurndal) - 2023-01-24 18:50 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 20:36 +0100
                Re: Server glitch vs other possibilities "Adam H. Kerman" <ahk@chinet.com> - 2023-01-24 19:50 +0000
                Re: Server glitch vs other possibilities Marc SCHAEFER <schaefer@alphanet.ch> - 2023-01-24 19:56 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-24 20:31 -0600
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-24 20:07 -0800
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) "Adam H. Kerman" <ahk@chinet.com> - 2023-01-25 05:02 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-24 17:47 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-24 13:30 -0500
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 20:42 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 20:46 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) scott@slp53.sl.home (Scott Lurndal) - 2023-01-24 19:56 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Manu Raju <MR@invalid.invalid> - 2023-01-24 22:00 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-25 00:00 +0100
                Re: Server glitch vs other possibilities snipeco.2@gmail.com (Sn!pe) - 2023-01-25 00:17 +0000
                Re: Server glitch vs other possibilities David Brown <david.brown@hesbynett.no> - 2023-01-25 09:43 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-25 10:39 -0600
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 14:51 -0500
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 00:00 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-25 23:49 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 09:23 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) iKook <iKook@gmail.com> - 2023-01-26 02:27 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 23:55 -0500
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) iKook <iKook@gmail.com> - 2023-01-26 18:22 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 09:44 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Öö Tiib <ootiib@hot.ee> - 2023-01-26 01:40 -0800
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 13:14 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) iKook <iKook@gmail.com> - 2023-01-26 18:13 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-27 22:12 -0600
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-28 13:20 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Pluted Pup <plutedpup@outlook.com> - 2023-01-28 20:20 -0800
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-29 12:00 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) gazelle@shell.xmission.com (Kenny McCormack) - 2023-01-29 12:01 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Daniel <danielaparker@gmail.com> - 2023-01-29 16:23 -0800
                [OT] Writing IMHO Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-30 01:14 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-25 22:58 +0000
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 13:10 +0100
                Thunderbird Broken Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Pluted Pup <plutedpup@outlook.com> - 2023-01-28 19:54 -0800
                Re: Thunderbird Broken Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-29 12:04 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-24 20:30 -0600
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-24 20:25 -0600
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 00:10 -0500
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-25 10:56 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Pluted Pup <plutedpup@outlook.com> - 2023-01-28 19:28 -0800
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-29 12:36 +0100
                Pluted Pup is trolling you, you blithering idiot (was: Server glitch vs other possibilities) "Adam H. Kerman" <ahk@chinet.com> - 2023-01-29 17:23 +0000
                Re: Pluted Pup is trolling you, you blithering idiot (was: Server glitch vs other possibilities) David Brown <david.brown@hesbynett.no> - 2023-01-30 08:22 +0100
                Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) "Adam H. Kerman" <ahk@chinet.com> - 2023-01-23 22:18 +0000
      Re: Compute Unique Numbers in a Set Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2023-01-19 17:08 +0000
        Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-19 17:15 +0000
    Re: Compute Unique Numbers in a Set gazelle@shell.xmission.com (Kenny McCormack) - 2023-01-19 16:54 +0000
    Re: Compute Unique Numbers in a Set Pluted Pup <plutedpup@outlook.com> - 2023-01-21 13:03 -0800
      Re: Compute Unique Numbers in a Set Pluted Pup <plutedpup@outlook.com> - 2023-01-21 14:01 -0800
  Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-19 16:30 +0000
  Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-19 16:48 +0000

csiph-web