Skip to content
This repository has been archived by the owner on Apr 23, 2021. It is now read-only.

Extensions repo has been DMCAed #1

Closed
mirh opened this issue May 12, 2018 · 11 comments
Closed

Extensions repo has been DMCAed #1

mirh opened this issue May 12, 2018 · 11 comments

Comments

@mirh
Copy link

mirh commented May 12, 2018

Supposedly, due to file: /src/background_script.js
Is it too hard to object the thing if wrong, or adjust the script a bit otherwise?

@onestay
Copy link
Owner

onestay commented May 12, 2018

I'm aware of this. What's written in the text is wrong and the source code is entirely written by contributors and me however the dmca law also says that you can send a dmca request to programs which circumvents access restrictions to copyrighted content which the extension kinda does. I would file a counternotice if 100% sure that I don't get into legal trouble.

@Blightwidow
Copy link
Collaborator

Do we still have the source code at least ?

I am surprise they went after the repo instead of the extensions.

Concerning their right to emit such notice, it is hard to say. We would need the help from a lawyer. Maybe a mail to the EFF or something but frankly I don’t think we stand a lot of chance

@Blightwidow
Copy link
Collaborator

Also just read the notice and yeah there request are totally bogus. The script access an API and none of the script was taken from Crunhyroll source code that we don’t have access to anyway.

@999eagle
Copy link
Collaborator

@Blightwidow we still have the code. I've create a private repository containing the code as I wrote in our Slack :)

@onestay
Copy link
Owner

onestay commented May 12, 2018

Yea the request doesn't make sense. Not sure why they wrote it like that. However I can see the reason for the dmca. And it wonders me too that they didn't dmca the extension.

@mirh
Copy link
Author

mirh commented May 12, 2018

@KolbyClark what about your bgp.js instead?

@KolbyClark
Copy link

@mirh I'm in the same sort of position. My code was all written by me and while I do consume an API that CR uses for their apps, that shouldn't really count. Nevertheless I contacted CR and the head of CS said "we can't give permission to post the source code" which is odd, since it is my code and I wouldn't need their permission to post anything. It is pretty stupid but I also didn't want to risk legal trouble by fighting it, so I just deleted my repo.

@mirh
Copy link
Author

mirh commented May 13, 2018

Those dudes seem pretty keen with wrong notices tbh.

@Blightwidow
Copy link
Collaborator

Classic not flagging wrong content and blackmail

@onestay
Copy link
Owner

onestay commented May 13, 2018

"Apparently, the only evaluation Remove Your Media LLC performed was to look for similarities in page titles and URLs without evaluating the actual page content and felt that was adequate for evidence of copyright infringement." That definitely seems super shady. I'll go ask some people that know more about this than I do.

@Dunky13
Copy link

Dunky13 commented Feb 2, 2019

Any updates on this by any chance?

@onestay onestay closed this as completed Feb 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants