response 5 of 49:

Dec 17 19:01 UTC 1999

        I don't know, but I'd love to find out. After all, if we can
        suffer animated trash when browsing, there must be a way.

response 7 of 49:

Dec 17 22:32 UTC 1999

        ARGGHHHHH!! "AOL" ACK GAG BLECH HEeeeeelllpp!

response 9 of 49:

Dec 18 02:19 UTC 1999

Yeah, as was pointed out to me (and when I started thinking some) programming
web-party in CGI would be too inefficient.  CGI works well for backend
database or script type programming, but wouldn't scale well to real-time,
multi-user chat we have in party.

Here's what Jan told me (in an e-mail) a week or so ago on the authentication
issue:

"Authentication is a problem.  It should definately
require a Grex login and password.  The mechanism used by backtalk and
web-vote may not be usuable.  If you implement this with a java ap on the
browser, and a server running on Grex, then the server has to be checking the
authentication (it could furn the pwauth program to do so), which means the
java app must send login and password to it.  But even if a user has already
logged into Backtalk, so the browser knows the login and password, the Java
app probably can't get it to send it to the party server.  You may need to
have a separate login box for party, which is ugly.  Maybe we need to rethink
our way of authenticating web users in hopes of coming up with something that
can be used more flexibly.  It would be nice to be able to offer a smoothly
integrated set of web interfaces to Grex." 

Jan also said that is was more tempting now to write a client-server version
of the textual party program, to jell in more smoothly.

And, I agree with John, I don't know of any other way to go than Java on the
front-end.  Java is widely used for this type of application and many more.
One can be near assured there won't be any serious problems with such an
applet, this one at least, as it'll be thoroughly tested before full-release.
Don't be Java-phobic, that's what I'm trying to be say (:  There are many more
eviler evils on the web, many of which you're probably unaware of.

response 11 of 49:

Dec 18 03:38 UTC 1999

One word: kerberos

response 13 of 49:

Dec 18 07:07 UTC 1999

Let's just go SESAME (:  Okay, so who's going to help me set Kerberos up with
both Backtalk and web-party?  By the way, do we have Kerberos source here?

response 15 of 49:

Dec 18 08:35 UTC 1999

Kerberos is an authentication framework designed at MIT as part of the Athena
project in the mid-late 80's for networks, providing a single log-on service.
I won't go into the details of the security architecture, but the basic idea
is someone could log on (let's say a university system) in the morning. 
He/she would not have to re-enter his/her password and username for every
application/system they use.  So, this is good because that person doesn't
have to remember multiple passwords.  There are also other advantages.  SESAME
is a much more complete security architecture, but used Kerberos as the basis
of its authentication framework.  SESAME also has audit and authorization
capabilities within its architecture.   SESAME was developed in Europe, and
whilst undoubtedly a better solution, Kerberos gained more popularity because
it was out there first, and also because the standards organizations are
predominantly made up of Americans - the process of standardization is by far
political rather than technical.
Anyways, this is a very brief overview.  You don't really want to learn all
about these architecture intracacies, but if you want to know more I can give
you plenty of references.

response 17 of 49:

Dec 19 00:34 UTC 1999

I don't think the makeup of the standards organizations has much to do
with what's standardized.  HTML was first invented in europe, as was
Pascal.

response 19 of 49:

Dec 20 04:58 UTC 1999

Perhaps you would care to explain what CCITT stands for?

response 21 of 49:

Dec 20 16:23 UTC 1999

Good.  Now you are prepared to explain the politics behind X.25.

response 23 of 49:

Dec 20 20:29 UTC 1999

I get accused of awful evil things if I do all the typing.

response 25 of 49:

Dec 20 21:01 UTC 1999

        "keatings of text"

        Janc? Why can't a web-party use the same methods as BackTalk?
        (I still have to wonder where the session-ID stuff is sent
        back and stored)

response 27 of 49:

Dec 21 11:51 UTC 1999

There exist Java telnet applets, maybe even free ones.  Would it be
feasible to hack one those so that a user who logs in through it
doesn't go into the telnet queue and would be put in a special shell
rather than their normal shell?  The special shell could be a
restricted version of party that doesn't allow shell escapes.  This
would be a quick and dirty way of providing web-based party that
wouldn't require an elaborate "party server" to be written.