I recently started to use the torrents branch and so far it works pretty well, so thanks for that!
Are you planning to add support for other public torrent indexers, such as TPB?
You can look at the Trello card linked in the first post to see what they’re planning to do or at least looking into. 
Ah, thanks. I missed that link
@MauriceW Sry TPB is atm a “no can’t do”, since they don’t have an api. Some other services use website scraping, but we don’t do that, it’s ugly and adds extra load to the website.
What if you write a scraper that exposes its own API and host it on one of your own servers? Or maybe you could define an API so that people could write their own scrapers that could use any random site and expose it through that generic API? That way power users could use their personal favourite trackers and possibly even share the scripts involved without you guys having to support them.
Another alternative could be a plugin system but that’s obviously a lot more work. 
Torrentznab. Would potentially make things easier for searching on kat, nyaa and those sites with borked apis. but anyone that’s publicly hosting the api is gonna get heat.
Which is why you should only specify the API interface and let people host their own scripts for it somewhere. That way if someone is crazy enough to host their own “indexer” people can link to that in their own the same way they do now for Newznab but at the same time I could host my own indexer which scrapes a torrent site and exposes the data it fetches through a generic API that you define. Would cost very limited effort on your end while providing the community with all the tools they need to support any source of torrents they prefer, including private trackers.
1 Like