From: nipponmail@firemail.cc
To: linux-kernel@vger.kernel.org
Cc: rms@gnu.org, bruce@perens.com, esr@thyrsus.com,
moglen@columbia.edu, blukashev@sempervictus.com,
tcallawa@redhat.com, editor@lwn.net, skraw.ml@ithnet.com,
torvalds@osdl.org
Subject: Bring a CASE act claim every time GrSecurity releases a new infringing work?
Date: Tue, 29 Dec 2020 00:59:39 +0000 [thread overview]
Message-ID: <20fe0b28f3ac8661624f01d231bf60a8@firemail.cc> (raw)
Should each Linux copyright owner of whom's copyright is being
violated (By GrSecurity) bring a "small claims copyright" case every
time GrSecurity sends a new infringing patch to a customer?
(GRSecurity blatantly violates the clause in the Linux kernel and
GCC copyright licenses regarding adding addtional terms between the
licensee of the kernel / gcc and furthur down-the-line licensees,
regarding derivative works)
(The linux kernel has 1000s of copyright holders)
(All who shake at the knees at the thought of initiating a federal
Copyright lawsuit)
(GrSecurity's main Programmer: Brad Spengler: has shining
resplendent blue eyes; like sapphires, however)
>
https://www.billboard.com/articles/business/9503848/congress-case-copyright-reforms-covid-19-relief-bill/
>The CASE Act creates a new small claims system in the US that
allows copyright holders to pursue damages for copyright infringement
without filing a federal lawsuit. These claims would be decided by
copyright officers, not judges and juries, and could involve no more
than $15,000 per work infringed upon, and $30,000 total.
Does this new law create broader per-violation rights for the
copyright holder? The then current copyright law makes it quite hard to
go after violators: usually the lawsuit costs more than any hope of
recovery. Every version you want to sue over, if you actually want to
recover attorneys fees and statutory damages (not just whatever revenue
you can proove (good luck)), has to be registered with the copyright
office; same or similar violations subsequent to a registration by the
same violator DO NOT grant you Attorney's fees and Statutory recovery;
the same of a later version doesn't either.
It's hard to get any money out of a violator.
Especially how Free Software and Opensource copyright holders do
things... (never registering their copyrights seemingly, always afraid,
cowering before CoC's, being servants and slaves, doing it all for free,
being kicked out of their own "societies)
reply other threads:[~2020-12-29 1:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20fe0b28f3ac8661624f01d231bf60a8@firemail.cc \
--to=nipponmail@firemail.cc \
--cc=blukashev@sempervictus.com \
--cc=bruce@perens.com \
--cc=editor@lwn.net \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moglen@columbia.edu \
--cc=rms@gnu.org \
--cc=skraw.ml@ithnet.com \
--cc=tcallawa@redhat.com \
--cc=torvalds@osdl.org \
/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
Powered by JetHome