Very _very_ disturbing file change notification

[Skywalka]

Hi there.

I just got this message in my inbox of AniDB:

Code: Select all

 24.02.2005 10:57
Title: 	[EDIT NOTICE] FILE: AA! Megami-sama: Chichaitte Koto wa Benri da ne - 9 (crc, ed2k, length, md5, sha1)
Body: 	
A database entry you either own or for which you have submitted a change
request in the past has just been modified.
You may want to verify the changes.

Changed Entry: FILE: 7676 - FILE: AA! Megami-sama: Chichaitte Koto wa Benri da ne - 9
Changed Fields: crc, ed2k, length, md5, sha1
Full Details: show CREQ

If you do not wish to receive these messages you can disable them in the profile settings.
This is an automated message of the creq system.

This is just plain wrong.

I have to dig up the medium I have this file on first and will leave the notify in my inbox untill then. Don't know where it is. Maybe this isn't as bad as it looks and actually there is part of the info that's not already lost but at the moment I cannot even judge whether before the CRC status was "invalid" or "unverified" because I simply get the info what was changed and not what it was before and with so many big changed I really feel the urge to get more info.

But honestly, how should I know which file I have, I cannot even identify it anymore, all values were changed! The only thing I could do is look through all of my files and search for a file that has this hashes and my guess would be that I will find NONE. Then I'd have to look for this episode of MiniGoddesses and every version I have of it and get the hashes of those and compare that info to what is in this entry now and then I will be in the situation that I can not possibly proove that I have the right file because everything is gone that would identify my file as anything related to this file except maybe the filesize.

I really was close to start getting insulting but maybe there actually _is_ a good explenation for the granting of this creq. I just want to hear it and then maybe we can get it resolved. Maybe I am also missing something. I don't know. It just seems so wrong to allow a creq that changes all hashes.

[Elias]

ed2k hash was also changed for this file? What about 45 users having this file (i'm one of them). I didn't got message about file i have has been switched in anidb to different one (file with different ed2k hash cannot be the same).
This is just plain wrong.

[wahaha]

Maybe this isn't as bad as it looks and actually there is part of the info that's not already lost [...]

Does the "show creq"-link not work for you? o_O

It should display a nice table that lists the changed values "before" and "after".

Anyway, you're of course perfectly right that such a change-request should've never been granted. Actually, it wasn't even granted, so the problem somewhat disappears ^^;

Let me explain:
The creq's comment starts with "This is data from the torrent on [...]". Considering the group-tag, it was fairly obvious that someone packed up a corrupted file, so normally the creq would've been denied... if it didn't also change the runlength-value from "0" to something proper.
Thus, I used "ignore" on all changes but this and granted the request. No hash-values were changed.

Short version:
There seems to be a bug with the change-notifications as the ignored changes still show up in the summary.

[Skywalka]

The comment is not shown when I open that CREQ... what I see is:

Code: Select all

field  	 Old Value  	 New Value
crc 	6426ff15 	85de6f73
ed2k 	b890d3bc8d51b34d6804703b04286904 	4ebce6bc8b806c18b946c52cede1409a
length 	0 	1406
md5 	999fbc99a5e7230500c06dc15059052b 	0737fce848716922e4e2049f4029b27a
sha1 	faf2efdf3ae60d2cbe07d34e59fddad6157166a3 	333abf105a156a40c69f4c9d5d11bf895feb429b

What is changed is marked in red, and that's all values. It is again mentioned on the bottom of the page.

So a big "whut? That's possible?" about the option to ignore certain values that were requested to be changed and of course you are right - there IS an "ignored" line in that creq, at the top of the page, it's also indicated in red and I simply overlooked it, I was too concentrated on the hash values and did not care about other values that might've also been altered.

I simply did not know there was the option to ignore stuff. Thanks for pointing that out.

Still it's pretty misleading if at the top it says stuff was ignored and then you see the old and new values of the stuff that might've been ignored mentioned two times below that.

There should be a way to mark only things that were really changed. At the moment it simply displays the content of the FID on the left and the content of the CREQ on the right as well as the admin's decision about the creq at the top.

It would be a good idea to only show the parts of the CREQ on the right that were really granted and especially all that which was ignored should be blanked out. Would be less confusing.

[wahaha]

I reported this as 107: Creq-Notifications should exclude ignored changes and 108: Mark ignored changes more clearly on creq-detail-page