If I can get just a handful of other nodes on the network, especially in other neighborhoods, we can relay some sorts of traffic via #NNCP ...
For nodes within wifi reach of each other #Yggdrasil seems like a pretty viable option for nodes to communicate.
I have finally started actually building my first node in what I hope to eventually become a local inter-neighborhood #MeshNetwork of nodes.
The premise is to have an open wifi access point #OffGrid both powered by solar and not connected to the internet, with a few simple things that might be useful to neighbors...
Not sure exactly what all it might have, but I envision at least a #Wiki ...
#EMail ? Mailing lists?
#XMPP ?
#SyncThing ?
#NNCP ?
#RSS feeds?
#Kiwix ?
In a near future, given the #internet censorship,
using #nncp packets over #minimodem with a #shortwave receiver
won't be a mad idea. Text files, Usenet
pulls, everything, but mainly
unidirectional. But good enough to
access to content #offline without
having to be connected to an ISP.
Convince your friends to host their own email server a home and do help them set it up…
Then set up NNCP routes to and from their email server to your own self-hosted email server(s) and any of your mutual friend's self-hosted email servers
@orsinium I know, they stole email from us claiming to combat spam and somehow there is still spam
==Email==
Maybe I only need to receive email over SMTP.
Otherwise email transfer using NNCP with known-trusted-hosts of friends and family?
Perhaps #FOAF even?
Perhaps as part of NNCPNET?
Maybe (text-only) #USENET also via NNCP?
Edit: bc I just found #NNCP and #NNCPNET and think this could be a solution
==Webdev==
I can use #RubyOnRails as needed ¯\_(ツ)_/¯
@karen With #NNCP, we break the tyranny of online with delay-tolerant networking. https://www.complete.org/nncp/ The new #NNCPNET is an email network running atop it -- with bridges to the public Internet. https://salsa.debian.org/jgoerzen/docker-nncpnet-mailnode/-/wikis/home
2/
What is NNCP? NNCP lets you securely send files, or request remote execution, between systems. It uses asynchronous communication, so the source and destination need never be online simultaneously. NNCP can route requests via intermediate devices – other NNCP nodes, USB sticks, tapes, radios, phones, cloud services, whatever – leading to a network that is highly resilient and flexible. NNCP makes it much easier to communicate with devices that lack Internet connectivity, or have poor Internet.
@ireneista Oh interesting! I'd enjoy hearing some about your project.
These days I am mostly working with its successor #NNCP but UUCP still is fun to work with also. Especially over slow radios like #LoRa.
I have a new blog post: "I'm not very popular, thankfully. That makes the Internet fun again."
I muse that not having to care about subscriber counts lets me write about the things that interest me, from non-square DOS VGA text mode pixels in Linux to #NNCP and such. I couldn't do that if I cared about advertisers and subscriber counts and so forth.
Simply configuring #NNCP to only run nncp-* commands as a user seems to work well enough for nodes not running a listening nncp daemon.
For a system running nncp-daemon I am still running as the "nncp" user and so "sudo -u nncp nncp-*" seems to work pretty well.
Vagrant Cascadian
Anthk
Dimly Lit Corners
Dimly Lit Corners
Neale
John Goerzen