Failed Files list Limit?

[6t5omde]

I noticed the "Failed Files" list only stores 1,000 files (well, it will go beyond that but knocks the list down to 1,000 upon restarting the program, removing the newest entries). I would like all duplicate posts I tried to download to remain red in color. Files over that limit revert to being shown just as "read" messages instead of displaying red in color.

[Quade]

The 1000 limits is probably only on restart. I have 2400 and counting in my failed list right now.

I don't know what sizes you guys need until you tell me. I cap it because failed list uses ram and takes time to load.

[Busty]

How can any of us give the limit when the limit is set by having a complete record of every download that has failed?

You can see from your own usage that if you had a crash or a hard reboot you have lost 50% of your records of what has failed.

How can you tell from 50% that no longer exists what ones you may have wished to retry to download to see if it was a Newsbin glitch , not enough headers , retry from a block account or to even source from an external site away from usenet?

[itimpi]

I don't understand what use a limit is to the customer either.

The comment from Quade mentions that the larger the number of entries the more RAM Newsbin requires to run. This seems a reason to apply a limit.

[Quade]

Takes longer for Newsbin to startup too.

[Quade]

6t5omde,

You'll be able to disable it. Not in 6.50B11 which is almost out but, in B12.

[SETTINGS]
TrimFailed = 0

Will turn off the trimming. Just have to add it to the NBI file. I already track downloads out of band, I might be able to track failures the same way, then you wouldn't have to depend on the fails list to turn files red.