We should really begin working together on a BOINC project whitelist membership & monitoring process - BOINC whitelist membership could rapidly change depending on project reliability, security and work availability.
I've compiled a list of all boinc projects from boincstats in order of available work (descending) & have highlighted dead/offline projects:
Note: You'll only be able to comment & view the spreadsheet. In order to start editing it yourself, you'll need to pm me your email address. Make a new gmail account for this sole purpose. I don't want to know your boinc email address!
An overview of all BOINC project's current work statistics: http://boincstats.com/en/page/projectStatusInfo
BOINC forum topic keeping on top of dead/offline BOINC projects: https://boinc.berkeley.edu/dev/forum_thread.php?id=8633&sort_style=&start=280
Projects IMO that should be removed:
We should immediately remove "boinc_projects="http://slinca.com/|slinca@home";" as the url has been hijacked & no longer/never did represent a real boinc project.
IMO, the following projects should be removed from the whitelist purely because they have 0 available work. Perhaps just disable them until they become active again?
RALPH@Home, DistrRTgen, iGEM@home, AlmereGrid Boinc Grid, MindModeling@Home, Najmanovich Research Group, Primaboinca, Rioja Science, SETI@Home Beta, Spatiotemporal Quality of service.
OProject@Home and Beal@Home both appear to be completely offline/the projects are dead, so might want to consider removing them.
SLinCA's website appears to be completely offline - might be a safe option to disable it incase it's currently under attack & malware gets uploaded as work units. Thoughts?
Projects IMO that should be added:
The following projects aren't in the whitelist, but have work:
FiND@Home, Universe@Home, ATLAS@Home, vLHCathome, Citizen Science Grid, TN-Grid, RADIOACTIVE@HOME, YAFU, Climateprediction.net Beta.
Is there any issue with whitespace between the end of the boinc project's URL and the | symbol? Because some have the space, and some don't.
We've got duplicate BOINC whitelist entries in the code:
Several boinc projects appear offline, but the last contact is within the last 6 days (since the new year) - I believe these are just temp issues since there's available work for most of them.
Potential whitelist process improvements:
Within the linked whitelist above, you can see the quantity of work units being worked on & can deduce potentially deduce whether or not it'd be fair to include it as a whitelisted project. If a BOINC project doesn't have enough work units available, then a small pool of users might gain an unfair advantage over others.
Should we have a minimum quantity of work units available before being considered viable as a project?
Should we take into account the BOINC project's current project status for whitelist status? (alpha/beta/production)
Should a BOINC project that has 10x the quantity of work units than another BOINC project have a higher magnitude cap than other whitelisted projects?
How fast can we adapt the BOINC whitelist to decisions made in this thread regarding whitelist status?
We should regularly be scanning every whitelisted BOINC project's work units with virustotal to verify that no malware is being distributed to our users.
Let's use this thread and a similar spreadsheet format for keeping ontop of BOINC project whitelist worthiness. If anyone has any suggestions regarding process improvements for whitelisting projects, please do speak up.
Edited by C.M, 27 January 2015 - 02:13 PM.