Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DMCA Takedown Notice #321

Open
sjmcallister opened this issue Mar 15, 2016 · 22 comments
Open

DMCA Takedown Notice #321

sjmcallister opened this issue Mar 15, 2016 · 22 comments
Labels

Comments

@mausvargas
Copy link

@xaiki
Copy link
Member

xaiki commented Mar 15, 2016

We got those too, we believe they are a mistake and have ask for comments from @github. Still waiting on an answer from them.

@xaiki
Copy link
Member

xaiki commented Mar 15, 2016

As a good faith move we have removed tvapi.js that was actually never used (plan was to release a butter-api without content infringing material but then we made butter providers)

@sjmcallister
Copy link
Author

@xaiki That's good to hear. Looking forward to getting this resolved.

@xaiki
Copy link
Member

xaiki commented Mar 15, 2016

9670072

@wjin0352
Copy link

So should I just delete that repo to be done with this notice?

@xaiki
Copy link
Member

xaiki commented Mar 15, 2016

our fork count went from 720+ to 596 now, i guess most people are doing that, we're (still) waiting on comments from @github

@xaiki
Copy link
Member

xaiki commented Mar 15, 2016

@streger
Copy link

streger commented Mar 15, 2016

Don't delete the forks by yourself. If you can please reply to their email stating that the updated repo no longer contains any infringing material. If more emails come in that can only be good to diversify this issue and to make a stand against bullying.

Github has to answer positively to sent email from people that forked it since there isn't a bit of infringing content anywhere in the repository and whole think from start is completely false and just a sad attempt from MPAA to disrupt completely open source project with no connection whatsoever with popcorn-time official.

All you need to do is update your repo to be in sync with current butterproject.
How-to:
https://help.github.com/articles/syncing-a-fork/
https://help.github.com/articles/pushing-to-a-remote/

Thanks for the support.

@xaiki
Copy link
Member

xaiki commented Mar 15, 2016

FYI that's the butter project's official response to GitHub

Hello,

It has now been more than 24hours since your Takedown notice, we have
still to hear from our previous comment, but there are a few things we'd
like to point out.

It has been brought to our attention that you sent this notification to
all Butter forks, between them many of our clients that our now asking
us for answers, one notable entity that got notified is the Brazilian
the Ministry of Culture.

We understand that your quire is with the 'popcorn-official' fork of our
project, as you know we have no control of what our forks decide to do
with our code, we can't be liable for what they do nor can other people
forking us.

Exceding the fact that the DMCA is intended for hosted content violating
copyright (here the hosted content is the code, and we have 100%
copyright over the code), not to bully activities you don't like. We
Butter Project never released any app, nor had in our history a way to
'assist in a massive copyright infringement'.

Our project goal is to build great VOD streaming apps, this statement
'literally all of the Project's source code "could be used to locate
infringing material"—in fact, this is its very purpose.' is hence plane
wrong.

In a nutshell, these massive (and abusive ?) takedown notices are
harming us, our reputation, the trust we built with our customers, and
our community (went from 720 to 585 forks on butter-desktop).

Any quick analysis will show that there is absolutely no base for the
supposed infrigements:

 - https://github.com/butterproject/butter-desktop/blob/master/src/app/lib/providers/tvshowtime.js
   this a plugin for tvshowtime.com how is that infriging ? should we sent
   DMCA notices to all of it's implementations ?

 - https://github.com/butterproject/butter-desktop/blob/master/src/app/lib/providers/ysubs.js
   this file has never been part of our project.

 - https://github.com/butterproject/butter-desktop/blob/master/src/app/lib/providers/tvapi.js
   that file is a generic plugin for a 'tvapi' endpoint that is a
   freesoftware daemon with many plugins for different data sources, we
   removed that file as we weren't using anyway.

 - https://github.com/butterproject/butter-desktop/blob/master/src/app/lib/views/torrent_collection.js
   this feature, not enabled by default, allows you to drop a random
   torrent on butter, we'll look for that torrent on kat, but we don't
   pull content from kat, the torent is user provided.

 - https://github.com/butterproject/butter-desktop/blob/master/package.json
   how can this be infriging ? this is a standard entrypoint for any
   node-webkit app…

To make things clear:
- Butter never allowed to distribute copyright infringing content
- Butter is not affiliated in anyway with the popcorntime.sh fork, we
  don't know who they are.
- We ask GitHub to desist from being the tool used by bullies to cripple
  free software.
- We ask GitHub to back us up because this sets a stanza of what the
  DMCA is for: hosted-content copyright infrigement.

Cheers,
--
Niv Sardi, Founder @ Butter Project

@insertc0in
Copy link

This whole situation is being badly handled by Github, you don't just go around distributing takedown notices to unrelated repositories, at least not based on the DMCAs that they submitted in the e-mails. Fix it, @github

@pentateu
Copy link

I got it too.

I have synced my repo with butter-desktop and I have responded to github notification.

Not let's see what happens next.

@xaiki
Copy link
Member

xaiki commented Mar 16, 2016

trying to keep this thread clean from spam. please do not feed the trolls.

@xaiki
Copy link
Member

xaiki commented Mar 17, 2016

so, still no reply from @github from our comments, but it seems no repository was closed down... they haven't published the DMCA request either, so we're in the dark about this issue.

we did get a contact from @github support about an abuse (on this very thread) where we were promise a 'quick response'.

@Breaking1
Copy link

Here is a great tool for anyone who don't have the time or knowledge to write a DMCA counter notice themselves. It's a simpel counter notice generator, you just check the boxes that fits your situation and it will generate a counter notice based on the information you provided.

https://lumendatabase.org/counter_notices/new

@xaiki
Copy link
Member

xaiki commented Apr 5, 2016

thanks @Breaking1 we still think it's a mistake from @github and still are waiting to hear from them, even though their silence is somehow unsettling at this point.

@Breaking1
Copy link

Yeah, hopefully this will be resolved without any more damages. No doubt it's a mistake, i think you only got caught in the crossfire.

Maybe more people will fight GitHub and take the time to file a counter notice and stand up against this kind of bullying when they have a tool that makes it a little easier.

@alxhotel
Copy link

I think we can close this issue now.

Just for the record, DMCA takedown letter published by Github: https://github.com/github/dmca/blob/master/2016/2016-03-16-MPAA.md

@xaiki
Copy link
Member

xaiki commented Aug 23, 2016

we still have NOT recieved any official response from @github, so i'd like to keep that open for the record.

@vankasteelj
Copy link
Member

@xaiki ?

@xaiki
Copy link
Member

xaiki commented Nov 15, 2016

this is memorabilia, @github never answered us nor anyone... when we write the history of shaddy this will be exbit A

@backus
Copy link

backus commented Aug 23, 2018

this is memorabilia, @github never answered us nor anyone... when we write the history of shaddy this will be exbit A

Just wanted to say thanks @xaiki for adding this final note heh. As someone who actually does spelunk random old Github issues, historical notes are useful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests