Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #88898
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Newsgroups | comp.lang.c++, news.admin.net-abuse.usenet |
| Subject | Re: Thunderbird Broken Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) |
| Date | 2023-01-29 12:04 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <tr5jrf$2npbg$4@dont-email.me> (permalink) |
| References | (17 earlier) <730105qr-2qrs-oo6q-30r7-p3o6r8p793p4@zvaqfcevat.pbz> <tqoluk$5cht$2@dont-email.me> <B1jyOFXZ9kwyO2oB1@bongo-ra.co> <tqpcje$8v5p$3@dont-email.me> <0001HW.2986256E023E4BBC306F0738F@news.giganews.com> |
Cross-posted to 2 groups.
On 29/01/2023 04:54, Pluted Pup wrote: > On Tue, 24 Jan 2023 11:46:54 -0800, David Brown wrote: > >> On 24/01/2023 18:47, Spiros Bousbouras wrote: >>> On Tue, 24 Jan 2023 14:20:19 +0100 >>> David Brown <david.brown@hesbynett.no> wrote: >>>> 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. >>> >>> It could be a Thunderbird issue. Note the following : >>> >>> All 3 of you use Thunderbird. Not precisely the same version but close. I assume >>> you have tried to reproduce the steps which originally led you to see the defective >>> post and you can no longer reproduce them. >> >> You are correct that we all use Thunderbird, and it is definitely >> something I considered. More relevantly, however, we all use >> news.eternal-september.org. And I have just tested using a clean >> installation of pan as an alternative newsreader, and seen exactly the >> same effect. >> >> I don't know why you think I can no longer reproduce the effect of the >> broken post - I have made no such suggestion, precisely because I /can/ >> replicate it. I still see it on two different computers with >> Thunderbird, and now also with Pan. >> >> For convenience, I have taken a screenshot of the effect. I have not >> used this site "paste.pics" before, and I apologise if there are >> unwanted adverts or other effects. If you are sceptical of clicking the >> link, then I can happily email the screenshot. But it seems a quick and >> easy way to make a link to the screenshot. >> >> <https://paste.pics/b4149f38abb4e210da0a71886714d014> > > That screen makes no sense and I would guess it to be a > Thunderbird problem. Thunderbird on mac has been broken > for me for many months and have quit trying to make it work. > A client problem, not a server problem. > It's a screenshot from Pan, not Thunderbird. (You realise this is Usenet, don't you? It is not personal email - you are allowed to read replies I have made to other people. Indeed, it's a good idea, and saves repetition.) It makes no sense because it shows a /server/ problem - the /server/ returned nonsense for that post. > So Thunderbird is broken or semi-broken depending on > Mac (broken), Windows (semi-broken), or Linux (somewhat > broken). > > If Mozilla (Thunderbird) doesn't want to support newsgroups > anymore, they should stop pretending to. This is me jumping > to conclusions. > I've found Thunderbird to work fine on Linux (I also use it on Windows, but not for Usenet). It's not perfect, but I've found few programs that /are/ perfect. And it shows the same glitch here as Pan does, because it is a /server/ glitch, not a client issue.
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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