After looking at the problem and some comments people have made, I don't think doing a whole reorganizing of who connects to what proxy is feasible. It looks like the only way to do this is on an individual basis, with each person deciding on a proxy server him/herself.
So, I'm gonna offer my SetiQueue as a full alternate to OK's. At peak traffic a few months ago my server was handling about 300WUs/day, with no adverse effects to system or network performance. I'm gonna go out on a limb and predict that I can handle at least 3 times that much traffic, or 1000WUs/day. I keep very large Q-sizes (20 days worth/user) but I actively delete waiting and pending WUs older than 30 days (except when Qs are running low). I also tend to shuffle WUs around to make sure that all users are stocked as much as possible.
All I ask in return is:
- New users PM me within a few days of beginning to use the server
- Users return the results of WUs back to my proxy (as much as possible)
- Users no longer planning to use the server PM me with that info
- Users PM me ahead of time if they expect a drastic increase/decrease in production
This is simply to help me better manage the resources available. One more thing I should mention is that I frown on users connecting to my proxy just to refill their own stockpile without notifying me. When people do this, they only get WUs as quickly as my machine can download them from Berkeley, and it prevents all the other users' Q's from getting any more WUs. When people do do this, I set their account to low priority and if it continues I'm forced to ban them from my proxy.
I may be strict, but it's the only way to make sure all my users are served properly. Anyone on the TeAm is welcome.