Jump to content

agaricus

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by agaricus

  1. Sorry if I was unclear. I mean someone has taken your game, album, movie, etc. and hosted it on their website. Their result may be the first thing that comes up when you google your movie, but google won't do anything about it. They have no responsibility to, they're not doing anything wrong, and they don't care. The correct action is to talk to the person's webhost, to the person themselves, to the government, to your lawyer. The correct action is not to talk to google, because they will do nothing.

    Actually Google will remove links to allegedly infringing content when reported. Copyright removal requests can be sent from http://www.google.com/dmca.html and they have published a report with more details of their process:

    How many of these requests did you comply with?

    We removed 97% of search results specified in requests that we received between July and December 2011.

    How quickly do you remove search results after a request is made?

    We remove search results that link to infringing content in Search when it is brought to our attention, and we do it quickly. As of December 2012, our average processing time across all removal requests submitted via our web form for Search is approximately 6 hours. However, many different factors can influence the processing time for a particular removal request, including the method of delivery, language, and completeness of the information submitted.

    Google as an "information location tool" online service provider chooses to operate under the DMCA safe harbor provision in 17 USC § 512(d):

    (d) Information Location Tools. — A service provider shall not be liable for monetary relief, or, except as provided in subsection (j), for injunctive or other equitable relief, for infringement of copyright by reason of the provider referring or linking users to an online location containing infringing material or infringing activity, by using information location tools, including a directory, index, reference, pointer, or hypertext link, if the service provider —

    (1)(A) does not have actual knowledge that the material or activity is infringing;

    (B) in the absence of such actual knowledge, is not aware of facts or circumstances from which infringing activity is apparent; or

    © upon obtaining such knowledge or awareness, acts expeditiously to remove, or disable access to, the material;

    (2) does not receive a financial benefit directly attributable to the infringing activity, in a case in which the service provider has the right and ability to control such activity; and

    (3) upon notification of claimed infringement as described in subsection ©(3), responds expeditiously to remove, or disable access to, the material that is claimed to be infringing or to be the subject of infringing activity, except that, for purposes of this paragraph, the information described in subsection ©(3)(A)(iii) shall be identification of the reference or link, to material or activity claimed to be infringing, that is to be removed or access to which is to be disabled, and information reasonably sufficient to permit the service provider to locate that reference or link.

    You may have noticed "In response to a complaint we received under the US Digital Millennium Copyright Act, we have removed 1 result(s) from this page." notices on some of your search results; this is why (but interestingly, most of the takedown notices are available on Chilling Effects and contain URLs of the allegedly infringing content in question – provided by the copyright owner themselves).

  2. Why isn't it hosted on technicpack.net any longer?

    Technical reasons mainly related to dependencies: MCPC+ heavily depends on the SpecialSource remapping tool developed by md_5 for NMS plugin support; he kindly offered hosting on his Jenkins so MCPC+ can automatically rebuild when SpecialSource is updated, pulling from the latest Maven snapshots (with MCPC-API as well). No anti-technic conspiracy here, promise. In fact we were originally going to keep both the build.technicpack.net and ci.md-5.net Jenkins active for MCPC+, and had them both online for a while, but because of the way the builds are kicked off the build numbers would necessarily desynchronize, resulting in confusion. The original hosting at Technic is very much appreciated but using md_5's makes more sense going forward.

    So be sure to grab the latest builds from http://ci.md-5.net/job/MCPC-Plus/ from now on, wouldn't want any bug reports from old builds since fixed, the new builds are much better =)

×
×
  • Create New...