public inbox for nncp-devel@lists.cypherpunks.su
Atom feed
From: Sergey Matveev <stargrave@stargrave•org>
To: nncp-devel@lists.cypherpunks.ru
Subject: Re: nncp-bundle, nncp-caller, and .seen not working?
Date: Wed, 30 Dec 2020 17:08:27 +0300	[thread overview]
Message-ID: <X+yJ5q4xgGIdOzBW@stargrave.org> (raw)
In-Reply-To: <877dozol3u.fsf@complete.org>

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

Greetings!

*** John Goerzen [2020-12-30 00:37]:
>I noticed that nncp-bundle put incoming data in a directory named for the
>local self's id, while nncp-caller put incoming data in a directory named for
>the neighbor's id.  Perhaps that's the issue?

Of course that was a bug. I do not know (or remember?) why it is not
placed in the sender's rx/ directory, but in the self's one. nncp-toss
worked anyway, because sender/recipient information is taken from
packet's header. I have fixed that in:
http://www.git.cypherpunks.ru/?p=nncp.git;a=commit;h=87245f236b40415c6e30fbaee18cdaf46b7f5c57
You can try it just by overwriting nncp-bundle/main.go file and
rebuilding it.

By the way, I plan to add ability to create uncompressed nncp-exec
packets. Currently nncp-exec always compresses the data inside, because
originally it was used only for email transmission. I will add another
plain packet type and an additional command line option for nncp-exec.
Everything will stay the same and backwards compatibility with existing
nncp-exec-generated packets won't break. After that I will create new
release with current nncp-bundle fix and documentation updates.

-- 
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 --]

  reply	other threads:[~2020-12-30 14:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30  6:37 nncp-bundle, nncp-caller, and .seen not working? John Goerzen
2020-12-30 14:08 ` Sergey Matveev [this message]
2020-12-30 15:37   ` John Goerzen
2020-12-30 15:44     ` John Goerzen
2020-12-30 19:10     ` Sergey Matveev
2020-12-30 19:16       ` Sergey Matveev
2021-01-01  5:36       ` John Goerzen
2021-01-02 12:56         ` Sergey Matveev
2021-01-01  5:39       ` John Goerzen
2021-01-02 13:04         ` Sergey Matveev
2021-01-06 17:15         ` Sergey Matveev
2021-01-06 18:55           ` Sergey Matveev
2021-01-07 17:56           ` John Goerzen