Mark hubs which the user is connected to multiple times

[LoRenZo]

Since it is possible to be connected to the same hub multiple times, I think it would come handy to visually mark the hubs in such cases.
Perhaps the best way would be to use a different (but matching) color for the hub tabs with duplicate connections, because it can be hard to track and filter such connections with the current client revisions.

[eMTee (realprogger)]

Well, generally it isn't possible to be connected to the same hub multiple times unless they're NMDC hubs, you use different nicks and two different hub URLs point to the same hub or the hub accepts connections for the same userbase in multiple ports.
If you know ways to connect to two hubs with absoultely same URL:port simultaneously, then it's a bug in DC++ and it should be investigated as a bug, not a feature request.
If it's not a bug but the above case with NMDC hubs then it's impossible to determine that the two hubs are the same or not, since hubs are identified by their address (URL:port) in DC++ and an NMDC hub identifies the user by their nick.

Note that due to the advanced user identification system this whole scenario isn't possible in ADC hubs at all.

[LoRenZo (lorenzo-mailbox-deactivatedaccount)]

The comment of eMTee actually covers what I was experiencing: I was connected to the same hub through two different URLs and with different nicks in each case.

[eMTee (realprogger)]

Nothing much can be done for this except maybe some optional checking for NMDC users in onUserUpdated for the same IP/Sharesize/whatever data that's advertised in the user information and if there's a match then send a warning status message to the mainchat about the possible multiple hub connection.
But it still wouldn't work well for all cases especially when the hub doesn't spread all the user info.

[poy (poy)]

that is too much effort to work around a deficiency of NMDC.