Live data from Hacker News

Comp.lang.c Google Group has been banned

groups.google.com

121–130 of 199 posts

Re: Comp.lang.c Google Group has been banned

#121
post #11

Probably some automated spam detector got it banned. Here's the ban message for posterity: https://i.imgur.com/0lFapQ1.png

"Back to safety". Gotta love corporate BS

By using this phrasing as loosely as big tech does, they have trained a lot of people to ignore these warnings.

Even I started to raise an eyebrow whenever one of these companies claims to do something for my "safety".

Re: Comp.lang.c Google Group has been banned

#122
post #111

Earlier quoted context omitted.

First of all, thank you for making this available. However without Search functionality the utility of this archive is very limited.

Is Google indexing the content? Maybe you can search it that way.

"site:usenetarchives.com" has a bunch of results, so it seems so.

Re: Comp.lang.c Google Group has been banned

#123
post #38

Earlier quoted context omitted.

But if you want to find a particular post, it really depends on the retention policy of the server you use. Free ones may have a year of retention. Commercial one's have 12 years or so. The only one that I know of where one can find posts further back than that is Google groups.

astranews has comp.lang.c back to 30 June 2003.

Astraweb's landing page states they have 4000 days of retention (which corresponds to March 2010 as of the time of this post). I guess certain text groups have signfiicantly longer retention times.

Re: Comp.lang.c Google Group has been banned

#124
post #116

Earlier quoted context omitted.

Not everything is deserving of being treated as historical artifacts worthy of retention. A friend has lamented that when he was in college in the late 80s, he used USENET as a way to connect with people and work through some pretty heavy emotional challenges. Retaining his personal struggles is hardly "history" - if anything, the historical value of retaining the struggles of one inconsequential person is far lower…

To a sociologist connect with people and work through some pretty heavy emotional challenges is a goodmine and insight into history.

Not sure why the sociologist’s desires should take precedence over the original posters’.

Re: Comp.lang.c Google Group has been banned

#125

Some fun comp.lang.c history: Dennis Ritchie posted, sharing an extremely early version of a C compiler. Richard Heathfield (well known C book author) jokingly chided Ritchie for posting something off-topic, as it was not part of ANSI C. In typical Usenet fashion, this triggered a huge thread, arguing over the appropriateness of the joke. Even Linus Torvalds got involved. Apparently Heathfield emailed Ritchie private…

Actually the annoying thing here is, that the pointless discussion is achieved, while the link to the source code doesn't work (maybe temporarily overloaded from HN? Maybe dead)

Re: Comp.lang.c Google Group has been banned

#126
post #70

Earlier quoted context omitted.

Remember when gay and lesbian bars were a thing; back when straight people steered clear of them because of the stigma? Not having the stigma is good overall, but in many places there's no longer queer-exclusive spaces. That whole segment of culture is rapidly becoming a thing of the past.

Isn’t that a good thing though? This reminds me of the people complaining cochlear implants are destroying deaf culture.

An absense of queer-exclusive spaces would be as much as a loss as the vanishing of any other major ethnic or cultural space.

Re: Comp.lang.c Google Group has been banned

#130

I am wondering if we could solve the current madness with arbitrary content policing by waiving copyright protection for monopolistic platforms and enforcing interoperability. Imagine if anyone was legally allowed to create their own fork of Reddit, or Google Groups, preserving the original content , and even being able to post new content through the fork, as if they did it directly. If google decided to ban some co…

> enforcing interoperability.

It's called "common carrier immunity".

Telephone companies have had it for decades, maybe even centuries. It works great. They're not responsible for words spoken on their telephone network as long as they don't regulate that content in any way.

Section 230 simply should have offered common carrier immunity to websites when they act as common carriers. Problem solved.

Post reply on HN