So back in the day when we were all about the xboxes (see also: San Andreas), searches on Google for the UDE exploit directed people to the xbox-scene thread where UDE was released. But, because of some restriction in the forums, the UDE people (Insert names here) posted the file as UUEncoded forum text. For the slow kids in the class, that means that the binary files were (rar'ed and) converted to ASCII text, like you'd find in Usenet, like you're reading right now. UUEncoding has some disadvantages, but the ultimate upshot of it is that it fits files into places that were not designed to host them. As it turns out, the Google Cache is one of those places. This means that you can have Google mirror your files (Within the Google Cache storage limit), which could (if you had a small file that EVERYONE wanted, which doesn't happen often) potentially save you some bandwidth. Once the cache was up, you could just link to it directly. Alternately, someone could dump text into poorly-programmed forums or guestbooks or whatever. Your humble narrator isn't aware of a firefox plugin that automatically filters and displays encoded text as a file link, but is quite sure that one should be made.

Now, you could take this one step further and make that page only accessible by Google Cache by having it display a 404 to everything that isn't the Googlebot. So people could access the file, and you wouldn't face the threat of (or could fake compliance with) a DMCA takedown notice (and the resulting legal trouble).

So what kind of small things will fit within the limit?
-Small pictures
-Encryption keys (Truecrypt, for example)
-certain cracks
-password lists (Like the output of a USB Switchblade)
-ascii text files (re-encoded as ascii text files)
-source code (leaked or otherwise)
-file checking mediums (SFV, PAR, maybe NFO)

These problems are left as an exercise to the reader:
So, just how much does Google Cache hold these days, anyway?
What about