Any advantages to this over scp, samba/nfs, or even something like LocalSend?
Basically the advantage is that it’s ridiculously easy to set up. You just install the app and open it. The downside is that it’s ad-hoc. It’s not meant to be a long running server like smb.
I’d argue LocalSend is a lot simpler. Install the app on both devices, open it, transfer files. Zero configuration needed in the majority of cases.
There’s no configuration needed for QuickDAV either, and it works on anything with a browser. You could transfer files to your Nintendo DS. ;)
Alright, fine I will try it. I have to admit the web browser part does sound interesting.
KDEConnect is honestly going to be better. It’s runs on everything (yes, Gnome and Cinnamon), has transport and device security, and offers more than just file transfer.
KDE Connect is one of the most amazing pieces of software I’ve used in my life
GSconnect extension on GNOME, and its honestly amazing. Send files, copy clipboard, auto pause my music when a phonecalls comes in. Custom commands from the phone to lock my session if I’m away from my desk. Such a great application.
It also has
kdeconnect-cliwith e.g.kdeconnect-cli --share myfile.txtso don’t think you are stuck with a GUI to use KDEConnect.KDEConnect is great, but I don’t think it can share a folder. If you want to transfer a folder from, say, a MacBook to a Linux PC, I think QuickDAV would be better suited than KDEConnect. Also, QuickDAV works on Win/Mac/Lin.
You can send entire folders from Android/iOS just fine with a normal file browser.
Downloads for all platforms: https://kdeconnect.kde.org/download.html
“go to another machine on your LAN”
So its basically syncthing?
But that its not able to decide who gets whick file as there is only one option to log in in QuickDAV?
But maybe more intuitive?Syncthing (as the name implies) is meant to synchronize folders across machines. QuickDAV is meant to transfer files/folders from one machine to another. They definitely both have there uses, and there uses might overlap in a lot of cases, but they also have there own niches. Like, I wouldn’t use Syncthing to transfer a photo to my desktop once, and I wouldn’t use QuickDAV to keep my photos directory synchronized across several machines.
for one time transfers (e.g. friends phone) I use warpinator.
if I own the device I use scp/rsync.
to keep files in sync I use syncthing
I just install openssh server, because I need it anyways, and use an SFTP client to transfer files. Seems to be fast, secure, and easy. No new ports to open up.
I’ve transferred many terabytes of data this way, no complaints. Rsync is nice for syncing huge folders, and walking away, so I’ll also use that when the need arises.
A bit of self-promotion here: check out my free app SSH Pilot that supports SFTP/SCP file upload/downloads https://sshpilot.app/
You lost me athaving to use flatpak.
Lol what? Are you against Flatpak? Are you a snap fan?
You’re strawmanning their comment— I’d imagine they’d have the same, if not more, issues with snap.
Flatpak doesn’t integrate well with all systems. For me personally, on Arch, I have to update and store Flatpak versions of some dependencies, like proprietary Nvidia drivers, separately from the rest of my system and its package management system. And it does take up some space to store the runtime too.
Also Flatpaks may require some extra set up and/or workarounds due to their sandboxed environment. That’s not inherently bad and has some big security upsides, but it’s a consideration.
Also I don’t know how well it plays with immutable distros, but I’d imagine there may be similar integration issues there, too.
It’s still probably a lot easier for devs to have a consistent distribution format though, and they are typically more secure, so I’m not saying there’s not merits to only providing a Flatpak. Just pointing out that your reply here was misguided, imo.
I wasn’t strawmanning, I was asking a question.
deleted by creator