I looked into the complexity of implementing webtorrent (which is just websocket signaling and webrtc data channel connections to peers rather than the traditio

I looked into the complexity of implementing webtorrent (which is just websocket signaling and webrtc data channel connections to peers rather than the traditional http signaling with udp to peers) in libtorrent and it is kind of a giant mess of C++ :p The problem is more that every desktop client, for some reason, has also reimplemented bittorrent. Specifically, Transmission, Deluge, and KTorrent all use their own bittorrent protocol implementations, and none of them are particularly or easily extensible enough to provide webtorrent support easily. But let it be known eyes are on the prize and have at least looked into it, it is just a hard problem, exacerbated by implementation fragmentation.