Feature: torrent creation

[feross]

I have no immediate plans to implement this, but adding an issue here for when I get around to it.

• Use piece size recommendations from here: http://wiki.depthstrike.com/index.php/EAD:Utilities:TorrentBuild

[transitive-bullshit]

I'd like to help with this, but where should it reside and look like?

Here's one possibility:

/**
 * Creates a new torrent from the local file or directory pointed to by `path`.
 * @returns Buffer containing torrent contents
 * @param {string} path  filesystem path to file or directory containing files for torrent
 * @param {Object} opts  optional creation params
 * @param {Array<string>} opts.announce   tracker urls to add to the torrent
 * @param {string} opts.comment           user-defined comment to add to torrent
 * @param {Boolean} opts.private          whether or not to create a private torrent (defaults to false)
 */
Client.prototype.createTorrent = function (path, opts) {
   ...
}

We'll need to have the ability to add Torrents to a Client that are backed by existing data to have more solid offline tests and to support seeding without downloading and seeding partially downloaded torrents. This is definitely related to torrent creation, but I'm not sure how all the pieces should fit together here.

[feross]

Last night, I published create-torrent, a module for creating torrents. I think it belongs inside webtorrent.app, similar to how apps like transmission have torrent creation functionality.

Moving this to https://github.com/feross/webtorrent.app/issues/19