Hey PH!
We are enabling private and much faster P2P file transfer over the web.
By using web protocol WebRTC, we eliminate the slow and costly initial upload step traditionally required when sharing files via Dropbox/CloudApp/etc. For most files, this is a big deal. Instead of first sending the file to an external server, the sender immediately gets a link they can distribute. And when a recipient clicks it, they connect directly to the sender’s computer to complete the download, eliminating the server middleman. Because the file is never actually saved on, or even touches, our servers, the transfer is incredibly private and secure.
Going to have to make a couple pizzas using your url recipes!
…pizza/peppers-zucchini-turkey-brie
…pizza/tuna-venison-avocado-beans
…pizza/dill-fungi-colby-spinach
Great easter egg. Makes me curious how many 4 topping pizzas there are possible.
Had no idea that .pizza was actually a domain.
Report
This one doesn't seem to work. It stays on 0, 0, 0 without giving any sort of detail. A log would be nice, i think.
Report
File transfer started and failed twice, then after restarting browser (Firefox) transfer wouldn't even start. It's a shame, free and direct (no cloud storage) secure file transfer was exactly what I wanted.
@fredrivett Chrome has issues with file downloads over 500mb due to an outstanding ticket (375297). Firefox doesn't seem to have a limit, however we haven't tested it yet on files >2gb. Interested to hear how it holds up.
Report
@fredrivett@kerncancode I recently put file transfer on my site http://simulchat.com and I also ran into the issue on Chrome. It seems the way to overcome this is to use Chrome's FileSystem API that writes to a sandboxed part of the hard drive. If I solve it, I will let you know
Report
@kerncancode@wessel_wessels Interesting. Are these limits due to using peer-to-peer over file storage like WeTransfer?
Report
@kerncancode@fredrivett No not at all. You can send any size over peer-to-peer. The data is sent in small pieces, so sending is not the problem. The problem is receiving. The data coming in is stored in RAM. When you are done receiving, you save the file from RAM to your hard drive. The problem is that Chrome can't handle that big files in RAM and crashes. What should happen is that the data coming in is stored in a temporary "file" on your hard drive until you are ready to save it. Hope it answers your question. Ask again if you still don't understand completely
Report
@kerncancode@wessel_wessels Great answer, thanks Wessel! Might be worth you guys adding a small FAQ sometime if you find others have similar questions, just to clarify these sort of things :)
@tzhongg We think it's ridiculous how difficult it can be to send someone a file, even in 2015. Kern and I believe this xkcd comic sums it up quite nicely :)
https://goo.gl/HUJWs2
Atlantic Money
VotePlz
LongShorts Stories
noplace
