I've been monitoring OK's proxy (SetiQueue) for a few days and there is a pattern that matches the announcement made by S@H. During the day OK's proxy is not able to get through to S@H; thus, he builds up a large cache of our results. Around 9:00 PM PST Berkley raises the network priority to high for S@H and things flow like crazy. Last night at 10:00 PM CST (8:00 PM PST) I checked and OK had about 800 results stored. This morning when I checked at 5:45 AM CST (3:45 AM PST) everything had been flushed and things were working normally. Some where around 6:45 AM PST they reduce the S@H network priority to low (or, the other traffic picks up.) This allows other campus traffic to take priority and we get shut out. If there is a lull in other campus traffic then some of our data gets through.
Due to this new policy forced onto S@H by Berley, we are going to have connect to a proxy, or have our own cache. SetiQueue works great as you can have it connect once per day at a time you specify. I have my queues (3 locations) flush to OK's TeAm Proxy. I also have some remote boxes with SetiDriver that connect to OK's Proxy. They have no idea that there is a bandwidth restriction for S@H. They just keep crunchin'!
So, please don't get discourage! Instead find a way to make this work for you!
I would suggest spreading out our use of proxies and not all us the same one. It might be nice to have a round robin as they have with RC5.