I don't know how big a problem that would be, but it is something to consider. If I understand correctly, the scheme under discussion here would require these users to update BOINC (or at least the project app) themselves, unless they have their device set to get updates automatically. And I suspect there is a significant percentage of users who rarely update their apps. My understanding is that this problem did not show up during beta testing on / many users set their device to not download and install updates automatically (I am one of them, as I don't want updates happening at inopportune times). BOINC then automatically downloads the new needed to update their new app because after deployment they found that their app crashed only on Macs with a certain configuration, and it took some experimentation to determine the cause. When a project distributes an app and only then finds it has a critical flaw (for example, one that crashes the app, returns bad results or even worse, crashes BOINC), they can change their tasks to require the updated app. > (the beta project of has released 3 different version of app during the last week Given the fact that the server status page says the download server is down Id. Per-project apps? Is there a way to have them communicate among each Has anyone ever evaluated the possibility of having independent To potentially avoid this issue I'm curious to know what kind ofĪlternatives have been discussed and rejected in the background of In fact mean that BOINC has to accept responsibility, doesn't it? I doubt that the Android/iOS policiesĪllow execution of 3rd party code (downloaded or integrated) which would Sign-off the apps included (and updated)? That's political, proceduralĪnd even legal challenge as BOINC is responsible what it does, as a ![]() I think the goal needs to be *automated* weeklyĪpart from that: has anyone yet thought about how to integrate and > projects to submit their apps or app versions. > Client (bundle) then, say, every quarter, with reasonable deadlines for > I suggest we should plan for a fixed update cycle of the official BOINC It was one of the first volunteer computing projects, and not designed with a high level of security. The original SETI client was a non-BOINC software exclusively for SETIhome. History BOINC was originally developed to manage the SETIhome project. On 06.04.20 10:50, Bernd Machenschalk wrote: BOINC is free software released under the terms of the GNU Lesser General Public License (LGPL).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |