> Dave, ya right, but there is still an issue within the +x model undernet > will use, issue is a users hosts gets 'hidden' *AFTER* he successfully > authed with X, so that system is actually kinda useless in my opinion.
Future versions of ircu will hopefully allow a user to auth at login. In the mean time, this can be worked around by authing and going +x before joining any channels. > The other fact is that ircu sets the new host by emulating a quit/rejoin of > the user, thus showing quits all over the channels. Kinda irritating if you > got 70k users constantly reauthing etc. I think it will put a hell lot more > stress on the server handling then if you would handle the hostchange > internally, also imagine that clients also have event handlers, some of them > might return output after a join/quit, thus increasing the bandwidth usage > dramatically as well. Handling it internally like other ircd's already do > releases that pressure. This is necessary because we're worried clients might get desynched with respect to host name changes...and many bots probably will. This is also the reason you can't do /umode -x. > Another thing is: why do you actually use > <currentident>@<AC-id>.users.undernet.org and not <AC-id>@users.undernet.org > ? For opers it might become <AC-id>@opers.undernet.org. Either way is acceptable, it's just the way that it was coded when it was submitted. -- Kevin L. Mitchell <[EMAIL PROTECTED]>
