The meaning of the ++ tag

What do the DC++-style tags mean?

Notation

The following information appears in the Tag column for every user in the user list of the Hub window: <++ V:x,M:x,H:x/y/z,S:x[,O:x]>, where
V(ersion)
x = client version
M(ode)
x = mode (A = Active, P = Passive, 5 = SOCKS5)
H(ubs)
x = number of hubs connected to where you're not a registered user
y = number of hubs you're registered in
z = number of hubs you're registered as an operator
S(lots)
x = number of upload slots you have open (note that they may be in use already)
O(pen an extra slot if speed is below)
x = if total upload is below this value DC++ will open another slot
This part of the tag is only shown when the option for it is enabled.
The tag is updated every 1-2 minutes if there are changes. Other clients may introduce more tag elements such as L:x or B:x which means usage of upolad bandwith limiter where x is the amount of maximal upload bandwith in KiBs.
History
The DC++ tag was introduced back when the only available Direct Connect client was Neo-Modus DirectConnect (NMDC) v1.0. That particular client could only connect to one hub at a time, which ensured that the upload slots available were assigned to other users connected to that hub. At first, hub owners considered DC++ to be a cheat client, because it could connect to multiple hubs at once. The DC++ tag was introduced so hub owners could check if the users were connected to a reasonable amount of hubs and had enough upload slots available for sharing.
At this point, almost every client, whether it's capble of joining multiple hubs or not, has a similar tag in it's description field. The custom is to replace "++" with some other identifier uniquely identifying the client type (common are "StrgDC++", "ApexDC++" and "PWDC++").

This table is an sample of some of the legact DC++ clients and the tags they impemented.

Client )----------------( Tag )-----------------------------( Information )
DC++ )-----( <++ V:x,M:x,H:x/y/z,S:x,O:x> )-----( V: Client version )
-------------------------------------------------( M: Mode, A = Active, P = Passive, 5 = Socks5
-------------------------------------------------( H:
-------------------------------------------------( x = number of hubs connected to where you're not a registered user)
-------------------------------------------------( y = number of hubs you're registered in )
-------------------------------------------------( z = number of hubs you're registered as op )
-------------------------------------------------( S: Number of slots open )
-------------------------------------------------( O: If the current total upload speed of a user is lower than the number after O:, DC++ will automatically open another slot.

That's why Clients should NEVER have a Custom Tags!! Unfortunately, they have it and now the informations are not accurate from some clients!

Example: <ApexDC++ V:21653,M:P,H:42/0/1,S:3>
Example 2: <Lama V:500,M:A,H:1/0/0,S:15> Hublist Show: <FlylinkDC++ V:r504-x64-21653,M:A,H:30/0/3,S:15>

Only OP Clients should have Custom Tags under the name BOT!
Example: <BOT V:1.1,M:P,H:0/0/1,S:3>
Example 2: <BOT V:0.1,M:P,S:3>
Example 3: <BOT >