Scratch

You can't use cookies or IP sensing for the first task, that would only work if the user requested the "list" page in the same session or in the same network that he did the upload. You have to associate the files with the user that uploaded them, in the database.

For the second task, you have to search for some url-shortening service that you can use. I never used one of those for creating a feature of a webpage, but there should be some that provide some type of web-service that you can use. You'd send the base address and the service responds with the url-shortened version.

nathanprocks wrote:

i don't think IP sensing would work with dynamic IP addresses

Yeah, I realised.  Currently, I'm thinking about user registration, but that still leaves the problem of dynamic IP's. As I only want 1 account per IP, this would totally leave me devestated,.  However, I believe having to use emails would help prevent this problem, but still not totally fix it.  If you have any other ideas, please tell me.  Could it be that people have to download a plugin for their browser to signup to the service?   However, downloading wouldn't bother me to much, it's the uploading which I want to monitor.  It would be 1gb per acount, and as it's 1 account per IP, email, and plugin (possibly), I believe this would prevent any future problems?  If not, can you please tell me how I can prevent multiple accounts for 1 person?