public inbox for nncp-devel@lists.cypherpunks.ru
Atom feed
From: Sergey Matveev <stargrave@stargrave•org>
To: nncp-devel@lists.cypherpunks.ru
Subject: Re: A Public NNCP relay
Date: Fri, 30 Jul 2021 11:57:34 +0300	[thread overview]
Message-ID: <YQO/CdR5sXj90IKx@stargrave.org> (raw)
In-Reply-To: <87tukeeysv.fsf@complete.org>

[-- Attachment #1: Type: text/plain, Size: 2811 bytes --]

Greetings!

*** John Goerzen [2021-07-28 19:41]:
>I am contemplating setting up an experimental public NNCP relay for people.
>I would like to hear thoughts on this: would anyone be interested, what do
>you think of the plan, etc.
>Thoughts?

Personally I have no strong opinion about all of that. I assume that all
NNCP users are rather advanced users and all of them have either their
own home server, or VPS or something similar. So hardly can imagine if
public relay would be really useful. But that are only thoughts, no any
confidence in them :-).

Possibly we can use it (also) for sharing of something useful among all
of few NNCP users. But... I do not know what exactly could it be. New
NNCP release tarballs through multicast area? Some kind of
chat/maillist/echo conference -- but there is already that maillist
exists and we have to determine format of the messages and exec-commands
for that tasks (for example simple recfile-formatted UTF-8 plaintext
message with From/Date/Subject lines and exec-command accepting it
through stdin). It is solvable and interesting task of course, but I am
fear that it could lead to creation of yet another class of messaging
system :-)

But anyway I would be glad to help somehow with all of that. I can also
provide my resources two: 100Mbps connection to home server with several
hundred of gigabytes of free diskspace.

>I could set up nncp-daemon and nncp-toss and use ZFS "project" quotas to
>limit the size of each spool directory to something reasonable.

I also use ZFS quotas at home for preventing accidental running out of
disk space :-)

>I wonder if there is a way to queue up an outbound packet that says
>"send via one of these lists of paths and delete the others once it's
>sent?")

At first sight I do not like idea to remove others, possible duplicate,
packets, because there are no delivery guarantees of the first one. I
think it is better to have excess packets, possibly leading to more
transferred traffic, but with higher probability of guaranteed delivery.

>One could also route NNCP messages over UUCP.  But then.... why?

Unrelated remark, but that week I successfully transferred hundreds of
packets for several days through the serial COM-port with NNCP, by
running relatively easy setup PPP with link-local IPv6 addresses (no IP
configuration was necessary) and multicast nodes discovery. Writing of
sliding-window protocol with *efficient* guaranteed data delivery is not
trivial task and it is easier to setup PPP+TCP (that are still available
out of box in most BSD systems I believe), that will also work good with
the modems, not only null-modem connection.

-- 
Sergey Matveev (http://www.stargrave.org/)
OpenPGP: CF60 E89A 5923 1E76 E263  6422 AE1A 8109 E498 57EF

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-07-30  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  0:41 A Public NNCP relay John Goerzen
2021-07-30  5:52 ` Shawn K. Quinn
2021-07-30  8:57 ` Sergey Matveev [this message]
2021-07-31 12:12 ` Jonathan Lane