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.
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
I remember as a kid I set up one of the first private Echomail nodes as part of my RBBS bulletin board. UUCP was a big part of that, as I was the hop for other nodes coming onboard in my area. I added another half-dozen modems eventually just to handle the email traffic, then had to offload it to a university because I didn't want to have to charge for the traffic and it was getting too big to handle. But it was pretty interesting at the time.
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
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