Question about Settings - is there any Documentation?

[albino1]

I've been using the Mirabis fork for a while now, but there's still several options I don't fully understand, so I was wondering if anybody could point me towards some documentation, or just explain them.

I'll just go by category:

 
SEARCH

Smartsearch (suggested -- removes weak matches)

I think in theory I understand what this does, but not specifically. I've turned it on and off, and the results definitely do seem to be better on, I just wonder if I'm ever accidentally missing something because I didn't phrase my search correctly and it got removed for being a weak match.

Cache results (suggested)

How long does the cache last? In builtin_params.ini the max_cache_age is set to 12, so I'm assuming that's 12 minutes?

In my experience the real benefit of caching is being able to sort by Size/Age/etc without it requesting results again. I think that's more of a bug in the original though, since even with caching turned off it really shouldn't have to re-query all your indexers every time you want to sort.

 
NEWZNAB HOST (API)

Extra

The default for this is API+Manual, with alternate options of API only and Manual only. API I get, but what exactly is Manual? Is it loading a site URL and scraping the HTML when API fails?

 
NEWZNAB HOST (WEB)

I have no idea what this is really for. It appears to be for Newznab indexers that support API, but don't support API keys? Can anyone give an example indexer that requires user/pass for API instead of API key? Or am I totally misreading what this is supposed to be for?

[Mirabis]

Newznab Manual = When you click on the [Search] button on the webPage. API Only = when integrating nzbMegasearch with CouchPotato for instance.

I myself have never tried NewzNab Web.

Smartsearch & cache results u already seem to understand :)

[albino1]

Newznab Manual = When you click on the [Search] button on the webPage. API Only = when integrating nzbMegasearch with CouchPotato for instance.

Oh, hah, I would never have guessed that. Took me a second to even understand what you were saying since I don't use NZBM's API, but then I got it :) I assumed it was related to the indexer API, not NZBM's own internal API, but that totally makes sense now and explains a lot. Thanks for the reply!