Discuss web gateway help
This page describes the meanings of various icon links that appear on
this gateway (as well as word links that are used instead of icons if
your browser doesn't support inlined images). It also describes how
to make non-public discuss meetings accessible to certain people
using the SSL certificate support in this server.
Links on all pages
Returns to the gateway root page.
Displays this page.
Links in meeting listings
Displays the preceding portion of the listing.
Displays the next portion of the listing.
Displays the listing starting from the first transaction.
Displays the listing of the last transactions in the meeting.
Enters a transaction in the current meeting.
Searches transactions in the current meeting.
Links in transactions
Displays the listing of the current meeting.
Displays the first transaction in the current meeting.
Displays the first transaction in the same chain.
Displays the previous transaction in the same chain.
Displays the previous transaction.
Displays the next transaction.
Displays the next transaction in the same chain.
Displays the last transaction in the same chain.
Displays the last transaction in the current meeting.
Enters a reply to the current transaction.
In some conditions, actions caused by some of the symbols would be
meaningless (e.g., going to "next" from the last transaction in a
meeting). In this case, graphics clients display "inactive" versions
of the icons, and in the text clients, the words are omitted. The
inactive icons look like this:
SSL certificate support
In order to make a non-public meeting accessible only to authorized users
via this gateway, you need to place the daemon.diswww@ATHENA.MIT.EDU
principal on the ACL for the meeting in question, giving it rs
access bits to allow read access or arsw bits to allow read-write
Using the command-line discuss client, this can be done as follows:
discuss: g meeting_name
discuss: set_acl rs daemon.diswww@ATHENA.MIT.EDU
Originally written by
<firstname.lastname@example.org>; gateway rewritten and currently
maintained by email@example.com.