Slashdot Mirror

← Back to Stories (view on slashdot.org)

SETI@home Becomes Part of BOINC

Posted by ScuttleMonkey on from the hard-to-choose dept.

Sudoku writes "On December 15th the Seti@home project will stop issuing new work to members and integrate with BOINC, the Berkeley Open Infrastructure for Network Computing. Once members have moved over to the BOINC client they can divide their computing time between such projects as climate prediction, search for gravitational signals emitted by pulsars and yes, you can still look for the aliens."

4 of 184 comments (clear)

  1. Foldit by gcnaddict · · Score: 5, Insightful

    I still think we're better off folding@home than hunting afar

    --
    Viable Slashdot alternatives: https://pipedot.org/ and http://soylentnews.org/
  2. Article inaccurately titled. by justinarthur · · Score: 5, Informative

    SETI@Home joined the BOINC project long ago, at least a year ago. There has also been an account migration service since the beginning of the BOINC integration. The only news here is that they are discontinuing support for the old SETI@Home client.

  3. Re:Lose members by Eddy+Da+KillaBee · · Score: 5, Funny

    Scientific Progress Goes BOINC?

  4. Re:BOINC blows by Eravnrekaree · · Score: 5, Informative

    I thought the BOINC client was a useability disaster when I tried it. It had numerous technical problems and was very unintiutive. While some may say that people should how to work with its unnecessarily involved configuration, I think this is is an arrogant assumption, especially for people who are DONATING their computers resources, if it isnt easy to install and provide some good graphics to show what it is doing, people will not bother and will give up, and the project will use a lot of users. The reason seti@home was such a success, was due to the fact it didnt require much user configuration to run (but was still configurable) and provide a nice graphics display to show that it was doing something. With BOINC the graphics display seemed to be difficult to access, and the whole thing seemed to involve a lot of configuration to use. I think the seti@home project will lose a large number of users from this.