Nice, just a couple of details that comes to mind...
Is needed to prepare something to prevent the database to host "incorrect" IRD files
Lets say... you and me have the same bluray game, and there is no IRD about it in the database
My disc is full of fingerprints, scratched, the internal hdd filesystem of my PS3 is destroyed, the hdd have bad sectors, etc... in few words, my IRD is crap
But i upload the IRD first to the database (so is going to be valid and is going to be acepted in the database because is the only sample of it)... after that you upload your IRD (that is good)
At this point the databasse have 2 different IRD's, and is imposible to know which one is good
I think the only way to prevent that problem is by using some kind of counter in the database to see how many people uploaded the same IRD
Lets say... if there are 7 IRD of a game that are exactly the same... and 1 is different, then the different one is wrong
For the managunz user it would be very handy to have a confirmation after the "send IRD to URL" to inform him/her if the IRD he/she uploaded matches with the other IRD's of that game that already existed in the database. The point is to do things in this sequence
1) insert bluray disc in the drive
2) create IRD and send to database
3) the database replyes with "your IRD matches, your dump is perfect"
This way you are creating an IRD and at the same time you are doing an IRD check... 2 birds in a shot... win win