This isn’t an issue, I’m offering my support as a developer.
I have been using Sonarr for a while, but it’s usefulness for me has almost come to an end for the only reason as the support for public trackers as pretty much dried up. I’m not pushing blame or anything like that.
I would like to contribute my time to help out and get this area of the software working again (“Make Sonarr Public trackers Great again!”…sorry, had to do it)
I’m aware of Jacket-Public, but honestly the dependency on another 3rd party piece of software, and one that is too complex to setup for what it does, I don’t find is a great solution.
As a developer I want to help. I want to hop into the code and help this project out. But it does appear that this area of the software has been neglected and I want to know if I do work in this area that the changes will be part of the future path of Sonarr.
If you would like the help in this area, I would also like to know more about your plans for it (if any) so that I can help carry those along.
The problem is on the side of the indexer, they don’t provide an API for Sonarr to use and we won’t support screenscraping, which is how Jackett is forced to implement it.
If the indexer supports RSS using a standard format Sonarr can support it via Torrent RSS, but without an API searching won’t work.
I understand that the goal isn’t to support sites that are missing APIs. Parsing webpages isn’t hard, but they do change frequently and do cause scraping to fail.
What about adding new public trackers, or getting the existing public ones to work (like RARBG)? Is there value in doing that?