#uucp by the way stands for unix-to-unix-copy, and that is what it was intended to do: copy files between different unix systems. those files soon enough were e-mails and newsgroup discussions. but they still were transmitted by copying from one system to another, until they finally reached their destination.
back the it could take days or even weeks for an email to reach the target, and people had to give the whole path between machines the email was supposed to take into the address
still working on the #uucp setup we were doing two weeks ago. I think I am getting to the point where my newsserver is peering with another server over uucp to bring #usenet into our private uucp network.
I have been spending entirely too much mental energy trying to figure out why my #uucp connections to my own computers don't want to work.
I already managed to mesh with another person's systems, so I really don't know what the issue is... besides using uucp in the first place.
Reading about uucp news/mail transfers right now I can't find an answer to a question I have on wikipedia: when exactly did the @ notation (user@example.com) become the standard instead of host!intermediate!receiver bang-paths?
Starting to think about a #p2p social media protocol that doesn't fall foul of the UK's ridiculously broad #OnlineSafetyAct, and leaves what you see in your own hands.
Feed curation as active or effortless as you like, using whatever approach you choose.
So a protocol that provides the basis for user respecting apps with different approaches.
Goal: curation with zero effort via support for 'algos' that serve you rather than the other way around.
@eludom UUNET is something I used back in the day.
I doubt very much that, like TCP/IP it was a complete and adequate protocol.
My focus is here and now.
I may look at existing approaches such as #XMPP and #Nostr for comparison, and perhaps even #UUCP now you mention it but I have limited time and won't make progress if that's all I do.
You suggesting UUCP as a solution to today's problems isn't convincing because first I want to hear from you, what problems and how it solves them.
@puniko I only know about the "Airgapped Transfer Protocol" because #UUCP is old amd ancient and not really good at all and doesn't work or gets implemented on modern hardware...
Whereas #ATP aims at transfering files using only cameras and screens...
It won't replace like a #USB or #Ethernet cable but can replace a #serial console...
> See, because you need an always-on computer in order to really reliably use #decentralized social media
Bruh. #Usenet, #Fidonet and #UUCP (#UUCPnet) beg to differ (no reason you couldn't use #NNCP for Usenet now if #NNTP isn't your thing).
Thanks to abbub on IRC who was playing with Xenix 286 and was able to hack up a 1.44MB version of the N1 installer disk, I'm now running Xenix 2.3.2 on my Bondwell B310 286 laptop that I'd previously build a ram expansion board for.
@ChartreuseK@mos_8502@dankski what about Coherent? It won't provide TCP/IP but it's another one from the era and you'll have a chance to enjoy handling #UUCP ... 😂