From: Jurgen Botz <jurgen@botz.org>
To: Thomas Hood <jdthood@mail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SSSCA: We're in trouble now
Date: Sat, 02 Mar 2002 09:47:24 -0800 [thread overview]
Message-ID: <17085.1015091244@nova.botz.org> (raw)
In-Reply-To: Message from Thomas Hood <jdthood@mail.com> of "01 Mar 2002 19:21:01 EST." <1015028463.2276.231.camel@thanatos>
Thomas Hood wrote:
> The problem is that copy-protection will only be effective
> if you impose Soviet style restrictions on the use of computers.
>
> Certain powerful corporations want effective copy-protection.
> Ergo, those powerful corporations will want to impose Soviet
> style restrictions on the use of computers.
I think Thomas is absolutely right about this, and for now it would
seem likely that this will eventually fail if for no other reason
than that many other powerful corporations, who have little direct
interest in consumer media content protection, would find such Soviet
style restrictions an extreme inconvenience. Powerful as the media
companies may be, ultimately they are still small compared to oil,
finance, or the heavy industries.
Not that I think we should rely on or wait for any corporations whose
interests happen to be coincidentally aligned with those of private
citizens... we need to also take action as citizens to halt this
rapid descent into a new information dark age. But it as part of
this action we should try to mobilize corporate interests who
are likely to be on our side... they might move too slowly otherwise
as it takes them a while to wake up to these kinds of threats to
their self-interest when they haven't yet visibly hit their bottom
line.
:j
--
Jürgen Botz | While differing widely in the various
jurgen@botz.org | little bits we know, in our infinite
| ignorance we are all equal. -Karl Popper
next prev parent reply other threads:[~2002-03-02 17:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-02 0:21 SSSCA: We're in trouble now Thomas Hood
2002-03-02 8:35 ` Florian Weimer
2002-03-02 17:34 ` M. Edward (Ed) Borasky
2002-03-04 8:30 ` Helge Hafting
2002-03-04 9:40 ` Martin Eriksson
2002-03-04 17:02 ` Paul G. Allen
2002-03-06 4:41 ` Petro
2002-03-06 9:27 ` Helge Hafting
2002-03-02 15:30 ` Paul P Komkoff Jr
2002-03-02 21:58 ` Rik van Riel
2002-03-03 1:29 ` Greg Louis
2002-03-06 4:51 ` Petro
2002-03-02 17:47 ` Jurgen Botz [this message]
2002-03-06 5:00 ` Petro
2002-03-06 16:42 ` Alan Cox
2002-03-06 18:24 ` Paul G. Allen
2002-03-06 23:56 ` Petro
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 17:20 Ed Vance
2002-03-06 18:31 ` Paul G. Allen
2002-03-04 19:27 Jesse Pollard
2002-03-01 19:46 Paul G. Allen
2002-03-01 20:27 ` Shawn Starr
2002-03-01 20:30 ` Xavier Bestel
2002-03-01 21:29 ` Shawn Starr
2002-03-01 22:19 ` Alan Cox
2002-03-02 3:08 ` Neale Banks
2002-03-02 3:03 ` eddantes
2002-03-02 18:32 ` Alan Cox
2002-03-01 22:47 ` Florian Weimer
2002-03-02 2:59 ` Paul G. Allen
2002-03-06 4:26 ` Petro
2002-03-06 4:41 ` Trever L. Adams
2002-03-06 16:26 ` Rik van Riel
2002-03-06 17:03 ` Richard B. Johnson
2002-03-06 18:16 ` Paul G. Allen
2002-03-06 18:35 ` Trever L. Adams
2002-03-07 22:54 ` Florian Weimer
2002-03-08 2:12 ` Tom Rauschenbach
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=17085.1015091244@nova.botz.org \
--to=jurgen@botz.org \
--cc=jdthood@mail.com \
--cc=linux-kernel@vger.kernel.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