From: Thomas Lord <lord@basiscraft.com>
To: help-gnu-emacs@gnu.org
Cc: help-gnu-emacs <help-gnu-emacs-bounces+lord=basiscraft.com@gnu.org>
Subject: Re: lamers on IRC
Date: Fri, 27 May 2022 21:39:32 -0700 [thread overview]
Message-ID: <feeee65511c4138da29906613c036f25@basiscraft.com> (raw)
In-Reply-To: <87k0a68eyl.fsf@dataswamp.org>
The wikipedia article looks at first glance to document the
alt groups correctly, as far as I recall.
The key thing to alts: no central moderator, yes, but also
every individual host operator had the capacity to simply
not carry some. Every user had a theoretical capacity
to operate their own host or to shop around for one who
carried the alt groups they preferred. Of course, the whole
thing being P2P, hosts upstream of a given host could
choose to shun it and hosts could shop around for their
choice of upstream hosts.
Google used its economic power and social influence to first
centralize what was left of mainstream netnews and then to
kill it off.
I dream of a world with a few very popular hosts and lots of
tangles and tentacles of more "semi-privateish" hosts with
groups that aren't big loud public broadcasts, more or less.
-t
On 2022-05-27 21:21, Emanuel Berg wrote:
> Thomas Lord wrote:
>
>> I wish something like this existed but with the
>> groups/moderator features (suitably updated) of
>> Usenet netnews.
>
> Weren't there parallel hierarchies, one of which was moderated
> and the other not so? Was that the "alt" thing? This was
> before my time ...
>
> Because then on IRC one could have
>
> #emacs
> #emacs-lamers
>
> LOL
next prev parent reply other threads:[~2022-05-28 4:39 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 [this message]
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
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=feeee65511c4138da29906613c036f25@basiscraft.com \
--to=lord@basiscraft.com \
--cc=help-gnu-emacs-bounces+lord=basiscraft.com@gnu.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).