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

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

apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups

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

Contents

  apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Lynn McGuire <lynnmcguire5@gmail.com> - 2023-10-31 17:32 -0500
    Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups George Neuner <gneuner2@comcast.net> - 2023-10-31 22:31 -0400
      Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups doctor@doctor.nl2k.ab.ca (The Doctor) - 2023-11-01 03:15 +0000
      Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups John Levine <johnl@taugh.com> - 2023-11-01 10:55 +0000
        Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups George Neuner <gneuner2@comcast.net> - 2023-11-01 09:06 -0400
          Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups John Levine <johnl@taugh.com> - 2023-11-01 13:47 +0000
      Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-11-01 14:52 -0400
    Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-11-01 06:40 -0600
      Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups John Levine <johnl@taugh.com> - 2023-11-01 13:03 +0000
        Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-11-01 12:14 -0600
          Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-11-01 14:53 -0400
          Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Michael S <already5chosen@yahoo.com> - 2023-11-01 22:12 +0200
            Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-11-01 14:19 -0600
              Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Retro Guy <retroguy@novabbs.org> - 2023-11-01 13:24 -0700
                Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-11-01 14:26 -0700
                Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-11-01 17:22 -0600
                  Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-11-01 23:35 -0400
              Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Stephen Fuld <sfuld@alumni.cmu.edu.invalid> - 2023-11-01 14:31 -0700
                Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Jack <invalid@invalid.net> - 2023-11-01 22:55 +0000
                  Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups BGB <cr88192@gmail.com> - 2023-11-04 02:18 -0500
      Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups red floyd <no.spam.here@its.invalid> - 2023-11-01 22:05 -0700
        Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-11-02 01:41 -0400
        Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups David Brown <david.brown@hesbynett.no> - 2023-11-02 09:07 +0100
        Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups wolfgang kern <nowhere@never.at> - 2023-11-03 11:25 +0100
    Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Branimir Maksimovic <branimir.maksimovic@icloud.com> - 2023-11-02 11:45 +0000
    Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Quadibloc <quadibloc@servername.invalid> - 2023-11-05 20:19 +0000

Page 1 of 2  [1] 2  Next page →

#117454 — apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups

Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read 
only at google groups to stop the spam floods.

Lynn

[toc] | [next] | [standalone]

#117455

On Tue, 31 Oct 2023 17:32:11 -0500, Lynn McGuire
<lynnmcguire5@gmail.com> wrote:

>Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read 
>only at google groups to stop the spam floods.
>
>Lynn

You mean the spam floods that Google openly condones and possibly also
facilitates in order to promote its own group services?

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

#117456

In article <a1e3kihl2o606a97g3746247qurdl0alfm@4ax.com>,
George Neuner  <gneuner2@comcast.net> wrote:
>On Tue, 31 Oct 2023 17:32:11 -0500, Lynn McGuire
><lynnmcguire5@gmail.com> wrote:
>
>>Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read 
>>only at google groups to stop the spam floods.
>>
>>Lynn
>
>You mean the spam floods that Google openly condones and possibly also
>facilitates in order to promote its own group services?

Apt way of putting it!
-- 
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Today is not tomorrow, and this world provides no guarantees. -unknown https://mindspring.com

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

#117457

According to George Neuner  <gneuner2@comcast.net>:
>>Lynn
>
>You mean the spam floods that Google openly condones and possibly also
>facilitates in order to promote its own group services?

I think you vastly overestimate how much anyone at Google cares about Groups.
The whole thing has been on autopilot for years, it can't possibly be making
them enough money to deal with the hassle.

FWIW I get plenty of spam directly from Groups when people yet again load
up a spam list and blast out mail in languages I cannot read.



-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

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

#117462

On Wed, 1 Nov 2023 10:55:06 -0000 (UTC), John Levine <johnl@taugh.com>
wrote:

>According to George Neuner  <gneuner2@comcast.net>:
>>>Lynn
>>
>>You mean the spam floods that Google openly condones and possibly also
>>facilitates in order to promote its own group services?
>
>I think you vastly overestimate how much anyone at Google cares about Groups.
>The whole thing has been on autopilot for years, it can't possibly be making
>them enough money to deal with the hassle.

Maybe.  But remember that Google trades in eyeballs ... the money, in
some sense, is secondary.  


"group" is overloaded.

Google Groups (GG) is a unified interface that provides access to
Usenet, public mailing lists, and to Google's own group services.

But there is a substantial difference: Google offers spam filtering to
its own groups, while denying it to others.


>FWIW I get plenty of spam directly from Groups when people yet again load
>up a spam list and blast out mail in languages I cannot read.

Sure it can happen.  

GG's spam filtering has to be opted into by the group administrator.
However, there is no way provided for an outside group to do that, so
even those non-Google Usenet groups and mailing lists that /have/
living administrators have no way to opt into Google's spam filtering.

Also, my experience with GG has been that its spam filtering only
checks posts made via email (the "list" interface).  It seems that
posts made directly via the web UI are checked only for abusive
language (and then only in English), and once accepted they can be
removed only by the group adminstrator or via user complaints.


The major point here is that Google provides (some semblence of) spam
filtering - but only for its own groups.

YMMV.

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

#117463

It appears that George Neuner  <gneuner2@comcast.net> said:
>The major point here is that Google provides (some semblence of) spam
>filtering - but only for its own groups.

This is completely consistent with it being on autopilot. Someone
built the spam filter for their own groups, nobody got around to
making it work with usenet. I can easily imagine them saying there's
so much garbage in usenet from other places, what difference would
it make?

As the old saw reminds us, don't assume malice until you've ruled out
incompetence.

-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

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

#117467

On 10/31/23 22:31, George Neuner wrote:
> On Tue, 31 Oct 2023 17:32:11 -0500, Lynn McGuire
> <lynnmcguire5@gmail.com> wrote:
>
>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>> read only at google groups to stop the spam floods.
>>
>> Lynn
>
> You mean the spam floods that Google openly condones and possibly also
> facilitates in order to promote its own group services?

How exactly is that supposed to work? What are the group services that
it's promoting, and how does make it's own news feed unreadable serve to
promote them?

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

#117460

Lynn McGuire <lynnmcguire5@gmail.com> writes:

> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
> read only at google groups to stop the spam floods.

No, I'm reading through Eternal September. Blocking posts with Thai
characters eliminates nearly all of the flood for me (but geez, it's
awful that it's necessary).

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

#117461

According to Joe Pfeiffer  <pfeiffer@cs.nmsu.edu>:
>Lynn McGuire <lynnmcguire5@gmail.com> writes:
>
>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>> read only at google groups to stop the spam floods.
>
>No, I'm reading through Eternal September. 

That's "read only" as in they don't let people post new articles.

People continue to read those groups all over the place.  You
couldn't stop if if you wanted to.

-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

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

#117464

John Levine <johnl@taugh.com> writes:

> According to Joe Pfeiffer  <pfeiffer@cs.nmsu.edu>:
>>Lynn McGuire <lynnmcguire5@gmail.com> writes:
>>
>>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>>> read only at google groups to stop the spam floods.
>>
>>No, I'm reading through Eternal September. 
>
> That's "read only" as in they don't let people post new articles.
>
> People continue to read those groups all over the place.  You
> couldn't stop if if you wanted to.

Ummm.... so they allow followups but not new topics?

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

#117468

On 11/1/23 14:14, Joe Pfeiffer wrote:
> John Levine <johnl@taugh.com> writes:
>
>> According to Joe Pfeiffer <pfeiffer@cs.nmsu.edu>:
>>> Lynn McGuire <lynnmcguire5@gmail.com> writes:
>>>
>>>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>>>> read only at google groups to stop the spam floods.
>>>
>>> No, I'm reading through Eternal September. 
>>
>> That's "read only" as in they don't let people post new articles.
>>
>> People continue to read those groups all over the place. You
>> couldn't stop if if you wanted to.
>
> Ummm.... so they allow followups but not new topics?

No, GG no longer allow posting new messages, or follow-ups to those
newsgroups. The only new messages you see on GG were posted elsewhere.

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

#117475

On Wed, 01 Nov 2023 12:14:54 -0600
Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:

> John Levine <johnl@taugh.com> writes:
> 
> > According to Joe Pfeiffer  <pfeiffer@cs.nmsu.edu>:  
> >>Lynn McGuire <lynnmcguire5@gmail.com> writes:
> >>  
> >>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
> >>> read only at google groups to stop the spam floods.  
> >>
> >>No, I'm reading through Eternal September.   
> >
> > That's "read only" as in they don't let people post new articles.
> >
> > People continue to read those groups all over the place.  You
> > couldn't stop if if you wanted to.  
> 
> Ummm.... so they allow followups but not new topics?

Read-only. No posting. Neither newtopics nor followups. None. Nada.

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

#117476

Michael S <already5chosen@yahoo.com> writes:

> On Wed, 01 Nov 2023 12:14:54 -0600
> Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
>
>> John Levine <johnl@taugh.com> writes:
>> 
>> > According to Joe Pfeiffer  <pfeiffer@cs.nmsu.edu>:  
>> >>Lynn McGuire <lynnmcguire5@gmail.com> writes:
>> >>  
>> >>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>> >>> read only at google groups to stop the spam floods.  
>> >>
>> >>No, I'm reading through Eternal September.   
>> >
>> > That's "read only" as in they don't let people post new articles.
>> >
>> > People continue to read those groups all over the place.  You
>> > couldn't stop if if you wanted to.  
>> 
>> Ummm.... so they allow followups but not new topics?
>
> Read-only. No posting. Neither newtopics nor followups. None. Nada.

But I posted this followup to comp.arch through eternal-september.

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

#117477

On Wed, 01 Nov 2023 14:19:19 -0600
Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:

> Michael S <already5chosen@yahoo.com> writes:
> 
> > On Wed, 01 Nov 2023 12:14:54 -0600
> > Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
> >
> >> John Levine <johnl@taugh.com> writes:
> >> 
> >> > According to Joe Pfeiffer  <pfeiffer@cs.nmsu.edu>:  
> >> >>Lynn McGuire <lynnmcguire5@gmail.com> writes:
> >> >>  
> >> >>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
> >> >>> read only at google groups to stop the spam floods.  
> >> >>
> >> >>No, I'm reading through Eternal September.   
> >> >
> >> > That's "read only" as in they don't let people post new articles.
> >> >
> >> > People continue to read those groups all over the place.  You
> >> > couldn't stop if if you wanted to.  
> >> 
> >> Ummm.... so they allow followups but not new topics?
> >
> > Read-only. No posting. Neither newtopics nor followups. None. Nada.
> 
> But I posted this followup to comp.arch through eternal-september.

You can post from anywhere you want that carries the group, you just
can't post from google groups

-- 
Retro Guy

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

#117481

On 11/1/2023 1:24 PM, Retro Guy wrote:
> On Wed, 01 Nov 2023 14:19:19 -0600
> Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
> 
>> Michael S <already5chosen@yahoo.com> writes:
>>
>>> On Wed, 01 Nov 2023 12:14:54 -0600
>>> Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
>>>
>>>> John Levine <johnl@taugh.com> writes:
>>>>
>>>>> According to Joe Pfeiffer  <pfeiffer@cs.nmsu.edu>:
>>>>>> Lynn McGuire <lynnmcguire5@gmail.com> writes:
>>>>>>   
>>>>>>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>>>>>>> read only at google groups to stop the spam floods.
>>>>>>
>>>>>> No, I'm reading through Eternal September.
>>>>>
>>>>> That's "read only" as in they don't let people post new articles.
>>>>>
>>>>> People continue to read those groups all over the place.  You
>>>>> couldn't stop if if you wanted to.
>>>>
>>>> Ummm.... so they allow followups but not new topics?
>>>
>>> Read-only. No posting. Neither newtopics nor followups. None. Nada.
>>
>> But I posted this followup to comp.arch through eternal-september.
> 
> You can post from anywhere you want that carries the group, you just
> can't post from google groups
> 

We can still use google groups for some searching purposes. Remember 
when they, Google, tried to outright ban comp.lang.c a while back? Not 
even able to read it...

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

#117484

Retro Guy <retroguy@novabbs.org> writes:

> On Wed, 01 Nov 2023 14:19:19 -0600
> Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
>
>> Michael S <already5chosen@yahoo.com> writes:
>> 
>> > On Wed, 01 Nov 2023 12:14:54 -0600
>> > Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
>> >
>> >> John Levine <johnl@taugh.com> writes:
>> >> 
>> >> > According to Joe Pfeiffer  <pfeiffer@cs.nmsu.edu>:  
>> >> >>Lynn McGuire <lynnmcguire5@gmail.com> writes:
>> >> >>  
>> >> >>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>> >> >>> read only at google groups to stop the spam floods.  
>> >> >>
>> >> >>No, I'm reading through Eternal September.   
>> >> >
>> >> > That's "read only" as in they don't let people post new articles.
>> >> >
>> >> > People continue to read those groups all over the place.  You
>> >> > couldn't stop if if you wanted to.  
>> >> 
>> >> Ummm.... so they allow followups but not new topics?
>> >
>> > Read-only. No posting. Neither newtopics nor followups. None. Nada.
>> 
>> But I posted this followup to comp.arch through eternal-september.
>
> You can post from anywhere you want that carries the group, you just
> can't post from google groups

Ah, OK. When I originally posted that I was reading from e-s, it was
pointed out to me that I couldn't post. Which seemed very odd, under the
circumstances.

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

#117485

On 11/1/23 19:22, Joe Pfeiffer wrote:
> Retro Guy <retroguy@novabbs.org> writes:
...
>> You can post from anywhere you want that carries the group, you just
>> can't post from google groups
>
> Ah, OK. When I originally posted that I was reading from e-s, it was
> pointed out to me that I couldn't post. Which seemed very odd, under the
> circumstances.

You misunderstood. No one said you couldn't post to eternal-september.

On 11/1/23 09:03, John Levine wrote:
> According to Joe Pfeiffer <pfeiffer@cs.nmsu.edu>:
>> Lynn McGuire <lynnmcguire5@gmail.com> writes:
>>
>>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>>> read only at google groups to stop the spam floods.

Notice: "at Google Groups", he didn't say anything about
eternal-september's policies.

>>
>> No, I'm reading through Eternal September.
>
> That's "read only" as in they don't let people post new articles.

"they" refers to Google, it doesn't apply to eternal-september.

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

#117482

On 11/1/2023 1:19 PM, Joe Pfeiffer wrote:
> Michael S <already5chosen@yahoo.com> writes:
> 
>> On Wed, 01 Nov 2023 12:14:54 -0600
>> Joe Pfeiffer <pfeiffer@cs.nmsu.edu> wrote:
>>
>>> John Levine <johnl@taugh.com> writes:
>>>
>>>> According to Joe Pfeiffer  <pfeiffer@cs.nmsu.edu>:
>>>>> Lynn McGuire <lynnmcguire5@gmail.com> writes:
>>>>>   
>>>>>> Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now
>>>>>> read only at google groups to stop the spam floods.
>>>>>
>>>>> No, I'm reading through Eternal September.
>>>>
>>>> That's "read only" as in they don't let people post new articles.
>>>>
>>>> People continue to read those groups all over the place.  You
>>>> couldn't stop if if you wanted to.
>>>
>>> Ummm.... so they allow followups but not new topics?
>>
>> Read-only. No posting. Neither newtopics nor followups. None. Nada.
> 
> But I posted this followup to comp.arch through eternal-september.

There has been some confusion in this thread recently.  Anyone with an 
account can read and post messages using Eternal September.  The "read 
only" is apparently just Google Groups.  That is, anyone can read any 
article through Google Groups, but no one can post new articles nor 
replies to the group using Google Groups.



-- 
  - Stephen Fuld
(e-mail address disguised to prevent spam)

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

#117483

On 01/11/2023 21:31, Stephen Fuld wrote:
>
> There has been some confusion in this thread recently.  Anyone with an 
> account can read and post messages using Eternal September.  The "read 
> only" is apparently just Google Groups. That is, anyone can read any 
> article through Google Groups, but no one can post new articles nor 
> replies to the group using Google Groups.
>
>
>

There is another server called "paganini.bofh.team". You don't need an 
account but spam is not allowed. People abusing the server will have 
their IP address blocked.

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

#117545

On 11/1/2023 5:55 PM, Jack wrote:
> On 01/11/2023 21:31, Stephen Fuld wrote:
>>
>> There has been some confusion in this thread recently.  Anyone with an
>> account can read and post messages using Eternal September.  The "read
>> only" is apparently just Google Groups. That is, anyone can read any
>> article through Google Groups, but no one can post new articles nor
>> replies to the group using Google Groups.
>>
>>
>>
> 
> There is another server called "paganini.bofh.team". You don't need an
> account but spam is not allowed. People abusing the server will have
> their IP address blocked.
> 

IP blocking is a bit questionable though in this era of ISP grade NAT 
and similar (say, the IP address they see on their cable modem is 
10.x.x.x; with some other IP address visible to the outside world), and 
with a dynamic external IP address.

So, if one person is posting spam with a given ISP, then blocking fails 
to block the spammer (as their external IP keeps changing), but will 
ultimately end up blocking random other people who happen to have their 
traffic routed through an IP address which was previously used for 
spamming (well, at least until their ISP causes their connections to 
jump over to some other IP address that hasn't been blocked yet).

...


It seems like a strategy that mostly (only) really makes sense in a 
context where one assumes that each node has a statically-assigned 
global IP address.

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web