I am tinkering with my own *coin project, and one part of it was missing in OSS world - Faucet. (Block Explorer already exists - Abe!)
As a test, I set up Namecoin Faucet at http://faucet.yepcorp.com
. luke-jr and cocktopus already donated enough namecoins to it, so you can try it in action.
GitHub page - https://github.com/hippich/Faucet
It is based on Catalyst perl framework, which leverage my Catalyst::Model::Bitcoin module (which in turn leverage another, Toby's, module Finance::Bitcoin).
It is very simple - it uses Cache::FastMmap to keep track of IP addresses of visitors and number of requests done. What this mean - simply deployment (no DB) and no persistence between server restarts (application restarts should be fine, since session file stored in /tmp folder by default). Also, if amount of cached data will become bigger then cache size - unused records will get purged from the cache...
Protection from double-requests based only on IP addresses and reCAPTCHAs right now. No Google Account authentication like Gavin's Faucet have. Might be included in version 2 if it ever happen
So.. Please help test both front end and, if someone good enough with perl/linux, backend.