Sharedrop – Easy P2P file transfer powered by WebRTC
github.com
github.com
the same tired battle lines have been baked into tech for 12 years now, and it exhausts me to read the Google ones these days
it's sad that this is a source of innovation, but simply switching from Apple "infrastructure" and languages has been a massive step change in my productivity.
If you're really unsure, audit network traffic and the code
I would have guessed because they'd be liable for breach of contract or GDPR or whatever.
What does Google say about its analytics applied to its Firebase customers?
[0]: https://github.com/RobinLinus/snapdrop
Edit: just seen this was mentioned earlier down thread.
That being said, Sharedrop seems to be a different use case, only sharing file between folks on the same network. I applaud the effort, I will certainly like to try this out soon!
Turns out there's very few options available for really large P2P file transfers, short of hosting an FTP server.
(Most of the BitTorrent docs assume you're intending to distribute the files publicly.)
Not that the data was really worth protecting — it was just GoPro videos from a recent ski trip. But still, I didn't want to share my (unedited) home movies publicly.
I am not sure if Free version supports limited sharing But I guess you can open a folder for your one-time use then remove it afterward
So a good chunk of users will get really angry if a client comes with that bug. I haven't yet even found a way to make any ignore this.
Paying for extra space seemed overkill, given that this was literally a one-time P2P file transfer. I really should just be able to send a file to another IP address without having to pay for storage somewhere.
https://serverfault.com/questions/53531/copy-large-file-from...
Sorry to keep bike shedding this!
No mobile app yet but it already works on macOS, Windows and Linux.
cryo file manager
Drop your 80gb in the folder
Data syncs over p2p e2ee overnight.
Friend removes the copy from their sync folder and it vanishes from yours
Maybe it's possible to make a native iOS app you could send the files to that would use same WebRTC protocol but going the other way, Mac to iOS device seems impossible. Where as I just tried it via real AirDrop. I choose a file on my Mac in Finder. Picked Share->Airdrop. Selected my iPhone. I was given the option to open the file which then gave me a list of all apps that I could send it to. I picked an app and the app's folders appeared. I chose a folder to save it to and then ran the app to check it worked. It did.
I supposed Mac to iOS you could make your native iOS app the target and then from there select the files and "share" them with other apps on the phone.
AirDrop is one of those things that is truly wonderful in how easily and simply it works, but makes me really annoyed with Apple for not opening it and allowing it to be cross platform. Android had something similar for a while but it barely worked, and Google never put any effort into making an iOS app (which obviously would not have been as good as native, but better than nothing). Bluetooth itself has a function of airdrop-like sharing actually, but it was mainly used for spam and it’s basically nonexistent in modern mobile Bluetooth stacks. Something like AirDrop that truly works well cross-platform but wasn’t easy to spam would be so wonderful.
* Native Client (in Go so you use pretty much everywhere)
* Uses PAKE for E2E security. Even if the server is hostile they can't get anything.
I think the main difference is that webwormhole tries to use STUN/firewall hole punching to connect two nodes, while the original implementation will use a TCP-TCP relay as fallback.
I recently needed to transfer a 30 GiB file within a restricted network but the firewall blocked webwormhole, so I ended up with -williams instead.
Hopefully at some point all these project can converge into something that supports ALL the solutions :-)
That's an interesting definition of "same local network". So, this doesn't work for networks not behind NAT? Or for IPv6?
> who's on a single network (i.e. who has the same public IP)
Those aren't even close to equivalent. Now that most ISPs offer IPv6, they aren't even equivalent most of the time.
What happened to AirDrop? It used to "just work" and now it rarely works.
In the last two days I experienced: - Unable to discover devices (a constant AirDrop frustration) - Transferred a video from iPhone to Mac, had to wait for video to be converted first? - Transferred video from (different) iPhone to Mac, transfer repeatedly resulted in a corrupt 0 byte file
AirDrop has become totally unreliable.
AirDrop is nice - I understand Apple’s business reasons for keeping it Apple-exclusive, but the lack of bog-standard Bluetooth file transfer in iOS is just being mean.
I had always thought of AirDrop as a straight file transfer, but that's not the case.
It sounds like a neat feature. I wish I could use it.
When I tried this on iOS (different browsers, though they’re all using the same engine underneath), it was stuck on the loading screen. Turning off content blockers didn’t have any effect.
Edit: Figured out that this doesn’t work on iDevices (at least older iOS versions). There’s an alternative called SnapDrop [2], whose FAQ has this question and answer:
> SnapDrop a fork of ShareDrop?
> No. ShareDrop is built with Ember. Snapdrop is built with vanilla ES6. I wanted to play around with Progressive Web Apps and then I got the idea of a local file sharing app. By doing research on this idea I found and analysed ShareDrop. I liked it and thought about how to improve it. ShareDrop uses WebRTC only and isn't compatible with Safari browsers. Snapdrop uses a Websocket fallback and some hacks to make Snapdrop work due to the download restrictions on iDevices.
SnapDrop looks like a better alternative to me.
[1]: https://airdroid.com
> FIREBASE WARNING: The Firebase database 'sharedrop' has reached its peak connections limit. If you are the Firebase owner, consider upgrading. (https://sharedrop.firebaseio.com)
Powered by W? Is W a new programming language or JavaScript framework?
It looks like @todsacerdoti is not aware that Hacker News submissions are limited to 80 characters in the title. They probably wanted to submit “HTML5 clone of Apple's AirDrop - easy P2P file transfer powered by WebRTC” which is 73 characters long and represents the current project headline on GitHub, but then they added the project name at the beginning “Sharedrop:” turning the title into a 79 characters long string cutting “WebRTC” out. I think this would have been enough: “Sharedrop - Easy P2P file transfer powered by WebRTC”.