response 45 of 168:

Nov 1 23:24 UTC 2001

I'm against the bar to removing text.  I would _like_ to be able to edit
responses, but I can live without that ability.  I _really_ want the censored
log linked to /dev/null, but I can live with it being permitted only to staff
(with the definition of "staff" left open).

I intend to vote for Ken's original proposal.  Whether it passes or fails,
I will vote against Mary's, should it be put to a vote.

My arguments have not changed since last summer.  Feel free to go read them
as referenced above. :)

response 49 of 168:

Nov 2 18:18 UTC 2001

Re #45: I think having staff able to read the log is probably a 
necessary evil.

response 51 of 168:

Nov 3 05:37 UTC 2001

Jamie, I'd still like to hear what your larger goal is.  I think a lot of
people are assuming it's a destructive goal, but I'd like to hear it from
you.

response 55 of 168:

Nov 4 03:10 UTC 2001

Funny kind of obvious, that.  Taking a law that can only be used
destructively, and using it just that way.  As for corporations, the
little ones knew going that they were on the wrong end of this, much of
what the DMCA does for "protection" is not accessible to people who think
in numbers smaller than millions as a matter of course.

response 57 of 168:

Nov 4 15:08 UTC 2001

Jamie - the reason I keep asking what your larger goal is, is that I am
trying hard not to jump to conclusions.  But you're not giving me much to
work with when you never answer the question.

response 59 of 168:

Nov 5 04:52 UTC 2001

#57..I think we'll know jp2's larger goals on election day.  just watch to
see how many members nobody's ever heard of start showing up on the
members list and just happen to vote that day.

response 65 of 168:

Nov 8 03:43 UTC 2001

Some discussion of this at the board meeting made me think of some of the
implications if this passes, and how I, as a staff member would tend to want
to interpret things.  It's worth discussing these up front, since they may
influence how people want to word this.

An example of the kind of case where staff involvement might come up is this:

  User A deletes one of his postings.  User B notices the deletion, pulls a
  copy of the deleted response out of his scrollback buffer, and reposts it.
  User A asks staff to delete the copy.  What does staff do?

If this motion passed, my interpretation would be that the author of a hunk
of text has the right to withdraw it from Grex, wherever it may appear.  The
copyright remains with the author, and the author has a right to revoke any
license given in the past to Grex to publish it.

So, in the case described above I would delete the copy of the text upon
request of the original author.

Some caveats to this:

  -  I would not delete anything without an explicit request from the author.
     Grex's staff is not obligated to investigate every possible copyright
     violation to see if the poster actually had permission from the author.
     Though, of course, if I post a New York Times article, anyone (staff or
     not) who wants to is welcome to ask the New York Times if they care,
     and if the New York Times responses by asking staff to delete it, we
     will do so.  I would not view it as the responsibility of staff to
     make such inquiries, though it would certainly be within the rights of
     any staff member who wanted to.
     
  -  I have to be reasonably sure the request to delete is actually from the
     author.  I wouldn't be terribly hard nosed about this, we'll give people
     reasonable benefit of doubt, but the law actually puts some fairly
     tough requirements on such request - they must have a legal signature on
     them (electronic or ink on paper) and so forth.  So we are within our
     rights to demand reasonable evidence, though I'd not normally actually
     require that all the hoops be jumped through as long as I were satisfied
     with the legitimacy of the complaint.

  -  In the above scenario, if instead of reposting the full original text
     of the deleted response, user B posted a summary in his own words of
     the content of the deleted response, perhaps even with some short
     quotes from the original, then I would *not* honor a request to delete.
     Copyright protects only the exact words, not the ideas, and short quotes
     are "fair use".  (P.S. - this is another reason I'd like to keep a staff
     readable copy of deleted text - so that we can tell if a posted summary
     is the original wording or not.)

  -  In fact, in some instances, when deleting text, I might myself replace
     it with a short summary of what was deleted.  If this were done, clear
     steps would have to be taken to make it obvious that the words were mine,
     not the original author's or the poster's.  I'm not totally sure I'd do
     this, but I'm sure it'd be legal.  Mostly I think this would be best
     done by replacing the original text with a forward reference to a response
     under my own name that includes any explanation I want to make.

I'm not completely sure how to handle a case where a response that was
originally entered in one place on Grex and then gets copied to another place
on Grex, either because the item was linked, or because someone copied a
response from one item into another.  What do I do if the author wants it
revoked from one place, but not the other?

To some degree, I'm disinclined to handle things piecemeal.  Either you gave
Grex permission to publish, or you didn't.  Revoke permission and we'll
delete it entirely from everywhere on Grex.  On the other hand, it might be
silly to fuss about, since if I insist that they have to delete it from
everywhere, then they could do that and then repost it themselves to only
the places they want it to be.  Mostly though, I think having given people
a right to decide whether or not their text is to appear on Grex, we don't
have to give too much credence to quibbles about *where* on Grex a given
piece of text is placed.

Some people have claimed that users should have a right to edit.  I don't
think copyright law does that.  A copyright is on the exact wording of a
document.  I think editing a document would be viewed in copyright law as
destroying one document and creating a new one.  On Grex you would have both
those rights if this motion passes.  There is no particular need for us to
let you place your new document in the same place the old one was.

response 67 of 168:

Nov 8 05:26 UTC 2001

Actually, editting a document creates a "derivative" work under
copyright law.  If the person doing the editting is a different person
than the copyright owner, both people have copyrights on the resulting
material.

response 69 of 168:

Nov 8 23:43 UTC 2001

You better check your facts.  Actually, audio recordings are a special
case; if you make an audio recording of an event, you own the copyright
on *that* recording, which is separate from anyone else's copyright.
Hence, if CNN news makes an audio recording of a speech given by a
politician, they have a copyright on that recording, which is separate
and independent from NBC's recording of the same speech.  This is one of
the reasons why they don't generally allow you to make recordings of
concerts.  Music often has 2 copyrights; one is of the audio recording
and sometimes ends up owned by the performers, although more often it
ends up owned by some giant media corporate conglomerate, the other is
of the music itself.  If you look at pop music at the end of a movie,
you'll often see 2 copyrights per song because of this.  Classical music
may only have 1 copyright because the music has passed into the public
domain.

As a general rule, authors of original creative works that are marketted
commercially do not permit derivative works to be made.  Hence, in your
average book, you will only see 1 copyright notice.  In a few cases,
such as corrections to books, etc., the authors may require you to
assign any rights you have to them before they make use of your
material; this is common with "letters to the editor" in newspaper
columns for instance.  There *are* cases where you will see derivative
works with multiple copyright notices -- for instance, commercial Unix
releases commonly have this because they've incorporated software with
various forms of BSD software in them.

Note that all of copyright law is changing; it's *possible* that DMCA
has somehow fundementally changed the nature of derivative works,
although I've never heard anyone claim this as a feature of DMCA.