From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IRC
From: forsyth@vitanuova.com
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-gbjlgrqtntduvltqyexndmphze"
Message-Id: <20011128144451.F173819A64@mail.cse.psu.edu>
Date: Wed, 28 Nov 2001 14:51:10 +0000
Topicbox-Message-UUID: 2bf2ba68-eaca-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-gbjlgrqtntduvltqyexndmphze
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

the way i sometimes structure this is similar to acme's: to have the usual connection directory
with clone (or new) and an index.  a ctl request sets a name that shows up in the index.


--upas-gbjlgrqtntduvltqyexndmphze
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <9fans-admin@cse.psu.edu>
Received: from punt-1.mail.demon.net by mailstore for forsyth@vitanuova.com
          id 1006957585:10:02786:130; Wed, 28 Nov 2001 14:26:25 GMT
Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net
           id aa1118025; 28 Nov 2001 14:14 GMT
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id E6DB319A63; Wed, 28 Nov 2001 09:14:13 -0500 (EST)
Delivered-To: 9fans@cse.psu.edu
Received: from devil.lucid (pc1-dale5-0-cust136.not.cable.ntl.com [80.1.76.136])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 9B4CE19A51
	for <9fans@cse.psu.edu>; Wed, 28 Nov 2001 09:13:16 -0500 (EST)
Received: from there (localhost [127.0.0.1])
	by devil.lucid (8.11.6/8.11.6) with SMTP id fASEE2T57818
	for <9fans@cse.psu.edu>; Wed, 28 Nov 2001 14:14:03 GMT
	(envelope-from matt@proweb.co.uk)
Message-Id: <200111281414.fASEE2T57818@devil.lucid>
Content-Type: text/plain;
  charset="iso-8859-1"
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IRC
X-Mailer: KMail [version 1.3]
References: <Pine.GSO.4.10.10111280717010.4127-100000@ultra5c.usask.ca>
In-Reply-To: <Pine.GSO.4.10.10111280717010.4127-100000@ultra5c.usask.ca>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.7
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Help: <mailto:9fans-request@cse.psu.edu?subject=help>
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
Date: Wed, 28 Nov 2001 14:14:02 +0000

On Wednesday 28 November 2001 13:27, you wrote:
> why not do it the plan 9 way, if you're going to write a complete client
> anyway? ircfs? sounds right, doesn it?
>
> $ ircfs <mynick> <myserver>
> $ cd /irc/#mychan1
> $ echo "hi all" >> data
> $ cat topic
> $ ls 				# /who #mychan1
>
> (in a different window)
> $ cd /irc/#mychan2
> $ #...
>
> andrey

irc channel names are invalid plan9 file names

You are now talking on #/\/\/\_Hey_/\/\/\#

http://www.rfc.net/rfc1459.html

I've spent a few hours thinking about it but never came up with an elegant
solution that I liked.
--upas-gbjlgrqtntduvltqyexndmphze--