1–7 of 7 posts
http://fppr.co
What do you think? Do the people need that kinde of service or they will prefare use clouds to share files?
* People that care about privacy are probably a target market for you if your service is able to deliver.
* The name of your site is "fppr". Pronounced quickly, that sounds like "Fapper". Please tell me that this is intentional because that's amusing.
* I'm not sure what you mean when you say "no server storage". It seems like it temporarily does have to be stored on your server to facilitate transfer. Please correct me if I'm mistaken or update your site to explain how your site works. * People that care about privacy are probably a target market for you if your service is able to deliver. * The name of your site is "fppr". Pronounced quickly, that sounds like "F…
EDIT: It would appear that it is the latter, in that it uses Socket.IO to stream it to the server and down to the recipient. The server could copy it as it is streamed, and I didn't really delve into the source of the webpage to know if it has any encryption or anything.
* I'm not sure what you mean when you say "no server storage". It seems like it temporarily does have to be stored on your server to facilitate transfer. Please correct me if I'm mistaken or update your site to explain how your site works. * People that care about privacy are probably a target market for you if your service is able to deliver. * The name of your site is "fppr". Pronounced quickly, that sounds like "F…
Thank you for your advice. Next step is privacy and encryption!
I've never thought about "Fapper"!... :) Well, it is "FilePopper" and fppr is for short url...
* I'm not sure what you mean when you say "no server storage". It seems like it temporarily does have to be stored on your server to facilitate transfer. Please correct me if I'm mistaken or update your site to explain how your site works. * People that care about privacy are probably a target market for you if your service is able to deliver. * The name of your site is "fppr". Pronounced quickly, that sounds like "F…
My best guess is that it uses WebRTC for P2P transfer. It may also use WebSockets to connect to a private room (which only one source-client and one destination-client may join) and streams it. EDIT: It would appear that it is the latter, in that it uses Socket.IO to stream it to the server and down to the recipient. The server could copy it as it is streamed, and I didn't really delve into the source of the webpage…
I find direct transfer really convenient and preferable to dropbox for certain things (like large files that you only need to send once and to one person). I could see something like you're doing being helped by being built into a chrome plug-in or something so people can automatically receive. The angle of my project is being in the background and automatic, but giving the receivers full control over what types of things they want to accept.
I have a similar project that attacks this problem from a different angle: http://deployanything.com I find direct transfer really convenient and preferable to dropbox for certain things (like large files that you only need to send once and to one person). I could see something like you're doing being helped by being built into a chrome plug-in or something so people can automatically receive. The angle of my project…