Support Forum

"developer" is now about at the same level as "0.7.x". You can rebase and create a new pull request. Sorry for all the delays. By the time I'm ready syncing "develop" with "0.7.x", I will hand-merge your solution into "develop". I'll get back to you...

By the time I'm ready syncing "develop" with "0.7.x", I will hand-merge your solution into "develop". I'll get back to you then, so that you can easily create a new pull-request, so that your authorship is acknowledged. Currently, I'm simply flooded with other things i...

Not what you are asking but this type of check is in the current version on Git in the 0.7 branch. It seems a bit inconsistent with other features as it does not save periods or commas in the list of extensions you give it (so it may not be working correctly) unlike the remove extensions option but ...

I have been using 0.8 for a long time but with all the new additions to 0.7 I am thinking of going back to the updated 0.7 release.

Can I just use the same ini file and let SAB sort it out or do I need to remove any files to get 0.7 working?

TIA

Currently "develop" is seriously behind 0.7.x This has to do with the fact the the Unicode-ification makes the code bases divergent. As soon as 0.7.17Final is out, I will start the merge actions. It has become quite a challenge. Sounds good. I will update and give it a try when you have t...

However, I thought I was following your directions for how I should contribute, since I was originally working on the master branch: If you based in on "develop" then you did the right thing. It's only me who is behind with the work of merging patches from "0.7.x" to "devel...

Treat it as two pools of servers. The first pool is tried first then the second pool is then tried. It is a pity the patch for proper server priority has not been applied until it is the above is the best you can do. I do not know the reason why but Shypike seems to be a bit reluctant or just does n...

Set both EU and US Astra as primary servers - if the article is missing on one the other is tried anyway. Set your block server as the backup. Treat it as two pools of servers. The first pool is tried first then the second pool is then tried. It is a pity the patch for proper server priority has not...

I would use it is to find the more popular groups for manual searching and finding my most used groups.

Thanks but it was particularly when the item is in the queue that I would find this useful so I can make the decision before the item is processed. For my RSS setup it would also be helpful if it included the RSS name (this means you know what search matched what from the same source). Just the sour...

Could the history be enhanced to include the groups that were used to process the queue item?

To keep thing simple just check the first or first few lines.

(e.g. <group>this bit</group> from the nzb file)

It would be a great feature to have an indication of where queue items came from? If a queue item came from a rss feed called "reliable" or a rss feed called "unreliable" (simple case of only 2 rss feeds defined I have many more). If the item did not come from a rss it could be f...

I am confused - should the develop branch have Fmstrat server priority patch but not the 0.7.17 changes? I can't find neither Fmstrat or 0.7.17 changes in the develop branch? shypike do you need something from Fmstrat as I would also like to try out these changes? It is a bit strange that there are ...

shypike I am following your develop branch (for some reason this does not have your 0.7.17 beta release but it has the server totals in history which is why I am using develop) would it be feasible to get these server priority enhancements into your develop branch? It is great someone has taken the ...

Another option that works for some is assign 1 connection to the most expensive backup server and a high number of connections to your other backup servers. This means all servers will still be available but the server with 1 connection will hardly get used. Monitor how much is used on the servers p...