rns.recipes

Hi all, I'm still very much a noob when it comes to this, so I apologize in advance if this is a dumb question.

I'm running NomadNet and am able to connect to peoples pages just fine. I stumbled upon WeatherBuddy (64ace45d1e9c1b2192f80e19e20fe383) and I thought it would be cool to be able to send them a message to get a weather update in my area but when I add their LXMF address to my Conversations list and try to send a message I get this:

You cannot currently message this peer, since its identity keys are not known. The keys have been requested from the network and should arrive shortly, if available. Close this conversation and reopen it to try again. To query the network manually, select this conversation in the conversation list, press Ctrl-E, and use the query button.

I tried to query the network manually but nothing happens. I tried this with a few other nodes and get the same thing. It doesn't matter if I add them as a Trusted or Untrusted contact either.

Hi! Feel free to send me a test message: 7cafffb51eb97f9fda848eb40ed02cc9

Sojourner wrote:

Hi! Feel free to send me a test message: 7cafffb51eb97f9fda848eb40ed02cc9

I sent you a message about 20 minutes ago.

Anonymous wrote:

Sojourner wrote:

Hi! Feel free to send me a test message: 7cafffb51eb97f9fda848eb40ed02cc9

I sent you a message about 20 minutes ago.

Alas, I didn't get anything. Are you connected to any interfaces?

Sojourner wrote:

Anonymous wrote:

Sojourner wrote:

Hi! Feel free to send me a test message: 7cafffb51eb97f9fda848eb40ed02cc9

I sent you a message about 20 minutes ago.

Alas, I didn't get anything. Are you connected to any interfaces?

Yes I'm currently using this one, but I'll try another one

[[RNS Android Sideband App Server]]
Type = TCPClientInterface
Enabled = yes
Target_host = sideband.connect.reticulum.network
Target_port = 7822

Sojourner wrote:

Anonymous wrote:

Sojourner wrote:

Hi! Feel free to send me a test message: 7cafffb51eb97f9fda848eb40ed02cc9

I sent you a message about 20 minutes ago.

Alas, I didn't get anything. Are you connected to any interfaces?

I sent you another message using SparkN0de as my interface. Could you try to send me a ping? 64d963a64bb6fd13ec1681e658d78381

Try mine:
-rns.sofia-
BackboneInterface
IP: 193.193.182.147
Port: 4242

I cannot seem to find any info on the [[RNS Android Sideband App Server]] anywhere. The name sounds a bit sucked out of a middle finger... :D

You can test your connection with Sofia EchoBot, it will send back whatever you throw at it.
37d955c0c87c4e0043d80dc18f67576a

EchoBot worked just fine. Sojourner I got your message, I replied. I did notice that when I send messages to the bot it I see this:

✓ → just now

Where as when I send messages to Sojourner I see this:

→ 6m ago

Not sure why I'm seeing the little arrow instead of the check. I'll try rns.sofia next.

Edit:
Looking through the logfile and the last message I sent to Sojourner says:

[2026-06-22 02:31:19] [Verbose] Sending lxmf.delivery announce
[2026-06-22 02:33:16] [Verbose] Direct delivery of <LXMessage 57285b6232e18f75bcc7f8b62d450644e524077d15d22def6bc978ab28b5a87b> failed. Retrying as propagated message.

He is just offline or not reachable. But there is another aspect. There are many nodes now, that are set as propagation nodes, but there is also a vast majority of those, which do not do their job for different reasons, mainly not being set up properly. When you let this to be chosen automatically, Columba or SB just use whatever one thy deem closest in response and hops, and in many cases, this will not work, for the abovesaid reasons. This is why I have set my PN on a power-backed-up server with very good internet connection and the whole thing is properly set up. LXMD sometimes just dies, but this is rare, like once in a month, and I normally catch it pretty fast and restart the daemon. So please, you are welcome to use it too, if it works good for you. It is set up as public service rns.sofia Propagation Node : 1e96a12e2ac59bfebd604a6e3cb95a68

aetherlab wrote:

He is just offline or not reachable. But there is another aspect. There are many nodes now, that are set as propagation nodes, but there is also a vast majority of those, which do not do their job for different reasons, mainly not being set up properly. When you let this to be chosen automatically, Columba or SB just use whatever one thy deem closest in response and hops, and in many cases, this will not work, for the abovesaid reasons. This is why I have set my PN on a power-backed-up server with very good internet connection and the whole thing is properly set up. LXMD sometimes just dies, but this is rare, like once in a month, and I normally catch it pretty fast and restart the daemon. So please, you are welcome to use it too, if it works good for you. It is set up as public service rns.sofia Propagation Node : 1e96a12e2ac59bfebd604a6e3cb95a68

Much appreciated. I have to head off to work, but I'll mess around with this a bit more tonight!