jakob/PairDrop
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update faq.md

Browse source
This commit is contained in:
RobinLinus 2015-12-28 02:35:54 +01:00
parent 1a2f6f4041
commit f2fba8e4db
1 changed files with 9 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
faq.md
View file

@ -7,12 +7,19 @@ If WebRTC isn’t supported (Safari, IE) it uses a Web Sockets fallback for the
### What about privacy? Will send files be saved on third-party-servers? ### What about privacy? Will send files be saved on third-party-servers?
No files are saved on a third-party-server. None of your files are ever saved on any server. If you are curious have a look [at the Server](https://github.com/capira12/snapdrop/blob/master/server/ws-server.js)
Snapdrop doesn't even use cookies or a database.
It does use Google Analytics.
### Is SnapDrop a fork of ShareDrop? ### Is SnapDrop a fork of ShareDrop?
No. ShareDrop is built with ember. Snapdrop is built with Polymer. 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. 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.
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.
### Where can I see the source? ### Where can I see the source?
[Github](https://github.com/capira12/snapdrop) [Github](https://github.com/capira12/snapdrop)
### Snapdrop is awesome! How can I support it?
* [Buy me a cup of coffee](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FDAHZJH3228D6)
* Fix bugs and do a Pull Request. This is my first open source project, so I am not very used to the common workflow, but we'll figure it out!