mcavic - 8:09 am on Dec 12, 2006 (gmt 0)
I've cleaned up after people with that approach. Often.
What approach? Designing a system around a powerful, simple, and fast language and database? You probably mean cleaned up after people who didn't know what they were doing.
"I want to know when my site is rejected, so I can immediately suggest it again."
Ok, but with a proper database, you can store all of the domains ever suggested, and refuse duplicates.
The specifications, let alone the implementation, were complex enough that implementation would have been a high risk.
If you have a Web site that lets editors see the pending URLs, and there are buttons to approve or reject a URL, all you have to do is make those buttons find the email address that sent in that URL, and shoot off an email.