|
Grex > Coop11 > #174: A motion to protect Grex from copyright infringement suits. | |
|
| Author |
Message |
| 25 new of 78 responses total. |
aruba
|
|
response 36 of 78:
|
Jun 6 02:45 UTC 2000 |
I agree with John.
|
gelinas
|
|
response 37 of 78:
|
Jun 6 03:41 UTC 2000 |
Y'know, Senators and Representatives get to edit their comments as they
appear in the Congressional Record, adding or deleting as they see fit.
Why should members (and other uses) of grex not have the same privilege?
|
i
|
|
response 38 of 78:
|
Jun 6 04:33 UTC 2000 |
Re #37: Remember the scandal of the House Bank? Most grexers don't want
to feel that we're the same kind of self-serving scum that Congressmen are.
I know less about the law than remmers, but i share his feeling that the
conference logs on grex are, in some senses, both public records and press
accounts of public events. If i write a speach, file for copyright, and
openly read the speach in the town square, then my copyright either must
or should have to give way (to some extent) to the freedom of the press.
I feel that the same applies here on grex.
|
jmsaul
|
|
response 39 of 78:
|
Jun 6 04:50 UTC 2000 |
Sigh. Congresspersons have a responsibility to the public that mere members
of the public like us do not. This isn't a deliberative body, and none of
us represent anyone but ourselves. We're private citizens, not public
figures. The idea that it's somehow immoral for us to delete our own words
from a computer BBS because it's immoral for elected officials to tamper with
public records is frankly bizarre. It borders on the surreal.
You can feel that conference items are public records as strongly as you like,
but the rest of the public -- and the genuine legislators -- do not agree.
|
md
|
|
response 40 of 78:
|
Jun 6 12:32 UTC 2000 |
I was astonished to learn that a Grex item of
mine got copied and pasted -- item number, item
header, my name, my "md" id and all -- into a
YAPP bbs in Austin TX. How public is that?
|
jmsaul
|
|
response 41 of 78:
|
Jun 6 13:33 UTC 2000 |
I didn't know there were any YAPP BBSes in Austin TX.
|
janc
|
|
response 42 of 78:
|
Jun 6 18:00 UTC 2000 |
Sounds like Paul Terry Walhaus's system, The Spring. Didn't know that
still existed. Yup, it does - http://www.spring.net
http://208.165.85.156/yapp-bin/public/read/movies/12 seems to be the
md item - a list of oscar nominees, which Paul Terry Walhus seems to
have imported from Grex.
|
mwg
|
|
response 43 of 78:
|
Jun 6 18:19 UTC 2000 |
I repeat, pulling copyright in to inappropriate places is a bad idea. But
if you must, consider this: Anyone with the computer sophistication to
get into a system like Grex is aware that anything they place in
discussion sections *WILL* be seen all over the world. Posting here is
like feeding your words into an on-demand printing press, then deciding
after 5000 copies have been mailed all across the world, to filch the
printing plates out of the machine.
If people are going to insist on thumping copyright law on this, simply
create a policy that says that text entered by its' creator in public
areas of Grex is placed in the public domain, without asserting any rights
over copyright material that may be posted without the consent of the
owner. If someone wanted to expose something on Grex and still retain
any semblance of copyright, they could post a file pointer to a non-public
space, the pointer would become public domain, but the file could always
be removed later.
Several people will point out that they will leave if this is implemented.
The existance of the argument pretty much indicates that some of the
losers will leave no matter what the winning position is. Accept that
this issue will drive some people away and opt for the smooth running of
Grex.
The coffee is hot.
|
aaron
|
|
response 44 of 78:
|
Jun 6 18:24 UTC 2000 |
It doens't matter if the text can be seen all over the world. You can
go buy a book that can be purchased all over the world -- it isn't
public domain. You can go to a movie that can be seen all over the world --
it isn't public domain. You can watch a TV show that can be viewed all
over the world -- it isn't public domain.
And in each of those cases, the copyright holder can at any time "filch"
the printing plates. Because it is the copyright holder's intellectual
property.
|
jmsaul
|
|
response 45 of 78:
|
Jun 6 18:49 UTC 2000 |
Re #43: Ah, a restatement of the "only people who are computer experts
and never make mistakes should post on BBSes" argument. You
even included the obligatory silly analogy to other types of
communication that aren't really analogous. Perfect example
of the form.
|
remmers
|
|
response 46 of 78:
|
Jun 6 23:05 UTC 2000 |
I'm not going to attempt to argue with lawyers about what the law
is, but I'll stand by what I said regarding what the law should
and shouldn't be.
Here's a hypothetical for y'all: Suppose a user posts some responses,
time passes, the user stops logging in, and the account lapses. The
user then no longer has the technical ability to exercise the
scribble command on the responses. Suppose the user later decides
he wants to delete the text and is able to furnish reasonable proof
that he is the person who posted it. Is the staff obligated to
scribble the text or enable the user to do so?
|
void
|
|
response 47 of 78:
|
Jun 6 23:21 UTC 2000 |
absolutely.
grex is not a governing body and has no authority to establish law,
no matter what its users might think of various laws already extant.
|
remmers
|
|
response 48 of 78:
|
Jun 6 23:34 UTC 2000 |
(Of course Grex can't establish law.)
|
other
|
|
response 49 of 78:
|
Jun 6 23:36 UTC 2000 |
Ok, now suppose the same case as remmers presents in resp:46 except that
the user is *not* able to prove their identity, but argues vehemently the
case that the posted text is theirs and is to be removed. Have they a
legal leg to stand on should they pursue legal remedy? Is Grex staff in
any way obligated to respond to the demands presented sans proof of
identity?
|
jmsaul
|
|
response 50 of 78:
|
Jun 7 01:27 UTC 2000 |
As I explained in the agora.cf where remmers also posted this, the same thing
could happen under your current policies. The only difference would be
whether it would be possible to see the responses in /bbs/censored or not.
If that hypothetical is intended to be any kind of argument against closing
the censored log or deleteing responses entirely, it falls flat.
Re #49: Regardless of what happens to scribbled comments, Grex could be
forced by court order to scribble someone's comments if someone
were really willing to go to the trouble -- and could also be
forced to delete them entirely even if scribble doesn't do that.
It would, however, require proof of the person's identity -- and
before you all jump in with "Aha! You can't prove who anyone is
on the Internet, so it could never happen!", keep in mind that the
standard for proof in civil cases is not absolute certainty, but
merely "the preponderance of the evidence."
So what you're saying if you keep the scribble command the way it
is is not "you can't remove text, and we won't do it either,"
but instead "you can't remove text unless you're enough of an
asshole to sue us over it, in which case we'll take it out for
you." Not the message I'd want to send, but what the hey...
|
other
|
|
response 51 of 78:
|
Jun 7 14:29 UTC 2000 |
OK, so in an effort to actually move this debate into the realm of
practical movement, let's look at the following options, which I think
cover all the choices being promoted in this discussion:
- Do nothing.
- Change nothing, but inform users a) that scribble saves to a publicly
readable file, and b) how to read it.
- Make /bbs/censored readable by staff only (whether or not we make
additional policy regarding how staff may access/use file contents).
- Disable/remove scribble entirely.
- Link /bbs/censored to /dev/null so that scribble actually completely
removes responses (without consideration of whether removed responses
have already been copied and/or reposted).
Now if everyone will please pick one of the above and make a condensed
argument for why this is the best choice for Grex, instead of picking
apart the choices everyone else is making, is it possible that we can
actually get done with this and make it go away?
If you're viewing this in picospan, apparently the list is not
numbered, as it is in backtalk. You can refer to the choices by number
(1 through 5). -- Jan, is there any particular reason why backtalk
translates <ol> identically to <ul> for picospan?
|
jmsaul
|
|
response 52 of 78:
|
Jun 7 15:11 UTC 2000 |
Good summary. You did leave one out, though:
* Have the scribble command completely delete responses, but leave a note
in their place telling who did the scribbling and when.
Condensed argument: People own their responses, and should be allowed to
remove them from the system. This is especially important in situations where
they've entered something they later have reason to regret, and/or where the
response in question causes harm to a third party (e.g. infringes their
privacy), but is really a basic principle. (As well as one backed by
copyright law.) Refusing to allow posters to remove responses from public
view also raises questions as to whether Grex could become liable as a
publisher for libelous material or material that invades privacy. (Grex
would already be liable for material that infringes copyright, because the
ISP immunity doesn't apply there, but Grex's existing "removal of illegal
material" policy could be stretched to cover that.)
Whether Grex retains a staff-access-only copy of removed responses is a
separate issue. The benefit for retaining one is that it permits
responses to be restored if necesary (such as if someone makes an account
with the same name as a previously expired one and kills old responses).
The downside is that, should a legal dispute involving response text ever
occur, it makes Grex a target -- both for lawsuits about the disposition
of the text and for requests for access to it. Should Grex be in the
position of maintaining records useful for suing its users, and should
Grex put itself in opposition to a user who wants the text to really be
gone for good? Does the possible benefit of being able to restore
responses outweigh that? I'd lean toward removing the material
completely, but see the merit in keeping it staff-accessible as well.
|
other
|
|
response 53 of 78:
|
Jun 7 15:38 UTC 2000 |
Thank you. I think that your suggested additional option would be an
improvement over the existing option of making scribble actually remove
responses, rather than a separate option. The "who" would be obvious,
but adding a "when removed" would be valuable, as seen in context of the
dates of the adjoining/subsequent responses.
Anyone else?
|
pfv
|
|
response 54 of 78:
|
Jun 7 15:41 UTC 2000 |
I especially like #52 because grex and logs are another issue.
|
remmers
|
|
response 55 of 78:
|
Jun 7 16:10 UTC 2000 |
Of the various options presented, I don't know what the best choice
is because I don't know what the law is. I've read various claims
here about what the law is and what it implies for Grex, but before
basing any policy decisions on that, I would want, at the very least,
a second opinion.
|
cmcgee
|
|
response 56 of 78:
|
Jun 7 16:13 UTC 2000 |
I like the option that really removes, but also leaves who and when in its
place.
I'm willing to discuss the destroy/save for staff eyes only as a separate
issue. I'm still undecided on that one.
|
aaron
|
|
response 57 of 78:
|
Jun 7 17:43 UTC 2000 |
re #46: Is that your way of agreeing with Mr. Bumble, albeit on a
slightly different point of law?
re #55: Opinions aren't hard to come by.
|
remmers
|
|
response 58 of 78:
|
Jun 7 17:50 UTC 2000 |
Especially around here! :)
|
janc
|
|
response 59 of 78:
|
Jun 7 21:11 UTC 2000 |
On logs:
Grex keeps lots of logs of all sorts of stuff. I can tell you every
time you logged onto Grex for the last several years. I can tell you
every backtalk button you clicked for the last week, and I can tell you
the exact x/y coordinates your mouse was at when you clicked it.
It's possible that lawyers might someday descend on us demanding some of
this data. So what? I don't see that as a reason for not keeping it or
not keeping it. Yes, it might incriminate someone, but it might also
exonerate someone. And if the data is accurate, it will tend to
incriminate the guilty and exonerate the innnocent, which is probably a
good thing on the whole.
The very idea that we should avoid knowing anything because it might
involve us in a lawsuit just doesn't make any sense to me. We aren't
running a crackhouse here. We should keep it if we think it is worth
the disk space to us, and not worry one way or the other about whether
some lawyer will someday want it.
|
jmsaul
|
|
response 60 of 78:
|
Jun 7 22:17 UTC 2000 |
Some of your users may feel differently. People who get sued, or threatened,
for things they post are not necessarily "guilty" of anything other than
having an opinion that disagrees with the opinion of someone with resources.
You should take the possible detrimental effects of keeping the censored text
around into account, weighing it against possible benefits.
|