>The fact that life doesn't end is not an excuse to poach. Poaching hurts >the project because it drives away participants. It is not harmless. I >don't know why people keep defending it.
I think that there are two possible solution paths to poaching. 1. Punishment (capital punishment?) and making poaching hard to do. 2. trying to understand causes behind poaching and then change the server software more milestone friendly. I think that we are like to reach milestones. I personally refer option 2. I like when we reach milestones and here are few things I would like to change : 1. Why one size fits to all? 60 days expiry time to all task is not a good idea. Smaller tasks should have lower one. Like 30 days. 2. I would like to assign bottom 5 % of double check assignments to trusted searches (who have shown that they return their jobs fast and reliably. 3. When George release small exponents to triple check then these should assigned to trusted searches. 4. very slow computers should concentrate to trial factoring. 5. maximum time limit to bottom 5% double checks (like 6 months) I think that poacher does not necessarily care about cpu credit so taking that away from poacher is not sure solution. I don't know any other realistic punishment. Rejecting work does not sound very clever idea. I think that we should start with option 2 and wait some time and only after that start using option 1. Yours, Nuutti _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
