Sure, but while he was working on these new versions, Mr. Kan asked everyone to stop using his old ones.

Read Alex's post at the end of my link. At the time he made that request, he wasn't aware that there was a recent change in the stock app, resulting in what has now become an overclaim. He now feels that the advice he gave was wrong (and has apologized for it). These apps are not the 'new' ones he was (and still is) developing, but quick interim releases to bring the credit claims back into line.

I don’t know if this was suggested, but couldn’t the packets being sent back be stamped with what client there using? And SETI would, after warning everyone start ignoring those packets for credit? I know this would put a lot of people up in arms about credit. But it would solve fraudulent claims for credit?

As typed this message my eye kind of opened to this actually being very difficult to do because of people modifying there optimized client to imitate the stamp on an accepted client.

Ohh well just my 2 cents.

---

I don’t know if this was suggested, but couldn’t the packets being sent back be stamped with what client there using? And SETI would, after warning everyone start ignoring those packets for credit? I know this would put a lot of people up in arms about credit. But it would solve fraudulent claims for credit?

As typed this message my eye kind of opened to this actually being very difficult to do because of people modifying there optimized client to imitate the stamp on an accepted client.

Ohh well just my 2 cents.

The only problem here is many of those old clients are being run by users who do not keep up much with the project, but are still contributing. I see no reason to deny them credit altogether, but I think the validation/credit granting process could be reworked to avoid them penalizing the users with current clients and apps who are claiming the proper credit values. Award the pre floppers their lower claim, but also award the up to date user their correct claim.

---

"Time is simply the mechanism that keeps everything from happening all at once."

If you are using the anonymous platform to run an optimized app, the onus is on YOU to make sure it is always up-to-date. You got your 'official notification' to upgrade or revert to the stock app when the project started sending out the stock v5.27 app. It is long past time when people should have updated their optimized apps to either a new v5.27-compatible release or (if one is not yet available) reverted to stock. The only reason for someone holding out for some sort of 'official announcement' on the main page of the website's news section is that they want to game the credit system, and that isn't exactly honest.

Agreed - but note that Mac users have been stuck between a rock and a hard place for the last week or two. Either use Alex Kan's optimised app (which overclaims), or revert to the current Berkeley stock app (which overclaims even more).

Problem solved - Alex has released revised optimised apps, which are clearly the correct way forward.

Thanx to Alex for releasing his Mac apps with the proper credit multi. Are the current stock Mac apps up to date, or are they still using the higher multi that they were when released from Beta?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Thanx to Alex for releasing his Mac apps with the proper credit multi. Are the current stock Mac apps up to date, or are they still using the higher multi that they were when released from Beta?

Well, I just checked the Applications page and it's still showing 5.23 as current for the Mac. So I'd have to say the new build for stocker hasn't been pushed out yet based on the anecdotal eveidence.

Alinator

Thanx to Alex for releasing his Mac apps with the proper credit multi. Are the current stock Mac apps up to date, or are they still using the higher multi that they were when released from Beta?

Well, I just checked the Applications page and it's still showing 5.23 as current for the Mac. So I'd have to say the new build for stocker hasn't been pushed out yet based on the anecdotal eveidence.

Alinator

Well, Alex has done his part for the Macs, time now for the project to tidy up the stock Mac app, I guess.
One piece at a time, this will all get sorted.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Well, Alex has done his part for the Macs, time now for the project to tidy up the stock Mac app, I guess.
One piece at a time, this will all get sorted.

Thanks Alex.

who?

After another quick look, it appears that most of the crunching being done by those above me in the top 20 computers are still overclaiming with either the 2.2b Chicken app or the older Alex Kan Mac app.
How 'bout updating, folks?

---

"Time is simply the mechanism that keeps everything from happening all at once."

why dont you contact the users in question and tell them about the changes ?

regards

adream

---

63. (1) (b) "music" includes sounds wholly or predominantly characterised by the emission of a succession of repetitive beats

why dont you contact the users in question and tell them about the changes ?

regards

adream

Because rather than approach them directly, I thought that since most of them more than likely are following this board it would be more polite to ask them as a group to do the update out in the open and in front of everybody instead of trying to try to make a private matter out of it.
I had hoped that their sense of fair play would prevail and they would update voluntarily without a direct request to each one individually.

---

"Time is simply the mechanism that keeps everything from happening all at once."

why dont you contact the users in question and tell them about the changes?

This is really a matter for Eric or the SETI team to do. I hate to whinge, be seen to be whinging, be ignored out of spite and then feel aggrieved...

The validator should ummm well, validate. Any version of app that isn't 5.27 should be ignored and BOINC should be able to mail the owner of the optimised app to upgrade and let them know that their results are now not valid.

I could even update the BOINC code if there's no one else to do it...

why dont you contact the users in question and tell them about the changes?

This is really a matter for Eric or the SETI team to do. I hate to whinge, be seen to be whinging, be ignored out of spite and then feel aggrieved...

The validator should ummm well, validate. Any version of app that isn't 5.27 should be ignored and BOINC should be able to mail the owner of the optimised app to upgrade and let them know that their results are now not valid.

I could even update the BOINC code if there's no one else to do it...

If proposed changes are implimented, this will all be a thing of the past. The credit multi may soon be a part of the WU header info rather than coded into the apps. And there have been several angles proposed to adjust the way the validator awards credits so the underclaims do not reduce a correct claim.
This can all be fixed with reasonable adjustments rather than with a sledge hammer.
I don't want this to seem like it is purely my personal quest to get other users into line with their apps. It is not.
Simon, Alex, and crunch3r have ALL individually asked every user of their optimized apps to update to the current app with the correct credit multiplier so that they are not overclaiming credits. I am simply asking as a fellow Seti participant they everybody does so.

---

"Time is simply the mechanism that keeps everything from happening all at once."

The validator should ummm well, validate. Any version of app that isn't 5.27 should be ignored and BOINC should be able to mail the owner of the optimised app to upgrade and let them know that their results are now not valid.

As long as Solaris, Mac, and Linux/64 is only available as v5.12 or v5.23, you can't ignore pre-v5.27-applications.

Also, it's very easy for users to lie about the version-number.

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

The validator should ummm well, validate. Any version of app that isn't 5.27 should be ignored and BOINC should be able to mail the owner of the optimised app to upgrade and let them know that their results are now not valid.

As long as Solaris, Mac, and Linux/64 is only available as v5.12 or v5.23, you can't ignore pre-v5.27-applications.

Also, it's very easy for users to lie about the version-number.

Agreed, and technically the Validator's job is to check the science, not enforce to rules of the project.

In any event, even though the ideas forwarded lately for enforcing the rules with an eye to making the credit sytem more uniform seems simple in concept and certainly addressed the issues raised recently. However, there are a myriad of difficulties which need to be investigated and overcome to ensure it would be as foolproof as possible without being overly restrictive with regard to the anonymous platform.

I think the idea of the passed with WU multiplier stands a better than even monet chance of making it to the mainstream. It's biggest advantage is it makes it easier for the developers to work up fixes in the application for other problems and get them out the door sooner, as well as allowing adjustments to the rates be made without forcing new builds of the app. This has to be a win-win scenario for all concerned.

Alinator

I've converted.... bump the thread

maybe some day the Mac people will stop over claiming and convert to their new app tooooo...

---

I still have once of my three on 2.2B but it's on the other side of town and I only get there a couple times a month. As soon as I'm over there I'll switch that one out as well to 2.4V.

---

I've converted.... bump the thread

maybe some day the Mac people will stop over claiming and convert to their new app tooooo...

Give 'em a chance.....
Some of them tried to switch to Alex's first revision and found that there were some validation issues with it. Alex posted corrected revisions only yesterday, and a few of the Mac users have already reported that they have switched over and the errors appear to be fixed.

---

"Time is simply the mechanism that keeps everything from happening all at once."

maybe some day the Mac people will stop over claiming and convert to their new app tooooo...

Maybe some day the project will release a Mac app that makes correct claims.

---

i'm one of the mac people that have had trouble with the new apps over the last couple of weeks

the proper working app has only been available for 48 hrs so perhaps a little patience is called for RottenMutt !

roll on the top 10 being macs he heh :-)

regards

adream

---

63. (1) (b) "music" includes sounds wholly or predominantly characterised by the emission of a succession of repetitive beats

I am another person who had problems, I was even mentioned in a few posts.

---