Description tag problems.

[LordAdmiral]

This isn't a true bug per se, but it does cause many unwanted difficulties, especially with various hub scripts.

When using certain options, like opening an extra slot if under a certain upload speed, DC++ automatically adds an extra tag to the end of the DC++-generated description (in this case, it is an 'o', as no doubt you know already). Unfortunately, certain hub scripts check for the integrity of this description to see whether the person is using a normal or a modified client. In many cases, these hubs who do not like DC clients other than DC++ or NMDC ban users using otherwise. Thus, a number of people are getting kicked and/or banned for being, well, nicer.

There are two methods of fixing this problem. The first option is to include everything in the automatically generated description. This way, regardless of what feature somebody uses, there will be no extra tags tacked on to the end. The other way is to remove the addition of the extra tags. I don't really condone the latter, as the extra tags are probably as important as the hub and share tags (though most people don't even know they're there). Thus, this is a bug in the sense that it causes unexpected behavior when connecting to certain hubs running certain scripts. It is, in reality, a bug of the scripts themselves. But as it is nearly impossible from the user end to inform every script writer and hub operator that these extra tags exist (and as every user has a potential to be an operator/scripter, that means informing every user), it should really be addressed here, on the development end. At the very least, the next release message should include a little something about the extra tags.

[sarf]

Perhaps adding an option to disable the reporting of extra tags would be useful in the meantime?

Sarf
---
The only real problem in life is what to do next.