-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Headless seeding #122
Comments
Yes, peers in web browser share data throught WebRTC, so it is not compatible with classic TCP/UDP peers (like Transmission). If you want to seed from CLI, maybe you could try webtorrent-hybrid. But it is pretty heavy (creates a hidden Electron process) so it's not ideal. I've created an issue for your use case: #123 |
Awesome, a heavy solution is better than no solution. Thanks for the links and the new issue. |
Just leaving a pointer to the WebTorrent issue tracking WebRTC support in popular/classic torrent clients: webtorrent/webtorrent#369 |
Yes, I think this great feature is under-documented, at least it was not obvious for me: You can use the "Download" option, select "Torrent" and then open the torrent file in WebTorrent Desktop (https://webtorrent.io/desktop; or presumably any other WebTorrent-compatible client from the link above). This isn't exactly "headless", but it is much better than seeding via the browser. Most importantly, you don't have to re-download the video every time you close the client and open it again. And it works pretty well, I am using it right now to help seed Datagueule's new movie and I've already uploaded a couple of GBs... |
Am comeing back to the subjects of seedboxs after being off doing other stuff for a year. Q. is the a working webRTC DIY seedbox sultion, read threw lots of threds and could not find anything concreat. |
I've decided to revive this issue since this one #2958 got closed. The fact that we can now use regular clients to seed is a huge news https://feross.org/libtorrent-webtorrent and we should do something about it, no? |
will seedbox work now for peertube for holding the core video off the main server and in a distributed home seedboxs? |
Why has this been closed if it's not really possible? |
@Chocobozzz could you please reopen the issue as it hasn't been solved yet? |
No sorry:
|
That list contains zero working solutions. Also this sentence from the second link:
"We're the only use-case where WebTorrent would really shine but we're not waiting for any implementations" Really premature and tautological really. |
There are: https://webtorrent.io/desktop/ or https://wiki.vuze.com/w/WebTorrent or https://github.com/webtorrent/webtorrent-hybrid |
So there's only Vuze, which is approximately a quarter of the marketshare. It really takes more than that, especially if we look at seedboxes. |
Wait a little bit longer. Meanwhile some popular open-source clients are working on updating to use You might find other clients with Alternatively, there is a Go based torrent lib implementation, it has WebTorrent support and there are some clients built on top of that. It doesn't seem as full featured as Personally I think once the bigger open-source clients are able to provide hybrid support, WebTorrent will be a much more attractive option. That said, the linked admin docs explains very well the benefits of HLS for video content playback. I'm not too familiar with the related p2p media solution to compliment it, but I assume that helps about as much as, if not better than WebTorrent presently does. |
This might just be a documentation request : is there a way to add a seed server without having to open a browser with a tab on each video ?
On a local setup, I have three browsers open, the number of peers is correct at 3. When I use the download link, it opens a torrent file in Transmission, it shows only one peer (the web server), I guess that the file can't be served from the browser peers. The number of peers in the browsers doesn't go up one number when the transmission "traditional" torrent is seeding.
I guess these are different channels and the bandwidth can't be shared. If this is the case, do you know of any hack where one could have headless browsers on a headless server that open the videos URL to serve the content from multiple locations without a user in front of it ?
The text was updated successfully, but these errors were encountered: