EmbeddedRelated.com
Forums

comp.lang.embedded blocked on Google Groups!

Started by Rick C July 25, 2020
 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
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.
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?
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
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.
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
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
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.
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
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.