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


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

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

From John Levine <johnl@taugh.com>
Newsgroups comp.lang.c++, comp.arch, comp.lang.fortran
Subject Re: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups
Date 2023-11-01 13:47 +0000
Organization Taughannock Networks
Message-ID <uhtktv$1re4$1@gal.iecc.com> (permalink)
References <uhrv9b$1833l$1@dont-email.me> <a1e3kihl2o606a97g3746247qurdl0alfm@4ax.com> <uhtaqa$2dpi$1@gal.iecc.com> <kvg4ki9573mpia1vc35s0u4nlis86ld9kf@4ax.com>

Cross-posted to 3 groups.

Show all headers | View raw


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

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


Thread

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

csiph-web