The Theory of Leech Computing
Phil Frisbie, Jr. writes "I am defining Leech Computing as 'a program running on a client computer without user knowledge that can process data and report back the results, but otherwise does not effect the usability of the client computer and makes no changes to the client'. Leech Computing, Part 1 covers basic theory."
Spyware seems to fit this definition as a less-appreciated form of leech computing.
I'm not afraid of falling, it's the sudden stop at the end that frightens me.
There's also a good page quickly discussing Villain-to-Victim computing. The point is to use correctly configured machines to do things they were not intended to.
Not true. If you give the task a very low priority, it will only use cycles that are truly "spare" on most modern multitaking OSes.
When the user does anything interactive, the task will just get shoved to the back of the queue and won't get any cycles until the user had finished whatever they are doing. The user won't notice a thing.
It wouldn't have to be a button, just about any event on the page can be made to execute a javascript function: page load, page exit, link clicks, entrance/exit of form fields, mouseovers of various sorts...
The user might never realize the event had occurred.
I don't need /. readers to write part 2 for me....I am already working on the CGI program and JavaScript for the demos.