I think this is an innovative approach to getting more people involved with grid computing for major computations and a clever way to market it in general. However, I agree with some other people here, there has got to be some sort of licensing issue. As much as the whole "you clicked okay to the TOS, you gave us permission." is a tank in court, it still seems to risky. If nothing else, it would risk users no longer using the games from the providers using that service if they found out that their computer slowed down at all during playing that game because it was doing things it wasn't supposed to. Not that I would likely have a problem with it, but lets face it...the general public is slap happy with lawsuits.
Also privacy issues in the entire concept. I didn't notice any (note: I didn't go out of my way to find one either) way for the end users to directly go and see exactly what kind of materials were being processed and what data, if any, was being collected from the user's machine. That might also be a source of trouble in the long run.
Interesting comments. First, let me explain that the client side runs entirely within memory; the hard drive is not touched at all. All processing or computation is done within the Java sandbox. In other words, you are not giving us unfettered access. In fact, it's quite the opposite. :) We follow everything listed at http://java.sun.com/sfaq/, whether we're running an applet from the browser or from within a desktop application.
Second, although we encourage disclosure, we leave the disclosure up to the individual sites and some have chosen to use some form of opt-out or opt-in. That being said, we also provide a TOS that they can use for disclosure if they choose. If the disclosure is done in a positive way, the users should see the benefits of getting more game features for free.
Nice rebuttal, I wish you the best of luck, it seems like something with a good amount of potential. I especially liked your perspective on because the gaming services do this and you pay them for it, they can implement better features for their own users.
Also privacy issues in the entire concept. I didn't notice any (note: I didn't go out of my way to find one either) way for the end users to directly go and see exactly what kind of materials were being processed and what data, if any, was being collected from the user's machine. That might also be a source of trouble in the long run.