The image host is functionally done, code-wise.
SUMMARY:
-Albums can be created and images can be moved into and out of them.
-Viewing an album will display only the images assigned to it.
-For coding purposes, allowing more than 1 album per image won't be possible. It's a lot of database work that doesn't need to happen.
-User- and album-specific URL's exist. I need to run through the code for album-specific privacy. The entirety of a user's uploads (in albums and not) and private images are protected, though.
--- http://aserverwith.no-ip.org/img.php?user=Phauss, http://aserverwith.no-ip.org/img.php?us ... &album=all, and http://aserverwith.no-ip.org/img.php?us ... album=none will return a "prohibited" page.
--- http://aserverwith.no-ip.org/img.php?us ... album=GIFs will return the "GIFs" album page.
--- http://aserverwith.no-ip.org/img.php?us ... album=test and http://aserverwith.no-ip.org/img.php?album=test will both return a "doesn't exist" page (unless you made an album called "test".)
-Images that are individually private will not be shown to other users regardless of that user's privacy settings unless directly linked.
-If someone other than the uploader is viewing an image album, they will not be able to change individual image settings. The album navigation menu and the overall privacy toggle button are also hidden.
To do:
-Make an album viewable to those not logged in. (Should be easy.)
-Allow album editing (name, privacy.)
-Clean up how images are displayed. Purely aesthetic with no code change.