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'm trying to figure out how to add it to Mailcow Dockerized and hook the existing containers. If I sort it out, I'll probably PR it to Mailcow. I think it would a nice addition to start to build out a network that isn't susceptible to the same spam attacks as regular email (yet).
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.
9 Comments
rowanthorpe@lemmy.ml · 9 pts · 1y
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 :-)
MigratingApe@lemmy.dbzer0.com · 4 pts · 1y
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.
mhzawadi@lemmy.horwood.cloud · 6 pts · 1y
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
MigratingApe@lemmy.dbzer0.com · 5 pts · 1y
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?
mhzawadi@lemmy.horwood.cloud · 2 pts · 1y
yeah, I think so. So nodes are over meshtastic and some are over quux
mhzawadi@lemmy.horwood.cloud · 2 pts · 1y
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
N0x0n@lemmy.ml · 7 pts · 1y
Really cool stuff !! Something I need to try out for sure !
Just to bad they didn't add a multiuser setup example :( !
ikidd@lemmy.world · 2 pts · 1y
I'm trying to figure out how to add it to Mailcow Dockerized and hook the existing containers. If I sort it out, I'll probably PR it to Mailcow. I think it would a nice addition to start to build out a network that isn't susceptible to the same spam attacks as regular email (yet).
ikidd@lemmy.world · 1 pts · 1y
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.