Plura has a java applet which you can embed into a webpage that gets viewed for a long duration, such as a game or a streaming video.
Affiliates embed an iframe which loads their applet as the user plays their game. The user's CPU goes up a bit, and they can help generate revenue for the game makers.
They're targeting desktop apps. The Java app downloads the pages, so it needs high permissions, so you get the default Java unfriendly popup asking you for confirmation.
Plura supports desktop and web-based games.
If the game is hosted on a website, like a Flash game, the
developer only needs to include 1 line of iframe code. We
will soon be releasing a Javascript API for dynamically
controlling how this iframe is loaded, giving the developer
control over starting, stopping, and controlling CPU usage
in Plura. The iframe loads a Java web applet, which runs
completely in memory. This applet is forcibly restricted
from accessing the user's computer by the sandbox model
provided by Sun.
So far as I understand, they have multiple models.
One affiliate model is "Plura for Java Applets", where-as another is "Signed Java Applets"
I imagine there may be fewer options for unsigned applets, leaving the developer with less potential revenue every month, where as desktop application developers and signed java applications are left with the providers who don't need signed applications.
That said, I agree the Java dialog is ugly and scary ;(
If I were an Affiliate, I'd want to avoid it. It breaks the user-experience of your site into some gaudy and jarring, not to mention unbranded and unrelated to the information the user is after.