I mentioned in my new introduction that I am interested in #uucp, and I thought I should get into this a bit more.
uucp is technically only a unix tool, or maybe toolset, that came around very early in computing (first proper release in '79), to help with early network connections.
The abbreviation is for unix-to-unix-copy, and that's exactly what it does: it copies files between different systems 1/?
Of course these were the days when computers were not connected to the network with permanent connections, so the whole shebang was based on dial-up services: if you copy a file it is copied to a spool and then sent onwards during the next time the system connects. This was extended by allowing to send files over multiple remote systems. So you might copy a file from computer A to computer C, and the file would travel first to computer B, then to C when B connected with that one.
A text file is a file, and could be sent to another computer.
An email is basically just a text file, and so emails could be sent. Forums (the usenet) were invented when someone started sending and distributing text files to public folders, and had them propagate on.
Even commands could be sent, allowing remote execution of tasks on other computers. Sure, it wasn't fast, especially as systems often only connected to the wider internet once a day and had to spread whatever transmission was send over the network hop-by-hop.
But it definitely started the first actual online communities. People all of a sudden were able to talk to other people on the other side of the country, or even across the ocean.
Even primitive #filesharing was possible, with some dial-up systems allowing public access to their file areas (often paid).
Users would send a command requesting a file listing the files on offer, and after receiving it requested the files they wanted.
This was all SLOW of course. But it was possible.
As fascinating as I find it, #uucp (and the modernized version #nncp) has limited actual use nowadays. For one, most machines nowadays are connected to the internet constantly, eschewing the need for delayed commands and file requests.
And it's not like many people still have dial-up modems around, or even the infrastructure to use them.
(who even has a landline still? and there seems to be an issue running modem signals over glass fiber as well)
@kyonshi This is one reason that I mostly use #NNCP instead of #UUCP these days. There are some use cases where UUCP is *perfect*. For instance, long-distance, low-power, low-speed radios such as #LoRa or #XBeeSX. LoRa has speeds similar to the modems UUCP used back in the day, and it can be quite useful for that. But nowadays, nicer support for USB drives and encryption is a win.
@kyonshi https://www.complete.org/ideas-for-nncp-projects/ talks about some of the things I do with NNCP. Airgapped backups is one huge area; I think a lot of people have poorly-resilient backups (it seems like ARRL's recent cyberattack also got into their online backups, making it much worse.) I often go into wilderness areas (and live in a rural area myself) and Internet access isn't always-on there. But you're right, not everyone will have a use case for it. Syncthing is also interesting https://www.complete.org/syncthing/
@jgoerzen I think syncthing is much more resource intensive. I have it running on a few machines, and while it's not too bad, I can see nncp doing better with with some use cases. My tiny pi zero sometimes seems a bit overloaded when I am syncing stuff.
@jgoerzen for usb I definitely would use nncp. from what I have seen support for that is inbuilt in that.