Circumventing maximum slot rules

Most (all?) hubs have a minimum slot ratio which means that you have to have x amount of slots open per hub you’re in. x changes of course depending on hub.

There are a lot of hubs that also have a limit on the amount of total slots opened. That is, x slots can’t override the limit y. This can make people use multiple instances, or use another technique to circumvent this “limit y”.

The technique is to use DC++’s rich feature set to avoid “going beond” y without actually going beond it. As explained in Slots, slots, slots…, there are plenty of slots DC++ have. One of the features, the ‘Open an extra slot if speed is below…’, is the one I wouldn’t recommend to use as a circumvent. Why? Well, sure, it will still accomplish the task (set the option to something really high) but the setting will be broadcasted (in the form of “O:x”) so operators can take action. The second option is to set ‘Mini slot size’ to something really high. This is the preferred way in my opinion. Why? Yes, it will also do the same, but nothing is broadcasted to users (they might notice it if they download from you). I’ve yet to see any hub have a rule against method one, but it’s even more unlikely there’s a rule for the mini slot size.

It’d be really amusing if hubs started checking for “O:x” because of this post…

Why you would need to circument the limit y, I have no idea as y is usually something ridiculous (50+). If you’re in need for that many slots because of the slots/hub ratio, you might want to cut back on the number of hubs you’re in…

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: