- October 22, 2005
- 145
- 32
- Thread starter
- #51
No it won't download the wrong data again.
If the data exists locally on your computer (remember you deleted the content of data directory, then filled it up again by grabbing the data from MSN) then DUGG will simply re-load that data and not look for it on FTP.
The noftp command completely disables all FTP functions including upload. It is mostly for people on networks that have closed port 21 but it has other uses like this also.
I realize this does nothing to help everyone else but it fixes your data at least.
I can manually delete data from the FTP and I will do so if people report an error like this. That way subsequent users when they grab the data again will upload a "good" copy. The program can automatically delete bad data from the FTP but giving this power to end users is a recipe for chaos; it would take just 1 disgruntled person to delete everything every day.
Detecting obviously corrupt data is relatively easy but detecting changed data is difficult.
For example if your copy says that CSI is on at 8PM but my copy says that Law and Order is on, how can the program decide who is right?
I have been toying with the idea of embedding an MD5 hash and a timestamp into the data. The MD5 hash can detect if the data is different, and if so, the time-stamp can decide which is newer. The program could then be trained to assume that when different, the newer data is more correct. This will require a fair-bit of coding (ever seen the MD5 algorithm?) but it might be worth the effort I think.
I don't actually watch much TV so I'm not likely to spot errors in my TV guide like the one you describe. Does it happen very often ?
Oh...and the noftp command is one of many undocumented commands I put in there to deal with situations like this. I'm always happy to hear from people if they have some particular dilemma because there is almost always a work-around.
If the data exists locally on your computer (remember you deleted the content of data directory, then filled it up again by grabbing the data from MSN) then DUGG will simply re-load that data and not look for it on FTP.
The noftp command completely disables all FTP functions including upload. It is mostly for people on networks that have closed port 21 but it has other uses like this also.
I realize this does nothing to help everyone else but it fixes your data at least.
I can manually delete data from the FTP and I will do so if people report an error like this. That way subsequent users when they grab the data again will upload a "good" copy. The program can automatically delete bad data from the FTP but giving this power to end users is a recipe for chaos; it would take just 1 disgruntled person to delete everything every day.
Detecting obviously corrupt data is relatively easy but detecting changed data is difficult.
For example if your copy says that CSI is on at 8PM but my copy says that Law and Order is on, how can the program decide who is right?
I have been toying with the idea of embedding an MD5 hash and a timestamp into the data. The MD5 hash can detect if the data is different, and if so, the time-stamp can decide which is newer. The program could then be trained to assume that when different, the newer data is more correct. This will require a fair-bit of coding (ever seen the MD5 algorithm?) but it might be worth the effort I think.
I don't actually watch much TV so I'm not likely to spot errors in my TV guide like the one you describe. Does it happen very often ?
Oh...and the noftp command is one of many undocumented commands I put in there to deal with situations like this. I'm always happy to hear from people if they have some particular dilemma because there is almost always a work-around.