Two seeders connects to each other when using this tracker implementation.
Why is this a problem?
It does not have the same behavior as webtorrent tracker implementation.
How does the behavior differ?
When using webtorrent tracker implementation, offers from two peers, where both are seeders, are not passed to each other through the tracker. Since both peers wants leechers to seed to, it is unnecessary to connect two seeders to each other.
According to my testing, this tracker implementation (as it's hosted on tracker.openwebtorrent.com 2021 Feb 15) does not care about which clients are seeding or leeching when passing offers around.
Action
Don't connect seeders to each other when passing offers around.
(Assuming the same torrent hash)
Problem:
Two seeders connects to each other when using this tracker implementation.
Why is this a problem?
It does not have the same behavior as webtorrent tracker implementation.
How does the behavior differ?
When using webtorrent tracker implementation, offers from two peers, where both are seeders, are not passed to each other through the tracker. Since both peers wants leechers to seed to, it is unnecessary to connect two seeders to each other.
According to my testing, this tracker implementation (as it's hosted on tracker.openwebtorrent.com 2021 Feb 15) does not care about which clients are seeding or leeching when passing offers around.
Action
Don't connect seeders to each other when passing offers around.