News for hackers. Stuff that matters.
Re:Seeding torrents from S3 by mikeash on Tuesday May 06, 2014 @01:38PM (#7705936)
Providing an extra seed seems useful too. You can do the initial seed from somewhere faster, but S3 will provide a backstop in case that seed goes down. It might be too slow for the full download, but it can help fill in the last little pieces in case you get into a situation where everybody in the swarm has 99% of the file but nobody has some particular chunks.
Re:Seeding torrents from S3 by toomuchtodo on Tuesday May 06, 2014 @01:41PM (#7705953)
CORRECTION: It was pointed out by /u/teraflop that the Bittorrent functionality and Requestor Pays functionality are incompatible on the same bucket.

Indeed. S3 also has the ability to have the requestor pay for the bandwidth costs of a object retrieval. You could, for example, get the object free from the swarm, and pay for the last few MB/GB if it was unavailable from anyone else.

http://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPays...

http://docs.aws.amazon.com/AmazonDevPay/latest/DevPayDevelop...

Re:Seeding torrents from S3 by teraflop on Tuesday May 06, 2014 @01:45PM (#7705979)
"Requester Pays buckets do not support the following. [...] BitTorrent"
Re:Seeding torrents from S3 by toomuchtodo on Tuesday May 06, 2014 @01:48PM (#7706000)
Corrected and cited. Thanks.
Re:Seeding torrents from S3 by mikeash on Tuesday May 06, 2014 @01:58PM (#7706054)
I didn't know about the requestor pays functionality, so it's good to know that even if it doesn't apply here.
Re:Seeding torrents from S3 by fat0wl on Tuesday May 06, 2014 @05:07PM (#7707096)
Yah exactly -- you can seed the file yourself but just have this as a backup in case your PC/laptop/whatever is turned off. Slower, but at least its there. Once it is seeded beyond a couple initial users it's a moot point anyway.

Doubt that AWS is trying super hard to get into the torrent sphere, its just +1 cool thing they support.