I appreciate every single attempt at solving xkcd #949, but so far, all I'm seeing is an ever-growing pile of evidence for #927.
Peer-to-peer file transfers in the browser
61–70 of 272 posts
Re: Peer-to-peer file transfers in the browser
#62I keep a long list of browser based and CLI p2p file transfer tools[1]. LimeWire (which now has its crypto currency probably) has been on a rampage recently aquiring some of really good tools including ShareDrop and SnapDrop. https://pairdrop.net/ is the last one standing so far. [1]: https://gist.github.com/SMUsamaShah/fd6e275e44009b72f64d0570...
You should add sendme, it's one of the best I've tried for the CLI. https://www.iroh.computer/sendme
Re: Peer-to-peer file transfers in the browser
#63Earlier quoted context omitted.
https://wormhole.app/ has been spared and is pretty good. Encrypted, dl can start before up is finished, decent size limit. Unrelated to the wormhole python cli tool and associated file sharing protocol.
It's not a p2p tool btw.
It can be, if you send files larger than 5GB. https://wormhole.app/faq
Re: Peer-to-peer file transfers in the browser
#64I wish there was a way to do local peer discovery with WebRTC. Right now both endpoints need an active Internet connection and a shared identifier (in this case a special URL) in order to find each other. Can't do offline local sharing.
You can! https://github.com/pion/offline-browser-communication It uses mDNS for discovery. You can only do one browser though. I don’t see a path forward on browser/browser that is obvious. It would make it so easy to fingerprint if you could set your mDNS hostname in JS
A QR code should work if at least one of the browsers has camera access, I suppose?
Re: Peer-to-peer file transfers in the browser
#65Oh i love the use of webrtc for this, thank you for sharing! This was my half day covid project to share file... inspired by firefoxsend a while back... https://www.relaysecret.com/ the infra is super lightweight and you can deploy yourself with aws account, it costed me nothing to run and quite useful when needed :)
Nice! This uses server-side storage though, right?
Re: Peer-to-peer file transfers in the browser
#66It's so strange that this should have been a solved problem decades ago, but somehow a robust and secure non-commercial solution never gets off the ground. Speaking of which, how is the IPFS project doing these days?
It was solved a decade ago, BitTorrent protocol
Very different use case. It seems both too heavy weight and not capable enough for e.g. sharing a screenshot or PDF from an Android phone to a Linux laptop without Internet connectivity.
Re: Peer-to-peer file transfers in the browser
#67Opera browser used to have P2P file transfers as a short lived feature in ~2010, called Unite. I remember it also had skeuomorphic GUI of a 'fridge' where users could put post-it style notes that could be seen by others. One of many everything-and-the-kitchen-sink features Opera Presto had during its heyday. Others included a separate Bittorrent client, desktop widgets that could be moved outside of the browser windo…
Can we have that do-it-all Opera back? RSS, email, torrents. Feels like we had it all internet wise in 2007-2010 and then decided to throw it all away.
I think Vivaldi have both RSS and email, it's sort of the spiritual successor to the original Opera.... I miss the old Opera.
Re: Peer-to-peer file transfers in the browser
#68These are neat but... it's 2025, and there is still no first class standardized ways to move files over the Internet between PC/mobile/edge devices.
That's on purpose.
Imagine being able to just send a file from an Android phone to an iPhone without a centralized service and an Internet connection (i.e. like we could in the time of feature phones and early smartphones via Bluetooth)...
Please think of the shareholders and the lawful interceptors before you suggest something as subversive!
Re: Peer-to-peer file transfers in the browser
#69>filepizza
Horrible name dude
Re: Peer-to-peer file transfers in the browser
#70Ignorant question: isn't WebRTC just... built into the browser? Do you really need a stack of 20 things to tell the browser to connect to another browser with WebRTC? Isn't one HTML page with a few lines of javascript enough?