Lee

All you need to do is reduce the number of downloads that can run.. :)

StrongDC++ RC11 has improved performance is this area..

Not bad. Looks a bit dull though.. :)

This is being looked into.

It's up now. Closed.

If you have downloaded over 50MB off a user, give him one point. 100MB, two points, etc.. This probs cannot be stored for every user, so it would only apply for one session. The more points, the large percentage of upload speed they require. Obviously this is a very basic idea.. Another very simple idea would be to give a user more speed if they have uploaded 100MB to you. Maybe this could be configured to the user's preference. I'm not sure how the speed would be detected and distributed.

Combo: So basically you want an option to 'reward good uploaders' which will prioritise them and give more bandwidth to those users. However, I believe this is against DC rules to prioritise users?

Well, I could easily provide you with that source... I have the author's details.

We cannot use any of the code because it's outdated... I heard the author was trying to update the program though..

Kulmegil: We'll work the slot improvement side first, and then maybe introduce your feature at a later stage. Please remind me if it's not in 1.0 Beta..

Old System User A - Person ready to upload the 2GB file and 5MB music files User B - Wants to download 2GB file and started it before User C User C - Wants to download a set of 5MB music files So, how annoying is that? I was User A and realised this must be frustrating for User C since he was waiting 12 hours before eventually receiving a slot for the music. New System Same situation and files as above. User A - Has enabled 'auto-grant user downloading file below 10MB', or allowed one slot for files below 10MB (small file queue) User B - Downloading 2Gb file, losing some speed because User C has started User C - Downloading 5MB music files via User A's small file queue system Later on this situation, User C will finish his files within say, an hour and User B is still downloading the file. Both users are happy because they have a slot, rather than User C waiting until the 2GB file is complete. It depends how we implement this system and how customisable it is. For example, do we have small file slots ontop of regular slots? Option 1: x small upload slots for files below x MB (x being customisable) Option 2: 1 small upload slot for files below 10MB (simple) Option 3: Auto-grant user slot when requesting to download file below 10MB/xMB (only one granted slot available -no more slots granted after one used) Add your comments below.

Phantom DC++ is no longer developed, and therefore has outdated code. :)

You: "Hey, aren't you the guy who shares the new Lost episodes in the hub?" Him: "Sure am. I love to download your latest selection of porn at 3AM in the morning. It kills time.." You: "How come the guy who shares the new Smallville episodes isn't here?" Him: "I think he's waiting them at home, should be sharing them in the hub within 40 minutes." :)

User email validation has been disabled until our host fixes the issue. Fixed and Unpinned: Problem resolved, everyone should get their activation email. :)

If you haven't received your validation email to activate your account do not re-register. Simply request to Re-send your validation email and you should receive it shortly. Not receiving your email? Check your Junk Mail folder... still not? Please post below with your registered username. You MUST have used a valid email address in order to do this. Guests and validating members can post here.

Request 4 is a leeching feature. Request 7 is pointless, filelist hashes change all the time... you'll have too many different hashes of the same username. What do you mean by request 3?

PeerWeb DC++'s old format was number 3, then it switched to number 2 because the way the /me command is written you cannot remove the space between the username and 's to make it "Lee's" rather than "Lee 's". I personally prefer number 1, it's neater and actually makes sense. If you have any suggestions post below, the way number 1 can be formatted can change (e.g. have ratio first).

Both do the same job though Zlobomir, it's just two different ways of performing the task.

What do you mean by 'to stop people spamming'?

slot granting system? You'd have to set it so it only auto - grants x number of slots to files under x MB

Because the small upload slots (basically for filelists) already does this feature... but only for files below 100KB. We need to somehow change this to only apply to filelists and not allow them to change the max file size. The ability to change the size should be moved to the small lots instead, and put at 5MB default. So we have a regular slot, filelist slot, small files slot... all of them being configurable.. I'd say these are defaults: Regular: 2 slots Filelist: 3 slots Small: 1 slot

This website is for ApexDC++, a direct connect client like PeerWeb DC++. There are no movie links available (this place is not like PeerWeb), they just support this site. :mellow:

Added, go vote. Please reframe from the ratio spam posts, just vote.

Moved to Client Discussion. Please wait for a future announcement regarding the development of the client (watch out for StrongDC++'s RC11 release too - when that is out, coding on ApexDC++ will begin). Apex is the highest point, e.g. a tip of a mountain... which is why the current favicon is a mountain (logo to be revised). More detailed information is available here regarding the client's release date. If you want to be notified of future updates via MSN Alerts, then click here. :mellow: