Unfortunately there is no way to do this perfect. The way I would do this is to make the users and the webserver members of the same group (create a new group especially for this purpose). Then set the group-owner of the newly created dir to that group, and the permissions to 775, like this:
$path = "/home/foo";
mkdir("$path/artist");
chgrp("$path/artist", $groupname);
chmod("$path/artist", "0775");
This will allow the group to modify the directory (remove it, move and so on). Something that you'll have to do if you do this is to make the FTP server perform a chroot() so when user [FONT=courier new]foo[/FONT] ftp's in and his start directory is is home ([FONT=courier new]/home/foo[/FONT], that is made his root. This prevents the user from leaving the home-directory. I'll try to show you what I mean with this "log":
[FONT=courier new]
C:>ftp ftp.foo.net
Connected to nic.foo.net.
220 ftp.foo.net FTP Server (bogus software inc.) ready.
User (nic.foo.net🙁none)): bar
331 User bar okay, need password.
Password:
230-
230 Restricted user logged in.
ftp> pwd
257 "/" is cwd.
ftp> cd ..
250 "/" is new cwd.
ftp>
[/FONT]
When the user bar is logged in, his home is the topmost directory (as seen in the bolded line above). This prevents the user from entering other users homes, and thus from tampering with other users files in the artist-dir.
Another important aspect is that you shouldn't give out shell-access to this machine, as users logging in via telnet or ssh will be able to enter other users artist-directories.
Good luck,
Olle