DC++ and registered user are becoming a problem
Moderator: Moderators
DC++ and registered user are becoming a problem
Might not be the right forum, but, b-but but...
More and more hubs offer the "service" to get your nickname registered, so nobody "steals" it. But this is becoming a problem, because dc++ hubs where the user is "a normal user", not hubs where the user is "a registered user" or OP.
I'm currently connected to 6 hubs (OP in one of thus) and the "H" parameter in my description displays 2.
I think it would be more useful if the "H" parameter actually reflected the amount of hubs the user was connected to (or at least all them where the user isn't an OP)
More and more hubs offer the "service" to get your nickname registered, so nobody "steals" it. But this is becoming a problem, because dc++ hubs where the user is "a normal user", not hubs where the user is "a registered user" or OP.
I'm currently connected to 6 hubs (OP in one of thus) and the "H" parameter in my description displays 2.
I think it would be more useful if the "H" parameter actually reflected the amount of hubs the user was connected to (or at least all them where the user isn't an OP)
For the newest release of MulTiBoT visit www.cwain.dk
because dc++ hubs => because dc++ registers hubs
i need a need brain
i need a need brain
For the newest release of MulTiBoT visit www.cwain.dk
Re: DC++ and registered user are becoming a problem
I agree, and all OPs I know. this has been suggested before, but I can't recall any response from arne.FRANKE wrote:I think it would be more useful if the "H" parameter actually reflected the amount of hubs the user was connected to (or at least all them where the user isn't an OP)
please arne? think about it..
(and I agree on OPs keeping the privilege, after all they are in some hubs not for their own leeching pleasure)
http://dc.selwerd.nl/hublist.xml.bz2
http://www.b.ali.btinternet.co.uk/DCPlusPlus/index.html (TheParanoidOne's DC++ Guide)
http://www.dslreports.com/faq/dc (BSOD2600's Direct Connect FAQ)
http://www.b.ali.btinternet.co.uk/DCPlusPlus/index.html (TheParanoidOne's DC++ Guide)
http://www.dslreports.com/faq/dc (BSOD2600's Direct Connect FAQ)
Maybe we could add some kind of extension to the protocol to tell DC++ not to decrease the number of slots - eg. the bot sends $UserIsNotVIP when the hub allows nickname registration? This won't break existing hubs who only allow real VIPs to get their nickname registered, and it's a simple change in the scripts that allow users to register their nickname automatically.
well my hub is private and many of the hubs my users are in are private so this is a major problem for me and many other private hubs i know of
its possible to be in 10 private hubs with 3 slots and get away with it
if you don't have access to all 10 (and the time ) to check them all out your beat
i beg for this to be implemented
mrdylan
its possible to be in 10 private hubs with 3 slots and get away with it
if you don't have access to all 10 (and the time ) to check them all out your beat
i beg for this to be implemented
mrdylan
-
- The Creator Himself
- Posts: 296
- Joined: 2003-01-02 17:15
arne, although I'm very pleased with now getting to see the regged hubs, imho that small h: would further enlarge the already big tag. I think it's quite acceptable to just change behaviour of the H:.
I wonder why registered users were left out in the first place. and now adding a small h seems like a rather ugly solution.
if it is the point that the (un-)registered number of hubs should be shown, then a different format might be more appropriate, like H:x/y/z where x=non-regged,y=regged and z=op. this would contain more info and use the same amount of space.
ender, I don't quite follow. what would this command do?
I wonder why registered users were left out in the first place. and now adding a small h seems like a rather ugly solution.
if it is the point that the (un-)registered number of hubs should be shown, then a different format might be more appropriate, like H:x/y/z where x=non-regged,y=regged and z=op. this would contain more info and use the same amount of space.
ender, I don't quite follow. what would this command do?
http://dc.selwerd.nl/hublist.xml.bz2
http://www.b.ali.btinternet.co.uk/DCPlusPlus/index.html (TheParanoidOne's DC++ Guide)
http://www.dslreports.com/faq/dc (BSOD2600's Direct Connect FAQ)
http://www.b.ali.btinternet.co.uk/DCPlusPlus/index.html (TheParanoidOne's DC++ Guide)
http://www.dslreports.com/faq/dc (BSOD2600's Direct Connect FAQ)
-
- Posts: 147
- Joined: 2003-01-04 02:20
- Location: Canada http://hub-link.sf.net
- Contact:
Keeping the first value after H: for the total amount of hubs might preserve backwards compatibility with old bots. Then showing how many of them are registered or op would let the hub runner fine tune his bot if he wants to grant such users privileges (I do not think that being an op dispenses me to respect hubs rules).
Well my client just counts the hubs you are not an op in (well I think I broke the counter when I did that so it needs to be fixed ) ... it's not all that difficult to change because you need to check the OpList to see if op commands are enabled or not. As an added bonus, $LogedIn can be ignored! (Not much, but it's something )
I would think that most people that are ops are there to "do their duty" and that the bulk of registered users are private hubs, register-nick script, etc. There are exceptions and some people won't like it, but what are they going to do? Go back to NMDC?
I would think that most people that are ops are there to "do their duty" and that the bulk of registered users are private hubs, register-nick script, etc. There are exceptions and some people won't like it, but what are they going to do? Go back to NMDC?