Hubzilla/WebTorrent/server: Difference between revisions
from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
< Hubzilla | WebTorrent
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Hubzilla]] extensions for serving [[../|WebTorrents]] include: | [[Hubzilla]] extensions for serving [[../|WebTorrents]] include: | ||
* BitTorrent Server: [https://github.com/roere/bittorrentserver/tree/master GitHub] v0.2 alpha, as of 2017-09-08 | * '''BitTorrent Server''': [https://github.com/roere/bittorrentserver/tree/master GitHub] v0.2 alpha, as of 2017-09-08 | ||
** Although labeled as a "BitTorrent" server, the GitHub documentation states that "The idea behind this plugin was to use Webtorrents in Hubzilla. Libtorrent does not support Webtorrent yet, also it is planned since quite some time: https://github.com/arvidn/libtorrent/issues/223" | ** Although labeled only as a "BitTorrent" server, the GitHub documentation states that "The idea behind this plugin was to use Webtorrents in Hubzilla. Libtorrent does not support Webtorrent yet, also it is planned since quite some time: https://github.com/arvidn/libtorrent/issues/223" | ||
So the serving of WT may be the bottleneck. (Surely the [[WebTorrent]] software itself can be adapted somehow?) | So the serving of WT may be the bottleneck. (Surely the [[WebTorrent]] software itself can be adapted somehow?) | ||
Latest revision as of 08:33, 9 September 2017
Hubzilla extensions for serving WebTorrents include:
- BitTorrent Server: GitHub v0.2 alpha, as of 2017-09-08
- Although labeled only as a "BitTorrent" server, the GitHub documentation states that "The idea behind this plugin was to use Webtorrents in Hubzilla. Libtorrent does not support Webtorrent yet, also it is planned since quite some time: https://github.com/arvidn/libtorrent/issues/223"
So the serving of WT may be the bottleneck. (Surely the WebTorrent software itself can be adapted somehow?)
