Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That doesn't have the reply from ChainPatrol:

Hello! This was a false positive in our systems at @ChainPatrol . We are retracting the takedown request, and will conduct a full post-mortem to ensure this does not happen again.

We have been combatting a huge volume of fake YouTube videos that are attempting to steal user funds. Unfortunately, in our mission to protect users from scams, false positives (very) occasionally slip through.

We are actively working to reduce how often this happens, because it's never our intent to flag legitimate videos. We're very sorry about this! Will keep you posted on the takedown retraction.



Completely ignoring the release dates for the videos is simply amazing.


The database they are comparing to is probably not only youtube videos. So the freebooted or matching video, in their database, has a creation data which is earlier than the 3blue1brown video.


The database they are comparing to does not exist. They are making shit up and spam reporting high view count videos to get the revenue from them.


Why would they trust that date?


Abusing the DMCA to take down videos stealing user funds seems... questionable.


Completely agree. It should be on YouTube to do that and not a 3rd party.


Nice that they are admitting to perjury on twitter like that.


As other threads have pointed out, Google's copyright violation system is a process that's private. It's before the DMCA laws get involved.

So maybe it's a ToS violation?

(This isn't defending the person issuing copyright strikes. Their behavior, right or wrong, just isn't perjury. I think. Good thing I'm not anyone's lawyer.)


The original Twitter link doesn't show any replies either. Maybe it does if you're signed in, but I no longer have a Twitter account (and nor do most people).


How is this failing the most fundamental check: upload date?


Generally a good idea, but there are edge cases that need to be handled for this to work.

A copyrighted video might not be uploaded to YouTube, in which case you'd have to fall back on the video creation date, which would have to be manually added in their DB (e.g. Hollywood produced movies).

You can also have leaks of videos before their official release. Admittedly a rare scenario that should can be accounted for in other ways (i.e. skip this check if before upload).


> A copyrighted video might not be uploaded to YouTube, in which case you'd have to fall back on the video creation date

Correct, but in this case we know there was no earlier video anywhere, so the only conclusion to draw is that they simply weren't checking the date at all. If the only "source" video being compared with the "offending" video had a newer upload date, the claim never should have been allowed to happen. If there's truly some external video with an earlier upload date, compare to that.


Neither does the x.com link if you connect via well-known VPNs.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: