[Prev][Next][Index][Thread]

# Re: Regulating Multimedia [Was Re: Pueblo and Java.]

- Date: Sat, 9 Nov 1996 11:17:20 PST
- From:
- cc: moo-cows@parc.xerox.com
- Content-Type: TEXT/PLAIN; charset=US-ASCII
- In-Reply-To: <Pine.SOL.3.91.961108194320.20188A-100000@laurel>

    Well yeh, obviously users need to be able to turn off what comes at them,
    but they can't just turn off offensive stuff.  I mean whos going to want
    to USE the whole multimedia moo thing if they cant use it?  Lemme get
    this straight, ....a user goes into some characters room, and gets
    spammed out by Bimbos on Ice, they are offended, SO they look to your
    options, what do they see? 'turn off multimedia' so they figure heck..i
    dont want to be offended like that again, so I'll just turn it off.
    Eventually who's going to be left using it? The perverts who are the
    cause of this discussion in the first place, thats who.

    slartibartfast

    On Fri, 8 Nov 1996, Michael Brundage wrote:

    > On Fri, 8 Nov 1996, jer wrote:
    > > The only thing that can really be done about it is, like you said,
    > > regulate who (or what ;) has the permissions to send multimedia stuff.
    >
    > This is not true.  There is another way, namely filtering.  A responsible
    > client will provide options to refuse or accept content from other users.
    > Ideally, this includes some server-side support, since otherwise tons of
    > info would be sent to the client (like getting an email spam; mail
    > servers should allow you to turn off the spigot at the server, instead of
    > filling up your inbox and having to rely on your mail reader to filter).
    >
    > This becomes especially important when you take multimedia to the next
    > level, which is directing applications remotely.  Once I have the ability
    > to "fax" you a document through your MOO client by printing it out on
    > your printer, you want to be able to say "Who is this person? Do I really
    > want to let them print something out on my printer?"
    >
    > Although I don't pretend this is an easy thing to do, or that the
    > problem of regulating content (in any media) will ever be fully, perfectly
    > solved, MOO at least provides the flexibility to add those controls,
    > as opposed to other systems.
    >
    > > But as you also said that defeats the whole purpose of MOO.
    >
    > MOO, like duct tape, has a lot more uses than originally intended.
    >
    >
    > michael
    > brundage@ipac.caltech.edu
    >
    >

References:

- Regulating Multimedia [Was Re: Pueblo and Java.]

- From: Michael Brundage <brundage@laurel.ipac.caltech.edu>

- Prev: Regulating Multimedia [Was Re: Pueblo and Java.]
- Next: Re: Regulating Multimedia [Was Re: Pueblo and Java.]
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index