Can't use Google Nearby Share? Use open source Snapdrop instead
Nearby Share is a built-in feature on Android to share files with others using Bluetooth. Google launched a Windows preview of Nearby Share this week, but it is limited in several ways.
If enabled, it allows Windows users to send and receive files with Android devices. Sharing can be limited, e.g., to other devices owned or Google contacts.
Nearby Share has several limitations. First, that it is only available on Android and now also as a preview on Windows. Then, that it requires a Google account and that some functionality relies on contacts associated with that Google account.
What if there was an alternative, that is platform agnostic, does not require an account, and is available anywhere?
Snapdrop file sharing
Snapdrop is an open source service that is available as a web service. It works in any modern web browser that supports WebRTC, has plenty of "unofficial" instances available, and may also be set up by users on their own servers.
Here is how it works:
- Open a modern web browser on any device you own and load the Snapdrop website, or another instance. The official website was not working at the time, but some of the instances were.
- The device should receive a codename automatically.
- Now open the same website on another device. The web service should identify both devices automatically, if they are on the same network.
- In case they are not detected, select the link icon in both browsers and enter the code that is displayed in one of them. This pairs both devices, even if they are not connected to the same local network or if the detection fails to detect it.
- All that is left to do is click or tap on one of the devices to send files or messages. A left-click opens the file sending option, a right-click the message sending feature on PCs. On mobile devices. use short and long taps for the functionality.
Files are transferred using WebRTC. They are encrypted during transit and files are transferred directly between peers using the technology. Snapdrop can't view the files due to the encryption.
Probably the only issue right now is that the Snapdrop web service may go down at times. There are instances, but one has to trust these instances. The other option is to set up a Snapdrop instance and use it exclusively. The GitHub repository offers instructions on how to do so.
Closing Words
Snapdrop is a straightforward option to transfer files and messages between devices. It is a bit more comfortable if all devices are connected to the same network, but does not require this. The service is open source, platform agnostic and really easy to use.
Cautious users could encrypt files before they transfer them to add another layer of protection to the process.
Now You: how do you transfer files between devices?
Remember good old SMB and FTP/FTPS/SFTP still work over the WLAN. Or just use Telegram or WhatsApp to send them over the web.
The only devices I “trust” – to the degree I trust anything – is my phone and my home PC. The phone runs Android and the home PC run openSUSE Leap 15.4, which has KDE Connect, which is also installed on my phone. Trivial to move files from the PC to the phone using the Dolphin file browser. Slightly hard to move files from the phone to the PC – IF I try to use the KDE app. But why bother when I can see everything on the home PC file browser?
Now of course this is useless in transferring a file to someone else. Fortunately I never do that and wouldn’t trust opening my phone’s connections to anyone else’s malware-laden phone.
When it comes to transferring files when away from home, I could use OneDrive, PCloud or Google Drive, or JuiceSSH – if I had the SSH server active at home, which I don’t. I could also use a variety of VNC-type apps and home services – if I had them running, which I don’t. I don’t because I don’t transfer files from anywhere to home or to the phone when out and about.
I don’t even carry my phone when I’m out and about. :-)
See how simple that becomes? :-)
“Files are transferred using WebRTC.”
Wait! You’ve told your readers to disable WebRTC due to privacy concerns.
https://www.ghacks.net/2015/07/02/you-can-block-webrtc-from-leaking-your-ip-now-in-ublock-origin/
https://www.ghacks.net/2018/03/29/how-to-check-if-sites-use-webrtc/
Many readers may have even followed your manual directions: “You can do the same thing manually by setting media.peerconnection.enabled in about:config to false.”
Now, about face, forget privacy concerns and use a program that relies on WebRTC.
That’s silly when there are so many other options–several of which I mentioned in your first article on Google Nearby Share service.