101–110 of 272 posts
Earlier quoted context omitted.
Yeah, your can do your dishes with the fire hose too.
People drive one ton pickup trucks to commute to their desk job. Or to get two bags of groceries.
Modern American SUVs are an abomination too. The American auto industry started pushing them because they're legally classified as "light trucks" which lets them take advantage of certain safety and environmental standard loopholes
> Because data is never stored in an intermediary server, the transfer is fast, private, and secure. But WebRTC needs a TURN server for when hole punching/STUN doesn't work when both clients are behind NAT. Data is never stored in an intermediate server, but it can pass through . How is the privacy and security ensured that the TURN server won't/can't read your data? Do you just have to trust them? Or is a form of E2…
Earlier quoted context omitted.
It was solved a decade ago, BitTorrent protocol
I think people mean something seamless like AirDrop is on Apple devides, but some public standard that gets implemented on all platforms like iOS, Android, Windows, macOS and Linux, so all these platforms can just easily send files to each other simply and securely over WiFi.
I 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...
Peer-to-peer: https://en.wikipedia.org/wiki/Peer-to-peer
I don't see which use case this is solving that hasn't already been solved by multiple other P2P file sharing browser based software available.
Nice project and I always like playing with WebRTC but there is something that has me a little concerned . > Transfers are now directly from the uploader to the downloader's browser (WebRTC without WebTorrent) with faster handshakes. Maybe I'm wrong, but there is a signaling server in the middle somewhere along the chain here no ? unless it's just the same as PeerJS in which you first need the clients ID, but connect…
Earlier quoted context omitted.
i like the name. pizza invokes thoughts of sharing anyway
As someone who had the misfortune of moderating a platform with filesharing features, I agree that the name is... really bad. (Cheese) Pizza is slang for CSAM. https://www.urbandictionary.com/define.php?term=Cheese%20piz...
Hopefully this isn't a "they knew what they were doing" situation
These 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.
> no first class standardized ways to move files over the Internet between PC/mobile/edge devices FTP? You can open an app on your phone, start an FTP server, use UPnP to poke a hole in the router, show their public IP address, send a text message to your friend with the IP, port, username & password in a single URL, connect, send/receive files.
I also meant things regular people can easily use and that can be used as conveniently as e.g. Apple's AirDrop (which is nice but only works between Apple stuff).
It's part a UI/UX problem and part a missing standards problem. The latter precedes the former.
I love this WebRTC based attempt to send files browser to browser. Too bad I’ve not yet seen it working without hiccups. I’m currently testing keet, which is in beta but promising as well. https://keet.io/
It'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?
I think it's because of all the NAT, which makes any attempt cumbersome for a lot of people.