From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: lamers on IRC
Date: Sat, 28 May 2022 18:54:00 +0200 [thread overview]
Message-ID: <877d65oaxj.fsf@dataswamp.org> (raw)
In-Reply-To: f1ae16f7cc92318feb75567b7a2ad2bc@basiscraft.com
Thomas Lord wrote:
> Although individual posts flow in both directions between
> peers, in practice, some nodes emerged, the main function of
> which was to form a kind of high bandwidth backbone carrying
> all the net-work wide popular groups, and offering peering
> to many peripheral nodes.
>
> To continue the example: at the little start-up I worked at,
> they didn't try to carry all the groups available at the
> time. They carried some obvious groups (such as comp.lang.c,
> about the C programming language) and, beyond those core
> groups, they would add anything someone asked for and that
> the big "upstream" peer had.
>
> The big upstream peer got most of its very large set of
> groups to choose from by peering with other big hosts.
> They also carried back posts from "edge nodes" to the rest
> of the world.
>
> The p2p software - that today might easily be replaced with
> something close to rsync(1) - saw peers as symmetric.
> The IRL social network operating netnews recognized the
> big-iron/big-pipes/serves-many "upstream" as different from
> the local hosts/low activity/selected groups "downstream".
> Maybe a bit like how the logical functions of Internet
> routers are symmetrical, but an upstream/downstream topology
> emerges on the basis of the physical network and who is
> connected where.
Got it,
inner node = server, upstream
edge node = host (client), downstream
but in theory the server could act as a host and the host as
a server?
>> I've heard the so called binary groups (which contained
>> multimedia) were part of the reason of the fall in popular
>> use since people were sharing files - so not the least XXX
>> rated movies - to the extent it ate up most of the
>> bandwidth while there still wasn't a monetary incentive to
>> keep providing the service, from the ISP's POV ...
>
> My initial encounter with net news did not involve ISPs or
> the IP protocol. It was company X's computers running a cron
> script to dial up and log in to computers at company Y.
> (Some others at the same time were already peering over
> the Arpanet.)
So how did that happen if not the Internet, telephone line
and UUCP?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-05-28 16:54 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 21:20 lamers on IRC Emanuel Berg
2022-05-23 6:50 ` Jean Louis
2022-05-23 10:51 ` Colin Baxter
2022-05-23 21:45 ` Emanuel Berg
2022-05-23 15:30 ` Eric Abrahamsen
2022-05-23 15:41 ` Philip Kaludercic
2022-05-23 16:12 ` Eric Abrahamsen
2022-05-24 22:14 ` Jon Fineman
2022-05-24 22:49 ` Eric Abrahamsen
2022-05-25 16:55 ` Philip Kaludercic
2022-05-25 5:07 ` Jean Louis
2022-05-23 16:47 ` Thomas Lord
2022-05-23 21:46 ` Emanuel Berg
2022-05-23 21:42 ` Emanuel Berg
2022-05-25 5:26 ` Jean Louis
2022-05-25 22:36 ` Emanuel Berg
2022-05-25 23:55 ` Samuel Wales
2022-05-25 23:58 ` Samuel Wales
2022-05-26 1:48 ` Samuel Banya
2022-05-27 2:25 ` Jean Louis
2022-05-27 10:13 ` Jean Louis
2022-05-27 14:16 ` Philip Kaludercic
2022-05-27 15:12 ` Emanuel Berg
2022-05-27 16:13 ` Jean Louis
2022-05-28 0:17 ` Emanuel Berg
2022-05-27 15:06 ` Emanuel Berg
2022-05-27 15:51 ` Samuel Banya
2022-05-28 0:08 ` Emanuel Berg
2022-05-28 4:11 ` Thomas Lord
2022-05-28 4:21 ` Emanuel Berg
2022-05-28 4:39 ` Thomas Lord
2022-05-28 4:54 ` Emanuel Berg
2022-05-28 5:04 ` Thomas Lord
2022-05-28 5:12 ` Thomas Lord
2022-05-28 15:11 ` Emanuel Berg
2022-05-28 15:08 ` Emanuel Berg
2022-05-28 16:12 ` Thomas Lord
2022-05-28 16:54 ` Emanuel Berg [this message]
2022-05-29 3:50 ` Thomas Lord
2022-05-29 23:52 ` Emanuel Berg
2022-05-30 0:07 ` Emanuel Berg
2022-05-30 0:57 ` Thomas Lord
2022-05-30 2:24 ` Emanuel Berg
2022-05-30 2:33 ` Thomas Lord
2022-06-01 0:13 ` Emanuel Berg
2022-06-09 9:13 ` Emanuel Berg
2022-05-28 6:49 ` Jean Louis
2022-05-28 15:16 ` Emanuel Berg
2022-05-27 16:19 ` Jean Louis
2022-05-28 0:18 ` Emanuel Berg
2022-05-28 4:04 ` Emanuel Berg
2022-05-28 4:30 ` Byung-Hee HWANG
2022-05-28 4:32 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d65oaxj.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).