Author Topic: Import as paused: SFV files  (Read 2155 times)

Offline icecube

  • Contributor
  • ***
  • Posts: 29
Import as paused: SFV files
« on: March 20, 2009, 10:34:15 pm »
Hi,
In the "Import as Paused" options, you can auto-pause all the extra not needed files except for SFV files. I have block downloads so I pay per byte and over time every little byte helps. To me, I find this file pointless to download as the small par2 file does the exact same thing plus more (par2 repairing obviously). Any chance of including the .sfv file to be imported as paused as well?

Zeikzeil

  • Guest
Re: Import as paused: SFV files
« Reply #1 on: March 21, 2009, 12:50:56 am »
I see how you say in case of block accounts all bits can help. I currently have close to 300 collections queued, all of them with a .sfv. It totals to almost 1.5TB of data. The .sfv files' total size is less than 700K. Yes, I went through all of them manually :P
I can see your point but unless it's a very easy implementation I don't really think it's worth the effort.

Offline icecube

  • Contributor
  • ***
  • Posts: 29
Re: Import as paused: SFV files
« Reply #2 on: March 21, 2009, 08:48:38 am »
Yeah, thats true. SFV files arent big at all. But seeing as we already have the option to auto pause certain files, I just thought we might as well include another extra file thats not needed. I dont think it should be too hard to implement, the import as paused feature is already there, all that needs to be added is a filter for *.sfv files.

Offline mysteryman

  • Contributor
  • ***
  • Posts: 66
Re: Import as paused: SFV files
« Reply #3 on: March 28, 2009, 10:07:58 am »
I agree most the mainstream posting is done including pars. However (without actually looking) I would wager to believe there are some cases where par files are not included. Also, if a person used the "delete par2 files" option, and the original files were saved (which, I do), it WOULD be necessary to use these sfv files in the future... if there was ever a problem.

Obviously ... these are the exceptions to the rule, but so is complaining about 1MB of sfv files after downloading 1.5TB of data. They really are miniscule, EVEN IF they were truly redundant.

I doubt it would take much to implement (as the functionality is already there) ... but I believe people who chose to use the option would end up with problems at some point.