-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The objective of login-on-connect is to avoid real-host discovery...
The problem is that most clients have autojoin channels, joining
those channels with make ur host visible. Notify can reveal it too if
u are connected. Login-on-connect waits for X's
What harm or problem would it be to have a command in X for mode +x,
just like autoop? As _KcuTzZ_ said?
It would end the "X lag problem", allow users to "set" the mode only once
on login, and give the users the option to use the mode or not.
stoney`
At 11:56 PM 10/20/2002 -0400, you wrote:
--
> >The UNIX-based clients I've seen use : as field separators in server
> >specifications, i.e., server.name:port:password:other-fields--and
> >yes, I believe some use "other-fields". Thus, ':' is not the best
> >choice for a field separator here :)
>
> That doesn't rule out using the password st
>> You don't understand. wcc:mypass is a valid password string. It would
>> not require client modification. As far as the client is concerned,
>> [[optional server password]:[:]] is ONE
>> password. The server would then parse the password,
>separating it by the
>> ':'. Take a look at how bahamu
On Mon, Oct 21, 2002 at 09:07:21PM +0800, Alex Dawson wrote:
> Also, I would also say that users who use the login-before-connect
> method have +x set by default, while users who login after connect
> have to set +x after logging in. The reason for this is that I think
> we can expect most user
