You're looking at Less Wrong's discussion board. This includes all posts, including those that haven't been promoted to the front page yet. For more information, see About Less Wrong.

CellBioGuy comments on Crazy Ideas Thread, Aug. 2015 - Less Wrong Discussion

7 Post author: polymathwannabe 11 August 2015 01:24PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (240)

You are viewing a single comment's thread. Show more comments above.

Comment author: Sherincall 12 August 2015 10:48:29AM 7 points [-]

A botnet startup. People sign up for the service, and install an open source program on their computer. The program can:

  • Use their CPU cycles to perform arbitrary calculations.
  • Use their network bandwidth to relay arbitrary data.
  • Let the user add restrictions on when/how much it can do the above.

For every quantum of data transferred / calculated, the user earns a token. These tokens can then be used to buy bandwidth/cycles of other users on the network. You can also buy tokens for real money (including crypto-currency).

Any job that you choose to execute on the other users machines has to be somehow verified safe for those users (maybe the users have to be able to see the source before accepting, maybe the company has to authorize it, etc). The company also offers a package of common tasks you can use, such as DDoS, Tor/VPN relays, seedboxes, cryptocurrency mining and bruteforcing hashes/encryption/etc.

Comment author: gwern 15 August 2015 07:45:20PM *  5 points [-]

It's been done, or at least, tried for legal services: http://www.cpusage.com/ http://www.gomezpeerzone.com/ http://zennet.sc/ https://pluraprocessing.wordpress.com/ and there were some older ones which I can't seem to refind at the moment. (Naturally, the illegal ones are fairly successful in being sold for DDoS and spamming and theft purposes.)

My best guess at the failure is that relying on consumer hardware is too high latency, too failure prone, hard to guarantee any sort of security or confidentiality, high overhead in finding and negotiating with and supporting all the ordinary people running your cloud software, and not particularly cost-effective since consumer hardware may be energy-inefficient and long out of date, especially compared to cloud companies like Amazon EC2 where they build custom hardware to get more efficiencies of scale.

(Note to other commentators: Ethereum isn't what he is proposing because it is incredibly inefficient compared to a regular distributed computing project, for mostly good reasons related to its goals and threat model.)