linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mikeeusa@redchan.it
To: GitHub Staff <support@github.com>
Cc: linux-kernel@vger.kernel.org, esr@thyrsus.com, misc@openbsd.org
Subject: Re: DMCA takedown notice
Date: Sat, 16 Mar 2019 03:21:02 +0000	[thread overview]
Message-ID: <72d085e3d1e9c2abf1967ceb40c3f988@redchan.it> (raw)
In-Reply-To: <discussions/31b6c69e24b211e98081e6b282f84ff2/comments/5870232@github.com>

I am going to sue your staff for contributory copyright infringement in 
their personal capacity, in addition to you company.
I have given you ample notice to remove the work.

> Moreover, you have not addressed other doctrines, such as reliance or 
> promissory estoppel, which would prevent revocation even in the absence 
> of valuable consideration.

These are equitable defenses. Not defenses-at-law. They are determined 
on a case by case basis. Promissory estoppel is most often "awarded" 
when a defendant has, on the reliance of explicit promises to him by the 
owner, laid out monies to purchase improvements for the affected 
property.

An example is when one builds extra buildings on a piece of land one was 
promised ownership on upon the owners death.  It is much related to the 
old Livery of Seisin which was used in the conveyance of land and is, in 
fact, a modern substitute for it.

There is little relevance between such and a licensee, one of many, who, 
for no outlay, had permission to use a piece of software. Permission 
which was later revoked.

> Similarly, based on the information you've provided, we are unable to
> locate facts which would support for your argument that any of the GPL
> licensed code here was granted that license without an exchange of
> valuable consideration.

The John Doe would have to prove that there was a contract, it is not 
me, the copyright holder, who's duty it is to show that there was none.
One cannot prove a negative. You know this very well.
It is the consideration (payment) that would create a contract which a 
licensee could attempt to rely upon.
Where there is no such consideration there is no contract.

Here the John Doe admitted that he simply downloaded the work and also 
admitted that there was no contract between him and I
"Thank God", he added.

This is attested to in the original complaint, the John Doe is quoted, 
and his testimony is linked.
However it is not my duty to prove to you that there is _not_ any 
consideration.

That is proving a negative. It is a duty of the John Doe's defense to 
prove that there is such a payment, which there is not.
I was never paid by the John Doe.

You are being completely disingenuous here. You think you are clever, 
but you will be sorry once my legal bill is being paid out of your 
personal expenses for your blatant copyright infringement of my work. 
The courts won't think you're "cute" or "clever".

I have addressed your claim that my signature was invalid. Your 
understanding of what is required of a signature and the purpose of a 
signature is incorrect. A signature simply shows assent of the party to 
the validity of the document. An X is sufficient. Here I have chosen to 
use my long-held pen name, MikeeUSA. I have also published these notices 
at the place of the publication of the work, to give further 
confirmation.

https://sourceforge.net/projects/gpcslots2/
https://sourceforge.net/projects/gpcslots2/files/notes/

Forewarned is forearmed.

Sincerely,
Signed,
--MikeeUSA--


On 2019-03-07 02:30, GitHub Staff wrote:
> Hi MikeeUSA,
> 
> I've done my best to address your concerns below. Until you provide a
> complete DMCA takedown notice, we are unable to act on your request.
> 
>> My publishing of these notices on my long-held sourceforge account,
>> along side the download link is sufficient for a reasonable person
>> to conclude that I, the author of the program, am the issuer of the
>> request.
> 
> As explained in our previous email, that is not the standard required
> by 17 U.S.C. 512(3)(a)(i).
> 
>> I have chosen to do so in rescinding the license of the John Doe.
> 
> Based on the information you've provided, we are unable to determine
> that any valid license revocation has taken place here.
> 
>> A license, that is not supported by an interest, is revocable ...
>> An interest attaches when a licensee pays
>> the copyright holder for the receipt of a license, or transmits 
>> valuable
>> bargained-for consideration to the copyright holder. Absent such 
>> anattached
>> interest there exists only a revocable-at-will bare license.
> 
> Similarly, based on the information you've provided, we are unable to
> locate facts which would support for your argument that any of the GPL
> licensed code here was granted that license without an exchange of
> valuable consideration. Moreover, you have not addressed other
> doctrines, such as reliance or promissory estoppel, which would
> prevent revocation even in the absence of valuable consideration.
> 
>> The url you link to advances a false legal theory unsupported under US
>> Jurisprudence.
> 
> While they are in easily-missed footnotes, the linked article contains
> citations to three cases which support their respective underlying
> legal theories. Please note the article is provided for informational
> purposes, and GitHub is unable to give legal advice about open-source
> licensing or copyright questions.
> 
> If you would like to revise your notice to include the required
> details, please send back the entire revised notice, and not only the
> corrected
> sections. Once we've received a complete and actionable DMCA notice,
> we will process it expeditiously.
> 
> Thanks,
> 
> GitHub Staff

  parent reply	other threads:[~2019-03-16  3:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5c51daed7c023_2fcf3fe7576d45c417207b@github-lowworker-89d05ac.cp1-iad.github.net.mail>
     [not found] ` <5c51ee838b18f_74e53fd6ff0d45c41780e2@github-lowworker-5909e27.cp1-iad.github.net.mail>
     [not found]   ` <5c522f5b6cb8a_60733fc5256d45b412831@github-lowworker-39ccb07.cp1-iad.github.net.mail>
     [not found]     ` <5c534f0336ca6_19ae3fcbf5cd45b4186161@github-lowworker-e55e3e3.cp1-iad.github.net.mail>
     [not found]       ` <5c535110f0f30_3aa13fafe46d45c4222962@github-lowworker-dcc078e.cp1-iad.github.net.mail>
2019-02-01  4:38         ` DMCA takedown notice - GPC-Slots 2 (after GPL Revocation from "John Doe") mikeeusa
     [not found]           ` <5c5489478eb20_56f33fd9e9ad45b43146ec@github-lowworker-4f62d42.cp1-iad.github.net.mail>
     [not found]             ` <5c55ecdcb298_3a283fd6dfcd45c4309246@github-lowworker-63e61ec.cp1-iad.github.net.mail>
     [not found]               ` <5c563190ae6cc_18c33fcb464d45bc1523b0@github-lowworker-39ccb07.cp1-iad.github.net.mail>
     [not found]                 ` <5c586b095281b_4c6d3ffba28d45b8120450@github-lowworker-e51511d.cp1-iad.github.net.mail>
     [not found]                   ` <5c58a56f8ded7_36e93f9cb4ad45b8932e7@github-lowworker-e55e3e3.cp1-iad.github.net.mail>
     [not found]                     ` <312c3d91f6c4a71c34b96728a2efb385@redchan.it>
     [not found]                       ` <5c5b1609a1561_1ac23fbe2d6d45b88762d0@github-lowworker-dcc078e.cp1-iad.github.net.mail>
     [not found]                         ` <discussions/31b6c69e24b211e98081e6b282f84ff2/comments/5812163@github.com>
2019-02-11 23:10                           ` DMCA takedown notice mikeeusa
2019-03-06  4:48                             ` Martin Schroeder
2019-03-21 23:15                               ` mikeeusa
2019-03-21 23:20                               ` DMCA takedown notice - Reply to Martin Schroeder mikeeusa
     [not found]                           ` <d6326acd7a9a52a5cf4de2bd3841fc5c@redchan.it>
     [not found]                             ` <discussions/31b6c69e24b211e98081e6b282f84ff2/comments/5851873@github.com>
2019-03-06  2:08                               ` DMCA takedown notice mikeeusa
     [not found]                               ` <1ad00463db02ac58f89c4ac99b2299e4@redchan.it>
     [not found]                                 ` <CAKSHBJW4qkrozz0HrWvXnbpHicSBRoRKycC7xBoK0uWZJx5NkQ@mail.gmail.com>
     [not found]                                   ` <discussions/31b6c69e24b211e98081e6b282f84ff2/comments/5870232@github.com>
2019-03-16  3:21                                     ` mikeeusa [this message]
2019-04-03 11:24                                     ` License revocation from GitHub and GitHub Staff (regarding GPC-Slots 2) " mikeeusa
2019-04-26 10:56                               ` GPL Is Revocable - 4chan discussion mikeeusa
2019-05-03 19:31                               ` Free Licenses are revocable by the Copyright holder mikeeusa
2019-03-06  2:10 DMCA takedown notice mikeeusa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72d085e3d1e9c2abf1967ceb40c3f988@redchan.it \
    --to=mikeeusa@redchan.it \
    --cc=esr@thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=misc@openbsd.org \
    --cc=support@github.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).