Open cybericius opened 10 months ago
The tracker matching code only matches against hostname, so differing ports should not be a problem. Does every torrent carry a potentially different subdomain and not just multiple tracker urls, such that a fallback is always available?
If that is the case, it would technically be possible to ignore subdomain or something similar, but I want to be careful there because you can fast make unintended matches then.
subdomain1.ncore.sh subdomain2.ncore.sh ... subdomain1.ncore.pro subdomain2.ncore.pro ... Can it be managed, or would I have issues with these? I would be more relaxed to set "ncore." in my filtering criterion to match the tracker site as I'm pretty sure this sub-string wouldn't match other trackers.
Hi,
I like this project, though I haven't set it up yet. My concern is that the torrent site I use has multiple sub-domains and different ports in the tracker FQDN. This can lead to unmatched condition and finally site ban. :) Would it be possible to only look for a specific sub-string (like Excels' HAS function) and not the whole FQDN to identify the tracker? Thanks.