[skreutzer]

Regarding the term “uploading”: nearly everything on the web was once uploaded. A webserver is a computer system (it could even be an ordinary machine, but often it is a specialized one) which as a webserver software running on it. This software turns an otherwise “client computer” to a “server computer”, because the software listens for incoming requests by other computers over the network it is attached to, and serves them files which are located on its hard drive. If you with your client computer want to make a file accessible to all other clients who have access to the webserver, you need to “upload” it by transferring your file onto the hard drive of the webserver. There are programs to do that, one insecure (password gets transmitted in plain text) but commonly used is a so called “FTP program” for direct upload and download to the servers hard drive. As it is usually inconvenient to download and then view files with a FTP program, we use other programs which are called “browsers”. They combine downloading and viewing to one single step. Also, for uploading there are ways to use a browser too: a webserver software can be configured that it serves websites which provide an upload facility, either by a “choose file” button or by a text field in a form, which after submission gets transferred to the webserver, which either places the uploaded file on his hard drive or stores it in a database, so that every “download/view” attempt later gets the stored text of the database served. Wiki's, forums and blogs use the latter method.

I've seen that you use a blogspot blog. Its software is limited to only allow text and image upload (as far as I've read), but all the resources you present there were uploaded by you, and if I look at them, I download them automatically (then it's my choice to save it permanently or not). For a fully functional personal website, usually one rents so called “webspace” (a certain portion of hard drive storage) on a webserver, while for convenience the webspace provider operates and takes care of the webserver software for you. By default, there are no files to serve for such a website, so one has to upload the manually coded websites or install some web software onto the rented storage, like blog-, forum- or CMS-software. A database (well, several database instances) should be part of the rental. Now I don't know if there are any ways to provide files with blogspot, but if not, there are still options if you don't want to rent your own webspace somewhere: you could use the webspace of somebody else. There are services which allow upload to their servers free of charge (but those sites usually include some kind of advertisement of theirs, maybe a link to a public DropBox directory?), or you know somebody who operates his own website with rented webspace. But again, it depends on your expectations. I for instance have plenty of webspace rented for my projects, but a downloader would then see my domain instead something which is clearly attached to you. And I guess you don't want to publicly distribute your text to everybody, so uploading it to a file sharing platform or an e-book distributor might not be an option.

On rented webspace, I for instance run a piece of code which auto-responds requests to a contact form, and it would be easy to mail the requester the link to your file, which isn't linked somewhere else on a website, so web-crawlers couldn't find it as long as no one of your e-mail recipients posts the link on the web. If the file has a name which is hard to guess or at an place where somebody wouldn't expect it, it would be hard to find it by humans (but not impossible, because you can be sure that network traffic and e-mails get scanned all the time if it isn't encrypted, and even if it is encrypted, people have all kinds of malicious software on their computers that spies the user even before the moment of encryption).

Probably you could too send an auto-respond e-mail with some web-software, which contains the e-book as attachment, but I personally don't know how to construct such an e-mail (yet?), and I haven't looked into existing software which does this kind of thing. Certainly there are already existing solutions for both, e-mail attached delivery and download delivery, but in any case one has to look up or to find out advantages and disadvantages of them. If you're really interested in delivery by e-mail attachment per auto-responder, I could invest some time and find out how this is technically solved and if it would be easy enough to just write a script for that. Please note that I only know how to implement an e-mail auto-responder to a button click on a website, but I don't know how to auto-respond to e-mails which get received by the e-mail software of the webserver. A clickable button on a website is findable by all people, but maybe that's not a problem, because you would otherwise have to publish your contact e-mail address for free of charge e-books too.