I agree. Original message follows.
On Thu, Jun 12, 2003 at 09:52:18PM +0100, Chris Crowther wrote:
> On Thursday 12 Jun 2003 9:30 pm, you wrote:
>
> > channels should be listed with the channel name clearly shown... and either
> > display the topic, or show "" (or something similiar) in
> > it's
CHANMODEPRIV syntax:
chanmodetoken = "CHANMODEPRIV=" chantype level ":" modes [,chantype level
":"
modes[,...]]
chantype = character defined in CHANTYPES 005 token
level = mode character defined in PREFIX 005 token
modes = mode character(s) defined in CHANMODES 005 token with the addition
of
"+","-
X-Scanned-By: MIMEDefang 2.29 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by trek.sbg.org id h5IE9neY011311
>>On Tue, 17 Jun 2003, Radium wrote:
>>
>> Hello,
>> I had an idea that would help channel operators fight s
Radium said:
"Basically, for the servers, the user never left the channel (thus does not
lose the @). The client-server protocol would not change and for the users
on the channel, it would look like a real PART, JOIN, MODE +o sequence."
Basically like '/mode nick +x' does at the moment onl
I think he is talking about extending the server-server protocol, so
that *servers* only get/send 1 cycle command instead of 3
JOIN/PART/MODE. On recieving a cycle command each server still sends
out 3 JOIN/PART/MODE to each of the affected clients (but one).
But in reality the bandwidth savings o
Umm... if the clients dont see the user parting/joining the channel, how
exactly are the on-join spammers going to send them a message.. on join?
GK
On Tue, 17 Jun 2003, Radium wrote:
> Hello,
> I had an idea that would help channel operators fight spamming
> on their channels. I suggest
Dear Sir/ Mdm.,
Please find below a brief summary about the Company, Tricubes Computers Sdn.
Bhd.
Tricubes was founded in 1995 to spearhead the design and development of
handheld computers and software solutions to read and authenticate the
Malaysian ID card, a project involving the implementation