Peer Leakage Yesterday we started receiving reports of members receiving DMCA notices for BTN torrents. After an investigation, we found that one user was relaying our peers to a public tracker. That user has been banned. Due to the inherent nature of the current BitTorrent, there isn't really any way for us, or anybody, to prevent peer leakage. Peerlists are known information to the membership, but as a private tracker, we expect no member will make them public information. Unfortunately, despite our best efforts, a few bad apples are bound to slip in eventually. Although we can't fully prevent peer leakage, we're putting measures in place that will allow us to identify it faster in the future. If you were active on one of the affected torrents, you have received a PM explaining what happened and suggesting that you change your port then restart your torrent client. Doing so will invalidate your entry on any cached peerlists. If you did not receive a PM then we believe you weren't affected, although it would be prudent to change ports and restart your client anyways. This is also a good opportunity for a reminder about BTN's rules on VPNs. The gist is that although we have some requirements for accessing the website via a VPN, any user may seed or leech using a VPN. Doing so may provide additional protection against DMCA notices if you currently seed from your home connection. Update: There is no need to StaffPM about DMCA's with timestamp before 2015-04-25 15:00 GMT. Information that could be gathered from those has already been gathered. If you receive DMCA where infringement date is after 2015-04-25 15:00 GMT, please check that you've indeed changed the client port. Majority of the notices seem to have gone to Comcast/Ramnode customers.
