DCBase

I was just wondering, is the ability to redirect a user to another hub purely a client feature, or does the hub software have some role to play?

Redirect is a hub->client protocol, its up to the recieving client (support or settingswise) what to do with the recieved redirect. The hub can ofc choose to disconnect the redirected user after sending the command. The hub can also have support to recieve commands from users (some kind of OP in i asume all hubs) to redirect other users.

Edit: I think this should go under protocol talk

Redirecting goes as a flag in QUI message , in which case the client after being disconnected needs to connect to the specified address. The client needs not to disconnect, the hub must disconnect the user.
So yes, the hub specifies the redirect address ( who else? ) , either if the redirect is a default redirect from the hub or given as a redirect command from some operator.

Ah yes, I'd forgotten about that little RD flag on QUI. Thankyou.

I guess then for redirect to be used on a hub, the hub must have a 'redirect user(s)' user command, since only the hub can be the originator of the actual QUI message. I had better go write one of those

And yes, as it quickly became a protocol discussion, it probably should be moved to the Protocol Talk forum

Your wish is granted

In NMDC, kicks and redirects were done by other users directly using the hub like a dispatcher. In ADC, operators send some redirect/kick message by a hubsoft specific way, then the hub uses the standard protocol message to say to the users they have been kicked. Either like that, either that they have bad fields or do not comply to hub restrictions in which case the hub auto redirects them to some addresses that the hub operators previously defined.