LYLEG  If you would like to store things on a server and make them easily available to others, pay the trivial registration fee and get and use FileChute.

"Things" could be photos you want to use in a post to a forum, or a 6 MB file you want to give to a colleague but which is too big to attach to an email.

You just drag your file to FileChute, and it uploads it and hands you a URL to use for it. The process is so easy, so fun, you will find yourself using photos more often in your posts just so you can use FileChute. It is poetry in motion. It is so easy, that to an old-timer like me, it is startling.

But the best way to see how wonderful FileChute is, is to download it and try it out.  
(Version 4.2.5)

LYLEG  So I look at my mailserver's queue, and see that one of my clients is trying to email, as an attachment, a file that is 248 MB in size. That's a quarter gig. What is he thinking? It has been uploaded, as my server lets my clients get away with murder. But the destination server is having none of it.

So, I walk down to his office (fortunately in the same building as my datacenter) and he says it's just a scanned document he's sending to his payroll company.

Now, I could have gotten into the whole world of resolution, pixel depth, image editing, and software he doesn't have, but instead had him copy the file to a thumb drive, from which I then dropped the file onto FileChute on my PowerBook.

Filechute gave me the URL to where it was putting the file it was uploading, and I emailed that to my client. I told him to paste that into an email to his payroll company.

"That's it?!", he asked, incredulous. He could not believe he wasn't going to have to FedEx a paper copy or send the file in 100 pieces or do anything even more painful.

Words like "That's it?!" have to be music to a developer's ears.

I extolled the virtues of the Mac and FileChute while the file uploaded, then unplugged the PowerBook and went on my way.

My client may purchase a Mac just so he can run FileChute. It is that good.  
(Version 4.0.1)