[Whishlist] BEP22 in qBittorrent

[xcme]

Hello!

I am a network engineer in ISP. In my network of about 50 thousands subscribers, many of whom are using torrent software. For this reason, I use the service, known as 'retracker'. After the introduction BEP22 for the my network, number of records in the retracker-database increased by about a third. This is a very good result and it is convenient for both subscribers and the provider.

But there's some problem - only uTorrent able to work with BEP22 and receive retracker-address from ISP. At the same time, uTorrent is too adware, and can not be recommended for regular use. =)

I look forward to the appearance of support BEP22 in qBittorrent in the future.

BEP22: http://bittorrent.org/beps/bep_0022.html

[thalieht]

As mentioned here #1785 this is handled by libtorrent

[xcme]

This is a very old issue (2011). Thus, no chance?

[thalieht]

I think @arvidn moved the libtorrent project here on github because google code is closing. Alas i'm not familiar with it. Maybe he can clear this up.

[sledgehammer999]

We use libtorrent-rasterbar for the bittorrent protocol. We don't implement it. So any BEP or additional protocol functionality needs to come from libtorrent-rasterbar.

[ngosang]

@xcme you can open an issue here https://github.com/arvidn/libtorrent/issues

[sledgehammer999]

There is already an issue open in libtorrent: https://code.google.com/p/libtorrent/issues/detail?id=220

[xcme]

Thank you! I opened a new issue for libtorrent.