Does anyone know who all it can be used with, other than HDAccess?
I can’t promise yet, we’re hoping it will make it’s way into the u-232 torrent tracker base code. But not sure if it will, and even then it would take some time for any torrent site to adopt it.
We still plan on adding generic rss btw, but the PR for that isn’t ready.
1 Like
Thanks for the info. 
Good luck Taloth!
We tried to implement something like this in CouchPotato a while back. But getting traction from the “tracker developer community” seems hard at best, https://github.com/RuudBurger/CouchPotatoServer/wiki/Couchpotato-torrent-provider
Yes I know, it’s not going to be easy but at least we’ll be able to point at something if ppl ask for ‘their’ indexer to be implemented 
Not expecting wide adoption anytime soon, but I also intended this api to serve as a method for enthusiasts writing their own proxy/cache.
I think using newznab as basis is a good choice coz it isn’t custom made for just tv or just movies, apart from some additional attributes it’s a proven standard for usenet.
As for trackers. It’s not necessarily competing with their existing community, it’s possible to make it supplementary through the karma system. Once they see the potential in it they might actually start liking the idea it will only take a decade or so.
But if you want Torznab in CP… have at it. 
It’s pretty much just a copy of the newznab code, so not that much work.
If you combine it with using the recent feed instead of periodic backlog searches it would limit api calls too.