making AdvancedDCHub private?
Status: Inactive
Brought to you by:
quasireality
Menu
▾
▴
Hello and thank you for creating py-dchub.
About two weeks ago i helped set up a dc-hub for a friend using PrivateDCHub. It only had some minor glitches with UTF-8, but it worked good enough for my friend.
Later, we had a talk about simplifying the administration and the result of that was setting up a second hub using AdvancedDCHub and pysqlite. The advanced bot made things much easier for my friend and he was happy.
Today he called me and had a problem to solve. His problem is that his client software (DC++) reports that he is attached to a public hub when he's connected to the advanced hub. This makes it impossible for him to enter some other hubs because they don't allow logins to clients attached to public hubs. My friend was surprised by this. The advanced hub doesn't allow any file sharing until the user is verified by an operator. Yet his and his friend's clients report that they are attached to a public hub.
Is it possible to solve my friend's problem with the current design of AdvancedDCHub? If so, how?
And what exactly makes a hub "public"?
UTF-8 isn't supported by the Direct Connect protocol, which provides no specification of character set. I'm not sure what the UTF-8 glitches were, but they're probably related to the hub treating everything as ASCII. The hub doesn't block any high-ASCII characters, so the only UTF-8 glitches I can think of is it might truncate a string in the middle of a multibyte character.
I'm not sure why DC++ is reporting that he is attached to a public hub. It may be that DC++ is reporting that you are connected to a server that doesn't require a username and password to login. If that is the case and they want to fix that, they need to either to patch DC++ or have an actual account on the AdvancedDCHub. You could theoretically patch AdvancedDCHub to accept any login/pass and treat that user as a guest unless they had an account, but they would still need to enter a username and password.
Personally, I'm not sure why DC++ would report that information to any other hubs. I can't see how it benefits the users. I can see where it may help misguided hub operators, but as DC++ is a client program I'm not sure why it would go out of they way to help them.