snip...@gmail.com (Sn!pe) writes:
> yeti <ye...@tilde.institute> wrote:
>
>> Kestral Gaian <
k...@kesgai.com> writes:
>>
>> > On 21/12/2023 18:28, Marco Moock wrote:
>> >> Does your university still operate an NNTP server?
>> >
>> > I wish - it's never had one. I might explore the security impact of
>> > getting one up and running in the new year, but I'm very keen to
>> > support the protocol and the 'net as a whole if I can.
>>
>> Maybe let's try to add a P2Pish NNTP dimension? Via DynDNS/I2P/Tor?
>> Everyone would be responsible for their own node only. That could be
>> chaos for a while with groups popping into and out of existence like
>> virtual particles, but after a while a rule set for an a bit more
>> fluid/flexible sibling of Usenet may crystallise out.
>>
>> Smells like a nice experiment.
>
> Wouldn't that be equivalent to each group having an owner in charge,
> just like a web forum? I thought the main advantage of Usenet was
> precisely that no one person is in charge.
I think the USENET is for people like us. Many folks can't easily
handle this no-one-is-in-charge. So, one thing that I think
universities and organizations can do is to set up an authenticated NNTP
server for their internal discussions --- something closed. (Abusers
would be easily suspended by system administrators. No privacy. Just a
local NNTP forum.) But, this local NNTP server would also carry some
USENET groups that could be of some interest to the local people. The
locals wouldn't be able to post to the USENET groups, but they could
read it --- and this way the USENET would be presented to students or
whoever they are. People would likely ask --- why can't we post to
these groups? And we would instruct people on how to join the USENET.
Universities send and receive a lot of mail. A local NNTP server would
serve them a lot better. Threaded, archived, public. The mail box
would get a lot quieter. Maybe that's precisely what people don't want
--- but I would really like that.