Mh, if you are on a somewhat trustworthy network - like your home WLAN - and need to get some files from a host on that network to another once, there is <pytho

Mh, if you are on a somewhat trustworthy network - like your home WLAN - and need to get some files from a host on that network to another once, there is <python3 -m http.server>. Lookup your local IP, port 8000 is open, the PWD is being served. Throw wget/curl/telnet/nc at it and that's it. For a more permanent setup, I tend to run SyncThing between my laptop and my stationary tower, for example to keep my ~/Projects and my ~/Documents up to date with each other. Sure, everything is in git as well. But it's neat to be able to just open up the laptop and your exact last project state or your last dwarfen fort is right there without really caring about it or dealing with it. From there I'm currently considering adding a small vServer as a third SyncThing node so I don't have to start my laptop after travel once to get the data back onto the workstation. Would also add a bit of redundancy in case of fire, theft or law enforcement. I'd also consider using the server as a bit of a file storage for some archival and data hoarding purposes, mirrors for some cloud services as well as backups of the syncthing state and such, but I'm not really sold on the tech to use there. Something like OwnCloud/Nextcloud looks pretty as a file store and might also allow family to store some stuff there... but it's quite the chunk of tech to maintain, patch, monitor and secure for something I technically could have via... sshd and some cloud volume? Not really decided there.