0ndjultomte

Member
  • Content count

    5
  • Joined

  • Last visited

Posts posted by 0ndjultomte


  1. Look at the number of views of this thread! There is clearly a huge demand/interest for such a feature! ;) and its just a extension of the already implemented crc check code ... :)

    Plugin or not doesn't matter. As long as you get the functionality.


  2. Define "complete release"?

    No, I am not stupid and I know what you mean by it, but my point is... there is no such thing as "release" defined anywhere in any standard... and no program can say if anything that has unknown number of definitions is complete or incomplete. This is a fact.

    Thus, what you asked is impossible and as you said yourself there is no such program (even a DC client such as fulDC is not such a program).

    What we can do is check finished file's integrity against an .sfv file but that in no way guarantees what you ask. Sure you can say that every scene release contains an .sfv file, but what you fail to see is this: DC is not the original distribution method for these releases, so it is perfectly possible that the .sfv is incorrect or has gotten corrupted during the transfer from scene ftp to DC users share in a hub (which is quite often through more than one people's computer).

    Or alternatively, I could create a "scene release" of my own out of the dvd made from the film footage taken on my last family holiday in Egypt, and share it on DC, and no program could tell the difference between this fraud tailored by me. (with this I intend to point out, that creating .nfo files split-file archives and an .sfv, is not a secret zen art known only to those that release stuff to scene ftps).

    Besides you seem to get the function of the .sfv file wrong, even though I am no specialist, I can be fairly certain when I say that its original purpose is to check the files for possible corruption during the transfer from ftp to users computer (DC clients have TTH to check for corruption during transfers), and hardly to check for missing files. (I can be fairly certain of this because, if scene release is incomplete, non working or corrupted it gets nuked).

    However, as a final note, to check release completeness with the .sfv is fools doing, for in order to do that you could have to download many files that would turn out to be useless if the release proves to be incomplete (just use the .nfo file, your eyes and and your common sense to see if it is obviously incomplete or not, when queuing stuff).

    Btw. If people request a feature for checking scene release integrity we can't implement such a feature because if we did it might be seen as encouraging our users into using our program for illegal activities, which we do not do or sign in any way.

    Oh boy, you are really missing the point here. It's obvious that you are not a active dc users in anything but public hubs.

    Yes a complete release is in this context well defined! And its the first thing one bases a eventual nuke upon. The SFV file! Tada...

    The sfv file is a check sum that you use to verify that you have all the rar files and that they are intact.Hence why not use it ? Right now only the crc checking is done. Every single SFV check program checks for complete releases... if a file is missing there will be a log of that or even a file created in its place with the extension .missing.

    Well since you cant see the point of utilizing sfv to more then 50%, let me put it in simple terms.

    User X get a release written to a directory that is shared( via manual copying or ftp) when a refresh is schedualed the DC client check each file against the checksum and if its ok its shared, if not its not shared. And why not fully utilize the sfv? dont share each file directly only share each file in that directory if all files are ok.

    This would mean that you could share a incoming directory and hence it would spread releases faster! and wont require manual labour (as in moving sfv checked releases into a shared directory) ...

    It's all about sharing! Automating the steps makes life a better place for us all ;)

    A question for you, have you every downloaded a release and when its done just realizing it was a incomplete share that you downloaded? Now you have to search for that release again and start dl again to get the missing files! Extremely annoying and a waste of time.


  3. maybe the best solution would be to implement something like OnDownloadComplete.. something like File preview section.. users can define which programs should run after successful download of some filetype (or some other criteria)..

    so, you guys who want sfv so badly, you can find a small client that can check the validity of a music file (according to its sfv file), by simply putting a OnDownloadComplete entry for say mp3 files or so..?

    fuldc et. al. already checks dl files against the sfv. what we want is a feature that ensures that only complete releases are hased into the share, there is no such program.

    you would need a program that changed a rel directorry name and adds incomplete and add incomplete to your skiplist. but that wont be good since you would alter the relase name :)


  4. Verifying that only complete releases get hashed into the share by the sfv would be a invaluable feature for many hubs!

    If there's a missing or broken file that directory wont be added to the share. Its as valuable as TTH sums...


  5. I will soon release a 1.8 version of the original ADL search , but I wont release a 2.0 until theres better support for regular expressions in the clients.

    I have no problems that you use my ADL toast, just add appropriate source credit