Hacker News new | past | comments | ask | show | jobs | submit login

Removing adverse incentives is a step in the right direction! Now, any employee at a copyright holder assigned to send out manual copyright claims will become a cost center. No longer will copyright holders be able to justify such assignments via captured revenue from creators - instead, they will legitimately need to value the cost of the claiming against the actual damages done to the copyright holder made by the sharing of copyrighted music.

On the other hand, there are a lot of music videos on YouTube that copyright holders might have been fine allowing to exist, and now their only option is to nuke them from orbit. Mashups, etc. may suffer. Essentially, this is a move that may reduce spurious claims, but may come at the expense of certain grey-zone expressions.




Content ID content owners have a lot of options when dealing with their content appearing in videos.

For one[0], they can choose "block" - prevents it from showing in some/all countries, "monetize" - takes the videos's revenue (note that there is now revenue sharing so that claims don't always take 100% of the revenue[1]), or "track" - just track the video analytics.

It might be worth it to set up "if 2 minutes or less of my 4 minute song appear in a video, monetize", "if 30 seconds or less is used, just track it", and finally "if the entire video is my song or uses my song in its entirety, block it". Not sure how advanced the Content ID system really is since it's easier to get the Copyright Match Tool than Content ID, but I wouldn't doubt Google's ML had something like "match certainty" copyright holders can use to filter content like mashups and remixes. It's most likely up to the content owners to use this to filter, though, since the entire purpose of Content ID is to help both YouTube and Copyright holders avoid DMCA lawsuits.

0: https://support.google.com/youtube/answer/9245819?hl=en ("Content ID" wrapper)

1: https://support.google.com/youtube/answer/3301938




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: