@Dendrobatus_Azureus frankly, I dont get hype around localsend. Never used it but I hate it. You must install on both ends, like KDE connect, but KDE connect gives you a lot more than just sharing a file. And if the only thing you need is filesharing, then you have plenty of solutions to choose from - most of them only need serverside, and nothing new to be installed on client. So where is benefit of localsend?
Discussion
Loading...
@Dendrobatus_Azureus frankly, I dont get hype around localsend. Never used it but I hate it. You must install on both ends, like KDE connect, but KDE connect gives you a lot more than just sharing a file. And if the only thing you need is filesharing, then you have plenty of solutions to choose from - most of them only need serverside, and nothing new to be installed on client. So where is benefit of localsend?
Thank you for your reaction.
Your statement
'never used localsend but hate it'
fascinates me. Can you elaborate on how your process of thought flows when you say that?
I cannot hate something I don't know, I don't test, I don't try out, and I do not even hate things or people, because it is positive energy, that I flipped around to negative energy, which benefits no one; not even me
#KDE #Gnome #Cairo #library #Xfce4 #airdrop #localsend #kdeconnect #ftp #Linux #ARM #SBC #programming #opensource #technology
@Dendrobatus_Azureus yeah I know, thats why I said it. I just think local send is over-hyped. It is meant for LAN files sharing, and this problem humanity solved in like 90s. Diffrent solutions get their own place in my heart. Syncthing for easy NAT traversal. KDE Connect for Apple like experience on any phone. Nextcloud for its web interface. In single houshold setup I'd use SMB (Wndows built-in default) or SFTP (default on Linux). Less configuration, less programs to work with. The standards.
I've read your responses to my toot twice. Thank you 💕 for reacting.
IMHO your though process does not justify the hate you've got for localsend.
Your hate towards, the for you unknown program, localsend is **unfounded*"
Cherish the fact that there is choice and diversity in OpenSource programming.
Stable release versions for synchronizing files exist since the 1970s, not the 1990s. You've clearly not been around long enough to realize that fact **
Ever since plain simple sh existed, such programs were coded. One such program was coded more than fifty years ago and is still in active use.
Please be so kind to use wisdom and intelligence when you react and respond to toots. You acted like a typical snobbish Linux user. Reactions like yours don't contribute anything positive, no one learns from toots like the ones you posted in this thread.
I've never had such responses from the people in the BSD range of Operating Systems.
Even here on the FediVerse the diverse responses from Linux only users and programmers were not of such nature and low caliber.
I'm surprised, yet paradoxically expected your motivational chain.
** If you have been around long enough, to know open source code from the 1970s, look in the mirror and ask yourself why you have reacted in such a manner .
I will still wish you a good day / night, wherever you may reside.
EOF
^Z
#KDE #Gnome #Cairo #library #Xfce4 #airdrop #localsend #kdeconnect #ftp #Linux #ARM #SBC #programming #opensource #technology
@Dendrobatus_Azureus @florke64 sharing *between phones* is still annoying though.
Localsend works well in this respect - no logins, and cross-platform, simple interface, broadcast advertisements, and can transfer whole folders with ease.
I've used it to send files to mates sitting next to me multiple times.
Even if there's no WiFi, I can enable my hot-spot and then transfer files directly, and then turn it off again.
I totally agree that this sort of thing should have been fixed decades ago with some sort of standard for ad-hoc file sharing on LANs that is cross-platform, but every time someone tries, it doesn't get very far, and then vendors try and tie you in to their "standard", like Apple Airdrop or Samsung quickshare.