transmission/transmission

Support webrtc for webtorrent clients

Open

#47 opened on Sep 30, 2016

View on GitHub
 (58 comments) (138 reactions) (0 assignees)C++ (10,996 stars) (1,154 forks)batch import
good first issuepr welcometype:feat

Description

Hi, how difficult would it be to support clients connecting via webrtc?

Gitocin bounty details:

For all people who will be working on from Gitcoin required things is (the % is what you will be paid) :

Websocket tracker support [25%] Exchange file beetween nodes [70%] Use webtorrent if node is behind nat and can't use nat-pmp or upnp [5%] The port for webtorrent doesn't need to be the same than regular torrent, (cause webtorrent use ICE)

Contributor guide

Tech stack
cpp
Domain
desktop
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
C++WebRTCBitTorrent protocolNetworking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate how WebRTC can be integrated into Transmission's existing networking layer. Look at the WebTorrent project for reference implementation. Consider the bounty breakdown: websocket tracker support, file exchange between nodes, and using WebTorrent when behind NAT. Review Transmission's codebase (especially libtransmission) for networking and peer connection handling. There are 58 comments discussing approaches, so read those for context. No linked PRs exist.
Support webrtc for webtorrent clients · transmission/transmission#47 | Good First Issue