commit 1a2f6f404147dbb8bf591efb52978dffe8cf8f6d parent bda1a15750e4a3bdf4124ababf5dd06a5a8d0640 Author: RobinLinus <robin_woll@capira.de> Date: Sun, 27 Dec 2015 23:25:54 +0100 Create faq.md Diffstat:
A | faq.md | | | 18 | ++++++++++++++++++ |
1 file changed, 18 insertions(+), 0 deletions(-)
diff --git a/faq.md b/faq.md @@ -0,0 +1,18 @@ +# Frequently Asked Questions + +### What about the connection? It's a P2P-connection directly from device to device or is there any third-party-server? +It uses a P2P connection when WebRTC is supported by the browser. (WebRTC needs a Signaling Server, but it is only used to establish a connection and is not involved in the file transfer). + +If WebRTC isn’t supported (Safari, IE) it uses a Web Sockets fallback for the file transfer. The server connects the clients with a stream. + + +### What about privacy? Will send files be saved on third-party-servers? +No files are saved on a third-party-server. + +### Is SnapDrop a fork of ShareDrop? +No. ShareDrop is built with ember. Snapdrop is built with Polymer. +I wanted to play around with Progressive Web Apps and then I got the idea to clone Apple’s Airdrop. By doing research on this idea I found and analysed ShareDrop. + + +### Where can I see the source? +[Github](https://github.com/capira12/snapdrop)