Received: by ATHENA-PO-2.MIT.EDU (5.45/4.7) id AA21432; Mon, 15 May 89 20:08:03 EDT
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA23823; Mon, 15 May 89 20:07:35 EDT
Received: from crl.dec.com by decwrl.dec.com (5.54.5/4.7.34)
	id AA16356; Mon, 15 May 89 15:35:58 PDT
Received: from crl.dec.com by decwrl.dec.com (5.54.5/4.7.34)
	for alens@athena.mit.edu; id AA16356; Mon, 15 May 89 15:35:58 PDT
Received: by crl.crl.dec.com (5.57/Ultrix2.4-C)
	id AA02856; Mon, 15 May 89 18:34:27 EDT
Message-Id: <8905152234.AA15617@cirocco.DEC.COM>
To: alens@ATHENA.MIT.EDU
Subject: Lens in the News
Date: Mon, 15 May 89 18:34:13 EDT
From: Win Treese <treese@crl.dec.com>


------- Forwarded Message

Return-Path: nsb+@andrew.cmu.edu
Received: from DECWRL.DECnet MAIL11D_V3 by crl.crl.dec.com (5.57/Ultrix2.4-C)
	id AA02692; Mon, 15 May 89 17:07:59 EDT
Date: Mon, 15 May 89 17:07:53 EDT
Message-Id: <8905152107.AA02692@crl.crl.dec.com>
From: nsb+@andrew.cmu.edu (Nathaniel Borenstein  15-May-89 1353 EDT)
To: Info-Andrew <info-andrew+@andrew.cmu.edu>
Subject: Re: Bulletin Board Permissions without AFS

I have always felt that a graphical front-end to FLAMES is what is
really needed.  An Information Lens-like tool could very easily produce
FLAMES output, which would be just the ticket.

Other than that, I think others have answered your questions correctly. 
The key point is that posting authorization is enforced entirely from
the FLAMES files; only the actual owner of the bboards needs to have
write permission on the raw database, but it can decide whether or not
to incorporate submitted posts based on information in a FLAMES program.

========================================================================
Received: from ATHENA.MIT.EDU by decwrl.dec.com (5.54.5/4.7.34)
	id AA09957; Mon, 15 May 89 14:08:33 PDT
Received: from ATHENA.MIT.EDU by decwrl.dec.com (5.54.5/4.7.34)
	for crl::treese; id AA09957; Mon, 15 May 89 14:08:33 PDT
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA20439; Mon, 15 May 89 17:07:28 EDT
Received: by po5.andrew.cmu.edu (5.54/3.15) id <AA01977>; Mon, 15 May
89 16:34:30 EDT
Received: via switchmail; Mon, 15 May 89 16:34:18 -0400 (EDT)
Received: from po5.andrew.cmu.edu via qmail
          ID </afs/andrew.cmu.edu/service/mailqs/sq2/QF.kYPl7he00Vs1E1G044>;
          Mon, 15 May 89 14:07:44 -0400 (EDT)
Received: from larimer.andrew.cmu.edu via qmail
          ID </afs/andrew.cmu.edu/service/mailqs/q005/QF.wYPkyay00Uk4I0v05o>;
          Mon, 15 May 89 13:58:00 -0400 (EDT)
Received: from larimer.andrew.cmu.edu via qmail
          ID </afs/andrew.cmu.edu/usr2/nsb/.Outgoing/QF.oYPkuGi00Uk400ZvFS>;
          Mon, 15 May 89 13:53:23 -0400 (EDT)
Received: from
Messages.7.3.N.CUILIB.3.45.SNAP.NOT.LINKED.larimer.andrew.cmu.edu.rt.r3
          via MS.5.6.larimer.andrew.cmu.edu.rt_r3;
          Mon, 15 May 89 13:53:22 -0400 (EDT)
Message-Id: <EYPkuGe00Uk4Q0Zv9c@andrew.cmu.edu>
In-Reply-To: <IYO2Rzz0-cs295UGNW@icase>
References: <0YLTONy00UkM0150cY@andrew.cmu.edu>,
	<oYNRPTz0-cs2IWUElx@icase>,
	<sYNV7yy00UkM47GEhf@andrew.cmu.edu>,
	<8YNlOLy00VsL8=bp4m@andrew.cmu.edu>,
	<IYO2Rzz0-cs295UGNW@icase>

------- End of Forwarded Message