Plex is a versatile streaming platform that allows users to watch, organize, and curate their favorite media entertainment. Sharing your Plex library is also an option. There are also concerns about copyright infringement. To “avoid the spread of copyright infringement,” Plex asked his GitHub to remove repositories where he could reshare libraries that were not originally his. TorrentFreak reports: The US-based Swiss company asked GitHub to remove the Plex Reshare repository, saying it could contribute to copyright infringement issues. “Plex Reshare” does not host any copyright-infringing material and, as far as we can confirm, does not mention any copyrighted works. Its main purpose is to allow a Plex user to browse shared Plex directories on his web. This allows directories to be “reshared” without being the original owner. “The reason behind this project is to make your PLEX share available to other friends who are unrelated to the original library owner,” explains Plex Reshare developer Peter.
Although the repository does not host or link to infringing content, Plex claims it can be used to “amplify” copyright infringement. “We have discovered infringing material on your website that is actually another 'Plex Server.' The allegedly infringing material will be immediately removed or access to it will be disabled and ,” the takedown notice states. To read. The first part of the sentence is a little confusing. Plex-reshare is not his Plex server, but the company may use “OTHER Plex Server” as an internal classification category. In any case, Plex claims that this repository could contribute to an increase in copyright infringement on the platform.
Plex cites the Online Copyright Infringement Liability Limitation Act to require GitHub to take immediate action or face liability. It's not clear what this liability claim is based on, as the takedown notice makes no mention of actual copyright infringement. Despite the broad nature of this claim, GitHub actually took the repository offline and replaced it with a DMCA takedown reference. GitHub is known for putting developers first when it comes to these types of issues, so this probably wasn't a simple decision. In this case, it took him over three weeks for GitHub to start responding, much longer than usual. This suggests that GitHub may have allowed the developer to respond and sought legal advice from its in-house counsel to ensure that the rights of all parties were properly considered. Masu. The report notes that Plex reshared code is also listed on Docker Hub and could face a similar fate.