Order que sources + more.

[floppa]

A) Wouldnt it be great to have easier a better sorting to file sources in download que.
its a problem when your sources reaches a cetain amount.
maybe this then would be a solution.

* make possible to see download speed of souce. (you already download filelist).
* easier sorting and filtering (move up & down, total ban people from accuring as source etc)
* make possible to always add favorite users.
* maybe more options (the time is 3 in the night )

example.
nick (red color, no slots) | move upp | move down
nick (orange color, slots bad speed) | move upp | move down
nick (green color, slots good speed) | move upp | move down

this is just a suggestion but a good one i think.

B) Create a standard Nickname praxis.
* maybe Three letter ISP
* maybe Speed (Up/down)
* maybe City
* Nick
or something so we get a standad on all the hub through out the p2p network.

example.
[BBB | Sthlm] Nick

/magnus

[BSOD2600]

A) Whats wrong with the current system of sorting? 5 different priorities is not enough? As for sorting, how much more logical can they get than displaying the full path of where they are going to be downloaded to? How many files do you have in your download queue this this method becomes a problem?

* Displaying the download speed of a filelist might be handy, but often for those that have small filelists, they download at speeds which are not a true prepresentation of the persons speed. Furthermore, lets say you download the filelist from a person now and dont get a slot until 6 hours later. At the time you got the filelist he had all 4 slots full. Now 6 hours later all slots are free. In this situation, DC++ would have probably dismissed him as a viable/fast source for files. Generally a bad idea.

* A global 'remove user' from the download queue, would be handy.

* Always add fav users? DC++ should automatically find them and add their files already. This feature is not needed.

B) This is not a DC++ issue. This should be addressed per hub.

[GargoyleMT]

There are existing requests in the feature tracker that handle all of your requested additions.

At least, all of those that are likely to be changed.

First-come-first-serve for downloads is likely to change if multi-source ever gets implemented. Naming systems? They're the exclusive domain of the hub. They're VERY ugly, and seem to de-humanize people. "I am not a number."

[floppa]

my idea with a namingconvention for usernames is because of all the different
ideas of how to name a user between all the hubs therefor it would be a lot
easier for all if dc++ should start handling the naming convention.
you still have an oppurtunity to have a personalized username
in sweden we are pretty good att handling it and getting better but in the rest of the
world its still not so good in that front.

for example
if have the swedish ISP "Bredbandsbolaget" (most users of that isp use the prefix [BBB] + username)
i would never download something from another person with no prefix because its often a user with bad upload/download speed but there are people with good speeds also and those you wanna know about and they vice versa.

so with a good namingconvetion it would be easier to find the user in the same network
and when so many people are using it, so why not help them and everyone get a standard.

[GargoyleMT]

my idea with a namingconvention for usernames is because of all the different
ideas of how to name a user between all the hubs therefor it would be a lot
easier for all if dc++ should start handling the naming convention.

But... user tags are ugly. Another solution, such as letting users put their ISP in the connection type, makes much more sense.

I go around introducing myself as Todd, not [Verizon]Todd, or [USA.PA]Todd.