RNS Logo

rns.recipes

◈ 9ce92808be498e9e05590ff27cbfdfe4

RNS 1.5.1 Released

Started by Mark bc7291552be7a58f... ·

Anonymous
#21

This fixed my KeyError: 'txdrp' problem:

pipx list
pipx uninstall-all
pipx install rns
pipx install lxmf
pipx install nomadnet
reboot
Anonymous
#22

Mark, I am wondering, if I put RNS 1.5.4 on my server, will it still interoperate fine with devices running Sideband or MeshChat with RNS 1.4.2? I know that 1.5.0 began a shift in the way transport works, so I just want to make sure it would interoperate before beginning the transition.

Mark 8dd57a7382268096...
#23

There should be no interop problems, you can upgrade however is most practical. I will always note clearly if there are any backwards-incompatibility issues to be aware of clearly in the release notes.

daylight-hub
#24

Mark wrote:

There should be no interop problems, you can upgrade however is most practical. I will always note clearly if there are any backwards-incompatibility issues to be aware of clearly in the release notes.

 

Thank you!

C.S.Burner 39a25f495615fa16...
#25

Mark, to relax from all the AI and licence drama here is a little nitty kritty thing: When listing i2p peers with Fff0rnstatus -d i2pdf you get configuration hints like:

 

Fff0Configuration Entry: [[Discovered I2PInterface]] type = I2PInterface enabled = yes peers = hioyjs43a24ihdjhskpepct53veddb5g2am325t7dp73fu2e35gaf

 

Copying this into configuration gives an error, because peer must be defined with ending Fff0.b32.i2pf in the configuration as

 

Fff0peers = hioyjs43a24ihdjhskpepct53veddb5g2am325t7dp73fu2e35ga.b32.i2pf

 

Just a little hint from a user who struggeled a while with this.

Post a Reply

Supports Markdown: **bold**, *italic*, `code`, ```code blocks```, [links](url)

Log in to upload images

Quote
Copied to clipboard