I hadn’t even heard of the underlying protocol NNCP yet, and it seems to solve out of the box several things I was trying to do in some of my own hobby-projects. I’d been battling with automating and integrating Tor/I2P, Openssl, Tox, GPG, Wireguard, etc. If NNCP lives up to the hype it will be a big shortcut, when I next get time to work on stuff :-)
I wonder how hard and if feasible at all it would be to have something like an email over NNCP over meshtastic network. Total independence and resilience.
Ooh, that’s interesting. But I assume there is nothing stopping me from using both quux AND alternative routes to nodes (via meshtastic for instance) at the same time? I don’t have to go fully one way or another?
I hadn’t even heard of the underlying protocol NNCP yet, and it seems to solve out of the box several things I was trying to do in some of my own hobby-projects. I’d been battling with automating and integrating Tor/I2P, Openssl, Tox, GPG, Wireguard, etc. If NNCP lives up to the hype it will be a big shortcut, when I next get time to work on stuff :-)
I wonder how hard and if feasible at all it would be to have something like an email over NNCP over meshtastic network. Total independence and resilience.
you could do that, set the use NNCPNET_NO_NODELIST to 1.
Then your into private node https://salsa.debian.org/jgoerzen/docker-nncpnet-mailnode/-/wikis/configuration#adding-private-nodes
Ooh, that’s interesting. But I assume there is nothing stopping me from using both quux AND alternative routes to nodes (via meshtastic for instance) at the same time? I don’t have to go fully one way or another?
yeah, I think so. So nodes are over meshtastic and some are over quux
I didnt know of NNCP either, it looks amazing and super simple to setup. might have to look at how I run a NNCP forwarder to Gmail