Live data from Hacker News

Some thoughts on social networking and Usenet (2018)

jfm.carcosa.net

61–70 of 81 posts

Re: Some thoughts on social networking and Usenet (2018)

#61

Earlier quoted context omitted.

Some are still going.. https://groups.google.com/u/1/g/sci.electronics.design https://groups.google.com/u/1/g/comp.arch https://groups.google.com/u/1/g/rec.arts.sf.written https://groups.google.com/u/1/g/rec.radio.amateur.misc https://groups.google.com/u/1/g/comp.compilers

rec.arts.sf.written was the one I was referring to.

Killfiles under slrn solved this fastly enough.

Re: Some thoughts on social networking and Usenet (2018)

#62
post #49

How was poster identity handled in Usenet/NNTP? From what I remember, it was just a "From:" header and spoofing was easy. Or was there more to it? (Maybe because most posters wrote to their local server which require auth, you could see which server the message originated from and decide if the sender's address matched the server address...? It's been so long.) If not, then Twitter, Mastodon, etc. all seem to have a…

It was the old internet. There was no identity verification.

One day identity verification will occur at the network level. Until then, we have all this half-baked shit.

Re: Some thoughts on social networking and Usenet (2018)

#63
post #5

In addition to the `trn` and Gnus readers that the article mentions, another great one was `strn`. They were much more powerful than any other forum interface I've seen since. Though the very compact thread views like in `old.reddit.com` and HN are nice.

Don't forget Nuntius, which was the best NNTP mac client. MT-NewsWatcher was pretty good too.

Good times.

Re: Some thoughts on social networking and Usenet (2018)

#64
post #12

Earlier quoted context omitted.

In 1996, my local ISP ran Usenet on the beefiest PC-platform machine I had ever seen: a dual Pentium-II 400 with 128MB of RAM and 6 9GB SCSI disks. At times Usenet ate most of a T1 (that's a 1.5Mb/s pipe). So if you want Usenet, right now, every $5/month minimal VM that I'm aware of has more than enough CPU, RAM, disk and I/O to support you and two dozen friends, as long as you don't take binaries froups.

> At times Usenet ate most of a T1 (that's a 1.5Mb/s pipe). How much of that was due to alt.binaries.*?

> How much of that was due to alt.binaries.?

Most ISPs stopped carrying .binaries.* groups because of this.

Re: Some thoughts on social networking and Usenet (2018)

#65
post #49

How was poster identity handled in Usenet/NNTP? From what I remember, it was just a "From:" header and spoofing was easy. Or was there more to it? (Maybe because most posters wrote to their local server which require auth, you could see which server the message originated from and decide if the sender's address matched the server address...? It's been so long.) If not, then Twitter, Mastodon, etc. all seem to have a…

> From what I remember, it was just a "From:" header and spoofing was easy.

Yes. Same was true of email back in the day.

Re: Some thoughts on social networking and Usenet (2018)

#66

Any of you archivers out there know whatever became of the Deja News Archive after Google bought it? https://www.wired.com/2001/02/google-buys-deja-archive/ This was integrated into Google seearch, it worked great for many years, and then it seems Google slowly chipped away at access to the archive and now it all but gone. I know about the various Usenet archives on archive.org (utzoo (rip), some CD usenet archive),…

Deja News -> Google Groups.

Re: Some thoughts on social networking and Usenet (2018)

#67
post #49

How was poster identity handled in Usenet/NNTP? From what I remember, it was just a "From:" header and spoofing was easy. Or was there more to it? (Maybe because most posters wrote to their local server which require auth, you could see which server the message originated from and decide if the sender's address matched the server address...? It's been so long.) If not, then Twitter, Mastodon, etc. all seem to have a…

> If not, then Twitter, Mastodon, etc. all seem to have a somewhat strong notion of identity.

Some of us would sign Usenet messages with PGP/GPG to deal with this. Lots of user didn't know what to do with the "geek code block" at the bottom of the message.

Re: Some thoughts on social networking and Usenet (2018)

#68

Some of the most interesting and intellectually interesting conversations I have every had online were on USENET back in the 80's. I literally made friends all over the world in fields spanning areas from model aircraft to electronics, software development and aerospace. Met a bunch of them. Visited each others' homes. Etc. Today? Geez. No comment. Every meaningful relationship I have online is from people I knew and…

I remember as a little kid getting some dude in Australia to somehow call us ( I believe over some type of IP phone or something) and he put the phone up next to the australian motoGP FM radio announcement. This was by far the best way to get the most up to date announcing on races. Now its so easy !

Re: Some thoughts on social networking and Usenet (2018)

#70

Part of the problem with Usenet is that it isn't "free" like Twitter and Facebook are. (They're free because they host ads, and there are all sorts of problems with that, of course, but you don't pay a monthly subscription to them). Way back, it used to be you got an NNTP server bundled with your ISP which was ok, because you were the only customer who knew what that was and how to use it, so you weren't creating a l…

Sounds like NNTP combined with BitTorrent.. Back in the day I remember dreaming ways to optimize the NNTP server- surely there was a better way than storing each article in a separate file.. but actually it was a very convenient to have a shell account on the same system that ran the server. This is why I enjoyed TheWorld (Software Tool & Die). You could cat the articles if you wanted. /usr/spool/news, C-News, innd (…

When you did you get on TheWorld? What was it like?
Post reply on HN