gounlimited.to | BANNED FROM WJ

Status
Not open for further replies.
The best option now I think, would be to modify MD5 hash checks, so when user uploads new file (to working server), all old links/dead files from damaged servers will "link" to the new file. Kind of "reverse" md5 checks. This way, when users re-upload files, their old (dead/not working) links will point to new files = saves them a lot of time to remove/replace them. This would be very helpfull mechanism, that would come handy in future too Im sure.

If not done "on the fly" atleast setup some "batch" job in the backend, to run "scans/searches" once a day or something for new files with the same md5 hash as the damaged ones, and "replace/link them together"

This would allow You to increase the recovery rate drastically in my opinion, with, as You said many users doing reuploads now.
 
Last edited:
@GO Unlimited I reuploaded using FTP some file got the VIDEO ENCORE ERROR and some file get the media file couldn't found... Please check it again.
Please send me some examples via a PM.

Hello Sir @GO Unlimited

Kindly check my skype message please thank you.
I will check as soon as possible.

The best option now I think, would be to modify MD5 hash checks, so when user uploads new file (to working server), all old links/dead files from damaged servers will "link" to the new file. Kind of "reverse" md5 checks. This way, when users re-upload files, their old (dead/not working) links will point to new files = saves them a lot of time to remove/replace them. This would be very helpfull mechanism, that would come handy in future too Im sure.

If not done "on the fly" atleast setup some "batch" job in the backend, to run "scans/searches" once a day or something for new files with the same md5 hash as the damaged ones, and "replace/link them together"

This would allow You to increase the recovery rate drastically in my opinion, with, as You said many users doing reuploads now.
I will check the possibility of that.
 
The best option now I think, would be to modify MD5 hash checks, so when user uploads new file (to working server), all old links/dead files from damaged servers will "link" to the new file. Kind of "reverse" md5 checks. This way, when users re-upload files, their old (dead/not working) links will point to new files = saves them a lot of time to remove/replace them. This would be very helpfull mechanism, that would come handy in future too Im sure.

If not done "on the fly" atleast setup some "batch" job in the backend, to run "scans/searches" once a day or something for new files with the same md5 hash as the damaged ones, and "replace/link them together"

This would allow You to increase the recovery rate drastically in my opinion, with, as You said many users doing reuploads now.

I like your point. Very usefull!
 
Uploaded a bunch of files today on fs307 but stream speed is unacceptable slow... can you please make something for this... I think there is no reason to continue uploading more files if network suffers of slow speed
 
Admin have gives us double rate for whole week But I am saying that money is not everything I am Loosing my visitor again due to not playing videos on my site My Visitor will not comeBack.
 
Status
Not open for further replies.
Back
Top