I'd say that first one (api_info) is semi-plausible in terms of being "configured" for piracy, in that it hard codes the production API of the site, and I assume the data accessible therein is largely piracy.
It is also true that one would need to modify quite a few places to make this codebase sensibly usable for anything non-piracy. Even if an Anime studio decided to make their back catalog available over torrent (for some reason), this site really is not designed for their needs.
However, I strongly suspect this list of files is roughly the set that have 'nyaa' as a stand alone word (i.e. not part of a snake case word or other compound). I suspect they loaded the code into a search engine, and searched for "nyaa.si", and flagged all results. Many search engines will treat the '.' like a space, will filter out "si" as being too short, and thus search for "nyaa", and only find results for that when it exists as a separate word.
It is also true that one would need to modify quite a few places to make this codebase sensibly usable for anything non-piracy. Even if an Anime studio decided to make their back catalog available over torrent (for some reason), this site really is not designed for their needs.
However, I strongly suspect this list of files is roughly the set that have 'nyaa' as a stand alone word (i.e. not part of a snake case word or other compound). I suspect they loaded the code into a search engine, and searched for "nyaa.si", and flagged all results. Many search engines will treat the '.' like a space, will filter out "si" as being too short, and thus search for "nyaa", and only find results for that when it exists as a separate word.