Subject: RE: [chairs] OASIS IRC
Jamie et al:
I have used Doug’s work and it is perfect for TC business. The queue mechanism is great.
From: James Bryce
Doug, if I recall correctly, you wrote this.
(Matt did create a similar, queuing-only widget last year, as well.)
Seems like a handy device, and obviously the minor amount of persistence is
helpful. Assuming that it proves feasible -- which is a matter I leave to
our tech staff -- is that code that you would be willing to let OASIS
run? And is there any obvious reason (from the external viewpoint) why we
couldn't? As opposed to hosting on what I assume is a personally owned
branch of some TUCOWS node. The latter is the sort of thing that
our rules encourage us to replace with persistent OASIS resources.
FYI - that chat that Paul is talking about is located at: http://soaphub.homeip.net/conf
Paul Fremantle <firstname.lastname@example.org>
It would be interesting if OASIS could configure their IRC server to allow connections on port 80. Many of us are behind restrictive firewalls with few ways to get through other than port 80. mIRC can proxy via a http proxy, but that disables most features of IRC beyond barebones chat.