Grad Student Project Uses Wikis To Stash Data, Miffs Admins
Anonymous writes "Two graduate students at the Ivy League's Brown University built a P2P system to use abandoned wiki sites to store data. The students were stealing bandwidth from open MediaWiki sites to send data between users as an alternative to BitTorrent. There was immediate backlash as site operators quickly complained to the University. The project appears to be shutdown, but many of the pages still remain on the web. The project homepage was also taken down and the students posted an apology this afternoon." The same submitter links to two different forum discussions on the project.
The students were stealing bandwidth from open MediaWiki sites
The fact that some "admin" abandoned a site, with open privileges to post on it, does not constitute theft. I manage servers and write code for a living, and while I'd put a stop to such practices on any site I managed, the use of the term "theft" is laughable.
This is very much reminiscent of Microsoft crying to the media that all their security problems were due to evil hackers, and not their abject failure to follow long-accepted industry practices for code reviews and architecture. My response: cry me a river, and congrats to the grad students for their innovative work in the field of distributed communications.
512 MB RAM, 20 GB disk, 200 GB transfer, five datacenters. $19.95/month.
I did some research into this a number of years ago (before torrents were around). I found that you can store 64 KB (if I recall correctly) in a slashdot comment. Now, the idea was not to to use slashdot as storage, they'd quickly put a stop to that. The trick is using slashdot and other forums and wikis as a way to get your data into the Google cache, where it will be served rapidly for everyone who wants it. There should also be forward correction data uploaded (like parity files) so that if some segments get lost, they can be recovered. Then what you need is an index file (kind of like a torrent file) that tells you what Google keywords you need to search for to find any given segment of the file, and software that will parse this file, download, and assemble the chunks into the completed data.
I wrote a little bit of code for it. It's all very straightforward, I just never got the time to get enough of it implemented to release anything. With torrents, it seems somewhat worthless to pursue now.