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

Groups > comp.arch.embedded > #29859 > unrolled thread

comp.lang.embedded blocked on Google Groups!

Back to article view | Back to comp.arch.embedded

Contents

  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

#29859 — comp.lang.embedded blocked on Google Groups!

 Banned Content Warning
The group you are attempting to view (comp.lang.forth) has been identified as containing spam, malware, or other malicious content. Content in this group is now limited to view-only mode for those with access.

Group owners can request an appeal after they have taken steps to clean up potentially offensive content in the forum. For more information about content policies on Google Groups see our Help Center article on abuse and our Terms of Service. 


WTF!!!???  

Anyone know what is going on?  Was this some spam attack or did someone report the bickering as spam?  

-- 

  Rick C.

  - Get 1,000 miles of free Supercharging
  - Tesla referral code - https://ts.la/richard11209

[toc] | [next] | [standalone]

#29861

On 26/07/2020 01:06, Rick C wrote:
> Banned Content Warning The group you are attempting to view
> (comp.lang.forth) has been identified as containing spam, malware, or
> other malicious content. Content in this group is now limited to
> view-only mode for those with access.
> 
> Group owners can request an appeal after they have taken steps to
> clean up potentially offensive content in the forum. For more
> information about content policies on Google Groups see our Help
> Center article on abuse and our Terms of Service.
> 
> 
> WTF!!!???
> 
> Anyone know what is going on?  Was this some spam attack or did
> someone report the bickering as spam?
> 

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.

But it strikes me as yet another reason why it is long past time to dump
that broken client and get a real newsreader and real newsserver.

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

#29868

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.

Theo

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

#29869

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.

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

#29870

On 2020-07-28, David Brown <david.brown@hesbynett.no> wrote:

> For most Usenet users, it's often a good thing that Google Groups blocks
> posting to a group.

You mean there are people who haven't plonked all posts from GG?  I
told slrn to do that years and years and years ago.

--
Grant

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

#29874

Grant Edwards <invalid@invalid.invalid> wrote:

> You mean there are people who haven't plonked all posts from GG?

I did, but after more and more decent people started using GG due to 
shortage of available newsservers, I removed this rule.

-- 
A misplaced decimal point will always end up where it will do the
greatest damage.

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

#29875

On 7/29/2020 12:12, John A. Zoidberg wrote:
> Grant Edwards <invalid@invalid.invalid> wrote:
> 
>> You mean there are people who haven't plonked all posts from GG?
> 
> I did, but after more and more decent people started using GG due to
> shortage of available newsservers, I removed this rule.
> 

I view this group - and occasionally some other, like SED - mainly
via google groups; when I post I use a news thingie, Thunderbird.
I think I saw the newsserver (eternal September) not working
once or twice last few years, may be last 10 years - but I am
not a hugely frequent poster.

Not so sure what spam via google groups the talk is about, looking
at CAE every day it takes months between the odd spam posts.
Of course the text reformatting is somewhat unpredictable if one
posts without recent experience with their web interface.

Dimiter

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

#29871

On Tuesday, July 28, 2020 at 11:20:27 AM UTC-4, David Brown wrote:
> 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.

God, what a whiner.  How can you stand to even be on the Internet? 

-- 

  Rick C.

  + Get 1,000 miles of free Supercharging
  + Tesla referral code - https://ts.la/richard11209

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

#29872

On 28/07/2020 19:24, Rick C wrote:
> On Tuesday, July 28, 2020 at 11:20:27 AM UTC-4, David Brown wrote:
>> 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.
> 
> God, what a whiner.  How can you stand to even be on the Internet? 
> 

Perhaps I was a little hasty in mentioning Rick.  But I still have hopes
that you will leave the dark side one day.

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

#29873

On Tuesday, July 28, 2020 at 2:45:36 PM UTC-4, David Brown wrote:
> On 28/07/2020 19:24, Rick C wrote:
> > On Tuesday, July 28, 2020 at 11:20:27 AM UTC-4, David Brown wrote:
> >> 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.
> > 
> > God, what a whiner.  How can you stand to even be on the Internet? 
> > 
> 
> Perhaps I was a little hasty in mentioning Rick.  But I still have hopes
> that you will leave the dark side one day.

Yeah, that's what I expected rather than cleaning up your act. 

-- 

  Rick C.

  -- Get 1,000 miles of free Supercharging
  -- Tesla referral code - https://ts.la/richard11209

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

#29862

Am 26.07.2020 um 01:06 schrieb Rick C:
>   Banned Content Warning
> The group you are attempting to view (comp.lang.forth) 
........................................^^^^^^^^^^^^^^^^

Doesn't look like that says comp.arch.embedded there, does it?

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

#29905

Google Groups introduced a new interface "with a fresh new look" a week ago.  Simultaneously, major newsgroups like this one, and comp.lang.python, were locked out of Google Groups.  I saw the message you posted here in multiple places.

I was starting to think about how I could find an alternate news server, but I decided to check Google Groups one more time.  As of today, it is working again.  I hope it stays that way.

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

#29906

On Saturday, August 1, 2020 at 3:36:58 PM UTC-4, john....@gmail.com wrote:
> Google Groups introduced a new interface "with a fresh new look" a week ago.  Simultaneously, major newsgroups like this one, and comp.lang.python, were locked out of Google Groups.  I saw the message you posted here in multiple places.
> 
> I was starting to think about how I could find an alternate news server, but I decided to check Google Groups one more time.  As of today, it is working again.  I hope it stays that way.

I still use the classic interface.  I have no idea why they feel a need to change thing that appear to work fine without having a clear idea of what they want to "fix".  I can't see anything better about it and the organization seems to make some things less useful. 

-- 

  Rick C.

  -+ Get 1,000 miles of free Supercharging
  -+ Tesla referral code - https://ts.la/richard11209

[toc] | [prev] | [standalone]

Back to top | Article view | comp.arch.embedded

csiph-web