New Team Creation Requirement (1 Credit Awarded)
We have noticed an uptick in spam teams being created by users with 0 credits crunched. These teams are often advertising sketchy services and are not created in the spirit of working together to help crunch workunits or build a community. In an effort to combat this, we recently implemented a newer version of reCaptcha during account creation to reduce abuse of the team system by spammers and bots.
This new reCaptcha seems to have helped, but not enough. Effective immediately, we are requiring any new team owners crunch 1 credit to before creating team. In reality, this will not be an issue for anyone signing up for the project to actually contribute to the community. It will however make it vastly more difficult for bot accounts to create teams.
If you have any suggestions for helping us reduce abuse of our website and the team system, please let me know below and we can discuss.
Thank you all for your continued support.
13 Dec 2017, 21:55:34 UTC
Repealing Net Neutrality Could Affect MilkyWay@home
On December 14th, 2017, the Federal Communications Commission (FCC) plans to take a vote to remove the Title II classification of Internet Service Providers (ISPs). In effect, this will remove the FCC's authority to enforce the doctrine known as net neutrality. Net neutrality is the idea that all traffic on the Internet, regardless of its origin, should be treated equally. This doctrine is responsible for the massive success of the Internet today. It allows any company, institutions, and individuals to host their own websites and web services without the fear of having their web-traffic throttled to accommodate another company, institute or individual who has more money to pay for their traffic to be prioritized. It also prevents ISPs from throttling or being paid to throttle websites for any reason, such as, political, or ideological reasons.
Why is this important for MilkyWay@home? As a research group that survives off of donations from our wonderful volunteers and government grants, we do not have the means to pay for things like paid prioritization, or any other potential ransoms that ISPs may decide to charge in the future to transmit data. This could lead to a decrease in our workunit availability and overall reduction to our abilities to make discoveries. The repeal of net neutrality can also lead to new fees for our volunteers. For example, ISPs will be allowed to sell access to certain websites as part of "bundled" packages. This means to receive workunits from us or any other BOINC project, or visit our websites, you will have to buy into a "bundle" that includes our or other BOINC websites. In our minds, this is not a partisan issue as there is overwhelming support for net neutrality from both parties, (76% of Americans, 81% of Democrats and 73% of Republicans). 
If you live in the United States and would like to help protect net neutrality, the best thing you can do is contact your congressmen and senators to let them know how you feel about net neutrality, why it is important to you, and why they risk your vote in future elections if they do nothing to protect it. Additionally, if you would like to help fund larger efforts to prevent the repeal of net neutrality or if you live outside of the United States and would still like to help, consider donating the Electronic Frontier Foundation or the American Civil Liberties Union to allow them to cover the costs of the looming legal battle.
Thank you all for your continued support and I hope for everyone's sake network neutrality can be saved.
The MilkyWay@home Staff
7 Dec 2017, 19:22:08 UTC
New Badges for Membership Time
I am updating the badges for membership time. These new badges will be available for our very special 9 and 10 year members. The new badges are the iridium tier badges shown below.
Thank you all for your support, especially those who are about to earn this new prestigious badge. These people have been with the project from the beginning and we really appreciate their support.
6 Dec 2017, 18:56:57 UTC
Quick Server Update
I am going to be doing a quick server update. Shouldn't take longer than a few minutes. There will also be a whole new set of separation runs put up after the update. If you notice any problems with the runs, please post them here.
6 Dec 2017, 18:20:16 UTC
I noticed some database instability this weekend. I'm going to update some server applications to try to fix this. If you notice any issues over the next couple days, let me know.
27 Nov 2017, 19:53:36 UTC
New Runs 11/21
I just put up some new runs. Let me know if you see any issues.
21 Nov 2017, 22:45:55 UTC
Issues With Work Generation
Just noticed some issues with the work unit generator. Working on it.
Was a quick fix. I'll keep an eye on things for the rest of the night.
1 Nov 2017, 19:39:57 UTC
Update on This Weeks Errors
I just wanted to give you all a quick and more technical update on what we have been dealing with over the last week.
Our project has been running for upwards of 10 years now and we have been crunching literally billions of workunits over those years. As a result of all of your hard work and dedication, we have actually calculated enough results that we have run out of room to store the IDs of all of these results in a normal unsigned integer value (the default data type used for storing IDs in BOINC databases). As a result, on Tuesday night, I updated our database to be able to store IDs in a much larger data type to prevent this issue from happening again during the remaining life of the project. As a result, I also had to quickly patch the BOINC code we run on the server to allow it to use this newly available data type in the database.
During this process, I missed one of the foreign keys that refers to the results, specifically in the validation process. This led to an issue in validation of work units over the last couple days. I had trouble diagnosing this issue because before the workunit queue clear, everything was running fine however, after the workunit queue clear, when new work with large IDs was being returned, it silently failed to validate workunits.
I have implemented a fix for this last issue and my hope is that things will be smooth sailing from here on with regards to this issue. Of course, there is always the possibility I missed another bug in this pipeline, or I might realize I need to force validation on workunits received over the last couple days. In any case, I will be watching the server pretty closely over the next couple days to make sure its running correctly.
Sorry for all of the trouble over the last couple days and I hope you all continue to support the important research we are doing into the future.
21 Oct 2017, 18:11:25 UTC
Workunits Not Validating
I see a lot of workunits aren't validating. I think I know why. I'm going to take the server down for an hour or two while I try to fix it.
Sorry, for all of the trouble recently.
I implemented a fix. I will monitor it for the rest of the weekend.
21 Oct 2017, 15:42:26 UTC
Clearing the Queue
We will have to clear the workunit queue for both separation and nbody. This will cause many invalid workunits. We apologize for this, as this is the only way to clear the system for it to return to normal operation.
Thanks for your continued support,
Jake and Sidd
18 Oct 2017, 19:21:21 UTC
News is available as an RSS feed