Fans are having a royal time with Fortnite Battle Royale right now. Epic had its video for the Battle Pass of Season 6 striked due to a copyright infringement. At least that’s what YouTube claims. But can you trust the bots there?
This amuses the fans: A user on reddit noticed that the video for the current Battle Pass in Fortnite Season 6 cannot be viewed. This is the “promo video” that shows the new skins for Calamity or the werewolf.
YouTube reported: The video is no longer accessible due to a copyright claim from Epic Games.
What is a copyright strike? A copyright strike is issued for videos that violate copyright.
If there is a suspicion that rights may be violated, the video will be initially blocked. Users can no longer see it but receive a message that the video is “no longer available.”
It is then relatively complicated to bring it back online:
- The creator of the video can accept this blocking or decide to contest the strike.
- Then the “strike distributor” can decide whether to uphold or retract their objection.
The strike distributor ultimately has the option to pursue their claims legally. This has previously caused a 14-year-old cheater to end up in court over Fortnite.
Epic has to take a lot of heat
This is how fans react: The post about the “self-block due to copyright” has received over 26,000 upvotes on reddit and a lot of mocking comments.
Players say:
- Trust no one! Not even yourself.
- “It hurt itself in confusion” – a nasty Pokémon reference.
- “Okay this is Epic” – A pun with “epic” and the developers Epic Games.
What is behind this? Some are discussing the topic more seriously. They believe that it is not Epic’s fault, but that the culprit lies within YouTube’s system.
It seems that bots have taken over control and act according to algorithms on how to distribute these strikes. Instances occur that seem inexplicable from a “human perspective”.
This is a problem with YouTube. It happens when bots take over control.
Meanwhile, the video has been restored anyway. A comment from Epic regarding what has happened is still pending.
A similar problem with algorithms is described here:
