Automatic crc for local checks?

[mirkosp]

After local uploads are done, users get prompted to download a test copy to check if the upload went fine. Wouldn't it be faster to also tell what the crc32 or the md5 of the uploaded file is, so that people that do know what it is can speed up the confirmation without having to redownload the file first?

[BasharOfTheAges]

Wouldn't that assume the average user is smart enough to know what a crc or md5 is? I think thats honestly asking too much of the user base. XD

[mirkosp]

I didn't say to use it as the ONLY way, just as a further alternative to the current way, so those that DO know what crc32 or md5 are can speed up the process, especially on big videos, and considering that now we allow donators to upload upwards 300MB for single files, it might actually have a point.

[Nya-chan Production]

Or alternatively, it could check for CRC string within filename and if it matches CRC of the file, it passes automatically.

For a CRC inclusion, there could be a guide.

[mirkosp]

That would be cool too, yes. Basically, it would speed up the upload process a lot, which would certainly be a good thing.

[Qyot27]

Another vote for, since it would make it easier for those users who encode their upload copies in a form their computers can't handle playing back (speaking from personal experience here). I've had to resort to 'download the test copy, compare checksums, confirm' anyway - being able to skip the test download would streamline it pretty well.


It's fairly safe to assume that Windows users will be using one of the NT platforms, so HashCheck would be fine for the majority. .sfv or .md5 files could be made available so that all the user would need to do to is download that .sfv/.md5 file, make sure it's in the same directory as their video, and double-click on the .sfv/.md5 - the HashCheck dialog box will appear and show them whether it's correct. Since it also works from the file's Properties dialog and integrates into Windows Explorer's right-click menu, it could also be used to gather the info before uploading or to put in the filename for the autocheck idea.

Alternatively, there is this application:
http://sinf.gr/en/hashcalc.html

It's cross-platform, but doesn't do CRC32.

[Nya-chan Production]

Another vote for, since it would make it easier for those users who encode their upload copies in a form their computers can't handle playing back (speaking from personal experience here). I've had to resort to 'download the test copy, compare checksums, confirm' anyway - being able to skip the test download would streamline it pretty well.


It's fairly safe to assume that Windows users will be using one of the NT platforms, so HashCheck would be fine for the majority. .sfv or .md5 files could be made available so that all the user would need to do to is download that .sfv/.md5 file, make sure it's in the same directory as their video, and double-click on the .sfv/.md5 - the HashCheck dialog box will appear and show them whether it's correct. Since it also works from the file's Properties dialog and integrates into Windows Explorer's right-click menu, it could also be used to gather the info before uploading or to put in the filename for the autocheck idea.

Alternatively, there is this application:
http://sinf.gr/en/hashcalc.html

It's cross-platform, but doesn't do CRC32.

IMO server-side check against something user already input would be faster than RE-downloading and THEN checking. But it depends on how easy that would be to implement.