-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
WebTorrent support #4163
Comments
It'd be nice to have webtorrent support, but, uh..
So, in other words, it'd be a monkeypatch from hell... |
You guys should follow this issue instead: arvidn/libtorrent#223. It's the backend qBittorrent is using. |
Good idea! Will push my +1 there. :) |
Closing since this needs implementing from libtorrent. |
Fair enough; will hope Libtorrent picks this up. |
这个不是早支持了嘛 |
Let’s track arvidn/libtorrent#223 |
PR is merged! |
Note that the PR has been merged to the It will be a while until those last 2 conditions are met. In the meantime, this can be left open, but I'll lock it preemptively to prevent spam until there are new developments |
Hey folks,
I use qBittorrent and love it. Thanks! :)
I'd love to see WebTorrent peers supported by qBittorrent. If you're unfamiliar, see the site; it's a very exciting development and one which could hugely influence the future of bittorrent overall.
The big problem right now is that WebTorrent peers can only communicate with other WebTorrent peers, so they are cut off from global swarms. That's because browsers can't do regular UDP/uTP bittorrent, essentially. There is a hybrid peer that can bridge between webtorrent swarms and regular bittorrent swarms, but ideally WebRTC-using peers would become part of the global swarm for all torrents, by implementing WebRTC in libtorrent and other bittorrent clients.
Could qBittorrent be the first mainstream client to do so? :)
Thanks!
There is a $15 open bounty on this issue. Add to the bounty at Bountysource.
DISCLAIMER: There are trustworthiness and solvency issues with BountySource. qBittorrent is not affiliated with them. Use them at your own risk.
The text was updated successfully, but these errors were encountered: