[Feature Request] In `peer_info`, add a field which says which tracker(s) each specific peer came from

[DeflateAwning]

In the peer_info call, add a field which indicates which tracker(s) each specific peer came from.

This is required to solve the qBittorrent feature request here: https://github.com/qbittorrent/qBittorrent/issues/17901

[master255]

This looks like an improvement in user tracking rather than an increase in information transfer efficiency. You're not from the police?

[arvidn]

It's not so simple to add this information in an efficient way. Any peer can have been received from any tracker, and there may be very many peers and very many trackers. That may end up being a large matrix (although, each cell only has to be 1 bit).

To make the data structure efficient enough to not make the cost too high for everyone.

[MassaRoddel]

If a peer came via PEX first and later via tracker would the tracker still count as source? In such cases the trackers might seem more popluar than they acutally are.

[DeflateAwning]

If a peer comes in via multiple trackers (counting PEX, DHT, etc. as trackers), then it will show all relevant trackers.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[DeflateAwning]

I still want this

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[DeflateAwning]

I still want this

[master255]

It will never be in the general version of the library. Since you're the only one who needs it. If you need a custom enhancement, it should be a paid enhancement.