Thank K0nr4d for the input - indeed for this to work, tube authors need to add it for sure. All I can provide are the tools (eg a compiled C script to fingerprint the movie and then developer notes on what to do with that). FWIW, false positives in my tests are extremely rare, but I'll get a POC up for people to test out before I make any more assumptions.
The clip concept is interesting - a content producer with a 60 minute movie adds that to the copyright db. They then release a 5 minute clip that does the rounds on the tubes. The 5-minute clip would of course match the 60-minute movie and get flagged, which isn't at all what we want.
hmmm...
The fingerprint of both movie and clip contains the video lengths, so it's possible to only raise a flag if the queried fingerprint is > xx% of the db fingerprint.
In that case, xx% would need to be configurable by the tube owner. Of course, the tube script could also allow flagging of certain user's to not be checked.. this is all down to the tube author to implement...
The clip concept is interesting - a content producer with a 60 minute movie adds that to the copyright db. They then release a 5 minute clip that does the rounds on the tubes. The 5-minute clip would of course match the 60-minute movie and get flagged, which isn't at all what we want.
hmmm...
The fingerprint of both movie and clip contains the video lengths, so it's possible to only raise a flag if the queried fingerprint is > xx% of the db fingerprint.
In that case, xx% would need to be configurable by the tube owner. Of course, the tube script could also allow flagging of certain user's to not be checked.. this is all down to the tube author to implement...


Comment