Q: Isn't this another stupid hack with no purpose
A: This is a cool hack that adds utility over other file system hacks. Its
an anonymous, persistent shared filesystem. Once something is uploaded,
only the database admin can delete it. Everyone can read it. No one can
know who created it.

Q: Aren't you picking on TinyURL?
A: Not really. Out of the box, TinyDisk is not configured by default to even
use TinyURL. Out of the box, you cannot upload files larger than 2 megs. I
am actively distributing a alternative system so people can play with
TinyDisk *without* polluting TinyURL's database.

Q: This damn thing doesn't work! #@%& You!
A: Did you just download it and run it? RTFM! It is configured about of the
box to use an instance of Nanourl running on localhost. Edit the config file
TinyDisk.config and select the TinyURL stuff.

Q: This damn thing doesn't work on large files! #@%& You!
A: Did you not read the manual? Man I wish I could punch you in the face over
TCP/IP! Change the config file's MaxSize line. By default the limit is 2 megs.


Q: I've been a cipherpunk since 1983, and this is not "anonymous." Whats up?
A: The system is more anonymous than say, the Gmail File System. There are no
requirements to post info into TinyURL. There is no account to track. All
there is an IP. TinyDisk is HTTP based, so you can always you a proxy to hide
the IP. Other people are solving anonymous HTTP/TCP traffic. Go get Tor
(tor.eff.org)

Q: TinyDisk sounds a lot like the Eternity Service. Have you heard of it?
A: Yes it does and yes I have. The Eternity service was a way of publishing
information so that it can not be removed. An implementation of it described
in Phrack used USENET. TinyDisk resides on only one server, so it is
controllable. However the write-once-read-many globally shared goals of
TinyDisk were inspired by the Eternity Service.

Q: How can I find meta files?
A: I have uploaded a few books into TinyURL, and the meta files are on the
website. I did not create a BitTorrent/Search Engine/Distribution System for
the meta files. The cool thing is groups can use TinyURL and keep the meta
files a secret.

Q: Can't TinyURL shut this down when ever they want to?
A: Sure. They can search their database for big clusters are delete them.
They can limit the number of hashes an IP can create in a day. They can search
for Base64 encoded data in their database. they can find meta files and delete
the clusters specified.

Q: Do you have countermeasures to these methods?
A: Yes, but none are enabled. TinyDisk can create meta files that look exactly
like PGP/GPG public keys, so TinyURL cannot find them. You can limit the size
of the cluster in code so its a reasonable size. I can use a proxy framework
and post all the data through a list of proxies. I can prefix all the data with
a legit URL like Amazon or Google or another size that uses Base64 encoded
parameters.

I really don't want to get in a tit-for-tat butter battle with TinyURL. They
have a cool service. There are things they can do to try and stop TinyDisk.
There are ways to avoid most all of their defenses. I have crippled TinyDisk
out-of-the-box so their database does have gigs and gigs of pr0n uploaded into
it. I don't think I'll even register on their radar.

Q: Could TinyDisk work with other services?
A: Sure. Currently it doesn't, but if there is a way to store any amount of 
information in a backend website database and retrieve it, TinyDisk could
work. Amazon reviews perhaps?