From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: lamers on IRC Date: Sat, 28 May 2022 18:54:00 +0200 Message-ID: <877d65oaxj.fsf@dataswamp.org> References: <87wnedb6xe.fsf@dataswamp.org> <87o7zox6w4.fsf@dataswamp.org> <87pmk1b5ot.fsf@dataswamp.org> <9109efc3-0d1d-4d21-8160-24da6f7cd256@www.fastmail.com> <87bkvj9fr7.fsf@dataswamp.org> <87ee0eselt.fsf@dataswamp.org> <5b08e28cbbd8e3c63febe68ead319316@basiscraft.com> <87k0a68eyl.fsf@dataswamp.org> <875ylq8dev.fsf@dataswamp.org> <2a7698a89c8e34126dbc7e357feea8e0@basiscraft.com> <874k19pue3.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36905"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:lB2GAoKNRxuRarpaegORRpEvKHs= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat May 28 18:54:45 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nuzi9-0009O1-3m for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 28 May 2022 18:54:45 +0200 Original-Received: from localhost ([::1]:49896 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nuzi8-0005fY-2m for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 28 May 2022 12:54:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39388) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nuzha-0005ej-UF for help-gnu-emacs@gnu.org; Sat, 28 May 2022 12:54:11 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:42084) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nuzhZ-000750-2a for help-gnu-emacs@gnu.org; Sat, 28 May 2022 12:54:10 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nuzhX-0008hF-OW for help-gnu-emacs@gnu.org; Sat, 28 May 2022 18:54:07 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:137454 Archived-At: 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