public inbox for nncp-devel@lists.cypherpunks.ru
Atom feed
From: Sergey Matveev <stargrave@stargrave•org>
To: nncp-devel@lists.cypherpunks.ru
Subject: Re: Thoughts on flexible mesh-routing of NNCP packets
Date: Mon, 1 Feb 2021 11:39:00 +0300 [thread overview]
Message-ID: <YBe+MMbjqQwobZX4@stargrave.org> (raw)
In-Reply-To: <87zh0omhp1.fsf@complete.org>
[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]
*** John Goerzen [2021-02-01 00:21]:
>Which reminds me - when you get back a file from nncp-freq, or any other
>event that sends something back, I'm assuming it uses the via path (if any)
>defined on the system that's sending back the response?
Yes, correct.
>So I wouldn't suggest anybody just rip out nncp-call(er) and go to Syncthing
>entirely; nncp-call and the daemon are quite useful and more efficient than
>Syncthing would be in fixed topology cases, or situations with a non-TCP
>transport.
I understand. There can not be killer solution for all cases.
>One particularly interesting use for this - Syncthing can to local LAN
>discovery.
Once I wanted to create same thing in nncp-daemon/caller -- multicasted
notifications about NNCP daemons presence.
>very nice alternative to things like Dropbox, or even Nextcloud, since it can
>be run entirely serverless and disconnected.
Dropbox is not the choice of course, because it is not free software.
>Being an append-only log has me somewhat concerned. It seems to be something
>like a "public Syncthing, but unidirectional." IPFS seems to be catching on
>more than DAT at the moment.
I like DAT idea because it is very close to WARC:
https://en.wikipedia.org/wiki/Web_ARChive
whole website distribution through single file.
And DAT (seems) allows to effectively publish changes to it.
It seems can be conveniently archived for long term storage.
>And thank you, again, for NNCP. Unlike many of these other things, it's
>fairly simple, well-documented, and secure and private by default.
Hope so! Glad you like it!
>Heck, a person could even use Google Drive for the packets, if one wanted.
Yes, of course, no barriers.
--
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 --]
next prev parent reply other threads:[~2021-02-01 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 7:03 Thoughts on flexible mesh-routing of NNCP packets John Goerzen
2021-01-31 11:19 ` Sergey Matveev
2021-02-01 6:21 ` John Goerzen
2021-02-01 8:39 ` Sergey Matveev [this message]
2021-01-31 15:16 ` Sergey Matveev