• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Boycott @ Predictor @ Home

RobertE

Senior member
You may or may not have read the threads on the various Bonic boards about a supposed trojan install.

Well it looks like things have reached critical mass over at Predictor.

Linky

Personally, I'm glad I detached some time ago. Only regret is that I attached at all. 🙁

If you crunch for P@H, take a moment and look at what is going on. Judge for yourself. I will not be back to P@H ever.
 
Afraid I've never heard of the project😱
What is it?

And what's the short version of the story? (I haven't got time to read all that)
 
Similar goals to Rosetta just a different approach.

Cliffs (sorta) [cut-n-paste from other posts]:

-Team Italy found out about a trojan BOINC installer when an Italian victim contacted them

-Team Italy members contacted Dr David Anderson at boinc

-Team Italy or boinc identified Wate's account

-Dr Anderson (or another member of the boinc team) contacted and informed managers of the affected projects. (PAH perhaps didn't receive this notification, for whatever reason)

- CPDN-admins did some research and connected the account of Wate to this installer, they proved this fact, (though not necessarily the culpability of the user Wate personally)

- They acted on this issue by closing the account and making it impossible for the hijacked machines to recieve new work.

- They as well zeroed the credits of the account with the hijacked machines attached to, i.e. Wates account

- They informed the other projects via fora - Other users spread the news to other projects fora.

The other projects admins acted on behalf of the trojan and relieved the hijacked machines from their unwanted burden. It's irrelevant whether Wate himself or somebody misusing the name Wate hijacked the machines, it's illegal to hijack machines. So they had to be disconnected from the project, and in BOINC this is afaik only possible for the whole account from the projects perspective.

Here nothing happened on behalf of the hijacking. The infected machines were not cut off, the alleged hijacker was crunching undisturbed on pole position in the RAC, and as the other crunchers demanded an explanation for this they were told to shut up.

When they still insisted on a further discussion of this issue, their posts were deleted, they were banned. After they still refused to be gagged, they were told to be an angry mob, to ah heck off to other projects, and not to disturb this fine, quiet, sleeping project with the harsh reality any longer.

If the real person behind the account Wate is really innocent, s/he will probably be very pleased to be disconnected from the criminal trojan programmer, at least I would be. If my account would be misused in the way you still think is possible for W***, I would want all credits wiped out, get another password, account key, user name, just to get every connection between this hijacking and my name wiped out

 
I deleted what I forst posted here. Didn't really think it through. If you read the post of Lee at the very bottom of the link, he's got a point there. Honestly, I don't know enough about all that's been going on, so I'll just keep my mouth shut.

Sorry. 🙁
 
There was another post about this about a month ago, with a brief desription of what was going on.
Text

It's too bad the admins at Predictor don't bother to delete his account when they know what's going on. Apparently other projects have. This is the kind of PR that DC does not need 🙁

Wonder why so many people downloaded Windows Updates from a non-MS site 😕
 
I used to crunch for them, but about 2 years ago they kept on having a problem where you'd have to re-register ALL the machines under your account. When this happened a second time Rosetta was just starting up so I switched to that and haven't looked back.
 
Predictor@Home is a project that to me has always been pretty unresponsive to the users. When you couple that with the results they have in the CASP trials versus the results Rosetta has it makes it extremely difficult for me to recommend the project to anyone. Rosetta has better results and a very responsive admin team. This incident has unfortunately added to a long list of things wrong with Predictor.
 
Back
Top