thaughts

[Jonte]

The hub works fine for me, i haven't had any trouble at all.
Well, the "+stats" in the "+help"-menu don't get on a new line, but it's nothing...
Here is a feature that you could add as an option:
If a Super User, OP or VIP logs in, DCH++ replaces the [ISP](or just adds it, if he dont have a [ISP]-tag) with the name of the userlevel.

And i would like to add som features to the OpCom-bot, like let the users rate the hub, if it's good or bad, and some other stuff.
But don't know if you want to give out the source.

Anyway, great work with the hub, arne!

Sedulus had some great sugestions aswell.

[Sedulus]

If a Super User, OP or VIP logs in, DCH++ replaces the [ISP](or just adds it, if he dont have a [ISP]-tag) with the name of the userlevel.

can't be done.
the first $Hello recieved is not interpreted as your own name. not by dc++ and not by nmdc. so the nick sent in $ValidateNick stands.
(I tested this with [edit]a modified[/edit]dcrh. I did notice that dc++ does show private messages with a different $To field, whereas nmdc does not, but that's irrelevant)

a solution to that would be that the user itself sees it's original name, and that the other users see (for instance) [VIP] in front of it. this would however cost a lot of cpu cycles, because the hub would have to translate all commands involving a nickname. this would costs way too much cpu cycles, and for what?

if you want your (for instance) VIP's to have [VIP] in front of their name, use a script that disconnects them and tells them to do so.

[Jonte]

Okay, i didn't know the dc-protocol worked that way.
I wan't the hub to run as little resources as possible, so it stays the way it is.

thanks