Skip to content
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

Open
ghost opened this issue Nov 24, 2015 · 9 comments
Open

WebTorrent support #4163

ghost opened this issue Nov 24, 2015 · 9 comments
Labels
Bounty Feature request Libtorrent Waiting upstream Waiting for changes in dependent libraries

Comments

@ghost
Copy link

ghost commented Nov 24, 2015

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.

@apfeltee
Copy link

It'd be nice to have webtorrent support, but, uh..

In order to support WebRTC's connection model, we made a few changes to the tracker protocol.
Therefore, a browser-based WebTorrent client or "web peer" can only connect to other clients that support WebTorrent/WebRTC

So, in other words, it'd be a monkeypatch from hell...

@Chocobo1
Copy link
Member

You guys should follow this issue instead: arvidn/libtorrent#223. It's the backend qBittorrent is using.

@ghost
Copy link
Author

ghost commented Nov 24, 2015

Good idea! Will push my +1 there. :)

@sledgehammer999
Copy link
Member

Closing since this needs implementing from libtorrent.

@ghost
Copy link
Author

ghost commented Nov 26, 2015

Fair enough; will hope Libtorrent picks this up.

@1265578519
Copy link

这个不是早支持了嘛

@Gallaecio
Copy link

Let’s track arvidn/libtorrent#223

@defaultpage
Copy link

PR is merged!

arvidn/libtorrent#4123

@FranciscoPombal FranciscoPombal changed the title WebTorrent Support (No, not WebSeed) WebTorrent support Jul 1, 2020
@FranciscoPombal FranciscoPombal added Feature request Libtorrent Waiting upstream Waiting for changes in dependent libraries labels Jul 1, 2020
@FranciscoPombal
Copy link
Member

FranciscoPombal commented Jul 1, 2020

PR is merged!

arvidn/libtorrent#4123

Note that the PR has been merged to the master branch. qBittorrent will only benefit from this once:
1- this is merged into one of libtorrent's RC_x_y branches (according to the libtorrent author in arvidn/libtorrent#4123 (comment): "some other branch after 2.0")
2- qBittorrent supports said RC_x_y branch.

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

@qbittorrent qbittorrent locked and limited conversation to collaborators Jul 1, 2020
This was referenced Sep 12, 2020
@sledgehammer999 sledgehammer999 changed the title WebTorrent support WebTorrent support [$15] Nov 18, 2020
@sledgehammer999 sledgehammer999 changed the title WebTorrent support [$15] WebTorrent support Nov 22, 2020
@qbittorrent qbittorrent unlocked this conversation Sep 29, 2023
@qbittorrent qbittorrent locked and limited conversation to collaborators Sep 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bounty Feature request Libtorrent Waiting upstream Waiting for changes in dependent libraries
Projects
None yet
Development

No branches or pull requests

7 participants