+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 15 of 26
  1. #1
    Junior Member
    Join Date
    Jan 1999
    Posts
    9

    Seti@home merger

    I know there is still a little bit of bad blood between AnandTech and Sysopt members in regards to the failed RC5 merger attempt. However, that case was complicated because there were several hundred members on each team. If the 2 Seti@home teams were to merge now it would be very painless, as there are only 90 members between the two teams. This would be beneficial to both teams presently(it would nearly double their output), but would be absolutely huge once more people switch from RC5 to Seti@home. I believe that now would be the absolute best time to do it. I'm going to post this at AnandTech as well and get their reactions. Let me know what you all think.

  2. #2
    Joel Kleppinger
    Guest
    Personally, I am all for a merger if all you SETI@Home guys want to. Since, I only do RC5, this won't really affect me anyway.

    However, let us know what you want to do, and we'll do it. I'm not positive how amok has thought to do it, but perhaps a new team would be the most fair. However, this means both teams lose all their current units sent to either team. (at least if it's anything like RC5).

    Anyway, let us know, and we'll try to work something out. If you have any ideas about this, be sure and tell us.

    Thanks,

    Joel

  3. #3
    Junior Member
    Join Date
    Jan 1999
    Posts
    9
    A new team would definitely be the most fair. And yes, we would lose our work units up to this point, but we've not really accumulated a lot of work units anyway. A combined effort would be much better than both teams working alone, and now is the time to do it with only 90 members between the 2 teams.

  4. #4
    Junior Member
    Join Date
    Feb 1999
    Posts
    12
    ---
    X Posted on:
    www.anandtech.net/bbs/Forum13/HTML/001166.html

    www.sysopt.com/forum/Forum7/HTML/000080.html
    ----

    I think the merger is a good idea!
    The RC5 merge was a good idea too but I think we tried it the wrong way.

    All I need to assign 2 of CrackRacks nodes to S@H is a howto for the S@H client under linux connecting via a http proxy server.

    cu

    The Magicman

    Team AnandTech RC5
    Team Anandtech Seti@Home (Inactive)

  5. #5
    Joel Kleppinger
    Guest
    Well, initial response on both boards appears to be unanimous. I suppose we should come up with a name. Suggestions?

    If we don't lose any units, then now is definitely the time. I'm certain that if we didn't lose blocks in rc5, a merger could still happen. But I'm not giving up more than a million blocks anytime soon.

    Joel

  6. #6
    Mod w/ an attitude Sterling_Aug's Avatar
    Join Date
    Jun 1999
    Location
    Schuylkill Haven, PA 1797
    Posts
    12,786
    Joel: If RC5 allows retirement of an e-mail account, then wouldn't they allow the retirement of a team? Seems like they should to me. All I did to change my e-mail was to set the machines to the new address, run 1 day to accumalate blocks, then retire the old address and ALL blocks went to the new address and team association.

  7. #7
    Joel Kleppinger
    Guest
    Because Distributed.net has made it officially clear that they do not want teams merging together, throwing all previous blocks that both teams did to a new team.

    That is different from retiring emails because when you retire an email, you're just keeping rc5 up with your latest email (which is bound to change). They do that to lessen fragmentation for a person, that way they don't have like 3 or 4 emails that have cracked blocks.


    Joel

  8. #8
    Junior Member
    Join Date
    Jun 1999
    Location
    Chicago,Ill,USA
    Posts
    20
    This may seem a little premature but,
    these names arent taken:

    Pheonix
    Team Pheonix
    The Pheonix Group

    BTW,

    Valhallas Forge
    [This just popped into my head]
    [Strike a little fear into the opposition?
    Doh!]

    Isnt taken either.

    I dont mean to be some kind of boss, but,
    lets get going and make a move.

    And they dont sound like "Lamb Chop"!

    I'll cross post this.

  9. #9
    Junior Member
    Join Date
    Jun 1999
    Location
    Chicago,Ill,USA
    Posts
    20
    The Seti@Home guys are to fast!

    As of right now,

    If you join another team, your old work
    units stay with the old team.

    You have to start over.



    I just dashed off an E-Mail to Seti@Home
    about an option to allow the combining
    of teams.

    Or to at least leave it as it was.




    [This message has been edited by MGallik (edited 06-21-99).]

  10. #10
    SysOpt
    Guest
    I don't think that's accurate. I accidently created our team in the wrong category, and joined it. I had a few work units there. Then, I created a new team in the proper category and joined it instead - the units transferred.

    Scott

  11. #11
    Junior Member
    Join Date
    Jun 1999
    Location
    Chicago,Ill,USA
    Posts
    20
    I hope your right.

    But you had better look at this.

    It's new.

    http://setiathome.ssl.berkeley.edu/c..._form&id=10843




    [This message has been edited by MGallik (edited 06-21-99).]

  12. #12
    SysOpt
    Guest
    hmmm.. Interesting.. Maybe mine transferred only because I was the one creating the team. Argh... If the units don't transfer, we'll be back to the argument of "who joins who", on top of what to name the joint team.

  13. #13
    Junior Member
    Join Date
    Jun 1999
    Location
    Chicago,Ill,USA
    Posts
    20
    Maybe a form letter so all of us, as individuals, can ***** to Set@Home.

    I'm getting burned out, I've been running
    around like a mad man at this all day.

    No. I'm at home, no pay.

    Our #4 guy bailed yesterday and took all
    his Work Units with.

    It's funny how we keep getting screwed.

    I feel like I'm running up hill and someone
    keeps throwing barrels in front of me.

    Hmmmm.....

    Didnt I see that in a game somewhere?

    [This message has been edited by MGallik (edited 06-21-99).]

  14. #14
    Junior Member
    Join Date
    Jan 1999
    Posts
    9
    We can avoid the whole who joins who argument by simply creating a new team. At worst we'll lose a few work_units, but this isn't a short term project, and the benefits of joining now would more than exceed the benefits of keeping the 400-700 WUs each team has done so far. I believe most of us want this merger, so why don't we start thinking up and voting on a few names ?

  15. #15
    Junior Member
    Join Date
    Jun 1999
    Location
    Chicago,Ill,USA
    Posts
    20
    I already put my 2 cents in for a name up
    above.

    I really like:

    Valhallas Forge




    Here's another thread to look at, member 3?

    http://www.arstechnica.com/forum/ubb...ML/000669.html


    [This message has been edited by MGallik (edited 06-21-99).]

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts







New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke