Live data from Hacker News

DMCA Copyright Complaint to Google

chillingeffects.org

11–20 of 168 posts

Re: DMCA Copyright Complaint to Google

#11
http://www.google.com/transparencyreport/removals/copyright/...

That page shows all the dmca requests to google that target github.com. Wicked pictures shows up in a number of requests but they are by no means the only copyright holder issuing requests.

You can click through to the request pages and get links to chilling effects and it will also tell you which URLs were requested that were _not_ taken down. ChillingEffects just reports on the requests, not the actions.

Re: DMCA Copyright Complaint to Google

#12
post #4

This removes a variety of projects from Google search results, including ones from Mozilla (specifically, Rust), Facebook, Yahoo, Netflix, openSUSE, as well as github documentation, e.g. - https://github.com/yahoo/pure - https://github.com/rust-lang/cargo - https://github.com/openSUSE/wicked - https://github.com/Netflix/Lipstick - https://github.com/facebook/rebound - https://help.github.com/articles/dealing-with-non…

I wonder if a bunch of these companies might get together and sue the sender of take down for defamation, loss of business, something.

Knowingly filing a false takedown is a crime, but it's pretty hard to prove. This isn't really defamation.

Re: DMCA Copyright Complaint to Google

#13
post #12

Earlier quoted context omitted.

I wonder if a bunch of these companies might get together and sue the sender of take down for defamation, loss of business, something.

Knowingly filing a false takedown is a crime, but it's pretty hard to prove. This isn't really defamation.

Legal question - If you send a bad DMCA and can't be proven to have sent it in bad faith (so the penalties under that law don't apply), could you still be sued for negligence, loss of business, etc etc? I.e. you didn't break the federal law, but you still damaged me.

Re: DMCA Copyright Complaint to Google

#14
Have submitted a counter-complaint (#2-4109000005746) for the following:

# curl https://www.chillingeffects.org/notices/10275257 | grep github

     https://help.github.com/articles/dealing-with-non-fast-forward-errors/
     https://github.com/Zizzamia/ng-tasty
     https://github.com/zen-kernel/zen-kernel
     https://github.com/yahoo/pure/releases/
     https://github.com/yahoo/pure
     https://github.com/YabataDesign/afterglow-theme
     https://github.com/wet-boew/wet-boew
     https://github.com/wearefractal/glob-watcher
     https://github.com/wanderlust/wanderlust
     https://github.com/thombergs/wicked-charts
     https://github.com/Thibauth/python-pushover
     https://github.com/tcnksm/vagrant-pushover
     https://github.com/substack/pushover
     https://github.com/SteveSanderson/knockout-es5
     https://github.com/sps/pushover4j
     https://github.com/sensu/sensu-community-plugins/blob/master/handlers/notification/pushover.rb
     https://github.com/schneems/wicked/wiki/Testing-Wicked-with-RSpec
     https://github.com/schneems/wicked
     https://github.com/satyr/coco
     https://github.com/satyr
     https://github.com/sampsyo/beets/issues/546
     https://github.com/rust-lang/cargo
     https://github.com/rniemeyer/knockout-delegatedEvents
     https://github.com/rniemeyer/knockout-amd-helpers
     https://github.com/qbit/node-pushover
     https://github.com/openSUSE/wicked/issues/432
     https://github.com/openSUSE/wicked
     https://github.com/Nuku/Flexible-Survival/blob/master/Stripes/Candy
     https://github.com/Netflix/Lipstick
     https://github.com/nemomobile/lipstick
     https://github.com/mrmrs/colors
     https://github.com/mirage
     https://github.com/mileszs/wicked_pdf/issues/78
     https://github.com/LubosD/darling
     https://github.com/laprice/pushover
     https://github.com/kryap/php-pushover
     https://github.com/krisselden/broccoli-sane-watcher
     https://github.com/Knockout-Contrib/Knockout-Validation
     https://github.com/knockout/knockout
     https://github.com/knockout
     https://github.com/kirang20/wgxp-java-rosa
     https://github.com/jreese/znc-push/blob/master/doc/pushover.md
     https://github.com/jnwatts/pushover.sh
     https://github.com/jfinkels/flask-restless/
     https://github.com/jasonlewis/resource-watcher
     https://github.com/huxi/lilith
     https://github.com/hannorein/rebound
     https://github.com/gregghz/Watcher
     https://github.com/feuerbach/tasty
     https://github.com/facebook/rebound-js
     https://github.com/facebook/rebound
     https://github.com/erniebrodeur/pushover
     https://github.com/entertailion/Fling/blob/master/README.md
     https://github.com/enkydu/raspi_runner
     https://github.com/dyaa/Laravel-pushover
     https://github.com/danesparza/Pushover.NET
     https://github.com/crazed
     https://github.com/callmenick/css-loaders-spinners-2/tree/master/js
     https://github.com/callmenick/css-loaders-spinners-2
     https://github.com/allure-framework/allure-core
     https://github.com/abrt/satyr
Thanks for reaching out to us!

We have received your legal request. We receive many such complaints each day; your message is in our queue, and we'll get to it as quickly as our workload permits.

Due to the large volume of requests that we experience, please note that we will only be able to provide you with a response if we determine your request may be a valid and actionable legal complaint, and we may respond with questions or requests for clarification. For more information on Google's Terms of Service, please visit http://www.google.com/accounts/TOS

Regards,

The Google Team

Re: DMCA Copyright Complaint to Google

#15
This is most likely due to a script screwing up. A lot of these companies retain companies that specialize in filing these requests (see: www.google/com/transparencyreport/removals/copyright/faq/ for some more details.

My limited understanding is that these companies just use google search apis to try to find search results matching keywords. Then they file requests for every matching url. This is how obviously wrong requests show up.

There are also cases where requests appear to be malicious, but there are really no consequences since you (iirc) have to prove bad faith which is next to impossible and since everything is being adjudicated via third parties, there is really no incentive.

Re: DMCA Copyright Complaint to Google

#16
post #6

Have submitted a counter-complaint (#2-4109000005746) for the following: # curl https://www.chillingeffects.org/notices/10275257 | grep github https://help.github.com/articles/dealing-with-non-fast-forward-errors/ https://github.com/Zizzamia/ng-tasty https://github.com/zen-kernel/zen-kernel https://github.com/yahoo/pure/releases/ https://github.com/yahoo/pure https://github.com/YabataDesign/afterglow-theme https://gi…

Google should raise the bar for those who abuse the DMCA system like this. Maybe require submissions to be in writing, and notarized.

Re: DMCA Copyright Complaint to Google

#17
post #4

This removes a variety of projects from Google search results, including ones from Mozilla (specifically, Rust), Facebook, Yahoo, Netflix, openSUSE, as well as github documentation, e.g. - https://github.com/yahoo/pure - https://github.com/rust-lang/cargo - https://github.com/openSUSE/wicked - https://github.com/Netflix/Lipstick - https://github.com/facebook/rebound - https://help.github.com/articles/dealing-with-non…

Actually, this was sent by "Takedown Piracy LLC" working on behalf of Wickedpictures. They file DMCA notices by the truckload according to the results I get in Chilling Effect's search, so you can safely assume they're a DMCA notice spammer.

Unfortunately, it does not list the individual lawyer who signed off on this complaint, or I would be tempted to draft a letter to their local bar association pointing out how careless they are, as no reasonable person could mistake Github's documentation for a porno movie.

Re: DMCA Copyright Complaint to Google

#18
post #12

Earlier quoted context omitted.

Knowingly filing a false takedown is a crime, but it's pretty hard to prove. This isn't really defamation.

Legal question - If you send a bad DMCA and can't be proven to have sent it in bad faith (so the penalties under that law don't apply), could you still be sued for negligence, loss of business, etc etc? I.e. you didn't break the federal law, but you still damaged me.

I don't see why not

Re: DMCA Copyright Complaint to Google

#19
post #4

This removes a variety of projects from Google search results, including ones from Mozilla (specifically, Rust), Facebook, Yahoo, Netflix, openSUSE, as well as github documentation, e.g. - https://github.com/yahoo/pure - https://github.com/rust-lang/cargo - https://github.com/openSUSE/wicked - https://github.com/Netflix/Lipstick - https://github.com/facebook/rebound - https://help.github.com/articles/dealing-with-non…

I wonder how these pages got picked up. If Wickedpictures is doing some type of Natural Language processing to identify these pages as their content, it would be interesting to analyze the content of these pages and reverse-engineer Wickedpictrue's system.

Then of course, you could package that reverse-engineering work as a service that will insert red-herring comments in source code to set off the automated DMCA takedowns, creating a free semi-private repository on github.

Re: DMCA Copyright Complaint to Google

#20
post #12

Earlier quoted context omitted.

Knowingly filing a false takedown is a crime, but it's pretty hard to prove. This isn't really defamation.

Legal question - If you send a bad DMCA and can't be proven to have sent it in bad faith (so the penalties under that law don't apply), could you still be sued for negligence, loss of business, etc etc? I.e. you didn't break the federal law, but you still damaged me.

(I am not a lawyer, but did read coverage of the SCO lawsuit extensively)

Falsely claiming to hold copyright in a work to which you do not hold copyright may open the possibility for slander of title (which was one of the claims in the SCO lawsuit).

I would be interested to see some sufficiently-deep-pocketed entity try to use that to turn an automated-DMCA-complaint house into a smoking hole in the ground, pour encourager les autres.

Post reply on HN