I have noticed that one by one, all of the Undernet servers are moving to 
new code which masks a users server, prevents us regular users from using 
the +s mode, masks general server information in routing synch/de-synch 
messages, and disables the links and map commands.  Perhaps there are other 
enhancements that I have not noticed yet. :)

The advantages of masking server/router locations are obvious, and we 
applaud any such improvements that help enhance security and stability of 
the Undernet.  Thank you ~ :) .

Unfortunately, some of us channel ops used these commands and features to 
keep track of what parts of Undernet were lagged, where splits occurred, etc 
. . .

This allowed us to make good guesses at when a user was legitimately lagged, 
and when they were just ignoring us with ctcp replies turned off.

In a major/lengthy split, I could also move to the other side of a split to 
help in channel in the event that no ops went with the lost servers. . .

If possible, it would be nice to have some new tools to help us keep the 
channels running smoothly too. :)  To that end, I humbly offer the following 
two suggested enhancements for consideration:

1.  It would be nice to be able to have a utility to ping the server of the 
user, regardless of what it is.  This would assist the average channel op in 
determining if there is a *network* lag that is causing a user to be slow in 
responding, or if the user has turned off CTCP replies.

We would not need to know what server it was I think, but just how far away 
it was lag wise. (since it would always be a public server anyway, you might 
provide the server name too ??  That would be *nice* to know sometimes too, 
but opens up the user for some attacks (??), so may be better to keep it 
hidden?  You guys know this stuff far better than us ;) )

2.  It would be nice to be able to see all of the *regular* servers on our 
side of the split.  This information would be invaluable in determining 
where a lost user/channel bot might be found.



On a related note, I noticed that nick collision messages are still showing 
some server/routing information:

*** Chrilith (~[EMAIL PROTECTED]) Quit (Killed 
(*.undernet.org (NewYork-R.NY.US.Undernet.Org <- 
arlington.va.us.undernet.org (nick collision from same user@host))))

(Shown on Amsterdam 22 AUG 01 )

Well thanks for your time and consideration. :)

I hope I have not come accross as a complete nut.  :)

Take care and have a wonderful day

-stephen


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

Reply via email to