tag:blogger.com,1999:blog-37798047.post8511810170406335870..comments2024-01-16T05:48:33.523-05:00Comments on Errata Security: BitTorrent curiousitiesDavid Maynorhttp://www.blogger.com/profile/09921229607193067441noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-37798047.post-54339496322714598372007-02-10T20:29:00.000-05:002007-02-10T20:29:00.000-05:00There are groups out there that intentionally pois...There are groups out there that intentionally poison downloads. I believe they eventually get voted off the island in most torrent systems.<BR/><BR/>There was a better hashing arrangement, merkel hashes. Bram never implemented it though, and tended to squash any discussion by others.Ryan Russellhttps://www.blogger.com/profile/13265663681454609204noreply@blogger.comtag:blogger.com,1999:blog-37798047.post-77125330563836969772007-02-10T08:46:00.000-05:002007-02-10T08:46:00.000-05:00You said "For example, a client could compare the ...You said "<B>For example, a client could compare the bad chunk with the eventual re-download of a good chunk. It could run tests on the regions of the pieces that differ.</B>". What should it do, then? <BR/><BR/>Tell the user? Does she care? Would she take the time to understand the problem and do something about it (if she could and cared)? Don't think so.<BR/><BR/>There may be some small gains in trying to catch those errors. But in times where bandwith is cheap, why not just download the same chunk from somewhere else and ignore the one machine sending out bad data.<BR/><BR/>A better idea might be to report stations which send bad chunks to a central authority: "<I>That guy is sharing some music files, but he sends it corrupted so there is no copyright violation. No need to call the cops on him</I>".<BR/><BR/>I guess some users would like to switch on some feature like that. ;-)a.https://www.blogger.com/profile/08927986504610741040noreply@blogger.com