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

Groups > comp.lang.c++ > #85390 > unrolled thread

A plea...

Back to article view | Back to comp.lang.c++

Contents

  A plea... Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-07-17 03:24 +0100
    Re: A plea... olcott <NoOne@NoWhere.com> - 2022-07-16 21:32 -0500
      Re: A plea... Skep Dick <skepdick22@gmail.com> - 2022-07-17 03:35 -0700
        Re: A plea... olcott <NoOne@NoWhere.com> - 2022-07-17 07:51 -0500
    Re: A plea... Juha Nieminen <nospam@thanks.invalid> - 2022-07-17 14:38 +0000
      Re: A plea... Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-07-18 01:24 +0100
        Re: A plea... olcott <NoOne@NoWhere.com> - 2022-07-17 19:43 -0500
          Re: A plea... Richard Damon <Richard@Damon-Family.org> - 2022-07-17 22:44 -0400
            Re: A plea... Manfred <noname@add.invalid> - 2022-07-18 05:34 +0200
              Re: A plea... olcott <NoOne@NoWhere.com> - 2022-07-17 22:39 -0500
            Re: A plea... olcott <NoOne@NoWhere.com> - 2022-07-17 22:35 -0500
        Re: A plea... Juha Nieminen <nospam@thanks.invalid> - 2022-07-18 05:28 +0000
          Re: A plea... "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2022-07-18 13:49 -0700
        Which newsreader (was Re: A plea...) Vir Campestris <vir.campestris@invalid.invalid> - 2022-07-18 22:03 +0100
          Re: Which newsreader (was Re: A plea...) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-07-18 23:39 +0100
            Re: Which newsreader (was Re: A plea...) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2022-07-18 17:27 -0700
              Re: Which newsreader (was Re: A plea...) David Brown <david.brown@hesbynett.no> - 2022-07-19 09:23 +0200
                Re: Which newsreader (was Re: A plea...) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2022-07-19 15:37 -0700
              Re: Which newsreader (was Re: A plea...) Muttley@dastardlyhq.com - 2022-07-19 08:29 +0000
                Re: Which newsreader (was Re: A plea...) David Brown <david.brown@hesbynett.no> - 2022-07-19 14:06 +0200
                  Re: Which newsreader (was Re: A plea...) Muttley@dastardlyhq.com - 2022-07-19 14:54 +0000
                Re: Which newsreader (was Re: A plea...) Ralf Fassel <ralfixx@gmx.de> - 2022-07-19 14:34 +0200
                  Re: Which newsreader (was Re: A plea...) Muttley@dastardlyhq.com - 2022-07-19 14:56 +0000
              Re: Which newsreader (was Re: A plea...) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2022-07-20 01:27 +0100
                Re: Which newsreader (was Re: A plea...) Manfred <noname@add.invalid> - 2022-07-20 03:09 +0200
                I addressed your plea Can you please review my work again if I post the source-code? olcott <NoOne@NoWhere.com> - 2022-07-21 14:11 -0500
          Re: Which newsreader (was Re: A plea...) Muttley@dastardlyhq.com - 2022-07-19 08:30 +0000
          Re: Which newsreader (was Re: A plea...) Jack Lemmon <invalid@invalid.net> - 2022-07-19 19:50 +0100
            Re: Which newsreader (was Re: A plea...) Jim the Geordie <jim@jimXscott.co.uk> - 2022-07-20 00:49 +0100
            Re: Which newsreader (was Re: A plea...) Vir Campestris <vir.campestris@invalid.invalid> - 2022-07-25 12:11 +0100
    Re: A plea... olcott <NoOne@NoWhere.com> - 2022-07-18 07:58 -0500

Page 1 of 2  [1] 2  Next page →

#85390 — A plea...

Please don't respond to Peter Olcott's posts here.  His threads have
taken over comp.theory, but there is no reason that comp.lang c (or
comp.lang.c++) should suffer the same fate.  These two groups have had
many interesting threads over the years, but they will die if they fill
up with junk.

If you want to reply to him, just pick any of the thousands of posts in
comp.theory and he'll be as happy to insult you and call you ignorant
there as he is here.

I've not made this a head post because I don't want to single anyone
out.  Everyone who'd got something out of comp.lang.c should care about
its curation...

-- 
Ben.

[toc] | [next] | [standalone]

#85391

On 7/16/2022 9:24 PM, Ben Bacarisse wrote:
> Please don't respond to Peter Olcott's posts here.  His threads have
> taken over comp.theory, but there is no reason that comp.lang c (or
> comp.lang.c++) should suffer the same fate.  These two groups have had
> many interesting threads over the years, but they will die if they fill
> up with junk.
> 
> If you want to reply to him, just pick any of the thousands of posts in
> comp.theory and he'll be as happy to insult you and call you ignorant
> there as he is here.
> 
> I've not made this a head post because I don't want to single anyone
> out.  Everyone who'd got something out of comp.lang.c should care about
> its curation...
> 

As soon as I get closure (very close now) I won't need to post on USENET 
at all. The current version of my work can only be properly reviewed by 
software engineers. The computer science issues are being addressed 
through emails to computer scientists.


-- 
Copyright 2022 Pete Olcott

"Talent hits a target no one else can hit;
  Genius hits a target no one else can see."
  Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]

#85398

On Sunday, 17 July 2022 at 04:32:43 UTC+2, olcott wrote:
> As soon as I get closure (very close now) I won't need to post on USENET 

Your closure-seeking loop seems to be stuck in an infinite loop.

If your halting decider actually worked you would've terminated your closure-seeking loop by now.

Irony has a certain flavour...

[toc] | [prev] | [next] | [standalone]

#85418

On 7/17/2022 5:35 AM, Skep Dick wrote:
> On Sunday, 17 July 2022 at 04:32:43 UTC+2, olcott wrote:
>> As soon as I get closure (very close now) I won't need to post on USENET
> 
> Your closure-seeking loop seems to be stuck in an infinite loop.
> 
> If your halting decider actually worked you would've terminated your closure-seeking loop by now.
> 
> Irony has a certain flavour...
> 

The problem is that I perfectly makes my point and my reviewers simply 
ignore all these words and change the subject.

-- 
Copyright 2022 Pete Olcott

"Talent hits a target no one else can hit;
  Genius hits a target no one else can see."
  Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]

#85433

In comp.lang.c++ Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
> Please don't respond to Peter Olcott's posts here.  His threads have
> taken over comp.theory, but there is no reason that comp.lang c (or
> comp.lang.c++) should suffer the same fate.  These two groups have had
> many interesting threads over the years, but they will die if they fill
> up with junk.

Since usenet posts are threaded, it's very easy to ignore the threads
created by him.

(This is, in fact, a major reason to *not* killfile someone you don't
want to see: If you killfile that person you won't see if a thread
was started by that person. Instead, you will only see the replies,
which will mislead you into the thread. You are essentially hiding
the thread original poster from yourself, which makes no sense.
You *want* to see who created the thread so that you can decide
whether to even open it or not. Why would you want to hide it
from yourself?

Usenet killfiles are the perfect example of something that sounds
good on paper but actually ends up being more detrimental to yourself
than useful. This is because of the threaded nature of usenet. Unless,
perhaps, your usenet reader is somehow capable of hiding entire threads
based on the original poster. But then, why do you care if that person
posts or not? It's all hidden from you.)

[toc] | [prev] | [next] | [standalone]

#85449

Juha Nieminen <nospam@thanks.invalid> writes:

> In comp.lang.c++ Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>> Please don't respond to Peter Olcott's posts here.  His threads have
>> taken over comp.theory, but there is no reason that comp.lang c (or
>> comp.lang.c++) should suffer the same fate.  These two groups have had
>> many interesting threads over the years, but they will die if they fill
>> up with junk.
>
> Since usenet posts are threaded, it's very easy to ignore the threads
> created by him.

Agreed.  The trouble, as evidenced by other groups, it the junk drives
non-regulars away so newcomers will be few, and fresh questions and
ideas dry up.

> (This is, in fact, a major reason to *not* killfile ...

My newsreader has a scoring system that is far more sophisticated than a
kill file.  I can even "score down" sub-threads where PO jumps in to
poison the thread.  The trouble is that newbies don't do this sort of
thing.  One look at comp.lang.c++ in GG and they will go elsewhere.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]

#85451

On 7/17/2022 7:24 PM, Ben Bacarisse wrote:
> Juha Nieminen <nospam@thanks.invalid> writes:
> 
>> In comp.lang.c++ Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>>> Please don't respond to Peter Olcott's posts here.  His threads have
>>> taken over comp.theory, but there is no reason that comp.lang c (or
>>> comp.lang.c++) should suffer the same fate.  These two groups have had
>>> many interesting threads over the years, but they will die if they fill
>>> up with junk.
>>
>> Since usenet posts are threaded, it's very easy to ignore the threads
>> created by him.
> 
> Agreed.  The trouble, as evidenced by other groups, it the junk drives
> non-regulars away so newcomers will be few, and fresh questions and
> ideas dry up.
> 
>> (This is, in fact, a major reason to *not* killfile ...
> 
> My newsreader has a scoring system that is far more sophisticated than a
> kill file.  I can even "score down" sub-threads where PO jumps in to
> poison the thread.  The trouble is that newbies don't do this sort of
> thing.  One look at comp.lang.c++ in GG and they will go elsewhere.
> 

All that anyone would have to do to get me to leave these two groups is 
simply apply the correct and quite simple software engineering to 
validate the software engineering of what I have said.

I am working with people offline so this may quickly resolve things too.

I am, also trying to help get Richard and Flibble to stop talking about 
non-software engineering related stuff here too. I moved Flibble to 
comp.theory already. I would be willing to unblock Richard if he goes 
there too.

-- 
Copyright 2022 Pete Olcott

"Talent hits a target no one else can hit;
  Genius hits a target no one else can see."
  Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]

#85453

On 7/17/22 8:43 PM, olcott wrote:
> On 7/17/2022 7:24 PM, Ben Bacarisse wrote:
>> Juha Nieminen <nospam@thanks.invalid> writes:
>>
>>> In comp.lang.c++ Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>>>> Please don't respond to Peter Olcott's posts here.  His threads have
>>>> taken over comp.theory, but there is no reason that comp.lang c (or
>>>> comp.lang.c++) should suffer the same fate.  These two groups have had
>>>> many interesting threads over the years, but they will die if they fill
>>>> up with junk.
>>>
>>> Since usenet posts are threaded, it's very easy to ignore the threads
>>> created by him.
>>
>> Agreed.  The trouble, as evidenced by other groups, it the junk drives
>> non-regulars away so newcomers will be few, and fresh questions and
>> ideas dry up.
>>
>>> (This is, in fact, a major reason to *not* killfile ...
>>
>> My newsreader has a scoring system that is far more sophisticated than a
>> kill file.  I can even "score down" sub-threads where PO jumps in to
>> poison the thread.  The trouble is that newbies don't do this sort of
>> thing.  One look at comp.lang.c++ in GG and they will go elsewhere.
>>
> 
> All that anyone would have to do to get me to leave these two groups is 
> simply apply the correct and quite simple software engineering to 
> validate the software engineering of what I have said.
> 
> I am working with people offline so this may quickly resolve things too.
> 
> I am, also trying to help get Richard and Flibble to stop talking about 
> non-software engineering related stuff here too. I moved Flibble to 
> comp.theory already. I would be willing to unblock Richard if he goes 
> there too.
> 

In other words, you are asking people to LIE for you, since you are NOT 
using actual correct software engineering principles.

I have pointed out the errors that you have made in software-engineering 
principles, but you just ignore it, because fixing them would break your 
"proof"

I am only here, because you said you blocked me in comp.theory

[toc] | [prev] | [next] | [standalone]

#85454

On 7/18/2022 4:44 AM, Richard Damon wrote:
> On 7/17/22 8:43 PM, olcott wrote:
>> On 7/17/2022 7:24 PM, Ben Bacarisse wrote:
>>> Juha Nieminen <nospam@thanks.invalid> writes:
>>>
>>>> In comp.lang.c++ Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>>>>> Please don't respond to Peter Olcott's posts here.  His threads have
>>>>> taken over comp.theory, but there is no reason that comp.lang c (or
>>>>> comp.lang.c++) should suffer the same fate.  These two groups have had
>>>>> many interesting threads over the years, but they will die if they 
>>>>> fill
>>>>> up with junk.
>>>>
>>>> Since usenet posts are threaded, it's very easy to ignore the threads
>>>> created by him.
>>>
>>> Agreed.  The trouble, as evidenced by other groups, it the junk drives
>>> non-regulars away so newcomers will be few, and fresh questions and
>>> ideas dry up.
>>>
>>>> (This is, in fact, a major reason to *not* killfile ...
>>>
>>> My newsreader has a scoring system that is far more sophisticated than a
>>> kill file.  I can even "score down" sub-threads where PO jumps in to
>>> poison the thread.  The trouble is that newbies don't do this sort of
>>> thing.  One look at comp.lang.c++ in GG and they will go elsewhere.
>>>
>>
>> All that anyone would have to do to get me to leave these two groups 
>> is simply apply the correct and quite simple software engineering to 
>> validate the software engineering of what I have said.
>>
>> I am working with people offline so this may quickly resolve things too.
>>
>> I am, also trying to help get Richard and Flibble to stop talking 
>> about non-software engineering related stuff here too. I moved Flibble 
>> to comp.theory already. I would be willing to unblock Richard if he 
>> goes there too.
>>
> 
> In other words, you are asking people to LIE for you, since you are NOT 
> using actual correct software engineering principles.
> 
> I have pointed out the errors that you have made in software-engineering 
> principles, but you just ignore it, because fixing them would break your 
> "proof"
> 
> I am only here, because you said you blocked me in comp.theory

That is not a good reason to spread olcott's garbage in this group.

I, like many others I guess, don't have a sophisticated newsreader as 
Ben has, and, although I have blocked PO a wile ago, I still get a /lot/ 
of his garbage because of your replies.
Now, I could block you too, but so far I don't have a reason to do this, 
unless you keep pouring olcott's stuff in here.

All in all, Ben is very much right when he says that being filled up 
with junk is the biggest threat to usenet in general (which is in fact 
largely dead already because of this exact problem), and c.l.c and 
c.l.c++ in particular, which have somehow managed to keep some standard 
of activity and interest.
It would be a pity if these groups would die too.

[toc] | [prev] | [next] | [standalone]

#85456

On 7/17/2022 10:34 PM, Manfred wrote:
> On 7/18/2022 4:44 AM, Richard Damon wrote:
>> On 7/17/22 8:43 PM, olcott wrote:
>>> On 7/17/2022 7:24 PM, Ben Bacarisse wrote:
>>>> Juha Nieminen <nospam@thanks.invalid> writes:
>>>>
>>>>> In comp.lang.c++ Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>>>>>> Please don't respond to Peter Olcott's posts here.  His threads have
>>>>>> taken over comp.theory, but there is no reason that comp.lang c (or
>>>>>> comp.lang.c++) should suffer the same fate.  These two groups have 
>>>>>> had
>>>>>> many interesting threads over the years, but they will die if they 
>>>>>> fill
>>>>>> up with junk.
>>>>>
>>>>> Since usenet posts are threaded, it's very easy to ignore the threads
>>>>> created by him.
>>>>
>>>> Agreed.  The trouble, as evidenced by other groups, it the junk drives
>>>> non-regulars away so newcomers will be few, and fresh questions and
>>>> ideas dry up.
>>>>
>>>>> (This is, in fact, a major reason to *not* killfile ...
>>>>
>>>> My newsreader has a scoring system that is far more sophisticated 
>>>> than a
>>>> kill file.  I can even "score down" sub-threads where PO jumps in to
>>>> poison the thread.  The trouble is that newbies don't do this sort of
>>>> thing.  One look at comp.lang.c++ in GG and they will go elsewhere.
>>>>
>>>
>>> All that anyone would have to do to get me to leave these two groups 
>>> is simply apply the correct and quite simple software engineering to 
>>> validate the software engineering of what I have said.
>>>
>>> I am working with people offline so this may quickly resolve things too.
>>>
>>> I am, also trying to help get Richard and Flibble to stop talking 
>>> about non-software engineering related stuff here too. I moved 
>>> Flibble to comp.theory already. I would be willing to unblock Richard 
>>> if he goes there too.
>>>
>>
>> In other words, you are asking people to LIE for you, since you are 
>> NOT using actual correct software engineering principles.
>>
>> I have pointed out the errors that you have made in 
>> software-engineering principles, but you just ignore it, because 
>> fixing them would break your "proof"
>>
>> I am only here, because you said you blocked me in comp.theory
> 
> That is not a good reason to spread olcott's garbage in this group.
> 
> I, like many others I guess, don't have a sophisticated newsreader as 
> Ben has, and, although I have blocked PO a wile ago, I still get a /lot/ 
> of his garbage because of your replies.
> Now, I could block you too, but so far I don't have a reason to do this, 
> unless you keep pouring olcott's stuff in here.
> 
> All in all, Ben is very much right when he says that being filled up 
> with junk is the biggest threat to usenet in general (which is in fact 
> largely dead already because of this exact problem), and c.l.c and 
> c.l.c++ in particular, which have somehow managed to keep some standard 
> of activity and interest.
> It would be a pity if these groups would die too.

For that reason I addressed Ben's plea.
Ben has been reviewing my work since 2006.

On 10/17/2006 7:03 PM, Ben Bacarisse wrote:
 > "Peter Olcott" <NoSpam@SeeScreen.com> writes:


-- 
Copyright 2022 Pete Olcott

"Talent hits a target no one else can hit;
  Genius hits a target no one else can see."
  Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]

#85455

On 7/17/2022 9:44 PM, Richard Damon wrote:
> On 7/17/22 8:43 PM, olcott wrote:
>> On 7/17/2022 7:24 PM, Ben Bacarisse wrote:
>>> Juha Nieminen <nospam@thanks.invalid> writes:
>>>
>>>> In comp.lang.c++ Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>>>>> Please don't respond to Peter Olcott's posts here.  His threads have
>>>>> taken over comp.theory, but there is no reason that comp.lang c (or
>>>>> comp.lang.c++) should suffer the same fate.  These two groups have had
>>>>> many interesting threads over the years, but they will die if they 
>>>>> fill
>>>>> up with junk.
>>>>
>>>> Since usenet posts are threaded, it's very easy to ignore the threads
>>>> created by him.
>>>
>>> Agreed.  The trouble, as evidenced by other groups, it the junk drives
>>> non-regulars away so newcomers will be few, and fresh questions and
>>> ideas dry up.
>>>
>>>> (This is, in fact, a major reason to *not* killfile ...
>>>
>>> My newsreader has a scoring system that is far more sophisticated than a
>>> kill file.  I can even "score down" sub-threads where PO jumps in to
>>> poison the thread.  The trouble is that newbies don't do this sort of
>>> thing.  One look at comp.lang.c++ in GG and they will go elsewhere.
>>>
>>
>> All that anyone would have to do to get me to leave these two groups 
>> is simply apply the correct and quite simple software engineering to 
>> validate the software engineering of what I have said.
>>
>> I am working with people offline so this may quickly resolve things too.
>>
>> I am, also trying to help get Richard and Flibble to stop talking 
>> about non-software engineering related stuff here too. I moved Flibble 
>> to comp.theory already. I would be willing to unblock Richard if he 
>> goes there too.
>>
> 
> In other words, you are asking people to LIE for you, since you are NOT 
> using actual correct software engineering principles.
> 

No I am asking you to move to comp.theory so you don't ruin comp.c and 
comp.c++

> I have pointed out the errors that you have made in software-engineering 
> principles, but you just ignore it, because fixing them would break your 
> "proof"
> 
> I am only here, because you said you blocked me in comp.theory

So I unblocked you to address Ben's plea.

-- 
Copyright 2022 Pete Olcott

"Talent hits a target no one else can hit;
  Genius hits a target no one else can see."
  Arthur Schopenhauer

[toc] | [prev] | [next] | [standalone]

#85457

Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
> My newsreader has a scoring system that is far more sophisticated than a
> kill file.  I can even "score down" sub-threads where PO jumps in to
> poison the thread.  The trouble is that newbies don't do this sort of
> thing.  One look at comp.lang.c++ in GG and they will go elsewhere.

Usenet is mostly dead anyway.

[toc] | [prev] | [next] | [standalone]

#85464

On 7/17/2022 10:28 PM, Juha Nieminen wrote:
> Ben Bacarisse <ben.usenet@bsb.me.uk> wrote:
>> My newsreader has a scoring system that is far more sophisticated than a
>> kill file.  I can even "score down" sub-threads where PO jumps in to
>> poison the thread.  The trouble is that newbies don't do this sort of
>> thing.  One look at comp.lang.c++ in GG and they will go elsewhere.
> 
> Usenet is mostly dead anyway.

Yet, this group still produces wonderful and insightful answers from 
highly talented, experienced programmers. Btw, "mostly dead" reminds me 
of the following scene from the Princess Bride:

https://youtu.be/d4ftmOI5NnI?t=40

[toc] | [prev] | [next] | [standalone]

#85465 — Which newsreader (was Re: A plea...)

On 18/07/2022 01:24, Ben Bacarisse wrote:
> My newsreader has a scoring system that is far more sophisticated than a
> kill file.  I can even "score down" sub-threads where PO jumps in to
> poison the thread.  The trouble is that newbies don't do this sort of
> thing.  One look at comp.lang.c++ in GG and they will go elsewhere.

Which newsreader are you using? It doesn't plant the agent name.

(I'm using Thunderbird which has developed a really annoying bug. It 
hides all threads, not just the unread ones, and forgets the sort 
settings. For some groups at random...)

Andy

[toc] | [prev] | [next] | [standalone]

#85467 — Re: Which newsreader (was Re: A plea...)

Vir Campestris <vir.campestris@invalid.invalid> writes:

> Which newsreader are you using? It doesn't plant the agent name.

Gnus.  I thought it did announce itself, or I'd have said.  Maybe
something has changed over the years.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]

#85469 — Re: Which newsreader (was Re: A plea...)

Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
> Vir Campestris <vir.campestris@invalid.invalid> writes:
>
>> Which newsreader are you using? It doesn't plant the agent name.
>
> Gnus.  I thought it did announce itself, or I'd have said.  Maybe
> something has changed over the years.

That's odd.  I use Gnus, and it inserts this header line:

    User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]

#85473 — Re: Which newsreader (was Re: A plea...)

On 19/07/2022 02:27, Keith Thompson wrote:
> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>> Vir Campestris <vir.campestris@invalid.invalid> writes:
>>
>>> Which newsreader are you using? It doesn't plant the agent name.
>>
>> Gnus.  I thought it did announce itself, or I'd have said.  Maybe
>> something has changed over the years.
> 
> That's odd.  I use Gnus, and it inserts this header line:
> 
>      User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
> 

Perhaps Ben has been secretly posting from a Windows machine, and has 
turned off the User-Agent line so that no one sees it :-)

[toc] | [prev] | [next] | [standalone]

#85483 — Re: Which newsreader (was Re: A plea...)

On 7/19/2022 12:23 AM, David Brown wrote:
> On 19/07/2022 02:27, Keith Thompson wrote:
>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>>> Vir Campestris <vir.campestris@invalid.invalid> writes:
>>>
>>>> Which newsreader are you using? It doesn't plant the agent name.
>>>
>>> Gnus.  I thought it did announce itself, or I'd have said.  Maybe
>>> something has changed over the years.
>>
>> That's odd.  I use Gnus, and it inserts this header line:
>>
>>      User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
>>
> 
> Perhaps Ben has been secretly posting from a Windows machine, and has 
> turned off the User-Agent line so that no one sees it :-)
> 

LOL!

[toc] | [prev] | [next] | [standalone]

#85475 — Re: Which newsreader (was Re: A plea...)

On Mon, 18 Jul 2022 17:27:03 -0700
Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>> Vir Campestris <vir.campestris@invalid.invalid> writes:
>>
>>> Which newsreader are you using? It doesn't plant the agent name.
>>
>> Gnus.  I thought it did announce itself, or I'd have said.  Maybe
>> something has changed over the years.
>
>That's odd.  I use Gnus, and it inserts this header line:
>
>    User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

Emacs? Don't tell me its now a newsreader too?

[toc] | [prev] | [next] | [standalone]

#85477 — Re: Which newsreader (was Re: A plea...)

On 19/07/2022 10:29, Muttley@dastardlyhq.com wrote:
> On Mon, 18 Jul 2022 17:27:03 -0700
> Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>>> Vir Campestris <vir.campestris@invalid.invalid> writes:
>>>
>>>> Which newsreader are you using? It doesn't plant the agent name.
>>>
>>> Gnus.  I thought it did announce itself, or I'd have said.  Maybe
>>> something has changed over the years.
>>
>> That's odd.  I use Gnus, and it inserts this header line:
>>
>>     User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
> 
> Emacs? Don't tell me its now a newsreader too?
> 

As the saying goes, the only difference between Emacs and a complete OS 
is the lack of a simple text editor.  Yes, Emacs has a newsreader.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.c++

csiph-web