Google's interpretation of Apple's AirDrop, Nearby Share, is now officially out of beta for Windows.
https://blog.google/products/android/nearby-share-windows-android/Open linkView original on lemmy.world107
Comments23https://blog.google/products/android/nearby-share-windows-android/Open linkView original on lemmy.world
www.localsend.org
Same thing, no Google.
also great, and entirely in web browser so no download needed:
https://www.sharedrop.io/ - also works over the internet! no local network necessary
https://snapdrop.net/
And you can run your own local instance of Snapdrop too! Got it running in Docker on my Synology NAS.
PairDrop is an improved version of SnapDrop that works both locally and over the Internet. I've found it more reliable to set up.
Pairdrop is great. Lives in a tiny Docker container and hasn’t failed me yet.
oh yup! i’d heard of that one but couldn’t remember its name
From reading the app description:
Does this mean devices have to be on the same Wi-Fi network for this to work? This looks extremely interesting as someone that runs Linux on my home computer, and the vast majority of my transfers are between devices on my home WiFi network, but I'd just like to know if it works elsewhere.
As the name implies, it's local only. GNOME Warp supposedly works both via internet and LAN.
Although you could make any local app also work via internet using wireguard, tailscale or similar.
Thanks for sharing! Just a heads up that we typically ask that the original source be posted (in this case, the release from Google at https://blog.google/products/android/nearby-share-windows-android/). If you don't mind editing the submission, it'd be much appreciated! On Lemmy, we can update both the title and link :).
Edit: this was actually already shared it seems! https://lemdro.id/post/121569
Oki doki, done, I had no idea you could do that.
Can someone explain to me why google needs to know when I am sharing a file locally?
Because Google. I will say tho that at least during a beta it's very normal for the terms and conditions to specify sending info about each transfer and also bugs..
Analytics of how many times users use certain features is very normal in software development
KDE Connect - available for Linux, Android, iPhone, iPad, Windows
A ported version is available for Mac.
It supports to transfer files, clipboard, able to access/send SMS, use it as remote keyboard/mouse, pass terminal commands from mobile to pc and many more without Google.
The peer devices should be on same Wi-Fi, that's the requirement.
I don't know what the experience is like for other people but KDE connect sucked to use on windows for me. It was a coin toss whether or not it would detect my devices. Nearby Share has been flawless so far.
Official document for your issue: https://userbase.kde.org/KDEConnect#I_have_two_devices_running_KDE_Connect_on_the_same_network,_but_they_can't_see_each_other
This document explains why you don't deduct the devices. It's caused by firewall, you just need to open the ports or add exception to the app.
This doesn't fix my issue. Like I said, the devices do see each other, it's just that it only happens sometimes. I can't be bothered with tinkering with my router just to have software working when there are easier alternatives that work out of the box.
The thing with apple is once they release a feature that has been on other phones for ages, they release it as if they had just made the whole concept up "now for the first time users will be able to..." just doesn't resonate with me if the whole core concept was already stabilised.
Now do mac... ? :(
Is it just on my end or it takes about half a minute for the Windows device to detect the Android device, but not the other way around?
For me it takes minutes to find each other
Completely unusable