Selfhosted

Depends on what I'm transferring and to/from where:

• scp is my go-to since I'm a Linux household and have SSH keys setup and LDAP SSO as a fallback
• sshfs if I'm too lazy to connect via SMB/NFS (or I don't feel like installing the tools for them) or I'm traversing a WAN
• rsync for bulk transfer and backups
• Snapdrop/Pairdrop for one-off file/text shares between devices with GUIs (mostly phone <--> PC)
• SMB if I'm on a client PC and need to work with the files directly from the fileserver
• NFS between servers
• To get bulk data to my phone (e.g. updating my music library), I connect via USB in MTP mode and copy from the server via SMB or sshfs.

I have a shared syncthing folder on all my devices

SFTP! 😃

Resilion Sync

I work from home, however my two systems (home and work) are on the same LAN, they don't see each other for file sharing. I get paid via direct deposit like everyone else which means my pay stubs are all electronic. I print those out and then use WinSCP to copy those over to my desktop. No other files are ever sent.

At home, depending on the amount of files, I either use SFTP via Filezilla, or if the mood strikes me and for a single file, I will just use SCP if I'm already on the cli which is most of the time it seems anymore doing work on my personal servers. I've found that SFTP is faster at transferring than doing a copy/paste to the NFS share to the same drive.

I like unison personally. It is a bit more of a hassle but it works pretty well.

Just regular old WinSCP, or XPipe for smaller stuff and editing config files.

I need a GUI, I'll use rsync to migrate a lot of data to a new server or something occasionally, but it's just a pain compared to a nice graphical file browser.

rsync over an SMB share was pretty seamless.

you can use a regular ftp server with administrator and user rights, distribute rights to those who replenish, and those who just take - guests at home I transfer in this way from computer to computer without connecting them to a common network, what could be simpler? why invent some ways with keys or bash if there is a 40-year-old technology that just works great, and to open ftp it is enough to enter the IP address in the explorer

Snapdrop if they both have a gui/webbrowser. https://github.com/SnapDrop/snapdrop

Scp otherwise

Ähm. So your not gonna like this but I just connect with vscode remote-ssh and drag'n drop em from the os file explorer into the vscode one.

So long story short scp I guess.

rsync -are ssh from to@pc:/dir

rsync over ssh or scp.