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


Groups > comp.arch.embedded > #29869

Re: comp.lang.embedded blocked on Google Groups!

From David Brown <david.brown@hesbynett.no>
Newsgroups comp.arch.embedded
Subject Re: comp.lang.embedded blocked on Google Groups!
Date 2020-07-28 17:20 +0200
Organization A noiseless patient Spider
Message-ID <rfpfnn$k94$1@dont-email.me> (permalink)
References <8099b54f-7161-4616-8b42-f35fdb50c9f8o@googlegroups.com> <rfjobj$25v$1@dont-email.me> <Eoy*GJaYx@news.chiark.greenend.org.uk>

Show all headers | View raw


On 28/07/2020 15:09, Theo wrote:
> David Brown <david.brown@hesbynett.no> wrote:
>> It seems to be working fine for real newsservers and real newsreaders.
>> (It's not a group I follow, but I checked it out for you.)  Perhaps it's
>> just Google Groups that sees a problem.  GG posters are usually the
>> source of spam and floods - maybe Google has started doing something
>> about it.
> 
> uk.telecom was troubled by drugs spam from Google Groups posters.
> The group got blocked in a similar way, making the archive inaccessible.
> It said the group owner could get it unblocked.
> People raised tickets with Google 'support', who didn't understand that
> there was such a thing as Usenet groups and they have no owner.
> Eventually the support agent managed to understand and said they would take
> it further.  Nothing happened.
> Someone said they knew someone in Google and would take it up with them.
> It's still blocked.
> 

For most Usenet users, it's often a good thing that Google Groups blocks
posting to a group.  Obviously GG is not the source of /all/ problem
posters, but they have a heavy share of them - people who can't get
attributions right, can't get line lengths right, can't trim, fly-by
posters, spammers, and especially necroposters.  There are certainly
plenty of good posters that use GG (such as Rick, who started this
thread), but most of these can move to a real newserver and newsclient
without too much disruption.

But blocking the searchable archives is a different matter.  If Google
were to make its interface read-only, I think a lot of us would be happy.

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

comp.lang.embedded blocked on Google Groups! Rick C <gnuarm.deletethisbit@gmail.com> - 2020-07-25 16:06 -0700
  Re: comp.lang.embedded blocked on Google Groups! David Brown <david.brown@hesbynett.no> - 2020-07-26 13:10 +0200
    Re: comp.lang.embedded blocked on Google Groups! Theo <theom+news@chiark.greenend.org.uk> - 2020-07-28 14:09 +0100
      Re: comp.lang.embedded blocked on Google Groups! David Brown <david.brown@hesbynett.no> - 2020-07-28 17:20 +0200
        Re: comp.lang.embedded blocked on Google Groups! Grant Edwards <invalid@invalid.invalid> - 2020-07-28 15:27 +0000
          Re: comp.lang.embedded blocked on Google Groups! zoidberg@planet.express (John A. Zoidberg) - 2020-07-29 09:12 +0000
            Re: comp.lang.embedded blocked on Google Groups! Dimiter_Popoff <dp@tgi-sci.com> - 2020-07-29 15:50 +0300
        Re: comp.lang.embedded blocked on Google Groups! Rick C <gnuarm.deletethisbit@gmail.com> - 2020-07-28 10:24 -0700
          Re: comp.lang.embedded blocked on Google Groups! David Brown <david.brown@hesbynett.no> - 2020-07-28 20:45 +0200
            Re: comp.lang.embedded blocked on Google Groups! Rick C <gnuarm.deletethisbit@gmail.com> - 2020-07-28 11:47 -0700
  Re: comp.lang.embedded blocked on Google Groups! Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2020-07-26 14:41 +0200
  Re: comp.lang.embedded blocked on Google Groups! john.ladasky@gmail.com - 2020-08-01 12:36 -0700
    Re: comp.lang.embedded blocked on Google Groups! Rick C <gnuarm.deletethisbit@gmail.com> - 2020-08-01 16:00 -0700

csiph-web