The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780
Date: Wed, 15 Mar 2023 20:55:35 -0500	[thread overview]
Message-ID: <20230316015535.26hepjsjee3kfsi2@illithid> (raw)
In-Reply-To: <CAFH29tptXfuTPCzU3LgoRgWD60qBHuKqb=5MNOTO4Tnrbm1xCA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3684 bytes --]

[replying only to list]

At 2023-03-15T20:36:06-0400, Rich Salz wrote:
> > Yea. However, there could be novel, perhaps untested, legal theories
> > one could use in this circumstance.
> 
> All you need is one person who can claim (or show) that they are a
> copyright holder to serve TUHS with a DMCA take-down, and kiss this
> group goodbye.

Speaking here as an observer of many DMCA fights over the past ~25
years, having become politically animated by it at the time of the law's
passage, but not as a person qualified to give legal advice (because I'm
not a lawyer)...

I would counsel against this sort of pessimism.  Sites survive DMCA
takedown notices all the time.  (Part of) the point of the takedown
notices prescribed by the DMCA is that if you comply with one, your
liability ends there.  Your whole site doesn't have to die, just the
infringing material.

https://www.legalzoom.com/articles/i-got-a-dmca-notice-now-what

Secondly, in a situation of obvious historical and educational
interest[1], arguably low commercial impact, and almost certainly no
meaningful trade secret implications[2], it's an issue worth
pursuing--if not on the TUHS site, then perhaps one set up for this
express purpose.

Thirdly, a DMCA takedown notice has specifically identify the allegedly
infringed work and the copyright holder.  For cases where the chain of
title is unclear or complicated by a multi-party revision history, this
may not so easily be asserted with confidence to a standard that would
satisfy the DMCA law.  How much money did IBM and SCOX(E) spend on this
very issue, with it _still_ remaining unresolved?  My guess is "more
than a rights holder could possibly hope to recover in damages even in a
lunatic fringe fantasty".

Fourthly, a DMCA takedown notice can be challenged with a
counter-notice.  If the takedown notice is defective, serving
counter-notice often (usually?) disposes of the issue for practical
purposes.[3]  The Electronic Frontier Foundation has taken on cases like
this, and won.  Doubtless many defective or even fraudulent takedown
notices have been successful because the recipient lacked the courage to
respond, demanding clarification as they are entitled to under the law.

Protecting ordinary Internet users and business from investigation,
seizure, and litigation by overbearing private firms and the government
agencies to which they've outsource enforcement is EFF's literal origin
story.[5]

They also happen to have attorneys-at-law, and _can_ dispense legal
advice.

Regards,
Branden

[1] https://en.wikipedia.org/wiki/Lenz_v._Universal_Music_Corp.

[2] I trust we all recall the amusement of reading the source to the
    System V "true" and "false" shell scripts on many thousands of
    machines accessible to college undergraduates, which were proclaimed
    as highly sensitive "UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T" or
    similar verbiage.

[3] It may be impossible to know any real data here.  Like the use of
    deadly force by U.S. police agencies[4], there is no reporting
    requirement for issuance of DMCA takedown notices, and almost
    certainly no interest among institutional copyright holders and
    their trade cartels (the MPAA, the RIAA, etc.) to report reception
    of counter-notices and the success rate of counter-notices at
    voiding the takedown notice.  (You can be sure we'd hear all about
    it if the success rate were extremely low.)

[4] https://www.cnn.com/2018/09/30/us/police-use-of-force-legislation/index.html

[5] https://en.wikipedia.org/wiki/Steve_Jackson_Games,_Inc._v._United_States_Secret_Service

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-03-16  1:55 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 11:59 Noel Chiappa
2023-03-15 21:03 ` Warren Toomey via TUHS
2023-03-15 21:08   ` Clem Cole
2023-03-15 21:15     ` Luther Johnson
2023-03-15 21:18     ` Seth Morabito
2023-03-15 21:22       ` Larry McVoy
2023-03-15 21:27         ` Clem Cole
2023-03-15 21:38           ` KenUnix
2023-03-16 23:18             ` Clem Cole
2023-03-16 23:48               ` Charles H. Sauer (he/him)
2023-03-17  1:08                 ` Steve Nickolas
2023-03-15 21:46           ` Steve Nickolas
2023-03-15 21:50         ` Luther Johnson
2023-03-15 21:56         ` steve jenkin
2023-03-15 22:15           ` Larry McVoy
2023-03-15 23:30           ` Warner Losh
2023-03-15 23:41             ` Luther Johnson
2023-03-16  0:29               ` Warner Losh
2023-03-16  0:36                 ` Rich Salz
2023-03-16  1:55                   ` G. Branden Robinson [this message]
2023-03-16 21:14                   ` Dave Horsfall
2023-03-17  0:33                     ` Rich Salz
2023-03-17  1:03                       ` [TUHS] copyright (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17  1:05                       ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 segaloco via TUHS
2023-03-17  2:03                         ` G. Branden Robinson
2023-03-17  3:17                           ` Dave Horsfall
2023-03-17  3:30                             ` [TUHS] Reply-To and Mail-Followup-To (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17 15:12                               ` [TUHS] " Pete Turnbull
2023-03-17 15:33                                 ` segaloco via TUHS
2023-03-17 16:42                                   ` Steve Nickolas
2023-03-17 18:27                                     ` Marc Donner
2023-03-16  1:15               ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Larry McVoy
2023-03-16  2:14                 ` Luther Johnson
2023-03-15 23:44             ` Brad Spencer
2023-03-16  4:37         ` Dave Horsfall
2023-03-15 23:56   ` [TUHS] Re: OSF/1.0 Sources Joseph Holsten
2023-03-17  2:28   ` [TUHS] Re: UNIX System V Warren Toomey via TUHS
  -- strict thread matches above, loose matches on Subject: below --
2023-03-15 22:25 [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Noel Chiappa
2023-03-15 22:39 ` segaloco via TUHS
2023-03-15  0:59 Noel Chiappa
2023-03-15  8:05 ` arnold
2023-03-15  8:52   ` Dave Horsfall
2023-03-15 11:09     ` KenUnix

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=20230316015535.26hepjsjee3kfsi2@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).