The marathon project does seem to be confirmed as SiDock. it currently has 3 day task deadlines, so there's not much benefit to bunkering anything before May 2nd at 00:00 UTC otherwise the tasks will hit their deadline before it starts. There was some talk of changing the task deadlines, but I'm not sure if it would be increased(probably unlikely) or decreased(seems more likely).So when do I start bunkering ??? And the project is sidock ?
There were no controversies, just your belly aching.
I'll wait with an update of post #1 until there is SG's canonical announcement.Cat's out of the bag.
I am not. They have been functioning this way for apparently much longer than I for one am involved with Distributed Computing. I am not a moderator, but the thread opener, and as such I mention that I am entirely disinterested in dealing with them, even in talking about them.I'm fairly surprised
Ah, interesting. In anticipation of the confirmation, I went ahead and configured another BOINC instance and attached it to SiDock. Ready to go...
While there is no official announcement yet, pschoefer (organizer) made comments in the SiDock message board, the Pentathlon shoutbox, and the SG forum on the fact that the slip of tongue at least won't cause massive pre-bunkering due to SiDock's 3-day reporting deadline.I'll wait with an update of post #1 until there is SG's canonical announcement.
|Thread starter||Similar threads||Forum||Replies||Date|
|BOINC Pentathlon 2022||Distributed Computing||140|
|Limit the number of downloaded tasks for a single BOINC project||Distributed Computing||11|
|S||BOINC: empty gui_rpc_auth.cfg doesn't work anymore||Distributed Computing||3|
|BOINC Games- Live for Alpha Testing||Distributed Computing||22|