One of the most common sources of frustration I have on a regular basis is that of filesharing. That’s because while everyone has the internet, how we have it and how we use it is so unique to each of us, that we often end up with a few incompatibilities.
Let’s take email. Everyone’s got an email address. But not everyone supports the same file size for attachments and downloads. I can send 20MB files (thank you GMail), but you might only support 5-10MB (like my Cox account supports). Now what?
How bout IM’s? Excellent. I use AIM. You use MSN? How are we even friends? Ok I use Adium. What? Ya, it lets me use AIM, MSN, Yahoo, etc. Great. Wait, does it let me share files across? Yes. But crap, I’m on a router, so now I have a firewall. What, you’re on a router too? But it says the file is sending. Of course, it’s said that for the last 10 minutes. And ya, I’m just trying to send you a small jpg, so this should have been done nine minutes ago.
Ok how bout FTP? Great. I have one. Do you have a server? What’s your ftp address. What, that’s private. Ok. I’ll post the file on my webspace. Wait, now it’s too public.
Using a common protocol is tough for sharing because we may not have any in common. Making a file public is bad because now the file is public. It’s funny because the answers we seek end up being their own problems. So what if I had a place where I could store files, make them public or private on a file or folder level, share them via email, a special link, or otherwise, and generally have the ease of use of a download for our users, while we have the security of using a service with its own protocol on our backend.
Oh ya, what if it were free too, unless you want to move single files that are over 100MB (which at the rate cameras keep upgrading the sensors and megapixels might be next year)? Keep on reading! [Read more →]
Tags: general by PShizzy
8 Comments »