News for hackers. Stuff that matters.
Re:Classic Usenet posts on computer architecture, operating ... by mrweasel on Sunday May 19, 2024 @03:51AM (#40405109)
The older I get the more I feel like Usenet was/is a lost opportunity. With a few improvements if could have taken the place of Facebook (not the original connecting with friends version Facebook) and Reddit. It could have been a great option for local business promotion and news distribution, and the same segmentation into groups would map almost perfectly into subreddits.

It is decentralized, multiple clients where available and you could segment into as narrow topics as you'd like.

Re:Classic Usenet posts on computer architecture, operating ... by kseistrup on Sunday May 19, 2024 @04:51AM (#40405409)
@asjo over at koldfront.dk is still using NNTP for all sorts of things (RSS aggregator, blog engine, ActivityPub server): https://koldfront.dk/just_call_me_mr_nntp_1871

Indeed, it was a lost opportunity. The protocol os easy to understand, and it plays well with decentralization as you say, and with self hosting.

With Python 3.12 out, its nntplib module is scheduled for deletion/removal in v3.13. What a pity.

The NNTP protocol surely deserves a revival.

Re:Classic Usenet posts on computer architecture, operating ... by ktosobcy on Sunday May 19, 2024 @05:32AM (#40405593)
This!

I still hands on a couple of groups though the traffic there is getting thinner with each day...

It was simple. I wasn't forced with account (though would be nice/useful nowadays I guess with all the impersonation and whatnot), threading was awesome. Scoring+plonk was even more amazing. There was a problem with syncing what was read and not but that could be easily improved now...

I think I mostly miss scoring - it was such an amazing tool to manage/filter out desired content...

Re:Classic Usenet posts on computer architecture, operating ... by mmcgaha on Sunday May 19, 2024 @07:58AM (#40406328)
I hope the last post is in alt.obituaries for usenet itself. Unfortunately it will probably be a post about a free ebook download cross posted to half of usenet.
Re:Classic Usenet posts on computer architecture, operating ... by immibis on Sunday May 19, 2024 @05:34AM (#40405602)
There was some minor discussion in this direction in the thread about email 2.0: https://news.ycombinator.com/item?id=40392709

Bad service drives out good service just like bad money, for some reason. Centralized beats decentralized because convenience. The convenience is what they're paying to entice you to come into their home and let them eat your brains, and every single person falls for it, probably including you and me.

Classic Usenet is still around. If you have an email address, you can get an account on Eternal September. There aren't that many users. You can be one of them.

Re:Classic Usenet posts on computer architecture, operating ... by mr_mitm on Sunday May 19, 2024 @09:16AM (#40406753)
It's not just convenience. Having a centralized authority - with all its downsides - comes with some crucial advantages. They can:

* provide identities

* moderate content

* vouch for integrity

* enforce a consistent set of features

The same problems haunt email. It's also why Marlinspike was always against federating Signal. Decentralization comes with some hard problems.

Re:Classic Usenet posts on computer architecture, operating ... by bithead on Sunday May 19, 2024 @10:48AM (#40407324)
True enough but we know what scientology believes because of USENET (alt.religion.scientology). The church of scientology literally ran out of lawyers for DMCA takedowns, which don't work on USENET because it is structured like the internet.

NNTP needed things to be sure but the above issues have technical solutions that seemed out of reach not because they were too complex to solve, but is seemed as if society itself wanted multimedia web pages like a coke addict.

Also things like digital identity seemed to flag as innovation for such things stalled out around the time HTTP became rising. I remember moving data between mainframes from different vendors and what was once a set of problems that seemed intractable suddenly fell as TCP/UDP/IP took off with a suite of solutions that worked so well together.

USENet was a better place to get good information compared to web pages at that time in parts due to bad web site designs and DMCA takedowns, neither of which was an issue for NNTP. I like Reddit because (at least old.reddit) is similar to USENet in how it is structured.

Had NNTP adopted HTML and Netscape written a browser for news groups using HTML, the so-called 'world wide web' and it's anachronistic client-server model might not have effectively displaced NNTP.

Re:Classic Usenet posts on computer architecture, operating ... by mr_mitm on Sunday May 19, 2024 @05:37AM (#40405617)
Usenet has a few hard problems, no? Mostly related to moderation. You want to be able to edit or delete content, either your own, or, if you are a moderator, other content which turned out to be illegal later (which already implies content moderation before allowing content to be published). Spam is another big problem.

To avoid impersonation, you'd have to sign everything, which I guess is possible, but experience shows crypto done properly is a huge pain. We already see how unsatisfactory this works with email.

Plus, does usenet scale as well as, say, reddit? Sometimes heated threads are more like comment streams with probably dozens of comments per second.

How can these be solved with a few improvements?

Re:Classic Usenet posts on computer architecture, operating ... by ThinkBeat on Sunday May 19, 2024 @05:51AM (#40405681)
Impersonation and spam are things you find on other ways of running a forum.

On Usenet you can easily stop following a group or person.

Re:Classic Usenet posts on computer architecture, operating ... by mr_mitm on Sunday May 19, 2024 @05:58AM (#40405720)
Isn't spoofing an email sender address much easier than taking over an account on a web-based forum? I think forums are very robust against that, while email and usenet are not.
Re:Classic Usenet posts on computer architecture, operating ... by badgersnake on Sunday May 19, 2024 @08:32AM (#40406523)
Plonk
Re:Classic Usenet posts on computer architecture, operating ... by immibis on Sunday May 19, 2024 @05:43AM (#40405643)
A parallel copy of Usenet is used for piracy, with a posting volume measured in double-digit gigabits per second. It can probably handle Reddit.
Re:Classic Usenet posts on computer architecture, operating ... by mr_mitm on Sunday May 19, 2024 @05:56AM (#40405706)
That's regarding the size of the entries, not the frequency though. Many small comments in a short time frame will have a huge overhead.

Also, there is a reason why binary content was first frowned upon, then became essentially a paid feature. It's expensive.

Re:Classic Usenet posts on computer architecture, operating ... by throw0101c on Sunday May 19, 2024 @10:01AM (#40407036)
> You want to be able to edit or delete content, either your own, or, if you are a moderator, other content which turned out to be illegal later (which already implies content moderation before allowing content to be published).

Or you accept the fact that what you write is a permanent record. (Local admins can delete messages from their servers if there is a problem with the content.)

That being said, there are Control messages (RFC 5536 § 3.2.3), and one of the things that they can do is cancel an article (RFC 5537 § 5.3). You'd probably want to authenticate the cancel messages of course:

* http://fi.archive.ubuntu.com/ftp.isc.org/pub/pgpcontrol/READ...

* https://en.wikipedia.org/wiki/Control_message

Worth noting that you can't force servers to honour the cancel messages and delete the article on their local storage.

Re:Classic Usenet posts on computer architecture, operating ... by abc123abc123 on Sunday May 19, 2024 @05:54AM (#40405695)
Why? It works great. Since google dropped usenet access through the web, spam is down, discussions are great, and if there is no discussion start one. I'm enjoying usenet immensely!
Re:Classic Usenet posts on computer architecture, operating ... by sourcepluck on Sunday May 19, 2024 @06:19AM (#40405814)
How do you get set up and started?

I could trawl through a few blogs of course, but I'd be interested to hear what you do yourself for a current snapshot of usage. I think it sounds interesting myself, and have read some quite convincing propagandastic material from Harley Hahn about it working through some Unix book a little while back.

Re:Classic Usenet posts on computer architecture, operating ... by ptero on Sunday May 19, 2024 @07:38AM (#40406219)
eternal-september.org is a good, free option. But the frequency of usenet posting (at least on groups that I still look at) is pretty low...
Re:Classic Usenet posts on computer architecture, operating ... by sourcepluck on Thursday May 23, 2024 @06:45PM (#40460795)
Thanks, will have a look there.
Re:Classic Usenet posts on computer architecture, operating ... by actionfromafar on Sunday May 19, 2024 @06:07AM (#40405759)
Back in 1998 my ISP dropped NNTP because it was pretty expensive to run, it required large, fast SCSI disks and ate quite a bit of bandwidth, constantly. At the same time rather few customers used it, so it was an easy decision for them to just decommission that server.
Re:Classic Usenet posts on computer architecture, operating ... by immibis on Sunday May 19, 2024 @06:13AM (#40405782)
That must have been before the high-bandwidth binary side decoupled from the forum side.
Re:Classic Usenet posts on computer architecture, operating ... by actionfromafar on Sunday May 19, 2024 @07:23AM (#40406130)
Yes but no: my ISP never carried alt.binaries
Re:Classic Usenet posts on computer architecture, operating ... by immibis on Sunday May 19, 2024 @11:53PM (#40412114)
Current text volume is on the order of a few gigabytes per day, including spam.
Re:Classic Usenet posts on computer architecture, operating ... by actionfromafar on Monday May 20, 2024 @03:07AM (#40413055)
Way back then my ISP had a T1 shared among hundreds of customers. :-D
Re:Classic Usenet posts on computer architecture, operating ... by speckx on Sunday May 19, 2024 @09:26AM (#40406804)
I recall my ISP doing the same eventually around the same time. At first, they stopped carrying binary groups and, later, all of Usenet.
Re:Classic Usenet posts on computer architecture, operating ... by ChicagoDave on Sunday May 19, 2024 @07:59AM (#40406338)
There was horrible arrogant gatekeeping for new feeds, especially if you asked for a moderated feed.

Those gatekeepers never saw the train coming (web) and then it was too late.

Re:Classic Usenet posts on computer architecture, operating ... by treyd on Sunday May 19, 2024 @08:37AM (#40406553)
That's more of a social problem than a technical one. Although iterating on the technology ultimately circumvented it, it could have been addressed without completely throwing away usenet.
Re:Classic Usenet posts on computer architecture, operating ... by TheOtherHobbes on Sunday May 19, 2024 @09:49AM (#40406958)
Usenet was never thrown away. It's still there if you want it, but you'll have to pay to use it.

https://www.usenet.com/

What changed was the user profile. Late 80s/early 90s internet was used almost exclusively by academics and engineers. Mid-90s onwards it was open to everyone, and Usenet access was a free feature of most dial-up accounts.

Usenet was ground zero for that change, because university and corporate admins had to deal with a lot of new groups - including those devoted to binaries, and especially porn.

There was a lot of gatekeeping, but the useful groups either migrated or disappeared under spam, and the conversations moved elsewhere.

HN is probably the closest thing to the original culture, but HN's single page design means you don't get the intense focus and conversational momentum of Usenet's professional groups.

Re:Classic Usenet posts on computer architecture, operating ... by mg on Sunday May 19, 2024 @03:40AM (#40405056)
I wish there was a way to sort these by date.
Re:Classic Usenet posts on computer architecture, operating ... by Bewelge on Sunday May 19, 2024 @05:10AM (#40405487)
You can paste this into your console :-)

Not entirely sure that I parsed all the dates correctly. Simply used the first occurrence of "Date: **" for each link.

https://gist.github.com/Bewelge/1f42c4ba999128ae1ded6f0ecc63...

Re:Classic Usenet posts on computer architecture, operating ... by quotemstr on Sunday May 19, 2024 @02:14AM (#40404624)
https://yarchive.net/comp/sandboxes.html is an interesting example of Clarke's first law: " When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong."

The post, from Theodore Ts'o, argues that software sandboxing is, if not quite impossible, rather difficult: in his post, he argues that either the user or the sandboxed program has to configure a sandbox. The user won't know what to do, and the executable can't be trusted. The author neglects to consider a third possibility: the OS dictates the shape of all sandboxes and software conforms to fit. This is model we use in Android and iOS and increasingly even on conventional Linux (via snap and flatpak). Sandboxing is not only possible, but essential.

Anyway, being wrong is no great crime. Everyone's wrong sometimes. The author went on to do great things with the Linux kernel. It's interesting to think of why smart people are wrong and to be skeptical of claims of impossibly.

Re:Classic Usenet posts on computer architecture, operating ... by contingencies on Sunday May 19, 2024 @04:35AM (#40405328)
You can also profile the execution in a less trusted environment and use that to define the sandbox, like running Linux in NSA SEL learning mode. This allows a black box approach to systems monitoring which works well with secret, forgotten and proprietary systems and is good engineering practice for most systems anyway, whether hardware or software, as anomalies are often highly detectable.
Re:Classic Usenet posts on computer architecture, operating ... by immibis on Sunday May 19, 2024 @05:37AM (#40405615)
You can, but it doesn't work very well.
Re:Classic Usenet posts on computer architecture, operating ... by contingencies on Sunday May 19, 2024 @04:47PM (#40409632)
Au contraire, it works very well in many domains of engineering (source: I use it all the time). I suspect you may be viewing the general approach through a narrow lens of one particularly demanding requirement (targeting "absolute security"), and comparing an existing approach with input costs that are often considered high or unrealistic (eg. specialist manual configuration).

For example, if the target system is a software system, and the baseline is "no extra security", then running a full codebase coverage test battery across software with network activity monitoring, computation monitoring, memory monitoring, kernel API monitoring, filesystem monitoring, etc. is going to get you a really strong profile of what isn't used to reduce the effective attack surface. This can be done at multiple levels: system API restriction, filesystem restriction, resource restriction, firewalling, VLAN segmentation, intrusion detection system ruleset generation, etc. This is awesome versus manual config, as it is free, precise, adapts with upgrades once plugged in to CI/CD, and requires zero specialist humans... who often function to perform similar processes in an iterative fashion on a best-effort basis.

Re:Classic Usenet posts on computer architecture, operating ... by Veserv on Sunday May 19, 2024 @02:56AM (#40404805)
It is not even that. All you need is the program to present a “understandable” manifest of its requirements and you can choose to accept or deny. Standardized sandboxs just facilitate ease of use and analysis, and enable application developers to target easy-to-understand security models.

The problem with the post is that it assumes that the most important thing is making sure that all non-malicious programs run no matter how convoluted. It is the same thought process that makes people say nonsense like formal methods are impossible due to the halting problem. No, we can just reject unless you make it easy to analyze; halting problem averted.

Re:Classic Usenet posts on computer architecture, operating ... by quotemstr on Sunday May 19, 2024 @03:04AM (#40404844)
> It is not even that. All you need is the program to present a “understandable” manifest of its requirements and you can choose to accept or deny.

Sure. And if these understandable manifests contain requests only from a predefined set that the system provides, we call these requests "permissions" in the iOS and Android sense. You don't get to request arbitrary things and ask the user to approve them.

> The problem with the post is that it assumes that the most important thing is making sure that all non-malicious programs run no matter how convoluted

Agreed.

> No, we can just reject unless you make it easy to analyze; halting problem averted

Yes, and it's this idea that makes minimalism essential in OS design. The narrower your contract, the more flexibility you have to change your implementation.

Re:Classic Usenet posts on computer architecture, operating ... by Veserv on Sunday May 19, 2024 @03:38AM (#40405039)
Agreed. It was unclear from your original post if you were talking about coarse-grained sandboxs or more fine-grained systems.

To clarify, a system that defines coarse classes of sandboxs could declare a class of sandbox for non-networked applications, a sandbox for games, a sandbox for applications with storage exclusively for configuration data, etc. Such a system is different in many respects from a system that defines relatively fine-grained composable requirements. Obviously, a fine-grained system could be composed to present a model at the coarse abstraction level, but the way you target a application differs based on what abstraction level you are targeting.

Re:Classic Usenet posts on computer architecture, operating ... by immibis on Sunday May 19, 2024 @05:35AM (#40405608)
Okay, then every program demands every permission. Your choice is to let the program use your camera or to not use the program. And some of these programs are probably very important for your livelihood, so we know what the outcome is going to be.
Re:Classic Usenet posts on computer architecture, operating ... by aeonik on Sunday May 19, 2024 @08:36AM (#40406549)
I miss rooting my Android phone and spoofing access to the GPS or camera.

I could pipe arbitrary bits to any application.

[dead]
Re:Classic Usenet posts on computer architecture, operating ... by Taniwha on Sunday May 19, 2024 @03:27AM (#40404964)
uucp and the internet were not the same things - but both hosted usenet and mail.

The big issue with commercialising the internet was really that originally internet connected companies were prohibited from routing packets to 3rd parties, what really changed things was the change of that policy - after that anyone could join

Re:Classic Usenet posts on computer architecture, operating ... by DonHopkins on Sunday May 19, 2024 @03:47AM (#40405093)
Of course uucp and the internet are different, but seismo, later uunet, run by the same person, were central hubs where they connected, and ftp.uu.net was one of the main software distribution points. Before seismo became the most popular, it was Bell Labs ihnp4 (Indian Hill), decvax, ucbvax, mcvax in Europe, etc.

That's why email addresses in signatures and mailing lists were usually expressed relative to seismo like "...!seismo!foo!bar!baz!user" (pure uucp routing), or "foo!bar!baz!user@seismo" (mixed internet/usenet routing), or later "user%foo%bar%[email protected]" (uunet gateway with fully qualified domain name), because everybody knew how to get to seismo (later uunet).

Re:Classic Usenet posts on computer architecture, operating ... by Taniwha on Sunday May 19, 2024 @05:31AM (#40405587)
only if you happened to live in that geographical area (and seismo was a close routing) - I still have business cards with a ucbvax relative address, never used seismo
Re:Classic Usenet posts on computer architecture, operating ... by tomalbrc on Sunday May 19, 2024 @02:51AM (#40404788)
Can we not use ChatGPT to write garbage HN comments please
Re:Classic Usenet posts on computer architecture, operating ... by DonHopkins on Sunday May 19, 2024 @03:01AM (#40404828)
What do you mean by garbage? Is it incorrect in any way? As I stated, I used ChatGPT because I tried and failed to find the original sources. I checked all the information myself, and searched google groups and the wayback machine for the original sources, and linked to what I could find (like the suck.com Net.Mogul cards), but I don't have all the usenet and email archives any more.

Can you please constructively suggest some better citations that have the same information instead of just complaining? Or should I just leave out all that relevant information, even though I checked ChatGPT's results against what I know from being there at the time? Or would you rather I just not disclose that I used ChatGPT to write the comment, so as not to trigger you?

Edit: Gumby: then that's what he should have said. But I'm responding to what he did actually say. Were all the facts correct, according to your memory? And can you cite a better source with the same information? I'd be grateful and glad to rewrite the comment to point to that, then.

Re:Classic Usenet posts on computer architecture, operating ... by gumby on Sunday May 19, 2024 @03:17AM (#40404913)
Don, I’m guessing the complaint is really that sure, your comment is a piece of Usenet history, but not really germane to the post.
Re:Classic Usenet posts on computer architecture, operating ... by gary_0 on Sunday May 19, 2024 @03:24AM (#40404948)
Posting AI generated info-dumps is considered bad netiquette.
Re:Classic Usenet posts on computer architecture, operating ... by camus_absurd on Sunday May 19, 2024 @03:53AM (#40405119)
We’ll see for how long I guess
Re:Classic Usenet posts on computer architecture, operating ... by DonHopkins on Sunday May 19, 2024 @04:01AM (#40405157)
So was distributing commercial software over the Internet, which was my point. And I got flamed for that, too. ;)

I at least tried to find original sources first, included the ones I did find, fact checked and edited ChatGPT's output, and disclosed its use. What more do you want, that information to be lost, or people not to disclose ChatGPT's use to avoid being flamed for violating netiquette? Is it prohibited by HN guidelines? Should it be?

Is posting working code partially written by ChatGPT that solves a problem and has been checked and tested also a violation of netiquette? Where is the line? Or does it move over time?

Sounds like an interesting topic for an HN discussion to me...

Re:Classic Usenet posts on computer architecture, operating ... by pvg on Sunday May 19, 2024 @10:25AM (#40407186)
Sounds like an interesting topic for an HN discussion to me...

It's a mostly settled topic for now, you can find many moderation comments about it - don't use generated content in comments. The problem is that the overwhelming majority of LLM generated comments are not checked for accuracy, they're just random summaries of articles or unverified pastes of whatever the model spat out in response to a prompt. Even though you're trying to do this 'right' - checking and/or editing the output, disclosing the LLM use for the relevant part of the comment, etc - it's too difficult for anyone to tell the difference.

Re:Classic Usenet posts on computer architecture, operating ... by doener on Sunday May 19, 2024 @04:52AM (#40405414)
One of the Usenet postings that still gives me the chills is this on from Berlin November 10, 1989:

https://groups.google.com/g/eunet.politics/c/LbrVEM7zp-Y/m/a...

Re:Classic Usenet posts on computer architecture, operating ... by amadeuspagel on Sunday May 19, 2024 @06:02AM (#40405737)
I saw this on HN a year ago[1]. I was amazed to see people discuss this event that I only knew from documentaries just like we discuss so many things on HN.

[1]: https://news.ycombinator.com/item?id=35937637

Re:Classic Usenet posts on computer architecture, operating ... by xucian on Sunday May 19, 2024 @05:40AM (#40405635)
whoa, I just learned usenet was started in 1980. this is incredible
Re:Classic Usenet posts on computer architecture, operating ... by lionkor on Sunday May 19, 2024 @05:09AM (#40405485)
Thats madness. I sent it to my dad who lives in west berlin since 1950
Re:Classic Usenet posts on computer architecture, operating ... by macintux on Sunday May 19, 2024 @09:51AM (#40406977)
That thread is an interesting read. Predicting the future is hard.
Re:Classic Usenet posts on computer architecture, operating ... by cowboylowrez on Tuesday May 21, 2024 @10:53AM (#40429264)
"On the subject of reunification, the next day on the Today program on BCC Radio 4 they were interviewing various "notable" people about the situation. A very interesting comment was made by some notable Frenchman that Germany has only ever been unified between ~1890 and 1945 and it wasn't exactly as runaway success then."

1980's savagery could that even be typed today in polite circles? lol

Re:Classic Usenet posts on computer architecture, operating ... by amadeuspagel on Sunday May 19, 2024 @05:44AM (#40405648)
> There is also a vicious circle here, because the primary audience for a new programming language is existing programmers -- people who are already accustomed to using programming languages with English keywords. Folks who have trouble with English keywords probably aren't working as programmers, so their voices are not heard.[1]

This is a problem way beyond english and programming languages.

[1]: https://yarchive.net/comp/english.html

Re:Classic Usenet posts on computer architecture, operating ... by amadeuspagel on Sunday May 19, 2024 @05:54AM (#40405692)
> Why do you think Linux ends up being the most widely deployed Unix? It's avoided niches, it's avoided inbreeding, and not being too directed means that it doesn't get the problems you see with unbalanced systems.[1]

[1]: https://news.ycombinator.com/item?id=40404440

Re:Classic Usenet posts on computer architecture, operating ... by anthk on Sunday May 19, 2024 @06:55AM (#40405966)
For offline usage:

https://yarchive.net/downloads/

If you use something like Midnight Commander under GNU/Linux or BSD, you can directy read the files without extracting them, it's handy.

Re:Classic Usenet posts on computer architecture, operating ... by SyberShock on Sunday May 19, 2024 @09:57AM (#40407009)
For those who might think that NNTP does not scale, keep in mind that in its heyday Usenet was not the only NNTP network. There were countless niche NNTP servers not necessarily peering with Usenet. Some niche NNTP communities continue to thrive to this day.

A small closed network of just a few peers can service hundreds to thousands of participants. Social media architecture has accustomed users to having the whole world flooding their feed or inbox, when it need not be this way. This is why I like NNTP. The lack of overwhelming mass participation is a feature, not a bug.